FY26 SW Fusion Risk Management Product Description v2 1 14 JAN 2026.pdf

Product Description Template_MAY_16_2025_Rev.1 PD Template Revision History

PRODUCT DESCRIPTION (PD) TEMPLATE

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Infrastructure Operations (IO)

For Brand Name or Equal - Fusion Risk Management Software Licenses and

Maintenance

Date: January 14, 2026

VA-26-00028791

PD Version Number: 2.1 https://dvagov.sharepoint.com/:w:/r/sites/VACOOALC/TACNJ/DLR/VOA%20Template/CAP%20Template/OPAL%20Acquisition%20Requirements%20Package%20(ARP)%20Templates/Other%20Templates%20(Standard%20Templates)/Product%20Description%20Template_Revision%20History_MAY_16_2025_Rev.1_JUN_02_2025.docx?d=w6cee9ba225d04a51a6398ef2459b2fbf&csf=1&web=1&e=O62pc5

Brand Name or Equal Fusion Risk Management TAC Number: VA-26-00028791

Product DescriptionTemplate_MAY_16_2025_Rev.1

Contents

1.0 PRODUCT REQUIREMENTS

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY

(ICT) STANDARDS

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

3.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS AND

SERVICES

4.0 SHIPMENT OF SOFTWARE

5.0 GENERAL REQUIREMENTS

5.1 ASSESSMENT, AUTHORIZATION, AND CONTINUOUS MONITORING

5.2 VA TECHNICAL REFERENCE MODEL

5.3 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

5.4 SOCIAL SECURITY NUMBER (SSN) REDUCTION

5.5 INTERNET PROTOCOL VERSION 6 (IPV6)

5.6 SOFTWARE AND LICENSING REQUIREMENTS

5.7 TRUSTED INTERNET CONNECTION (TIC)

6.0 POINTS OF CONTACT

1.0 PRODUCT REQUIREMENTS

The Department of Veterans Affairs (VA), Office of Information Technology (OIT), Infrastructure Operations (IO) requires the purchase of Commercial-off-the-Shelf Software-as-a-Service (SaaS) Brand Name or equal Fusion Risk Management as a replacement to the existing Business Continuity Planning Solution.

The Business Continuity Planning Solution replacement shall already be developed and can support an initial user base of 100 concurrent users with the ability to increase capacity to 400 users. This system will alleviate the manual creation for 300+ Business Continuity Plans, Business Impact Analysis, Disaster Recovery Plans, Information System Contingency Plans, Cyber Incident Response Plans, and current vulnerabilities.

Provide capability to support identifying potential vulnerabilities and assessing impacts on operations.

The solution will empower managers to easily maintain their business, disaster recovery, cyber incident response, contingency and continuity plans. Business Continuity Management will be implemented as a sustainable process, allowing Business Continuity professionals to use their time to analyze risk exposures, enhance preparedness, and strengthen their Business Continuity plans and programs.

The Contractor shall deliver only a Commercial off the Shelf (COTS) solution as SaaS and a cloud hosting environment in which the SaaS is hosted. The entire environment and entire solution shall be Federal Risk and Authorization Management Program (FedRAMP) authorized at a Moderate FISMA impact level by June 1, 2026. As part of the environment and the solution the Contractor shall provide the software, database, hosting, licensing, and services necessary to support IO Business Continuity Planning activities. The Contractor shall provide data migration and training, implementation, operation and maintenance support, documentation and activities to support VA personnel’s efforts to obtain an Authority to Operate (ATO) if not already achieved, system cloud hosting, system licensing, software maintenance, production support, application monitoring/program evaluation, transition planning, and data governance support.

Annual Software Licensing and support shall include updates, patches and bug fixes.

Support includes Original Equipment Manufacturer software maintenance support.

Deliverables will include updated software licensing information and instructions on how to place service requests. The subscription support shall include service level one coverage by telephone, email or online. The technical support shall provide one telephone number and/or a point of contact for VA to contact with the ability to open support maintenance service calls.

