Showing posts with label Service. Show all posts
Showing posts with label Service. Show all posts

Tuesday, September 22, 2015

Framework Flexibility - From CLAP to CLIP



As many readers may have noticed, there are some fairly significant gaps in the CLAP Framework. In the perfect world, it is really intended as a guide for how to execute Business Goals into practical IT Projects. But there  may be some flexibility in the simplicity of that framework.

A colleague pointed out that maybe the missing component wasn't necessarily the Application, as those needs are covered off in the Functional Requirements. He suggested that instead the framework should consider the Information Architecture itself.

For the purposes of this framework, lets consider that data is the raw input of a process, and information is the output. Information needs to have a defined structure and each element has a distinct meaning. Consider the difference between distance an speed. Distance is a unit of measure, denoting how far something is. Speed is the distance divided by the time taken to travel the distance. Speed is the result of a process. applied to the data.

In the CLIP Framework, the notion of Information Architecture is added. It describes the processed data, its flow from system to system, and its attributes. For example, is information synchronous (live from a source) or asynchronous (delivered by a different process). Further, we see where the Requirements and Standards get applied, and how Security Requirements need to be considered through every step of the process.

Finally, we see the Validation step happens just before the solution is transitioned to Operations. It asks the question "Did the final physical solution deliver what was designed ?". Arguably, there is another validation step, which asks the question "Does the Solution Architecture satisfy all of the requirements ?".

The validation is key, as this largely waterfall process needs to map the entire solution all the way back to the original Business Activities, described in the functional & non-functional requirements. As you can see, the framework is flexible enough to be applied to many IT Goals, and not so rigid as to be unmanageable.

Sunday, September 13, 2015

Pulling It All Together - CLAP + PMLC

In a series of previous posts, we took a look at various frameworks for bringing valuable IT Services to an Enterprise. Starting with the CLAP Framework, we saw took a look at a basic way of starting with Business Activities and building the necessary Conceptual, Logical & Physical Infrastructures to deliver valuable IT Services.

Next, we saw how to use a tool like the ERRC Canvas to achieve the Enterprise Strategy, by mapping the strategy to goals & objectives. The key function of the canvas is to separate the objectives into four areas: Eliminate, Reduce, Raise & Create. 

Once divided, metric for success are applied, and plans can be created. These plans can be prioritized and dependencies mapped. Getting from Business Strategy to IT Execution is no easy feat - so this post describes a method of execution.

Of course, understanding goals as they relate to Strategy is also very important. We took a look at how to create SMART Goals.
Illustration: CLAP and PMLC Together on One Page

We are now in a position to pull all of those concepts into one diagram, shown above. I have attempted to layer the various concepts together, and embellished them with some extra information, such as when a project can expect to need to engage various roles within the RACI.

Finally, we see three vertical lines which describe a form of IT Governance. In a future post, I will describe the make-up of the ARB/TRB and explain the importance of the Architectural Validation Plan.

Sunday, December 1, 2013

Cloud - Platform as a Service

This is part three of a continuing discussion of The Cloud. In Part 1, we discussed how people perceive the cloud, and where these perceptions come from. In Part 2, we looked at Software as a Service (SaaS). Now let's look at what was the next logical evolutionary step - Platform as a Service (PaaS).

In discussing PaaS, we first need to understand a couple of other major milestones in computing history - virtualization and clustering. Virtualization has a big name for a simple topic. These days, almost anything can be virtualized: applications, operating systems, even hardware. We use the term "virtualization" to describe a method of abstraction. For example, a company called VM-Ware has made a business out of PC hardware abstraction, allowing them to virtualize the operating system of a computer. This allows them to run multiple instances of operating systems on the same compute platform, simultaneously.

A computer's operating system (OS) is responsible for "talking" to the hardware. For example, it interfaces with the hard-drive, so the applications we use don't have to know how to write the data to the disks. It interfaces with all of the various components, including the microprocessor, the random access memory (RAM), the hard disks, the network interface cards, and so on.

Then the virtualization layer comes into play, called a hypervisor, abstracting the hardware from the OS. Acting like a translator, it says "don't worry what KIND of processor or RAM" you think I'm supposed to have, I'll translate your queries & responses in a way that you will understand. This abstraction layer means that the OS can be deployed onto any piece of hardware, running the same hypervisor ! The underlying hardware layer becomes unimportant.

The first way this became important was in the area of Disaster Recovery. Since the OS and it's applications were now encapsulated into a computer file, and hardware-specific drivers were no longer important, moving the OS from one hardware platform to another became trivial. If a systems administrator could move the OS across the computer room, why not across town ? Or across the country ? Suddenly, disasters weren't catastrophic to a business.

Another key element to PaaS is the concept of the server cluster. Prior to virtualization, server clustering allowed PC-based servers to perform two duties - 1) scale the load of a single application beyond the hardware capabilities of a single server (aka a "node"), and 2) allow redundancy in the event of maintenance or a hardware failure. Google's famous search engine runs on many multiple server clusters, which are in turn load-balanced across different data-centers, so that new search requests go to less busy servers. So when a query comes to the virtual address of the cluster, the cluster-manager software determines which node to send the request to. The decision can be based on any number of criteria, such as how busy the nodes are, or the relative distance from the originator of that request.

