Showing posts with label Process. Show all posts
Showing posts with label Process. 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.

Saturday, September 12, 2015

Business Service Model for IT


IT exists for one purpose: to provide the tools necessary to enable Business Activities. Like we saw in the CLAP Framework, Business Capabilities are made up of a number of discrete Business Activities. But it is in the delivery of the Business Capabilties as a Service that IT provides value to the Enterprise.

The model for a Business Service is clearly defined by the ITIL framework. In short, it is composed of People, Process and Technology. Certainly, the framework also describes the meta-data, which includes the Service Owner, the Service Consumer and the Service Provider.

Once the functional and non-functional requirements of the Business Capabilities are mapped out, the application and its underlying infrastructure become straightforward to build out. As I have posted about previously, the Project Management Life Cycle can be easily applied to deliver these capabilities to the Enterprise. Of course, more than one capability can be provided by a single service. Often many services get grouped together to form a broader service.

There is also another relationship hidden in a simple model like this one. The degree to which a process is repeatable (and can therefore be automated) has implications to the People part of the equation. The more highly repeatable and automated a process is, the lower the required skill-set for the labour, which should in turn lower the cost of the Service to the Enterprise.


Friday, September 11, 2015

Project Management Life Cycle

Illustration: Project Management Life Cycle
We all know that IT projects don't just happen. They usually start with an idea that gets socialized internally, until somebody decides it is interesting enough to write a business case, justifying why the idea might be good for the Enterprise. The Project Management Life Cycle (PMLC) walks the reader, from left to right, through all the components of a project. It assumes the project has been instantiated and has executive sponsorship. Other activities prior to the project itself include the Opportunity Assessment, a Cost/Benefit Analysis, and likely ROI and TCO studies.

The PMLC illustration above is designed to show three things at each stage: the roles that contribute to the project, their responsibility and their deliverable. Starting on the left, the Stakeholders typically sit on a Steering committee, and provide budgetary approvals for the project.

The project is run by the Project Manager, who is responsible for budget, timeline & resources. They usually draft the Project Charter, which defines the objectives and scope of the project. They are responsible for reporting back to, and taking direction from the steering committee. It is their responsibility to deliver the project to successful completion.

The Business Analyst does a lot of leg-work, dealing with the stakeholders to understand requirements, both functional and non-functional. They will take raw data they have collected, and produce information which is valuable to the project, and consumable by all members of the project team.

Now that you have a general idea of the flow, you can interpret the rest of the illustration for yourself. Other information that will later become key is called the RACI. It is an artifact that names all of the roles (as seen in the illustration), and determines who is Responsible, who is Accountable, who is Consulted and who is Informed when a project decision has to be made.

This is a general look at how IT projects move through their life cycle. In a future post, I'll overlay the CLAP Framework, to pull together all of the concepts into a single view.


Thursday, September 10, 2015

From Business Strategy to IT Execution

Illustration - Strategy to Execution


As we have seen in my previous posts, I am always keen to tie IT Activities to Business Strategy. Whether it is in utilizing the CLAP Framework to map Business Activities to physical IT infrastructure, or in achieving your goals using the ERRC Canvas, the end-goal is always to drive Business Value.

In this basic diagram, the basic questions of Who, What, Why and How are directly addressed, leaving the When up to the Executive sponsors to decide in the Project Charter. The centrepiece is the ERRC Canvas, which helps define the Objectives (the What) & IT Activities that would meet the Goal. As with all SMART Goals, the element of Metrics help define the How.

Finally, the Plan is actually the domain of the Project Management Office. It would include the Project Charter and supporting artifacts, including dependency maps and budget estimates. Conventional Wisdom is that the Project Manager is responsible for Time, Resources and Budget.

Wednesday, September 9, 2015

How to Achieve Your Goals - the ERRC Canvas

Illustration - the ERRC Canvas

 

