SOW_-_FBO.docx

Section C - Descriptions and Specifications

STATEMENT OF WORK

09 November 2018

STATEMENT OF WORK

FOR

PRODUCTION OF THE

SHIP TO SHORE CONNECTOR (SSC) SKIRT SYSTEMS

1.0 SCOPE

The Naval Surface Warfare Center, Panama City Division (NSWC PCD), Ship to Shore Connector Branch Code E32 has been tasked with production and supply support for the Ship to Shore Connector (SSC) skirt system. This Statement of Work (SOW) specifies the requirements for the fabrication and production of quantities of SSC skirts and related spare parts. This SOW is for an Indefinite Delivery Indefinite Quantity (IDIQ) type of contract with delivery orders specifying and funding the deliverables. Ordered assemblies and items are to be Firm Fixed Price (FFP). Delivery orders will specify in full detail the deliverables (i.e. the quantity of SSC skirts or spare parts).

2.0 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of this Statement of Work (SOW) to the extent specified herein. In the event of conflict between the documents referenced and the contents of this SOW, the SOW shall take precedence. Second tier and lower references, (i.e., those referenced in the primary references) shall be used for guidance with the exception of Program Peculiar Documents that specify mandatory second tier references. Additional applicable military standards, specifications, or other documents may be specified in individual delivery orders for specific tasks issued under this indefinite quantity contract. Government standards and specifications are available at https://assist.dla.mil/online/start/. Drawings and Project Peculiar Documents cited herein will be provided as an attachment with the solicitation and referenced in Section J.

2.1 MILITARY SPECIFICATIONS: None

2.2 MILTARY STANDARDS

Furnished to Government Activities 3/21/2000

2.3 OTHER DOCUMENTS

Requirements released 8/3/2006

2.4 NSWC PCD DRAWINGS

3.0 REQUIREMENTS

The Contractor shall provide the personnel, tooling, equipment, and facilities to accomplish fabrication, assembly, packaging, shipment and storage of SSC skirts or spare parts in accordance with the requirements paragraph of this SOW and as specified in individual delivery orders.

3.1 SSC SKIRT FABRICATION AND PRODUCTION (CDRL A001, A002)

When SSC skirts are required, they will be ordered via a delivery order under this contract, up to a maximum of 8 skirts per year. SSC skirts shall be fabricated, inspected, packed, and shipped in accordance with the Technical Data Package (TDP) that consists of the drawings (SOW paragraph 2.4) and the Project Peculiar Documents (SOW paragraphs 2.3(e) and 2.3(f)) or as detailed in each delivery order. The Contractor shall provide the weights of each of the Segments and Breakdown joints with the delivery of each skirt.

3.2 SPARE PARTS

When spare parts are required, they will be ordered via a delivery order under this contract. Spare parts shall be fabricated, inspected, packed, and shipped in accordance with the assembly drawings, subassembly drawings, detailed part drawings, Bill of Materials, quality control procedures, and specifications detailed in each delivery order.

3.3 STORAGE

The Government may request modifications to the delivery schedule that will require the Contractor to temporarily store raw material, spares, and/or fabricated skirts. Under these circumstances, the Contractor, within five (5) business days from notification, shall provide the Government a written cost estimate for additional expenses incurred for storing material or product in a climate controlled facility.

3.4 MARKING, PACKAGING, AND SHIPPING

All items fabricated under delivery orders issued under this contract shall be marked in accordance with the requirements of SECNAVINST 4440.34 and MIL-STD-130N unless otherwise specified in the delivery order. Items shall be packaged in accordance with ASTM D3951-10 and marked for shipment in accordance with MIL-STD-129P unless otherwise specified in the delivery order. The Contractor shall comply with FED-STD-313D for any items containing hazardous materials. Shipping locations shall be as specified in the individual delivery orders issued under the contract.

3.5 DESIGN AND PRODUCTION CHANGES (CDRL A003, A004)

Periodically the Government may change the skirt system design to address emerging capability gaps, reliability or producibility issues. All changes to the skirt system design will be documented via the Engineering Change Proposals (ECP) process. A Technical Data Package (TDP) representing the most recent baseline will be provided with the issuance of each individual delivery order. Additionally, the Contractor may propose rework items to meet the requirement of a specific delivery order. The Contractor may submit requests for deviations or waivers to the TDP requirements for Government approval.

For this SOW, Deviations and Waivers are defined as follows:

Deviation: authorization, granted prior to the manufacture of an item, to depart from a particular performance or design requirement of a specification, drawing or other document, for a specific number of units or a specific period of time.

Waiver: authorization to accept an item which, during manufacture or after having been submitted for inspection, is found to depart from specified requirements, but nevertheless is considered suitable for use "as-is" or after repair by an approved method

3.6 CONTRACT QUALITY REQUIREMENTS

3.6.1 QUALITY MANAGEMENT SYSTEM REQUIREMENTS

