STATEMENT_OF_WORK.doc

STATEMENT OF WORK

FOR

NAVY MINE COUNTERMEASURES DIORAMA

27 March 2014

1.0

SCOPE

The Naval Surface Warfare Center Panama City Division (NSWC PCD) requires contractor support to fabricate a diorama that depicts the Navy’s currently in-service (legacy) and future Littoral Combat Ship Mine Counter Measures Mission Package (LCS MCM MP) mine countermeasure platforms and systems depicted in their typical operating environment. The purpose of this diorama is to visually enhance an individual’s understanding of the MCM mission, its mission space or environment and the major platforms and associated systems used to conduct MCM operations. The contractor shall provide all material, personnel, and facilities to fabricate a diorama that meets the requirements of paragraph 3.0 below.

2.0

APPLICABLE DOCUMENTS

None

3.0

REQUIREMENTS

3.1 Navy Mine Countermeasure Diorama Content

The contractor shall fabricate a diorama that depicts the LCS MCM MP systems in their typical operating environment. The following is a list of in-service and future MCM platforms and associated systems that shall be displayed in the diorama:

3.2 Physical Requirements and Configuration The Navy MCM Diorama shall have the following features that relate to desired benefits:

3.3 Quality

The contractor shall inspect, in the presence of a Government representative, the fit, function, and quantity of all items purchased under this SOW prior to acceptance of said items by the Government. The contractor shall submit a copy of the inspection report to the Government.

3.4 In-Process Reviews

3.4.1 Kick-Off Brief

The contractor shall prepare a purchase order kick-off brief. This brief may be a virtual telecon and hall be presented to the Government no later than five (5) working days after purchase order award. The contractor shall present the final design, risks, and delivery schedule at this meeting.

3.4.2 Preliminary Review

The contractor shall conduct a virtual telecom design review with the Government point of contact at the 30% completion point. The purpose of the preliminary review will be to evaluate the progress, technical adequacy, and risk resolution of the selected design approach.

3.4.3 Secondary Review

The contractor shall conduct a virtual telecom design review with the Government point of contact at the 60% completion point. The purpose of the preliminary review will be to evaluate the progress, technical adequacy, and risk resolution of the selected design approach.

3.4.4 Final Review

Final inspection and acceptance of the MCM Diorama will be made by the Government at the contractor’s facility prior to shipment to the PEO LCS office. All Government comments shall be incorporated into the final MCM Diorama prior to shipment.

3.5 Monthly Status Report

The contractor shall prepare a monthly status report that documents the status of contractor effort towards achieving contract objectives. The report shall identify accomplishments to date and difficulties encountered, and compare the status achieved to planned goals and the resources expended.

4.0

GOVERNMENT FURNISHED INFORMATION (GFI)

GFI in the form of MCM platform and system pictures, drawings, and descriptive data will be provided with the request for proposal (RFP). Disposition of GFI will be made at purchase order completion. Any additional requests for GFI may be made to the technical point of contact (TPOC), Harry Guthmuller, Mine Warfare Integration & Interoperability Chief Engineer, (850)235-5193, harry.guthmuller@navy.mil.

5.0

DELIVERIES

5.1 Hardware Deliverables

The contractor shall provide one (1) Navy MCM Diorama containing all the attributes listed in SOW paragraph 3.2 within 180 days after award of purchase order. Delivery will be made to the PEO LCS Office at the Washington Navy Yard.

5.2 Data Deliverables

All data deliverables shall be submitted in accordance with the attached DD Form 1423.

6.0

PERIOD OF PERFORMANCE

The period of performance for this effort shall be from date of award of purchase order until 180 days after award of purchase order.

7.0

SECURITY

This task is UNCLASSIFIED. Performance under this purchase order will not require access to nor generation of classified information.

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

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

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

7.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 7.5 Information Security Guidelines for Protection of Unclassified DoD Information on Non-DoD Systems (per DTM 08-027)

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

(3) 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 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.

8.0

DISTRIBUTION LIMITATION STATEMENT

Technical documents generated under this task order shall be marked with Distribution Limitation Statement D. Word processing files shall have the statements included on the cover page of any resultant hard copy. All technical data gathered under this task order shall carry the following Distribution Limitation Statement and handling caveat:

DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO DOD and U.S. DOD CONTRACTORS (ADMINISTRATIVE OR OPERATIONAL PURPOSES) (DATE STATEMENT APPLIED). OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO NSWC PANAMA CITY (MIW I&I CHENG).

DESTRUCTION NOTICE - FOR CLASSIFIED DOCUMENTS, FOLLOW PROCEDURES IN DOD 5220.22-M, NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, CHAPTER 5, SECTION 7 OR DOD 5200.1-R, INFORMATION SECURITY PROGRAM REGULATION. FOR UNCLASSIFIED, LIMITED DOCUMENTS, DESTROY BY ANY METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OF RECONSTRUCTION OF THE DOCUMENT.