As you might already know, I love canvases. They provide a simple means of communicating ideas. The image at left describes a very basic canvas to convey a very powerful idea: What do I have to do to achieve a Goal ?

In another BLOG entry, I will discuss Goals - specifically what makes good goals vs what makes difficult goals. If you want to do some homework, in a future BLOG I will discuss SMART Goals and why they are effective.

In general, and especially true in Business and IT, Goals can be achieved by placing tasks into one of four broad categories - Eliminate, Reduce, Raise, Create. Let's take a closer look at these simple yet powerful concepts. But remember, Goals are only important as a means of realizing a Strategy. Often, strategies are realized through the successful completion of a number of goals. Equally, there may be more than one Strategy being realized !

Eliminate - this is a pretty straightforward concept. Ask yourself the question "What do I need to remove from the environment to achieve the Goal ?". It could be simple, like lets eliminate duplicate services. If two systems can service the same Business Activity, then one of them is redundant. Ergo, one of them could be eliminated & help achieve the Goal.

Reduce - this is also a simple concept. If the Goal is to "decrease server sprawl", then the use of a consolidation solution (think of server virtualization) would reduce the number of physical compute hosts required to service the the Business Activities. Implementing server virtualization reduces the number of server's required to host the workloads, realizing the Goal.

Raise - this often goes hand-in-hand with Reduce in that often reducing one element will raise another. In the above example, we looked at implementing server-virtualization as a means of reducing server sprawl. It also has the opposite effect of raising the rate of physical server utilization !

Create - This is the tricky one. What do I have to ADD to the environment to achieve the goal ? Fortunately, the context of these canvases is around achieving IT Goals, in alignment with Business Strategy. So you might create a new process for deploying the virtualized servers into the compute environment, perhaps to enable a new Business Activity.

Now, each one of these sections of the canvas can contribute to the overall goal, meaning you might have many entries in each quadrant, all in alignment to the goal. This helps develop a list of activities which might need prioritization & dependency-mapping in order to complete. But at least now you have a defined method of achieving the established goal !

 

Tuesday, September 8, 2015

CLAP Framework for IT

Many Enterprises struggle with IT frameworks. These frameworks are meant to help turn Business strategy into executable plans. Some frameworks, such as TOGAF or Zachmann will help an Enterprise IT group understand WHAT it needs to do to achieve its goals. Other frameworks, like COBIT or ITIL will further explain HOW to achieve those goals. When an Enterprise does not follow any of the established frameworks, they will often try to devise their own. The diagram above illustrates one such framework - the "CLP" framework (the "A" was added later, after missing information was identified).



Conceptual - this stage of the framework takes the Business Activities into account. Each discrete activity can be mapped out as a few elements in a process, describing a single activity. An example might be "calculate price".

Logical - this stage maps the discrete activities required. To calculate price, we need some information from a number of sources, such as the gross price, a taxation rate, a discount and a profit margin. Further, architectural governance (standards) are applied, such as use of a Linux operating system, or mandating a particular security framework. Finally, Non-Functional Requirements (NFRs) are described, such as how quickly a system must respond or how many transactions per minute the system must satisfy.

Application - this stage is where we begin to apply some business logic about what to do with the information. It maps out what the information should be expected to look like, such as expressing numbers in Currency notation, with two decimal points of precision. It will also describe any user interfaces and other means of accessing information. It specifically maps business activities to Functional Requirements.

Physical - this final stage helps identify all of systems that are required. Items such as CPU utilization and storage requirements are calculated to determine how best to implement the system into a computing environment. It describes systems interactions in terms of protocols and transports.

This is not an exhaustive look at frameworks, and many Enterprise Architects will keenly assess missing elements from this simplistic framework. But, executed properly, a framework such as this one could be sufficient for an Enterprise to begin taking advantage of IT to realize their business strategy.


Monday, August 17, 2015

Staying Alert When Shooting

