PERFORMANCE WORK STATEMENT (DRAFT)

RC-12X/MC-12SCockpit Procedural Trainer (CPT)Reconfigurability Implementation

Prepared byProject Manager, Fixed Wing

5030 Bradford Drive, Suite 101Huntsville, AL 35805

12 December 2014

Table of Contents

1. SCOPE.............................................................................................................................................................1

1.1 BACKGROUND...................................................................................................................................................1

2. APPLICABLE DOCUMENTS.....................................................................................................................3

2.1 OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS............................................................3

3. REQUIREMENTS.........................................................................................................................................5

3.1 SYSTEM DESIGN................................................................................................................................................53.1.1 System Definition Stage..........................................................................................................................53.1.2 Preliminary Design Stage.......................................................................................................................53.1.3 Detailed Design Stage.............................................................................................................................63.1.4 Fabrication, Assembly, Integration and Test Stage................................................................................63.1.5 Architecture Design................................................................................................................................6

3.2 SOFTWARE DESIGN...........................................................................................................................................63.2.1 Software Test...........................................................................................................................................7

3.3 HARDWARE DESIGN..........................................................................................................................................73.4 HARDWARE AND SOFTWARE INTEGRATION.....................................................................................................73.5 SYSTEM DELIVERY...........................................................................................................................................83.6 ITEM UNIQUE IDENTIFICATION (IUID).............................................................................................................83.7 PRODUCT DEFINITION DATA (PDD).................................................................................................................83.8 REQUIREMENTS MANAGEMENT........................................................................................................................8

3.8.1 Requirements Analysis............................................................................................................................93.8.2 Requirements Validation.........................................................................................................................9

3.9 LOGISTICS MANAGEMENT................................................................................................................................93.9.1 Maintenance Support Strategy................................................................................................................9

3.10 SUPPORTABILITY ENGINEERING......................................................................................................................103.10.1 Supportability Analysis and Logistics Management Information....................................................103.10.2 Contractor Logistics Support (CLS)................................................................................................103.10.3 Availability.......................................................................................................................................103.10.4 Usage...............................................................................................................................................103.10.5 CLS Program Support......................................................................................................................113.10.6 CLS to LCCS Transition..................................................................................................................113.10.7 Commercial Off-the-Shelf (COTS) Manuals....................................................................................113.10.8 Operator Manual.............................................................................................................................113.10.9 Maintenance Manual.......................................................................................................................113.10.10 Publications In Process Reviews (IPRs)..........................................................................................12

3.11 POST PRODUCTION SYSTEM SUPPORT (PPSS)................................................................................................123.11.1 Obsolescence Management and Technology Insertion....................................................................133.11.2 Concurrency Upgrades....................................................................................................................133.11.3 Software Transition..........................................................................................................................133.11.4 System Modifications and Enhancements........................................................................................133.11.5 Information Assurance Updates.......................................................................................................13

3.12 TRAINING SERVICES........................................................................................................................................143.12.1 Operator Training............................................................................................................................143.12.2 Maintenance Training......................................................................................................................14

3.13 QUALITY ENGINEERING..................................................................................................................................143.13.1 Test Discrepancies...........................................................................................................................15

3.14 INFORMATION ASSURANCE (IA).....................................................................................................................153.14.1 Personnel Security Requirements for Accessing Government IT Systems.......................................153.14.2 Security Assessment.........................................................................................................................153.14.3 Information Assurance Process.......................................................................................................153.14.4 Design Actions.................................................................................................................................163.14.5 Software Integrity Certification.......................................................................................................163.14.6 IA Compliance..................................................................................................................................163.14.7 IA Certification................................................................................................................................163.14.8 Acquisition of IA Products...............................................................................................................16

3.15 TECHNICAL REVIEWS......................................................................................................................................173.15.1 Technical Interchange Meetings (TIMs)..........................................................................................17

3.16 PROGRAM MANAGEMENT...............................................................................................................................173.16.1 Technical and Management Work Planning....................................................................................173.16.2 Work Scheduling..............................................................................................................................183.16.3 Financial Management....................................................................................................................183.16.4 Risk Management.............................................................................................................................183.16.5 Configuration Management (CM)...................................................................................................18

3.17 INTEGRATED TESTING.....................................................................................................................................213.17.1 Software Defect Management..........................................................................................................223.17.2 Test Readiness Review (TRR)..........................................................................................................22

3.18 SAFETY............................................................................................................................................................22

APPENDIX A – ENTRANCE AND EXIT CRITERIA..........................................................................................23

1. SYSTEM REQUIREMENTS REVIEW (SRR)........................................................................................23

1.1 SRR ENTRANCE CRITERIA..............................................................................................................................231.2 SRR EXIT CRITERIA:......................................................................................................................................23

2. PRELIMINARY DESIGN REVIEW (PDR).............................................................................................23

2.1 PDR ENTRANCE CRITERIA..............................................................................................................................232.2 PDR EXIT CRITERIA.......................................................................................................................................23

3. CRITICAL DESIGN REVIEW (CDR)......................................................................................................23

3.1 CDR ENTRANCE CRITERIA.............................................................................................................................233.2 CDR EXIT CRITERIA.......................................................................................................................................24

4. SYSTEM TEST............................................................................................................................................24

4.1 CONTRACTOR SYSTEM TEST...........................................................................................................................244.1.1 Contractor System Test Entrance Criteria...........................................................................................244.1.2 Contractor System Test Exit Criteria....................................................................................................24

5. GOVERNMENT ACCEPTANCE TEST (GAT)......................................................................................24

5.1 FORMAL GAT ENTRANCE CRITERIA..............................................................................................................255.2 FORMAL GAT EXIT CRITERIA........................................................................................................................255.3 TEST DISCREPANCY PRIORITIES.....................................................................................................................25

Table of FiguresTable 1: Pro Line 21 CPT Training Tasks.......................................................................................1

Performance Work Statement (PWS)

RC-12X/MC-12SCockpit Procedural Trainer (CPT)

1. SCOPE This PWS establishes the Contractor’s tasks related to the design, modification, integration, testing, management, fielding, documentation, and support for a reconfigurable RC-12X/MC-12S Cockpit Procedural Trainer (CPT).

