Draft SOW 4Apr25.docx

Statement of Work (SOW) Control Systems Technical Support Services

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles.

This requirement is for NSWCPD Subject Matter Experts (SME), which are responsible for the lifecycle engineering of the Hull, Mechanical & Engineering (HM&E) Control Systems and Networks associated with the Arleigh Burke Destroyer, LCS Freedom variant and America Class Amphibious Assault platforms.

1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied

1.0.3 Government/Contractor Relationship

1.0.3.1 The services to be delivered under this Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

1.0.3.2 The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

1.0.3.3 Contractor personnel under this Contract shall not engage in any of the inherently Governmental functions listed at FAR Sutbpart 7.5 or DFARS Subpart 207.5.

1.0.4 Employee Relationship:

1.0.4.1 The services to be performed under this Contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

1.0.4.2 Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

1.0.4.3 Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

1.0.4.4 It is the Contractor's, as well as the Government's, responsibility to monitor Contract activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

1.0.4.4.2 The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

1.1 BACKGROUND

1.1.1 Arleigh Burke Background: The United States Navy (USN) Arleigh Burke class of guided missile destroyers is a warship that entered service starting in 1988, hereafter, known in this document as DDG-51. Lockheed Martin is the sole manufacturer and the initial design agent of the Hull, Mechanical, & Electrical (HM&E) Machinery Control System (MCS) and the LM2500 Engine Controller (EC). USN began a modernization program starting in 2010, to provide a comprehensive mid-life upgrade to ensure the warship remains effective. Lockheed Martin was selected again as the sole manufacturer and design agent of the Modernized HM&E MCS and EC. The current hardware and software design pedigree is a reflection of the original Modernized HM&E MCS and EC.

1.1.2 LCS Freedom Variant Background: In the year 2011, Lockheed Martin began construction the third Littoral Combat Ship (LCS) Freedom vessel for the United States Navy, hereafter, known in this document as Freedom variant. As these vessels cross into the in-service phase of their lifecycle, specific support services are required to maintain their operational profile. The Navy currently has five ships of this class that are in-service.

1.1.3 LHA America Class Background: In the year 2016, USN began construction of the improvised version of the Wasp Class Amphibious Assault Ship, hereafter, known in this document as America Class. As these vessels cross into the in-service phase of their lifecycle, specific support services are required to maintain their operational profile. The Navy currently has one ship of this class that are in-service.

1.2 SCOPE OF WORK

This performance work statement will provide support for the overall engineering and life cycle efforts of NSWCPD Division 50 and 30. The desired support is comprised of engineering design, integration, test and evaluation, hardware/software/interface development and delivery, logistics product development and distribution, shipboard troubleshooting, obsolescence support, configuration management, and training systems.

These activities will be executed in support of the DDG-51, LCS Freedom variant, and America Class HM&E equipment, inclusive of associated control systems. This statement of work is written on the behalf of the PEO LCS Program Office, specifically targeting the Lockheed Martin Freedom variant of the LCS program; PMS 400D, PMS 407 and PMS 443 Program Offices that specifically target the DDG-51 Ship Class; along with PMS 377, PMS 321 and PMS 443 Program Offices that specifically target the LHA-8AF America Ship Class . This statement of work does not include support for the Littoral Combat Ship Mission Module program, planning services or planning yard services nor the Sustainment Execution Contract (SEC).

1.2.1 DDG-51 Scope

The Contractor shall provide following work products as specified at the Task Order Level that shall cover the following:

1.2.1.1 DDG-51 Labor

1.2.1.1.1 QTY (3) - Minor Hardware/Software Baseline Change (As Required)

1.2.1.1.2 QTY (3) - Major Software Baseline Change (As Required)

1.2.1.1.3 QTY (2) - Major Hardware Baseline Change (As Required)

1.2.1.1.4 QTY (5) - Major Hardware Baseline Change (As Required)

1.2.1.1.5 QTY (20) - Major Hardware Baseline Change (As Required)

1.2.1.2 DDG-51 Material

1.2.1.2.1 Year 1

None

1.2.1.2.2 Year 2

1.2.1.2.2.1 Qty (2) – MCS Simulation/Stimulation Test Equipment

1.2.1.2.2.2 Qty (2) – EC Simulation/Simulation Test Equipment

1.2.1.2.3 Year 3

1.2.1.2.3.1 Qty (6) – MCS Prototype Input/Output Circuit Card Assemblies

1.2.1.2.3.2 Qty (6) – EC Prototype Input/Output Circuit Card Assemblies

1.2.1.2.4 Year 4

1.2.1.2.4.1 Qty (1) – MCS DT&E System (UCC1, DIU2, DIU5)

1.2.1.2.4.2 Qty (1) – EC DT&E System

1.2.1.2.4.3 Qty (6) – MCS Prototype CPU Circuit Card Assemblies

1.2.1.2.4.4 Qty (2) – EC Prototype CPU Circuit Card Assemblies

1.2.1.2.4.5 Qty (2) – EC HMI Prototype CPU Circuit Card Assemblies

1.2.1.2.5 Year 5

1.2.1.2.5.1 Qty (1) – MCS Prototype System (UCC1, DIU2, DIU5)

1.2.1.2.5.2 Qty (1) – EC Prototype System

1.2.2 Freedom Variant Scope

The Contractor shall provide following support specified at the Task Order Level that shall cover the following:

