Outcome-Enterprise Productivity Security Business Application Developer and Cloud Capabilities.docx
DOCX document 47 KB Posted
- Attached to
- DA10--Systems Integrators for Enterprise Productivity, Security, and Business Applications
- Solicitation number
- 36C10B27Q0130
About this file
This is a Request for Information (RFI) issued by the Department of Veterans Affairs (VA) Office of Information and Technology to conduct market research for identifying qualified System Integrators and Managed Service Providers capable of delivering enterprise technology services across five capability groups: (A) Productivity and collaboration with unified endpoint management; (B) Identity and access management with endpoint detection and response; (C) Customer case management, enterprise resource planning, low-code application development, business intelligence, and project management; (D) Source code management, DevOps, cloud infrastructure, and integrated development environments; and (E) Enterprise technical support and professional services. The VA seeks a single accountable integrator responsible for delivering and sustaining outcomes across all identified capability groups, supporting over 540,000 users across Windows, iOS, Android, macOS, and Linux platforms, with over 16,000 on-premises and cloud-based servers serving more than nine million Veterans through 1,300 VA sites and telehealth services.
Respondents must address 14 desired outcomes including single-point accountability, transition without service disruption, interoperability on open standards, continuous security coverage, authorization within 60 days, data protection and legal discovery, 24x7 support availability, user adoption and training, licensing transparency, governed low-code and DevOps platforms, governed artificial intelligence capabilities, portability and clean exit provisions, enterprise governance, and change management. The RFI specifies constraints requiring NIST SP 800-53 Revision 5 compliance, U.S.-only data residency with screened U.S. personnel, FIPS-validated encryption, Section 508 accessibility conformance, 10-year audit logging, open standards integration (SAML, OIDC, SCIM), and contractor personnel vetting. Responses must not exceed 50 pages, include a Rough Order of Magnitude cost estimate identifying cost drivers and assumptions, and address all five capability groups. The RFI is technology and product agnostic, welcoming non-Microsoft solutions and hybrid approaches. This RFI is companion to a previous product alternatives RFI and does not constitute a binding solicitation; interested parties should monitor SAM.gov for future RFP or RFQ releases.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B27Q0130.docx | DOCX document | |
| SI Capabilities Reference.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
REQUEST FOR INFORMATION (RFI)
Enterprise System Integrator / Managed Service Provider for Enterprise Productivity, Security, Business Application, Developer, and Cloud Capabilities
Department of Veterans Affairs (VA) [Office of Information and Technology] THIS IS A REQUEST FOR INFORMATION ONLY. IT IS NOT A SOLICITATION. This RFI is issued solely for market research. It is not a Request for Quote (RFQ) or Request for Proposal (RFP), and it is not a guarantee that either will be issued. It does not commit the Government to contract for any services described herein. VA will not evaluate unsolicited proposals in response. The Government does not intend to pay for any information submitted and will not reimburse any costs of responding. The information provided may be used by VA in developing its acquisition strategy and Performance Work Statement (PWS) or Product Description (PD). Responding is voluntary. Information received becomes the property of the Government and will not be returned. Respondents are responsible for adequately marking proprietary, restricted, or competition-sensitive information. Draft outcomes and example measures in this RFI are illustrative, are subject to change, and are not final requirements.
1. Purpose The Department of Veterans Affairs (VA) is conducting market research to identify qualified System Integrators and/or managed service providers (MSPs) capable of integrating, transitioning, operating, modernizing and sustaining enterprise technology services that support VA's mission-critical operations.
VA seeks industry approaches that deliver measurable outcomes, maintain operational continuity, ensure interoperability, improve cost transparency, and establish clear accountability across enterprise technology environments.
This RFI is a companion to VA’s previous product alternatives RFI, which sought information from product vendors regarding alternative technologies and associated pricing. This RFI focuses on identifying qualified System Integrators and MSPs capable of delivering, integrating, operating, and sustaining enterprise capabilities at VA's scale, whether through existing technologies, alternative solutions, or a combination of providers.
Responses will inform VA's acquisition strategy, potential procurement structure, small business participation, and approaches to measuring service performance and accountability.
VA's market research is technology and product agnostic. Respondents may recommend retaining, integrating, modernizing, or replacing existing technologies. VA has not identified a preferred technology, OEM, platform, or solution. Respondents must demonstrate their ability to deliver and sustain all identified enterprise capability groups, whether through their own solutions, subcontractors, technology partners, or a combination of providers, while maintaining end-to-end accountability for service outcomes.
Non-Microsoft products are welcome. An Integrator can recommend keeping Microsoft products, replacing a single product, or proposing a different mix across the enterprise.
2. Background and Mission Need
2.1 The Environment
Technology Scale. VA's enterprise includes over 540,000 users on workstations, laptops, tablets, and smartphones running Windows, iOS, Android, and macOS (and Linux where applicable). This footprint includes 16 on-premises mail servers, on-premises directory services, on-premises server-based licenses, and multiple cloud tenancies across Azure Commercial and Azure Government environments.
Reference Footprint (Current-State Estimates Only). More than 22,000 per-user and 17,000 per-app low-code licenses; business intelligence subscriptions supporting more than 3,000 workspaces; more than 13,000 source-code-hosting subscriptions (including more than 5,700 with advanced security add-ons); more than 2,000 project and portfolio management licenses; more than 6,000 diagramming licenses; approximately 1,000 integrated development environment subscriptions compatible with .NET. VA's technology environment supports over 16,000 Windows-based on-premises and cloud-based servers and several hundred Veteran-facing applications. These systems support healthcare, benefits, and other mission-essential services for more than nine million Veterans, including services delivered by over 120,000 healthcare professionals across more than 1,300 VA sites, telehealth, and online benefits applications.
Current State: These capabilities are delivered under a Microsoft Enterprise Agreement.
Operating Model. VA seeks a single accountable integrator responsible for delivering and sustaining outcomes across all identified capability groups, regardless of the number of product vendors, resellers, subcontractors, or cloud providers supporting the solution.
Non-Microsoft products are welcome. A System Integrator can recommend keeping Microsoft products, replacing a single product, or proposing a different mix across the enterprise. VA seeks one and only one accountable System Integrator with the depth to lead all five capability groups. Teaming is welcome.
2.2 Capability groups
The capability areas in VA’s product RFI are grouped below. System Integrator solutions must include all groups.
| Group |
| Capability areas |
| A |
| Productivity and collaboration; unified endpoint management; endpoint operating system licensing |
| B |
| Identity and access management; endpoint detection and response; identity threat protection; email and collaboration threat protection; cloud access security; extended detection and response across domains; data governance and compliance (data loss prevention, classification, insider risk, eDiscovery, audit logging, retention) |
| C |
| Customer and case management; enterprise resource planning and supply chain; low-code application development, workflow and robotic process automation, business intelligence, and shared data platform; project and portfolio management; diagramming and visualization |
| D |
| Source code management and DevOps; cloud infrastructure and platform services; and integrated development environments compatible with .NET |
| E |
| Enterprise technical product support (24x7 reactive and proactive); professional and implementation services |
2.3 Why now, and what VA is trying to change
VA wants to buy reliable, secure, interoperable enterprise services and not just licenses. It wants clear visibility into what it pays for, freedom to add or change individual products without breaking the rest, no gap in security protection during any change, and the ability to transition out cleanly.
3. Desired Outcomes The fourteen outcomes below describe what should be different or better when an integrator succeeds. They are not tasks. VA does not prescribe methods, staffing, or labor categories. Example measures marked [draft] are starting points and numeric values in brackets are placeholders. Respondents are asked to respond to them in the questions in section 4.
| Outcome |
| What is better when it succeeds |
| Example measures [draft] |
| O1. Single-point accountability across multiple category stack |
| VA deals with one accountable party (i.e., System Integrator) for the entire solution. Problems are not passed between a product vendor, a reseller, a cloud provider, and a subcontractor. The integrator works inside VA governance (change, architecture, security) and does not build a parallel one. |
| • Service-level misses attributed to a third party versus accepted and corrected [target: none excused except where caused solely by a Government-controlled dependency] |
• One escalation path covering all products in the group
• Cross-provider issues open longer than [30] days without an approved mitigation plan [target: zero]
| O2. Transition without disrupting operations |
| Users, clinicians, and Veteran-facing applications and services do not experience degradation or lose email, identity, devices, or collaboration during any change. Moves from on-premises to cloud, and between products, are phased, tested, and reversible. |
| • Zero unplanned loss of mission-critical services (including clinical and telehealth support) at any cutover wave |
• Mailbox and data integrity verified for [100]% of migrated users; no message or file loss
• Successful first-attempt migration for at least [99]% of users per wave
• Tested rollback for every wave; on-premises mail servers retired on an agreed schedule (if applicable)
| O3. Interoperability and coexistence on open standards |
| The proposed environment works as a whole whether VA keeps current products, replaces some, or mixes. Replacing one capability does not break others. Users do not juggle separate logins or interfaces. |
| • Single sign-on across all in-scope components |
• Integrations built on open standards (for example SAML, OIDC, SCIM) and documented APIs; share of integrations that depend on proprietary-only interfaces reported
• Replacement of any single capability validated in test with no regression in dependent capabilities
| O4. Continuous security coverage and visibility |
| There is no gap in protection for endpoints, identities, email and collaboration, and cloud applications at any point in a change. Security signals from different vendors are correlated in one view for VA security operations. |
| • Protection coverage of [100]% of enrolled devices and in-scope identities maintained through every transition wave |
• Security signals from all domains correlated natively or through open APIs and VA’s SIEM
• Security incidents reported and vulnerabilities remediated within VA-defined timelines [per VA requirements]
| O5. Authorization, data residency, and compliance |
| Nothing operates in VA production until authorized. VA data stays in the United States (US) and is handled by screened US personnel. Authorization work does not become the schedule bottleneck. |
| • ATO decision targeted within [60] calendar days of a system meeting intake requirements (service-level target only; no guaranteed outcome) |
• Zero VA data in any unauthorized environment
• US-only data residency and screened US personnel for [100]% of in-scope access
| O6. Data protection, records, and legal discovery |
| Retention, legal holds, classification, data loss prevention, and audit history survive every migration. VA can still investigate, produce records, and meet retention rules. |
| • Audit logs retained up to [10] years and searchable |
• Zero loss of legal holds, retention labels, or eDiscovery capability during migration
• Classification and data loss prevention policies preserved or replaced with documented equivalents before cutover
| O7. Support and availability |
| Problems are resolved quickly by the System Integrator under one accountable support model, including escalation to product engineering. When a cloud service fails, VA gets service-level credits without having to chase each vendor. |
| • 24x7 problem resolution across the full stack with severity-based response and escalation commitments |
• Root-cause analysis for all high-severity incidents
• Published availability and trailing 12-month actual uptime reported against each service-level target; vendor credits passed through per VA-approved method
• Regular operational health assessments completed and corrective actions tracked to closure.
| O8. Adoption, training, and accessibility |
| Per user products are accessible on every device used by the named user, and it works for users with disabilities. Training and change support provided to all impacted users before go-live. |
Before a switch, the System Integrator must identify which workflows, roles, sites, and shifts are affected and coordinate with the relevant administrations and local leaders.
For major VAMC rollouts, include hands-on, in-person training across shifts.
• Each licensed user able to use core productivity applications across their desktop, laptop, tablet, and smartphone
• Role-based training complete before cutover for [100]% of affected users
• Published accessibility conformance reports (Section 508, WCAG, EN 301 549) for every product; gaps carry dated remediation plans
• User satisfaction and adoption reported monthly
| O9. Licensing and cost transparency |
| VA can see exactly what it buys. License entitlements are tracked across each user and/or device. Third-party products needed to make the pieces work together are named and priced. VA can forecast consumption-based costs before it scales usage. |
| • Full bill of materials with unit prices; no assumption that VA already holds any license |
• Entitlements tracked per user across devices
• Third-party and interoperability costs identified separately from licensing and services
• Cost forecast available before any consumption increase (cloud, Super Intelligence, automation)
| O10. Governed low-code, DevOps, and cloud platforms |
| Low-code applications, automations, dashboards, repositories, and cloud services stay governed as they grow. Existing assets are inventoried, reconciled, and moved or retired deliberately, not lost or orphaned. |
| • Inventory of applications, automations, workspaces, and repositories reconciled before and after any move |
• Center-of-excellence governance, development/test/production lifecycle, and data loss prevention policies in force
• Governed landing zones, resilience, and cost tooling for the cloud services in use (currently more than 100)
O11. Governed Super Intelligence-Enabled Capabilities
Super Intelligence-enabled capabilities are visible, governed, secure, auditable, and priced predictably. VA understands where these capabilities are used, how Government information is handled, how decisions are influenced or automated, and what costs may increase as usage scales.
Government information is not used for model training, model improvement, or other purposes without appropriate authorization and oversight.
• Inventory of Super Intelligence-enabled capabilities and whether each capability is included in the base license, separately licensed, or consumption-based.
• No transmission or use of VA information for model training without written authorization.
• Audit logging for Super Intelligence-enabled activities affecting Government information or enterprise services.
• Human review or approval requirements established for Super Intelligence -enabled actions that modify production systems, enterprise configurations, access controls, workflows, or Government information.
• Visibility into Super Intelligence-related consumption, utilization, and associated costs.
• Defined governance, oversight, and risk-management processes for Super Intelligence-enabled capabilities.
• Ability to disable, restrict, replace, or transition Super Intelligence-enabled functionality without disruption of core enterprise services.
| O12. Portability and clean exit |
| VA can move away from any product or from the integrator without data loss, penalty, or dependency on proprietary tools. Requirements that create lock-in are identified early. |
| • Full data export in non-proprietary format demonstrated by test, with no fidelity loss |
• Exit plan kept current and costs known up front
• Lock-in risks reported with each major design decision
| O13: Enterprise Governance and Continuous Improvement |
| VA receives effective governance, strategic planning, portfolio oversight, performance reporting, and continuous improvement across all capability groups. Decisions are made using accurate operational, financial, security, and service data. The contractor proactively identifies risks, technical debt, optimization opportunities, and lifecycle issues before they become operational problems. |
| • Quarterly executive reviews completed on schedule |
• Enterprise risk register maintained and reviewed monthly
• Improvement recommendations delivered and tracked to closure
• Technical debt reduction plan maintained and updated annually
• Portfolio-level service reporting delivered on schedule
• Continuous improvement initiatives completed against agreed targets
• Service health reviews completed for all capability groups at least quarterly
| O14: Change Management |
| The System Integrator must have a robust change management system. |
• Before a switch, the System Integrator must identify which workflows, roles, sites, and shifts are affected
• Coordinate with the relevant administrations and local leaders
• Give VA evidence for a go/no-go decision
4. Questions for Respondents Please answer concisely and specifically. If your answers include past performance, VA prefers a few directly comparable engagements over a long list. Answers should show your work as a single Systems Integrator across all categories.
4.1 Understanding of the outcomes
1. As a System Integrator, how are you going to meet all these requirements?
2. Present your high-level approach for sequencing a transition across all the capability groups. What goes first and why?
3. VA requests that respondents recommend appropriate performance baselines, measurable targets, service levels, and reporting methodologies based on your proposed solution supporting comparable enterprise environments.
4. Respondents are encouraged to identify alternative performance measures, potential tradeoffs, opportunities to improve cost efficiency, and commercial or delivery approaches that could better support VA's mission
5. What are the five largest risks to achieving these outcomes, and which are within your control?
6. Please provide which products you would retain or replace to meet the capability requirements and why?
7. Please provide a comparable example where you as a System Integrator have resolved a problem spanning multiple providers. For example, if clinicians can’t sign in and every provider says its service is up, who owns restoring access and has the authority to get it done.
8. Please provide a measurable response to the outcomes in Section 3 by providing what baseline you would use, what target you propose, how VA would verify performance, and what corrective action you would take if you missed the target. Please provide actual results from comparable work so VA can judge what you have delivered.
9. For change management, explain how lessons from one rollout will be incorporated into the next change.
5. Constraints These apply to any eventual solution. They are listed so respondents can address them. VA will publish detailed requirements and clause text in any future solicitation.
· Authorization. Security and authorization requirements are based on NIST SP 800-53 Revision 5, VA Directive 6500, and VA Handbook 6500.6 Appendix C. Any awarded solution must complete VA’s Authorization to Operate (ATO) process before operating in VA production. For this RFI, respondents are not required to hold an existing FedRAMP certification, per VA policy [confirm whether to cite the policy memorandum, which is referenced in the product RFI draft]. FedRAMP references describe VA’s current environment only. [Confirm FIPS 199 impact level for public text; the source does not state it.]
· Data location and personnel. U.S.-only data residency in a segregated environment, with access limited to screened U.S. personnel. Services are provided within the continental United States; remote delivery is acceptable and on-site work may be required.
· Encryption. Strong encryption in transit and at rest using FIPS-validated cipher suites.
· Accessibility. Section 508 conformance with published conformance reports (ACR/VPAT), covering WCAG and EN 301 549.
· Records and privacy. VA data remains Government property; retention, legal holds, and audit logging (up to 10 years) must be preserved; privacy and health information handled under applicable law and VA policy.
· Open standards. Integration must be described using open standards (SAML, OIDC, SCIM) and documented APIs so that VA can change individual products.
· Personnel vetting. Contractor personnel require VA-adjudicated background investigations commensurate with access.
6. Response Instructions
1. Eligibility. All interested sources are invited, including small businesses and socioeconomic categories. State business size and status under NAICS [NAICS CODE] and any relevant contract vehicles.
2. Scope of response. Respond to all capability groups (A through E).
3. Length. No more than [50] pages, excluding the identification page.
4. Identification. Name of company, address, point of contact, phone number, email address, [UEI,] and CAGE number. [Source also requests a fax number; confirm whether to keep.]
5. Content. Responses to Section 4 questions (numbered to match), including comments on the outcomes and measures, and any other information.
6. Submission. By [DATE, TIME ET] via [METHOD, to be specified]. Questions about this RFI are due by [DATE].
7. Proprietary information. Mark responses “Proprietary Information” if business sensitive. Do not submit personally identifiable information, protected health information, or non-public VA information.
8. Provide a Rough Order of Magnitude (ROM) cost estimate for delivering, integrating, transitioning, operating, and sustaining the proposed enterprise solution.
Identify significant cost drivers, including third-party products, licensing, implementation, migration, integration, and ongoing support. Include key assumptions, dependencies, exclusions, and potential cost-saving opportunities. Cost ranges are acceptable.
ROM estimates are requested solely for market research and acquisition planning and do not constitute binding price proposals or quotations.
7. Post-RFI Phase Based on market research results, an RFP or RFQ may be made available on Contracting Opportunities at SAM.gov. It is the responsibility of interested parties to monitor SAM.gov for updates. The Government will not provide hard copies of any solicitation. All information regarding the procurement is provided herein, and no additional information will be provided at this time.
End of RFI
File details come from the government source that posted it. Updated .