TwinWorks supports document-grounded drafts, expert review and approved technical-document revisions. Authors create or review visual work instructions on imported models and publish reviewed content for its intended use. That is much of the day-to-day work behind two parts of ISO 9001:2015: clause 7.5 on documented information and clause 8.5.1 on controlled conditions for production and service.
Below, each requirement is mapped to what TwinWorks does today, followed by a short note on AS9100 for aerospace and a list of what stays with your quality management system (QMS).
Clause 7.5.2: creating and updating documented information
When documents are created or changed, ISO 9001 asks that they are clearly identified, kept in a suitable format and language, and reviewed and approved as fit for purpose before use.
- Drafting: TwinWorks can draft procedure text from reference PDFs and import PDF or Word manuals as editable technical-document drafts. Imported models support visual authoring and CAD-aware assistant proposals; authors review the steps and 3D actions.
- Review: reviewers comment directly on the content, request changes or approve. Nothing is published until an expert approves it.
- Approval: each approval creates a new revision, so the approved state of every document is on record.
- Language: approved content can be translated, and the translation goes back to a reviewer.
Clause 7.5.3: controlling documented information
Control means the right version is available and fit for use where and when it is needed, protected against misuse or loss of integrity, and managed through distribution, access, storage, version control, retention and disposal.
- Availability where needed: approved content is published to the web and as PDF, and reviewed procedures open step by step at the point of use.
- Version control: TwinWorks tracks revisions, shows what changed between them, keeps the history of each content block and saves draft checkpoints. Restoring earlier work creates a new checkpoint instead of overwriting history.
- Protection: approved revisions are locked; any later edit starts a new draft that needs approval again.
- Retention: earlier revisions stay in the document history. How long you keep them, and how printed or downloaded copies are withdrawn, is set by your own procedures.
Clause 8.5.1: controlled conditions on the shop floor
Clause 8.5.1 asks for production and service to run under controlled conditions. Three of the conditions it lists depend directly on work instructions:
- Documented information that defines the work and the expected result: each reviewed procedure shows the action for every step with the 3D view of the part, highlights and annotations, exactly as your experts approved it.
- Competent people: the same reviewed procedures can be reused for training. Qualification and competence records stay in your QMS.
- Actions to prevent human error: clear visual steps at the point of use are one of those actions. Execution records then show how each run went: step status, duration, comments and optional photos, exportable as PDF, Word or Excel for quality review.
When the product changes
Clause 8.5.6 asks you to review and control changes to production or service, and to keep a record of the review, who authorized the change and the actions it required. When an engineering change arrives, TwinWorks flags the content it touches through the links between parts, procedures and documents: the footprint of the change. Your experts review and approve each update. See how TwinWorks maps the footprint of an engineering change.
AS9100 for aerospace
AS9100D, the quality management standard used across aviation, space and defense, contains ISO 9001:2015 in full and adds aerospace requirements, so clauses 7.5 and 8.5.1 apply as described above. One addition matters directly for documentation: configuration management (clause 8.1.2), which keeps the product configuration identified and controlled throughout its life. Manuals and work instructions are part of that configuration, so they have to follow every approved change. The change footprint and revision history in TwinWorks relate to that work; configuration identification, change authority and status accounting stay in your configuration management process.
Where to start
Pick one procedure your auditors have asked about, or one that changed recently. Check who approved it, which revision is in use on the floor and how you would show that in an audit. The free starter kit gives you a documentation structure, a review checklist and a revision log to work through it. To see how reviewed procedures and execution records work on inspection tasks, read TwinWorks for quality control.