1
© Value Team ApS A part of the Process Reference Framework. For more information visit www.LeadFrameworks.com. E AD EMAIL [email protected] WEBSITE www.ValueTeam.biz INPUT OUTPUT OUTPUT INPUT OUTPUT INPUT Gateways Pools, Lanes, Business Competencies and Flows Process, Workflow and Collaboration Introduction Decomposition & Composition of a Process Interaction Model Tasks and Activities Conversation Diagrams Choreographies Events How to use Notation Artifacts in Layered Architecture Service Model None Untyped events, indicate start point, state changes or final states. A Task is a unit of work, the job to be performed. When marked with a (+) symbol it indicates a sub-process, an activity that can be defined. Below is an example of a public process diagram in a collaboration Example of a process workflow and collaboration diagram Below is an example of the LEAD Blueprinting Approach Below is an example of the Business View and Process View Below is an example of a private process diagram in a collaboration Task Transaction Event Sub-process Call Activity A Transaction is a set of activities that logically belong together; it might follow a specified transaction protocol. Event-based Represents a branching point in the process where the alternative paths that follow the gateway are based on events that occur. An Event Sub-process is placed into a process or sub-process. It is activated when its start event gets triggered and may interrupt the higher level process context or run parallel (non- interrupting) depending on the start event. A Call Activity is a wrapper for a globally defined task or process reused in the current process. A call to a process is marked with a (+) symbol. Standard (start) Catching Throwing Standard (end) Event sub-process interrupting Event sub-process non-interrupting Boundary interrupting Boundary non-interrupting Start Event Caught Message Start Thrown Message End Intermediate Event End Event Objects Message Receiving and sending messages. Timer Cyclic timer events, points in time, time spans or timeouts. Escalation Escalating to a higher level of responsibility. Conditional Reacting to changed business conditions or integrating business rules. Link Off-page connectors. Two corresponding link events equal a sequence flow. Error Catching or throwing named errors. Cancel Reacting to cancelled transactions or triggering cancellation. Compensation Handling or triggering compensation. Signal Signalling across different processes. A signal thrown can be caught multiple times. Multiple Catching one out of a set of events. Throwing all events defined. Parallel Multiple Catching all out of a set of parallel events. Terminate Triggering the immediate termination of a process. What are events? The concept of an Event and its classification are basic modelling principles when compared to BPMN events, as there are literally tons of event types and various ways to classify them. The Event concept is fundamental to BPMN, as it allows to describe processes in an event-driven manner. In general, an Event is something that happens during the course of a process. Events affect the flow of the model and usually have a cause (trigger) or an impact (result). There are three major categories of events, depending on how they affect the workflow of the process: • A Start Event begins the process flow and to avoid confusion, only one Start Event for a process is preferred. PO (Production Order) Received is a Start Event, triggered by the arrival of a Retailer PO (Production Order) message. • An Intermediate Event indicates something that happens between the start and end of a process. Such events are usually related to intermediate messages sent or received. Production Order Transferred is an Intermediate Event. • An End Event indicates where a path in the process will end. As many End Events as needed are allowed, as the process may end in many ways. Within our sample, Correction(s) Request Sent is an End Event. Although there are few generic event types without explicit triggers and results, these concepts are precisely the reasons why events multiply so happily. The kind of event triggers and results are indicated by small icons inside their symbols. In order to see the wood from the trees however, we will use only one kind of a trigger and result, namely a message. Two of the presented event examples have a small message icon inside. In BPMN-speak and in line with its conventions, PO Received (Production Order Received) Start Event catches the incoming Retailer PO message and the icon is transparent. Produc- tion Order Transferred Intermediate Event throws the Production Order message and this in turn is indicated by a black icon. Business Process Management - Lessons Learned • Pool: A Pool represents a Participant in a process. It also acts as a graphical container for partitioning a set of activities from other Pools, usually in the context of B2B situations. • Lane: A Lane is a sub-partition within a Pool and will extend the entire length of the Pool, either vertically or horizontally. Lanes are used to organize and categorize activities. • Business Competency: A Business Competency represents the area of business in which the process takes part. It is essential to reflect which part of a company’s business mechanics are directly involved in the flow within the Business Process Diagram (BPD). What are pools, lanes and business competencies? The LEAD Methodology based on BPMN 2.0 utilizes the concept of both Pools, Lanes, and Business Competencies as a mechanism to organize activities into separate visual categories in order to illustrate different functional capabilities or responsibilities. The LEAD BPMN supports swimlanes with three main constructs. The three types of swimlane objects are: • Sequence Flow: A Sequence Flow is represented by a solid line with a solid arrowhead and is used to show the order (the sequence) that activities will be performed in a process. • Message Flow: A Message Flow is represented by a dashed line with a solid arrowhead and is used to show the flow of messages between two separate process Participants (business entities or business roles) that send and receive them. • Association Flow: An Association Flow is represented by a dotted line and is used to associate text and other artifacts with flow objects. Association Flows are used to show the inputs and outputs of activities. • Data Association Flow: A Data Association Flow is represented by a dotted line with a solid arrowhead and is used to associate data (electronic or non-electronic) with flow objects. Data Associations are used to show the inputs and outputs of activities. What are flows? Flow Objects are connected together in a diagram to create the basic skeletal structure of a business process. There are four connecting objects that provide this function. These connectors are: Pools, lanes and business competencies represent responsibilities for activities in a process. The order of message exchanges can be specified by combining message flow and sequence flow. A Sequence Flow can travel freely within a pool, but cannot cross its boundaries. A Message Flow can be used to connect process elements residing within different pools, as well as to connect pools as such. However, it cannot be used to connect elements of the same process, i.e. contained within one pool. A Message Flow arrow has a circle as a starting point. An Association Flow is used to associate an artifact or text to a flow object. A Data Association Flow is used to associate data elements to activities, processes and global tasks. What are gateways? Gateways are used to control how process paths converge and diverge within a process. In other words, they are decision points concerning further process flow. The term ‘Gateway’ implies that there is a mechanism that either allows or disallows passage through the Gateway. Again, there are plenty of Gateway types, but only two of them will be utilized in the LEAD case. An Exclusive Gateway is used to create alternative paths within a workflow of the process. This is basically the “OR” logical operator, as for a given process instance only one of the paths can be selected. A ‘PO OK?’ is an example. A Parallel Gateway is used to create or to combine parallel flows and acts as an “AND” logical operator. Obviously, a Parallel Gateway initiates parallel paths without checking any conditions, therefore it is not labeled. Such a Gateway follows Check Stock Levels Sub-process. What are choreographies? A Choreography model is one of the types of models to specify choreographies in BPMN. It consists of choreog- raphy tasks and sub-processes and common BPMN elements, such as gateways and events. A Choreogra- phy does not only describe what a business process does, but also defines how individual processes interact with each other. In short, it depicts all the processes and their required interactions in a business process diagram. However, unlike BPMN’s process, it doesn’t belong to any pool. A Choreography Task represents an Interaction (Message Exchange) between two Participants. A Sub-Choreography contains a refined choreogra- phy with several Interactions. A Call Choreography is a wrapper for a globally defined Choreography Task or Sub-Choreography. A call to a Sub-Choreography is marked with a (+) symbol. What Are Conversation Diagrams? The BPMN Conversation Diagram shows the conversations between the participants, and shows them as conversation objects (hexagons) without showing the individual message flow, which can go back and forth within a conversation. A Conversation defines a set of logically related message exchanges. When marked with a (+) symbol it indicates a Sub-Conversation, a compound conversation element. A Call Conversation is a wrapper for a globally defined Conversation or Sub- Conversation. A call to a Sub-Conversation is marked with a (+) symbol A Conversation Link connects Conversations and Participants. Business Object Represents a business object like product, employee, customer, partner, service, etc. Collection of Business Objects Represents a collection of business objects like products, employees, customers, partners, services, etc. Business Input Is an external input for the entire business function and/or business service. A kind of input parameter. Business Output Is the business result of the entire progression. A kind of output param- eter. Business Store Is a place where the business object resides. Information Object Represents a container of information about a real-world object like a person, an employee, a product or a service, etc. Collection of Information Objects Represents a collection of information objects about real-world objects like people, employees, products or services, etc. Information Input Is an external input for the entire information function and/or information service. A kind of input parameter. Information Output Is the information result of the entire progression. A kind of output parameter. Information Store Is a place where the information object resides. Data Object* Represents a container of information within the flow of the process, such as business documents, e-mails, or letters. Collection of Data Objects* Represents a collection of data objects, e.g. a list of order items. Data Input Is an external input for the entire process. A kind of input parameter. Data Output Is the data result of the entire process. A kind of output parameter. Data Store Is a place where the process can read or write data, e.g. a database or a filing cabinet. It persists beyond the lifetime of the process instance. What are data objects? A Data Object is considered an artifact and not a flow object. They are consid- ered an artifact because they do not have any direct effect on the Sequence Flow or Message Flow of the process, but they do provide information about what the process does. That is, how documents, data, and other objects are used and updated during the process. While the name “Data Object” may imply an electronic document, they can be used to represent many different types of objects, both electronic and physical. What are information objects? An Information Object is used to specify information about real-world objects (people, employees, products or a sales order, etc.) and therefore it is the digital representation of an existing entity within an Information System e.g. Oracle ERP and/or SAP. It encompasses both the business information (in the form of functions and method) and the application information (in the form of attributes) of this entity. Information objects can be found, and therefore modelled, in business functions, business services and within the process itself. What are business objects? A Business Object is the term used to express real-world objects like people, employees, products or a sales order, customers and revenue. In terms of modelling, business objects uses a patented semantic layer that shields users from the complexities of table names and relationships. Once the semantic layer has been defined, users work with familiar real-world business objects such as products, customers and revenue. What is the link between the service model and the process model? This pattern generally describes how to establish remote write operations on services asynchronously. This decouples the frequently time-consuming write operation from the process flow on the consumer side. Asynchronous operations and communication may be useful when method calls are invoked across process boundaries via remote mechanisms. In particular, when calling web services using SOAP or similar remote protocols, network latency and bandwidth restrictions create communication bottlenecks. Asynchronous com- munication therefore will not hinder the process flow, but will just initiate the remote operation and processing of data. What is a service task? A Service Task is a Task that uses some sort of service, which could be a web service or an automated application. A Service Task object shares the same shape as the Task, which is a rectangle that has rounded corners. However, there is a graphical marker in the upper left corner of the shape that indicates that the Task is a Service Task. A Service Task is a rounded corner rectangle that must be drawn with a single thin line and includes a marker that distinguishes the shape from other Task types. The Service Model What is a process, process workflow and process collaboration? BPMN defines a process as a sequence or flow of Activities in an organization, with the objective of carrying out work. In BPMN, a process is depicted as a graph of flow elements, which are a set of Activities, Events, Gateways, and Sequence Flows. Thereby the sequence of flows should follow the organizational workflow, where a process flow can be depicted either on a Collaboration Diagram, generally if there are several pools, or on a Business Process Diagram, if there is only one pool. In any case, a process must be fully embedded within one pool and it can communicate with other pools only via message exchanges. What are interaction models? Interaction models are new in BPMN 2.0. They allow to model B2B cooperations. Business services are characterized by interactions between businesses and their customers and partners. They are usually agreed or assumed ahead of time, and do not detail the intemal activities of the participants. Agreements determine what information, goods, or personnel are needed by whom and at what time, how complaints and unusual situations are handled, and so on. The interactions might be very short from start to end, or take place over a long period. The process to the left could be public, because it only sends and receives messages. The process to the left shows a possible private process containing Activities that are not interactive and unsually not shown to other Participants A holistic way of working with Process Mapping, Process Architecture, Process Notations and Process Modelling Process Reference Framework E AD Send Order Status Search Internal Records Evaluate Credit Receive Credit Score Request Credit Score Book Room Multi-Instance Pool (Black Box) Pool (Black Box) Pool (Black Box) Conversation Sub-Conversation Order Drinks Identify Customer Requirements User Task Write Poll Task Task Credit Request Credit Request Credit Response Customer Order Customer Order Order Response Credit Response Order Response Credit Agency Customer Credit Agency Buyer Competency Competency Role Role Pool Pool Competency Competency Role Role Pool Pool Participant A Choreography Task Participant A Participant B Participant B Participant C Sub-Choreography Participant A Participant B Call Choreography Pool Competency Role Lane Lane Manual Service Task Automated Service Task Pool Pool Competency Role Competency Role What are tasks and activities? In general, an Activity is a generic term for work that a company performs in a process. Activities are thus the executable elements of a process. The basic activity categories are Tasks and Sub-processes. A Task is an elementary Activity used when the work in the process is not broken down to a finer level of Process Model detail. Activity Markers Markers indicate execution behavior of activities: Sub-process Marker* Loop Marker Parallel MI Marker* Sequential MI Marker Ad Hoc Marker Compensation Marker BPMN Task Types Type specify the nature of the action to be performed: * = Is also available in SAP Netweaver 7.2+ MI = Multiple Instance All task types and activities are available in iGrafx Send Task* Receive Task* User Task* Manual Task Rule Task Manual Service Task Script Task Annotation Marker* What is RACI mapping and how is it used? RACI is an acronym derived from the four key responsibilities most typically used: Responsible, Accountable, Consulted, and Informed. The RACI model describes the participation by various roles in completing tasks or deliverables for a project or business process. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and processes. RACI Modelling Principle At least one ‘R’ has to be assigned to each activity, but several ‘R’s are possible. Only one ‘A’ can be assigned to an activity. The same role might be concurrently ‘R’ and ‘A’. If there is only one ‘R’ but no ‘A’ assigned to an activity, it is assumed that ‘R’ is also ‘A’ for that activity. Business Process Representation Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEAD Framework and will be subject to continuous improvement and development. History of Business Process Modelling Notations March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. August 2004: BPMN 1.0 specification was released to the public. Now maintained by the Object Management Group (OMG). January 2011: BPMN 2.0 specification was released to the public. The LEAD Framework further developed upon the BPMN 2.0 specification to include linkage to: Business Competencies (January 2011). Service Mapping (January 2011). Interaction Models (March 2011). RACI Mapping (May 2011). Value Mapping (November 2011). SAP Netweaver connection (January 2012). SAP Solution Manager connection (February 2012). Incorporation of LEAD BPMN principles into Adobe iGrafx (November 2012). ERP implementation in your Business Model, Service Model, and Operating Model Many ERP implementations today are supporting business innovation and transformation and are looking to change either their Business Model, Service Model, and/or their Operating Model. As a result of this, the Actors, Roles, Functions, Processes and Controls will also change – but not all existing processes support the wanted target models. Therefore, without a confident ‘As-Is’ business process baseline, the mapping of processes and activities to SAP functional- ities has to be reverse engineered from the basis of the Target Business Model (TBM), Target Service Model (TSM) and/or Target Operating Model (TOM). The goal is to review all available documentation and process flows (APQC, SCOR, LEAD Process MAP, SAP Solution Manager, etc.) to leverage all existing work- flows, standards and best practices that, while considering the core competitive, core differentiating and non-core competencies where the last mentioned need the support of the generic ‘best practice - vanilla’ implementation, is maintaining the project goals of realized optimal transformation and cost savings for the organization. Where the organization has core competitive and/or core differentiating competencies, and therefore best practice can't be applied, process mapping that captures the organization’s own practice should be undertaken to ensure value creation. Business Process Definition A structure of related activities designed to create results for the organization. This structure of related activities can be mapped into process models. Relating these structures in a different sequence in order to optimize, re-engineer or innovate will create a new result for the organization: 1) the Main Processes, which consists of the delivery of your main business. Main Processes are the essential processes of the business that create value for the external customer. They are business strategy, product delivery, and customer support type of processes. 2) the Supporting Processes, which consists of processes that support the business. Supporting Processes are all the processes that supply resources to the other processes and largely are non-value adding to customers. They generally are the Human Resources, Supply Management, and Information Technology, to name a few. 3) the Management Processes, which consists of processes that manage the business. Management Processes are all the processes that set direction (e.g. objectives, goals, etc.), plan, forecast, and control (monitor, measure and govern) the performance or execution of any type of activity. Business Process Documentation Business process documentation is composed of two parts. The first part of the process documentation should cover a list of all parts of the process. It will describe the process and possibly information, such as the ownership (business competency), the hierarchy of the process, the objectives, the measurements, etc., but it will also describe all of the activity details, such as the inputs, outputs, roles and responsibilities, as well as the decision points and events. The second part consists of the visual graphic of the process, also known as the Process Model, and provides a visual representation of all the activities, interactions and workflow controls, such as decision points and exception paths. Process Modelling Rules The activity of modelling a business process usually predicates a need to change processes or identify issues to be corrected. This transformation may or may not require IT involvement, although that is a common driver for the need to model a business process. Change Management programmes are desired to put the processes into practice. Process modelling addresses the process aspects of an Enterprise Business Architecture, leading to an all encompassing Enterprise Architecture. The relationships of a business’ processes in the context of the rest of the enterprise systems (e.g. data, organizational structure, strategies, etc.) create greater capabilities in analyzing and planning a change. Process modelling has always been a key aspect of business process reengineering, and Continu- ous Improvement approaches seen in the LEAD Frameworks, Methods and Approaches. Notation Mapping Level The BPMN specification defines three levels of BPMN mapping: 1) Descriptive Models • Suitable for high level modelling - should be comfortable for analysts that have used flowcharts. • Working with basic set of BPMN elements. 2) Analytic Process Models • Contains the concepts most commonly used and covered in BPMN training. • Defines semantics and are subjects to its validation rules. 3) Common Executable Process Models • Focuses on the elements required for executable process models by adding XML underneath the shapes (new with BPMN 2.0). • Leads to automation using BPMS. Business Process Hierarchy Business processes can get quite complex and this makes it tough to model a very big process into just one graphical model. A process hierarchy is necessary to divide complex processes into smaller parts. A process hierarchy follows the "from abstract to concrete" principle. This means it provides information about the processes on different levels of granularity. Therefore it is possible to get information about the abstract value chain (e.g. Purchasing, Production, Sales) or about very specific process steps and their logical order (e.g. create customer, approve purchase order). A process hierarchy is defined by its levels and the information given in these levels. It is key to have a defined information base on each level (e.g. a process step is always performed by a specific role instead of an abstract organizational unit), otherwise process models will not be comparable at a later stage. The model to the right shows the Process Hierarchy Model and provides an example for each level - the Process Hierarchy Model consists of (at least) five process levels. Process Level 1: Business Process Area (e.g. Demand-to-Close) A Business Process Area is a set of process areas with the same business goals, spanning the organization from end-to-end (sometimes extending out to business partners). Thus, an enterprise‘s entire Business Process Area (operating structure) is not a business process but rather a categorization and can therefore be depicted by its combined Process Group groups. Process Level 2: Business Process Group (e.g. Demand Generation) A Process Group is not a Business Process either but a categorization as well, therefore a Process Group is a set of logically related Business Process Groups which has business processes within that performs to achieve a defined, measurable business outcome for a particular internal or external customer. Process Level 3: Business Process (e.g. Lead Management) A Business Process is the first level of processes where all business processes follow a certain flow in order to accomplish the defined business outcome. They generally consist of discrete, highly encapsulated business operations. Process Level 4: Business Process Step (e.g. Lead Distribution) A Business Process Step represents an operation of a business process that performs a defined function. The order of all business process steps illustrates the business logical flow followed in order to fulfill the purpose of the business process. Process Level 5: Business Process Activity (e.g. Convert Lead to Opportunity) A Business Process Module is the smallest business relevant activity or function, which has no process level below. Modules can consist of a single or multiple tasks, performed in an application, ideally represented in a transaction and accessed via a specific user interface. Reporting Task* Automated Service Task* Automated Task* Mapping Task* Notification Task* Ruleset* Flow Ruleset* Rule* Rulescript* Rule Flow* Decision Table* Exclusive Gateway* When splitting, it routes the sequence flow to one of the outgoing branches. When merging, it awaits one incoming branch to complete before triggering the outgoing flow. Gateway* Gateways are used to control how process paths converge and diverge within a process. Event-based Gateway* Is always followed by catching events or receive tasks. Sequence flow is routed to the subsequent event/task which happens first. Parallel Gateway* Is always followed by catching events or receive tasks. Sequence flow is routed to the subsequent event/task which happens first. Inclusive Gateway When splitting, one or more branches are activated. All active incoming branches must complete before merging. Complex Gateway Complex merging and branching behaviour that is not captured by other gateways. * = Is also available in SAP Netweaver 7.2+. Exclusive Event-based Gateway (instantiate) Each occurence of a subsequent event starts a new process instance. Parallel Event-based Gateway (instantiate) The occurence of all subsequent events starts a new process instance. Solution Development Solution standards, functions, rules, object development (e.g. business, information and data) Solution Documentation (Solution scenario, object definition) Organizational Units Master Data Business Requirements Process Scenarios Business Processes Object & Transactions (Function, Task and Services, Collection of Objects, Object Storage) System Information (Application Component) Interfaces (Point 2 Point & Multiple Point 2 Point, Object Input & Output) Building sustainable assets through business blueprint in Solution Manager Process Step Process Activities Process Step Responsible Role(s) that carry (carries) out the activity. RACI Responsibility Type R A C I Description BPM Link Type Accountable Role that is ultimately accountable for the success of the activity and occupies authority to delegate its execution. Consulted Role(s) to be asked before/during carrying out the activity (two-way communication). Informed Role(s) to be informed after/during the activity is carried out (one-way communication). Carries out Is ultimately accountable for Has consulting role in Must be informed about Covered by Business Content Quality Foster high quality Process Models Support efficiency and effective modelling Faithful to Business Reality Complete Sustainable Content-wise Consistent Covered by Business and IT Structural Quality Modelling Unambiguous/Clear Easy-To-Read Uniform Comparable Fast Enablement Easy Modelling Prevent Chaos in Distributed Modelling Help Focus on Important Tasks Formally Consistent BUSINESS LAYER APPLICATION LAYER DATA LAYER TECHNOLOGY LAYER Application Services Business Process Information Flow Business Service Flow Business Competency Business Competency Business Process Application Services Data Services Data Services Platform Services Automated Service Infrastructure Services Manual Service Task Automated Service Task Strategy Planning Forecast Budget Value & Performance Management BUSINESS COMPETENCY VIEW BUSINESS PROCESS STANDARDIZATION VIEW BUSINESS MEASUREMENTS VIEW Strategic Management Process of Executives Strategic KPI’s and PPI’s Main Process Standardization Supporting Process Standardization Control & Monitoring Evaluation & Reports Operational Plan Policies, Rules & Guidelines Administration Measurements Audits Tactical Tactical KPI’s and PPI’s Management Process of Managers Main Process Standardization Executing Operational Administration Delivery Operational Measurements Processing Operational Oversight Operational Reporting Operational Operational KPI’s and PPI’s Management Process of Employees Main Processes Standardization Supporting Process Standardization Supporting Processes Standardization Business Services Service Workflow Level 3a Business Process Level 4a Process Steps Level 5a Process Activities Business Workflow SAP Industry Value Chain SAP Value Chain Element SAP Business Scenario Group Legacy Task Legacy Functionality Legacy Services SAP Portal Scenarios SAP Portal Services SAP Product SAP Measurements Financial Operational SAP Process Workflow Business (Function) Identify Business Model Identify Business Goals Define Service Type Use SAP Process Reference content Capture Value Drivers Capture Performance Drivers Identify Service Need Process (Macro-level) Function (Micro-level) Function SAP Business Scenario SAP Process Activity SAP Process Step SAP Process Configuration Variant Agile LEAD Blueprinting Approach Solution Manager and the LEAD Blueprinting Approach ESRP ERP Solution Scenarios Interoperability Solution Scenarios Legacy Solution Portfolio delivers supports orchestrates, decomposes orchestrates supports decomposes consists of belongs to consists of belongs to belongs to groups consists of belongs to consists of is a sequence of is part of is part of is part of is part of covers is measured by is represented on is used within creates and uses is composed of has a is a variant of Level 3b Business Process Variant Level 4b Process Steps Variant Level 5b Process Activities Variant Business Architecture Process Architecture SAP Information Architecture = Business Layer Component = Application Layer Component = Technology Layer Component = Decomposition Component = Composition Component BUSINESS COMPETENCY Which business competency uses the process? MODELS Organizational Chart Competency Map Competency Matrix Business Model Level 1-3 Business and Information Object Organizational Construct Business Area Business Group Business Function Business Resource Core Differentiating Competency Core Competitive Competency Non-Core Competency Cost (Revenue) Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Application Component Application Module Application Feature Application Function Application Task Application Service Goal Objective Performance Indicator Requirement Performance Expectation Performance Driver Value Proposition Service Construct Service Delivery Main Service Supporting Service Service Provider Service Consumer Service Tiers Business Process Process Step Process Activity Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Policies Guidelines Standards Regulations Governance Controls Risk Management Audit Evaluation Security Monitoring Business Performance Indicator Business KPI’s Service Level Agreement Process Performance Indicator System Measures Performance Measurement Service Measurement Scorecards Dashboards Cockpits Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Object Information Object Data Object Infrastructure Service Business Rule Service Rule Process Rule Application Rule Data Rule Security Rule Business Process Process Step Process Activity Events Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Events Gateways Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Gateways Business Owner Process Owner Service Owner Value Owner Performance owner Information Owner Application Owner Data Owner Platform Owner Infrastructure Owner Security Owner Compliance Owner Platform Device Platform Service Business Role Process Role Data Component Data Entity Data Service Business Workflow Value Flow Reporting Flow Service Flow Information Flow Process Workflow Application Workflow Scenarios Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process Business Process Process Step Process Activity Gateways Management Process Main Process Supporting Process Media As Communication Media Store, Advertising Media, Broadcast Media/Electronic Communication Networks, Digital Media, Electronic Media, Hypermedia, Mass Media, Multimedia, Print Media, Recording Media, Social Media Media Used In Computer Computing Media/Data Storage Devices, Application Software OWNER Who is the owner of the process? MODELS Ownership Map Ownership Matrix Ownership Model Business Model Level 1-3 Information Object ROLES Which business roles works with the process? MODELS Roles Map Roles Matrix Roles Model Information Object PROCESS COMPLIANCE Which process needs to be compliant? MODELS Compliance Map Compliance Matrix Compliance Model Information and Data Object PROCESS MEASUREMENT How is the process measured? MODELS Measurement Map Measurement Matrix Reporting Model Business and Information Object DATA Which data are used, modified and/or produced? MODELS Data Map Data Matrix Data Model Information and Data Object PLATFORM Which platform is used to enable the process? MODELS Platform Map Platform Matrix Platform Model Information and Data Object SERVICE Which service is created by or needed for the process? MODELS Service Map Service Matrix Service Model Business and Information Object PROCESS FLOW Which process proceeds and follows? MODELS Flow Map Flow Matrix Flow Model Business, Information and Data Object PROCESS RULES Which rules govern the process? MODELS Rules Map Rules Matrix Rules Model Information and Data Object APPLICATION What kind of application enables and automates the process? MODELS Application Map Application Matrix Application Model Business, Information and Data Object CHANNEL Which channel is being used to deliver the process? MODELS Channel Map Channel Matrix Channel Model Business, Information and Data Object MEDIA With which media does the process interact? MODELS Media Map Media Matrix Media Model Business, Information and Data Object PROCESS DECOMPOSITION Process Area Process Group Business Process Process Step Process Activity Events Gateways Management Process Main Process Supporting Process MODELS Process Map Process Matrix Process Model INFRASTRUCTURE What kind of infrastructure enables the process execution? MODELS Infrastructure Map Infrastructure Matrix Infrastructure Model Information and Data Object C A L L/O U T P U T M E C H A N IS M M E C H A N I S M M E C H A N I S M M E C H A N I S M I N P U T / C A L L C O N T R O L M E C H A N IS M C O N T R O L C O N T R O L I N P U T / C A L L C A L L / O U T P U T C O N T R O L M E C H A N I S M C O N T R O L C A L L REQUIREMENT & GOAL What is the requirement and goal of the process? MODELS Strategy Map, Requirement Map, Stakeholder Map, Strategy Matrix, Requirement Matrix, Value Model, Performance Model Business Object OBJECTS What kind of objects are used with the process? MODELS Object Map Object Matrix Object Model Business, Information and Data Object Business Perspective Marketing Channel, Sales Channel, Distribution Channel, Service Channel, Channel Partner Technology Perspective Communication Channel Digital Image/Screen Channel Programming Channel Broadcasting Channel, I/O Channel, Audio Channel Automated Task* Automated Task* Rule* Flow Ruleset* Decision Table* (Value and Performance) Decision Table* Ruleset* Rule Flow* Manual Task User Task* Send Task* Receive Task* Send Task* Receive Task* Mapping Task* Notification Task* (Process and Service) Rule* Rule* Flow Ruleset* Decision Table* Rule Script* Rule Script* Ruleset* Ruleset* Rule Flow* Rule Flow* Notification Task* Reporting Task* Mapping Task* Reporting Task* Script Task Script Task Rule Task Rule Task Rule Task Manual Service Task Automated Service Task Automated Service Task Automated Task* Mapping Task* Reporting Task* Script Task Rule Task Automated Service Task Annotation Marker* Ad Hoc Marker Sub-process Marker* Parallel MI Marker* Sequential MI Marker Loop Marker Sub-process Marker* Parallel MI Marker* Sequential MI Marker Loop Marker Compensation Data Object* Data Object* Data Store Data Store OUTPUT Data Output INPUT Data Input OUTPUT Data Output INPUT Data Input OUTPUT Data Output INPUT Data Input Collection of Data Objects* Collection of Data Objects* Collection of Business Objects INPUT Business Input OUTPUT Business Output Information Output OUTPUT Information Input INPUT Business Store Information Output OUTPUT Information Input INPUT Information Store Collection of Information Objects Collection of Business Objects Collection of Information Objects Business Object Information Object Business Object Information Object Escalation (start) Timer Signal (start) Escalation (end) Error (start) Signal (end) Multiple (start) Link (start) Multiple (end) Cancel (start) Cancel (end) Compensation (end) Compensation (start) Conditional Error (end) Parallel Multiple Terminate Link (end) Escalation (start) Timer Signal (start) Escalation (end) Error (start) Signal (end) Multiple (start) Link (start) Multiple (end) Cancel (start) Cancel (end) Compensation (end) Compensation (start) Conditional Error (end) Parallel Multiple Terminate Link (end) Escalation (start) Timer Signal (start) Escalation (end) Error (start) Signal (end) Multiple (start) Link (start) Multiple (end) Cancel (start) Cancel (end) Compensation (end) Compensation (start) Conditional Error (end) Parallel Multiple Terminate Link (end) Escalation (start) Timer Signal (start) Escalation (end) Error (start) Signal (end) Multiple (start) Link (start) Multiple (end) Cancel (start) Cancel (end) Compensation (end) Compensation (start) Conditional Error (end) Parallel Multiple Terminate Link (end) Gateway* Exclusive Gateway Parallel Gateway* Complex Gateway Parallel Event-based Gateway Exclusive Event-based Gateway Inclusive Gateway Event-based Gateway* Gateway* Exclusive Gateway Parallel Gateway* Complex Gateway Parallel Event-based Gateway Exclusive Event-based Gateway Inclusive Gateway Event-based Gateway* Gateway* Exclusive Gateway Parallel Gateway* Complex Gateway Parallel Event-based Gateway Exclusive Event-based Gateway Inclusive Gateway Event-based Gateway* Gateway* Exclusive Gateway Parallel Gateway* Complex Gateway Parallel Event-based Gateway Exclusive Event-based Gateway Inclusive Gateway Event-based Gateway* BUSINESS LAYER APPLICATION LAYER DATA LAYER TECHNOLOGY LAYER * = Item is available in SAP NetWeaver v7.2+ and in Adobe iGrafx Process Tool OBJECTS ACTIVITIES EVENTS GATEWAYS TASKS • Ability to rapidly change Business Processes in response to business events and opportunity. • Ability to respond to changes in regulatory requirements and industry standards. • Being more advanced and innovative in the marketplace. • More agility to enter new businesses. • Integrate Stakeholder Management requirements and thereby the Strategic Business Objectives (Business Goals) and Critical Success Factors into the Business Processes. • Enable Business Model innovation and transformation with Business Process optimization and innovation. • Integrate the scorecards into the process measurements, monitoring and controlling. • Integrate the strategy map of the company and develop value drivers and performance drivers that can be integrated into the process measurements. • Identified Performance Drivers. • Cost reduction. • Reduced cost per transaction. • Increased customer satisfaction. • Automated decision making. • Improved regulatory compliance. • Reduced risk. • Reduced waste / scrap. • In support of ISO 9000 certification. • Support outsourcing. • Innovations in products and services and business process. • New business models and the ability to change these rapidly in the Business Processes. • Faster response to service requests. • Superior process collaboration — internally and externally. • Better facilitation of mergers and acquisitions or divestitures. • Reducing the time it takes to respond to new business requirements. • Enabling the right level of service and information need. • Develop and automate the Business Capabilities/ Competencies. • Better information sharing and collaboration across LOB. • Higher productivity per person. • Higher employee satisfaction. • Reduced FTE’s - fewer people needed. • Improved coordination (cross-functional). • Improved organization agility and flexibility. • Automated reporting on worker performance. • Bridge geographically dispersed workers. • Staff reduction. • Improved productivity through process automation, workflows and business rules. • Improved, near real-time responsiveness to out-of-bounds conditions and KPI’s. • Elimination of errors, risk, waste, non-value-added activities and variation. • Faster time to market. • Faster production cycle time. • Reducing the level of process complexity involved. • Improved quality/reduced errors. • Reduced number of steps. • Increased process efficiency/productivity. • Continuous process improvement. • Improve process quality/consistency/compliance. • Automate administration tasks. • Better reporting of process performance/executive dashboards. • Ability to re-use processes (sub-routines). • Flexible/agile processes. • Increased security (e.g. access only available through process interface). • Process simulation (e.g. pre-emptive bottleneck prevention). • Expanded customer and partner involvement. • Component and process re-use. • Cost reduction. • Cost reduction with Best Practice use. • Reduced cost per transaction. • Enabling the right level of service and information need. • Higher implementation productivity. • Improved coordination (cross-functional). • Higher productivity per person. • Ability to apply Agile implementation approach. • Process simulation (e.g. pre-emptive bottleneck prevention). • Elimination of errors, risk, waste, non-value-added activities, and variation. • Faster time to market. • Faster production cycle time. • Reducing the level of process complexity involved. • Improved quality/reduced errors. • Reduced number of steps. • Increased process efficiency/productivity. • Increased security (e.g. access only available through process interface). • Better application integration. • Shared work queues. • Accelerate deployment of new applications. • Costs of ongoing process maintenance, administration and governance. • Change and increasing process complexity driven by business events. • Lower business operating cost through process standardization and integration. • Identifying unnecessary duplication and cost. • Define the right level of Continuous Improvement & Process Lifecycle Management. • Enabling external users. • Application integration. • Cost-effective integration inside the firewall. • Shared work queues. • Accelerate deployment of new applications. • Cost-effective integration outside the firewall. • Adding “State” to stateless applications. • Increased process efficiency/productivity. • Continuous process improvement. • Improve process quality/consistency/compliance. • Automate administration tasks. • Support outsourcing. • Reduced cost per transaction. • Increased customer satisfaction. • Automated decision making. • Improved regulatory compliance. BUSINESS VALUE TECHNICAL VALUE Organizational Context Process Context Technical Context Cost of Implementation Technical Context Cost of Operations Strategic Context INPUT Task Looped Sub-process Call Activity Manual Task Send Task Multi Instance Task (Parallel) Ad Hoc Sub-process Sub-process Group Event Sub-process Collection of Information Objects End Event Exclusive Gateway Parallel Gateway Parallel Gateway Message End Event Signal End Event Condition Reporting Task Decision Table Rule Task Flow Ruleset Attached Intermediate Event Error End Event Conditional Start Event Parallel Multiple Intermediate Event Link Intermediate Event Message Flow Notification Message Received Start Event Timer Intermediate Event Data Object Escalation End Event Link Intermediate Event Collection of Business Objects End Event Attached Intermediate Timer Event Pool Pool (Black Box) Competency Role Competency Role Automated Task Automated Service Task Event-based Gateway Message Received Intermediate Event © Copyright Value Team ApS

