N00024-23-R-6211_A0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this Amendment, A0001, to RFP N00024-23-R-6211 is to:

1. Under Section C, Descriptions and Specif ications:

a. Update paragraph 2.2.1 to add “MIL-STD-882E, System Safety”

b. Update f irst sentence in paragraph 3.3.9 to “The Contractor shall establish and maintain a System Safety Program Plan (SSPP) (CDRL

A046) to support eff icient and effective achievement of overall system safety objectives using MIL-STD-882E and PMS435 SSMP as guidance.

2. Under Section F, Deliveries or Performance:

a. Update CLIN 0006 PoP to 01-AUG-2024 to 31-JUL-2034

3. Under Section L, Instructions, Conditions and Notices to Bidders:

a. Update paragraph 1.7.1 to address fold out pages

1. CONTRACT ID CODE PAGE OF PAGES

S 1 70

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 28-Aug-2023

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002423R6211

X 9B. DATED (SEE ITEM 11)

14-Aug-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

28-Aug-2023

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002423R6211

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

FOR

AN/BLQ-10 (Submarine Electronic Warfare System)

1.0 SCOPE

This Statement of Work (SOW) defines the efforts required to upgrade and modernize AN/BLQ-10, the Submarine

Electronic Warfare System. These upgrades will cover Technology Insertion/Advanced Processor Builds (TI/APB) cycles TI-26, TI-28, and TI-30. Efforts hereunder include program management, systems engineering, engineering, software development, logistics and supportability engineering, configuration management, hardware and software integration (including material procurement or fabrication, and integration of Government-Furnished Material

(GFM), as applicable), testing, evaluation, and installation. The AN/BLQ-10 is designated for all submarine classes except existing OHIO class submarines. Production units shall be built for VIRGINIA, COLUMBIA, LOS

ANGELES, and SEAWOLF Class submarines.

The work shall be performed as specified in the Contract Schedule and as identified in individual Delivery Orders and Technical Instructions, as applicable. This procurement includes the following:

Design, develop, test, and integrate upgraded AN/BLQ-10 for installation on new construction and modernization submarines. This task shall include the preparation of platform variants, including installation drawings, for new construction and modernization submarines.

Provide “end-to-end” system engineering development, software development, integration, testing, environmental qualification, and life cycle support for the AN/BLQ-10.

Provide production capabilities for the timely production of new construction and modernization variant

AN/BLQ-10 systems for delivery to modernization alteration installation teams and for delivery and installation on new construction ships.

The initial delivery of each platform variant shall include all baseline engineering documentation, product lists, logistics support products, curriculum and support materials, spares, and INCO (installation and checkout) as necessary to provide the “as developed” product support, including Contractor personnel to provide training onboard the submarines.

Support the management, oversight, and execution of evaluation plans and system level testing as part of the

Command, Control Communications, Computers, Combat, and Intelligence (C5I) system platform integration design/build team for all platform variants.

Define and depict the optimum balance of simulation and simulation equipment needed to execute subsystem level testing and integration.

Define the interface baseline, including all requirements necessary, to connect to the Imaging System, Carry

On Equipment, and the Submarine Warfare Federated Tactical System (SWFTS) network and share information.

Participate in the integration efforts, including technology refresh/insertion planning and validation testing and integrations across SWFTS boundaries. Transition new technologies and capabilities to production and integrate into future TI/APB baselines.

Support platform level INCO planning requirements, including participation in Installation Integrated Project

Teams, new construction and modernization planning meetings, and various reviews and working group meetings.

Develop source material for Logistics Data, Interactive Electronic Technical Manuals (IETM), Interactive

Courseware (ICW)/Computer Based Training (CBT) and Interactive Multimedia Instruction (IMI) using common authoring systems and formats to ensure efficient integration with SWFTS. This includes integrating source material as delivered by the interfacing shipboard-subsystems contractors for integration for a complete AN/BLQ-10 delivery.

Support installation, field integration, repair, and refurbishment efforts as required.

Procure spares/repair parts, technology refresh/insertion kits, pre-production/production hardware, engineering change kits, and associated hardware including spares.

Include cybersecurity considerations in system design and engineering and correctly implement cybersecurity measures and design characteristics in the AN/BLQ-10 system. Provide support to the Government for all tasks required to achieve cyber security certifications and obtain Authority to Operate for all installed systems.

1.1. Navy Organization

Program Executive Officer, Undersea Warfare System (PEO UWS) is the acquisition executive for this procurement. The Submarine Electromagnetic Systems Program Office (PMS435) is responsible for the acquisition, development, production, fleet introduction, and support of the AN/BLQ-10 for all classes of submarines and appropriate Joint Program Office efforts.

1.2. Program Background

In a joint collaborative development environment, the Submarine Combat Systems Program Office (PMS425) and

PEO IWS5 Advanced Science and Technology Office (ASTO) established a Combat Systems Research and

Development Model to facilitate the rapid transition of advanced science and technology products to the fleet in

Certified Operational Combat Systems. This concept was first instituted in acoustics systems with dramatic, successful results. A pre-requisite to achieving this success was the development of an open system architecture

