SOLICITATION_N00178-14-R-1010.pdf

CODE

(Hour)

PAGE(S)

until 12:00 PM local time 27 May 2014

X

A

X B

X C X D

EX

X

G

F 38 - 46

47 - 57

X H 58 - 64 roberta.moss@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

DO-A7 1 64

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N00178 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 4 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Suite 102, BLDG 183 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

ROBERTA C. MOSS (540) 653-1053

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 3

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

4 - 13

14 - 15

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

17 - 18 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 19 - 23 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 24 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

25 - 36

PART II - CO NTRACT CLAUSES

NSWCDD

ATTN: CS20-4

ROBERTA.MOSS@NAVY.MIL

17632 DAHLGREN ROAD STE 157

DAHLGREN VA 22448-5110

540-653-1053

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

24 Apr 2014

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N00178-14-R-1010

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Each Spar - Tactical Sensor Mast Buoy

FFP

The Contractor shall deliver one Spar - Tactical Sensor Mast Buoy in accordance with Section C, Description/Specifications/Statement of Work

FOB: Origin

NET AMT

0002 1 Lot OPTION Six Month Field Test

FFP

The Contractor shall provide Six Month Field Testing support in accordance with

Section C, Description/Specifications/Statement of Work

0003 Lot Data Deliverables

The Contractor shall deliver data in accordance with Exhibit A, DD Form 1423, Contract Data Requirements List - THIS ITEM IS NOT SEPARATELY PRICED

FOB: Destination

CLAUSES INCORPORATED BY FULL TEXT

HQ C-1-0001 ITEM(S)

CLIN 0003 - 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), attached hereto.

(End of Text)

Section C - Descriptions and Specifications

SPECIFICATIONS

SECTION C – DESCRIPTION/SPECIFICATION/WORK STATEMENT

C.1 SCOPE

This Statement of Work (SOW) defines the effort required for the design, development, manufacture and testing of a Spar - Tactical Sensor Mast (TSM), a moored sensor platform, with a backhaul data communication system. It includes associated program management, system documentation, and test support requirements.

C.1.1 BACKGROUND

The TSM is a moored sensor platform that hosts air, surface, and subsurface maritime domain awareness sensors at strategically important locations in either coastal or open ocean environments. The TSM will incorporate a passively stabilized mast with low pitch and roll motions to collect data from 30 pounds of sensors at a nominal elevation of 20 feet above sea level. A backhaul data communication system will be employed to offload a multitude of streaming data from the sensors through a standard Transmission Control Protocol/Internet

Protocol Version 4 (TCP/IPv4) connection.

The TSM will provide enhanced maritime security at strategically and tactically important locations. The low pitch and roll motions enable high resolution air, surface and subsea data under varying environmental conditions. The low cost and high persistence of this system make it very attractive when compared with ship-based systems. The payoff is increased maritime domain awareness at reduced cost. Rapid global deployment is possible using existing Navy and commercial vessels.

The TSM will increase threat standoff, expand communications capabilities, enable earlier detection and support interdiction of threats, feed the larger global maritime domain awareness networks, and be the experimental platform from which a new generation of sensors and interdiction systems can be tested and ultimately fielded.

C.2 APPLICABLE DOCUMENTS

C.2.1 System Requirements Specification for the Spar – Tactical Sensor Mast (TSM) with

Backhaul Data Communication System.

C.3 REQUIREMENTS

The work required by this contract will be performed in accordance with the System

Requirements Specification for the Spar - Tactical Sensor Mast (TSM) with Backhaul Data

Communication System, hereafter referred to as the System Specification, and this Statement of

Work (SOW).

C.3.1 DESIGN, ENGINEERING AND FABRICATION

C.3.1.1 The contractor shall design and develop a prototype TSM equipped with a backhaul data communication system to meet the performance criteria specified by the System Specification.

C.3.1.2 The contractor shall determine all Coast Guard and other regulatory requirements for deployments of the TSM in a Continental United States (CONUS) coastal location and for deployment of the TSM in international waters and identify how the TSM will meet these requirements. (CDRL A001)

C.3.1.3 The contractor shall conduct a Critical Design Review (CDR) at its own facility. The

CDR will be attended by up to ten (10) Government personnel. At the CDR, the contractor shall formally present the TSM design and any potential issues. The contractor shall incorporate all design changes approved during the CDR into the final design. (CDRL A002)

C.3.1.4 The contractor shall manufacture one (1) prototype TSM equipped with a backhaul data communication system according to the approved final design.

C.3.1.5 The contractor shall provide an official contractor certification that the TSM meets all

Coast Guard and other regulatory requirements for deployment of the TSM in a CONUS coastal location and for deployment of the TSM in international waters. (CDRL A003)

C.3.2 FACTORY ACCEPTANCE TEST (FAT)

