RTCA DO-297 Integrated Modular Avionics Development

RTCA DO-297 Integrated Modular Avionics Development

1. What Is RTCA DO-297 Integrated Modular Avionics Development?

RTCA DO-297 Integrated Modular Avionics Development is a development-assurance approach for aircraft functions hosted on shared computing resources. Its formal document title is Integrated Modular Avionics (IMA) Development Guidance and Certification Considerations. Unlike a conventional management framework, it organizes technical responsibilities, integration evidence, and acceptance activities supporting airworthiness.

The executive question is straightforward: Who must demonstrate what when independently developed applications share an avionics platform? For aircraft manufacturers and avionics suppliers, use that question to structure supplier agreements, engineering ownership, evidence delivery, and release decisions—not merely certification paperwork.

2. Origin and Background

RTCA Special Committee SC-200 prepared DO-297, issued on November 8, 2005. Its original context was civil-aircraft certification, specifically the assurance challenges arising when reusable platforms and separately developed applications are combined into an IMA system. EUROCAE publishes the corresponding guidance as ED-124.

Recognition by aviation authorities established its certification significance. The Federal Aviation Administration’s Advisory Circular AC 20-170, issued October 28, 2010, recognizes and supplements DO-297. The circular describes an acceptable means of obtaining approval; it is not itself a mandatory regulation or the only permissible compliance approach.

For management, the important implication is that modular engineering requires modular accountability—but aircraft-level responsibility cannot disappear between supplier boundaries.

3. How RTCA DO-297 Integrated Modular Avionics Development Works

IMA separates the computing platform from the applications performing aircraft functions. The platform supplies defined hardware and software services; applications use those services within specified constraints. Integration must demonstrate that their combination works as intended.

  • Integrated: Multiple aircraft functions use shared resources.
  • Modular: Hardware and software building blocks can be developed and assessed separately.
  • Avionics: The hosted applications perform aircraft electronic-system functions.

The approach separates responsibilities among module/platform developers, application developers, integrators, certification applicants, and organizations supporting continued airworthiness. A company may perform several roles, but its evidence obligations still need explicit boundaries.

DO-297’s six tasks connect component acceptance, system integration, aircraft integration, changes, and reuse. The following labels are plain-language summaries, not substitutes for the document’s detailed objectives. Tasks involving change and reuse are lifecycle activities, not simply final steps in a linear project.

TaskPractical interpretation
1. Module acceptanceEstablish the module’s capabilities, limitations, interfaces, and supporting assurance evidence.
2. Application acceptanceEstablish application behavior, platform dependencies, resource needs, and assurance evidence.
3. IMA system acceptanceVerify the combined platform, applications, configuration, and interactions.
4. Aircraft integrationDemonstrate that the installed IMA system satisfies aircraft-level requirements.
5. ChangesAssess modifications and determine affected evidence and verification activities.
6. ReuseEstablish whether previously accepted modules or applications remain suitable in their new context.

Two concepts deserve particular attention. Robust partitioning provides isolation between functions using shared resources; it requires more than separate software folders. The usage domain defines the conditions and limitations within which a component’s demonstrated properties remain valid. Integration must respect both.

The useful management units are therefore specific module versions, applications, interfaces, partition schedules, configuration files, and installed aircraft configurations—not suppliers considered as undifferentiated entities.

4. When to Use RTCA DO-297 Integrated Modular Avionics Development

Use this approach when independently developed applications share an independently developed platform, or when incremental certification credit is anticipated. Relevant decisions for commercial aerospace manufacturers include introducing shared computing, adding hosted functions, and evaluating component reuse across derivatives.

It is especially powerful when supplier boundaries and integration dependencies would otherwise obscure responsibility. Before committing to an architecture, ask whether reusable evidence is accessible, its assumptions match the installation, and someone owns every cross-component verification activity.

Required inputs include requirements, safety assessments, interface definitions, resource limits, configuration baselines, verification results, and unresolved problem reports. Involve systems engineering, software and hardware assurance, suppliers, configuration management, airworthiness specialists, and maintenance representatives. Treat this as a lifecycle undertaking, not a workshop-sized compliance exercise.

