Business_Process_Modeling_Training.ppt

<Insert Picture Here>
Fusion Business Process Model Training
BPE Team

Agenda
• Oracle Business Process Modeling Overview
– Oracle Business Process Modeling and Analysis Overview
– Oracle Business Process Body of Knowledge
– BPM and APM Lifecycle
– Business Process Model Architecture
• Creating a Fusion BPM Task Flow Step-by-Step
• Visio How To’s for Common Modeling Errors
• AIA Business Process Modeling Overview
• Information on BPE Team
Last Updated 02/23/2011 © 2010 Oracle Corporation – Proprietary and Confidential 3

Oracle Business Process
Modeling Overview

Oracle Business Process Modeling and Analysis
Overview
Our Understanding of Business Process
Management
• Business Process Management (BPM) includes a set of activities
that organizations perform to either optimize their business
processes or adapt them to new organizational needs.
• Important elements include business process modeling and
analysis (BPA), orchestration (BPEL), and business activity
monitoring (BAM).

Overview
What is the Challenge?
• Coordinating business processes is not simple or linear as might
be portrayed in the world of traditional task management.
• Business is constantly changing, messy, unordered and chaotic;
work activities and tasks have to be processed in parallel.
• Coordination requires the spawning and asynchronous execution
of nested tasks and parallel activities.
• And it is not just tasks that occur in parallel, but decision-making,
distributed computation and the movement of information within
the company and across the value chain.

Overview
What is the Answer?
• The best way to understand how your business is running - is to
understand your processes.
• The first step in doing that is to model your business processes.
• Oracle has created and delivered business process models for
those processes supported by Oracle Application Integration
Architecture. These business process models will enable you to
see and understand how Oracle Application Integration
Architecture provides application integration solutions for your
business processes.

Oracle Business Process Body of Knowledge

BPM and Fusion APM Lifecycle
System
Test
Oracle
Customers & Partners Application
Implementation
Application
Management
User
Training
BPM
All Levels
Fit-gap Analysis
Process Simulation
Configuration
Extensions/Customizations
BPM
All Levels
Work Procedures
Training Material
BPM
All Levels
Operations
Monitoring
Configuration/Change
Field
Readiness
Application
Maintenance
BPM Level
3 - 4
Bug
Enhancement
BPM
All Levels
Demo
Training
Documentation
Reference
Models
Requirements
Analysis
BPM
Level 3
BRD
Requirements
Application
Design
BPM
Level 3 – 4
Page Flow
Usability Test
Fnctl Design
Tech Design
Design
Application
Development
BPM
Level 3- 4
Code
Unit Tests
Documentation
Construct
Functional
& Market
Assessment
Strategy
Product
Scope
Release
Planning
BPM
Level 0 – 2
Analysis
and
Communication
Launch Maintenance
BPM
Level 3 – 4
System Test
Upgrade Test
Migration Test
Integration Test
Integration
& Test
BPM
Level 0 –2
Analysis
and
Communication

 Idea
 Concept
 High Level Conceptual Design
 Scope
 Conceptual Design with Roles
 Functional Design
 Technical Design
 Build
 Test
 Implement
 Train
 Deploy
 Manage
 Simulate
 Re-engineer
 Governance
 Execute
 Upgrade
Business Process
Lifecycle
Communication: High-Level Steering Committee Presentations
Conceptual Level Models (L0, L1, L2)
BRD Business Process Context
Release Planning Input; Annotation for “In Scope”, “Future Scope”
Conceptual Task Flow Model (L3)
FDD; Refined L3 Models; Conceptual EBOs/EBSs
Finished Publishable Models that Correspond to Delivered Solutions
Test Scenarios for Test Scripts
Fit/Gap Analysis; Implementation Team Understanding
TDD; Refined L3 Models; Real EBOs/EBSs; Security Access Design
Understanding of Deployed Solutions; Quicker Uptake
Understanding of Deployed Business Processes
BPA Suite Simulation
Training Content; New Hire Onboarding Collateral
Foundation for Internal Controls Reviews
Supplement to Standard Operating Procedures
Fit/Gap Analysis; Upgrade Team Understanding
Foundation for “As Is”, “To Be” Business Processes
Use of Models Throughout Fusion Business Process
Lifecycle