1.1 Background The U.S. Army has a requirement for pilot cockpit procedural training for the Pro Line 21 equipped MC-12S aircraft. To satisfy this training requirement, the Contractor shall modify the existing RC-12X Universal Avionics CPT to add the capability to train and sustain proficiency in specified MC-12S aircraft (Pro Line 21 equipped) individual and crew tasks. The CPT shall maintain all training capability for the RC-12X Universal Avionics configuration. The CPT shall be augmented with the hardware, software, media, and documentation necessary for training Pro Line 21 aircrews in the tasks listed in this PWS. The upgraded reconfigurable CPT is referred to as the RC-12X/MC-12S CPT in this document, except when referring to only the Universal Avionics configuration or only the Pro Line 21 configuration.

Table 1: Pro Line 21 CPT Training Tasks

219-3001 Operate Rockwell Collin FMS 3000 (FMS)

a. Initialize FMSb. Programs a Flight Planc. Program a Standard Instrument Departured. Program Enroute changese. Program Fuelf. Perform Navigation functionsg. Program Standard Instrument Arrivalsh. Program GPS approachesi. Program VOR, NDB, and TACAN overlay approachesj. Perform Holding proceduresk. Use Command Heading functionl. Familiarization with all Menu and List functions of all FMS pages

219-3002 Operate Mission Control Audio Panel (MCAP)

a.       Operate Communication Radio thru MCAPb.      Operate Navigation Radio thru MCAPc.       Operate Transponder and TCAS thru MCAPd.      Operate TACAN thru MCAP

219-3003 Operate Pilots and Copilots AFD-3010 - PFD, MFD Pilots Display Unit (PFD).

All changes apply to the Pilots PFD, Pilots MFD, or Copilots PFD; all displays have the same interface capabilities as the aircraft equipment.

a. Change Navigation Source between FMS1, FMS2, VOR1, VOR2, TACAN or Nothingb. Change Bearing Pointer between FMS1, FMS2, VOR1, VOR2, TACAN or Nothingc. Set V Speeds (V1, V2, Vr, Target, and Vref)d. Display Traffic Collision Avoidance System (TCAS) - Test Onlye. Display Enhanced Ground proximity Warning System (EGPWS) – Test Onlyf. Display Airports and Navaidsg. Change display between 360 Map, 360 HIS, arc Map, arc HIS and Normal Modeh. Determine Wind Vectors

219-3004 Operate Flight Director

a. Operate Flight Director in the NAV modeb. Operate Flight Director in the HDG modec. Operate Flight Director in the APP moded. Set up for precision approach e. Set up for non-procession approachf. Climb or decent based on Indicated Air Speed (IAS) or Vertical Speed (VS)g. Set up for GPS (LNAV, or LPV) approaches

Flight related Tasks

a. Fly Instrument Landing System (ILS) Approaches.b. Fly VOR Approaches.c. Fly GPS Approaches.d. Fly NDB Approaches.e. Fly TACAN Approaches.f. Fly Missed approaches and holding patterns.g. Navigate off all flight plans and inputs to FMS.h. Climb, descend, and hold altitude as selected in flight director.i. Change heading by using heading command on flight director.

The Pro Line 21 CPT configuration will provide training on the avionics package provided by the Rockwell Collins Pro Line 21 avionics equipment. The RC-12X/MC-12S CPT will maintain the core hardware and software architecture of the existing RC-12X Universal Avionics CPT. The fidelity and functionality provided by the RC-12X Universal Avionics CPT configuration shall not be diminished by the implementation of this upgrade to the training device. Both the Universal Avionics CPT configuration and the Pro Line 21 CPT configuration will include pilot and copilot stations with controls, displays, and instruments with necessary and sufficient fidelity for training the tasks required for each respective configuration. This PWS defines all tasks and responsibilities of the Contractor associated with modifying the two existing RC-12X CPTs at

the U.S. Army Intelligence Center of Excellence (USAICoE) training facility at Ft. Huachuca, AZ to incorporate the Proline 21 configuration capability. There shall be no reduction in the existing training capability provided by the CPT when configured in either the Pro Line 21 configuration or the Universal Avionics configuration.

2. APPLICABLE DOCUMENTS The following documents of issue form a part of this PWS to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this PWS, the contents of the PWS shall be the governing requirement.

2.1 Other Government Documents, Drawings, and Publications

Document Number Document Name

AR 25-1Army Knowledge Management and Information Technology, dated 4 Dec 08

AR 25-2 Information Assurance, dated 24 Oct 2007

DoDD 8500.1Information Assurance, dated 24 Oct 2002, Certified Current as of 21 Nov 03

DoDI 8500.2Information Assurance Implementation, dated 6 Feb 2003

DoDI 8510.01Department of Defense (DoD) Information Assurance Certification and Accreditation Process (DIACAP), dated 28 Nov 07

N/ADefense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs)

DoDD 5220.22-MNational Industrial Security Program Operating Manual, dated 27 Sep 04, Certified Current as of 1 Dec 06

DISR DoD Information Technology Standards

TBDPro Line 21 Performance Specification, Version 1.0, dated 23 March 2011

P/N 130-590031-254Super King Air 250ER & 350CER (Models B300 & B300C) Pilots Operating Handbook and FAA Approved Airplane Flight Manual, October 2007

Operator’s Guide FMS-3000 v4.0 Flight Management System for King Air Series Aircraft

Operator’s Guide Pro Line 21Avionics System with Optional IFIS for the Raytheon King Air

MIL-STD-130N Identification Marking of U.S. Military Property

MIL-STD-882D Standard practice for System Safety

3. REQUIREMENTS The Contractor shall design, build, integrate, and deliver a system that meets the requirements as defined in this PWS, the Pro Line 21 CPT Performance Specification, and associated Pro Line 21 CPT Fidelity Analysis. The Contractor shall provide all effort, resources, facilities, equipment, and personnel necessary to complete the tasks in this PWS. The Contractor shall perform all activities to integrate and assemble the hardware and software to produce a system that performs and operates in accordance with the Performance Specification and Contractor generated specifications. The Contractor shall verify the functionality of the hardware and software of each subsystem, and of the fully integrated system, through the utilization of formalized test procedures. The Government shall provide all existing RC-12X CPT documentation as GFI, and the Contractor shall update that documentation in accordance with the data delivery requirements of this PWS.

3.1 System DesignThe Contractor shall perform the necessary engineering activities to design the Pro Line 21 CPT reconfigurable implementation in a manner that fully satisfies the requirements delineated in this PWS, the Pro Line 21 Performance Specification and the Pro Line 21 Fidelity Analyses. Selected designs and standards shall be based on performance, cost, industry adoption, long-term availability, and supportability. The Government will provide the Contractor with all RC-12X CPT technical design information, system executable and COTS software, and the source code for all Government owned RC-12X CPT software. The contractor will be provided limited access to an RC-12X CPT at Ft. Huachuca (on a non-interference basis) to conduct data collection, requirements analysis, and integration efforts.

