DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware
Section 7: Configuration management process – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware 7.2.3: 7.2.3 Problem reporting, tracking and corrective action

Problems (non-compliance with plans or standards, deficient process outputs, anomalous product behaviour, inadequate tools or processes) are recorded and resolved, starting no later than the baseline from which credit is taken. Every problem gets a report identifying the affected configuration; reports needing corrective action invoke change control; closed reports describe the action taken including data changes; not all reports must close before certification, but all are evaluated and those with safety or certification impact are closed; and the system tracks status, approval and disposition.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • A-8.3 Problem reporting, change control, change review and status accounting in place

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Section 7: Configuration management process – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.