Attachment 1 - Surface Undersea Warfare SOW.docx

ATTACHMENT 1 - EXAMPLE SURFACE UNDERSEA WARFARE STATEMENT OF WORK

The following Statement of Work is derived from solicitation N00024-17-R-5225 as updated in May 2017.

3.0 REQUIREMENTS

This SOW defines the efforts required for the program management, production manufacturing, systems engineering, software development, logistics and supportability engineering, configuration management, hardware and software integration (including material procurement or fabrication, and integration of GFP, as applicable), test, evaluation, and installation support of Surface Ship USW systems. The requirements set forth in this SOW are applicable to specific tasks performed by the Contractor under this contract to the extent specified and through any written individual Technical Instructions issued by the Contracting Officer’s Representative (COR) in accordance with Naval Sea Systems (NAVSEA) clause C-242-H003 or assigned task with this solicitation. Such guidance or clarification can be in the form of replication or by reference to SOW paragraph numbers in part or in total.

The Surface Ship USW Combat Systems Contractor shall provide the material, equipment, supplies and technical engineering required to define, design, develop, integrate, test, deliver and support the CG-47s, DDG-51s, LCSs, FFs, DDG-1000s, future surface combatants, Foreign Military Sales (FMS) cases for similar systems, and other platforms.

Frequently within ship classes there are multiple versions of hardware and software. This procurement is for the integration of capabilities to create evolutionary baselines via the ACB process and provide upgrades/replacement to these diverse platforms in an Open Architecture (OA) environment.

The requirements in Sections 3.1 through 3.8 of the SOW have been organized into the following subparagraphs:

3.1) Program Management: Details the overall Program Manager (PM) requirements across all elements of the contract.

3.2) Engineering: Requirements for development of each integrated ACB; requirements for the design of hardware baselines; requirements for the manufacture of hardware systems for contracted platforms.

3.3) Test and Evaluation: Details the test and evaluation activities associated with developing, certifying, and fielding USW combat system baselines and updates.

3.4) Integrated Logistics Support (ILS) Support: Details development of source material for ILS products created under other contract(s).

3.5) Configuration Management (CM): Details management of the hardware and software configurations across the development and fielding of USW combat system variants.

3.6) Training: Details activities associated with developing source material for USW combat system training products developed under other contract(s).

3.7) Installation, Checkout and Field Support: Details activities, to include on-site subject matter expertise, in support of USW combat system installation and check out (INCO) performed under other contract(s).

3.8) In-Service Engineering Agent (ISEA) Support: Addresses maintenance activities associated with required updates to USW combat system software configurations that have already been fielded.

3.1 PROGRAM MANAGEMENT

The Contractor shall designate a Program Manager (PM) who shall have the responsibility for the planning, execution, and control of all aspects of this contract and the authority to commit the Contractor to specific courses of action. In addition, the PM will be responsible for directing its subcontracting efforts. The PM shall have the necessary authority to utilize the company’s resources to assure the tasks of this SOW are accomplished. The PM shall be authorized to deal directly with PEO IWS 5 and/or the designated representative on all matters pertaining to this contract.

The Contractor shall facilitate participation by the large number of organizations contributing to the USW baseline, including establishing relationships with key small businesses participating in USW system development. The Contractor shall be responsible for organizing, coordinating, controlling and reporting the status of all contract activities related to this contract, including activities assigned to subcontractors, to ensure the on-time delivery of all supplies and services specified in this contract.

3.1.1 Financial Reporting

The Contractor shall maintain technical and financial status and generate progress reports. The financial status shall include the Actuals to Date (ATD), Estimate to Complete (ETC), amount funded and outlooks for when additional funding is required, as necessary, for tasks as identified in Technical Instructions.

3.1.2 Subcontract Management and Control

The Contractor shall identify and monitor subcontractor technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor’s own established subcontract management techniques. The USW system is comprised of functional segments developed and maintained by a multi-organizational community of experts, including a large number of small businesses. The infrastructure of the USW system is determined by the Program Office.

3.1.3 Contract Work Breakdown Structure

The Contractor shall develop and maintain the Contract Work Breakdown Structure (CWBS) and CWBS dictionary using MIL-HDBK-881A for guidance. The CWBS provides the basis for further extension by the Contractor to lower levels during the performance of the contract. The Contractor shall extend the CWBS down to a minimum of three (3) levels required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for Government visibility. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements specified in this SOW and the system specifications and translate them into a structure representing the products and services that comprise the entire work effort under the contract. Changes to the CWBS or associated definitions, at any reporting level, require approval of the Government.

3.1.4 Contractor Performance Management System

For production tasks, the Contractor shall utilize an Earned Value Management System (EVMS), segregated by production task, and provide a Contract Performance Report for tracking and reporting costs segregated by tasks. EVMS shall be linked to and supported by the Contractor’s management processes and systems to include the integrated master schedule, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for the early indication of cost and schedule problems, and their relation to technical achievement.

3.1.5 Integrated Baseline Reviews

The Contractor shall engage jointly with the Government’s Program Manager in Integrated Baseline Reviews (IBR) to evaluate risks inherent in the Contractor’s planned performance measurement baseline established from the culmination of Technical Instructions in effect per year during execution of the contract. The initial IBR baseline shall be jointly determined 90 days after a hardware order is issued; subsequent baselines will be established prior to the year of execution. Each IBR shall verify that the Contractor is using a reliable performance measurement baseline, which includes the entire scope of work for the culmination of Technical Instructions that are in place during the year of execution, and is consistent with Contract schedule requirements and has adequate resources assigned.

3.1.6 Integrated Master Schedule

The Contractor shall establish and maintain the initial baseline Integrated Master Schedule (IMS) by logically networking detailed program activities, task interdependencies, and critical path activities to completion of the contract. Any changes to the baseline require approval by the Government. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and all activities from contract award to the completion of each TI and ACB. The schedule shall reflect all assigned Technical Instructions. The IMS should have a direct and traceable correlation between events in the Program Management Plan (PMP). The Contractor shall make periodic deliveries of the IMS in accordance with (IAW) the DD1423. The Contractor shall assist the Government to incorporate the IMS data into applicable Government program level IMSs.

3.1.7 Program Risk Analysis

The Contractor shall perform a continuous analysis of program, technical, cost and schedule risk. The analysis shall identify the risks associated with each area, identify the impact of each risk on the overall program, and proposed approaches for reducing identified risks. Risk analysis status shall be reported in the Contractor’s Progress, Status and Management Report and presented during Program and Technical Reviews.

3.1.8 Program Management Plan

The Contractor shall develop a Program Management Plan (PMP) for the program that will support Government established schedule requirements as documented and specified in this SOW and any subsequent Technical Instructions. Using a metrics based management approach, the Contractor shall document in the PMP all planning, scheduling, technical, cost, risk, and quality monitoring/reporting of each Technical Instruction/contracted tasks with program-wide visibility of plan versus actual efforts under this contract. The Contractor shall provide their proposed metrics in the PMP. The PMP shall be provided to the Government for review and approval.

3.1.9 Meetings

The Contractor shall conduct program progress and status review meetings at regular intervals at times and places mutually agreed upon between the Contractor and IWS 5. These meetings shall be held quarterly. PEO IWS5 and/or such representatives as designated by PEO IWS5 shall be invited to the meetings. The Contractor shall issue a schedule for Program Reviews on a quarterly basis that plans at least 6 months into the future. Technical Interchange Meetings (TIM) shall be conducted in accordance with each Technical Instruction.

At each program review the Contractor shall report at a minimum the status of the following:

a) Cost/schedule performance

b) Small Business Utilization

c) Design and technical issues

d) Hardware and software engineering

e) Risk analysis activities

f) Reliability and maintainability

g) Test and evaluation activities

h) Production activities

i) Logistics development efforts

j) Safety program status

k) Configuration management activities

l) Government Furnished Property (GFP) and Government Furnished Information (GFI) status

m) Efforts authorized under Technical Instructions

n) Data items delivery schedule

o) Hazardous material management efforts

p) Cybersecurity/ Information assurance/Anti-Tamper

q) Field Engineering Support/Post Delivery Support activities

The Contractor shall prepare agendas for Contractor-hosted meetings, program reviews, Integrated Process Teams (IPTs) and all other meetings/reviews. The agendas shall be reviewed jointly between the Government and Contractor and distributed electronically via e-mail by the Contractor. Minutes of the meetings shall be kept by the Contractor unless otherwise directed by the Government. Minutes of major programmatic and technical review meetings highlighted above, shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and distributed electronically.

3.1.10 Design Disclosure, Intellectual Property and Data Rights

The Contractor shall establish and maintain a process that will provide design disclosure directly to third party developers via electronic access to in-process design documentation and computer software. The Contractor shall support initiatives of the Shipboard Combat Systems Development community intended to achieve open architecture and commonality. The Contractor shall establish an Associate Contractor Agreement with each third party developer and coordinate disclosure directly with the developers. The exchange of information shall be structured so as to protect the Contractor's and third party developers’ proprietary rights in the information. The Contractor shall furnish to the Procuring Contracting Officer (PCO) a copy of the Associate Contractor Agreement and copies of all written communication between the Contractor and the third party developers that is pertinent to this contract. The Contractor shall discuss and attempt to resolve any problems between the Contractor and the third party developers and notify the PCO if required, in writing, of any problems including documentation of problem resolution. The Contractor and their subcontractors are responsible to ensure that all software developed under this contract is properly marked with the delivered product. In addition, metadata for software and documents shall be provided with all final USN software and document products. In the case of software delivered for FMS, it shall be the Contractor’s responsibility to provide the Navy with a solution that includes only software and documentation that complies with Navy international release and disclosure policy for the specific FMS tasking.

3.1.11 Non-Developmental Items Licenses

The Contractor shall be responsible for the procurement of all hardware and software licenses for Non-Development Item (NDI) products delivered in this contract including both Contractor developed and third party NDI. If the Contractor needs to obtain a license for any NDI incorporated into a deliverable under this contract, the Contractor shall notify the Government immediately in writing. This notification shall specify whether the license(s) that need to be procured are transferable to the Government, FMS, and/or any other contractors. Specifically, licenses shall support transfer of the total integrated system to the Government, including FMS. The notification shall also provide all pricing information necessary to the Government for any such licenses that the Contractor procures under this Section.

The Contractor shall provide to the Government all licenses and documentation required by the Government to support any NDI that is modified by the Contractor.

3.1.12 Data Management

The Contractor shall be responsible for the digital generation, reception and electronic delivery of data. All data shall be developed, managed, used, and delivered/exchanged electronically to the greatest extent practical.

Controlled Unclassified Information (CUI) submitted by email shall be digitally signed and encrypted. All unclassified electronic deliverable data items shall be delivered via the Government’s web server, PEO IWS5 Integrated Product Data Management System (iPDM). Individual iPDM accounts must be requested by the Contractor for all personnel who will load and/or access data into the Government system. A Public Key Infrastructure (PKI) certificate is required to access all Government databases and will be the responsibility of the Contractor. The Government will provide the Contractor twenty-four hour a day access to iPDM (except for planned maintenance or unplanned outages). The Government shall provide training for using iPDM and iPDM application tools if requested. Tracking, review, comment generation and consolidation, comment resolution and approval of the Contract Deliverables shall be done via iPDM.

The Contractor shall maintain a record of any Government Furnished Property (GFP) received, data items submitted, and technical and logistic documents generated in support of USW combat system development and production which is submitted for Government use. Such data shall be cataloged in a Data Accession List (DAL). The Contractor shall provide the Government team access to all data listed in the DAL, created for this contract.

When data has been developed under a previous contract a certificate of prior submission may be submitted in lieu of submitting a duplicate data item. The item must, however, be certified by the Contractor as being 100% correct and in full compliance with the requirements of this contract. The Contractor shall provide a copy of previously submitted data, if requested, in writing, by the COR.

All contract data delivered by electronic media, shall be accessible by one or more of the following application programs:

a) NMCI Microsoft Office Suite (Word, Excel, PowerPoint, MS Project, Access)

b) AutoCAD 21.0 with compatibility to Solidworks 2016

c) MATLAB 9.0

d) Interactive Computer Aided Provisioning System (ICAPS) Stand-Alone 5.1 and ICAPS Client/Server (C/S) (for Provisioning Technical Documentation (PTD) only)

e) Computer-Aided Software Engineering (CASE) tools as agreed to via the approved Software Development Plan (SDP)

The version of the application programs may be changed to a different version with mutual consent of the Contractor and PEO IWS5. Other application programs may be used upon explicit approval by PEO IWS5.

If required, the Contractor shall establish secure communication capabilities for the transmission of sensitive and classified data and to provide support to the operating Fleet and its land based support activities.

Classified data deliveries that require digital media delivery shall be delivered in electronic media and hardcopy format. Deliveries too large for delivery by E-Mail or electronic media (file size, drawings, data packages etc.) shall be delivered in hardcopy format in accordance with the applicable DD Form 1423.

3.1.13 Integrated Product Team

It is essential that the Contractor works in a collaborative environment with a consortium of Navy, Navy Laboratories, Academia, and other industry partners to ensure continued success of the program. The Contractor (including subcontractors and vendors as necessary) shall attend, present as necessary, and participate in Integrated Product Team (IPT) meetings. Contractor participants shall be subject matter experts in the appropriate areas and have sufficient decision making authority to expedite process and product changes within the scope and terms of this contract. Efforts are expected to include activities such as participation in meetings, providing subject matter expertise, sharing of pertinent technical data and work products, sharing of cost data (as appropriate) and performing design analyses and trade studies for the respective Contractor’s area(s) of responsibility.

To the extent specified in the established charter, the IPTs shall have responsibility for the following functions:

a) Monitoring and reporting of Subsystem status and progress for both the Government and the Contractor

b) Joint identification, evaluation, management, and reporting of risk mitigation and cost reduction initiative efforts

c) Identification, collection, analysis, and reporting of appropriate metrics for measurement of cost/schedule control, engineering and production progress

d) Joint evaluation and management resolution of major issues associated with hardware and software engineering, production, integration, test, and Installation and Checkout (I&C) activities

e) Integration of appropriate cybersecurity measures in accordance with Navy instructions and Program Office direction.

e) Verification that the Contractor’s design disclosure process is providing data that is current, complete and accurate to third party developers

f) Joint evaluation and management of the Integrated Logistics Support (ILS) effort

g) Joint recommended approval of data items requiring approval under this contract

3.1.14 Contractor Facilities

The Contractor shall provide, operate, manage and maintain the hardware production, fabrication, assembly and test facilities required by the provisions of this SOW for the life of the contract. The production test facilities include Contractor sites used for fabrication, assembly, Incoming Inspection Tests, Production Inspection Test (PIT) and Production Reliability Acceptance Test (PRAT). PIT and PRAT require Contractor use of classified software. The Contractor shall provide appropriate classified test facilities.

The Contractor shall establish, administer, operate, and maintain shore-based facilities to support concurrent ACB development, integration, test, and maintenance activities (to include two development bays and one production bay for each unique hardware baseline on each distinct platform) required by the provisions of this SOW for the life of the contract.

The Contractor shall follow all applicable sections of the Contract Security Classification Specification (DD Form 254). In addition, facilities that process computer programs subject to Telecommunications Electronics Material Protected from Emanating Spurious Transmissions (TEMPEST) security requirements shall be subject to the requirements of OPNAVINST C5510.93D1 Government Implementation of National Policy on Control of Compromising Emanations.

3.1.15 Use of Contractor Facilities

The Contractor and its subcontractors shall provide and maintain secure office space with controlled access and related services for up to five technical representatives, authorized by the Government, on site at the Contractor’s facility beginning at contract award and continuing through the life of this contract. The Contractor and its subcontractors shall have mutual agreements which allow for similar office space access within their respective facilities. The related services at a minimum are:

a) Telephone services

b) Computer and network equipment to support analytical tasks, tracking tasks, word processing, and E-Mail services

c) Office equipment (e.g., desks, file cabinets)

d) Internet Services

e) Reproduction services (copying equipment) printing, copying, scanning

f) Classified material stowage containers

The Contractor shall make available to the technical representatives authorized by the Government all program data (e.g., working documents, databases, tracking systems, test results), including electronic access to computer files, pertaining to the Contractor and subcontractor activities in the performance of this contract.

3.1.16 Government-Furnished Property (GFP)

The Contractor shall manage any GFP received in accordance with FAR 52.245-1. The Contractor shall provide E- mail notification of receipt of any GFP. The Contractor shall report to the Government within ten (10) days of any GFP found damaged, malfunctioning, or otherwise unsuitable for use. The Contractor shall not modify or forward GFP without written approval from the COR or PCO. The Contractor shall comply with Government procedures for those GFP that are under Government Configuration Management.

The Contractor shall establish procedures for the adequate storage and maintenance of Government property. Records of all inspections and maintenance performed shall be maintained. The Contractor's procedures shall address the following:

a) Examination upon receipt, consistent with practicality, to detect damage in transit

b) Inspection for completeness, proper type and quantity

c) Methods for assurance of adequate storage conditions, proper handling, and protection from deterioration during storage

d) Testing, as required, to determine satisfactory operation

e) Identification and protection from improper use or disposition

These procedures shall be subject to review by the Government. GFP status and deficiency reports shall be delivered to the Government.

The Contractor shall present the Contractor’s procedures relating to GFP at the first scheduled Progress Meeting.

3.1.17 Program Security Requirements

The Contractor shall adhere to all security requirements imposed by the National Industrial Security Program Operating Manual (NISPOM), DoDD 5220.22, MIL-HDBK-1785 (DOD System Security Engineering Program Management Requirements), and the Contract Security Classification Specification (DD 254).

The Contractor shall maintain Information Security policies and procedures in accordance with appropriate sections of DODI 8500.2 ENCL 4, the Federal Information Processing Standards Publication (FIPS Publication (PUB)) 140-2, the NISPOM, and meet Defense System Security (DSS) certifications where applicable.

3.1.17.1 Cybersecurity

The Government intends to procure system(s) fully protected from loss of technological capability or denial of service by implementing appropriate cybersecurity protection in integrated systems involving software, such as the AN/SQQ-89(V) line of USW products. In support of achieving and maintaining a cybersecurity posture appropriate to the many constituent technologies and products associated with the USW combat systems, the Contractor shall be responsible to integrate cybersecurity as part of their delivered TI/ACB builds in accordance with Program Office direction and best industry practices.

3.1.17.2 Anti-Tamper

