Market · 2026-09-15

Canadian supplier publication readiness

We help Canadian supplier publications managers and engineering leads turn contract documents into a defined publication delivery scope. The work produces a requirements-to-check matrix, an assessed sample and an acceptance evidence package before production begins.

A supplier can have usable maintenance content and still lack an agreed basis for publication acceptance. The immediate job is to establish which rules govern the delivery, map them to checks and test a representative package. We scope correction and production from that evidence rather than treating conversion as the starting point.

Publication readiness is a shared delivery decision

This work is for publications managers preparing a supplier handover and engineering leads responsible for the source behind it. It also gives the customer's acceptance owner a concrete package to review. The useful outcome is an agreement about what will be delivered and how acceptance will be shown.

Dakota is listed in Cortona3D's official authorized reseller directory for both the United States and Canada. That listing establishes our regional reseller presence; it does not establish approval for a particular defense program. Cortona3D reseller directory

We propose a delivery sequence built around a scoped sample, an agreed mapping and a demonstrated revision. Production follows once the sample has exposed the decisions that affect repeatable work.

The consultation is context rather than a contract

DND/CAF consultation W6381-26-0007 described proposed layered business rules and asked suppliers about compliance. It was explicitly not a bid solicitation and closed on September 10, 2025. Its possible January 2026 implementation date is not evidence that a blanket mandate took effect. DND/CAF consultation

We begin the assessment with the customer's current contract and the guidance it invokes. We record document versions and ask the acceptance owner to resolve unclear status. A consultation document can identify questions to ask, but we do not use it to fill gaps in the delivery agreement.

Rules from another jurisdiction are not a substitute. For example, MIL-STD-3031 applies Army business rules to S1000D Issue 4.2 within its stated acquisition scope. That specificity illustrates why an issue and its applicable rules belong together in the assessment. It does not make those Army rules applicable to a Canadian package. ASSIST MIL-STD-3031

A representative package makes qualification useful

The qualification review works best with real source material and a named acceptance owner. We request the following inputs so that open decisions become visible before conversion starts:

  • The contractual deliverable and specified issue, with applicable national guidance and project business rules.
  • A representative source package with its graphics and known findings.
  • The expected PDF or IETP output and details of the receiving environment.
  • Configuration cases that expose differences in applicability or content.
  • The review process and delivery milestone, with the person authorized to accept the package.

We select the sample for the decisions it tests rather than its appearance. A clean procedure alone may leave illustration handling or configuration differences untested. Where an input is missing, we record the gap and its effect on scope instead of silently choosing a rule.

The delivery scope links findings to evidence

We define the work around artifacts that the supplier and acceptance owner can inspect. The proposed scope includes:

  • Requirements-to-check matrix. Each agreed rule maps to a check and expected evidence, with unresolved interpretations kept visible.
  • Representative assessment. Findings identify the affected source or delivery item and explain the correction needed.
  • Agreed conversion or correction work. Mapping decisions and findings dispositions establish what changes and what remains outside scope.
  • Publication outputs and acceptance evidence. The package pairs the agreed outputs with check results and review decisions.
  • Production and maintenance scope. Sample results define the repeatable work and the decisions still awaiting customer review.

Automated checks and human review have separate places in this scope. We avoid treating a check report as the whole acceptance record. The receiving team's review of the output remains a distinct activity in the proposed delivery plan.

A revision tests more than an initial publication

Our proposed demonstration carries the sample from source through the agreed checks and into the receiving environment. Review findings return to the affected content so that their disposition remains traceable.

Before scaling production, we then demonstrate a controlled revision. The acceptance owner can compare the changed source with the resulting publication and examine whether the delivery evidence identifies the change. This tests a different question from whether the initial package looks correct: can the team repeat the handover after engineering changes?

We use the demonstration to settle mapping decisions and separate routine correction from unresolved interpretation. Illustration work and output profiles inform the production scope. Review responsibilities and maintenance handover are agreed alongside them, rather than left until final delivery.

Bring a real source sample, the expected output and the acceptance owner to a publication readiness workshop.

Sources

Start with a real sample

Bring one representative procedure or data module. We scope the work against your contracted S1000D issue and business rules, then quote production.

Book a workshopContact