Session 4 & 5
Upcoming SlideShare
Loading in...5
×
 

Session 4 & 5

on

  • 1,012 views

ERP

ERP

Statistics

Views

Total Views
1,012
Views on SlideShare
1,010
Embed Views
2

Actions

Likes
0
Downloads
20
Comments
0

1 Embed 2

http://www.techgig.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Session 4 & 5 Session 4 & 5 Presentation Transcript

  • Session 4 Business 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
  • Introduction & 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. 
  • BPM 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
  • Objectives 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
  • Scope of BPM
    • Model
    • Leverage existing processes
    • Import from modeling tools like Aris
    • Automate
    • Reduce time between process steps
    • Ensure consistent process quality
    • Integrate
    • Leverage existing applications
    • Build a service oriented enterprise
    Manage Mobilize all existing resources Automate escalation and alternative processes Optimize Reports on process instances Simulate new processes
  • Integration Infrastructure for the Enterprise Model Set The Enterprise Process Perspective Function Perspective Data Perspective
  • Challenges 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.
  • Challenges continued
    • Representation extensibility
    • While 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 Compiling
    • An 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.
  • Modeling 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
  • MODELMOSIAC
    • 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.
  • Conceptual Architecture behind MODELMOSIAC Integration Knowledgebase Model Repository ER Win Petri Net Queuing Optimization CUSTOM EXTENSIONS Simulations BPR ABC SmartER PLUG-IN APPLICATIONS A10 Win ProSlim PrOnto ProCost Cost Ontology Process Function Data CORE COMPONENTS GUI Shell DB Services Integration Rules MODELERS
  • Conceptual 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.
    • Plug-in Applications
    • Another 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.