Commercial-Off-The-Shelf-based “landing pad” to introduce advanced development products. Additionally, open business practices and processes in an Integrated Product and Process Development culture were formed to allow for streamlined cooperative development strategies and efficient transition activities to apply Advanced Development, APB product integration with baseline systems.

Following on the success of the acoustic systems program, Advanced Submarine Support Equipment Program

(ASSEP) was established to develop advanced submarine electronic warfare and image processing technologies.

Developing these technologies is critical to improving submarine operational effectiveness in the increasingly dense and sophisticated electromagnetic environment caused by the proliferation of complex radar, communications, and navigation equipment of potential adversaries. Specifically, improvements are necessary for submarine electronic warfare to be effective in supporting the following mission areas: Joint Littoral Warfare, Joint Surveillance, Space and Electronic Warfare, Intelligence Collection, Maritime Protection, and Joint Strike.

The Submarine Electronic Warfare program consists of the inboard AN/BLQ-10 being procured under this contract, as well as the outboard components being procured separately, such as the AN/BSD-4 Multifunction Modular Mast

(MMM), and other outboard devices as specified in the Performance Specification. AN/BLQ-10 shall have the flexibility to address rapid shifts in the threat environment, budget, capability requirements, and technology.

AN/BLQ-10 shall provide core tactical capabilities and hotel services for integration with national assets. When national assets are integrated into the AN/BLQ-10 under operational conditions, the AN/BLQ-10 system shall be operated at the same Top Secret (TS)/Sensitive Compartmented Information (SCI) level as the national assets. The

AN/BLQ-10 system then becomes a national asset, which allows for the rapid deployment of national asset capability with the use of software applications. The Contractor shall be required to support interface design, full system testing and troubleshooting, and repair of AN/BLQ-10 systems in a TS/SCI configuration.

The Contractor shall provide development of electronic warfare technologies and support integration of development by third party. Development of these new technologies as required by this contract will require the

Contractor to utilize real-world TS/SCI recorded data throughout the design, build, test, and acceptance stages. The

Contractor shall be required to include progressively new technologies in each Technology Insertion build.

1.3. The Collaborative Development Environment

A collaborative development environment among a consortium of the Contractor, Navy Program Office(s), Navy laboratories, academia, and other industry partners is necessary to ensure continued success of the AN/BLQ-10 program. In addition, support for the “Open Source Initiative” will allow for the efficient integration of improvements into AN/BLQ-10.

Specifically, during development of advanced submarine electronic warfare technologies, the Contractor shall collaborate with PMS435, ASSEP, IWS5, the SWFTS Systems Engineering (SE) Integrated Product Team (IPT), the Technology Insertion IPT (TI-IPT), and other organizations as necessary for all aspects of the APB and Carry

On Equipment. Advanced submarine electronic warfare technologies and developments include procurement of hardware, systems engineering, software development, testing, supportability, logistics products, training, program reviews, design reviews, management of baselines, and delivery, acceptance and field installation of the TI Upgrade kits across all platform variants.

1.4. Open Systems Architecture Approach

Naval Open Architecture is the confluence of business and technical practices yielding modular, interoperable systems that adhere to open standards with published interfaces. AN/BLQ-10 systems shall have an open system architecture and corresponding components. As part of this contract, the Contractor shall define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards. The Contractor shall develop, maintain, and use an Open System Management Plan to support this approach and shall demonstrate compliance with open systems architecture during all design reviews.

As part of an open system architecture approach, the Contractor shall identify to the Government all Commercial-

Off-the-Shelf/Non-developmental Item (COTS/NDI) components as defined in IEEE STD 610.12-1990, their functionality and proposed use in the system, and provide copies of license agreements related to the use of these components for Government approval prior to use.

In addition, the Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated digital (or development) environment (IDE) and the ability to download artifacts throughout the term of the contract. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes. The Contractor shall provide 30 calendar days’ advance notice of any events, tests, or activity that the Government identifies as a specific item of interest.

2.0 APPLICABLE DOCUMENTS

The Contractor shall always use the latest revision of the following specifications, standards, handbooks, and reference documents if marked mandatory in the table below. If a conflict exists between the stated and referenced requirements, the order of precedence shall be in accordance with FAR Clause 52.215-8.

2.1 Incorporation by Reference

All specifications, exhibits, drawings or other documents which are referenced in this contract, but are not attached hereto, are hereby incorporated by reference.

2.2 Issue of Documents

The following documents listed in the Department of Defense Index of Specification and Standards (DODISS) form a part of this SOW to the extent specified herein.

2.2.1 Government Documents

Document Number Document Title Mandatory

(Y/N)

AN/BLQ-10AB SEP AN/BLQ-10AB Systems Engineering Plan for

Electronic Warfare AN/BLQ-10A/B ACAT Level III

Y

COMFLTFORCOMINST 4790.3 Rev D

Change 1

Joint Fleet Maintenance Manual (JFMM) SHIPALT

Liaison Action Request (LAR) reporting procedures

N

DCID 6/3 Director of Central Intelligence Directive 6/3, Protecting SCI within Information Systems

