Serio Blog

Tuesday, 06 Nov 2007

This is a follow-up post to ITIL V3 - what does it deliver?

This key phase looks at the design, development and implementation of service management as a strategic resource.  Service Strategy is critical to all the processes involved in the Service Lifecycle.

If your organisation has already adopted ITIL® processes for its Service Management, then the Service Strategy Phase can help you improve the synchronisation between your IT and Business strategies.  This part of the V3 lifecycle can be used as a guideline for developing an overview of your capabilities. 

Service Strategy urges you to think about “Why” rather than “How”…the “Why” is far more important to your customer’s business than the “How”.

The aim of Service Strategy is to identify your competition and then compete with them by making your business stand apart and by delivering superior performance.

ITIL® names the following building blocks of well-performing service providers:

Market Focus – know where and how to compete

Distinguishing capabilities – create distinctive and profitable assets that the business appreciates

Performance anatomy – organisational standpoints that are measurable and feasible, such as viewing services as a strategic asset in which constant improvement is necessary.

The Service Strategy phase of ITIL® V3 can help your organisation to do business in a strategic manner. It encourages you to ask the questions that will help you stand apart from the competition. You should emerge from this phase with a clear vision of where you want to be and what milestones you need to reach to achieve that vision.

There are three processes involved in this phase of the lifecycle.

  • Financial Management
  • Demand Management
  • Service Portfolio Management

Financial management is critical to ensure that the correct financing is available for delivery and purchase of services.

The goal of Demand Management is to predict and, if possible, regulate demand.  Poorly managed demand is a risk on two fronts.  Excess capacity results in cost that cannot be recovered.  Insufficient capacity impacts the quality of service and limits its growth.

Service Portfolio Management (SPM) starts with the Service Catalogue. The process is dynamic and ongoing and comprises the following stages

  • Define
  • Analyze
  • Approve
  • Charter  

I'll follow this up later with more about ITIL V3.

Wednesday, 31 Oct 2007

So you have invested time and money in becoming a qualified ITIL® professional. With the changes in V3, are these qualifications still valid and meaningful?

This is probably one of the biggest debates in the IT Service Management community currently.

What I can tell you about the current state of play regarding qualifications is that there are bridging courses now available at Foundation level so that you can upgrade existing V2 qualifications to the V3 framework. The Bridging exam and syllabus for the Manager’s certificate is still under review and last I heard it will not be available until the first quarter of next year.

The V3 Foundation training is being reviewed in the light of concerns raised regarding the emphasis on Continual Service Improvement and Service Strategy; changes are likely to the syllabus as a result of this.

There has been some interesting discussion on the topic of exams and training for V3 on the IT Skeptic blog.

The new Manager’s qualification (the ITIL Diploma – although the name is still up for debate) will be made up of credits – you will be able to pick and choose the areas which apply best to the area you are working in to gain sufficient credits for the qualification.

There is a planned level above the ITIL Diploma qualification (Advanced Service Management Professional qualification), but details on this still seem to be a bit sketchy – there is not expected to be much more available on this until next year.

My own personal opinion is that the tried and tested V2 syllabus and exams are still valuable and valid qualifications. These qualifications are likely to remain available past the end of 2008 following feedback from the ITSM community. If I was looking at starting out now I would be trying to get my V2 qualifications and then bridge these to V3 once the syllabus and exams have had all the kinks ironed out of them.

From what I have seen of the proposed structure for the ITIL Diploma qualification, this will be a FAR more economical way to get this prized qualification under your belt. The number of training days required to get enough modules for the Diploma qualification if you start from scratch with V3 is going to make this qualification financially out of reach for many in the industry, it is hard enough to build a business case to do the V2 Manager’s certificate – the training days required for the V3 Diploma appear to be 2-3 times as many.

To get the new diploma you need to get 22 credits by taking the foundation course and various practitioner courses. From what I have been able to find so far it would appear that each course, worth 3-4 credits will take you around 30 hours of training - so you are looking at around 180 hours of training time to get the diploma. The V2 Manager's certificate was around 80 hours including the Foundation. It appears that the V3 Bridging course will also be around 30 hours. So doing the math, it is pretty obvious that getting the V2 qualifications and bridging is going to save a lot of time and money!

One thing to remember though, the pass rate for the Manager's bridging exam has been set at 80%, so you are really going to have to know your stuff to pass.

Some of the information on the qualifications is still a bit hazy, and it is a bit hard to get the full picture until the new courses start and people begin to get these qualifications, but I know what I would be recommending right now.

