Session 4 & 5

13

Click here to load reader

description

ERP

Transcript of Session 4 & 5

Page 1: Session 4 & 5

Session 4Session 4Business Process ManagementBusiness Process Management

OVERVIEW• Introduction & Meaning to BPM• Objectives & Scope of BPM• Challenges of Enterprise Modeling• Integrated Modeling Environment• Multi-layered system Architecture• ModelMosiac• ModelMosiac Architecture

Page 2: Session 4 & 5

Introduction & Meaning to BPMIntroduction & Meaning to BPM

A business process is an aggregation of operations performed by people and software systems containing the information used in the process, along with the applicable business rules. 

Page 3: Session 4 & 5

BPM as an orchestra conductorBPM as an orchestra conductor

A Conductor

Orchestrates people who use their voices and instruments to produce notes in a particular order

BPM as a Conductor

Orchestrates people who use systems and applications to perform tasks in a particular order

Page 4: Session 4 & 5

Objectives of a BPM PlatformObjectives of a BPM Platform

To be a comprehensive BPM platform a system must not only automate processes, it must:

• Integrate with existing operational systems such as ERP and databases  

• Integrate business processes with those of a company’s suppliers and partners

• Incorporate the business rules that guide a business

• Provide managers with the visibility into those automated processes to monitor operations in real time

• Offer managers the ability to deal with exceptions when they occur by changing business rules or entire processes to respond to business conditions in real time

Page 5: Session 4 & 5

Scope of BPMScope of BPM

ModelLeverage existing processesImport from modeling tools like Aris

AutomateReduce time between process stepsEnsure consistent process quality

IntegrateLeverage existing applicationsBuild a service oriented enterprise

ManageMobilize all existing resourcesAutomate escalation and alternative processes

OptimizeReports on process instancesSimulate new processes

Page 6: Session 4 & 5

Integration Infrastructure for the Enterprise Model SetIntegration Infrastructure for the Enterprise Model Set

The EnterpriseThe EnterpriseProcess

PerspectiveProcess

Perspective

Function PerspectiveFunction

Perspective

Data Perspective

Data Perspective

Page 7: Session 4 & 5

Challenges of Enterprise ModelingChallenges of Enterprise Modeling

Heterogeneous methods & tools

Different conceptual enterprise models focus on different aspects of an organization such as data, activity, process and organizational structure.

But it takes beyond the assorted models as there need is to establish relationship between them and integrate each one of them in order to establish meaning to the enterprise.

Model Correlation

Need to correlate description and analyses of different models to define an organizational picture.

Removal of conflicts and inconsistencies between models, identify missing information and calculate effect of changes in one aspect of the enterprise on another.

Page 8: Session 4 & 5

Challenges continuedChallenges continued

Representation extensibilityWhile modeling an enterprise, decision makers and domain experts are limited by representation capabilities of a particular method or tool.

For example, if you wanted to add a new capability to a function modeling method in order to capture the priority of the activities within a process, you should have to record the priority in annotations of that activity object

Enterprise Model CompilingAn executable model like simulation or optimization model is built from scratch to analyze a problem or to take opportunity.

These are single-use, throw-way models which are expensive, time consuming and wasteful.

Challenge is to automate the creation of executable models from the descriptive representation on an as-needed basis.

Page 9: Session 4 & 5

Modeling methods / tools availableModeling methods / tools available

IDEF - Integrated Definition Methods developed by Knowledge Based System Inc.

CIMOSA - Computer Integrated Manufacturing & Corporate Action Processing

PERA - Purdue Enterprise Reference Architecture

Enterprise Integration website.

ARIS - BPM Platform from IDS Scheer AG (Best Seller)

CimTool - Tool for Business Process Modelling (system requirements modeling, BPR, Concurrent

Engineering, Activity-based Accounting Management)

IBM FlowMark - IBM’s Business Integration Tool

Page 10: Session 4 & 5

MODELMOSIACMODELMOSIAC

In order to overcome the challenges, Dursun Delen (AP, DMSIS, Oklahama State University, Tulsa), Nikunj P. Dalal (AoP, DMSIS, Perakath C. Benjamin have come up with an integrated modeling environment that supports the capture, representation, storage and interlinking of a variety of model types with seamless integration and correlation.

MODELMOSIAC is an software application that provides for an integrated modeling environment.

This application provides an integrated suite of enterprise modeling tools and extensible environment for enterprise analysis.

The information captured in various model types which constitute the enterprise model set is stored in a single integrated information base.

These models can be viewed and manipulated concurrently via a common GUI.

Page 11: Session 4 & 5

Integration Knowledgebase

Model Repository

Conceptual Architecture behind MODELMOSIACConceptual Architecture behind MODELMOSIAC

ER WinER Win

Petri NetPetri Net

QueuingQueuing

OptimizationOptimizationCUSTOM EXTENSIONSCUSTOM EXTENSIONS

Simulations Simulations

BPRBPR

ABCABC

SmartERSmartER

PLUG-IN APPLICATIONSPLUG-IN APPLICATIONS

A10 WinA10 Win

ProSlimProSlim PrOntoPrOnto

ProCostProCost

CostCostOntologyOntologyProcessProcess

FunctionFunction

DataData CORE COMPONENTSCORE COMPONENTS

GUI ShellGUI ShellDB ServicesDB ServicesIntegration RulesIntegration Rules

MODELERSMODELERS

Page 12: Session 4 & 5

Conceptual Architecture behind MODELMOSIACConceptual Architecture behind MODELMOSIAC

Modelers

• The first echelon of the architecture contains various models, called modelers which supports the creation and management of a single model type.

• The modelers are separate, complete components that interface with the core through the common database and common user interface.

• Each modeler requests the core component to create the necessary database tables and entries for data management.

• The modular construction allows new modelers to be added to the environment without disturbing the structure of the database.

Page 13: Session 4 & 5

Plug-in ApplicationsAnother level of functionality and integration.

• This echelon facilitates the development of enterprise model compilers to create bridges between basic modelers and a variety of analysis tools.

• They extend the environment on the core component and one or more of the modelers.

Custom Extensions• The goal is to make it easy for end users to extend the

modeling environment.• Gives unlimited extensibility while maintaining the

integrity and consistency of the formal technologies supported by the tool.