The arguments for standardization
of common processes are compelling: all the process actors have a consistent
interface; huge economies of scale in IT analysis, development and Integration
are obtained; operation, monitoring, tracing, audit and document control are homogenous
and then even outsourceable; process improvement, change management, training, performance
measurement and quality assurance are improved with much less effort.
Are these benefits
enough to sacrifice local variations that respond to local needs and then
having to decide between the global-local dilemma? Answer yourself, this is not
an easy decision, indeed.
The arguments for serving
the specific users requirements and then allowing and managing local and
personal variations in standard processes are, not only persuasive, but a key
factor of success for the massive adoption of BPM by eliminating one of the main barriers customers have against
standardized solutions, not only to BPM
ones:
“We are especial, we do the things in a very different
way than our competitors and therefore, we want to work as we have decided to
do. We are so especial that is not possible that a standard solution can
be adapted to our needs. We don’t want to be obliged to adapt our operations to
standard predefined working procedures because acting in such a way we will surely
lose our competitive advantage”.
By chance, have you
heard these words or similar ones before? Frankly speaking, do you really thing
this is true? The same reticence applied to ERPs
for years and finally standard solutions have clearly dominated this market.
dyPAS (dynamic
Process Application Server) developed by proceedit solves the
standard-custom contest by giving a consistent solution to BPM Process Classes standardization,
without renouncing to serve the strong customization requirements that users
are demanding and then resolving this dilemma in an efficient, robust,
flexible, affordable and sustainable way.
BPM Process Classes created with and served by dyPAS look in the front office (when acting with persons, applications,
machines, sensors and actuators) like a tailor made process solution but being,
in fact, 100 % standardized BPM Process Classes from
the back office point of view both in development, operation and maintenance
phases.
In the way we
represent in the next figure, this original proceedit approach allows that
each single Process Class works in a
“Glocal” modality being at the same
time standard but custom adaptable to the specific requirements of all
customers, independently of its size, sector and localization of the
organization using the BPM Process Class.
Moreover, this
approach works not only with horizontal common processes but also for the
vertical specialized ones and for not only a fixed pre-established behavior but
also performing dynamically real time adaptable reactions to the varying
context situation without hard changes in the BPM Process Class.
Finally yet
importantly, development, customization and real time dynamic operation is done
without any programming job at all! In other words, dyPAS technology follows an strict “0” code
approach, in which, first by simply declare the solution to our engine to
automatically create the BPM Process Class Form Server and then this is
customized on the fly using different parameters, business rules and context
variables describing the specific behavior of the BPM Process Class for each Process Task, Customer, User and Device
connecting to the BPM solution.
No comments:
Post a Comment