ATTACHMENT_06_MISTE_DO_SCETI_ACE_SOW_DRAFT_RFP.pdf

Distribution C – Authorized to U.S. Governemnt agencies and their contractors in support of this contracting effort. Other requests for this document shall be referred to PM ITTS, IMO.

STATEMENT OF WORK

FOR

MODERNIZING INSTRUMENTATION SOLUTIONS FOR

TEST AND EVALUATION

(MISTE)

System-of-Systems Controlled Environment Test Infrastructure (SCETI) Atmospheric Conditions Enhancement (ACE)

U.S. Army Program Executive Office for

Simulation, Training, and Instrumentation 12211 Science Drive

Orlando, FL 32826-3276

SOW-2018-0018

28 January 2019

Table of Contents

1 SCOPE

1.1 Background

2 APPLICABLE DOCUMENTS

2.1 Department of Defense Specifications

2.2 Availability of Department of Defense Specifications

2.3 Department of Defense Standards

2.4 Availability of Department of Defense Standards

2.5 Other Government Documents, Drawings, and Publications

2.6 Availability of Other Government Documents and Publications

3 REQUIREMENTS

3.1 Program Management

3.1.1 Integrated Master Schedule (IMS)

3.1.2 Configuration Management (CM)

3.1.3 Technical Performance Measures (TPM)

3.1.4 Risk Management

3.1.5 Management Reviews

3.1.5.1 Post Award Conference and Start of Work Meeting

3.1.5.1.1 Entry Criteria

3.1.5.1.2 Exit Criteria

3.1.5.2 Program Management Reviews

3.1.5.3 Integrated Product Teams

3.1.6 Access and General Protection Policy and Procedures

3.1.7 Anti-Terrorism (AT) Level I Training

3.1.8 iWATCH AT Training

3.1.9 Access to Government Information Systems and Networks

3.1.10 Operational Security (OPSEC) Awareness Training

3.2 Systems Engineering

3.2.1 System Design

3.2.1.1 System Definition Stage

3.2.1.1.1 Atmospheric Conditions Parameter Study

3.2.1.1.2 System Requirements Review

3.2.1.2 Preliminary Design Stage

3.2.1.2.1 Preliminary Design Review

3.2.1.3 Detailed Design Stage

3.2.1.3.1 Critical Design Review

3.2.2 Hardware Engineering

3.2.3 Software Engineering

3.2.4 Hardware and Software Integration

3.2.5 Cybersecurity

3.2.6 Specialty Engineering

3.2.6.1 Safety Engineering

3.2.7 Product Definition Data (PDD)

3.2.8 Site Surveys

3.3 Test Program

3.3.1 Test Readiness Review (TRR)

3.3.2 Contractor Test

3.3.3 Subsystem Testing

3.3.4 Site Acceptance Testing

3.4 Logistics

3.4.1 Supportability Analysis and Logistics Management Information. .. 17

3.4.2 Technical Publications

3.4.2.1 Operator and Maintenance Manuals

3.4.2.2 COTS Manuals

3.4.3 Item Unique Identification (IUID)

3.4.4 Training Products

3.4.4.1 New Equipment Training

3.4.5 Government Furnished Property (GFP)

3.4.6 Quality Assurance Surveillance Plan (QASP)

4 ACRONYMS

Table of Appendices

A.1 APPENDIX A – Review Entry and Exit Criteria and Data Products.22 A.1.1 System Requirements Review Entry and Exit Criteria A.1.1.1 SRR Entry Criteria A.1.1.2 SRR Completion/Exit Criteria A.1.1.3 SRR Products A.1.2 PDR Entry and Exit Criteria A.1.2.1 PDR Entry Criteria A.1.2.2 PDR Completion/Exit Criteria A.1.2.3 PDR Products A.1.3 CDR Entry and Exit Criteria A.1.3.1 CDR Entry Criteria A.1.3.2 CDR Completion/Exit Criteria

Distribution C – Authorized to U.S. Governemnt agencies and their contractors in support of this contracting effort. Other requests for this document shall be referred to PM ITTS, IMO.

A.1.3.3 CDR Products A.1.4 TRR Entry and Exit Criteria A.1.4.1 TRR Entry Criteria A.1.4.2 TRR Exit Criteria A.1.4.3 TRR Products

Statement of Work (SOW) For

System-of-Systems Controlled Environment Test Infrastructure (SCETI) Atmospheric Conditions Enhancement (ACE)

1 SCOPE.

This SOW describes the requirements for developing the SCETI ACE, which includes the development of the Snow Development Capability (SDC), the Fog Development Capability (FDC), and enhancements to the existing Atmospheric Measurement (AM) capability to measure the new environmental conditions. SCETI ACE will be awarded as a Delivery Order (DO) under the Modernizing Instrumentation Solutions for Test and Evaluation (MISTE) contract.

