Attachment 1 Statement of Work Revised Amend 0001.pdf

SP330020Q5013 Attachment 1 – Statement of Work Page 1 of 5

1. Background

The Defense Logistics Agency (“DLA”) is the Department of Defense’s largest logistics combat support activity. DLA provides worldwide support, primarily to the military services. Other customers include US civilian entities and foreign countries.

This Statement of Work (“SOW”) supports a joint project between the DLA J6 Innovation Team and DLA Distribution to build and prototype the collection of data through Internet of Things “(IoT)” edge devices.

DLA Information Operations (“DLA J6”) provides information technology (“IT”) to the DLA community. This technology is secure, modern and functional. The Innovation Team rapidly delivers prototype IT capabilities, with a focus on stakeholder engagement, experimentation and the iterative cycle. The team builds new things that have the potential to change how DLA does business.

The mission of DLA Distribution is to provide a full range of distribution services using a seamless, tailored, worldwide Department of Defense distribution network that delivers effective, efficient and innovative support to combatant commands, military services, and other agencies during peace and war.

A. DLA Distribution Susquehanna, Pennsylvania is a dual-sited operation, headquartered in New Cumberland, Pa. with additional facilities at Mechanicsburg, Pa., that provides nine million square feet of covered storage space, and as of 2015, maintains nearly 770,000 different National Stock Numbers worth $13 billion. It coordinates material management and distribution of mission critical items including military and commercial repair parts, industrial, medical supplies, tires, and aerial delivery equipment, optimizing all resources with a focus on safety, quality, and continuous process improvement.

B. The DLA Distribution Susquehanna, Pennsylvania’s mission is to provide world-class distribution services to enhance the readiness of the DoD and other customers, through effective and efficient receipt, storage, control, shipment, and disposal of materiel. It strives to be a values-based team known for workforce excellence and providing superior distribution services on time, every time.

2. Funding, Period of Performance and Evaluation

This Prototype is not to exceed $250,000.00. Required delivery and install is 45 calendar days after award and one year from time of award for cloud management, CLIN 0003 and ongoing support.

DLA shall make award in accordance with this not to exceed amount. Offerors shall be evaluated in accordance with the following technical factors, on a best value basis in accordance with FAR

13.106. Section three provides the specifics. Generally, DLA seeks the best mix of:

SP330020Q5013 Attachment 1 – Statement of Work Page 2 of 5

• number of IoT devices

• sensor functionality

• connectivity methods

• security; and

• offeror’s ability to provide ongoing and support for the pilot effort (to include potential in-person participation)

3. Scope

A. General

This SOW supports the Innovation Team to build and test a rapid prototype for an end-to-end IoT platform from physical IoT hardware that includes various sensors, Connectivity and Cloud hosted device console to measure DLA Distribution warehouse equipment. Specifically, we seek to attach IoT hardware with sensors to various (yet-to-be-identified) pieces of equipment. This equipment might be: 1. fixed to the floor, such as conveyor belts; or 2. in intermittent locomotion, such as forklifts.

Part of the scope of this pilot (see details below) shall be to determine the equipment that, if tagged with IoT hardware, would yield the most valuable data.

These IoT hardware must be able to attach to the wide range of equipment without causing any damage on connection or removal.

B. Sensor Technology

CLIN 0001: The IoT hardware must have plug-and-play capability that allows the provider’s cloud solution to automatically understand the device and start interacting with it without the user of the device having to write any device code. For this prototype, the IoT devices will be placed on SI Systems Towlines, Honeywell (FKI) Series 55, 56, and 57 Man aboard Cranes and Baldor belted conveyor systems. The IoT hardware will need to be fitted with sensors that have the capability to measure and capture the following:

1. Vibration

2. Noise

3. Voltage usage

CLIN 0002: In addition, the prototype will need to measure and capture the daily utilization of a fleet of Hyster 4K Sitdown lift forklifts individually. It is up to the vendor to determine the appropriate sensors to be used on the IoT hardware to measure utilization, specifically hours of each forklift.

SP330020Q5013 Attachment 1 – Statement of Work Page 3 of 5

Even though this prototype is restricted to the scenarios above, it is desired the IoT hardware selected also have the capability to be fitted with sensors that have the capability to capture the following:

• Acceleration (Accelerometer)

• Distance (Ultrasonic sonar, Time of Flight)

• Location (GPS)

• Humidity

• Rotation (Gyroscope)

• Power consumption

• Motion (IR Beam-break)

• Flex

• Force

• Pressure

• Gas

The IoT hardware should be able to perform basic edge computing on the data that is being captured by the installed sensors so that to limit the amount of data being transported to the providers online cloud platform. The IoT hardware must be housed in a protective outer layer to shield the electronics from the warehouse environment. The IoT hardware may be self-powered so long as they are designed to operate for at least 3 years or they can draw from an external power source.

C. Connectivity/Data Extraction