1.2.2.1 Freedom Variant Labor

1.2.2.1.1 Minor Hardware/Software Baseline Change (As Required)

1.2.2.1.2 Major Software Baseline Change (As Required)

1.2.2.1.3 Annual Cybersecurity Monitoring/Remediation

1.2.2.2 Freedom Variant Material

1.2.2.2.1 Year 1

1.2.2.2.1.1 Qty (1) – MPCMS Control Software

1.2.2.2.1.2 Qty (1) – MPCMS Control Software Source Code Files

1.2.2.2.2 Year 2

1.2.2.2.2.1 Qty (1) – MPCMS Control Software

1.2.2.2.2.2 Qty (1) – MPCMS Control Software Source Code Files

1.2.2.2.3 Year 3

1.2.2.2.3.1 Qty (1) – MPCMS Control Software

1.2.2.2.3.2 Qty (1) – MPCMS Control Software Source Code Files

1.2.2.2.4 Year 4

1.2.2.2.4.1 Qty (1) – MPCMS Control Software

1.2.2.2.4.2 Qty (1) – MPCMS Control Software Source Code Files

1.2.2.2.5 Year 5

1.2.2.2.5.1 Qty (1) – MPCMS Control Software

1.2.2.2.5.2 Qty (1) – MPCMS Control Software Source Code Files

1.2.3 America Class Scope

The Contractor shall provide following support specified at the Task Order Level that shall cover the following:

1.2.3.1 America Variant Labor

1.2.3.1.1 Minor Hardware/Software Baseline Change (As Required)

1.2.3.1.2 Major Software Baseline Change (As Required)

1.2.3.1.3 Major Hardware Baseline Change(As Required)

1.2.3.1.4 Design Analysis

1.2.3.1.5 Qty (20) – Quarterly Cybersecurity Monitoring/Remediation

1.2.3.2 America Material

1.2.3.2.1 Year 1

None

1.2.3.2.2 Year 2

1.2.3.2.2.1 Qty (1) – MCS Simulation/Stimulation Test Equipment

1.2.3.2.2.2 Qty (1) – EC Simulation/Simulation Test Equipment

1.2.3.2.3 Year 3

1.2.3.2.3.1 Qty (6) – MCS Prototype Input/Output Circuit Card Assemblies

1.2.3.2.3.2 Qty (6) – EC Prototype Input/Output Circuit Card Assemblies

1.2.3.2.4 Year 4

1.2.3.2.4.1 Qty (1) – MCS DT&E System

1.2.3.2.4.2 Qty (1) – EC DT&E System

1.2.3.2.4.3 Qty (6) – MCS Prototype CPU Circuit Card Assemblies

1.2.3.2.4.4 Qty (2) – EC Prototype CPU Circuit Card Assemblies

1.2.3.2.4.5 Qty (2) – EC HMI Prototype CPU Circuit Card Assemblies

1.2.3.2.5 Year 5

1.2.3.2.5.1 Qty (1) – MCS Prototype System

1.2.3.2.5.2 Qty (1) – EC Prototype System

2.0 APPLICABLE DOCUMENTS

2.1 ISO/IEC/IEEE 12207 | Systems and Software Engineering – Software life cycle processes

2.2 ISO/IEC/IEEE 14764 | Software Engineering – Software life cycle processes – Maintenance

2.3 ISO/IEC/IEEE 15288 | Systems and Software Engineering – System life cycle processes

2.4 ISO/IEC/IEEE 15289 | Systems and Software Engineering – Content of Life-Cycle Information Items

2.5 ISO/IEC/IEEE 15939 | Systems and Software Engineering – Measurement process

2.6 ISO/IEC/IEEE 16085 | Systems and Software Engineering – Risk Management

2.7 ISO/IEC/IEEE 16326 | Systems and Software Engineering – Project Management

2.8 ISO/IEC/IEEE 24748-1 | Systems and Software Engineering – Part 1 – Guide for Life Cycle Management

2.9 ISO/IEC/IEEE 24748-2 | Systems and Software Engineering – Part 2 – Guide to Application of ISO 15288

2.10 ISO/IEC/IEEE 24748-3 | Systems and Software Engineering – Part 3 – Guide to Application of ISO 12207

2.11 ISO/IEC/IEEE 24748-4 | Systems and Software Engineering – Part 4 – Systems Engineering Planning

2.12 ISO/IEC/IEEE 24748-5 | Systems and Software Engineering – Part 5 – Software Development Planning

2.13 ISO/IEC/IEEE 24765 | Systems and Software Engineering – Vocabulary

2.14 ISO/IEC/IEEE 24774 | Systems and Software Engineering – Guidelines for Process Description

2.15 ISO/IEC/IEEE 26514 | Systems and Software Engineering – Requirements for Designers and Developers of User Documentation

2.16 ISO/IEC/IEEE 26515 | Systems and Software Engineering – Developing in Agile Environment

2.17 ISO/IEC/IEEE 26531 | Systems and Software Engineering – Content Management for Product Life Cycle, User and Service Management Documentation

2.18 ISO/IEC/IEEE 29119-1 | Systems and Software Engineering – SW Testing – Part 1 – Concepts & Definitions

2.19 ISO/IEC/IEEE 29119-2 | Systems and Software Engineering – SW Testing – Part 2 – Test Processes

2.20 ISO/IEC/IEEE 29119-3 | Systems and Software Engineering – SW Testing – Part 3 – Test Documentation

