N61331-16-R-0011_Draft_SOW.doc

STATEMENT OF WORK

FOR

FABRICATION OF LANDING CRAFT AIR CUSHION (LCAC)

PROPELLER DUCT AFT FOUNDATION FITTING ASSEMBLIES

1.0

SCOPE

The Naval Surface Warfare Center (NSWC) has a requirement for fabrication of LCAC Aft Foundation Fitting assemblies for five years. This Statement of Work (SOW) covers the requirements for the fabrication of these items.

2.0

APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of this SOW to the extent specified herein. In the event of conflict between the documents referenced herein and the SOW, the contents of this SOW shall take precedence.

2.1 Military Standards: None

2.2 Military Specifications: None

2.3 Other Documents:

(a) Drawings

NAVSEA 182-5749535 Rev J, LCAC Aft Foundation Fitting Propeller Duct STA 41 . 57 dated 19 January 1982

(b) Solid Model Files 3.0

REQUIREMENTS

The Contractor shall provide labor to fabricate, assemble, and deliver a First Article set consisting of:

(a) One (1) each 5749535-9 LCAC Aft Foundation Fitting Assembly

(b) One (1) each 5749535-10 LCAC Aft Foundation Fitting Assembly

The Contractor shall fabricate the items in accordance with NAVSEA 182-5749535 Rev J and the Solid Model files provided with the solicitation. The Contractors workmanship shall ensure that surfaces of the finished fitting assemblies are uniformly finished and free from burrs, sharp edges, cracks, coarse marks, and processing materials. The Government will inspect the First Article items for workmanship and dimensionally check each First Article item to determine that it meets the requirements of NAVSEA 182-5749535 Rev J and the Solid Model files prior to acceptance. The Government will accept or reject the First Article items within 15 days after receipt of the items.

In accordance with referenced drawing NAVSEA 182-5749535 Rev J; two bushings installations are required for each assembly; p/n KRJ8-SV-024 and KRJ12-SV-024. Shop fabrication substitution is permitted for bushings KRJ12-SV-024 and KRJ8-SV-024 with certified 17-4 PH material. The remaining four MS14237C05-025 bushing installations and machining of the .4375 holes referenced in NAVSEA 182-5749535 Rev J drawing section R-R are not required under this SOW. The 5749535-5 Rudder Actuator Clevis Fittings are identified as part of the Foundation Fitting but are not required under this SOW. Marking and painting (note 2 and 4 of drawing NAVSEA 182-5749535 Rev J) are not required under this SOW. Machining of the pilot holes identified in Section K-K of the drawing NAVSEA 182-5749535 Rev J are not required under this SOW. (Note: these items are not required because they must be custom fitted to the individual LCAC propeller shrouds and that work is done by the Government.)

3.1 The Contractor shall, as specified in individual delivery orders to be issued under the contract, fabricate and deliver the items in accordance with NAVSEA 182-5749535 Rev J as specified in each order.

3.2 The Contractor shall provide a material certification, dye penetrant inspection in accordance with drawing NAVSEA 182-5749535 Rev J note 8, and QA Inspection Report for each hardware delivery. (CDRL A002, A003)

3.3 Inspection and Acceptance will be at:

NSWC Panama City Division

110 Vernon Ave

Panama City, Fl. 32407-7000 3.4 Status Reporting (CDRL A001)

The Contractor shall report status of the effort on a monthly basis.

4.0

GOVERNMENT FURNISHED MATERIAL (GFM)

None

5.0

SECURITY

This requirement is UNCLASSIFIED. The Contractor will not require access to classified nor be required to generate classified material to meet the requirements of this order.

Technical papers, either classified or unclassified, which the Contractor may wish to present at government-sponsored classified or limited attendance symposia must be submitted through the NSWC PCD Technical Point of Contact to initiate the process. Approval must be granted prior to Contractor presentation.

Information on this contract is not releasable to foreign nationals or personnel processing “Reciprocal” clearance without the written approval of NSWC PCD Security. The only exceptions to this requirement are a visit of a foreign national duly authorized by the DOD through established channels or if authorized under the International Traffic in Arms Regulation ( ITAR).

The Prime Contractor shall:

(1) Direct the Subcontractor to obtain approval, through the prime Contractor, for the public release of information received or generated by the sub through the prime Contractor.

(2) Submit the Subcontractor’s request for public release through the NSWC PCD technical point of contact.

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

Prior to access, Contractor personnel requiring access to 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.2 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides (OPNAVINST 5513 series) and unclassified limited documents (e.g., 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.3 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.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 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 DoD 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 (DoD 8582.01) DoD Policy

Adequate security 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 (TLS).

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 TLS 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 IDs 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.