OUTPUT Information Output © Copyright Value Team ApS...Business Output Is the business result of the entire progression. A kind of output param-eter. Business Store Is a place where

  • Upload
    others

  • View
    8

  • Download
    0

Embed Size (px)

Citation preview

Page 1: OUTPUT Information Output © Copyright Value Team ApS...Business Output Is the business result of the entire progression. A kind of output param-eter. Business Store Is a place where

© Value Team ApSA part of the Process Reference Framework. For more information visit www.LeadFrameworks.com.EAD [email protected]

WEBSITEwww.ValueTeam.biz

INPUT

OUTPUTOUTPUT

INPUT

OUTPUT

INPUT

Gateways

Pools, Lanes, Business Competencies and FlowsProcess, Workflow and Collaboration

Introduction Decomposition & Composition of a Process

Interaction Model

Tasks and Activities Conversation Diagrams

Choreographies

Events How to use Notation Artifacts in Layered ArchitectureService Model

NoneUntyped events, indicatestart point, state changesor final states.

A Taskis a unit of work, the job to be performed. Whenmarked with a (+) symbol it indicates a sub-process,an activity that can be defined.

Below is an example of a public process diagram in a collaboration

Example of a process workflow and collaboration diagram

Below is an example of the LEAD Blueprinting Approach