Y

DoDM 5105.21 (Volume 1) DoD Manual: Sensitive Compartmented Information

(SCI) Administrative Security Manual:

Administration of Information and Information

Systems Security

Y

DoDM 5200.01 Vol 4 DoD Information Security Program: Control

Unclassified Information (CUI)

Y

DoD 5200.1-PH DoD Guide to Marking Classified Documents Y

DoDD 8140.01 Cyberspace Workforce Management Y

DoD-HDBK-292-1 (Navy) Training Materials Development N

DoDI 8320.04 Item Unique Identification (IUID) Standards for

Tangible Personal Property

Y

DoDI 8551.01 Ports, Protocols, and Services Management (PPSM) N

DoD 4151.22-M Reliability Centered Maintenance (RCM) Y

DoD 5200.2-R DoD Personnel Security Program Y

DoD 5220.22-M National Industrial Security Program Operating

Manual (NISPOM)

Y

DoD 8500.2 Information Assurance (IA) Implementation Program Y

DoDI 5000.02 Operation of the Adaptive Acquisition Framework Y

DoDI 5200.39 Critical Program Information (CPI) Identification and Protection within Research, Development, Test, and Evaluation (RDT&E)

Y

DoDI 5200.44 Chg 3 Protection of Mission Critical Functions to Achieve

Trusted Systems and Networks (TSN)

Y

DoDI 8500.01 Chg 1 Cybersecurity Y

DoDI 8510.01 Risk Management Framework for DoD Systems Y

DoDI 8523.01 Communications Security (COMSEC) Y

DoDM 5205.02M

DoD Operations Security Manual

DoD IMP-IMS-Guide Ver 0.9 Integrated Master Plan and Integrated Master

Schedule Preparation and Use Guide

Y

IPC/J-STD-001D Requirements for Soldered Electrical and Electronic

Assemblies

Y

MIL-D-23140D Drawings, Installation Control, for Electronic

Equipment

Y

MIL-DTL-15024/1B Set or Group Identification Plate Y

MIL-DTL-15024/4A Modification Identification Plate Y

MIL-DTL-15024G Plates and Tags for Identification of Equipment, General Specification for

Y

MIL-DTL-24784D Manuals, Technical: General Acquisition and

Development Requirements, General Specification for

Y

MIL-HDBK-189C Reliability Growth Management N

MIL-HDBK-251 Reliability/Design Thermal Applications N

MIL-HDBK-29612-5 Advanced Distributed Learning (ADL) Products and

Systems

MIL-HDBK-470A_NOTICE-2 Designing and Developing Maintainable Products and Systems Volume I

N

MIL-HDBK-502A Product Support Analysis N

MIL-P-15024 Military Specification: Plates, Tags, and Bands for

Identification of Equipment, General Specification for

Y

MIL-PRF-29612B_NOTICE-4 Training Data Products Y

MIL-DTL-901 Rev E Shock Tests, H. I. (High-Impact) Shipboard

Machinery, Equipment, and Systems, Requirements for

Y

MIL-STD 1472H Human Engineering Y

MIL-STD-130 Rev N_CHG-1 Identification Marking of U.S. Military Property Y

MIL-STD-464D Electromagnetic Environmental Effects

Requirements For Systems

Y

MIL-STD-108E Definitions Of And Basic Requirements For

Enclosures For Electronic Equipment

Y

MIL-HDBK-2036 Electronic Equipment Specifications, Preparation of Y

MIL-STD-740/1 Airborne Sound Measurements And Acceptance

Criteria Of Shipboard Equipment

Y

MIL-STD-1474E Noise Limits Y

MIL-STD-1399-300C Interface Standard for Shipboard Systems Y

MIL-STD-1605A Procedures for Conducting a Shipboard EMI Survey Y

MIL-STD-1629A Failure Modes, Effects, and Criticality Analysis Y

MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment

(Type1 Environmental and Type II-Internally

Excited)

Y

ANSI/ESD S20.20-2021 Protection of Electrical and Electronic Parts Y

MIL-STD-2042C Fiber Optic Topology Installation Standard Methods for Surface Ships and Submarines

Y

MIL-STD-2073-1E(4) Standard Practice for Military Packaging N

MIL-HDBK-2155 Failure Report, Analysis and Corrective Action

Taken

Y

MIL-STD-3018_CHG-2 Parts Management N

MIL-STD-3022-CHG-1 Documentation of Verification, Validation, and

Accreditation (VV&A) for Models and Simulations

Y

MIL-STD-31000B Technical Data Packages Y

MIL-STD-461G Requirements for the Control of Electromagnetic

Interference Characteristics of Subsystems and

Equipment

Y

MIL-STD-810H CHG-1 Environmental Engineering Considerations and

Laboratory Tests

Y

MIL-STD-881F Work Breakdown Structure for Defense Materiel

Items

N

PEO 435-SAFETY-SSMP PMS435 System Safety Management Plan (SSMP) Y

MIL-DTL-24643C Cables, Electric, Low Smoke Halogen-Free, for

Shipboard Use General Specification for

Y

