Amend_0003_N0002419R5600_modification_copy.docx

N0002419R5600

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

The purpose of amendment 0003 to the solicitation N00024-19-R-5600 is to make administrative changes to Sections B through M as follows:

Section B:

1. Changed Part Number for CLIN 1004 in extended description.

2. Updated CLIN 0024 from First Article Unit Testing to First Article Requirement in extended description.

Section C:

3. Updated Attachment X to reflect Attachment J-3 in 3.6.3.

4. Added 3.12.5.2 as Reserved

5. Added the sentence, “As identified in the FAT plan and procedures (provided with TDP, attachment J-2) or suitable alternatives, subject to Government approval. Specifically, bidders will be required to develop and document the Test Plan and Procedures for the following Conversion Group Tests in Section 4.3.7 of 3071593 MOD1 ACEGIO FAT Plan: VLP, DAP, GDP, BMS, and ATP. As well as, develop and document the necessary Test Fixtures indicated in Section A2.3 of the same document and submit for NSWC, Dahlgren Division Design Agent Approval and Acceptance for incorporation into MOD1 source TDP.” in A2.

6. Corrected the ECP CDRL number discrepancy in 3.6.1.

7. Removed CLIN 0300 under paragraph 3.11

8. Deleted sentence regarding travel and incidental material for CLIN 200 series in C-1.

Section E:

9. Changed Inspection and Acceptance for CLINs 0017-0025 from destination to origin in Clause E-246-H017.

Section H:

10. Changed Drawing Number for AECGIO1 in the GFE Table in Clause 5252.245-9109.

Section I:

11. Removed Clause 52.243-6 Change Order Accounting

12. Removed DFARS Clause 252.227-7039 Patents- Reporting of Subject Inventions

13. Added the original DFARS Clause 252.246-7001 Warranty of Data Clause

14. Removed DFARS Clause 252.227-7026 Deferred Delivery of Technical Data or Computer Software

15. Removed FAR Clause 252.227-7010, License to Other Government Agencies

Section K:

16. Incorporated FAR 52.230-1 deviation

Section L:

17. Update Page Limit for CWBS in Section L.2

18. Update Page Limit for Table of Contents in L.2

19. Update Page Limit for Volume Cross Reference in L.2

20. Update Technical Volume Page Count in L.2

21. Updated Microsoft 2010 to Microsoft 2016 in L2.1

22. Incorporated FAR 52.230-2

23. Updated “major” to 55M in Section L.5.

24. Added the word REPAIRS to FIRM FIXED PRICE INCO SPARES in Section L.6 item 3

Section M:

25. Added the word REPAIRS to FIRM FIXED PRICE INCO SPARES on the M.3 table and item 3 in Section M.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0024

The CLIN description has changed from First Article Unit Testing to First Article Unit Requirements.

The CLIN extended description has changed from:

First Article Unit Testing - Air Cooled PS2See Notes A, B, D

To:

First Article Unit Requirements- Air Cooled PS2See Notes A, B, D

CLIN 1004

The CLIN extended description has changed from:

Water-Cooled AEGIS LAN Interconnect System (ALIS) Cabinet DWG# - 856367See Notes A, B, C

To:

Water-Cooled AEGIS LAN Interconnect System (ALIS) Cabinet DWG# - 8563367See Notes A, B, C

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

CONTRACT LINE ITEM DESCRIPTION

C-1 DELIVERABLES

The Network, Processing and Storage (NPS) Equipment is comprised of CPS TI-16 Mod 1 and portions of the AAU Equipment Suites, under CLINs 0001-0016 (if exercised 1001-1016, 2001-2016, 3001-3016, 4001-4016) – If procured, the Contractor shall manufacture, assemble, test, and deliver the following Network, Processing and Storage Equipment in accordance with the applicable Technical Data Package (Attachment J-2) and the requirements defined in the statement of work of this contract.

INCO, SPARES, REPAIR CLINs 0100 (if exercised, 1100, 2100, 3100, and 4100) – If procured, the Contractor shall test and deliver INCO/spares and repair parts. The INCO/spare and repair part descriptions and quantities shall be as established in each contract modification.

ENGINEERING SERVICES CLINs 0200 (if exercised, 1200, 2200, 3200, and 4200) - If procured, the Contractor shall provide engineering services (ES), conduct engineering studies, provide engineering analysis and trade-off studies, and/or support engineering changes as directed by the Government. The specific tasks shall be defined in each contract modification.

OTHER DIRECT COSTS (ODCs) CLIN 0300 (if exercised, 1300, 2300, 3300 and 4300) – If procured, the Contractor shall provide any travel or incidental material consumed in the performance of the required Engineering Services. The specific ODC details shall be defined in each contract modification.

FIRST ARTICLE CLINs 0017-0024 – The Contractor shall support and complete first article requirements as defined in the Statement of Work.

PRR CLIN 0025 – The Contractor shall successfully support and complete a Production Readiness Review (PRR) as defined in the Statement of Work.

