Questions_and_Answers_-_17_Oct_19.pdf

Item Master Logistics Capability Initiative (IMLCI) Request for Proposal FA8770-20-R-0004 Questions and Answers

# Question Answer

In RFP Attachment 5: Section L there is no mention of the timeline between completion of the Assertion Gate and to offer to submit a full proposal other than “… The due date for full proposal submission shall be determined/ communicated by the PCO at the conclusion of the Gate. Offerors will receive 30 days from the date of notification to submit a full proposal…”

As we must have resources available to meet a 30 day turn, we would request more detailed information on how much time the program office is planning for review of the assertions.

10 days? 30 Days? 90 Days? Any approximation would be helpful.

The Government intends to notify offerors whether or not they are provided the opportunity to submit a full proposal on or around 1 November 2019.

2 Reference: Section K, FAR 52.204-08 We would like to clarify the solicitation offeror size standard since the Reps & Certs includes the SB NAICS code 541511, yet this does not appear to be a small business set-aside in other text. Please confirm what size standard of offerors will this solicitation will be awarded.

The referenced information is simply identifying the NAICS code for this acquisition and the associated size standard. This acquisition IS NOT a small business set aside, rather a full and open competition in accordance with FAR 15.3 as stated in the solicitation.

3 Reference: Section L, 4.2.4.4 Subfactor 4 – Product Evaluation

“…Populate the website with data prepared by the Offeror in sufficient detail to demonstrate each capability; the Offeror can create and pre-populate as many data structures as necessary to enable the desired capabilities…”

Is it your intention to provide this data upon acceptance of the ITFR assertions? Is it possible to get this added to the current solicitation?

The Government does not intend to provide a data set for this subfactor. The Offeror should prepare the proposed product with a data set of their choosing that will demonstrate the product’s capabilities.

4 Reference: Section L, 4.2.4.4 Subfactor 4 – Product Evaluation

“…Provide the capability to manage interface integrations using the Offeror’s exchange framework (See RFP Attachment 8, Product Evaluation Supplement) to allow the Source Selection Team to complete the following:

a. Create new interfaces (3 inbound and 3 outbound)

There is no DID associated with subfactor 4 for the RFP. Formats for legacy interfaces are in the TDP and the DLA spec will be released post contract award.

Item Master Logistics Capability Initiative (IMLCI) Request for Proposal FA8770-20-R-0004 Questions and Answers

b. Update an existing interface by changing a data element (name, structure, and/or length)

c. Update an existing interface by adding a data element

d. Import and Export test data (stubbed data load);

e. Test business rules and error handling against stubbed data loads in accordance with the Offeror’s instructions…”

Will there be any specific DID or formats that these interfaces will be required to meet? Any existing APIs to current data, specific sources, etc? Again is it possible to get this information as soon as possible?

5 This RFP contemplates procurement of commercial items, yet it cites DFARS 252.227- 7013, Rights in Non-Commercial Technical Data; -7014, Rights in Non-Commercial Computer Software; and -7015, Rights in Commercial Technical Data as the governing Data Rights clauses for this procurement.

These clauses are not applicable to commercial computer software and commercial computer documentation. Please confirm that offerors are permitted to propose that commercial computer software and documentation be subject to the offeror’s standard commercial license as contemplated in FAR 12.212.

Offerors are permitted to propose commercial computer software and documentation to be subject to the offeror’s commercial license.

However, any non-commercial technical data or non-commercial software would be subject to the applicable DFARS clauses.

6 In the Basic IDIQ Model Contract, section AFLCMC/HIK-H003(1)(a) states that the Contractor must deliver source code if it “ceases to support the Source Code Materials generally.” Could you please provide further detail on what ceasing to support Source Code means?

Ceasing to support shall occur when the offeror no longer provides sustainment, bug fixes, patches etc… that maintains the underlying product.