ORD OneStream Implementation Services 2.0

VA-27-00011736

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology (OIT) Office of Research and Development

ORD OneStream Implementation Services 2.0

Date: November 13, 2026

VA-27-00011736

PWS Version Number: 3.0

Contents

BACKGROUND

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Office of Research and Development (ORD) requires implementation, configuration, deployment, training, security authorization support, and post-deployment support services associated with the commercial off-the-shelf (COTS) OneStream software platform.

ORD currently utilizes multiple budgeting, planning, reporting, and analytical processes that support research operations, financial planning, field-level budget formulation, portfolio management, and executive reporting. To improve standardization, reporting capabilities, workflow management, data integration, security, and long-term maintainability, ORD is expanding implementation of the OneStream COTS platform as its enterprise planning and performance management solution.

This requirement is for product-associated services necessary to configure and deploy OneStream and its commercially available modules, capabilities, and connectors to support ORD business processes. Required activities include OneStream application configuration, workflow configuration, planning and reporting configuration, role-based security configuration, product-supported data integrations, testing, training, deployment support, documentation, and security authorization support.

Services acquired under this effort are limited to those necessary to make the OneStream COTS solution operational within the VA environment and to support adoption of the configured solution by ORD users. The requirement does not include stand-alone management consulting services, unrelated staff augmentation, or custom software development independent of the OneStream platform.

The resulting OneStream implementation will provide ORD with an integrated platform supporting budgeting, planning, forecasting, workforce planning, analytics, reporting, and related business processes while leveraging commercial capabilities available within the OneStream product suite.

APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

2. Attachment A – Location of all 113 VAMC Sites

3. Federal Information Processing Standards (FIPS) Publication 140-3, “Security Requirements for Cryptographic Modules”, March 22, 2019

4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

6. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022

7. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

9. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters

10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

11. VA Directive 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

12. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

13. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended

15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended

17. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

18. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended

20. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

21. VA Directive 6500, “VA Cybersecurity Program,” September 22, 2026

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25-17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)

23. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

24. VA Handbook 6500.6, “Acquisition Cybersecurity,” October 2, 2026

25. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025

26. VA Handbook 6500.10, “Mobile Device Security Policy,” August 24, 2026

27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

28. OIT Process Asset Library (PAL), OIT Process Asset Library.

29. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

31. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024

32. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024

33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

34. VA Directive 6300, “Records and Information Management,” September 21, 2018

35. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

37. NIST SP 800-53 Rev. 5.2.0 “Security and Privacy Controls for Information Systems and Organizations,” August 27, 2025

38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 19, 2025

39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 18, 2025

40. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

41. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

42. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

43. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

45. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025

46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

47. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

48. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

49. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

50. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

51. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007

52. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

53. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

54. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and Actions,” dated January 20, 2025

55. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

56. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

57. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

58. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

59. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

60. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

61. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

62. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

63. Social Security Number (SSN) Fraud Prevention Act of 2017

64. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

65. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

66. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

67. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

68. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

69. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026

70. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

71. NIST SP 800-88 Revision 2 “Guidelines for Media Sanitization,” September 26, 2025

72. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

73. CISA BOD 26-04: Prioritizing Security Updates Based on Risk, June 10, 2026

74. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

75. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

76. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020

77. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025

78. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025

79. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025

80. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI) Through Unbiased AI Principles,” December 11, 2025

81. OMB Memorandum M-26-10, “Reinforcing Transparency, Accountability, and Oversight of Federal Technology”, March 31, 2026

SCOPE OF WORK

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Office of Research and Development (ORD) requires Contractor support to implement, configure, deploy, and support the OneStream commercial off-the-shelf (COTS) software platform and associated OneStream modules and capabilities.

The Contractor shall provide the OneStream product expertise and implementation services necessary to configure budgeting, planning, forecasting, workforce planning, analytics, reporting, workflow management, data integration, security, and related business capabilities within the OneStream platform. The Contractor shall configure the software to support ORD business processes, including intermediate budget formulation, field-level budgeting, research analytics, operating plan modernization, and associated reporting requirements.

