Attachment_0001-_Sentinel_A4_SOW_13_Jan__17.docx

Statement of Work For the Sentinel Increment A4 Program Engineering Manufacturing Development, Low Rate Initial Production, and Initial Fielding

Version 1.0 Draft Request for Proposal #1 13 January 2017

PREPARED BY:

Cruise Missile Defense Systems (CMDS) Project Office

ATTN: SFAE-MSL-CM

Redstone Arsenal, AL 35898-5000

***** DRAFT *****

i

Contents

1.0 GENERAL

This Statement of Work (SOW) defines the work to execute the Sentinel Increment A4 Program, hereafter referred to as the Sentinel A4. This program will cover Sentinel A4 Engineering Manufacturing Development (EMD), Low Rate Initial Production (LRIP), and initial fielding. In the event that there is a conflict between this SOW and other contract attachments, this SOW shall take precedence.

1.1 Background

The AN/MPQ-64A4 Sentinel, or Sentinel A4, is a three-dimensional X-band phased array radar system equipped to support beyond visual range air defense engagements. The Sentinel A4 is a modification to the Sentinel A3. The Sentinel A4 will provide new antenna subsystem components to add detection, classification, identification, and reporting capability against Rocket, Artillery, and Mortar (RAM) threats to support the Indirect Fire Protection Capability (IFPC) Increment 2-Intercept Block 2 mission. It also addresses current Sentinel A3 obsolescence issues and improving existing Sentinel capability against Cruise Missile (CM), Unmanned Aerial System (UAS), Rotary Wing (RW), and Fixed Wing (FW) threats.

1.2 SOW Overview

This SOW specifies requirements for the design, development, integration, documentation, testing, and production of the Sentinel A4. The SOW paragraphs contain three (3) task groups: common tasks spanning the entire contract, optional LRIP tasks, and optional tasks supporting a First Unit Equipped (FUE) initial fielding. Paragraph titles identify LRIP and FUE tasks; all other tasks not so designated are common tasks.

2.0 APPLICABLE DOCUMENTS

The contract Document Summary List (DSL) contains applicable documents by number, title, and date. The contractor shall use the version shown on the DSL for the Applicable Documents.

3.0 GENERAL REQUIREMENTS

The contractor shall design, develop, integrate, test, document, evaluate, and produce a modification to the Sentinel A3 system to create a Sentinel A4 system that meets the requirements of System Specification MIS-60990. The system includes the prime mover, trailer, and all other contractor and Government provided equipment and software necessary for Sentinel A4 to operate and communicate.

Security: The contractor shall follow all required security clauses and provisions in the contract. The contractor shall comply with the Contract Security Classification Specification, DD Form 254, and applicable attachments and the Antiterrorism/Operations Security (AT/OPSEC) Continuation Sheet, Section II Standard Contract Provision and Clause Text Applicability. The contractor shall use the latest Sentinel A4 Security Classification Guide that defines the classification of information and material for the Sentinel A4 program. The contractor shall obtain a SECRET (or higher) facility clearance from the Defense Security Service (DSS) and provide cleared personnel at the SECRET (or higher) level to perform classified tasks. The contractor is required to have at the minimum a SECRET level facility clearance in order to retain this contract. Contractor personnel performing with classified or sensitive information are required to maintain, at the minimum, a SECRET level security clearance to work on this contract. Contractor personnel ONLY requiring access to computer systems will have, at the minimum, a National Agency check with Written Inquiries (NACI) completed, with no derogatory information note upon review of the SF86, or equivalent, or discovered during the investigation, to be employed on this contract.

3.1 Sentinel A4 Modification

3.1.1 Sentinel A4 Antenna/Transceiver Subsystem Prime Mission Product The contractor shall design, develop, and build a new replacement antenna subsystem and its supporting elements for the Sentinel A4 to meet the requirements in the Sentinel A4 System Specification MIS-60990 and System Interface Description Document (IDD) 13717283. The contractor may incorporate existing Sentinel A3 subsystems or components as reused or modified reuse items where suitable to provide required functionality for the Sentinel A4. The contractor shall define, document, and follow a Modular Open Systems Approach in the design of the Sentinel A4 system and its interfaces.

3.1.2 Government Furnished Property Subsystem Integration and Interfaces The contractor shall integrate the following Government-Furnished Property (GFP), including associated interfaces, into the Sentinel A4 system: platform (Family of Medium Tactical Vehicles (FMTV) truck and trailer), prime power, electronics items, and Identification Friend or Foe (IFF). Relevant interfaces shall be compliant with the IDD 13717283. The electronics items include the Remote Control Display Unit, the Integrated Air and Missile Defense Battle Command System (IBCS) kit, router, North Finding System, Global Positioning System, and communications components. The Government will also provide the existing Sentinel Signal Data Processor as GFP. Use of the Signal Data Processor kit is optional. The contractor shall incorporate and integrate the executable GFP software specified as mandatory in the IDD to include Composite Tracker and Classifier (CTC) software and IBCS software.