SCETI is an outdoors instrumentation test system currently under development at Redstone Test Center (RTC) and used to verify the functionality of aircraft sensor assemblies within Degraded Visual Environment (DVE) conditions. SCETI will be comprised of an Emulated Flight Capability (EFC) to replicate rotary winged flight scenarios with the sensor assemblies secured to a payload structure, a Rain Development Capability (RDC) to develop DVE rain conditions, and an AM capability to characterize rain and dust developed by the RDC and existing Government dust generation capabilities. The EFC technology is based off existing commercial solutions used in the entertainment industry to capture video via a cablecam. The RDC uses commercial water cannons to generate rain.

The SDC and FDC developed and delivered to RTC under this delivery will generate operationally relevant DVE snow and fog conditions to test and evaluate the functionality and ability of Systems Under Test (SUT) to provide situational awareness to rotary wing pilots in DVE conditions. The enhanced AM will characterize the snow and fog conditions generated in order to support Test and Evaluation (T&E). The contractor will be required to develop and integrate the SDC, FDC, and enhanced AM capabilities into the SCETI instrumentation test facility.

Detailed requirements for the capability to be delivered to SCETI are included in the SCETI ACE System Performance Specification.

1.1 Background.

The U.S. Army Program Executive Office for Simulation, Training and Instrumentation has a requirement to deliver a capability to test DVE pilotage systems in an operationally relevant environment.

As the Army and Department of Defense (DOD) develop new systems to aid aircrews to be able to fly in DVE conditions, these new systems have to be tested. Hardware and software-in-the-loop simulations using spectral specific weather models do not exist.

Currently, the only way to test these new systems is to conduct costly, higher risk open air flight testing in the actual DVE conditions. However, a test program relying solely on flight in naturally occurring DVE conditions will greatly increase test schedule and cost, and ultimately lead to verifying system functionality in only a subset of the desired DVE conditions.

A significant shortfall exists in DVE testing, specifically the lack of capability to test new DVE sensors in emulated flight under controlled DVE conditions. The SCETI program addresses this shortfall by developing a multi-functional test capability that will expose the DVE SUT to controlled, repeatable, and realistic DVE conditions. The capability will create a limited area of controllable, physically induced, and natural DVE environments through which individual or aggregate DVE sensors and systems can be moved, emulating relevant aircraft flight dynamics such that operational system performance can be evaluated. The SCETI capability will interface with RTC test networks to enable pilot-in-the-loop interaction and control of the DVE by Government-developed pilot software. The pilot software will be integrated through a modular interface to produce results that are comparable to open air sensor performance flight test. The capability will be reconfigurable to enable simultaneous testing of multiple aircraft sensors, while minimizing cost and risk compared to traditional open air flight testing.

Currently, a team is developing the SCETI baseline capability at Redstone Arsenal.

The capability is situated over a 1000 foot x 400 foot area on RTC Test Area 6. A modified cablecam system will be used to mount the SUT at this location and place it into emulated flight at heights up to 80 feet through a DVE provided either by dust fans or the RDC. The ACE contractor will be expected to provide snow and fog conditions over a 200 foot long, 100 foot wide and 80 foot high volume within the flight path without interfering with the free range of motion of the SUT.

2 APPLICABLE DOCUMENTS.

2.1 Department of Defense Specifications.

MIL-Performance (PRF)-32216A - Evaluation Of Commercial Off-The-Shelf (COTS) Manuals and Preparation Of Supplemental Data, dated 12 Aug 2011

2.2 Availability of Department of Defense Specifications.

Copies are available on the WWW at URL: http://assist.daps.dla.mil/quicksearch.

http://assist.daps.dla.mil/quicksearch

2.3 Department of Defense Standards.

MIL-STANDARD (STD)-130 - Identification Marking of U.S. Military Property MIL-STD-40051-2C - Page-Based Technical Manuals MIL-STD-810G - Department of Defense Test Method Standard, Environmental Engineering Considerations and Laboratory Tests w/ Change Notice 1

2.4 Availability of Department of Defense Standards.

Copies are available on the WWW at URL: https://assist.dla.mil/online/start/.

2.5 Other Government Documents, Drawings, and Publications.

PRF-PT-703 - System-of-Systems Controlled Environment Test Infrastructure Atmospheric Conditions Enhancement System Performance Specification (SCETI ACE), 14 January 2019

PEO-STRI-2017-W071 - Statement of Work For Modernizing Instrumentation Solutions For Test and Evaluation (MISTE), 12 July 2018

2.6 Availability of Other Government Documents and Publications.

Copies of the above documents are available at Army Contracting Command - Orlando, ATTN: SCETI Contract Specialist, 12211 Science Dr., Orlando, FL 32826-3224

3 REQUIREMENTS.

The contractor shall use their proposed/approved Test Instrumentation Systems Enterprise (TISE) solution under the subject DO, which shall comply with the requirements stated at Sections 3., 3.1, 3.1.1, 3.1.2, 3.2, 3.3, 3.3.1, 3.3.1.1, 3.3.1.2,