Business Process Model Architecture
Industry (L0)
Conceptual model depicting
a collection of all Business
Process Areas, enterprise-
wide, within a given industry
Business Process Area
(L1)
a collection of all Business
Processes within a given
Business Process Area
Business Process (L2)
a collection of Activities
within a given Business
Process
Activity (L3)
Breakdown of one activity
from the Business Process.
Depicts a group of related
Tasks that are required to
complete the Activity. An
Activity has a specific
objective
Enterprise Management
Enterprise Management
Planning and Performance Management
Planning and Performance Management
Operations
Field Service
Field Service
Support
Support
Procurement Product Design
Procurement Product Design Production
Production
Operations Support
Marketing
Marketing Order Fulfillment
Order Fulfillment
Sales
Sales
Financial Control
and Reporting
and Reporting
Program
Management
Cash Management
Financial Control
and Reporting
Program
Management
Cash Management
Reward
Development
Deployment
Recruiting Reward
Development
Deployment
Recruiting
Abstract very high-level
summary of all end-to-end
processes
Abstract high-level logical
summary of one end-to-end
process; no implementation
details
Still abstract; no implementation
details; however conceptual
analytic and implementation
requirements can be prescribed
Detailed; application-specific
task flows are shown; tasks are
associable with application
pages or services; detailed
analytics and integration points
are represented
SOA and BPEL details can be
added

Business Process Model Architecture

Multiple Sets of Models for 360° Usage
•Application Design
•Integration Design
•Business Intelligence Design
•System Testing
•BPEL Manager Integration
•OER Integration
•Tutor Integration
•UPK Integration
•Sales/Demo Content (TOIs, Solution Sets)
•Marketing Content
•Partner Collaboration
•Customer Baseline for BPM
•Accelerators

Cross-Industry Level 0 - Conceptual
Each object on model is a L1 Business Process Area
All L0 models created and maintained by BPE Team

Business Process Area Level 1 - Conceptual
Each object on model is a L2 Business Process

Business Process Level 2 - Conceptual
Each object on model is a L3 Activity

Activity Level 3 - Logical
BPM Task Flow
Objects on model are L4 Tasks
All L3 models created and maintained by Fusion Team Subject Matter Experts

Functional Process Drilldown
Conceptual Level 0
Conceptual Level 1
Conceptual Level 2
Level 3

Creating a Fusion BPM
Task Flow Step-by-Step

Create Fusion BPM Task Flow
• Teams are REQUIRED to create a Fusion BPM Task Flow which documents the
process for transactional L3 Activities within a Business Process
– Requires BPE Team review and approval
– Included in OBPA Fusion Repository
• Teams can OPTIONALLY create Set Up Task Flows which document tasks
performed during implementation, these are infrequent or one-time tasks
– Does not require BPE Team review and approval
– Will not be included in the OBPA Fusion Repository
• BPM Task Flows for Localization
– If tasks across the locales are mostly the same, one task flow is required, annotating tasks
that are specific to one locale
– If tasks are completely different between locales, multiple task flows may be required.
Consult the BPE Team before creating localization task flows.

Step 1 - Review Conceptual Context
• Locate any related business processes, reviewing them gives you context to start
creating a BPM Task Flow
– Review Fusion Business Process Activity Listing spreadsheet
– Or Review ADR
– L0 Cross-Industry model
– Review multi-level Visio models
Last Updated 02/23/2011
Fusion Business Process Models Activity Spreadsheet
ADR
Multi-level Visio Model
© 2010 Oracle Corporation – Proprietary and Confidential 21

