EMD-SOW.pdf

FOR OFFICIAL USE ONLY

ROUTE CLEARANCE & INTERROGATION SYSTEMS (RCIS) TYPE I

Engineering and Manufacturing Development (EMD) Phase Statement of Work (SOW)

Document Date: 12 May 2015

Version 0.1 (Draft)

Route Clearance & Interrogation Systems (RCIS) Statement of Work

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Contents

C.1 GENERAL

C.2 PROGRAM STRUCTURE AND MANAGEMENT

C.3 MEETINGS/AUDITS/ASSESSMENTS/REVIEWS

C.4 SYSTEMS ENGINEERING

C.5 SOFTWARE ENGINEERING

C.6 CYBERSECURITY

C.7 CONFIGURATION MANAGEMENT (CM)

C.8 DATA MANAGEMENT

C.9 RISK MANAGEMENT

C.10 RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM

C.11 ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH (ESOH)

C.12 HUMAN SYSTEMS INTEGRATION (HSI)

C.13 SUPPORTABILITY / INTEGRATED LOGISTICS SUPPORT (ILS)

C.14 GOVERNMENT FURNISHED EQUIPMENT/GOVERNMENT FURNISHED

INFORMATION (GFE/GFI)

C.15 SYSTEM FABRICATION, INTEGRATION AND HARDWARE DELIVERABLES

C.16 EMD PHASE TEST AND EVALUATION…………………………………………………

C.17 MANUFACTURING AND PRODUCTION READINESS

C.18 QUALITY / PRODUCT ASSURANCE

C.19 SECURITY

C.1 GENERAL

C.1.1 Introduction This Statement of Work (SOW) encompasses the Engineering and Manufacturing Development (EMD) phase of the Route Clearance & Interrogation System (RCIS) Type I program.

C.1.1.1 The RCIS Type I will enable a Soldier to excavate, interrogate, and classify deep buried explosive hazards, Improvised Explosive Devices (IEDs), and caches in a wide range of road surfaces and soil conditions, as well as clear routes by moving explosive hazards, debris and rubble, and filling potholes. The RCIS Type I will be operable either in a manned mode by a Soldier in the RCIS (host) vehicle or in an unmanned mode by a Soldier in a separate control vehicle.

C.1.1.2 The RCIS Type I will use a High Mobility Engineer Excavator (HMEE) including its Crew Protective Kit (CPK) as the host vehicle. To enable a Soldier to perform interrogation tasks, the RCIS Type I provides various attachments including a front loader, backhoe bucket, clam shell bucket, rake and spork, air spade, classification camera, light and measurement device.

C.1.1.3 The RCIS Type I includes a Semi-Autonomous Control (SAC) system that provides the capability to control the RCIS Type I vehicle and attachments in the unmanned mode. The SAC system also provides a reduced set of capabilities in the manned mode. The electrical, mechanical, and hydraulic systems of the HMEE host vehicle require modification by the HMEE vehicle Original Equipment Manufacturer (OEM) to enable semi-autonomous control.

C.1.2 Scope

C.1.2.1 C.1.2.1 The Contractor shall design and develop a SAC system IAW the Performance Specification For RCIS Type I SAC System (Attachment 0001), hereafter referred to as the RCIS Performance Specification.The Contractor shall integrate SAC system components onto HMEE host vehicles in accordance with the Interface Control Document for the Modified HMEE and SAC System (Attachment 0002). The Contractor shall integrate SAC system components onto control vehicles, specifically the Buffalo Mine Protected Clearance Vehicle (MPCV), IAW the Interface Control Document for the Buffalo MPCV and SAC system, (Attachment 0003).

Figure 1: RCIS Type I

The Government will provide the following items as Government Furnished Equipment (GFE) for EMD: base HMEE vehicles with modifications to the platform to accept the SAC kits; boom arm interrogation attachments, technical and installation data to support future development of the modifications and attachments, and Buffalo MPCV control vehicles.

Figure 2: RCIS Semi-Autonomous Control (SAC) System

C.1.2.2 The Contractor shall perform Contractor testing, deliver the SAC systems integrated on Government Furnished Equipment (GFE) vehicles, and support Government testing as specified in C.16. The Contractor shall perform and complete all activities and deliveries to comply with the requirements in this SOW.

C.1.2.3 For information regarding RCIS Type I missions refer to the Operational Mode Summary / Mission Profile (OMS/MP) (Attachment 0005).

C.2 PROGRAM STRUCTURE AND MANAGEMENT

C.2.1 The Contractor shall define and ensure its key roles (including Project Management (PM) and Integrated Product Team (IPT) leads) are staffed with personnel of commensurate education, training, work experience, and technical training necessary to effectively and efficiently perform required tasks. The Contractor shall present its organizational key roles at the Start of Work Meeting (SOWM) and discuss its plan for communicating and transitioning personnel changes. When the Contractor intends to change the personnel working in key roles, the Contractor shall provide ten business days notice to Contracting Officer Representative (COR) and receive confirmation of the changes prior to the personnel transition. For the purposes of this SOW business days are Monday through Friday. The Government has ten business days to acknowledge receipt.

C.2.2 Integrated Product Teams (IPTs) For purposes of this contract, any joint deliberative or task-focused body, regardless of its formal or informal title, (e.g., "Working Group," "Integrated Design Team", etc.) will be considered an Integrated Product (or Process) Team, or "IPT". IPTs will be established to serve as a tool to manage performance under this SOW and as key method of communication for this contract.