3.3.1.3. 3.3.1.4, 3.3.1.5 of the Base MISTE contract SOW (PEO-STRI-2017-W071).

Each individual DO will be fully integrated into the TISE environment to ensure compliance with the Base MISTE contract SOW.

3.1 Program Management.

The contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished In Accordance With (IAW) this SOW. The contractor shall track program progress utilizing metrics. The contractor shall plan, implement, and maintain a Life Cycle Cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design and support alternatives, and select the resource support requirements. The contractor shall define and monitor metrics and Technical Performance Measures (TPMs) to evaluate the performance of each critical technical and management process and conformance of the evolving products with contract https://assist.dla.mil/online/start/ requirements and objectives, including cost requirements and objectives. The contractor shall report program progress to the Government through monthly written reports. (DI-MGMT-80227, Contractor’s Progress Status and Management Report)

3.1.1 Integrated Master Schedule (IMS).

The contractor shall develop, implement, manage to, update, and maintain the ACE IMS. All schedule information delivered or presented at program reviews shall originate from the IMS and shall contain all critical events and exit criteria, accomplishments, predecessor and successor events, and their dependencies. The IMS shall be conformed to the Government schedule as applicable. The IMS shall address total program activities including activities performed by major subcontractors. The contractor shall develop a logical resource loaded network that accurately portrays the sequence and relationship of activities defining the total development program. These network activities shall be keyed to the Contract Work Breakdown Structure (CWBS).

The contractor shall conduct critical path analysis of the tasks to forecast and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

The IMS shall be reported as a part of the contractor’s monthly status report. The current SCETI ACE project schedule is depicted in Figure 3.1.1-1. [DI-MGMT-81861A, Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6]; (DI-MGMT-80227, Contractor’s Progress Status and Management Report); (DI-MGMT-81334D, Contract Work Breakdown Structure)

Figure 3.1.1-1 SCETI ACE Current Project Schedule

3.1.2 Configuration Management (CM).

The contractor shall use an automated internal CM process to ensure designs are traceable to requirements, change is controlled and documented, interfaces are defined, and there is consistency between the product and its supporting documentation.

Contractor’s CM program shall address configuration identification, configuration control, status accounting, and audits within contractor’s overall systems engineering environment. Contractor’s CM program shall employ processes to monitor, update, and control configuration documentation, physical media, and physical parts representing or comprising system configuration items. Contractor’s CM program shall flow down CM responsibilities to subcontractors. Contractor’s CM process shall handle levels of product and process integration to build and support the product, to include Cybersecurity (CS). Contractor shall develop and maintain allocated baseline, initial product baseline, Interface Control Documents (ICD), and software requirements and product specifications until final delivery. Contractor’s CM process shall define software CM to include tools used, software requirements linkage to source code, method and tools for creation and resolution of Deficiency Reports (DRs), frequency and process for interim and final software builds, and how they will be tested. The Government will maintain control of the Functional Baseline (FBL) defined by the system performance specification, ICDs, and software requirement specifications. Contractor shall develop, submit, and maintain a CM Plan as part of the Systems Engineering Management Plan (SEMP) to document CM procedures and processes. Contractor shall execute CM IAW the CM Plan. 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.

3.1.3 Technical Performance Measures (TPM).

The contractor shall select technical performance parameters that reflect key indicators of program success. TPM parameter inter-relationships shall be depicted through construction of tiered dependency trees similar to the specification tree. Each parameter shall be correlated with a specific CWBS element. As the development activity progresses, the achievement to date shall be tracked continually for each of the TPMs. If the data falls outside the tolerance band a new profile or current estimate shall be developed immediately. The current estimate shall be determined from the “achievement to date” and the remaining time and budget. An analysis shall be accomplished on the variation to determine the causes and to assess the impact on higher level parameters, on interface requirements, and on system cost effectiveness.

For performance in excess of requirements, opportunities for reallocation of requirements and resources shall be assessed.

3.1.4 Risk Management.

The contractor shall prepare, implement, and maintain a risk management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The contractor shall develop and implement CS risk management, which will include security safeguards. These safeguards shall include, but are not limited to local policy and guidance, identified threats, problems and requirements. The contractor shall plan for the resources required and provide these safeguards. The contractor’s risk management process shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints. The CS risk shall be addressed across the risk management process, including multiple areas as appropriate. The contractor shall report risks in the monthly status report. The contractor shall be prepared to discuss risks in SCETI Integrated Product Team (IPT) meetings. (DI-MGMT-80227, Contractor’s Progress Status and Management Report)

3.1.5 Management Reviews.

The contractor shall participate in project management reviews. The required meetings are detailed in the following subsections.

3.1.5.1 Post Award Conference and Start of Work Meeting.

A Post Award Conference and Start of Work meeting shall be held at the contractor’s facility with teleconference access within 30 calendar days after contract award. The post award conference shall immediately precede the start of work meeting. The Post Award Conference shall introduce the key IPT participants, identify points of contact, and discuss both parties understanding of the scope of work and other contract issues.

