Skip to main content

Standard Operations and Maintenance

Sandy, if you have any more questions, just let me know!

Standard Operations and Maintenance is really something that gets defined in the Service Level Agreement in consultation and negotiation with the customer. It is not really a determination made solely by IT or Operations. It is the customer or receiver of service that helps to establish whether an “outage” has occurred. Because we want to adhere to the terms and conditions set forth in the SLA we want strong controls in place.

I think it is not a question as to whether the Change Management process will be used or not used. It is more a question of the degree of Change Management that will be used. A solid approach would be to establish a clear definition of a Service Change in the organization.

ITIL says it is any “addition, modification or deletion of elements of the delivery of service” [paraphrased]. This is a broad definition and covers just about everything we do in IT.

So, next we need to identify what we actually do in IT to deliver and support services and see if it matches that definition. If it does we need to decide if we want to apply full ITSM control and tracking to that activity (e.g. rebooting a server). This means identifying Configuration Items, applying Incident and Problem Management, and so on through all our established ITSM processes.

Once we have identified the activities we do that constitute Service Changes, we can decide which ones fall under Standard, Normal and Emergency Change types. This will help us determine the degree of Change Management control for that activity.

• Standard: Pre-approved (one time to the Change Advisory Board), low risk, low cost changes, little potential for an “outage”

• Normal: Unique, higher risk, higher cost, greater potential for an “outage”

• Emergency: Cannot wait, serious impact, true emergencies (failure to complete paperwork does not count), “outage” already exists

The bulk of what might be considered “Standard Operations and Maintenance” should be done using Standard Changes. Like for Like (break fix-e.g. swapping network cards) items can be handled as Incidents, which are in effect substituting for a Standard Change.We should use Change Management to establish control, risk management and assurance of the delivery of service (value to the customer), rather than seeing it as an optional process.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with