C.2.3 Integrated Master Schedule (IMS) The Contractor shall develop and maintain the project’s IMS by logically networking detailed program activities. (IAW CDRL A001 IMS) using the Government provided RCIS Program Plan (Attachment 0015 – RCIS Program Plan) as a guide.

C.2.4 Contract Work Breakdown Structure (CWBS) The Contractor shall utilize the CWBS and related dictionary found in Attachment 0006 as a departure point for preparation and submittals of the CWBS. The CWBS shall be developed using the latest version of MIL-STD-881C (WBS) as guidance and continue the CWBS numbering scheme. (IAW CDRL A002 CWBS).

C.2.5 Contract Funds Status Report The Contractor shall prepare, update and submit the Contract Funds Status Report (CFSR). (IAW CDRL A003 Contract Funds Status Report (CFSR)).

C.2.6 Internet-Based Collaboration

C.2.6.1 The Contractor shall notify the COR via email immediately upon submission of new or updated documents being posted to a collaboration environment. The notification email shall include a hyperlink to the location of the posted content. Correspondence to the COR shall not be submitted via an internet-based collaboration tool without prior authorization.

C.2.6.2 The Contractor shall use Versatile Information Systems Integrated On-Line Nationwide (VISION) , VISION Digital Library System (VDLS) to access data from Government testing. Details on specific tools, requirements for access, and approach for use will be discussed at the SOWM (reference C.16.5.1).

C.2.6.3 The Government will sponsor access to Army Knowledge Online (AKO), Product Manager (PdM) Applique and Large Unmanned Ground Systems (ALUGS) Portal, Defense Connect Online (DCO), and VDLS.. The Government can only sponsor accounts for U.S. Citizens. The Contractor shall provide all names, contact information, level of access (upload or download), and training required for personnel requiring access to these tools no later than the SOWM for all internet-based systems except VDLS. The list of contractor personnel requiring VDLS access shall be provided to the Government no later than 50 days prior to the Test Readiness Review (TRR).

C.2.6.4 In order to access the above referenced internet-based systems (C.2.6.3), the Contractor shall have or obtain an AKO account, External Certification Authority (ECA) Certificates and Department of Defense (DoD) Common Access Cards (CAC) for all personnel required to access the above referenced internet-based systems in C.2.6.2 though C.2.6.4. The Contractor shall designate an Information Assurance (IA) Officer to work with PdM ALUGS and the Government IA Manager in order to obtain and implement usage of the ECA and CAC program in compliance with DoD Directive

8190.3 Smart Card Technology, and DoD Instruction 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling.

C.2.7 Earned Value Management System (EVMS) In the performance of this contract, the Contractor shall use an EVMS that complies with Table 5 (Earned Value Management (EVM) Implementation Policy) in DoDI 5000.02 (Operation of the Defense Acquisition System), the American National Standards Institute/Electronic Industries Alliance Standard 748 (ANSI/EIA-748), DI-MGMT-8161, DFARS Clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004, and the contractor’s own documented EVMS Description. The contractor shall use an EVMS that has been formally reviewed and determined by the Defense Contract Management Agency (DCMA) to be in compliance with the EVMS guidelines in ANSI and EIA-748.