2.21 ISO/IEC/IEEE 29119-4 | Systems and Software Engineering – SW Testing – Part 4 – Test Techniques

2.22 ISO/IEC/IEEE 29119-5 | Systems and Software Engineering – SW Testing – Part 5 – Keyword-Driven Tests

2.23 ISO/IEC/IEEE 29148 | Systems and Software Engineering – Requirements Engineering

2.24 ISO/IEC/IEEE 42010 | Systems and Software Engineering – Architecture Description

2.25 IEC 60092-101 | Electrical Installations in Ships - Part 101: Definitions and General Requirements

2.26 IEEE Std 315 | Graphic Symbols for Electrical and Electronics Diagrams

2.27 IEEE Std 828 | Configuration Management in Systems and Software Engineering

2.28 IEEE Std 1012 | System, Software and Hardware Verification and Validation

2.29 IEEE Std 15288.1 | Application of Systems Engineering on Defense Programs

2.30 IEEE Std 15288.2 | Technical Review and Audits on Defense Programs

2.31 SAE EIA-649B | Configuration Management Standard

2.32 SAE ARP1834 | Fault/Failure Analysis for Digital Systems and Equipment

2.33 SAE AS9102 | Aerospace First Article Inspection Requirement

2.34 SAE JA1000-1 | Reliability Program Standard Implementation Guide, Appendix A, Method A10 and A32

2.35 ISO/ANSI/ASQC Q9001-2015 | Quality Management Systems – Requirements

2.36 ASME Y14.100 | Engineering Drawing Practices

2.37 ASTM F1166-07 | Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities

2.38 COMFLTFORCOMINST 4790.3 | Joint Fleet Forces Maintenance Manual (JFFM)

2.39 DoD Inst 8500.01 | Cybersecurity

2.40 DoD Inst 8510.01 | Risk Management Framework (RMF) for DOD Information Technology (IT)

2.41 DOD-STD-1399 | Section 301A: Ship Motion and Attitude

2.42 FAR 31.205-46 | Federal Acquisition Regulation, Travel Costs

2.43 FED-STD-595 C | Colors Used In Government Procurement

2.44 JTR | Joint Travel Regulations

2.45 L00041BSPC-2113-04093 | LCS FLIGHT 0 BUILD SPEC

2.46 MIL-DTL-901D | Shock Tests, H.I. (High-Impact) Shipboard Machinery, Equipment, and Systems, Requirements For

2.47 MIL-DTL-15024F | Plates, Tags, and Bands For Identification Of Equipment, General Specification For

2.48 MIL-DTL-15024F | Type E: Plates, Tags, and Bands For Identification Of Equipment, General Specification

2.49 MIL-HDBK-61A (SE) | Configuration Management Guidance

2.50 MIL-HDBK 263B | Electrostatic Discharge Control Handbook for Protection Of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices) (Metric)

2.51 MIL-HDBK 344A | Environmental Stress Screening of Electronic Equipment

2.52 MIL-HDBK-881C | Work breakdown Structures for Defense Material Items

2.53 MIL-HDBK 2164A | Environmental Stress Screening Process for Electronic Equipment

2.54 MIL-M-38510J | General Specifications for Microcircuits

2.55 MIL-M-43719 | Type 1 : Marking Materials and Markers, Adhesive, Elastomeric, Pigmented; General Specification

2.56 MIL-STD-100 | Engineering Drawing Practices

2.57 MIL-STD-129R | Military Marking for Shipment and Storage

2.58 MIL-STD-130N | Identification Marking Of U.S. Military Property

2.59 MIL-STD-167-1A | Mechanical Vibrations Of Shipboard Equipment (Type I - Environmental and Type II - Internally Excited)

2.60 MIL-STD-461F | Requirements For The Control Of Electromagnetic Interference Characteristics Of Subsystems and Equipment

2.61 MIL-STD-686C | Cable and Cord, Electrical; Identification Marking and Color Coding Of

2.62 MIL-STD-810G | Environmental Engineering Considerations and Laboratory Tests

2.63 MIL-STD-882E | Standard Practice System Safety

2.64 MIL-STD-883J | Test Method Standard Microcircuits

2.65 MIL-STD-1310H | Shipboard Bonding, Grounding, and Other Techniques For Electromagnetic Compatibility, Electromagnetic Pulse (Emp) Mitigation, and Safety

2.66 MIL-STD-1662 | Ordinance Alteration (ORDALT) Instructions, Preparation of

2.67 MIL-STD-1686C | Electrostatic Discharge Control Program for Protection Of Electrical and Electronic Parts, Assemblies And Equipment (Excluding Electrically Initiated Explosive Devices)

2.68 MIL-STD-3018 | Parts Management

2.69 MIL-STD-31000A | Technical Data Packages

2.70 NAVSEA Clarification letter SER 05P3-047, dtd 9 Apr 03, "CLARIFICATION OF MIL-S-901 SHOCK TEST REQUIREMENTS CONCERNING SHOCK QUALIFICATION OF CLASS I AND CLASS II EQUIPMENT”

2.71 NAVSEA Letter 55X/SH, Serial 87, dated 17 February 1984

2.72 NAVSEA S0420-AA-RAD-010 | Radiological Affairs Support, Program Manual

2.73 NAVSEAINST 3900.8A SER 03/011 20MAY05 | Human Systems Integration (HSI) Policy In Acquisition and Modernization