The Contractor shall provide the services required to configure and deploy the OneStream solution, including project management, solution configuration, product-supported integrations, testing, training, security authorization support, knowledge transfer, and post-deployment support. All services performed under this PWS shall be directly related to the implementation, operation, and sustainment of the OneStream COTS solution.

PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12 months with two 12-month option periods.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission. When necessary, tasks under this PWS shall also be performed in VA facilities located in Washington, DC. The Government PM or COR will coordinate with Contractor when on-site performance is required.

Travel may be required to selected VA Medical Centers (VAMCs), research offices, and other Government-designated locations to support field budgeting implementation activities, pilot deployments, training, requirements validation, user acceptance testing, and operational readiness activities associated with the OneStream COTS solution. On-site visits will be scheduled and authorized by the Government as necessary to support successful deployment and adoption of the solution. All travel shall be coordinated in advance with the COR and performed in accordance with the terms and conditions of the contract.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is three (3). Anticipated locations include the following, estimated at two (2) days in duration.

The location could be any of the 113 VAMC research programs.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

PROJECT MANAGEMENT

CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA Program Manager (PM) approved CPMP throughout the PoP.

The Contractor shall prepare and publish agendas and minutes for the kick- status meeting within one business day. The Contractor shall provide monthly status reports to include updates to the PMP, progress reports, identified risks and mitigation plan. Copies of these agendas and minutes shall be provided to the COR.

Deliverables:

A. Contractor Project Management Plan B. Kickoff Meeting Minutes and Agenda

REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

Deliverable:

A. Monthly Progress Report cooperative studies program and million veteran program Intermediate Budget Process The Contractor shall meet the following objectives:

The Contractor shall design, develop, and deliver a comprehensive OneStream solution to modernize existing internal budgeting processes for the Cooperative Studies Program (CS) and Million Veterans Program (MVP). The solution shall include a unified budgeting model supported by a Configuration Design Document that outlines the business requirements, functional and non-functional requirements, overall solution approach, and configuration design. The model shall accommodate more than 113 field sites through customized workflows that facilitate field-level budget inputs, as well as the aggregation of submissions to coordinating centers for review, coordination, and approval. To support these processes, the contractor shall develop planning forms and/or detailed LIM planners to capture CSP and MVP project costs and implement a unified personnel planning model that supports all intermediate budgeting processes while incorporating updated CSP and MVP requirements.

Additionally, the solution shall support a minimum of two budget submissions per fiscal year, with the flexibility to accommodate additional data submission cycles as needed. To promote accuracy and completeness, the contractor shall implement validation controls to ensure that all costs are appropriately planned and accounted for before submissions are finalized. The Contractor shall also develop OneStream export functionality to facilitate the transfer of data into the Research Allocation and Forecasting Tool (RAFT). Also, the Contractor shall implement a role based security model to ensure that each user community has appropriate access to the data and functionality within the solution, consistent with its assigned responsibilities.

Deliverables:

A. CSP and MVP Requirements and Configuration Design Document B. Configured OneStream CSP and MVP Budgeting Model Investigators, Scientific Review and Management Intermediate Budget Process