C.2.8 Over-Target Baseline (OTB) or Over-Target Schedule (OTS) In exceptional circumstances indicated by contract performance (per the Contractor's EVMS Description), the Contractor shall submit a request to the PCO for approval to initiate an OTB or OTS. The request shall include a top-level projection of cost or schedule growth, a recommendation of whether or not performance variances should be retained on record, and a schedule for implementing a new baseline. The Contractor shall not implement the OTB or OTS restructuring prior to receiving written approval from the PCO.

C.2.9 Application to Subcontractors The Contractor shall flow-down EVM requirements to subcontractors meeting the applicable thresholds (per DFARS clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004). The performance information reported by the subcontractors shall be incorporated and integrated into the contractor's management system. The Contractor shall conduct Integrated Baseline Reviews (IBRs) on any subcontractors with contracts requiring EVM. Although the Government may attend these IBRs, the actual event shall be the Contractor's responsibility.

C.3 MEETINGS/AUDITS/ASSESSMENTS/REVIEWS

C.3.1 Participation/Administration The Contractor shall participate in the meetings, audits, assessments, and reviews required in this SOW. When mutually agreeable, the meeting host will schedule face-to-face meetings for multiple topics to minimize personnel resources and travel expenses.

The Contractor shall host, unless otherwise specified in the paragraphs below, all meetings, audits, assessments, and reviews. The Contractor's hosting duties and responsibilities shall include providing facility, sending invitations, media resources, security, minutes, hard copy materials related to the preparation and execution of the meetings, audits, assessments, and reviews. The Contractor shall allow physical, dial-in access (telephone), and Defense Connect Online access (DCO) to the Government for all meetings, audits, assessments, and reviews.

C.3.1.1 Agenda and Read-Ahead Packages The Contractor shall submit an agenda and read-ahead package, IAW CDRL A071 Conference Agenda, in Contractor format three business days prior to all meetings, audits, assessments, and reviews in Section C.3.

C.3.1.2 Minutes The Contractor shall record and submit minutes IAW CDRL A069 “Meeting Minutes” for all meetings, audits, assessments, and reviews in Section C.3 and otherwise called out in this contract. The Contractor shall identify its recorder at the beginning of each event.

Minutes shall be submitted to the COR for approval. Any discrepancies or inconsistencies identified by shall be revised accordingly by the Contractor in the Minutes and resubmitting to the COR for approval.

C.3.1.3 Reserved

C.3.2 Start of Work Meeting (SOWM) The Contractor shall participate in a SOWM at the Government Product Manager site within 20 business days after contract award, as mutually agreed to by the Contractor and Government. This meeting will introduce and align the Government and Contractor teams. The SOWM will consist of a SOW review, a System Requirements Review (SRR), and an IMS Review. The agenda topics for the SOWM are identified in the SOWM Agenda (Attachment 0007). The SRR shall follow the guidance of Defense Acquisition Guidebook (DAG) Section 4.2.10. The SRR will be a line-by-line review of the RCIS Performance Specification (Attachment 0001). For planning purposes, the participants should anticipate this meeting to be a consecutive two-day event.

C.3.3 Program Management Reviews (PMR) The Contractor shall conduct quarterly PMRs, beginning with the first quarter after contract award. The PMRs shall include Contractor senior-level program management personnel. The Contractor shall present cost, schedule, performance, and risk status at each PMR and be prepared for detailed discussion with the Government. The Contractor shall present issues in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact. For planning purposes, the participants should anticipate these meetings to be a one-day event.

C.3.4 Technical Reviews

C.3.4.1 The Contractor shall conduct program technical reviews in accordance with the Government IMS. The Technical Review Criteria (Attachment 0009) provides high-level entrance and exit criteria for each technical review. The Contractor shall finalize entrance and exit criteria jointly with the Government at least 20 business days prior to the associated technical review. The Contractor shall remedy all unsatisfactory entrance criteria prior to entry into each technical review.

C.3.4.2 The Contractor shall describe in its System Engineering Management Plan (SEMP) (Refer to Section C.4.1) the internal processes that will be used to prepare for and conduct the technical reviews. The Contractor shall document the proceedings of all technical reviews in Meeting Minutes and deliver IAW with CDRL Data Item No.

A070. The Contractor shall document all action items that result from the technical reviews in the Meeting Minutes.

C.3.4.3 The Procurement Contracting Officer (PCO) will have the sole authority to certify the successful completion of the technical reviews and provide written authorization to the Contractor to proceed based on successful completion of the entrance and exit criteria and closure of action items.

C.3.4.4 Preliminary Design Review (PDR) The Contractor shall conduct a Preliminary Design Review at the Contractor site. The PDR shall follow the guidance of DAG Section 4.2.12. The Contractor shall establish the RCIS Type I's allocated baseline as defined in DAG Section 4.2.12. The Contractor shall demonstrate the RCIS Type Isatisfies the requirements of the Capability Production Document (CPD) within the currently allocated budget and schedule. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.5 Critical Design Review (CDR) The Contractor shall conduct a Critical Design Review at or near the Contractor site.

The CDR shall follow the guidance of DAG Section 4.2.13. The Contractor shall establish the initial product baseline and demonstrate the RCIS Type Isatisfies the requirements of the CPD within the currently allocated budget and schedule. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.6 Test Readiness Reviews (TRR)

C.3.4.6.1 Contractor Conducted Pre-Test Readiness Review (pre-TRR) The Contractor shall conduct a Pre-TRR to present to the Government the readiness of the vehicles to enter into Government system level testing. The Pre-TRR shall be held at the Contractor build site, at least five business days prior to the Government TRR (C.3.4.5.2). The Pre-TRR shall address the content detailed in the Technical Review Criteria (Attachment 9) and the Pre-TRR Checklist (Attachment 0010). For planning purposes, participants should anticipate this meeting to be a two-day event.

C.3.4.6.2 Government Conducted Test Readiness Reviews (TRR)

The Contractor shall attend the Government TRR, conducted at Aberdeen Proving Ground (APG). The Government TRR is anticipated to be held no more than five business days prior to vehicle delivery and will assess both the Contractor's and the Government's test readiness. The Contractor shall provide all of the information prepared for the Pre-TRR. For planning purposes, participants should anticipate this meeting to be a one-day event.

C.3.4.7 System Verification Review (SVR) and Functional Configuration Audit (FCA) The Contractor shall conduct a SVR and a Functional Configuration Audit (SVR/FCA) at the Contractor site. The SVR/FCA shall follow the guidance of DAG Section 4.2.14. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.8 Production Readiness Review (PRR) The Contractor shall conduct a Production Readiness Review (PRR) at the Contractor site. The PRR shall follow the guidance of DAG Section 4.2.15. For planning purposes, participants should anticipate this meeting to be a one-day event.

C.3.5 Integrated Product Team (IPT)/Working Group (WG) Meetings The Contractor shall provide Meeting Minutes IAW with CDRL Data Item No. A070 “Meeting Minutes” for all IPT and WG Meetings. The Contractor shall provide an agenda, IAW CDRL A071 Conference Agenda, one business day prior to scheduled meetings, provided to the COR via email.

C.3.5.1 Program Management (PM) IPT Meetings The Contractor shall conduct monthly PM IPT Meetings intended to be at the Assistant Product Manager (APM) level and below. If mutually agreed to by the parties the Contractor may conduct additional PM IPT meetings. The PM l IPT Meetings shall commence the month following the SOWM. PM IPT Meetings shall include Contractor program management and working level IPT personnel; the Contractor shall be prepared for detailed discussion on cost, schedule, performance, and risk status. The Contractor shall present technical issues in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact.

C.3.5.2 Systems Engineering IPT Meetings The Contractor shall conduct weekly System Engineering (SE) IPT meetings to discuss the technical planning and execution of RCIS Type I system analysis, design, development, and integration activities.

C.3.5.3 Logistics Guidance Conference The Contractor shall conduct The Logistics Guidance Conference to address Logistics Management data and products. The conference shall be in conjunction with the SOWM.

C.3.5.4 Software Working Group The Contractor shall conduct weekly Software Working Group meetings to discuss the design and development of the RCIS Type I software.

C.3.5.5 Human Systems Integration (HSI) IPT The Contractor shall conduct monthly HSI meetings (IAW C.12). IPT meetings will be held jointly with the System Safety and Environmental Working Group (IAW C.11.6) (the group is a combination of contractor and government personnel) with Government participation and oversight, providing HSI integration system status, HSI event findings, issues database updates, recommendations and design data. The Contractor shall prepare for detailed discussion of these topics. The meetings shall include Contractor HSI personnel and working level IPT personnel. The Contractor shall address HSI domains of safety, health hazards, human factors engineering, soldier survivability, manpower, personnel and training. The Contractor shall address HSI database issues in terms of risk assessment, mitigation, cost, and identification of organization and personnel responsible for a resource schedule to resolve issues.

C.3.5.6 Corrosion Prevention Advisory Team (CPAT) The Contractor shall attend CPAT meetings, complete assigned action items, and inform the CPAT of new corrosion issues and their impact on the corrosion prevention and control of the SAC system. CPAT meetings will be teleconferences held on a quarterly basis (no travel required).

C.3.5.7 Test and Evaluation Working-level Integrated Product Team (T&E WIPT) The Contractor shall provide an engineering representative to the Government-led T&E WIPT to plan and support Government and contractor test activities.The primary purpose of the RCIS Type I T&E WIPT is to optimize the use of T&E expertise, instrumentation, facilities, Modeling and Simulation (M&S), and the collected resources of the represented agencies and organizations to integrate the collective T&E efforts.

The T&E WIPT will collectively plan, budget, resource, execute, and continuously evaluate the RCIS Type I T&E program as a principal risk management agent for the Product Manager. The primary product of the T&E WIPT is the program test strategy, which is captured in the RCIS Type I Test and Evaluation Master Plan (TEMP), Attachment 0017 TEMP. The T&E WIPT shall meet every two weeks after contract award and be the instrument that will tailor the T&E tools and strategy to maximize effectiveness and efficiency of the test procedures, while determining which specific tests are required to support the RCIS Type Iassessment for approval and systems safety certification.

C.3.5.8 Program Protection Working Group (PPWG) The Contractor shall host three PPWG meetings at PDR, CDR, and at the end of the contract. A Government systems engineer will chair each PPWG and the co-chair shall be either the Contractor security manager or a Contractor engineer. The Contractor shall ensure any updated assumptions, rationale, and results related to criticality analysis, vulnerability assessments and risk evaluations, as well as supply chain risk information and mitigation are made available for Government review at PPWGs. For planning purposes, participants should anticipate this meeting to be a one-day event.

C.4 SYSTEMS ENGINEERING

C.4.1 Systems Engineering Management Plan (SEMP) The Contractor shall prepare and execute a SEMP detailing the systems engineering process for developing the RCIS Type I. The Contractor shall prepare and deliver the SEMP in accordance with CDRL A004 Systems Engineering Management Plan (SEMP).

C.4.2 System/Subsystem/Component Specification

The Contractor shall develop and deliver system, subsystem, and component specifications (IAW CDRL A005 System/Subsystem/Component Specification) for the RCIS Type I system. The System Specification shall be derived from and trace to the RCIS Performance Specification (Attachment 0001). The Subsystem Specifications shall be derived from and traced to the RCIS Type I specification. The Component Specifications shall be derived from and trace to their subsystem specifications. The System, Subsystem and Component Specifications shall represent performance requirements of the RCIS Type I at the end of the EMD phase.

C.4.3 Requirements Compliance Matrix (RCM) The Contractor shall develop, deliver and update a Requirements Compliance Matrix (RCM) (IAW CDRL A006 Requirements Compliance Matrix (RCM)) that assesses compliance towards achieving all RCIS Performance Specification (Attachment 0001) requirements. The RCM shall trace to the RCIS Performance Specification (Attachment 0001) and include information supporting each requirement’s assessment. The RCM shall be delivered IAW the rcm Format spreadsheet embedded in CDRL A006 and include supporting data that describes the analysis that has been done to support the assessment of compliance. The RCM shall describe and include all related data which includes sketches, preliminary drawings, schematics, functional diagrams, test results necessary to support compliance assessment. The Contractor shall present the RCM and supporting information at formal technical reviews IAW Section C.3.4.

C.4.4 System/Subsystem Design Description (SSDD) The Contractor shall develop and deliver a System/Subsystem Design Description (SSDD) (IAW CDRL A007 System/Subsystem Design Description (SSDD)) for the RCIS Type I system.

C.4.5 Interface Control Documents (ICDs) The Contractor shall prepare, deliver and update Interface Control Documents (ICDs) (IAW CDRL A008 Interface Control Documents (ICDs)) that identify the interface requirements between: Hardware Configuration Items (HWCI) (HWCI to HWCI);

Software Configuration Items (SCI) and hardware configuration items (SCI to HWCI);

and HWCI and SCI to systems external to the SAC system.

C.4.6 Open Systems Architecture The Contractor shall define and follow an open systems architecture for using modular designs, standards based interfaces, and widely supported standards. The Contractor shall document its open systems approach in its SEMP (C.4.1). The Contractor shall demonstrate compliance with its open systems architecture during formal technical reviews per Section C.3.4.

C.4.7 Unmanned Ground Vehicle (UGV) Interoperability Profile (IOP) The Contractor shall utilize the Unmanned Ground Vehicle (UGV) Interoperability Profile (IOP) (Attachment 0014) in the design and implementation of the SAC system for RCIS Type I. In cases where the UGV IOP does not support the Contractor's implementation, the contractor shall provide a non-proprietary interface description with electrical, signal, mechanical, connector, and digital message protocol information in contractor format (IAW CDRL A009 IOP Contractor Standards) to describe the implementation for consideration in adopting the solution in the next version of the UGV IOP. The Contractor shall present its IOP approach and supporting information at formal technical reviews per Section C.3.4.

C.4.8 Application for Equipment Frequency Allocation (DD 1494) The Contractor shall deliver a completed DD 1494 form, Application for Equipment Frequency Allocation (IAW CDRL A011 Frequency Allocation Data), no later than ten business days prior to PDR. The Contractor shall conduct the necessary coordination with the Government to complete the DD 1494 data entries prior to submittal.

C.4.9 Co-site Mitigation and Antenna Optimization The Contractor shall coordinate with the Government for placement of all antennas on the HMEE host vehicle and control vehicles, and provide necessary technical information to support Government analysis for final antenna placement. The Contractor shall provide this information to the Government at PDR.

C.4.10 Proposed Vehicle Modifications The Contractor shall minimize vehicle modifications necessary to integrate the SAC system and its components onto the HMEE host vehicle and control vehicles. The Contractor shall provide to the Government at PDR sufficient information to develop engineering change proposal(s) (ECPs) that detail all proposed vehicle modifications.

The Contractor shall not implement any vehicle modifications without prior PCO written approval. (IAW CDRL A012 Proposed Vehicle Modifications)

C.4.11 Routing Diagrams-Cabling, Wiring Harnesses, and Plumbing The Contractor shall deliver detailed wiring diagrams, schematics, and physical routing diagrams (harnesses, cables, and plumbing) of all designed SAC system integration cables and lines for both the HMEE host vehicle and control vehicles. This information shall be available to the Government and discussed at IPT meetings as well as formal technical reviews IAW Section C.2.1 and C.3.4. (IAW CDRL A013 Routing Diagrams- Cabling, Wiring Harnesses, and Plumbing)

C.4.12 MIL Grade Connector Waivers The Contractor shall submit waiver requests for non-MIL grade connectors using the format defined in MIL Grade Connector Waiver Form (Attachment 0012), and shall include technical justification and qualification standards for the use of the alternate connector. Non-MIL grade connector waivers shall be submitted to the COR No later than 20 business days prior to PDR. Waivers will be dispositioned (approved or rejected) by the Government at PDR.

C.4.13 Corrosion Prevention and Control In the design and fabrication of the SAC system and its components, the Contractor shall use compatible materials, inherently corrosion resistant, or treated to provide protection against the various forms of corrosion and deterioration to which they are susceptible.

C.5 SOFTWARE ENGINEERING

C.5.1 Reserved. Reserved

C.5.2 Software Development Plan (SDP) The Contractor shall provide a Software Development Plan IAW DI-IPSC-81427A (IAW CDRL A0014 Software Development Plan (SDP)). The SDP shall be consistent with the SEMP (C.4.1) and shall describe the Contractor’s software lifecycle process, including the processes for design of RCIS Type I software and algorithms, integration of hardware and software components, software modifications, software quality process (including tools, techniques, coding standards, processes, and measures), software measurement, software data management, and reliability and maintainability attributes throughout the entire lifecycle. The SDP shall also document how the Contractor plans to address information assurance/security, software safety, maintainability, and Intellectual Property Rights (IPR). The Contractor may use Institute of Electrical and Electronics Engineers (IEEE)/Electronic Industries Association (EIA) 12207.0, IEEE/EIA 12207.1, and IEEE/EIA 12207.2 as guidance.

C.5.3 Software Requirements Specification (SRS) The Contractor shall provide a Software Requirements Specification IAW DI-IPSC- 81433A (IAW CDRL A0015 Software Requirements Specification (SRS)). The SRS shall specify all software requirements and the methods to verify compliance for each requirement. The SRS shall include a matrix that shows requirements traceability between the SRS and the RCIS Type I specification. The Software Requirements Specification (SRS) shall specify the requirements for all Computer Software Configuration Item (CSCIs) and the methods to be used to ensure each requirements has been met. Requirements pertaining to the CSCIs external interfaces may be presented in the SRS or in one or more Interface Requirements Specifications (IRSs) (DI-IPSC-81434) referenced from the SRS.

C.5.4 Interface Requirements Specification (IRS) The Contractor shall provide an Interface Requirement Specification IAW DI-IPSC- 81434A, (IAW CDRL A016 Interface Requirements Specification (IRS)). The IRS shall specify the interface requirements for the RCIS Type I components.

C.5.5 Interface Design Description (IDD) The Contractor shall provide an Interface Design Document IAW DI-IPSC-81436A (IAW CDRL A017 Interface Design Document (IDD)). The IDD shall describe the interface characteristics selected to meet the requirements of the IRS.

C.5.6 Software Design Description (SDD) The Contractor shall deliver an Software Design Description IAW DI-IPSC-81435A (IAW CDRL A018 Software Design Description (SDD)). The SDD shall describe design decisions, architectural design, and the detailed design needed to implement the software. There shall be separate SDDs developed for each CSCI.

C.5.7 Contractor Support for Government Stress Testing The Contractor shall provide online software engineering technical support (in the form of telephone and email communication) during Government Software Stress Testing of the SAC system software source code and executables delivered per Section C.5.12. The Contractor shall review the results of the Software Stress Testing and corrective actions during the Software Working Group meeting(s) (Section C.3.5.4). The Contractor shall implement corrective actions and resolve to closure for software defects as identified by the Software Working Group.

C.5.8 Software Test Plan (STP) The Contractor shall provide a Software Test Plan IAW DI-IPSC-81438A (IAW CDRL A019 Software Test Plan (STP)). The STP shall address the software test methods, test criteria, test environments, test types, and test schedule.

C.5.9 Software Test Description (STD) The Contractor shall provide a Software Test Description IAW DI-IPSC-81439A (IAW CDRL A020 Software Test Description (STD)). The STD shall describe the test preparations, test cases, and test procedures to perform qualification testing of the RCIS Type I.

C.5.10 Software Test Report (STR) The Contractor shall provide Software Test Reports IAW DI-IPSC-81440A (IAW CDRL A021 Software Test Report (STR)). The STRs shall document all software testing conducted. For each CSCI and the RCIS Type I, the STRs shall document test objectives, methods, types, criteria, environment, dates, data, results, conclusions, description and analysis of failures, and identify COR-designated personnel (Government or Contractor) who witnessed each test.

C.5.11 Software Version Description (SVD) The Contractor shall provide a Software Version Description IAW DI-IPSC-81442A (IAW CDRL A022 Software Version Description (SVD)). The SVD shall be used to release, track, and control software versions.

C.5.12 Source Code and Executables The Contractor shall deliver a copy of all software images, executables, parameter files, configuration files, and source code utilized on the SAC system and developed by the Contractor or any subcontractors under this effort and funded by the Government. The information used to create this CDRL shall be delivered upon request to the Government and discussed at IPT meetings as well as formal technical reviews per Section C.3.4.

(IAW CDRL A023 Source Code and Executables)

C.5.13 Software License Package The Contractor shall develop a Software License Package, IAW CDRL A024 Software License Package, to identify and deliver all commercial software licenses for all software utilized on the delivered SAC systems. The information used to create this CDRL shall be delivered upon request to the Government and discussed at IPT meetings as well as formal technical reviews per Section C.3.4. ()

C.5.14 Software Quality Assurance Plan (SQAP) The Contractor shall develop, deliver and maintain a SQAP in accordance with IEEE STD 730-2014. The SQAP shall describe procedures, techniques and control methods to ensure that a product meets the requirements specified in the SRS.

C.5.15 Software Configuration Management (CM) – The Contractor shall establish and maintain a software CM system in accordance with its SDP to establish and maintain a software baseline. The contractor shall implement a change control process for the approval or rejection by the COR of all change requests that are sent against any baseline. The contractor shall maintain a software identification table for each piece of software and its corresponding hardware component. This list shall consist of the hardware serial number and its correlating software version number to ensure that correct software versions resides on the production hardware.

C.6 CYBERSECURITY

C.6.1 Cybersecurity Strategy The Contractor shall establish appropriate administrative, technical, and physical safeguards to protect all Government data, to ensure the confidentiality, integrity, and availability of Government data in accordance with Department of Defense Instruction (DoDI) 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems.

C.6.2 Policies The Contractor shall comply with Cybersecurity requirements in accordance with DoDI

8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), DoD

