09 Ponencia: Arquitectura BPaaS y dyPAS como tecnología esencial para la estandarización > reutiliza

Cloud BPM Discovery Seminar - dyPAS the key for Process Standardization & Customization on the fly

V 01 P 1

proceeditCloud BPM Discovery

Seminar - dyPAS the key for Process Standardization & Customization on the fly


V 01 P 2

Standardization in BPM, the Critical Echelon

Co-Development

Reutilization

Low Cost

Affordableand SustainableBPM Deployment

> Massive

Standardization

?

!

Task 1 of Task Class Instance

BPMS Platform

Form Task 1

Task 1 of Task Class Instance

BPM Process Class

A


V 01 P 3

Traditional Model for BPM Process Classes Development

Process ClassData Model

Form Task n

1Tailor made development for each Process Class

4 20

Very high and growingComplexity!

At the end, hundreds or thousands isles of information


V 01 P 4

BPMS-dyPAS Standard-Custom Frontend-Backend

Standard-Custom

BPM Process Class

BPMS<>dyPAS

Real-time dynamic Changes on Parameters,

Business Rules & Context Variables

Customizedby defect

Parameters & Business Rules

Data Base

Administrators

Supporters

Developers

Supervisors

Auditors

Users

Backend Frontend

Standard Customlike “tailor made”

IBM ODMIBM BPM


V 01 P 5

Arquitectura Tecnológica BPaaS

Worklight

Procesos BPM

Data Cap

BPM dyPAS ODM

Documentos

FileNet

Proceso

DB2Datos

InformixReglas

DB2

Process Data Model (ERP)

BPMS Platform a

Process Class X Form

BPM Process Class X


V 01 P 6

proceedit’s BPM Process Standardization Architecture

dyPASDynamic Universal

Process App Server

BRMSRules & Paramfor Real Time Custom FormServing dynamic

views per Task 1from the Process

Class X Form

Serving dynamic views per Task …from the Process

Class X Form

Unified Process Data

Model

BAM Platform a

WorkFlow Area Data & Forms Area

Task … of the Process Class X Instance

Task 1 of the Process Class X Instance

Serving dynamic views per Task nfrom the Process

Class X Form

Task n of the Process Class X Instance

One single Process Class Form serving custom Views for each Process Class Personal Task

Custom Views, created ad hoc, dynamically & on real time, at the execution level, for each Process Personal Task, Customer, User and Device


V 01 P 7

Integration Mechanism dyPAS<>BPMS Platforms

BPMS Platform a

BPMS Platform c

Unified Task Inbox

Task 2

Task …

Task n

BPMS Task Form

BPMS Task Header

Task 1

iFrame

dyPASDynamic Process

Application Server

BRMSRules & Paramfor Real Time Custom Form

Task View of the Process Form

BPMS Platform b

1

2 6

4

5

7

8

Requests the Process Task

Sends Process Form View Parameters

Launches the Process Task

Provides RTParameters & Business Rules

Provides Data Model and Repository

Serves the Process Task Form View

3

9

Serves the Process Task

10

Interacts with Process Task Form View

Interacts with Process Data

Closes the Task & Sends Process

Data & Rules

Unified Process Data

Model


V 01 P 8

proceedit Standardization “Dogma”

1. Only one Process Class for each Process type.

2. Only one Form Class for each Process Class.

3. Real time dynamically generated views of the Form

Process Class customized on the fly at the instance

level depending on: Process Task Class, Customer,

User and Device requesting the form.

4. Own developed Forms & Data Model Generator, the

dynamic Universal Process Application Server

(dyPAS).

5. Unified Process Data Model for all Process Classes.

6. Continuous unique version of each Process Class

serving all customers.

7. … till nearly 40 standardization rules.

Application Forms

Declaration


V 01 P 9

BPM Process Building, Testing & Refining Procedure

Application Data Model Generator

Process Form ViewsGenerator on the fly

Parameters & Rules DB

Testing Process

Application & WorkFlow

Assign Parameters

& Rules

Process Application & WorkFlowOperation

Application Data Model

DB

Configure WorkFlow

Building Process

WorkFlow

Process Data Model DB

Refining Process

Application

Refining of Process

WorkFlow

Evolution of Process

Application

Evolution of Process

WorkFlow

ProcessApplicationDesigner

Process WorkFlowDesigner

Operational SupportTeam

Process Data Model Generation

BPMS

dyPAS

dyPAS

Engine 1

Engine 2


V 01 P 10

8 dyPAS main Advantages in Process Class Full Life Cycle

1. Full customization. 100 % adaptability to client/user/device

requirements > increases usability > increase adoption success.

2. Effortless. Reduces drastically (to 1/10) the development and

maintenance efforts > lower time to market > lower costs.

3. Increases agility. Proportions agility and flexibility in development,

operation, maintenance and eventual BPMS migration phases.

4. Allows reusability. Permits reuse of the same BPM Process Classes for

all customers > multitenant solutions > usage cost reduction.

5. Less complexity. Reduces to 1/10 system complexity in terms of data