3.1.1 System Definition Stage The Contractor shall decompose the Government provided requirements (as contained in the PWS and Performance Specification) into a verifiable set of system, subsystem, and component operational and interface requirements. The Contractor shall establish the verification methodology for all system requirements and shall create a Requirements Traceability Matrix that captures linkages between the Performance Specification, low-level design requirements, and verification plans/procedures.

(DI-IPSC-81431A) System/Subsystem Specification (SSS)

3.1.2 Preliminary Design Stage The Contractor shall include recommended components and interfaces, risk assessment and risk management plans, and an analysis of quality factors to include producibility, verifiability, usability, supportability, trainability, and configurability with the RC-12X CPT for each subsystem in the preliminary design. The Contractor shall conduct technical reviews and prepare associated documentation for each subsystem during the preliminary design stage. The Contractor shall document and present the initial design approach and decisions at a formal Preliminary Design Review (PDR). The purpose of the PDR is to ensure that:

The subsystem design is sufficiently mature to meet systems engineering criteria.

Component allocations and preliminary component specifications are reasonable and provide a sound subsystem design concept.

Subsystem risks have been assessed and managed to a level sufficient for continued production.

Decisions made in arriving at the subsystem design are well supported by analysis and technical data.

3.1.3 Detailed Design Stage The Contractor shall complete subsystem design down to the lowest component level to include identification of recommended parts and interfaces, risk assessment and risk management plans, and an assessment of quality factors to include producibility, verifiability, usability, supportability, and trainability. The Contractor shall conduct technical reviews and prepare associated documentation for each subsystem during the detailed design stage. The Contractor shall document and present the detailed design approach and decisions at a formal Critical Design Review (CDR). The purpose of the CDR is to ensure that:

The subsystem design is sufficiently mature to satisfy functional and performance criteria.

Component specifications are reasonable and provide a sound component design concept. Component and related life cycle process risks have been assessed and managed to a

level appropriate to support the fabrication, assembly, integration, and test phases. Trade-study data are adequate to substantiate that detailed component requirements are

achievable. Decisions made in arriving at the detailed component definition configuration are well

supported by analysis and technical data.

3.1.4 Fabrication, Assembly, Integration and Test Stage The Contractor shall integrate all hardware design components into the final system configuration. The Contractor shall verify that the assembled and integrated components satisfy specifications and shall resolve system deficiencies when specifications for the system, product, subsystem, assembly, or component are not met, as determined by the specified verification methodology.

3.1.5 Architecture Design The architecture of the RC-12X/MC-12S CPT shall not deviate from the RC-12X CPT baseline except when approved by the Government as necessary to satisfy Pro Line 21 CPT functional or performance requirements.

3.2 Software Design The Contractor shall develop the system software and firmware and follow the Contractor’s software development practices consistent with at least Level 3 of the Software Engineering Institute’s Capability Maturity Model for Software (CMMI). The design should incorporate an assessment of open source software products, ease of software maintenance, operation, and upgrade, and any features that reduce cost, schedule, risk, and the amount of documentation required to meet the requirements of this PWS. The Contractor design shall maximize the reuse

of Government owned and COTS software. Any software developed specifically for use in the Pro Line 21 CPT shall be delivered as non-proprietary.

The Contractor shall utilize an approved Design Change Request (DCR) process to request revisions to Government requirements, even where such revisions would result in cost schedule or performance benefits. The Contractor shall define and document the software requirements and verification methodology for each software item, and document the traceability between the software item requirements, the SSS, and the System Performance Specification.

The Contractor shall document the system and interface design approach in the Pro Line 21 CPT Software Design Description. The Contractor shall document the compilation, build, modification, and installation procedures and identify all hardware, software, and tools necessary to develop deployable software from source code and data.

(DI-IPSC-81433A) Software Requirements Specification (SRS)(DI-IPSC-81435A) Software Design Description (SDD)(DI - IPSC-81441) Software Product Specification (SPS)

3.2.1 Software Test The Contractor shall follow an established software item testing process. The Contractor shall establish test cases (in terms of inputs, expected results, and evaluation criteria), traceability between the test case and the system requirements, detailed procedures for conducting the test, and test data corresponding to each software item. The Contractor shall test the software in accordance with the unit test cases and procedures. The Contractor shall analyze the results of item testing and record the test and analysis results.

(DI-IPSC-81439A) Software Test Description (STD)

3.3 Hardware Design The Contractor shall integrate and assemble the system hardware that satisfies the requirements identified in the Pro Line 21 CPT System/Subsystem Specification. The Contractor shall make use of commercial and Non-Developmental Items (NDI) in all cases where there is a demonstrable life-cycle cost benefit. In cases where commercial or NDI items are not used, the Contractor shall provide justification and a cost-benefit analysis to the Government at the PDR.

3.4 Hardware and Software Integration The Contractor shall perform all activities to integrate developed and commercial software with the system hardware to achieve a fully functional system that performs and operates in accordance with the Pro Line 21 CPT Performance Specification and Government approved Contractor specifications. The Contractor shall verify the complete integration of each hardware and software subsystem and the overall system through the utilization of Software Test Descriptions and formalized test procedures. The Contractor shall specify the functional, logical, and physical interfaces between the computer program products and any equipment hardware with which it must operate. The final hardware and software integration for the Pro Line 21 configuration shall be performed on one of the two RC-12X CPTs located at Ft. Huachuca. This CPT will support all hardware/software integration efforts and a subsequent First Article

Government Acceptance Test (GAT) for the Pro Line 21 configuration. After the first Pro Line 21 configured CPT is certified by the Government as Ready For Training (RFT), the second RC-12X CPT shall be upgraded by the Contractor to the Pro Line 21 configuration and will undergo an approved Production GAT.

3.5 System Delivery The Contractor shall be responsible for all efforts and resources necessary to design and document the Pro Line 21 CPT configuration and shall upgrade both RC-12X CPTs on site at Ft. Huachuca. The Contractor shall plan, coordinate, and perform the Pro Line 21 CPT system upgrade at the training site in a manner to accommodate concurrent training activities and concurrent work by the Government, Government support Contractor, associate Contractors, and others at the site during the upgrade effort.

