QuestionsResponses_Ext.pdf

QUESTIONS & RESPONSES (after Amendment #0001 to Extend)

RFP #15A00019R00000071/0001 – Barcode Scanner SDK, Page 1 of 2

Procurement:

Question 1: Are you required to purchase a perpetual license, or is there an option to purchase an annual yearly contract?

o A: ATF will entertain both options if the Offeror submits pricing for both.

Question 2: If perpetual license is the only purchase method, are you looking to purchase the licenses outright and then pay monthly for support? Or spread the license payments over the course of the 5-year term?

o A: Please submit pricing for both since the budget/fund sources for out years are not fully known.

Technical Requirements:

Question 3: Is Native SDK and Web SDK licenses required on all mobile devices?

o A: ATF plans to integrate the scanning functionality into an application using a Web SDK (ex: scanning one item during a workflow) and also have a Native SDK for a specific use case (scanning multiple items in an evidence vault) on the same mobile device. These SDKs would interface/integrate with the same software application.

o A: ATF anticipates using the Native SDK on approximately 2,000 active devices and the Web SDK on approximately 3,100 active devices. Tiered pricing as described in the RFP should be provided for both. ATF would like the option to select a combination of either, for the same device.

Question 4: Or will specific devices require only Native SDK and others only Web SDK?

o A: No. ATF would plan to use one or both on the same device.

• If so, please provide the breakdown of the number of devices that will require Native SDK and Web SDK.

o A: See above.

“4.5 Requirement 5 – Downloading Scanned Items The SDK must support wireless transmission of scanned information to Spartan.”

Question 5: Is this a requirement for both Web SDK and the SDK product?

o A: The intent of this requirement is to ensure a device does not have to be connected to an external device in order to download information (i.e. a docking station connected to a laptop). It appears both the Web SDK and Native SDK satisfy this requirement.

QUESTIONS & RESPONSES (after Amendment #0001 to Extend)

RFP #15A00019R00000071/0001 – Barcode Scanner SDK, Page 2 of 2

“4.7 Requirement 7 – SDK Implementation

The SDK must support native implementation and web implementation options.”

Question 6: Is the ATF looking to procure a license for both a Web SDK as well as a Native SDK?

o A: ATF will entertain both options if the Offeror submits pricing for both.

“4.8 Requirement 8 – Security Considerations

The SDK must not transmit any of the following information to the software company:

• Location information of the scan

• IP address

The SDK shall run internally on ATF’s network without any outside interaction. If the SDK requires outside interaction, such as usage monitoring, the offeror must clearly state what is being sent outside ATF’s network and to where because ATF may need to disable this capability of sending information outside of ATF’s network.”

Question 7: Does the ATF prefer a non-communicating license for the SDK or will you accept a product that requires connectivity to servers in Europe (Switzerland)?

o A: ATF requires a non-communicating license for SDK. No information can be transmitted outside ATF’s network.

Question 8: And if so will the ATF be able to provide some other method to provide proof of active license use? As an example we would accept a quarterly screen shot of an MDM or other product that shows the count of devices being used o A: Yes. ATF is open to providing usage information such as the example on a set interval as agreed. The method can be agreed upon between ATF and the vendor.

“4.8 Requirement 8 – Security Considerations