Control software evidence in a MOSAIC program

The decision behind this topic

For software, systems, and compliance managers, the useful question is not simply what MOSAIC says. The work is avoiding an evidence gap between installed functionality and supplier claims. The management decision is which software processes and records support the function and its safety significance. That requires an aircraft-specific record, not a generic interpretation copied into a schedule.

A credible program distinguishes confirmed requirements from assumptions, ties each conclusion to the configuration it covers, and gives unresolved items an owner and a decision date. This is especially important when prior certification work, supplier evidence, or commercial forecasts are being reused in a new U.S. context.

Evidence to put on the table

A practical way to proceed

1. 1

   classify functions and assurance expectations early

2. 2

   contract for access to necessary supplier data

3. 3

   repeat impact analysis for every software change

The output should be a traceable recommendation with conditions, not an unsupported yes or no. Where evidence is incomplete, show the closure method, cost and schedule exposure, and the event that will change the decision.