N6134019R1203_DRAFT_DO1_VA_ICL_SOW.docx

STATEMENT OF WORK

FOR THE

MRTS 3D® VA INTERNAL COUNTERMEASURE LAUNCHER (ICL) SIMULATION

DEPARTMENT OF THE NAVY

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3275

APPROVED BY: DATE:

Mark Reemsnyder Lead Engineer, Undersea/MRTS 3D Code 4.6.8.4

APPROVED BY: DATE:

David Thomas Program Manager, Undersea/MRTS 3D Code 1.3.6.2.1

DISTRIBUTION STATEMENT C - Distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to COMMANDING OFFICER, NAVAL AIR WARFARE CENTER, TRAINING SYSTEMS DIVISION, 12211 Science Drive, Orlando, FL 32826-3224

MRTS 3D ACTS IDIQ DO

ICLS DO

1 JUNE, 2018

Multipurpose Reconfigurable Training System (MRTS) 3D, MRTS 3D, and the MRTS 3D logo are registered trademarks of the U.S. Navy.

1. SCOPE

This statement of work (SOW) defines the effort required for the design, fabrication, installation, testing, and delivery of the VIRGINIA (VA) class submarine’s Internal Countermeasure Launcher (ICL) system simulation, hereafter referred to as “MRTS 3D® ICL”. Acceptance testing for the MRTS 3D ICL shall be conducted either at the Advanced Computer-based Training System (ACTS) IDIQ contractor’s site or at the Naval Air Warfare Center Training Systems Division (NAWCTSD), Orlando, FL and will be at the discretion of the government.

1.1. Background

The MRTS 3D concept consists of networked, PC-based systems utilizing flat panel touch screen technology to simulate tactical equipment for operations and maintenance training. MRTS 3D uses the Unity® 3D Game Engine and a MRTS 3D Instructor Operating System (IOS) Middleware and Software Development Kit (MSDK), hereafter referred to as the MRTS 3D MSDK. The MRTS 3D MSDK supplements the Unity 3D gaming engine with software modules designed for reuse across multiple programs. All MRTS 3D software is either Government owned, royalty free, and incurs no licensing fees. MRTS 3D provides a suitable training environment to support the hands-on, skills training required by the selected training tasks.

The Fleet would like to conduct operational training on the VA class Submarine’s ICL on a MRTS 3D system.

1.2. Overview

The MRTS 3D ICL simulates tactical system components necessary for an ICL operator training using the MRTS 3D concept.

1.3. Method of Tasking

This delivery order (DO) will be conducted in accordance with the ACTS SOW and will be a Firm Fixed Price (FFP) procurement.

2. APPLICABLE DOCUMENTS

The following Government Furnished Documents (GFD) form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1. Referenced Government Documents

The following specifications, standards, and handbooks of the exact revision listed below form a part of this specification to the extent specified herein.