The Start of Work meeting shall be limited to Government personnel and the contractor’s key team members identified in the proposal, and shall be a no more than two-day session with emphasis on top level management of the program, agreement on metrics that will be used as management indicators during the program, and partnering approach to implement.

3.1.5.1.1 Entry Criteria

Prior to the Start of Work meeting the contractor shall meet the following entry criteria:

a. Meeting agenda is coordinated with the Government;

b. Draft SEMP is submitted;

c. Risk Assessment is documented;

d. Contract Data Requirements List (CDRL) clarification items are documented (if applicable);

e. WBS elements developed;

f. IPT structure, members, and responsibilities are documented;

g. SOW clarification items are documented (if applicable);

h. Performance Specification clarification items are documented (if applicable);

i. TPMs have been developed; and

j. Action item reporting approach is documented.

3.1.5.1.2 Exit Criteria

The Start of Work meeting is considered complete after the following exit criteria have been completed:

a. All topics on the meeting agenda have been discussed;

b. Risks identified have been deemed acceptable;

c. All CDRLs have been clarified, if necessary;

d. WBS elements have been established (if applicable);

e. IPT charter with structure, members, and responsibilities has been established;

f. Draft SEMP deemed acceptable;

g. SOW clarification items have been addressed (if applicable);

h. Performance Specification clarification items have been addressed (if applicable);

i. TPMs established and agreed to;

j. Agreements are documented;

k. Meeting minutes have been documented and disseminated; and

l. Action items are assigned with due dates

3.1.5.2 Program Management Reviews.

The contractor shall conduct monthly program management reviews which shall begin no more than one month following the Post Award Conference. The program management reviews may be cancelled or postponed with the approval of the Government’s technical representative when circumstances necessitate. The location of the reviews shall be mutually agreed upon and teleconference access shall be made available. The program management review shall provide a program overview and a detailed discussion of pre-selected topics. Status and information at the review shall reflect currency since the previous review.

3.1.5.3 Integrated Product Teams.

The contractor shall conduct and participate in IPT meetings to be held at both contractor and Government facilities, or by teleconference on a bi-weekly basis. The meetings shall be co-chaired by a Government and contractor representative. IPT meetings shall be used for review of program status, risk management, testing and travel planning, and review of program technical issues.

3.1.6 Access and General Protection Policy and Procedures.

The contractor and all associated subcontractors’ employees shall comply with applicable installation, facility, and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements, as required either by the Provost Marshal Office, Director of Emergency Services, or the Security Office. The contractor workforce must comply with all personal identity verification requirements, as directed by DOD, Headquarters, Department of the Army, and/or local policy. Contractors shall be escorted during the period of time that they are at RTC to conduct site surveys;

characterization studies; installation and integration; and facilitate testing.

3.1.7 Anti-Terrorism (AT) Level I Training.

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, and controlled access areas shall complete AT Level I Awareness training within 30 calendar days after contract start date, or within 30 calendar days of new employees commencing employment. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the Government within 10 calendar days after completion of training by affected employees and subcontractor personnel. AT Level I Awareness training is available at the following website: https://atlevel1.dtic.mil/at.

3.1.8 iWATCH AT Training The contractor and subcontractors shall brief employees on the local iWATCH program, which details training standards that are provided by the requiring activity AT Officer.

iWATCH training will be used to inform employees of the types of behavior to watch for, and instruct employees how to report suspicious activity to the appropriate personnel.

Government will provide iWATCH training package to contractor and associated subcontractor for execution. iWATCH training shall be completed within 30 calendar days of contract award, and prior to commencing work performance.

The contractor shall provide a training completion list to the Government prior to work performance.

3.1.9 Access to Government Information Systems and Networks.

All contractor and subcontractor employees who require access to Government information systems or networks shall be registered in the Army Training Certification Tracking System and shall complete the DOD Cyber Awareness Challenge training on an annual basis before issuance of access. The contractor shall identify all contractors https://atlevel1.dtic.mil/at who require access to Government information systems or networks for approval by the Government. DOD Cyber Awareness Challenge training can be accessed at https://ia.signal.army.mil/DoDIAA/.

3.1.10 Operational Security (OPSEC) Awareness Training

Contractor employees and all associated subcontractors requiring access to Government installations, facilities, and controlled access areas shall complete Level I OPSEC Awareness training within 30 calendar days after the contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable, and annually thereafter. New employees shall be trained within 30 calendar days of their reporting for duty and annually thereafter. OPSEC Awareness training is available at the following website: http://cdsetrain.dtic.mil/opsec.

3.2 Systems Engineering.

