24-021-OITA -IDT Innovation and 24-022-OITA - IDT Detection_Questions and Responses.docx

24-021-OITA - Identity Theft Innovation and 24-022-OITA - Identity Theft Detection

RFI Vendor Questions and Consolidated Responses are as follows:

Q1. Microsoft Word or PDF. Not to exceed 20 pages not including the required business information and cover page. Pages should be single-spaced, minimum 11-point Times New Roman font with a minimum of one-inch margins on all sides.”

Is the government requiring offerors to submit a Microsoft Word or PDF capabilities statement in addition to submitting the excel files or will simply completing the excel files suffice as a response?

· A word or PDF capability statement is acceptable in providing the capabilities statement. The excel spreadsheet is optional.

Q2. The government stated that this work is a recompete. Can you please provide industry with the incumbent contract information to include contractor name and contract number?

· These two requirements (Innovation and Detection) are a recompete of work that is currently distributed across three contracts:

· Identity Theft (IDT) Detection 2032H5-19-F-00795 (Deloitte Consulting LLP)

· Identity Theft (IDT) Strategic Analysis and Portfolio Management Support 2032H5-19-F-00836 (ASR Analytics LLC)

· Identity Theft (IDT) Innovation 2032H5-19-F-00531 (ASR Analytics LLC)

Q3. Both 24-IRA-021-OITA – Identity Theft (IDT) Innovation Questions.xlsm and 24-IRA-022-OITA – Identity Theft (IDT) Detection Questions.xlsm are identical, does the IRS want respondents to submit both documents if a vendor is submitting capabilities to support one PWS (Innovation or Detection)?

· If you want to be considered for one or both PWSs, please indicate this in your documentation and provide the capability statements for one or both.

Q4. Is this initiative linked to the IRS SOP and funded by IRA?

· At this time, these PWSs are not IRS SOP or anticipated to be funded by IRA.

Q5. (innovation) Section 4.4. Task 4: Quick Response and Innovation: Can the government confirm if these requests also include requests that are used for law enforcement entities?

· Yes, these requests at times support law enforcement efforts within the IRS.

Q6. (Innovation) Section 4.5. Task 5: Segmentation and Network Analysis: Can the government provide a list of the software stack, tools & algorithms currently in use?

· Tools and methods change over time to provide most applicable analytic solution. Modeling efforts include neural networks and tree-based ensemble models. Team leverages Linux shell scripts, Apache Spark, Kubernetes, Apache Iceberg, MinIO, Python, Postgres CLI, Jupyter Lab, Cytoscape.

Q7. (Innovation) Section 4.6. Task 6: Strategic Path and Anomaly Detection and Mitigation: Can the government confirm if assessments of risk activity targeting Tax Assistance Center interactions is included in the threat path analysis?

· Yes, this type of analysis is performed in this workstream, as well as within the broader IDT Portfolio.

Q8. (Innovation) Section 4.6. Task 6: Strategic Path and Anomaly Detection and Mitigation: Can the government provide the analytics capabilities that are being used today for to identify and mitigate abuse through IRS phone lines?

· No.

Q9. (Innovation/Detection) Can the government provide Key Personnel requirements needed for this task order?

· This information may be provided with the RFQ.

Q10. (Innovation/Detection) Will the government provide an estimated hours by task area for the LH tasks (Task 2, 4, 5, 7)?

· This information may be provided with the RFQ.

Q11. (Innovation/Detection) Will this PWS be competed under the RAAS DAIS 2.0 contract or under a separate competitive procurement?

· This has not been determined at this time.

Q12. (Innovation/Detection) Please provide the current number of FTEs for each task area.

· The current FTE information will not be provided.

Q13. (Innovation) Are there specific constraints preventing the current pilot from moving to production?

· If this question is related to the IDT Innovation PWS "The anomaly detection model was developed in RAAS in 2023 and is in a pilot stage," there are no specific constraints to keep the model from production.

Q14. (Innovation) Does the IRS have the ability to proactively identify developing patterns to quickly deter bad behaviors?

· The work of these PWSs analyzes tax return data near to real-time in addition to historical analysis of trends and is largely reactive to emergent patterns.

Q15. (Detection) Does the current solution capture metrics so RAAS can real-time monitor performance and TCO/ROI?

· Yes.

Q16. (Detection) Would IRS consider buying a tested and proven “a fit for purpose” software product now in use by several tax authorities?

· Neither Innovation nor Detection has authority to purchase software.

Q17. (Detection) Is the IRS considering releasing the solicitation as a small business set-aside?

· That has not been determined at this time.

Q18. (Detection) 4.11 - Task 11. IDT Taxonomy and Neutral Dataset: Can the government provide clarity on IMF/BMF Taxonomies; can you specify the code base, datasets, and current analytic methodology?

· IMF Taxonomy: Evaluates record-level IMF data to create taxonomy populations and associated revenue. SQL and Python scripts are used to create the underlying datasets and R-scripts are used to produce samples from each of the taxonomic categories. Monte Carlo simulations are applied to the samples to arrive at estimates.

· BMF Taxonomy: Evaluates record-level BMF data to create taxonomy populations and associated revenue. Python scripts that execute SQL code develop descriptive reports of taxonomy categories using basic statistical methods to calculate revenue categories. The BMF Taxonomy also leverages sampling for part of the taxonomy and develops confidence intervals for samples.

Q19. (Detection) 4.12 - Task 12. Transition of Work: Does the government have an FY that the government intends to transition Task 8, 9, 10 and 11 to the government personnel?

· That has not been determined at this time.