MIL-HDBK-2165 DoD Testability Handbook for Systems and

Equipment

Y

MIL-HDBK-217F Reliability Prediction of Electronic Equipment Y

MIL-HDBK-454C General Guidelines for Electronic Equipment Y

MIL-STD-1839D Calibration and Measurement Requirements Y

MIL-STD-3034A Reliability-Centered Maintenance (RCM) Process Y

MIL-STD-38784B General Style and Format Requirements for

Technical Manuals

Y

MIL-STD-40051/1D DoD Standard Practice: Preparation of Digital

Technical Information for Interactive Electronic

Technical Manuals (IETMs)

Y

MIL-STD-740-2 Structure-borne Vibratory Acceleration

Measurements and Acceptance Critical of Shipboard

Equipment

Y

MIL-STD-792F DoD Manufacturing Process Standard: Identification

Marking Requirements for Special Purpose

Components

N

MIL-STD-882E System Safety Y

MIL-STD-961E(4) NOT 3 Defense and Program - Unique Specification Format and content

Y

MS No. 6310-081-015 Revision D SUBMEPP Submarine Maintenance Standard, -

Submarine Preservation

Y

NAS 411 National Aerospace Standard: Hazardous Materials

Management Program

N

Memo for DoN Deputy Chief

Information Officer

Navy Implementation of the Risk Management

Framework (RMF) for DoD Information Technology

(IT)

Y

NAVSEA 0924-062-0010, Revision C Submarine Safety (SUBSAFE) Certification Manual Y

NAVSEA 0948-LP-045-7010 Material Control Standard Y

NAVSEA 0948-LP-045-7010 Vol 1 Material Control Standard (Non-Nuclear) Y

NAVSEA Commander's Intent Memo NAVSEA Commander’s Intent Memo - NAVSEA

Commander’s Intent for Shipboard and Selected

Shore Control-Platform Information Technology

Systems Cyber Readiness Improvements

Y

NAVSEAINST 04790.004A Equipment Identification Code Y

NAVSEAINST 4720.006A Preliminary & Final Cost Estimates by Industrial

Activities for Ship Alterations

N

NAVSEA 0400-AD-URM-010/TUM,

CAN 1/A to Rev 06

Tag-out User’s Manual Y

NAVSEA 0901-LP-480-0002/Chapter

General Requirements for Piping Systems Y

NAVSEA 0902-LP-018-2010 General Overhaul Specification for Deep Diving

SSBN/SSN Submarines (DDGOS)

Y

NAVSEA 4720.15A Machinery Alterations (MACHALTS) o HM&E

Equipment and Systems

Y

NAVSEA 9400.2M NAVSEA PIT-Control System Cybersecurity

Implementation Manual

Y

NAVSEA S9070-AA-MME-

010/SSN/SSBN

Guidance Manual for Submarine Temporary

Alterations

Y

NAVSEA S9074-AQ-GIB-010/248 NAVSEA Technical Publication, Requirements for

Welding and Brazing Procedure and Performance

Qualification

Y

NAVSEA S9086-RK-STM-010 Naval Ships Technical Manual Chapter 505 Piping

Systems

Y

NAVSEA S9407-AB-HBK-010 Handbook of Shipboard Electromagnetic Shielding

Practices

Y

NAVSEA SE000-00-EIM-110 (0967-LP-

000-0110)

Electronics Installation and Maintenance Book, Installation Standards

Y

NAVSEA SL720-AA-MAN-010/020

Rev2

Fleet Modernization Program Management and

Operation Manual

Y

NAVSEA SS800-AG-MAN-010/P-9290 System Certification Procedures and Criteria Manual for Deep Submergence Systems

Y

NAVSEA Standard Item 009-04 Provide Quality System N

NAVSEA TS9090-310E 30022 Technical Specification Alternations to Ships

Accomplished by Alternation Installation Teams

(AIT)

Y

NAVSEAINST 4720.14D Temporary Alterations to Active Submarines Y

NAVSEAINST 5000.39 Acquisition and Management of Integrated Logistics

Support for Ships, Systems, and Equipment

Y

NISTIR 7622 Notional Supply Chain Risk Management Practices for Federal Information Systems

N

OPNAV-P-111-1-86 Navy Training Plan Manual Y

OPNAVINST S5513.8C - (05) ELINT, General Y

OPNAVINST S5513.8 – (69.4) AN/BLQ-10 Security Class Guide Y

OPNAVINST S5513.8C – (77) Cluster SNOOP Security Class Guide Y

PMS435-ESM-CMP-12-1 PMS435 Configuration Management Plan Y

PPD 802-6335704/6337449 Project Peculiar Documents for VA Class Shock

Testing

Y

PPD 802-6335704 Project Peculiar Documents for SEAWOLF Class

Shock Testing

Y

N/A PMS435 Program Protection Plan N

SECNAVINST 4440.34 Implementation with Item Unique Identification within the DON

Y

SL130-AD-MAN-010 PMS-425 Engineering Change Instruction (ECI) Development

Manual

Y

SWTFS Systems IA Baseline SWTFS Systems IA Baseline - SWTFS Systems