I went out on a shoot last night. There were a number of shots I have been meaning to take, but the conditions haven't bee favourable. This first one I have been I visioning for months. There's an on-ramp into Stoney Trail (Calgary's ring road) which has runoff basins on either side. They fill with the runoff from the highway, and the rainwater is meant to evaporate, but never seems to.
I like to shoot frames in triplets for HDR purposes. It actually achieves two purposes. The first frame is perfectly exposed. The second is 2/3 of a stop over, and the third is 4/3 of a stop over. This gives me the ability to bring up the dark & shadowy spots. Then after I apply the HDR process, I can always play with the exposure rate to get the mood I am looking for, without losing the details.
The challenge To shooting triplets at night is that you have to remember to be situationally-aware ! I was so concerned with getting the exposure correct, I failed to notice the traffic. The first exposure was about 4 seconds, the second about 6, and during the final 9 second exposure a pickup truck came racing through my shot !


Monday, July 27, 2015

Rush, Rush, Rush...

No, not the famous Canadian trio of Geddy Lee, Neil Peart & Alex Lifeson (although they are awesome !). Rushing is the bane of the amateur photographer ! In this day of digital photography, it is way too easy to hurry and not think about setting up your shot.

For example, look at these two photos:

This one has the white balance set for a sunny afternoon, about 5000 degrees Kelvin. See how yellow it looks ? I look like I have jaundice or something !

 

This photo has had the white balance corrected to indoor, flourescent lighting, about 3200 degrees Kelvin. Notice how it looks a quite a bit lighter, and more natural ?

 

 

 

 

 

In fact, both photos were taken with flash & a 1/2 Green gel to compensate for the lighting. But because I had the white balance set up wrong - because I was rushing - all the photos were like this. Thanks goodness it was an easy thing to correct in post-processing !

Note to self - Stop. Check EVERY setting before looking through the lens...

 

Thursday, February 27, 2014

Project365 - Auto Strobism

Introduction
I have started following a blog which gives an introductory course to Strobism - the advanced use of various types of lights and light modifiers in photography. I started with a course called "Lighting 101". It is a fantastic resource for amateur photographers who want to sharpen their skills with lighting various situations.
In the course of my reading, I came across a challenging situation, in which the author was attempting to light a helicopter mid-flight ! While I haven't got a helicopter of my own to photograph, I thought I would attempt to duplicate the technique.
The Setup
My trusty Canon 60D was mated with the general-purpose Canon 24-105mm f/4 L lens & mounted on the Manfrotto tripod. The flash was mounted with the Cactus v5 remote trigger, so that it could be mounted off-camera.

This nifty little DIY mod is called a "lightbulb". The idea is that the sour cream container acts as a diffuser, and the light is thrown in all directions. In practice, it works very well, and I will likely keep this little mod in my kit.
























The Photos
Here is the basic setup: the "lightbulb" is placed inside the car between the front seats, and when triggered will light the car from inside. As you can see, I substituted Pat's car in the dark garage for the helicopter in the night sky.


This is a step towards the end product - you can see the desired effect. You can ALSO see the lightbulb peeking up above the dash !


I couldn't decide how to set up the shot with only one flash. So I also tried it in the back seat, to see how it looked. I don't like it as well, as the front seats are in deep shadow and you can't see anything but the silhouette of the fuzzy dice. In the perfect world, I'd like to shoot this with two flashes, one in the front, and one in the back.


Here is the final photograph, with the desired effect. Overall, I'm pleased with the effect, although one day I'll re-shoot it with a second flash.









Lessons Learned
Photography is really the craft of manipulating light. I thoroughly enjoyed this shoot, as it is an interesting & creative way to experiment with light. I might later try to reuse the technique, but with more light sources, and even models in the cabin.

Tuesday, February 25, 2014

Project365 - Get Out of the Way !

Introduction
While experimenting with Depth of Field, in a previous post, Pat suggested that using a fork on a plate might be a bit boring ! Instead, she handed me her David Yarmin ring to shoot. It's beautiful, to begin with, but has lots of interesting details - the facets of the stone, the twists in the ring itself, and the detail around the stone.

The Setup

Of course, the camera body was my Canon 60D, and I mounted it on a Manfrotto tripod. Next I mounted the Canon 40mm f/2.8 prime lens, and a 20mm extension tube because my subject was small, and wanted it to fill the frame. Next, I mounted my Canon 430EX II flash with the Cactus v5 triggers on a second tripod, and affixed a 8" snoot to focus the light very tightly. The flash was set to 1/64 power, and a 108mm beam.

The Photos

Oops ! See the orange tinge in the stone and the setting ? That's a reflection off of my t-shirt ! I only noticed it after I started processing the photos. This will never do...

 

 

This one is better. But if you look carefully at the bottom right of the stone, you can see my shadow outlined ! Sigh - another decent photo ruined by an accidental reflection. Next !

 

This picture is pleasing to the eye - no reflections, nice Depth of field, and an interesting composition. I also like how the facets of the cut stone show up, and the position of the flash helps draw out the detail of the mount.

 

 

 

Lessons Learned

As the first two photos illustrate, I must remember to get OUT of my own photos ! Being aware of one's surroundings, and how they might affect the photograph, are of paramount importance to the budding photographer.

 

Friday, January 17, 2014

Project365 - A Little HDR

Introduction
OK, OK... I said I wanted to stay away from post-processing, and to concentrate on my basic skills. Well... What if the technique I wanted to play with was a post-processing technique ? Let me explain...
As part of my "process" I drive around the city and I see all kinds of cool things, and I wonder what it would be like to shoot them. I may scout the location four or five times, assessing everything from daylight to traffic to weather. I live near the top of a hill in Calgary. Across the valley stands Canada Olympic Park. Its a snow-sports training ground, where athletes train to ski, ski-jump, snowboard, bobsled and luge. Of course it is also open to the public, being a city-owned facility.

The Setup
Camera - Canon 60D, Lens - Canon 70-200mm f/4 L, Tripod - Manfrotto 190CX Pro 3

Simple enough - I stood on the opposite hill, set the long lens to infinity, set the Aperture to f/11, the ISO to 1000 and shot at about 1/50th of a second. I also set the camera up to bracket one full stop (+1 EV, 0 EV, -1 EV). This gave me the under-exposure, correct exposure and over exposure. Three photos to give me the lowlights & the highlights.

The Photos
This is a technique in creating High Dynamic Range (HDR). There are three images - the source files, and finally the HDR-rendered image. I am trying out a piece of trial software called "Photomatix", which is considered "the name" in the field. I haven't paid for a license, so I must live with their stamps.

The first image is under-exposed by one stop. This means it is darker, but when you watch the ski-jump you see more of the detail.

This second image is properly exposed. You can see more of the detail under the lights on the ski-hill itself. But the ski jump is a little washed out.


This image is over-exposed by one for stop. The ski-jump is completely washed out, and the ski-hill appears well-lit.

 

This photo is the HDR version. The ski jump has nice detail, and the ski-hill seems reasonably lit. You can make out more of the details in the merged image.








Lessons Learned
HDR is not easy to capture. I have a little piece of pseudo-HDR software on my iPad which works with two images. Its not all that fantastic. The more images you have to work with, the more reference points the software can include - which creates some stunning images !
The skill is in the setup. Tripod, composition, exposure, getting the bracketing set up, etc. If these are all set fairly well, you have a shot at some good HDR images. This is merely a sample of something I will likely work more on.

Just for giggles, here is the best HDR I can do on my iPad. It's passable, but nothing compared to what Photomatix does on my MacBook Pro ! Compare the individual lights on the ski-hill. It's about an order of magnitude better resolution.

Now to be fair, my iPad only gets JPEG photos, while my MacBook Pro is getting the RAW photos. Of course, that will make a huge difference.

 

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.

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.