Exhibit R, DCS RFO Language (POL-604-10).pdf

SERVICE MANAGEMENT MANUAL

Enterprise Policies

DCS RFO Language

Policy Document

Doc. No.: POL-604-10 Version: 14.0

Version Date: 8/28/2025

DCS RFO Language

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 2 of 22

Table of Contents

1 Data Center Services RFO Language for DCS Agencies seeking IT Solutions

1.1 Data Center Services (DCS) Infrastructure Requirements

1.2 Infrastructure Hosting

1.3 Software as a Service (SaaS)

1.4 Solution Proposal Guidance

1.5 DCS Public and Private Cloud Compute

1.6 DCS Process Management

2 DCS Public Cloud

2.1 Semi-Managed Public Cloud Support

2.2 Fully Managed Public Cloud Support

2.3 Platform as a Service (PaaS)

2.4 Self-Service PaaS: Advanced Cloud Accounts

2.5 Virtual Cross Connect

2.6 Virtual Private Cloud (VPC)

3 DCS Private Cloud

3.1 Fractional Intel Virtualization (Consolidated Data Center)

3.2 Enterprise SAN Storage

3.2.1 Server Enterprise SAN Storage Tiers

3.3 Private Cloud Managed Support Services (available for all compute platforms)

3.3.1 Fully Managed Private Cloud

3.3.2 Semi-Managed Private Cloud

3.3.3 Database Standards

3.3.4 Standard Databases

3.3.5 Non-Standard Databases

3.4 Oracle Database Offerings

3.4.1 Enterprise Exadata

3.4.2 Enterprise Exadata Oracle Database Software and Options

3.4.3 Fractional Oracle

3.4.4 Database Services Support Options

3.5 Private Cloud Hardware and Software Currency

4 Level I Help Desk

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 3 of 22

5 Functions Retained by <agency> – Not Provided by Data Center Services

6 Shared Technology Services/Agency Program Responsibilities Overview

7 Document Control

7.1 Revision History

7.2 SP Process Owner Approval

7.3 QA Review and Approval

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 4 of 22

1 Data Center Services RFO Language for DCS Agencies seeking IT Solutions

All Data Center Services (DCS) designated agencies are required to include DCS hosting requirements language below in Requests for Offers (RFO) that include IT infrastructure as either a hosted solution or Software as a Service (SaaS) solution.

The intent of this language is:

1) to give respondents a clear understanding of the requirement to use the State’s DCS program public or private cloud,

2) how respondents should propose technical solutions hosted in DCS, and

3) to communicate how respondents are expected to integrate with the DCS program vendors and services throughout the life of their contract.

The areas highlighted in yellow below indicate places where the Agency should customize the wording to fit their specific Agency, situation, or RFO structure.

The term “Agency” below refers to the DCS Customer.

RFO Language:

1.1 Data Center Services (DCS) Infrastructure Requirements

The Texas Legislature, by action of House Bill 1516, 79th Legislature (Regular Session), established the foundation of a shared technology infrastructure and directed Department of Information Resources (DIR) to coordinate a statewide program to consolidate infrastructure services. Section 2054.391 requires State agencies included in the DCS program to use such services, unless otherwise approved by DIR through a Data Center Services Exemption.

Texas State Agencies are also required to comply with all application development reporting requirements as identified in Texas Government Code 2054, the General Appropriations Act, Article IX, and Texas Administrative Code 216. Successful Respondents are required to support the Agency with their reporting requirements.

1.2 Infrastructure Hosting

All hosted solutions offered in response to this RFO (including custom developed application, COTS, and Portal or Website managed content) must host the application or solution in the DCS program, using either public or private cloud compute and DCS managed services provided.

Respondents should comprehensively list their infrastructure or compute requirements, to be hosted in either a DCS public or private cloud, for financial review by the <agency>. The <agency> will facilitate the process to request an estimate of the cost to host the solution within the DCS program.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 5 of 22

More details about the DCS Vendor Contracts, Master Services Agreements (MSA) and Statements of Work (SOW) may be found on DIR’s website at: www.dir.texas.gov.

1.3 Software as a Service (SaaS)

If the Respondent intends to propose SaaS, then the Respondent must demonstrate that the solution clearly meets the National Institute of Standards and Technology (NIST) standard definition of SaaS (NIST Definition of Cloud Computing Special Publication 800-145). The solution must be TX-RAMP certified if the <agency> determines the solution requires TX-RAMP.