Information Assurance (IA) Baseline Requirement

Document

Y

Anti-Tamper (AT) Security Classification

Guide (SCG)

Anti-Tamper (AT) Security Classification Guide

(SCG)

Y

Department of the Navy (DON) Chief

Information Office (CIO) Acquisition

Information Assurance Strategy (AIAS)

Guidance

Department of the Navy (DON) Chief Information

Office (CIO) Acquisition Information Assurance

Strategy (AIAS) Guidance, http://www.doncio.navy.mil

2.2.2 Non-Government Documents

Document Number Document Title Mandatory

(Y/N)

ANSI/AIAA-R-100A-2001E Recommended Practice for Parts Management N

ANSI/NCSL Z540.3-2006 (R2013) American National Standard for Calibration –

Requirements for the Calibration of Measuring and

Testing Equipment

Y

ASME Y14.100 Engineering Drawing Practices Y

ASME Y14.35M Revision of Engineering Drawings and Associated

Documents

Y

ASME Y14.5M Dimensioning and Tolerancing Y

ASME Y14-24 Types of Application of Engineering Drawings Y

CNSSI No. 1253 Committee on National Security Systems Instruction

(CNSSI) No. 1253 Security Categorization and

Control Selection for National Security Systems

Y

EIA-632 Processes for Engineering a System Y

EIA-649C Configuration Management Standard Y

FED-STD-313E Material Safety Data, Transportation Data and

Disposal Data for Hazardous Materials Furnished to

Government Activities

Y

Intelligence Community Directive (ICD)

Number 503 (ICD 503)

Intelligence Community Information Technology

Systems Security Risk Management, Certification and Accreditation

Y

IEEE STD 1058-1998 Software Project Management Plan Y

IEEE STD 15288.1 IEEE Standard for Application of Systems

Engineering on Defense Programs

Y

IEEE STD 15288.2 IEEE Standard for Technical Reviews and Audits on

Defense Programs

Y

IEEE STD 610.12-1990 IEEE Standard Glossary of Software Engineering

Terminology

Y

IEEE/EIA 12207.0/1/2 Software life cycle processes; life cycle data;

implementation considerations

Y

IEEE/EIA-STD-12207.1, Section 5.2.1 Guide for Information Technology - Software Life

Cycle Processes - Life Cycle Data

Y

ISO 10012 Measurement Management Systems – Requirements for Measurement Processes and Measuring

Equipment

Y

ISO-9001 International Organization for Standardization (ISO)

Quality Management Systems – Requirements 9001

Y

National Fire Protection Association

(NFPA) Standard 51B;

Standard for Fire Prevention during Welding, Cutting and Other Hot Work

Y

NFPA Standard 312; Standard Fire Prevention of Vessels During Construction, Conversion, Repair and Lay-up

Y

NIST SP 800-30 Guide for Conducting Risk Assessments N

NIST SP 800-34 Rev 1 Contingency Planning Guide for Federal

Information Systems

N

NIST SP 800-53 Security and Privacy Controls for Federal

Information Systems and Organizations

Y

NIST SP 800-61 Rev 2 Computer Security Incident Handling Guide Y

SD-22 Diminishing Manufacturing Sources & Material

Shortages Guidebook

3.0 GENERAL REQUIREMENTS

The work required by this contract shall be performed in accordance with the AN/BLQ-10 System Performance

Specification (Attachment J-5) and this SOW. Unless stated otherwise, the work required by this section 3.0 of the

SOW is applicable to all requirements (engineering services and production) under this contract. This SOW contains the requirements applicable to the hardware and software upgrade and modernization of the AN/BLQ-10 Electronic

Warfare (EW) System for Technology Insertion (TI) cycles TI-26, TI-28, and TI-30. These upgrades and modernization requirements include the design, development, testing, systems and production engineering, technology insertion / refreshment, engineering services, field engineering services, and system support for the

AN/BLQ-10 lifecycle.

There are specific circumstances during all phases of this contract including design, development, integration and testing that will require personnel to be cleared for access to TS/SCI. The Contractor will need to support this

TS/SCI level configuration in all phases of this contract, design, development, integration, test, production, installation, and field support.

3.0.1 Waiver of Requirements

Notwithstanding the requirements of any of the clauses or provisions of this contract, if the Contractor discovers during performance of the work under this contract that the requirements of any of the clauses or provisions are in conflict with security instructions issued to the Contractor by the Contracting Officer, the Contractor shall notify the

Contracting Officer of the conflict. At such time, the Contracting Officer shall either (i) modify or rescind the conflicting security requirements or (ii) issue written instructions to the Contractor regarding compliance with the requirements of the conflicting clauses or provisions. Any waiver of compliance with the clauses or provisions of this contract issued by the Contracting Officer shall be in writing.

3.0.2 Security Clearance Requirements

In performance on this contract, the Contractor will:

Require to maintain a TS/SCI facility security clearance level. When national assets are integrated into the

AN/BLQ-10 Electronic Warfare System under operational conditions, the AN/BLQ-10 system as a whole becomes TS/SCI. The contractor will support interface design, full system testing and troubleshooting, and repair of AN/BLQ-10 systems in a TS/SCI configuration.

Require to maintain a level of safeguarding for classified information, material, and data at the TS/SCI security clearance level.

Require COMSEC to accommodate the use of secure communications and will be required to maintain a

COMSEC account for SIPRNET equipment, STE telephone equipment and associated keying material.

Require access to non-SCI since this contract relates to the development and integration of submarine stealth technology to counter the threat of potential adversaries. Contractor’s personnel may be exposed to

Non-SCI information material during troubleshooting operations of electronic warfare equipment aboard ship.

Require to have access to Controlled Unclassified Information (CUI) with developers and integrators, Receive, store, and generate classified information. The contractor will assist in modernizing systems that are classified. Techniques to modernize this equipment, testing of this equipment, email/written reports, and overall system performance could be classified. In this capacity, the contractor will generate and be in receipt of classified material.

Fabricate, modify, or store classified hardware: The contractor will fabricate and modify classified components in support of this contract and then store this hardware until completion of all requirements.

Access to Naval Nuclear Propulsion Information (NNPI).

Adhere to all security requirements imposed by the latest revised Contract Security Classification

Specification form DD254. Contractor personnel working under this contract shall maintain at least an active SECRET security clearance. Contractor key personnel working under this contract shall maintain at least an active TOP SECRET security clearance.

3.0.3 Location of Works

The preponderance of activity under this contract is expected to take place at the prime and sub-contractor (if applicable) facilities as reflected in the DD-254.

3.0.4 Level of Safeguarding for Classified Information / Material

Certain prime and sub-contractor facilities (if applicable), as reflected in the DD-254, shall safeguard information and material up to Secret in support of the AN/BLQ-10 systems Program

3.1 Contract Line Item Number (CLIN) Descriptions

3.1.1 CLINs 0001 and (if option is exercised) 1001: Engineering Support

The Contractor shall provide services of qualified engineers to meet the requirements of the contract and achieve the

AN/BLQ-10 System Performance Specification (Attachment J-5) and this SOW. Engineering support will be issued by Task Order and may be further specified in accordance with Section C text, NAVSEA C-242-H003, TECHNICAL INSTRUCTIONS. The general objective of these efforts shall be the common development, modernization, maintenance and technology upgrade of the undersea electronic warfare systems or components which meet the performance requirements of the various U.S. Navy platform missions, where commonality offers the greatest cost and technical benefits.

The Contractor shall provide qualified engineers to perform engineering technical services tasks related to AN/BLQ-

10 development, upgrade, technology insertions, or installation for all platform variants (VIRGINIA, COLUMBIA, LOS ANGELES, and SEAWOLF Class submarines). These services shall include, but are not limited to, software/hardware design, development, modification, integration and checkout, test and evaluation, training, repairs, installation and checkout, inspection, technical issues resolution, trade studies, engineering change development, documentation, logistics analyses, and troubleshooting. Technical support shall include software and hardware enhancements using emerging technologies, when feasible.

The Contractor shall provide qualified electrical/electronic, mechanical and software engineers and technicians where required for field engineering or maintenance repair and sustainment to support the fleet. Field engineering and maintenance support shall include on-site assistance to submarine platforms for Electronic Warfare System troubleshooting and repair. The Contractor shall provide engineering and technical services related to platform variant delivery, installation, and maintenance VIRGINIA, COLUMBIA, LOS ANGELES, and SEAWOLF Class submarines.

The Contractor shall provide scientists or engineers to conduct studies and analyses of the AN/BLQ-10

Performance. The Contractor shall document the results of special studies and analyses.

3.1.2 CLINs 0002 and (if option is exercised) 1002: Incidental Material and Travel Support for

Engineering Support

The Contractor shall provide incidental material or travel to meet the requirements of the contract and achieve the

AN/BLQ-10 System Performance Specification (Attachment J-5) and this SOW. The Contractor shall provide incidental materials and travel necessary for the completion of Delivery Orders (DOs) or Technical Instructions

(TIs) issued in accordance with the Section C text, NAVSEA C-242-H003, TECHNICAL INSTRUCTIONS within the Government’s estimated amount. The Contractor shall be reimbursed for actual, allowable, and allocable costs less any discounts taken, plus applicable burdens, incurred in the performance of these items.

In order to minimize travel costs, the Contractor and its subcontractors at all tiers shall comply with DoD Joint

Travel Regulations (JTR) in conducting travel of employees. In any instance in which recurring travel to one location for more than 180 days is planned for personnel at any tier, the Contractor shall obtain prior written approval from the Contracting Officer’s Representative (COR), and the request for approval shall include a cost comparison addressing permanent change of station and long-term temporary duty assignment (TDY).

(a) Travel time necessary for performance of such services shall be included in computing the man days of service.

When services are performed at sea and the engineer(s) is unable to leave the vessel when work is completed, the remaining time aboard the vessel shall be considered travel time for purposes of computing the man days of services. However, the Contractor shall be paid for no more than one man day of service per calendar day for each engineer while in travel status.