Data Migration shall include discovery, planning, configuration, user account type setup (e.g. – administrator, district user, user), data migration from on-premise Microsoft Structured Query Language (SQL) database into the SaaS solution database, and support of the above throughout the base period.

Training shall include one live online, web-based session for 8 program users, which shall be recorded for future use, as well as on-demand application training. Additionally, on-demand application training for up to 400 business users shall be available throughout the contract's lifecycle.

There shall be a dedicated System Administrator training program for clients who will manage and configure the platform. This instructor-led course shall provide comprehensive guidance on user administration, security settings, reporting, workflows, integrations, and advanced system features. Upon completion, participants shall have the opportunity to earn a System Administrator Certification, establishing in-house expertise and confidence in managing the system independently.

All clients shall receive access to an online knowledge base and learning portal, which includes user guides, on-demand tutorials, recorded training sessions, and best-practice documentation. These resources shall be available anytime and are suitable for onboarding new users, reinforcing training concepts, and supporting daily operations as the program evolves.

For continued growth after implementation, advisory and consulting services shall be available. These services shall provide access to subject-matter experts who can deliver advanced training, best-practice guidance, roadmap development, and tailored support aligned with program goals. This option is especially valuable as the organization expands its use cases, adds new solution areas, or focuses on program maturity.

The period of performance for the base period shall be for 12-months from date of award, for the Data Migration and Training, and four 12-month option year periods if exercised. The delivery of software shall be within ten (10) days after the receipt and processing of the delivery order.

The Contractor shall provide Brand Name or equal Fusion Risk Management software and associated support, data migration, and training as outlined below:

Base Period Period of Performance 12 months following award

Item No Product Description QTY Unit

0001 Continuity Foundations Package 1 EA

0002 Business User Licenses 100 EA

0003 Program User Licenses 8 EA

0004 ServiceNow Connector 1 EA

0005 Fusion Framework Shield Platform Encryption 1 EA

Base Period Period of Performance 12 months following award

Item No Product Description QTY Unit

0006 Training 1 EA

0007 Data Migration 1 EA

Option Period 1 Period of Performance 12 months following conclusion of the Base Period

Item No Product Description QTY Unit

1001 Continuity Foundations Package 1 EA

1002 Business User Licenses 100 EA

1003 Program User Licenses 8 EA

1004 ServiceNow Connector 1 EA

1005 Fusion Framework Shield Platform Encryption 1 EA

Option Period 1 Optional Tasks

1006 Business User Licenses 150 EA

Option Period 2

Period of Performance 12 months following conclusion of Option Period 1

Item No Product Description QTY Unit

2001 Continuity Foundations Package 1 EA

2002 Business User Licenses 100 EA

2003 Program User Licenses 8 EA

2004 ServiceNow Connector 1 EA

2005 Fusion Framework Shield Platform Encryption 1 EA

Option Period 2 Optional Tasks

2006 Business User Licenses 300 EA

2007 Fusion Intelligence+ Package 1 EA

Option Period 3 Period of Performance 12 months following conclusion of Option Period 2

Item No Product Description QTY Unit

3001 Continuity Foundations Package 1 EA

3002 Business User Licenses 100 EA

3003 Program User Licenses 8 EA

3004 ServiceNow Connector 1 EA

3005 Fusion Framework Shield Platform Encryption 1 EA

Option Period 3 Optional Tasks

3006 Business User Licenses 300 EA

3007 Fusion Intelligence+ Package 1 EA

Option Period 4 Period of Performance 12 months following conclusion of Option Period 3

Item No Product Description QTY Unit

4001 Continuity Foundations Package 1 EA

4002 Business User Licenses 100 EA

4003 Program User Licenses 8 EA

4004 ServiceNow Connector 1 EA

4005 Fusion Framework Shield Platform Encryption 1 EA

Option Period 4 Optional Tasks

4006 Business User Licenses 300 EA