While the return to training organisations for each person who qualifies for the Diploma will be far greater than for the V2 Manager’s certificate, I think it will be a hard sell to get people to make the financial commitment needed to get there. So while I have heard a number of comments about what a windfall this is to trainers, I have a feeling that the opposite may be true…I guess time will tell.

Monday, 29 Oct 2007

ITIL® V3 was unveiled in May 2007. So what does it really mean to your business? If you designed the management of your IT Service on ITIL® processes, do you need to make changes?

The short answer is no…if you have robust processes that are delivering what your customers need and want then you don’t need to change anything.  The ITIL® v2 processes are still a valid and proven way to structure your IT Service offerings.  Maybe there is some added value you could get from investigating v3, but my advice is “if it’s not broken, don’t fix it!”

What v3 can help you do is move from an implementation of individual ITIL® processes to a truly service-centric model.  It gives you the ability to bring transparency to the relationship between IT and the business.

If you are new to ITIL® and looking at implementing processes then v3 gives some very good advice, it is more prescriptive than previous versions and gives you process models, flowcharts and organisational charts to help you model the processes in your organisation.  This is something that was missing in V2 and the most common complaint I heard about ITIL® – “it doesn’t tell us HOW to do it”.

This more detailed guidance can help you speedup ITIL® implementations and make them more cost effective.  You must remember, however, that these templates are just guides, you still need to determine your own business and IT requirements.  If you do not do this, no process design, flowchart or template is going to deliver the desired results.  The old adage still applies – you get out what you put in.

ITIL(R) V3 looks at service management from a lifecycle approach.  The lifecycle approach aims to give an improved and holistic structure to the functions, processes, roles and responsibilities that make up IT Service Management.

The Service Lifecycle has 5 distinct phases.  Each of the new ITIL® volumes describes one of these phases.

  1. Service Strategy
  2. Service Design
  3. Service Transition
  4. Service Operation
  5. Continual Service Improvement

Service Strategy is the hub around which the other phases revolve.  Service Strategy has links to all other phases.  This is where you make your policies and set your objectives.  The other phases are where you implement these strategies.

While Service strategy is the hub, Continual Service Improvement is an all encompassing phase which concentrates on learning from and improving on all the other lifecycle phases. ITIL® V3 still has the familiar processes from V2, these processes may belong in more than one of the lifecycle phases.

The  path of the Service Lifecycle is from Service Strategy to Service Design, to Service Transition and on to Service Operation.  Then we go through the Service improvement phase which puts us back to Service Strategy and so on.

Wednesday, 24 Oct 2007

This is a follow-up post on the subject of Change Plan Templates (the last post is here). I propose that this will be the last in the series, at least for a while, because there are other subjects I'd like to cover.

Recall, we've now create a Change Plan Template (CPT) on the non-IT subject of how to change a wheel, and have created both Stages and Tasks to represent that. You'll have noticed you could populate the editing forms with a lot more data – you can explorer these separately, my aim was to complete the CPT with the minimum amount of fuss and as quickly as possible.

As a reminder, please note that the blog here at isn't product documentation – you'll find all of that distributed with the product – just press F1 within SerioAdmin or SerioClient to access the HowTo guide.

You can see how the CPT looks in the flowchart view in Figure 1.CPT in flowchart view

With the Change Plan we currently have, Serio can follow the Stages we've defined, and can create Tasks for people to perform. The people working on the Tasks can Action them (i.e., resolve them) using the Actions that they would normally. However, it's often much nicer to create just a few Actions that are relevant to the Change Plan Template in hand, and to only present these to Agents.

Example: If you have an Authorisation Task, it is much nicer if the only Actions offered to those performing the authorisation are Accept or Reject.


Figure 1 - CPT in flowchart view

I'm going to make it so that for each Task that is created as part of this Change Plan Template, there are just 3 Actions as follows:


This is how you do it.

1. Login to SerioAdmin, and open a new Change Explorer.

2. Expand 'Change Set-up' and click on 'Change Plan Templates'.

3. Open the 'Wheel Change' CPT for editing by double-clicking.

4. Open Stage 1 for editing, and then edit the first Task which will be 'Deploy Safety Warning Triangle'.

5. Go to the Task Options tab in the Task editor. The first thing we are going to do is create a new Action Category called 'Change std'. To do this, click the new Action Category icon – it's displayed to the right of the Action Category lookup (as a blank sheet of paper). Create the new Action Category as follows:

Name: Change std
Long Name: Standard Change Actions

