18R0010_Solicitation.pdf

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot Design and Engineering

FFP

Base Year - Design the Sensor Interface Unit (SIU), design the SIU Tester, design, develop source code, integrate, test, document, and deliver system software and component firmware in accordance with SOW paragraph 3.2-3.6.7 and 3.9(CDRL A001, A002, A003)

FOB: Destination

PSC CD: 5998

NET AMT

0002 1 Lot Technical Data Package

FFP

The TDP shall include those items listed in Section 3.2. The TDP shall also include production representative drawings of production and peculiar test equipment.

(CDRL A004) SOW Paragraph 3.7

0003 4 Each First Articles

FFP

Fabricate and deliver four (4) first article SIUs for verification testing. (CDRL A005, A006); Factory Acceptance Test (CDRL A007, A008) and other testing in accordance with SOW Paragraph 3.8 &3.10

0004 1 Lot Travel

FFP

Travel Not-To-Exceed (NTE) $12,350.00 in support of CLIN 0001, 0002 and 0003. Base year only. No Fee shall be applied to the travel cost. Specific travel location and duration will be identified in individual delivery orders.

0005 10 Each Production Units

FFP

Base Year- Labor, Materials, and Delivery to fabricate the LCAC SIU's in accordance with the finalized TDP and. SOW paragraph 3.15.1

Contract Data Requirements List (CDRL)

Exhibit A, DD Form 1423-1 in accordance with Section C, Statement of Work

(SOW)

Not Separately Priced

1001 16 Each OPTION Production Units

FFP

Base Year- Labor, Materials, and Delivery to fabricate the LCAC SIU's in accordance with the finalized TDP and. SOW paragraph 3.15.1

2001 16 Each OPTION Production Units

FFP

Base Year- Labor, Materials, and Delivery to fabricate the LCAC SIU's in accordance with the finalized TDP and. SOW paragraph 3.15.1

3001 16 Each OPTION Production Units

FFP

Base Year- Labor, Materials, and Delivery to fabricate the LCAC SIU's in accordance with the finalized TDP and. SOW paragraph 3.15.1

4001 16 Each OPTION Production Units

FFP

Base Year- Labor, Materials, and Delivery to fabricate the LCAC SIU's in accordance with the finalized TDP and. SOW paragraph 3.15.1

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contract, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term "residual dollar amount" shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ B-2-0010 NOTE (OPTION)

NOTE B - Option item to which the option clause in SECTION I-2 applies and which is to be supplied only if and to the extent said option is exercised.

(End of Text)

HQ B-2-0020 TRAVEL COSTS – ALTERNATE I (NAVSEA) (APR 2015)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs determined to be allowable, allocable and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer or their duly authorized representative, as advised by DCAA.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

Section C - Descriptions and Specifications

HQ C-2-0009 ASSIGNMENT OF SERIAL NUMBER(S) (NAVSEA) (SEP 1990)

The Contractor shall request serial number assignment, in writing, from the Cognizant Technical Program Office, with a copy to the cognizant Contract Administration Office. The request for serial number assignment shall contain the following minimum information:

(a) Contract number;

(b) Assigned line item number and description;

(c) Assigned type designation;

(d) Assigned model number;

(e) Top drawing number and ID (List of Drawings) number;

(f) Exact quantity for which serial numbers are being requested, including preproduction samples required by the contract; and

(g) National Stock Number

HQ C-2-0014 CONTRACTOR'S PROPOSAL (NAVSEA) (MAR 2001)

(a) Performance of this contract by the Contractor shall be conducted and performed in accordance with detailed obligations to which the Contractor committed itself in Proposal dated in response to NAVSEA Solicitation No. N61331-18-R-0010.

(b) The technical volume(s) of the Contractor's proposal is incorporated by reference and hereby made subject to the provisions of the "ORDER OF PRECEDENCE" (FAR 52.215-8) clause of this contract. Under the "ORDER OF PRECEDENCE" clause, the technical volume of the Contractor's proposal referenced herein is hereby designated as item

(f) of the clause, following "the specification" in the order of precedence.

HQ C-2-0026 FIRST ARTICLE (CONTRACTOR TESTING) (NAVSEA) (SEP 1990)

(a) For the purpose of this contract, the "First Article" is synonymous with the terms "preproduction model(s) and "preproduction equipment".

(b) The First Article shall conform in every respect to the requirements of this contract and shall be fully tested by the Contractor at its own expense to determine compliance with said requirements. The production equipment shall be manufactured with tools, material and methods which are the same as or representative of the tools, material and methods which were used to manufacture the First Article.