The Contractor shall support implementation of Anti-Tamper (AT) technologies and protocols to protect critical infrastructure in accordance with applicable AT Plans (e.g., TI-20 ACB-19 AT Concept Plan).

3.1.18 Transition Plan

The Contractor shall provide a transition plan to address execution of Statement of Work requirements within 90 days after contract award. This shall include assumptions, schedule, facility start-up, staffing, technical requirements, training, and documentation requirements. In addition, the Contractor shall include establishment of a software development and test site and the transition of the following GFP software system components:

· System Services Software

· Fire Control Software

· Hull Active Transmit Software

Technical Instructions will be issued to support the Government approved transition.

3.2 ENGINEERING

The Contractor shall provide engineering services to implement specified functionality and meet the defined requirements of the contract to achieve Surface Ship USW Systems performance.

Any requested changes or deviations to the contract or System Performance shall be submitted to PEO IWS 5 for approval. This may include software development required to 1) integrate third- party systems, equipment, computer programs and software components, 2) extend open architecture components, and 3) resolve software trouble reports.

As directed in specific Technical Instructions, requirements may include:

a) Continued Surface Ship USW system development in support of evolving improvements;

b) Support of PEO IWS 5 program planning and concept development to identify risk reduction activities to support Surface Ship USW system engineering and computer program development efforts;

c) Surface Ship USW system and software engineering efforts including requirements analysis, performance assessment, modeling and simulation, advanced concept initiatives, and product/process improvement;

d) Investigation of the applicability and synergy with existing/planned programs to ACB development efforts including interoperability with off-board sensors and joint systems;

e) Studies to define Surface Ship USW system TI/ACB content.

f) Facilitation of PEO IWS 5 sponsored SBIR topics.

g) Provide on-site Installation and Fleet In Service Support, both waterfront and at-sea, as directed by the Government for various USW combat systems.

h) Provide support to adequately resolve critical problems in fielded baselines.

Any problems that affect safety or the ability to operate (without a workaround) shall be directed to the Government within 24 hours. The Contractor shall submit a summary of field maintenance and repair services as a part of the quarterly Contractor's management report.

As specified in the Technical Instruction, the Contractor shall:

i. Receive and integrate GFP as provided by PEO IWS5. In some cases the Contractor may be required and directed to work directly with Original Equipment Manufacturer (OEM) developers.

ii. Design the TI computing environment(s) to support USW combat system ACB baseline in accordance with the TI/ACB schedule and fielding plan.

iii. Stand up and maintain sufficient infrastructure to support software development, test, certification, and post-fielding maintenance through the end of the contract for each TI for each platform configuration in accordance with the current TI/ACB schedule and fielding plan.

iv. The contractor shall provide training system software and infrastructure to meet Fleet training requirements and related system development.

v. Develop the ACB software baseline(s) to run on appropriate TI computing environment(s) in accordance with the TI/ACB schedule and fielding plan. Define, develop, maintain, and deliver Application Programming Interfaces (APIs) as required.

vi. Trace the Ship, Warfare System, and operational requirements to components to ensure that test cases are maintained for each requirement.

vii. Develop/modify tools, test cases, and test environments to test the capability performance to ensure conformance with Navy requirements.

viii. Develop and deliver a Software Development Plan (SDP) to support the development of key system software components.

ix. Modify and update software components and elements allocated to the Contractor as required to support the ACB baseline.

x. Develop and deliver software design documentation as source material for the Interactive Electronic Technical Manual (IETM).

xi. Conduct systems engineering and analysis on classified operational data at the secret level using approved personnel and facilities as authorized by the contract DD-254.

xii. Identify candidate improvements for system operational and/or performance improvements. CDRL

The Government will provide applicable USW Performance Specifications as GFP and will maintain CM of the Performance Specification. If the Contractor cannot meet some of the requirements of the Performance Specification, the Contractor shall request changes to the Performance Specification for Government approval through submission of Requests for Deviations (RFDs) and Requests for Waivers (RFWs). The Contractor shall receive Government approval prior to procurement or manufacturing of those items.

The Contractor shall develop the System Requirements Verification Matrix (SRVM) for each TI/ACB pair to ensure traceability between the test requirements and the Performance Specifications for applicable USW Product Environmental Test and Quality Assurance Requirements and applicable USW Design Constraints Documents.

The SRVM maps to the test verification and shall establish the minimum verification, validation, and acceptance criteria for the Surface Ship USW systems and shall include the requirements that the Contractor must comply with. These requirements include:

a. System-level requirements

b. End-to-End performance requirements

c. Functional Segment (FS) to FS interface requirements

d. Functional Segment performance requirements

The Contractor shall conduct detailed system engineering and design analyses of the proposed software and hardware system IAW the specifications included in individual Technical Instructions. Systems engineering analyses shall include but not be limited to the following:

a) Analysis to determine and evaluate reliability and maintainability of the Surface Ship USW system hardware and software in the Fleet

b) Evaluate Fleet problems, provide recommended solutions and implement enhancements when directed by Technical Instructions

c) Develop and code software to meet requirements and integrate GFP

d) Integrate system elements to successfully function as a complete combat system in a Naval warfare environment

e) Participate as a member of various working groups to identify and recommend interface changes required to implement the ACBs onto the TI hardware and deliver a fully integrated Surface Ship USW system

f) Development of ACBs and execution of unit, element, and system level test

g) Recommend changes to the system baselines as necessary

h) Perform factory acceptance testing

i) Implement Production Engineering Support

The Contractor will brief the Navy on identified problems and recommend solutions, including risk assessment and cost estimates. The Contractor shall document all engineering analyses.

3.2.1 Systems Engineering

The Contractor shall provide a System Engineering Management Plan (SEMP) for how development will progress with the incorporation of inputs from the various supporting working groups. The Contractor shall describe how the various technical inputs to the systems engineering effort will be integrated into a collaborative development environment.

3.2.1.1 Safety

The Contractor shall establish and maintain a System Safety Program to support efficient and effective achievement of overall system safety objectives using MIL-STD-882 as guidance.

3.2.1.2 Environmental Compliance

The Contractor shall ensure that work performed under the contract is performed in accordance with OPNAVINST 5090.1D.

Hazardous material that is required to be used in, supplied with, or required to support the system shall require approval from the program office. To facilitate approval the Contractor shall document the analysis conducted to evaluate alternatives in a Health Hazard Analysis Report and provide Material Safety Data Sheets (MSDS) (Occupational Safety and Health Administration (OSHA) Form 174).

3.2.1.3 Problem Reporting System

The Contractor shall establish a single Problem Report (PR) system for the identification, tracking, and resolution of all hardware, software and baseline documentation problems identified during system development, integration and testing. The PR System shall be used to track test documentation problems and technical manual errors. Data on the problems covered in this system shall be included with the Contractor’s Progress, Status and Management Report. The data within this PR system belongs to the government and shall be provided in a spreadsheet-compatible format.

3.2.1.4 Open Systems Architecture Approach

In satisfying the Government’s requirements, the following system architecture approach characteristics shall be utilized:

a) Open Architecture: The Contractor shall develop and maintain an architecture that incorporates appropriate considerations for reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b) Modular, Open Design: The Contractor shall develop an architecture that is layered and modular and uses COTS/NDI hardware, Operating Systems (OS), and middleware that utilize non-proprietary or non-vendor-unique, key Application Programming Interfaces (APIs). The Contractor’s design approach shall be applied to all subsystems and components. The Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated development environment throughout the term of the contract.

c) Modular Open Systems Approach (MOSA): The Contractor’s design approach shall produce a system that consists of hierarchical collections of software and hardware configuration items (components). These components shall be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach shall emphasize the selection of components that are available commercially or within the DOD, to avoid the need to redevelop products that already exist and that can be re-used.

As part of technical and design reviews, the Contractor shall, at a minimum:

i. Describe how the proposed system architecture meets the modular, open design goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

ii. Describe its rationale for the modularization choices made to generate the design.

iii. Provide rationale that explicitly addresses any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

iv. Provide rationale for maintaining continued access to cutting edge technologies and products from multiple suppliers.

v. Describe how it will mitigate the risks associated with technology obsolescence.

vi. Describe how it will avoid being locked into proprietary or vendor-unique technology, and reliance on a single source of supply over the life of the system.

vii. Describe how it will implement cybersecurity measures to maintain operability and protect critical technology in accordance with Program Office direction

3.2.1.5 Modeling, Simulation and Test Suites

The Contractor shall develop new, modify existing, document, maintain, and deliver system level models, simulations and test suites to support the validation and verification of the system requirements, design, and software in accordance with applicable DoD USD(AT&L) guidance documents detailed in Section 2 of this SOW. Test suites shall be designed to test required functionality of the system. These test suites must be able to test upon completion of the development of the Unified Modeling Language (UML), Extensible Markup Language (XML), and executable code. These test suites shall be placed under Configuration Management (CM). These suites must be able to support Independent Verification and Validation (IV&V), Developmental Test (DT) and Operational Test (OT). The Contractor shall support Verification, Validation, and Accreditation (VV&A) conducted by the Government for the test suites. Results of testing of each software build will be made available to project personnel.

The Contractor will report on modeling, simulation, and testing at reviews. The Contractor shall modify the Surface Ship USW computer program, develop, test and integrate the changes to interact or support the new ACB. The Contractor shall maintain applicable GFP Modeling and Simulation (M&S) capabilities and provide Performance Analysis in support of ACB design activities.