3.6 Item Unique Identification (IUID) The Contractor shall coordinate among the IPT members to determine items requiring IUID including embedded subassemblies, components and parts, and identify the UID to be used for each item. The Contractor shall provide IUID, or a DoD recognized IUID equivalent, for all identified items delivered. IUID marking design for each item shall be both machine readable and human readable in accordance with MIL-STD-130, paragraph 5.2.

(DI-MISC-80711A) Scientific and Technical Reports

3.7 Product Definition Data (PDD) During the systems engineering and design phase, the Contractor shall update the Product Definition Data (PDD) to accurately depict the final product. The PDD is the technical description of items adequate for production, engineering, and logistics support. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files and meta data) and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional engineering design effort. The Contractor shall maintain and update the PDD to incorporate any changes to the Hardware (H/W) and Software (S/W) baselines. (DI-SESS-81003C) Commercial Drawings and Associated List(DI-SESS-81000C) Product Drawings and Associated List

3.8 Requirements Management The Contractor shall establish a means to manage hardware and software requirements (including derived requirements) through use of a requirement traceability matrix. The requirements traceability matrix should provide traceability from the System Performance Specification through the lower level specifications down to the system test procedures. The Contractor shall maintain and update the requirements traceability matrix throughout the life of the contract.

3.8.1 Requirements Analysis The Contractor shall complete systems requirements analysis to establish:

System capabilities Performance objectives in quantitative and measurable terms The operational environment The human-system interfaces The physical and aesthetic characteristics Constraints that affect design solutions

3.8.2 Requirements Validation The Contractor shall perform a validation of the requirement baseline established during requirement analysis. Validation shall consist of:

An evaluation of the requirements baseline to ensure that it represents identified expectations and project or external constraints

An assessment of the requirements baseline to determine whether the full spectrum of possible system operations and system life cycle support concepts has been adequately addressed

The Contractor shall repeat the requirements analysis and validation phases, as needed, until the requirements baseline is validated and approved. The Contractor shall capture the results of the Requirements Analysis and Requirements Validation phases in the SSS and the SRS.

3.9 Logistics Management The Contractor shall ensure the operational and maintenance supportability of the system through planning, implementation, and verification of materials and services to meet the operational requirements. Readiness, availability and supportability shall be the primary logistics design factors.

3.9.1 Maintenance Support Strategy The Contractor shall provide both on-site maintenance and depot-level maintenance support of the RC-12X/MC-12S CPT for the time period specified in the contract, commencing with Government Acceptance of both upgraded CPTs. On-site maintenance includes system activation, adjustments and alignments, troubleshooting, and removal/replacement of failed components by site maintenance personnel. On-site maintenance includes preventive maintenance, which consists of daily readiness check and services, adjustments to controls and other maintenance performed by the operator or trained technician without the aid of special tools, support equipment, additional training knowledge, or skills, either on site or at a local CLS or Life Cycle Contractor Support (LCCS) maintenance facility. Depot-level maintenance involves the return of equipment for repair to an off-site maintenance facility. It includes the use of designated repair points operated by the CLS/LCCS Contractor, or the original manufacturer/vendor, in order to overhaul, rebuild, replace, or calibrate failed equipment.

3.10 Supportability Engineering

3.10.1 Supportability Analysis and Logistics Management Information The Contractor shall identify support resource requirements and the cost for required spares, special tools, and test equipment. The Contractor shall include a source list to enable procurement of spares and repair parts required to maintain the equipment and meet the system operational requirements.

The Contractor shall analyze existing LCCS structures, and create an optimized support infrastructure for production and deployment. The recommended support resources shall be sufficient to allow another Contractor with comparable skills to assume operation, maintenance, and support of the system and sustain the system availability requirement. The Contractor shall use the form, fit, function, and interface requirements in the performance specifications for provisioning, training, and maintenance planning.

The Contractor shall conduct repair level analyses, develop diagnostic, preventative maintenance and repair procedures, conduct facilities analyses, define hardware and software maintenance and support concepts, and identify support resource requirements including required spares and support equipment. The Contractor shall create a listing of which items are repairable along with an estimated repair cost. The analysis shall include a consideration of the following:

All input data and their corresponding value and source of the data Operational scenario modeled, assumptions made, constraints assumed, and non-

economic factors imposed Maintenance alternatives considered Analytical method and models used to perform the economic evaluations Discussion of the sensitivity evaluation performed and results obtained

(DI-ALSS-81529) Logistics Management Information (LMI) Data Product(s)(DI-ALSS-81530) Logistics Management Information (LMI) Summaries

3.10.2 Contractor Logistics Support (CLS) The Contractor shall provide, for the period of time specified in the contract after Government acceptance of both upgraded CPTs, all necessary personnel, supervision, management, materials, services, communications, tools, equipment, and facilities to provide CLS maintenance and operations services as needed by the on-site training instructor.

3.10.3 Availability The Contractor shall be responsible for maintaining a minimum 90% Operational Availability (Ao) for the RC-12X/MC-12S CPTs. The CPT device is considered available when all student stations, the Instructor Operator Station (IOS), and subsystems are operational and training can proceed.

3.10.4 Usage The Contractor shall provide CLS on-site operational support for 8 hours per day and 5 days per week for 52 weeks per year.

3.10.5 CLS Program Support The Contractor shall provide technical representation at management reviews and technical briefings with other Contractors or other Government agencies, as necessary and as directed by the Government. The Contractor shall provide technical assistance in the planning and preparation for the installation of equipment, communications, support environments, and shall provide supplies and materials necessary to perform the task.

3.10.6 CLS to LCCS Transition When directed by the Government, the Contractor shall develop a CLS transition plan. The transition plan shall address the transition of CLS services from the Contractor to another Government designated agency or contractor in a manner that ensures an orderly transition and minimizes any undesirable impact on operational readiness of the devices. The Contractor shall include plans to address any proprietary hardware and software and the associated cost impacts. The Contractor shall continue to provide CLS services until the Government-directed transition date, and provide the designated CLS agency access to all sites and to all technical documentation and publications. The Contractor shall correct all system deficiencies and replace all inventory deficits prior to transitioning to the follow-on CLS Agency. The Contractor shall conduct a joint audit of any Government furnished property provided during the contract with representatives of the Government and the LCCS Contractor, noting all changes, modifications, and repairs in process.

(DI-MGMT-80259) Physical Inventories Report