(b) Passports, visas, inoculations and other medical requirements necessary for performance of engineering services shall be at the sole responsibility and expense of the Contractor.

3.1.3 CLINs 0003, 0004, 0005 and (if options are exercised) 1003, 1004, and 1005: AN/BLQ-10 EW

Production Systems

The AN/BLQ-10 EW Systems Production requirements are specified in Section 4.0 of Section C.

3.1.4 CLIN 0006: Data Requirements

The data to be furnished hereunder shall be prepared and delivered in accordance with the Contract Data

Requirements List, DD Form 1423, Exhibit A attached hereto.

3.1.5 CLIN 0007: Technical Data / Upgrade License Rights (OPTION)

If exercised, the Contractor shall grant the corresponding Data Rights license for each item of Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) identified on Attachments J-7B, J-8B, J-

9B, and J-10B. Following option exercise, the Contractor shall remove or revise markings and legends and resubmit previously submitted Exhibit A CDRLs to be consistent with the rights furnished hereunder. In addition, the

Contractor shall deliver all future data submittals with markings and legends consistent with the rights furnished hereunder.

3.2 Integrated Program Management

The Contractor shall designate a Program Manager who shall have responsibility for all aspects of this contract and the authority to commit the Contractor to specific courses of action. The Contractor shall perform all administrative, technical, and financial management functions required to support this effort and shall maintain the status, including all technical activities, problems or deficiencies, and recommended solutions. The Contractor shall be responsible for those activities assigned to subcontractors, to ensure the delivery of all supplies and services specified in this contract. The deliverable for this work shall be the Contractor's Progress and Status Report (CDRL A001).

3.2.1 Contractor Performance Management System

The Contractor shall establish, maintain, and use in the performance of this Contract, an integrated performance management system. The Contractor’s shall include the following management processes and systems in the established integrated performance management system: 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 early indication of cost and schedule problems, and their relation to technical achievement. The deliverable for this work shall be included in the Integrated Program

Management Data and Analysis Report (CDRL A002).

3.2.2 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain the CWBS (CDRL A003) and the CWBS dictionary using MIL-STD-

881C for guidance. The CWBS shall be to the lowest level necessary to reach manageable units of functional tasks that reflect the work being performed while ensuring the correlation of these lower levels to the specification, contract line items, data items, and work statement tasks. 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 also deliver the raw accounting data from their accounting system of each TI-

26, TI-28, and TI-30 manufacturing lot, at the completion of that lot, in Enterprise Resource Planning (ERP)

Reports (CDRL A004). It shall include an additional field identifying each database record with the corresponding lowest WBS element that those costs were reported. The Contractor shall analyze the system requirements specified in the SOW and system specification and translate them into a structure representing the products and services that comprise the entire work effort under the Contract. The Contractor's team or organizational entity responsible for the systems engineering of the system prepares the technical elements of the extended Contract WBS. The Contractor, if necessary, shall update the CWBS during the execution of the Contract. Changes to the CWBS or associated definitions, at any reporting level, require approval of the Government.

3.2.3 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

The Contractor shall develop and maintain an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) using the DOD Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the Contract. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The IMP and IMS shall be included in the Integrated Program Management Data and Analysis Report (CDRL A002).

3.2.4 Post Award Conference (PAC)

The Contractor shall host and conduct a PAC with the Government within forty five (45) calendar days of contract award. The PAC shall be held no longer than two business days. The Contractor shall develop the PAC structure and agenda. Contractor shall make available read-ahead material and presentation material ten (10) calendar days prior to the PAC. The Contractor shall generate and record minutes, attendance list, and action items of the PAC, and produce copies of all information presented. The Conference shall be held at the Contractor’s facility.

Representatives from each major subcontractor on the Contractor's team shall attend. Minutes of the meetings shall be kept by the Contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and be distributed electronically. The deliverables for this work shall be Meeting Agenda (CDRL A005), and Report, Record of Meeting/Minutes

(CDRL A006).

The purpose of the PAC is as follows:

a) Review the Contract and Technical requirements

b) Discuss the roles and working relationships between the Contractor and the Government

c) Discuss the Contractor’s planned management effort and requirements verification process

d) Discuss required meetings, periodicity, and reporting requirements

e) Review the Contractor’s facility plans

f) Review the Contractor’s recommendations for AN/BLQ-10 EW System Integration and Test

g) Identify the Integrated Product Teams and their respective roles and responsibilities

h) Management and Contract Mechanics

1) Contract Administration

2) Team Introductions

3) Review GFI/GFP utilization plans

4) Integrated Baseline Review (IBR)

5) Quarterly Program Reviews (QPR)

6) Quarterly Financial Reviews (QFR)

i) Technical Discussions

1) Requirements Traceability overview

2) Configuration Management processes

3) Major Technical Risk Areas

4) Design Review execution and schedule

5) Configuration Management processes

3.2.5 Integrated Baseline Reviews (IBRs)

