On this page
A baseline identifies what was approved
For this business exercise, a configuration baseline is the controlled record of a particular installation’s approved hardware, software, settings and engineering documents. It gives the local and overseas teams a common starting point for support.
The systems engineering handbook from NASA (the National Aeronautics and Space Administration) describes identifying baselines, controlling changes and keeping configuration status. Those are NASA engineering-management methods, not mandatory rules for every commercial equipment supplier. ELN’s smaller register below is an original planning adaptation.
The support file can describe a different installation
Fictional example: the parent’s support folder contains drawing revision C and application version 4. The U.S. site record says the machine was handed over with drawing revision B and application version 3. An engineer cannot safely infer which file is correct merely from the newest filename.
Ask the responsible technical team to reconcile the approved handover, subsequent change approvals and observed installation. A proposed update is a different decision from establishing what is present.
| Register entry | Evidence to link |
|---|---|
| Machine/site identity | The specific installation and responsible customer contact. |
| Approved documents and software | Versions released for that installation, with approval references. |
| Observed configuration | Who verified it, when and with what limitations. |
| Changes since handover | Request, approval, implementation and verification records. |
| Open mismatch | The technical owner, affected support advice and next decision. |
Do not confuse the baseline with a network list
An operational technology (OT) asset inventory identifies devices and connections for security and support planning. The approved baseline identifies which engineering state is authorised. Link the records so that a component swap does not leave the support folder describing an earlier configuration.
Protect detailed customer drawings and settings in the authorised document system. Do not copy them into the public expansion brief.
Make record maintenance part of service work
Someone must update the baseline after an approved change and make it available to the people entitled to use it. Include that work in the support offer. Management should show one complete installation history before the owner assumes the method can be repeated across many U.S. sites.
Scope
- An original commercial adaptation of NASA configuration-management concepts. It does not establish a correct machine design, approve a change or prescribe a safety-critical configuration.
Next step
Keep the installation register in a controlled operating system. Use Launch dependencies to assign any missing handover evidence or unresolved version mismatch before expanding support.
Terms used here
- Configuration baseline
- The controlled record of the hardware, software, settings and documents approved for a particular installation.
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.