8500.01 Cybersecurity, NIST SP 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Lifecycle Approach, NIST SP 800-53 Recommended Security Controls for Federal Information Systems and Organizations, CJCSM 6510.01IA Chairman of the Joint Chiefs of Staff Manual, 6212.01E Interoperability and Supportability of Information Technology and National Security Systems, National Industrial Security Program Operating Manual (NISPOM), DoDI 8551.1 Ports, Protocols and Services Management (PPSM), DoD 5220.22-M, Department of Defense Federal Information Security Management Act (FISMA) and AR 25-2, Information Assurance. Cybersecurity policies shall be enforced to secure access, data, information systems (IS), and data repositories; increase trust and trusted relationships; employ technical and operational security mechanisms; deny all unauthorized accesses; and permit necessary exceptions to support Army, DOD, and Joint Interagency and Multinational (JIM) tactical and sustaining-base operations.

C.6.3 Training In accordance with cybersecurity directives, the PM requires cybersecurity support. To achieve Cybersecurity accreditation, the Contractor cybersecurity support must comply with training requirements and certifications mandated by DoDD 8570.01-M Information Assurance Workforce Improvement Program.

C.6.4 Security Plan and Assessment Testing

The Contractor shall develop a security plan in accordance with DoDI 8510.01 using the template from the Risk Management Framework (RMF) Knowledge service (IAW CDRL A025 Security Authorization Package). The Contractor shall support security assessment of the RCIS Type I by providing the cybersecurity -related analyses, tests, evaluations, and assessments. The Contractor shall also support the PM in the development of required accreditation documentation and its approval process. The Contractor shall provide 15 business days advanced notice of security assessment testing and the government will have the option to observe security assessment testing. A Security Authorization Package shall be provided using the template found on the Risk Management Framework (RMF) Knowledge service (https://rmfks.osd.mil/rmf/). The Security Authorization Package shall have the following worksheets filled out:

• Security Plan (SP): The Contractor shall develop a security plan in accordance with DoDI 8510.01 using the template from the Risk Management Framework (RMF) Knowledge service and include any external documentation required to document compliance with security controls. Name of document and section of document that demonstrated compliance with security controls shall be listed in the comments column.

• Security Assessment Report (SAR): Security Controls shall be assessed and results documented in he SAR worksheet.

• Plan of Actions and Milestones (POA&M): System vulnerabilities shall be documented and a plan developed to mitigate these vulnerabilities on the System POA&M worksheet.

In addition all documentation required to demonstrate compliance with security controls shall be produced and provided.

C.6.5 Use of BBPs and STIGs The Contractor shall use Best Business Practices (BBPs) and Security Technical Implementation Guides (STIGs) to define specific standards, measures, practices, or procedures necessary to meet Cybersecurity requirements in support of Army policy requirements.

C.6.6 Product Development and Updating During product development for the Government, the Contractor shall ensure that all cybersecurity mitigation strategies have been applied to the development environment prior to any Government data being loaded onto any assets or software for testing or delivery. Cybersecurity mitigation strategies include security updates, service packs, and changes to operating procedures as physical and cyber vulnerabilities are detected.

Operating systems, routers, servers, development platforms and the application delivered to the Government shall comply with all known applicable Department of Defense Computer Emergency Response Team (DoD-CERT) Alerts, Bulletins, and Technical Advisory Notices published during the past 36 months.

C.6.7 Product NIST, NIAP, and FIPS Usage The Contractor shall ensure that all cybersecurity and cybersecurity enabled products are National Security Telecommunications and Information Systems Security Policy Number 11 (NSTISSP-11) compliant and are validated by accredited labs under National Security Agency (NSA), the National Information Assurance Partnership (NIAP) Common Criteria Evaluation and Validation Scheme or National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) Cryptographic Module Validation Program (CMVP) to include; FIPS Pub 197 Advanced Encryption Standard, FIPS Pub 140-2 Security Requirements for Cryptographic Modules, FIPS Pub 198-1 The Keyed-Hash Message Authentication Code (HMAC), and IETC RFC 2560 X.509 Internet Public Key Infrastructure.

