Skip to main content

Operational Support and Analysis (OSA)

What if we did not build an operational support system to meet current business requirements?  That might sound a bit outrageous and contradictory to everything we have learned.

If you are a service provider than you are aware that what we consider premium service support today could be accepted as the norm and sometimes can be outdated before it becomes a reality.  The key to sustaining underpinning operations for any industry is in the constructs of the system.   If we build a system to provide what the customer and business outcomes require now then that is what we will have.  The likelihood is that we will have a system that provides for a service that will render itself less than optimized in a shorter time than we would like to think.

What is required is an operational support system that can deliver fast but also one that is able to shift, bend and weave with the ever-changing environment and outcomes that it supports.  We need a growing living moving system that can adapt to changing business and customer requirements.  A dynamic, not static support system.

At the core this system will need to have the capability to monitor, analyze, predict and most importantly to act.  All of this must be done at an exponential rate in order to meet the dynamic needs of our customers and strategic business requirements.  But wait… isn’t that what we have always done?

In order to build a system that is not static to today’s requirements, but rather one that can adapt to changing requirements, the core principles of best practice still apply.  For example what if we exploit Event, Incident and Problem Management systems to monitor and analyze patterns of business activity and forecast what would be required to meet future changes?  What if we could automate the feedback loops and adjust our service assets to provision and optimize business assets ahead of time?   It is difficult to exploit and build upon an operational system if our baseline is reactive or chaotic.

It all starts with knowing the important role of Operational Support and Analysis in service provision and understanding how processes interact with other Service Lifecycle processes. 

Long gone are the days when the data center was in the basement and the help desk was a necessary evil. Today, businesses are irreversibly dependent upon technology and real dollars are lost when IT services are not available.

To gain knowledge and certification in OperationalSupport and Analysis


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 policies (r…

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 the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…