Step 1 - Review Conceptual Context
Multi-Level Model
Depicts three levels:
Each activity will be
decomposed into a Task
Flow model
Level 1: Business
Process Area (title at
the top of page)
Level 2: Business
Process (large gray
group boxes)
Level 3: Activities
(small white boxes
inside gray boxes)

Step 2 - Determine High Level Conceptual Flow
• Review L1 and L2 models to determine which process areas the Oracle application
SUPPORTS
• Break-down the conceptual flow to determine if any new L2 Business Processes or
L3 Activities are needed
L1
L2
New L2 Manage Returns
needed
New L3 Activities (Authorize
Returns and Analyze Returns)
needed

Step 3 - Brainstorm L3 Activity
• Identify tasks which describe the OUTCOME of the L3 Activity
– Sequence and how the application works is not important at this time, you are making sure
you have the right L3 Activity and determining job roles in this step
• Identify the job roles which perform each task to ensure a new job role is not
needed
– Use ONLY approved Roles Fusion Business Process Role Listing spreadsheet
– Roles are centrally managed by BPE Team
– Model primary role

Step 4 - Submit Change Requests
• Submit change requests via RMS for any new L2 Business Processes, L3
Activities or Job Roles needed to complete the BPM Task Flow
• Complete the CR with the following information for each new item needed. Include
relevant parties on the “Impacts/Assessments” tab. Once the preliminary reviews
and approvals are complete, add Lynn Valdez to the “Approvals” tab to request
final approval. If the CR is for a job role change, also add Pat Krebs to the
“Approvals” tab.
– New L2 Business Processes
• Driving Deliverable Type – 3-12: BPM – Detailed Business Process (L2)
• CR Name – Request new L2 “xxx”
• Reason for Change – Provide detailed justification for need
– New L3 Activities
• Driving Deliverable Type – 3-1: BPM – Activity (L3)
• CR Name – Request new L3 “xxx”
– New Job Roles
• Driving Deliverable Type – 3-13: BPM – Role
• CR Name – Request new job role “xxx”

Step 5 - Model the L3 Activity Process
• Identify:
– Business Objective
– Starting Events
– Tasks, Steps and Group boxes
– Decision Points
– Hand Offs and End Events
– Consider Modeling Design Patterns
– Consider Process Verbs
• Good Modeling Practices:
– Display tasks within each lane from left to right, top to bottom
– In the Western world, we read from left to right, the process appears to flow naturally from
beginning to end and tell a story
– Objects should be spaced on major grid line, 2 squares apart at 100% , unless additional
space is needed for text on a line
– Keep objects in different swimlanes aligned along the same grid
– Use lines with arrows to show the sequence or flow between tasks
– Ensure lines connect to the connection points on each object, this ensures the lines stay
connected when the object moves

Create New Model File
• Download and use ONLY Oracle’s approved Visio template and stencil
– Stencil and template located on the Business_Process_Engineering OFO site
– Visio Template - Oracle Cross-Functional Flowchart (US units).vst
– Visio stencil - Oracle Cross-Functional Flowchart Shapes Horizontal (US units).vss
– Using the approved template and stencil ensures task flow converts easily into OBPA
– To open stencil once in Visio, click File -> Shapes -> Open Stencil and navigate to this
stencil
• File Name - Use Activity name found in the Fusion Business Process Activity
Listing spreadsheet (ie. Activity Name_mmddyy.vsd)
• Title of Model – Oracle Fusion Activity Name (ie. Oracle Fusion Authorize Returns)
Template Stencil

Oracle Visio Stencil Objects Defined