COUNTRY OF ORIGIN STUDY CLIN 0026 – The Contractor shall determine the components for the country of origin for all major electronic assemblies/subassemblies as defined in the Statement of Work.

DATA/CDRLs CLIN 0400 - The data to be furnished hereunder shall be prepared in accordance with the requirements of this contract and the Contract Data Requirements List (CDRL), DD Form 1423, Exhibit A, B and C. The item is Not Separately Priced (NSP).

PROVISIONED ITEMS ORDERS CLIN 5000 - Provisioned Items Orders will be placed in accordance with the Section C clause PROVISIONED ITEMS ORDERS. The supplies or services shall be identified in each Order.

SECTION C-2 STATEMENT OF WORK

THE FOLLOWING STATEMENT OF WORK (SOW) IS APPLICABLE TO ALL LINE ITEMS UNLESS OTHERWISE SPECIFIED

This SOW will refer to CPS and portions of the AAU equipment suite throughout this document indicating this alignment of functions and requirements, which is reflected in the title of this future contract “Network, Processing, and Storage Equipment”. This Statement of Work (SOW) defines the efforts required for the manufacture, assembly, and test of the Network, Processing and Storage Equipment. The Contractor’s facilities shall be cleared at the secret level in accordance with the attached DD 254 (Attachment # J-1).

1.0 SCOPE

This Statement of Work (SOW) defines the efforts required for the manufacture, assembly, and test of the Network, Processing and Storage Equipment, spares, and associated technical services, including logistics product development. The Network, Processing and Storage Equipment is comprised of the Common Processing System (CPS) Technology Insertion (TI) 16 Mod 1 and portions of the Aegis Weapon System (AWS) Aegis Modernization (AMOD) Upgrade (AAU) equipment suite. The Network, Processing and Storage Equipment is designed to support the Program Executive Office for Integrated Warfare Systems’ (PEO IWS) implementation of an Open Architecture (OA) for Navy combat systems. The equipment maximizes flexibility and modularity by incorporating commercial hardware and software compliant with Open Architecture Computing Environment (OACE) technologies and standards, when available. The equipment provides the computer processing and memory, data storage and extraction, and Input/Output (I/O) interfaces to support host software applications of Navy combat systems.

1.1 BACKGROUND

The Network Processing Storage equipment supports the hardware resource requirements for multiple Combat and Weapon Systems. Technical requirements have been driven by AEGIS new ship construction (SCN), AEGIS Modernization (AMOD), AEGIS Ashore (AA), Ship Self Defense System (SSDS), Aircraft Carrier – Tactical Support Center (CV-TSC), Surface Electronic Warfare Improvement Program (SEWIP), Guns Weapon System (GWS), Foreign Military Sales (FMS), Fast Frigate (FFG), U.S. Coast Guard (USCG), MQ-25 Unmanned Carrier Aviation (UCA) UCA Mission Control System (UMCS), Amphibious Ships, and Littoral Combat Ship (LCS).

The CPS TI-16 Mod 1 portion of the contract consists of two different Enclosure Assemblies (MCE and EMCORP) and three variants – a Core Computing System (CCS) Cabinet, an Advanced Storage Area Network (ASAN) Cabinet, and a Processing and Storage Subsystem (PS2) air-cooled Cabinet. The CCS provides core computing resources for Navy Combat System application programs. The ASAN Cabinet provides storage for load files, program data storage, video files, data extraction files, database management, and other mass storage and archive requirements for the Combat System. The PS2 cabinet combines processing and storage into a single cabinet with reduced processing and storage capacities.

CPS TI-16 Mod 1 provides solutions to address diminishing manufacturing supply and obsolescence issues with TI 16 Mod 0. Additionally, the CPS TI 16 Mod 1 procurement incorporates AAU components. TI 16 Mod 1 mitigates DMS impacts to the TI 12 AAU configuration, drives the AWS design toward the use of “common building blocks” thereby reducing the count of line repairable units (LRUs), incorporates IA requirements and system protection features into the initial design, and upgrades AWS processors and displays to allow the implementation of ACB 16 improvements.

The portions of the AAU contract will produce four variants of populated cabinets – an AEGIS LAN Interconnect System (ALIS) cabinet, an AEGIS Conversion Equipment Group Input/Output (ACEGIO) #1 Cabinet, and ACEGIO #2 Cabinet, and a Digital Video Display System (DiVDS) Cabinet. The ALIS cabinet provides the mechanism for Combat System and external systems to communicate with the AEGIS Weapons System, the core connectivity between cabinets that host AEGIS Weapons System Elements, and the capabilities for cabinet management, network switching, intrusion detection, firewall services, gateway services, a detonation chamber, and cross domain solutions. The ACEGIO cabinets provide legacy equipment interface support, network time protocol dissemination electro-mechanical integration, and installation of legacy VME / interface cards. The DiVDS provides shipboard operators with access to analog video data from multiple sources to include consoles, camera locations, tactical applications and video walls.

2.0 APPLICABLE DOCUMENTS.

The following documents form part of the SOW to the extent specified herein. In the event of a conflict between the documents referenced herein and the contents of this SOW, the SOW shall be considered the superseding requirement. These documents are updated frequently, Offerors should refer to the latest approved version of these documents.

2.1 Government Documents

Program Executive Office, Integrated Warfare Systems (PEO IWS) – Deputy Commander, Naval Sea Systems Command Research and System Engineering Warfare Systems Engineering and Human Systems Integration Directorate (NAVSEA 05H) Technical Review Manual (TRM) v2.0 18 Dec 2009

Naval Sea Systems Command Warfare Systems Engineering Directorate (NAVSEA) Contracts Handbook 09 December 2009

Configuration Management Plan (CMP) for Program Executive Office, Integrated Warfare Systems

(PEO IWS) 1.0

17 January 2014

Naval Sea Systems Command Warfare Systems Engineering Directorate (NAVSEA) Instruction 9078.22, Naval Ships Critical Safety Items (CSI) Program Technical Requirements 15 May 2008

Naval Sea Systems Command Warfare Systems Engineering Directorate (NAVSEA) Clinger-Cohen Act (CCA) Compliance Guide April 2008

2.2 Joint Chiefs of Staff, Department of Defense, and DoD Services Documents

Defense Acquisition Guidebook 4.3.3.4.7, Production Readiness Review (PRR) https://dag.dau.mil 06 August 2013

2.3 Military Standards (MIL-STD)

MIL-STD-129P DoD Standard Practice, Military marking for Shipment and Storage, 19 September 2007

MIL-STD 130N Department of Defense Standard Practice Identification Marking of U.S. Military Property 15 June 2007

2.4 Other Military Documents

MIL-PRF-29612B Training Data Products

31 August 2001

2.5 Handbooks

2.6 Non-Government Documents/ Commercial Standards

2.7 Non-Government Documents

American Society for Testing of Materials (ASTM)

ASTM F1337-10

Standard Practice For Human Engineering Program Requirements For Ships And Marine Systems, Equipment, And Facilities

International Organization for Standards (ISO) ISO 9001:2015, Quality Management Systems – Requirements 30 November 2008

International Organization for Standards (ISO) ISO 10007:2003 Quality Management Guidelines for Configuration Management 01 June 2003

3.0 REQUIREMENTS.

3.1 GENERAL. The Contractor shall furnish all cleared labor and materials, other than the items provided by the Government as GFE/GFP as identified in Section H, necessary for the manufacture, assembly, and test of the Network, Processing and Storage Equipment, spares, and associated technical services, including logistics product development. Program information, deliveries, and data shall be handled in accordance with the Contract Security Specification, (DD Form 254, Attachment J-1).

3.2 Program Management and Control (Applicable to All CLINs). The Contractor shall provide program management oversight to ensure all work conducted within this contract is planned and executed in a manner that will achieve all quality, schedule, and cost objectives.

3.2.1 Program Management Office. The Contractor shall establish a Program Management Office that is responsible for the management and control of Program Management Plan (CDRL A001) elements in order to support the successful on-time delivery of the contract requirements. The Program Management Plan shall incorporate detailed production planning, milestones, and metrics capable of supporting the execution of all tasks required by the Contract and this SOW.

Deliverable Data Item (See DD-1423):

CDRL A001: “Program Management Plan”

3.2.2 Program Manager. The Contractor shall designate a Program Manager who will ensure all work conducted within this contract is planned and executed in a manner that will achieve all management, technical, logistics, budget, and schedule objectives.

3.2.3 Subcontractor Management (Applicable to all CLINs).The Contractor is responsible for executing the requirements of this contract and shall institute appropriate management actions relative to subcontractor performance. The Contractor shall flow down the requirements of this entire SOW to all Subcontractors, regardless of contract value. Requirements that are contractually specified shall apply to Subcontractor performance; however, the Contractor shall be accountable for the subcontractor’s compliance and is responsible for ensuring all deliverables comply with the contract requirements.

3.2.4 Monthly Progress, Status and Management Reports. The Contractor shall deliver a Contractor’s Progress, Status and Management Report (CDRL A002) to the government. Data item requirements shall include:

· Status of significant program events (e.g. Post Award Conference, Interchange Meetings, Program Reviews);

· Status of significant/major production and/or issue resolution;

· Cost reporting (funded, expended, monthly burn rates, and remaining) for all non-FFP CLINs by Contract Modification;

· Risk assessment;

· Environmental Safety and Occupational Health (ESOH) hazard status;

· Logistics Product Development Schedules and Status (see para 3.12);

· Schedules for contract modifications and equipment production/deliveries;

· Action item status;

· Invoices submitted to Wide Area Work Flow (WAWF).

Deliverable Data Item (See DD-1423):

CDRL A002: “Contractor’s Progress, Status and Management Report”

3.2.5 Meetings. The Contractor shall coordinate, prepare for, conduct, facilitate, and participate in reviews, meetings, and conferences as specified herein. The Government reserves the right to attend all (boards, reviews, etc.) meetings between the prime and its subcontractors. The Contractor shall provide the Government notice of any such meeting in writing at least fourteen (14) days in advance. The Contractor shall provide a Conference Agenda (CDRL A003), Presentation Material (CDRL A004), and Conference Minutes (CDRL A005) for each meeting. At a minimum, the Contractor shall support meetings identified within the following paragraphs. Teleconferencing shall be used whenever possible; otherwise, meetings shall be held at the Contractor’s facility. When teleconferencing is required, the Contractor shall provide teleconferencing services, including web conferencing and telephone dial-in numbers, at the request of the Contracting Officer’s Representative (COR). These services shall be able to accommodate up to forty (40) attendees. Reference the table below for an overview of the meetings that will be required by this Contract.

Deliverable Data Item (See DD-1423):

CDRL A003: “Conference Agenda”

Deliverable Data Item (See DD-1423):

CDRL A004: “Presentation Material”

Deliverable Data Item (See DD-1423):

CDRL A005: “Conference Minutes”

3.2.5.1 Bi-Weekly Program Management Reviews (PMRs). The Contractor shall coordinate, participate in, and facilitate Bi-Weekly PMRs. Bi-Weekly PMRs shall be conducted in person at the Contractor’s plant or via teleconferencing with the Contractor providing a summary of its current program status to include Contractor’s Progress, Status and Management Reports (CDRL A002). The current program status report shall contain the following main sections: Summary, Accomplishments, Current Status, Problem Areas, Risks and Mitigations, Cost and Schedule Data, and Future Plans. The reporting period shall be for the duration of the contract.

3.2.5.2 Program Assessment Reviews. The Contractor shall conduct quarterly Program Assessment Reviews (PARs), beginning four (4) months after award of contract, to assess the Contractor’s progress and status. The Contractor shall provide, at a minimum, an overview of production status, a review of program Diminishing Manufacturing Sources and Material Shortages (DMSMS) status including disclosure of any and all known DMSMS items, the planned action to mitigate its engineering and Integrated Logistics Support (ILS) impacts, and a report on its small business utilization. The status of the Contractor’s efforts to achieve the requirements set forth in the contract will be emphasized. Vendor/subcontractor status and problems shall also be addressed; as such, vendors/subcontractors may be requested to support the review as required. In addition, a separate review may be conducted to cover a special set of circumstances or troublesome area(s), but the reviews shall be considered part of and conducted with the PAR. An Action Item List shall be prepared and maintained by the Contractor during the life of this contract to enable tracing the closure of generated action items.

3.2.5.3 Integrated Product Team (IPT) Meetings. The Contractor shall participate in, provide inputs to, and support monthly IPT meetings to ensure integrated work across all elements of the CPS program.

3.2.5.4 Post Award Kickoff Meeting. The Contractor shall schedule a Post Award Kickoff Meeting within twenty-one (21) calendar days of contract award and conduct the Post Award Kickoff Meeting within forty-five (45) calendar days of contract award at the Contractor’s facility. During the Post Award Kickoff Meeting, the Contractor shall provide a detailed briefing on its management and contract execution strategy. The contract briefing shall include: any updates following the proposal submittal; an organizational overview; key personnel; schedules, specifically material purchasing and Production Readiness Review (PRR) schedules; a description of the Contractor’s quality process, including designation of the quality manager; and a discussion of risk and risk mitigation strategies. The Contractor shall plan for a one-day Post Award Kickoff Meeting.

3.2.5.5 Local Change Configuration Board (LCCB) and Engineering Working Group (EWG) Meetings. The Contractor shall participate in and support monthly LCCB meetings and bi-weekly EWG meetings as required.

3.2.5.6 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Meetings. The Contractor shall participate in and support quarterly DMSMS meetings. The Contractor shall prepare briefings that discuss the current status, forecast, and resolution of CPS DMSMS in support of this meeting.

3.2.5.7 Reliability and Maintainability (R&M) Reviews. The Contractor shall participate in and support quarterly R&M review meetings. The Contractor shall prepare briefings in support of this meeting.

3.2.5.8 Problem Review Boards (PRBs). The Contractor shall participate in and support monthly PRB meetings. The Contractor shall prepare briefings in support of this meeting.

3.2.5.9 Interchange Meetings. The Contractor shall coordinate and participate in up to four interchange meetings per exercised First Article Unit (FAU).

3.2.5.10 Production Readiness Review (PRR). The Contractor shall conduct a Production Readiness Review (PRR) within four (4) months of contract award.

3.2.6 Data Management

The Contractor shall post contract data and applicable deliverables to a Government specified website, unless otherwise specified on the applicable CDRL DD Form 1423-1. The Contractor shall provide electronic-mail (e-mail) notification to the COR and other Government personnel identified on the CDRL Addressee List within 24 hours of CDRL delivery (posting new/revised information and CDRL deliverable(s) on the website or delivering as specified on the associated DD Form 1423-1). The Contractor shall create and maintain a Contract Status Deliveries Report (CDRL A006). This report shall include the status of each data deliverable required by this contract, including contract identification, shipping/transmittal data, acceptance status, security classification, and scheduled due date information.

Deliverable Data Item (See DD-1423):

CDRL A006: “Status Report: Contract Deliveries Status”

3.2.7 Security Management. The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store classified material up to the SECRET Level as referenced in Attachment J-1, DD Form 254.

3.2.7.1 Controlled Unclassified Information (CUI) (Formerly for Official Use Only Information): The contractor shall be required to have access to CUI with developers and integrators.

3.2.7.2 Receive, Store, and Generate Classified Information: The contractor shall assist in modernizing systems that are classified. Techniques to modernize this equipment, testing of this equipment and overall system performance could be classified and the subject to email and written reports. In this capacity, the contractor shall generate and be in receipt of classified material.

3.2.7.3 International Traffic in Arms Regulations (ITAR). The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical Assistance Agreements (TAA), etc. required by the International Traffic in Arms Regulations and must obtain specific written authorization from the Procuring Contracting Officer (PCO), COR, or IWS 1.0 Security Manager before exercising those approvals or licenses.

3.2.7.4 Contractor Security. The Contractor shall implement security procedures in concert with Defense Security Service (DSS) National Industrial Security Program Operating Manual (NISPOM) per DoD 5220.22-M.

3.2.7.5 Public Release of Information. All public releases of information concerning this project must receive written approval of the PCO two weeks prior to release.

3.2.7.6 Website Security. The Contractor shall ensure that its publicly-accessible web-sites are free of For Official Use Only (FOUO) and/or indicators that could tip-off adversaries about impeding program activity. The Government will provide additional Operational Security (OPSEC) guidance as necessary.

3.2.7.7 Contractor’s Internal Network and Data Security. The Contractor shall ensure that its internal networks and data have sufficient protection to prevent intrusion from sources outside its facilities.

3.2.7.8 Detailed Tasks, Cybersecurity (All Items) The Contractor shall implement the security requirements of the clause under Section I of this contract entitled DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, and National Institute of Standards and Technology (NIST) Special Publication 800-171.

3.2.7.8.1 System Security Plan. The Contractor shall develop and submit a Technical Report – Study/Services, POAM and Systems Security Plan (SSP) (CDRL A031) that implements the security requirements of DFARS 252.204-7012.

In accordance with DFARS 252.204-7012, the SSP shall implement, at a minimum, all security requirements in NIST 800-171 (Rev. 1) standards 3.1 to 3.14; or ensure that any unimplemented security requirements have been adjudicated by an authorized representative of the DoD CIO to be non-applicable or to have an alternative, but equally effective, security measure in its place. The SSP shall provide proof of such adjudication by DoD CIO. Further, the SSP shall contain a description of the system boundary, the operational environment, how the specific security requirements are currently implemented, and the relationships with or connections to other systems. The POAM shall detail how and when the Contractor will meet all security requirements of SP 800-171 that are not fully implemented except for the requirements noted in the specific bullets below, which must be fully implemented in the SSP. The Contractor shall permit the Government to validate information in the SSP every three years, on an ad hoc basis with no notice to the Contractor, other than to coordinate any necessary security requests, but not more than five business days, or upon replacement or rotation of the Government program manager.

The SSP shall:

· Fully implement Multi-factor authentication, including authentication and authorization of users in a manner that is auditable

· Implement FIPS 140-2 validation encryption at a minimum of Level 1

· Employ the principle of least privilege or “need to know”

· Require the Contractor to review, in a manner that can be audited, user privileges at least annually

· Require monitoring and controlling remote access sessions and includes mechanisms to audit the session and methods

3.2.7.8.2 SSP and POAM Review. The Contractor shall allow the Government to evaluate the SSP and POAM upon request, including on the Contractor’s site, on an ad hoc basis. The Government will provide sufficient notification, but not more than five business days, to the Contractor to allow for the processing of visit requests to the site, if necessary. The Contractor shall support this evaluation in accordance with NIST SP 800-171A.

3.2.7.8.3 Subcontractors. The Contractor shall provide the plan to track flow down of covered defense information and to assess DFARS clause 252.204-7012 compliance for these suppliers/subcontractors.

3.2.7.8.4 Encryption of Data at Rest. Covered Defense Information (CDI) and Covered Contractor Information Systems (CCIS) are defined within clause 252.204-7012. Information at rest is defined as the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. On all CCISs, the Contractor shall encrypt CDI at rest in accordance with NIST 800-171.

3.2.7.8.5 Incident Reporting. The Contractor shall report cyber incidents, as defined in DFARS 252.204-7012, to the Damage Assessment Management Office (DAMO) via the DIB-Net website within 72 hours, per DFARS 252.204-7012. In addition to the reporting requirements above, the Contractor shall deliver all information related to cyber incidents, defined in DFARS 252.204-7012, in a Technical Report – Study/Services, Cyber Incident Report (CDRL A053). The Contractor shall segregate DON CUI from Contractor-owned information, when feasible. Segregation may be implemented through logical isolation, physical isolation, a hybrid approach, or other technological processes to achieve required delivery of compromised data in cyber incidents.

Deliverable Data Item (See DD-1423):

CDRL A053: “Technical Report: Cyber Incident Report”

3.2.7.8.6 Coordination with NCIS. The Contractor consents to installation by the Naval Criminal Investigative Service (NCIS) of network sensors, owned and maintained by NCIS, on the Contractor's CCIS or other information technology assets when intelligence indicates a vulnerability or a potential vulnerability for the duration of the contract performance period. If NCIS determines that the Contractor’s own sensor capability is adequate, the Contractor consents to cooperation with NCIS on cybersecurity, to include sharing information from its sensor capability and networks.

Both routinely and in response to emergent developments, NCIS engages in outreach efforts to the defense contracting community to coordinate cybersecurity efforts. The Contractor shall regularly monitor and engage with such efforts to ensure that contractor is aware of the most up-to-date cybersecurity information and strategies. As part of these efforts, the Contractor shall consider implementing all recommendations from NCIS for additional hardening (e.g., more stringent configuration settings) of DON critical programs and technologies.

Deliverable Data Item (See DD-1423):

CDRL A007: “ Contractor’s System Security Plan”

3.2.8 Risk Assessment and Management. The Contractor shall create and maintain a Contractor’s Risk Management Plan (CDRL A008), which shall include risk identification, assessment, ranking, trends, mitigation, and monitoring. Risk metrics shall be generated in accordance with PEO IWS Instruction 5000.8, Risk Management, and reported as part of the Contractor’s Progress, Status and Management Report (CDRL A002) and during all program reviews. The Risk section of the subject report shall include, as a minimum, the following:

Deliverable Data Item (See DD-1423):

CDRL A008: “Contractor’s Risk Management Plan”

3.2.9 Management and Accountability for Government Furnished Material (GFM). The Contractor shall deliver a plan for the management and accountability of all GFM, GFE, and GFI as part of the Program Management Plan (CDRL A001). The plan shall ensure that items furnished by the Government are properly managed and accounted for.

3.2.10 End of Contract Transition Planning. The Contractor shall develop an End of Contract Transition Plan (CDRL A009) that addresses the long-term support requirements of all of the Network, Processing, and Storage Equipment procured under this contract, as support agent responsibility transitions from the Contractor. This plan shall describe how the Contractor would transition the follow-on support of the Network, Processing, and Storage Equipment to a third party. The plan shall identify all hardware and software (including firmware) information, GFE/GFP and equipment required to support all of the Network, Processing, and Storage Equipment. The transition plans shall address the turnover of all of the Network, Processing, and Storage Equipment databases (e.g. Environmental Safety and Occupational Health (ESOH) database and test hardware). Additionally, the end of contract transition plan shall address the supply support topics specified in this SOW.

Deliverable Data Item (See DD-1423):

CDRL A009: “Technical Report – Studies/Services: End of Contract Transition Plan”

3.2.11 Formal Proposals, Rough Orders of Magnitude (ROM), and Technical Instructions (TIs) (Applicable to all CLINs) Formal proposals for contract modifications shall be prepared and submitted only in response to requests received from the Contracting Officer. Contractor proposals shall include all costs, including material costs, technical costs and man-hour estimates, required to complete tasking provided via contract modifications. Incomplete or unknown information shall be identified within three (3) business days and concurrence obtained from the Contracting Officer, to preclude delays. (Man hour Estimates and Technical Cost Proposals, CDRL A010)

Deliverable Data Item (See DD-1423):

CDRL A010: “Man Hour Estimate and Technical Cost Proposals”

The Government may request Rough Orders of Magnitude (ROM) estimates in support of program efforts not included in the completion scope of this contract. Unless otherwise agreed to by the Government, ROM estimates shall be submitted within fifteen (15) calendar days of the request. Incomplete or unknown information shall be identified within three (3) business days and concurrence obtained from the Contracting Officer Representative (COR), to preclude delays. These ROM estimates are not contractually binding. Upon COR approval and signature of the ROM, the Contractor shall provide a TI that details the efforts associated with the work to be accomplished.

The Contractor must obtain written COR approval prior to expending any effort associated with the proposed TIs or proposed TI scope modifications.

3.3 MANUFACTURE, ASSEMBLY, AND TEST (Applicable to CLINs 0001, 0003-0009, 0011-0016, 1001, 1003-1016, 2001, 2003-2016, 3001, 3003-3016, 4001, 4003-4016. The Contractor shall build and deliver the Network, Processing and Storage Equipment in accordance with the Technical Data Packages (TDPs) and relevant specifications listed in Attachment J-3. Engineering changes or deviations shall be submitted for Government approval via the Configuration Management process by the Contractor. After the change is approved the TDP shall be updated by the Contractor and provided to the Government. The Government will provide the GFI (Attachment J-3) and the GFP listed in Section H, 5252.245-9109 GOVERNMENT-FURNISHED PROPERTY (INCORPORATION), 5252.245-9115 RENT-FREE USE OF GOVERNMENT PROPERTY and 5252.245-9108 GOVERNMENT-FURNISHED PROPERTY (PERFORMANCE).

For all CPS variants, all parts produced by Artesyn shall be assembled in USA, including but not limited to:

Foreign Military Sales (FMS): (CLINs 0002, 0010, 1002, 1010, 2002, 2010, 3002, 3010 4002 and 4010) The Contractor shall provide the following FMS units of the equipment variants as required below in separately identifiable contract modifications.

· FMS Water Cooled CCS - Processing Subsystem: Top Level Drawing – 8563369

The above FMS Water Cooled CCS cabinet shall be built and tested in a similar fashion to a fully configured CCS cabinet, top level drawing # 8563369 (CLINs 0001, 1001, 2001, 3001 and 4001) minus the components listed below that will be provided as GFE for test verification. Upon completion of System Burn-in Test (SBT) and Factory Acceptance Test (FAT) and verification of cabinets functionality, these components shall be removed prior to delivery and shall be reused for testing of the subsequent FMS Water Cooled CCS cabinets. There will be no separate TDP for the FMS Water Cooled CCS cabinets configuration. Dispositioning of GFE shall be in accordance with CDRL A009.

Item 1: 8563505 _ PROCESSING BLADE, ATCA, 7540 (Qty 12) Item 2: 8563503_ SOLID STATE DRIVE, KIT, INSTALLATION (Qty 12) Item 3: 8563502_ SOLID STATE DRIVE, NVME, 1TB (Qty 12)

3.3.1 Technical Data Package (TDP). (Applicable to CLINs 0001-0016, 1001-1016, 2001-2016, 3001-3016, 4001-4016). The applicable Networks, Processing and Storage Equipment Technical Data Packages (TDPs) and the associated Installation Control Drawings and Interface Control Documents are provided as GFI. The Contractor shall update and maintain the TDP and modeling files for each of the Network, Processing and Storage Equipment as a result of approved Engineering Change Proposals (ECPs) (CDRL B001-B003). The Contractor shall mark these CDRLs such that they require government approval. The TDP shall be “Build to Print” Production Level III and contain all data and information sufficient for a third party to manufacture all of the Networks, Processing and Storage Equipment. The TDP shall be delivered without any proprietary markings and, at a minimum, with Government Purpose Rights (GPR) as defined at DFARS 252.227-7013. Drawings and associated lists updated and created by the Contractor shall be developed and structured in accordance with ASME Y14.24M-1999. The Contractor shall incrementally deliver the updated TDP to the Government’s specified website and via DVD to the COR. To update and maintain the TDPs for: Water-Cooled CCS 8563369, Water-Cooled ASAN 8563368, Water-Cooled ALIS 8563367, Water-Cooled ACEGIO1 8563365, Water-Cooled ACEGIO2 8563366, Water-Cooled DiVDS 8563370 and Air-Cooled PS2 8601113-001, the Contractor must use the latest version of Solidworks that has had a service Pack 3 or higher release. The Contractor shall provide redlined drawings in the initial quarterly TDP delivery, immediately following a change occurs for Government approval prior to incorporation of final drawings. Upon Government approval of the redlined drawings, the Contractor shall deliver finalized drawings in the quarterly TDP delivery immediately following Government approval. The quarterly TDP deliveries shall include a summary of the drawings that changed since the previous delivery. (CDRL B001)

Deliverable Data Item (See DD-1423):

CDRL B001: “Technical Data Package”

The Installation Control Drawings (ICDs) and Interface Control Documents are provided as GFI. The Contractor shall update and maintain the Installation Control Drawings and Interface Control Documents – for both operator and maintainer, as required to define the mechanical mounting, cooling, electrical power, and the HSI footprint around the Network, Processing and Storage Equipment for both the operator and the maintainer. (CDRLs B002, B003)

Deliverable Data Item (See DD-1423):

CDRL B002: “Installation Control Drawings

Deliverable Data Item (See DD-1423):

CDRL B003: “Interface Control Documents (ICD)

The Contractor should use the latest copy of the production documentation provided as GFI. If Contractor identifies the specifications and associated documentation and drawings provided as GFI are inadequate to ensure system conformance and/or impact the Contractor’s ability to manufacture and assemble a component/item, the Contractor shall notify the Contracting Officer via the bidders question process.

3.3.2 Mission Critical Enclosure Qualification (CLIN 0001-0007, 1001-1007, 2001-2007, 3001-3007 and 4001-4007). The Mission Critical Enclosure (MCE) drawings will be included within the applicable cabinet TDP(s), which will be provided as GFI.

The CCS, ASAN, ALIS, ACEGIO and DiVDS units utilize the standard Mission Critical Enclosure (MCE) TYPE 74200700-107.

The Contractor shall qualify any MCE vendor that is not listed as a source on the TDP. Vendor qualification shall include production of a First Article Unit (FAU), a First Article Inspection (FAI), consisting of a Physical Configuration Audit (PCA) and a Function Configuration Audit (FCA), and a Production Readiness Review (PRR). During the PRR, the vendor shall demonstrate the ability to manufacture the MCE by providing various artifacts including, but not limited to, the Manufacturing, Inspection, Non-Destructive Test, Quality Assurance, and Configuration Management Plans. The Contractor shall submit FAI and PRR documentation to the Government for approval prior to each review. The FAI and PRR will be held at the vendor’s production facility and the Government reserves the right to participate. Final acceptance of the FAU will be conducted by the Government. The Contractor shall develop a Qualification Test Report (CDRL A011).

Deliverable Data Item (See DD-1423):

CDRL A011: “Qualification Test Report”

If the contractor proposes to make the MCE, it shall be subject to Government qualification under each CLIN for the following FAU builds: CCS, ASAN, ALIS, ACEGIO and DiVDS as described in SOW sections 3.4.1 and 3.4.2.

3.3.3 Factory Acceptance Test Plan. The Factory Acceptance Test (FAT) plan and procedures are delivered as GFI (provided with TDP, attachment J-2). The GFI includes the operating environment and license(s) required to conduct FAT. Included in the FAT documentation for all applicable Network, Processing and Storage Equipment (CLINs 0001-0024), will be a listing of all materials (hardware and software) required to successfully execute FAT. The Contractor shall update and maintain FAT Procedures (CDRL A012). The FAT shall be conducted at the Contractor’s facility. The Contractor shall provide Test/Inspection Reports (CDRL A013) for all acceptance tests.

Deliverable Data Item (See DD-1423):

CDRL A012: “Test Plans/Test Procedures: Factory Acceptance Test Procedures”

Deliverable Data Item (See DD-1423):

CDRL A013: “Test/Inspection Report: Factory Acceptance Test and System Burn-In Test”

The Contractor shall conduct the FAT and System Burn-in Test (SBT) on each Networks, Processing and Storage Equipment. The Contractor shall furnish all labor and materials necessary to conduct the FAT and System Burn-in Test (SBT) on each applicable Network, Processing and Storage Equipment other than the items provided by the Government as GFE/GFI/GFP “As identified in the FAT plan and procedures (provided with TDP, attachment J-2) or suitable alternatives, subject to Government approval. Specifically, bidders will be required to develop and document the Test Plan and Procedures for the following Conversion Group Tests in Section 4.3.7 of 3071593 MOD1 ACEGIO FAT Plan: VLP, DAP, GDP, BMS, and ATP. As well as, develop and docement the necessary Test Fixtures indicated in Section A2.3 of the same document and submit for NSWC, Dahlgren Division Design Agent Approval and Acceptance for incorporation into MOD1 source TDP. The SBT shall operate 72 hours error-free. FAT includes the functional, electrical, mechanical, and visual tests performed to verify that the Network, Processing and Storage Equipment is operational. The Contractor shall notify the Government at least fourteen (14) calendar days prior to commencement of FAT. The Government reserves the right to witness FAT.

In the event of a production test failure, the Test/Inspection Reports (CDRL A013) shall include the circumstances of the failure, identification of the equipment under test, the testing step conducted when the failure occurred, physical observations, meter readings (as applicable) and the corrective action taken to resolve the immediate failure and prevent future failures (i.e., replaced part, repaired cable, etc.). The report shall include an analysis of the test failure and corrective measures to be taken to prevent further test failures.

3.3.4 Software (CLINs 0001-0016, 1001-1016, 2001-2016, 3001-3016, and 4001-4016).

3.3.4.1 Software Support Documents

The Contractor shall develop and deliver a Firmware Support Manual (FSM). (CDRL A014)

Deliverable Data Item (See DD-1423):

CDRL A014: “Firmware Support Manual (FSM)”

3.3.4.2 Software Maintenance

The Contractor shall, update Network, Processing and Storage Equipment software to resolve production system software found not to meet the requirements of the SRDs or CIDS.

Software changes shall be processed in accordance with the Government approved Contractor’s CM Plan.

3.3.5 As-Built Configuration. The Contractor shall develop and deliver an As-Built Configuration List: Indentured Bill of Materials (CDRL A015) for each delivered item. The as-built list shall extend down to the Lowest Replaceable Unit (LRU) level including LRUs embedded in assemblies and be recorded in a Configuration Status Accounting database.

CDRL A015: “As Built Configuration List (ABCL): Indentured Bill of Materials”

3.3.6 Configuration Status Accounting.

The Contractor shall establish a Configuration Status Accounting (CSA) database to record and track status of CPS hardware and software. This database shall be established and functional prior to PRR. The Contractor shall provide the Government electronic access to this database throughout the term of the contract. The Contractor shall record the CSA data for each CPS system, including FAUs, in this database when each system is delivered. The CSA data shall be identified to the LRU level as defined in the TDP (CDRL A016).

Deliverable Data Item (See DD-1423):

CDRL…