C.7 CONFIGURATION MANAGEMENT (CM)

C.7.1 The Contractor shall maintain a CM process to control all hardware and software configurations comprising the RCIS Type I. The Contractor shall use HBK-649A and MIL-STD-3046 as guidance. The Contractor shall maintain configuration management responsibility throughout the period of performance of this contract. The Contractor's part numbering system shall maintain links to any Original Equipment Manufacturer (OEM) part numbers. The Contractor shall manage and control the RCIS configuration until CDR (C.3.4.4). After CDR, Government written approval is required (IAW C.7.4.2) for all changes to the Product Baseline..

C.7.2 Configuration Management Process The Contractor shall develop a life cycle CM plan for all hardware and software items and manage the implementation of that plan. The Contractor shall provide the life cycle CM plan in the SEMP deliverable.

C.7.3 Configuration Baselines The Contractor shall deliver the Allocated and Initial Product Baselines in separate Baseline Description Documents. Reference the DAG Section 4.3.7. - Establishment of Configuration Baselines as a guide for defining the Allocated and Product Baselines.

Configuration baselines status shall be discussed at IPT meetings as well as the technical reviews defined in C.3.4. (IAW CDRL A026 Configuration Baseline)

C.7.4 Configuration Control Board

C.7.4.1 Change Log The Contractor shall maintain a change log to track changes and status of each change implementation. The change log shall include a description of changes, parts affected, reason for change, classification of change, status of change (New, In Design, In Validation, Approved, Implemented, Verified), date opened, date closed, deficiencies corrected, associated problems related. The Contractor shall make this information available to the Government (post to Integrative Data Environment (IDE) see Section C.8.2) and present this information at IPT meetings and technical reviews as defined in C.3.4.

C.7.4.2 Baseline Change Notification (BCN) After the CDR, the Contractor shall submit a BCN (IAW CDRL A027) for all Class I changes to the COR. The Contractor shall maintain configuration management of the Product Baseline.

C.7.4.2.1 Change Reporting After the CDR, the Contractor shall use the following classifications for all changes made to the baselines:

Class I: A change to Contractor approved configuration documentation, and:

(a) Affects any physical or functional requirement in Contractor approved ALLOCATED configuration documentation, OR

(b) Affects Contractor approved PRODUCT configuration documentation AND one or more of the following:

i) Government Furnished Equipment (GFE),

ii) Safety,

iii) Compatibility, interoperability, or logistic support,

iv) Contract schedule delay,

v) Will require retrofit of delivered units,

vi) Interchangeability, substitutability, or replaceability of any item down to non-repairable subassemblies,

vii) Sources on a source control drawing,

viii) Skills, manning, training, biomedical factors or human engineering design,

ix) Configuration item cost increase.

Class II: All other changes are Class II changes.

C.8 DATA MANAGEMENT

C.8.1 The Contractor shall possess an authoritative product data, engineering or CM system and the processes to effectively manage, securely store, release, validate, and track multiple versions and iterations of the as-designed and as-integrated configuration baselines. This includes management of product structures, product definition documents or data or both, Contractor or subcontractor or both test and analysis data, Government Furnished Information (GFI) and other related technical data. The Contractor shall allow Government personnel (identified at the SOWM) access to their CM system with read and download privileges for collaboration on in-work and released program data.

C.8.2 RCIS Integrated Data Environment (IDE) The RCIS IDE is a Windchill based, secure Government server that will be used to facilitate information sharing and collaboration between the Government and Contractor for controlled, distributed access to RCIS program information, both released and in-work. Types of information that will be processed and maintained within the IDE shall include RCIS program documents, reports, program management data, IPT/WG meeting-related information, modeling and simulation and/or analysis data, pertinent manufacturing information, and test data, consistent with the RCIS Security Classification Guide provided by the Government at the SOWM. Any posting to the IDE is considered a data deliverable in the context of DFARS Data Rights clauses including 252.227-7013, 252.227-7014 and 252.227-7020. The IDE will only be used for sharing Controlled Unclassified Information (CUI). The Contractor shall send all classified information via registered mail to the RCIS classified mailing address or other agreeable secure data transfer environment identified by the Government at the SOWM.

The Contractor shall deliver all data IAW the DD1423 CDRLs. The RCIS IDE has several distinct segregated areas (Government and Contractor). To access the RCIS IDE, Contractor associates shall have a DoD approved Public Key Infrastructure credential, obtainable through the DoD External Certification Authority (ECA) program:

http://iase.disa.mil/pki/eca/Pages/certificate.aspx. In the event Contractor associates are unable to obtain DoD approved Public Key Infrastructure credentials, all required data exchanges, with exception to classified data, shall be submitted directly to the COR.