and when you are ready, save this and close the Action Category editor.

6. Back within the Task editor, select the Action Category you created above into the lookup – this tells Serio 'don't show all Actions, just offer the ones contained within this Category'.

7. At the bottom of the editor you'll see a list of Actions – which is currently blank, as we haven't added any yet to the Action Category. We can do all we need to do here however. Simply right-click in the list, and choose 'Edit Action Categories'. Simply move over the Actions you want into the Action Category, and then save your work. Close the Task editor.

8. For each of the remaining Tasks, repeat Step 6 – simply use the Change std Action Category in the lookup. There is no need to keep re-configuring the Action Category as we've already done that in step 7, so it will take almost no time.

The Change Plan is now ready to go. To use it, log a Change and then click the 'Attach Change Plan' button. Serio will respond by logging a linked Task for you, as directed in the Change Plan Template.

I'll do a short post later about some of the simpler management tools at your disposal. Have fun!

Thursday, 18 Oct 2007

As some of you are aware, we’re currently working hard on a major upgrade to both the Serio Helpdesk and Serio Service Desk lines, which we are planning to release in the next quarter (although a firm release has not been set yet).

Currently the changes list details some 40 amendments, some big, some small.

The ‘big-ticket’ items relate to web access and web functionality.


The first of these is PocketSerio-i. This is a browser-based piece of software that complements our mobile product line by allowing you to:

Manage Incidents and Changes

Manage Items

from a handheld, mobile device. We’ve been quite careful with what we assume that the host browser is capable of (ie, it doesn’t need to be the latest and greatest Internet Explorer version, or even Internet Explorer at all), so it should run on a wide-range of hand-held devices that have an ‘always on’ internet connection.

This product doesn’t replace PocketSerio, it complements it. PocketSerio is still good for users that need a download/work and edit/upload model where no persistent wireless internet connection exists.

PocketSerio-i however is aimed at mobile engineers performing site visits to resolve problems, and those performing on site inventory checks and reconciliations where the engineer has an always-connected device. PocketSerio-i actually been around for some time, but Release 5 will be the first time we've bundled it with the standard distribution.