The contractor shall implement a system engineering process that will transform all system/subsystem and IA/CS requirements into a set of lower level performance requirements that define the system. The process shall accomplish planning of technical activities; identify and allocate functional requirements; identify necessary trade studies and other activities to reduce risk; develop technical documentation; and include design reviews. The system engineering effort shall integrate all elements of a multifunctional engineering effort to meet system requirements. The contractor shall ensure the timely integration of engineering specialties such as reliability, maintainability, security engineering, logistics engineering, human factors engineering, safety, value engineering, standardization, and transportability into the development process. The contractor shall develop and complete all planned tasks for each milestone. The contractor shall as part of the systems engineering effort develop, update, and maintain the SEMP as a living document. The contractor shall use the SEMP to identify and assure control of the overall technical management process.

(DI-SESS-81785A, Systems Engineering Management Plan)

3.2.1 System Design.

The contractor shall design, integrate, test, verify, deliver, install, train users, and provide documentation IAW the SCETI ACE Performance Specification and SOW. The contractor shall use commercial and best industry processes and practices to reduce development, production, and operational support costs to the maximum extent possible without changing the Government requirements. The contractor shall produce designs and specifications based on performance, affordability, wide industry use and consensus/acceptance, long-term availability and supportability, and upgradeability.

https://ia.signal.army.mil/DoDIAA/ http://cdsetrain.dtic.mil/opsec

At the conclusion of each design stage, the contractor shall participate in various system engineering reviews – Preliminary Design Review (PDR) for Preliminary Design, or Critical Design Review (CDR) for Detailed Design – prior to approval to enter the next stage of development. The contractor shall document the results of each review, including any resulting action items. Additionally, the contractor shall conduct Technical Interchange Meetings as required. The contractor shall meet all entrance and exit criteria for each review as specified in Appendix A – Review Entry and Exit Criteria and Data Products.

3.2.1.1 System Definition Stage.

The contractor shall complete the system, subsystems, interface requirements, and verification definitions. The contractor shall establish a system baseline and complete technical reviews. The contractor shall decompose system requirements into subsystem requirements, allocate requirements to subsystem specifications, and derive requirements at the subsystem and component levels required to meet performance requirements at the system level. The documentation generated during system definition shall be used to guide subsystem design, development, and integration. The contractor shall develop System/Subsystem Specifications with traceability to the System Performance Specification in a format compatible with the International Business Machines (IBM) Rational Dynamic Object-Oriented Requirements System (DOORS) requirements management tool, in addition to standard human-readable documentation format(s). The contractor shall document traceability between performance, system, and subsystem specification requirements in a Requirements Traceability Verification Matrix (RTVM). Decisions made in arriving at the system definition configuration are well supported by analysis, test, and other technical data, including estimation of the manpower required to operate and maintain the system, the skills and abilities of the personnel required to operate and maintain the system, the training plan for operators and maintainers, and safety and health hazard considerations associated with the system.

At the end of System Definition Stage, the contractor shall enter and successfully complete a System Requirements Review (SRR) prior to initiating Preliminary Design.

(DI-IPSC-81431A, System/Subsystem Specification); (DI-MGMT-82133, Requirements Traceability Verification Matrix)

3.2.1.1.1 Atmospheric Conditions Parameter Study.

As part of the system definition effort, the contractor shall complete a study to determine the appropriate operationally relevant characteristics of snow and fog DVE conditions.

The contractor shall identify the characteristics to be generated by the SDC and FDC which shall be measurable by the enhanced AM capability. MIL-STD-810G, Department of Defense Test Method Standard: Environmental Engineering Considerations and Laboratory Tests, Part 3 World Climatic Regions-Guidance, Paragraph 5.3, can be used as guidance for determining snow characteristics. The contractor shall provide a report on the results of the study to the Government, and shall use the results of this study to update the System/Subsystem Specifications. (DI-MISC- 80711A, Scientific and Technical Reports)

3.2.1.1.2 System Requirements Review.

The SRR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into the Engineering and Manufacturing Development (EMD) phase, and that all system and performance requirements are defined/testable and consistent with cost, schedule, risk, technology readiness, and other system constraints. This review assesses the system performance requirements as captured in the System Performance Specification, and ensures that the system performance requirements are consistent with the system solution and available technologies. Of critical importance to this review is the understanding of program technical risk inherent in the System Performance Specification. Acceptable level of risk is key to a successful review. The contractor shall successfully complete SRR before entering the Preliminary Design Stage. See Appendix A for Entry and Exit Criteria and SRR Products.

3.2.1.2 Preliminary Design Stage.

During Preliminary Design, the contractor shall initiate subsystem design and establish any applicable Computer Software Configuration Items (CSCI) and Hardware Configuration Items (HWCI) to establish the allocated baseline. The contractor shall create subsystem-level definition and design-to baselines to guide component development. The contractor shall ensure that the design considerations include systems functional and non-functional requirements and Human System Interfaces.

