VITA-RFP 2026-03 - 01.4 Exh (Operating Level Agreement Outline).docx

DOCX document 69 KB Posted

Attached to
End User Computing (EUC) Services
Solicitation number
RFP-123896
Issued by
Richmond City, Roanoke City, Virginia

About this file

This document is an Operating Level Agreement (OLA) Outline for the End User Computing (EUC) Services contract opportunity issued by the Virginia IT Agency (VITA) on behalf of the Commonwealth of Virginia. The RFP seeks a single strategic supplier to deliver enterprise-wide, next-generation end-user computing services to Virginia Executive Branch agencies and other public bodies. The supplier will provide fully managed, secure, and compliant end-user services with flexibility to support both supplier-owned and Commonwealth-owned/leased devices. Key deliverables include end-to-end service delivery encompassing device support, software support, troubleshooting, lifecycle management, and financial and asset tracking processes (including CMDB and GASB compliance). The supplier may propose value-added or premium services as optional capabilities and will be required to continually improve service and device offerings throughout the contract term while focusing on service quality, operational efficiency, and customer experience.

The EUC supplier will function as a full Tier 1 supplier integrated within VITA's managed services infrastructure (MSI) platform and toolkit. All EUC-provided tools must be non-proprietary and cannot utilize formats that hinder or prohibit integration into the MSI platform. VITA and the MSI integrator shall maintain full, uninhibited real-time visibility into the content and configuration of all EUC-provided tools. This Operating Level Agreement Outline serves as a framework document defining the operational expectations and service level commitments between VITA and the selected supplier, establishing the baseline service delivery model that will build on the current framework while optimizing and modernizing services to align with current capabilities and operational realities.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

RFP 2026-03: End User Computing (EUC) Services Exhibit 1.4: OLA Outline

SUPPLY CHAIN MANAGEMENT (SCM)

REQUEST FOR PROPOSAL

Exhibit 1.4 Operating Level Agreement Outline

RFP 2026-03: End User Computing (EUC) Services

COMMONWEALTH OF VIRGINIA

VIRGINIA IT AGENCY (VITA)

SUPPLY CHAIN MANAGEMENT (SCM)

7325 BEAUFONT SPRINGS DR

RICHMOND, VA 23225

Table of Contents

1.0Introduction2
2.0General3
3.0OLA Framework3
4.0Interdependency Commitments4

Introduction This Exhibit 1.4 (OLA Outline) sets out the framework and requirements for the Operating Level Agreements (each, an “OLA”) that will be agreed to and maintained between each of the Integrated Suppliers. It is intended that this outline will guide the Integrated Suppliers through an iterative process to identify and address material work practices where each party has a reliance or dependence on the other.

Ongoing maintenance of each OLA between Integrated Suppliers as defined in Exhibit 3.1 (Service Level Matrix), Recurring Deliverable 2.14, will include changes to preserve alignment with each party’s operational commitments in each of their respective agreements with VITA, including alignment with changes in the Service Management Manual or their respective Descriptions of Services, Service Levels, Task timeframes, project plans, and other changes impacting services, including Corrective Action Plans.

General The Supplier acknowledges and agrees that the delivery of the Services to VITA and Customers requires significant integration, cooperation, and coordination of processes and procedures among the Integrated Suppliers, and OLAs will be used to document commitments between the Integrated Suppliers to ensure seamless delivery of the services each is providing to VITA and the Customers and to address the joint operation, issue resolution, and governance of the delivery of the services being provided by the Integrated Suppliers. A template will be provided.

The Supplier and other Integrated Suppliers (including the MSI) must share with each other various materials, data, and information, and provide access to systems, equipment, personnel, and other resources, in each case related to the services performed by one or more of such parties for VITA and Customers.

The Supplier and other Integrated Supplier will acknowledge and agree in each of their OLAs that the MSI will assist and coordinate the delivery of Services to VITA and Customers. In addition, the Integrated Suppliers will each promptly disclose to the other any material difficulties or delays experienced in connection with the delivery or operation of their respective services.

Notwithstanding anything provided in this Exhibit 1.4 (OLA Outline), under no circumstances shall any OLA change, limit, or otherwise impact any Supplier’s obligations under its Agreement with VITA, including, without limitation, the Supplier’s obligation to provide the Services to meet the Requirements set forth in its respective Exhibit 2.1 (Description of Services – End User Computing (EUC) Services).

OLA Framework This OLA outline and the specifications for what will be an acceptable level of detail to guide the parties in the development of OLAs will evolve and further develop in line with the refinement and completion of each of the Integrated Supplier’s agreements with VITA. Set out below is an initial checklist to guide the parties:

0. Document Control and Version Information: The OLA will be under VITA Governance control and reside in the Document Data Store.

0. Authorizations, Dates, and Signatures: The OLA must have the authority to allow enforcement. Each OLA will be signed by an authorized representative of the applicable Integrated Suppliers.

0. Objectives: To be clearly stated with measurable benchmarks, whether for a discrete service component or the services overall, as applicable.

0. Obligations: Obligation to cooperate. State specifically the obligations of each Integrated Supplier by scope of service (Service Tower), service diagram, handoff and dependencies, listing the deliverables for each party and any costs associated with deliverables that need to be paid to any Integrated Supplier (Example: Disaster Recovery Certificates), Force majeure, intellectual properties, and assignment. This is not the same as the services covered under the Description of Services, but rather the obligations of each party to the other with respect to delivery of the services.

0. Governance: Approach to managing the OLA that includes managing and coordinating issues, communications, and oversight responsibility that are aligned with and reference Exhibit 1.2 (Governance Structure).

0. Issue Escalation and Resolution: The OLA must include procedures to resolve any problems or complaints between the parties regarding the delivery of the Services that are aligned with and reference the processes and procedures for dispute and escalation, in accordance with the Agreement and the Service Management Manual. The procedures should be focused on resolution of problems, assurance of prompt service delivery, and the acceleration of support for high priority issues.

0. Reporting, Reviewing, and Auditing: The OLA must include procedures for oversight reporting and quality review. This section defines under what conditions to review the OLA, and when, what and to whom to report. Include approach to updating interdependency commitments (described in Section 4.0 below), including alignment and dependencies with the Service Management Manual.

Interdependency Commitments In alignment to the processes defined in the SMM 4.1.3.9 Supplier Management, the parties to each OLA will identify the interdependencies and document their respective commitments, between the MSI and each of the other Integrated Suppliers and between the Integrated Suppliers with responsibility for Service Towers, needed to deliver the respective services within their respective OLAs. Descriptions of the following elements should be identified and described for each commitment:

0. Description: Explain the interdependency and specifications of interfaces including the relationships between Integrated Suppliers.

0. Shared Roles and Responsibilities: Document who has which responsibility(ies) in delivering the shared services.

0. Qualitative Standard: Describe the distinguishing characteristics that satisfy the expected interaction.

0. Quantitative Measures: Define measures that are reflective or indicative of the expected performance. For example, these provisions might include the definition of initial response to inquiry, time to review and evaluate, time to perform diagnostics, etc. These times must align with the escalation times. These should be specific timeframes for each supplier related to a service or incident that combined will equal to no more than the total time to deliver the service.

0. Dependencies: Describe solution-based dependencies related to shared use of facilities, equipment, licenses, tools, systems, materials, staffing, and other resources including any financial agreements or implications. List specific dependencies related to the process or other operating procedure. These may include related inputs or outputs to process or procedure.

0. References: Include references to related documentation, procedures, definitions, Service Management Manual procedures, and any other resource that make it easier to follow, understand, or maintain the OLA.

image1.jpeg

File details come from the government source that posted it. Updated .