3.10.7 Commercial Off-the-Shelf (COTS) Manuals The Contractor shall provide operational and maintenance manual(s) for all Commercial Off-The-Shelf equipment. MIL-PRF-32216 will be used in the evaluation of submitted COTS manuals. The Contractor shall provide an index of all the COTS manuals for identification and inventory purposes.

(DI-TMSS-80527B) Commercial Off-The-Shelf (COTS) Manual and Associated Supplemental Data

3.10.8 Operator Manual The Contractor shall deliver an updated operator's manual that describes the setup, configuration, and operational use of the training system.

(See Annex to Exhibit C) Technical Publications (MIL STD 40051-2, Operator Manual)

3.10.9 Maintenance Manual The Contractor shall deliver a updated maintenance manual that describes installation, fault isolation, and maintenance procedures for the training system.

(See Annex to Exhibit C) Technical Publications (MIL STD 40051-2, Maintenance Manual)

3.10.10 Publications In Process Reviews (IPRs) The Contractor shall host and co-chair Publication IPRs to ensure the technical publications are being prepared according to contracts. Each Publication IPR shall be scheduled to coincide with system level program reviews defined in the integrated master plan. The Contractor shall act on decisions and discrepancies resulting from each Publication IPR. Each review shall include a review of incorporated corrections or comments from previous Publication IPRs. If any IPT member identifies previous Publication IPR comments that are not included in the technical publications, the Publication IPR will be considered incomplete.

3.10.10.1 Publications Validation Validation shall be accomplished on all technical publications, changes, supplemental data, and revisions thereto. Publications will be validated prior to start of system testing. A technical publication will be approved upon validation or verification that the following conditions have been fulfilled:

An Engineering technical review has been completed Information, illustrations, and parts lists reflect correct configurations of the system and

equipment, to include all engineering changes Procedural instructions are readily understandable by the intended user and adequate to

perform all operations and maintenance functions All procedures have been performed to assure accuracy and performance requirements Adequacy of data is checked to ensure that it supports the approved maintenance and

support plan Hardware of the proper configuration is available for the validation and verification effort All safety hazards identified in the safety assessment report are resolved and identified

within the text as cautions or warnings necessary to protect the equipment or personnel as appropriate

3.10.10.2 Verification The Contractor shall assist PEO STRI IPT members with verifying that the Technical Manuals (TMs) are accurate. The IPT may choose to perform verification concurrently with the validation effort. Correction of discrepancies and changes resulting from training, testing, and reviews shall be incorporated into the TMs. The Contractor shall provide system equipment, technical and engineering support and facilities as required to aid in the performance of verification effort. The Contractor shall incorporate all comments from compliance-reviews, technical accuracy reviews and verification reviews into final submission of TMs.

3.11 Post Production System Support (PPSS)The Contractor shall establish a program that provides system support services for the time period identified in the contract commencing with Government acceptance of both upgraded CPTs. The PPSS program shall provide the services described in the following subsections.

3.11.1 Obsolescence Management and Technology Insertion The Contractor shall research, select, evaluate, test, verify, validate, install, and deploy new technology as necessary and as directed by the Government to ensure that the fielded RC-12X/MC-12S CPT system remains supportable in accordance with the supportability approach. The Contractor shall make recommendations to the Government’s CPT Change Control Board (CCB) for incorporation of new technology and shall test and incorporate approved items into the configuration baseline. The Contractor shall perform cost benefit analysis of candidate products for technology insertion and provide necessary information to support IPT and CCB decisions. The Contractor shall ensure that Line Replaceable Units (LRU) and Shop Replaceable Units (SRU) of the CPT System meet the requirements of the specification. The Contractor shall provide and maintain an item interchangeability matrix of all LRUs and SRUs within the RC-12X/MC-12S CPT System. This matrix shall include the relation of the RC-12X/MC-12S CPT System software to LRUs and SRUs.

3.11.2 Concurrency Upgrades At the Government's direction, the Contractor shall implement hardware, software, and database modifications necessary to maintain concurrency of the RC-12X/MC-12S CPT. Concurrency upgrades shall occur no more frequently than once per 12-month period, commencing with the start of the PPSS support effort.

3.11.3 Software Transition The Contractor shall create a software transition plan, which identifies all of the resources required to maintain and support the delivered software, in accordance with the Contractor software intergration process. The Contractor shall work with the IPT to develop cost-effective approaches to transition and training requirements.

(DI-IPSC-81429A) Software Transition Plan (STRP)

3.11.4 System Modifications and Enhancements As directed by the Government, the Contractor shall correct latent defects and make hardware and software engineering changes to improve the device and increase the maturity of the system software. The Contractor shall perform minor changes resulting from modified requirements due to installation of commercial system software upgrades. The Contractor shall maintain configuration management of the device hardware and software baseline. The Contractor shall review, analyze, and track status of software deficiencies, and hardware and software baseline engineering changes and determine their impact on the RC-12X/MC-12S CPT. The Contractor shall assemble, integrate, test, store, and distribute all RC-12X/MC-12S CPT modifications and enhancements to the fielded systems.

3.11.5 Information Assurance Updates The Contractor shall monitor and assess Information Assurance Vulnerability Alerts (IAVAs) and Security Technical Implementation Guides (STIGs) for applicability to the RC-12X/MC-12S CPT system. The Contractor shall evaluate the impact of associated security fixes on the RC-12X/MC-12S CPT system and deploy all fixes that do not introduce unacceptable effects on the performance of the system. The Contractor shall establish and implement a process to

periodically evaluate and update antivirus software and definitions, firewalls, intrusion detection/prevention products, and any other implemented security controls.

3.12 Training Services The Contractor shall create and provide Instructor, Operator, and Maintainer Training through a combination of classroom presentations, written instructions, and hands-on operation. The Contractor shall develop all training courseware including program of instruction, lesson plans, and practical exercises. The Contractor shall conduct operator and maintenance training courses (2 courses total), not to exceed 40 hours for each type of training, each class with a class size of no more than six students.

(DI-ILSS-80872) Training Materials

3.12.1 Operator Training The Contractor shall conduct and document the completion of the operator course. This course shall be conducted on-site after delivery of the initial systems. The course shall provide comprehensive training for operators in the concepts, knowledge, and skills needed system operation. The course shall provide familiarization with trainer operations and emphasize the utilization of the instructor station, its functions, and controls. The course shall address the physical and functional descriptions and operation of the equipment including features, advantages, and configurations.