The Contractor shall design, develop, and implement a OneStream model to support the Intermediate Planning Process for Investigators, Scientific Review, and Management (ISMR). The solution shall include a Configuration Design Document outlining the business requirements, functional and non-functional requirements, solution overview, and configuration design. To support a comprehensive and integrated planning process, the Contractor shall establish data integrations with JIT and the Research Allocation and Forecasting Tool (RAFT), as well as develop forms that display the current status of JIT and RAFT projects. The solution shall provide functionality to update key project information within the integrated data, including project dates, PI assignments, project titles, project costs, and other relevant fields. Additionally, the Contractor shall implement business rules to recalculate estimated program costs based on changes to project start and end dates, along with other applicable planning factors. The model shall support budget planning for the current fiscal year and four subsequent fiscal years, while accommodating the execution of four (4) year review cycles annually. The solution shall provide targeted commentary capabilities to document and explain budget changes and shall include a LIM planner to felicitate the collection of project information and associated costs not captured in authoritative systems. Also, the solution shall include a minimum of 25 workflows to support the various ISRM portfolios, along with reporting, dashboards, and analytics capabilities to facilitate budget oversight and informed decision making. The Contractor shall also implement validation controls to ensure that costs are accurately planned and accounted for before submissions are finalized. Lastly, a role-based security model shall be estimated to ensure that each user community has appropriate access to data and functionality within the solution based on its assigned roles and responsibilities.

Deliverables:

A. ISRM Requirements and Configuration Design Document B. Configured OneStream ISRM Budgeting Model ORD Field Budgeting Capability

The Contractor shall design, develop, and implement a comprehensive budgeting process within OneStream to support field-level submissions of personnel, research project, and other non-research costs as part of the Intermediate Planning Process for Investigators, Scientific Review, and Management (ISRM). The solution shall include a Configuration Design Document outlining the business requirements, functional and non-functional requirements, solution overview, and configuration design, while supporting more than 113 field sites through established workflows for intermediate budget rollouts, reviews, and approvals. To enhance financial tracking and oversight, the Contractor shall establish sub-fund control points at each site to monitor project costs and budgets and implement automated integrations with IFCAP data to support field-level cost assignment, analysis, and monitoring. Additionally, the Contractor shall replace existing Research Management System (RMS) processes with a consolidated budgeting approach within OneStream, including the import and classification of project costs to the appropriate sub-fund control points. The solution shall also incorporate a field-level People Planner configuration to address requirements not captured within existing intermediate budgeting processes and support field-level compensation planning. Also, the Contractor shall provide the capability to aggregate field-level budgets into consolidated intermediate and headquarters-level reviews, supported by validation controls that ensure costs are accurately planned and accounted for before submissions are finalized. A role-based security model shall also be implemented to ensure each user community has appropriate access to data and functionality based on its assigned responsibilities. Furthermore, the Contractor shall deliver both a pilot and finalized comprehensive budgeting solution that enables more than 113 VAMC field sites to submit personnel, research project, and other non-research costs through a standardized and consolidated budgeting process.

Deliverables:

A. ORD Field Budgeting Requirements and Configuration Design Document B. Configured OneStream Field Budgeting Model

Research Analytics The Contractor shall design, configure, and implement automated data integrations from the VA Innovation Research and Review System (VAIRRS), the Research allocation and Forecasting Tool (RAFT), and ePromise into OneStream using OneStream’s Smart Integration Connector. The Contractor shall develop and deliver a comprehensive data model that consolidates information from these source systems while addressing and resolving differences in metadata and data structures to ensure consistency and accuracy across the integrated solution. To support data integrity and reliability, the Contractor shall provide a Data Reconciliation and Validation Report that includes validation results, data quality assessments, data mapping validation, and documented reconciliation methodologies. Additionally, the solution shall be configured to support the modification and translation of data in detailed and summary levels, where appropriate, through the use of forms and line-item planners. The Contractor shall also deliver a minimum of 20 dashboards and/or reports that provide integrated views of financial, portfolio, and scientific data sets, offering a comprehensive and holistic view of VA-funded research. Moreover, the Contractor shall implement a role-based security model to ensure that each user community has appropriate access to data and functionally within the solution based on its assigned roles and responsibilities.

Deliverables:

A. OneStream Research Analytics Data Model B. Data Reconciliation and Validation Report C. Configured Dashboards and Reports ORD Operating Plan Modernization