3.1.3 Sentinel A4 Software

The contractor shall develop, deliver, implement, and maintain the required software needed to meet the Sentinel A4 performance and interface specifications.

3.1.3.1 Software Engineering

The contractor shall develop, implement, and maintain software development processes and metrics in accordance with (IAW) the Software Engineering Institute's Capability Maturity Model (CMM) or Capability Maturity Model Integration (CMMI) Level 3 or higher. The contractor shall develop and deliver a Software Development Plan (SDP) IAW DI-IPSC-81427. The SDP shall document the software processes and metrics. The contractor shall develop, manage, control configuration, and execute Software Quality Assurance (SQA) IAW the SDP.

The contractor shall develop, implement, and maintain the necessary software design to meet the requirements derived from MIS-60990 and IDD 13717283. The contractor shall document and deliver the software design and provide Software Design Descriptions for all Computer Software Configuration Items (CSCIs) IAW DI-IPSC-81435. The contractor shall allocate, decompose, and derive software requirements from higher-level system requirements to create the software-level component of the allocated baseline for the Preliminary Design Review (PDR). The contractor shall deliver Software Requirements Specifications (SRS) IAW DI-IPSC-81433.

The contractor shall isolate any proprietary software components or interfaces with adaptation layers that provide open interfaces. The contractor shall define, document, and follow a Modular Open Systems Approach in the design of the system software and interfaces. The contractor shall document the software architecture in the Architecture Description Document IAW DI-MISC-80508.

3.1.3.2 Computer Software, Firmware, and Executable Software

The contractor shall deliver the following documentation for software, firmware, and executable software: a) software executables IAW DI-AVCS-80700 to include software source files, build-and-make files, firmware, and related documentation and b) Software Version Description Documents for software changes IAW DI-IPSC-81442.

3.1.3.3 Software Integration, Assembly, Test and Checkout

The contractor shall conduct software integration, assembly, formal test, and qualification for each software build prior to release for use in system testing. The contractor shall conduct Software Qualification Testing (SQT) to verify the requirements in the Software Requirements Specifications, each IAW the specified qualification method. The contractor shall document and deliver a Software Test Description (STD) IAW DI-IPSC-81439 that describes the test preparations, test cases, test procedures, and methods to perform SQT of each software release. The contractor shall deliver Software Test Plans IAW DI-IPSC-81438 and Software Test Reports IAW DI-IPSC-81440. The contractor shall conduct SQT IAW the STD for each software release using production representative hardware where available. The contractor’s SQA personnel shall witness or audit all SQT events. The contractor shall invite the Government to participate in software testing events and shall provide a 30-day notice and invitation to witness prior to test events via the Integrated Product/Process Team (IPT) process.

3.1.4 Antenna Subsystem Integration, Assembly, Test and Checkout The contractor shall integrate, assemble, and qualify the antenna subsystem and supporting software to the required A4 specifications and interfaces. The contractor shall develop and deliver Acceptance Test Procedures (ATPs) IAW DI-NDTI-80603 that demonstrate Line Replaceable Unit (LRU) and antenna subsystem-level performance to all required performance specifications. The contractor shall include all necessary test equipment and methods for product acceptance. The contractor shall provide the Government a 30-day notice and invitation to witness prior to test events.

3.2 System Integration, Assembly, Test and Checkout

The contractor shall integrate, assemble, and qualify the Sentinel A4 hardware and software as a complete radar system meeting MIS-60990. The contractor shall perform ATP IAW DI-NDTI-80603 at the system-level prior to contractor system-level testing and prior to Government testing or use. The contractor shall include all necessary test equipment and methods for product acceptance. The contractor shall provide the Government a 30-day notice and invitation to witness prior to test events.

3.3 System Engineering

3.3.1 Engineering Management

The contractor shall manage the Systems Engineering process to include requirements development, requirements analysis/allocation, design, integration, and verification/validation. The contractor shall establish and maintain a Systems Engineering IPT. The contractor shall be responsible for developing and maintaining the currency and accuracy of the established system baselines (Functional, Allocated, and Product) to ensure form, fit, function, and interfaces of the Sentinel A4. The contractor shall establish definitive processes for baseline management and maintenance.

3.3.1.1 System Engineering Management Plan