Below is an example of the Business View and Process View

Below is an example of a private process diagram in a collaboration

Task

Transaction

Event Sub-process

Call Activity

A Transactionis a set of activities that logically belong together; itmight follow a specified transaction protocol.

Event-basedRepresents a branching point in the process where thealternative paths that follow the gateway are based onevents that occur.

An Event Sub-processis placed into a process or sub-process. It is activatedwhen its start event gets triggered and may interruptthe higher level process context or run parallel (non-interrupting) depending on the start event.

A Call Activityis a wrapper for a globally defined task or processreused in the current process. A call to a process ismarked with a (+) symbol.

Standard(start) Catching Throwing

Standard(end)

Eventsub-processinterrupting

Eventsub-process

non-interrupting

Boundaryinterrupting

Boundarynon-interrupting

Start Event

CaughtMessage Start Thrown Message End

Intermediate Event End Event

Objects

MessageReceiving and sendingmessages.

TimerCyclic timer events, pointsin time, time spans ortimeouts.

EscalationEscalating to a higherlevel of responsibility.

ConditionalReacting to changedbusiness conditions orintegrating business rules.

LinkOff-page connectors. Twocorresponding link eventsequal a sequence flow.

ErrorCatching or throwingnamed errors.

CancelReacting to cancelledtransactions or triggeringcancellation.