(Copies of these documents are available online at http://quicksearch.dla.mil/ or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

2.2. Other Government documents, drawings, publications and media Government documents, drawings, publications and media of the ACTS IDIQ SOW shall be used as needed.

2.3. Non-Government Furnished Documents

Non-Government documents listed in the ACTS IDIQ SOW shall be used as needed.

2.4. Government Furnished Information (GFI)

The following Government documents, drawings, publications and media form a part of this document to the extent specified herein.

MRTS 3D Documentation:

Fault Insertion Guide (FIG) template

Self-explanatory

ICL Documentation:

3. REQUIREMENTS

3.1. General

The requirements defined herein form the basis for all work and products delivered to the Government as a part of the DO. This SOW defines the scope of the projects which apply to the contract. The Contractor shall organize, coordinate, and control all program activities under contract to ensure compliance with the contract requirements and delivery of the required products and incidental services. The Government shall retain unlimited rights to all works, as defined at DFARS clause 252.227-7020, created, generated, or produced and required to be delivered under this contract. The Contractor shall assign copyright to the Government for all works that are required to be delivered under this DO. All requirements from ACTS IDIQ SOW, Section 3 shall be followed in the execution of this delivery order when applicable in the development of the products defined herein.

The expected delivery timeframes are as follows:

a. The government desires the MRTS 3D ICL Software Product to be delivered no later than 12 months after DO award. The contractor shall include a projected delivery schedule in their proposal.

The following plans shall be submitted within 30 days of contract award.

a. CDRL A001 – Software Development Plan (SDP): The SDP shall be reviewed for completeness for the work defined in this DO and delivered at the Kickoff meeting if changes are warranted.

b. CDRL A002 – Systems Engineering Master Plan (SEMP): The SEMP shall be reviewed for completeness for the work defined in this DO and delivered at the Kickoff meeting if changes are warranted.

c. CDRL A003 – Configuration Management Plan (CMP): The CMP shall be reviewed for completeness for the work defined in this DO and delivered at the Kickoff meeting if changes are warranted.

d. CDRL A004 – Risk Management Plan (RMP): The RMP shall be reviewed for completeness for the work defined in this DO and delivered at the Kickoff meeting if changes are warranted.

e. CDRL A005 – Test & Evaluation Master Plan (TEMP): The TEMP shall be reviewed for completeness for the work defined in this DO and delivered at the Kickoff meeting if changes are warranted.

f. The contractor shall perform all tasks and subtasks in ACTS SOW Section 3.1.2.2 Operations Security (OPSEC) Plan.

3.2. Detailed Tasks

3.2.1. Simulator Design, Development and Fabrication

This DO will consist of the following subtasks:

3.2.1.1. Product development – MRTS 3D ICL Software Product will be inclusive of the following requirements:

3.2.1.1.1. Under this DO, the contractor shall develop a software product to include operations in accordance with the MRTS 3D ICL Performance Specification.

3.2.1.1.2. Under this DO, the contractor shall produce, update, verify or provide documentation for the CDRLs outlined in Paragraph 3.2.3, Required CDRLs and Table A - 1 CDRL List.

3.2.1.2. MRTS 3D ICL Travel

3.2.1.2.1. Under this DO, the contractor shall propose travel to ensure resources are employable to complete and support associated requirement tasks/events, as agreed upon by the Government. The contractor shall refer to the most current Joint Travel Regulation (JTR) as a guideline for reimbursable costs.

3.2.2. Systems Engineering Processes (SEP)

The contractor shall use the system engineering processes as defined in the ACTS SOW Section 3.2.2 to define the requirements for the MRTS 3D ICL. The contractor shall perform all the tasks and subtasks in ACTS SOW Section 3.2.2 and the following subtasks.

3.2.2.1. Cybersecurity

The contractor shall perform all tasks and subtasks in ACTS SOW Sections 3.1.3.2, 3.1.3.7, 3.1.3.8, 3.1.3.9, and 3.1.3.10.

3.2.2.2. MRTS 3D ICL Software Development

The contractor shall develop the MRTS 3D ICL Software Application IAW the provided GFI listed in 2.4 above as reference along with the MRTS 3D MSDK as outlined in NAVAIR documentation. The contractor shall develop an Instructor Operating System (IOS) plugin IAW the MRTS 3D MSDK to meet the MRTS 3D ICL IOS application software requirements. The contractor shall use the following features of the MRTS 3D MSDK; the IOS framework, the MRTS 3D Data Tracking System (MDTS) to store student records, the Simulation Based Model (SBM) framework of the MRTS 3D SDK, and the networking model to meet the MRTS 3D ICL application software requirements. The contractor shall develop the MRTS 3D ICL IOS and client station software IAW the MRTS 3D Style Guide Specification. The contractor shall develop the MRTS 3D client software IAW the ACTS Modeling Guide. Some of the GFI supplied will be CONFIDENTIAL and possibly SECRET, the training application shall be at a maximum level of For Official Use Only (FOUO). The desired classification level is UNCLASSIFIED.

3.2.2.3. The contractor shall be responsible for deriving any required step-by-step procedures from the NAVSEA OD 44979 Volume 02 Part 14(Firing Craft Operating Procedures and Checklists for 3-Inch Launcher) to drive the simulator.

3.2.2.4. Fault Design Documents (FDDs) for ICL simulation

The contractor shall develop Fault Design Documents (FDDs) for the corrective actions of the operator faults listed in the System Specification for the MRTS 3D ICL, in accordance with the detailed Software Requirements Specification (SRS) and the Requirements Traceability/Verification Matrix (RTVM) developed as a part of this DO, and using the GFI listed in 2.4 above as reference. These documents shall be delivered IAW CDRL A00B, Software Design Description (SDD).

The contractor is encouraged to use the legacy Fault Design Documents, included as GFI, as a reference, but develop their own format for the Fault Design Documents, as these design documents will be utilized by Graphics Artists and Software Developers in the development of the faults.

3.2.2.5. Fault Insertion Guides (FIGs) for ICL Faults

The contractor shall develop FIGs for operator and maintenance faults, outlined in the System Specification for the MRTS 3D ICL using the FIG Template, provided as GFI, as a reference. These guides shall be delivered IAW CDRL F003, the Software User Manual (SUM).

3.2.2.6. Simulations for the Fault Troubleshooting and Corrective Action for ICL Faults The contractor shall simulate the Fault Troubleshooting for the ICL faults, outlined in the System Specification for MRTS 3D ICL IAW the detailed SRS and RTVM, the FDDs and FIGs developed as a part of this DO, and utilizing the GFDs and GFI provided with this DO.

3.2.2.7. Simulator Operator System

The contractor shall use a Windows 10 Secure Host Baseline (SHB) in all MRTS ICL computers.

3.2.2.8. Conferences/Meetings

The contractor shall conduct, attend, and participate in meetings and reviews to be held at both the contractor and Government facilities. The specific locations, dates, and duration of the meetings shall be as specified in the DO. Meetings and reviews will be chaired by a Government representative. The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare drawings and other data to aid in the presentations. The contractor shall have key personnel and support available to carry out the meeting. Subcontractors shall attend meetings and reviews when required to address key elements. The contractor shall prepare the Conference Agenda (CDRL B002), Conference Minutes (CDRL B003), and Presentation Material appropriate for the meetings and reviews. Except where noted herein, meetings and reviews shall be considered fulfilled when the following items are completed:

A. A formal meeting has been conducted and the meeting and reviews are presented to the Government.

B. Topics required for discussion and presentation have been covered.

C. Action items requiring contractor response have been resolved.

D. The Government has accepted the meeting minutes.

3.2.2.8.1. Systems Engineering Technical Reviews (SETR)

The contractor shall conduct and participate in SETR events chaired and attended by the Government. The SETR events will be conducted IAW NAVAIRINST 4355.19D. The SETRs shall not be a place for problem solving, but to verify that problem solving has been accomplished. The SETR shall be event driven vice schedule driven and are scheduled when the required system baseline has achieved a level of maturity for the intended review. Any results from the SETR shall not eliminate the contractor’s responsibility to meet contract requirements. Regardless of Government interaction in the design review process, the contractor shall maintain design responsibility for the system.

3.2.2.8.1.1. Kick-off Meeting

The contractor shall attend a government-scheduled one-day kick-off meeting at the Government’s facility within 30 days of issuance of a DO. The purpose of the kick-off meeting shall be to establish the framework of the contractor and Government interaction during the performance of the DO. The contractor’s management leads, functional leads, technical leads and contractual personnel should be in attendance. At a minimum, the contractor shall present:

A. Introduction and contract overview B. Discussion and clarification of Spec and SOW requirements C. Presentation of a complete, accurate, and realistic Integrated Master Schedule (IMS) and detailed schedule with status D. Identification of the critical paths within the IMS and detailed schedule E. CDRL delivery schedule and status F. Program life cycle model selection and rationale G. Action item reporting and status H. Long lead time item identification and status I. Contractor IPT structure (names, responsibilities, phone numbers, and email addresses) J. Monthly report content and format (Metrics collection process, analysis, and reporting)

3.2.2.8.1.1.1. Kick-off Meeting Entry/Exit Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. The government has reviewed and accepted:

i. Systems Engineering Master Plan (SEMP)

ii. Reviewed Software Development Plan (SDP)

3. The contractor has delivered its first submission of:

i. Configuration Management Plan (CMP)

ii. Risk Management Plan (RMP

iii. Test & Evaluation Master Plan (TEMP)

4. The contractor has delivered the Integrated Master Schedule.

B. Exit Criteria

1. Meeting topics have been discussed

2. Reviewed and accepted the following plans:

i. Systems Engineering Master Plan (SEMP)

ii. Software Development Plan (SDP)

iii. Configuration Management Plan (CMP)

iv. Risk Management Plan (RMP)

v. Test & Evaluation Master Plan (TEMP)

3. Risks and mitigations have been discussed, documented, and agreed upon.

4. Action Items assigned with suspense dates for closure

5. Integrated Master Schedule accepted.

C. Meeting Minutes – Meeting minutes shall be consolidated by the contractor and submitted to the government.

3.2.2.8.1.2. System Requirements Review(SRR)-II- System Functional Review (SFR) The contractor shall conduct a combined SRR-II-SFR. The SRR-II is a multi-disciplined product and process assessment to ensure that the system under review can proceed into preliminary design, and that the system functional requirements, including derived and decomposed requirements, are defined and consistent with program cost, schedule, risk, and other system constraints. The SRR-II-SFR shall assess the system functional requirements and ensure that the required system performance is fully defined and is traceable to the functional baseline described in the SOW and associated specification. At the SRR-II-SFR, the contractor shall:

A. Identify and discuss program resource availability to support the schedule B. Describe implementation of the SDP C. Provide a software system organizational structure D. Show that the functional requirements are traceable to the system requirements E. Show that the explicit and derived requirements are quantified and documented F. Address the following applicable functional areas:

1. Test and Evaluation (T&E)

2. Logistics

3. Information Assurance (IA)

4. Configuration Management (CM) G. Present the results of a comprehensive risk assessment for design, integration, and testing

3.2.2.8.1.2.1. SRR-II-SFR Entry/Exit Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. Contractor presentation material has been delivered to the Government with sufficient time for review (at least five (5) working days) prior to the event.

3. The RTVM has been submitted to the Government IAW CDRL A007 first submission requirements.

4. All applicable updated SRS documents submitted to the Government IAW CDRL A009 first submission requirements.

5. IMS submitted with any changes noted with substantiation.

B. Exit Criteria

1. Meeting topics have been discussed

2. RTVM accepted

3. Updated SRS documents accepted

4. Risks and mitigations have been discussed, documented, and agreed upon.

5. Integrated Master Schedule accepted.

6. Action items assigned with suspense date for closure.

C. Meeting Minutes – Meeting minutes shall be consolidated by the contractor and submitted to the government. As part of the minutes the presentation material shall be revised and submitted to document any changes requested by the Government or proposed by the contractor.

3.2.2.8.1.3. Preliminary Design Review (PDR)

The contractor shall conduct a PDR. The purpose of the PDR is for the Government to formally review the activities and work products generated by the contractor during the performance of the preliminary design stage in order to develop the allocated baseline, and to verify that the approach for the system design is ready to proceed into the detailed design phase. The contractor shall present and describe the proposed training system design and program status. The following items shall be topics of discussion and presentation at the PDR:

A. Training system software design, including:

1. Instructor Operator Station (IOS) IAW SDK IOS Framework

2. Trainee station

3. Computational systems

4. SDK Subcomponents

i. Network

ii. Software tools

iii. Trainer databases

iv. Design modularity and commonality

v. Simulation Based Model

5. Software development files

6. Software interfaces B. Contractor facility and integration lab planning C. Logistics design aspects and concerns D. T&E E. Security and IA, including systems security design, initial security risk assessment, security test approach, security training approach, and any other security and IA relevant information.

F. Program problem and risk areas, recommended solutions, and evaluation of alternatives G. Updated RTVM

3.2.2.8.1.3.1. PDR Entry/Exit Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. Contractor presentation material has been delivered to the Government with sufficient time for review (at least five (5) working days) prior to the event.

3. RTVM has been submitted to the Government IAW CDRL A007 subsequent submission requirements noting any changes, as required.

4. All SDD documents as identified by the contractor and agreed upon by the Government, submitted to the Government IAW CDRL A00B first submission requirements.

5. IMS submitted with any changes noted with substantiation.

6. Preliminary Test Plan submitted IAW CDRL A00D

B. Exit Criteria

1. Meeting topics have been presented, discussed, and documented

2. RTVM accepted

3. SDD documents accepted with noted changes as discussed with authorization to proceed to critical design phase.

4. Risks and mitigations have been discussed, documented, and agreed upon.

5. Integrated Master Schedule accepted.

6. Action items assigned with suspense date for closure.

C. Meeting Minutes – Meeting minutes shall be consolidated by the contractor and submitted to the government. As part of the minutes the presentation material shall be revised and submitted to document any changes requested by the Government or proposed by the contractor.

3.2.2.8.1.4. Critical Design Review (CDR)

The contractor shall conduct a CDR. The purpose of the CDR is for the Government to formally review the activities and work products generated by the contractor during the performance of the critical design stage in order to develop the product baseline, and to verify that the system is ready to proceed into the hardware-software coding, assembly, and integration phase. The contractor shall present and describe the finalized training system design and program status, and address the design changes made since the PDR. The following items shall be topics of discussion and presentation at the CDR:

A. Training system software design, including:

1. Instructor Operator Station (IOS) IAW SDK IOS Framework

2. Trainee station

3. Computational systems

4. SDK Subcomponents

i. Network

ii. Software tools

iii. Trainer databases

iv. Design modularity and commonality

v. Simulation Based Model

5. Software development files

6. Software interfaces B. Contractor facility and integration lab planning C. Logistics design aspects and concerns D. T&E E. Security and IA, including systems security design, initial security risk assessment, security test approach, security training approach, and any other security and IA relevant information.

F. Program problem and risk areas, recommended solutions, and evaluation of alternatives G. Updated RTVM

3.2.2.8.1.4.1. CDR Entry/Exist Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. Contractor presentation material has been delivered to the Government with sufficient time for review (at least five (5) working days) prior to the event.

3. RTVM has been submitted to the Government IAW CDRL A007 subsequent submission requirements noting any changes, as required.

4. All SDD documents as identified by the contractor and agreed upon by the Government, submitted to the Government IAW CDRL A00B first submission requirements.

5. IMS submitted with any changes noted with substantiation.

6. Preliminary Test Plan submitted IAW CDRL A00D

B. Exit Criteria

1. Meeting topics have been presented, discussed, and documented

2. RTVM accepted

3. SDD documents accepted

4. Risks and mitigations have been discussed, documented, and agreed upon.

5. Integrated Master Schedule accepted.

6. Action items assigned with suspense date for closure.

C. Meeting Minutes – Meeting minutes shall be consolidated by the contractor and submitted to the government. As part of the minutes the presentation material shall be revised and submitted to document any changes requested by the Government or proposed by the contractor.

3.2.2.8.1.5. Integrated Product Team (IPT) Meetings

The contractor shall attend and participate in IPT meetings to be conducted throughout the entire contract. IPT meetings shall provide a forum suitable for maintaining a continuous interchange of ideas, issues, and to identify and resolve potential problem areas. Upon request, the contractor shall document the agenda and conference minutes IAW CDRL B003.

3.2.2.8.1.6. In-Process Reviews (IPR)

The contractor shall conduct IPRs as required IAW IDIQ SOW.

3.2.2.9. System Test and Evaluation (T&E)

The testing events shall be designated as Developmental Test (DT) events. The test phases are designated as DT-1 (NPE) through DT-3 (GFI). The contractor shall attend and participate in the T&E IPT meetings. T&E IPT meetings will be the forum for discussion, coordination, and resolution of test planning goals, strategy, and issues.

3.2.2.9.1. T&E Program Components

The T&E program shall consist of test phases described below and in the TEMP (CDRL A005). Test phases will be structured by the T&E IPT to provide the DT required to support the verification of requirements. The T&E program for this delivery order shall consist of the following components:

A. DT-1 (Government Preliminary Evaluations) B. DT-2 (Contractor Preliminary Inspection (CPI)) C. Test Readiness Review (TRR-1) D. Physical Configuration Audit (PCA)

E. DT-3 (GPI)

F. TRR-2

3.2.2.9.1.1. DT-1 (Navy Preliminary Evaluation (NPE))

Government Subject Matter Experts (SMEs) and engineers will perform preliminary evaluations during the development of the product to ensure early identification of major problem areas. DT-1 (NPE) shall occur in-plant after hardware assembly or in the integration labs, depending on the type of DO. DT-1 (NPE) shall occur when sufficient controls and displays are operational to evaluate trainer characteristics, to determine the training potential, and to determine if there are gross deficiencies of the fidelity of the trainer. The contractor shall provide operational support for test procedures established by the Government test team. Full systems operation is not required but special recording instrumentation that may not be a part of the normal trainer configuration shall be available for use during DT-1 (NPE). Tests conducted shall include the trainer characteristics tests specified herein. When needed, additional DT-1 (NPE) phases (i.e., DT-1a, DT-1b, and so on) shall be scheduled for the purposes of evaluating changes made to correct problem areas and to assess progress with the integration of major trainer subsystems. The timing, duration, and number of DT-1 (NPE) phases shall be coordinated between the contractor and Government test team as part of the T&E IPT meetings.

3.2.2.9.1.1.1. Exit Criteria

To consider DT-1 successful and proceed to Contractor Preliminary Inspection, the following criteria needs to be demonstrated met:

A. Preliminary Test Procedures accepted B. All requirements have been implemented and the software is mature enough that no discernable Priority 1 or 2 deficiencies exist in the software.

3.2.2.9.1.2. DT-2 (Contractor Preliminary Inspection)

The contractor shall perform DT-2 (CPI) in-plant IAW the Government-accepted test plan (TP) and other Government-accepted test plans as documented in the TEMP (CDRL A005) using the appropriate trainer hardware. A Government technical representative may witness the performance of DT-2 (CPI). The contractor shall document that the test procedures have been run start-to-finish as a complete test, without segregation of elements of individual tests, prior to TRR-1. The contractor shall annotate in the TP, procedural changes made as a result of DT-2 (CPI) and shall provide a copy of the annotated TP to the Government prior to the start of DT-3 (GPI). The contractor shall document the DT-2 (CPI) results in the Test/Inspection Report. The contractor shall record tests results that do not comply with specification requirements as deficiencies. The contractor shall correct the deficiencies found during DT-2 (CPI) prior to the commencement of DT-3 (GPI). The documented DT-2 (CPI) results, including open deficiencies, shall be presented to the Government on an incremental basis at the next scheduled T&E IPT meeting and in final total form at the Test Readiness Review-1 (TRR-1).

3.2.2.9.1.2.1. DT-2 Entry/Exist Criteria

A. Entrance Criteria

1. Test Plan submitted to the Government IAW CDRL A00D subsequent submission requirements, noting any changes since CDR.

2. Test Procedures submitted to the Government IAW CDRL A00E first submission requirements.

3. All logistics documentation CDRLs have been submitted to the Government IAW their respective first submission requirements. Affected CDRLs are:

4. Software User Manual (SUM) (CDRL F003)

B. Exit Criteria

1. Test Plan executed with all deficiencies recorded with no Priority 1 or 2 deficiencies noted. All Priority 3, 4 and 5 deficiencies have been reviewed and agreed upon by the Government as acceptable.

2. All redlines to the test plan and procedures have been reviewed and approved by the Government.

3. Action items assigned with suspense date for closure.

3.2.2.9.1.3. Test Readiness Review-1

TRR-1 will be conducted by the Government, following completion of DT-2 (CPI) and after the TRR entry criteria specified in the DO. The purpose of the TRR-1 is to determine trainer readiness for DT-3 (GPI). The contractor shall provide the resources, including facilities, equipment, and personnel to support the TRR-1. The TRR-1 will include a review of the T&E program, including the test results, presentation of contractor certification of test readiness, and open deficiencies remaining from DT-2 (CPI). The contractor shall present the RTVM, in contractor’s format, to verify that the DO requirements have been tested. The TRR-1 shall include a contractor-conducted, Government-witnessed demonstration of trainer stability for testing. The trainer stability demonstration shall consist of the performance of a stress test IAW the verification requirements of the DO. The TRR-1 will be repeated until the trainer has been determined by the Government to be acceptable for commencement of the Conformance Inspections. TRR-1 will be considered complete when all DRs are resolved and an acceptable level of program risk is ascertained. During TRR-1, the following shall be reviewed and discussed:

A. Trainer test procedures B. Updated RTVM to verify specification requirements have been tested C. DT-2 (CPI) test results (including Software Items (SI) test results) and deficiencies when applicable D. DT-3 (GPI) Test Inspection Report Submitted E. Identification of software test tools to be used during DT-3 (GPI) F. Summary of software problems status G. Courseware H. Status of spare capacities, such as CPU (timing), memory capacity, and disk storage I. Cold start procedures J. Mission exercises K. Logistic Support

3.2.2.9.1.3.1. TRR-1 Entry/Exit Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. RTVM has been submitted to the Government IAW CDRL A007 subsequent submission requirements noting any changes, if required.

3. Test/Inspection results with any deficiencies reports from DT-2 submitted to the Government IAW CDRL A00F subsequent submission requirements.

4. IMS submitted with any changes noted with substantiation.

5. Test Plan submitted to the Government IAW CDRL A00D subsequent submission requirements, if changes were encountered in testing. Changes to the Test Plan shall be identified.

6. Test Procedures submitted to the Government IAW CDRL A00E subsequent Submission requirements, if changes were encountered in testing. Changes to the Test Procedures shall be identified.

B. Exit Criteria

1. Meeting topics have been presented, discussed, and documented

2. RTVM accepted and approved

3. Test Plan accepted and approved as Final

4. Test Procedures accepted and approved as Final

5. All deficiencies have been recorded, categorized, and dispositioned with:

i. All priority 1 & 2 deficiencies have been resolved

ii. All priority 3 deficiencies have Government approved workarounds identified.

iii. All priority 4 and 5 deficiencies agreed upon as acceptable for delivery

6. Risks and mitigations have been discussed, documented, and agreed upon.

7. Integrated Master Schedule accepted.

8. Action items assigned with suspense date for closure.

3.2.2.9.1.4. DT-3 (Government Preliminary Inspection)

DT-3 (GPI) will commence upon notification by the Government’s technical representative that the exit criteria for TRR-1 have been met. DT-3 (GPI) will be conducted in-plant by the Government test team as defined in the TEMP (CDRL A005). DT-3 (GPI) will consist of Government-conducted tests to demonstrate compliance with the specified performance requirements. DT-3 (GPI) will be conducted IAW the Government-accepted TP (revised to include corrections made during DT-2 (CPI)) and other Government-accepted test plans as documented in the TEMP (CDRL A005). The contractor shall provide the Government with a copy of the revised TP prior to DT-3 (GPI). The Government reserves the right to perform additional tests to ensure compliance with the specified requirements. Testing will commence with the establishment of a software baseline resulting from a PCA and cold start requirements specified in this SOW, the verification requirements of the DO, and the Government-accepted TP. Following the cold-start, the Government will perform the IA verifications IAW the verification requirements of the DO, and the Government-accepted TP. Deficiency correction verification and validation, including additional cold-starts, will be at the discretion of the Government test team. The typical test schedule may consist of a 10-hour test day followed by the contractor’s deficiency clean-up and trainer maintenance periods. The contractor shall provide the resources, personnel, equipment, and facilities needed to support the tests. Software configuration item testing and design documentation verification and validation will be conducted as an integral part of DT-3 (GPI). Deficiencies found during these tests shall be corrected by the contractor and verified by the Government test team prior to shipment of the trainer to the installation site, unless otherwise authorized by the Government test director.

3.2.2.9.1.5. DT-3 (GPI) Exit Criteria

The exit criteria for DT-3 (GPI) shall consist of Government concurrence with the following:

A. Cold start has been successfully performed to establish the trainer’s software baseline configuration to be used for testing.

B. TP tests have been executed and accepted.

C. A complete TP test or acceptable regression test series representative of the complete TP (as determined by the Government) has been run after the final DR ready for re-test. TP tests may be reduced within acceptable regression testing guidelines determined by the Government.

D. Updated tests results have been recorded in the contractual test documentation, including date/time of final results and red-lines (when necessary).

E. Deficiencies have been documented, categorized for severity, and tracked to final resolution.

F. DT-3 (GPI) has demonstrated that test equipment needed to execute the complete TP has been used, functions properly, and is currently available, calibrated, and working.

G. CM baseline (software and hardware) has been maintained throughout DR correction. CM deficiencies identified during DT-3 (GPI) have been corrected.

3.2.2.9.1.6. Test Readiness Review-2

TRR-2 will be conducted by the Government, following completion of DT-3 (GPI) and after the TRR-2 entry criteria specified below have been met. TRR-2 will be considered complete when all DRs are addressed per the guidance below and an acceptable level of program risk is ascertained. During the TRR-2, the following shall be reviewed and discussed:

A. Trainer test procedures B. Updated RTVM to verify specification requirements have been tested C. Recorded R&M data D. The contractor’s test log E. DT-4 (CFI) test results (including SI test results) and deficiencies F. Test discrepancy reporting process and applicable test discrepancy report form to be used during DT-5 (GFI).

G. Identification of software test tools to be used during DT-5 (GFI) H. Summary of software problems status I. Courseware J. Status of spare capacities, such as CPU (timing), memory capacity, and disk storage K. Cold start procedures L. Mission exercises M. Logistic Support

3.2.2.9.1.6.1. TRR-2 Entry / Exit Criteria

A. Entrance Criteria

1. Contractor submitted agenda is complete and acceptable

2. RTVM has been submitted to the Government IAW CDRL A007 as final.

3. Test/Inspection results with no deficiency reports from DT-3 submitted to the Government IAW CDRL A00F subsequent submission requirements.

4. Final Test Procedures submitted to the Government IAW CDRL A00E subsequent submission requirements.

5. All logistics documentation CDRLs have been submitted to the Government IAW their respective subsequent submission requirements. Affected CDRLs are: A00H, E001, F001, F002 and F003.

6. PCA has been successfully conducted.

B. Exit Criteria

1. Meeting topics have been presented, discussed, and documented

2. All products have been demonstrated to be functional with no unacceptable deficiencies.

3. All documentation has been delivered and accepted in final format.

4. RTVM accepted and approved as final

5. All deficiencies have been recorded, categorized, and dispositioned:

i. All priority 1 & 2 deficiencies have been resolved

ii. All priority 3 deficiencies have Government approved workarounds identified.

iii. All priority 4 and 5 deficiencies agreed upon as acceptable for delivery

6. All action items associated with the project have been closed.

3.2.2.9.1.7. Physical Configuration Audit (PCA)

A PCA will be conducted in conjunction with DT-3 (at the approved DT-3 site) to ensure that all updates, primarily software and documentation, have been properly delivered and installed in the MRTS EPM. All logistics documentation CDRLs shall be submitted to the Government IAW their respective second submission requirements. The PCA shall be conducted by the Government with assistance from the contractor. At the successful completion of PCA the terms of this delivery order are considered complete.

3.2.3. Required CDRLs

The following CDRLs are required and shall be delivered by the contractor to support this DO:

A. CDRL A007 – Requirements Traceability/Verification Matrix (RTVM): An updated RTVM for the MRTS 3D ICL. The contractor shall develop the RTVM according to their methods and tools using the GFI provided with this delivery order and the detailed SRS developed as a part of this DO. The contractor shall maintain the RTVM throughout the life of this contract and deliver the final RTVM to the Government at the end of this delivery order.

B. CDRL A009 – Software Requirements Specification (SRS): A detailed SRS shall be developed for the MRTS 3D ICL. For this DO, the detailed SRS shall document the detailed/derived requirements of the MRTS 3D ICL. The contractor shall develop the detailed SRS according to their methods and tools using the MRTS 3D ICL System/Software Requirements Specification (SRS) and other GFI provided with this delivery order.

C. CDRL A00B – Software Design Description (SDD): There shall be, at a minimum, one SDD for each major Computer Software Configuration Item (CSCI) identified at CDR. It is at the contractor’s discretion to identify additional SDDs that may be required to support their development efforts. All application programming interfaces (APIs) that are created to streamline MRTS 3D development efforts shall be documented in the appropriate SDD.

D. CDRL A00D – Test Plan – The contractor shall create the Test Plan IAW with the CDRL.

E. CDRL A00E – Test Procedures – The contractor shall create the Test Procedures IAW with the CDRL.

F. CDRL A00F – Test/Inspection Report – The contractor shall create the Test/Inspection Report IAW with the CDRL.

G. CDRL A00G – Software Version Description: Software Version Description (SVD): The software baseline created for this effort shall be documented with a SVD.

H. CDRL A00J – Computer Software Product End Item (CSPEI): There shall be one combined delivery of all software developed under this delivery order. All software shall be delivered in accordance with CDRL A00J.

I. CDRL A00L – The contractor shall use Engineering Change Proposals (ECPs) and Request for Deviations (RFDs) to request changes to an approved baseline. The contractor shall prepare the Engineering Change Proposal (ECP) and Request for Deviation (RFD) IAW CDRLs A00L and A00M, respectively.

J. CDRL B005 – Integrated Program Management Report, Integrated Master Schedule (IMS) (Only the IMS is required for this CDRL). The contractor shall provide updates to the IMS as required to accurately reflect procurement schedules and advise the government of any slippage in schedule at the earliest possible time.

K. CDRL F003 – Software User Manual (SUM) – The SUM documentation shall be generated and updated as needed in support of MRTS 3D ICL. Fault Insertion Guided (FIGs) for the ICL faults, should be included in the SUM. The contractor shall develop FIGs for the ICL faults. The FIGs will be used by the Instructor during training. The contractor is encouraged to use the FIG Template, included as GFI, as a reference, but may modify the format in the template.

Contract Data Requirements List (CDRL) A.1 All applicable CDRLs are listed in table Table A - 1 CDRL List

A005

image1.jpeg