The <agency> will be required to request and receive from DIR a DCS program exemption before a contract can be awarded to a Respondent if the solution is not on DIR’s approved blanket SaaS products list.

1.4 Solution Proposal Guidance

Respondents should propose one technical solution: either SaaS or DCS hosted and managed. If your proposal is for a hosted solution, it will need to be hosted in the State’s DCS program, which offers both public and private cloud hosting options. This program provides all server management functions including system administration, operating system management and patching, base security services, dedicated local area network connectivity, storage services, backup services and disaster recovery services. Respondents should indicate whether it is proposing fully managed, or semi managed DCS infrastructure hosting and compute solutions required.

Respondents are not required to estimate the cost to host within the DCS program; however, Respondents are required to provide complete technical specifications in order for the <agency> to estimate.

Collectively, the DCS contracts provide participating agencies’ mainframe and server operations, both public and private cloud services, disaster recovery, and bulk print and mail services.

1.5 DCS Public and Private Cloud Compute

As a participating entity in the DCS program, <agency> is required to acquire all in-scope infrastructure compute and services through the DCS program. Infrastructure compute includes server hardware and operating system software. Respondents must include complete compute infrastructure requirements in their response for the <agency> to estimate DCS hosting costs.

The Successful Respondent is required to participate in the procurement process, including submitting the request for service into the DCS ServiceNow Tool, participating in the requirements gathering sessions, and validating the acquisition proposals received. Proper long-range planning is required to ensure compute is provisioned to meet project schedules.

1.6 DCS Process Management

http://www.dir.texas.gov/

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 6 of 22

The Successful Respondent will be required to participate in the defined DCS processes for incident management, problem management, change management, release management, configuration management, and request management. In the management plans described in this RFO Section x, the Respondent must describe its interactions with the DCS program (For the agency: The DCS Services Management Manual is available for you to provide to your bidders .

Please contact DIR to request a copy).

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 7 of 22

2 DCS Public Cloud

Industry leading public cloud services available from DIR Shared Technology Services are hardened public cloud virtual data center solutions with a focus on aligning the DCS Operating Model with Industry Best Practices, technical and security assurances, and onboarding of public cloud services through Amazon Web Services (AWS), Azure, Google, and Oracle.

Leveraging Cloud Native tooling, the DCS Cloud Service model is poised to align to the value of Cloud Service Providers by evolving capabilities with investment in Service Evolution of the Public Cloud. Our expanded Public Cloud model delivers Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and SaaS services with products and tooling built for and within the Public Cloud to leverage the full benefits of Public Cloud services with the security assurances of

DCS.

2.1 Semi-Managed Public Cloud Support

The Semi-Managed Cloud operational model is intended for environments where the Agency is responsible for operating system management and monitoring, application-level support and associated incident and change management. This environment requires connectivity through a DCS managed Direct Connect/Virtual Cross Connect (VXC) solution, delivering integration of private cloud resources with public cloud resources including DCS assurances.

DCS solutions enabled for Agencies include the following operational functions for the semi managed environments.

• Native Public Cloud console available with full read access to the cloud environment.

• Specific console roles can be discussed with Public Cloud Manager (PCM).

• SaaS-based log aggregation services to capture, extract, transform and load pertinent security, and event details from Public Cloud management environments.

• Advanced analytics and data correlation greatly extend the success of forensic research and investigation.

• Capture Cloud Service Provider events Cloud Access Security Broker solution providing sophisticated analytics to identify violation of policy and combat cyberthreats.

• Utilizing the Security Instrumentation platform (SIP) to measure against cybersecurity Key Performance Indicator (KPI) and targets. Tests effectiveness of network, endpoint, and cloud controls.

• Advanced, customizable reporting with comprehensive Application Platform Interface (API) access and integration across multiple platforms.

• Endpoint protection online or offline with integration into tools such as Windows System Center for compliance and regulatory requirements and mandates.

The DCS SCP is responsible for:

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 8 of 22

• Provisioning and deprovisioning,

• Enabling Agency console and IaaS access,

• Acquiring, installing, and patching the operating system,

• Installing and maintaining antivirus,

• Backups and recovery,

• Performing Security Information and Event Management (SIEM) logging, critical watch reporting and security incident response, and

• Asset discovery and Configuration Management Database (CMDB) integration.

2.2 Fully Managed Public Cloud Support

The Fully Managed Cloud operational model is intended for environments where the SCP is responsible for all aspects of the service lifecycle including provisioning, deprovisioning, ongoing operating system (OS) support, monitoring, environment maintenance, Agency incident request, change requests, and service requests. Connectivity over a new or previously existing VXC between on-premises consolidated data center (CDC) resources and cloud resources enables the extension of DCS assurances to the hybrid environment.