The Contractor shall development and implement an enhanced OneStream solution to modernize the Office of Research and Development (ORD) operating plans, budget execution, and budget formulation processes through the integration and utilization of iFAMS actuals. As part of this effort, the Contractor shall deliver a comprehensive Configuration Design Document outlining the business requirements, functional and non-functional requirements, solution overview, and configuration design. The Contractor shall establish and configure the necessary FMS actuals to support iFAMS financial data and automate the integration of iFAMS actuals into OneStream using the Smart Integration Connector. These actuals shall be incorporated into the ORD Operating Plans model to provide project level financial visibility and strengthen budget execution capabilities. Additionally, the Contractor shall enhance existing operating plan forms and processes to incorporate iFAMS project actuals, allowing users to monitor financial activity and make more informed execution decisions. The Solution shall further improve project level forecasting by leveraging detailed actual cost data to increase forecast accuracy and provide greater insight into project spending. To support financial oversight and reporting, the Contractor shall modernize existing ORD dashboards and reports to incorporate the newly integrated actuals, providing improved visibility into financial performance and budget execution. Also, the Contractor shall enhance the budget formulation process through the implementation of OneStream narrative reporting capabilities, enabling proved development, documentation and communication of budget information and supporting narrative. These enhancements shall provide a more integrated and streamlined approach to ORD budget formulation, financial planning, forecasting and execution.

Deliverables:

A. ORD Operating Plan Modernization Requirements and Configuration Design Document B. Updated Operating Plan Model Configuration using iFAMS Actuals

Training The Contractor shall conduct system training using a live, virtual Train-the-Trainer approach. The Contractor shall create and provide all necessary training materials such as role-based user guides, training videos, and frequently asked questions (FAQs).

The Contractor shall provide Train-the-Trainer training and support for transitioned budget workflows for up to 25 ORD personnel and 113 field personnel.

Deliverable:

A. Train-the-Trainer training – User guides, Videos, and FAQ’s Assessment, Authorization, and Continuous Monitoring

The Contractor (including producers and resellers) shall comply with Office of Management and Budget (OMB) M-26-05 when using third-party software on VA Information systems or otherwise affecting the VA information. This includes new software purchases and software renewals for software developed or modified by major version change. The term “software” includes firmware, operating systems, applications and application services (e.g)., cloud-based software), as well as products containing software. The Contractor shall provide a self-attestation that secure software development practices are utilized as outlined by Executive Order (EO)14028 and NIST Guidance. A third-party assessment provided by either a certified Federal Risk and Authorization Management Program (FedRAMP) Third Party Assessor Organization (3PAO) or one approved by the agency will be acceptable in lieu of a software producer's self-attestation.

The information system must be assessed by an accredited Third Party Assessment Organization to support initial authorization and whenever there is a significant change to the system’s security posture in accordance with the FedRAMP Continuous Monitoring Plan.

The Contractor shall apply the appropriate set of baseline controls in accordance with VA’s categorization of the system (as defined in Federal Information Processing Standards (FIPS) 199), as required in the FedRAMP Security Requirements Baseline document to ensure compliance to security standards.

The Contractor shall, where applicable, assist with the VA ATO process to help achieve and maintain agency authorization of a cloud service or migrated application.

The Contractor shall maintain a security management continuous monitoring environment based upon the latest edition of FedRAMP Security Controls Baseline and FedRAMP Continuous Monitoring Strategy Plan.

To the extent required to carry out the FedRAMP assessment and authorization process and FedRAMP continuous monitoring, to safeguard against threats and hazards to the security, integrity and confidentiality of any non-public VA data collected and stored by the Contractor, the Contractor shall afford VA access to the Contractor and Cloud Service Provider’s facilities, installations, technical capabilities, operations, documentation, records, and databases.

If new or unanticipated threats or hazards are discovered by either VA or the Contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party in accordance with security appendix B.

The Contractor shall comply with all VA and FedRAMP privacy requirements.

VA has the right to perform manual or automated audits, scans, reviews, or other inspections of the vendor’s IT environment being used to provide or facilitate services for the VA.