The IoT hardware should utilize LTE cellular technology to communicate with the providers cloud platform. If a specific IoT hardware device is not able to connect to provider’s cloud platform via a cellular due to a weak cellular signal, the capability must exist to utilize a mesh network with other IoT hardware devices to pass the sensor data to the provider’s cloud platform. All sensor data that is passed from the IoT hardware device via cellular or through the mesh network must be encrypted.

The sensor data that is being collected by the IoT hardware devices will be captured in the providers online cloud platform. The providers online cloud platform will provide the capability to manage all the IoT hardware devices at the New Cumberland facility. This includes

1. Firmware updates

2. Remote Diagnostics of the IoT Hardware devices

3. Device specific metrics

Provider’s cloud platform must have the capability to export data in a general format that can be ingested to an environment DLA uses for IoT data. DLA anticipates using Microsoft Azure IoT Hub to pass the captured sensor data because it is an existing toolset to which DLA has access. DLA is responsible to transport data from the provider’s cloud environment to DLA’s Azure IoT Hub environment (or similar). Upon that transfer, the

SP330020Q5013 Attachment 1 – Statement of Work Page 4 of 5 data shall be deleted from the provider’s cloud environment. To the maximum extent practicable, the provider shall help DLA facilitate the data transfer.

D. Operational and Cyber Security

(1) The contractor is required to apply Operations Security (OPSEC) to enhance protection of classified and critical information (CI) pursuant to DoD Directive 5205.02, "DoD OPSEC Program;

DoD 5205.02-M, "OPSEC Program Manual;" National Security Decision Directive Number 298, "National Operations Security Program;" DLA Instruction 3606.01 “Operations Security (OPSEC) Program," Oct. 03, 2018; DLA Manual 3606.01, "Operations Security (OPSEC)Program," Oct. 10, 2018 ; and supplementary instructions. Service OPSEC guidance may also apply if the contracted activity is performed in a Service level operational environment. If a conflict is identified between Service and higher-level guidance, contact the servicing Contract Officer for clarification.

(2) The contractor will accomplish the following minimum requirements in support of the DLA OPSEC Program. Protect those items of CI, applicable to operations. Items of critical information are those facts, which individually, or in the aggregate, reveal sensitive details about the mission, operation, etc., and thus require protection from adversarial collection or exploitation.

(3) Include OPSEC as part of its ongoing security awareness program and take all required OPSEC training provided by DLA.

(4) Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the contractor in support of the mission.

As included in the contract

DFARS 252.204-7000 – DISCLOSURE OF INFORMATION (OCT 2016)

(a) The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless—

(1) The Contracting Officer has given prior written approval;

(2) The information is otherwise in the public domain before the date of release; or

(3) The information results from or arises during the performance of a project that involves no covered defense information (as defined in the clause at DFARS 252.204-7012) and has been scoped and negotiated by the contracting activity with the contractor and research performer and determined in writing by the contracting officer to be fundamental research (which by definition cannot involve any covered defense information), in accordance with National Security Decision Directive 189, National Policy on the Transfer of Scientific, Technical and Engineering Information, in effect on the date of contract award and the Under Secretary of Defense (Acquisition, Technology, and Logistics) memoranda on Fundamental Research, dated May 24, 2010, and on https://www.acq.osd.mil/dpap/dars/dfars/html/r20190215/252204.htm#252.204-7012

SP330020Q5013 Attachment 1 – Statement of Work Page 5 of 5

Contracted Fundamental Research, dated June 26, 2008 (available at DFARS PGI

204.4 (DFARS/PGI view)).

(b) Requests for approval under paragraph (a)(1) shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 10 business days before the proposed date for release.

(c) The Contractor agrees to include a similar requirement, including this paragraph (c), in each subcontract under this contract. Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.

E. Workshop and ongoing Support

The awardee shall provide technology (as described elsewhere in this document) that is essential to the prototype. However, this technology is just one of many elements, all of which the Innovation Team must coordinate with a “Design Sprint.” This process is an adapted version of Google Venture’s process1. Under this acquisition, the awardee agrees to become part of an ad hoc team and work inside this process. Other stakeholders include other OTA awardees, military service subject matter experts and other key individuals across the DLA enterprise. Therefore, the awardee shall participate, in-person, for three to four days at the DLA facility where we prototype this technology. This facility is described in section 1 background.

In addition the awardee shall provide ongoing support for all firmware updates, remote diagnostics of hardware devices, network connectivity issues, data forwarding and collection for the duration of the contract. All support calls need to be answered within one hour of being received with a dedicated customer service representative.

1 1 https://www.gv.com/sprint/ http://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/PGI204_4.htm http://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/PGI204_4.htm http://www.acq.osd.mil/dpap/dars/pgi/frameset.htm?dfarsno=204_4&pgino=PGI204_4&dfarsanchor=204_4&pgianchor=204_4