A Framework for Business Process Architecture

A Framework for Business 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 University Process Center of Expertise, Allstate Insurance Company

Do you know where your processes are? Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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? Business Integration & Web Services Conference – Chicago, April 22, 2003

Business Process Architecture Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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” Business Integration & Web Services Conference – Chicago, April 22, 2003

A Short Story Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion The Three Stone Masons • Imagine a 14th Century Monk • An Encounter with 3 Stone Masons • Carving Stones • Building a Wall • Building a Cathedral • Context Business Integration & Web Services Conference – Chicago, April 22, 2003

Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion 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) Business Integration & Web Services Conference – Chicago, April 22, 2003

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, 2003

DATA PROCESS LOCATION ROLE TIMING MOTIVATION List of things important to the business. List of processes the business performs List of locations in which the business operates List of business responsibilities. List of business events. List of business goals. . . . . BUSINESS SCOPE BUSINESS SCOPE . . EVENT: class of significant business events. ENTITY: class of business thing RESP.: class of business responsibilities PROCESS: class of business processes. NODE: business location. ENDS: mission(s)/goal(s). Business entities & their inter-relationships Flows between business processes Communications links between locations Business Organization. Business Cycles. Business Strategies BUSINESS MODEL BUSINESS MODEL NODE: business unit LINK: business relationship (org., product, information) PROCESS: business process I/O: business resource (including information) ENDS: goal(s)/mission(s) MEANS: tactics/plans EVENT: business event CYCLE: lapse/lag ENTITY: business entity REL'SHIP: business rule RESP: work unit/structure WORK: business resources Service Support Environment Model of the access requirements. Model of the business data and inter-relationships Distribution network Flows between application functions Model of the process control structure. ---------------------- INFORMATION SYSTEMS MODEL INFORMATION SYSTEMS MODEL ENDS: service level agreements MEANS: I/S plans & change tactics PROCESS: application function I/O: user views (set of data elements). NODE: I.S. function (processor, storage, etc.). LINK: line characteristics EVENT: logical process event CYCLE: precedence/timing ENTITY: data entity RELTNSHIP: data relationship RESP: system privilege WORK: access requirements Database Design System Design System Architecture Access Design Processing Environment Availability Design TECHNOLOGY MODEL TECHNOLOGY MODEL ENDS: benchmark models MEANS: availability of windows and measures ENTITY: segment, row, record RELTNSHP: pointer, key, index PROCESS: computer function I/O: screen/device formats NODE: hardware/system software LINK: line specifications RESP: access authorizations WORK: access group EVENT: physical process event CYCLE: processing calendar Database Schema and Subschema Definition Program Code and Control Blocks Configuration Definition Access Definition Job Processing Definition Performance Definition TECHNOLOGY DEFINITION TECHNOLOGY DEFINITION ENTITY: fields, access privledge RELTNSHP: access methods, addresses EVENT: transactions, job submittal CYCLE: job & region schedules ENDS: benchmark targets MEANS: benchmark testing, system monitoring/tuning RESP: access object WORK: access profiles PROCESS: source code I/O: control blocks NODE: addresses LINK: protocols System Management Facilities Data Storage Structures and Access Mechanisms Executable Code System Configuration Access Privileges Processing Schedules INFORMATION SYSTEM INFORMATION SYSTEM User-id’s, access controls ..... Programs, jobs, transactions..... Processors, networks, switches. monitors..... Batch jobs, transactions, run/rerun instructions ..... Monitoring facilities, problem management ..... Databases, data ..... Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987. The Zachman Information Systems Architecture 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, 2003

Focuses or Topics ? ? ? ? ? ? WHERE WHO WHEN WHY HOW WHAT (place) (person) (period) (purpose) (process) are is do are does (product) is it things involved things things it made located happen done function of ? ? ? ? ? ? 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, 2003

Perspectives or Views PLANNER Scope or Context View OWNER Business/Product Requirements or Conceptual View DESIGNER System Model or Logical Design View BUILDER Technical Model or Physical Design View SUB- CONTRACTOR Detail Representation or Out-of-Context View CONSUMER End Product or Usage View 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, 2003