Add Job Roles
Visio Stencil Objects:
Rules for Use:
• Use ONLY approved Roles Fusion Business Process Role Listing spreadsheet
• Model primary Role
– Place single job role in swimlane
– Activity can have multiple roles
– If multiple roles perform same tasks select primary role and use Annotation object to depict secondary
role
Definition:
• A role portrays a key participant in a business process. A role is a title for a set of skills
needed to perform the process. They are usually job titles, but not necessarily specific jobs.
A person’s job usually consists of multiple roles in different processes. If multiple roles
perform same tasks, select primary role to model and make note using Annotation object for
secondary roles.

Add Start Event, Context Items and Title Block
Rules for Use:
• Only one Start Event allowed
• Any number of Context Items allowed
• Completely fill out all fields in Title Block
Definition:
• A start event signifies the start of the activity. Label the start event with “Need to Activity
Name” or other text that describes what event triggers the start of this activity.
• A context item is the L3 Activities that precede or provide input to the current Activity when
used at the beginning of the model. Can also be used at the end of the model to show the
subsequent L3 Activities. Generally, the context item will connect to the start event.

Add Tasks
Rules for Use:
• Task should be stated in [Verb Noun] syntax
• Verb should be an approved action verb such as, Create, Identify, Determine, Provide,
Advise, Obtain, etc. and then information about the action, such as, Approve Customer Order
• Task names should be in title case
• A Task is a logical representation of the physical implementation
• Avoid using jargon, acronyms or system terms in the task box
• Tasks can be associated to multiple Activities (i.e. Reusable tasks)
• Do not put the Role in the task box
• Do not resize task boxes. If text does not fix, rethink task name or reduce the text size
• Do not color task boxes
Definition:
• A task is a unit of work that results in a specific outcome. A task describes what is being
performed. Two or more tasks completed in a prescribed sequence results in the completion
of the Activity. It is ultimately supported by a component or page in an application.

Task Guidance
Questions to ask…
• Is it a logical business task that attributes to making the model more meaningful? Is it
important to the business story?
• Is it separately securable?
• Is it an important feature/functionality?
• Does it state the end users goal with respect to the Activity?
If you can answer Yes to the above questions you have a task

Additional Task Guidance
Additional Guidance:
• First think about the business objective of the activity and the expected result. This frames
the task flow and defines boundaries.
• The task flow is a sequence of tasks; not a data flow of information, not a data model.
• Place yourself in the business role; not the application developer role.
• Think of it as the business user is reading instructions on the first day of work.
• The natural tendency when looking at the system is going to be to write all tasks in terms of
CRUD functions (create this, read that, update this and delete that). Look at your tasks and
phrase them in an implementation-neutral manner and in terms of end-user goals where
possible.
– e.g. If a screen has a button labeled 'Shipping Methods' that leads to a dialog for selecting a shipping
method, the task should be: 'Select shipping method' not just 'View shipping method'.
• Step away from the system and list the tasks that the user needs to do without looking at it,
then go back and match them to the ones you have derived from looking at the system to see
if you missed any. Sometimes it’s difficult to avoid CRUD language and system-specific
tasks while looking at the system; at this point, we really want to be thinking about real user
tasks, not the system.

Add Task Group (if needed)
Rules for Use:
• Where it enhances understanding of the task flow, a logical group box (bordered by a dotted
line) can optionally be used to group tasks that are related.
• The Task Group Box name will correspond to a task group in ADR. The tasks within the
Task Group Box will correspond to the individual tasks in ADR.
• Lines should connect to the actual tasks within the Task Group Box.
Definition:
• A task group box is a logical grouping of related tasks.
Task Group Box Example:

Task Naming Examples
Yes
No
Select Saved
Search
Select information
type you want to
provide
OR
Do you want to
execute Saved
Search?
OR
Will you use
advanced search?
Select Search
Criteria
Select
Predetermined
Search Criteria
Yes
No
OR
Execute Saved
Search?
OR
Advanced Search?
Rebates
Calculate and
Apply Rebates
Decision text is a briefly
stated question
Start with Action Verb;
Express Complete Thought
Candidate enters
their work
preferences and
notification
preferences
Identify Work and
Notification
Preferences
Role expressed in role bar
No need to use in task box
Business User’s Voice
No pronouns
Incorrect Naming Correct Naming
Task name is title case

