Post has attachment
Hi all,

If you haven't had a chance to check out the programme for this year's virtual conference you may not have seen the fantastic topics we have planned - Agile for ITSM, Risk management, BRM and Customer Experience to name a few.

Speakers this year include Jeff Rumburg of MetricNet, Mark Smalley, Julie Mohr, Karen Ferris, Suresh GP and Dr. Mauricio Corona.

Take a look!

p.s. If you register you also get access to the recordings so you don't miss anything even if you can't join live.

Post has shared content
Almost 36% of respondents use public cloud for production workloads, according to a poll at ISACA’s EuroCACS conference in Copenhagen. ISACA Immediate Past International President Robert Stroud discusses the cloud adoption trend in his latest Forrester blog post

Post has attachment

Post has attachment
The steering committee met yesterday. We have reached a point where the meta-model has developed as far as makes sense, purely theoretically. Here:

and in more detail:

We now need to decide where to take it from here.

We all have ideas, but, we realised, we need to know, and agree, what our collective understanding is of where we want to end up.

In other words, we need understand our vision for the future.

Please help, by contributing to this discussion - What should the vision statement of TSF be for the Adaptive Service Model?

The main discussion is here:

Post has attachment
Version 0.15 of the Adaptive Service Model has been released

Based on the discussion on 'Resources' and 'Capabilities' on LinkedIn a request for change ("Johann Botha 2022015 RFC") was proposed and recently accepted. That has led to the release of an updated version of the model.

In summary all the enablers for service are now considered resources, while capability is defined as a characteristic or an attribute of the configuration of these resources, i.e. a characteristic of the Service System. As a side benefit that simplifies the model quite a lot.

By this change we leave the definition of resources and capabilities introduced with ITIL V3 and align with the more common definition of resources and capabilities used by most business schools etc. 

To give an example: A taxi company (a service system) may have different resources such as cars, drivers, IT and communication systems, processes, skills knowledge etc. Dependent on the dynamic configuration and use of these resources the company may have a capability to offer traditional taxi service and another capability to offer a limo service. The traveller (service system) on the other side may have different resources such as a body, skills, knowledge and money. Dependent on the dynamic configuration and use of these resources the traveller (service system) may have a capability to consume a taxi service and another capability to consume a plane service with the same service system but not a capability to consume a train service (e.g. disabled) or a limo service (e.g. limited money).

For those of you that have signed up for the wiki the detailed description of the proposal can be found here:

The new definitive version of ASM can be found in our definitive library ( It consists of:

- The updated block diagram (

- The updated diagram ( In ARCHI format:

- The updated description of objects and attributes (   

We still hope to complete the meta model layer soon by settle the discussions on the concepts of process, service act and governance. So stay tuned - we will soon be back! 

I don't think this is going to work. It's easy enough to delete the community, but copying the discussions out seems impossible - or very difficult. 

If anybody else can find a means of extracting them, then we could try this.

Discussion thread for the ways of working being discussed by the gang of three.

This is just a test group for establishing what is possible with google+ - please ignore, it's work in progress.

Here's a new post from me in this thread.

Here is a new post??

Post has attachment
We are currently facilitating three discussions on LinkedIn (  with regards to key objects in the ASM meta model:

- Resources and capabilities
- Processes
- Governance and service eco-system

One more discussion on Service Dynamics (service co-creation) will soon be launched.

In addition we have started the first discussion on the next layer, the detailed model:
- What instances of Service Systems shall ASM include

Please feel free to contribute
Wait while more posts are being loaded