Now that we have a hardware-independent hypervisor, and the ability to cluster our hypervisors, we can now discuss how to deploy PaaS. When an IT Department needs to set up a service, say a web-server, they can skip the phases of hardware and OS procurement, the phases of assembling the hardware, installing the OS and hardening it for security purposes. They skip ALL of that by simply logging onto their cloud-provider's management web-site & making a few choices and pressing the "provision" button. Then all they need do is install & configure the web-server and connect it to the data source. Clustering is important for making the OS Guest redundant across the provider's data-centers.

The main advantage of such a configuration is that it allows the service to be deployed in an elastic fashion. That means it can grow and shrink according to actual demand, rather than having to guess in advance what demand might be. Since the IT group doesn't need to buy new equipment for each new node, there is a shift from capital expenditure (CAPEX) to operational expenditure (OPEX), as well as potential savings related to the delay in time it takes to procure and deploy the new server hardware. Obviously, the cloud isn't free. Providers of PaaS typically charge for their service according to a number of metrics, including compute cycles, amount of disk-space required, and so forth. The positive is that the IT Group only pays for what they use, on an ongoing basis, rather than guessing and paying for it up front.

Again, we are seeing a shift in the business model. Now, the deployment can be very rapid, eliminating the acquisition phase altogether. The provider supplies the hypervisor and the operating system, and the client need only deploy the application. This allows the IT group to be agile in providing the services that its business requires, while having predictable costs associated with operating the service.

 

Sunday, November 25, 2012

Alberta Internet Exchange

I'm proud to discuss my latest project : the Alberta Internet Exchange. It mixes the concepts of Open Source and public interest really well. I have been asked to contribute to the architecture committee, and am happy to participate !

So what is an Internet Exchange, you ask... The idea is to peer member networks together, so that they don't have to traverse the Internet itself in order to exchange data. Think of it like a chat-room: interested parties can join the chat-room and exchange information, without having their data traverse the Internet & return via Des Moines or Beijing ! This video helps explain it really well. The Eurpoean IX

What makes the Internet Exchange so exciting to me is that it will be made available for the smaller Internet Serice Providers and clients alike, so that they can compete on a level playing-field with the big Telcos. This offers the users of the service abundant choice to determine which provider can best suit their needs. Most importantly, it serves the needs of Western Canada, who wold otherwise be forced to peer at Toronto or Seattle.

 

Sunday, November 18, 2012

The Importance of Process

 
I haven't blogged in some time. Seems life can get overwhelmingly busy at times, and well - it has been some of those times ! I've been spending a lot of time lately working on things that are process-oriented. Seems that when organizations want to define the products and services they sell, they ignore the industry-accepted definition.

According to ITIL, a Service is made up of people, process and technology. All too often, the organization believes that they can simply purchase and implement a tool, and all of their problems will miraculously disappear. I am working with two clients, who are approaching their delivery of a Service differently.

The first client is a large player in the Energy sector. To date, they have eschewed the use of ITIL terms to define their IT Service, as it doesn't readily fit their model for doing business. How could they let IT tell them how to run their business ?

When this client wanted to clean up their IT monitoring systems, they chose to segment the work into business-identifiable Services. They presumed they could buy a tool, and their visibility into their IT Operations would magically improve. They have been profitably in business for decades, so surely their processes and people were fine ?

In examining the first Service, it became apparent that the technology they were employing was actually satisfying 90% of their needs. It seemed the issues came up after the monitoring system alerted to a problem. Multiple service tickets were generated, usually causing a firestorm of activity - usually within the wrong groups ! To exacerbate the issue, the groups weren't communicating. This meant there was almost always a large duplication of troubleshooting effort.

In the case of the first client, the processes which were initiated were the root-cause of their issues. The technology did what it was supposed to do: send an alert when a problem arose. The people simply followed the process and reacted to the alert in a timely fashion. Unfortunately the process didn't allow for communication and co-ordination of their efforts, leading to delays and confusion in the IT personnel.

The second client is a small services company. They are re-building the company from the ground up; I call it going back into startup mode. In so doing, they are examining the services they provide to their clients. From the very basest levels, they want to be able to create repeatable, sustainable & desirable solutions for their clients.

This is being achieved by turning everything they do into a "project", with somebody responsible for managing that project at the helm. Project Management 101 would tell us that the Project Manager is responsible for Resources, Timeline and Budget - does this sound like what a Management Team should be concerned about ? So whether it is a team which is conducting Research and Development on a new physical product, or the Marketing guy working on building a new web-site, everything is a project. This provides visibility into "who ?", "when ?" and "how much ?" questions.

What this also means is that the second client can begin to normalize their Operations. By treating everything like a project, they have a repeatable framework to follow. The standard body of documentation required for every project (Charter, Cost/Benefit Analysis, Project Plan, Work Breakdown Structure and Closeout Report) allows for repeatability. Need a tower built ? Here's the required artifacts. Need a portable antenna installed ? Heres the project plan.