It is not an architecture-selection scorecard or a universal requirement for every avionics computer. Military programs should establish applicability with their military airworthiness authority and program assurance basis rather than assume civil approval guidance automatically governs them.

5. How to Apply RTCA DO-297 Integrated Modular Avionics Development: Step-by-Step

The following management workflow helps organize execution. It does not replace the standard’s objectives or authority-agreed compliance plans.

  1. Clarify the decision and approval scope.

    Specify the aircraft variant, hosted functions, platform baseline, intended installation, and release horizon. Determine whether the work concerns new development, modification, or reuse. Confirm the assurance approach with the responsible approval specialists.

  2. Gather controlled inputs.

    Request requirements, safety allocations, supplier acceptance data, interface specifications, resource budgets, verification records, configuration identifiers, and open problem reports. Record provenance and missing evidence; do not treat supplier presentations as equivalent to controlled engineering records.

  3. Define the units and responsibilities.

    Identify each module, application, interface, and configuration item by version. Assign platform, application, integration, aircraft-level, and maintenance responsibilities. Resolve who owns partition configuration, resource allocation, fault handling, and changes before detailed integration begins.

  4. Construct an assurance map.

    Build a task-by-component matrix showing objectives, evidence, owners, acceptance dependencies, usage restrictions, and unresolved issues. Connect it to requirements and configuration records. This proposed management artifact makes handoffs visible; it is not a prescribed DO-297 form.

  5. Analyze compatibility and gaps.

    Challenge whether application assumptions match platform guarantees. Examine timing, memory, communications, restart behavior, and fault containment. Distinguish an absent document from an unproven technical property: the latter may require engineering work, not administrative closure.

  6. Translate findings into funded actions.

    Assign missing analyses and tests, amend supplier deliverables, reserve integration facilities, and establish evidence-based release gates. Make schedule dependencies explicit. A completed supplier delivery is not necessarily a completed acceptance activity.

  7. Test alternative assumptions.

    Evaluate added applications, heavier message traffic, revised partition schedules, replacement hardware, and changed operating conditions. Identify which changes could invalidate existing evidence. Present executives with the affected scope and proposed verification effort—not a generic contingency percentage.

  8. Align stakeholders and maintain the baseline.

    Review the map with engineering, suppliers, airworthiness, and maintenance. Resolve disputed assumptions through documented decisions. Update ownership, evidence applicability, and configuration status after every relevant change, including changes introduced during service.

Dedicated program management support can translate these dependencies into an integrated workplan, evidence-delivery schedule, and escalation process. Keep coordination authority distinct from technical acceptance and approval authority.

6. Example: RTCA DO-297 Integrated Modular Avionics Development in Action

Fictional situation: Northstar Aircraft is developing a surveillance derivative of a civil aircraft. Its redundant avionics platform hosts navigation, cockpit-display, and mission-recording applications supplied by different organizations. The program wants to add a higher-volume sensor feed without unnecessarily reopening unaffected development work.

Application: The chief engineer uses the DO-297 task structure to map module acceptance evidence, application assumptions, IMA integration activities, and aircraft-level verification. The units of analysis are the platform baseline, three application releases, network configuration, and partition schedule. The team reviews requirements, resource budgets, supplier evidence, problem reports, and representative operating scenarios.

Insight: In this illustration, average processor loading appears acceptable, but sensor-message bursts exceed the documented communications limits. A navigation application’s prior evidence also references a different platform software version. Neither issue is resolved by calling the platform “previously accepted.”

Decision and action: Northstar limits mission-data traffic, retains the established platform baseline, and assigns the navigation supplier a compatibility assessment. The integrator plans targeted verification of timing, fault handling, and application interactions. The program director funds the missing work and postpones release until the relevant evidence gaps are closed.

The management benefit is a defensible scope of work and clear ownership—not a presumed approval or an invented savings claim.

7. Strengths and Limitations

Strengths

  • Clear accountability: Separates what platform suppliers, application suppliers, and aircraft integrators must demonstrate.
  • Visible dependencies: Helps management connect evidence readiness with integration milestones.
  • Disciplined reuse: Provides a basis for evaluating reusable components without assuming their previous context is interchangeable.
  • Lifecycle perspective: Brings modifications and continued-airworthiness responsibilities into development planning.

Limitations

DO-297 does not select the commercially optimal architecture or eliminate aircraft-level integration. FAA reuse guidance addresses previously accepted modules and applications; it does not permit automatic reuse of previously accepted data at the complete IMA-system level. Treat acceptance credit as bounded by its demonstrated context.

Nor does modularity remove shared-resource risks. Separate acceptance cannot, by itself, establish that the combined installation is safe. Supplier evidence access, configuration differences, and unresolved assumptions can make an apparently attractive reuse decision impractical.

8. Common Pitfalls and How to Avoid Them

  • Equating acceptance with installation approval: A component’s accepted properties do not establish suitability for every aircraft installation. Identify the remaining integration and aircraft-level obligations.
  • Leaving configuration ownerless: Partition schedules and resource settings can fall between supplier contracts. Assign an accountable owner and controlled approval process.
  • Relying on average loading: Comfortable averages can conceal adverse operating scenarios. Require analysis and verification against the relevant limits and conditions.
  • Buying inaccessible evidence: A promised reusable platform has limited practical value if the applicant cannot obtain necessary assurance information. Define evidence access and delivery obligations before award.
  • Confusing management status with assurance status: “Delivered” and “tested” are incomplete descriptions. Report the applicable baseline, demonstrated properties, open issues, and remaining acceptance work.
  • Stopping at first approval: Plan ownership of problem reporting, configuration compatibility, and modification assessment throughout service.

Where these gaps reflect organizational ambiguity, strengthen decision rights and governance around interface ownership, release authorization, and supplier escalation.

9. How RTCA DO-297 Integrated Modular Avionics Development Relates to Other Frameworks

Aircraft development and safety assessment: The SAE ARP4754 family structures aircraft and system development, while the ARP4761 family supports safety assessment. Use these upstream and iteratively alongside DO-297: they establish the functions, hazards, and requirements that IMA integration must satisfy. DO-297 addresses the additional shared-platform assurance problem.

Software and electronic-hardware assurance: DO-178C and DO-254 address software and airborne electronic-hardware development assurance respectively. They operate alongside DO-297, rather than being replaced by it. Choose the applicable editions and supplementary guidance through the project’s agreed approval approach.

Airworthiness security: Where security is relevant, the DO-326A framework addresses the airworthiness security process. Do not treat functional partitioning or a completed IMA assurance map as a substitute for security assessment.

A responsibility matrix can complement these technical frameworks by clarifying ownership. It cannot demonstrate that an isolation, timing, or safety requirement has been met.

10. Key Takeaways

  • DO-297 structures assurance for applications sharing an avionics platform.
  • Manage specific component versions, configurations, interfaces, and evidence—not just suppliers.
  • Make usage restrictions and integration assumptions explicit.
  • Reuse requires demonstrated suitability, not a “previously accepted” label.
  • Convert assurance gaps into funded work, accountable owners, and release gates.

11. FAQs About RTCA DO-297 Integrated Modular Avionics Development

Is DO-297 mandatory for every avionics system?

No. Applicability depends on the architecture and approval approach. FAA AC 20-170 describes an acceptable means of compliance, not the only means or a standalone regulation.

Does an accepted IMA platform eliminate aircraft-level approval work?

No. The applicant must establish that the configured platform and hosted applications are suitable for the installation. Component acceptance does not automatically establish installation approval.

Can defense programs use DO-297?

Yes, when their program assurance basis supports it. Establish applicability and acceptance expectations with the relevant military authority; do not assume civil certification evidence automatically constitutes military approval.

How long does applying DO-297 take?

Separate initial planning from completing assurance activities. Duration depends on component maturity, evidence availability, configuration differences, integration complexity, and unresolved technical issues. An ownership workshop can launch the work; it cannot complete it.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]