RFP N64498-24-R-4016 Amendment 0002.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 is to:

1) Provided updates to Section C Statement of Work. Section 3.16.13 update to Quality Assurance reference ASQ/ANSI/ISO 9001:2015.

2) Fill in of clause 52.246-11 HIGHER-LEVEL-CONTRACT QUALITY REQUIREMENT (DEC 2014).

3) Update of C-209-H001 (CONTRACTOR TESTING) to APR 2024 version.

4) Update of Section L Element 1 D Softw are Development Plan to include Clause references.

5) Update of Section M Element 1D Softw are Devleopment Plan to icnlude Clause reference.

6) Update of Section M.2 RELATIVE IMPORTANCE OF EVALUATION FACTORS.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 94

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

16C. DATE SIGNED

BY 15-Jul-2024

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 N6449824R4016

X 9B. DATED (SEE ITEM 11)

01-Jul-2024

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 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

08-Jul-2024

CODE

NAVAL SURFACE WARFARE CENTER PHILA

CODE 0241, EMILY-REBECCA SIMPSON

EMILY-REBECCA.SIMPSON.CIV@US.NAVY.MIL

5001 SOUTH BROAD STREET

PHILADELPHIA PA 19112

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6449824R4016

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been added by full text:

C-209-H001 FIRST ARTICLE (CONTRACTOR TESTING) (NAVSEA) (APR 2024)

(a) The First Article shall conform in every respect to the requirements of this contract. The First Article shall be manufactured with tools, materials, and methods which are the same as the tools, material and methods which will be used to manufacture the production units. All items delivered under the contract shall be manufactured under the same conditions and quality established by the First Article. Any changes to tools, material, or methods after the first article approval shall be documented by the contractor and approved by the Contracting Officer before they are used.

(b) The Contractor shall make a record of all data obtained during such tests in a form similar to the guidance provided in MIL-HDBK-831A dated 25 June 2013.

(c) Pursuant to paragraph (e) of the clause entitled "First Article Approval--Contractor Testing" (FAR 52.209-3), the First Article shall not be delivered as part of the production quantity.

(End of Text)

The following have been modified:

STATEMENT OF WORK

Statement of Work (SOW) for DDG-Modernization (DDG-M) Repair Station Console (RSC)

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 both NSWCPD Code 226 and NSWCPD Code 223, which is responsible for DDG Modernization and DDG Ship Construction, Navy (SCN) respectively.

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 Subpart 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:

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

1.1 BACKGROUND

Naval Surface Warfare Center - Philadelphia Division (NSWCPD) Code 551, 552, and 554 are the Machinery Controls Systems (MCS) branches for the USS ARLEIGH BURKE Class (DDG

51) guided missile destroyer. Current programs under Code 554’s responsibility include the

Procurement of the Repair Station Console (RSC) hardware in support of new construction, modernization, and technical refresh efforts.

1.2 SCOPE OF WORK The Contractor shall provide engineering and technical services required for the design, development, fabrication, test, repair, delivery and fleet implementation of Repair Station Console (RSC).

2.0 APPLICABLE DOCUMENTS

Navy Issuances https://www.secnav.navy.mil/doni/default.aspx

DOD Issuances https://www.defense.gov/Resources/Forms-Directives-Instructions/

NAVSEAINST Library https://www.navsea.navy.mil/Resources/Instructions/

Commercial Issuances https://www.secnav.navy.mil/doni/default.aspx

2.1.1 ISO/IEC/IEEE 15289:2019, Second Edition: Systems and Software engineering – Content of life-cycle information items (documentation), section 10

2.1.2 MIL HDBK-61A (SE): Configuration Management Guidance

2.1.3 SAE EIA-649B: National Consensus Standard for Configuration Management

2.1.4 MIL-STD-882E

2.1.5 NAVSEAINST 3900.8A SER 03/011 20MAY05

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

2.1.7 ANSI/ASQC Q9001-2000

2.1.8 MIL-STD-1686C

2.1.9 MIL-HDBK 263B

2.1.10 MIL-M-38510J: Microcircuits

2.1.11 MIL-STD-883J: Microcircuits

2.1.12 SAE JA1000-1, Appendix A, Method A10 and A32.