The contractor shall develop and execute a Factory Acceptance Test (FAT) for the TSM and backhaul system to demonstrate the key design elements of the TSM and the capability of the backhaul system. The TSM shall be subjected to a FAT at the contractor’s location. The

Government will install and operate sensor measurement devices and sensors on the TSM during the FAT. (CDRL A004, CDRL A005)

C.3.3 TSM DELIVERY

The contractor shall deliver the TSM and the backhaul data communication system to the

Government upon completion of the Factory Acceptance Test (FAT).

C.3.4 SIX-MONTH FIELD TEST (OPTIONAL CLIN 2)

The Government shall have the option to obtain the contractor’s support during a six-month field test of the TSM. During this field test, the Government shall install up to 30 pounds of sensor equipment on the TSM, and shall operate and collect data from the sensors continuously for a period of six months. If this option is exercised, the following requirements shall apply.

C.3.4.1 Following the Government installation of sensors on the TSM, the contractor shall transport the TSM to the test site and moor the TSM in water at least 50 feet deep at a CONUS location selected by the contractor. The field test location must be approved by the Government to ensure that it adequately represents typical operating conditions for the TSM.

C.3.4.2 The contractor shall visit the TSM at least once every 30 days during the six-month test period to ensure that the TSM equipment and the backhaul data communication system equipment are operating properly, and to refuel the TSM if necessary. The contractor shall provide all fuel required by the TSM during the six-month test period.

C.3.4.3 The contractor shall participate in a 30-minute teleconference with the Government once per week during the six-month test period to review the TSM status and the backhaul data communication system status, and to address any technical issues.

C.3.4.4 Upon completion of the six-month field test, the contractor shall remove the TSM from the water and allow the Government to recover the sensor equipment. The contractor shall replace all mooring equipment on the TSM with new mooring equipment, and then return the

TSM and the backhaul data communication system to the Government.

C.3.5 DOCUMENTATION

The contractor shall develop instructions for the operation, maintenance, transportation and deployment of the TSM including the backhaul data communication system, including any safety considerations. Operational instructions must include instructions for the TSM mooring, unmooring and mooring equipment replacement operations, as well as the typical time, manpower and tools/equipment required to replace the mooring equipment on the buoy.

Transportation instructions must address loading, unloading and transporting the TSM on a flatbed truck, flatbed railcar, and the deck of a ship. Deployment instructions must address deploying the TSM from the shore and into the water, and removing the TSM from the water and onto the shore. (CDRL A006)

C.3.6 PROGRAM MANAGEMENT

The contractor shall monitor technical progress and schedule related to the project. (CDRL

A007)

C.4 DELIVERY SCHEDULE

1. Critical Design Review 30 DAC

2. Construction Complete 120 DAC

3. Factory Acceptance Test (FAT*) 150 DAC (*Note: Government may postpone FAT up to 60 days to achieve better weather conditions for FAT)

4. Deliver TSM to Government 30 days after completion of FAT

5. Begin Six-Month Field Test 30 days after completion of FAT

6. Six-Month Field Test Complete 210 days after completion of FAT

SYSTEM REQUIREMENTS SPECIFICATION FOR THE

SPAR – TACTICAL SENSOR MAST (TSM) WITH BACKHAUL DATA

COMMUNICATION SYSTEM

1. TACTICAL SENSOR MAST (TSM) REQUIREMENTS

1.1 The TSM shall have a vertical mast that supports 30 pounds of sensors on a platform at the top of the mast which is 20 feet above the water level.

1.2 The platform at the top of the mast shall have a sensor mounting plate that is 12 inches square, with a 10 inch square bolt pattern with 5/8 inch through bolts.

1.3 The buoy platform at the base of the mast shall be large enough to allow one 250 lb. person to walk safely completely around the mast. This buoy platform shall be equipped with four sensor mounting plates (one in each quadrant) which are identical in size and bolt pattern to the sensor mounting plate at the top of the mast.

1.4 The mast shall be telescoping to provide both a stowed configuration and a deployed configuration. In the stowed configuration, the height of the mast from the buoy platform to the sensor mounting plate shall be less than 5 feet. The mast shall be capable of being lowered to the stowed configuration while the buoy is in the water to allow for maintenance of the sensors on the sensor mounting plate.

1.5 The mast shall be passively stabilized to provide the following minimum requirements from

Sea State 0 up to and including World Meteorological Organization (WMO) Sea State 4:

1.5.1 The mast shall not exceed 60 degrees per second in pitch, roll, or yaw speed.

1.5.2 The mast shall not exceed 60 degrees per second squared in pitch, roll, or yaw acceleration.

1.5.3 The mast shall not exceed an angle of more than 45 degrees in any direction with respect to horizon.

1.6 The TSM shall survive intact through World Meteorological Organization (WMO) Sea

State 6. In the event that the TSM is damaged or sunk, the TSM shall be designed to be recoverable in order to minimize water hazards.