(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.*

HQ C-2-0027 FIRST ARTICLE (GOVERNMENT TESTING) (NAVSEA) (SEP 1990)

(a) For the purpose of this contract, the "First Article" is synonymous with the terms "preproduction model(s)" and "preproduction equipment".

(b) The production equipment shall be manufactured with tools, materials and methods which are the same as, or representative of the tools, material and methods which were used to manufacture the First Article. The First Article shall not be delivered for first article approval tests as provided for in the clause of this contract entitled "FIRST ARTICLE APPROVAL--GOVERNMENT TESTING" (FAR 52.209-4) until after the Contractor has fully tested it, at its expense, to determine compliance with said requirements and it has been preliminarily accepted by the Contract Administration Office. The Contractor shall make a record of all data obtained during such tests in such form as is consonant with good engineering practice and furnish five (5) copies thereof. The cover sheet of each copy of this record shall be marked with this contract number and the item identification. One (1) copy shall be furnished to the Contract Administration Office at the time of inspection for preliminary acceptance, one (1) copy shall accompany the First Article on delivery thereof, and three (3) copies shall be furnished to the Naval Sea Systems Command at the time of First Article delivery.

(c) Pursuant to paragraph (e) of the clause entitled "FIRST ARTICLE APPROVAL--GOVERNMENT TESTING", the First Article shall not be delivered as part of the production quantity.

HQ C-2-0051 SPECIFICATIONS AND STANDARDS (NAVSEA) (AUG 1994)

(a) Definitions.

(i) A "zero-tier reference" is a specification, standard, or drawing that is cited in the contract (including its attachments).

(ii) A "first-tier reference" is either: (1) a specification, standard, or drawing cited in a zero-tier reference, or (2) a specification cited in a first-tier drawing.

(b) Requirements.

All zero-tier and first-tier references, as defined above, are mandatory for use. All lower tier references shall be used for guidance only.

HQ C-2-0059 UPDATING SPECIFICATIONS AND STANDARDS (NAVSEA) (AUG 1994)

If, during the performance of this or any other contract, the contractor believes that any contract contains outdated or different versions of any specifications or standards, the contractor may request that all of its contracts be updated to include the current version of the applicable specification or standard. Updating shall not affect the form, fit or function of any deliverable item or increase the cost/price of the item to the Government. The contractor should submit update requests to the Procuring Contracting Officer with copies to the Administrative Contracting Officer and cognizant program office representative for approval. The contractor shall perform the contract in accordance with the existing specifications and standards until notified of approval/disapproval by the Procuring Contracting Officer. Any approved alternate specifications or standards will be incorporated into the contract.

STATEMENT OF WORK

FOR THE

SENSOR INTERFACE UNIT (SIU)

1. SCOPE

The Naval Surface Warfare Center Panama City Division (NSWC PCD) Code E31, as the ISEA for the Landing Craft Air Cushion (LCAC) program, is tasked with the support of the LCAC Service Life Extension Program (SLEP) craft configuration. This requirement is for the design, fabrication, test, and delivery of LCAC Command, Control, Computers, Communications, and Navigation (C4N) Sensor Interface Units (SIU). The SIU is the required interface and aggregator for various craft sensors and transmits the data collected to the LCAC Control & Alarm Monitoring System (CAMS). The SIU sensors monitor critical operating machinery and craft transducers. It is the Government’s desire that currently designed solutions and Commercial Off-The- Shelf (COTS) products be utilized to meet this requirement as opposed to newly designed solutions. The craft configuration is designed to be outfitted with four identical SIUs per craft.

2. APPLICABLE DOCUMENTS

The following specifications, standards, and handbooks form a part of this SOW to the extent cited herein. All reference documents may be used for guidance unless otherwise specified within the body of this SOW. Guidance documents may be used as an aid in identifying applicable topics to be addressed consistent with meeting the requirements of the program. The Contractor is not required to use any document cited “for guidance” or “as guidance”.

In the event of conflict between the documents referenced herein and the contents of this SOW, the order of precedence clause of this contract shall apply. When, in the opinion of the Contractor, a deviation from standards or requirements of this SOW is in order, the Contractor shall make a request for deviation in writing to the Administrative Contracting Officer (ACO) with an information copy to the designated technical representative. The Government will notify the Contractor in writing of approval or disapproval, of the deviation, within thirty (30) days after receipt by the ACO.

2.1 Military Specifications and Standards

Number Title Date

MIL-STD-882E System Safety 11 May 2012

MIL-STD-31000A with Notice 1 Technical Data Packages 12-Dec-2017

2.2 Military Instructions

DODI 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems 27 Oct 2017

DODI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT) 28 July 2017

DOD 8570.01-M Information Assurance Workforce Improvement Program 10 Nov 2015

2.3 Other Government Documents

CDR-Checklist-FRM Critical Design Review (CDR) Entrance and Exit Criteria Feb 2016

