Source register
Source scope consolidated during drafting and independent review on 10 November 2026. These sources support limited conceptual and capability statements. They do not validate a complete implementation, contractual regime or CM-II compliance claim.
| ID | Primary source | Supports | Scope boundary |
|---|---|---|---|
| S01 | NASA Systems Engineering Handbook: fundamentals | Systems engineering spans definition, realisation, technical management, operation and retirement. | Use as conceptual grounding, not a universal programme process. |
| S02 | NASA Systems Modeling Handbook, NASA-HDBK-1009A | System modelling supports requirements and verification/validation work products. | Handbook scope supports modelling practice; no tool-specific conformance is established. |
| S03 | Siemens manufacturing process planning | Teamcenter capabilities for MBOM, BOP and engineering/manufacturing reconciliation. | Verify version/module-specific data objects and workflows. |
| S04 | Siemens Capital connectors | Capital integration with the product-development environment and Teamcenter. | Verify electrical/mechanical ownership and transfer semantics. |
| S05 | SAP PLM system integration documentation | SAP documents integration with Teamcenter and associated compatibility/configuration material. | Select ERP edition, integration product and supported versions before prescribing mappings. |
| S06 | IpX CM2 framework | Framework owner's description of enterprise configuration and change management. | Confirm chosen reference edition and historical CM-II/current CM2 terminology crosswalk. |
| S07 | IpX CM2-04 change-process course | Framework owner identifies closed-loop and fast-track change processes. | Obtain authoritative process detail before prescribing exact roles, gates and terminology. |
| S08 | ISO/IEC/IEEE 15288:2023 | Lifecycle process framework. | Publisher scope checked; full clause mapping not yet undertaken. |
| S09 | INCOSE publications | Systems Engineering Handbook fifth edition and lifecycle guidance. | Public publisher information is not a substitute for the complete handbook. |
| S10 | NASA Systems Engineering Handbook, Revision 2 | Institutional review vocabulary and evidence-based readiness. | NPR 7123.1C was found marked obsolete during review and is not used as current procedural authority. |
| S11 | DoD Systems Engineering Guidebook, February 2022 | Defence technical-review and audit vocabulary. | Guidance reference; not assumed to govern this programme. |
| S12 | BSI BS 8888 overview, current edition | Technical product specification/documentation; 2025 edition identified by BSI. | Public scope checked; inspect full standard before detailed prescriptions. |
Additional chapter references
Chapter citations locate each claim beside its evidence. The following sources supplement the framework references above; vendor sources establish capability categories rather than a configured deployment.
| Primary reference | Use and boundary |
|---|---|
| NASA interface management | Interface identification, control and integration responsibilities; institutional guidance, not a universal contractual obligation. |
| NASA configuration management | Identification, controlled change, status and configuration verification; does not prove CM-II conformance. |
| NASA technical planning | Technical plans and coordination; programme-specific tailoring remains necessary. |
| NASA product verification and product validation | Specified requirements versus intended use, configuration and evidence. Acceptance rights remain contract-specific. |
| NIST SP 800-160 Volume 1 Revision 1 | Lifecycle systems-security scope. No certification or clause-level compliance claim is made. |
| JPL QC120 | A concrete example of supplier disposition rights; these terms do not automatically apply to another contract. |
| SAP Digital Manufacturing | Execution and manufacturing-operations capability categories; not evidence of installed licensing or integration. |
| Siemens Capital electrical systems | Electrical connectivity and harness lifecycle scope; exact configured tools and exchanges require qualification. |
| Siemens NX product and manufacturing information | Model-based product-definition capabilities; does not establish the completeness of a particular definition package. |
| Siemens Teamcenter classification | Classification capabilities; programme taxonomy and licensing are separate choices. |
Evidence boundaries
The book combines sourced engineering concepts with a reasoned operating model and a fictional teaching programme. Public standard descriptions establish scope, not complete normative requirements. Public product descriptions establish capability categories, not installed modules, native object mappings, exchange behaviour or throughput. Some vendor checks relied on indexed primary-source excerpts where full pages were inaccessible. Detailed IBM DOORS baseline/link behaviour is not assumed; the selected edition and integration must be qualified.
Exact CM-II/CM2 role mappings and conformity require an identified governing reference beyond public framework and course descriptions. The vehicle examples are explanations of engineering decisions, not validated designs. Standards, obligations and acceptance rights must be selected for the actual programme.