(Kirchmer, 2011). In many cases they are already
developed using standard modelling methods. The
industry common practices reflected in those models
are only adjusted to the specific organization when
this is absolutely necessary. The process design
work focusses on “making the industry standard
happen”. If process areas are identified where the
industry standard cannot be applied, e.g. due to
product specifics, only those areas will be designed
in a company specific way, keeping the adjustments
as close to the industry standard as possible. Process
solutions can here often be found through a simple
application of the mentioned traditional
improvement methods like Lean and Six Sigma
since a pure efficiency focus is in most cases
justified here. However, it is important to keep in
mind that it is in general not worth improving above
industry standard performance.
This value-driven process design approach is
visualized in figure 5. It shows that also for the
design of high impact processes reference models
can be used as an input. But this is only one
component of getting all information together to
come up with real innovative and optimized
solutions.
Figure 5: Value-driven process design approach.
In both cases process models are developed until
the level of detail that still provides relevant
business information through the design. The
decomposition of the function “Enter Customer
Order” into “Enter First Name”, “Enter Last Name”,
etc. would from a business point of view not add any
additional relevant content (but may be necessary
later for the development of software). When
reference models are used this can mean that in areas
where the design deviates from the initial industry
model a higher level of modelling detail is required
then in other “standard” areas.
Both, high impact and commodity processes are
part of overlying end-to-end business processes.
Process-interfaces in the underlying detailed
processes reflect this overall context and make sure
that the various process components or sub-
processes fit together. Hence, during the process
improvement work cause-and-effect considerations
have to take place in order to avoid fixing issues in
one area while creating new ones in other processes.
5 VALUE-DRIVEN
IMPLEMENTATION
The very organization specific process models for
high impact business processes are in general
implemented using highly flexible next generation
process automation engines and require in most
cases the development of application software
components. The process models reflecting the
optimized and innovative design are the entrance
point for the more detailed modelling of the
underlying software. At this point the modelling
method can change, for example to the Unified
Modelling Language (UML), reflecting the desired
software structure to support the high impact
processes. Also the workflow engine of next
generation process automation engines can be
configured based on those models, depending on the
underlying modelling and execution technology
even automatically or semi-automatically. The
integration between process modelling and
execution tools can be extremely beneficial in this
situation.
The overall architecture of such next generation
process automation environments is often referred to
as Service Oriented Architecture (SOA). In such an
architecture the “execution software” and the
“process logic” (workflow) are separated (Kirchmer,
2011) (Slama, Nelius, 2011). Hence, the developed
process models can on one hand be sued to
configure the workflow and on the other hand to
develop the software services that are not available
in existing libraries. Existing software services may
include detailed process reference models that can
be included in the process design. This architecture
of next generation process automation environments
is visualized in figure 6.
Key advantage of such an architecture is the high
degree of flexibility in adjusting process flows and
functionality. This can be crucial for a company
looking for agility and adaptability. Main
disadvantage is the effort for providing the
appropriate governance while running such an
environment as well as modelling efforts in the
building phase.
Fourth International Symposium on Business Modeling and Software Design
300