The contractor shall develop, deliver, implement, and maintain a Systems Engineering Management Plan (SEMP) IAW DI-SESS-81785 using the Government-furnished System Engineering Plan (SEP) as reference.

3.3.1.2 Manufacturing Plan

The contractor shall develop, deliver, implement, and maintain a detailed Manufacturing Plan IAW DI-MGMT-81889 for EMD and transition to LRIP. The contractor shall describe the program, operations, and supply chain management related to asset production. The contractor shall document the manufacturing schedule, establish entry/exit criteria for all reviews, and demonstrate through analysis or simulation the production capacity to meet the required delivery schedule. The contractor shall document its manufacturing/operating systems, product/process flow, facility selection criteria, site qualification plans, test plans, test equipment, expected yields, and process control mechanisms. The contractor shall describe the tooling management approach from creation to disposal, in-process documentation and procedures, and the contractor’s security plan. The contractor shall identify all long-lead parts and materials. The contractor shall detail all labor by skill, certification, and training.

3.3.2 Requirements Development and Allocation

The contractor shall translate the Government System Performance Specification (MIS-60990) and interface requirements (IDD 13717283) into a contractor system-level specification and interface documents and allocate these requirements to contractor-controlled lower-level specifications. The contractor shall develop, deliver, implement, and maintain these specifications IAW DI-IPSC-81431 using MIL-STD-961 as guidance.

3.3.3 Design Verification

The contractor shall verify meeting the system and subsystem performance requirements contained in the contractor-developed specifications using the verification methods outlined in the specifications. The contractor shall verify requirements through demonstration, inspection, analysis, similarity, simulation, and/or testing as specified in the applicable specification verification matrix.

3.3.4 Modeling and Simulation

The contractor shall leverage the current Sentinel Digital Simulation (SDS) to develop, deliver, implement, and maintain a Sentinel A4 digital simulation, to include all contractor developed source code, IAW DI-AVCS-80700. The contractor shall prepare and deliver a User’s Manual IAW DI-IPSC-81443 that contains detailed instructions for execution of the simulation. The contractor shall deliver a detailed Programmer’s/Analyst’s Guide IAW DI-IPSC-81633. This document shall include a definition of inputs/outputs and detailed algorithm and model descriptions to include fidelity-level and limitations. The contractor shall deliver periodic updated simulation deliveries to the Government after implementing modifications and fixes. Adjustments/upgrades shall reflect the most recent validated test data. The contractor shall develop and deliver a Verification and Validation (V&V) Plan IAW DI-MSSM-81751 and V&V Report IAW DI-MSSM-81752, and update these documents to reflect changes. The model shall have the fidelity to support performance predictions and system requirements verification. The contractor shall develop the model with the capability to meet the required confidence level in the system specifications. The contractor shall provide test data for Independent Government Verification, Validation and Accreditation activities.

The Government will develop hardware and software based target injection and environment injection capabilities for development, verification, and life-cycle support actions. The contractor shall provide technical data to the Government regarding the development and validation of this target injection capability. The contractor shall incorporate injection ports (with timing and control signals) such that signal injection is readily feasible. The contractor shall coordinate the signal injection capability with the Government at or before the Sentinel A4 PDR.

3.3.5 Information Systems and Technology Protection

3.3.5.1 Information Assurance / Cybersecurity

For all requirements in this SOW, the contractor shall adhere to Cybersecurity (CS) / Information Assurance (IA) regulations and security policies including the following:

a. Federal Information Security Management Act (FISMA)

b. AR 25-1

c. AR 25-2

d. AR 25-2 Pamphlets

e. DoDI 8500.01

f. DODI 8510.01

g. NIST SP 800-53

h. CNSSI No. 1253

i. DoD Directive 8570.01

j. DoD Manual 8570.01-M

k. DoDI 8580.1

l. DoDI 8582.01

m. DoDI 8530.1

n. National Security Agency (NSA) Guides

o. National Institute of Standards and Technology (NIST) 800 Series

p. Defense Information System Agency (DISA) Security Technical Implementation Guides (STIGs)

q. Defense Federal Acquisition Regulation Supplement (DFARS) Clauses 252.204-7012 and 252.204-7008

r. Army best business practices/Network Enterprise Technology Command (NETCOM) Tactics, Techniques and Procedures (TTPs)

The contractor shall meet the requirements set forth in these Department of Defense (DoD) and Army regulations to obtain and maintain an Authorization to Operate (ATO) under the DoD Risk Management Framework (RMF) process. The contractor shall use security/network scanning tools to verify system software compliance to the DISA STIGs and quarterly IA Vulnerability Alert (IAVA) patches on the DoD Patch Repository located at https://patches.csd.disa.mil. Scanning tools for CS/IA and STIGs are located at http://iase.disa.mil/stigs/Pages/index.aspx. If downloads are unavailable, the contractor shall contact the Government for coordination of scan tool shipment. These scripts provide system developers a method to verify compliance of their software to the latest STIG requirements. Based on the information above, the contractor shall deliver an IA Design Review Information Package (IA DRIP) IAW DI-MGMT-81845.

3.3.5.2 Information Assurance Vulnerability Management

The contractor shall develop, deliver, implement, and maintain an IA Vulnerability Management (IAVM) Plan IAW DI-MGMT-81844. The IAVM Plan shall outline how updates (in the above-mentioned DISA website) are tested, approved (via a configuration control board), and implemented. The contractor shall quarterly review and evaluate the patches released onto the DoD Patch Repository and update the system software with the patches applicable to the operating system or applications resident on the system software. The contractor shall document and deliver all IA and CS scan test results in an IAVM Quarterly Release Test Results Report IAW DI-MGMT-81843. This IAVM Quarterly Release Test Results Report shall specify the IA and CS test/scans performed and results of all tests, applicable patches assessed/checked per system software versions, new patches implemented and not implemented for each quarterly DISA STIGS security scan performed, and IAVA CD or DVD distribution. This report shall contain the applicable IAVMs released and noted this quarter, the status of IAVMs regression testing, and recommended application of these IAVMs. If the contractor cannot apply an IAVM, the contractor shall provide the technical justification and identify what would be critically impacted and how this would affect the overall mission. After the Central Technical Support Facility (CTSF) releases the CD or DVD, the Government will provide the IAVA CD or DVD each quarter. The contractor shall perform activities required for CS/IA Certification of the baselines covered under this SOW.

3.3.5.3 DoD Information Technology Standards Registry

The contractor shall evaluate and document the system design, hardware and software designs, and software development environment compliance with the applicable portions of the DoD Information Technology Standards Registry (DISR). The contractor shall identify deviations from the standards and practices delineated in the DISR prior to implementation.

3.3.6 Program and Technology Protection

3.3.6.1 Program Protection Planning

The contractor shall establish and maintain a Program Protection IPT. The contractor shall execute the Sentinel A4 Program Protection IPT security management tasks. The following list is representative of those tasks: Identification, review, and update of Critical Program Information (CPI), Critical Technology (CT), Mission Critical Functions/Components and Information, and Communications Technology (ICT) critical end-items/components, as required; CPI/CT vulnerability assessments; and development of protective countermeasures. The contractor shall develop, implement, and maintain an integrated System Security Engineering (SSE) process as part of its System Engineering process and document this SSE process in the SEMP.

The contractor shall develop, deliver, implement, and maintain a Program Protection Implementation Plan (PPIP) IAW DI-ADMN-81306 to ensure effective and efficient protection of essential program information, technologies, and systems. The PPIP shall include the contractor’s security management structure and CPI physical locations under the contractor or subcontractor’s control. The contractor shall assess the vulnerability of the CPI to intelligence collection in the following areas: Human Intelligence (HUMINT), Open Source Intelligence (OSINT), Signals Intelligence (SIGINT), Imagery Intelligence (IMINT), and Computer Network Operations (CNO).

The contractor shall, IAW the PPIP, identify and implement countermeasures at each site where CPI exists from the following security domains (as applicable): physical security, personnel security, telecom and network security, application/systems development, cryptography, security architectures, operational security, and network and Information Technology (IT) access control. The contractor shall address any special handling procedures required for CPI and procedures for recovering CPI in the event of a mishap. The contractor shall follow required procedures for ensuring compliance with Government export statutes and regulations. The contractor shall follow required procedures for public release of program information.

3.3.6.2 Software Assurance

The contractor shall conduct a software assurance evaluation using Common Vulnerabilities and Exposures (CVE), Common Attack Pattern Enumeration and Classification (CAPEC), and Common Weakness Enumeration (CWE). The contractor shall develop, document, and update the Software Assurance Countermeasures Table, software assurance plans, and actuals IAW the table description provided in the Defense Acquisition Guidebook section 13.7.3 (https://acc.dau.mil/dag13.7.3) and provide as part of the PPIP. The contractor shall provide testing results that determine vulnerabilities and threats in the appropriate sections of the PPIP. The Government will provide the contractor a list of the Top-n most important CWEs. The contractor shall outline its process to deliver all software free of all CWEs in the Government’s Top-n CWE list in the PPIP. The contractor shall develop and deliver a Software Assurance Evaluation Report IAW DI-MISC-80508.

3.3.7 Anti-Tamper

The contractor shall implement an Anti-Tamper (AT) program and AT Plan as appropriate to identify and protect CPI and CT in each system and subsystem as defined by DoDI 5200.39, or as indicated in DoDI S-5230.28. The contractor’s AT program shall protect critical design and manufacturing process knowledge and slow Reverse Engineering (RE) and technology proliferation. The contractor shall include AT on the agenda for all Program Management Reviews and major program reviews.

The contractor shall develop, deliver, implement, and maintain an AT Plan IAW DI-MISC-80508 for the configuration. The contractors’ initial AT Plan shall enable the Government to determine the contractor’s understanding of the AT engineering process and evaluation of associated risk. The AT Plan shall also establish a basis for further development.

The AT Plan shall contain the following information:

a. Sentinel A4 performance requirements

b. Contractor’s proposed Sentinel A4 architecture

c. The CT for proposed architecture and locations of CT in the architecture

d. Impacts if CT is exploited by an adversary

e. Required protection timelines

f. Threat scenarios for loss of CT

g. Vulnerabilities of CT in the proposed system

h. Attack tree analysis

i. Available AT techniques for proposed system

j. Identify potential AT solutions for proposed systems

k. The AT development schedule, including system/subsystem technical reviews, AT Technical Interchange Meetings (TIMs), V&V schedule

l. Plan to integrate AT into SSE for each spiral/incremental upgrade

m. An AT verification and validation plan as an appendix

The contractor shall develop, deliver, implement, and maintain a cryptographic requirements and Key Management Plan IAW DI-MISC-80508. The contractor shall develop and implement a process to ensure sanitization of CPI-related engineering data (e.g., static state, dynamic state, algorithms, and system descriptions) from technical manuals, maintenance instructions, schematics, training documentation, operating manuals, tactics manuals, and software documentation. This process shall ensure the level of detail in the technical data is limited to the intended scope of the publication and the “need-to-know” of the intended audience. The contractor shall meet Government traceability requirements.

The contractor shall incorporate defense exportability features and Foreign Military Sales (FMS) considerations in the Sentinel A4 hardware and software designs and configurations.

3.3.8 Specialty Engineering

3.3.8.1 Environmental Safety and Occupational Health

All contractor and subcontractor activities shall comply with applicable federal, state, and local environmental laws and regulations. The contractor shall develop and deliver a Hazardous Materials Management Program (HMMP) Plan IAW DI-MGMT-81398. The contractor shall prepare a HMMP Report IAW DI-MISC-81397. The HMMP Reports shall identify via graphic or drawing of the specific location of each hazardous material contained in the final end-item(s).

Tracked HAZMATs in National Aerospace Standard (NAS) 411 shall be defined as Emergency Planning and Community Right-To-Know Act (EPCRA) 302/313 listed chemicals. In the HMMP Report, the contractor shall report the data elements found in MIL-STD-882E, Task 108, section 108.2.4 a, b, and d for Tracked HAZMATs. The contractor shall report coatings (identified by MIL SPEC), functional fluids (e.g., coolant, hydraulic fluid, lubricants, etc.), and energetics/solid rocket motor components (including Explosives Class Number) with the same 108.2.4 a, b, and d data elements. As part of the HMMP Report, the Contractor shall provide Material Safety Data Sheets (MSDSs) or Safety Data Sheets (SDSs) for all reported materials.

The contractor shall not use any Class I or Class II Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS), identified by the lists at http://www.epa.gov/ozone-layer-protection/ozone-depleting-substances, in the manufacture or support of items required by this SOW unless approved IAW Army ODS policy and/or Title 10 United States Code section 2402. All ODS alternatives shall be in compliance with the U.S. Environmental Protection Agency (EPA) Significant New Alternatives Policy (SNAP) program and identified as approved – per the specific application – in the lists at http://www.epa.gov/ozone/snap/lists/. All ODS alternatives shall also receive a Toxicity Clearance for the specific application from the US Army Public Health Center.

The contractor shall list any hazardous material, as defined NAS 411-1, used for the maintenance, sustainment, and demilitarization of the end item under this contract in the HMMP Report. The hazardous material shall be properly identified and include any applicable identification number, such as National Stock Number or Special Item Number. The contractor hazardous materials list shall be updated during performance of the contract whenever the contractor determines that any other material to be used in the maintenance, sustainment, and demilitarization of the end item under this contract is hazardous.

3.3.8.2 Health Hazards

The contractor shall identify all potential health hazards that are indigenous to and generated by the system, including GFP, and shall adhere to Occupational Safety and Health Administration (OSHA) compliance criteria or to Government approved levels when regulations do not exist. The contractor shall provide MSDSs for all hazardous materials used in/with the system. The contractor shall provide this information as an appendix to the Safety Assessment Report (SAR). The contractor shall identify health hazards through the System Safety Working Group (SSWG).