The contractor shall ensure that functional design considerations integrate CS functional requirements, and that these requirements are included throughout the development process. The contractor shall decompose identified subsystem functions into lower-level functions and allocate functional and performance requirements to component-level functional and physical architectures. Preliminary subsystem requirements and verification definition and preliminary design-to baseline shall be evolved into a subsystem specification and design-to baseline. Preliminary component requirements and verification definition and build-to baselines shall be defined for the components and the subsystem being developed. Final subsystem definition shall include identification of recommended components and interfaces; resolution of subsystem-level risks; assessment of component risks; and design for quality factors to include producibility, verifiability, usability, CS, supportability, trainability and disposability for each subsystem. System design shall indicate all permanent infrastructure required for the development and operation of the SCETI ACE. At the end of the Preliminary Design Stage, the contractor shall enter and successfully complete a PDR prior to entering Detailed Design. The results of the evaluation shall be documented. (DI-IPSC-81432A, System/Subsystem Design Description)

3.2.1.2.1 Preliminary Design Review.

The PDR is a multi-disciplined product and process assessment to ensure that the system can proceed into detailed design, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. This review will assess the system preliminary design as captured in performance specifications for each configuration item in the system (allocated baseline), and ensures that each function in the FBL has been allocated to one or more system configuration items. PDR determines whether the hardware, human and software preliminary designs are complete, and the IPT is prepared to start detailed design and test procedure development. The contractor shall successfully complete PDR prior to entering the Detailed Design Stage. See Appendix A for Entry and Exit Criteria and PDR Products.

3.2.1.3 Detailed Design Stage.

During detailed design, the contractor shall complete subsystem design down to the lowest component level and create a component requirements and verification definition and build-to product baseline for each component. Design artifacts shall trace to allocated baseline (CSCI and HWCI) artifacts. Final component definition shall include identification of recommended parts and interfaces; resolution of component-level risks and for each component, down to the lowest sub-component, the design for quality factors to include supportability, verifiability, support for validation, usability, CS, trainability and disposability. At the end of Detailed Design Stage, the contractor shall enter and successfully complete a CDR prior to beginning system and subsystem development and integration. The contractor shall integrate security engineering processes into the design to achieve an integrated secure solution. The contractor shall document the hardware and software interfaces through which the SCETI ACE subsystems are controlled from the SCETI Test Control Center (TCC). The results of the component review shall be documented. (DI-IPSC-81432A, System/Subsystem Design Description); [DI-SESS-81248B, Interface Control Document (ICD)]

3.2.1.3.1 Critical Design Review.

The CDR is a multi-disciplined product and process assessment to ensure the system can proceed into system fabrication, demonstration, test, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. This review will assess the system final design as captured in product specifications for each configuration item in the system (product baseline), and ensures that each product in the product baseline has been captured in the detailed design documentation. Product specifications for hardware must enable the fabrication of configuration items, and shall include product definition data. Product specifications for software (e.g., software design documents) must enable coding of a CSCI. Configuration items may consist of hardware and software elements.

The subsystem detailed designs shall be evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem, and whether the traceability of final subsystem requirements to final system detail design is maintained. At this review the IPT shall also review the results of peer reviews on requirements and final detailed design documentation, and ensure that latest estimates of cost (development, production, and support) are consistent with the detailed design.

A successful review is predicated on the IPT’s determination that the subsystem requirements, subsystem detail design, results of peer reviews, and plans for testing form a satisfactory basis for proceeding into system fabrication, demonstration, and test.

See Appendix A for Entry and Exit Criteria and CDR Products.

3.2.2 Hardware Engineering.

The contractor shall develop the system hardware that satisfies the performance and CS requirements stated in the approved specifications. The contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value and additional detail to the products defined in the prior application of the process. Through each of the subsequent design stages, updates to hardware requirements and design information shall be documented in the System/Subsystem Specification and System/Subsystem Design Descriptions. (DI- IPSC-81431A, System/Subsystem Specification); (DI-IPSC-81432A, System/Subsystem Design Description)

3.2.3 Software Engineering.

In order to control the SCETI ACE subsystems, the contractor shall develop a plugin to the Government-furnished RTC/Aircraft Survivability Equipment Architecture for T&E of Hostile Fire, which serves as the primary control software within the SCETI TCC. The software plugin shall be developed in compliance with recognized industry standards and a documented process. The contractor shall provide evidence for the efficacy of their software design processes. The design shall incorporate features that promote ease of operation, CS, ease of software maintenance, ease of future updates and modifications, data void work around, and also any smart designs that can justify a reduction in the amount of documentation. The contractor shall employ well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system security engineering principles. The contractor shall define and document software interfaces in the Software Design Description (SDD). The contractor shall document software requirements in an IBM Rational DOORS compatible format. The contractor shall deliver any software and source code developed for the SCETI ACE with build instructions. The Government shall have unlimited rights to data pertaining to an item, component, or process and software product which has been or will be developed exclusively with Government funds under the execution of this development. (DI-IPSC-81435A, SDD); [DI-IPSC- 81441A, Software Product Specification (SPS)]

