Business process redesign

11


Additional keywords and phrases: business objects, business logistics, frameworks, object-oriented simulation


slide: Business process redesign


Business objects

Designer -- define data model

Business user -- deploy views


slide: Business objects


(Business) frameworks


slide: Business frameworks



slide: The SanFrancisco framework


core business processes

common business objects

foundation object model classes


slide: SanFrancisco object layers



slide: Refining quality control

subsections:


Logistics-based modeling -- criteria for redesign

Product lead time -- time between order and delivery


slide: Logistics-based business models


Logistics-based modeling primitives


slide: Logistics-based modeling primitives


datahandler">

Derived from datahandler class:


slide: Classes derived from



slide: Processing alternatives

Current situation:
Our first model, (left), which represents the current situation, consists of a client producing, for example, requests for a loan at a bank. The requests are initially handled by a clerk whose task is to send requests for amounts greater than $10,000 to the boss. The boss, whose task is to approve or deny the loan, sends the result back to the clerk for processing. If the amount is less than $10,000, the clerk has authority to process the request himself.

Redesign alternative:
In our second model, (right), which is the result of a redesign effort, requests are handled by a clerk who enters the data into a computer. The computer now makes the decision as to whether the loan is improved -- for loans of value less than and greater than 10,000. The clerk then passes the results on to another clerk for the task of dispatching loans.


slide: Presenting a redesign alternative


script



  histogram leadtimes
  agent client generate leadtimes
  client -duration 60 poisson
  transport t1 
  t1 -duration 20
  employee clerk
  operation receive clerk
  receive -duration 20.0 5.0 normal 
  

slide: The script

connecting components



  client -next t1
  t1 -next clerk
  

subsections:


Logistics-based modeling -- criteria for redesign

Product lead time -- time between order and delivery


slide: Logistics-based business models


Logistics-based modeling primitives


slide: Logistics-based modeling primitives


datahandler">

Derived from datahandler class:


slide: Classes derived from



slide: Processing alternatives

Current situation:
Our first model, (left), which represents the current situation, consists of a client producing, for example, requests for a loan at a bank. The requests are initially handled by a clerk whose task is to send requests for amounts greater than $10,000 to the boss. The boss, whose task is to approve or deny the loan, sends the result back to the clerk for processing. If the amount is less than $10,000, the clerk has authority to process the request himself.

Redesign alternative:
In our second model, (right), which is the result of a redesign effort, requests are handled by a clerk who enters the data into a computer. The computer now makes the decision as to whether the loan is improved -- for loans of value less than and greater than 10,000. The clerk then passes the results on to another clerk for the task of dispatching loans.


slide: Presenting a redesign alternative


script



  histogram leadtimes
  agent client generate leadtimes
  client -duration 60 poisson
  transport t1 
  t1 -duration 20
  employee clerk
  operation receive clerk
  receive -duration 20.0 5.0 normal 
  

slide: The script

connecting components



  client -next t1
  t1 -next clerk
  

subsections:



slide: Retail USA © 1995--1999 Visible Decisions Inc.



slide: In3D architecture


Interaction -- visualization


slide: User interaction



slide: Conceptual architecture (DIVA)

DIVA is based on three requirements



slide: Screenshot


Collaborative visualization


slide: Collaborative visualization



slide: Architecture DIVA -- display agents


Business objects -- SanFrancisco framework

1



slide: Section 11.1: Business objects -- SanFrancisco framework


Business process modeling

2



slide: Section 11.2: Business process modeling


Object-oriented simulation

3



slide: Section 11.3: Object-oriented simulation


Visualization support

4



slide: Section 11.4: Visualization support


Migrating from legacy applications

5



slide: Section 11.5: Migrating from legacy applications


  1. Why would you need business objects? Discuss this from the perspective of the end-user as well as from the perspective of management.
  2. What are the motivations underlying the San Francisco framework?
  3. Give an overview of the component layers constituting the San Francisco framework.
  4. Explain the goals of logistics-based business modeling. Discuss possible means to support business modeling.
  5. Give an example of business process simulation.
  6. What classes can you think of for a library supporting object-oriented simulation?
  7. What are the requirements for visualization support? Can you think of actual classes?
  8. Discuss the issues that may arise in migrating from legacy applications. What possible solutions can you think of?

slide: Questions

For more information on business process redesign, consult  [Davenport90],  [Hammer90] and  [Wastell94]. For an in-depth treatment of simulation, you may read, for example,  [Watkins93].