Operational Test and Evaluation

During the Operational Test and Evaluation phase the new system/subsystem is installed in operational aircraft and exercised by the end user community (Launch airline customer). While testing up to this point has focused on assuring that identified requirements have been verified, this phase focuses on validation, i.e., assuring that the end-users needs regarding the system have been satisfied.

5.7.1 Inputs

1. 1. Installation kit for each aircraft.
2. 2. Updated flight and maintenance manuals.
3. 3. Crew Familiarization Training materials.

5.7.2 Process

In this phase, OEM plays a support role, such as conducting training, consultation, etc.

Reported anomalies and crew-recommended changes are investigated and corrective actions are initiated or recorded for correction later.

As part of its validation effort, OEM supports the customer(s) in its Operational Suitability, Safety, and Effectiveness (OSS&E) assessment. Airworthiness of the airplane by generating the final Modification Airworthiness Certification Criteria (MACC) matrix, whereby explicit criteria are identified as being impacted by the design and associated verification evidence determined. Completion of the MACC provides the basis for airworthiness certification.

Outputs

1. 1. Anomaly reports, as needed.
2. 2. Final, as-built requirements specifications, ICDs, and design documents.
3. 3. Final test reports for end items and for the system/subsystem as a whole.
4. 4. Final, as-built Software Version Descriptions/Version Description Documents (SVDs/VDDs) for software and as-built drawings for hardware.
5. 5. Released Specification Change Notices (SCNs) for the System Specification and Prime Item Development Specification (PIDS) or, at the customer’s option, updated.
6. 6. System Specification or PIDS incorporating SCNs to date.
7. 7. Final Requirements Trace Matrix/Verification Cross-Reference Matrix (RTM/VCM).
8. 8. Delivered software media.
9. 9. Completed Modification Airworthiness Certification Criteria (MACC).
10. 10. Formal Customer(s)’ acceptance of delivered hardware, software, and documents.

Milestone Reviews

A Functional Configuration Audit (FCA) is held, with support from SE, to assure that all requirements at the system level and at the end item level have been satisfied. The RTM/VCM data support this analysis.

A Physical Configuration Audit (PCA) is also held, with support from SE, to assure that the final, as-built configuration matches the final design documentation.

The FCA and PCA are usually held concurrently.