CompensationHandling or triggeringcompensation.

SignalSignalling across differentprocesses. A signal throwncan be caught multiple times.

MultipleCatching one out of a set ofevents. Throwing all eventsdefined.

Parallel MultipleCatching all out of a set ofparallel events.

TerminateTriggering the immediatetermination of a process.

What are events?The concept of an Event and its classification are basic modelling principles when compared to BPMN events, as there are literally tons of event types and various ways to classify them. The Event concept is fundamental to BPMN, as it allows to describe processes in an event-driven manner. In general, an Event is something that happens during the course of a process. Events affect the flow of the model and usually have a cause (trigger) or an impact (result). There are three major categories of events, depending on how they affect the workflow of the process:• A Start Event begins the process flow and to avoid confusion, only one Start Event for a process is preferred. PO (Production Order) Received is a Start Event, triggered by the arrival of a

Retailer PO (Production Order) message.• An Intermediate Event indicates something that happens between the start and end of a process. Such events are usually related to intermediate messages sent or received. Production Order

Transferred is an Intermediate Event.• An End Event indicates where a path in the process will end. As many End Events as needed are allowed, as the process may end in many ways. Within our sample, Correction(s) Request Sent is an

End Event.

Although there are few generic event types without explicit triggers and results, these concepts are precisely the reasons why events multiply so happily. The kind of event triggers and results are indicated by small icons inside their symbols. In order to see the wood from the trees however, we will use only one kind of a trigger and result, namely a message. Two of the presented event examples have a small message icon inside. In BPMN-speak and in line with its conventions, PO Received (Production Order Received) Start Event catches the incoming Retailer PO message and the icon is transparent. Produc-tion Order Transferred Intermediate Event throws the Production Order message and this in turn is indicated by a black icon.