For the technically minded amongst you, PocketSerio-i is an ASP.NET application that uses SerioServer in the same way as the other Serio applications do (in other words, it's a another client using the same business object layers).

As soon as we've sorted-out a few hosting issues, you'll be able to obtain access to this over the web. Simply contact support, letting them know the exact model designation of the mobile device you are using, and the type of wireless connection you have, and we'll send you the access details once we know them. The system will be connected to a simple database we'll set-up for you.


Although this won't replace SerioClient, at least in Release 5, it will allow customers to log Incidents, Problems and Changes over the web, as well and manage Incidents, Problems and Changes. It will certainly allow you to log new tickets, and to place Actions on them (for instance, so make assignments, send eMails, or record resolutions).

Like I said, the plan is not to replace SerioClient immediately but to offer SerioClient-i as an alternative for off-site working.

There are other enhancements due as well. I'll post about these at a later date. Release 5 will be available to customers with a current (active) support plan.

Tuesday, 16 Oct 2007

This is a follow on from last week’s imaginatively titled post ‘Creating a Change Plan Template Part 3’ – follow the posts backwards to catch up.

Recap: I’m creating a simple 4 Stage Change Plan Template (CPT) on the subject of how to change a wheel. So far, I’ve done all the up-front designing I need to do, I’ve created an empty Change Plan, and into this I’ve placed 4 Stages as per my design.

So far so good. At the moment, we still can’t use this CPT because it does not have any Tasks. As I’ve mentioned previously, Tasks are the things the people actually do, and so a Stage without any Tasks is not much use.

I’ve already written down my Tasks – you’ll find them in Parts 1 and 2. What I’ll do now is add them to the Change Plan Template, which you can do as follows.

1. Login to SerioAdmin, and then open a Change Explorer.

Because we are going to create Tasks, we need to create something called an Issue Template. This is basically a shortcut for an Incident – it contains the Issue Type, Problem Area, Priority and other such data. We'll use it when creating the Task.

2. Expand ‘Change Set-up’ and click ‘Issue Templates’. Open-up a new Issue Template editor, and create an Issue Template as follows:

Name: Generic/Generic Issue Template
Description: (You can leave this blank if you wish).
Enter some non-specific values for Issue Type and Problem Area. Examples might be:
Issue Type: Change
Problem Area: Change Task

Set a medium or moderate Priority, and save your work.

4. Within the Change Explorer, click ‘Change Plan Templates’.

5. Select the ‘Change Wheel’ Template, open the flowchart viewer as I described in my last post, and then double-click the 'Change Wheel' Template to begin editing it. You’ll see the Template details and the Stages all listed in the editor form.

6. Double-click the first Stage, called ‘Location Inspection’. This will allow you to edit that Stage. Notice that at the bottom of the Stage edit form there is a list of Tasks – which is of course empty. Right-click here and click ‘New’ from the pop-up menu to add a new Task.

7. Using the Task form, create a Task as follows.

Task Name: Deploy Safety Warning Triangle
Task No: 1
Description: The safety triangle should be deployed about 50 metres behind the vehicle. If you are on a bend, choose a location that gives good visibility to traffic travelling in your direction (Notice that the description is basically the same as the one I created in Part 1.).
Issue Template: Generic (the one we created earlier in this post).

Save this Task.

8. Close the Task editor down, and you’ll see the Task you’ve just created listed with its Stage. Now repeat the process for the second Task which is called ‘Inspect the location of the Vehicle’.

Task Name: Inspect location of Vehicle
Task No: 2
Description: If you are changing a driver-side wheel, and are close to the flow of traffic, abort the Change. If the vehicle is in the flow of traffic, abort the Change.

Save your work.

9. Close down the Stage editor we have open for Stage ‘Location Inspection’. For each of the remaining 3 Stages, add the Tasks I wrote down in Parts 1 and 2.

The CPT is almost ready to go. The next post will create the Actions we need, and then we can run it.

Friday, 12 Oct 2007

Just as we are getting our heads round the idea of online applications, the wheel, we are told, is turning a full circle and the focus is moving back to the desktop. A number of browser plug ins are bringing applications out of the browser and creating hybrid apps that have been dubbed the new webtops. These include Microsoft’s Silverlight, Google’s Gears and Adobe’s AIR. Crucially though, Adobe takes things a step further with AIR, which can operate entirely independently of the browser. The race is on to develop must-have website applets for the desktop, keeping websites in the user’s face as never before, which is exciting the marketing and media types, and potentially replacing core desktop applications such as word processing with hybrid web/internet applications, which is scaring IT support. But why should the hapless user give up precious desktop space anyway? This confusing state of affairs is best clarified by example. A developer might write a desktop application that links to an online service allowing local storage to be combined with online features such as streaming media. The success of this latest generation of webtops lies as always with the killer app. In a move that could well put pressure on Google’s online apps offer, Adobe bought up the Buzzword online word processor this month as part of its strategy for internet application development. Buzzword was built with Adobe's Flex and runs in Flash, allowing people to collaborate on documents - and work with hosted and local documents. As well as its purchasing muscle, Adobe is using the latest crowdsourcing development methodology, running an AIR developer derby with $100,000 for the winning developer and last week it got together with MTV to launch another big ticket developer competition. Some big names have got in the web-desktop act – Ebay, AOL, The New York stock exchange NASDAQ and Business Objects are reported to have demoed hybrid applications for business and consumers. Applets can be knocked up in AIR by web developers in HTML (JavaScript, CSS, XML) and Adobe Flash (ActionScript, Flex, XML) and can be run on Windows or Mac operating systems, with versions for Linux and mobile devices in the pipeline. A big advantage is that browser specific code can be used to create the independent desktop app too. Downsides are the 10Mb runtime load and the need to install the application. Regular readers may remember mutterings about the security threats posed by desktop gadgets and widgets and there are similar murmurings that webtop hybrids carry the same risk of being a chink in the network armour. That health warning aside though, the results of the AIR developer derby should make interesting viewing. [tags] Adobe AIR, Applets [/tags]

Tuesday, 09 Oct 2007

This is a follow-up to Part 2, posted last week. Recall I’m setting-up a simple 4 Stage Change Plan Template (CPT). The previous posts carry all of the background and set-up info you need.

So far, you’ve created a CPT. However, it isn’t terribly useful at the moment in that it’s just a hollow shell – it has no Stages, and no Tasks. However, as we’ve written these down beforehand it’s a simple case of data entry. Follow these steps carefully to get the rest of the data entered.

1. Login to SerioAdmin, and open a new Change Explorer.

2. Expand ‘Change Set-up’ and click on Change Plan Templates. You’ll see the Change Plan ‘Wheel Change’ we created in Part 2. Make sure this is highlighted, and then right-click on it and choose ‘Show Flowchart’.

This is where having a big, high resolution display comes in handy. Move the Flowchart window over to the side, so that you can still see it and use SerioAdmin at the same time.

3. Right click on ‘Change Wheel’ and then click ‘Amend’.

4. You’ll be presented with the Change Plan Template edit form. Look to the bottom of this, and you’ll see a list of Stages, which is (of course) blank – because we haven’t defined any.  Right-click on this list and select ‘New’.

5. You will now see the ‘New Stage’ form. Create your first Stage as follows.

Name: Location Inspection.
Stage Number: 1 (recall we previously defined this [Stage Number 1] as the starting Stage).
Description: Use the summary I created for this Stage – the one beginning ‘Check that the car is not in a dangerous location…’. This helps you to focus on what this Stage is for.

That’s all we need to enter for now.  Save your work. Notice that the flowchart has updated for you.

6. Now repeat the process, and create Stages for ‘Inspect spare wheel and tools’ and ‘Replace wheel’. When creating these, increment the Stage Number you use, so that Inspect is Stage Number 2 and Replace is Stage Number three.

Example flowchart

7. When you create the final Stage (Safety Inspection) you need to do things in the same way, but before saving click the ‘Stage Start/End’ tab you’ll find on the Stage editing form. We need to tell Serio this is our end point (i.e., this is where the Change ends). Click this tab, and choose the option ‘End the Change Plan’ and then save your work.

The flowchart will now show you how your Stages look within the CPT. It should look something like the flowchart in Figure 1.






Figure 1 - Example Flowchart

Let’s recap what we’ve done. We’ve create a Change Plan Template, and then defined the 4 Stages that comprise this. We’ve entered this into Serio, which is now able to show us a graphical representation of what is involved in Wheel Change (in as much as it knows the correct order of Stages). However, the CPT is not useable right now because there are no actual Tasks for people to perform. What we have now however is a framework into which those Tasks can be added.

I’ll move onto Tasks and Actions in the next post.

Thursday, 04 Oct 2007

Part 1 (Server Core and Windows Server Virtualization)

Whilst the first two posts that I wrote for this blog were quite generic, discussing such items as web site security for banks and digital rights management, this time I'm going to take a look at the technology itself – including some of the stuff that excites me right now with Microsoft’s Windows Server System.

Many readers will be familiar with Windows XP or Windows Vista on their desktop but may not be aware that Windows Server operating systems also have a sizable chunk of the small and medium size server market.   This market is set to expand as more enterprises implement virtualisation technologies (running many small servers on one larger system, which may run Windows Server, Linux, or something more specialist like VMware ESX Server).

Like XP and Vista, Windows 2000 Server and Advanced Server (both now defunct), Windows Server 2003 (and R2) and soon Windows Server 2008 have their roots in Windows NT (which itself has a lot in common with LAN Manager).  This is both a blessing and a curse as while the technology has been around for a few years now and is (by and large) rock solid, the need to retain backwards compatibility can also mean that new products struggle to balance security and reliability with legacy code.

Microsoft is often criticised for a perceived lack of system stability in Windows but it’s my experience that a well-managed Windows Server is a solid and reliable platform for business applications.  The key is to treat a Windows Server computer as if it were the corporate mainframe rather than adopting a   personal computer mentality for administration.  This means strict policies controlling the application of software updates and application installation as well as consideration as to which services are really required.

It’s this last point that is most crucial.  By not installing all of the available Windows components and by turning off non-essential services, it's possible to reduce the attack surface for any would-be hacker.  A reduced attack surface not only means less chance of falling foul of an exploit but it also means less patches to deploy.  It's with this in mind that Microsoft produced Windows Server Core - an installation option for the forthcoming Windows Server 2008 product (formerly codenamed Longhorn Server).

As the name suggests, Windows Server Core is a version of Windows with just the core operating system components and a selection of server roles available for installation (e.g. Active Directory domain controller, DHCP server, DNS server, web server, etc.).  Server Core doesn’t have a GUI as such and is entirely managed from a command prompt (or remotely using standard Windows management tools).  Even though some graphical utilities can be launched (like Notepad), there is no Start Menu, no Windows Explorer, no web browser and, crucially, a much smaller system footprint.  The idea is that core infrastructure and application servers can be run on a server core computer, either in branch office locations or within the corporate data centre and managed remotely.  And, because of the reduced footprint, system software updates should be less frequent, resulting in improved server uptime (as well as a lower risk of attack by a would-be hacker).

If Server Core is not exciting enough, then Windows Server Virtualization should be.  I mentioned virtualisation earlier and it has certainly become a hot topic this year.  For a while now, the market leader (at least in the enterprise space) has been VMware (and, as Tracey Caldwell noted a few weeks ago, VMware shares have been hot property), with their Player, Workstation, Server and ESX Server products.  Microsoft, Citrix (XenSource) and a number of smaller companies have provided some competition but Microsoft will up the ante with Windows Server Virtualization, which is expected to ship within 180 days of Windows Server 2008.  No longer running as a guest on a host operating system (as the current Microsoft Virtual Server 2005 R2 and VMware Server products do), Windows Server Virtualization will directly compete with VMware ESX Server in the enterprise space, with a totally new architecture including a thin “hypervisor” layer facilitating direct access to virtualisation technology-enabled hardware and allowing near-native performance for many virtual machines on a single physical server.  Whilst Microsoft is targeting the server market with this product (they do not plan to include the features that would be required for a virtual desktop infrastructure, such as USB device support and sound capabilities) it will finally establish Microsoft as a serious player in the virtualisation space (even as the market leader within a couple of years).  Furthermore, Windows Server Virtualization will be available as a supported role on Windows Server Core; allowing for virtual machines to be run on an extremely reliable and secure platform.  From a management perspective there will be a new System Center product – Virtual Machine Manager, allowing for management of virtual machines across a number of Windows servers, including quick migration, templated VM deployment and conversion from physical and other virtual machine formats.

Windows Server Core and Windows Server Virtualization are just two of the major improvements in Windows Server 2008.  Over the coming weeks, I’ll be writing about some of the other new features that can be expected with this major new release.

Windows Server 2008 will be launched on 27 February 2008.  It seems unlikely that it will be available for purchase in stores at that time; however corporate users with volume license agreements should have access to the final code by then.  In the meantime, it's worth checking out Microsoft's Windows Server 2008 website and the Windows Server UK User Group.

Tuesday, 02 Oct 2007

This is a follow on from Thursday's post about Change Plan Templates.

In this post, I’m going to continue my definition of the roadside wheel change. See Thursday’s post for more info and background. My last post got halfway through defining my Tasks, so before moving on I’ll finish this by refining Stages Replace Wheel and Safety Inspection.

Stage: Replace Wheel. Tasks: (1)

(Recall I said to avoid micro management. So I’m going to assume that the person replacing the wheel knows how to use a jack and a spanner. What I will do is put a few things that can go wrong).

1. Change Wheel. Wear the high-visibility vest and latex gloves. Using the Jack from the tool kit, remove the old wheel and replace with the new. Hub caps (if fitted) should be stored in the boot and not used on the spare wheel. Inflate the replacement tyre to 36PSI.

Stage: Safety Inspection. Tasks: (1)

(Another opportunity for checklists)

[ ] Re-check tyre pressure is at 36PSI.
[ ] Recover all tools from the work area. You should account for the old wheel, hub cap (if fitted), jack, 17mm spanner.
[ ] Recover the safety triangle.
[ ] Place warning note or sticker on the dashboard that the maximum vehicle speed should not exceed 60 MPH.

What we have then are 4 Stages, and 5 Tasks in our simple exercise. You could have set-up a single Stage (‘Change Wheel’) composed of 5 Tasks to achieve the same thing but I’ve used Stages in this way to communicate the most important steps involved. My Change is linear in that it does not have any branching – I’ve done this to make it as simple as possible. It also involves a single person, and does not co-ordinate teams or individuals. However, it will serve to illustrate the understanding of the problem domain you need to have before getting started, and will illustrate the basic use of the tool.

As always, please remember that this blog is NOT the product documentation – it’s designed to complement the product documentation, not replace it. The product documentation is distributed with the software, and you’ll find it in the HowTo guide.

Creating the Change Plan Template

I’m going to assume you know how to use SerioAdmin to create, amend and delete records.

1. Login to SerioAdmin on your test system.

2. Open a new Change Explorer.

3. Expand Change Set-up, click on Change Plan Categories and create a Change Plan Category called ‘Examples’.

4. Now click on Change Plan Templates. Create a new Change Plan Template as follows.

Name: ‘Wheel Change’
Category: ‘Examples’, as you created in 3.
Description: Use the definition of the Change I created in the last post (‘The safe and speedy replacement…’)
Start the Change with this Stage Number: Use the number 1 (this will be the Stage number we begin with).

Save when you are ready. You will now see that you can go and define Stages, which I’ll do in later posts