The Contractor shall:

a) Upgrade system Modeling & Simulation (M&S) tools to support the analysis of the new ACB’s multi- mission performance against threats and scenarios

b) Execute statistical performance runs of the ACB design against Compliance and Assessment cases

c) Analyze results for performance against key metrics as specified in the relevant Technical Instruction.

3.2.1.6 Quality Assurance

The Contractor shall implement and maintain a Quality Assurance (QA) program that meets program objectives during the performance of the contract. The Contractor shall develop and deliver the Quality Assurance Program Plan (QAPP) to the Government for review and approval.

At a minimum, the quality management process should include the following key QA activities:

a) Establishment of capable processes

b) Monitoring and control of critical processes and product variation

c) Establishment of mechanisms for feedback of field product performance

d) Implementation of an effective root cause analysis and corrective action system

e) Continuous process improvement.

3.2.1.7 System Security Requirements

The Contractor shall comply with Section 3.1.17.2 to protect critical program information in the Surface Ship USW systems produced under this contract, in accordance with DoDD 5200.47E, Anti-Tamper (AT) (4 Sep 2015). The Contractor shall work with the Government to ensure the ACB program is compliant with any approved AT Concept Plan(s) for Surface Ship USW systems.

The Contractor shall ensure success by coordinating the design of all system software in a manner that allows successful testing and certification of the system in accordance with Cybersecurity (CS) requirements. The Contractor shall establish and maintain a CS program to support the customer's system security certification and accreditation of Surface Ship USW systems to the DOD and Navy CS requirements. The Contractor shall work with the Government to ensure that the ACB program is compliant with any proposed cybersecurity solution set and that interface requirements are correctly implemented. The Contractor solutions shall satisfy all applicable data security requirements in DoDI 8500.01, Cybersecurity (14 Mar 2014) and DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) (12 Mar 2014). The Contractor shall provide solutions that will not result in vulnerabilities or combination of vulnerabilities causing the system to be assessed as high risk.

The contractor shall ensure that personnel performing cybersecurity functions obtain and maintain all certifications required for their position category. Refer to Appendix 3 of the current version of DOD 8570.01M, Information Assurance, for further guidance. The Contractor shall implement and apply safeguards such that information and resources maintain the appropriate level of confidentiality, integrity, availability, authentication, and non- repudiation based upon mission criticality, level of required cybersecurity and classification or sensitivity level of information entered, processed, stored, or transmitted for Surface Ship USW Systems. The Contractor shall safeguard information and information systems through the use of multi-disciplined defensive layers, as well as sound administrative and operational practices. The Contractor shall document its security engineering process in the PMP.

The Contractor shall manage and coordinate platform external interface tests with the Aegis Weapon System (AWS) or the Aegis Combat System (ACS) (non AWS) elements. The Contractor shall specify requirements for the simulation/stimulation tools needed to support the ACB test program, develop and deliver ACB computer program Build to support all shore site testing.

3.2.1.8 Studies/Analyses

The Contractor shall conduct studies and analyses to meet the requirements of the contract and achieve USW combat system performance. The Contractor shall document the results of special studies and analyses.

3.2.2 Software

3.2.2.1 Component Software Development Requirements

The Contractor shall be responsible for the design and development of the integrated USW components. The Contractor shall ensure successful integration of programs which control critical interfaces between USW software baselines and their appropriate sensors and external combat systems.

The Contractor shall deliver the Surface Ship USW system computer programs to the Navy as iterative deliveries and as a final system delivery after system level testing efforts. The Contractor shall provide evaluation of test results, investigation of noted discrepancies, and corrective actions to resolve problems. The Contractor shall use the UML to model the architecture of the software within each element. The Contractor shall develop an Interface Design Description (IDD) using the system model, plan transition from component IDDs to data models, and shall develop SDDs for each developed functional component using model outputs to replace legacy Computer Program Design Document (CPDD) for the changes required for the new ACB.

3.2.2.2 Software Requirements Specification

The Contractor shall update and maintain the Software Requirements Specifications (SRS) for any functional segment development allocated to the Contractor after Contract award.

3.2.2.3 Interface Requirement Specifications/Interface Design Description

The Contractor shall update and maintain the system level Interface Requirement Specifications (IRS) and Interface Design Description (IDD) for each functional component developed by the Contractor.

3.2.2.4 Data Design and Management

For all new and modified software the Contractor shall, as specified in the Technical Instructions:

a) Clearly define and describe all component and system data objects

b) Define and document all subsystem and Configuration Item (CI) level data objects to provide full functional, logical, and physical specifications

c) Identify processes for specifying the lowest level (i.e., subsystem or component) at and below which it intends to control and define “data” design by proprietary or vendor-unique standards and the impact of that upon its proposed logistics approach

