C- SOW.pdf

PDF 257 KB Posted

Attached to
LCS Table Fixture -WOSB SET-ASIDE Federal contract opportunity
Solicitation number
N61331-21-T-VT31
Issued by
Department of the Navy Naval Sea Systems Command

View the file

Other files for this federal contract opportunity

Other files attached to LCS Table Fixture -WOSB SET-ASIDE, newest first.
File Type Posted
N61331-21-T-VT31 Q-A.docx DOCX document
SUPPLY- COMMERCIAL-hq -options.docx DOCX document

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

22 February 2021

STATEMENT OF WORK

FOR

FABRICATION AND ASSEMBLY OF LITTORAL COMBAT SHIP (LCS)

TABLE FIXTURE DEVICE KITS

1.0 SCOPE

The Naval Surface Warfare Center Panama City Division (NSWC PCD) has a requirement for the fabrication of the following items:

(a) LCS Table Fixture Device Assemblies

(b) OPMA Mount Kits

This Statement of Work (SOW) covers the requirements for the fabrication of these items.

2.0 APPLICABLE DOCUMENTS

The following documents, of the most current issue, form a part of this SOW to the extent specified herein. In the event of conflict between the document referenced herein and the contents of this SOW, the contents of this SOW shall take precedence. Second tier and lower reference documents (i.e., documents referenced in the primary references) shall be used for guidance only.

2.1 Military Specifications:

2.1.1 None

2.2 Military Standards:

2.2.1 None

2.3 Other Documents:

2.3.1 NAVSEA Drawing 53711-8741732, LCS Table Fixture Device Assembly (includes sub-assemblies specified in drawings 8741737, 8741736, 8741735, 8741734, and

8741733)

2.3.2 NAVSEA Drawing 53711-87411743, OPMA Mount Kit (includes sub-assemblies specified in drawings 8741739 and 8741743)

2.3.3 ISO 9001:2015, Quality Management Systems – Requirements dated 15 Sept 2015

3.0 REQUIREMENTS

3.1 Fabrication

3.1.1 The Contractor shall provide the facilities, material and labor to fabricate the parts listed below. The Contractor shall have a quality system that meets the requirements of ISO

9001-2015.

(a). Eighteen (18) each LCS Table Fixture Device Assemblies in accordance with drawing 53711-8741732.

(b). Twelve (12) each OPMA Mount Kits in accordance with drawing 53711-

8741743.

3.1.2 The Sub-assemblies for each item shall be bagged and tagged by the Contractor in accordance with the drawings.

3.1.3 Additionally, the Contractor shall purchase and deliver Eighteen (18) each Pelican

Cases (with foam) PN 1745WF. The eighteen (18) cases shall have the foam cut to fit one fully assembled Table Fixture Devices per case. The foam removed from each case shall be returned to NSWC PCD at time of case delivery.

3.2 Documentation

3.2.1 The Contractor shall provide the following documentation:

(a). Certificate of conformance that items were fabricated to the drawing requirements. (CDRL A001)

(b). Copy of dimensional inspection. (CDRL A002)

3.3 Inspection and Acceptance

3.3.1 The completed items shall be shipped to:

NSWC Panama City Division

110 Vernon Ave

Panama City, Fl. 32407

The Inspection and Acceptance shall be performed at NSWC PCD.

3.3.2 The Government will inspect the items for conformance to the drawings (i.e.

Dimensionality and materials), functionality, and workmanship. It is anticipated that acceptance or rejection will occur within 14 days after receipt of the items.

4.0 GOVERNMENT FURNISHED PROPERTY (GFP)

4.1 Government Furnished Material (GFM):

4.1.1 None.

4.2 Government Furnished Equipment (GFE):

4.2.1 None.

4.3 Government Furnished Information (GFI):

4.3.1 Drawings listed in Section 2.3 will be provided with the Request for Quote (RFQ).

5.0 DELIVERABLES

5.1 Data Deliverables

All data deliverables shall be delivered in accordance with the schedule as specified in the attached

Contract Data Requirements List (CDRL), DD Form 1423, Exhibit A.

5.2 Hardware Deliverables

Deliver in accordance with Section F of the order.

6.0 PERIOD OF PERFORMANCE

The period of performance shall be within 5 months after date of award.

7.0 SECURITY

This requirement is UNCLASSIFIED. The Contractor will not require access to nor be required to generate classified information to perform the requirement.

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

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

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

7.3 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides and unclassified limited documents (e.g., CUI, 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.

7.4 CUI

CUI 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. CUI must be marked, controlled and safeguarded in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI)

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

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

8.0 DISTRIBUTION LIMITATION STATEMENTS

Technical documentation generated under this Agreement shall carry the following distribution limitation statement. Word processing / electronic files shall have the statements included in the file such that the first page of any resultant hard copy shall display the statements. For drawings, the statements shall be as near to the title as possible without obscuring any detail of the drawing. Additionally, each diskette delivered shall be marked externally with the statements.

For all documents and files generated under this contract:

DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO THE DEPARTMENT

OF DEFENSE AND U. S. DOD CONTRACTORS ONLY; CRITICAL TECHNOLOGY.

OTHER U.S. REQUESTS SHALL BE REFERRED TO THE PROGRAM EXECUTIVE

OFFICE, LITTORAL COMBAT SHIPS, ATTENTION: PMS 420.

DESTRUCTION NOTICE - CLASSIFIED INFORMATION, DESTROY IN ACCORDANCE WITH

SECNAVINST 5510.36B, (DON INFORMATION SECURITY PROGRAM) OR DOD 5220.22-M,

(NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL). UNCLASSIFIED

LIMITED DOCUMENTS, (E.G., FOUO, DISTRIBUTION STATEMENT CONTROL) DESTROY BY

ANY METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF

THE DOCUMENT

2021-04-05T12:36:59-0500
MONTGOMERY.FRANK.N.1245766757

File details come from the government source that posted it. Updated .