3.3.8.3 Hazardous Materials

The contractor shall not use highly toxic or carcinogenic materials without written authorization from the procuring activity prior to use as specified in the Registry of Toxic Effects of Chemical Substances (RTECS) and OSHA. The contractor shall not use materials identified in the RTECS, published by the National Institute for Occupational Safety and Health (NIOSH), since these materials produce toxic effects to the respiratory tract, eye, skin, or mouth. The contractor may use moderately toxic materials if the design and control(s) preclude personnel from exposure to environments in excess thresholds specified in 29 CFR 1910, OSHA, Sub part Z. The contractor shall not use materials that produce toxic fumes or support combustion when burning or exposed to high temperatures.

3.3.8.4 Human Systems Integration and Human Systems Engineering The contractor shall incorporate Human Systems Integration (HSI) requirements into the design IAW MIL-STD-1472. The contractor shall identify and document HSI related issues and concerns, and provide access to recommendations regarding problem resolution. The contractor shall address HSI related program status/issues as part of the IPT process. The contractor shall conduct analyses and testing of operator, maintainer, and support tasks that account for appropriate combat clothing and personal protective equipment for normal, arctic, and chemical, biological, radiological, and nuclear (CBRN) environmental conditions to demonstrate that the target audience can perform mission essential tasks. Analyses shall address training, personnel, survivability, human factors engineering, safety, and health hazards. The contractor shall document and provide access to HSI related analysis results as part of the IPT process.

3.3.9 Safety

The contractor shall ensure safety in all procedures, processes, and methods necessary to the performance of this contract. The contractor shall establish and maintain a SSWG consisting of contractor and Government representatives. The contractor shall use the SSWG as the coordinating body for compliance with SOW safety requirements.

3.3.9.1 System Safety Program

The contractor shall perform System Safety using MIL-STD-882 and MIL-STD-1472 and Software System Safety using Aviation and Missile Command (AMCOM) Regulation 385-17 for information and guidance. The contractor shall perform safety analysis and assessment. The contractor's System Safety Program (SSP) shall identify and mitigate system-level and subsystem hazards, as well as software system hazards. The SSP shall demonstrate compliance with and traceability to the Government-furnished Sentinel System Safety Management Plan (SSMP). The contractor shall provide inputs for SSWG meetings, customer interface meetings, Sentinel milestone decisions, AMCOM Software System Safety Technical Review Panel (SSSTRP) meetings, and interoperability with other Services and Agencies.

3.3.9.2 System Safety Program Plan

The contractor shall develop, deliver, implement, and maintain a System Safety Program Plan (SSPP) IAW DI-SAFT-81626 and AR 385-10, using AMCOM Regulation 385-17, DA PAM 385-16, MIL-STD-882, and MIL-HDBK-454 for information and guidance. As an appendix to the SSPP or as in-line sections of the SSPP, the contractor shall develop, implement, and maintain a Software System Safety Program Plan (SwSSPP) that addresses integration of software (including firmware) safety within system safety and the software development process. The SSPP shall address all new and modified Sentinel software to include non-developmental item (NDI), Commercial Off-the Shelf (COTS), and reuse software, as well as developed software. The SwSSPP shall define the processes for identification of safety-critical/safety-related software functions, software contributions to system-level hazards, safety-critical/safety-related software requirements necessary to mitigate hazards, and the safety verification process for software (i.e., Level of Rigor), to include regression testing for modified software. The contractor shall identify Software Hazard Criticality Indexes (SHCI) for all safety-critical and safety-related requirements/functions and document in the hazard tracking system. The contractor shall perform hardware and software hazard analyses, and document the analyses in a SAR. The Software Hazard Analysis process shall include verification that the actual design supports hazard elimination or reduction.

3.3.9.3 Safety Assessment

The contractor shall develop, deliver, implement, and maintain the SAR IAW DI-SAFT-80102. The contractor shall perform hardware and software hazard analyses and document the analyses in the SAR. The Software Hazard Analysis process shall include verification that the actual design supports hazard elimination or reduction. The SAR shall include the following as attachments:

a. Reports showing traceability/evidence of safety-critical/safety-related requirements

b. Hazard Tracking System Records

c. Functional Hazard Analyses (FHA) (includes FHA per SSPP)

d. Subsystem Hazard Analysis (SSHA) (includes SSHA per SSPP)

e. System Hazard Analysis (SHA) (includes software SHA per SSPP)

f. Operating and Support Hazard Analysis (O&SHA)

