Browse Definitions :
Definition

operational level agreement (OLA)

What is an operational level agreement? 

An operational level agreement (OLA) is a contract that defines how various IT groups within a company plan to deliver a service or set of services. OLAs are designed to address and solve the problem of IT silos by setting forth a specific set of criteria and defining the specific set of IT services that each department is responsible for. It should be noted that the term Service Level Agreement (SLA) is used in many companies when discussing agreements between two internal groups, but according to the Information Technology Infrastructure Library (ITIL) framework for best practices, this type of internal contract should be called an Operational Level Agreement. 

 

Six tips for crafting an OLA
1. Define all the services IT is responsible for in a Service Catalog.

2. As CIO, get involved in the process by understanding what each service entails.

3. Define the key players (the networking team, the server group, etc.) and their responsibilities.

4. Lay out each IT group's expectations for delivering each service.

5. Come up with contingency plans for unexpected events.
 
6. Test and retest OLAs, and make changes when needed. OLAs, like SLAs, shouldn't be static and should have a beginning, middle and end date.

Source: Laura DiDio

 

Though a component of the IT Infrastructure Library (ITIL), OLAs can be -- and often are -- implemented on a standalone basis.

This was last updated in March 2011

SearchCompliance

  • information governance

    Information governance is a holistic approach to managing corporate information by implementing processes, roles, controls and ...

  • enterprise document management (EDM)

    Enterprise document management (EDM) is a strategy for overseeing an organization's paper and electronic documents so they can be...

  • risk assessment

    Risk assessment is the identification of hazards that could negatively impact an organization's ability to conduct business.

SearchSecurity

  • honeypot (computing)

    A honeypot is a network-attached system set up as a decoy to lure cyber attackers and detect, deflect and study hacking attempts ...

  • spam trap

    A spam trap is an email address that is used to identify and monitor spam email.

  • cracker

    A cracker is someone who breaks into someone else's computer system, often on a network; bypasses passwords or licenses in ...

SearchHealthIT

SearchDisasterRecovery

  • risk mitigation

    Risk mitigation is a strategy to prepare for and lessen the effects of threats faced by a business.

  • call tree

    A call tree is a layered hierarchical communication model that is used to notify specific individuals of an event and coordinate ...

  • Disaster Recovery as a Service (DRaaS)

    Disaster recovery as a service (DRaaS) is the replication and hosting of physical or virtual servers by a third party to provide ...

SearchStorage

  • cloud testing

    Cloud testing is the process of using the cloud computing resources of a third-party service provider to test software ...

  • storage virtualization

    Storage virtualization is the pooling of physical storage from multiple storage devices into what appears to be a single storage ...

  • erasure coding

    Erasure coding (EC) is a method of data protection in which data is broken into fragments, expanded and encoded with redundant ...

Close