II_02_Amendmend 02_2032H323R00005 Questions and Answers.pdf

RFP 2032H323R00005 TRIP DATA COLLECTION, VALIDATION AND ANALYSIS

QUESTIONS REC’D AND GOV’T RESPONSE

Reference: II_01_b_RFP Attachment 1 - PWS v2.pdf, Page 2, Paragraph 1

Question 1: When was the existing system built?

Gov’t (Program Office) Response: TRIP Data Collection commenced in 2016. The TRIP Data Collection System is a contractor-owned system currently residing in a contractor environment. The system is not owned by U.S. Treasury.

Question 2: What is the current system or web system that the existing Excel file format is ingested into?

Gov’t (Program Office) Response: Treasury does not have insight into the specifications used by the incumbent contractor, as statutory requirements specify that data is to be collected by an insurance statistical aggregator outside of Treasury and then provided by the aggregator to Treasury in aggregated or anonymized format. The PWS calls for the proposal to specify the way the Contractor proposes to construct the system for the collection of data.

Question 3: What is the current process or methodology for data cleansing or error handling on Excel/.scv file format ingestion for TRIP insurance updates?

Gov’t (Program Office) Response: See response to Question 2. The PWS calls for the Contractor to address the way data validation is conducted, although provides certain guidance in that regard. See PWS 4.A.x.

Question 4: What administrative interface or console exists to manage trip Excel/.scv file submissions? Can we be afforded screen captures of that interface?

Gov’t (Program Office) Response: See response to Question 2. Treasury does not have screen captures of any interfaces.

Question 5: Is there a workflow or swim lane diagram for the TRIP Excel/.scv file ingestion and processing? What databases does this feed into? What existing cybersecurity/data security protocols or provisions are in place?

Gov’t (Program Office) Response: See response to Question 2. As a result, Treasury is unable to provide the required information. The PWS specifies the nature of cybersecurity/data protocols required to ensure secure collection of data.

Question 6: What is the current FTE load for processing/updating/amending TRIP and .scv submissions?

Gov’t (Program Office) Response: The Government anticipates that this contract will be firm-fixed price and not labor hour. As such, the contractor has responsibility to propose staffing. However, at a high level, Treasury estimates roughly 1.3 FTEs (2570 hours) over all labor categories per year.

Question 7: Is the TRIP filing system integrated within the IRS's SharePoint system or is it a stand-alone system?

Gov’t (Program Office) Response: The PWS calls for the Contractor to construct a system for the collection of data as specified in the PWS that resides outside of any USG systems.

Question 8 Has an instance of code injection ever been recorded, as a cybersecurity issue within the TRIP update system?

Gov’t (Program Office) Response: See response to Question 2; however, Treasury is unaware of any cybersecurity issues experienced by the incumbent contractor.

Question 9: What is the periodicity of submissions for TRIP updates?

Gov’t (Program Office) Response: Treasury is uncertain as to the nature of the question. The TRIP Data Call that is the subject of the PWS is an annual data call, such that only one submission (from numerous responding insurers) is required each year.

As the PWS specifies, the data collection elements may change from year to year.

Question 10: How are TRIP excel/.scv files that error out processed or are the files kicked back to the submitter for repair and reuploading?

Gov’t (Program Office) Response: Errors that the contractor detects in the provided data are to be resolved with the submitting company. If the contractor discovers a possible error, the contractor contacts the insurer, discusses the perceived error and a correction is made by either the contractor or the insurer.

Question 11: Are there periodic yearly high intake cycles, that need to be accounted for from a staffing basis?

Gov’t (Program Office) Response: As specified in the PWS, the greatest amount of activity under the PWS work statement will take place between February 1, when the annual data call commences, and June 1, when the contractor is responsible for providing the aggregated data to Treasury. The heaviest amount of work is from May 15, when the data call ends, to June 1, when the data reports must be submitted. Other work takes place throughout the course of the year, as late or corrected data may be submitted which must be integrated into updated existing reports.

Reference: II_01_b_RFP Attachment 1 - PWS v2.pdf, Pages 3-6, Paragraphs A-B

Question 12: Is the .scv file format layout identical to the excel file format layout?

Gov’t (Program Office) Response: The PWS calls for the contractor to create a .scv file format that collects data identical to the data called for in the Excel spreadsheets created and provided to the contractor by Treasury.

Question 13: What systems will the replacement update that this RFP allows for have to integrate with?

Gov’t (Program Office) Response: The PWS calls for the contractor to create a new system that will be used to collect and manage the annual TRIP Data Call; it will not integrate with any other system. The system will need to be able to generate reports in Excel format upon collection, validation, and aggregation of the data, as the reports must be provided by the contractor to Treasury in that format.

Reference: General Question(s)

Question 14: Since TRIP application is an internet portal application, will the government confirm whether the application need to be hosted by IRS managed services cloud/enterprise portal provider?

Gov’t (Program Office) Response: No, the collection site will need to be provided and managed by the contractor.