Add Steps (if needed)
Rules for Use:
• A task can optionally be broken down further into Steps that describe how the task is
performed
– A Step is always performed within the context of a task. It contributes to the completion of the task, but in and of
itself, does not accomplish the entire result.
– CRUD actions are not business tasks or steps; they are the four basic functions of persistent storage. They can
also be used to describe user interface conventions for viewing or searching. However, the verbs Create, Read,
Update and Delete can be used to indicate the actions on an entity towards meeting a business goal or
objective.
– Where such optional Steps are included, a group box (bordered by a solid line to distinguish from a task group
box) must be used to group steps that are related to accomplish a task. This Step Group Box will correspond to a
single task in ADR. The steps within the step group box will not appear in ADR at all. The permission to
complete all of the Steps in the Step Group must always be the same as the task the Steps complete.
– Lines should connect to the outside edges of the Step Group Box.
Definition:
• A step group box is a task showing the related steps that may be performed during the task.
Step Group Box Example:

Add Decisions
Yes
No
Assign Role to
Participant
Modify Participant
Detail
OR
Update
Participant?
Proactive
Navigation
Email
Notification
Work List
Entry
Receive Expense
Report Email
Notification
Access Summary
Listing of Expense
Reports
Retrieve Expense
Report Work List
Message
AND
OR
Method of
Awareness for
Approval
Rules for Use:
• Label decision criteria on the line
• Complete thought in diamond
• Use question mark if decision is truly a question, otherwise no punctuation is required
Decision Examples:
Inclusive decision - one, some, or all of
the options will occur
Yes/No Exclusive decision – only
one path will occur
Parallel decision – all the options will occur
Define Markets
Define Goals
and Strategies
Define Products
or Services
Define Goals and
Strategies for
Business
Define Markets
Business will
Compete In
Define Products or
Services
AND
Utilize Business
History

Add Annotations (if needed)
Rules for Use:
• Note additional role(s) within a swimlane
• Note additional relative details about a task
• Explain the condition when a task, step, task group or set of tasks would apply to a particular
feature
Annotation Examples:
Particular Feature
Multiple Roles Additional Detail

Hand-off’s and Endings
Rules for Use:
• Show the next L3 Activity or hand off to another L3 Activity within a different Business Process
as a Context Item that succeeds this process
• Context Item can be used to show when all tasks within another Activity must also be
performed to achieve the objective of the Activity being modeled
• Indicate conclusion of the process with the End Event
• Can have multiple End Events
Context Item and End Event Examples:
Analyze
Expenses
Update Expense
Transactions with
Payment
Information
Release Held
Expense Reports
End
Next Context Item End Event
Context Item within Activity

Step 6 - Submit Task Flow for Review
1. Review BPM Task Flow Approval Checklist to ensure task flow is ready for review
by BPE Team
2. Have your BPM and Info Dev POCs review task flow
3. Upload task flow to the appropriate version folder within
Fusion_Proposed_BP_Task_Flows
4. Email Lynn Valdez that task flow is uploaded
– A BPE Team member will work with you to get the model approved. Approved model will
be posted to OFO and imported into OBPA by BPE Team member.
5. Review approved task flow in OBPA Publisher
– Login=AIA/Welcome1
– Profile=Use the one that begins with Fusion_WIP
– Navigate to: Cross-Industry -> Fusion_WIP folder
6. Create an Oracle Review to document errors in OBPA version of task flow, assign
to BPE Team member who approved your task flow
Read “Task Flow Review Process” for full review process

BPM Task Flow in OBPA
• A member of the BPE Team will take the approved Visio BPM Task Flow and
import it into the OBPA Fusion Repository
• BPE Team will link BPM Task Flow to parent L2 model
• BPM Task Flow owner will do final review