1.7 The TSM shall be equipped with both shallow and deep water mooring equipment, enabling it to be moored in water depths from 50 to 10,000 feet. The moorings shall be designed to hold the TSM in place through World Meteorological Organization (WMO) Sea State 6 conditions.

The mooring equipment shall be easily replaceable with new mooring equipment.

1.8 The TSM shall provide a minimum of 1,000 watts (or 1 kilowatt) of continuous power for the sensors for at least 30 days without refueling. The TSM shall also be capable of producing a minimum of 6,000 watts (or 6 kilowatts) of power intermittently for at least 5% of the 30-day period without refueling.

1.9 The TSM shall provide both 12 VDC and 24 VDC outputs for the sensor equipment.

1.10 The TSM shall have an Operational Availability above 90% over one year.

1.11 The TSM shall be designed to operate for at least 30 days between any required maintenance or refueling operations.

1.12 The TSM shall provide protection to minimize water contamination in the event of corrosion or damage to fuel tanks or other buoy components.

1.13 The TSM shall meet all Coast Guard and other regulatory requirements for deployment of the TSM in a CONUS coastal location and for deployment of the TSM in international waters.

Any required signage or lighting on the TSM shall not interfere with the mounting or operation of the sensors on the TSM.

1.14 The TSM shall be equipped with methods to minimize electrolysis and corrosion for a period of at least 6 months without maintenance.

1.15 The contractor shall provide an appropriate fixture for transporting the TSM on a flatbed truck, flatbed railcar, and the deck of a ship.

1.16 The TSM shall be designed such that it can be towed while in the water.

2. BACKHAUL DATA COMMUNICATION SYSTEM REQUIREMENTS

In addition to the physical construction of the TSM buoy, design and construction of a backhaul data communication system is also required. This backhaul system is necessary to offload a multitude of streaming data from various sensor arrays from various fielded TSM buoys through a TCP/IP connection utilizing a standard Ethernet port (RJ45 connector). The TSM buoys may be placed in a variety of locations around the globe ranging from just off shore to deep sea environments.

Two requirement scenarios are specified below. The first scenario allows for higher throughput when the TSM buoy is within Line of Sight (LoS) of the receiving ground station or another node in a mesh network configuration in which at least one part of the network is within LoS of the ground station. Additional requirements are specified for the Non-Line of Sight (NLoS) scenario where a lower bandwidth is permitted as a tradeoff for global connectivity. A satellite communications (SATCOM) solution would be an example of a NLoS system.

The following requirements are necessary for the functionality, reliability and security of the backhaul data communication system.

2.1 GENERAL SYSTEM-WIDE REQUIREMENTS FOR BACKHAUL SYSTEM

2.1.1 The backhaul system shall provide the capability to be pre-configured before fielding, such that deployment of the system only requires the system to be powered on in order to connect and fully function.

2.1.2 The backhaul system shall not have any reoccurring license fees.

2.1.3 The backhaul system shall be configurable by the end user without the need for third party assistance.

2.1.4 The backhaul system shall be self-monitoring and provide Built-In Test (BIT) capabilities.

2.1.5 The backhaul system shall be FCC licensed prior to demonstration and/or delivery of the system.

2.1.6 The backhaul solution must utilize existing technology that has been fielded and which has demonstrated that it achieves its published performance characteristics under its advertised operational conditions. Emerging technologies and not-yet-mature technologies without a service record will not be considered a viable solution.

2.1.7 The backhaul system shall be properly shielded for continuous and prolonged exposure to seawater and weathering conditions in accordance with maritime environments up to and including World Meteorological Organization (WMO) Sea State 6.

2.1.8 In the event that both LoS and NLoS solutions are used to satisfy coverage and performance, the backhaul system shall automatically determine if a LoS route is available and give preference to that mode of communication. The system shall utilize a NLoS solution as an automatic backup should a LoS link not be available for any reason, without interrupting data connectivity and without any intervention from the user of the system past initial configuration.

2.1.9 The backhaul system shall provide a single data entry point on each end of the backhaul link utilizing a standard Ethernet connection. The Ethernet connection must support 100BASE-

TX and 10BASE-T speeds utilizing an RJ45 Connector (Standard Ethernet pinout). This connection must support TCP/IPv4 with minimum link speeds of 10 Mbps and 100 Mbps capable. In utilizing both the LoS and NLoS solutions, selection and switching between LoS and

NLoS shall be transparent to the devices connecting externally on each end of the backhaul link, and switching shall occur without service interruption. In the event that a single connection solution is used, that connection shall utilize the Ethernet connection described here. All

Ethernet lines shall be certified CAT5e or CAT6 or above.

2.2 LINE OF SIGHT (LoS) REQUIREMENTS FOR BACKHAUL SYSTEM

A Line of Sight (LoS) radio frequency (RF) link depends on numerous unpredictable variables that cannot be specified without considering each individual setup. However, the following LoS requirements are necessary to provide the desired nominal distance performance of the backhaul data communication system.

2.2.1 The LoS system shall be capable of a minimum link distance of at least 25 km over sea water between any two devices, given clear atmospheric conditions and appropriate Line of Sight with or without the use of height enhancing structures on either end.

2.2.2 The LoS system shall employ a method of self-forming, self-healing mesh network connectivity with other LoS systems of the same type.

2.2.3 The LoS system shall have a minimum link speed of 4.7 Mbps under optimum conditions.

2.2.4 The LoS system shall employ frequency hopping in order to hinder detection and interception of the RF link, and shall provide robustness against attempted jamming of the LoS communication system.

2.2.5 The LoS system shall support externally connected antennas on the TSM in order to accommodate the flexible placement of said antennas on the TSM.

2.2.6 Given the LoS system has been pre-configured, the system shall be designed to come up to full operation upon the application of power to its power supply lines with no other interaction.

2.2.7 The LoS system shall be tolerant of sudden disconnection and reconnection of supply power as a regular means of powering down and powering up the system.

2.2.8 The LoS system shall be able to run continuously and indefinitely for the lifetime of the system given adequate power, with no more than one power cycle per 30 days to fix errors. A power cycle is defined as disconnecting power to the power source lines and after 5 seconds reconnecting the power source.

2.2.9 The LoS system shall be able to maintain a connection in conditions up to and including

World Meteorological Organization (WMO) Sea State 4.

2.3 NON-LINE OF SIGHT (NLoS) REQUIREMENTS FOR BACKHAUL SYSTEM

2.3.1 The NLoS system shall be operational globally with the exception of arctic regions traditionally inaccessible by geosynchronous satellites due to angle of incidence to the earth’s surface from the satellites.

2.3.2 The NLoS system shall have a minimum link speed of 0.490 Mbps under optimal conditions.

2.3.3 Given the NLoS system has been pre-configured, the system shall be designed to come up to full operation upon the application of power to its power supply lines with no other interaction.

2.3.4 The NLoS system shall be tolerant of sudden disconnection and reconnection of supply power as a regular means of powering down and powering up the system.

2.3.5 The NLoS system shall be able to run continuously and indefinitely for the lifetime of the system given adequate power, with no more than one power cycle per 30 days to fix errors. A power cycle is defined as disconnecting power to the power source lines and after 5 seconds reconnecting the power source.

2.3.6 The NLoS system shall be able to maintain a connection in conditions up to and including

World Meteorological Organization (WMO) Sea State 4.

Ddl-C41 TERMINATION OF EMPLOYEES WITH NSWCDD BASE ACCESS

The contractor shall insure that all employees who have a NSWCDD badge and/or bumper sticker turn-in the badge and remove the bumper sticker immediately upon termination of their employment under this contract. The above requirement shall be made a part of the standard employee facility clearance procedures for all separated personnel.

The contractor shall advise NSWCDD Physical Security of all changes in their contract personnel requiring

NSWCDD base access.

For involuntarily separated personnel and those separated under adverse circumstances, the contractor shall notify

NSWCDD Physical Security in advance of the date, time and location where the NSWCDD representative may physically remove the employee’s automobile bumper sticker and retrieve the NSWCDD badge prior to the employee departing the contractor’s facility. In the event the employee is separated in his or her absence, the contractor shall immediately notify NSWCDD Physical Security of the separation and make arrangements between the former employee and NSWCDD Physical Security for the return of the badge and removal of the sticker.

DIGITAL DELIVERY OF DATA

(a) Delivery by the Contractor to the Government of certain technical data and other information is now frequently required to be made in digital form rather than in hardcopy form. The method of delivery of such data and/or other information (i.e., in electronic, digital, paper hardcopy, or other form) shall not be deemed to affect in any way either the identity of the information (i.e., as “technical data” or “computer software”) or the Government’s and the Contractor’s respective rights therein.

(b) Whenever technical data and/or computer software deliverables required by this contract are to be delivered in digital form, any authorized, required, or permitted markings relating to the

Government’s rights in and to such technical data and/or computer software must also be digitally included as part of the deliverable and on or in the same medium used to deliver the technical data and/or software. Such markings must be clearly associated with the corresponding technical data and/or computer software to which the markings relate and must be included in such a way that the marking(s) appear in human-readable form when the technical data and/or software is accessed and/or used. Such markings must also be applied in conspicuous human-readable form on a visible portion of any physical medium used to effect delivery of the technical data and/or computer software. Nothing in this paragraph shall replace or relieve the Contractor’s obligations with respect to requirements for marking technical data and/or computer software that are imposed by other applicable clauses such as, where applicable and without limitation, DFARS 252.227-7013 and/or DFARS 252.227-7014.

(c) Digital delivery means (such as but not limited to Internet tools, websites, shared networks, and the like) sometimes require, as a condition for access to and/or use of the means, an agreement by a user to certain terms, agreements, or other restrictions such as but not limited to “Terms of Use,” licenses, or other restrictions intended to be applicable to the information being delivered via the digital delivery means. The Contractor expressly acknowledges that, with respect to deliverables made according to this contract, no such terms, agreements, or other restrictions shall be applicable to or enforceable with respect to such deliverables unless such terms, agreements, or other restrictions expressly have been accepted in writing by the

Contracting Officer; otherwise, the Government’s rights in and to such deliverables shall be governed exclusively by the terms of this contract.

Section D - Packaging and Marking

Ddl-D13 NOTIFICATION OF SHIPMENT

When shipment is made, the contractor shall notify NSWCDD, Code [to be completed at time of award], phone

[to be completed at time of award], prior to arrival of the shipment at NSWCDD, but no later than three (3) days after shipment. Notification shall include the following items:

(a) Contract and item number,

(b) Date of item departure,

(c) Quantity shipped,

(d) Name of carrier,

(e) Method of shipping,

(f) Bill of lading number.

HQ D-2-0006 MARKING AND PACKING LIST(S) (NAVSEA) (NOV 1996)

(a) Marking. Shipments, shipping containers and palletized unit loads shall be marked in accordance with best commercial practice.

(b) Packing List(s). A packing list (DD Form 250 Material Inspection and Receiving Report may be used) identifying the contents of each shipment, shipping container or palletized unit load shall be provided by the Contractor with each shipment. When a contract line item identified under a single stock number includes an assortment of related items such as kit or set components, detached parts or accessories, installation hardware or material, the packing list(s) shall identify the assorted items.

Where assortment of related items is included in the shipping container, a packing list identifying the contents shall be furnished.

(c) Master Packing List. In addition to the requirements in paragraph (b) above, a master packing list shall be prepared where more than one shipment, shipping container or palletized unit load comprise the contract line item being shipped. The master packing list shall be attached to the number one container and so identified.

(d) Part Identification. All items within the kit, set, installation hardware or material shall be suitably segregated and identified within the unit pack(s) or shipping container by part number and/or national stock number.

HQ D-2-0008 MARKING OF REPORTS (NAVSEA) (SEP 1990)

All reports delivered by the Contractor to the Government under this contract shall prominently show on the cover of the report:

(1) name and business address of the Contractor

(2) contract number

(3) contract dollar amount

(4) whether the contract was competitively or non-competitively awarded

(5) sponsor:

(Name of Individual Sponsor)

(Name of Requiring Activity)

(City and State)

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 Origin Government Origin Government

0002 Origin Government Origin Government

0003 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-2 Inspection Of Supplies--Fixed Price AUG 1996

52.246-15 Certificate of Conformance APR 1984

52.246-16 Responsibility For Supplies APR 1984

252.246-7000 Material Inspection And Receiving Report MAR 2008

Section F - Deliveries or Performance

DELIVERY INFORMATION

SHIP TO (DELIVERY) ADDRESS WILL BE CITED ON AWARD DOCUMENT

CLIN 0001 shall be approximately 6 months after date of award – estimated 02/28/2015

CLIN 0002 shall be a six month period – estimated 03/01/2015 through 08/31/2015.

Exercise of this option is contingent upon acceptance of CLIN 0001.

CLIN 0003 shall be as set forth in the Statement of work and the CDRL’s

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS

0001 28-FEB-2015 1 each TBD

0002 6 mths. ADC 1 each TBD

0003 As Required by CDRL’s 1 lot TBD

F.O.B.: Destination

52.211-17 Delivery of Excess Quantities SEP 1989

52.242-15 Stop-Work Order AUG 1989

52.242-17 Government Delay Of Work APR 1984

52.247-34 F.O.B. Destination NOV 1991

Ddl-F20 RECEIVING HOURS OF OPERATION

All deliveries to the Receiving Officer, Dahlgren Division, Naval Surface Warfare Center, Dahlgren, VA shall be made Monday through Friday from 7:00 a.m. to 2:30 p.m., local time. Deliveries will not be accepted after 2:30 p.m. No deliveries will be made on government holidays.

Ddl-F30 PARTIAL DELIVERIES

Partial Deliveries will not be accepted without specific approval from the Contracting Officer.

Ddl-F40 CONTRACTOR NOTICE REGARDING LATE DELIVERY

In the event the contractor anticipates or encounters difficulty in complying with the contract delivery schedule or date, he/she shall immediately notify, in writing, the Contracting Officer and the cognizant Contract Administration

Services Office, if assigned. The notice shall give the pertinent details; however such notice shall not be construed as a waiver by the Government of any contract delivery schedule, or of any rights or remedies provided by law or under this contract.

Section G - Contract Administration Data

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

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

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by 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.acquisition.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 must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

TBD

(Contracting Officer: Insert applicable document type(s). Note: If a “Combo” document type is identified but not supportable by the Contractor's business systems, an “Invoice” (stand-alone) and

“Receiving Report” (stand-alone) document type may be used instead.)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in

