On this page
Keep a request separate from an approved design
A local team may ask to use another part because the specified item is unavailable. That can be commercially sensible to investigate, but the request does not establish compatibility, customer acceptance or permission to install it.
The configuration-management chapter from NASA (the National Aeronautics and Space Administration) distinguishes proposed changes, approved baselines and the records of changes. It is an engineering-management reference here, not a law imposed on your equipment business. The smaller change sheet below is ELN’s planning tool.
A substitute can affect more than the purchase order
Fictional example: a supplier offers Revision D in place of Revision C for twenty machines awaiting completion. Management needs to know whether the change affects interfaces, approved software, documentation, spares or customer requirements. A lower price and an earlier delivery date do not answer those engineering questions.
The qualified design authority must decide the technical evidence and testing needed. This article does not approve either revision or give fitting instructions.
| Before release | Evidence or decision to record |
|---|---|
| Reason and affected units | Which actual machines or future builds would change, and why. |
| Specification and compatibility | The differences and qualified assessment against the approved design. |
| Verification | Relevant test results and unresolved exceptions. |
| Approval and customer requirements | The authorised decision, conditions and required customer involvement. |
| Implementation and records | Who updates drawings, software, parts lists and affected installation baselines. |
Release the scope you can support
An approval for a particular build or customer does not automatically cover every installed machine. Record the scope and effective point clearly. Unapproved stock, obsolete drawings and a supplier’s changed revision need to be distinguishable in the operating records.
Include the parent engineering and local verification work in the change budget. If the only available approver is the owner overseas, that continuing dependency belongs in the operating model.
Close the change after implementation has been checked
Ask management to show that the approved change was actually implemented and that the relevant records now match the installation. A signed request and a changed filename are weaker evidence than the complete request, decision, implementation and verification trail.
Use a representative authorised change to test the method before promising that partners can manage a large installed base independently.
Scope
- Original commercial adaptation of configuration-management concepts. Actual design authority, testing, safety, customer and regulatory requirements remain specific to the product and installation.
Next step
Keep the engineering-change record in the controlled product system. Use Launch dependencies to assign approval, verification and affected-record tasks before a change is released.
Sources & review notes
National Aeronautics and Space Administration
Passage, dates and research notes
official-guidance · Section 6.5.1: inputs, baseline identification, change control and configuration status
Read the configuration-management chapter, including baseline, proposed changes and approval/status functions. NASA’s programme requirements are not requirements imposed on an ordinary commercial manufacturer; ELN’s smaller-company tables are original adaptations.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.