SOLIDWORKS Composer and PDM: Change-Controlled Shop-Floor Work Instructions

Define the instruction as a controlled document set

A work instruction usually has at least three layers: the controlling engineering source, the Composer authoring file, and one or more published deliverables consumed on the floor. Treating only the PDF as controlled leaves the authoring logic and source relationship ambiguous. Treating only the CAD as controlled leaves operators with no approved presentation.

Assign document numbers or relationships that let a reviewer move from the instruction to the source model, BOM, process plan, tooling requirement, inspection checkpoint, and change record. Record which source revision the instruction was authored against. If one instruction covers several product configurations, define the applicability clearly instead of relying on a filename.

Choose the consumption format from the workstation and task. Printed PDFs may be required at a bench, SVG or raster images may fit an MES page, and interactive Composer content may help with orientation or complex sequences. Every format needs the same revision authority and a method for removing old copies.

Author steps for the person doing the work

Composer can repurpose 3D CAD into illustrations, exploded views, BOM callouts, step-by-step procedures, and animations without changing the engineering model. Start with the work sequence, not camera angles. For each step, state the action, orientation, parts, tools, torque or process values if controlled elsewhere, inspection point, hazard reference, and the condition that proves the step is complete.

Use views to make position and sequence obvious. Hide irrelevant components, control transparency, add arrows and callouts, and keep the same visual orientation across adjacent steps unless the rotation serves a clear purpose. A beautiful exploded view can still fail if it does not show which fastener starts first or how an operator confirms seating.

Do not duplicate controlled specifications casually. If torque, adhesive, weld procedure, or inspection criteria belong to another controlled document, link or reference that authority and revision according to the quality system. Copying the value into several outputs creates multiple places to update after a change.

• Use one action or inspection decision per step when the sequence matters.
• Show tools, fixtures, orientation, access, and hidden interfaces that affect execution.
• Write callouts in operator language and keep part identifiers consistent with the manufacturing BOM.
• Identify variants and optional steps at the point where the path changes.
• Include the instruction number, revision, applicability, and page or step identity in published output.

Use PDM state to control authoring, review, and point-of-use access

SOLIDWORKS Composer 2026 provides an integrated SOLIDWORKS PDM ribbon tab when PDM Professional is installed. It exposes commands such as check in, check out, get versions, change state, search, and view card information. Those tools support a controlled authoring workflow, but the organization still has to define the states, transitions, permissions, and document relationships.

A practical workflow can separate work in progress, manufacturing review, quality or process approval, released, and obsolete. The author can edit the Composer project while reviewers access a controlled preview or published draft. Release should move the approved deliverable to the access path used by operators and remove superseded versions from ordinary point-of-use retrieval.

Test permissions as author, reviewer, operator or viewer, and administrator. Operators need simple access to the current instruction without the ability to revise it. Authors need the correct CAD and Composer versions. Reviewers need enough context to reject and return changes. Administrators need to recover history without becoming the routine approval authority.

Review the instruction at the workstation where it will be used

Have the assembler, machinist, technician, or inspector walk through the sequence using the proposed format and workstation. Include manufacturing engineering, quality, and safety review where the process requires them. Ask the user to point to the exact instruction element that answers each action instead of accepting a verbal explanation from the author.

Test lighting, screen size, glove use, zoom, print quality, color dependence, network availability, language, and how the operator returns to the right step after an interruption. A high-resolution illustration can become unreadable on a small terminal, while color-coded warnings can disappear on a grayscale print.

Capture defects by step and type: wrong geometry or BOM, missing process value, ambiguous orientation, sequence error, inaccessible fastener, missing quality check, unsafe assumption, unreadable output, or navigation problem. Correct the authoring source, republish, and repeat the affected walk-through.

Make source revisions trigger an instruction impact review

Not every CAD change alters the operator’s work, but every controlling change should receive an impact decision. Compare geometry, BOM, metadata, tooling, process, safety, inspection, and configuration applicability. Record “no instruction change” with the reviewer and reason when that is the correct outcome.

Composer document updates match geometry actors through net GUIDs derived from actor names. Renaming or rearranging actors, changing assembly level, changing import options, or making major parent-child structure changes can prevent or limit the update. New and deleted geometry may process correctly while callouts, visibility, or author-created objects still need review.

Detail views created with Digger, High Resolution, or Technical Illustration do not update automatically according to 2026 Help. After an approved source change, inspect every affected normal view, custom view, callout, detail view, BOM ID, animation, and published format before repeating the floor walk-through.

Release the new instruction and remove the old version from point-of-use access. Printed copies need a controlled replacement or expiration method. QR codes or links should resolve through a stable controlled location rather than directly to a revision-specific file that remains available after supersession.

Measure whether operators can find and trust the instruction

Track superseded-copy discoveries, time to retrieve the current instruction, questions by step, deviations caused by unclear content, change-to-release lead time, and instructions overdue for source-impact review. These signals measure document usefulness and control more directly than the number of illustrations produced.

Give the system named owners: engineering owns the product definition, manufacturing engineering owns the work sequence, quality and safety own their required approvals, the author owns the Composer source, PDM administration owns configuration, and operations owns point-of-use compliance. The exact titles can vary, but the decisions cannot remain ownerless.

A mature workflow lets another qualified author open the controlled project, identify the source revision, update a known view, republish through the approved settings, route the change for review, and replace the floor output without relying on a hidden local file or one person’s memory.

Frequently asked questions