Business Process Management - Lessons Learned

• Pool: A Pool represents a Participant in a process. It alsoacts as a graphical container for partitioning a set of activities from other Pools, usually in the context of B2B situations.

• Lane: A Lane is a sub-partition within a Pool and willextend the entire length of the Pool, either vertically or horizontally. Lanes are used to organize and categorize activities.

• Business Competency: A Business Competencyrepresents the area of business in which the process takes part. It is essential to reflect which part of a company’s business mechanics are directly involved in the flow within the Business Process Diagram (BPD).

What are pools, lanes and business competencies?The LEAD Methodology based on BPMN 2.0 utilizes the concept of both Pools, Lanes, and Business Competencies as a mechanism to organize activities into separate visual categories in order to illustrate different functional capabilities or responsibilities. The LEAD BPMN supports swimlanes with three main constructs. The three types of swimlane objects are:

• Sequence Flow: A Sequence Flow is represented by asolid line with a solid arrowhead and is used to show the order (the sequence) that activities will be performed in a process.

• Message Flow: A Message Flow is represented by adashed line with a solid arrowhead and is used to show the flow of messages between two separate process Participants (business entities or business roles) that send and receive them.

• Association Flow: An Association Flow is representedby a dotted line and is used to associate text and other artifacts with flow objects. Association Flows are used to show the inputs and outputs of activities.

• Data Association Flow: A Data Association Flow isrepresented by a dotted line with a solid arrowhead and is used to associate data (electronic or non-electronic) with flow objects. Data Associations are used to show the inputs and outputs of activities.

What are flows?Flow Objects are connected together in a diagram to create the basic skeletal structure of a business process. There are four connecting objects that provide this function. These connectors are:

Pools, lanes and business competencies represent responsibilities for activities in a process.

The order of message exchanges can be specified by combining message flow and sequence flow.

A Sequence Flow can travel freely within a pool, but cannot cross its boundaries.A Message Flow can be used to connect process elements residing within different pools, as well as to connect pools as such. However, it cannot be used to connect elements of the same process, i.e. contained within one pool. A Message Flow arrow has a circle as a starting point.An Association Flow is used to associate an artifact or text to a flow object.A Data Association Flow is used to associate data elements to activities, processes and global tasks.

What are gateways?Gateways are used to control how process paths converge and diverge within a process. In other words, they are decision points concerning further process flow. The term ‘Gateway’ implies that there is a mechanism that either allows or disallows passage through the Gateway. Again, there are plenty of Gateway types, but only two of them will be utilized in the LEAD case. An Exclusive Gateway is used to create alternative paths within a workflow of the process. This is basically the “OR” logical operator, as for a given process instance only one of the paths can be selected. A ‘PO OK?’ is an example. A Parallel Gateway is used to create or to combine parallel flows and acts as an “AND” logical operator. Obviously, a Parallel Gateway initiates parallel paths without checking any conditions, therefore it is not labeled. Such a Gateway follows Check Stock Levels Sub-process.

What are choreographies?A Choreography model is one of the types of models to specify choreographies in BPMN. It consists of choreog-raphy tasks and sub-processes and common BPMN elements, such as gateways and events. A Choreogra-phy does not only describe what a business process does, but also defines how individual processes interact with each other. In short, it depicts all the processes and their required interactions in a business process diagram. However, unlike BPMN’s process, it doesn’t belong to any pool.

A Choreography Taskrepresents an Interaction (Message Exchange) between two Participants.

A Sub-Choreographycontains a refined choreogra-phy with several Interactions.

A Call Choreographyis a wrapper for a globally defined Choreography Task or Sub-Choreography. A call to a Sub-Choreography is marked with a (+) symbol.

What Are Conversation Diagrams?The BPMN Conversation Diagram shows the conversations between the participants, and shows them as conversation objects (hexagons) without showing the individual message flow, which can go back and forth within a conversation.

A Conversationdefines a set of logically related message exchanges. When marked with a (+) symbol it indicates a Sub-Conversation, a compound conversation element.

A Call Conversationis a wrapper for a globally defined Conversation or Sub-Conversation. A call to a Sub-Conversation is marked with a (+) symbol

A Conversation Linkconnects Conversations and Participants.

Business ObjectRepresents a business object like product, employee, customer, partner, service, etc.

Collection of Business ObjectsRepresents a collection of business objects like products, employees, customers, partners, services, etc.

Business InputIs an external input for the entire business function and/or business service. A kind of input parameter.

Business OutputIs the business result of the entire progression. A kind of output param-eter.

Business StoreIs a place where the business object resides.

Information ObjectRepresents a container of information about a real-world object like a person, an employee, a product or a service, etc.

Collection of Information ObjectsRepresents a collection of information objects about real-world objects like people, employees, products or services, etc.

Information InputIs an external input for the entire information function and/or information service. A kind of input parameter.

Information OutputIs the information result of the entire progression. A kind of output parameter.

Information StoreIs a place where the information object resides.

Data Object*Represents a container of information within the flow of the process, such as business documents, e-mails, or letters.

Collection of Data Objects*Represents a collection of data objects, e.g. a list of order items.

Data InputIs an external input for the entire process. A kind of input parameter.

Data OutputIs the data result of the entire process. A kind of output parameter.

Data StoreIs a place where the process can read or write data, e.g. a database or a filing cabinet. It persists beyond the lifetime of the process instance.

What are data objects?A Data Object is considered an artifact and not a flow object. They are consid-ered an artifact because they do not have any direct effect on the Sequence Flow or Message Flow of the process, but they do provide information about what the process does. That is, how documents, data, and other objects are used and updated during the process. While the name “Data Object” may imply an electronic document, they can be used to represent many different types of objects, both electronic and physical.

What are information objects?An Information Object is used to specify information about real-world objects (people, employees, products or a sales order, etc.) and therefore it is the digital representation of an existing entity within an Information System e.g. Oracle ERP and/or SAP. It encompasses both the business information (in the form of functions and method) and the application information (in the form of attributes) of this entity. Information objects can be found, and therefore modelled, in business functions, business services and within the process itself.

What are business objects?A Business Object is the term used to express real-world objects like people, employees, products or a sales order, customers and revenue. In terms of modelling, business objects uses a patented semantic layer that shields users from the complexities of table names and relationships. Once the semantic layer has been defined, users work with familiar real-world business objects such as products, customers and revenue.

What is the link between the service model and the process model?This pattern generally describes how to establish remote write operations on services asynchronously. This decouples the frequently time-consuming write operation from the process flow on the consumer side.Asynchronous operations and communication may be useful when method calls are invoked across process boundaries via remote mechanisms. In particular, when calling web services using SOAP or similar remote protocols, network latency and bandwidth restrictions create communication bottlenecks. Asynchronous com-munication therefore will not hinder the process flow, but will just initiate the remote operation and processing of data.

What is a service task?A Service Task is a Task that uses some sort of service, which could be a web service or an automated application. A Service Task object shares the same shape as the Task, which is a rectangle that has rounded corners. However, there is a graphical marker in the upper left corner of the shape that indicates that the Task is a Service Task. A Service Task is a rounded corner rectangle that must be drawn with a single thin line and includes a marker that distinguishes the shape from other Task types.

The Service Model

What is a process, process workflow and process collaboration?BPMN defines a process as a sequence or flow of Activities in an organization, with the objective of carrying out work. In BPMN, a process is depicted as a graph of flow elements, which are a set of Activities, Events, Gateways, and Sequence Flows. Thereby the sequence of flows should follow the organizational workflow, where a process flow can be depicted either on a Collaboration Diagram, generally if there are several pools, or on a Business Process Diagram, if there is only one pool. In any case, a process must be fully embedded within one pool and it can communicate with other pools only via message exchanges.