4007 Fusion Intelligence+ Package 1 EA

1.1 SALIENT CHARACTERISTICS

The solution shall contain the below listed brand name or equal Fusion Risk Management products with better and or equivalent capabilities.

1.1.1 Continuity Foundations Package

The contractor shall provide:

• Access to the Continuity Foundation component of the Fusion Framework to include access to:

o Business Continuity Planning Framework o Business Impact Analysis o Gap reporting o Business Process Context Mapping o Dynamic Planning & Response o IT Disaster Recovery o Crisis and Incident Management

• Access to a non-production environment

• Access to software upgrades

• Technical support in accordance with the below incident response times:

Incident Severity Level

Incident – Description Response Response Time

“Severe Impact” is defined as problems that disable major functions required to do productive work within the SaaS. A “Severe Impact” shall include an unauthorized disclosure of Client Content.

Acknowledgment Within 2 hours Work around or temporary fix

No more than 48 hours

Final fix, update, or new release

No more than 5 business days

Communications

Every 4 hours until a work around or temporary fix is in place, once per day thereafter.

“Degraded Operations” is defined as reported problems disabling specific non-essential functions within the SaaS, or an error condition that is not critical to continuing operation of the application.

Acknowledgment Within 4 hours Work around or temporary fix

No more than 48 hours

Final fix, update, or new release

No more than 14 business days

Communications

Every 12 hours until a work around or temporary fix is in place; thereafter, daily.

“Minimal Impact” is defined as any deviation not otherwise Severity Level 1 or 2 (as defined above).

Acknowledgment Next business day

Work around, or temporary fix

No more than 72 hours

Final fix, update, or new release

No more than 120 business days

Communications At least monthly

Deliverable: Software Subscription Entitlement

1.1.2 Business User License

The contractor shall provide:

• Subscriptions for a “seat license” enabled by Client’s Admin User and assigned to a named individual for the duration of the term of the subscription or until Client’s Admin User reassigns the subscription to another named individual User.

•Users should be able to participate in plan reviews, enter or validate information, complete assigned tasks.

1.1.3 Program User License

The contractor shall provide:

• 8 subscriptions for an administrative user license with elevated privileges within the entire software suite.

• User provided the ability to administer the User subscriptions, enabling and disenabling access to the SaaS.

• Licenses to be assigned to a named individual for the duration of the term of the subscription or until Client’s Admin User reassigns the subscription to another named individual User.

• Full platform access to design, implement, and maintain core resilience processes.

• Create and manage plans, conduct BIAs, coordinate exercises, and drive incident response.

1.1.4 FFS Shield Platform Encryption

• Platform Encryption to enable native encryption of sensitive data at rest across all Salesforce apps, protecting PII, sensitive, confidential, or proprietary data and addressing both external and internal data compliance policies while keeping critical app functionality — like search, workflow, and validation rules. Shield Platform Encryption enables Client to natively encrypt Client Data at rest. It relies on a unique tenant secret that Client controls (“Tenant Secret”) and a master secret that is maintained by Salesforce.com.

1.1.5 Connector – ServiceNow

• The ServiceNow Connector for the Fusion Framework System to enable seamless, bi-directional data integration between Fusion’s operational resilience platform and ServiceNow’s enterprise workflow environment.

• An automated, secure link between the Fusion Framework System and ServiceNow, allowing key objects—such as incidents, issues, changes, requests, assets, and configuration items—to be synchronized or exchanged as part of a unified resilience workflow. By aligning data across systems of record, teams gain a single, trusted view of operational impacts and dependencies, supporting faster decisions and more coordinated response activities.

1.1.6 Fusion Intelligence+ Package

• Access to Fusion’s next-generation generative AI engine designed to elevate operational resilience, business continuity, and risk management through intelligent automation, natural-language interaction, and real-time insight generation.

• Specific AI features in the package include:

o Chat o Insights Library o Incident Management Analysis o Scenario & Tabletop Generator o inFusion + o Agents o Incident Coordinator

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT.

