RFI Response Template Attachment 2.xlsx
XLSX spreadsheet 136 KB Posted
- Attached to
- Internal Revenue Service (IRS) Extensible Markup Language Enhancement- Taxpayer Services
- Solicitation number
- 24802025
About this file
This is a Request for Information (RFI) response template for the IRS Extensible Markup Language Enhancement project for Taxpayer Services. The template consists of two main sections: Company Profile and Technical Capability. The Company Profile section requests basic vendor information including company details, points of contact, NAICS codes, existing government contracts, and socioeconomic status.
The Technical Capability section contains 23 specific questions focused on IT support services, labor categories, technical specifications, software capabilities, deployment options, security protocols, and integration requirements. Additional industry feedback is requested through 7 questions covering prior experience, estimated pricing, suggestions for requirement improvements, and feedback on PSC/NAICS code selections. The RFI response is due January 16, 2025 at 1:00 PM ET. The project involves providing a COTS XML authoring solution with licenses for up to 1,000 users to create and maintain tax instructions and publications, with specific requirements for IRS DTD compatibility, minimal training needs, and web-based deployment capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 24-80 RFI.docx | DOCX document | |
| 24-80 SOW Attachment 1.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Part I Company Profile
| 24-49-A-PMO-OBSA Microfilm Machine Servicing RFI Response | |
| RFI Response Due Date: XX/XX/XXXX at XX a.m. | |
| Part I: Company Profile | |
| 1 | Company Name and Address |
| 2 | Company technical Point of Contact (POC) and Contract Lead POC information to include name, title, telephone number, and email address |
| 3 | Applicable NAICS (North American Industry Classification System) Code |
| 4 | List active governmentwide contracts that your company has been awarded (GWACs, IDIQs, and BPAs – include applicable SIN) |
| 5 | Identify Business Classification / Socio-Economic Status (e.g., large, small, 8(a), women owned, hub-zone, SDB, Service-Disabled Veteran Owned) |
| 6 | Identify subcontracting/partnering/teaming possibilities |
Part II Technical Capability Enter Project Title RFI Response Matrix
| RFI Response Due Date: 01/16/2025 @ 1:00PM ET | ||
| Part II: Technical Capability | ||
| Enter Corresponding Task Header | ||
| Number | Questions | Answers |
| 1 | What kind of IT support services can you provide after delivery of the software? | |
| 2 | What labor categories do you think would be needed to support the IRS’ requirement, and why? | |
| 3 | What level of expertise would those resources have? | |
| 4 | Is it possible to customize the user interface and features to align with specific organizational requirements or XML schemas? | |
| 5 | How does the software ensure that all edits comply with XML schemas (e.g., XSD, DTD, or Relax NG)? | |
| 6 | Does the software include collaboration features, such as simultaneous editing or commenting, to facilitate teamwork? | |
| 7 | Is the software available for web, desktop (Windows, macOS, Linux), or mobile platforms? Are there cloud-based or on-premise deployment options? | |
| 8 | What are the minimum and recommended system requirements for deploying the software on various platforms (e.g., Windows, macOS, Linux, or web servers)? | |
| 9 | For web-based deployments, what server configurations (e.g., web server, database, or operating system) are required? | |
| 10 | What is the installation process, and does the company provide scripts or documentation for automating deployment? | |
| 11 | Are there options for configuring default settings, templates, or schemas during the deployment process to align with organizational standards | |
| 12 | For web-based applications, what browsers and versions are supported? Are there any specific browser extensions or plugins required? | |
| 13 | How are software updates delivered and managed? Is there a mechanism for deploying updates without disrupting ongoing work? | |
| 14 | For web-based supplication, is there additional cost for staging, testing in addition to the production environment? | |
| 15 | How does the software handle scalability as the number of users and documents grows? | |
| 16 | What measures are in place to ensure system uptime and reliability? | |
| 17 | Does the software support multi-factor authentication and integration with IRS security protocols? | |
| 18 | How does the solution align with Section 508 compliance requirements? | |
| 19 | Can the software integrate with existing IRS tools like SharePoint? | |
| 20 | What kind of technical documentation and training materials are provided? | |
| 21 | How does the software manage version control for XML documents? | |
| 22 | Does the software offer a sandbox environment for testing features or updates? | |
| 23 | How does the software address potential conflicts during simultaneous edits by multiple users? |
| Industry Feedback | |
| 1 | What is your company’s prior experience with delivering web-based XML software to the Government? |
| 2 | What is a ballpark estimated price to successfully deliver these requirements? |
| 3 | Please provide any additional insights that would help us craft the requirement(s) to best meet our needs to provide the contemplated services. |
| 4 | Are there any concerns with the primary Product Service Code (PSC) selected? If so, which PSC would be a better fit? |
| 5 | Are there any concerns with the NAICS code selected? If so, which NAICS code would be a better fit? |
| 6 | Does the draft SOW (RFI Attachment 1) clearly describe the Government’s requirement? |
| 7 | Is there any specific language in the draft documents that may be unnecessarily driving cost, schedule, or performance? |
File details come from the government source that posted it. Updated .