DCS solutions enabled for agencies include the following operational functions for the fully managed environments.

• Native Public Cloud console available with full read access to the cloud environment.

• Read access to view inventory and state information of cloud resources.

• Usage and cost reporting and budget management.

• Log aggregation services to capture, extract, transform and load pertinent security, and event details from Public Cloud management environments.

• Advanced analytics and data correlation greatly extend the success of forensic research and investigation.

• Capture Cloud Service Provider events Cloud Access Security Broker solution providing sophisticated analytics to identify violation of policy and combat cyberthreats.

• Utilizing the SIP to measure against cybersecurity KPI and targets. Tests effectiveness of network, endpoint, and cloud controls.

• Advanced, customizable reporting with comprehensive API access and integration across multiple platforms.

• Endpoint protection online or offline with integration into tools such as Windows System Center for compliance and regulatory requirements and mandates.

• Real-time intervention, blocking, and prevention for any in-process runtime attacks.

• Integration with third-party tools across the entire cloud native lifecycle.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 9 of 22

• Web Application Firewall protecting applications in the cloud with consistent policies and management capabilities as on-premise solutions (optional).

The DCS SCP is responsible for:

• Provisioning and deprovisioning,

• Enabling Agency console and IaaS access,

• Acquiring, installing, and patching the operating system,

• Ongoing OS support,

• Installing and maintaining antivirus,

• Monitoring and environment maintenance,

• Performing SIEM logging, critical watch reporting and security incident response,

• Backups and recovery,

• Agency incident request, change requests, and service requests, and

• Asset discovery and CMDB integration.

2.3 Platform as a Service (PaaS)

PaaS services are available to DCS agencies through the following procurement methods.

• Request for Solution (RFS) catalog item via the Shared Technology Services (STS) Service Catalog

• Advanced Cloud Account (Self-Service) access upon Agency request

Baseline Native Public Cloud console access will be available to Agencies for the following functions (Note: additional access will be enabled for Agencies requesting Advanced Cloud Account access).

• Read access to view inventory and state information of cloud resources.

• Usage and cost reporting and budget management.

• SaaS-based log aggregation services to capture, extract, transform, and load pertinent security and event details from Public Cloud Management environments.

• Advanced analytics and data correlation greatly extend the success of forensic research and investigation.

• Capture Cloud Service Provider events.

• SaaS-based log aggregation services to capture, extract, transform, and load pertinent security and event details from Public Cloud Management environments.

• Advanced, customizable reporting with comprehensive API access and integration across multiple platforms.

https://txdir.servicenowservices.com/sp?id=sc_cat_item_guide&sys_id=3d89093813aa17404210f65ed144b00e&sysparm_category=13941b94dbc5d3002f905eea4b9619e5

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 10 of 22

• Public Cloud Edge Security Services (PCESS) protecting applications in the cloud with consistent policies and management capabilities as on-premise solutions (optional).

The SCP is responsible for:

• Virtual Private Cloud (VPC)/Virtual Network (VNET),

• Integration between public cloud IaaS services and PaaS services as needed,

• Fulfillment of RFS requests, and

• Enabling Agency console access.

2.4 Self-Service PaaS: Advanced Cloud Accounts

Advanced Cloud Accounts for AWS and Azure is an environment allowing DCS Agencies and their vendors greater access and control of their PaaS resources while leveraging a secure environment configured to limit risk. Agency vendors coordinate with that Agency for appropriate access to an Advance Cloud Account. Additionally, the DCS Agency can provide more information about the Advance Cloud Account environment thru information available from the DCS program.

Agencies can access and deploy DIR-approved PaaS resources on demand through the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDK), and AWS Rest APIs.

The AWS Advanced Cloud Account environment is enabled with automated controls promoting alignment with DCS program Security policies and Managed Service Provider responsibilities. By leveraging Security Control policies, Identity Access Management (IAM) Permissions Boundaries and IAM roles, Agencies can safely increase the rate at which they can consume AWS PaaS resources.

PCM maintains the AWS cloud environment, but Agencies can implement PaaS services and their required permission structures on their own in alignment with program operational and security requirements.

2.5 Virtual Cross Connect

The DCS SCP uses MegaPort to provide a virtual networking solution that allows Agencies to securely connect to multiple Cloud Providers without having to establish direct connections between the individual Agency and Cloud Provider.