Visio How To’s for Common
Modeling Errors

Manipulating Text on Line
• Insert words on line
– Double click on line, dotted box will appear, enter text
• If you ever move the line, the text is actually associated with the line and the text moves with it.
• Do not add a text box next to a line, it will not be associated with the line
• Move, resize or center words on line
– Select the “Text Block Tool” in the Visio tool bar
– Move: wait for the “Move Text Block” icon, then drag text box as needed
– Resize: wait for the “Size Text Block” icon, then adjust size
– Center: wait for the “Size Text Block” icon, then adjust left and right edges of text box to
beginning and ending of the line

Resize Page to Fit Task Flow
• Do not resize objects or adjust their layout to make fit on page
• Adjust page size
– Click on File -> Page Setup
– Click on Page Size tab
– Select “Custom size,” then adjust numbers to fit contents of page

Line Connections
• Use the “Connector Tool” to draw lines between objects
• Do not use line objects from a stencil
• Do not change line attributes (color, size, etc)
• Ensures lines connect to the connection points on each object, this ensure the
lines stay connected when the object moves
• Turn connection points on
– Click on View -> Connection Points
– Objects will now show x’s where connection points are
• Add connection points, if needed
– Turn connection points on
– Select “Connection Point Tool”
– Select object to add connection point to
– Place cursor on line of object where connection point is needed, hold down the CTRL key
and click left mouse button

Object Layout

AIA Business Process
Modeling Overview

AIA Model Types and Deliverables
We create and deliver the following types of models with each AIA Release Vehicle:
• Reference Process Models (RPMs) – Horizontal, functionally scoped business process
models that depict all of the aspects of the processes supporting a particular function
(Marketing, Sales, and Order Fulfillment, for example).
• Industry Reference Process Models – Industry-specific business process models that
combine industry processes with relevant horizontal processes and variations of horizontal
processes.
• Composite Business Flows – End-to-end processes that are comprised of parts of several
functional business processes (Order to Cash, Procure to Pay, and Design to Release, for
example).
• Oracle Business Process Publisher is delivered along with each AIA product for customers
to be able to view the read-only published set of models.
• Oracle Business Process Architect .adb source model repository is also delivered along
with each AIA release. However, customers must separately license Oracle BPA Suite in order
to use the .adb source file.
• The published models include hyperlinks to entries in OER where technical details are
described for the AIA integration artifacts.

AIA BPM Models
• AIA BPM Models differ from Fusion BPM Task Flows:
– Combines the business view of the business analyst with a glimpse of the technical view of
the technical analyst
– Each swimlane contains an object for the application system being used
– Includes an AIA Integration Layer swimlane to show where AIA process integrations are
– Adds Enterprise Business Services (EBSs) to Tasks where needed to show an AIA
process integration
– Includes links for EBSs from model to Oracle’s Enterprise Repository

Information on BPE Team

Governance and Security
• Central BPE team:
– Establishes approach, methodology, standards and notation
– Controls master business process model repository
– Trains, coaches and supports model authors
– Reviews and approves all models
– Maintains “Controlled Object Library” in BPA repository
– Approves and controls all conceptual model levels
– Approves and controls all Job and Abstract roles
– Physically approves Fusion conceptual levels and roles in
Application Design Repository (ADR)
– Releases models to customers

Key References
• Link to Business Process Engineering Folder
– Contains all documents referenced in this presentation
• Link to APM Website
• Link to AIA RPM Website
• Questions and Modeling Assistance, Call:
– Lynn Valdez – 925.694.6311
– Pat Krebs – 925.694.4646
– Michelle Mendes – 925.694.4654

Business_Process_Modeling_Training.ppt

More Related Content

Similar to Business_Process_Modeling_Training.ppt (20)

More from ssuser50762b (8)

Recently uploaded (20)

Business_Process_Modeling_Training.ppt