LCAC-C4N-SPC-322

Specification for the LCAC SLEP Sensor Interface Unit (SIU) for the Landing Craft, Air Cushion (LCAC) Expeditionary C4N

Systems Branch

24 Apr 2018

MIL-HDBK-344A Environmental Stress Screening of Electronic Equipment 16 Aug 1993

NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations 22 Jan 2015

NIST SP 800-53A

Assessing Security and Privacy Controls in Federal Information Systems and

Organizations: Building Effective Assessment Plans

18 Dec 2014

PROC-2015-0011

System Baseline Configuration 4 (SBC4) Electromagnetic Interference/Environmental (EMI/ENV) Operational and Reference Test

Procedures for the Landing Craft, Air Cushion (LCAC) E31 Expeditionary Branch

1.0

SPEC-2018-0001

Specification for the LCAC SLEP Sensor Interface Unit (SIU) Tester for the Landing Craft, Air Cushion (LCAC) Expeditionary

C4N Systems Branch

11 May 2018

TRR-Checklist-FRM Test Readiness Review (TRR) Entrance and Exit Criteria Feb 2016

ISO 9001 Quality Management Systems - Requirements Sep 2015

ASTM-D3951 Packaging, Commercial 21 Dec 1990

NOTE: Military Specifications, Standards, Handbooks, and Data Item Descriptions are available from:

https://assist.dla.mil/online/start/. Requests for the specifications LCAC-C4N-SPC-322, SPEC-2018-0001, PROC-2015-0011, CDR-Checklist-FRM, and TRR-Checklist-FRM can only be made available to U.S. DoD contractors (distribution limited) upon request to the Contracting Office.

3. REQUIREMENTS

3.1 General

The work required by this contract shall be performed in accordance with LCAC-C4N-SPC-322, SPEC-2018-0001, and this SOW. In the event of a conflict or contradiction between LCAC-C4N-SPC-322 and this SOW, LCAC-C4N- SPC-322 shall have precedence. In the event of a conflict or contradiction between SPEC-2018-0001 and this SOW, SPEC-2018-0001 shall have precedence.

The Contractor shall plan, design, develop, fabricate, integrate, and test the Sensor Interface Unit to meet the requirements of LCAC-C4N-SPC-322, SPEC-2018-0001, and the detailed requirements in this SOW.

3.2 Design and Engineering

3.2.1 The Contractor shall design the Sensor Interface Unit (SIU) in accordance with specification LCAC-C4N-

SPC-322.

3.2.2 The Contractor shall design the SIU Tester in accordance with specification SPEC-2018-0001.

3.2.3 The Contractor shall design, develop source code, integrate, test, document, and deliver system software and component firmware for the configuration end item. Whenever possible, the contractor shall utilize software, hardware, or firmware that has already been designed, developed, coded, tested, and released. The cost of reutilizing hardware, software, or firmware (such as licenses) shall be included in the unit cost of the item or CDRL it is associated with. All software and firmware delivered as part of this contract shall include all source materials, including source code, source documentation, build-environment documentation, and licenses sufficient for the Government to be able to modify and/or reproduce the software executables.

(CDRL A001)

3.2.4 The Contractor shall prepare/update a Version Description Document (VDD) for the Computer Software

Configuration Items (CSCIs) and firmware provided under this product. (CDRL A002)

3.2.5 The Contractor shall ensure design reproducibility throughout the lifecycle of the product by using cost effective and reproducible methods, processes, and material for manufacturing the equipment to meet performance and cost objectives.

3.2.6 Reliability (CDRL A003)

• The Contractor shall calculate Mean Time Between Failure (MBTF) and provide to the Government.

• The Contractor shall calculate Mean Time To Repair (MTTR) and provide those to the Government.

• The Contractor shall perform a Fault Tree Analysis for the final product.

• The Contractor shall create a failure modes effects and criticality analysis for the configuration end-item.

• The Contractor shall calculate the reliability and maintainability metrics of the SIU in accordance with standard industry practices.

3.2.7 The use of special test or diagnostic equipment shall be minimized. The need for, description of, and planned execution of any special test or diagnostic equipment shall be presented at the Critical Design Review, Section 3.9.3, for approval by the Government or rejection for rework. If any diagnostic equipment is approved by the Government, it shall be demonstrated to the Government at NSWC PCD during the First Article Acceptance Testing (FAAT), and procedures shall be documented in the Operations User’s Manual.

The Contractor shall include the special test and diagnostic equipment as part of the TDP.

3.3 General Cybersecurity Requirements

3.3.1 The Contractor shall deliver an authorizable system in accordance with DoD Instruction 8510.01, Risk

Management Framework (RMF) for DoD Information Technology (IT).

