Business Process Modeling (BPM(N))
Business Process Modelling Notation, some might claim that it sits before the UML in the analysis process, some might claim not to use it. It does not matter.
We have used the UML notation to document processes exactly the same the BPM notation allows us to do.
The end of the day the graphics are there for guidance, describing the processes is "separating the COW from the BOYS".
Describing the business processes either in UML or BPMN is a skill that only comes from experience. Henk Harms has over 10 years of hands on modeling experience, using a several different notations, frameworks and case tools.
What have we done?
We used BPM(N) for modeling pretty much since the "beginning of time", using the UML notation initially for modeling, and since 2004 we use the BPM notation for our modeling.
We prefer the BPM notation but do not shy away from using UML notation to represent the business processes, it depends on what the direction is.
We have successfully used, introduced and implemented BPM in the following organisations:
- Optus (SingTel)
- Hewlett Packard
- Flight Centre
- Queensland Health
- National E-Health Transition Agency
- Smart Services Queensland
- Main Roads
- ENERGEX
- Santos
BPMN on its own does not work, support from management and a solid enterprise architecture is needed to succeed. The majority of BPMN projects fail due to the lack of it. We use BPMN in combination with business architecture, we build the metamodels that suit your organisation.
From the metamodel, all the way down to the individual documentation that is what we stand for. We provide a framework, the on the job BPMN training and BPMN mentoring.
We like to introduce a case tool to your organisation like visual paradigm, but it is not necessary, over the years we compared different tools in different situations we have found that visual paradigm has a quicker uptake. The support team is very responsive and are willing to introduce new items.
Some examples of our modeling work.
-- BPMN is a notation, it is not a methodology; the notation is there, to support understanding, it is not there, to enforce the audience to understand. (Henk) --