Service Catalog Solutions

The Vendor is required to provide an external Supplier to assist with improving and/or re-designing the current Service Now Service Catalog to include cloud services, specifically for the pre-approved and pre-assured Infrastructure-as-Code (IaC) patterns that have already been developed and establishing a framework to easily add more IaC patterns and pre-existing cloud services that are available through Microsoft Azure, with proper governance and financial transparency.
- Provide an IT Modernization effort to develop comprehensive landing zones within all three industry-leading cloud providers for customers seeking cloud-hosted solutions.
- The current catalog contains gaps and requires further qualifications to ensure completeness and alignment with customer needs.
- The portal hosts a catalog of service request items, including forms for data center hosting environments and storage configurations. 
- Some of these requests are partially automated via VMware vRealize Automation (vRA), enabling streamlined server deployment to agency data centers or to a pilot Microsoft Azure VMware Solution (AVS) environment.
- Solution should provide:
•    Restricted access mechanisms, allowing only authorized users to interact with phi via secure, dedicated virtual machines.
•    Data protection controls that prevent unauthorized data extraction, ensuring all analysis and processing occur strictly within the enclave.
•    Comprehensive security measures including encryption of data at rest and in transit, continuous monitoring, logging, and activity auditing to maintain compliance.
•    Up-to-date safeguards aligned with institutional and federal standards, with proactive maintenance and vulnerability management.
•    Secure collaboration capabilities for approved users, without compromising privacy or regulatory compliance
- Its new public cloud hosting offerings, our ServiceNow service portal will require catalog development to display available options, collect the necessary customer data, and deliver the hosting, compute and/or storage through IaC-based automations.
- The design must include request submission, review, approval, deployment, and ongoing operations of the IaC (including financial elements of cloud resources).
- Develop documentation for end users to use the catalog and for support teams to conduct ongoing maintenance.
- User-friendly design user experience (UX) will be an important component of this re-design. The revised Service Catalog should be easy to use, navigate, and interact with. Implement the design, including go-live support.
- The system should automatically apply standardized tagging (including application service name, aliases, cost center, ServiceNow ticket (RITM) number, and environment) to all VMs for traceability and financial reporting.
- The system should deploy VMs using HITS-approved, hardened OS images maintained in the enterprise image repository.
- The system should support deployment of approved Linux and Windows operating systems, aligned with enterprise security baselines.
- The system should accommodate both production and non-production environments with appropriate controls, separation, and policy enforcement.
- The system should allow requesters to select from predefined OS patch/maintenance windows and enforce patch scheduling via automation.
- The system should attach and configure storage for VMs based on catalog specifications, with options for block, file, or object storage.
- The system should provision and configure VMs according to approved templates and predefined Infrastructure-as-Code (IaC) patterns.
- The system should provide both standardized and custom VM configurations, subject to governance and approval workflows.
- To ensure long-term sustainability and maintainability of the ServiceNow catalog, the system must include lifecycle management capabilities.
- This includes comprehensive documentation of catalog items, version control for all custom code and configurations, and a structured knowledge transfer process to internal support teams.
- The system should support automated rolling patching and upgrades of container workloads, supporting blue/green or canary deployments.
- The system should automate creation and rotation of Kubernetes secrets, service accounts, and managed identities, integrated with enterprise IAM.
- The system should provision new namespaces, support auto-scaling workloads, and provision persistent volumes using Azure Disk, Blob, or enterprise-approved storage.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: November 18, 2025