Identified gaps between required FedRAMP Security Control Baselines and Continuous Monitoring controls and the contractor’s implementation as documented in the Security Assessment Report shall be tracked by the contractor for mitigation in a POA&M document. Depending on the severity of the gaps, the Department may require them to be remediated before a provisional authorization is issued.

No data shall be released by the Contractor without the consent of VA in writing. All requests for release must be submitted in writing to the Contracting Officer’s Representative (COR)/Contracting Officer (CO). * To the extent that a conflict of terms exists, Addendum B Section B.3, paragraph 10, item (i) (compliance with court orders) supersedes and takes precedence.

VA reserves the right to perform Penetration Testing. If VA exercises this right, the contractor shall allow VA employees (or designated third parties) to conduct Security Assessment activities to include control reviews in accordance with FedRAMP requirements.

FedRAMP deliverables shall be labeled “CONTROLLED UNCLASSIFIED INFORMATION” (CUI) or contractor selected designation per document sensitivity. External transmission/dissemination of For Official Use Only and CUI to or from a VA computer must be encrypted. Certified encryption modules must be used in accordance with FIPS PUB 140-2, “Security requirements for Cryptographic Modules.”

Deliverable:

A. FedRAMP ATO Sustainment Package Post Deployment Support The Contractor shall provide post-implementation support for 30 business days after go-live of new processes and capabilities. The Contractor shall provide dedicated resources to respond to and resolve functional, technical, and security issues with minimal interruptions. The Contractor shall also support the identification of opportunities for system optimization and performance enhancements.

5.10 OPTION PERIOD ONE

If Option Period One is exercised by VA, the Contractor shall provide all services, tasks, and deliverables in Sections 5.1 through 5.10 inclusive of all subparagraphs.

5.11 OPTION PERIOD TWO

If Option Period Two is exercised by VA, the Contractor shall provide all services, tasks, and deliverables in Sections 5.2 through 5.10 inclusive of all subparagraphs.

1. GENERAL REQUIREMENTS

ENTERPRISE AND IT FRAMEWORK

VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM). Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23-01, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-4, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-4 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

INTERNET PROTOCOL VERSION 6 (IPv6)

The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents).

STANDARD COMPUTER CONFIGURATION

The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, Windows 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 11 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.

VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM)

The Contractor shall support VA efforts IAW the Veteran-Focused Integration Process (VIP) Guide and Product Line Management (PLM) Playbook. The major focus of VIP is on Enterprise Oversight, Governance, reporting, and establishing practices that focus on outcomes and continuously delivering sustainable IT capabilities to benefit the Veteran. PLM is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Transformation Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Transformation Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.

The VIP Guide provides guidance for transitioning from project-centric to product-centric delivery. The VIP guide applies to all OIT Office of Management and Budget (OMB) reportable products that are required to collect and report costs, schedules, risks, and other valuable information in VA PARS (whether products are procured or developed by VA) and any VA Information Technology project effort in Software Product Management (SPM) and Infrastructure Operations (IO), or their successors, that touch the VA network regardless of IT organizational alignment (whether it spends government funding from VA's Congressional IT Appropriation or any other appropriation).

The PLM Transformation Playbook details how OIT leadership expects Product Lines (PLs) to implement PLM, DevOps, and Lean-Agile principles, methods, practices, and techniques through levels of maturity. The PLM Transformation Playbook applies to all Information Technology (IT) products aligned to PLs in the Software Product Management, Infrastructure Operations and Product Engineering organizations within the OIT organization.

Others outside the referenced groups or organizations may use the VIP Guide and PLM Transformation Playbook for situational awareness as needed.

PROCESS ASSET LIBRARY (PAL)

The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL includes a spectrum of OIT functions and activities, such as project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. OIT utilizes PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at process_CONB_ext.docx (live.com). The main PAL can be accessed at www.va.gov/process.

AUTHORITATIVE DATA SOURCES

The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:

1. Interfacing with VA’s Master Person Index (MPI) (formerly the Master Veteran Index (MVI)) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.

3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.

4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the…