3.12.2 Maintenance Training The Contractor shall conduct and document the completion of the maintainer course for Contractor maintenance personnel prior to, or immediately following, Government acceptance. This course may be conducted on-site after delivery of the initial systems. The course shall provide comprehensive training in the concepts, skills, and aptitude required to maintain the system. This course shall consist of instruction in troubleshooting and maintenance, diagnostics to fault isolation, calibration, adjustments, remove and replace procedures, use of built in test, and repair that is beyond operator level maintenance. After completion of the course, all personnel shall be capable of operating, maintaining, and troubleshooting the trainer to the board replacement level.

3.13 Quality Engineering The Contractor shall establish measurement points that provide maximum visibility into program processes to assure contractual requirements are being met. The Contractor shall select suitable methods to analyze the processes to implement system improvements. Metrics shall be developed to assist management visibility into a process control program. The Contractor shall utilize an established discrepancy tracking system with the ability to produce complete permanent records of all current and historical program discrepancy listings. The Contractor shall establish suspense timelines to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items.

3.13.1 Test Discrepancies The Contractor shall follow an established Test Discrepancy corrective action process to ensure timeliness of analysis and corrective action of each test discrepancy generated by any IPT member. The Contractor shall document a detailed description defining the changes made to the equipment, hardware, and software to correct each discrepancy. Each discrepancy correction that modifies or changes any baseline shall be documented and entered in the configuration management system.

3.14 Information Assurance (IA) The Contractor shall ensure that the Pro Line 21 CPT configuration design and production is in accordance with the program IA objectives, processes, and requirements and with DoDI 8500.01, 8510.01, and AR 25-2. The Contractor shall create and maintain an IA process in accordance with the following paragraphs.

3.14.1 Personnel Security Requirements for Accessing Government IT Systems The Contractor shall comply with the IA and Personnel Security Requirements for Accessing Government IT Systems as defined by DoDI 8500.2.

3.14.2 Security Assessment The Contractor shall assess the current system environment and the supporting infrastructure for security vulnerabilities and weaknesses. The Contractor shall identify assets to be protected and continuously evaluate the security of the system, both physical and logical, identify threats and vulnerabilities, and recommend and implement protective measures for reducing security risk.

3.14.3 Information Assurance Process The Contractor shall create and maintain an IA process to guide management and design actions, specify and track IA requirements, document level of effort, identify possible solutions, and maintain operational systems security as defined by DoDI 8510.01 (or current IA regulations). The Contractor process shall be predicated upon three overarching concepts: coordination, information exchange, and negotiation with other organizations to establish IA requirements. The Contractor shall establish or adopt standards for managing IA requirements and capabilities and an information system security engineering approach that emphasizes purposeful design or configuration of security solutions. The Contractor process shall provide security engineering and a level of IA sufficient for certification and accreditation. The design and integration of the Pro Line 21 reconfigurable capability shall have no negative impact on the existing security posture and measures implemented in the RC-12X CPT.

3.14.3.1 IA Data Package The Contractor shall document decisions and maintain a description of the system mission, target environment, target architecture, security requirements, and applicable data access policies. The Contractor shall prepare an IA documentation package that includes:

Descriptions of the operating environment and threat Descriptions of the system security architecture The Certification and Accreditation (C&A) boundary of the system to be accredited

Copies of formal agreements among the Designated Approving Authority (DAA), Certification Authority (CA), program manager, and representative

All requirements and information necessary for accreditation All information required by the definition, verification, and validation phase of the

certification and accreditation process as defined by DoDI 8510.01 Test plans and procedures, certification results, and residual risk

(DI-MISC-80711A) Scientific and Technical Reports

3.14.4 Design Actions The Contractor shall design, and document the security architecture for the RC-12X/MC-12S CPT that complies with the security requirements for a Mission Assurance Category (MAC) III, Sensitive device. At design reviews, the Contractor shall present the systems security design, initial security risk assessment, test approach, training approach, and any other security relevant information. The Contractor shall incorporate the Government approved virus protection software available at DoD website https://www.jtfgno.mil/#av_central. The Contractor design actions for this unclassified system shall include an engineering process that captures and refines information protection requirements and ensures their integration into the system design through purposeful security design or configuration.

3.14.5 Software Integrity Certification The Contractor shall verify and certify that the software in the RC-12X/MC-12S CPT functions as designed in a properly secured operating system environment and is free of elements or vulnerabilities that might be unacceptably detrimental to the secure operation of the system information resources, as described in DoDI 8500.01 and 8510.01. The Contractor shall provide Vendor Integrity Statements for each RC-12X/MC-12S CPT software application. Commercial Item software does not require an Integrity Statement.

3.14.6 IA Compliance The Contractor shall test, verify, and document that the security architecture of the RC-12X/MC-12S CPT complies with the security requirements as identified in DODI 8510.01 for a MAC III, Sensitive device.. The Contractor shall use DoD approved assessment tools to perform IA testing.

3.14.7 IA Certification The Contractor shall support the Government in the Certification and Accreditation (C&A) effort. The Contractor shall address and implement the IA security requirements for a MAC III system with a Confidentiality Level (CL) of Sensitive. The Contractor shall create all documentation required to certify and accredit the trainer.

3.14.8 Acquisition of IA Products Evaluated or validated IA and IA-enabled IT products that meet the Government’s definitions for Commercial Item or Non-Developmental Items shall be used to the maximum extent practicable to meet the IA requirements specified herein. The selected products shall provide for the

availability of the systems, ensure the integrity and confidentiality of information, and ensure the authentication and non-repudiation of parties in electronic transactions. Commercial IA and IA-enabled IT products shall be used to enter, process, store, display, or transmit national security information, to the maximum extent practicable. The RC-12X/MC-12S CPT shall incorporate IA-enabled operating systems that:

Are configurable IAW applicable DoD Security Technical Implementation Guides (STIGs) or System and Network Attack Center (SNAC) guides ( DoD STIGs and SNAC guides are available at http://iase.disa.mil/)

Can incorporate the DoD Information Assurance Vulnerability Management Program (IAVMP) IAW DoDI 8510.01

Are supportable for the expected lifecycle of the RC-12X/MC-12S CPT

3.15 Technical Reviews The Contractor shall conduct a System Requirements Review (SRR), a PDR, a CDR, and a TRR to provide analysis, design, and test plans and details, and status on technical progress. With prior approval of the Government, the SRR and PDR may be combined into a single review event. The Contractor shall document the results of each review, including any resulting action items. The Entrance/Exit Criteria for each review is defined in Appendix A. Each review shall assess the system requirements and allocations to ensure that requirements are unambiguous, consistent, complete, feasible, verifiable, and traceable to top-level system requirements. At each review, the Contractor shall address the risks associated with a continued production effort, and the program metrics used to track program status.

3.15.1 Technical Interchange Meetings (TIMs) The Contractor shall support TIMs. A TIM shall address specific topics or issues, address status of production or test activities between management reviews, address the functions of an established working group, or coordinate and provide guidance for engineering data or technical publications.

3.16 Program Management The Contractor shall organize, coordinate, and control all program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services. The Contractor shall provide the necessary program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this PWS. The Contractor shall monitor the progress of all the work performed and costs incurred under the contract.

(DI-MGMT-80227) Contractor’s Progress, Status and Management Report

3.16.1 Technical and Management Work Planning The Contractor shall develop and maintain a plan to formulate the management and technical approach to ensure compliance with the contract requirements and the timely delivery of the

required products and services. The Contractor shall identify and document events, accomplishments, and criteria pursuant to successful completion of the work efforts.

3.16.2 Work Scheduling The Contractor shall develop, implement, control, and maintain an Integrated Master Schedule (IMS) that presents the Contractor plans and schedules to meet the requirements of this PWS. The Contractor shall document the planning and scheduling effort, related Government responsibilities, and the interaction for the efforts required for production and delivery of the training products. The Contractor shall develop and document a tiered scheduling system based on the CWBS elements showing all program milestones and prerequisite events, conferences, reviews, data submittals, and deliveries. Contract deliverables and subcontractor schedules shall be integrated into the Contractor IMS. The Contractor shall construct the IMS to assure that these milestones are met and to assure deliveries as required by the contract. The Contractor shall synchronize and coordinate the IMS with the site training and utilization schedules, as required.

(DI--MGMT-81650) Integrated Master Schedule (IMS)

3.16.3 Financial Management The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and sub-line item. The Contractor shall document and track effort management plans which are consistent with internal organizations and processes. These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status.

3.16.4 Risk Management The Contractor shall conduct systematic risk management to control the uncertainty in the project’s ability to meet cost, schedule, and performance objectives. The Contractor shall conduct that part of risk management that directly affects the technical effort to include risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control. Risk management of product requirement objectives shall be covered at all program and technical reviews. The Contractor shall use the Contractor internal risk management tools to perform risk management. The Contractor shall provide Government insight into the Contractor tools, assessment, mitigation, and control techniques. The Contractor shall document risk management as part of the Contractor Progress, Status, and Management Report.

3.16.5 Configuration Management (CM) The Contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs). The Contractor shall implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system-engineering environment.

The Contractor shall develop, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The CM process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline (FBL) defined by the system performance specification, interface control documents, and software product specification.

3.16.5.1 Configuration Management Planning and Management The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The Contractor shall:

Plan implementation of the CM functions for the context and environment in which they are to be performed and manage in accordance with the planning

Determine the specific CM value-adding functions and levels of emphasis. Document how the Contractor organization will implement CM functions to document,

manage, and track system attributes, definitions and configuration information, throughout the applicable phases of the life cycle

Identify resources required to implement the CM functions and ensure they are applied throughout the systems life cycle

Assess the effectiveness of CM plan implementation and performance of the configuration management functions with performance measurements.

Flow down responsibility for CM performance to subcontractors Plan and identify information status levels for managing system configuration

information and ensure that transmitted data products are usable

3.16.5.2 Configuration Identification The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management. The Contractor shall:

(a) Define the functional, performance, interface and physical attributes of the system and components

(b) Determine the systems composition using its product definition information(c) Assign unique identifiers to configuration items so that they can be distinguished from

other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved

(d) Assign unique unit identifiers to individual components of the system(e) Update component identifiers when a system is modified reflecting the new configuration

without altering the system identifier and model identifier(f) Uniquely identify information so that it can be correctly associated with the applicable

configuration of the system(g) Apply information identification rules to maintain representation and version

relationships

(h) Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval

(i) Establish complete, valid and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed

(j) Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to the system or within the system

3.16.5.3 Configuration Change Management The Contractor shall establish a systematic and measurable process for managing product configuration changes and variances. Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall:

(a) Document and uniquely identify each change(b) Classify requested changes to aid in determining the levels of review and approval(c) Clearly and completely document request for change(d) Consider the technical, support, schedule, and cost impacts of a requested change before

making a judgment as to whether the change shall be approved for implementation and incorporation in the system and its documentation

(e) Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility

(f) Determine the effectiveness of each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit

(g) Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements

(h) Document variances, when authorized by the appropriate level of authority

3.16.5.4 Configuration Status Accounting The Contractor shall provide access to accurate, timely information about the system and its documentation. The Contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current and historical data. The Contractor shall:

(a) Systematically record, safeguard, validate, and disseminate system information(b) Establish methods, processes and procedures to provide controlled access to system

information(c) Capture configuration information as it evolves

3.16.5.5 Configuration Verification and Audit The Contractor shall verify and audit the system configuration information to ensure that requirement attributes are met and accurately documented through a Functional and Physical

Configuration Audit (FCA and PCA). There will be government participation to verify the results. The Contractor shall:

(a) Verify that system attributes through a systematic comparison with the associated results of system tests, analyses, inspections, demonstrations or simulation models

(b) Maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements

(DI-CMAN-81022C) Configuration Audit Summary Report

3.16.5.6 Software Configuration Management The Contractor shall establish and document a software CM process. The Contractor shall incorporate and manage the configuration of all security related patches to ensure the secure operation of the system.

3.16.5.7 Software CM Database The Contractor shall establish and maintain a software CM database in accordance with the software intergration process. A schema shall be developed for identification of software items and their versions. The Contractor shall perform the following: identification, analysis, and recording of change requests and implementation, verification, and release of the modified software item. The database shall contain an audit trail whereby each modification, the reason for the modification, and authorization of the modification can be traced.