3.2.4 Hardware and Software Integration.

Contractor shall perform activities to integrate and assemble hardware and software to achieve a fully functional and CS-accredited SCETI ACE system, with support systems that perform and operate IAW the Performance Specification. Contractor shall verify the complete integration of the hardware and software of each hardware and software component, subsystem, the overall system through the utilization of formalized Test Procedures (TPs). The contractor shall capture Deficiency Reports (DRs) and analyze test results. The contractor shall report DRs at IPT meetings.

3.2.5 Cybersecurity.

All CS and CS-enabled products shall be securely configured IAW DOD-approved security configuration guidelines. As part of the system design and component selection process, CS shall be considered as a requirement for all systems used to enter, process, store, display, or transmit information. CS shall be achieved through the acquisition and appropriate implementation of evaluated or validated Government Off- The-Shelf or COTS computer systems, and CS-enabled Information Technology (IT) products. The Computer Hardware Enterprises Software and Solutions (CHESS) shall be used as the primary source for commercial IT equipment and software. CHESS will provide a Statement of Non-Availability authority if equipment and/or an Army Enterprise Software Agreements cannot meet user requirements. Government approval will be required prior to procuring any computer or IT related equipment outside of CHESS. The contractor shall assist the Government in completing all CS activities, including but not limited to artifact documentation, and provide design artifacts to support CS activities. Primary responsibility for CS planning and accreditation lies with the RTC S6.

3.2.6 Specialty Engineering.

3.2.6.1 Safety Engineering.

The contractor shall develop and implement tasks and activities to identify, evaluate, and eliminate or control hazards throughout the system’s life cycle. The contractor shall ensure the safety of the system's design, operation, transportation, maintenance, support, and disposal. The contractor shall conduct safety analyses; hazard identification and classification; and hazards tracking integral to the system design effort. A hazard risk index including hazard severity and hazard probability levels shall be developed for all hazards. The contractor shall coordinate with, and adhere to, any special safety requirements dictated by the range-specific safety needs of the acquiring test range(s). (DI-SAFT-80102C, Safety Assessment Report)

3.2.7 Product Definition Data (PDD).

The contractor shall develop, produce, and maintain PDD that accurately depicts the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, production, engineering, CS, and logistics support. (DI-SESS- 81000E, Product Drawings/Models and Associated Lists); (DI-SESS-81003E, Commercial Drawings/Models and Associated Lists); (DI-IPSC-81431A, System/Subsystem Specification)

3.2.8 Site Surveys.

The contractor shall perform two site surveys, one for the SDC and one for the FDC, at the SCETI site to determine site modifications necessary to field the system. The contractor shall identify all facility modifications necessary to support delivery, installation, maintenance and operation of the SDC and FDC systems. The contractor shall provide the gathered site information to the Government.

3.3 Test Program.

The contractor shall plan, coordinate, establish and implement a comprehensive T&E program to include all configurations of the system to verify compliance with the SCETI ACE System Performance Specification. System T&E refers to the T&E activities that use the developed hardware together with the software to verify that the system meets the functional, technical, and performance requirements as stated in the System Specification and this SOW. System T&E includes all efforts associated with the design and production of models, specimens, fixtures, and instrumentation in support of the T&E program. The contractor shall develop a test plan detailing the overarching T&E program, supported by the RTVM. The contractor shall use the RTVM to ensure that all decomposed and derived requirements in the system baseline are tested, in order to ensure system performance requirements are fully verified. The contractor shall develop step-by-step testing procedures to be performed on items undergoing developmental testing. 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 test planning and TPs shall be structured to integrate all developmental, operational, modeling, and simulation activities to concentrate upon generation of data needed to ensure that a decision on the systems capability to meet the objectives identified in the systems specification is made with a minimum amount of uncertainty. The contractor shall document Test Incident Reports (TIRs) during developmental testing. All TIRs shall be resolved prior to final system delivery and be documented in the final report.

The contractor shall conduct the test program incrementally prior to delivery.

Development shall include testing of subsystems prior to Site Acceptance Test (SAT).

(DI-NDTI-80566A, Test Plan); (DI-MGMT-82133, Requirements Traceability Verification Matrix)

3.3.1 Test Readiness Review (TRR).

The contractor shall complete a TRR no later than five work days prior to the start of formal subsystem or SAT events. For subsystem tests, only documentation relevant to the subsystem being tested is required to enter and complete TRR. Readiness to convene a TRR is predicated on the program IPT’s determination that preliminary testing, functional testing, and pre-qualification testing results form a satisfactory basis for proceeding with a TRR and initiation of formal system level testing. The TRR shall assess test objectives, test methods and procedures, scope of tests, and determines if required test resources have been properly identified and coordinated to support planned tests. The TRR shall also verify the traceability of planned tests to program requirements. See Appendix A for TRR Entry and Exit Criteria and TRR Products.

3.3.2 Contractor Test.