What are interaction models?Interaction models are new in BPMN 2.0. They allow to model B2B cooperations. Business services are characterized by interactions between businesses and their customers and partners. They are usually agreed or assumed ahead of time, and do not detail the intemal activities of the participants. Agreements determine what information, goods, or personnel are needed by whom and at what time, how complaints and unusual situations are handled, and so on. The interactions might be very short from start to end, or take place over a long period.

The process to the left could be public, because it only sends and receives messages.

The process to the left shows a possible private process containing Activities that are not interactive and unsually not shown to other Participants

A holistic way of working with Process Mapping, Process Architecture, Process Notations and Process ModellingProcess Reference FrameworkEAD

Send Order Status

Search InternalRecords

Evaluate Credit

Receive Credit ScoreRequest Credit Score

Book Room

Multi-InstancePool

(Black Box)

Pool(Black Box)

Pool(Black Box)

Conversation

Sub-Conversation

Order DrinksIdentify Customer

Requirements

User Task

Write Poll

Task

Task

Credit Request

Credit Request Credit Response

Customer Order

Customer Order Order Response

Credit Response

Order Response

Credit Agency

Customer

Credit Agency

Buyer

Co

mp

ete

ncy

Co

mp

ete

ncy

Ro

leR

ole

Poo

lPo

ol

Co

mp

ete

ncy

Co

mp

ete

ncy

Ro

leR

ole

Poo

lPo

ol

Participant A

Choreography Task

Participant A

Participant B

Participant B

Participant C

Sub-Choreography

Participant A

Participant B

Call Choreography

Poo

l

Co

mp

ete

ncy

Ro

le

Lan

eLa

ne

ManualService Task

AutomatedService Task

Poo

lPo

ol

Co

mp

ete

ncy

Ro

le

Co

mp

ete

ncy

Ro

le

What are tasks and activities?In general, an Activity is a generic term for work that a company performs in a process. Activities are thus the executable elements of a process. The basic activity categories are Tasks and Sub-processes. A Task is an elementary Activity used when the work in the process is not broken down to a finer level of Process Model detail.

Activity MarkersMarkers indicate executionbehavior of activities:

Sub-process Marker*

Loop Marker

Parallel MI Marker*

Sequential MI Marker

Ad Hoc Marker

Compensation Marker

BPMN Task TypesType specify the nature of theaction to be performed:

* = Is also available in SAP Netweaver 7.2+MI = Multiple InstanceAll task types and activities are available in iGrafx

Send Task*

Receive Task*

User Task*

Manual Task

Rule Task

Manual Service Task

Script Task

Annotation Marker*

What is RACI mapping and how is it used?RACI is an acronym derived from the four key responsibilities most typically used: Responsible, Accountable, Consulted, and Informed. The RACI model describes the participation by various roles in completing tasks or deliverables for a project or business process. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and processes.

RACI Modelling PrincipleAt least one ‘R’ has to be assigned to each activity, but several ‘R’s are possible. Only one ‘A’ can be assigned to an activity. The same role might be concurrently ‘R’ and ‘A’. If there is only one ‘R’ but no ‘A’ assigned to an activity, it is assumed that ‘R’ is also ‘A’ for that activity.

Business Process RepresentationBusiness process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities.

BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEAD Framework and will be subject to continuous improvement and development.

History of Business Process Modelling Notations • March 2001: BPMI members began discussing the idea of creating a notation to

go along with the executable BPML. • August 2004: BPMN 1.0 specification was released to the public. • Now maintained by the Object Management Group (OMG). • January 2011: BPMN 2.0 specification was released to the public.

The LEAD Framework further developed upon the BPMN 2.0 specification to include linkage to: • Business Competencies (January 2011). • Service Mapping (January 2011). • Interaction Models (March 2011). • RACI Mapping (May 2011). • Value Mapping (November 2011). • SAP Netweaver connection (January 2012). • SAP Solution Manager connection (February 2012). • Incorporation of LEAD BPMN principles into Adobe iGrafx (November 2012).

ERP implementation in your Business Model, Service Model, and Operating ModelMany ERP implementations today are supporting business innovation and transformation and are looking to change either their Business Model, Service Model, and/or their Operating Model. As a result of this, the Actors, Roles, Functions, Processes and Controls will also change – but not all existing processes support the wanted target models. Therefore, without a confident ‘As-Is’ business process baseline, the mapping of processes and activities to SAP functional-ities has to be reverse engineered from the basis of the Target Business Model (TBM), Target Service Model (TSM) and/or Target Operating Model (TOM). The goal is to review all available documentation and process flows (APQC, SCOR, LEAD Process MAP, SAP Solution Manager, etc.) to leverage all existing work-flows, standards and best practices that, while considering the core competitive, core differentiating and non-core competencies where the last mentioned need the support of the generic ‘best practice - vanilla’ implementation, is maintaining the project goals of realized optimal transformation and cost savings for the organization. Where the organization has core competitive and/or core differentiating competencies, and therefore best practice can't be applied, process mapping that captures the organization’s own practice should be undertaken to ensure value creation.

Business Process DefinitionA structure of related activities designed to create results for the organization. This structure of related activities can be mapped into process models. Relating these structures in a different sequence in order to optimize, re-engineer or innovate will create a new result for the organization:

1) the Main Processes, which consists of the delivery of your main business. Main Processes are the essential processes of the business that create value for the external customer. They are business strategy, product delivery, and customer support type of processes.2) the Supporting Processes, which consists of processes that support the business. Supporting Processes are all the processes that supply resources to the other processes and largely are non-value adding to customers. They generally are the Human Resources, Supply Management, and Information Technology, to name a few.3) the Management Processes, which consists of processes that manage the business. Management Processes are all the processes that set direction (e.g. objectives, goals, etc.), plan, forecast, and control (monitor, measure and govern) the performance or execution of any type of activity.

Business Process DocumentationBusiness process documentation is composed of two parts. The first part of the process documentation should cover a list of all parts of the process. It will describe the process and possibly information, such as the ownership (business competency), the hierarchy of the process, the objectives, the measurements, etc., but it will also describe all of the activity details, such as the inputs, outputs, roles and responsibilities, as well as the decision points and events. The second part consists of the visual graphic of the process, also known as the Process Model, and provides a visual representation of all the activities, interactions and workflow controls, such as decision points and exception paths.

Process Modelling RulesThe activity of modelling a business process usually predicates a need to change processes or identify issues to be corrected. This transformation may or may not require IT involvement, although that is a common driver for the need to model a business process. Change Management programmes are desired to put the processes into practice. Process modelling addresses the process aspects of an Enterprise Business Architecture, leading to an all encompassing Enterprise Architecture. The relationships of a business’ processes in the context of the rest of the enterprise systems (e.g. data, organizational structure, strategies, etc.) create greater capabilities in analyzing and planning a change. Process modelling has always been a key aspect of business process reengineering, and Continu-ous Improvement approaches seen in the LEAD Frameworks, Methods and Approaches.

Notation Mapping LevelThe BPMN specification defines three levels of BPMN mapping:1) Descriptive Models

• Suitable for high level modelling - should be comfortable for analysts that have used flowcharts.• Working with basic set of BPMN elements.

2) Analytic Process Models• Contains the concepts most commonly used and covered in BPMN training.• Defines semantics and are subjects to its validation rules.

3) Common Executable Process Models• Focuses on the elements required for executable process models by adding XML underneath the shapes (new with BPMN 2.0).• Leads to automation using BPMS.

Business Process HierarchyBusiness processes can get quite complex and this makes it tough to model a very big process into just one graphical model. A process hierarchy is necessary to divide complex processes into smaller parts. A process hierarchy follows the "from abstract to concrete" principle. This means it provides information about the processes on different levels of granularity. Therefore it is possible to get information about the abstract value chain (e.g. Purchasing, Production, Sales) or about very specific process steps and their logical order (e.g. create customer, approve purchase order). A process hierarchy is defined by its levels and the information given in these levels. It is key to have a defined information base on each level (e.g. a process step is always performed by a specific role instead of an abstract organizational unit), otherwise process models will not be comparable at a later stage. The model to the right shows the Process Hierarchy Model and provides an example for each level - the Process Hierarchy Model consists of (at least) five process levels.

Process Level 1: Business Process Area (e.g. Demand-to-Close)A Business Process Area is a set of process areas with the same business goals, spanning the organization from end-to-end (sometimes extending out to business partners). Thus, an enterprise‘s entire Business Process Area (operating structure) is not a business process but rather a categorization and can therefore be depicted by its combined Process Group groups.

Process Level 2: Business Process Group (e.g. Demand Generation)A Process Group is not a Business Process either but a categorization as well, therefore a Process Group is a set of logically related Business Process Groups which has business processes within that performs to achieve a defined, measurable business outcome for a particular internal or external customer.

Process Level 3: Business Process (e.g. Lead Management)A Business Process is the first level of processes where all business processes follow a certain flow in order to accomplish the defined business outcome. They generally consist of discrete, highly encapsulated business operations.

Process Level 4: Business Process Step (e.g. Lead Distribution)A Business Process Step represents an operation of a business process that performs a defined function. The order of all business process steps illustrates the business logical flow followed in order to fulfill the purpose of the business process.

Process Level 5: Business Process Activity (e.g. Convert Lead to Opportunity)A Business Process Module is the smallest business relevant activity or function, which has no process level below. Modules can consist of a single or multiple tasks, performed in an application, ideally represented in a transaction and accessed via a specific user interface.

Reporting Task*

Automated Service Task*

Automated Task*