2.1.13 MIL-STD-881C: Work breakdown

2.1.14 NAVSEAINST 9491.1C

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

2.1.16 MIL-DTL-901E

2.1.17 MIL-STD-167-1A

2.1.18 MIL-STD-461G

2.1.19 MIL-STD-810G(1)

2.1.20 DOD-STD-1399, Section 301A: Ship Motion and Attitude

2.1.21 IEC 60092-101

2.1.22 MIL-HDBK 344A: Environmental Stress Screening of Electronic Equipment

2.1.23 MIL-HDBK 2164A: Environmental Stress Screening Process Improvement Study

2.1.24 FED-STD-595C

2.1.25 MIL-STD-686C

2.1.26 MIL-STD-130N

2.1.27 MIL-DTL-15024F Type E

2.1.28 MIL-M-43719 Type 1

2.1.29 MIL-STD-1310H

2.1.30 MIL-DTL-15024F

2.1.31 NAVSEA Technical Publication T9074-AS-GIB-010/271

2.1.32 NAVSEA LTR 9072 Ser 05P3/047 of 9 April 2003.

2.1.33 MIL-STD-1474E: Shipboard Equipment Noise

2.1.34 MIL-STD-31000A

2.1.35 Defense Federal Acquisition Regulation Supplement – 30 November 2015

2.1.36 MIL-STD-1399, Section 300B

2.1.37 NAVSEA LTR 9072 Ser 05P/411 of 06 December 2019

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

3.0 REQUIREMENTS

3.1 The Contractor shall design, fabricate, assemble and test Repair Station Consoles (RSC) to meet the performance requirements specified in the DDG-M RSC Performance Specification provided in Attachment A. 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 RSC. This includes, but is not limited to, machinery control system design and integration, mechanical and electrical power interface requirements, network systems, and design integration.

3.1.1 QUALIFICATION SET - A Qualification Set shall consist of the following components and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M RSC Performance Specification:

One (1) RSC Panel PC (including display(s), computer/processor, internal speaker, and data storage device) One (1) Fuel Oil Lab Panel PC (FOLPC) (including display, touchscreen capability, computer/processor, internal speaker, and data storage device) One (1) integrated keyboard/trackball device One (1) Un-Interruptible Power Supply (UPS) One (1) display configuration:

Configuration 1: 19” (minimum) LCD Flat Panel Display + 40” (minimum)

LCD Panel Display (separate mounting for each) One (1) network based printer External cabling for power: UPS to additional display , UPS to Panel PC, Panel PC to integrated keyboard/trackball device, and ship’s power to printer External cabling for signal/data: Panel PC to additional display, Panel PC to integrated keyboard/trackball device, Panel PC to UPS, and Gigabit Ethernet

Data Multiplex System (GEDMS) to printer One (1) license (with installation media) for the latest release of the Windows

IoT Enterprise LTSC (64-bit) Operating System.

Operating System should be installed, along with all necessary firmware.

All required drivers and COTS software licenses with installation media

3.1.1.1 The Contractor shall also provide a copy of the full development environment capable of compiling all Contractor developed software in the form of a fully loaded COTS desktop PC or laptop PC. This PC shall be a one-time delivery and shall be delivered as part of the Qualification Set CLIN.

3.1.2 SHIPSET CLIN- A Shipset set shall consist of the following components and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M RSC Performance Specification:

Seven (7) RSC Panel PC (s) (including display(s), computer/processor, internal speaker, and data storage device)

One (1) Fuel Oil Lab Panel PC (FOLPC) (including display, touchscreen capability, computer/processor, internal speaker, and data storage device)

Eight (8) integrated keyboard/trackball devices Seven (7) Un-Interruptible Power Supplies (UPS) Three (3) display configurations:

Configuration 1: 19” (minimum) LCD Flat Panel Display + 40” (minimum) LCD Panel Display (separate mounting for each)

Configuration 2: 19” (minimum), LCD Flat Panel Display + 19” (minimum) LCD Flat Panel Display. (separate mounting for each)

Configuration 3: 19” (minimum) LCD Panel Display Configuration 1: Quantity two (2) Configuration 2: Quantity three (3) Configuration 3: Quantity three (3) One (1) network based printer External cabling for power: Panel UPS to additional display, UPS to Panel

