LCAC_SIU_SOW-DRAFT.pdf

27 June 2018

STATEMENT OF WORK

FOR THE

SENSOR INTERFACE UNIT (SIU)

1.0 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.0 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-31000A Technical Data Packages 26 Feb 2013

2.2 Other Government Documents

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

16 Aug 1993

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

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

AS 9100D Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations

September 2016

PDR-Checklist-FRM Preliminary Design Review (PDR) Entrance and Exit Criteria

Feb 2016

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

Feb 2016

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

Feb 2016

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

https://assist.dla.mil/online/start/. The specifications LCAC-C4N-SPC-322 and SPEC-2018-0001 and checklists, PDR- Checklist-FRM, CDR-Checklist-FRM, and TRR-Checklist-FRM are provided with the Request for Proposal (RFP).

3.0 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 Software Version Description Document (SVD) 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.5.4, 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 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 also include production representative drawings of production and peculiar test equipment (i.e. alignment fixtures, test fixtures, and special tooling). Drawings that are considered NDI and COTS shall be documented on vendor item drawings

3.4 Fabrication

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

3.4.1 First Article (CDRL A005, A006)

The Contractor shall deliver eight (8) 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 four (4) 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.4.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.4.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.4.4 Certificate Of Conformance (CDRL A010)

(a) When authorized in writing by the cognizant Contract Administration Office (CAO), the Contractor shall ship any supplies with a Certificate of Conformance 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.5 Meetings and Reviews

3.5.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.5.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.5.3 Preliminary Design Review (CDRL A013, A014)

The Contractor shall conduct a Preliminary Design Review (PDR) at their location within 40 working days after contract award, which will be chaired by the Government and supported by the Contractor. This PDR shall be conducted following the completion of approximately 30% of the Technical Data Package (TDP). The PDR Entrance and Exit criteria shall be as detailed in PDR-Checklist-FRM.

3.5.4 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.5.5 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.6 Testing

3.6.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.6.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.7 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.7.1 Risk Management and Reporting (CDRL A016)

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.7.2 Integrated Master Schedule (CDRL A015)

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.8 Logistics

3.8.1 Operations and Maintenance Manual (CDRL A018)

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

3.8.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 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.8.3 Unique Identification (UID) (CDRL A020)

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

3.8.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 all parts may be to one of the following locations:

Receiving Office Naval Support Activity (NSA) Panama City Receiving Office Bldg 100 MARKED ATTN: ROSE LARRY CODE E31 100 Vernon Ave Panama City, FL 32407

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

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

3.8.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.9 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.10 Quality Assurance (CDRL A021)

The Contractor shall provide and maintain a Quality Management System (QMS) that meets the requirements of AS 9100D.

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.

4.0 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.0 SECURITY

This requirement will require the Contractor to access classified information up to the SECRET level to support testing onboard the LCAC. The Contractor will not be required to generate or store classified information.

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.

IT-1 DUTIES: Contractor employees whose duties require them to be designated as an IT-I, (e.g., member of the Cyber Security Workforce and designation as an IAT2 or IAT3, or an IAM) require Top Secret eligibility.

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 systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.

Information Safeguards

Unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

a. Non-public information provided to a Contractor (e.g., with a request for proposal).

b. Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

c. Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non- DoD information system. However, all unclassified DoD information in the possession or control of non-DoD entities on non- DoD information systems shall minimally be safeguarded as follows:

a. Do not process unclassified DoD information on publically available computers (e.g., those available for use by the general public in kiosks or hotel business centers).

b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

c. At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the Contractor or teaming partner.

e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

f. Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment.

Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security.

g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

i. Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of transport layer security or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).

j. Provide protection against computer network intrusions and data exfiltration, minimally including:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

(2) Monitoring and control of both inbound and outbound network traffic (e.g., at the external boundary, sub-networks, individual hosts), including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. Prompt application of security-relevant software patches, service packs, and hot fixes.

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, Critical Program Information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

m. Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

5.6 Operations Security

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.

Critical information includes information regarding:

- Operations, missions, and exercises, test schedules or locations;

- Location/movement of sensitive information, equipment, or facilities;

- Force structure and readiness (e.g., recall rosters);

- Capabilities, vulnerabilities, limitations, security weaknesses;

- Intrusions/attacks of DoD networks or information systems;

- Network (and system) user identifications and passwords;

- Movements of key personnel or visitors (itineraries, agendas, etc.); and

- Security classification of equipment, systems, operations, etc.

The Contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

- Practice OPSEC and facilitate OPSEC awareness;

- Immediately retrieve documents from printers assessable by the public;

- Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

- Protect information from personnel without a need-to-know;

- When promulgating information, limit details to that essential for legitimacy;

- During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

6.0 DISTRIBUTION LIMITATION STATEMENT

Technical documents generated under this order shall carry the following distribution limitation statement. Word processing files shall have the statements included in the file such that the first page of any resultant hard copy shall display the statements. Additionally, each diskette delivered shall be marked externally with the statements.

DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO DEPARTMENT OF DEFENSE AND U.S.

