DO-254 Configuration Management (avionics/do254/hardware-configuration-management)
Use when the task is DO-254 configuration management for airborne
electronic hardware: classifying a hardware change, deciding the
ECR/ECO path, and maintaining the hardware configuration index.
The logic handles nominal categories and identifiers only, so no
physical quantities and no unit conversions apply.
Domain quick reference
- DO-254 hardware configuration management keeps baselines of
hardware lifecycle data and controls changes through engineering
change requests and orders (ECR/ECO).
- The hardware configuration index (HCI) identifies each item, its
revision, and the baseline it belongs to.
- A change class (1 or 2) sets the depth of control: class 1
requires a formal ECR/ECO, a baseline update, and reverification.
- Class 1 applies when form, fit, or function changes, when any
safety effect is present, or when the item is complex AEH.
- Class 2 changes are documented and reviewed, but do not force
reverification or independent review.
- Complex hardware changes are reviewed independently of the design
activity that proposed them.
- DO-254 is accepted via FAA AC 20-152A.
Workflow
- Collect the change attributes: hardware class, safety effect,
and whether form, fit, or function changes.
- Classify with change_class to get the change class and its
rationale.
- Map the class with cm_actions to the CM actions: baseline
update, ECR/ECO, reverification, independent review.
- Record the item in the HCI with hci_entry (item, revision,
baseline).
- Attach every ECR/ECO and its disposition to the baseline.
Pitfalls
- Treating a simple item's change as class 2 when a safety effect
exists; safety effect alone forces class 1.
- Skipping reverification on a class 1 change.
- Reviewing a complex hardware change with the same people who
proposed it, which breaks independence.
- Recording an HCI entry without the baseline identifier.
Behavior contract (gate 3)
The change classification, CM action mapping, and HCI formatting
logic is exercised by the gate 3 contract test:
scripts/test_hardware_configuration_management.py against
scripts/hardware_configuration_management_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_hardware_configuration_management.py
Compliance
- Standards referenced, not reproduced: DO-254 text is proprietary
(RTCA/EUROCAE); summary-only per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: hardware-configuration-management3description: "Use when you must determine the DO-254 configuration management action for a hardware change: classify the change class, decide whether a formal engineering change order (ECR/ECO) with reverification applies, and produce the hardware configuration index (HCI) entry against the current baseline. A change to form, fit, or function, any safety effect, or complex hardware is class 1 with baseline update, reverification, and independent review; otherwise class 2 uses documented but lighter review. Trigger: do 254 hardware configuration, change class, engineering change order, ecr, eco, configuration baseline, hardware configuration index, hci."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: do-2548 reference-only: true9gated: false10domain: avionics11pack: avionics12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/hardware-configuration-management15 domain: avionics16 subdomain: do25417 tags: [do-254, configuration, change-class, ecr, eco, hci, hardware, review-independence]18 version: 0.1.019 author: Aero Agent Skills20---2122# DO-254 Configuration Management (avionics/do254/hardware-configuration-management)2324Use when the task is DO-254 configuration management for airborne25electronic hardware: classifying a hardware change, deciding the26ECR/ECO path, and maintaining the hardware configuration index.27The logic handles nominal categories and identifiers only, so no28physical quantities and no unit conversions apply.2930## Domain quick reference3132- DO-254 hardware configuration management keeps baselines of33 hardware lifecycle data and controls changes through engineering34 change requests and orders (ECR/ECO).35- The hardware configuration index (HCI) identifies each item, its36 revision, and the baseline it belongs to.37- A change class (1 or 2) sets the depth of control: class 138 requires a formal ECR/ECO, a baseline update, and reverification.39- Class 1 applies when form, fit, or function changes, when any40 safety effect is present, or when the item is complex AEH.41- Class 2 changes are documented and reviewed, but do not force42 reverification or independent review.43- Complex hardware changes are reviewed independently of the design44 activity that proposed them.45- DO-254 is accepted via FAA AC 20-152A.4647## Workflow48491. Collect the change attributes: hardware class, safety effect,50 and whether form, fit, or function changes.512. Classify with change_class to get the change class and its52 rationale.533. Map the class with cm_actions to the CM actions: baseline54 update, ECR/ECO, reverification, independent review.554. Record the item in the HCI with hci_entry (item, revision,56 baseline).575. Attach every ECR/ECO and its disposition to the baseline.5859## Pitfalls6061- Treating a simple item's change as class 2 when a safety effect62 exists; safety effect alone forces class 1.63- Skipping reverification on a class 1 change.64- Reviewing a complex hardware change with the same people who65 proposed it, which breaks independence.66- Recording an HCI entry without the baseline identifier.6768## Behavior contract (gate 3)6970The change classification, CM action mapping, and HCI formatting71logic is exercised by the gate 3 contract test:72scripts/test_hardware_configuration_management.py against73scripts/hardware_configuration_management_logic.py (stdlib unittest, offline). Run:74python3 scripts/test_hardware_configuration_management.py7576## Compliance7778- Standards referenced, not reproduced: DO-254 text is proprietary79 (RTCA/EUROCAE); summary-only per standards-map.yaml.80- compliance: STANDARDS-REF, gated: false.