3.3.2 The Contractor shall develop, document, configuration manage, and deliver a system compliant with the appropriate National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53A assessment procedures and the NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations, for the Government to obtain a Risk Management Framework (RMF) authorization IAW DoDI 8510.01.

3.3.3 The Contractor shall practice software assurance including static source code analysis on organic and third party open source software to mitigate software vulnerabilities during development.

3.3.4 The contractor shall ensure that each baseline and subsequent software builds are free from malicious code.

3.3.5 The Contractor shall ensure that for each software baseline and subsequent software builds, the Contractor’s software development environment incorporates updated Anti-Virus definitions that are current to within 30 days from the end of development.

3.3.6 The Contractor shall ensure that any embedded systems or solutions that only implement software via firmware are scanned with the most current Anti-Virus scanning tool(s) prior to delivery.

3.3.7 The contractor shall harden any COTS Operating Systems (OS) utilized using the applicable Defense

Information Systems Agency (DISA) Security Requirements Guide (SRG) or Security Technical Implementation Guide (STIG) and their associated DISA development tools which can be found at http://iase.disa.mil/.

3.3.8 The Contractor shall implement ports, protocols, and services in accordance with DODI 8551.1 and uninstall or disable ports, protocols, applications and services which are not used.

3.3.9 The Contractor shall comply with all current DoD and DISA standards and requirements for acceptable

Ports, Protocols, and Services. Any request for exception to these requirements must be made through the Project Manager to the AO.

3.3.10 The Contractor shall generate a list of ports, protocols, and services that are being used. (CDRL A022)

3.3.11 “Administrative” accounts, for use by the system administrator for System software upgrades and maintenance, shall be password protected. Administrative passwords shall be a minimum length of 15 characters and consists of a mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each.

3.3.12 The Contractor shall ensure that all factory-set or default firmware passwords are changed prior to delivery of the System. Each password shall be a minimum length of 15 characters and consists of a mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each. Each password shall be protected such that they are not embedded in access scripts or stored on function keys.

The architecture shall be designed to enable future growth with reasonable additional cost so that with Government concurrence, the password complexity can be modified as necessary. The Government understands that any additional work resulting from a changed requirement must have sufficient contract resourcing.

3.3.13 The Contractor shall evaluate ALL currently available DISA Security Technical Implementation Guides

