FAA Releases Digital Engineering Guidance for Avionics Certification — What Changes

The FAA's new digital engineering guidance allows model-based artefacts to satisfy some DO-178C and DO-254 certification evidence requirements, potentially reducing duplicate documentation but requiring new model governance processes.

FAA Digital Engineering: A Significant but Narrow Opening

The FAA's Order 8110.49 supplement on Digital Engineering Guidance (DEG) represents the first formal acknowledgement that model-based artefacts can substitute for traditional document-based certification evidence in some contexts. For avionics SE teams, this is significant — but the scope is more limited than some initial coverage suggested.

What the Guidance Actually Permits

The DEG allows model-based artefacts to satisfy evidence requirements in two specific categories: requirements traceability matrices (RTM) and architecture description documents. A SysML model with proper configuration control and an established model authority can substitute for a separate RTM document, provided the model governance process meets the DEG's process requirements.

For code-level evidence under DO-178C, the guidance is more conservative: tool qualification requirements for any model-to-code translation path remain stringent, and the DEG explicitly does not change DO-178C's stance on model-based development.

New Requirements: Model Governance

The tradeoff for accepting model-based artefacts is a new set of process requirements. The DEG mandates: a designated Model Authority responsible for model configuration control; a defined model data environment with access control and version tracking; a process for identifying and qualifying modelling tools; and a model data management plan submitted as part of the certification plan.

For organisations that have adopted MBSE practices organically without formal governance, meeting the DEG's model governance requirements may require more process investment than the documentation savings justify in the short term.

Practical Implications

Organisations whose primary pain point is RTM maintenance — maintaining traceability between requirements, design elements, test cases, and verification evidence — will benefit most. Organisations hoping for relief from DO-178C software evidence requirements will find the guidance unhelpful in the near term.

The longer-term trajectory is more promising: the DEG establishes the governance framework that future expansions of model-based certification evidence can build on.