Virtual Cross Connects (VXC) provide dedicated bandwidth for the agency to a cloud provider location, including traffic segmentation. The DCS program standard is to deploy two VXCs for improved network resiliency.

The DCS SCP is responsible for provisioning and management of VXCs.

2.6 Virtual Private Cloud (VPC)

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 11 of 22

A VPC is a public cloud networking construct roughly analogous to a Virtual Local Area Network (VLAN) in current CDCs. It is designed to enable network and security services to the workloads that run inside the public cloud.

VPCs go by different names based on the Public Cloud provider, i.e., Google and AWS call them VPCs, while Azure calls them VNETs. DCS prefers to use VPCs to mean the network construct used by the Public Cloud provider.

The DCS SCP is responsible for provisioning and management of VPCs.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 12 of 22

3 DCS Private Cloud

The Data Center Services program maintains two consolidated data centers geographically separated to provide disaster recovery. The Texas Private Cloud (TPC) provides technology infrastructure compute and storage based on standard reference models and managed services options.

Fully-managed or Semi-managed support services are available for all compute platforms with multiple service levels.

• Consolidated Fully Managed - Premier Plus

• Consolidated Fully Managed - Premier Plus (UNIX)

• Consolidated Fully Managed - Premier

• Consolidated Fully Managed - Premier (UNIX)

• Consolidated Semi Managed - Standard

• Consolidated Limited Managed – Sandbox

The DCS program supports operating system standards that include:

• Microsoft Windows,

• Red Hat Linux,

• SUSE Linux,

• OES Linux,

• AIX (non-standard - by advanced exception approval only), and

• Oracle Linux (Enterprise Exadata and Fractional Oracle only).

Data is protected by the Dell EMC Data Protection Suite, which writes to replicated tapeless systems in the alternate data center for Disaster Recovery purposes.

All DCS compute platforms use DCS enterprise SAN storage except for the Fractional Intel VxRail hyper-converged infrastructure (HCI) that uses an internal VSAN technology.

The DCS program offers CDC virtual compute solutions for Intel (Windows / Linux), and IBM Power System Platforms (by exception approval only) based on Agency business needs. See below for more information.

3.1 Fractional Intel Virtualization (Consolidated Data Center)

The Fractional Intel Virtualization solution is an Infrastructure as a Service (IaaS) offering providing an Intel virtualized environment based on both Converged and Hyperconverged hardware platforms. The Fractional Intel platforms support both Windows and Linux operating systems.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 13 of 22

Reliability is supported with the use of VMware virtualization and high availability clustering.

Flexible configurations are available in 1vCPU and/or 2GB memory increments. Maximum limits are 500GB memory and 72vCPU for HCI or 64vCPU for VBlock.

3.2 Enterprise SAN Storage

The DCS program provides Enterprise SAN storage services using a four-tiered model. The tiered storage methodology supports the use of various types of data storage architecture, pricing, and recovery. The solution provides enterprise class performance and resiliency.

3.2.1 Server Enterprise SAN Storage Tiers

• Tier 0 - All SSD storage: Highest IOPS and fastest response times

• Tier 1 – Ultra high-performance storage: Generally, for very high database transactions

• Tier 2 – High performance storage: OS and production databases requiring high performance

• Tier 3 – Medium performance storage: Standard storage requirements

3.3 Private Cloud Managed Support Services (available for all compute platforms)

3.3.1 Fully Managed Private Cloud

The SCP is responsible for all aspects of the IaaS lifecycle, including provisioning the:

• Ongoing OS support including monitoring,

• Ongoing database and middleware support (where optional services are selected),

• Hardware maintenance,

• Incident, change, and Agency service requests,

• Service Catalog requests,

• Asset discovery and CMDB integration,

• All base security functions (e.g., antivirus, patching, SIEM), and

• Optional advanced security available.

3.3.2 Semi-Managed Private Cloud

The Agency is responsible for OS support and all application-level support as summarized below.

SCP Responsibilities

• Provisioning

• Acquiring, installing, and patching the OS

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 14 of 22

• Installing and maintaining antivirus protection

• Performing SIEM logging, critical watch reporting and security incident response

• Performing hardware container maintenance and reboots

• Responding to incidents and Service Catalog requests related to hardware

• Asset discovery and CMDB integration

Agency Responsibilities

• OS management

• Monitoring

• Creating and managing incidents, change requests, and Service Catalog requests

3.3.3 Database Standards

Database management support for multiple database platforms are classified as two groups.

Each platform allows for support and management of a database environment with Agency privileged access and with varied availability requirements for each unique Agency.

3.3.4 Standard Databases

• Oracle

• MS SQL

• MySQL

• DB2

3.3.5 Non-Standard Databases

• Sybase

• Informix

• Adabas

3.4 Oracle Database Offerings

3.4.1 Enterprise Exadata

Enterprise Exadata is an option for Oracle Real Application Cluster (RAC) databases requiring high performance and high availability. Enterprise Exadata is a shared Oracle engineered system that provides an isolated multi-tenant environment. Enterprise Exadata provides virtual machine clusters consisting of two Oracle virtual machines (nodes) with support for up to 4 nodes to provide increasing levels of performance and resiliency.

Enterprise Exadata Resource Units (RU) are as follows:

• Exadata Cores – the number of compute cores on the Exadata platform dedicated to the Agency workload.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 15 of 22

• Exadata Memory – the amount of memory on the Exadata platform dedicated to the Agency workload. Memory is allocated in 2GB increments.

• Exadata Storage – the amount of storage on the Exadata platform dedicated to the Agency workload. Storage is allocated in 1GB increments.

3.4.2 Enterprise Exadata Oracle Database Software and Options

Minimum Requirements

• Oracle Enterprise Edition

• Oracle Real Application Clusters (RAC)

• Oracle Diagnostics Pack

• Oracle Tuning Pack

• Oracle Database Vault

• Oracle Advanced Security

• Database Lifecycle Management Pack

• Oracle Cloud Management Pack

• Oracle Partitioning

3.4.3 Fractional Oracle

Fractional Oracle is a potential refresh target for small databases and Oracle applications.

Fractional Oracle alleviates the software licensing issues with running Oracle Database software on VMware because it allows for sub-capacity licensing on Intel. It also provides better scalability and resiliency than bare metal servers. Fractional Oracle runs on the same converged infrastructure hardware as Fractional Intel and takes advantage of existing support resource units. However, Oracle Linux KVM is used as the virtualization software instead of VMware.

Fractional Oracle supports Oracle Linux, RHEL, and Windows virtual machine operating systems.

• Minimum Fractional Oracle vCPUs is 2 and can be scaled in increments of 2 to a maximum of 60 vCPU. Virtual memory can be allocated in 2 GB increments up 500 GB.

• Minimum Oracle Database software requirements for Fractional Oracle.

• Oracle Standard or Enterprise Edition version 19c.

• Oracle RAC is not required in the Fractional Oracle environment, but it is an available option for databases requiring high availability.

3.4.4 Database Services Support Options

The DCS Database support options provide DCS Agencies with greater flexibility to support application development, release initiatives, and aggressive application business availability requirements. The DCS program uses a two-level approach to support.

Fully-managed: Maintains the level of support that has historically been provided for databases.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 16 of 22

Semi-managed: The Agency has the majority of privileges and responsibilities but retains service provider support for availability, monitoring, maintenance, backups, patching, and upgrades.

3.5 Private Cloud Hardware and Software Currency

The DCS hardware infrastructure is refreshed on a 60-month refresh cycle. Operating software, database software, and application utility tools are required to be within n or n-1 of the currently supported versions of the software manufacturer. The Respondent is required to ensure the application software developed for <app name> will support the DCS standard hardware and software platforms as described in the DCS Standard Configurations.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 17 of 22

4 Level 1 Help Desk

If needed for the solution, the Successful Respondent is required to maintain a Level 1 Help Desk to triage all calls prior to submitting an incident to the DCS Support Center. Once the Successful Respondent has determined or suspects the cause of an incident is related to a DCS infrastructure component, the Successful Respondent will log into the DCS Support Center’s system to report the incident in accordance with the DCS Services Management Manual.

(Note to Agency: adapt this section to align with your Level 1 Help Desk support strategy.)

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 18 of 22

5 Functions Retained by <agency> – Not Provided by Data Center Services

For clarity, the following services are not provided by DCS Service Providers. In developing your response, the Respondent should clearly understand that the Requestor (Agency) performs these functions as needed.

• End-user computing, including desktop, mobile, and LAN-attached multi-function devices.

• Network support, including WAN/LAN support outside of the State data centers, voice/phone support.

• Help desk (Level 1 – all services).

• Expert troubleshooting and support for all non-DCS services.

• Technology planning, strategies, and visioning.

• Project management.

• Disaster recovery planning and testing for all retained services.

• Business continuity planning for Agency processes.

• Packaged imaging systems (scanners, servers, optical disks, etc.).