(STIGs), Security Checklists, and Security Requirements Guides (SRGs) (available at http://iase.disa.mil/) for system applicability.

3.3.14 The Contractor shall provide a list of those STIGs deemed applicable along with justification for those determined to be Not Applicable for Government concurrence. (CDRL A023)

3.3.15 The Contractor shall implement the Government approved list of STIGs to the extent possible without adversely affecting system development or operational performance.

http://iase.disa.mil/ http://iase.disa.mil/

3.3.16 The Contractor shall ensure assets under development have ALL applicable electronic patches for the system installed when the system is delivered to the Government.

3.3.17 The Contractor shall maintain any development environments in accordance with cybersecurity best practices and operational requirements. During product development for the Government, the Contractor shall ensure that all cybersecurity mitigation strategies have been applied to the development environment prior to any Government data being loaded onto any assets or software for testing or delivery.

• Cybersecurity mitigation strategies include security updates, service packs, and changes to operating procedures as physical and cyber vulnerabilities are detected. Operating system, routers, servers, development platforms, and the application being delivered to the Government shall comply with all known applicable Department of Defense Computer Emergency Response Team (DoD-CERT) Alert, Bulletin, and Technical Advisory Notices published during the past 36 months.

3.3.18 The Contractor shall assist the Government by preparing RMF documentation and perform the vulnerability testing necessary to assess and authorize the system IAW the RMF.

3.3.19 The Contractor shall employ the tenets of defense-in-depth for laying cybersecurity solutions within a given

IT asset and among assets; and ensuring appropriate robustness of the solution, as determined by the relative strength of the mechanism and the confidence that it is implemented and will perform as intended.

Additional guidance can be found in the Navy Information Assurance Technical Authority (IA TA) Defense-in-Depth Functional Implementation Architecture (DFIA) Standard.

3.3.20 The Contractor shall establish appropriate administrative, technical, and physicals safeguards to protect any and all Government systems and data, to ensure the confidentiality, integrity, availability, authentication, and non-repudiation of Government data. As a minimum, this shall include provisions for personnel security, electronic security, and physical security.

3.4 Platform Information Technology

3.4.1 The Contractor shall provide objective quality evidence for submittal to the appropriate Authorizing Official as required by published DON CIO Platform IT Policy and NAVSEA PIT-Control Systems Cybersecurity Governance and Guidance.

3.5 Cybersecurity Contractor Training and Certification

3.5.1 The Contractor shall ensure that personnel who are categorized as working within DoD IA Workforce meet the appropriate requirements of DoD 8570.01-M.

3.6 Supply Chain Safeguards for Systems Engineering

3.6.1 In addition to the components a program determines are critical for other reasons (e.g., safety critical), the Contractor shall identify the mission-critical functions that may result in Level I or Level II protection failures due to operational, system information, or component integrity aspects.

3.6.2 Adapting the MIL-STD-882E System Safety Program definitions of criticality to mission criticality the contractor shall define the following criticality levels:

• Level I (Catastrophic) protection failure – a failure that results in total compromise of mission capability which may cause unintended loss of system.

• Level II (Critical) protection failure – a failure that results in unacceptable compromise of mission capability or significant mission degradation which may cause significant system damage.

• Level III (Marginal) protection failure – a failure that results in partial compromise of mission capability or partial mission degradation.

• Level IV (Negligible) protection failure – a failure that results in little or no compromise of mission capability.

3.6.3 For each Level I and Level II mission-critical function identified by the Contractor in the criticality analysis, the contractor shall identify the associated logic-bearing system components that implement, or introduce vulnerability to these functions (hereafter referred to collectively as the “critical components”). (CDRL A024)

3.6.4 The Contractor shall demonstrate that the Contractor has visibility into its supply chain for critical components, understands the risks to that supply chain, and has implemented or plans to implement risk mitigations to counter those risks.

3.6.5 The Contractor shall plan for the reduction of foreign intelligence, technology exploitation, supply chain and battlefield threats, and system vulnerabilities that result in the catastrophic (Level I) and critical (Level II) protection failures, including:

1. The application of supply chain risk management best practices, applied as appropriate to the development of the system. Supply chain risk management key practices may be found in the NIST Interagency Report 7622, Piloting Supply Chain Risk Management for Federal Information Systems, and the National Defense Industrial Association Guidebook, Engineering for System Assurance, both publicly available.

2. The enumeration of potential suppliers of critical components, as they are identified, including cost, schedule, and performance information relevant for choice among alternatives and planned selection for the purpose of engaging with the government to develop mutually-agreeable risk management plans for the suppliers to be solicited.

3. The processes to control access by foreign nationals to program information, including, but not limited to, system design information, DoD-unique technology, and software or hardware used to integrate commercial technology.

4. The processes and practices employed to ensure that genuine information and communications technology (ICT) will be employed in the solution and that processes and requirements for genuine ICT are levied upon subcontractors.

5. The process used to protect unclassified DoD information in the development environment.

3.6.6 The provisions of SOW paragraph 3.6.1 and SOW paragraph 3.6.4 shall be included in the solicitations and subcontracts for all suppliers, suitably modified to identify the parties.

3.6.7 The Contractor shall ensure that updated criticality analysis assumptions, rationale, results, and supply chain risk information and mitigations are made available for Government review for each Systems Engineering Technical Review (SETR).

3.7 Technical Data Package (CDRL A004)

The Contract shall develop a production level TDP in accordance with the requirements of MIL-STD-31000A. The TDP shall include those items listed in Section 3.2. The TDP shall also include production representative drawings of production and peculiar test equipment (i.e. alignment fixtures, test fixtures, and special tooling); Version Description Document(s) (VDD); Failure Modes, Effects, and Criticality (FMECA) assessment; Firmware or Software Installation Procedures; Master Parts List (PL) with estimated component costs and weights; component information sanitization procedures; and component removal procedures. Drawings that are considered NDI and COTS shall be documented on vendor item drawings.

3.8 Fabrication

The Contractor shall fabricate the Sensor Interface Unit in accordance with the technical data package as developed under this statement of work.

3.8.1 First Article (CDRL A005, A006)

The Contractor shall deliver four (4) first article SIUs for verification testing. The First Article shall be produced in a manner that is representative of the manufacturing process and capability that will be used for the life of the order. The Contractor shall conduct the first article test on units in accordance with LCAC- C4N-SPC-322 prior to delivery using the provided SIU Tester as Government Furnished Equipment (GFE) and the newly developed SIU Tester. The Contractor shall document the First Article test results.

The Contractor shall not proceed with fabrication of the remaining items until first article approval is obtained in writing from the Procuring Contracting Officer (PCO). The Contractor shall be responsible for retesting the First Article for any failure to meet the requirements of LCAC-C4N-SPC-322. The Contractor shall inform the Government of any planned process or material changes for the production of the remaining articles prior to coordinating the First Article Testing.

Any effort by the Contractor to enter into production prior to acceptance of the preproduction unit shall be solely at the risk of the Contractor.

3.8.2 Factory Acceptance (CDRL A007, A008)

The Contractor shall conduct Factory Acceptance Tests on all units, including the First Article units, in accordance with the requirements contained in drawings and specifications listed in the Technical Data Packages and in accordance with the Contractor’s Factory Acceptance Test Plan. The Contractor shall not commence testing until the test plan is approved by the Government. The Government reserves the right to inspect the Contractor’s test equipment as part of the Government’s approval of the test plan. The Government reserves the right to independently test the First Article units (requirements contained in drawings and specifications listed in the Technical Data Packages) or witness the tests conducted by the Contractor. The Contractor shall prepare a Factory Acceptance Test Report which shall include appendices, personal notes, test analyses, error analyses, confidence levels, and all computerized data collection and reduction results.

3.8.3 Physical Configuration Audit and Functional Configuration Audit (CDRL A009) The Government will perform a PCA and FCA on first article samples provided by the Contractor. The Contractor shall develop a PCA/FCA Plan and provide the necessary hardware, inspection and workspace facilities, personnel, documentation, and other support to conduct the PCA/FCA. In addition, the Contractor shall submit the PCA/FCA Plan to the Government for approval. The audit team will consist of Government and Contractor personnel and will be chaired by the Government procuring activity project engineer or his designated representative. The Government co-chairmen shall have the authority to accept or reject the item if a discrepancy is found. The audit shall require complete disassembly of the Device and shall be conducted by visual and physical inspection, electrical inspection, and review of certification and inspection records.

Any observed difference between the components or materials and the approved baseline shall be considered a discrepancy. The audit team shall fully document the reasons for any discrepancy. In the event the audit should incidentally disclose a workmanship problem as opposed to a difference between the component and the Approved Baseline, the discrepancy shall be referred to the Contracting Officer. The contractor shall be responsible for providing a response to all discrepancies found during the audit. The audit response shall include resolutions to all audit findings. The item will be considered validated upon completion of the audit and upon the mutually agreeable resolution of discrepancies revealed and documented in the audit findings during the audit.

3.8.4 Certificate Of Conformance (CDRL A010)

(a) When authorized in writing by the cognizant Contract Administration Office (CAO), the Contractor shall ship with a Certificate of Conformance any supplies for which the contract would otherwise require inspection at source. In no case shall the Government’s right to inspect supplies under the inspection provisions of this contract be prejudiced. Shipments of such supplies will not be made under this contract until use of the Certificate of Conformance has been authorized in writing by the CAO, or inspection and acceptance have occurred.

(b) The Contractor’s signed certificate shall be attached to or included on the top copy of the inspection or receiving report distributed to the payment office or attached to the CAO copy when contract administration (Block 10 of the DD Form 250) is performed by the Defense Contract Administration Services. In addition, a copy of the signed certificate shall also be attached to or entered on copies of the inspection or receiving report accompanying the shipment.

(c) The Government has the right to reject defective supplies or services within a reasonable time after delivery by written notification to the Contractor. The Contractor shall in such event promptly replace, correct, or repair the rejected supplies or services at the Contractor’s expense.

(d) The certificate shall read as follows:

‘‘I certify that on __________ [insert date], the __________ [insert Contractor’s name] furnished the supplies or services called for by Contract No. __________ via __________ [Carrier] on __________ [identify the bill of lading or shipping document] in accordance with all applicable requirements. I further certify that the supplies or services are of the quality specified and conform in all respects with the contract requirements, including specifications, drawings, preservation, packaging, packing, marking requirements, and physical item identification (part number), and are in the quantity shown on this or on the attached acceptance document.’’

Date of Execution: _______________________________ Signature: ______________________________________ Title: _________________________________________

3.9 Reviews

3.9.1 Kick Off Meeting (CDRL A011, A012)

The Contractor shall conduct a Kick-off Meeting within twenty (20) working days after contract award at the contractor’s facility to discuss the specific requirements of the contract. At this meeting the discussion shall address issues and concerns held by the Contractor and program schedule shall be presented.

3.9.2 Technical Interchange Meetings

The Contractor shall conduct Technical Interchange Meetings and Teleconferences (TIMs) to provide the Government with additional insight into the technical aspects of the program and to provide a forum to resolve technical issues. The Contractor shall conduct these conferences monthly with additional conferences performed as needed, via teleconference (audio or video), between the Government and the contractor. The Contractor shall notify the Government of a scheduled teleconference a minimum of three

(3) working days prior to the meeting.

3.9.3 Critical Design Review (CDRL A013, A014)

The Contractor shall conduct a Critical Design Review (CDR) at their location within 80 working days after contract award, which will be chaired by the Government and supported by the contractor. This CDR shall be conducted following the completion of at least 80% of the TDP. The DR Entrance and Exit criteria shall be as detailed in CDR-Checklist-FRM.

3.9.4 Test Readiness Review (CDRL A013, A014)

The Contactor shall conduct a Test Readiness Review (TRR) prior to the start of contractor testing on the first article units at its facilities (or subsequent out-sourced laboratory facilities if utilized). The TRR shall be within 120 working days after contract award. The Government will chair the TRR, and reserves the right to witness all testing, either performed by the contractor, or its subcontractors, initiated and performed after TRR. The TRR Entrance and Exit criteria shall be as detailed in TRR-Checklist-FRM.

3.10 Testing

3.10.1 Contractor Integration Testing (CDRL A007, A008)

The Contractor shall perform the integration of the First Article units in the Government’s LCAC C4N System Integration Lab (SIL). Government personnel will be made available to answer questions during the contractor’s integration efforts. Once integration is complete, the contractor shall perform contractor test and check out of the units in accordance with its SIU TP. SIL testing shall be performed prior to LCAC craft testing of the SIU to ensure the craft is not damaged by the installation of the SIU.

The Contractor shall perform the integration of the First Article units on a LCAC at the Government’s facilities. Government personnel will be made available to answer questions during the Contractor’s integration efforts. Once integration is complete, the contractor shall perform contractor test and check out of the units in accordance with its SIU TP and acceptance test procedures on the first articles.

3.10.2 Government Acceptance Testing

The Government will perform Government Acceptance Testing (GAT) on a LCAC after contractor integration testing and checkout has been successfully completed on the first article units. The Government will document any failures that occur during Government Acceptance Testing and supply them to the contractor for immediate remediation. The Government will either approve or disapprove the First Article within five (5) working days after completion of the GAT.

3.11 Program Management (CDRL A017)

The Contractor shall maintain and implement a management program that clearly defines how the effort will be managed and controlled. The Contractor shall organize, coordinate, execute and control all internal project activities related to the fabrication effort (including those that are assigned to subcontractors to ensure the correct and timely delivery of all supplies and services specified in this contract. The Contractor shall conduct planning for the effective management of the program to include the management structure for orderly, controlled, and efficient execution of this contract and potential follow-on implementation of any contract options. The planning data shall provide a description of the Contractor's management structure, organizational responsibilities, system development approach and Government interfaces needed in the execution of this contract.

3.11.1 Risk Management and Reporting (CDRL A015)

The Contractor shall maintain a risk management program to assess the risks associated with program cost, schedule, and achievement of technical requirements. Specific risk management functions shall include, at a minimum:

• Identify known and potential risks

• Assess risks, including a relative ranking by program impact, and establish critical thresholds

• Define methods or alternatives to mitigate or minimize these risks, including the identification of criteria upon which a programmatic decision must be made to initiate alternatives or make other programmatic changes

If a risk identified is projected to exceed a critical threshold impacting program cost, schedule, or achievement of technical requirements, the Contractor shall immediately report said risk, mitigation plan, and alternatives and shall seek Government approval and direction.

3.11.2 Integrated Master Schedule (CDRL A016)

The Contractor shall develop the overall program schedule for program control, status monitoring, and reporting purposes. The program schedule shall identify major tasks and efforts with associated timeframes needed to execute the contract. The program schedule shall include all Contract Data Requirements List (CDRL) items (data deliverables) and will be the single place where due dates are tracked. The program schedule shall be developed using a "roll-up" scheme from lower-level (more detailed) schedules. The program schedule shall include appropriate task constraints and sequencing to support Critical Path Method (CPM) analysis and display. The program schedule shall be developed with software fully compatible with Microsoft Project for Windows.

3.12 Configuration Management (CM)

The Contractor shall maintain configuration control of the SIU during design, development, and production. The Contractor shall implement configuration status accounting and maintain records of the configuration available for review by the Government upon request.

3.13 Quality Assurance (CDRL A021)

The Contractor shall provide and maintain a Quality Management System (QMS) that meets the requirements of ISO 9001:2015. The Contractor shall submit a Quality Assurance Program Plan (QAPP) to the COR within 30 days after award that documents the quality system procedures, planning, and all other documentation and data that comprise the QMS for Government review and approval. The QAPP shall identify the means by which the Contractor will ensure quality system effectiveness and demonstrate comprehensive management and review of their process data, to identify trends and progress in quality of services and data products provided. The QAPP shall describe what is measured, how often it is tracked, and who reviews and assures that appropriate action is initiated when trends are unfavorable. The Government may perform inspections, validations, verifications and/or evaluations deemed necessary to asce1tain conformance and compliance to the requirements and adequacy of the implemented procedures.

The Government reserves the right to disapprove the QMS or portions thereof when it fails to meet its contractual requirements. The supplier shall require a QMS of its sub-tier suppliers to ensure control of quality of the services and data products or supplies provided.

3.14 Logistics

3.14.1 Operations and Maintenance Manual (CDRL A018)

The Contractor shall provide and deliver an Operations and Maintenance Manual, which can be combined with other manuals required under this contract.

3.14.2 Spares Identification and Support (CDRL A019)

The Contractor shall perform the necessary analysis to identify and recommend spare/repair parts to meet system/equipment operation and supportability for the end-item. This data shall be submitted with the TDP. The Contractor shall analyze and identify recommended spares and initial spares requirements.

The Contractor shall provide and deliver provisioning data for new and modified items.

As a goal, all replacement parts recommended after the approval of the TDP shall be fully Form, Fit, Function Interchangeable (F3I) with the current system at the Organization level. The contractor shall provide the Government visibility into all replacement parts. Replacement parts shall be reviewed at program TIMs.

3.14.3 Unique Identification (UID) (CDRL A020)

The Contractor shall perform UID in accordance with a contractor developed IUID Plan and LCAC- C4N-SPC-322 Section 3.4.

3.14.4 Packaging, Handling, Storage, and Transportation (PHS&T)

The Contractor shall package all deliverable end items for damage free transportation and storage in accordance with ASTM-D3951. Packaging shall handle all in-transit shock when shipped by truck, rail or air. Delivery of initial production units parts will be to:

Receiving Office Naval Support Activity (NSA) Panama City Receiving Office, Bldg 100 ATTN: Rose Larry Code E31 100 Vernon Ave Panama City, FL 32407

Delivery of follow-on production units may be to NSA Panama City or one of the following and will be determined when the option is exercised:

Naval Beach Unit 7 Defense Distribution Depot Yokosuka DET Sasebo Code DDYJ-J3S Bldg# 138 Muranchi Tategami-Cho, Sasebo-Chi, Nagasaki-Ken Sasebo City, JP 857-0063

M/F: R57078 ATTN: NBU7 Receiving Officer Commercial Number 011-81-956-50-4602

Assault Craft Unit Five (ACU5) Marine Corps Base Bldg 31916 Camp Pendleton, CA 92055-5161

Assault Craft Unit Four (ACU4) 2155 11th Street Virginia Beach, VA 23459-3018

3.14.5 Crew and Maintenance Training

The Contractor shall support an operations and maintenance demonstration prior to Government Acceptance Testing at the Government’s location in Panama City, Florida. The Contractor shall provide one (1) maintenance and operations training session consisting of two (2) days utilizing the Government approved training materials. The training session will occur at the Government’s facility in Panama City, Florida, on the first article units after GAT is accomplished.

3.15 Production

3.15.1 Initial Production

The Contractor shall produce ten (10) production units according to the finalized TDP after acceptance of the SIU by the government following Government Acceptance Testing.

3.15.2 Follow-On Production

The Contractor shall produce up to sixteen (16) production units in accordance with the finalized TDP each year for four option years following the initial production delivery.

4. GOVERNMENT FURNISHED PROPERTY (GFP)

4.1 Government Furnished Material (GFM):

None

4.2 Government Furnished Equipment (GFE):

Nomenclature Part Number Quantity

Test Set Interface 51-17840-003 1

NOTE: GFE shall be provided with existing manuals and software necessary for its operation.

4.3 Government Furnished Information (GFI):

None

5. CONTRACTOR INFORMATION SYSTEM SECURITY

This requirement shall require the Contractor to access classified information up to the SECRET level to support testing onboard the LCAC at a Government Facility. The Contractor shall not be required to receive, store, or generate classified information at the Contractor Facility. The work to be performed related to the SIU involves access to and handling of Controlled Unclassified Information (CUI).

RELEASE OF INFORMATION

(a) Release of information shall be in accordance with Section I, DFARS Clause 252.204-7000, Disclosure of Information.

(b) All technical data provided to the contractor by the Government shall be protected from public disclosure in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the appropriate NSWC PCD authority. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. The contractor shall provide adequate physical protection to such information to preclude access by any person or entity not authorized such access by the Government.

5.1 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

5.2 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Prior to access, Contractor personnel requiring access to Department of the Navy (DoN) controlled unclassified information (CUI) or "user level access to DoN or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DoN Central Adjudication Facility.

5.3 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides and unclassified limited documents (e.g., For Official Use Only (FOUO), Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

5.4 For Official Use Only (FOUO)

FOUO is a document designation, not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the Freedom of Information Act (FOIA). This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. FOUO must be marked, controlled and safeguarded in accordance with DoDM 5200.01, Vol. 4, DoD Information Security Program: Controlled Unclassified Information (CUI), February 24, 2012

5.5 Security of Unclassified DoD Information on Non-DoD Information Systems (DoDI 8582.01) DoD Policy

Adequate security shall be provided for all unclassified DoD information on non-DoD information systems.

Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.

Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information…