Mapping Task*

Notification Task*

Ruleset*

Flow Ruleset*

Rule*

Rulescript*

Rule Flow*

Decision Table*

Exclusive Gateway*When splitting, it routes the sequence flow to one of the outgoing branches. When merging, it awaits one incoming branch to complete before triggering the outgoing flow.

Gateway*Gateways are used to control how process paths converge and diverge within a process.

Event-based Gateway*Is always followed by catching events or receive tasks. Sequence flow is routed to the subsequent event/task which happens first.

Parallel Gateway*Is always followed by catching events or receive tasks. Sequence flow is routed to the subsequent event/task which happens first.

Inclusive GatewayWhen splitting, one or more branches are activated. All active incoming branches must complete before merging.

Complex GatewayComplex merging and branching behaviour that is not captured by other gateways.

* = Is also available in SAP Netweaver 7.2+.

Exclusive Event-based Gateway (instantiate)Each occurence of a subsequent event starts a new process instance.

Parallel Event-based Gateway (instantiate)The occurence of all subsequent events starts a new process instance.

Solution DevelopmentSolution standards, functions, rules,object development (e.g. business,

information and data)

Solution Documentation(Solution scenario, object

definition)Organizational Units

Master Data

Business Requirements

Process Scenarios

Business Processes

Object & Transactions(Function, Task and Services,

Collection of Objects, Object Storage)

System Information(Application Component)

Interfaces(Point 2 Point & Multiple Point 2 Point,

Object Input & Output)

Building sustainable assets through business blueprint in Solution Manager

Process Step

Process Activities

Process Step

ResponsibleRole(s) that carry (carries) out the activity.

RACI Responsibility Type

R

ACI

Description BPM Link Type

AccountableRole that is ultimately accountable for thesuccess of the activity and occupiesauthority to delegate its execution.

ConsultedRole(s) to be asked before/during carryingout the activity (two-way communication).

InformedRole(s) to be informed after/during theactivity is carried out (one-waycommunication).

Carries out

Is ultimatelyaccountable for

Has consultingrole in

Must be informedabout

Covered by Business

Content Quality

Foster high quality Process Models Support efficiency and effective modelling

Faithful to Business Reality

Complete

Sustainable

Content-wise Consistent

Covered by Business and IT

Structural Quality Modelling

Unambiguous/Clear

Easy-To-Read

Uniform

Comparable

Fast Enablement

Easy Modelling

Prevent Chaos in Distributed Modelling

Help Focus on Important Tasks

Formally Consistent

BU

SIN

ESS

LAY

ER

AP

PLI

CA

TIO

NLA

YE

RD

ATA

LAY

ER

TEC

HN

OLO

GY

LAY

ER

Application Services

Business Process Information Flow

Business Service FlowBusiness Competency Business Competency

Business Process

Application Services

Data ServicesData Services

Platform Services

Automated Service

Infrastructure Services

ManualService

Task

AutomatedService

Task

Strategy

Planning

Forecast

Budget

Value & Performance Management

BUSINESS COMPETENCY VIEWBUSINESS PROCESS

STANDARDIZATION VIEW BUSINESS MEASUREMENTS VIEW

Strategic

Management Process of Executives Strategic KPI’s and PPI’s

Main Process Standardization

Supporting Process Standardization

Control & Monitoring

Evaluation & Reports

Operational Plan

Policies, Rules & Guidelines

Administration

Measurements

Audits

Tactical

Tactical KPI’s and PPI’sManagement Process of Managers

Main Process Standardization

Executing

Operational Administration

Delivery

Operational Measurements

Processing

Operational Oversight

Operational Reporting

Operational

Operational KPI’s and PPI’sManagement Process of Employees

Main Processes Standardization

Supporting Process Standardization

Supporting Processes Standardization

BusinessServices Service Workflow

Level 3aBusiness Process

Level 4aProcess Steps

Level 5aProcess Activities

Business Workflow SAP IndustryValue Chain

SAP Value ChainElement

SAP BusinessScenario Group

Legacy Task

LegacyFunctionality

Legacy Services

SAP PortalScenarios

SAP PortalServices

SAP Product

SAPMeasurements

Financial Operational

SAPProcess Workflow

Business(Function)

Identify Business Model

Identify Business Goals Define Service Type

Use SAP ProcessReference content

Capture Value Drivers

Capture Performance Drivers

Identify Service Need

Process

(Macro-level)Function

(Micro-level)Function

SAPBusiness Scenario

SAPProcess Activity

SAPProcess Step

SAP ProcessConfiguration

Variant

Agile LEAD Blueprinting Approach Solution Manager and the LEAD Blueprinting Approach

ESRP ERP Solution Scenarios

Interoperability Solution Scenarios Legacy Solution Portfolio

delivers

supports

orchestrates,decomposes

orchestrates

supports

decomposes

consists of

belongs to

consists of

belongs to

belongs to

groups

consists of

belongs to

consists of

is a sequence of

is part of

is part of

is part of

is part of

covers

is measured by

is represented on

is used within

creates and uses

is composed of

has ais a variant of

Level 3bBusiness Process

Variant

Level 4bProcess Steps

Variant

Level 5bProcess Activities

Variant

Business Architecture Process Architecture SAP Information Architecture

= Business Layer Component = Application Layer Component = Technology Layer Component = Decomposition Component = Composition Component

BUSINESS COMPETENCYWhich business competency

uses the process?

MODELSOrganizational Chart

Competency MapCompetency Matrix

Business Model Level 1-3

Business and Information Object

Organizational ConstructBusiness Area

Business GroupBusiness FunctionBusiness Resource

Core Differentiating CompetencyCore Competitive Competency

Non-Core CompetencyCost

(Revenue)

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityEvents

Gateways

Application ComponentApplication ModuleApplication FeatureApplication Function

Application TaskApplication Service

GoalObjective

Performance IndicatorRequirement

Performance ExpectationPerformance DriverValue Proposition

Service ConstructService Delivery

Main ServiceSupporting Service

Service ProviderService Consumer

Service Tiers

Business ProcessProcess Step

Process ActivityGateways

Management ProcessMain Process

Supporting Process

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

PoliciesGuidelinesStandards

RegulationsGovernance

ControlsRisk Management

AuditEvaluationSecurity

Monitoring

Business Performance IndicatorBusiness KPI’s

Service Level AgreementProcess Performance Indicator

System MeasuresPerformance Measurement

Service MeasurementScorecardsDashboards

Cockpits

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ObjectInformation Object

Data ObjectInfrastructure Service

Business RuleService RuleProcess Rule

Application RuleData Rule

Security Rule

Business ProcessProcess Step

Process ActivityEvents

Management ProcessMain Process

Supporting Process

Business ProcessProcess Step

Process ActivityEvents

Gateways

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityEvents

Gateways

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityGateways

Business OwnerProcess OwnerService OwnerValue Owner

Performance ownerInformation OwnerApplication Owner

Data OwnerPlatform Owner

Infrastructure OwnerSecurity Owner

Compliance Owner

Platform DevicePlatform Service

Business RoleProcess Role

Data ComponentData Entity

Data Service

Business WorkflowValue Flow

Reporting FlowService Flow

Information FlowProcess Workflow

Application WorkflowScenarios

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

Business ProcessProcess Step

Process ActivityGateways

Management ProcessMain Process

Supporting Process

Media As CommunicationMedia Store, Advertising Media,

Broadcast Media/ElectronicCommunication Networks, Digital Media,

Electronic Media, Hypermedia, MassMedia, Multimedia, Print Media,Recording Media, Social Media

Media Used In ComputerComputing Media/Data Storage

Devices, ApplicationSoftware

OWNERWho is the owner of the

process?

MODELSOwnership Map

Ownership MatrixOwnership Model

Business Model Level 1-3

Information Object

ROLESWhich business roles works with

the process?

MODELSRoles Map

Roles MatrixRoles Model

Information Object

PROCESS COMPLIANCEWhich process needs

to be compliant?

MODELSCompliance Map

Compliance MatrixCompliance Model

Information and Data Object

PROCESS MEASUREMENTHow is the process

measured?

MODELSMeasurement Map

Measurement MatrixReporting Model

Business and Information Object

DATAWhich data are used, modified

and/or produced?

MODELSData Map

Data MatrixData Model

Information and Data Object

PLATFORMWhich platform is used to enable

the process?

MODELSPlatform Map

Platform MatrixPlatform Model

Information and Data Object

SERVICEWhich service is created by or

needed for the process?

MODELSService Map

Service MatrixService Model

Business and Information Object

PROCESS FLOWWhich process proceeds and

follows?

MODELSFlow Map

Flow MatrixFlow Model

Business, Information and Data Object

PROCESS RULESWhich rules govern the

process?

MODELSRules Map

Rules MatrixRules Model

Information and Data Object

APPLICATIONWhat kind of application enables

and automates the process?

MODELSApplication Map

Application MatrixApplication Model

Business, Information and Data Object

CHANNELWhich channel is being used to

deliver the process?

MODELSChannel Map

Channel MatrixChannel Model

Business, Information and Data Object

MEDIAWith which media does the

process interact?

MODELSMedia Map

Media MatrixMedia Model

Business, Information and Data Object

PROCESSDECOMPOSITION

Process AreaProcess Group

Business ProcessProcess Step

Process ActivityEvents

GatewaysManagement Process

Main ProcessSupporting Process

MODELSProcess Map

Process MatrixProcess Model

INFRASTRUCTUREWhat kind of infrastructure enables

the process execution?

MODELSInfrastructure Map

Infrastructure MatrixInfrastructure Model

Information and Data Object

CALL/OUTPUT

MECHANISM

MEC

HANI

SM

MEC

HAN

ISM

MEC

HANISM

INPUT/CALL