The contractor shall conduct engineering development tests to provide data to verify readiness of systems and/or subsystems to enter formal T&E with the Government.

Contractor tests shall provide data on performance; safety; achievement of critical technical parameters; refinement and ruggedization of hardware configurations; and determination of technical risk. The contractor shall ensure that systems and test equipment are operational and properly calibrated and tuned prior to start of test. The contractor shall analyze the results of each test and shall record the test and analysis results.

3.3.3 Subsystem Testing.

The contractor shall conduct formal subsystem-level tests to provide data to verify performance requirements of SCETI ACE subsystems below the system level prior to

SAT. Before each formal subsystem test, the contractor shall complete a TRR. The contractor shall ensure that systems and test equipment are operational and properly calibrated and tuned prior to start of test. The contractor shall analyze the results of each test and shall record the test and analysis results. To the greatest extent possible, subsystem test events for individual subsystem shall be conducted simultaneously. The contractor shall develop applicable test reports at the conclusion of testing to document results. (DI-NDTI-80603A, Test Procedure); (DI-NDTI-80809B, Test/Inspection Report)

3.3.4 Site Acceptance Testing.

Prior to delivery, the contractor shall develop step by step written test procedures and conduct and complete a formal SAT of the delivered capability. The contractor shall verify that installed configuration items operate to the specified performance requirements. A TRR shall be completed prior to site acceptance testing. The contractor shall document the results of the test. Site acceptance testing shall be witnessed by the Government. Approval by the designated Government witness is required for successful completion of site acceptance testing. (DI-NDTI-80603A, Test Procedure); (DI-NDTI-80809B, Test/Inspection Report)

3.4 Logistics.

The contractor shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. The contractor shall conduct trade studies;

evaluate design and support alternatives; and establish system supportability preliminary design configurations consistent with system readiness, availability, and LCC goals.

3.4.1 Supportability Analysis and Logistics Management Information.

The contractor shall conduct repair level analyses; refine hardware and software maintenance and support concepts; and identify support resource requirements including required spares and support equipment. The contractor shall develop a listing of which items should be repaired and which should be discarded, and the level of maintenance at which the repair should be performed with the associated cost. The contractor shall document the following in a database:

a. All input data and their corresponding value and source of the data.

b. Operational scenario modeled, assumptions made, constraints assumed, and non-economic factors imposed.

c. Maintenance alternatives considered.

d. Analytical method and models used to perform the economic evaluations.

e. Discussion of the sensitivity evaluation performed and results obtained.

(DI-SESS-81758A, Logistics Product Data); (DI-SESS-81759A, Logistics Product Data Summaries)

3.4.2 Technical Publications.

3.4.2.1 Operator and Maintenance Manuals.

The contractor shall describe each operation and maintenance task in detail and in logical, systematic steps for the work to be accomplished. The operations and maintenance instructions shall accurately provide the technician with all the information needed to keep the equipment operational. It shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. All tools, test equipment, and consumable items required to accomplish any maintenance or installation shall be identified just prior to, and as part of the task. All publications shall reflect the configuration of fielded hardware. (MIL-STD-40051-2C, Operation and Maintenance Manual)

3.4.2.2 COTS Manuals.

The contractor shall deliver COTS technical publications for all commercial equipment delivered with the system. The COTS documentation shall be sufficient to support the operation and maintenance of all COTS components per MIL-PRF-32216a. The contractor shall review the COTS documentation and identify deficiencies or deviations in the manuals. If the COTS document is not sufficient to support the operation and maintenance, and the contractor is unable to retrieve the required data from the vendor, the contractor shall develop supplementary data for inclusion in the main text of the Technical Manual ensuring that all required data for the COTS item is presented. (DI- TMSS-80527C, COTS Manuals and Associated Supplemental Data)

3.4.3 Item Unique Identification (IUID).

The contractor shall coordinate among the SCETI IPT members to determine items requiring UID including embedded subassemblies, components and parts, and identify the UID to be used for each item. The contractor shall provide a unique item identification, or a DOD recognized UID equivalent, for all identified items delivered.

IUID marking design for each item shall be both machine readable and human readable IAW MIL-STD-130, paragraph 5.2. [DI-MGMT-81858, Unique Identification (IUID) Marking and Verification Report]

3.4.4 Training Products.

3.4.4.1 New Equipment Training.

The contractor shall develop a course providing training based on the operations and maintenance manual for operators and maintainers in the concepts, skills, and aptitude to efficiently operate and maintain the system. This course shall consist of instruction in operation; 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.

3.4.5 Government Furnished Property (GFP).

The contractor shall be responsible for the accountability, control, and storage of all GFP while at the contractor’s facility, and while performing installation and integration of the SCETI ACE at RTC.

3.4.6 Quality Assurance Surveillance Plan (QASP)

Reference MISTE Base SOW Section 3.5.15 and MISTE Quality Assurance Plan (QAP) dated 14 December 2018.