models and forms to support.

6. Lower administration. Reduces deployment and administration

efforts by applying the continuous single version concept.

7. Real-time adaptability. Allows instant changes on the fly at Process

Instance and/or at Process Class level.

8. Easy migration. Reduces development effort on BPMS platform to less

than 20 % > Facilitates BPMS platform migration > reduces risk of

which BPMS vendor decision and further dependency.


V 01 P 11

dyPAS Reduces Complexity by Standardization

Unified EnterpriseData Model

200 Processes x 10Forms/Process =

2.000 Forms

200 Processes x 1Forms/Process =

200 Forms

200 Processes x 1Data Model/Process = 200 Data Models

Only 1 Data Model for 200 Processes

Tailor Made Development dyPAS by proceedit


V 01 P 12

BPMS Platforms Future > The Big BPMS Migration Journey

400+ Vendors

No + than 80Vendors

• Difficult election

• Fair to be wrong

• Delay in decisions

• Delay on obtaining

profits and benefits

• 8 over 10 software vendors will disappear

• Huge migration efforts will be required

Today In 5 Years from now

The Big BPMS Migration Journey


V 01 P 13

dyPAS Standardization > Easy Migration

Typical Average Efforts Distribution in

BPM Process Development using dyPAS

20 %

40 % 40 %Forms, Rules &

Data Model

SOAConnectors

Process Flow

80 % of the development effortis not depending

on the BPMSPlatform

Only 20 %of the effort

depends on the BPMS Platform


V 01 P 14

What dyPAS Standardization is Proportioning?

Frontend as if were tailor made > Usability, full

customization and comfort.

Backend standard & parameterized > Easy hot

customization on-line, at the instance level,

deployment and reusability.

Unique version for all Clients & Users > Robust,

low cost, agile/easy maintenance and

sustainable solutions.

Governed by external business rules > Dynamic

behaviour of form fields & workflow logic gates

Only 20 % of the effort in BPMS > Easy

migration when/if necessary.


V 01 P 15

Cause-effect Diagram dyPAS > BPM Deployment

dyPAS

100 % CustomReutilization

Low CostAffordable

& Sustainable

Standardization

BPM Process massiveadoption

1

5

4

3

2

6


V 01 P 16

Questions?

Questions?


V 01 P 17

Contact Information

Juan Carlos Guallart, proceedit

Product Development Director

[email protected]

+34 676 951 488

Josep Cos, proceedit

Managing Director

[email protected]

+34 660 193 163

mailto:[email protected]

mailto:[email protected]


V 01 P 18

Gratitude

Thanks for

your Attention!


V 01 P 19

Target

Our dynamic Process Application Server (dyPAS) fits into the

category of BFRMS (Business Forms & Rules Management

Systems) since its objective is to manage in a fast, flexible and

efficient way the definition, refinement and evolutionary change

of the forms, data models and workflows trough the usage of

dynamic parameters & business rules associated with the

automation of business processes.

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: 1) what information to display and how to manage it,

2) the forms behavioral characteristics in front of the user

depending on the task to manage the process, the client, the

user and the device from which the user accesses the system

and 3) the behavior of the workflow in each case, depending on

the real time business rules constructed and served on the fly

according to the present business scenario.


V 01 P 20

Distinctive & Disruptive Functionalities

1. “0” code Forms and Data Model generation.

2. Two generation modalities:

Substitution: for development and testing phases.

Addition: for corrective and evolutionary maintenance phases.

3. Separation of Workflow definition (made on the BPMS platform) from

Application (Forms and Data Model) definition (made on the dyPAS).

4. Sophisticated field types: conditional fields, groups and divisions; multi-

field searcher, nested grids, action buttons, and alarm lights and

document access buttons in grid fields, …

5. Forms Views for each Process Task Instance created on the fly.

6. Behavior of the form fields and divisions or each Form View are

determined on the fly according to external parameters, context

variables and business rules depending on the Process Task Class,

Customer, User and Device requesting the View.

7. Behavior of next Deviation Gate transmitted on the fly from external

business rules > dynamic process flow configuration depending again

on the context.


V 01 P 21

Distinctive & Disruptive Functionalities

9. Multilanguage labels and textual fields contents.

10.Multitenant: same application for all customers, different parameters,

business rules and data & documents for each customer.

11.Everything depending on Customer and User is external to the process

model definition as managers of business rules do.

12.Rules are managed externally and dynamically (on the fly) with a T-rule

engine.

13.Process diagrams are fully prepared to perform all tasks (full available,

all path are possible) but performed dynamically according to the

business rules which the client has contracted and selected to be

executed at any time depending on the context.

14.The dyPAS is not only suitable for BPM on the BPMN approach but also

and specially for the Case Management approach, since Forms and

Workflows should be still more flexible and variable in this late scenario

according to the options selected by initiating event activities.

15.Installable on any DB: MS SQL, Oracle, DB2, MongoDB, Informix, ...

Documents

09 Ponencia: Arquitectura BPaaS y dyPAS como tecnología esencial para la estandarización > reutiliza