Amendment 0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICAITON NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicble)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICIATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 11)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a)By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPIRATION DATA (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

SP330020Q5013

Amendment 0003

Vendor Questions:

Question 1: Regarding the number of IoT devices which should be included in the quote (CLIN0001 and 0002 Qty), it seems to indicate the bidder should propose this quantity AND the review criteria may favor bids with larger numbers of IoT devices delivered. As the not-to-exceed value for this contract is $250k, there is actually significant room there to potentially deliver several hundred IoT devices within this budget. Is the intention to have bidders look at utilizing the entire $250k available and deliver the most sensors possible, or would it be more advantageous to just propose something more like qty 10 for CLIN0001 and 0002, and target an overall quote cost much lower (more like $35k or so)?

Answer 1: It is the intention to have the bidders utilize the entire $250k available. This takes into account a year’s worth of cellular service for sensor, any costs for storing data on the bidders cloud environment and support costs including travel to initially install the sensors.

Question 2: If the larger number is desirable, is there any benefit to including additional sensor functionality on some of the sensors to allow the team to investigate other IoT sensor applications too? Our system is quite modular, so we could technically deliver IoT devices which meet CLIN0001 and 0002 requirements, but include additional sensor functionality as well, allowing them to potentially be used for other purposes if desired

Answer 2: For this specific project, we are just focusing on sensor functionality stated for CLIN 0001 and CLIN 0002. However, the IoT sensors selected should have the capability to be modular where additional sensors could be added for future opportunities.

Question 3: What are the success or acceptance criteria for a successful pilot?

Answer 3: The acceptance criteria for the successful are as follows. A historical baseline of measurements from CLIN0001 for the various equipment stated in the SOW to help with preventative maintenance, maintenance scheduling and possible fault indicators. For CLIN0002, the acceptance criteria is to have an automated way to collect usage in hours on the forklifts the IoT devices are installed on without having personnel to manually visit each forklift every month.

Question 4: Is it fair to assume that you’d like the vendor to engage with your teams in the process of deciding which assets to monitor (eg Forklifts, Towlines) and what the design & capabilities of the IoT initiative should be to deliver value in the form of reduced maintenance, location management, or other value drivers?

Answer 4: We expect the bidder to engage and assist with the placing of the IoT devices to ensure that the outcome as stated in the SOW is successful.

Question 5: How many ForkLifts and “conveyors” do you want to be monitored as a part of this prototype initiative?

Answer 5: That is up to the bidder to determine the optimum mix of CLIN 0001 and CLIN 0002 taking affect all costs associated with the cellular connectivity, cloud environment and support costs. However, CLIN 0001 and 0002 should be of equal quantities.

Question 6: What role will your innovation team play in this initiative and what technical capabilities do that possess?

Answer 6: The innovation team will help facilitate the workshop where various technical personnel will be involved to help with ensuring the success of this sprint. The capabilities range from network, security, application and some Azure IoT hub experience?

Question 7: Are you expecting, or otherwise interested in, training design to enable your team’s teams to develop firmware, hardware and cloud software on/with our products?

Answer 7: For this project, the firmware, hardware and cloud software will not be developed by the DLA. The bidder will handle all development for firmware and hardware. There might be minimum development on the cloud environment where maybe some reports might be built.

Question 8: Is quotation inclusive of all shipping costs and travel related costs for onsite work?

Answer 8: The quote and eventual award will be firm fixed price and must include all costs associated with this project.

Question 9: We do not appear to have a CAGE code assigned to it. How do we address/add to database?

Answer 9: Offerors may obtain information on registration requirements via the SAM website at http://www.sam.gov.

Question 10: Can you also please clarify the number of IOT prototype devices to be provided: 2 per location (2 CLIN 0001 and 2 CLIN 0002 total)?

Answer 10: For the Hill AFB location, there will only be one of each CLIN, this is so the DLA can troubleshoot prior to the New Cumberland delivery and install. For the New Cumberland location, the number of each is dependent on the bidder. See answer for question 1.

Question 11: Is building a web application to a part of the scope you would like us to prepare a bid for? Our Company provides out of the box fleet management capabilities but depending on your requirements to store, analyze and visualize information specific to your use case (eg location, vibration, noise, power consumption) there may be capabilities beyond the scope of our out-of-the-box Product.

Answer 11: The building of a web application is not a requirement of this bid. If some out of the box capabilities exist for visualization those could be possibly used. The data that is collected by the sensors will be migrated to DLA’s cloud environment where the customized visualization will be built.

Question 12: I noticed in the SOW document, there is a reference to a “CLIN 0003”, is this future work to build a web application requesting bid for a web app as well or just integration w/ Azure IoT Hub?

Answer 12: CLIN0003 is the bidder’s cloud environment that will capture IoT Sensor data. That data then will be transported to DLA’s cloud environment. The requirement of a complete end-to-end IoT solution requires that the bidder has some out of the box capability for minimal reporting of the IoT sensor data being collected. In addition, CLIN 0003 must support the pushing out of Firmware updates, Remote Diagnostics of the IoT Hardware Devices and as mentioned above some device specific metrics.

Question 13: Regarding CLIN 0001, are you looking to monitor all asset types in the prototype phase (eg “on SI Systems Towlines, Honeywell (FKI) Series 55, 56, and 57 Man aboard Cranes and Baldor belted conveyor systems.”) or can we focus on one during the 45 day sprint?

Answer 13: All asset types will be monitored during the entire performance of this prototype. There is no 45 day sprint, there will be a 3-4 day sprint.

Question 14: Regarding CLIN 0001, Can you provide details on the power supplies that our IoT devices can we tap into for these assets?

Answer 14: The main power sources are 480 VAC for all. Towline has 120VAC available. The Series cranes have 120VAC, 72VDC battery. Vendors would have to install additional DC to DC converters if lower DC voltages are required.

Question 15: Regarding CLIN 0002, our HW is built to be easily extensible with many sensor types including what your RFQ desires, would it be sufficient to demonstrate the portability/extensibility requirements by having a modular design that allows for added Pressure & humidity sensors? Other sensor mentioned (GPS, ToF, VOC) could be added in a similar fashion but it would increase scope and cost.

Answer 15: For CLIN 0002, the utilization of forklifts measured in hours is the only requirement. However, the capability to add different sensors to the IoT hardware is a requirement.

Question 16: Regarding CLIN 002, Can you provide details on the power supplies that our IoT devices can we tap into for the forklifts?

Answer 16: The IoT devices will need to utilize their own power source or possibly use the battery on the forklifts.

Question 17: Regarding CLIN 0003, this is only briefly alluded to in the SOW. What is this?

Answer 17: CLIN 0003 is cloud platform provided by the bidder to manage all the IoT hardware devices, collect the sensor data, manage firmware updates, provide remote diagnostics of the IoT Hardware devices and provide device specific metrics.

Question 18: The SOW states “Required delivery and install is 45 calendar days after award”.

When do you expect to award this contract? Also, there is a reference to '15 calendar days to UT AFB'. Can you please clarify this?

Answer 18: We expect to award the contract 2 weeks after the receipt of quotes. The 15 calendar days is for 1 of each CLIN 0001 and 0002 to be delivered to DLA technicians so that they can begin troubleshooting install prior to delivery and install of remaining HW to New Cumberland.

Question 19: The SOW states “the awardee shall participate, in-person, for three to four days at the DLA facility”, when do you expect to conduct this onsite ‘design sprint’, at the beginning or end of the 45 calendar day project? We would expect beginning as the design sprint would be necessary to align the goals and project teams towards the optimal outcome.

Answer 19: Once the contract is awarded, the install and delivery of the IoT sensors will be required within forty-five calendar days. One week after the delivery of the sensors, the design sprint will begin.

Question 20: How long will the “prototype devices” be used in the evaluation phase of this project? The SOW states “Required delivery and install is 45 calendar days after award and one year from time of award for cloud management,” Does this mean the devices will be evaluated for close to a year before moving on to the next stage of this IoT project?

Answer 20: The devices will be used for the entire year of the project to determine the feasibility of expanding the use of the devices to the entire New Cumberland location and possible other DLA locations

Question 21: Does the hardware delivered at the end of the 45 days need to be in the final form? Or can the HW be in a prototype state? The prototype HW will be usable and have all of the features, but just may be a couple of boards pieced together for this stage of the project.

Answer 21: Yes, the hardware should be in the final form after the forty-five calendar days.

Question 22: How many aisles are in the warehouse(s)?

Answer 22: The main warehouse does not have aisles. The high bay has 67 aisles where the cranes are, but rest of warehouse is broken up into multiple areas. Also note, there about 50 outer warehouses at DDSP that store and feed the main warehouse.

Question 23: How many items/parameters require sensor points? i.e. Each forklift will ultimately require N parameters to be monitored?

Answer 23: There are approximately nine hundred seventy forklifts on the installation.

Question 24: Is CLIN 0001 monitoring for preventative maintenance, maintenance scheduling, both, and/or other reasons?

Answer 24: CLIN 0001 monitoring will be used for both preventative maintenance, maintenance scheduling and possible fault indicators.

Question 25: For CLIN 0002 does it need to support/do all that is listed in CLIN 0001 (i.e.

vibration, noise, & voltage usage) in addition to what is listed for CLIN 0002, or is it a separate request?

Answer 25: The CLIN 0002 device is a separate device to capture the utilization or specifically the number of hours a forklift is being used.

Question 26: What restrictions, if any, exist for physically attaching sensors to all equipment needing to be monitored (e.g. motors, conveyors, forklifts)?

Answer 26: There are no restrictions at this time.

Question 27: What is “noise” specifically being referred to under CLIN 0001? Audio noise or physical motion noise or something else?

Answer 27: The noise being measured is the audio noise of the equipment to possibly capture worn bearings or bushings, broken or worn gear teeth, and rattles.

Question 28: What are all the specification requirements to be sensed for all listed sensors?

(e.g. Sampling rate, range…) Please see the table

• Any special processing required (e.g. rates of change, notifications when beyond a level, etc…)?

Vibration Noise Voltage Usage

Sampling Rate

Reporting Rate

Min / Max Range

Resolution

Other Special Needs / Comments

Answer 28: The goal of the CLIN 0001 sensors is to create a baseline for the various equipment stated in the SOW to help with preventative maintenance, maintenance scheduling and possible fault indicators. Once the baseline is established, the table above can be used to indicate anomalies in the equipment.

Question 29: Can you please provide a link to view the specific Honeywell Series 55, 56, & 57 man aboard cranes?

Answer 29: The cranes being used are over 15 years old and were built by FKI, but Honeywell bought FKI. There are no online links for these specific models.

Question 30: How much weight is placed on the offeror being evaluated by government databases as opposed to corporate references – i.e. has not worked for another government agency to date/ has no government references?

Answer 30: None, past performance will not be evaluated favorably or unfavorably based on an offerors past performance history, only on its acceptability/unacceptability as defined in the RFQ FAR 13.106-2 Evaluation of Quotes.

Question 31: What cellular providers are accessible inside the facility?

Answer 31: Verizon and AT&T

Question 32: In absence of a wireless capable sensor for a measurement, will a hardwired option to the gateway to capture data be permitted?

Answer 32: No

Question 33: If control tag information is available in PLC (example: voltage), will physical/wireless connection option to PLC to capture the data, be permitted in lieu of using additional sensor?

Answer 33:

No

Question 34: Please describe level of edge analytics required on-premise.

Answer 34: No edge analytics is required on-premise.

Question 35: Will the IoT data architecture be High Availability (HA), Fault Tolerant (FT), non-critical… required?

Answer 35: The IoT data architecture

Question 36: Will analytics platform on premise redundancy required to mitigate latency and cloud connection lost risks?

Answer 36: For this project, an analytics platform on premise is not required to mitigate latency and cloud connection.

Question 37: Are on premise IoT holistic equipment condition monitoring KPI’s needed? Or does DLA plan on just using their MS azure cloud KPI’s?

Answer 37: The monitoring of the IoT devices should be provided by the bidder’s cloud environment. At this time, we have not established KPIs but would expect at least a 99% connectivity rate for the sensors as well as a 99% cloud uptime.

Question 38: Please confirm if direct IoT data push to DLA azure cloud is permitted or only Provider cloud to DLA cloud IoT data sharing is permitted?

Answer 38: For this project, direct IoT data push from the IoT data devices to DLA Azure cloud is not permitted. Only the Provider Cloud environment to DLA Cloud is permitted.

Question 39: Does DLA requires restricted SIM ranges for LTE telecom provider and does DLA already have existing restricted SIM to be used for LTE cellular communication?

Answer 39: There is no restricted SIM ranges for LTE telecom provider.

Question 40: Please confirm level of data encryption required?

Answer 40: 128 bit cryptographic key minimal with 256 bit cryptographic key preferred.

Question 41: Please confirm type of locations the on-premise edge gateway and IoT sensors will be mounted for environmental considerations and physical security hardening (example:

panel, pillar…)

Answer 41: They will be mounted on Hyster 4K Sitdown lift forklifts, SI Systems Towlines, Honeywell (FKI) Series 55, 56, and 57 Man aboard Cranes and Baldor belted conveyor systems.

Question 42: Please confirm scalability requirements taking in considerations regional climates and communications requirements?

Answer 42: If this project is deemed successful, the same technology can be used by multiple DLA sites throughout the continental United States.

Question 43: Scope for initial pilot? How many systems, sensors, sensor types? One of each, many?

Answer 43: See answer for question 1 and Schedule of Supplies table of the RFQ.

Amendment 0001 wording

ACQUISITION OPERATIONS J7-AB

430 MIFFLIN AVENUE SUITE 3102A

NEW CUMBERLAND PA 17070-5008

717-770-4192 joshua.woodworth@dla.mil