CONTROL MECHANISM CONTROL

CONTROL

INPU

T/C

ALL

CALL/O

UTPU

T

CONTRO

L

MECHANISM

CONTROL

CALL

REQUIREMENT & GOALWhat is the requirement and

goal of the process?

MODELSStrategy Map, Requirement Map,

Stakeholder Map,Strategy Matrix, Requirement

Matrix, Value Model,Performance Model

Business Object

OBJECTSWhat kind of objects are used

with the process?

MODELSObject Map

Object MatrixObject Model

Business, Information and Data Object

Business PerspectiveMarketing Channel, Sales Channel,

Distribution Channel, Service Channel,Channel Partner

Technology PerspectiveCommunication Channel

Digital Image/Screen ChannelProgramming Channel

Broadcasting Channel, I/OChannel, Audio Channel

Automated Task*

Automated Task*

Rule*

Flow Ruleset*

Decision Table*(Value and Performance)

Decision Table*

Ruleset*

Rule Flow*

Manual Task

User Task*

Send Task*

Receive Task*

Send Task*

Receive Task*

Mapping Task*

Notification Task*(Process and Service)

Rule*

Rule*

Flow Ruleset*

Decision Table*

Rule Script*

Rule Script*

Ruleset*

Ruleset*

Rule Flow*

Rule Flow*

Notification Task*

Reporting Task*

Mapping Task*

Reporting Task*

Script Task

Script Task

Rule Task

Rule Task

Rule Task

Manual Service Task

Automated Service Task

Automated Service Task

Automated Task*

Mapping Task*

Reporting Task*

Script Task

Rule Task

Automated Service Task

Annotation Marker*

Ad Hoc Marker

Sub-process Marker*

Parallel MI Marker*

Sequential MI Marker

Loop Marker

Sub-process Marker*

Parallel MI Marker*

Sequential MI Marker

Loop Marker

Compensation

Data Object*

Data Object*

Data Store

Data Store

OUTPUT Data Output

INPUT Data Input

OUTPUT Data Output

INPUT Data Input

OUTPUT Data Output

INPUT Data Input

Collection of Data Objects*

Collection of Data Objects*

Collection of Business Objects

INPUT Business Input

OUTPUT Business Output

Information OutputOUTPUT

Information InputINPUT

Business Store

Information OutputOUTPUT

Information InputINPUT

Information Store

Collection of Information Objects

Collection of Business Objects

Collection of Information Objects

Business Object

Information Object

Business Object

Information Object

Escalation (start)

Timer

Signal (start)

Escalation (end)

Error (start)

Signal (end)

Multiple (start)

Link (start)

Multiple (end)

Cancel (start)

Cancel (end)

Compensation (end)

Compensation (start)

Conditional

Error (end)

Parallel Multiple

Terminate

Link (end)

Escalation (start)

Timer

Signal (start)

Escalation (end)

Error (start)

Signal (end)

Multiple (start)Link (start)

Multiple (end)

Cancel (start)

Cancel (end)

Compensation (end)

Compensation (start)

Conditional

Error (end)

Parallel Multiple

Terminate

Link (end)

Escalation (start)

Timer

Signal (start)

Escalation (end)

Error (start)

Signal (end)

Multiple (start)

Link (start)

Multiple (end)

Cancel (start)

Cancel (end)

Compensation (end)

Compensation (start)

Conditional

Error (end)

Parallel Multiple

Terminate

Link (end)

Escalation (start)

Timer

Signal (start)

Escalation (end)

Error (start)

Signal (end)

Multiple (start)

Link (start)

Multiple (end)

Cancel (start)

Cancel (end)

Compensation (end)

Compensation (start)

Conditional

Error (end)

Parallel Multiple

Terminate

Link (end)

Gateway*

Exclusive Gateway

Parallel Gateway*

Complex Gateway

Parallel Event-based Gateway

Exclusive Event-based Gateway

Inclusive Gateway

Event-based Gateway*

Gateway*

Exclusive Gateway

Parallel Gateway*

Complex Gateway

Parallel Event-based Gateway

Exclusive Event-based Gateway

Inclusive Gateway

Event-based Gateway*

Gateway*

Exclusive Gateway

Parallel Gateway*

Complex Gateway

Parallel Event-based Gateway

Exclusive Event-based Gateway

Inclusive Gateway

Event-based Gateway*

Gateway*

Exclusive Gateway

Parallel Gateway*

Complex Gateway

Parallel Event-based Gateway

Exclusive Event-based Gateway

Inclusive Gateway

Event-based Gateway*

BU

SIN

ESS

LAYE

RA

PPLI

CA

TIO

N L

AYE

RD

ATA

LA

YER

TEC

HN

OLO

GY

LAYE

R

* = Item is available in SAP NetWeaver v7.2+ and in Adobe iGrafx Process Tool

OBJECTSACTIVITIES EVENTS GATEWAYSTASKS

• Ability to rapidly change Business Processes inresponse to business events and opportunity.

• Ability to respond to changes in regulatoryrequirements and industry standards.

• Being more advanced and innovative in themarketplace.

• More agility to enter new businesses.• Integrate Stakeholder Management requirements and

thereby the Strategic Business Objectives (Business Goals) and Critical Success Factors into the Business Processes.

• Enable Business Model innovation and transformationwith Business Process optimization and innovation.

• Integrate the scorecards into the processmeasurements, monitoring and controlling.

• Integrate the strategy map of the company anddevelop value drivers and performance drivers that can be integrated into the process measurements.

• Identified Performance Drivers.• Cost reduction.• Reduced cost per transaction.• Increased customer satisfaction.• Automated decision making.• Improved regulatory compliance.• Reduced risk.• Reduced waste / scrap.• In support of ISO 9000 certification.• Support outsourcing.

• Innovations in products and services and businessprocess.

• New business models and the ability to change theserapidly in the Business Processes.

• Faster response to service requests.• Superior process collaboration — internally and

externally.• Better facilitation of mergers and acquisitions or

divestitures.• Reducing the time it takes to respond to new business

requirements.• Enabling the right level of service and information

need.• Develop and automate the Business Capabilities/

Competencies.• Better information sharing and collaboration across

LOB.• Higher productivity per person.• Higher employee satisfaction.• Reduced FTE’s - fewer people needed.• Improved coordination (cross-functional).• Improved organization agility and flexibility.• Automated reporting on worker performance.• Bridge geographically dispersed workers.• Staff reduction.

• Improved productivity through process automation,workflows and business rules.

• Improved, near real-time responsiveness toout-of-bounds conditions and KPI’s.

• Elimination of errors, risk, waste, non-value-addedactivities and variation.

• Faster time to market.• Faster production cycle time.• Reducing the level of process complexity involved.• Improved quality/reduced errors.• Reduced number of steps.• Increased process efficiency/productivity.• Continuous process improvement.• Improve process quality/consistency/compliance.• Automate administration tasks.• Better reporting of process performance/executive

dashboards.• Ability to re-use processes (sub-routines).• Flexible/agile processes.• Increased security (e.g. access only available through

process interface).• Process simulation (e.g. pre-emptive bottleneck

prevention).• Expanded customer and partner involvement.

• Component and process re-use.• Cost reduction.• Cost reduction with Best Practice use.• Reduced cost per transaction.• Enabling the right level of service and information

need.• Higher implementation productivity.• Improved coordination (cross-functional).• Higher productivity per person.• Ability to apply Agile implementation approach.• Process simulation (e.g. pre-emptive bottleneck

prevention).• Elimination of errors, risk, waste, non-value-added

activities, and variation.• Faster time to market.• Faster production cycle time.• Reducing the level of process complexity involved.• Improved quality/reduced errors.• Reduced number of steps.• Increased process efficiency/productivity.• Increased security (e.g. access only available through

process interface).• Better application integration.• Shared work queues.• Accelerate deployment of new applications.

• Costs of ongoing process maintenance,administration and governance.

• Change and increasing process complexity driven bybusiness events.

• Lower business operating cost through processstandardization and integration.

• Identifying unnecessary duplication and cost.• Define the right level of Continuous Improvement &

Process Lifecycle Management.• Enabling external users.• Application integration.• Cost-effective integration inside the firewall.• Shared work queues.• Accelerate deployment of new applications.• Cost-effective integration outside the firewall.• Adding “State” to stateless applications.• Increased process efficiency/productivity.• Continuous process improvement.• Improve process quality/consistency/compliance.• Automate administration tasks.• Support outsourcing.• Reduced cost per transaction.• Increased customer satisfaction.• Automated decision making.• Improved regulatory compliance.

BUSINESS VALUE TECHNICAL VALUE

Organizational Context Process ContextTechnical Context

Cost of ImplementationTechnical ContextCost of OperationsStrategic Context

INPUT Task

Looped Sub-process

CallActivity

Manual Task

Send Task

Multi InstanceTask (Parallel)

Ad HocSub-process

Sub-process

Group

Event Sub-process

Collection ofInformation Objects

End Event

ExclusiveGateway

ParallelGateway

ParallelGateway

MessageEnd Event

Signal End Event

Condition

ReportingTask

DecisionTable

Rule Task

Flow Ruleset

AttachedIntermediate

Event

ErrorEnd Event

ConditionalStart Event

ParallelMultiple

IntermediateEvent

LinkIntermediate

Event

Message Flow

Notification

Message ReceivedStart Event

TimerIntermediate Event

Data Object EscalationEnd Event

LinkIntermediate Event

Collection ofBusiness Objects

End Event

AttachedIntermediateTimer Event

Poo

l

Pool (Black Box)

Co

mp

ete

ncy

Ro

le

Co

mp

ete

ncy

Ro

le

Automated Task

AutomatedService Task

Event-basedGateway

Message ReceivedIntermediate Event

© Copyright Value Team ApS