Published

Engineering approves a revised assembly. One plant will adopt it on January 5; another will continue the earlier configuration until January 12. Quality has approved the new work instruction. A link labelled “latest instruction” is now too vague: staff need the instruction authorised for the product configuration they are actually making.
Quality document control usually complements product lifecycle management (PLM). Keep product structures and engineering-change authority in the system chosen for those responsibilities. Place controlled instructions in the application that meets their review, release and access requirements, which may already be the PLM. If FormKiQ holds that document lifecycle, connect the exact release to the product and plant scope that permits its use.
PLM products can include document management, approvals and manufacturing instructions. PTC describes Windchill capabilities for product structures, engineering changes, CAD data and manufacturing process planning. Siemens describes Teamcenter document management and work instructions aligned with product configurations and design changes. These responsibilities can share one platform.
This can fit when its licensed capabilities and configured workflows meet the required instruction review, plant access, release, history and retrieval needs. Demonstrate those paths with the people who use the instructions.
This can fit when controlled documents also serve quality, operations or other departments, or require a different application experience or deployment boundary. Define the document application's responsibility and the product context it must receive.
A separate document application needs a clear purpose. Replacing PLM's part structures or engineering authority with a collection of PDFs would discard responsibilities that document storage alone does not perform. Equally, adding another repository is unnecessary if the existing PLM already meets the operating requirements.
| Record or decision | Responsible process | Connection to retain |
|---|---|---|
| Product definition | Engineering manages parts, configurations and the bill of materials in the selected PLM. | The product and configuration that an instruction covers. |
| Engineering change and applicability | The authorised change process decides the approved product change and where and when it applies. | Change reference, affected configuration, plant scope and applicable date or other changeover condition. |
| Controlled instruction | The document owner and controller manage the exact content, review decisions and permitted release. | Document identity, approved revision, release conditions and earlier revisions. |
| Readiness and actual use | Production and quality confirm the agreed prerequisites and retain the operational record of what was used. | Accepted readiness evidence and the instruction revision associated with the production activity. |
Engineering approval and instruction approval answer different questions. The first authorises the product change; the second accepts the proposed document content. Decide how those decisions, operational readiness and the applicable changeover condition combine before staff use the changed instruction.
Carry the authorised product change, configuration and plant context into the instruction review.
Retain the exact instruction revision and the prerequisites governing its use.
Return the released revision, applicable scope and any unresolved conditions to the change owner.
A PLM change should be able to identify its connected instructions and whether their required work is outstanding. The document view should identify the product context behind the revision. Keep drafts, approved content and permission to use a release distinguishable in both views.
If an integration update fails, show the unresolved relationship and its owner. A failed status handoff should not make a draft appear released or erase an already accepted release. The safe-retry guide covers uncertain and repeated updates; apply those controls to the agreed integration.
In this fictional manufacturing process, change ECO-882 introduces a revised fastener configuration for assembly P-300. The approved plan starts that configuration at Winnipeg on January 5 and Brandon on January 12. Work instruction revision 7 covers the new configuration; revision 6 covers the earlier one.
Engineering retains the approved change in PLM. The connected document process identifies the work instruction and inspection plan affected, with their product, configuration and plant references.
The document owner prepares revision 7. Reviewers assess its content against ECO-882 and the associated product information. The controller retains those decisions and the prerequisites for using the revision.
Quality approves revision 7 before January 5. Winnipeg completes its agreed readiness checks for that date. Brandon continues the earlier configuration under its authorised plan until January 12. The configured document view selects the instruction for the plant and configuration, rather than substituting revision 7 everywhere because it is newest.
The receiving PLM view incorrectly shows Brandon's instruction change as complete for January 5. The owner identifies the mismatched plant/date relationship, corrects it through the agreed process and verifies both views. The affected work waits if its authorised configuration and instruction cannot be confirmed.
After Brandon's authorised changeover, both plants can resolve revision 7 for the new configuration. Earlier production records retain the instruction revision actually used, alongside the relevant product context. Later changes do not replace those historical relationships.
These dates and release rules illustrate a configured process. The retraining guide explains how to assess a changed task and record any required learning. An acknowledgement of the instruction remains separate from evidence of competence or an operational record of its use.
Give authorised staff a direct route to the instruction for their work. Preserve the earlier revision and the records establishing its past use. The controlled-revision guide explains why a saved file version and an authorised release are different.
Set document access for the relevant departments, business uses and, where applicable, customer tenants. A link from PLM supplies context; access to the document still needs the configured permissions. Retain the required history when product structures or application interfaces change.
Keep document control in PLM where it meets the requirements. Use a connected FormKiQ document workflow where it has a defined role, with engineering authority and product configuration remaining clear. Prove the boundary with one product change whose instructions become usable at different plants on different dates.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.