g. Fault Tree Analysis (or equivalent level of detailed safety analysis) for catastrophic and critical hazards related to Sentinel

h. Top Level Events (inadvertent/erroneous track and/or release)

i. System Safety Risk Assessments (SSRA)

j. Existing SARs that are applicable.

3.3.9.4 Engineering Change Proposal Safety Analysis

The contractor shall assess all Engineering Change Proposals (ECP) and Request for Variance (RFV) for safety impact; the contractor shall include safety impact assessment in the ECP or RFV package. For each ECP, the contractor shall include an Engineering Change Proposal Safety Report prepared using DI-SAFT-80103 as guidance. For each RFV, the contractor shall include a Waiver or Deviation System Safety Report prepared using DI-SAFT-80104 as guidance.

3.3.9.5 Hazard Tracking System

The contractor shall develop, deliver, implement, and maintain a Hazard Tracking System (HTS) database to document, track, and manage all hazards identified during design, development, and test activities and deliver a System Safety Hazard Analysis Report IAW DI-SAFT-80101. The contractor shall track all identified Sentinel A4 hazards, interface to integration hazards (if interfacing an existing system), and Sentinel A4 contributions to system of systems top level events in the HTS database. The HTS shall address Sentinel A4 contributions to potential system-level hazard occurrence (including system of systems), or have references to the documented detailed description of contributions to hazards and how those contributions are mitigated. The contractor shall update and maintain the SSWG approved Sentinel hazards within the HTS as required. The contractor shall ensure that subcontractors address and incorporate system and subsystems hazards in the HTS.

3.3.10 Configuration Management

3.3.10.1 Configuration Management Plan

The contractor shall develop, deliver, implement, and maintain a Configuration Management Plan (CMP) IAW DI-SESS-80858 and ANSI/EIA-649-1, using MIL-HDBK-61 as guidance. The CMP shall include the contractor’s Configuration Management Operating Plan/Instructions and shall describe the contractor’s hardware and software Configuration Management (CM) program. The CMP shall describe the CM program organization; conduct of the CM program; and the methods, procedures, and controls of effective configuration identification, change control, and status accounting.

3.3.10.2 Configuration Changes

The contractor shall establish and maintain baseline control of the Sentinel A4 hardware and software product specifications, drawings, and related technical data that comprises the Technical Data Package (TDP) through formal technical reviews within the IPT process. The contractor shall document all contractor change requests that establish the Functional, Allocated, or Product Baselines by an ECP. The contractor shall prepare and deliver ECPs IAW DI-SESS-80639 and Notices of Revision (NOR) IAW DI-SESS-80642. The contractor shall submit ECPs on RDMR Form 523; submit NORs on RDMR Form 524. The contractor shall prepare Engineering Release Record (ERR) IAW DI-SESS-80463 and submit on RDMR Form 526. The contractor shall prepare and deliver a RFV IAW DI-SESS-80640 for all major and minor nonconformities. The contractor shall prepare and deliver Source Control Drawing Approval Requests IAW DI-SESS-81010.

3.3.10.3 Configuration Audits

The contractor shall develop, deliver, implement, and maintain a Configuration Audit Plan IAW DI-SESS-81646 in support of Government-conducted configuration audits. The contractor shall prepare and deliver the audit results IAW DI-SESS-81022.

3.3.10.4 Functional Configuration Audit

The contractor shall prepare and deliver a Functional Configuration Audit (FCA) Plan IAW DI-SESS-81646. The contractor, IAW the FCA Plan, shall prepare and make available all documentation required for the conduct of the FCA. The contractor shall conduct an FCA, with Government witnesses, to verify that the product baseline adequately reflects the requirements of the system and subsystem specifications. The contractor shall prepare and deliver the audit results IAW DI-SESS-81022. The report shall document the matrix flow-down of the demonstrated performance requirements through test, observation, or analysis for presentation at the FCA.

3.3.10.5 Request for Nomenclature

The contractor shall prepare and deliver Requests for Nomenclature (RFNs) (DD Form 61) IAW DI-SESS-81254.

3.3.10.6 Serialization / Numbering

The contractor shall prepare and deliver reports of all Government serial numbers issued to hardware under the contract IAW DI-SESS-81253. The report shall identify the usage of each serial number assigned, consumed, or destroyed due to test or material loss. The contractor shall assign serial numbers to all hardware items produced as specified by the Government. The Government will provide serial numbers upon request. The contractor shall apply serial numbers IAW applicable drawings and specifications for the items requiring the serial number.

The contractor shall use Army specification and drawing numbers provided by the Government for documents developed under this SOW. The contractor shall prepare, deliver, and maintain the Drawing Number Assignment Report IAW DI-SESS-81011. The contractor shall include the Commercial and Government Entity (CAGE) code assigned by the Government on all drawings and specifications.