HOW WHAT WHY WHERE WHO WHEN List of List of CONTEXTUAL List of List of List of List of things Organization Units Business Processes Locations Events Scope Goals/Stat. Business CONCEPTUAL Business Logistics Work Flow Master Business Process Entity Model Network Model Schedule Plan Business Model Model Application System Human LOGICAL Logical Data Processing Business Process Network Interface Model Structure Rule Model System Model Model Model Paradigm Application Network PHYSICAL Physical Presentation Control Structure Technology Rule Design Data Model Architecture Structure Technology Model Chart Model OUT-OF- Data Network Interface Timing Rule CONTEXT Program Definition Components Components Definition Specification Components PRODUCT DATABASE APPLICATION NETWORK ORGANIZATION SCHEDULE STRATEGY Functioning System Zachman Framework for Enterprise Architecture 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, 2003

Focuses for Process? Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion WHY WHEN HOW WHAT WHO WHERE (purpose) (period) (process) (product) (person) (place) Goal/ Objective Events Processes Output Role/ Skills Facility ? Business Integration & Web Services Conference – Chicago, April 22, 2003

Meta Model PROCESS PERIOD PURPOSE PRODUCT PEOPLE PLACE Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion Adapted from Don Soulsby Business Integration & Web Services Conference – Chicago, April 22, 2003

What’s your process “stack”? Standards Instructions Forms TASK Skills Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion PROCESS ACTIVITY SUB-PROCESS Business Integration & Web Services Conference – Chicago, April 22, 2003

Domain Layering Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion Business Operations Technical Adapted from Don Soulsby Business Integration & Web Services Conference – Chicago, April 22, 2003

Perspectives or Views Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion ENTERPRISE Strategic Planning BusinessDomain BUSINESS Business Redesign/Reengineering OPERATIONS Process Improvement DESIGNER Requirements Model TechnologyDomain BUILDER Applications Specification OPERATOR Working System Business Integration & Web Services Conference – Chicago, April 22, 2003

A Business Process Framework WHAT/INPUTS & OUTPUTS HOW/PROCESSES & TASKS WHERE/FACILITIES & EQUIPMENT WHO/ROLE & SKILLS WHEN/EVENTS & DURATION WHY/MOTIVATION & METRICS Business Model BUSINESS SCOPE ENTERPRISE VIEWS Operations Model BUSINESS MODEL DIRECTOR/ OWNER VIEW Procedural Model LOGICAL PROCESS MODEL ANALYST/ DESIGNER VIEW Workflow Systems Model WORKFLOW MODEL BUILDER/ MANAGER VIEW Physical/Technical Specifications SPECIFICATION OPERATOR VIEW Measurement & Control PRODUCTION MONITOR VIEW 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, 2003

Strategic Plans INNOVATION Business System Opportunities TECHNOLOGY PROJECTIONS ALIGNMENT Planning for Change Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion Business Domain Technology Domain PRODUCT PROCESS DATA APPLICATION PEOPLE PLACE INTERFACE DISTRIBUTION Business Models Technical Models Adapted from Don Soulsby Business Integration & Web Services Conference – Chicago, April 22, 2003

”...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, 2003

Words 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, 2003

Goals of “Manage by Process” We will be managing by process when: We agree on what our processes are We know how the processes interact what each process delivers how each process produces it’s deliverables what skills are required for each process how well each process performs We can measure effectively and manage by these facts We have an owner for each 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, 2003

What’s a Model? Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

Create the Process Framework Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

Build a Process Repository Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

How To Build It Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

Benefits of a Business Process Repository Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

Benefits of a Business Process Framework Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion • 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 Business Integration & Web Services Conference – Chicago, April 22, 2003

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, 2003

Introduction A Short Story The ZachmanFramework A BusinessProcess Framework The Goal How to Build It Benefits Discussion You may contact me with any questions or feedback at: Brett Champlin, CSP/CCP brett@abpmp.org vp_online_services@dama.org vicepres@iccp.org Business Integration & Web Services Conference – Chicago, April 22, 2003

A Framework for Business Process Architecture