Skip to content
AeroSystems
AEAIP knowledge · Standards

Standards & framework mapping for aerospace engineering assurance

In short

AEAIP is designed to map engineering evidence and workflows against applicable engineering, assurance, quality, safety, cybersecurity and certification frameworks.

Mapping shows which evidence supports which expectation of a framework. It is not certification and does not make an organisation compliant; compliance remains the organisation's responsibility, assessed by its customers, auditors and authorities.

01

Mapping is not compliance

Engineering organisations work to frameworks that their customers, regulators and own quality systems invoke. A mapping connects a framework's expectations to the evidence that addresses them, so gaps are visible before an audit or review rather than during it.

To be explicit about what is not claimed:

  • AEAIP is not “NASA compliant”, and GAMYAA has no NASA affiliation or endorsement.
  • AEAIP is not “ECSS certified”; ECSS publishes standards rather than certifying software tools.
  • Using AEAIP or DAQIP™ does not guarantee AS9100 or AS9102 compliance.
  • Neither AEAIP nor AirCert AI™ guarantees airworthiness or provides regulatory approval.
  • No security certification (such as SOC 2 or ISO/IEC 27001) is held for AEAIP.

02

How a mapping works

Illustrative examples. Framework expectations are paraphrased and referenced, never reproduced.
Illustrative framework-to-evidence mapping
Expectation (paraphrased)Referenced frameworkEvidence pattern in AEAIP
Verification records identify the requirement version and product version verifiedNASA SE Handbook, product verificationEvidence → produced on → configuration; requirement revision on every closure
Configuration status is recorded and auditableSAE EIA-649C; ISO 10007Configuration nodes, change history, as-tested versus as-built comparison
Each design characteristic is accounted for at First Article InspectionAS9102C (via DAQIP™)Characteristic → method → measurement → evidence → approval
Security requirements are verified and findings tracked to closureNIST SP 800-160 Vol. 1 Rev. 1Security requirement → control → test → finding → remediation → retest

03

Framework families

Frameworks a programme may apply, depending on its domain, customer and jurisdiction. Links go to the publisher or official source.

05

Frameworks are tailored per programme

Programmes rarely apply a framework wholesale. They tailor it: selecting applicable requirements, adjusting levels, adding customer-specific expectations. The tailoring is itself an engineering decision that needs to be visible.

That is why AEAIP treats frameworks and review gates as configuration, not code; see Configurable Assurance Gates.

References / Engineering Sources

Explanations on this page are original GAMYAA paraphrase. Standards are referenced, not reproduced; paid standards link to their publisher. Referencing a framework does not imply compliance with it.

  1. 01
    NASA Systems Engineering Handbook, NASA/SP-2016-6105 Rev 2 (opens in a new tab)

    NASA

    Life-cycle phases, technical reviews and the systems-engineering process model.

  2. 02
    NPR 7123.1D, NASA Systems Engineering Processes and Requirements (opens in a new tab)

    NASA Office of the Chief Engineer

    NASA's life-cycle and technical review entrance and success criteria (for NASA programmes).

  3. 03
    ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processes (opens in a new tab)

    ISO / IEC / IEEE

    Life-cycle process descriptions, including verification and validation processes.

  4. 04
    ECSS-E-ST-10-02C Rev.1, Space engineering — Verification (opens in a new tab)

    European Cooperation for Space Standardization

    Verification methods (test, analysis, review-of-design, inspection), levels and stages.

  5. 05
    ECSS-M-ST-10C Rev.1, Space project management — Project planning and implementation (opens in a new tab)

    European Cooperation for Space Standardization

    ECSS project phasing and its own set of project reviews.

  6. 06
  7. 07
    AS9102C, Aerospace Series — First Article Inspection Requirements (opens in a new tab)

    SAE International / IAQG

    First Article Inspection requirements and FAI Report structure.

  8. 08
    SAE EIA-649C, Configuration Management Standard (opens in a new tab)

    SAE International

    Configuration management functions and principles.

  9. 09
    SAE ARP4754B, Guidelines for Development of Civil Aircraft and Systems (opens in a new tab)

    SAE International

    Aircraft and system development assurance (civil aviation context).

  10. 10
    NIST Cybersecurity Framework (CSF) 2.0 (opens in a new tab)

    National Institute of Standards and Technology

    Outcome-based cybersecurity risk management framework.

Published by
Gamyaa AeroSystems — Engineering Assurance Research
Last reviewed
Status
Status: Research

Which frameworks does your programme answer to?

Tell us which standards your customers invoke, and where evidence mapping costs you the most time.