The Contractor shall host an IBR no later than 180 calendar days after contract award. The Contractor shall work with the Government to develop the IBR agenda. The Contractor shall make available read-ahead material and presentation material ten (10) calendar days prior to the IBR. The Contractor shall generate and record minutes, attendance list, and action items of the IBR, and produce copies of all information presented. The prime Contractor shall lead the IBRs, with active participation by the Government. The IBR shall be held at the Contractor’s facility and shall be no longer than two business days. The deliverables for this work shall be Design Review Information

Package (DRIP) (CDRL A007), Meeting Agenda (CDRL A005), and Report, Record of Meeting/Minutes (CDRL

A006).

Minimum IBR Entry Criteria

a) CWBS and CWBS Dictionary approved

b) Control Accounts established and Control Account Managers (CAMs) assigned

c) Initial IMS submitted in Integrated Program Management Data and Analysis Report (CDRL A002).

As determined by the COR, the Contractor shall conduct an IBR assessment for any major change to the contract, after the exercise of significant contract options, and/or the incorporation of major design modifications. The

Government will use IBRs throughout the life of the AN/BLQ-10 EW System program to facilitate and maintain mutual understanding of:

a) The scope of the Program Management Baseline (PMB) consistent with authorizing documents

b) Management control processes

c) Risks in the PMB associated with cost, schedules, and resources

d) Corrective actions where necessary

3.2.6 Progress Reporting

The Contractor shall prepare and deliver monthly Progress, Status, and Management Reports to provide status of all assigned tasks, report progress against milestones, and identify technical or schedule problem areas or risks along with recommendations for resolution Contractor's Progress and Status Report (CDRL A001). The Contractor shall provide monthly Contract Funds Status Report (CFSR) (CDRL A008). Reports shall be tailored to provide required Cost, Technical, and schedule information. The financial status shall include the Estimate at Completion

(EAC), 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.2.7 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

Contractor shall report subcontractor status in the Contractor's Progress and Status Report (CDRL A001).

3.2.8 Program Risk Analysis

The Contractor shall identify significant program issues and raise them to the Program Office so that they can be monitored and resolved. The Contractor shall perform a continuing analysis of program, technical, performance, cost and schedule risks following the AN/BLQ-10SEP -Systems Engineering Plan (SEP) for Electronic Warfare

(EW). Risks shall allow for the identification of both technical and non-technical risks, risk assessment, the development of appropriate actions and mitigations to effectively manage these risks, and tracking of potential impacts to cost, schedule, or performance impacts. 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 and Status Report [CDRL A001] and presented during

Program and Technical Reviews.

3.2.9 Program Reviews

The Contractor shall prepare agendas for Contractor-hosted meetings, program reviews, 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 shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and be distributed electronically. The deliverables for this work shall be Meeting Agenda

(CDRL A005), and Report, Record of Meeting/Minutes (CDRL A006). The Contractor shall conduct quarterly program reviews (QPR) and Quarterly Financial Review (QFR) every three (3) months, at its facility or alternate

Government facility for a period not to exceed one (1) day. An informal “read-ahead” brief shall be provided electronically to the Government 10 calendar days prior to the review.

3.2.9.1 Quarterly Program Review (QPR)

The purpose of the QPR is to ensure the Contractor’s approach and progresses are technically sound, meet the requirements, and are mutually understood and properly documented. At each QPR, the Contractor shall report status, issues, risks, and recommendations for the following items (at a minimum):

a) Schedule progress against the IMS (3 month history and 6 months projected)

b) Contract deliverables completed and projected (3 month history and 6 months projected)

c) Design and technical issues

d) Test and evaluation activities, plans, results

e) Logistics source data development and support efforts

f) Development activities -- completed and planned

g) Risk analysis and mitigation activities

h) Quality program status

i) Safety program status

j) GFP and GFI status

k) Proposed changes to the any baseline

l) Status of action items from previous reviews

m) Hazardous material management efforts

n) Configuration management activities

o) Production and Manufacturing readiness status

p) Efforts authorized under Technical Instructions

q) Reliability and maintainability

r) Hardware and software engineering

3.2.9.2 Quarterly Financial Review (QFR)

The purpose of the QFR is to ensure the Contractor has adequate financial resources and planning to execute the contract. At each QFR, the Contractor shall report status of the following (at a minimum):

a) Cost/Schedule performance and variances against plan

b) Financial projection/actual (3 month history, 6 month future)

c) Risk analysis and mitigation activities

d) Status of action items from previous reviews

3.2.10 Design Disclosure, Intellectual Property and Data Rights

The Contractor shall establish and maintain a process that shall provide ‘early and often’ design disclosure directly to third party developers via electronic access to in-process design documentation and computer software. The

Contractor shall support an Open Source Initiative with other participants within the Shipboard Combat Systems

Development community. 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 each Associate Contractor Agreement and copies of all written communication between the Contractor and the third party developers that is pertinent to this contract as a

Technical Information Report (CDRL A030). 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.

3.2.11 Data Management

The Contractor shall manage the development and use of data under this contract so as to afford the Government visibility of all data.

The Contractor shall maintain Contract Data Status for recording, planning, scheduling, and reporting the status of program data requirements including electronic mail transmittals; and maintain a list of all Contractor and subcontractor data generated in support of this contract.