Have you ever had this happen?
The drawing changed. The job didn't.
Have you ever found the correct revision after the work was already done?
Fictional business scenarios. Companies, scenes and resolutions are invented to illustrate Smokejumper's approach; they are not customer results.
The situation
A defense supplier is preparing a shipment. Quality spots a mismatch: the customer requirement references one revision, document control shows another, and the traveler followed an older instruction. Engineering issued the change. Production followed the packet it received. Now the team is deciding what needs inspection, rework or customer clarification while the shipping clock keeps running.
An engineering change is only as useful as the decisions it changes downstream. Publishing a new document does not establish that every affected job is ready to use it.
How we would approach it
Connect the problem to the company plan.
01. Begin with the business outcome: accepted work with fewer surprises at release. Trace one change across the contract, controlled documents, work instructions and affected jobs. Make the quality and engineering owners explicit.
02. Agree the authoritative sources and the rules for conflicting or missing revisions. Identify what information may be used in the development environment with the company's responsible security and contractual specialists.
03. Have employees and specialists test assistance that highlights inconsistencies, shows the supporting records and sends an exception to the responsible person. Test old packets and incomplete changes as carefully as clean examples. Keep engineering disposition and shipment release with authorized people.
The fictional resolution
A better decision, with an owner.
In this fictional resolution, the mismatch appears while work is being prepared. The owner can see what changed, which jobs may be affected and what must be resolved before release. The team has an accountable way to act on a change, rather than hoping a notification reached everyone.
What we would measure
Compare revision discrepancies detected before and after work starts, rework attributed to revision confusion and unresolved changes at release. Preserve the evidence behind each classification.
Bring one real example
When engineering changes something, how do you know the change reached the work?
Start with a free 20-minute introduction with Dan Caulfield, Smokejumper CEO. Discuss where you want the company to go and whether a company-level strategy and plan would be useful.
760.803.7619 · Explore the company plan · How the Innovation Center works