Responses to Vendor Questions 47QTCB21R0002 020121.pdf

RFP 47QTCB21R0002

Responses to Vendor Questions

QUESTION ANSWER

1. Are contractors responding expected to use existing systems, solutions/software to complete the task, or will we need to propose a solution that can connect CONEXUS, ALLTax, etc?

The contractor will not be using government systems to perform work. The contractor will transmit the file via a secure access link to

CONEXUS.

2. Is the scope of the structured changes described in section 3.3.3.2.3 limited to changes for which no further analysis is required by the contractor because the EPRE COR or CO is providing a determination as to how the changes should be recorded in the ALLTAX database (e.g., the COR/CO provides a determination that a given tax is allowable or unallowable)? Can you explain precisely how “structured” TFS changes are distinguished from those addressed in subsection 3.3.4, Directed TFS Allowability Reviews?

Identified Changes are changes to the ALLTAX file discovered by the Contractor. These are transmitted within three business days of discovery.

Structured Changes are changes to the ALLTAX file directed by the Government. These are transmitted within three business days of notification.

Structured Changes include changes resulting from the EIS CO’s allowability determinations on questioned items reviewed by the EPRE contractor;

however, the EIS CO may under certain circumstances direct structured changes on items which are not the subject of a specific EPRE Allowability Review. The EPRE CO or COR will communicate structured changes to the EPRE contractor.

Directed TFS Allowability Reviews, PWS 3.3.4, describes the effort associated with defined allowability review projects where the EPRE contractor has been asked to review specific TFS items. The EIS CO allowability determination considers the findings presented in the Directed TFS Allowability Review. If the review results in a structured change, the EPRE CO or COR will direct the contractor to make the appropriate change in the ALLTAX file.

3. Assuming "Company X" bids on the RFP on Feb. 9th, 2021, is it correct that its Volume 1A filename should be as follows: "1A Solicitation Package V1 2-9-21 Company X"?

Correct.

“1A Solicitation Package V1 2-9-21 Company X” describes Version 1 of Volume 1A submitted on February 9, 2021 by Company X.

4. If a bidder has a prior record in CPARs and intends to rely on CPARs as evidence of past performance, does the bidder need to provide copies of its CPARs evaluations with its RFP proposal package?

You are not required to attach CPARS reports as our evaluators will access your record through CPARS. Be sure to list your current and prior contracts and task orders on the Past Performance Record tab of Volume 1B Price Proposal.

5. If a bidder has completed its annual certifications and representations in the SAM

Include the certifications required in SECTION K, REPRESENTATIONS, CERTIFICATIONS, AND system, does the bidder need to provide a copy of those representations/certifications (i.e., a FARs Report from SAM) with its RFP proposal package?

If so, should the FARs Report be provided within Volume 3 (Other Addendums) or in another Volume?

OTHER STATEMENTS OF OFFERORS OR

RESPONDENTS, and Attachment 11, Offeror Representations and Certifications, in Volume 1A RFP/Solicitation Package.

You do not need to provide copies of your SAM representations. If you are registered in SAM and your certifications are up to date refer to the instructions in K.1, Offeror Representations and Certifications.

6. Was the duplication on Attachment 10, Past Performance, rows 19 and 25, intentional?

List prior or current Federal contracts or task orders under row 19. The repeat entry on row 25 is an unintended duplication.

7. If a bidder has a DUNS number and a Cage Code and has completed its annual registration in SAM, must the bidder also obtain a "Unique entity identifier" as referenced in 52.212-1(h)? If so: (a) how does a bidder obtain such a Unique Entity Identifier, and (b) which box, if any, must that Unique Entity Identifier appear in the bidder's completed SF33 form?

SAM will begin using the Unique Entity Identifier (UEI) in lieu of the DUNS in April 2022.

If you do not have a UEI assigned, you may continue to use your DUNS. A UEI will be assigned to your enterprise at a later date and no further action is required at this time.

More information about the UEI is available at this address:

https://www.gsa.gov/about-us/organization/federal-acquisition-service/office-of-systems-management/integrated-award-environment-iae/iae-information-kit/unique-entity-identifier-update

8. Should bidders provide the completed representations in Attachment 11 with its RFP proposal package? If so, should Attachment 11 be provided within Volume 1A (RFP/Solicitation Package) or in another Volume?

Yes. Per L.4, Required Proposal Content, include all representations (including those in Attachment 11, Offeror Representations and Certifications) with Volume 1A RFP/Solicitation Package. Note K.1, Offeror Representations and Certifications, if you are already registered in SAM.