Government_Rd2_Answers_(10072019).pdf

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 1 of 6

Document Description Page # Section/ Paragraph Question/ Comment Proposed Action/ Change Government Answer

Attachment_1_- _CLIN_Structure_(03142 019)

CLINs 1-4 & 5-8

Q&A 1 confirmed that the requirement is no longer for a single COTS solution, therefore an updated Attachment 1 is now required.

Please amend the Attachment 1 - CLIN structure to allow for additional software CLINs, e.g. Device Inventory/Auditing Solution under CLIN 1-4 and 5- 8, plus additional CLINs for Secure-Release and Pull-Printing via CAC/PIV, under existing CLINs such as 1a-4a and 5a-8a, for example.

Attachment 1 - CLIN structure will not be changed because all capabilities of the COTS solution will be required for every order.

Attachment 2 - Statement of Work (09092019)

3 4.3 Regarding the QA response in round 1, page 6, it is stated that within the DOD the software must be compatible with an embedded CAC solution and a 3rd party CAC solution, whatever is used on the existing device.

Please consider limiting this to MFDs with embedded CAC solutions only, as there are limitations to external CAC solutions that are only compatible with one or another specific Secure Release software. Many of these external CAC solutions are not FIPS 201 compliant, nor can they allow users an interface to manage print jobs at the MFD. If the MFD cannot support an embedded solution, it should either be excluded, or the vendor should be allowed to replace the external solution with one that is FIPS 201 compliant and compatible with their Secure Release software. Please add an optional CLIN to replace an external CAC authentication solution, under the scheme proposed in our question regarding CLINs 1-4 and 5-8 in Attachment 1, e.g. CLINs 1b-4b, 5b-8b. SOW will not be changed because external CAC Solutions on all DLA MFD contracts are FIPS 201 compliant.

Attachment 2 - Statement of Work (09092019)

6 7.5 Compliance with DOD wide SMARTCARD and DOD PKI standards, and support all approved physical cards related to CAC released print, throughout the contract term.

Please remove or change this requirement, as this is a hardware device specific issue. All CAC authentication is by nature governed at the MFD as a Sole Sign On, (a.k.a. SSO). All CAC-PKI compatible Secure Release software uses the device’s PKI authentication, and is compatible with CAC SSO authentication at the device to identify the user. CAC users authenticate at each device to make the connection to a Secure Release server, as the CAC users cannot insert their CAC cards directly into a Secure Release server.

Please note that there will be case where hardware from a specific OEM can no longer support a PKI standard or network change during the contract term. This hardware will need replacement or updating by the installing OEM under that hardware contract. This is a hardware requirement, and cannot be included under this software agreement.

Updated Section 7.5 of the SOW to remove the requirement to support all approved physical cards related to CAC released print.

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 2 of 6

Attachment 2 - Statement of Work (09092019)

7 10.1 MPS software license must be transferable to a replacement device if original device is removed from the network during the contract period.

Please consider removing or changing this requirement. Secure Release software is designed specifically for each OEM hardware, and is transferrable to new hardware from the same OEM.

This is not always the case where there is a change in OEM hardware. Furthermore, device configurations for Secure Release software differ from OEM to OEM, and may not be configured properly by a new OEM to be compatible with the Secure Release software. Those new OEM hardware contracts must stipulate compatibility and configuration with the awarded Secure Release software vendor for this requirement to be implemented. Not all Secure Release software will be transferable from one OEM hardware to another OEM hardware, and may incur additional licensing fees. SOW wil not be changed and this requirement remains the same.

SP700019R1002_(Confor med_09092019)

3 & 46 There is a contradiction in these two sections. Page 3 states this will be a single award IDIQ.

However, Page 46 L.26/(2) (iv) states the Govt will make only one award for each line item.

Please clarify the intent and structure for award.

The Government understands this concern and this is a single award IDQ so only one award will be issued to the lowest priced technically acceptable vendor. This comment results in no change to the RFP.

SP700019R1002_(Confor med_09092019)

3 Period of Performance

This section states the IDIQ will have an up to 3-year ordering period from time of award. The estimated period of performance is January 12, 2020 - January 11, 2022 (which is only a 2 year period).

Please clarify the intended Period of Performance.

This is an error by the Government and the up to 3-year ordering period is January 12, 2020 - January 11, 2023.

SP700019R1002_(Confor med_09092019)

3 Important Dates

If any answers to the Round 2 Q&A create a contradiction or confusion, please confirm that clarifications may be submitted.

Vendors can submit clarifications after the Government submits round 2 answers. However, the Government reserves the right to provide an answer or to not provide an answer to the requested clarification. If the Government provides a clarification, it will be provided via an amendment so all vendors are aware of the clarification provided.

SP700019R1002_(Confor med_09092019)

3 Important Dates

We request a minimum of two weeks to finalize and submit proposals once all Q&A have been posted. The Government will make this determination prior to posting the round 2 answers.

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 3 of 6

IN Structure SP7000-19-R-1 1 CLIN 10, 11

Can DLA clarify the 365 on-site training and consulting? It can be read one of two ways.

(1) DLA expects the vendor to be on call for training, help and consulting (backend support), if/when it's needed, throughout the year; or (2) DLA expects an FTE, on site at DLA, to assist DLAs IT teams with the software. Only need the clarification, because pricing changes when it's backend support for a year vs. the offerer supplying an FTE for each CLIN (10 and 11), to DLA. CLINs 0010 and 0011 refers to backend support as requested, but the technician must arrive onsite to provide the support.

Standard Form 1449 Also Page 4 of Question and Answer #1 8 DLAD Note Re

Please clarify with the auction that if for instance 3 businesses qualify for the technical. And 3 businesses take part in the Auction - only 1 Business is going to be awarded the contract? Thank you for the clarification

In-accordance-with (IAW) page 3's "General" paragraph a single award IDIQ will be the result of this RFP. All vendors found to be technically acceptable will be able to participate in the reverse auction (RA). The single award IDIQ will be awarded to the vendor who's proposal represents the lowest priced technically acceptable offer. This comment results in no change to the RFP.

Attachment 1 1

CLIN

STRUCTURE

0010 & 0011

Is the EACH Price per Hour or is the EACH Price per 8 hour period The EACH price is per 8-hour typical work day or daily price.

Attachment 1 1 CLIN STRUCT

The $30k maybe used for initial installation travel as well as future service call travel?

As stated by the Government's Rd 1 answers page 9, "The $30,000 listed on Attachment 1, CLIN 0012, is a set amount the Government expects to obligate to cover the awardee's travel required for orders placed for MPS during life of the IDIQ contract and its subsequent orders. Any unused CLIN 0012 funds will be deobligated from the IDIQ orders." With that said, CLIN 0012 is only to be used for travel required by the Government for CLINs 0010 & 0011. Travel required for initial installation shall be included in the per license costs.

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 4 of 6

Attachment 1 1

Attachment 1

CLIN

Structure Form & Page 7 of SF 1449 Pricing

The only pricing being submitted is that which would be included in 0001 to 0012?

Confirming all that is required is to complete the Unit Price Column for 0001 to 0012?

2.PRICING says submit a price proposal for the three year ordering period, but with no knowledge of exact quantities that is not possible.

All the vendors need to do is submit pricing in the RFP's "Attachment 1 - CLIN Structure (03142019" MS Excel document. This document already contains quantities with a 3-year ordering period weighting assigned. The weighting assigned on this document provides an estimated percent of orders that will be placed off of a given tier/CLIN.

4.4.3 The

requirement to report on devices which are relocated is complex.First, someone would need to provide an update to the location and then the system would need to log each change activity as a move.

Since there could be devices from multiple manufacturers they would all be required to report moves consistently.

Please remove the requirement to track relocation.

Updated Section 4.4.3 of the SOW to remove the requirement to track device relocations.