d) Consider an overall Information Assurance (IA)/Cybersecurity strategy that implements IA/Cybersecurity processes in accordance with DoD Instruction 8500.2 and other IA requirements that are part of the Contract baseline when developing all data objects and architecture, including options to tag security levels of data objects

e) If applicable, select data objects from existing open or Government standards (DoD Core Architecture Data Model (CADM)) on the Defense Information Services Agency (DISA) web site, with an emphasis on enterprise-level interoperability. The Contractor shall describe how its selection of data object designs will maximize the ability of the system to easily accommodate technology insertion (both computing hardware and software) and facilitate the insertion of alternative or reusable modular system elements.

3.2.2.5 Software Product Specification

The Contractor shall develop and update a Software Product Specification (SPS) for each Computer Software Configuration Item (CSCI) which they have developed/modified for the integration baseline. The SPS shall contain and reference the executable software, source files, and software support information, including "as built" design information and compilation, build, and modification procedures for each CSCI developed/modified.

3.2.3 Hardware

The Contractor shall work in cooperation with the Hardware IPT to select a hardware baseline, which uses a common core GFP architecture to support the USN and FMS USW configurations. The Contractor shall develop, update and maintain a hardware functional, performance and interface requirements baseline and generate program- unique specifications for the Surface USW programs.

3.2.3.1 Hardware Requirements Definition

The Contractor shall develop, update and maintain functional, performance and interface requirements for hardware baselines and generate program-unique specifications for the Surface Ship USW hardware. As applicable, this hardware requirements definition shall address system security elements associated with paragraph 3.2.1.7.

3.2.3.2 Hardware Design

All Mission Critical Functions shall be implemented in Shock Grade A qualified cabinets. Non-Mission Critical functions may be implemented in either Grade A or Grade B shock qualified cabinets. The hardware baseline shall host the USN and FMS USW integrated software baselines. The Contractor shall be responsible for ensuring that USW combat system Environmental Test and Quality Assurance Requirements are met for the product baseline hardware configuration. The Contractor shall complete the systems engineering for the hardware design including participation in, execution of and reporting for Preliminary Design Review/Software Specification Review (PDR), Critical Design Review (CDR), and Production Readiness Review (PRR), or the functional equivalent within the USW ACB development process.

Subject to government approval, the Contractor shall specify materials and components to be incorporated into the system or subsystems including a listing of any hazardous materials or processes incorporated or used in the fabrication of the system or subsystems. The design analyses shall consist of detailed examinations of the design techniques and materials that the Contractor plans to use to meet the requirements of the specifications. The design analyses shall be specific on both the system and component levels. Any soldering shall be performed in accordance with ANSI/J-STD-001.

The Contractor shall implement a program to project the obsolescence of systems and components at final acceptance and beyond. The Contractor will provide the engineering resources to support the COTS technology surveys, identification of emergent obsolescence and Diminished Manufacturing Sources/Material Shortages (DMS/MS) issues and the selection, evaluation and regression testing of candidate replacement COTS components as well as the management of software licenses. As a part of the modernization of the Surface Ship USW system computing infrastructure, the Contractor shall design hardware changes for COTS refresh computing and network equipment, operating systems, and middleware to address obsolescence issues.

The Contractor shall develop and deliver engineering design data review information packages to the Government.

Materials and components to be incorporated in the system shall be specified by the government. Stress levels and safety factors, as appropriate, shall be identified for all mechanical and electrical parts. Methods and materials to be used to protect the components from the environment shall be identified using MIL-S-901D, MIL-STD-461F, MIL- HDBK-470 as guidance. In addition to the system hardware physical considerations, the design analyses shall evaluate the system concept in terms of operability, reliability, producibility, maintainability and supportability objectives using MIL- STD-1472F, MIL-HDBK-251 and MIL-HDBK-470 as guidance. The Contractor shall examine the design details and modify them, as necessary, to ensure that the system design will conform to established Navy precepts for minimum practical manning, personnel and training requirements.

The Contractor shall provide engineering drawings, parametric data, and technical system information required for PEO IWS5 to develop Installation Control Drawings (ICD) in accordance with MIL-D-23140D. Information shall include all system interface requirements, recommended cable types, cable running sheets, connector/backshell required and cable EMI category. Engineering drawings and data for each unit to include Unit name, Unit number, Wet Weight, Crated Weight, Cubical Content, Power Requirements, AC Voltage, Voltage Tolerance, Frequency Tolerance, Phase, Current, Power, Power Factor Lead/Lag, DC Voltage, Voltage, Heat Dissipation To Air, Heat Dissipation To Water, Relative Humidity, Base Plate Loading (Lbs./Sq. Ft), and Operating Temperature (Fahrenheit).