7D20--Abacus Visual Playbook Builder and Automation Orchestrator (VA-26-00041469)

Form / Attachment / Pricing Sheet

This document outlines the professional services requirements for a Hyperconverged Infrastructure (HCI) Vendor and S3 Object Storage solution, specifically for the Abacus Visual Playbook Builder and Automation Orchestrator. It details the vendor's responsibilities in procuring, installing, and configuring HCI hardware, an HCI Cluster Manager, an HCI Management Console, and S3-compatible object storage.

• HCI Infrastructure: Requirements for HCI nodes, cluster manager, and management console, including hardware procurement, physical installation, and configuration.
• S3 Object Storage: Configuration of S3-compatible storage, including bucket creation (abacus-playbook-assets), versioning, and access control for specific users (abacus-assets-writer, aap-assets-reader).
• Access and Security: Configuration of secure HTTPS access using TLS certificates signed by the Government's internal CA, and Active Directory authentication for management interfaces.
• Integration Points: Details on how the HCI vendor's solution integrates with Red Hat Ansible Automation Platform (AAP) and the Primary Contractor's Abacus platform, particularly concerning S3 object storage access and presigned URLs.
• Timelines and Deliverables: Outlines key milestones, including hardware delivery by Month 3, cluster and storage configuration by Month 5, and final acceptance by Month 12. It also specifies deliverables such as hardware, configured systems, documentation, and access credentials.
• License Activation: Production licenses are deferred until the Final Acceptance milestone (Month 12), with evaluation licenses provided during the performance period.

This document is crucial for potential bidders offering HCI and S3 object storage solutions. It defines the technical requirements, scope of work, integration needs, and delivery timelines for the infrastructure supporting the Abacus platform. Bidders must understand these requirements to accurately propose a solution and estimate costs. It also clarifies the vendor's responsibilities versus the Government's and other contractors'.

Statement of Objectives (SOO) / Request for Information (RFI)

This document is a Draft Statement of Objectives (SOO) for a Request for Information (RFI) concerning the "Abacus Visual Playbook Builder and Automation Orchestrator" for the Department of Veterans Affairs (VA), Veterans Health Administration (VHA), VISN 23. The VA requires a system to automate the management of clinical workstations and servers across geographically distributed, air-gapped (dark-site) medical facilities. The current manual or fragmented scripting processes lead to inconsistencies and slow deployment. The "Abacus System" aims to enable non-technical administrators to build, share, and execute automation without requiring scripting or command-line expertise.

• Integrated Solution: The effort requires contractor-developed software and systems integration, not solely configuration of an existing product. It will leverage commercial components like Red Hat Ansible Automation Platform (AAP) for orchestration, Red Hat OpenShift for hosting, hyperconverged infrastructure (HCI), and S3-compatible object storage.

• Visual Playbook Builder: A browser-based interface allowing users to construct automation via a card-based design, without direct YAML authoring.

• Content Storefront: A centralized repository for sharing roles, playbooks, and configurations across sites, with provenance tracking and version management.

• Asset Management: Browser-based upload of files (up to 12 GB), compressed to .zip, stored in S3-compatible storage, and retrieved via presigned URLs during playbook execution using a custom Ansible collection (abacus.retrieve).

• VM Provisioning: User-initiated VM creation on existing Nutanix HCI infrastructure via the web interface, with automated onboarding and optional playbook execution.

• Multi-Site Operations: Support for eight physical sites with site-scoped access control and Active Directory integration, plus a ninth administrative site.

• Dark-Site Delivery: All components must operate in an air-gapped environment, requiring offline transfer and installation of release bundles, container images, and databases.

• No persistent software agents on clinical workstations.

• WinRM is the only permitted remote management protocol for Windows; OpenSSH cannot be enabled.

• Support for non-domain-joined Windows targets using certificate-based authentication.

• Management of both Windows and Linux operating systems.

• Requirement for an orchestration platform with a REST API.

• Operation in a completely air-gapped environment.

• Support for eight physical sites, up to 50 projects per site (400 total).

• Up to 1,500 managed hosts across all inventories.

• At least 10 concurrent users.

• Projects may manage 1-60 hosts, with 15-35 roles per project, each with 20-60 actions.

• Attachment A: Red Hat Professional Services integration requirements.

• Attachment B: HCI vendor professional services requirements (hardware, cluster formation, S3 storage).