C.8.3 EMD Technical Data Package (TDP) The Contractor shall develop, deliver, manage and maintain the TDPs for RCIS IAW MIL-STD-31000 throughout the contract performance period. (IAW CDRL A028 EMD

TDP))

C.8.4 CAD/CAE Technical Data Requirements http://iase.disa.mil/pki/eca/Pages/certificate.aspx

C.8.4.1 Simulation-based Design Model Data The Contractor shall deliver simulation-based Computer Aided Engineering/Finite Element Analysis (CAE/FEA) model data for completed Modeling and Simulation work, IAW CDRL A028. Simulation data shall be provided for each physical test and each acceptance test. The simulations shall provide data to calculate the performance cited in the RFP. The simulations shall be the integrating methodology, which brings together the key design goals, progress in meeting design goals, tests metrics, percent improvement in operational, combat, and cost effectiveness. Prior to submission, the Contractor shall verify that the Top Level Assemblies open without errors. Simulation based design model data in work shall be posted to the IDE (ref. C.8.2) and discussed at IPT meetings as well as technical reviews as defined in C.3.4.

C.8.4.2 Design CAD Data The Contractor shall deliver Design CAD Data for the RCIS Type I to be included in the TDP IAW CDRL A028. Prior to submission, the Contractor shall conduct solid model data Geometric Validation Properties (GVP) checks on CAD solid models to identify part, assembly, and installation shape and fit (geometry and topology) problems that will affect downstream applications, such as analysis, modeling and simulation, rapid prototype, and data exchange. Prior to submission, the Contractor shall verify that the Top Level Assembly opens without errors from the deliverable storage device (e.g. hard drive or DVD). The Contractor shall present Design CAD Data status for discussion at IPT meetings as well as technical reviews as defined in C.3.4

.C.9 RISK MANAGEMENT

C.9.1 Risk Management Plan The Contractor shall execute a risk management program by identifying, assessing, and mitigating technical, cost, and schedule risks IAW the Risk Management Guide for DOD Acquisition. The Contractor shall include its risk management plan as part of the SEMP.

The Contractor shall present system risks and mitigation plan status at formal technical reviews per Section C.3.4.

C.9.2 Risk Management Status Reports The Contractor shall prepare and deliver Risk Management Status Reports. (IAW CDRL A029 Risk Management Status Reports)

C.10 RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM

C.10.1 Reliability & Maintainability (R&M) Program Plan (RPP) The Contractor shall develop an R&M program, deliver an R&M Program Plan (RPP), and execute an R&M program for both hardware and software to achieve the reliability and maintainability requirements established in the RCIS Performance Specification (Attachment 0001). The Contractor shall use GEIA-STD-0009 as a guide for reliability practices. The RPP shall address each of the R&M activities described below. (IAW CDRL A030 Reliability & Maintainability Program Plan (RPP)). The RPP shall include:

a. Reliability Management and Organization. The report shall include an organizational chart that provides visibility into the management and organizational structure of those responsible and accountable for the conduct of reliability activities. The organization structure shall clearly define how those responsible for reliability activities interact with the design, systems engineering, test and evaluation, cost, and supportability teams. The organization structure shall also depict the interface between the Government and all subcontractors/suppliers (when applicable). The report shall define all responsibilities for the reliability team.

b. Reliability Requirements. The report shall include all reliability requirements and the source of the requirements. Any derived requirements shall include all assumptions related to the derivation of the reliability metric.

c. System Reliability Model (SRM). The report shall address the methods and tools that will be used for developing and refining the SRM. The report shall document how the SRM will be updated as the design evolves and new information about failure modes is identified. The SRM is a graphical depiction of the system with an underlying analysis such as Reliability Block Diagram, Fault Tree, or Event Tree.

d. Critical Elements. The report shall identify how critical elements will be identified.

C…