Configuration & Data Manager
Configuration & Data Manager Perspective
Protects requirement IDs, baselines, parent-child links, and digital-thread artifacts as Product Support requirements are decomposed and updated in JAMA.
- Preserve identifiers, baselines, and links
- Maintain digital-thread integrity
- Coordinate ARB-driven re-baselines
Primary responsibilities
- Preserve requirement identifiers and baseline integrity through decomposition cycles.
- Maintain parent-child traceability and downstream digital-thread artifacts.
- Coordinate baseline updates triggered by ARB naming/behavior changes.
- Ensure JAMA structure reflects the agreed Level 4 elements and architecture updates.
Day-to-day work activities
- Audit JAMA daily for ID drift, broken links, and unauthorized structure changes.1
- Process baseline updates after each ARB cycle and tag the affected requirement set.2
- Maintain digital-thread links: requirement ↔ architecture element ↔ interface ↔ verification.3
- Manage release of baselines to customer reviews and audits.4
- Coordinate with Project Engineer on freeze windows around ARB and major reviews.5
Baseline and data artifacts
| Artifact | Role of CM/DM | Trigger |
|---|---|---|
| JAMA baseline | Owner | ARB approval / scheduled release |
| Requirement ID registry | Owner | New decomposition |
| Trace matrix (parent ↔ child ↔ verification) | Owner | Any link change |
| Digital-thread package | Owner | Customer / audit review |
Government approvals touched
- Baseline release approvals for customer reviews and audits.
- Configuration Control Board actions for change requests affecting baselined requirements.
- Audit evidence for traceability and digital-thread integrity.
Configuration checklist
- Requirement IDs are stable across re-baselines.
- Parent-child links are intact after decomposition.
- ARB-approved naming/behavior is reflected in the baseline.
- Digital-thread artifacts (verification, interfaces) are linked.
- JAMA structure aligns with the agreed Level 4 layout.