SOO Attachment 3 Initial Operating Capability.pdf

Initial Operating Capability (IOC)

Checklist

Definition: IOC is defined as the minimum viable products to conduct one Radar Cross- Section (RCS) Use Case that includes completing:

1) Secure Special Access Program (SAP) storage (infrastructure/facility modifications, fire suppression)

2) Conducting LSAR measurements for a full use case frequency range on a static stand (RCS measurement systems)

3) Engine support infrastructure needed to mount, remove, transport and store an engine that is the unit under test (Engine Test Stand, Shroud and Controls)

4) Ability to post-process the collected data

All the necessary components will have completed testing, with reports delivered and be fully functional.

Product Criteria Acceptable Unacceptable Baseline Documentation

Bi-directional traceability has been documented

Baseline Documentation

Configuration of the system or system element(s) is clearly defined

Any design changes made to the system element(s) since CDR are documented in the technical documentation (TDP)

All approved engineering change proposals (ECP), requests for deviation, and requests for waiver have been incorporated into the system product baseline

For software, a technical understanding is reached on the validity and the degree of completeness of the software test reports and as appropriate, computer system operator’s manual, software user’s manual, and the system diagnostic manual

Audit of PDR and CDR minutes shows that all technical review findings have been addressed, all action items closed and corrections listed in corrective action plans have been successfully completed for the baseline documentation being audited

Demonstrated the capability to satisfy KPP and KSA thresholds based on available test data, analysis or inspection

Acceptance test reports are complete, have been reviewed, and deficiencies have been addressed

Audit of supplier/subcontractor test procedures and results shows compliance with specification requirements as mapped down to the lowest level end item in the requirements verification traceability documentation, and that formal test data is complete and accurate as judged against the test procedures

Assessment of the documented system product baseline for the initial production system shows a low risk of operational test failure during FOC

Technical Plans SEMP is complete, adequate, and aligned with the program SEP

Technical Plans Logistics support analysis and maintenance task analysis are complete and the results incorporated into the LCSP

Technical Plans Detailed plans and schedules have been established and sufficiently resourced to proceed into FOC activities

Technical Plans Training plan that adequately supports IOC is consistent with the system product baseline and has been reviewed and approved

Technical Plans TEMP is up-to-date, signed, and being properly executed

Process Control Adequate processes are in place for the program to succeed

Process Control Critical program information (CPI) is being adequately managed and protected

Process Control CCB is processing configuration changes in accordance with industry standards, supplier instructions, processes and procedures, and maintaining the proper configuration baselines

Process Control Configuration changes have been identified as required for reliability growth to ensure threshold compliance at FOC

Risk Assessment Technical risks are identified, and mitigation plans are in place

Risk Assessment Risk management process is in place demonstrated by documented execution results of existing mitigation plans associated with the purpose of the review

Life-Cycle Cost Estimate

System production cost model has been updated

Life-Cycle Cost Estimate

Updated CARD is consistent with the approved initial product baseline

Verification All system specification qualification test requirements have been successfully completed

Verification Each requirement listed in the requirements verification traceability documentation has been successfully verified in accordance with the identified methodology based on all available test data, analysis, or inspection

Verification

All subsystem and system tests are completed and documented (Test Reports)

Subsystem/element performance has been verified against the allocated baseline, and integrated functional performance has been verified against the functional baseline

Adequately detailed requirements verification traceability documentation exists outlining the method for verification for each requirement

System-level performance has been verified as satisfactory against the functional baseline