9 There is no CLIN for training. With very different costs for on-site vs vitrual, there seems to be a need for multiple.

Please provide CLINS to cover on-site and remote training. Set duration expectations in the

CLIN.

CLINs 0001-0004's description, "Device Software Licenses to include Installation, Training/Technical Support, & 1st Year Maintenance"; initial training shall be provided within the per license pricing provided by the vendor.

Additionally, any additional training beyond the initial training required by the Government is convered by CLIN 0010 which the pricing provided by the vendor is per day where a day accounts for 8 hours.

This comment results in no change to the RFP.

8 10.5 Rebuilding device management servers

Will this be a new CLIN? IAW the Government's Rd 1 answer provided on page 9, "Section 10.5 is added to the SOW to address server rework.

Also, CLIN 0009 description is updated to include server rework."

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 5 of 6

4 4.5.1 Section 508 Compliance

Device Management applications are not intended for general end user use, but only for IT administrators. Section 508 compliance should not be a requirement when only a small group would be accessing the application. Request the government withdraw this requirement.

IAW the Government's Rd 1 answer provided on page 5, "Section 508 of the Rehabilitation Act of 1973 & 29 U.S.C § 794(d) applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology.

Information technology, as defined by FAR 2.101, includes software and is as follows, "The term “information technology” includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources.

Also, IAW the Government's Rd1 answer provided on page 7, "As stated in the RFP's DLAD Procurement Note L29 Section 508 Requirements on page 46, "By submission of its offer, the offeror affirms that its Electronic Information Technology (EIT) supplies and services are accessible as outlined in the law, the standard, and FAR Subpart 39.2." IAW this statement, an offerors MPS proposed software shall be 508 compliant at time of submission of its offer."

This comment results in no change to the RFP.

SOW 2 4.2.2/4.2.3

It is not clear whether each location will have it's own implementation of the solution and if so, how many of them there will be an in what branches of the service.

Additionally, it is not clear how DLA will gain concurrence from the branches to allow this information to be sent outside their network. Finally, the requirement that be gathered and made available real time does not take into account that the data will likely be rather "near real time" within the customer network but then will need to be sent to a centralized database on a periodic basis.

Please clarify the expected technical architecture expected including which DoD networks will be covered, how many of them there will be and where the centralized database will reside and how it should be populated. Consider utilizing a FedRAMP authorized provider to store the centralized database as most of the locations will already be using one or more for something.

Information on technical architecture expected cannot be determined in advance. Orders will be placed as customers provide their requirements for MPS software that they intend to manage within their internal network. "Near real time" or real time data gathered within the customer network is acceptable.

Also, the sending of this near real time or real time data to a centralized database on a periodic basis is acceptable, but the user must be able to define the period, as well as, be able to set up adhoc transmission.

SOW 3 4.4.2

Will DLA be providing costs to be used in these analyses? Please clarify the source of this information.

Costs may be provided if a available, but if costs are not available, the MPS software must use industry standard costs.

SP7000-19-R-1002 Attachment 5 - Question and Comment Form Page 6 of 6

SOW 2 4.2.8

In order for the solution to produce downtime data, the help desk tickets generated by the solution (and presumabley by phone as well) will need to be closed.

Please clarify how the information regarding the closure of tickets will be provided in order to provide downtime reporting.

Downtime data will only have to track when the device goes down.

Attachment 1 1 Item 0012

The limit of a total of $30,000 for travel expenses is not commensurate with the expected need for on-site implementations across the country.

Request that travel be quoted on a per server implementation basis as are professional services for software installation

Travel for initial implementation shall be included within the per license pricing for CLINs 0001-0004

SOW 8 10.3

Test environments take the same number and types of resources as production environments.

These should be considered additional implementations and included in the costs just as production implementation should be. You may consider adding a CLIN for the cost to convert a test environment from test to production as the implementation will not have to be completely redone, but there will be effort involved. SOW and CLIN will remain unchanged.

Attachment 7