3.17 Integrated Testing Government Acceptance Testing (GAT) shall be performed on an upgraded CPT that incorporates both the Universal Avionics and the Pro Line 21 Configuration at Ft. Huachuca. Test Procedures shall be submitted to PEO-STRI for review and approval prior to the start of GAT in accordance with the Contract Data Requirements List (CDRL). The Test Procedures shall include verification of all Pro Line 21 configuration functionality requirements and an approved subset of Universal Avionics configuration regression tests. The Contractor shall follow the established Test and Evaluation (T&E) processes to include the execution of Software Test Descriptions and Test Procedures. The Contractor shall identify items to be tested, the test equipment and support required, the test conditions to be imposed, the parameters to be measured, and the pass and fail criteria against which the test results will be measured. The entrance and exit criteria for testing under this PWS are defined in Appendix A. Exit criteria for one phase of testing must be accomplished before entrance into the next phase of testing.

(DI-NDTI-80603) Test Procedure

3.17.1 Software Defect Management The Contractor shall implement a closed-loop defect management process. The Contractor shall document each problem detected in software products. The Contractor shall implement a corrective action system for handling each problem detected. Software item deliveries, including incremental deliveries, shall include defect history and open problems against the software item.

(DI - IPSC-81442A) Software Version Description (SVD)

3.17.2 Test Readiness Review (TRR) The Contractor shall conduct a TRR prior to the start of formal Test Procedure execution. The entrance criteria for TRR will be in accordance with the criteria defined for Formal System Test in Appendix A of this PWS. Prior to initiation of TRR, all exit criteria for Hardware Software Integration (HSI) and Informal System Test shall be met.

(DI-NDTI-80809B) Test/Inspection Report

3.18 Safety The Contractor shall implement a safety risk-management program to ensure the safety of the design, installation, transportation, maintenance, support and disposal of the RC-12X/MC-12S CPT trainer without any unacceptable safety hazards. The Contractor shall identify hazards, assess the risk, track hazards, mitigate hazards, and verify corrective actions have been implemented, and verify hazards have been eliminated or reduced to acceptable risk levels. The Contractor shall ensure that all information pertinent to the safeness of the RC-12X/MC-12S CPT is available for Government review.

(DI-SAFT-80102B) Safety Assessment Report (SAR)

Appendix A – Entrance and Exit Criteria

1. System Requirements Review (SRR)

1.1 SRR Entrance Criteria A preliminary agenda has been coordinated 30 days prior to the SRR. SRR technical products listed below for both hardware and software system elements

have been made available to the SRR participants prior to the review: o Draft System/Subsystem Specificationo All Design Change Request (DCRs) o Updated risk assessmento Updated schedule data

1.2 SRR Exit Criteria: The SRR is considered complete when all DCRs, the SRR Meeting Minutes, all Contractor Action Items are approved, and the Government has approved the SRR package.

2. Preliminary Design Review (PDR)

2.1 PDR Entrance Criteria A preliminary agenda has been coordinated 30 days prior to the PDR. The following technical products have been made available to the PDR participants prior

to the review:o Any System/Subsystem Specification updates submitted since completion of the

SRRo Draft Software Requirements Specification (SRS)o A documented Preliminary Design approacho Updated risk assessmento Updated schedule data

2.2 PDR Exit Criteria The PDR is considered complete when all DCRs, the PDR Meeting Minutes, all Contractor Action Items are approved, and the Government has approved the PDR package.

3. Critical Design Review (CDR)

3.1 CDR Entrance Criteria A Preliminary Design Review (PDR) has been successfully completed with Government

approval of the PDR Exit Criteria All PDR actions are resolved The design is mature and stable A high percentage of the drawings are completed A preliminary agenda has been coordinated 30 days prior to the CDR.

The following technical products have been made available to the CDR participants prior to the review:

o Updates to the SSS, if requiredo A documented system Design approacho Current risk assessmento Logistics documentationo SDD complete and placed under configuration management

3.2 CDR Exit Criteria The CDR is considered complete when:

Verification of the functional/performance requirements for the system are complete, Interface control documents are complete, Approval to start fabrication is given, and All DCRs, the CDR Meeting Minutes, and all Contractor Action Items are approved

4. System Test The System entrance and exit criteria are described below. System testing comprises a Contractor Engineering dry run, a Contractor Quality Assurance (QA) run and a Government-witnessed formal execution of approved Test Procedures.

4.1 Contractor System Test The Contractor System Test includes an Engineering dry run followed by a Contractor QA run of the approved Test Procedures (TPs). The intent of the Contractor Engineering dry run is to identify defects in the TPs and provide early identification of discrepancies. The intent of the Contractor QA run of the TPs is to provide final verification of system operation prior to Government formal execution.

4.1.1 Contractor System Test Entrance Criteria TPs have been generated and submitted to the Government for review and approval Integrated software has been incorporated into a CM Test load Formal Execution of all software tests has been completed

4.1.2 Contractor System Test Exit Criteria The informal System Test is complete when the following exit criteria have been satisfied

All sections of the final approved TPs have been successfully run by Contractor QA All Informal TP DRs have been documented and provided to the Government

5. Government Acceptance Test (GAT) The GAT focuses on verification of the Pro Line 21 CPT System/Subsystem Specifications (SSS) requirements. A TRR will be held prior to the start of the Formal Government System Test Event to identify the status of the system under test, and to verify the entrance criteria has been met.

5.1 Formal GAT Entrance Criteria All HSI/STDs have been completed successfully All TP sections have been run by Contractor QA All Internal and Formal DRs found during Contractor System Test are documented and

reviewed with the Government as part of TRR Corrective Action Plan(s) have been developed for all DRS and reviewed with the

Government as part of TRR After evaluation of all open DRs, the Government grants concurrence for executing

Formal System Test

The PEO STRI Test Director or appointed representative and Government Subject Matter Experts (SMEs), supported by the Contractor Test Director or his representative and Contractor SMEs as required, execute the TPs. During the conduct of the TPs, formal Discrepancy Reports (DRs) are generated, as appropriate. DRs are assigned priorities by the Discrepancy Review Board (DRB) composed of Contractor and Government personnel using an established process and approved priority definitions.

5.2 Formal GAT Exit Criteria The Formal GAT is complete when the following exit criteria have been satisfied:

All TP sections have been successfully completed. All DRs are documented and associated Corrective Action Plan(s) developed. The Government Test Director grants concurrence that the GAT has been successfully

completed. Concurrence signifies Test completion, only, and does not necessarily imply that the system has successfully satisfied all system requirements.

Test Procedures are submitted as FINAL.

5.3 Test Discrepancy Priorities. The Contractor shall assign level of effort to correct discrepancies based on the priority codes assigned by the test team, in accordance with the ground rules established by the IPT. The Government reserves the right to make the final determination of the priority of any test discrepancy.