DOD CONTRACTORS ONLY; CRITICAL TECHNOLOGY; 31 MARCH 2009. OTHER U.S. REQUESTS SHALL

BE REFERRED TO PEO SHIPS AMPHIBIOUS WARFARE PROGRAM OFFICE (PMS 377)

WARNING - THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS RESTRICTED BY THE ARMS EXPORT CONTROL ACT (TITLE 22, U.S.C., SEC 2751, ET SEQ.) OR THE EXPORT ADMINISTRATION ACT OF 1979 (TITLE 50, U.S.C., APP. 2401 ET SEQ.), AS AMENDED. VIOLATIONS OF THESE EXPORT LAWS ARE SUBJECT TO SEVERE CRIMINAL PENALTIES. DISSEMINATE IN ACCORDANCE WITH PROVISIONS OF DOD DIRECTIVE 5230.25., WITHHOLDING OF UNCLASSIFIED TECHNICAL DATA FROM RELEASE.

DESTRUCTION NOTICE – CLASSIFIED INFORMATION, DESTROY IN ACCORDANCE WITH SECNAV M-

5510.36, DON INFORMATION SECURITY PROGRAM OR DOD 5220.22-M, NATIONAL INDUSTRIAL

SECURITY PROGRAM OPERATING MANUAL. CONTROLLED UNCLASSIFIED INFORMATION (CUI), (E.G., FOUO, DISTRIBUTION STATEMENT CONTROLLED) DESTROY BY ANY METHODS THAT WILL PREVENT

DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT.

APPENDIX A - ACRONYMS

LIST OF ACRONYMS

A ACO Administrative Contracting Officer ACSN Advance Change Study Notice ADC After Date of Contract ADV RIC Advanced Resource/Repairable Identification Code

AFATA After First Article Test Approval ANSI American National Standards Institute ANSI ASC American National Standards Institute Accredited Standard Committee ASME American Society of Mechanical Engineers ASQ American Society for Quality ASTM American Society for Testing and Materials ATE Automatic Test Equipment

B BIT Built-in-Test BITE Built-In-Test Equipment

C CAIV Cost As an Independent Variable CAGE Commercial and Government Entity CDRL Contract Data Requirements List CI Configuration Item CID Component Identification Data CM Configuration Management CMP Configuration Management Plan CNO Chief of Naval Operations CPM Critical Path Method CSA Configuration Status Accounting

D DCN Design Change Notice

DD Form 254 Contract Security Guide DoD Department of Defense DoDI Department of Defense Instruction DoDISS Department of Defense Index of Specifications and Standards DWG Drawing

E

E3 Electromagnetic Environmental Effects EC/EDI Electronic Commerce/Electronic Data Interchange ECP Engineering Change Proposal EIA Electronic Industries Alliance E-mail Electronic Mail EMC Electromagnetic Compatibility EMI Electromagnetic Interference EMS Electromagnetic Susceptibility EMV Electromagnetic Vulnerability ESD Electrostatic Discharge

F FAAT First Article Acceptance Testing

FAT Factory Acceptance Testing Fax Facsimile FRACAS Failure Reporting, Analysis and Corrective Action System FY Fiscal Year

G GFE Government-Furnished Equipment GFI Government-Furnished Information GFM Government-Furnished Material GFP Government-Furnished Property GPETE General Purpose Electronic Test Equipment

H HAZMAT Hazardous Material HE Human Engineering HERO Hazards of Electromagnetic Radiation on Ordnance HMMP HAZMAT Management Program HWCI Hardware Configuration Item

I IT-21 Information Technology for the 21st Century IMPS Integrated Master Program Schedule IPPD Integrated Product and Process Development IPT Integrated Product Team ISO International Organization for Standardization IAW In Accordance With

J JIT Just-in-Time JTF Joint Task Forces

L

M MCM Mine Countermeasures MIL-HDBK Military Handbook MIL-STD Military Standard

N NAVSEAINST Naval Sea Systems Command Instruction NDI Non-Developmental Item NSN National Stock Number NSWCPCD Naval Surface Warfare Center Panama City Division

O ODS Ozone Depleting Substances OPNAVINST Office of the Chief of Operations Instruction

P PCA Physical Configuration Audit PCO Procuring Contracting Officer

PEO LCS Program Executive Office Littoral Combat Ships PHS&T Packaging, Handling, Storage and Transportation PM Program Manager or Program Management PM IPT Program Management Integrated Product Team PMS495 Program Manager for Mine Warfare PR Problem Report PRR Production Readiness Review

Q QA Quality Assurance QAS Quality Assurance System

R RADHAZ Radiation Hazard R&M Reliability and Maintainability RBD Reliability Block Diagram RMA Reliability, Maintainability, and Availability RMP Risk Management Plan

S SE System Engineering SECNAV Secretary of the Navy SOW Statement of Work SSR Software Specification Review STD Software Test Description SVD Software Version Description

T TBD To Be Determined TDP Technical Data Package

V V&V Verification & Validation

W WBS Work Breakdown Structure WG Working Group