3.3.10.7 As-Built Records

The contractor shall prepare and deliver Configuration Status Accounting Information IAW DI-SESS-81253. The contractor shall define, record, and report the configuration actually delivered (as-built) including serialization and lot data. This report shall cover all hardware and software produced under this contract. The contractor shall maintain traceability of all reused components back to the original system configurations and as-built records. The contractor shall maintain the reused components in the same configuration as delivered with the addition of new hardware and software. The contractor shall maintain these records utilizing systems currently in existence. The Government reserves the right to audit these records periodically to ensure compliance with these requirements. The contractor shall maintain production records to deliver Production Configuration Traceability Reports IAW DI-SESS-81253 of implemented ECPs and RFVs for all delivered hardware and shall provide the traceability accuracy in the Traceability of Changes, Deviations, and Waivers in the Configuration Status Accounting Information.

3.3.10.8 Physical Configuration Audit (LRIP option)

The contractor shall prepare and deliver a Physical Configuration Audit (PCA) Plan IAW DI-SESS-81646. The contractor, IAW the PCA Plan, shall prepare and make available all documentation required for the conduct of the PCA. The contractor shall conduct, in conjunction with the Government, PCAs for critical items to confirm proper translation of the tested design into the engineering drawings and system and subsystem documentation. The contractor shall prepare and deliver a Configuration Audit Summary Report IAW DI-SESS-81022.

3.3.11 Quality Assurance

The contractor shall develop, implement, and maintain a quality system IAW ANSI/ISO/ASQ 9001:2000 or AS 9100 or equivalent systems as approved by the Government. The contractor shall deliver a Quality Assurance Program Plan (QAPP) IAW DI-QCIC-81722 that documents this system. The Government will approve changes or exclusions to the contractor’s quality management system. The contractor shall make available, for review by the Government, quality system procedures, planning and all other documentation and data that comprise the contractor's quality system for both hardware and software. The Government will review the documents that comprise the quality system, and may perform necessary inspections or evaluations to confirm conformance to requirements and adequacy of the quality system.

3.3.11.1 Quality Assurance Program Plan

The QAPP shall describe the methodology used throughout all phases of the program (development, fabrication, test, delivery, and post-delivery support) to meet the quality requirements for this program. The QAPP shall identify the industry model used in calculating software and hardware reliability prediction and growth. This QAPP shall maximize the use of existing policies and procedures to the extent that they meet the quality requirements. The QAPP shall contain a listing of the procedures that are used to satisfy program Quality Assurance requirements.

3.3.11.2 Conformance

The contractor shall deliver items that conform to the requirements of the specifications referenced in this SOW. Surveillance, inspection, or tests made by the Government, at a contractor facility or at a Government facility, or the contractor’s compliance with the QAPP and all applicable Quality Assurance requirements, shall not relieve the contractor of the responsibility to furnish items that conform to the requirements. Unless granted an exception or waiver, the contractor shall comply with all restrictions on the acquisition of foreign products and services imposed by DoD appropriations and authorization acts and other statutes.

3.3.11.3 Nonconformance

The contractor shall use a Government-approved process and tracking system, outlined in the QAPP, for evaluation and disposition of non-conforming material. The contractor shall use this system for tracking, analyzing to determine root cause, and assuring effective preventative/corrective action implementation. The contractor shall ensure that all products meet specified contractual requirements. The contractor shall not use non-conforming products without specific Government authorization. The contractor shall not disposition non-conformances as “use as is” or “repair” without Government approval. Rework to print is acceptable. The contractor shall maintain a procedure to control the identification, documentation, evaluation, disposition, and segregation requirements of non-conforming products. The contractor shall notify the Government of non-conforming products via the Material Review Board (MRB) or RFV process. The contractor shall notify the Government immediately of discovered non-conformances that may exist in previously delivered product. Notification shall include a description of the suspected nonconformance, potential risk or product impact, contract number, Part Number, National Stock Number (NSN), affected serial numbers, or lot numbers, when applicable.

3.3.11.4 Subcontractor and Supplier Management

The contractor shall document procedures and policies for managing subcontractor and supplier quality. The contractor shall develop, implement, and maintain a Subcontractor/Supplier Quality Management Plan. The plan shall identify processes for selecting, qualifying, and managing subcontractors and suppliers; how the contractor will manage the products and processes; and the flow-down of applicable quality requirements to subcontractors and suppliers. The plan shall address assessing subcontractor/suppliers capabilities; verifying compliance of subcontractors/suppliers; and establishing metrics for continuously monitoring and rating supplier quality performance.