Proceedit dyPAS creates automatically standard and dynamically customizable BPM Process solutions allowing them to act glocally serving all type of organizations with a single fixed BPM Process Class

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. 

 

The dyPAS (dynamic Process Application Server) developed by Proceedit is being recognized as the best Methodology & Technology for BPM Process Standardization

With the traditional IT approach (tailor made projects for each customer) and the usual way to use BPMS technologies by BPM technologists (almost all the configuration of the process class, personal tasks forms, data model, business rules, automatic tasks, … is made on the platform), the effort for massive BPM adoption and the technological complexity generated (see next figure) by hundreds of Process Class that are required to deploy and maintain is simply not possible to afford by mid and small size organizations.

proceedit considers that the clue to overcome these tremendous barriers of effort and complexity goes through a drastic change of paradigm in the BPM Industry. Indeed, We stand for applying the new value chain Co-development > Standardization > Reutilization > Low Cost that is, in our opinion, the only way to achieve a massive, affordable and sustainable BPM Process adoption, especially when we are talking about the mid/low-end market.

After 4 years of intensive development, piloting and testing efforts, proceedit announces the availability of the first full operative version (already in operation) of its methodological and technological platform dyPAS (dynamic Process Application Server) that, combined with any of the BPMS platforms available in the market today, provides an easy to use and maintain, flexible, robust and resilient engine for BPM Process Classes standardization.

The dyPAS outcome is to manage in a fast, flexible and efficient way the definition, refinement and evolutionary change of the forms, views, data models, and workflows trough the usage of dynamic parameters & business rules associated with the automation of business processes. 

Using our dyPAS technology for BPM Process Classes development, we apply several methodological rules:

•  Only one Process Class for each business process type,
• Only one Form Class for each Process Class,
• Real time dynamically generated Views of the Process Form Class customized on the fly at the instance level depending on: Process Task Class, Customer, User and Device requesting the form, and other contextual variables, parameters and business rules,
• Unified Process Data Model (Business Ontology) for all Process Classes
• Continuous unique version of each Process Class serving all customers but customized on real time, 
•  ... and till nearly 40 standardization rules.

And this all managed from a single centralized system which handles the real-time behavior of all the forms and workflows of all automated processes in one or more organizations, both in terms of:

• What information to display and how to manage it,
• The Process Forms Views behavioral characteristics in front of the User depending on: the Process Task, the Client, the User and the Device from which the user accesses the system, and
• The behavior of the workflow in each use case, depending on the real time business rules constructed and served on the fly, according to the present business scenario.

The above behavior is sustained in the architecture showed in the figure here below, being the main applied concept the separation in different areas and supporting platforms (BPMS and dyPAS respectively) what refers to Workflow management and what refers to the Data, Forms and Rules management.