2.74 NAVSEAINST 5400.95 | Waterfront Engineering and Technical Authority Policy

2.75 NAVSEAINST 9400.2 | Implementation of Naval Sea Systems Command (NAVSEA) Afloat Information Assurance (IA) Governance and Guidance

2.76 NAVSEAINST 9491.1C | Location Of Approved Class Hi Shock Testing Facilities

2.77 NSWCPDINST 5100.1D | Occupational Safety and Health Instruction

2.78 NVR | ABS Guide for Building and Classing Naval Vessels, 2004

2.79 SECNAVINST 5210.8D | Department Of the Navy Records Management Program

2.80 International Standard EN 60529 | Degrees of Protection Provided by Enclosures

2.81 6320.3A | COMUSFLTFORCOM/COMPACFLT INSTRUCTION

2.82 T9074-AS-GIB-010/271 | NAVSEA Technical Publication : Requirements For Nondestructive Test Methods

2.83 TS9090-600 | NAVSEA technical specification

2.84 TS9090-400 | NAVSEA technical specification

2.85 TS9090-310 | NAVSEA technical specification

2.86 MIL-STD-3034A | Reliability Centered Maintenance Process

All commercial documents can be referenced at https//www.ihs.com.

All DoD documents can be referenced at https://www.assist.dla.mil.

The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

3.1 General

The Contractor shall design, fabricate, assemble, qualify, repair, test and deploy (if required) onto DDG-51, Freedom variant and America Class control system equipment to meet the requirements specified in the performance specification or requirements provided at Task Order Level. Sample DDG-51 MCS and EC Performance Specifications provided as Attachment A and Attachment C respectively. The DDG-51 control system equipment includes the Universal Control Console (UCC), Data Interface Unit (DIU) and Engine Controllers (EC) and Legacy Consoles, such as but not limited to the Electric Plant Control Console (EPCC), Propulsion/Auxiliary Control Console (PACC), Shaft Control Unit (SCU) and Engineering Officer of the Watch Console (EOOW). The Freedom variant control system includes Control Console (CC), Data Acquisition Unit (DAU) and Core Network Switch (CNS). The America Class control system includes all equipment considered part of Machinery Control System (MCS) and Engine Controller (EC). This includes, but is not limited to, machinery control system design and integration, engine controller system design, mechanical and electrical power interface requirements, network system interfaces, and design integration. The Contractor shall also provide a software model of the control system as specified in performance specification or requirements provided at Task Order Level. Unless indicated as provided by the Government, all assemblies, subassemblies, and components identified, or required for proper operation of the equipment, shall be furnished by the Contractor. The Contractor shall provide qualified personnel, materials, facilities, equipment, controls and control interfaces, test instrumentation, data collection and analysis, hardware, software, and services that support the product areas and applicable documents for the control system equipment.

Definitions:

Configuration 1: Flight I/II DDGs Configuration 2: Flight III DDGs Configuration 3: Flight IIA DDGs

3.1.1 The Contractor shall provide all plans, technical data, drawings, pass/fail criteria, procedures, methods and results to the Government (including Government ISEA) for approval in accordance with Contract Data Requirements Lists, Exhibits A, B, C, D, E, F, G, and H.

(Note: CDRLs cited herein are applicable to the identified SOW Section and related SOW Subsections that follow the identified SOW Section specified).

3.1.2 The Contractor shall be appraised at a CMMI maturity level three (3) or higher by a certified SEI appraiser and must utilize their CMMI processes in performance of this contract.

3.1.3 The Contractor shall utilize and maximize the use of the vocabulary defined in Reference 2.13 to articulate and develop documentation for the control system.

3.1.4 All work performed under this contract shall comply with applicable Federal, State, and local laws and regulations. The Contractor shall have all valid permits and licenses necessary prior to performing the associated scope of work. The Contractor shall maintain valid permits and licenses throughout the period of performance of this contract.

3.2 Project Management/Planning Engineering

3.2.1 System Engineering Management Plan (SEMP)

The Contractor shall develop and maintain the control system SEMP as specified in References 2.3, 2.7 and 2.11 that includes an event based Work Breakdown Structure (WBS), reflecting how the effort shall be executed. The WBS shall be developed by the Contractor in a manner that reflects the Contractor’s customary way of organizing commercial projects and the need to have a direct relationship between project events and WBS. The WBS shall include a person- hour and labor category allocation for each separately identified task. The SEMP shall include an Integrated Master Schedule (IMS) that reflects the event based WBS. The Contractor shall develop and maintain a WBS dictionary as specified in Reference 2.52. The schedule shall be maintained in Microsoft Project™ 2016 format and shall be made available to the Government electronically at regular intervals during the execution of the effort. The Government reserves the right to conduct an in-plant visit to the Contractor to review implementation of the Contractor’s schedule management system and to understand the methods the Contractor utilizes to determine progress. The intent of this in-plant visit(s) (business review(s)) is to ensure maximum visibility of the Contractor’s performance.

CDRLs | 3.2.1 | A003

3.2.2 Integrated Master Schedule (IMS)

The Contractor shall develop, implement, manage to, update, and maintain the control system Program Integrated Master Schedule (IMS) by logically networking detailed program activities. The IMS shall be maintained in Microsoft Project™ 2016 format. The IMS shall be consistent with schedule of the Government. All Contractor schedule information delivered or presented at program reviews shall originate from the IMS. The IMS shall be traceable to the Program Plan and shall contain all critical events, accomplishments, criteria, predecessors and successors, and their dependencies. The IMS shall include a schedule for all WBS efforts using a Gantt chart. The Contractor shall conduct critical path analyses of the tasks and report problem areas and corrective actions required to eliminate/reduce schedule impact. The Contractor shall quantify the risk and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The Contractor shall ensure schedule integration with its subcontractors and shall verify/ensure the validity of the subcontractor’s schedule data, including demonstrating effective methods for incorporating schedule data from subcontractors into the Contractor’s IMS.

CDRLs | 3.2.2 | A004

3.2.3 Decision Management Process

The Contractor shall establish, develop, manage and implement the control system Decision Management Process in accordance with the SEMP based upon the references listed in Section 2.11 and 2.12. The Contractor shall utilize the Design Decision Memorandums (DDM) to record rationales that inform key decisions made throughout the lifecycle phases of the control system during execution of the SEMP, SDP and FDP. The meaning of “key decisions” and the approach for providing the rationale shall be described in the SEMP. The Contractor shall enumerate, explain, and present traceability of decisions to the control system Requirements, performance specification or requirements provided at Task Order Level. The SEMP shall describe the Contractor’s decision management control process and the Government’s role in this process.

CDRLs | 3.2.3 | A005

3.2.4 Risk Management Plan (RMP)

The Contractor shall develop, manage and implement the control Risk Management process in accordance with the RMP based upon the reference listed in Section 2.6. The Contractor shall identify, manage, mitigate risks associated with the development of the control system equipment based upon the requirements as defined by the performance specification or requirements provided at Task Order Level and Contractor system, software, interface, test and facility requirements. The RMP shall identify Risks in accordance with Severity and Likelihood while providing Risk Mitigation Steps utilizing a waterfall approach. The RMP shall describe the Contractor’s risk management control process and the Government’s role in this process.

CDRLs | 3.2.4 | A006

3.2.5 Configuration Management Plan (CMP)

The Contractor shall develop, manage and implement the control system Configuration Management Process in accordance with the CMP based upon the references listed in Section 2.7. The Contractor shall control the configuration of the control system equipment based upon the requirements as defined by the performance specification or requirements provided at Task Order Level and Contractor system, software, interface, test and facility requirements. The CMP shall describe the Contractor’s configuration control process and the Government’s role in this process.

3.2.5.1 The Contractor shall control access to all configuration-controlled items. The Contractor shall allow only privileged users requiring access to the configuration controlled data to access the configuration-controlled data

3.2.5.2 The CMP shall address procedures for a Physical Configuration Audit (PCA) of the first production unit, Configuration Status Accounting (CSA) procedures and requirements outlined in Section 1.4.2. The CMP, PCA procedures, PCA data, CSA procedures, and CSA data shall be provided to the Government. The CSA procedures shall describe the Contractor’s method of ensuring that technical documentation, parts and components in INCOS (Installation & Check-Out Spares) and Onboard Repair Parts Kits match the configuration of the production units.

CDRLs | 3.2.5 | A007

3.2.6 Software Development Plan (SDP)

The Contractor shall develop, manage and implement the control system Software Development Process in accordance with the SDP that is based upon the references listed in Section 2.1 and 2.12. The SDP shall specify the entire software program and the performance characteristics of each Computer Software Configuration Item (CSCI). The Contractor shall allocate the control system equipment performance requirements into the CSCIs listed in the SDP. SDP shall include both a Software Configuration Management Plan (SCMP) and Software Quality Assurance Plan (SQAP), or utilize the Control System CMP and QAPP. The SDP shall describe the Contractor’s software development process and the Government’s role in this process.

CDRLs | 3.2.6 | A008

3.2.7 Firmware Development Plan (FDP)

The Contractor shall develop, manage and implement the control system Firmware Development Process similar to the control system Software Development Process, in accordance with the FDP that is based upon the references listed in Section 2.1 and 2.12. The FDP shall specify the entire firmware program and the performance characteristics to meet the functional requirements of the respective Hardware Configuration Items (HWCI) and Computer Software Configuration Items (CSCI). The Contractor shall allocate the control system performance requirements into the HWCIs listed in the FDP. FDP shall include both a Firmware Configuration Management Plan (FCMP) and the Firmware Quality Assurance Plan (FQAP) utilize the Control System CMP and QAPP. The FDP shall describe the Contractor’s firmware development process and the Government’s role in this process.

CDRLs | 3.2.7 | A009

3.2.8 Test and Evaluation Program Plan (TEPP)

The Contractor shall develop, manage and implement the control system Test and Evaluation Process in accordance with the TEPP that is based upon the references listed in Section 2.28. The TEPP shall describe the purpose, goals and scope of the Verification and Validation (V&V) effort, including waivers and deviations. The TEPP shall include all V&V efforts associated with System, Software, Hardware and Interface Level testing. It shall also defined the environment and relationships to the test tool and test facilities required to perform the V&V efforts. The TEPP shall describe the Contractor’s V&V process and the Government’s role in this process.

CDRLs | 3.2.8 | A010

3.2.9 Software Transition Plan (STrP)

The Contractor shall develop, manage and implement the control system Software Transition Process in accordance with the STrP that is based upon the references listed in Section 2.1 and 2.12. The STrP shall specify the migration and transition of the development and production environment for the CSCI from the Contractor to the Government. The STrP shall describe the Contractor’s software migration and transition process and the Government’s role in this process.

CDRLs | 3.2.9 | A011

3.2.10 Parts Management Plan (PMP)

The Contractor shall establish and maintain a Parts Management Program in accordance with Reference 2.68 for equipment delivered. This program will ensure that the use of parts meet the contractual requirements, reduce proliferation of parts within and across DOD weapons systems and equipment, through standardization, and enhance reliability and supportability to meet material readiness objectives, and reduce total-life-cycle costs. The Contractor shall describe how the parts management process is validated, how process improvements are incorporated, and how process variation is controlled. The Contractor’s plan shall also describe the Contractor’s processes to minimize impacts due to Diminishing Manufacturer Sources & Material Shortages (DMSMS). An Obsolescence Management Plan shall be included in the Parts Management Plan.

3.2.10.1 Contractor and subcontractor (where appropriate) participation in the System Obsolescence Working Group and Government’s Parts Engine Controller Obsolescence Management Integrated Product Team (IPT).

3.2.10.2 Describe procedures for identifying and controlling obsolete technologies and provide the lowest cost/lowest risk solutions to recognized obsolescence problems.

3.2.10.3 Support IPT in the analysis of this list and identify those items at high risk for obsolescence at Shop Replaceable Unit (SRU), LRU, and piece part levels. Support IPT reports and their findings and recommendations.

3.2.10.4 Use of a non-proprietary system for managing obsolescence, such as the Obsolescence Management Information System (OMIS) or Horizon, in coordination with IPT efforts.

CDRLs | 3.2.10 | A012, G005

3.2.11 Electrostatic Discharge (ESD) Control Program

The Contractor shall establish the control system ESD Control Program in accordance with References 2.50 and 2.67. This program shall be applicable to ESD sensitive parts listed in References 2.50 and 2.67. The program shall be applicable from contract award date. The program shall include all procured electrical/electronic equipment, parts, and assemblies that were certified and qualified using the Electrostatic Discharge Sensitivity (ESDS) classifications 1, 2, and 3 designators and testing requirements specified under MIL-M-38510J and MIL-STD-883J. ESDS equipment, parts, and assemblies shall be identified and supplied to the Government Agency.

CDRLs | 3.2.11 | A013

3.2.12 Quality Assurance Program Plan (QAPP)

The Contractor shall provide and maintain a quality program that, as a minimum, adheres to the requirements of Reference 2.35.

The Contractor shall provide and maintain a quality program acceptable to the Government for all supplies and services furnished. The quality program procedures, plans, data, and all other documentation that the quality program comprises shall be submitted to the Government for review. The QAPP shall be resubmitted any time major policy or process changes affect the scope of the contract. If the current QAPP has been approved, only changes to the plan need to be submitted along with the supporting documentation for review and approval by the Government prior to implementing the change. The Contractor shall require of sub-contractors a quality program achieving control of the quality of services and/or supplies provided consistent with the contract specifications and/or the intended use of the supplies/services. The Government reserves the right to disapprove the quality program or a portion thereof when it fails to meet the contractual requirements.

The Contractor’s and subcontractors’ quality programs shall be in accordance with the requirements of this contract and ANSI/ASQC Q9001- 2000, American National Standard, Quality Systems-Model for Quality Assurance in Design, Development, Production, Installation and Servicing as supplemented below:

Design Control (add to section 4.4 of ANSI/ASQC Q9001-2000, hereinafter Q9001). The requirements of section 4.4, “Design Control,” of ANSI/ASQC Q9001 apply to design work conducted under this contract.

Control of customer-supplied product (add to section 4.7 of Q9001). The Contractor shall report to the Government any Government-furnished property or material found damaged, malfunctioning, or otherwise unsuitable for use. In the event of damage or malfunction during or after installation, the Contractor shall determine and record probable root cause and necessity for withholding property or material from use. As used in Section 4.7, the term “material” includes and applies to Government furnished equipment to be installed in or furnished with the end item. The term “property” is Government equipment which is used in the fabrication or assembly of the end item, and which is not delivered as part of the end item.

Contractor Inspection, test and audit records (add to section 4.10.5 of Q9001). Inspection and test records shall, at a minimum, indicate the nature of the observations, number of observations made and the number and type of deficiencies found. Audit records shall include the scope of the audit, persons contacted, processes reviewed, checklists completed, nature and number of observations made, the number and type of findings, and corrective action taken. Data included in inspection, test and audit records shall be complete, legible and accurate, and shall be usable by the Contractor and the Government for trend analysis and to assess corrective action effectiveness.

Third party certification. Certification of a Contractor’s or sub-Contractor’s quality system by a third party auditing organization (other than the Contractor or sub-contractor) may be used to supplement the assessment of a Contractor’s or sub-contractor’s quality system, but is not required.

CDRLs | 3.2.12 | A014

3.2.13 Operational Concept Description (CONOPS)

The Contractor shall describe the control system in a high-level manner indicating the operational features that are to be provided without specifying design details in accordance with Reference 2.23. The CONOPS shall include the operational policies and constraints, description of proposed control system, modes of system operations, user classes and involved personnel and support environment.

CDRLs | 3.2.13 | A015

3.2.14 Technical Reviews/Meetings

The Contractor shall plan, conduct, and document Technical Reviews and Meetings held between the Government and the Contractor. The Contractor shall identify dates for the reviews in the SEMP and IMS. The Contractor and the Government shall develop agendas for meetings jointly. Electronic Copies of all presentation materials shall be made available to the Government for the purpose of documenting the meeting. The Contractor shall prepare Meeting Minutes which document all material presented, key discussions, decisions made, and any action items resulting from the meeting.

3.2.14.1 The Contractor shall participate in a post contract award conference at a site mutually agreed upon by the Contractor and the Government. The post award conference shall last no longer than one day and shall occur within the first two weeks of the contract. Scheduling and coordination of technical reviews shall be at Contractor’s facility unless otherwise determined at post contract award conference.

3.2.14.2 The Contractor shall support working groups such as government sponsored Failure Review Boards (FRB), meetings, and Integrated Product Team(s) (IPTs).

3.2.14.3 The Contractor shall plan and conduct formal technical reviews on matters as coordinated with the Government identified within the SEMP and based on Reference 2.30. The following Technical reviews shall be included throughout the development lifecycle of the control system:

3.2.14.3.1 System Requirements Review (SRR)

3.2.14.3.2 System Functional Review (SFR)

3.2.14.3.3 Software Specification Review (SSR)

3.2.14.3.4 Preliminary Design Review (PDR)

3.2.14.3.5 Critical Design Review (CDR)

3.2.14.3.6 Software Incremental Review (SWIR)

3.2.14.3.7 Test Readiness Review (TRR)

3.2.14.3.8 Production Readiness Review (PRR)

3.2.14.3.9 Final Configuration Audit (FCA)/System Verification Review (SVR)

3.2.14.3.10 Physical Configuration Audit (PCA)

3.2.14.4 The Contractor shall provide the Technical Review Information Package (TRIP) based on the entrance and exit criteria as identified in Reference 2.30. The Contractor shall plan to travel to and conduct all reviews meetings at the Philadelphia Naval Base government facility. The Contractor has the option to schedule Technical Manual In-Process Reviews and Provisioning Guidance Conference(s) (PGC) with the Government. The Contractor shall notify the Government of reviews with preliminary agenda topics, security considerations, locations, and times. The Contractor shall make available, in electronic format, the presentation material that is to be presented at the reviews and conferences cited in this provision. The material, including agenda, shall be made available at least two weeks in advance of the review and/or conference start.

CDRLs | 3.2.14 | A016, A017, A018, F003, F004, G001, G002

3.2.15 Engineering Change Proposal (ECP)

An Engineering Change Proposal (ECP), also referred to as a Design Change Notice in Attachment D, shall be used by the Contractor to define a proposed change to a configuration item. The ECP form to be used will be provided 30 days after contract award. The ECP shall describe the scope of the change and contain sufficient data to allow evaluation of the effect on technical performance, logistics support, interface considerations, and costs of the proposed change. Class 1 changes are subject to Government approval. The Contractor shall maintain the configuration definition established in the performance specification or requirements provided at Task Order Level.

3.2.15.1 The Contractor shall maintain and provide updates to all technical data that requires design changes and revisions resulting from form, fit, and function changes or added during the service life of the control system equipment provided by the Contractor.

CDRLs | 3.2.15 | A019

3.2.16 System Deficiency Reporting (SDR) Process

The Contractor shall establish, develop, manage and implement the control system SDR Process in accordance with the SEMP based upon the references listed in Section 2.11 and 2.12. The government identifies this as System Problem Improvement Resolution (SPIR) Process. The Contractor shall utilize SDR/SPIR to record issues and failures with requirements, design, development, testing and sustainment throughout the various lifecycle phases of the control system. The SDR/SPIR shall articulate and inform the severity of the issue, probability of the issue occurring along with the risk to the operational availability of the integrated control system. The Contractor shall enumerate, explain, and present traceability of SDR/SPIR to the control system Requirements, performance specification or requirements provided at Task Order Level. Each SDR/SPIR shall be tracked from discovery to resolution with a state of resolution that is articulated to the government. The SDR Process shall be incorporated within the SEMP. The SEMP shall describe the Contractor’s System Deficiency Process and the Government’s role in this process.

CDRLs | 3.6.7 | A020

3.2.17 Trip/Travel Report

The Contractor shall furnish, to the Government, a trip report upon travel, per task conducted for this contract or task order.

CDRLs | 3.2.17 | A021

3.2.18 Alteration Installation Team Quality Assurance Workbook The Contractor shall provide an Alteration Installation Team Quality Assurance Workbook for any hardware or software installation that is conducted on government sites that includes United States Naval vessels.

CDRLs | 3.2.18 | A022

3.2.19 Government Furnished Equipment (GFE) Inventory Report

The Contractor shall furnish, to the Government, a monthly inventory of all GFE Equipment stored and utilized at the Contractor Facility provided and procured as part of this contract.

CDRLs | 3.2.19 | A023

3.2.20 Contractual Shipping Documentation

The Contractor shall submit to the Government pertinent shipping information associated with equipment including artifacts that are delivered to the Government.

CDRLs | 3.2.20 | A024

3.2.21 Contractual Baseline Report

The Contractor shall submit to the Government a Contractual Baseline Report at PDR. Additionally, the Contractor shall submit a new Contractual Baseline Report to the Government within 14 days after a change has been made to the contractual baseline.

CDRLs | 3.2.21 | A025

3.2.22 List/Status of All Deliverables

