Management of Change: plan changes early, implement them cleanly, prove every step

Where changes fail

Not in the idea but in the implementation: who does what and when lives in e-mails, spreadsheets and meeting notes. Production learns about the new drawing too late, purchasing still orders the old revision, and in the end nobody can prove that every measure was actually carried out.

How CaRD Plan maps your change process

Every type of change becomes a template: assessment, approval, implementation steps, verification and effectiveness check – with predecessors, owners and expected times. Each actual change becomes its own plan created from it. Whatever gets stuck is recorded on the step and flows back into the template.

• Form-fit-function (FFF) changes and new developments with the same structure, just different steps
• Approvals as steps of their own – skipped only with a reason in the comment
• Drawings, bill-of-material extracts and test reports attached directly to the step
• Management overview of all running changes with progress and delay

Objects and costs per change

Which objects a change touches – material numbers, routings, change numbers – is defined by the activity in the catalogue; in the plan only the number is entered at each task. Estimated planned costs and the actual costs per task come on top. At the end the overview shows what the change cost and which objects it affected – also in the closing report. The tenant switches the function on when needed.

Integrate early instead of repairing late

Because the change exists as a plan with predecessors, everyone involved sees from the start when it is their turn. Purchasing, production and service are not surprised after the approval – they prepare their part while the assessment is still running.

Complements your existing change management

The change request and the bill of materials stay in your PLM or ERP system. CaRD Plan steers the implementation across all departments and proves it: who started, finished or skipped which step, when, and why – as a closing report and project archive.