PC, Panel PC to integrated keyboard/trackball device, and ship’s power to printer

External cabling for signal/data: Panel PC to additional display, Panel PC to integrated keyboard/trackball device, Panel PC to UPS, and GEDMS to printer

All required drivers and COTS software licenses with installation media One (1) license (with installation media) for the latest release of the Windows

IoT Enterprise LTSC (64-bit) Operating System.

Operating System should be installed, along with all necessary firmware

3.1.3 INCO I CLINs - An INCO I (Installation & Check-out) Initial Kit shall consist of the following components and subsystems, at a minimum:

Two (2) RSC Panel PC(s) (including display, computer/processor, internal

One (1) Fuel Oil Lab Panel PC (FOLPC) (including display, touchscreen capability, computer/processor, internal speaker, and data storage device) Two (2) 19” LCD Flat Panel Display(s) One (1) solid state drive Two (2) Un-Interruptible Power Supplies (UPS) Two (2) UPS Battery Pack(s) Two (2) keyboard/trackball device(s) Two (2) 40” (minimum) LCD Panel Display (separate mounting for each) One (1) network based printer Three (3) licenses (with installation media) for the latest release of the

Windows IoT Enterprise LTSC (64-bit) Operating System.

3.1.4 INCO R CLINs -An INCO R (Installation & Check-out) Replenishment Kit shall consist of the following components and subsystems, at a minimum:

One (1) RSC Panel PC(s) (including display, computer/processor, internal speaker, and data storage device) One (1) 19” LCD Flat Panel Display(s) One (1) solid state drive One (1) Un-Interruptible Power Supplies (UPS) One (1) UPS Battery Pack(s) One (1) keyboard/trackball device(s) One (1) licenses (with installation media) for the latest release of the Windows

IoT Enterprise LTSC (64-bit) Operating System.

3.1.5 OBRP CLINs - An OBRP (Onboard Repair Parts) Kit shall consist of the following components and subsystems, at a minimum:

One (1) RSC Panel PC (included display, computer/processor, internal

One (1) keyboard/trackball device One (1) 19” LCD Flat Panel Display One (1) license (with installation media) for the latest release of the Windows

IoT Enterprise LTSC (64-bit) Operating System.

3.1.6 SUPPORT SERVICES CLIN

This CLIN shall include support services described in sections 3.1.6.1 through 3.1.6.15 below.

3.1.6.1 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components

3.1.6.1.1 The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor may recommend a solution to include the impact on the contract price and delivery. The contractor shall not initiate any item redesign or incur any additional costs without the express, written authorization of the contracting officer.

3.1.6.2 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS)

Contract Requirements

3.1.6.2.1 Parts Management Plan. The Contractor shall utilize a previously developed, Government approved, in-house process or shall develop and deliver, for the government’s approval, a Parts Management Plan.

The plan shall detail the process to address and mitigate obsolescence/DMSMS issues. This plan shall address the following:

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

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

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.

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

Reference CDRL: A071

3.1.6.3 Product Selection Supportability Analysis: Contractor shall provide an analysis discussing the supportability of the proposed system over a ten year period. Analysis shall discuss supportability at the board level. Example: Processor input/output, video, digital interface etc. The following shall be addressed:

Commercial lifespan, availability, and market usage for the product line and products within.

Identification of parts/products unique to proposed system at the COTS board level or component level for designed boards.

Commonality with other known Navy or military applications employing the products to be used in proposed system.

Parts/technologies at risk of obsolescence within ten years. This shall be to the COTS board level or component level for designed boards.

Reference CDRL: A037

3.1.6.4 Technology Refresh Analysis: Contractor shall provide an analysis in the form of a plan for technology refresh of the proposed system. This shall be based on Product Supportability Analysis and requirements to mitigate obsolescence/supportability issues but using a twenty year timeframe. Analysis shall include:

Predicted schedule for required refresh(s), identified as a unique Refresh configuration (TR 1, TR 2…). This schedule shall be overlaid on proposed production schedule of baseline configuration.

Discussion of the level of hardware and software changes required for each technical refresh.

Required milestones to meet proposed technical refresh i.e. life of type buys, bridge buys, recover/refurbish assets removed as part of technical refresh installs to support remaining baselines etc.

ILS considerations such as Training or Technical documentation that may be a significant cost driver as a result of Technical refresh.

Reference CDRL: A038

3.1.6.5 INDENTURED PARTS LIST/INTERCHANGEABLE PARTS LIST. The Contractor shall develop and deliver an indentured parts list of all system unique components, and electronic or electromechanical equipment baselines to the piece part level with corresponding manufacturing part numbers in Excel spreadsheet electronic format.

3.1.6.5.1 The Contractor shall prepare, maintain, and update an electronic

(compatible with Microsoft EXCEL) indentured list of discontinued components used in the equipment, referred to as an Interchangeable Parts List. The next higher assemblies shall also be provided along with reference designators, alternate, and generic part numbers. A copy of the Interchangeable Parts List shall be provided on a bi-monthly basis to the Government.

3.1.6.5.2 The Contractor shall include the following data in the Indentured Parts

List for all system assemblies, including sub-vendors and sub-contractors providing any and all System Assemblies, Sub-assemblies, and COTS:

Part reference designator

Manufacturer part number Manufacturer Cage/FSCM Code Contractor part number Contractor CAGE/FSCM Code Part number associated National Identification Item Number

(NIIN), if stock-listed Generic die number (applicable to microelectronics only) Part nomenclature (description) Total part quantity per system (sum of all quantity per assemblies per system) Approved alternate manufacturer part number Alternate part manufacturer CAGE/FSCM Code

3.1.6.5.3 The format of the Indentured Parts List shall be provided by the

Government at the time of Contract Award.

3.1.6.5.4 Annually, the Contractor shall deliver an up-to-date BOM reflecting all changes to the system affecting the Indentured Parts List.

Reference CDRL: A010 and A056

3.1.6.6 DMSMS ALERTS & NOTIFICATIONS. The Contractor shall notify the Government, no later than 14 (fourteen) working days after discovery, of any component that becomes obsolete on deliverable equipment. This notification shall include any Contractor initiated “life time buys” to support fielded equipment. The notification shall be by electronic means and include a summation of any Contractor survey(s) conducted by the Contractor, information regarding impacts to system and components, and possible resolutions.

3.1.6.6.1 The Contractor shall prepare and submit responses to DMSMS Alert

Notices provided by the Government. In their response the Contractor shall provide:

The Contractor’s component utilization history over the last two years.

The Contractor’s anticipated component consumption for the life of the contract.

The Contractor’s on-hand inventory and outstanding orders.

Impact to supportability of the equipment.

3.1.6.6.2 The Contractor shall submit DMSMS Notifications and responses to

DMSMS Alerts electronically in an EXCEL spreadsheet form approved by the Government.

Reference CDRL: A011

3.1.6.7 SW BASED QUALIFIED PARTS LIST. The Contractor shall provide a complete list of all installed software including firmware, drivers, and operating systems and its supplier.

Reference CDRL: A007

3.1.6.8 Customized Microelectronic Devices Source Selection Plan. System components shall be sourced only from responsible companies. Responsible companies are defined in Defense Federal Acquisition Regulation Supplement – 30 November 2015.

The system shall only contain supported components. Unsupported system components shall be replaced with equivalent supported components. The contractor shall submit a Customized Microelectronic Devices Source Protection Plan that documents how the contractor’s supply chain management is conducted in accordance with the following:

3.1.6.8.1 The contractor shall implement supply chain protections to ensure system components are legitimate. The contractor shall implement supply chain protections to ensure system components are not compromised. The contractor shall implement supply chain protections to ensure system components are not infected with malicious code. The contractor shall document their implemented supply chain protections.

The contractor shall provide their documentation of implemented supply chain protections to the Government.

Reference CDRL: A080

3.1.6.8.2 The contractor shall implement an anti-counterfeit policy. The contractor shall implement procedures that include the means to detect counterfeit components. The contractor shall implement procedures that include the means to prevent counterfeit components from entering the system. The contractor shall provide their anti-counterfeit policy to the Government. The contractor shall provide documentation on how the contractor will detect counterfeit components. The contractor shall provide documentation on how the contractor will prevent counterfeit components from entering the system. The contractor shall implement a process for addressing any counterfeits parts found. The contractor shall provide documentation on how they will address found counterfeit parts to the Government. The contractor shall notify the contracting officer within 48 hours of finding a counterfeit part.

Reference CDRLs: A073, A080

3.1.6.8.3 The contractor shall require their subcontractors to implement supply chain protections to ensure system components are legitimate. The contractor shall require their subcontractors to implement supply chain protections to ensure system components are not compromised. The contractor shall require their subcontractors to implement supply chain protections to ensure system components are not infected with malicious code. The system shall only contain supported components.

Unsupported system components shall be replaced with equivalent supported components.

3.1.6.9 Parts Obsolescence

The contractor shall establish and implement a parts obsolescence program. In the event that manufacturing phase-out or discontinuance of production of such items is contemplated, the contractor is required to notify the contracting officer and publish the discontinuance in the Government-Industry Data Exchange Program (GIDEP), where feasible; and to provide immediate advance notice of production phase-out to NSWCPD RSC ISEA (C/517) and NSWCPD ILS rep (C/311).

3.1.6.9.1 STORAGE and MAINTENANCE REQUIREMENTS. The Contractor shall provide a Preservation and Preventative Maintenance Plan for the RSC equipment. This plan shall detail recommended preservation and preventive maintenance procedures for the RSC equipment during storage at the Shipyard and for an installed system in an industrial shipboard environment for a period of inactivity greater than 180 days.

3.1.6.9.2 The Contractor shall supply protection for all equipment during shipping.

3.1.6.9.3 Reusable, water resistant, fire retardant protection shall be used for equipment when required.

3.1.6.9.4 Desiccants shall be provided where applicable

3.1.6.10 Contractor shall include equipment storage prior to and during shipboard installation and Shipyard equipment light-off.

3.1.6.10.1 All Shipset RSC batteries shall be stored and preserved at vendor's facility until they are required at the shipyard. The government will notify the vendor when the batteries are required at the shipyard and should be shipped. The Contractor shall agree with holding the material until availability is identified to ship the GFP to a Government facility/location.

3.1.6.10.2 The safe and secure transportation of all materials and equipment(s) required shall be the responsibility of the Contractor.

3.1.6.10.3 The Contractor shall receive, maintain, and store material items as necessary until required for assembly and test.

3.1.6.10.4 The vendor must agree with holding the material and NOT invoicing for it until availability is identified to ship the GFP to a Government facility/location.

Reference CDRL: A057, A063

3.1.6.11 All documents and information generated under the contract shall be backed up at least once a week. All documents and information generated under the contract shall be backed up at least once every two weeks to an offsite location. Backups shall be verified by restoration at least once every two weeks. Backups shall be validated by restoration at least once every two weeks. The Contractor shall identify an alternate storage site for backup data. The Contractor shall utilize the identified alternate site for storage of backup data. The Contractor shall store a copy of all the backup data for the contract at the identified alternate site. The Contractor shall ensure the backed up contract data/information is secured in the same manner as the original data. The Contractor shall ensure the backed up contract data is protected in the same manner as the original data. The Contractor shall ensure the backed up contract data is encrypted with AES-256. The Contractor shall provide documentation on their alternate site. The Contractor shall provide the backup safeguard documentation to the Government as part of the INFOSEC Boundary Configuration Management Plan.

The Contractor shall provide the backup security documentation to the Government.

The Contractor shall document the process for recovery of all systems required to accomplish tasking for the contract. The Contractor shall provide documentation that demonstrates the process for recovery has been proven. The Contractor shall provide documentation that demonstrates the process for recovery can be accomplished within one week of a system failure.

Reference CDRL: A086

3.1.6.12 An Engineering Change Proposal (ECP), also referred to as a Design Change Notice in Attachment B, shall be used by the Contractor to define a proposed change to a configuration item. The ECP form (See Attachment D) shall be used, and 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 DDG-M RSC Performance Specification.

Reference CDRL: A050

3.1.6.12.1 Design Change Notice (DCN).The contractor shall notify the TSA of all changes, whether of a production or modification type, which are approved for incorporation into the end item and which modify, add to, delete, or supersede parts in the end item or its supporting equipment.

An approved engineering design or production change requires new identification when:

i. performance or durability is affected to such an extent that superseded items must be discarded for reasons of safety or malfunctioning;

ii. parts, subassemblies, or complete articles are changed to such an extent that the superseded and superseding items are not functionally or physically interchangeable;

iii. superseded parts are limited to use in specific articles or models of articles and the superseding parts are not so limited;

iv. an item has been altered or determined that additional requirements for selection of that part (form, fit, tolerance, performance or reliability) are necessary;

v. interchangeable repairable assemblies contain a non-interchangeable part, its next assembly and all the progressively higher assemblies shall be changed up to and including the assembly where interchangeability is reestablished;

vi. an item is changed in such a way that necessitates a corresponding change to an operational, self-test or maintenance test computer program, the part number identification of the item and its next assembly and all progressively higher assemblies shall be changed up to and Including the assembly where computer programs are affected.

The contractor shall submit Provisioning Technical Documentation (PTD) revisions via DCNs in accordance with the following:

i. When the approved change affects interchangeable repairable assemblies so as to introduce non-interchangeable parts, identify the part number before the change as a deletion and the part number after the change as an addition

ii. Change and document the part number of the next higher assembly, and those of all progressively higher assemblies, up to the assembly where interchangeability is reestablished. PTD shall include the interchangeable assembly

iii. Engineering Data for Provisioning (EDFP) is not required for deleted items

iv. Changes that occur after PTD has been delivered shall be documented as a revision to the applicable PTD.

Reference CDRL: A053

3.1.6.13 Quality Assurance Program. The Contractor shall provide and maintain a quality program that, as a minimum, adheres to the requirements of ASQ/ANSI/ISO 9001:2015.

3.1.6.13.1 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 Quality Assurance Plan shall be resubmitted any time major policy or process changes affect the scope of the contract. If the current Quality Assurance Plan 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.

Reference CDRL: A026

3.1.6.14 FAILURE REPORTING AND ANALYSIS PROGRAM. A Failure Reporting and Analysis Program (FRAP) shall be implemented by the Contractor. The Failure Reporting and Analysis Program shall include OS software and failures. A summary list of all failures for which failure analysis reports have been prepared shall be provided to the Government.

A Failure Analysis summary list for all systems must be submitted 30 days after the occurrence of failure rather than all at once to allow for more time to implement corrective action.

Reference CDRL: A031 and A039

3.1.6.15 The Contractor shall develop, implement, manage to, update, and maintain the RSC Program Integrated Master Schedule (IMS) by logically networking detailed program activities. The IMS shall be maintained in Microsoft Project™ 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.

Reference CDRL: A032 and A033

3.1.7 FIRST ARTICLE TESTING AND NON-RECURRING ENGINEERING CLIN The Contractor shall perform First Article Tests in accordance with sections 3.1.8.1 through

3.1.8.26 and 3.2 through 3.5 on the Qualification equipment set CLIN. This testing includes verification that the system complies with the requirements for service use and that it performs all of its functions as part of the RSC in a satisfactory manner. This CLIN shall include Non-Recurring Engineering costs including research, design, and development.

3.1.7.1 SOFTWARE ENGINEERING. The Contractor shall develop software to meet the requirements in the DDG-M RSC Performance Specification, Attachment A.

3.1.7.1.1 A Software Development Plan (SDP) shall be generated and implemented. SDP shall include the Software Configuration Management Plan (SCMP) and Software Quality Assurance Plan

(SQAP).

Reference CDRL: A025

3.1.7.1.2 The Contractor shall develop the following software documentation for all software developed under this contract: detailed Interface Design Descriptions (IDD), Software Requirements Specifications (SRSs), Software Design Descriptions (SDD), Software Programmers Guide (SPG), Software Version Description (SVD), Software User’s Manual (SUM), Software Installation Plan (SIP), Software Test Plan (STP), Software Test Descriptions (STDs), Software Test Reports (STRs), Software Product Specifications (SPSs), System Deficiency Report (SDR), and Software Transition Plan (STrP). The software requirements shall be provided to the government as DOORS 9.6 compatible files. An export file of RSC PANEL PC software requirements from DOORS into Microsoft EXCEL file format is required with each DOORS file delivery. The Contractor shall provide the origin for all Software Development Tools and Software used to satisfy the requirements of this contract. This includes the origin of all physical media and source link for all downloaded tools from the internet.

Reference CDRLs: A012, A013, A014, A015, A016, A017, A018, A019, A020, A021, A022, A023, A024

3.1.7.1.3 The Contractor shall design and develop the software architecture in a manner which shall ensure maintainability throughout the development and lifecycle of the software. The Contractor shall be appraised at a CMMI maturity level three (3) or higher by a certified Software Engineering Institute appraiser and must utilize their CMMI processes in performance of this contract. The Contractor shall develop all software following the ISO/IEC/IEEE 15289, Second Edition: Systems and Software engineering – Content of life-cycle information items (documentation). The Contractor shall follow software development processes such as those developed for compliance with SEI SW CMMI Level III. The Contractor shall address software safety within their Program Plan. Safety assurance shall be addressed in the SDP and safety requirements for software shall be addressed in the SRSs. The Contractor shall conduct testing on all of the CSCIs developed under this contract. The Contractor shall perform the software testing in accordance with the STP and report the test results via the STR. The Contractor shall validate the software is in compliance to the SRSs and IDDs developed under this contract. The Contractor shall address the software unit testing, software integration testing and software system testing in the STP and STD developed under this contract.

3.1.7.1.4 Contractor shall provide the following items along with the SPS deliverable: applications, operating systems, licenses, Application Interfaces (APIs), all development tools, and documentation, including Software User Manuals, to the Government for all Contractor provided COTS software, firmware, and hardware/device drivers.

Reference CDRL: A007, A019, A023

3.1.7.2 Software Documentation: The Contractor shall provide a Software Documentation

Report detailing all applications, utilities, system services, scripts, configuration files, databases, firmware, and all other software required for the system to meet all system requirements.

The contractor shall also provide a Software Documentation Report with all media deliveries to the Government. The Software Documentation Report shall address the following for media deliveries:

All system media shall be marked as Controlled Unclassified Information (CUI), All Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document.

All media shall be checked for malicious code prior to use on the system.

The contactor shall document all media scans in monthly report detailing the media scanned, the information on each media scanned, the results of each scan, the software version utilized to conduct the scan, the date of the signature file utilized for the scan, and the date the scan was conducted.

All media containing malicious code shall be dealt with in accordance with National Security Agency Guidance for Addressing Malicious Code Risk dated 10 September 2007.

The contactor shall document all media found to contain malicious code in a monthly report that contains the details the media scanned, the information on the media scanned, the results of each scan, the software version utilized to conduct the scan, the date of the signature file utilized for the scan, and date the scan was conducted.

The contractor shall document the steps followed out of the National Security Agency Guidance for Addressing Malicious Code Risk dated 10 September 2007, including the final disposition of the media.

The contractor shall encrypt all delivery media with a software product that supports AES-256.

The contractor shall provide a monthly report detailing all delivery media, the information on each delivery media, the software product used to encrypt the media, and the date the encryption was conducted.

The contractor shall provide the encryption key for each delivery media via encrypted email to the Government designated recipient of the delivery media on the same business day the media is shipped or otherwise provided.

The contractor shall utilize a unique AES-256 encryption key for each media delivery.

The contractor shall provide the encryption key via secure communications to the Government on a per delivery basis.

Reference CDRL: A081

3.1.7.3 Software Design/Development: The Contractor shall design and develop all software using the following general requirements:

No Binary or machine executable public domain software products with limited or no warranty such as those commonly known as freeware or shareware shall be used.

Open Source Software (OSS) binary installation packages shall be obtained from official project download links provided by the project group maintaining the OSS package.

OSS binary packages unavailable for download from a trusted OSS server shall be documented under appropriate supply chain and configuration management policies.

OSS servers located in the continental United States in the .gov or .mil top level domain shall be considered trusted.

OSS servers located in the continental United States not in the .gov or .mil top level domain shall be considered untrusted.

OSS servers not located in the continental United States regardless of .gov or .mil top level domain shall be considered untrusted.

Software/Firmware shall ensure that file system objects are truncated before reusing the same name.

Software/Firmware shall ensure that unused objects contents are zeroed before they are deallocated and relinquished to the operating system.

Software/Firmware shall protect against buffer overflows, dynamic memory errors, dangling pointers, double frees, invalid frees, null pointer accesses, uninitialized variables, wild pointers, out of memory errors, stack overflows and allocation failures.

Software/Firmware shall perform input validations of all data passed to a CSCI from any external interfaces such as but not limited to network packets, user provided input, and other CSCIs.

Reference CDRL: A019, A023

3.1.7.4 The Contractor shall provide installation procedures for complete installation, configuration, and set-up of all Contractor and COTS software, including drivers as part of the SPS. The SPS shall include an installation and set-up procedure of all RSC Panel PC BIOS, operating systems, and Contractor provided applications from initial hardware startup.

CDRL: A019

3.1.7.5 Contractor shall provide with SPS deliverable including but not limited to the following: compiled binaries/executables, licenses, source code, APIs, BSP (Board Support Package), and development tools for all Contractor developed software scripts and software applications not developed exclusively at private expense in accordance with DFARS 252-227-7017. The Contractor shall provide a SPG for all contractor developed software.

CDRL: A019, A023

3.1.7.6 System libraries shall be managed and maintained to protect privileged programs and to prevent or minimize the introduction of unauthorized code. A plan shall be developed by the vendor that illustrates this process. The plan shall be provided to the Government.

CDRL: A025

3.1.7.7 The Contractor shall provide documentation of development practices and standards applied to Contractor-written software, including firmware, used to ensure a high level of defense against unauthorized access. The Contractor shall provide documentation of coding practices used in developing the delivered software. The Contractor shall provide documentation detailing all applications, utilities, system services, scripts, configuration files, databases, and all other software required. The Contractor shall provide documentation detailing the revisions and/or path levels for each of the computer systems associated with the control system.

Reference CDRL: A074, A087

3.1.7.8 Any Data Rights and Patent Rights offered in addition to those provided in Section K clause DFARS 252.227-7017 shall be provided. The Contractor shall cite specific examples of the Government's rights that illustrate the tenets of the offer, including an overview of the information provided in the following required attachments, as well as a discussion of how the information contained in the attachments impacts or illustrates the tenets of the proposal:

The Contractor shall provide the following information:

A. Rights in Noncommercial Technical Data (TD), Noncommercial Computer Software (CS), and Noncommercial Computer Software Document (CSD).

(i) The 7017 List. The Contractor shall provide a list identifying all noncommercial TD, CS, and CSD that it asserts should be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7017 (Jun 1995) clause incorporated at Section K of this solicitation.

(ii) The 7028 List. The Contractor shall provide a list identifying all noncommercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to TD, CS, or CSD that the Contractor has delivered to, or is obligated to deliver to, the Government under any contract or subcontract. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7028 (Jun 1995) clause incorporated at Section K of this solicitation. Additionally, if there is no data or software to be identified in the 7028 list, the Contractor shall submit the list and enter "None" as the body of the list. If the Contractor is awarded a contract, the 7028 List shall be attached to the contract.

(iii) Supplemental Information. The Contractor provide a statement, entitled “Supplemental Information--Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of noncommercial TD, CS, or CSD that the Contractor asserts should be delivered with specifically negotiated license rights or other non-standard rights (as discussed at DFARS 252.227-7013 (NOV 1995) and/or DFARS 252.227-7014 (JUN 1995)), sets forth a complete description of all such proposed non-standard restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information may be provided by referencing any proposed non-standard license agreement that is attached to the statement. The Contractor shall submit the statement as an attachment to its offer, dated and signed by an official authorized to contractually obligate the Contractor. If there is no information to be included in the statement, the Contractor need not submit the statement. If the Contractor is awarded a contract, any statement provided will be

B. Rights in Commercial TD, Commercial CS, and Commercial CSD.

(i) The Contractor shall provide a list, entitled “Commercial

Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-–Government Use Restrictions” (the Commercial Restrictions List), that provides the following information regarding all commercial TD, CS, and CSD that the Contractor (including its subcontractors or suppliers, or potential subcontractors or suppliers, at any tier) intends to deliver with other than unlimited rights: (1) identification of the data or software; (2) basis for asserting restrictions; (3) asserted rights category; and (4) name of the person asserting restrictions.