The Contractor shall submit to the Government a monthly list and status of all CDRL(s) identified to be delivered at Task Order Level.

CDRLs | 3.2.22 | A026

3.2.23 Contractor Progress Reports

The Contractor shall submit a monthly Progress Report that reflects the financial, technical and schedule status of the effort. The Progress Report shall contain the following information:

3.2.23.1 Planned efforts

The Contractor shall provide a copy of the updated IMS. The Contractor shall provide a brief description of the work envisioned for the ensuing reporting period highlighting any changes to the schedule, the objectives of those efforts, and an estimate of man-hours associated with planned efforts. The Contractor shall identify any technical risks, technical challenges, and problems anticipated in the next reporting period.

3.2.23.2 Actual efforts

The Contractor shall provide a copy of the IMS to reflect work performed during the current reporting period. The Contractor shall maintain one schedule that shall be updated monthly for both planned and actual efforts. The Contractor shall detail work performed during the current reporting period. The Contractor shall maintain an action list for programmatic and technical items that arise during the course of the effort and a status of deliverable items, including CDRLs.

3.2.23.3 Reports shall include:

3.2.23.3.1 Latest copy of the IMS.

3.2.23.3.2 Technical activities planned for the current reporting period.

3.2.23.3.3 Technical activities accomplished.

3.2.23.3.4 Developments noting significant results.

3.2.23.3.5 Identification of major problems with impacts and recommended solutions.

3.2.23.3.6 Identification of deficiencies with impacts and recommended solutions.

3.2.23.3.7 Technical activities planned for the next reporting period.

CDRLs | 3.2.23 | A001

3.2.24 Contractor Personnel Roster

The Contractor shall submit a monthly Personnel Report that reflects the contractor personnel directly tasked to manage and develop the control system. Roles and Responsibilities of the contractor personnel shall be identified in the Personnel Report.

CDRLs | 3.2.24 | A002

3.2.25 Data Rights and Patent Rights

3.2.25.1 Unlimited Rights

Contractor shall provide the Government with Unlimited Rights for the control system software and technical data to be used, except for the commercial operating systems, in the event of contract award under this SOW

3.2.25.2 Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD (7017 List) The Government will be provided with the uncompiled source code and object code as required by the contract. The Government will have unlimited rights to use, modify, reproduce, release, perform, display, and disclose noncommercial Technical Data (TD), noncommercial Computer Software (CS), and noncommercial Computer Software Documentation (CSD) in accordance with the terms of the solicitation and Defense Federal Acquisition Regulations Supplement (DFARS) 252.227-7013 and DFARS 252.227-7014.

for Assertion Asserted Rights Category Name of Person Asserting Restrictions

3.2.25.3 Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD Previously Delivered to the Government (7028 List) The Government will have unlimited rights to use, modify, reproduce, release, perform, display, and disclose noncommercial Technical Data (TD), noncommercial Computer Software (CS), and noncommercial Computer Software Documentation (CSD) that the Contractor has previously delivered to, or is obligated to deliver to, the Government under any contract or subcontract, in accordance with the terms of the solicitation and Defense Federal Acquisition Regulations Supplement (DFARS) 252.227-7028.

for Assertion Asserted Rights Category Name of Person Asserting Restrictions

3.2.25.4 Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation – Government Use Restrictions The Government may use, modify, reproduce, release, perform display or disclose commercial technical data in accordance with the terms of the solicitation and DFARS 252.227-7015. Commercial computer software will be provided under the licenses customarily provided to the public, except to the extent such licenses are inconsistent with federal law.

for Assertion Asserted Rights Category Name of Person Asserting Restrictions

Microsoft Windows Operating System

3.2.25.4.1 Background Inventions – Identification and Licensing No rights to Background Inventions are required from the Contractor

3.2.26 Government Responsibilities

Additional information, beyond that included in this contract, shall be furnished by the government on an as needed and if available basis. The Contractor shall identify the need for additional information. Inability of the government to make available the requested information shall not be cause for the Contractor to depart from the requirements of this contract. The Government provides Government Furnished Information (GFI) in good faith; but if the Contractor finds any discrepancies with the GFI, it is the Contractor’s responsibility to notify the Government immediately.

3.3 Requirement Engineering

The Contractor shall develop, manage, and maintain the control system requirements processes and artifacts through the control system development lifecycle as identified at the task order level to meet the performance specification or requirements provided at Task Order Level in accordance with the References 2.15 and 2.23 All Cybersecurity Requirements shall be embedded within the various Requirement Classifications.

The Contractor shall enumerate, explain, and present traceability of requirements from the performance specification or requirements provided at Task Order Level to the design. The Contractor shall document verification of all requirements and reference other documents that verify specific requirements (e.g. reliability analysis).

3.3.1 Verification Cross Reference Matrix (VCRM)

The Contractor shall provide a Verification Cross Reference Matrix that shows bi-directional links from stakeholder requirements to the derived system requirements. The VCRM shall also depict the bi-directional linkage from the derived system requirements to the software requirements. The VCRM shall also contain the bi-directional links from the derived test requirements to either the derived system and/or software requirements. Lastly the VCRM shall allow the user to bi-directional links from the facility requirements to all other control system requirements. The VCRM shall be provided to the Government as DOORS 9.6 compatible database. An export file of the VCRM from DOORS into Microsoft EXCEL file format is required with each DOORS file delivery.