WAWF, as specified by the contracting officer.

https://www.acquisition.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

(Contracting Officer: Insert inspection and acceptance locations or “Not applicable”.)

(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 ____

Issue By DoDAAC ____

Admin DoDAAC ____

Inspect By DoDAAC ____

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 or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the “Send Additional

Email Notifications” field of WAWF once a document is submitted in the system.

(Contracting Officer: Insert applicable email addresses or “Not applicable.”)

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

(Contracting Officer: Insert applicable information or “Not applicable.”)

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

Ddl-G10 GOVERNMENT CONTRACT ADMINISTRATION POINTS-OF-CONTACT AND

RESPONSIBILITIES

[ ] Procuring Contracting Officer (PCO):

(a) Name: Karen Lenox

Code CS20-3

Naval Surface Warfare Center

Dahlgren Division

17632 Dahlgren Road Suite 157

Dahlgren, Virginia 22448-5110

Phone: (540) 653-7081

E-mail: karen.lenox@navy.mil

(b) PCO responsibilities are outlined in FAR 1.602-2. The PCO is the only person authorized to approve changes in any of the requirements of this contract or orders issued thereunder and, notwithstanding provisions contained elsewhere in this contract, the said authority remains solely the PCO’s. The contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting

Officer or is pursuant to specific authority otherwise included as part of this contract. In the event the contractor effects any change at the direction of any person other than the PCO, the change will be considered to be unauthorized.

[ ] Contract Specialist:

(a) Name: Roberta Moss

Code CS20-4

Naval Surface Warfare Center

Dahlgren Division

17632 Dahlgren Road Suite 157

Dahlgren, Virginia 22448-5110

Phone: (540) 653- 1053

E-mail: roberta.moss@navy.mil

(b) The Contract Specialist is the representative of the Contracting Officer for all contractual matters.

[ ] Technical Point of Contact (TPOC)

(a) Name: TBD

Code

Address:

Phone:

E-mail:

(b) The TPOC is the PCO’s representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished

Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) as/if specified in the contract as well as the inspection and acceptance of all contract deliverables.

[ ] Alternate Point of Contact (ATPOC) mailto:karen.lenox@navy.mil mailto:roberta.moss@navy.mil

Code:

Address:

E-mail:

(b) The ATPOC is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.

[ ] Paying Office

Address:

(b) The Paying Office makes all payments under the contract.

(c) For the status of payments please use MyInvoice at https://myinvoice.csd.disa.mil/index.htm. First time users must register prior to use MyInvoice.

Ddl-G12 POST-AWARD MEETING

(a) A Post-Award Meeting with the successful offeror may be conducted within 14 days after award of the contract.

The conference will be held at the address below:

Location/Address: NSWCDD DAHLGREN VIRGINIA 22448

(b) The contractor will be given 7 working days notice prior to the date of the meeting by the Contracting Officer.

(c) The requirement for a post-award meeting shall in no event constitute grounds for excusable delay by the

Contractor in performance of any provisions in the contract.

HQ G-2-0002 CONTRACT ADMINISTRATION DATA

Enter below the address (street and number, city, county, state and zip code) of the Contractor's facility which will administer the contract if such address is different from the address shown on the SF 26 or SF 33, as applicable.

https://myinvoice.csd.disa.mil/index.htm

SUPPLEMENTAL INSTRUCTIONS REGARDING ELECTRONIC INVOICING (NAVSEA) (SEP 2012)

(a) The Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the technical instruction (TI), sub line item number (SLIN), or contract line item number (CLIN) level, rather than on a total contract/TO basis, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of other direct costs

(ODCs), materials, and travel, by TI, SLIN, or CLIN level. For other than firm fixed price subcontractors, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal. Subcontractors may email encryption code information directly to the Contracting Officer (CO) and Contracting Officer Representative (COR).

Should the subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the CO and COR; or other method as agreed to by the CO.

