Profile picture for user rob davis

You have purchased ARIS (or downloaded ARIS Express) and you are all keen to get modelling – but wait – as with any project it is important to think about your aims and objectives before you start.

You may think strange that someone from IDS Scheer tells you hold back from modelling, after all modelling is fun – well I think it is, but then I have written three books about it! Seriously, one of the biggest issues that I come across when working with customers is that they start producing models without any thought to what they are going to be used for, who is going to use them and how they will be kept up-to-date. Of course creating an enterprise process portal is an excellent way to start BPM , and process transparency is one of the main benefits of modelling, but you can’t just assume that everyone in the business is going to flock to your website and passionately read all your models.

There are two pieces of advice I would urge you to think about before you start:

  • Consider your customers
  • Ask the “6 W’s” – Why, Who, What, When, Where, and HoW

Of course this is nothing new. In any big project, it is normal to identify your customers, deliverables and create a project plan. However, for some reason, when people start modelling they tend to forget all of this good practice.

A process model is just that, “a model”, it is not the real thing but a representation of it. Just like any other sort of model, the representation is created for specific purpose with a specific scale, with a certain detail and with a certain view point. The model can be used for many purposes, but it will only make sense if the detail, scale and viewpoint match that purpose. So before you start modelling it is vital to identify what it will be used for.

Firstly, think about the ‘customers’ for your model – the people who will use it. Ask yourself:

  • Are there different users?
  • What is the scope of the model they are interested in?
  • What detail do they want to see?
  • What will they use it for (e.g. training, IT development, business improvement)
  • Do they actually want to see the models or results derived from them?

The answers to these questions will start to define detail, scale (scope) and viewpoint.

Also think about the ‘real’ end customers of your business or organisation. How is your modelling going to benefit them?

  • Will it improve their experience of your business?
  • Will it get new products to them faster?
  • Will it lower prices?

If you can see any benefit to your end customers then you might want to think again about why you are doing it. You can then further refine these answers by asking the “6 W’s”:

Why are you modelling?

  • Document operational processes
  • Capture information for business improvement project
  • Support business restructuring
  • Provide requirements for IT development
  • Enable a new product launch

Who are the customers for the models?

  • Business users
  • Business Architects
  • Process professionals
  • Process users
  • IT designers

What are you modelling?

  • The whole enterprise
  • An end-to-end process
  • A department’s processes
  • The processes involved in an improvement activity
  • A process that is going to be automated

When are you modelling?

  • “As-is” – if so, is it what people tell you happens, or what really happens
  • “To-be” – if so, exactly when and what assumptions is this built on
  • Is this a one-off exercise or do they need to be maintained?

Where will the models be used?

  • Published on the Intranet
  • To generate documentation
  • To define interfaces with suppliers
  • Directly enacted (e.g. SAP Blueprints or Workflow)
  • As IT development requirements

How will you model?

  • Using ARIS (which tools and which models and objects?)
  • Using modelling standards
  • Notations (BPMN, UML)
  • Following corporate guidelines (have you created them)?
  • Do the models link into an enterprise process map or framework?
  • Using process frameworks (e.g. ETOM, SCOR, etc)
  • Reusing business and IT services
  •  

Once you have answered these questions you will be in a much better position to start your modelling with a clear idea of what you need to achieve. It also will provide a very useful input to an ARIS Methods and Standards Workshop that will define the models, objects, relationships and attributes you will need. Again, many customers try to define these without a clear idea of what they are going to do with the models.

Also remember: Processes are not just for fun – they must:

  • Deliver a product or service to someone outside of the process
  • Provide some value to that person or organisation
  • Add value to the organisation operating the process (or fulfil a necessary function)
  • Align with, or fulfil, a business objective

So there are many things to think about before you put pen to paper (or mouse to ARIS!). I hope this has given you some useful guidelines.

If you would like to learn more about preparing to model, please have a look at our free ARIS Community Online Academy training course

“Lesson 2: "Before you start modelling"

 

**If you are an ARIS User within the UK and Ireland why not join our ARIS UK and Ireland Community. As a member you have direct access to the latest developments of Business Process Management (BPM) related topics. It offers a platform for information exchange and enables shared discussions with other UK & Ireland based Business Process Professionals.  Please email Ms. Joanne Richesif you want to join this group!**

by Konstantin Ivanov
Posted on Tue, 06/22/2010 - 12:56

Rob, basic but great guidelines!



All what you said applies not only to processes, but to modelling of any part of the reality, either its core business or supporting part.

As per IEEE 1471-2007, you need first understand who are the stakeholders, what concerns they have, what kind of viewpoints can address these concerns, then define the underlaying metamodel and ONLY THEN start creating architecture descriptions in form of models and views.

One small addition to the content of the post - besides the shorter time-to-market and cost optimization, risk management and compliance could be a driver for transparency in processes etc too.

/Konstantin

0
by Ismael Shameem Etowar
Posted on Tue, 06/22/2010 - 18:13

Dear M. Davis,

 

Many thanks for this post.

Really interesting indeed.

 

Cheers

 

Shameem

0
by Marcus Jennings
Posted on Wed, 06/23/2010 - 15:21

The 6 W's should be a mantra throughout a modeling exercise or project and not just at the start. It's too easy to follow related process paths or expose excessive levels of detail that lead away from the original objectives of the customer, because as modellers we often want to model everything.

 

0
by Jagdish Mohite
Posted on Wed, 07/28/2010 - 12:24

Dear M.Devis

Very good Information on before starting modeling, Can people outside UK & Ireland  join your group ?  if not why?

Regards

Jagdish

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock