Existing procedures may look complete in a PDF yet leave the conversion team uncertain about step boundaries, illustration ownership or revision history. The job is to turn that material into a maintainable authoring project, not just reproduce its pages. We use a representative sample to establish what can be reused and where an author must resolve gaps.
The work starts with the publication owner and engineering lead
This service is for publications managers, manufacturing documentation teams and OEM suppliers with existing procedures. Engineering and PLM leads join the scope discussion when geometry or product structure forms part of the proposed delivery. The publication owner identifies who can accept the content and who will maintain it after handover.
Dakota is listed in Cortona3D's authorized reseller directory for the United States and Canada. That listing establishes our reseller status, not acceptance of a particular conversion or program deliverable. Cortona3D reseller directory
The target project determines the conversion mapping
We scope selected Word, FrameMaker or Flare sources for conversion. PDF and existing XML can also enter the assessment. A reference PDF shows the intended presentation; the source assessment establishes which content and relationships can become editable objects in the agreed project.
RapidAuthor is a modular suite that reuses CAD for publications and supports HTML5 and PDF outputs. We therefore select the target module and inspect the available geometry before agreeing the deliverable set. A product's output options do not establish whether a particular source is ready for conversion. RapidAuthor
We record missing source structure and uncertain technical meaning as exceptions. An unresolved instruction stays visible for review rather than becoming an apparently finished procedure.
The sample tests difficult content and a later revision
Choose a procedure family that exposes the real work. Include straightforward content alongside difficult tables or callout relationships. Include a revision example with enough source history to show what changed and what should remain untouched.
We propose accepting the mapping only after that revision has passed through the editable project and its outputs. A matching initial publication can hide a mapping that fails during maintenance. The review should separate conversion defects from source defects so the production team does not repeatedly investigate the same ambiguity.
The inputs establish content ownership and acceptance
For the scoping review, assemble the following material:
- Representative source files with reference PDFs and the intended procedure or manual type.
- Available geometry and source illustrations, with part identifiers and callout conventions.
- The target RapidAuthor version and authoring model, including any Teamcenter context.
- The contracted S1000D issue and applicable program rules where S1000D delivery is in scope.
- Required outputs and applicability cases, with named review owners and accepted examples.
Do not infer the S1000D issue from the tool choice. For Army work, the cited MIL-STD-3031 record identifies business rules applying S1000D Issue 4.2 within its stated acquisition scope. Establish whether those rules apply to the contract before approving the mapping. MIL-STD-3031 record
The handover includes the mapping and unresolved decisions
The scoped sample delivery pairs editable content with evidence that explains how it was converted:
- A source inventory, conversion mapping and exceptions register.
- A representative RapidAuthor project with source-to-target traceability.
- Review records for references and callouts, with illustration and applicability decisions.
- The agreed published outputs and a production scope based on the sample findings.
Production batches and maintenance support are separate scope decisions. Handover instructions should identify how to repeat the conversion and publication steps. They should also identify which exceptions need engineering approval rather than an editorial correction.
Teamcenter changes the revision path that must be tested
RapidAuthor for Teamcenter connects publications authoring with engineering geometry and bills of materials. Its listed capabilities include S1000D and multilingual publishing. Those capabilities make the engineering-to-publications handoff part of the sample when this architecture is selected. RapidAuthor for Teamcenter
We scope source transformations and publishing components around the actual content. The sample review then checks the agreed revision path, including who releases the engineering source and who approves its publication use.
Acceptance checks maintainability as well as appearance
We propose agreeing these acceptance checks before production:
- The sample opens in the target environment and the receiving author can edit it.
- Source content designated for retention is accounted for; unresolved interpretations remain recorded.
- Part identifiers and callouts reconcile with the selected source evidence.
- References and selected applicability cases produce the expected content.
- The revised outputs pass the agreed structural and visual checks, followed by task review.
Record environment access and source cleanup as delivery dependencies. Geometry readiness and unresolved program decisions also belong in that record before committing to production scope.
A real sample establishes whether the work is ready
Start by deciding what must remain editable, which outputs must match and who accepts the result. Treat PDF reconstruction as work to assess, not an assumed automatic import. Bring a representative source, its required output and the delivery approver to a conversion workshop.
Sources
- Authorized reseller directory — Cortona3D, date not stated
- RapidAuthor — Cortona3D, date not stated
- MIL-STD-3031 Army Business Rules for S1000D — US Defense Logistics Agency / ASSIST, 2025-07-31
- RapidAuthor for Teamcenter — Cortona3D, date not stated