A supplier can prepare a publication package without resolving how the receiving organization will accept it. The gap may sit in the selected business rules, the configuration being delivered or the evidence attached to the handoff. We scope the work around that gap: establish the delivery basis, correct a representative sample and demonstrate its revision before defining production.
The job connects publication work to acceptance
This work is for publications managers responsible for supplier deliveries and engineering leads responsible for the source handoff. It also involves the receiving organization's acceptance owner. Each brings a different question: what content is ready, which configuration it describes and what evidence supports release.
Our proposed scope joins content correction to publishing and handoff checks. It separates defects in the supplied material from unresolved decisions about the delivery requirement. That distinction gives reviewers a useful choice: approve a correction, clarify a rule or accept a documented exception through the customer's process.
The controlled requirement sets the delivery basis
The UK Military Aviation Authority's RA 5815 publication provides a starting point for rule discovery. Issue 5 cites DEF STAN 00-601 Part 1 for AIR S1000D business rules. That citation identifies a relevant standard; it does not establish the complete requirement for a particular supplier package. MAA RA 5815
We use the customer's controlled requirements to establish the applicable issue and project tailoring. For access to defence standards, the official route is the Ministry of Defence's Defence Standardization guidance. UK Defence Standardization
In the assessment, we record unresolved differences between the contract and the supplied rules rather than silently choosing a preferred interpretation. A conversion decision made before that clarification can become repeated correction work across the package.
A useful sample includes its acceptance context
For qualification, we ask for material that exposes the handoff rather than only the cleanest source file. The proposed review set includes:
- The contractual deliverable and applicable specification issue, with national guidance and project business rules.
- Representative source content and a delivery package, including graphics and known findings.
- The requested PDF or interactive electronic technical publication output and access details for the receiving environment.
- Configuration cases that show which content belongs in each delivery.
- The acceptance owner and review process, with the planned delivery milestone.
- An engineering change that can be followed from source through the revised publication.
If an input is unavailable, we mark the assessment boundary. For example, an output can be inspected without a receiving-system trial, but we would not present that inspection as evidence of a successful handoff.
The agreed package includes content and its evidence
We define deliverables from the sample findings rather than treating conversion as the whole job. The proposed package contains:
- A requirements-to-check matrix linking each agreed check to its source and evidence.
- A representative assessment distinguishing content defects from rule questions and environment constraints.
- Agreed conversion or correction work with a findings disposition.
- Publication outputs tied to the assessed source and configuration.
- A handoff record showing completed checks and open decisions.
- A production and maintenance scope based on what the sample demonstrated.
For each finding, we propose recording the affected item and the decision owner alongside the disposition. A closed finding then points to evidence or an approved decision, not merely a changed status. Work outside the sample's coverage remains visible in the production scope.
A revision test makes the sample useful for production
Our proposed acceptance demonstration starts with the agreed sample in its intended output. Reviewers compare it with the selected configuration and inspect the recorded findings. We then follow an engineering change through the same content and repeat the relevant checks.
The revision test asks whether the changed source reached the correct publication content. It also checks whether related graphics and references still make sense. The acceptance owner reviews the revised output in the receiving environment when that environment is available.
This sequencing separates an attractive initial publication from a repeatable delivery process. If a change depends on an undocumented manual repair, the production scope can name that work before it becomes a recurring handoff problem.
Qualification establishes the scope without implying approval
Dakota is listed among Oxygen XML consulting partners under training and consulting. Oxygen XML partners That listing is not evidence of UK regulatory approval or acceptance of a customer's publication package.
We qualify the delivery work through the sample and its review record. Rule maturity and source quality shape the correction scope. Illustration work, output profiles and review cycles shape the production plan. Open acceptance questions remain explicit rather than being hidden inside an authoring estimate.
Bring a real source sample, the required output and the acceptance owner to a delivery workshop.
Sources
- Regulatory Article RA 5815 Instructions for Sustaining Type Airworthiness — UK Ministry of Defence / Military Aviation Authority, 2025-11-28
- UK Defence Standardization — UK Ministry of Defence / Defence Equipment and Support, 2024-01-30
- Oxygen XML partners — Oxygen XML, publication date not stated