These standards are found in their entirety at: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

☒ E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

☒ E204 Functional Performance Criteria ☐ E206 Hardware Requirements ☒ E207 Software Requirements ☒ E208 Support Documentation and Services Requirements

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery.

The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

3.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS AND

SERVICES

Not Applicable. This is for procurement of software license and maintenance.

https://www.access-board.gov/ict/ https://www.access-board.gov/ict/

4.0 SHIPMENT OF SOFTWARE

ELECTRONIC DELIVERY

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination

Ship To and Mark For: Delivery of software licenses and/or maintenance shall be submitted electronically. Delivery of DSI form shall be sent to AAClicense@va.gov (see Deliverable Support Information CLIN) and provide notice to:

Name: Chris Cockle Voice: 512.820.7329 Email: Chris.Cockle@va.gov

Name: IT Asset Management Software Team Address: 1615 Woodward St. Austin, TX 78772 Email: IO CoS A&L Software Team (oititopssoiobusfboitamsoftware@va.gov)

5.0 GENERAL REQUIREMENTS

5.1 ASSESSMENT, AUTHORIZATION, AND CONTINUOUS MONITORING

The information system solution selected by the Contractor shall comply with the Federal Information Security Management Act (FISMA).

2. The Contractor shall comply with FedRAMP requirements as mandated by Federal laws and policies, including making available any documentation, physical access, and logical access needed to support this requirement.

3. The Contractor shall, where applicable, assist with the VA ATO Process to help achieve agency authorization of the cloud service or migrated application.

4. The Contractor shall provide IRP scenario within 14 days and complete Table- Top exercise within 21 days of award unless current VA IRP can be provided.

5. The Contractor shall provide a System Boundary Diagram that demonstrates implementation and any proposed VA interconnections including required ports and protocols at the time award.

6. The Contractor shall complete a FedRAMP System Security Plan (SSP) and supporting documentation at the time of award.

7. The Contractor shall complete a Third-Party Assessment Organization (3PAO) Security Assessment Plan (SAP) at the time of award.

8. The Contractor shall complete a 3PAO Security Assessment Report (SAR) at the time of award.

mailto:AAClicense@va.gov mailto:Chris.Cockle@va.gov mailto:oititopssoiobusfboitamsoftware@va.gov

9. The Contractor shall afford VA access to the Contractor’s and Cloud Service Provider’s (CSP) facilities, installations, technical capabilities, operations, documentation, records, and databases.

10. 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 the security addendum B.

11. The Contractor shall not release any data 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).

12. For live VA data to be used in this system, a FedRAMP Authorization and Agency ATO will be required.

Deliverables:

A. System Boundary Diagram B. FedRAMP System Security Plan (SSP) and supporting documentation C. 3PAO Security Assessment Plan (SAP)

3PAO Security Assessment Report (SAR)

5.2 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.

5.3 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 https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

Critical Controls after implementation will result in VA discontinuing the use of the system.

5.4 SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

5.5 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.

5.6 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119 operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

5.7 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.)

6.0 POINTS OF CONTACT

VA Program Point of Contact/ Contracting Officer’s Representative:

Name: Kyle Hooley Voice: 512-981-4961 Email: Kyle.Hooley@va.gov

Project Manager

Name: Christopher Cockle Voice: 512-820-7329 Email: Chris.Cockle@va.gov

Contracting Officer:

Name: Patrick J. Hamilton Address: 23 Christopher Way, Eatontown NJ 07724 Voice: 848-377-5056 Email: Patrick.Hamilton2@va.gov

Contract Specialist:

Name: Anthony Pavese Address: 23 Christopher Way, Eatontown NJ 07724 Voice: 848-377-5021 Email: Anthony.Pavese@va.gov https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents mailto:Kyle.Hooley@va.gov mailto:Chris.Cockle@va.gov mailto:Patrick.Hamilton2@va.gov mailto:Anthony.Pavese@va.gov