• Coordination of data center print services, including coordinating form changes with business units, volume trending.

• Data security, security design and policy development, systems access requests (directory/file, ID creation and removal, determination of access rights).

• Logical database administration.

• Application development, support, maintenance, and monitoring.

• Electronic payment processing services.

• Data import and export to the environment (FTP services).

• Reporting services.

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 19 of 22

6 Shared Technology Services/Agency Program Responsibilities Overview

Services STS Customer Systems/Environment Monitoring

• IaaS/PaaS (Network, Compute, Service, Storage and OS, Middleware, Database) R

• Application

Security Monitoring and Management

• IaaS/PaaS (Network, Compute, Service, Storage and OS, Middleware, Database) - Solutions, Monitoring, Management, Patching, SIEM, CSOC (ITD/ITP, Malware, DDOS, logging). DCS SIEM is for DCS-managed environments (IaaS/PaaS) events

Network Provisioning and support -Direct Connect and Public Cloud Virtual networking (e.g., VPC, VNET, firewalls)

R

IaaS/PaaS Compute, Storage and Services Provisioning R Support Services

• Incident, Request, Change, Problem, Availability, Management R

• IaaS/PaaS (Network, Compute, Service, Storage and OS, Middleware, DB) R

• Installation and Upgrade Support (Software Services) R

Service Request Management (e.g., startup shutdown services for IaaS, PaaS environment support)

Event Management

Asset and Configuration Management

• Application - Software discovered is populated in STS CMDB. Agency responsibility for Business and relationship correlation of application data in MSI-provided APM (Application Portfolio Management System)

Backup and Recovery R

Disaster Recovery R

Production Scheduling - Application level scheduling is responsibility of the Agency

R R

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 20 of 22

Services STS Customer

• Availability Management (IaaS, PaaS) R

Identity and Access Management

• IaaS/PaaS (Network, Compute, Service, Storage and OS, Middleware, DB) -

Privileged Access Management for DCS Provider managed IDs

• Application - Includes DB where Agency not choosing Optional DCS DB support services

• Account Lifecycle Management-For respective areas of support responsibility

R R

• Active Directory – Agency-owned AD with access granted to DCS as required for delivery of managed services. Agency and SCP co-exist with responsibility for respective identities.

R R

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 21 of 22

7 Document Control

7.1 Revision History

Version Date Author Title and Company Description

5.0 10/5/2020 Sally Ward DIR Updated for Transition

6.0 5/4/2021 Cyndi Barcio Process Analyst, Capgemini

Converted to Policy Document from Ancillary

7.0 8/15/2021 Cyndi Barcio Process Analyst, Capgemini

Updated to template for FY2021 Currency

8.0 2/12/2022 Brad Helbig DIR No changes needed for Currency

9.0 3/8/2022 Gloria Rivera Director, DIR Updated for new SaaS policy

10.0 2/2/2023 Brad Helbig DIR Updated with new PaaS information

11.0 4/3/2024 Sally Ward DIR Updated Private Cloud and Public Cloud service information

12.0 6/21/2024 Sally Ward DIR Updated section 1.6

13.0 6/18/2025 Gloria Rivera DIR Updates to section 1.3

14.0 08/28/202 5 RPA RPA, Capgemini Updated ServiceNow links & email as part of GCC migration

7.2 SP Process Owner Approval

Version Name Title and Company Date Signature

N/A

7.3 QA Review and Approval

Version Name Title and Company Date Signature

5.0 Cyndi Barcio Process Analyst, Capgemini 10/5/2020 Approved

DCS RFO Language| Policy |Version 14.0 |Version Date: 8/28/2025 22 of 22

Version Name Title and Company Date Signature

6.0 Cyndi Barcio Process Analyst, Capgemini 5/4/2021 Approved

7.0 Cyndi Barcio Process Analyst, Capgemini 8/15/2021 Approved

8.0 Cyndi Barcio Process Analyst, Capgemini 2/12/2022 Approved

9.0 Cyndi Barcio Process Analyst, Capgemini 4/1/2022 Approved

10.0 Cyndi Barcio Process and Training

Lead, Capgemini 2/2/2023 Approved

11.0 Cyndi Barcio Process and Training

Lead, Capgemini 4/3/2024 Approved

12.0 Cyndi Barcio Process and Training, Capgemini 7/27/2024 Approved

13.0 Jesse Ware Process and Training

Analyst, Capgemini 6/18/2025 Approved

3.5 Private Cloud Hardware and Software Currency