This will allow the client to have very tight control over their operations. This leads to increased productivity of the resources, as well as predictability in their Finance department, in terms of budget and revenue. The Sales and Business Development people can look at an exisiting Project Plan and estimate for themselves roughly how long it should take to complete a project. Further, if they are simply repeating a pre-exisiting project, they can likely provide a pricing quotation on their own.

So in both cases, we are seeing how these two very different clients are approaching their issues by examining the Services they provide. And in so doing, they are recognizing the importance of having well-documented procedures for their people to follow. The technologies they employ are all but irrelevant.

Monday, July 2, 2012

Open Source Frameworks

I will immediately start by saying that I have shamelessly stolen the idea for this blog. Massimo Banzi is one of the original creators of the Open-Source hardware platform, called the Arduino. It allows an inventor to program the microcontroller to control whatever mechanical system in whatever fashion they want. Imagine budding tinkerers building their own stop-lights, or fashioning their own motor-control systems ! 

In his Ted Talk (found here: How Arduino is Open Sourcing Imagination ), Massimo discusses how the Arduino gives inventors and tinkerers alike the ability to build with their imagination, pretty much free from the constraints of having to know very much about the hardware. Whether its the Arduino or one of the other new platforms, inventors and imaginers are free to explore the creative side, without getting too bogged down in the nuts & bolts of the hardware.
 

I'm going to make a leap here, so follow along... Another one of my Blogs describes my IT Service Management project, and briefly describes the use of the ITIL Framework. The purpose of the ITIL Framework, and more importantly the ITIL Dictionary, is to provide a common language for IT people to discuss the work that they do, and the services they provide.

 

Here's the leap: Arduino provides a common platform for tinkerers, inventors and imaginers to develop & share their ideas. Be they heliostats or stop lights. Just like the Global Village Construction Set describes plans for building the 50 commonly-used tools for building a society, Arduino provides a common platform for building the tools that society needs to control things.

 

Are you seeing the theme ? Open Source projects are providing the "Common Platform" required to get big, important things done. Like controlling mechanical devices, or building a society, or defining how we look at computer systems. This is why Open Source is so important.

 

Saturday, June 9, 2012

Chasing Shiny Objects

Shiny Objects

As my ITSM project continues, I am once again forced to have a series of uncomfortable conversations with my client. It seems that a smooth-talking sales rep has convinced an Operational Manager that they can solve all of their "monitoring and alerting" problems by simply ripping out what they currently have, and implementing a shiny new solution !

Shiny Services

Another Operational Manager has been consorting with a local Services Provider, who promises that if my client simply outsources their monitoring & alerting to them, all the problems will go away. For a low monthly fee ! Just sign a PO Mr Customer, and we can get started right away !

What's a Service ?

Now remember that the ITIL definition of a Service indicates that it is comprised as People, Process and Technology. In the first instance above, it appears that Manager believes he can buy a shiny new object, and all of his problems will go away ! That might speak to the Technology, but delivers nothing for the people or processes. In the second instance, the Manager is hoping to be able to outsource to the Services company, thereby dealing with the people aspect. But the Technology, and possibly the Processes are not being addressed. As such, neither solution deals with the underlying desire to take a "service-oriented" view of the IT Operation.

So in order to address this project properly, we will need to address all three facets of a service: Technology, Processes and People. I have re-ordered them because that is the most logical to me. I see the steps as:

  1. Interview the Executive Sponsors to determine what their objectives are. In essence, I like to ask "What business problem are we trying to solve ?"
  2. Interview the Operations Managers to determine what they see as being success criteria for the project.
  3. Interview the Operations Team Leads. They will provide deep knowledge of the environment, the tools, and the current processes.

Technology

These three sets on interviews will provide the information required for the first phase of the project : Information Gathering & Gap Analysis. The Gap Analysis artifact is the first real Deliverable of the project. Once complete the Gap Analysis will help define what Technology is suited for the overall monitoring needs.

Process

I am in the middle of developing a series of Process Diagrams. These are visual representations of the processes that Operations personnel must go through when a specific condition is detected and alerted upon. There are two diagrams per alert - current state, and desired state. Any gaps between the two are highlighted and root-cause analysis is applied. Typically, these types of exercises uncover communications errors, and/or inefficiencies in the processes.

People

Finally, the thorniest part of the project is examining the People on the various Operations teams. This gets sticky, because the objective is to examine whether or not the team members have the correct skills to perform the Future-State processes, with the tools highlighted in the Technology section. It is never intended as a criticism, but many teams feel threatened by this step.

Summary

So as you can see, an ITSM Project is a lot more than a discussion of how to monitor IT Infrastructure. It involves examining the People and Processes as well as the Technologies. Simply buying and implementing a shiny new technology won't adequately satisfy the objectives of delivering Service-oriented IT.

What's Next ?

In a future BLOG, I will examine the second phase of this project, which involves classifying the collected information into alerts and data-sets, with an eye to event correlation & reporting.