Attachment_J.1_DD1155_Cradle_Weldment_.pdf

N61331-19-R-0015 Attachment J.1

MAC order under solicitation N61331-19-R-0015 J.1

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

MASC Supplies

FFP

NET AMT

0001AA 1 Lot $ First Article of (1) Cradle Weldment, P/N 24952-1 in accordance with drawings in Section J.

FOB: Destination

0001AB 19 Lot $ AN/AQX-24A Cradle Weldment, P/N 24952-1 in accordance with drawings in

Section J.

0001AC 1 Lot $ Not Separately Priced Technical Data

Contract Data Requirements List (CDRLs) in accordance with Section J.

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

FOR

AN/AQS-24A (Q24) CRADLE WELDMENT ASSEMBLY FABRICATION SUPPORT

10 May 2019

1.0 SCOPE

This Statement of Work (SOW) defines the effort required to support Naval Surface Warfare Center

Panama City Division (NSWC PCD) Code A22 to manufacture AN/AQS-24A Cradle Weldment Assemblies. The scope of the effort includes the task requirements identified in section 3.0.

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 in the Requirements Section of this SOW. In the event of conflict between the documents referenced herein, and the contents of the SOW, the contents of this SOW shall take precedence. Second tier and lower reference documents (i.e., those reference in the primary references) shall be used for guidance only.

2.1 Military Standards

None

2.2 Military Specifications

a) MIL-STD-130 Identification Marking of U.S. Military Property

2.3 Other Documents

a) NSWC PCD Drawing 24952, CAGE 07070 Cradle Weldment

b) NSWC PCD Drawing 39936, CAGE 07070 Epoxy Polyamide Specification

3.0 REQUIREMENTS

3.1 Q24 Cradle Weldment

The contractor shall fabricate twenty (20) AN/AQS-24A Cradle Weldment, P/N 24952-1 in accordance with NSWC PCD Drawing 24952 (Cradle Weldment) and NSWC PCD Drawing 39936 (Epoxy Polyamide Specification). The contractor shall first manufacture one (1) Cradle Weldment, P/N 24952-1 as a first article to be approved by NSWC PCD before manufacture of the final nineteen (19).

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

3.3 Travel

No travel is required.

4.0 GOVERNMENT FURNISHED PROPERTY (GFP)

4.1 Government Furnished Property (GFM)

4.2 Government Furnished Equipment (GFE)

4.3 Government Furnished Information (GFI)

GFI in the form of the documents listed in SOW paragraph 2.3 will be provided with the Request for

Proposal (RFP). Disposition of GFI will be made at contract completion.

5.0 DELIVERABLES

5.1 Hardware Deliverables

Item Qty Date Due First Article Q24 Cradle Weldment 1 45 DAC* Q24 Cradle Weldment 19 120 DAC

*DAC means “Days After Award of Contract

5.2 Data Deliveries

All data deliverables shall be submitted in accordance with the schedule as specified in the attached Contract Data Requirements List (CDRL), DD Form 1423, Exhibit A.

6.0 PERIOD OF PERFORMANCE

The period of performance is from issuance of order until 120 days after date of award.

7.0 SECURITY

This task is UNCLASSIFIED.

7.1 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.2 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.3 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.4 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.

7.5 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

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

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

Technical documents generated under this contract shall carry the following limitation statement. Word processing files shall have the statements included on the cover page of any resultant hard copy. Each delivered diskette shall be marked externally with the statements. All technical data gathered under this purchase order shall carry the following Distribution Limitation Statement and handling caveat:

DISTRIBUTION STATEMENT D - DISTRIBUTION AUTHORIZED TO THE DEPARTMENT

OF DEFENSE AND U.S. DoD CONTRACTORS ONLY; ADMINISTRATIVE OR OPERATIONAL

USE (MM/DD/YYYY). OTHER U.S. REQUESTS SHALL BE REFERRED TO NAVAL SURFACE

WARFARE CENTER PANAMA CITY DIVISION, 110 VERNON AVENUE, PANAMA CITY, FL.

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 OR RECONSTRUCTION OF

THE DOCUMENT.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 N/A N/A N/A N/A 0001AA Destination Government Destination Government 0001AB Destination Government IAW DD 1423 Government 0001AC Destination Government IAW DD 1423 Government

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS UIC

N/A N/A N/A N/A

0001AA 45 days DAC 1 N61331 NSWC Panama City 110 Vernon Ave Panama City, FL 32407-7018

N61331

0001AB 120 days DAC 19 N61331 NSWC Panama City 110 Vernon Ave Panama City, FL 32407-7018

0001AC IAW 1423 1 IAW 1423

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232- 7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

Combo https://www.sam.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC TBD Issue By DoDAAC N61331 Admin DoDAAC** TBD Inspect By DoDAAC N61331 Ship To Code ____ Ship From Code ____ Mark For Code ____ Service Approver (DoDAAC) ____ Service Acceptor (DoDAAC) ____ Accept at Other DoDAAC ____ LPO DoDAAC ____ DCAA Auditor DoDAAC ____ Other DoDAAC(s) ____

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert “See Schedule” or “Not applicable.”)

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

Section J – List of Documents, Exhibits and Other Attachments

Document Description Pages Date Attachment J.1a Drawing 24952 Rev. V.(available upon request to Contract Specialist) 7 19 January 2014

Attachment J.1b Drawing 39936 Rev. C. (available upon request to Contract Specialist)

1 30 June 2014

Exhibit A CDRL IAW DD1423 2 25 September 2014