(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data

Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and CO on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and CO email notification as required herein.

Section H - Special Contract Requirements

Ddl-H10 EMPLOYMENT OF US GOVERNMENT PERSONNEL RESTRICTED

In performing this contract, the Contractor shall not use as a consultant or employ (on either a full or part time basis) any active duty U.S. Government personnel (civilian or military) without the prior written approval of the

Contracting Officer. Such approval may be given only in circumstances where it is clear that no laws and no DoD or

U.S. Government instructions, regulations, or policies might possibly be contravened and no appearance of a conflict of interest will result.

Ddl-H50 NOTICE OF INCORPORATION OF SECTION K

Section K of the solicitation (Representation, Certifications and Other Statements of Offerors) will not be distributed with the contract; however, it is incorporated in and forms a part of the resultant contract as though furnished in full text therewith.

Section I - Contract Clauses

52.203-3 Gratuities APR 1984

52.203-5 Covenant Against Contingent Fees APR 1984

52.203-6 Restrictions On Subcontractor Sales To The Government SEP 2006

52.203-7 Anti-Kickback Procedures OCT 2010

52.203-8 Cancellation, Rescission, and Recovery of Funds for Illegal or

Improper Activity

JAN 1997

52.203-10 Price Or Fee Adjustment For Illegal Or Improper Activity JAN 1997

52.203-12 Limitation On Payments To Influence Certain Federal

Transactions

OCT 2010

52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber

Content Paper

MAY 2011

52.204-7 System for Award Management JUL 2013

52.209-6 Protecting the Government's Interest When Subcontracting

With Contractors Debarred, Suspended, or Proposed for

Debarment

AUG 2013

52.209-9 Updates of Publicly Available Information Regarding

Responsibility Matters

JUL 2013

52.209-10 Prohibition on Contracting With Inverted Domestic

Corporations

MAY 2012

52.211-5 Material Requirements AUG 2000

52.211-15 Defense Priority And Allocation Requirements APR 2008

52.215-2 Audit and Records--Negotiation OCT 2010

52.215-8 Order of Precedence--Uniform Contract Format OCT 1997

52.215-10 Price Reduction for Defective Certified Cost or Pricing Data AUG 2011

52.215-12 Subcontractor Certified Cost or Pricing Data OCT 2010

52.215-14 Integrity of Unit Prices OCT 2010

52.215-15 Pension Adjustments and Asset Reversions OCT 2010

52.215-18 Reversion or Adjustment of Plans for Postretirement Benefits

(PRB) Other than Pensions

JUL 2005

52.215-19 Notification of Ownership Changes OCT 1997

52.215-23 Limitations on Pass-Through Charges OCT 2009

52.219-8 Utilization of Small Business Concerns JUL 2013

52.219-9 Small Business Subcontracting Plan JUL 2013

52.219-16 Liquidated Damages-Subcontracting Plan JAN 1999

52.222-3 Convict Labor JUN 2003

52.222-19 Child Labor -- Cooperation with Authorities and Remedies JAN 2014

52.222-20 Walsh-Healey Public Contracts Act OCT 2010

52.222-21 Prohibition Of Segregated Facilities FEB 1999

52.222-26 Equal Opportunity MAR 2007

52.222-35 Equal Opportunity for Veterans SEP 2010

52.222-36 Affirmative Action For Workers With Disabilities OCT 2010

52.222-37 Employment Reports on Veterans SEP 2010

52.222-40 Notification of Employee Rights Under the National Labor

Relations Act

DEC 2010

52.222-50 Combating Trafficking in Persons FEB 2009

52.222-54 Employment Eligibility Verification AUG 2013

52.223-18 Encouraging Contractor Policies To Ban Text Messaging

While Driving

AUG 2011

52.225-13 Restrictions on Certain Foreign Purchases JUN 2008

52.227-1 Authorization and Consent DEC 2007

52.227-2 Notice And Assistance Regarding Patent And Copyright

Infringement

DEC 2007

52.227-11 Patent Rights--Ownership By The Contractor DEC 2007

52.229-3 Federal, State And Local Taxes FEB 2013

52.232-1 Payments APR 1984

52.232-8 Discounts For Prompt Payment FEB 2002

52.232-9 Limitation On Withholding Of Payments APR 1984

52.232-11 Extras APR 1984

52.232-17 Interest OCT 2010

52.232-23 Assignment Of Claims JAN 1986

52.232-25 Prompt Payment JUL 2013

52.232-33 Payment by Electronic Funds Transfer--System for Award

Management

JUL 2013

52.233-1 Disputes JUL 2002

52.233-3 Protest After Award AUG 1996

52.233-4 Applicable Law for Breach of Contract Claim OCT 2004

52.242-13 Bankruptcy JUL 1995

52.243-1 Changes--Fixed Price AUG 1987

52.244-5 Competition In Subcontracting DEC 1996

52.244-6 Subcontracts for Commercial Items DEC 2013

52.246-23 Limitation Of Liability FEB 1997

52.249-2 Termination For Convenience Of The Government (Fixed-

Price)

APR 2012

52.249-8 Default (Fixed-Price Supply & Service) APR 1984

52.253-1 Computer Generated Forms JAN 1991

252.203-7000 Requirements Relating to Compensation of Former DoD

Officials

SEP 2011

252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense-

Contract-Related Felonies

DEC 2008

252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013

252.203-7005 Representation Relating to Compensation of Former DoD

Officials

NOV 2011

252.204-7000 Disclosure Of Information AUG 2013

252.204-7003 Control Of Government Personnel Work Product APR 1992

252.204-7004 Alt A System for Award Management Alternate A MAY 2013

252.204-7006 Billing Instructions OCT 2005

252.205-7000 Provision Of Information To Cooperative Agreement Holders DEC 1991

252.209-7001 Disclosure of Ownership or Control by the Government of a

Terrorist Country

JAN 2009

252.209-7004 Subcontracting With Firms That Are Owned or Controlled By

The Government of a Terrorist Country

DEC 2006

252.211-7007 Reporting of Government-Furnished Property AUG 2012

252.211-7008 Use of Government-Assigned Serial Numbers SEP 2010

252.215-7000 Pricing Adjustments DEC 2012

252.215-7002 Cost Estimating System Requirements DEC 2012

252.219-7003 Small Business Subcontracting Plan (DOD Contracts) AUG 2012

252.223-7008 Prohibition of Hexavalent Chromium JUN 2013

252.225-7001 Buy American And Balance Of Payments Program DEC 2012

252.225-7002 Qualifying Country Sources As Subcontractors DEC 2012

252.225-7012 Preference For Certain Domestic Commodities FEB 2013

252.225-7013 Duty-Free Entry OCT 2013

252.226-7001 Utilization of Indian Organizations and Indian-Owned

Economic Enterprises, and Native Hawaiian Small Business

Concerns

SEP 2004

252.227-7013 Rights in Technical Data--Noncommercial Items FEB 2014

252.227-7014 Rights in Noncommercial Computer Software and

Noncommercial Computer Software Documentation

FEB 2014

252.227-7016 Rights in Bid or Proposal Information JAN 2011

252.227-7019 Validation of Asserted Restrictions--Computer Software SEP 2011

252.227-7025 Limitations on the Use or Disclosure of Government-

Furnished Information Marked with Restrictive Legends

MAY 2013

252.227-7026 Deferred Delivery Of Technical Data Or Computer Software APR 1988

252.227-7027 Deferred Ordering Of Technical Data Or Computer Software APR 1988

252.227-7028 Technical Data or Computer Software Previously Delivered to the Government

JUN 1995

252.227-7030 Technical Data--Withholding Of Payment MAR 2000

252.227-7037 Validation of Restrictive Markings on Technical Data JUN 2013

252.227-7038 Patent Rights--Ownership by the Contractor (Large Business) JUN 2012

252.227-7039 Patents--Reporting Of Subject Inventions APR 1990

252.231-7000 Supplemental Cost Principles DEC 1991

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

JUN 2012

252.232-7010 Levies on Contract Payments DEC 2006

252.235-7003 Frequency Authorization DEC 1991

252.243-7001 Pricing Of Contract Modifications DEC 1991

252.243-7002 Requests for Equitable Adjustment DEC 2012

252.244-7000 Subcontracts for Commercial Items JUN 2013

252.247-7023 Transportation of Supplies by Sea JUN 2013

252.247-7024 Notification Of Transportation Of Supplies By Sea MAR 2000

52.202-1 DEFINITIONS (NOV 2013)

When a solicitation provision or contract clause uses a word or term that is defined in the Federal Acquisition

Regulation (FAR), the word or term has the same meaning as the definition in FAR 2.101 in effect at the time the solicitation was issued, unless--

(a) The solicitation, or amended solicitation, provides a different definition;

(b) The contracting parties agree to a different definition;

(c) The part, subpart, or section of the FAR where the provision or clause is prescribed provides a different meaning;

or

(d) The word or term is defined in FAR Part 31, for use in the cost principles and procedures.

52.243-7 NOTIFICATION OF CHANGES (APR 1984)

(a) Definitions.

"Contracting Officer," as used in this clause, does not include any representative of the Contracting Officer.

"Specifically authorized representative (SAR)," as used in this clause, means any person the Contracting Officer has so designated by written notice (a copy of which shall be provided to the Contractor) which shall refer to this subparagraph and shall be issued to the designated representative before the SAR exercises such authority.

(b) Notice. The primary purpose of this clause is to obtain prompt reporting of Government conduct that the

Contractor considers to constitute a change to this contract. Except for changes identified as such in writing and signed by the Contracting Officer, the Contractor shall notify the Administrative Contracting Officer in writing, within 10 calendar days from the date that the Contractor identifies any Government conduct (including actions, inactions, and written or oral communications) that the Contractor regards as a change to the contract terms and conditions. On the basis of the most accurate information available to the Contractor, the notice shall state--

(1) The date, nature, and circumstances of the conduct regarded as a change;

(2) The name, function, and activity of each Government individual and Contractor official or employee involved in or knowledgeable about such conduct;

(3) The identification of any documents and the substance of any oral communication involved in such conduct;

(4) In the instance of alleged acceleration of scheduled performance or delivery, the basis upon which it arose;

(5) The particular elements of contract performance for which the Contractor may seek an equitable adjustment under this clause, including--

(i) What contract line items have been or may be affected by the alleged change;

(ii) What labor or materials or both have been or may be added, deleted, or wasted by the alleged change;

(iii) To the extent practicable, what delay and disruption in the manner and sequence of performance and effect on continued performance have been or may be caused by the alleged change;

(iv) What adjustments to contract price, delivery schedule, and other…