Hidden reuse
A shared block or embedded procedure can affect several publications even when its filename never changes.
Engineering change impact
Engineering changes should not create a manual rewrite project
TwinWorks shows where explicitly referenced parts, tools, sources, and procedures are used. Documentation teams can scope the review, prepare changes, and keep authorized experts in control of the approved revision.
Start with one changed identifier and one real manual or procedure set. No generic sales presentation.
The documentation blast radius
The hard part is finding every place the old fact still lives
A changed component can appear in a maintenance step, a tool list, a safety note, a training module, and an embedded procedure. Email and folder search find words; they do not reliably show how controlled content is related.
Broken references
Deleted, unpublished, or changed source material can leave a document pointing at stale or missing content.
Approval ambiguity
A detected impact is not an approved correction. The responsible expert still needs to judge technical meaning.
A controlled workflow
Move from a changed reference to an approved revision
The current product evidence supports semantic where-used and conflict analysis. It does not support pretending that an arbitrary CAD upload can rewrite every downstream document autonomously.
- Name the changeStart with the affected part, tool, consumable, source, or procedure relationship.
- Find where it is usedSee the modules and blocks that explicitly reference that item.
- Review conflictsSurface broken references, stale embedded procedures, and shared dependencies.
- Prepare the editAuthors and assistants prepare a reviewable proposal without self-applying approval.
- Approve a revisionReviewers comment or request changes; an authorized approver creates the revision.
Expert control
Impact detection is not technical authority
TwinWorks can narrow the review surface. It cannot decide whether a changed torque, warning, sequence, or configuration is safe. The accountable expert remains the decision-maker.
What “AI-assisted, expert-approved” means
Assistant suggestions can be applied or dismissed. Reviewers can anchor comments, request changes, endorse, reject, or approve. Approval materializes a new revision.
- Trace the source: retain the relationship that explains why content was flagged.
- Separate finding from fix: an impact hit starts a review; it is not an autonomous edit.
- Preserve review history: use comments, diffs, block provenance, and checkpoints to understand the decision.
- Validate scope in a pilot: measure how many known impacts the relationship model finds on one real change.
A useful first evaluation
Map one change your team already understands
Use a closed engineering change with a known documentation outcome. That gives both sides a factual way to test coverage, false positives, review effort, and the path to an approved publication.
Bring
A changed identifier, its source context, and the manuals or procedures your team knows were affected.
Measure
Discovery time, known-impact coverage, irrelevant hits, review effort, and approval handoffs.
Decide
Whether explicit relationship coverage is strong enough for the next product family or publication set.
Continue the evaluation
Connect impact discovery to control and publishing
Engineering-change documentation FAQ
What is documentation change-impact analysis?
It is the process of finding manuals, modules, blocks, and procedures that reference a changed product source, part, tool, consumable, or embedded procedure, then deciding which content needs review.
Does TwinWorks approve documentation changes automatically?
No. TwinWorks can identify affected content and prepare suggestions. Reviewers comment, request changes, endorse, reject, or approve; an authorized approver creates the approved revision.
Can TwinWorks analyze any uploaded CAD revision automatically?
The current verified workflow is relationship-based. It shows where explicitly referenced parts, tools, sources, and procedures are used. A universal CAD-revision-to-documentation blast-radius workflow is not a current public claim.
What should we test first?
Choose one closed product change whose documentation impact your team already knows. Compare known-impact coverage, irrelevant hits, review time, and the approval path.
See the real review surface of one product change
Bring a known change and the documents it affected. We will map the relationships, show the current product boundary, and define a credible pilot.