The Contractor’s quality program shall define the methods and resources which ensure the use and control of appropriate best management, engineering, design, manufacturing, handling and delivery practices, with emphasis on the prevention of defects. The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ISO 9001-2008, Quality Management Systems. The quality management system shall identify, monitor, measure, analyze, control and improve the processes to be used and provide methods to control process variability. The quality management system shall identify and provide required training and certification of quality and special process personnel. The quality management system shall provide methods for identification and correction of nonconformities and methods for the timely notification and feedback to contracting and program offices in areas such as major and critical deficiencies, potential manufacturing process problems, and subcontractor, supplier, or special process facilities or personnel problems that potentially impact the program. The quality management system approach, including the establishment and interaction of quality management system processes, shall be documented in a Quality Manual. The Quality Manual shall reference relevant quality management system documentation, as applicable, in explaining adherence to the requirements of the quality management system. The quality management approach shall be subject to Government or other independent assessments and oversight of the Contractor's quality management process and its implementation, including those related to assessments or oversight of subcontractors, suppliers, and special process facilities.

3.6.2 QUALITY PLANNING AND EXECUTION (CDRL A005)

Quality may be determined by the extent that products conform to specifications and requirements and satisfy the customer at an affordable cost. A Quality Plan provides a means of relating the specific requirements of the SOW to work methods and practices necessary for achieving the quality objectives of the SOW and that support product realization. The Contractor shall provide and maintain a Quality Plan which identifies the specific methods, activities, resources, and quality management system elements that will be applied to meet the specifications and requirements of this SOW. The Quality Plan shall indicate how the required activities will be carried out, either directly or by reference to appropriate documented procedures, work instructions, process specifications or other documents. The Government will assess conformity to ISO 9001:2008 and acceptability of the Contractor’s Quality Plan.

The Contractor shall establish, equip, certify and operate all work processes and Quality Management, Quality Assurance, and Quality Control (QM/QA/QC) activities based on the fundamentals of ISO 9001-2008. Each delivery order shall be subject to the QM/QA/QC program unless and as specifically exempted by the delivery order. The contractor shall subject all deliverables and elements thereof to QM/QA/QC requirements, including purchased parts and subcontracted work unless exempted by the Delivery Order (DO). The contractor shall provide inspection reports and certifications data.

3.6.3 PRODUCTION, INSPECTION, TEST AND CERTIFICATION (CDRL A006)

The Contractor shall provide the capabilities and quality program to produce, inspect, test, document, and certify that the items delivered meet the physical and functional requirements of the TDP and each delivery order. The Contractor shall perform inspection of lots or batches and furnish inspection reports in accordance with the delivery order and sampling plans and in accordance with American National Standard ASQ Z1.4-2008. Unless otherwise specified, attributes, which if defective would prohibit or reduce the usability of the product for its intended purpose, shall be inspected at an acceptance quality limit (AQL) of 1.0. Attributes which do not materially reduce the usability of the product shall be inspected at an AQL of 2.5. Any attributes classified as critical on the technical documentation shall be inspected on each unit of product submitted. Any instruments or equipment used shall be maintained in calibration in accordance with NCSL Z540-1- 1994 R2004. The Government reserves the right to reject any unit of product found nonconforming during inspection whether that unit of product forms a part of a sample or not, and whether the lot or batch as a whole is accepted or rejected.

3.7 PRODUCTION REVIEWS (A007, A008)

The contractor shall conduct Production Reviews quarterly (every 3 months after award) that cover delivery orders in process to provide the Government with additional insight into production and delivery issues and to provide a forum to resolve technical issues. The contractor shall conduct these Production Reviews if feasible via NetMeeting or teleconference between the Government and the contractor to minimize travel expenses. The contractor shall coordinate for production reviews a minimum of 5 working days prior to the requested meeting or NetMeeting or teleconference. The contractor shall provide the agenda and subject briefing to the Government a minimum of three (3) working days prior to the meeting.

3.8 MONTHLY STATUS REPORTING (CDRL A009)

The Contractor shall monitor progress and report status on a monthly basis.

4.0 GOVERNMENT FURNISHED PROPERTY (GFP)

This contract contains the clause entitled "Government Furnished Property". However, receipt of Government Furnished Property or Contractor Acquired Property is not authorized under this contract. Such property may be acquired only upon receipt of a fully executed delivery or task order or modification to a delivery or task order that specifically authorizes acquisition of the property by the contractor. Requests for Contractor Acquired Property must be made to the cognizant Contracting Officer.

Any property acquired by the Contractor without a delivery or task order or modification to a delivery or task order authorizing such acquisition, is done so at the Contractor's own risk.

There is no GFP anticipated at this time however individual delivery orders may include GFP if circumstances warrant.

5.0 SECURITY REQUIREMENTS

The work to be performed under this contract will be UNCLASSIFIED. The Contractor will not require access to nor be required to generate classified information to perform this effort. 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 Contracting Officers Representative (COR).

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 INFORMATION SECURITY GUIDELINES FOR PROTECTION OF UNCLASSIFIED DOD INFORMATION ON NON-DOD SYSTEMS (PER DTM 08-027)

(a) 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

(c) Prompt application of security-relevant software patches, service packs and hot fixes.

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

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

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

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

CLAUSES INCORPORATED BY FULL TEXT

HQ C-1-0001 ITEM(S) CONTRACT DATA REQUIREMENTS (NAVSEA) (SEP 1992)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A, attached hereto.

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.