Upload
phamnguyet
View
212
Download
0
Embed Size (px)
Citation preview
A Framework A Framework for for Business Process ArchitectureBusiness Process Architecture
Brett Champlin, MBA, CSP/CCP
VP Online Services, DAMA International Board of Directors & Vice President, ICCP
Adjunct Faculty, Heller College of Business, Roosevelt UniversityProcess Center of Expertise, Allstate Insurance Company
Business Integration & Web Services Conference – Chicago, April 22, 200322
Do you know where your processes are?Do you know where your processes are?• Are you doing Process Re-Design?
– Reengineering? Improvement?
• Are you implementing Workflow?– Document Management? Task Management?
• What’s a core process?– Support Process? Control Process?
• What’s the difference between a Process– Activity, Task, Operation, Method
• Where do you put all those process models and designs?
• Should you buy a Process Modeling, Process Engineering, or Business Process Management package?
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200333
Business Process ArchitectureBusiness Process Architecture• Business NOT Systems Architecture• Define the Key Terms and Components
– “the stack”• Represent Key Points of View• Support Process Innovation Methods• Support Process Management Program• The Business “Blueprint”
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200344
A Short StoryA Short StoryThe Three Stone Masons
• Imagine a 14th Century Monk
• An Encounter with 3 Stone Masons
• Carving Stones
• Building a Wall
• Building a Cathedral
• Context
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200355
A Process Architecture is built with models
as a house is built with stones- but a collection of models
is no more a Process Architecture
than a heap of stones is a house.
(with apologies to Poincare)
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200366
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
“A rock pile ceases to be a rock pile
the moment a single man [sic] contemplates it,
bearing within him the image of a cathedral”
- Antoine de Saint Exupery, author and aviator (1900-1945)
Business Integration & Web Services Conference – Chicago, April 22, 200377
The Zachman Information Systems ArchitectureThe Zachman Information Systems Architecture
BUSINESSSCOPE
BUSINESSMODEL
INFORMATIONSYSTEMSMODEL
TECHNOLOGYMODEL
TECHNOLOGYDEFINITION
INFORMATIONSYSTEM
List of things important to the business.
ENTITY: class of business thing
List of processes the business performs
PROCESS: class of business processes.
List of locations in which the business operates
NODE: business location.
DATA PROCESS LOCATION
Business entities & their inter-relationships
Flows between business processes
Communications links between locations
ENTITY: business entityREL'SHIP: business rule
PROCESS: business processI/O: business resource (including information)
NODE: business unitLINK: business relationship (org., product, information)
Model of the business dataand inter-relationships
Flows between application functions
Distribution network
ENTITY: data entityRELTNSHIP: data relationship
NODE: I.S. function (processor, storage, etc.).LINK: line characteristics
Database Design System Design System Architecture
ENTITY: segment, row, recordRELTNSHP: pointer, key, index
Database Schema andSubschema Definition
Program Code and Control Blocks
Configuration Definition
ENTITY: fields, access privledgeRELTNSHP: access methods, addresses
Data Storage Structures and Access Mechanisms
Databases, data .....
Executable Code
Programs, jobs,transactions.....
System Configuration
Processors, networks,switches. monitors.....
Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987.
PROCESS: application functionI/O: user views (set of data elements).
PROCESS: computer functionI/O: screen/device formats
NODE: hardware/system softwareLINK: line specifications
PROCESS: source codeI/O: control blocks
NODE: addressesLINK: protocols
List of business responsibilities.
RESP.: class of business responsibilities
List of business events.
EVENT: class of significant business events.
List of business goals.
ENDS: mission(s)/goal(s).
ROLE TIMING MOTIVATION
Business Organization. Business Cycles. Business Strategies
RESP: work unit/structureWORK: business resources
EVENT: business eventCYCLE: lapse/lag
ENDS: goal(s)/mission(s)MEANS: tactics/plans
Model of the access requirements.
Model of the process control structure.
Service Support Environment
RESP: system privilegeWORK: access requirements
Access Design Processing Environment Availability Design
RESP: access authorizationsWORK: access group
Access Definition Job Processing Definition Performance Definition
RESP: access objectWORK: access profiles
Access Privileges
User-id’s, access controls .....
Processing Schedules
Batch jobs, transactions,run/rerun instructions .....
System Management Facilities
Monitoring facilities, problemmanagement .....
EVENT: logical process eventCYCLE: precedence/timing
EVENT: physical process eventCYCLE: processing calendar
ENDS: benchmark modelsMEANS: availability of windowsand measures
EVENT: transactions, job submittalCYCLE: job & region schedules
ENDS: benchmark targetsMEANS: benchmark testing, system monitoring/tuning
BUSINESSSCOPE
BUSINESSMODEL
INFORMATIONSYSTEMS
MODEL
TECHNOLOGYMODEL
TECHNOLOGYDEFINITION
INFORMATIONSYSTEM
ENDS: service level agreementsMEANS: I/S plans & change tactics
----------------------
.. . ..
.
Mainframe
IBM AS/400
IBM Compatible
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200388
?WHAT
(product)is it
madeof?
?HOW(process)does
itfunction
?
?WHERE
(place)are
thingslocated
?
?WHO(person)
isinvolved
?
?WHEN
(period)do
thingshappen
?
?WHY
(purpose)are
thingsdone
?
Focuses or TopicsFocuses or TopicsIntroduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200399
CONSUMER End Product or Usage View
SUB- CONTRACTOR Detail Representation or Out-of-Context View
BUILDER Technical Model or Physical Design View
DESIGNER System Model or Logical Design View
OWNER Business/Product Requirements or Conceptual View
PLANNER Scope or Context View
Perspectives or ViewsPerspectives or ViewsIntroduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031010
List of things
BusinessEntity Model
Logical DataModel
PhysicalData Model
DataDefinition
List ofProcesses
BusinessProcess
Model
ApplicationProcess
Model
ApplicationStructure
Chart
Program
List ofLocations
LogisticsNetwork
SystemNetwork
Model
NetworkTechnology
Model
NetworkComponents
List ofOrganization
Units
Work FlowModel
HumanInterface
Paradigm
PresentationArchitecture
InterfaceComponents
List ofEvents
MasterSchedule
ProcessingStructure
ControlStructure
TimingDefinition
List ofBusiness
Goals/Stat.
BusinessPlan
BusinessRule Model
Rule Design
RuleSpecification
DATABASE APPLICATION NETWORK ORGANIZATION SCHEDULE STRATEGY
WHAT
HOW
WHERE
WHO
WHEN
WHY
CONTEXTUALScope
CONCEPTUALBusiness Model
LOGICALSystem Model
PHYSICALTechnology Model
OUT-OF-CONTEXTComponents
PRODUCTFunctioning System
Zachman Framework for Enterprise ArchitectureZachman Framework for Enterprise ArchitectureIntroduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031111
WHY
(purpose)
Goal/Objective
Focuses for Process?Focuses for Process?
WHEN
(period)
Events
HOW
(process)
Processes
WHAT
(product)
Output
WHO
(person)
Role/Skills
WHERE
(place)
Facility
??
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031212
Meta ModelMeta Model
PURPOSE
PEOPLE PLACE
PROCESS
PRODUCT
PERIOD
Adapted from Don SoulsbyAdapted from Don Soulsby
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031313
Standards
Instructions
Forms
Skills
ACTIVITY
PROCESS
SUB-PROCESS
TASK
What’s your process “stack”?What’s your process “stack”?Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031414
Domain LayeringDomain Layering
Business
Operations
Technical
Adapted from Don SoulsbyAdapted from Don Soulsby
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031515
Perspectives or ViewsPerspectives or Views
OPERATOR Working System
BUILDER Applications Specification
DESIGNER Requirements Model
OPERATIONS Process Improvement
BUSINESS Business Redesign/Reengineering
ENTERPRISE Strategic Planning
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business
Business
Dom
ainD
omain
TechnologyTechnology
Dom
ainD
omain
Business Integration & Web Services Conference – Chicago, April 22, 20031616
Procedural ModelProcedural Model
Operations ModelOperations Model
Workflow Systems ModelWorkflow Systems Model
Physical/Technical SpecificationsPhysical/Technical Specifications
Measurement & ControlMeasurement & Control
Business ModelBusiness Model
WHAT/WHAT/INPUTS & INPUTS & OUTPUTSOUTPUTS
HOW/HOW/PROCESSES &PROCESSES &
TASKSTASKS
WHERE/WHERE/FACILITIES &FACILITIES &EQUIPMENTEQUIPMENT
WHO/WHO/ROLE &ROLE &SKILLSSKILLS
WHEN/WHEN/EVENTS &EVENTS &DURATIONDURATION
WHY/WHY/MOTIVATION &MOTIVATION &
METRICSMETRICS
BUSINESSBUSINESSSCOPESCOPE
BUSINESSBUSINESSMODELMODEL
LOGICALLOGICALPROCESSPROCESS
MODELMODEL
WORKFLOWWORKFLOWMODELMODEL
SPECIFICATIONSPECIFICATION
PRODUCTIONPRODUCTION
ENTERPRISEENTERPRISEVIEWSVIEWS
DIRECTOR/DIRECTOR/OWNEROWNER
VIEWVIEW
ANALYST/ANALYST/DESIGNER DESIGNER
VIEWVIEW
BUILDER/BUILDER/MANAGERMANAGER
VIEWVIEW
OPERATOROPERATORVIEWVIEW
MONITORMONITORVIEWVIEW
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
A Business Process FrameworkA Business Process Framework
Business Integration & Web Services Conference – Chicago, April 22, 20031717
Planning for ChangePlanning for ChangeBusiness Domain Technology Domain
PROCESS
PLACE
PRODUCT
PEOPLE
APPLICATION
DISTRIBUTION
DATA
INTERFACE
Business Models Technical Models
StrategicPlans
INNOVATION
TECHNOLOGYPROJECTIONS
BusinessSystem
ALIGNMENT
Opportunities
Adapted from Don SoulsbyAdapted from Don Soulsby
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20031818
”...would you tell me, please which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don't much care where----" said Alice.
"Then it doesn't matter which way you go," said the Cat.
Business Integration & Web Services Conference – Chicago, April 22, 20031919
Words of wisdomWords of wisdom
• “Always design a thing by considering it in its next larger context -
a chair in a room, a room in a house, a house in an environment, an environment in a city plan.”
- Eero Saarinen
Business Integration & Web Services Conference – Chicago, April 22, 20032020
We agree on what our processes are
We know how the processes interactwhat each process delivershow each process produces it’s
deliverableswhat skills are required for each processhow well each process performs
We can measure effectively and manage by these facts
We have an owner for each process
We will be managing by process when:
Goals of “Manage by Process”Goals of “Manage by Process”Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032121
What’s a Model?What’s a Model?
• A model is information• It contains:
– one or more pictures (diagrams)– information about the objects & relationships on the diagram– information about the relationships between objects in
multiple diagrams– information about how the thing it “models” behaves or
performs• It is a vehicle for understanding how things work
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032222
Create the Process FrameworkCreate the Process Framework
• This is the overall solution to storing and managing enterprise process information
• We need this to support a process management program.
• We need this to support our Business Process Planning method and services
• It will support business analysis and reuse of business information (Strategic Integration)
• It will be the basis for maneuverability – agility – strategic repositioning
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032323
Build a Process RepositoryBuild a Process Repository
The Framework is a “blueprint” for a Business Process Model ‘Repository’
It is a map of the structure for the Business Process Model Repository
that can be used to store, locate, access, and navigate
through enterprise process information
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032424
How To Build ItHow To Build It
• Build the Organizing Structure (the Framework)– information model– structural hierarchies
• Build role-based Views – cross-structural perspectives – consistent levels of granularity
• Define Notation to express those views– the diagrams & the objects that appear on them
• Define techniques to develop the models– and the transitions between views
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032525
Benefits of a Business Process RepositoryBenefits of a Business Process Repository
• With an Business Process Model Repository in place:– a project team will have a place to store the business models
they create for future reference– the models can be integrated into an enterprise wide view– the models can be used in defining systems requirements– a process’s information is available to anybody, anytime– the models can be used in change management– The models can be used as reference guides – the repository can be used to do impact analysis – the models can be used in business planning– the models can be used in IM planning– the models can be used in training
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032626
Benefits of a Business Process FrameworkBenefits of a Business Process Framework
• Common Frame of Reference • Integrated views of processes• Consistent method of organization
– Persistent storage of process information• the models are available• the models are in a consistent format
• A new powerful information resource for the organization to use in many new ways that were previously not available or feasible
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 20032727
A Parting Thought...A Parting Thought...
Wisdom is knowing what to do next…
Skill is knowing how to do it, and…
Virtue is doing it!
- David Starr Jordan
Business Integration & Web Services Conference – Chicago, April 22, 20032828
Brett Champlin, CSP/CCPBrett Champlin, CSP/CCP
[email protected][email protected]@[email protected]
You may contact me You may contact me with any questions or feedback at:with any questions or feedback at:
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion