Your customer. A defined delivery team.

The engagement model names who owns the work

Partner managers and delivery directors can bring us a bounded publication work package rather than an open-ended staffing request. The scope may cover conversion, publication integration or continuing operations. We propose an engagement model that makes customer contact and acceptance ownership explicit.

• Referral. Dakota qualifies and proposes the delivery scope. The handoff records the introduction, account contact and route for opportunity updates.
• Joint delivery. The parties name the lead contractor and divide the work packages. A shared acceptance plan records the customer-facing team and escalation route.
• White-label subcontract. The partner keeps the customer contract and agreed branding. The subcontract defines Dakota’s inputs, evidence and communication boundaries.

These are proposed working arrangements, not assumptions about an existing agreement. We settle the model before exchanging customer material or making delivery commitments.

A sample makes the delivery boundary visible

A useful sample contains the difficult content, not just the cleanest page. We use it to expose mapping decisions and missing inputs while the scope is still small enough to change.

• RapidAuthor conversion. The proposed package covers a source inventory and representative conversion. Handoff evidence includes reference checks, illustration checks and an editable deliverable, followed by a production estimate.
• Teamcenter publication handoff. We scope an interface agreement and representative engineering change. The sample connects configured output to acceptance evidence and an operating runbook.
• Arbortext migration. We inventory customizations and separate authoring decisions from composition decisions. The sample includes editable content and a comparison against the agreed reference PDF.

For a Teamcenter scope, Siemens describes tracking reused objects and their parent documents, including referenced fragments. That gives the sample a concrete test target: follow a changed fragment through the agreed publication path rather than treating an export as proof of a complete handoff. Siemens content reuse

Source readiness is part of qualification

We ask for the source package and required output alongside the person authorized to accept delivery. A PDF alone leaves questions about editable source and rights to reuse material. Qualification records those questions instead of hiding them inside the conversion estimate.

• Representative source files with referenced graphics and linked content.
• The program’s specified S1000D issue and supplied business rules.
• Target environment details and an agreed route to platform access.
• Reference output and known defects that affect acceptance.
• Review ownership and the proposed support handoff.

We distinguish supplied program obligations from proposed delivery checks. Missing rules or inaccessible systems become scope decisions for the partner and customer, not silent assumptions made by the conversion team.

Technical authority and acceptance authority are separate

The person who approves a mapping may not be the person who accepts the publication. We record both roles in the responsibility matrix. We also name who resolves source defects and who approves changes to the agreed scope.

The statement of work captures branding and customer communication boundaries. It also records review windows and escalation handling. Any capacity reservation or response commitment belongs in the engagement terms rather than in a general service description.

The handoff includes evidence as well as content

The proposed delivery package includes the approved sample and editable assets. It also carries the mapping decisions and unresolved exceptions so that the receiving team can distinguish accepted behavior from deferred work.

• Source-to-target mapping with decisions about references and illustrations.
• Validation reports tied to the agreed rules and test environment.
• Published output with recorded comparison findings.
• A revision record and runbook for repeating the demonstrated process.

Tool scope stays explicit. Oxygen documents schema validation and data module PDF/HTML publishing in its S1000D Framework add-on; we treat full-publication and common source database acceptance as separate scoping questions. Oxygen S1000D Framework

Antenna House documents PDF composition from XML or HTML using XSL-FO or CSS. We scope composition around the selected configuration and reference output rather than treating engine capability as customer acceptance. Antenna House Formatter

A revision proves more than an initial conversion

Our proposed acceptance sequence starts with the mapped sample, then introduces an agreed source change. We regenerate the affected output and compare the result. The evidence records what changed and any manual intervention.

This sequence exposes a common delivery gap: an initial conversion can succeed while responsibility for repairing references remains unclear. We resolve that ownership before using the sample as the basis for production scope.

Published experience and sample evidence serve different purposes

Dakota is listed among Oxygen XML consulting partners under training and consulting. That is a documented relationship, not proof of acceptance for a particular customer environment. Oxygen consulting partners The engagement sample supplies the environment-specific evidence.

Bring a real source sample, the required output and the acceptance owner to a scoping workshop.

Sources

• Reuse content easily with Teamcenter Technical Publishing — Siemens, 2023-07-05
• S1000D Framework add-on — Syncro Soft / Oxygen, publication date not supplied in the brief
• Antenna House Formatter V7 — Antenna House, publication date not supplied in the brief
• Oxygen XML partners — Syncro Soft / Oxygen, publication date not supplied in the brief