BPM Definations and Overview
A Big overview of BPM: One page Executive summary by Oracle
So what definitions do you need to build an architecture?
The rules for mapping your organization into the BPM space
Criteria must be in place to translate the real organization into BPM, which includes defining the following things:
Patterns for organizational units
Patterns for organizational roles
Patterns for groups
Assignment of participants to OUs
Assignment of participants in groups
Assignment of organizational roles to participants and groups
The infrastructure components
The distribution of applications and services and the way they communicate is a critical part of the architecture. Actually, this is the technical architecture of the solution. Here is a basic list of applications you need to include and the type of configuration needed.
BPM Enterprise Servers
Type (Standalone, WebLogic)
Configuration (Clustering, Location)
Database configuration
HiPer Workspace for BPM
Configuration (Clustering, Location)
Other modules
Business process dependencies
The process deployment topology
Business processes have to be inserted in the infrastructure and the organization: This is the deployment topology. The topology has a direct impact on the infrastructure and on the way people use the processes. The definitions are simple, but they need to be carefully defined based on the organization and the infrastructure.
The mapping to the organization
The OUs that the process will be deployed
The mapping of process roles to organization roles
The mapping to the infrastructure
The enterprise server that will execute the processes
The external resources required by the processes