Request for Information (RFI)

This RFI is for planning purposes to gather information regarding the "Abacus Visual Playbook Builder and Automation Orchestrator" (VA-26-00041469). The government is not obligated to acquire any products or services based on this RFI, and responses will not be entitled to payment. This is not a solicitation for proposals.

Vendors are requested to provide information on their capabilities and proposed technical approaches related to:

• Developing and delivering contractor-developed web applications for VA healthcare environments, specifically focusing on Visn 23 Healthcare Technology Management (HTM) usability.

• Systems integration using Red Hat Ansible Automation Platform, Red Hat OpenShift, and enterprise infrastructure components.

• Coordinating multi-vendor professional services engagements.

• Developing and deploying containerized applications in air-gapped (dark-site) environments.

• Building user interfaces for non-technical users.

• Experience with Ansible module or collection development, particularly for Windows targets.

• Responses are due by April 8, 2026, 15:00 Eastern Time.

• Submissions must be emailed to Robert Robinson (Robert.Robinson7081@VA.Gov) and Christopher Minetti (Christopher.Minetti@VA.Gov).

• Subject line: "Abacus Visual Playbook Builder".

• Page limitation: 15 pages. No marketing materials allowed.

• Responses must include company name, address, POC, business size/status, UEI, etc.

• Specific information required includes:

  • Summary of capability to meet requirements in the attached "Draft Statement of Objectives".
  • Experience and capabilities with specific technologies and integration challenges.
  • Proposed technical approach for dark-site delivery, technology stack, user experience, and cybersecurity.
  • Rough Order of Magnitude (ROM) for MVP delivery timeline, level of effort, and costs for the first year and option years.
  • Information on self-performance vs. subcontracting.
  • Corporate experience and specific contract references.
  • For SDVOSB/VOSB vendors: Intent and ability to meet set-aside requirements.
  • Feedback on the sufficiency of the draft PWS.

• Set-aside: SDVOSBC (Service-Disabled Veteran-Owned Small Business Concern).

• SDVOSB/VOSB vendors must be certified by the SBA. Proof of certification is required.

• SDVOSB/VOSB prime contractors must ensure that not more than 50% of the contract performance is subcontracted to firms that are not certified SDVOSBs.

• NAICS Code: 541512 (Size Standard: $34.0 million).

• Product Service Code: 7D20.

• Referenced attachments: RFI_Statement of Objectives_v1.3_final, ATTACHMENT_A_v2 _ final, ATTACHMENT_B_v2 _ final.

Form / Attachment / Pricing Sheet

This document, Attachment A, serves as a Performance Work Statement (PWS) addendum detailing the scope and requirements for Red Hat Professional Services engagement related to the Abacus Visual Playbook Builder and Automation Orchestrator acquisition. It outlines the technical areas requiring Red Hat expertise for integration with Ansible Automation Platform (AAP).

• VM Provisioning and VLAN Management: Automating Windows VM creation and network management across eight Nutanix sites using a single AAP installation. Focus on multi-site security isolation and API-driven provisioning.
• Windows Certificate Authentication: Establishing secure, scalable authentication for managing Windows hosts (domain-joined and workgroup) using a two-certificate architecture (self-signed server certs, CA-signed client cert) to overcome limitations of traditional methods.
• Certificate Management Workflows: Four distinct workflows for preparing, rotating, and distributing certificates and root CAs, designed for administrator ease of use with minimal manual intervention.
• Presigned URL Workflow: A two-job AAP workflow for securely retrieving assets from S3 (Nutanix Objects) for playbook execution.
• Real-Time Job Output Streaming: Guidance for integrating Abacus with AAP's WebSocket endpoints to stream job execution output to the Abacus UI with low latency.
• AAP Infrastructure and Self-Management: Recommendations for operational best practices, including backup, monitoring, logging, and using AAP to manage its own operational tasks.
• Technical Environment: Details on the Windows, Certificate, Nutanix, and supporting infrastructure (Git, Active Directory, OpenShift).

This attachment defines critical technical requirements and Red Hat's scope for the Abacus integration. Bidders should note the emphasis on automation, certificate-based authentication for Windows hosts, multi-site management, and real-time data streaming. It clarifies Red Hat's deliverables, including AAP installation, configuration, specific job templates, playbooks, and guidance documentation. The document also outlines constraints and assumptions that shape the implementation approach.