Business Process Worksheets - ebXML · Appendix C Drop Ship Scenario Example The members of the...
Transcript of Business Process Worksheets - ebXML · Appendix C Drop Ship Scenario Example The members of the...
Copyright © ebXML 2001. All Rights Reserved.
Business Process AnalysisBusiness Process AnalysisBusiness Process AnalysisBusiness Process Analysis1
Worksheets & GuidelinesWorksheets & GuidelinesWorksheets & GuidelinesWorksheets & Guidelines2
Procedures for developing business processes3
in ebXML45
Document Version: 0.106
Status: DRAFT7
Date: 30 April 20018
1. Status of this Document9
This document specifies an ebXML DRAFT for the electronic business community.10
Distribution of this document is unlimited.11
The document formatting is based on the Internet Society’s Standard RFC format.12
This version:13http://www.ebxml.org/working/project_teams/jdt/ts/BpWorksheets-DRAFT-0.10.pdf14
Latest version:15http://www.ebxml.org/working/project_teams/jdt/ts/BpWorksheets-WIP-0.8e.pdf16
Previous version:17http://www.ebxml.org/working/project_teams/jdt/ts/BpWorksheets-WIP-0.8e.pdf18
DRAFT
Business Process Analysis Worksheets and Guidelines 2
Copyright © ebXML 2001. All Rights Reserved.
2. ebXML participants19
Business Process Project Team Co-Leads20Paul Levine, Telcordia21Marcia McLure, McLure-Moynihan, Inc.22
We would like to recognize the following for their significant participation to the development of this23document.24
Editors25Charles Fineman, Arzoon.26Brian Hayes, Commerce One.55%27
28Jennifer Loveridge, Nordsrom.com.29David Welsh, Nordstrom.com.30
Contributors31Jim Clark, International Center of Object Technology.32Randy Clark, Baker Hughes, Inc.33Bob Haugen, Logistical Software.34Larissa Leybovich, Vitria35Bill McCarthy, Michigan State University36Nita Sharma, Netfish Technologies.37
38
DRAFT
Business Process Analysis Worksheets and Guidelines 3
Copyright © ebXML 2001. All Rights Reserved.
3. Table of Contents39
1. STATUS OF THIS DOCUMENT 140
2. EBXML PARTICIPANTS 241
3. TABLE OF CONTENTS 342
4. INTRODUCTION 643
4.1. SUMMARY 6444.2. AUDIENCE 7454.3. RELATED DOCUMENTS 7464.4. DOCUMENT CONVENTIONS 847
5. DESIGN OBJECTIVES 848
5.1. GOALS/OBJECTIVES/REQUIREMENTS/PROBLEM DESCRIPTION 8495.2. THE ANALOGY 10505.3. CAVEATS AND ASSUMPTIONS 1051
6. WORKSHEET BASED ANALYSIS OVERVIEW 1152
6.1. BASIC GUIDELINES FOR FILLING OUT WORKSHEETS 12536.1.1 Focus on public Business Processes 12546.1.2 The REA Ontology 12556.1.3 Use the worksheets in the order that makes the most sense for you 12566.1.4 The worksheets can be used for projects of various scopes 12576.1.5 Think how will people use what you construct 13586.1.6 Re-use is one of the primary goals of ebXML 13596.1.7 Note on optional fields in the worksheets 13606.1.8 Number your worksheets 1461
6.2. WORKSHEETS TO METAMODEL MAPPING 1462
7. BUSINESS PROCESS IDENTIFICATION AND DISCOVERY 1663
7.1. GOALS 16647.2. GUIDELINES 1765
7.2.1 How does one decide how big to make the various groupings at this level? 17667.2.2 What is the boundary of the business area? 1767
7.3. WORKSHEETS 17687.3.1 Business Reference Model 17697.3.2 Business Area 19707.3.3 Process Area 20717.3.4 Identify Business Processes 2172
8. BUSINESS PROCESS ELABORATION 2173
8.1. GOALS 21748.2. WORKSHEET 2275
9. BUSINESS COLLABORATION AND ECONOMIC EVENTS 2376
9.1. GOALS 23779.2. WORKSHEETS 2478
10. BUSINESS TRANSACTIONS AND AUTHORIZED ROLES 2579
10.1. GOALS 258010.2. GUIDELINES 2581
DRAFT
Business Process Analysis Worksheets and Guidelines 4
Copyright © ebXML 2001. All Rights Reserved.
10.3. WORKSHEETS 2682
11. BUSINESS INFORMATION DESCRIPTION 2683
11.1. GOALS 268411.2. WORKSHEETS 2685
11.2.1 Document Content Description 288611.2.2 Content Mapping 2987
APPENDIX A BUSINESS PROCESS IDENTIFIERS 3088
APPENDIX B THE PORTER VALUE CHAIN 3289
APPENDIX C DROP SHIP SCENARIO EXAMPLE 3590
C.1 BUSINESS PROCESS IDENTIFICATION AND DISCOVERY: BRM-1.0-DIRECT-TO-CUSTOMER-DROP-SHIP-91RETAIL-MODEL 3892
C.1.1 Business Areas 4093C.1.1.1 BA-2.0-Direct-to-Customer-Retail 4094C.1.1.2 BA-2.1-Finacial 4195
C.1.2 Direct To Customer Retail Process Areas 4296C.1.2.1 PA-3.1-Customer-Order-Management 4297C.1.2.2 PA-3.2-Customer-Order-Fulfillment 4498C.1.2.3 PA-3.3-Vendor-Inventory-Management 4599C.1.2.4 PA-3.4-Product-Catalog-Exchange 46100
C.1.3 Financial Process Areas 47101C.1.3.1 PA-3.5-Payment 47102
C.1.4 Customer-Order-Management Business Process Summaries 47103C.1.4.1 BPS-4.1-Firm-Sales-Order 47104C.1.4.2 BPS-4.2-Customer-Credit-Inquiry 48105C.1.4.3 BPS-4.3-Customer-Credit-Payment 48106
C.1.5 Customer Order Fulfillment Business Process Summaries 49107C.1.5.1 BPS-4.4-Purchase-Order-Management 49108C.1.5.2 BPS-4.5-Ship-Goods 49109
C.1.6 Vendor Inventory Management Processes Summaries 49110C.1.6.1 BPS-4.6-Inventory-Management 49111
C.1.7 Product Catalog Exchange Business Processes Summaries 50112C.1.7.1 BPS-4.7-Sales-Product-Notification 50113
C.1.8 Payment Business Process Summaries 50114C.1.8.1 BPS-4.8-Invoice-Presentment 50115
C.2 BUSINESS PROCESS ELABORATION 51116C.2.1 BPUC-5.1-Firm-Sales-Order 51117C.2.2 BPUC-5.2-Customer-Credit-Inquiry 53118C.2.3 BPUC-5.3-Customer-Credit-Payment 55119C.2.4 BPUC-5.4-Purchase-Order-Management 56120C.2.5 BPUC-5.5-Ship-Goods 57121C.2.6 BPUC-5.6-Inventory-Management 58122C.2.7 BPUC-5.7-Sales-Product-Notification 59123C.2.8 BPUC-5.8-Present-Invoice 59124
C.3 BUSINESS COLLABORATION AND ECONOMIC EVENTS 61125C.3.1 BC-6.1-Create-Customer-Order 61126C.3.2 BC-6.2-Check-Customer-Credit 63127C.3.3 BC-6.3-Process-Credit- Payment 64128C.3.4 BC-6.4-Create-Vendor-Purchase-Order 66129C.3.5 BC-6.5-Shipment-Instruction 67130C.3.6 BC-6.6-Confirm-Shipment 69131C.3.7 BC-6.7-Vendor-Inventory-Reporting 70132C.3.8 BC-6.8-Request-Inventory-Report 72133C.3.9 BC-6.9-Sales-Product-Offering 74134
DRAFT
Business Process Analysis Worksheets and Guidelines 5
Copyright © ebXML 2001. All Rights Reserved.
C.3.10 BC-6.10-Invoice-Presentment 75135C.4 BUSINESS TRANSACTIONS AND AUTHORIZED ROLES 78136
C.4.1 BT-8.1-Firm-Customer-Sales-Order 78137C.4.2 BT-8.2-Check Customer Credit 79138C.4.3 BT-8.3-Charge-Customer-Credit 80139C.4.4 BT-8.4-Create-Vendor-Purchase-Order 81140C.4.5 BT-8.5-Vendor-Inventory-Report 83141C.4.6 BT-8.6-Request-Inventory-Report 85142C.4.7 BT-8.7-Shipment-Notification 87143C.4.8 BT-8.8-Confirm-Shipment 89144C.4.9 BT-8.9-Product-Offering 91145C.4.10 BT-8.11-Present-Invoice 93146
C.5 BUSINESS INFORMATION DESCRIPTION 95147C.5.1 Purchase Order 95148
C.5.1.1 Purchase Order Business Information Context 95149C.5.1.2 CD-9.1-Order 96150C.5.1.3 CD-#.#-Order-Summary 96151
C.5.2 Content Mapping 98152C.5.2.1 CM-11.1-Order-Summary 98153
APPENDIX D DISCLAIMER 100154
APPENDIX E CONTACT INFORMATION 100155
156
FiguresFiguresFiguresFigures157
Figure 5-1, Worksheets Architectural Context ............................................................................... 9158
Figure 6-1 Overview of mapping from Worksheets to Metamodel .............................................11159
Figure 7-1 Business Process Identification and Discovery Worksheet to Metamodel Mapping16160
Figure 8-1 Mapping from business processes to the BRV .........................................................21161
Figure 9-1 Mapping from Business Collaboration to BRV ..........................................................23162
Figure 11-1, Direct To Customer Retail Transaction and Physical Goods Flow Overview......38163
Figure 1-2, <<BusinessOperationsMap>>Direct To Customer Drop Ship Retail......................39164
Figure 1-3, <<BusinessArea>>Direct to Customer Retail...........................................................41165
Figure 1-4, <<BusinessArea>> Finance ......................................................................................41166
Figure 1-5, <<ProcessArea>>Customer Order Management ....................................................43167
Figure 1-6, <<ProcessArea>>Customer Order Fulfillment .........................................................44168
Figure 1-7, <<ProcessArea>>Vendor Inventory Management ..................................................45169
Figure 1-8, <<ProcessArea>>Product Catalog Exchange..........................................................46170
Figure 1-9, <<ProcessArea>> Payment ......................................................................................47171
Figure 1-10, <<BusinessProcessActivityModel>> CustomerCreditCheck.................................54172
Figure 1-11, <<BusinessProcessActivityModel>> ProcessCreditPayment ...............................56173
Figure 1-12, Figure , <<BusinessProcessActivityModel>> PurchaseOrderManagement ........57174
DRAFT
Business Process Analysis Worksheets and Guidelines 6
Copyright © ebXML 2001. All Rights Reserved.
Figure 1-13, <<BusinessCollaborationProtocol>> CreateCustomerOrder ................................62175
Figure 1-14, <<BusinessCollaborationProtocol>> CheckCustomerCredit ................................63176
Figure 1-15, <<BusinessCollaborationProtocol>> ProcessCreditPayment ...............................65177
Figure 1-16 , <<BusinessCollaborationProtocol>> CreateVendorPurchaseOrder....................66178
Figure 1-17, <<BusinessCollaborationProtocol>> ShipmentInstruction ....................................68179
Figure 1-18, <<BusinessCollaborationProtocol>> ConfirmShipment ........................................70180
Figure 1-19, <<BusinessCollaborationProtocol>> VendorInventoryReporting..........................72181
Figure 1-20, <<BusinessCollaborationProtocol>> RequestInventoryReport.............................73182
Figure 1-21, <<BusinessCollaborationProtocol>> SalesProductOffering..................................75183
Figure 1-22, <<BusinessCollaborationProtocol>> InvoicePresentment ....................................76184
Figure 1-23, <<BusinessTransaction>> FirmCustomerSalesOrder...........................................79185
Figure 1-24, <<BusinessTransaction>> PurchaseOrderRequest ..............................................82186
Figure 1-25, <<BusinessTransaction>> VendorInventoryReport...............................................84187
Figure 1-26, <<BusinessTransaction>> RequestInventoryReport .............................................86188
Figure 1-27, <<BusinessTransaction>> ShipmentInstruction.....................................................88189
Figure 1-28, <<BusinessTransaction>> ConfirmShipment.........................................................90190
Figure 1-29, <<BusinessTransaction>> ProductOffering............................................................92191
Figure 1-30, <<BusinessTransaction>> PresentInvoice.............................................................94192
193
4. Introduction194
4.1. Summary195
The primary goal of the ebXML effort is to facilitate the integration of e-businesses throughout the196world with each other. Towards this end much of the work in ebXML has focused on the notion of a197public process: the business process(es) by which external entities interact with an e-business.198The specification and integration to such public processes has long been recognized as a199significant cost to such businesses. In order to reduce this cost ebXML is recommending the use of200Business Libraries. The principle goals of these libraries are to:201
a) Promote reuse of common business processes and objects202
b) Provide a place where companies and standards bodies could place the specifications of203their public processes where appropriate trading partners could access them.204
In order to realize these goals, a lingua franca needed to be leveraged so that all users of this205repository could understand what each other here specifying. The ebXML community has decided206to use as it's lingua franca the semantic subset of the UMM Metamodel, specified by the207UN/CEFACT Modeling Methodology in the N090 specification.208
The UMM “is targeted primarily at personnel knowledgeable in modeling methodology who209facilitate business process analysis sessions and provide modeling support. It also serves as a210
DRAFT
Business Process Analysis Worksheets and Guidelines 7
Copyright © ebXML 2001. All Rights Reserved.
checklist for standardized models when a previously specified business process is contributed to211UN/CEFACT for inclusion and incorporation as a standard business process model.” [UMM]212
People without the expertise in analysis and modeling will likely find that the UMM will be useful as213a reference manual. These people will use UMM complient approaches or, even, alternative214methodologies during the analysis of business processes. Practical experience tells us that it will215be more useful to the electronic business community to have an approach that does not require216such analysis and modeling expertise. An approach that a businessperson can apply would be217most useful. The Business Process Analysis Worksheets and Guidelines provide such an218approach.219
This document contains several worksheets that guide analysts towards UMM compliant220specifications of their common business processes. We have tried to provide tools for users221regardless of whether we’re working on behalf of a standards body or an individual company.222Furthermore, we provide a variety of scenarios guiding how one might go about filling out these223worksheets (e.g. top-down vs. bottom up)224
Different degrees of rigor are required within these worksheets. As we approach the lower level,225certain elements and organization of the specification are required to meet the requirements of the226ebXML technical framework. At higher levels there is a good deal of latitude about the way227concepts are grouped. In many cases, things such as assumptions and constraints will be228specified in natural language rather then in a formal one.229
4.2. Audience230
We do not expect the users of these worksheets to be experts in business modeling, however it is231expected that they are subject matter experts in their respective areas of practice. They should232have detailed knowledge of the inter-enterprise business processes they use to communicate with233their trading partners.234
This document could also be used by industry experts to help express their sectors business235processes in a form that is amenable to the goals of the ebXML registry and repository.236
Of course, software vendors that are supplying tools (modeling and otherwise) in support of the237ebXML framework will find useful information within.238
4.3. Related Documents239
[TAS] ebXML Technical Architecture Specification. Version 1.0. 4 January 2001. ebXML240Technical Architecture Project Team.241
[UMM] UN/CEFACT Modeling Methodology. CEFACT/TMWG/N090R8E. October 2000.242UN/CEFACT Technical Modeling Working Group.243
[MM] ebXML Business Process Collaboration Metamodel.244
[SCOR] Supply Chain Operations Reference model, The Supply Chain Council245(http://www.supply-chain.org/)246
[CCBP] ebXML Catalog of Business Processes. Version TBD. Date March 17, 2001. ebXML247Business Process Project Team248
DRAFT
Business Process Analysis Worksheets and Guidelines 8
Copyright © ebXML 2001. All Rights Reserved.
[BPAO] ebXML Business Process and Business Document Analysis Overview. Version TBD.249Date March 17, 2001. ebXML Business Process Project Team250
[RCRCCBP]ebXML The role of context in the re-usability of Core Components and Business251Processes. Version 1.01. February 16, 2001. ebXML Core Components Project Team.252
[REG1] ebXML Registry Information Model. Version 0.56. Working Draft. 2/28/2001. ebXML253Registry Project Team.254
[REG2] ebXML Registry Services. Version 0.85. Working Draft. 2/28/2001. ebXML Registry255Project Team.256
[REA] Guido Geerts and William.E. McCarthy "An Accounting Object Infrastructure For257Knowledge-Based Enterprise Models,"258IEEE Intelligent Systems & Their Applications (July-August 1999), pp. 89-94259
[PVC] Michael E. Porter, Competitive Advantage: Creating and Sustaining Superior260Performance, 1998, Harvard Business School Press261
262
4.4. Document Conventions263
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT,264RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be265interpreted as described in RFC 2119 [Bra97].266
Heretofore, when the term Metamodel is used, it refers to the UMM e-Business Process267Metamodel as defined in [UMM].268
5. Design Objectives269
5.1. Goals/Objectives/Requirements/Problem Description270
ebXML business processes are defined by the information specified in the ebXML UMM e-271Business Process Metamodel (hereafter referred to as the “Metamodel”). The Metamodel272specifies all the information that needs to be captured during the analysis of an electronic273commerce based business process within the ebXML framework. ebXML recommends the use of274the UN/CEFACT Modeling Methodology (UMM) in conjunction with the Metamodel. The UMM275provides the prescriptive process (methodology) to use when analyzing and defining a business276process.277
The ebXML Business Process Worksheets are a set of business process design aids, to be used278with the UMM as a reference. An ebXML business process, that is defined based on the UMM279Metamodel, will sufficiently reflect all the necessary components of a business process and enable280it's registration and implementation as part of the ebXML compliant electronic trading relationship.281The Worksheet based approach that provides an easier way of applying the UMM and the UMM282Metamodel.283
DRAFT
Business Process Analysis Worksheets and Guidelines 9
Copyright © ebXML 2001. All Rights Reserved.
The intent of the worksheets (or a business process editor4) is to capture all the bits of information284that are required to completely describe a business process so that it can be registered, classified,285discovered, reused and completely drive the software.286
To develop company business processes for an ebXML compliant electronic trading relationship,287use the UMM as a reference guideline plus the ebXML Business Process Worksheet to create the288necessary business process models. These are the recommended steps for using the ebXML289Business Process Worksheets290
1. A business need or opportunity is identified and defined before using these procedures.291
2. A Focus Project Team, usually representing a multifunctional set of experts from IT, business292process ownership and business process experts needed to work out the business process293using the ebXML Business Process Worksheet.294
3. Using the ebXML Business Process Worksheets, the Focus Project Team will be able to295develop an ebXML Business Process Specification that can be reviewed and verified by the296business. In addition, all necessary information to populate the ebXML Metamodel will be297made available to enable an ebXML trading relationship.298
Figure 5-1, Worksheets Architectural Context299
4 A group of ebXML contributors are working on a prototype of an editor that uses wizards to guide the user through theconstruction of a UMM compliant Business Process.
Browser
Public and Private Registries:Public and Private Registries:- Business Processes- Business Processes- Document and Component- Document & ComponentDomain Libraries Domain Libraries- Core Component Libraries- Core Component Libraries- Collaboration Protocol Profiles- Collaboration Protocol Profiles
Worksheets
DRAFT
Business Process Analysis Worksheets and Guidelines 10
Copyright © ebXML 2001. All Rights Reserved.
5.2. The Analogy300
The following analogy is useful in understanding the role of the Worksheets and other301documentation and tools to the ebXML Business Process Collaboration Metamodel and the302UN/CEFACT Modeling Methodology.303
Item United States Internal Revenue Service (IRS)Tax System
ebXML Business Process CollaborationMetamodel
UN/CEFACT Modeling Methodology.
Entire tax code
Worksheets and Templates IRS Forms
Methodology Guidelines IRS Instruction Booklets
Business Process Editor Tool Suite
Repository of Business Process Specifications,Core Components, etc.
Something like TurboTax and other softwarepackages for preparing personal or business taxforms where these packages would have on-lineaccess/search of all your tax and tax relatedrecords and the Tax code.
304
In order to actually specify a business process all we really need is the Worksheets and305Templates5. However, in order to ensure that we fill in the forms properly we will need to have a set306of instructions that augment the templates and provide some of the rationale behind the templates.307
5.3. Caveats and Assumptions308
The worksheets in this document are targeted towards the UMM as specified in the Revision 8E309document. Revision 9 has come out while this document was under development but there was310not enough time before the delivery date of this document to align it with the changes present in311Rev 9. While we expect the UMM to continue to evolve, we also expect the specification schema to312commit itself to compliance with a specific version. The intent is for this document to converge313towards the version of the UMM the specification schema targets.314
This document is non-normative; the documents identified above should be considered the315authority on the definitions and specifications of the terminology used herein. This document is316intended to be an application of those principals and technologies.317
5 A template is a document or file having a preset format that is used as a starting point for developing human-readableversions of the business process specifications so that the format does not have to be recreated each time it is used.
DRAFT
Business Process Analysis Worksheets and Guidelines 11
Copyright © ebXML 2001. All Rights Reserved.
6. Worksheet Based Analysis Overview318
As stated above, the purpose of this document is to provide worksheets that guide the user319through the construction of a UMM compliant specification of their business processes. The320following diagram shows mapping from the worksheets to the high level components of the UMM.321Note, the document definition worksheet is currently not included in the set of worksheets.322
Figure 6-1 Overview of mapping from Worksheets to Metamodel323
The expectation is that after the worksheets have been completed, there will be sufficient324information to mechanically produce a Metamodel based specification of the modeled business325process(es). The worksheets given above are:326
Business Reference Model – Use this to define the “frame of reference” of the rest of the327worksheets. This provides definitions of terms and, perhaps, canonical business processes (e.g.328[SCOR]6)329
Business Process Identification and Discovery – Use this to do an inventory of the business330processes. This is really just a set of high-level use cases merely to identify the existence of331processes and the stakeholders without going into detail.332
Business Process Elaboration – These worksheets are used to flesh out the business333processes. This identifies the actual actors as well as pre and post conditions for the business334process.335
6 Defines plan, source, make and deliver business areas in their Supply Chain Operations Reference (SCOR) model
Business ProcessIdentification and Discovery
Business Operations MapModel
Business Reference Model
Business Requirements ViewModel
Business Service ViewModel
Business Transaction ViewModel
Business CollaboationConstruction
Business Process Ellaboration
Business TransactionDefinition
Business InformationDefinition
DRAFT
Business Process Analysis Worksheets and Guidelines 12
Copyright © ebXML 2001. All Rights Reserved.
Business Collaboration Definition – In these worksheets we define the economic events that336take place to fulfill the business process. This is where one defines the system boundaries and the337protocols that flow between them.338
Business Transaction Definition – These worksheets are more technically oriented than the339others (which have a decidedly more “modeling” orientation). At this stage one defines the actual340activities and authorized parties within the organization that initiate these transactions.341
Business Information Definition – In these worksheets one defines the contents of the342information field, widths, data types, descriptions, requirement traceability and, perhaps, the343additional context ([RCRCCBP]) necessary to construct the document from the Core Components344subsystem.345
6.1. Basic Guidelines for filling out Worksheets346
6.1.1 Focus on public Business Processes347
While these worksheets could be used to model any kind of business process, the focus of the348ebXML effort is to make trading partner integration easier, cheaper, and more robust. Therefore the349expectation is that the primary focus will be on public faces of your business processes.350
6.1.2 The REA Ontology351
The UMM and ebXML groups are recommending the use of the Resource-Economic Event-Agent352Ontology for the formalization of business collaborations. The worksheets in the main body of this353document are intended to be more generic in nature however please refer to [BPAO] for further354information on this topic7 and associated worksheets.355
6.1.3 Use the worksheets in the order that makes the most sense for you356
For the purposes of this document we proceed from the top-level step (Business Reference Model)357down to the lowest-level step (Business Transaction). It is important to note, however, that these358worksheets can be filled out in whatever order makes the most sense from the user’s perspective.359For example, a person who is trying to retrofit an existing document based standard (e.g.360EDIFACT) might want to start by filling in the Business Transaction Definition worksheets (perhaps361only specifying trivial definitions for the higher level worksheets). A person looking to formalize the362definitions for an entire industry may very well start from the Business Reference Model worksheet.363
6.1.4 The worksheets can be used for projects of various scopes364
Although the Metamodel has definite requirements on what objects need to be present to comprise365a complete specification, it says little about the scope of what those specifications represent. For366example, if you are only trying to model a specific interaction with one of your trading partners, you367do not need to include a complete Business Reference Model for your entire industry, just include368the parts that are directly relevant for the interaction you are modeling. Similarly, if you are just369doing a small set of interactions for your company, you might choose to have the Business Area or370Process Area just be your own company.371
7 Worksheets will be made available in a future version of this document.
DRAFT
Business Process Analysis Worksheets and Guidelines 13
Copyright © ebXML 2001. All Rights Reserved.
6.1.5 Think how will people use what you construct372
As you fill in these worksheets please keep in mind how the generated UMM specification will be373used by a user of the repository. The two principal uses envisioned are:374
• To determine if a given collaboration is appropriate for reuse (or at least is a close enough375match for subsequent gap analysis)376
• To be used as an on-line implementation guide. A potential trading partner (or a 3rd party377on their behalf) could examine the public processes/collaborations you provide and378construct an integration plan.379
This means trying to use industry wide terms (or at least Business Reference Model terminology)380to decrease the ambiguity or misunderstanding between you and the eventual consumers of these381specifications.382
6.1.6 Re-use is one of the primary goals of ebXML383
As stated above, the hope is that users will develop models that are reusable by others. Towards384that end, it is intended that the Worksheets be used in conjunction with a browser that lets the user385search business process libraries for items that have already been defined. The items (e.g.386business processes, business collaborations, document schemas, etc.) can be referenced (re-387used as is) or copied to the worksheets and changed as needed. Over time, business process388catalogs will become populated with a sufficiently large number of business processes. When this389happens, the analysis processes will often become a matter of validating pre-defined business390processes against requirements.391
6.1.7 Note on optional fields in the worksheets392
Some of the worksheets contain entries that are labeled as optional for ebXML. These are393attributes that appear in the UMM but are not required as part of the ebXML Specification Schema.394These are typically business objective/justification topics. While these are obviously very important395aspects of any modeling endeavor, ebXML is oriented towards exposing an organization’s public396processes to their trading partners. Advertising that organizations justifications for such interfaces397could potentially publicize strategic information that said organization would prefer to keep private.9398
9 There has been discussion on private vs. public repositories where some or all aspects of the model are stored in arestricted access repository.
DRAFT
Business Process Analysis Worksheets and Guidelines 14
Copyright © ebXML 2001. All Rights Reserved.
6.1.8 Number your worksheets399
Each of the worksheets has an entry for a Form ID. This ID can be used to reference one form400from another. In addition, if you use an outline numbering scheme, it will be easy for the reader to401determine parent-child relationships between elements of the model (of course, if you do a bottom402up approach this will be significantly harder to do up front!).403
The recommended format is:404
<Form Type>-<Number>-<Description>405
Where <Form Type> is406
BRM for Business Reference Model407BA for Business Area408PA for Business Process Area409BP for Business Process Summary410BPUC for Business Process Use Case411BC for Business Collaboration412BT for Business Transaction413
<Number> is, perhaps, an outline entry number414
<Description> is some descriptive name.415
Please see the example in the Appendix for an illustration of this in practice.416
6.2. Worksheets to Metamodel Mapping417
The following diagram sketches out a more detailed mapping from the Worksheets Model to the418Metamodel defined by the UMM. The leftmost column is the selection of the main elements that the419Worksheets need to specify or edit. The rightmost column are the Metamodel elements that those420worksheets map to, also showing intervening elements that the Worksheets need to construct and421manage in order to be able to save and retrieve the business process model correctly (in terms of422the Metamodel). The rightmost column also shows the base element for each element. The423middle column is the other elements that are part of the Worksheets. They are the same as the424Metamodel elements of the same name.425
DRAFT
Business Process Analysis Worksheets and Guidelines 15
Copyright © ebXML 2001. All Rights Reserved.
Business Process(Use Case)
BOMModel
Business AreaModel
Process AreaModel
BRVModel
Business CollaborationProtocol
(Activity Graph)
BTVModel
BusinessTransactionActivity
(Action State)
BusinessTransaction(Activity Graph)
Business ProcessIdentification
BusinessReference Model
Business Area
Process Area
BusinessCollaboration
Business Transaction
WorksheetModel Metamodel
Partner Type
AuthorizedRole
Business Activity
Document Envelope
Business CollaborationUse Case
(Use Case)
Business Collaboration(Collaboration)
Business Document
Choreography -states, transitions, etc.
Business Actor
Business Document
Business ProcessElaboration
Business Process(Use Case)
Business TransactionUse Case
(Use Case)
Different path forsingle transaction
collaborations.
426
DRAFT
Business Process Analysis Worksheets and Guidelines 16
Copyright © ebXML 2001. All Rights Reserved.
427
7. Business Process Identification and Discovery428
7.1. Goals429
The first set of worksheets helps the user begin formalize the domain they are trying to model430processes in. The first stage in the methodology is to identify the “top level” entities and organizing431concepts in the domain.432
BP Identification andDiscovery
BOM
Business ProcessUse Case
BOMModel
Business AreaModel
Process AreaModel
Business ProcessIdentification
BusinessReference Model
Business Area
Process Area
433
Figure 7-1 Business Process Identification and Discovery Worksheet to Metamodel Mapping434
At this stage we define terminology and identify the players as well as which business processes435those players interact with. To quote the UMM, at this stage in the model the goal is to:436
� To understand the structure and dynamics of the business domain,437
� To ensure that all users, standards developers and software providers have a common438understanding of the business domain,439
� To understand the daily business in the business domain independent of any technical440solution,441
� To create categories to help partition the business domain that enables an iteration plan to442complete the model,443
� To structure the model in the form of a Business Operations Map (BOM),444
� To capture the justification for the project,445
� To identify the stakeholders concerned with the modeled domain, some who will be446independent of the processes within the domain.447
The modeling artifacts that correspond to the UMM are:448
DRAFT
Business Process Analysis Worksheets and Guidelines 17
Copyright © ebXML 2001. All Rights Reserved.
� Business Area [Package]449
� Process Area [Package]450
� Process(es) [Use Cases]451
7.2. Guidelines452
7.2.1 How does one decide how big to make the various groupings at this453
level?454
Referring back to the primary guidelines, think about what you are trying to communicate. If you455are more focused on identifying the public processes, then think about grouping them by partner456type or, perhaps by the area of your business these partners interact with. If you are trying to457formalize an entire business sector, determine the archetypes that are prevalent in that sector and458group them by business function area. These are just rules of thumb and this is still largely an “art”.459Keep in mind your potential audience and think what would make the most useful organization for460them.461
The activity diagrams in this workflow will likely discover more refined business process use cases.462The Business Operations Map (BOM) Metamodel allows a business process to be represented by463more refined business processes. NOTE: At the point where the business process can not be464broken down into more child business processes, the parent business process can be called a465business collaboration use case as specified in the Requirements workflow.466
7.2.2 What is the boundary of the business area?467
According to the [UMM] the following guidelines are to be used in defining a business area:468
• Stakeholders that are within the scope of the business domain and outside the scope of469the business domain but affect or are affected by inputs/outputs to/from processes within470the business domain. A stakeholder is defined as someone or something that is materially471affected by the outcome of the system but may or may not be an actor. For example one472who funds the business modeling project is a stakeholder. Actors are stakeholders that473are involved in the business process and are thus part of the business model.474
• Information passing into or out of the business domain. Where possible, the domain475boundaries should be chosen so that a business transaction is logically initiated and476concluded within them.477
• Key business entity classes. (i.e., things that are accessed, inspected, manipulated,478processed, exchanged, and so on, in the business process)479
7.3. Worksheets10480
7.3.1 Business Reference Model481
Often times it is useful to define a “frame of reference” for the business processes being identified.482This frame of reference might define basic terms accepted by the given industry segment. For483
10 Note that the examples given in the following worksheets more or less come from the hypothetical business processdescribed in section 8.4 of [CCBP].
DRAFT
Business Process Analysis Worksheets and Guidelines 18
Copyright © ebXML 2001. All Rights Reserved.
example the SCOR model defines a frame of reference for supply chain. VICS defines a frame of484reference for trading partners in the retail industry. It also might be a more horizontal view such as485the Porter Value Chain.486
Form: Describe Business Reference Model
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Business Reference ModelName
[Provide a name for the reference model. You can use an existingreference model such as the Supply Chain Council or the Porter’sValue Chain or create your own name.] DOTCOM DROP SHIPRETAIL MODEL
Industry Segment [Provide the name of the industry segment that this business appliesto. Search the business process library for a list of possible industrysegments. If the industry segment does not exist, then provide anappropriate name/label for the industry segment.] Retail.
Domain Scope [Provide a high level statement that encapsulates the scope of all thebusiness areas.] Online catalog, distribution center, delivery, billing.
Business Areas [List the business areas within the scope. A business area is acollection of process areas. A process area is a collection ofbusiness processes. You may wish to refer to the ebXML Catalog ofBusiness Processes that provides a list of normative categories thatmay be used as business areas.] Order Management, AR.
Optional for ebXML
Business Justification [Provide the business justification for the collection of businessprocesses] Define more efficient on-line retailer/vendor interaction.
487
DRAFT
Business Process Analysis Worksheets and Guidelines 19
Copyright © ebXML 2001. All Rights Reserved.
7.3.2 Business Area488
As mentioned in the guidelines section, there are no hard and fast rules for how to divide up the489model into different business areas. One suggestion is to group business processes according to490the primary business function. You might consider using the Porter Value Chain classification491scheme (see Appendix B).492
Form: Describe Business Area
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Business Area Name [Provide a name for the business area. This should be listed in theBusiness Areas section of at least one Business Reference Model.]
Direct to Customer Retail
Description [A brief summary of this functional area. ]
Scope [Provide a high level statement that encapsulates the scope of all thebusiness areas. The scope of the business area must be within thescope of the encompassing business reference model. Typically thescope of the business area will be more constrained or limited thanthe scope of the business reference model.] Online catalog, orderplacement, distribution center, delivery, billing.
Boundary of the BusinessArea
[Describe the boundary of the business area. This defines the entitiesthat interact in this business area; actors, organizations, possiblysystems] Customer, Retailer, DSVendor, Carrier, Credit Authority.
References [Any external supporting documentation.] VICS, SCOR
Constraints [Identify any constraints on the process areas (and, thus, businessprocesses) within this business area.] 1. Completely automatedsystem. 2. Web browser limitations. 3. Domestic orders only
Stakeholders [Identify the practitioners that care about the definition of this businessarea. At this level, this is likely to be some participants in an industrygroup (perhaps a standards body or an enterprise). These are thepeople who will define the BRV.] Customer, Retailer, DSVendor,Carrier, Credit Authority.
Process Areas [List the process areas within the scope. A process area is acollection of business processes. You may wish to refer to the ebXMLCatalog of Business Processes that provides a list of normativeprocess groups that may be used as process areas.] CustomerCommitment, Order fulfillment, Billing, Inventory Management.
Optional for ebXML
Objective [Describe the objective of this business area.] To deliver a product toa customer in a timely efficient manner.
Business Opportunity [Describe the business opportunity addressed by this business area.]
DRAFT
Business Process Analysis Worksheets and Guidelines 20
Copyright © ebXML 2001. All Rights Reserved.
7.3.3 Process Area493
Typically a business reference model would define a canonical set of process areas (see the494Porter or SCOR reference models for examples). A process area consists of a sequence of495processes that are combined to form the “value chain” of the given business area.496
497
Form: Describe Process Area
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Process Area Name [Provide a name for the process area. This should be listed in theProcess Areas section of at least one Business Area.] OrderFulfillment
Objective [Describe the objective of this process area.] To deliver the goodsordered to the customer.
Scope [Provide a high level statement that encapsulates the scope of all thebusiness areas. The scope of the business area must be within thescope of the encompassing business reference model. Typically thescope of the process area will be more constrained or limited than thescope of the corresponding business area.] To fulfill customer’s orderusing the third party supplier for a drop ship delivery.
References [External supporting documentation.]
Boundary of the ProcessArea
[Describe the boundary of the process area. The communicatingservices.] Retailer and third party vendor.
[Issue: How is this different than Scope?]
Constraints [Identify any constraints on the business processes within thisprocess area.] Inventory availability. On time delivery. Systemconstrain.
Stakeholders [Identify the practitioners involved in this process area. Question: isthis a subset of those listed in the Business Area?.] Retailer, Thirdparty vendor
Business Processes [List the business processes within the scope of this process area.You may wish to refer to the ebXML Catalog of Business Processesthat provides a normative list of business processes.] ManagePurchase Order.
Optional for ebXML
Business Opportunity [Describe the business opportunity addressed by this process area.]
498
DRAFT
Business Process Analysis Worksheets and Guidelines 21
Copyright © ebXML 2001. All Rights Reserved.
7.3.4 Identify Business Processes499
For each business process in the process area fill in the following worksheet. A suggested rule of500thumb for the appropriate granularity for a business process is that it is the smallest exchange of501signals between stakeholders that has an identifiable economic value (cref. [REA]).Note that this is502not always appropriate since “negotiation” could be a valid business process but it doesn’t really503result in an economic consequence.504
Be sure to validate the information in the process area against the encompassing business area.505For example, validate that the scope of the process area is within the scope of its business area.506
Form: Identify Business Process
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Business Process Name [Provide a name for the business process. You may wish to refer tothe ebXML Catalog of Business Processes [CCBP] that provides asuggested set of commonly used business processes.] ManagePurchase Order
Process Area [A process area is a group of business processes. Complete aProcess Area form.] Order Fulfillment
Business Area [A business area group together related process areas. Create aBusiness Area form.] Direct to Customer Retail
507
8. Business Process Elaboration508
8.1. Goals509
At this stage we begin to move from requirements analysis to design analysis. Consider the510following diagram:511
BusinessProcessElaboration
BRVBRVModel
Business Process(Use Case)
Business ProcessElaboration
Business Actor Business Actor
512
Figure 8-1 Mapping from business processes to the BRV513
DRAFT
Business Process Analysis Worksheets and Guidelines 22
Copyright © ebXML 2001. All Rights Reserved.
A business process is a use case that is used to gather requirements about business processes.514Inputs to the business process must be specified in the preconditions and outputs from the515business process must be specified in the post-conditions.516
8.2. Worksheet517
One of these is filled out for each business process. Keep in mind that a business process could be518nested. You should use whatever organization makes sense for your purposes (though you might519want to think in terms of reuse when considering possible decompositions).520
Form: Business Process Use Case
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Business Process Name [Provide a name for the business process. This should be a nameidentified on the form “Identify Business Process” and on a“Describe Process Area” form. If you are starting with this form, youmay wish to refer to the ebXML Catalog of Business Processes thatprovides a normative list of business processes.] Manage PurchaseOrder.
Identifier [This is a unique identifier that follows the Business ProcessIdentifier Naming Scheme. This can be provided when the businessprocess description is submitted to a business process library. SeeAppendix A for a more detailed discussion.]bpid:ean.1234567890128:ManagePurchaseOrder$1.0
Actors [List the actors involved in the use case.] Retailer, Vendor
Performance Goals [A specification of the metrics relevant to the use case and adefinition of their goals. Non-functional requirements may be asource of performance goals. For each performance goal, providea name of the performance goal and a brief description of theperformance goal.]
Preconditions [Preconditions are constraints that must be satisfied starting the usecase.] 1. Valid Sales Order 2. Valid Vendor Relation
Begins When [Describe the initial event from the actor that starts a use case.]SSaalleess OOrrddeerr VVaalliiddaattiioonn ((eexxpprreesssseedd aass eevveennttss))
Definition [A set of simple sentences that state the actions performed as partof the use case. Include references to use cases at extensionpoints.] A valid Purchase Order placed by retailer with the vendorand a PO Ack is received from the vendor.
Ends When [Describe the condition or event that causes normal completion ofthe use case.] PPOO AAcckknnoowwlleeddggeedd rreettuurrnneedd ttoo rreettaaiilleerr..
Exceptions [List all exception conditions that will cause the use case toterminate before its normal completion.] 11.. PPOO RReejjeecctteedd ((FFaaiilluurreessttaattee ooff aa pprroocceessss)) 22.. LLaattee PPOO aacckknnoowwlleeddggeedd
DRAFT
Business Process Analysis Worksheets and Guidelines 23
Copyright © ebXML 2001. All Rights Reserved.
Postconditions [Post-conditions are constraints that must be satisfied ending theuse case.] 11.. VVaalliidd PPOO 22.. AAllllooccaatteedd PPrroodduucctt
Traceability [These are the requirements covered (as shown in Annex 4, UseCase Specification Template, in the UMM).] "PRD-FOO-6.5.4"(meaning Product Requirements Document for FOOproject/solution, requirement 6.5.4).
9. Business Collaboration and Economic Events521
9.1. Goals522
These worksheets develop the Business Requirements View (BRV) of a process model.523
524
Figure 9-1 Mapping from Business Collaboration to BRV525
The following items are specified:526
• The business collaboration protocols that tie economic events together527
• The system boundaries between which the protocols flow528
• The input and output triggers of these collaborations529
• The roles and constraints associated with the collaboration530
The purpose of the Partner Collaboration and Economic Agreements Worksheets is:531
“… to capture the detailed user requirements, specified by the stakeholders, for the business-532to-business project. … This workflow develops the Business Requirements View (BRV) of a533process model that specifies the use case scenarios, input and output triggers, constraints and534system boundaries for business transactions (BTs), business collaboration protocols (BCPs)535and their interrelationships.” ([UMM, 3.1])536
The modeling artifacts to be identified are:537
BusinessCollaboration
BRV
Business Collaboration
Partner Type
Business Collaboration Use CaseUse Case
Business CollaborationCollaboration
Choreography -states, transitions, etc.
Business Transaction Use CaseUse Case
Partner Type
DRAFT
Business Process Analysis Worksheets and Guidelines 24
Copyright © ebXML 2001. All Rights Reserved.
� Business Transactions [Use Case]538
� Business Collaboration [Use Case]539
� Business Collaboration Use Case [Use Case Realization, Activity Diagram]540
� Economic Modeling Elements [Business Entities]541
9.2. Worksheets542
Detail the information in the table below for each business collaboration. Note that it may make543sense to use UML diagrams to convey some of this information.544
Form: Business Collaboration
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Description [Provide a descriptive overview of the collaboration.]
Partner Types [This is a list of entities that participate in the collaboration. Theseparticipants exchange the events that form the collaboration.]
Authorized Roles [These are the roles that a partner must be authorized to play toissue specific transitions in the collaboration (by sending certainsignals).]
Legal steps/requirements [If any step in the collaboration has any legal standing, it should becaptured here.]
Economic consequences11 [If any step in the collaboration has and economic consequence, itshould be captured here.]
Initial/terminal events [List the events that initiate this collaboration and how it terminates.]
Scope [Specify the set of business actions this collaboration encapsulates.]
Boundary [Specify the systems and users that communicate with each otherover he course of this collaboration.]
Constraints [Spell out any special constraints that are relevant to thiscollaboration (e.g. business scenario, pre-conditions.)]
545
11 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
DRAFT
Business Process Analysis Worksheets and Guidelines 25
Copyright © ebXML 2001. All Rights Reserved.
10. Business Transactions and Authorized Roles546
10.1. Goals547
The goal of this worksheet is to identify the individual transactions that implement the workflow of a548Business Collaboration. A transaction is made up of several activities and each activity has an549authorized role that the signaler must have in order to initiate that activity.550
The modeling artifacts generated as a result of this worksheet is the BusinessTransaction Activity551Diagram. Fill out one worksheet for each transaction in the collaborations552
10.2. Guidelines553
The UMM has defined several transaction patterns. It may be useful for you to identify your554transactions with one of those (if for no other reason to make it clear to others the basic interaction555pattern you intend to follow)556
Some of these patterns have intrinsic semantics (e.g. non-repudiation, authorization) in them. If you557choose to base this transaction on one of those patterns you do not have to repeat those here.558However if you do not and you have these semantic requirements, make sure they are described559here.560
DRAFT
Business Process Analysis Worksheets and Guidelines 26
Copyright © ebXML 2001. All Rights Reserved.
10.3. Worksheets561
Form: Business Transaction
Form ID [Provide an ID for this form so other forms can reference it (§6.1.8)]
Description [Provide a descriptive overview of this transaction.]
Pattern [If you have chosen to follow one of the canonical transactionpatterns in the UMM12 (or elsewhere) denote it here. If not and youhave special semantics (as mentioned above), describe them here.]
Agents and Services [This is a list of agents and services that initiate activities.]
Business activities andassociated authorized roles
[List each activity (along with it’s initiator) and the role required toperform that activity]
Constraints [Any constraints should be listed here.]
Requesting Partner Type [Partner type from collaboration.] Customer
Requesting Activity Role [Role from collaboration] Buying Customer
Requesting ActivityDocument
[Document initiating the transaction. Might reference a standarddocument (e.g. an X12 document). ] Sales Order
Responding Partner Type [See above.] On-line Retailer
Responding Activity Role [See above.] Customer Service
Responding ActivityDocument
[See above.] Confirmation email
11. Business Information Description562
11.1. Goals563
The goal of this set of worksheets is to identify the information requirements for the business564documents specified in the business transactions.565
11.2. Worksheets566
The first step in specifying business documents in a business process and information model, is to567attempt to reuse business information objects in a Business Library. If an existing business568document cannot be found then, domain components from Domain Libraries and core components569from the Core Library can be used. Until the Business Library is built up, or imported from a570creditable source, core components are likely to be referred to frequently, to first add to the571repertoire of business information objects in the Business Library, and second, to create business572documents.573
The steps for completing these worksheets are as follows:574
12 See chapter 4 in [UMM].
DRAFT
Business Process Analysis Worksheets and Guidelines 27
Copyright © ebXML 2001. All Rights Reserved.
1. See what attributes are available in business information objects in the available Business Libraries575that can be used in a business document.576
2. If business information objects with appropriate attributes as required for business documents are577not available, new business information objects must be created.578
3. Look for re-usable information components in the business library and the Core Library as579candidates for business information object attributes. Take context into account, as specified in the580business process and information models. Extend existing business information objects, domain581components, and core components as required.582
4. Add the new attributes to existing business information objects, or introduce new business583information objects through a registration process that manages changes to the Business Library.584
5. Use the new attributes, now in the Business Library, as needed in creating the business585documents.586
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es28
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
11.2
.1 D
ocum
ent C
onte
nt D
escr
ipti
on58
7
Des
crib
e ea
ch e
lem
ent o
r gro
up o
f ele
men
ts in
the
docu
men
t. L
ogica
lly re
late
d el
emen
ts c
an b
e pl
aced
in s
epar
ate
form
s (F
or e
xam
ple,
a58
8do
cum
ent m
ay h
ave
logi
cally
thre
e pa
rts, a
hea
der,
body
, and
sum
mar
y. T
he b
ody
may
hav
e fu
rther
logi
cal p
artit
ioni
ng.).
Pos
sible
val
ues
589
for O
ccur
s in
clude
: 1 (o
ne in
stan
ce),
0..1
(zer
o on
one
inst
ance
), 0.
.* (z
ero
or m
ore
inst
ance
s), 1
..* (o
ne o
r mor
e in
stan
ces)
, or n
..m (n
to m
590
inst
ance
s w
here
n is
less
than
m).
Pos
sible
val
ues
for D
ata
Type
inclu
de p
rimitiv
e da
ta ty
pes
such
as
inte
ger,
strin
g, d
ate-
type
. If
you
591
happ
en to
kno
w th
e na
me
of a
reus
able
com
pone
nt fr
om a
n do
mai
n lib
rary
or t
he C
atal
og o
f Cor
e C
ompo
nent
s, th
en y
ou M
AY re
fere
nce
it.59
2Th
e Se
man
tic D
escr
iptio
n SH
ALL
be s
tate
d in
bus
ines
s te
rms
and
SHAL
L be
una
mbi
guou
s.59
3
Form
: Con
tent
Des
crip
tion
Form
Id:
[A n
ame
for t
he fo
rm.
For e
xam
ple,
“Inv
oice
” or “
Ord
er H
eade
r”]
Elem
ent/C
ompo
nent
Nam
eO
ccur
sDa
taTy
peFi
eld
Wid
thSe
man
tic D
escr
iptio
nNo
tes
[Pro
vide
a na
me
for t
heel
emen
t/com
pone
nt.
For
exam
ple,
“Ord
er S
umm
ary”
or
“Issu
ed D
ate.
”]
594
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
esD
RAF
T
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es29
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
11.2
.2 C
onte
nt M
appi
ng59
5
Thes
e fo
rms
SHO
ULD
be
com
plet
ed.
This
info
rmat
ion
is ve
ry im
porta
nt a
s it
show
s th
at th
e do
cum
ents
hav
e a
basis
in e
xistin
g st
anda
rds.
596
Furth
erm
ore,
the
info
rmat
ion
will
be u
sed
to c
reat
e do
cum
ent t
rans
form
atio
ns.
Stan
dard
s to
map
to in
clud
e ED
IFAC
T, X
12, x
CBL
,59
7R
oset
taN
et, a
nd o
ther
sta
ndar
ds s
uch
as O
BI.
Use
XPA
TH a
nd X
SLT
nota
tion
for r
efer
encin
g XM
L el
emen
ts a
nd d
escr
ibin
g th
e m
appi
ngs.
598
If a
new
doc
umen
t sch
ema
is cr
eate
d to
fulfil
the
cont
ent r
equi
rem
ents
spe
cifie
d in
the
Doc
umen
t Con
tent
Des
crip
tion
form
s, th
en a
set
of
599
Con
tent
Map
ping
form
s sh
ould
be
com
plet
ed fo
r tha
t sch
ema
(the
com
pone
nt n
ames
in th
e fo
rms
are
simpl
y re
quire
men
ts fo
r inf
orm
atio
n)60
0
For e
ach
Con
tent
Des
crip
tion
form
, com
plet
e a
Doc
umen
t Con
tent
Map
ping
form
for e
ach
stan
dard
to b
e cr
oss-
refe
renc
ed.
601
Form
: Con
tent
Map
ping
Form
Id:
[A n
ame
of th
e co
rresp
ondi
ng C
onte
nt D
escr
iptio
n th
e fo
rm.
For e
xam
ple,
“Inv
oice
” or “
Ord
er H
eade
r”]
Stan
dard
[Nam
e of
the
stan
dard
. Fo
r exa
mpl
e, U
N/E
DIF
ACT]
Vers
ion
[Sta
ndar
d ve
rsio
n nu
mbe
r. Fo
r exa
mpl
e, D
.01A
]
Elem
ent/C
ompo
nent
Nam
eM
appi
ng/T
rans
form
atio
nNo
te
602
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es30
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
603
App
endi
x A
Bus
ines
s Pr
oces
s I
dent
ifier
s60
4
Obj
ects
of t
he e
ntire
ebX
ML
busi
ness
arra
ngem
ent e
mbo
died
by
the
UM
M c
an b
e id
entif
ied
by a
Bus
ines
s Id
entif
ier N
amin
g Sc
hem
e, d
irect
ly60
5re
late
d to
the
laye
rs o
f the
UM
M. S
pecif
ically
the
Busin
ess
Ope
ratio
ns M
ap (B
OM
) with
a B
usin
ess
Proc
ess
Iden
tifie
r nam
ing
Sche
me
606
(BPI
NS)
, the
Bus
ines
s R
equi
rem
ents
Vie
w w
ith a
Bus
ines
s C
olla
bora
tion
Iden
tifie
r Sch
eme
(BC
INS)
and
the
Busin
ess
Tran
sact
ion
View
with
607
a Bu
sines
s Tr
ansa
ctio
n Id
entif
ier S
chem
e (B
TIN
S).
608
609
A BP
INS
nam
ing
sche
me
form
at is
def
ined
by
:61
0bp
id:<
agen
cy>:
<age
ncy-
id>:
<bus
ines
s-pr
oces
s-na
me>
$<m
ajor
-ver
sion-
num
ber>
.<m
inor
-ver
sion-
num
ber>
611
A BC
INS
nam
ing
sche
me
form
at is
def
ined
by
:61
2bc
id:<
agen
cy>:
<age
ncy-
id>:
<bus
ines
s-co
llabo
ratio
n-na
me>
$<m
ajor
-ver
sion-
num
ber>
.<m
inor
-ver
sion-
num
ber>
613
A BT
INS
nam
ing
sche
me
form
at is
def
ined
by
:61
4bt
id:<
agen
cy>:
<age
ncy-
id>:
<bus
ines
s-tra
nsac
tion-
nam
e>$<
maj
or-v
ersio
n-nu
mbe
r>.<
min
or-v
ersio
n-nu
mbe
r>61
561
661
7W
here
618
�
bpid
is th
e fi
xed
strin
g “b
pid”
indi
catin
g th
e en
tire
iden
tifie
r is
a bu
sines
s pr
oces
s id
entif
ier.
619
�
bcid
is th
e fix
ed s
tring
“bci
d” in
dica
ting
that
the
entir
e id
entif
ier i
s a
busi
ness
col
labo
ratio
n id
entif
ier.
620
�
btid
is th
e fix
ed s
tring
“btid
” ind
icatin
g th
at th
e en
tire
iden
tifie
r is
a bu
sine
ss tr
ansa
ctio
n id
entif
ier.
621
�
agen
cy id
entif
ier o
r nam
e of
the
agen
cy th
at o
wns
the
agen
cy-id
s an
d m
ust b
e a
glob
ally
uni
que
iden
tifie
r. Fo
r exa
mpl
e,62
2D
UN
S an
d EA
N.
623
�
agen
cy-id
ide
ntife
r of t
he o
rgan
izatio
n th
at o
wns
the
busin
ess
proc
ess
and
mus
t be
a gl
obal
ly u
niqu
e id
entif
ier.
No
othe
r62
4en
tity
SHAL
L us
e th
e ag
ency
iden
tific
atio
n of
ano
ther
ent
ity.
625
�
Maj
or a
nd m
inor
ver
sion
num
bers
are
eac
h in
tege
rs a
nd n
eed
to re
spec
t any
spe
cific
Reg
istry
Aut
horit
y co
nven
tions
def
ined
.62
6Th
e bu
sines
s-pr
oces
s-na
me,
bus
ines
s-co
llabo
ratio
n-na
me,
bus
ines
s-tra
nsac
tion-
nam
e sh
ould
be
desc
riptiv
e na
mes
. It i
s re
com
men
ded
that
627
the
desc
riptiv
e na
me
be in
cam
el-c
ase.
The
nam
es m
ust n
ot c
onta
in s
pace
s, p
erio
ds, c
olon
s, o
r dol
lar s
igns
. Th
e or
gani
zatio
n or
age
ncy-
id62
8th
at o
wns
the
busi
ness
tran
sact
ion
SHAL
L be
resp
onsi
ble
for g
uara
ntee
ing
that
the
iden
tifie
r is
uniq
ue..
629
630
Valid
exa
mpl
es o
f bus
ines
s pr
oces
ses
usin
g th
e id
entif
ier n
amin
g sc
hem
e in
clude
:63
1
btid
:ean
.123
4567
8901
28:D
istrib
uteO
rder
Stat
us$1
.063
2
bpid
:ican
n:m
y.co
m:N
ewBu
sines
sPro
cess
$2.0
633
634
635
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es31
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
With
resp
ect t
o th
e eb
XML
Reg
istry
Info
rmat
ion
Mod
el s
pecif
icatio
n13 th
e de
finitio
n is
as fo
llow
s:63
6B
PIN
S
R
egis
try
Info
rmat
ion
Mod
el63
7bp
id
Ex
trins
icObj
ect.o
bjec
tTyp
e63
8bc
id
Ex
trins
icObj
ect.o
bjec
tTyp
e63
9bt
id
Ex
trins
icObj
ect.o
bjec
tTyp
e64
0ag
ency
Org
aniza
tion.
nam
e64
1ag
ency
id
Org
aniza
tion.
uuid
642
busin
ess-
proc
ess-
nam
e Ex
trins
icObj
ect.n
ame
643
busin
ess-
colla
bora
tion-
nam
e Ex
trins
icObj
ect.n
ame
644
busin
ess-
trans
actio
n-na
me
Extri
nsicO
bjec
t.nam
e64
5m
ajor
-ver
sion-
num
ber
Extri
nsicO
bjec
t.maj
orVe
rsio
n64
6m
inor
-ver
sion-
num
ber
Extri
nsicO
bjec
t.min
orVe
rsio
n64
764
8An
Ext
rinsic
Obj
ect i
s a
spec
ial t
ype
of M
anag
edO
bjec
t (on
e th
at g
oes
thro
ugh
a de
fined
life
cycl
e); t
he e
xtrin
sic o
bjec
t is
not r
equi
red
for t
he64
9co
re o
pera
tion
of a
regi
stry
. A
n O
rgan
izatio
n is
defin
ed a
s an
Intri
nsicO
bjec
t; it
is co
re to
the
func
tion
of a
regi
stry
.65
0
13 C
ref [
REG
1] a
nd [R
EG2]
.
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es32
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
App
endi
x B
The
Por
ter
Valu
e C
hain
651
The
follo
win
g ta
ble
show
s th
e ca
tego
ries
of th
e Po
rter V
alue
Cha
in a
nd h
ow th
ey m
ap to
REA
con
cept
s. T
his
is in
clude
d as
an
aid
to h
elp
user
s fo
rmal
ize65
2th
eir c
lass
ificat
ion
of th
e el
emen
ts o
f a b
usin
ess
proc
ess
spec
ificat
ion.
653
Nor
mat
iveC
ateg
ory
Nor
mat
ive S
ub-
Cat
egor
yR
esou
rce
inflo
ws
&ou
tflow
Maj
or ty
pes
of e
vent
sEc
onom
icAg
ents
&R
oles
Proc
urem
ent
Bid
Subm
issio
nC
ontra
ctN
egot
iatio
nPu
rcha
se O
rder
Prep
arat
ion
Rec
eivin
g
Mon
eyR
aw m
ater
ials
Facil
ities
Serv
ices
Tech
nolo
gy
Paym
ents
Purc
hase
Purc
hase
Ord
ers
Price
Quo
tes
Con
tract
Neg
otia
tion
Buye
rSe
ller
Vend
orC
ashi
er
Hum
anR
esou
rces
Hiri
ngTr
aini
ngPa
yrol
lM
anag
emen
tPe
rson
nel
Dep
loym
ent
Mon
eyPu
rcha
sed
train
ing
mat
eria
lsPu
rcha
sed
bene
fitpa
ckag
es
Cas
hPa
ymen
tsAc
quisi
tion
of la
bor
Trai
ning
Empl
oyee
Stud
ent
Bene
ficia
ry
Tran
spor
tatio
nLo
adin
gSh
ippi
ngPa
ckag
ing
Raw
Mat
eria
lsD
elive
red
Raw
Mat
eria
lsM
anuf
actu
red
Goo
dsD
elive
red
Man
ufac
t. G
oods
Ship
men
tW
areh
ousin
g Ta
sks
Mat
eria
lH
andl
ing
Truc
king
Buye
rVe
ndor
Logi
stics
Wor
ker
Truc
ker
Man
ufac
turin
gPr
oduc
tD
evel
opm
ent
Prod
uct D
esig
nAs
sem
bly
Qua
lity c
ontro
l
Facil
ities
&Te
chno
logy
Labo
rR
aw M
ater
ials
Fini
shed
Goo
ds
Man
ufac
turi
ng Ope
ratio
nR
awM
ater
ial
Issu
e
Fact
ory
Wor
ker
Supe
rviso
rQ
CIn
spec
tor
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es33
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
Nor
mat
iveC
ateg
ory
Nor
mat
ive S
ub-
Cat
egor
yR
esou
rce
inflo
ws
&ou
tflow
Maj
or ty
pes
of e
vent
sEc
onom
icAg
ents
&R
oles
Man
ufac
turi
ng J
obM
arke
ting
&Sa
les
Adve
rtisin
g U
se &
Cam
paig
ning
Mar
ketin
gM
anag
emen
tSa
les
Cal
ling
Cus
tom
er C
redi
tM
anag
emnt
Labo
rAd
verti
sing
Serv
iceD
elive
red
Goo
dsPr
oduc
t Ser
vices
Cas
h
Cas
hPa
ymen
tC
usto
mer
Invo
iceSa
le O
rder
Price
Quo
tes
Con
tract
Neg
otia
tion
Cus
tom
erSa
lesp
erso
nC
ashi
er
Cus
tom
erSe
rvice
Afte
r Sal
es S
ervic
eW
arra
nty
Con
stru
ctio
n
Labo
rPu
rcha
sed
Serv
ices
Prod
uct W
arra
ntie
san
d Se
rvice
s
Serv
ice C
all
Prod
uct
Rep
air
Serv
iceC
ontra
ct
Cus
tom
erSe
rvice
Ag
ent
Cus
tom
er
Fina
ncin
gLo
an M
anag
emen
tSt
ock
Subs
crip
tions
and
Sale
sD
ivide
nd P
olic
y
Cas
hBo
nds
Stoc
ksD
eriva
tive
Inst
rum
ents
Inte
rest
Paym
ents
Stoc
kSu
bscr
iptio
ns D
ivide
ndD
ecla
ratio
nsC
ash
Rec
eipt
s
Stoc
khol
der
s Bond
Hol
der
s Inve
stm
ent
Brok
ers
Fina
ncia
lM
anag
ers
Adm
inist
ratio
nAc
coun
ting
Fina
ncia
l Rep
ortin
gEx
ecut
iveM
anag
emen
t
Empl
oyee
Lab
orEm
ploy
eeSe
rvice
Man
agem
ent
Pro
ject
s
Man
ager
sC
lerk
s
Business Process Analysis Worksheets and Guidelines
Appendix C Drop Ship Scenar io ExampleThe members of the ebXML Business Process Analysis Joint Deliverable Team are in the processof developing a proof of concept for presentation at the May 2001 ebXML meeting in Vienna. Thisappendix provides a partial snapshot of the worksheet based analysis being done for the businessreference model “Direct to Customer Drop Ship Retail.” In many cases, UMM UML diagrams areprovided. As with the rest of this document, it is work in progress. It is our hope that you find thisinformation helpful in understanding how you can make these worksheets work for you.
[1.0] Top level of Business Reference Model : defines the “frame of reference” of all worksheets.[2.0] Business Process Area : Form that defines the scope of the business area[3.0] Business Process Identification and Discovery : Forms that inventory all business processes.[4.0] Business Process Summary Name form[5.0] Business Process Elaboration : Forms used to describe the business processes and identifyactors as well as pre and post conditions for the business processes. (use cases)[6.0] Business Collaboration Definition : define the economic events that take place to fulfill thebusiness process, including system boundaries and the protocols that flow between them.[7.0] Collaboration Transitions <<�- Brian’s going to supply[7.1] Transaction Transitions <� Brian’s coming out with this.[8.0] Business Transaction Definition : Forms that defines the actual activities and authorizedparties within the organization that initiate these transactions.[9.0] content/document definition[10.0] Business information context[11.0] Content mapping
Model ContentsC.1 BUSINESS PROCESS IDENTIFICATION AND DISCOVERY: BRM-1.0-DIRECT-TO-CUSTOMER-DROP-SHIP-RETAIL-MODEL..........................................................................................................................................................38
C.1.1 Business Areas.....................................................................................................................................40C.1.2 Direct To Customer Retail Process Areas .........................................................................................42C.1.3 Financial Process Areas .....................................................................................................................47C.1.4 Customer-Order-Management Business Process Summaries ..........................................................47C.1.5 Customer Order Fulfillment Business Process Summaries ..............................................................49C.1.6 Vendor Inventory Management Processes Summaries .....................................................................49C.1.7 Product Catalog Exchange Business Processes Summaries.............................................................50C.1.8 Payment Business Process Summaries...............................................................................................50
C.2 BUSINESS PROCESS ELABORATION..............................................................................................................51C.2.1 BPUC-5.1-Firm-Sales-Order .............................................................................................................51C.2.2 BPUC-5.2-Customer-Credit-Inquiry..................................................................................................53C.2.3 BPUC-5.3-Customer-Credit-Payment ...............................................................................................55C.2.4 BPUC-5.4-Purchase-Order-Management.........................................................................................56C.2.5 BPUC-5.5-Ship-Goods........................................................................................................................57C.2.6 BPUC-5.6-Inventory-Management ....................................................................................................58C.2.7 BPUC-5.7-Sales-Product-Notification...............................................................................................59C.2.8 BPUC-5.8-Present-Invoice .................................................................................................................59
C.3 BUSINESS COLLABORATION AND ECONOMIC EVENTS................................................................................61C.3.1 BC-6.1-Create-Customer-Order.........................................................................................................61C.3.2 BC-6.2-Check-Customer-Credit .........................................................................................................63C.3.3 BC-6.3-Process-Credit- Payment.......................................................................................................64C.3.4 BC-6.4-Create-Vendor-Purchase-Order ...........................................................................................66
Business Process Analysis Worksheets and Guidelines
C.3.5 BC-6.5-Shipment-Instruction..............................................................................................................67C.3.6 BC-6.6-Confirm-Shipment ..................................................................................................................69C.3.7 BC-6.7-Vendor-Inventory-Reporting..................................................................................................70C.3.8 BC-6.8-Request-Inventory-Report......................................................................................................72C.3.9 BC-6.9-Sales-Product-Offering ..........................................................................................................74C.3.10 BC-6.10-Invoice-Presentment.............................................................................................................75
C.4 BUSINESS TRANSACTIONS AND AUTHORIZED ROLES .................................................................................78C.4.1 BT-8.1-Firm-Customer-Sales-Order..................................................................................................78C.4.2 BT-8.2-Check Customer Credit ..........................................................................................................79C.4.3 BT-8.3-Charge-Customer-Credit .......................................................................................................80C.4.4 BT-8.4-Create-Vendor-Purchase-Order............................................................................................81C.4.5 BT-8.5-Vendor-Inventory-Report .......................................................................................................83C.4.6 BT-8.6-Request-Inventory-Report ......................................................................................................85C.4.7 BT-8.7-Shipment-Notification.............................................................................................................87C.4.8 BT-8.8-Confirm-Shipment...................................................................................................................89C.4.9 BT-8.9-Product-Offering.....................................................................................................................91C.4.10 BT-8.11-Present-Invoice .....................................................................................................................93
C.5 BUSINESS INFORMATION DESCRIPTION .......................................................................................................95C.5.1 Purchase Order ...................................................................................................................................95C.5.2 Content Mapping.................................................................................................................................98
Table Of FiguresFigure 5-1, Worksheets Architectural Context ............................................................................... 9
Figure 6-1 Overview of mapping from Worksheets to Metamodel .............................................11
Figure 7-1 Business Process Identification and Discovery Worksheet to Metamodel Mapping16
Figure 8-1 Mapping from business processes to the BRV .........................................................21
Figure 9-1 Mapping from Business Collaboration to BRV ..........................................................23
Figure 11-1, Direct To Customer Retail Transaction and Physical Goods Flow Overview......38
Figure 1-2, <<BusinessOperationsMap>>Direct To Customer Drop Ship Retail......................39
Figure 1-3, <<BusinessArea>>Direct to Customer Retail...........................................................41
Figure 1-4, <<BusinessArea>> Finance ......................................................................................41
Figure 1-5, <<ProcessArea>>Customer Order Management ....................................................43
Figure 1-6, <<ProcessArea>>Customer Order Fulfillment .........................................................44
Figure 1-7, <<ProcessArea>>Vendor Inventory Management ..................................................45
Figure 1-8, <<ProcessArea>>Product Catalog Exchange..........................................................46
Figure 1-9, <<ProcessArea>> Payment ......................................................................................47
Figure 1-10, <<BusinessProcessActivityModel>> CustomerCreditCheck.................................54
Figure 1-11, <<BusinessProcessActivityModel>> ProcessCreditPayment ...............................56
Figure 1-12, Figure , <<BusinessProcessActivityModel>> PurchaseOrderManagement ........57
Figure 1-13, <<BusinessCollaborationProtocol>> CreateCustomerOrder ................................62
Business Process Analysis Worksheets and Guidelines
Figure 1-14, <<BusinessCollaborationProtocol>> CheckCustomerCredit ................................63
Figure 1-15, <<BusinessCollaborationProtocol>> ProcessCreditPayment ...............................65
Figure 1-16 , <<BusinessCollaborationProtocol>> CreateVendorPurchaseOrder....................66
Figure 1-17, <<BusinessCollaborationProtocol>> ShipmentInstruction ....................................68
Figure 1-18, <<BusinessCollaborationProtocol>> ConfirmShipment ........................................70
Figure 1-19, <<BusinessCollaborationProtocol>> VendorInventoryReporting..........................72
Figure 1-20, <<BusinessCollaborationProtocol>> RequestInventoryReport.............................73
Figure 1-21, <<BusinessCollaborationProtocol>> SalesProductOffering..................................75
Figure 1-22, <<BusinessCollaborationProtocol>> InvoicePresentment ....................................76
Figure 1-23, <<BusinessTransaction>> FirmCustomerSalesOrder...........................................79
Figure 1-24, <<BusinessTransaction>> PurchaseOrderRequest ..............................................82
Figure 1-25, <<BusinessTransaction>> VendorInventoryReport...............................................84
Figure 1-26, <<BusinessTransaction>> RequestInventoryReport .............................................86
Figure 1-27, <<BusinessTransaction>> ShipmentInstruction.....................................................88
Figure 1-28, <<BusinessTransaction>> ConfirmShipment.........................................................90
Figure 1-29, <<BusinessTransaction>> ProductOffering............................................................92
Figure 1-30, <<BusinessTransaction>> PresentInvoice.............................................................94
Business Process Analysis Worksheets and Guidelines
C.1 Business Process Identification and Discovery: BRM-1.0-Direct-To-Customer-Drop-Ship-Retail-Model
Customer
OrderEntry
DSVendor
Retail
B2B
Buyer Bank
1. Firm Customer Sales 1. Firm Customer Sales Order Order
Order Fulfillment Order Fulfillment Customer Commitment Customer Commitment
workflow
B2B
Global Registry
4. Purchase Order 4. Purchase Order RequestRequest
5. PO 5. PO AckAck..
B2BServe
Credit Authority
2. Authorize Credit Check2. Authorize Credit Check
7. Physical Delivery 7. Physical Delivery of goods of goods
8. Charge Credit 8. Charge Credit
Physical Movement Physical Movement
B2BInternet
Direct to Customer Retail Direct to Customer Retail
3. Available to Promise 3. Available to Promise Inventory Report Inventory Report
6. Confirmed Shipment ASN 6. Confirmed Shipment ASN
Inventory Reporting Inventory Reporting
9. Catalog Exchange 9. Catalog Exchange
Transport Transport Shipment instruction
Shipment confirmation
Figure 11-1, Direct To Customer Retail Transaction and Physical Goods Flow Overview
Form: Business Reference ModelForm Id BRM-1.0-Direct-To-Customer-Drop-Ship-Retail-Model
Business Reference ModelName
DIRECT TO CUSTOMER DROP SHIP RETAIL MODEL
Industry Segment Retail
Domain Scope Internet retail, catalog, distribution center, delivery, billing.
Business Areas � Direct To Customer Retail
� Finance
Optional for ebXML
Business Justification Define more efficient on-line retailer/vendor interaction. Reduce
Business Process Analysis Worksheets and Guidelines
inventory carrying costs.
Direct To Customer Retai l
<<Busines sArea>>Finance
<<BusinessArea>>
Figure 1-2, <<BusinessOperationsMap>>Direct To Customer Drop Ship Retail
Business Process Analysis Worksheets and Guidelines
C.1.1 Business Areas
C.1.1.1 BA-2.0-Direct-to-Customer-Retail
Form: Business AreaForm Id BA-2.0-Direct-to-Customer-Retail
Business Area Name Direct to Customer Retail
Description This is a demonstrative business process model, to illustrate ebXMLbusiness process modeling, and based on actual business practiceconventions today.
See ‘Objective’ section below in this form.
Scope Internet based retail, mail order catalog, direct to customer productfulfillment logistics, single piece product delivery from a distributioncenter to an end customer.
Boundary of the BusinessArea
• Customer• Retailer• Direct Supply Retail Vendor (DSVendor)• Transport Carrier• Credit Authority
References • EAN International• Global Commerce Initiative• VICS• SCOR• “my company typical Vendor Compliance Manual”
Constraints • Internet based retail customer service system• Web browser limitations.• Domestic customer orders only
Stakeholders • Customer• Retailer• Direct Supply Retail Vendor (DSVendor)• Transport Carrier• Credit Authority
Process Areas • Customer Order Management• Customer Order Fulfillment• Vendor Inventory Management• Product Catalog Exchange
Optional for ebXML
Objective To deliver a commercial product directly to a customer, in a timelyand efficient manner directly from a product supply source, with anonline Internet retailer taking the customer order and providing directcustomer service management.
Business Opportunity Reduce retailer inventory carrying costs. Shorten the supply chainfrom a domestic vendor to a domestic customer; thus save trees,energy and lives.
Notes:
Business Process Analysis Worksheets and Guidelines
1. The Business Area diagram (below) shows all the process areas in this business area.
Direct To Customer Retail
Customer Order Management
<<ProcessArea>>Customer Order
Fulfillment
<<ProcessArea>>Vendor Inventory
Management
<<ProcessArea>>Product Catalog
Exchange
<<ProcessArea>>
Figure 1-3, <<BusinessArea>>Direct to Customer Retail
C.1.1.2 BA-2.1-Finacial
Form: Business AreaForm Id BA-2.1-Finacial
Business Area Name Finacial
Description
Scope
Boundary of the BusinessArea
• Retailer• Direct Supply Retail Vendor (DSVendor)•
References •
Constraints •
Stakeholders • Retailer• Direct Supply Retail Vendor (DSVendor)
Process Areas • Payment
Optional for ebXML
Objective
Business Opportunity
Payment<<Proces sArea>>
Figure 1-4, <<BusinessArea>> Finance
Business Process Analysis Worksheets and Guidelines
C.1.2 Direct To Customer Retail Process Areas
C.1.2.1 PA-3.1-Customer-Order-Management
Form: Business Process AreaForm Id PA-3.1-Customer-Order-Management
Process Area Name Customer Order Management
Objective • Take a sales order from an Internet based customer• Validate a customer’s ability to pay for product upon delivery• Take payment from a customer’s credit card after a product
has been delivered directly to a customerScope • Fulfill customer orders using a 3rd party supplier for drop
ship (customer direct) delivery.References • “my company Vendor Operations Compliance Manual”
Boundary of the ProcessArea
Constraints • Customer promise of product availability most likely true at avendor location when a customer order is accepted by theretailer.
• Customer must have sufficient credit to eventually pay for theproduct after the product has been shipped.
Stakeholders • Customer• Retailer• Credit Authority
Business Processes • Firm Sales Order• Customer Credit Inquiry• Customer Credit Payment
Optional for ebXML
Business Opportunity
Business Process Analysis Worksheets and Guidelines
Customer (from Actors)
Firm Sales Order<<BusinessProcess>>
Customer Credit Inquiry<<BusinessProcess>>
Retailer
(from Actors)
CreditAuthority
(from Actors)
Customer Credit Payment <<BusinessProcess>>
Figure 1-5, <<ProcessArea>>Customer Order Management
Business Process Analysis Worksheets and Guidelines
C.1.2.2 PA-3.2-Customer-Order-Fulfillment
Form: Business Process AreaForm Id PA-3.2-Customer-Order-Fulfillment
Process Area Name Customer Order Fulfillment
Objective Allow a retailer to instruct a direct supply vendor to deliver (withinspecific delivery times) specific product to a specific customer.
Scope
References • “my company Vendor Compliance Operating Manual”
Boundary of the ProcessArea
Activities directly pertaining to the registration of firm customer salesorders, and credit payment of delivered customer sales orders.
Constraints • On hand product allocation to a customer order by a vendorimmediately after processing a retailer’s purchase order.
• On time product delivery from vendor to customer.• Immediate notification by a vendor to a retailer of a direct to
customer product delivery; with customer service details.Stakeholders • Retailer
• DSVendor• Transport Carrier• Customer
Business Processes • Purchase Order Management• Ship Goods•
Optional for ebXML
Business Opportunity
Retailer
(from Actors)Purchase Order Management
<<BusinessProcess>> DSVendor
(from Actors)
TransportCarrier(from Actors)
Ship Goods<<BusinessProcess>>
Figure 1-6, <<ProcessArea>>Customer Order Fulfillment
Business Process Analysis Worksheets and Guidelines
C.1.2.3 PA-3.3-Vendor-Inventory-Management
Form: Business Process AreaForm Id PA-3.3-Vendor-Inventory-Management
Process Area Name Vendor Inventory Management
Objective To allow a direct supply vendor to report “available on-hand”inventory to a retailer.
Scope
References • “my company Vendor Compliance Operating Manual”
Boundary of the ProcessArea
Constraints • Inventory, by product SKU identification, is “available on-hand” within the direct supply vendor’s inventorymanagement system.
Stakeholders • Retailer• DSVendor
Business Processes • Inventory Management
Optional for ebXML
Business Opportunity
DSVendor
(from Actors)Inventory Management<<BusinessProcess>> Retailer
(f rom Acto rs)
Figure 1-7, <<ProcessArea>>Vendor Inventory Management
Business Process Analysis Worksheets and Guidelines
C.1.2.4 PA-3.4-Product-Catalog-Exchange
Form: Business Process AreaForm Id PA-3.4-Product-Catalog-Exchange
Process Area Name Product Catalog Exchange
Objective To maintain an accurate catalog (list) of a vendor’s products, in aretailer’s business operating system; especially as vendor’s productsare introduced to the market or existing products require updatedproduct specifications between the vendor and the retailer.
Scope
References • “my company Vendor Compliance Operating Manual”
Boundary of the ProcessArea
Constraints • Existence of a valid business operating relationship betweena specific vendor and a retailer, such that products offered bya vendor can be in turn offered to an end customer by theretailer.
Stakeholders • Retailer• DSVendor
Business Processes • Sales Product Notification
Optional for ebXML
Business Opportunity
DSVendor
(f rom Actors)Sales Product Notification
<<BusinessProcess>> Retailer
(f rom Actors)
Figure 1-8, <<ProcessArea>>Product Catalog Exchange
Business Process Analysis Worksheets and Guidelines
C.1.3 Financial Process Areas
C.1.3.1 PA-3.5-Payment
Form: Business Process AreaForm Id PA-3.5-Payment
Process Area Name Payment
Objective For the vendor to invoice the retailer for goods shipped and servicesprovided.
Scope The scoped is defined by the following business processes:
� Present Invoice
References • “my company Vendor Compliance Operating Manual”
Boundary of the ProcessArea
Constraints • Valid business relationship
Stakeholders • Retailer• DSVendor
Business Processes • Present Invoice
Optional for ebXML
Business Opportunity
DSVendor
(f rom Actors)Present Invoice
<<BusinessProcess>> Retailer
(f rom Actors)
Figure 1-9, <<ProcessArea>> Payment
C.1.4 Customer-Order-Management Business Process Summaries
C.1.4.1 BPS-4.1-Firm-Sales-Order
Form: Business Process SummaryForm Id BPS-4.1-Firm-Sales-Order
Business Process Analysis Worksheets and Guidelines
Business Process Name Firm Sales Order
Identifier bpid:ean.1234567890128:FirmSalesOrder$1.0
Process Area Customer Order Management
Business Area Direct to Customer Retail
C.1.4.2 BPS-4.2-Customer-Credit-Inquiry
Form: Business Process SummaryForm Id BPS-4.2-Customer-Credit-Inquiry
Business Process Name Customer Credit Inquiry
Identifier bpid:ean.1234567890128:CustomerCreditInquiry$1.0
Process Area Customer Order Management
Business Area Direct to Customer Retail
C.1.4.3 BPS-4.3-Customer-Credit-Payment
Form: Business Process SummaryForm Id BPS-4.3-Customer-Credit-Payment
Business Process Name Customer Credit Payment
Identifier bpid:ean.1234567890128:CustomerCreditPayment$1.0
Process Area Customer Order Management
Business Area Direct to Customer Retail
Business Process Analysis Worksheets and Guidelines
C.1.5 Customer Order Fulfillment Business Process Summaries
C.1.5.1 BPS-4.4-Purchase-Order-Management
Form: Business Process SummaryForm Id BPS-4.4-Purchase-Order-Management
Business Process Name Purchase Order Management
Identifier bpid:ean.1234567890128:PurchaseOrderManagement$1.0
Process Area Customer Order Fulfillment
Business Area Direct to Customer Retail
C.1.5.2 BPS-4.5-Ship-Goods
Form: Business Process SummaryForm Id BPS-4.5-Ship-Goods
Business Process Name Ship Goods
Identifier bpid:ean.1234567890128:ShipGoods$1.0
Process Area Customer Order Fulfillment
Business Area Direct to Customer Retail
C.1.6 Vendor Inventory Management Processes Summaries
C.1.6.1 BPS-4.6-Inventory-Management
Form: Business Process SummaryForm Id BPS-4.6-Inventory-Management
Business Process Name Inventory Management
Identifier bpid:ean.1234567890128:InventoryManagement$1.0
Process Area Vendor Inventory Management
Business Area Direct to Customer Retail
Business Process Analysis Worksheets and Guidelines
C.1.7 Product Catalog Exchange Business Processes Summaries
C.1.7.1 BPS-4.7-Sales-Product-Notification
Form: Business Process SummaryForm Id BPS-4.7-Sales-Product-Notification
Business Process Name Sales Product Notification
Identifier bpid:ean.1234567890128:SalesProductNotification$1.0
Process Area Product Catalog Exchange
Business Area Direct to Customer Retail
C.1.8 Payment Business Process Summaries
C.1.8.1 BPS-4.8-Invoice-Presentment
Form: Business Process SummaryForm Id BPS-4.8- Present-Invoice
Business Process Name Present Invoice
Identifier bpid:ean.1234567890128:PresentInvoice$1.0
Process Area Payment
Business Area Finance
Business Process Analysis Worksheets and Guidelines
C.2 Business Process Elaboration
C.2.1 BPUC-5.1-Firm-Sales-Order
Form: Business Process Use CaseForm Id BPUC-5.1-Firm-Sales-Order
Business Process Name Firm Sales Order
Identifier bpid:ean.1234567890128:FirmSalesOrder$1.0
Actors • Customer• Retailer
Performance Goals • Accept a firm customer sales order for a product, andpromise the customer a delivery time at total sales amountincluding all taxes within seconds after the customer hasmade a product choice and given relevant personal details;ie. while customer is online.
Preconditions • Valid customer details (name, address, credit card)• Valid product details (product SKU details)
Begins When • Customer completes all personal identity data for Retailer.• Customer successfully selects valid product to be
purchased and specifies valid product quantity.• Customer accepts terms of sale.
Definition • Retailer needs to validate customer’s credit limit with aCredit Authority, and if enough credit is available to coverthe product to be purchased, the Retailer will accept theCustomers firm sales order.
Ends When • Valid customer sales order is created in Retailer’sbusiness operating system.
Exceptions • Customer fails internal credit check; ie. fraud.• Customer delivery needs violate Retailers standard terms
of sale.Postconditions •• Valid customer sales order.
• Customer is notified of positive sale, and can expectdelivery within promised delivery time.
Traceability Not Applicable
Business Process Analysis Worksheets and Guidelines
START
Create Order<<BusinessCollaborationTask>>
SUCCESS FAILURE
[ SalesOrder.Status=NEW ][ (CustomerCreditCheck.Status=FAILURE)
OR (SalesOrder.isValidDeliveryRequest=FALSE) ]
Figure , <<BusinessProcessActivityModel>>CreateCustomerOrder
Business Process Analysis Worksheets and Guidelines
C.2.2 BPUC-5.2-Customer-Credit-Inquiry
Form: Business Process Use CaseForm Id BPUC-5.2-Customer-Credit-Inquiry
Business Process Name Customer Credit Inquiry
Identifier bpid:ean.1234567890128:CustomerCreditInquiry$1.0
Actors • Retailer• Credit Authority
Performance Goals • Retailer expects the Credit Authority to perform a creditcard check for a specified sales amount and in seconds.
Preconditions • Customer credit card details known.• Total sales price, including taxes, known.
Begins When • Retailer can present both all customer credit card detailsand a requested total credit amount to be checked againstthis customer.
Definition • Retailer requests Credit Authority to authorize the totalsales amount against the customer’s credit amount.
• The Credit Authority responds to the Retailer with either apositive or negative credit report on the customer.
Ends When • Credit Authority returns either a positive or negativeCustomer report.
Exceptions • Credit Authority fails to respond to Retailer within anacceptable period.
Postconditions • Customer has a reserved credit cash equal to the totalpurchase amount authorized to the Retailer for a 24hour period.
Traceability Not Applicable
Business Process Analysis Worksheets and Guidelines
START
Check Credit<<BusinessCollaborationTask>>
[ Customer.isValid=TRUE ]
SUCCESS FAILURE
[ ConfirmCredit/Status=CREDIT-OK ]
[ ConfirmCredit/Status=CREDIT-NOT-OK ]
Figure 1-10, <<BusinessProcessActivityModel>> CustomerCreditCheck
Business Process Analysis Worksheets and Guidelines
C.2.3 BPUC-5.3-Customer-Credit-Payment
Form: Business Process Use CaseForm Id BPUC-5.3-Customer-Credit-Payment
Business Process Name Customer Credit Payment
Identifier bpid:ean.1234567890128:CustomerCreditPayment$1.0
Actors • Retailer• Credit Authority
Performance Goals • Retailer expects Credit Authority to positively charge theCustomer’s credit for the total sales amount immediatelyupon request.
Preconditions • Confirmed shipment, by Vendor, of purchased productdirect to Customer.
Begins When • Vendor confirms to Retailer that the specified productprescribed on the current updated version of a DSVendor’spurchase order has been actually shipped to the specifiedcustomer.
Definition • Credit Authority makes a credit charge against theCustomer’s account, on behalf of the Retailer.
• Credit Authority reports, to Retailer, the status of the creditcharge.
Ends When • Credit Authority reports back to the Retailer that thecustomer’s credit has been charged for the total salesamount; and thus credited to the Retailer’s account.
Exceptions • Credit Authority reports to Retailer that the customer’scredit account cannot be charged with total sales price.
Postconditions • Credit Authority transfers total sales amount from theCustomer’s account to the Retailer’s account.
Traceability Not Applicable
Business Process Analysis Worksheets and Guidelines
START
Process Credit Payment<<BusinessCollaborationTask>>
SUCCESS
[ Order.ShippingStatus=SHIPPED ]
[ Payment.Status=RECEIVED ]
Figure 1-11, <<BusinessProcessActivityModel>> ProcessCreditPayment
C.2.4 BPUC-5.4-Purchase-Order-Management
Form: Business Process Use CaseForm Id BPUC-5.4-Purchase-Order-Management
Business Process Name Purchase Order Management
Identifier bpid:ean.1234567890128:PurchaseOrderManagement$1.0
Actors • Retailer• Vendor
Performance Goals • DSVendor returns a PO Acknowledgment to the Retailerwithin 4 hours of receipt of the Purchase Order.
Preconditions • Valid Customer sales order with Retailer.• Valid Retailer–DSVendor relation; ie. terms and conditions.
Begins When • Retailer has created a valid Purchase Order Request.
Definition • Upon receiving a Purchase Order Request, the DSVendordoes a product allocation to the PO against availableinventory and returns a positive PO Acknowledgment tothe Retailer.
Ends When • Valid positive PO Acknowledgment returned from theDSVendor to the Retailer.
Exceptions • DSVendor does not return any PO Acknowledgment• DSVendor returns a negative Purchase Order
AcknowledgementPostconditions • DSVendor has allocated correct product to fill Purchase
Order• DSVendor has created all correct instructions for it’s
warehouse management system to pick, pack and ship.
Business Process Analysis Worksheets and Guidelines
Traceability Not Applicable
START
CreateVendorPurchaseOrder<<BusinessCollaborationTask>>
[ SalesOrder.isVal id=TRUE ]
SUCCESS
FAILURE
[ PurchaseOrderResponse.OrderStatus=REJECTED ]
Figure 1-12, Figure , <<BusinessProcessActivityModel>> PurchaseOrderManagement
C.2.5 BPUC-5.5-Ship-Goods
Form: Business Process Use CaseForm Id BPUC-5.5-Ship-Goods
Business Process Name Ship Goods
Identifier bpid:ean.1234567890128:ShipGoods$1.0
Actors • DSVendor• Transport Carrier
Performance Goals • Transport Carrier informs DSVendor within seconds of POpickup, and DSVendor registers PO transport trackingnumber within it’s business operating system withinseconds.
Preconditions • PO has been picked, packed and is ready to be shipped.
Begins When • DSVendor informs Transport Carrier of a PO needing to bedelivered to a specific Customer address.
Definition • DSVendor manifests PO with Transport Carrier• Transport Carrier registers transport, checks “ship to”
details and assigns a tracking number for the shipment.Ends When • Transport Carrier confirms PO pickup to DSVendor and
begin of ordered goods delivery to Customer.Exceptions • Transport Carrier detects that “Ship To” address is invalid.
• Transport Carrier fails to confirm PO pickup.
Business Process Analysis Worksheets and Guidelines
Postconditions • Carrier assigns Transport tracking number to PurchaseOrder and informs DSVendor of tracking number.
Traceability Not Applicable
C.2.6 BPUC-5.6-Inventory-Management
Form: Business Process Use CaseForm Id BPUC-5.6-Inventory-Management
Business Process Name Inventory Management
Identifier bpid:ean.1234567890128:InventoryManagement$1.0
Actors • Retailer• DSVendor
Performance Goals • Once a day, the DSVendor reports their “available on-hand” inventory to the Retailer.
Preconditions • Valid business agreement.
Begins When • Repeating event, occurs unsolicited from DSVendor toRetailer.
Definition • DSVendor reconciles “available on-hand” inventory andreports only product availability for those products whichare agreed upon between Retailer and DSVendor.
Ends When • Retailer has received a valid “available on-hand” inventoryreport from DSVendor.
Exceptions • No “available on-hand” inventory report received.• Reported product quantiry on hand with DSVendor is less
than any prior agreed Safety Stock level with Retailer.Postconditions • Retailers business operating system has recorded new
“available on-hand” inventory by product.Traceability Not Applicable
Business Process Analysis Worksheets and Guidelines
C.2.7 BPUC-5.7-Sales-Product-Notification
Form: Business Process Use CaseForm Id BPUC-5.7-Sales-Product-Notification
Business Process Name Sales Product Notification
Identifier bpid:ean.1234567890128:SalesProductNotification$1.0
Actors • Retailer• DSVendor
Performance Goals • None
Preconditions • Valid DSVendor – Retailer business relationship
Begins When • Initial start of the business relationship, for all relatedproducts.
• Whenever DSVendor has a product specification changeor addition that applies to the Retailer.
Definition • DSVendor initiates a product specification request to “offerfor sale” the Retailer.
• Retailer either accepts product offer, or rejects the offer.Ends When • Retailer responds to DSVendor acceptance or rejection of
product offer for sale.Exceptions • None
Postconditions • On product acceptance, Retailer can register product forsale to Customers.
Traceability Not Applicable
C.2.8 BPUC-5.8-Present-Invoice
Form: Business Process Use CaseForm Id BPUC-5.8-Present-Invoice
Business Process Name Present Invoice
Identifier bpid:ean.1234567890128:PresentInvoice$1.0
Actors • DSVendor• Retailer
Performance Goals •
Preconditions • Valid DSVendor – Retailer business relationship
• Corresponding Purchase Order was accepted
• Related Advance Shipment Notification was sent
Begins When • Whenever DSVendor wants to invoice the Retailer forgoods shipped.
Definition •
Business Process Analysis Worksheets and Guidelines
Ends When •
Exceptions •
Postconditions •
Traceability Not Applicable
Business Process Analysis Worksheets and Guidelines
C.3 Business Collaboration and Economic Events
C.3.1 BC-6.1-Create-Customer-Order
Form: Business CollaborationForm Id BC-6.1-Create-Customer-Order
Identifier bcid:ean.1234567890128:CreateCustomerOrder$1.0
Description The customer enters a sales order using on-line store-frontapplication.
Partner Types Customer
Retailer
Authorized Roles
Legal steps/requirements
Economic consequences14
Initial/terminal events
Scope
Boundary
Constraints
14 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
FAILURE
START
FirmCustomerSalesOrder<<BusinessTransactionActivity>>
SUCCESS
[ Bus inessTranaction("FirmCustomerSalesOrder" ).State=END ]
[ BusinessTranaction("FirmCustomerSalesOrder").State=CONTROL-FAILED ]
RetailerCustomer
Figure 1-13, <<BusinessCollaborationProtocol>> CreateCustomerOrder
Note that in this business collaboration protocol, there is only one business transactionactivity and the Customer (partner type) initiates it. The Retailer, although shown in thediagram for completeness, does not initiate any business transaction activity.
Form: Business Collaboration Protocol Table
Form Id BCPT-7.1-Create-Customer-Order
Identifier bcid:ean.1234567890128:CreateCustomerOrder$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Customer Create Order Retailer NONE
Create Order NOT-APPLICABLE
SUCCESS Customer BusinessTranaction("FirmCustomerSalesOrder").State=END ]
Create Order NOT-APPLICABLE
FAILURE Customer BusinessTranaction("FirmCustomerSalesOrder").State=CONTROL-FAILED ]
Business Process Analysis Worksheets and Guidelines
C.3.2 BC-6.2-Check-Customer-Credit
Form: Business CollaborationForm Id BC-6.2- Check-Customer-Credit
Identifier bcid:ean.1234567890128: CheckCustomerCredit$1.0
Partner Types • Retailer• Credit Authority
Authorized Roles • Retailer• Credit Authority Credit Service
Legal steps/requirements None
Economic consequences15 As the result of the credit check, the customer’s available credit isreduced by the total sales amount for a period of 24 hours.
Initial/terminal events Initial - Valid customer
Terminal – Customer bad credit causes Credit Authority check tofail.
Scope Credit Authority provides necessary information to retailer tocontinue processing order.
Boundary Systems include :
• Credit Authority service.• DSVendor customer order entry system
Constraints None
START
CheckCustomerCredit<<BusinessTransactionActivity>>
SUCCESS
FAILURE
[ BusinessTransaction("Check Customer Credit").State=END ]
[ BusinessTransaction("Check Customer Credit").State=CONTROL-FAILED ]
CreditAuthorityRetailer
Figure 1-14, <<BusinessCollaborationProtocol>> CheckCustomerCredit
15 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
Note that there is only one initiated activity, CheckCustomerCredit, in this collaboration.
Form: Business Collaboration Protocol Table
Form Id BCPT-7.2- Check-Customer-Credit
Identifier bcid:ean.1234567890128:CustomerCreditCheck$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Retailer Check CustomerCredit
Credit Authority
Check CustomerCredit
NOT-APPLICABLE
SUCCESS Retailer BusinessTransaction(“CheckCustomerCredit”).State=END
Check CustomerCredit
NOT-APPLICABLE
FAILURE Retailer BusinessTransaction(“CheckCustomerCredit”).State=CONTROL-FAILED
C.3.3 BC-6.3-Process-Credit- Payment
Form: Business CollaborationForm Id BC-6.3-Process-Credit- Payment
Identifier bcid:ean.1234567890128:ProcessCreditPayment$1.0
Partner Types • Retailer• Credit Authority
Authorized Roles • Retailer.Accounts Receivable• Credit Authority Service
Legal steps/requirements • Sale of goods has taken place•
Economic consequences16 • Retailer receives payment• Customer actually gets charged
Initial/terminal events Initial – Products are being delivered (in-route) or have beendelivered.
Terminal – Retailer receives payment
Scope Credit Authority credits customer’s credit, only after product(s) havebeen shipped (or are being shipped) to customer.
16 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
Boundary Systems include :• Credit Authority payment system
Constraints DSVendor must confirm that shipment of product direct to customerhas taken place.
FAILURE
START
ChargeCustomerCredit<<BusinessTransactionActivity>>
SUCCESS
[ BysinessTransaction("Charge Customer Credit").State=END ]
[ BysinessTransaction("Charge Customer Credit ").State=CONTROL-FAILED ]
CreditAuthorityRetailer
Figure 1-15, <<BusinessCollaborationProtocol>> ProcessCreditPayment
Form: Business Collaboration Protocol Table
Form Id BCPT-7.3-Credit-Card-Payment
Identifier bcid:ean.1234567890128:CreditCardPayment$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Retailer Charge CustomerCredit
Credit Authority NONE
Charge CustomerCredit
NOT-APPLICABLE
SUCCESS Retailer BysinessTransaction("ChargeCustomerCredit").State=END
Charge CustomerCredit
NOT-APPLICABLE
FAILURE Retailer BysinessTransaction("ChargeCustomerCredit").State=CONTROL-FAILED
Business Process Analysis Worksheets and Guidelines
C.3.4 BC-6.4-Create-Vendor-Purchase-Order
Form: Business CollaborationForm Id BC-6.4-Create-Vendor-Purchase-Order
Identifier bcid:ean.1234567890128:CreateVendorPurchaseOrder$1.0
Partner Types • Retailer• DSVendor
Authorized Roles • Retailer.InventoryBuyer• DSVendor.CustomerService
Legal steps/requirements Confirmed PO Acknowledgment implies a binding agreementbetween Retailer and DSVendor, per conditions of an existingbusiness relation and a specific open Purchase Order.
Economic consequences17 • Intent to purchase product (liability)• DSVendor allocates on-hand inventory to cover PO SKU
quantity for immediate direct shipment to customerInitial/terminal events • Valid sales order exists
• Purchase Order responseScope Checking DSVendor on-hand inventory to determine if a Purchase
Order can be accepted or rejected.
Boundary Systems include :• Retailer Purchase Order Management system• DSVendor Customer Order Entry system
Constraints Timely response within 4 hours of submitting PO Request
[ BusinessTransaction("Create Vendor Purchase Order").State=CONTROL-FAILED ]
START
CreateVendorPurchaseOrder<<BusinessTransactionActivity>>
SUCCESS
FAILURE
[ BusinessTransaction("Create Vendor Purchase
Order").State=END ]
[ VendorList.State=NO-MORE-VENDORS ]
DSVendorRetailer
Figure 1-16 , <<BusinessCollaborationProtocol>> CreateVendorPurchaseOrder
17 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
Form: Business Collaboration Protocol Table
Form Id BCPT-7.4-Create-Vendor-Purchase-Order
Identifier bcid:ean.1234567890128:CreateVendorPurchaseOrder$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Retailer Create VendorPurchase Order
DSVendor SalesOrder.Status=VALID
Create VendorPurchase Order
NOT-APPLICABLE
SUCCESS Retailer BusinessTransaction("CreateVendor PurchaseOrder").State=END
Create VendorPurchase Order
NOT-APPLICABLE
Create VendorPurchase Order
Retailer BusinessTransaction("CreateVendor PurchaseOrder").State=CONTROL-FAILED
Create VendorPurchase Order
NOT-APPLICABLE
FAILURE Retailer VendorList.State=NO-MORE-VENDORS
C.3.5 BC-6.5-Shipment-Instruction
Form: Business CollaborationForm Id BC-6.5-Shipment-Instruction
Identifier bcid:ean.1234567890128:ShipmentInstruction$1.0
Partner Types • DSVendor• Transport Carrier
Authorized Roles • DSVendor.Shipper• Transport Carrier.Customer Service
Legal steps/requirements Vendor declares goods of carriage to carrier.(note: for this example we are using domestic shipments only)
Economic consequences18 None
Initial/terminal events Initial – Successful Create Vendor Purchase Order businesscollaboration.Terminal – Transport Carrier provides vendor with transportmanifest.
18 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
Scope Pertains to arrangement of physical transport per prior agreementbetween Retailer and Transport Carrier.
Boundary Systems include :• DSVendor warehouse management / transport planning
system.• Transport Carrier manifesting / Bill of Lading document
management system.Constraints • Electronic shipment manifesting only
• Timely product pickup by transport carrier• DSVendor must use a pre-approved Transport Carrier as
specified by Retailer within Business Document details.
START
ShipmentInstruct ion<<BusinessTransactionActivity>>
[ BusinessTransaction("Create Vendor Purchase Order").State=END ]
SUCCESS
FAILURE
[ BusinessTransaction("Shipment Instruction")=END ]
[ BusinessTransaction("Shipment Instruction")=CONTROL-FAIL ]
TransportCarrierDSVendor
Figure 1-17, <<BusinessCollaborationProtocol>> ShipmentInstruction
Form: Business Collaboration Protocol Table
Form Id BCPT-7.5-Shipment-Instruction
Identifier bcid:ean.1234567890128:ShipmentInstruction$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START DSVendor ShipmentInstruction
TransportCarrier NONE
ShipmentInstruction
NOT-APPLICABLE
SUCCESS NOT-APPLICABLE
BusinessTransaction("ShipmentInstruction")=END
Business Process Analysis Worksheets and Guidelines
ShipmentInstruction
NOT-APPLICABLE
FAILURE NOT_APPLICABLE
BusinessTransaction(“ShipmentInstruction”)=CONTROL-FAIL
C.3.6 BC-6.6-Confirm-Shipment
Form: Business CollaborationForm Id BC-6.6-Confirm-Shipment
Identifier bcid:ean.1234567890128:ConfirmShipment$1.0
Partner Types • Retailer• DSVendor
Authorized Roles • Retailer.Customer Service
• DSVendor.Inventory Management
Legal steps/requirements • DSVendor declares customer shipment to Retailer• Retailer agrees to be billed by DSVendor for original
purchase price on the Purchase Order Acceptance.• (for this scenario, DSVendor provides free shipping to
customers)Economic consequences19 Point of sale between DSVendor and Retailer.
Initial/terminal events • Initial – DSVendor notifies Retailer of shipment• Terminal – DSVendor receives Transport Carrier shipping
instruction.Scope Notification of customer shipment by DSVendor.
Boundary Systems include :• DSVendor PO Management system• DSVendor Financial system• DSVendor Inventory Management system• Retailer PO Management system• Retailer Financial system• Retailer Customer Service Management system
Constraints Retailer must receive Avanced Shipping Note (ASN) asconfirmation of product shipment to customer in a timely fashion,and no later than 4 hours of physical product shipment from theDSVendor’s distribution point.
19 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
START
ConfirmShipment<<BusinessTransactionActivity>>
[ BusinessCollaboration("Shipment Instruction").State=END ]
SUCCESS
FAILURE
[ BusinessTransaction("ConfirmShipment").State= END ]
[ BusinessTransaction("ConfirmShipment").State=CONTROL-FAIL ]
DSVendorRetailer
Figure 1-18, <<BusinessCollaborationProtocol>> ConfirmShipment
Form: Business Collaboration Protocol Table
Form Id BCPT-7.6-Confirm-Shipment
Identifier bcid:ean.1234567890128:ConfirmShipment$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Retailer ConfirmShipment DSVendor NONE
ConfirmShipment NOT-APPLICABLE
SUCCESS NOT-APPLICABLE
BusinessTransaction(“ConfirmShipment”).State=END
ConfirmShipment NOT-APPLICABLE
FAILURE NOT-APPLICABLE
BusinessTransaction(“ConfirmShipment”).State=CONTROL-FAIL
C.3.7 BC-6.7-Vendor-Inventory-Reporting
Form: Business CollaborationForm Id BC-6.7-Vendor-Inventory-Reporting
Identifier bcid:ean.1234567890128:VendorInventoryReporting$1.0
Business Process Analysis Worksheets and Guidelines
Partner Types • Retailer• DSVendor
Authorized Roles • Retailer.Requestor• DSVendor.Reporter
Legal steps/requirements None.
Economic consequences20 None !
Initial/terminal events Initial – Inventory physically exists
Terminal – Retailer receives inventory position report.
Scope The DSVendor is reporting a latest stage of Available to Promisebut makes no warranty that when the Retailer places a PO, therewill be available product to cover the PO. Rather forecasting shouldbe used to cover at least sufficient safety stock.
Boundary Systems include :• Retailer inventory management systems• DSVendor inventory / sales management systems
Constraints Daily reporting by DSVendor. Only affected products, as a result ofthe Catalog Exchange process are to be reported by the DSVendor;and no other products are to be included. DSVendor reportsproduct availability by number of SKU’s, versus a grossclassification of ‘available or not available’.
20 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
START
SUCCESS
FAILURE
VendorInventoryReport<<BusinessTransactionActivi ty>>
[ BusinessTransaction("VendorInventoryReport").State=END ]
[ BusinessTransaction("VendorInventoryReport").State=CONTROL-FAILED ]
DSVendorRetailer
Figure 1-19, <<BusinessCollaborationProtocol>> VendorInventoryReporting
Form: Business Collaboration Protocol Table
Form Id BCPT-7.7-Vendor-Inventory-Reporting
Identifier bcid:ean.1234567890128:VendorInventoryReporting$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START Retailer VendorInventoryReport
DSVendor NONE
VendorInventoryReport
NOT-APPLICABLE
SUCCESS NOT-APPLICABLE
BusinessTransaction(“InventoryReport”).State=END
VendorInventoryReport
NOT-APPLICABLE
FAILURE NOT-APPLICABLE
BusinessTransaction(“InventoryReport”).State=CONTROL-FAILED
C.3.8 BC-6.8-Request-Inventory-Report
Form: Business CollaborationForm Id BC-6.8-Request-Inventory-Report
Business Process Analysis Worksheets and Guidelines
Identifier bcid:ean.1234567890128:RequestInventoryReport$1.0
Partner Types • Retailer• DSVendor
Authorized Roles • Retailer.Inventory Management• DSVendor.Inventory / Customer Service Management
Legal steps/requirements None
Economic consequences21 None
Initial/terminal events See BC-6.7-Vendor-Inventory-Management
Scope See BC-6.7-Vendor-Inventory-Management
Boundary See BC-6.7-Vendor-Inventory-Management
Constraints See BC-6.7-Vendor-Inventory-Management
START
SUCCESS
FAILURE
RequestInventoryReport<<BusinessTransactionActivity>>
[ BusinessTransaction("RequestInventoryReport").State=END ]
[ BusinessTransaction("RequestInventoryReport").State=CONTROL-FAIL ]
DSVendorRetailer
Figure 1-20, <<BusinessCollaborationProtocol>> RequestInventoryReport
Form: Business Collaboration Protocol Table
Form Id BCPT-7.8-Request-Inventory-Report
Identifier bcid:ean.1234567890128:RequestInventoryReport$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
21 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
START Retailer RequestInventoryReport
DSVendor NONE
RequestInventoryReport
NOT-APPLICABLE
SUCCESS NOT-APPLICABLE
BusinessTransaction(“RequestInventoryReport”).State=END
RequestInventoryReport
NOT-APPLICABLE
FAILURE NOT-APPLICABLE
BusinessTransaction(“RequestInventoryReport”).State=CONTROL-FAIL
C.3.9 BC-6.9-Sales-Product-Offering
Form: Business CollaborationForm Id BC-6.9-Sales-Product-Offering
Identifier bcid:ean.1234567890128:SalesProductOffering$1.0
Partner Types • DSVendor• Retailer
Authorized Roles • Retailer.Merchandising• DSVendor.Sales
Legal steps/requirements DSVendor warrants that products offered for consumer sale arevalid and legal.
Economic consequences22 None, unless prior business agreements of minimum salesquantities are applicable.
Initial/terminal events Initial – DSVendor sends Retailer valid product specifications
Terminal – Retailer receives valid product specifications.
Scope At start of a relationship, the DSVendor will offer a full list of allproducts that may be offered for consumer sale by the Retailer.
Boundary Systems include :• DSVendor inventory management systems• Retailer inventory management systems
Constraints Only products intended for consumer resale are offered by theDSVendor to the Retailer. (i.e. No spamming the Retailer).
22 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
[ BusinessTransaction("ProductOffering").State=CONTROL-FAIL ]
START
SUCCESS
FAILURE
ProductOffering<<BusinessTransactionActivity>>
[ BusinessTransaction("ProductOffering").State=END ]
RetailerDSVendor
Figure 1-21, <<BusinessCollaborationProtocol>> SalesProductOffering
Form: Business Collaboration Protocol Table
Form Id BCPT-7.9-Sales-Product-Offering
Identifier bcid:ean.1234567890128:SalesProductOffering$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START DSVendor ProductOffering Retailer NONE
ProductOffering NOT-APPLICABLE
SUCCESS NOT-APPLICABLE
BusinessTransaction(“ProductOffering”).State=END
ProductOffering NOT-APPLICABLE
FAILURE NOT-APPLICABLE
BusinessTransaction(“ProductOffering”).State=CONTROL-FAIL
C.3.10 BC-6.10-Invoice-Presentment
Form: Business CollaborationForm Id BC-6.10-Invoice-Presentment
Identifier bcid:ean.1234567890128:InvoicePresentment$1.0
Partner Types • DSVendor• Retailer
Business Process Analysis Worksheets and Guidelines
Authorized Roles • Retailer.ProcessPayment• DSVendor.ProcessPayment
Legal steps/requirements
Economic consequences23
Initial/terminal events
Scope
Boundary •
Constraints
START
SUCCESS
FAILURE
PresentInvoice<<BusinessTransactionAct ivity>>
[ BusinessTransaction("PresentInvoice").State=END ]
[ BusinessTransaction("PresentInvoice").State=CONTROL-FAIL ]
RetailerDSVendor
Figure 1-22, <<BusinessCollaborationProtocol>> InvoicePresentment
Form: Business Collaboration Protocol Table
Form Id BCPT-7.10-Invoice-Presentment
Identifier bcid:ean.1234567890128:InvoicePresentment$1.0
From BusinessActivity(Transaction)
Initiating PartnerType
BusinessActivity
Responding/ReceivingPartner Type
TransitionCondition
START DSVendor Present Invoice Retailer NONE
23 Worksheets that address REA to greater detail and help users through the process of developing REA orientedcollaborations will be developed in the future.
Business Process Analysis Worksheets and Guidelines
Present Invoice DSVendor SUCCESS NOT-APPLICABLE
BusinessTransaction(“PresentInvoice”).State=END
Present Invoice DSVendor FAILURE NOT-APPLICABLE
BusinessTransaction(“PresentInvoice”).State=CONTROL-FAIL
Business Process Analysis Worksheets and Guidelines
C.4 Business Transactions and Authorized Roles
C.4.1 BT-8.1-Firm-Customer-Sales-Order
Form: Business TransactionForm Id BT-8.1-Firm-Customer-Sales-Order
Identifier btid:ean.1234567890128:FirmCustomerSalesOrder$1.0
Description Register customer demand for specific product to be fulfilled.
Pattern Business Transaction (per UMM pattern specification)
Agents and Services
Business activities andassociated authorized roles
Constraints • Valid Customer• Valid Product• Valid Vendor
Requesting Partner Type Customer
Requesting Activity Role Buying Customer
Requesting ActivityDocument
Sales Order
Responding Partner Type Retailer
Responding Activity Role Customer Service
Responding ActivityDocument
Confirmation email
Business Process Analysis Worksheets and Guidelines
CONTROL-FAILED
START
Data Entry<<CommercialTransactionActivity>>
Sales Order : HttpPostEND Process Sales
Order
Confirmation : Email
[ SalesOrder.Status=ACCEPTED ]
[ SalesOrder.Status=REJECTED ]
CustomerSe rv ice:Res pondingRoleBuyingCustomer:RequestingRole
Figure 1-23, <<BusinessTransaction>> FirmCustomerSalesOrder
C.4.2 BT-8.2-Check Customer Credit
Form: Business TransactionForm Id BT-8.2-Check Customer Credit
Identifier btid:ean.1234567890128:CheckCustomerCredit$1.0
Description With complete customer details, including a total sales amount,check the customer’s credit ability to eventually pay for productonce drop shipped from the vendor.
Pattern Request/Response (according to UMM)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.2- Check-Customer-Credit
Constraints • Valid business agreement with vendor• Valid customer details
Requesting Partner Type Retailer
Requesting Activity Role Customer Service
Requesting ActivityDocument
Credit Check (typically a proprietary document)
Business Process Analysis Worksheets and Guidelines
Responding Partner Type Credit Authority
Responding Activity Role Credit Service
Responding ActivityDocument
proprietary document
Form: Business Transaction Transition Table
Form Id BTTT-8.2- Check-Customer-Credit
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE RequestCheck Credit
Retailer.CustomerService
NONE
RequestCheck Credit
Retailer.CustomerService
Credit CheckRequest
ProcessCredit Check
CreditAuthority.CreditService
NONE
ProcessCredit Check
CreditAuthority.CreditService
Credit CheckResponse
RequestCheck Credit
Retailer.CustomerService
NONE
RequestCheck Credit
Retailer.CustomerService
NONE END NOT-APPLICABLE
CreditCheckResponse.Status=GOOD-CREDIT
RequestCheck Credit
Retailer.CustomerService
NONE CONTROL-FAILED
NOT-APPLICABLE
CreditCheckResponse.Status=BAD-CREDIT
C.4.3 BT-8.3-Charge-Customer-Credit
Form: Business TransactionForm Id BT-8.3-Charge-Customer-Credit
Identifier btid:ean.1234567890128:ChargeCustomerCredit$1.0
Description Given all customer details, plus total sales amount based onproduct actually shipped by DSVendor, do a charge on thecustomer’s credit.
Pattern Business Transaction (per UMM patterns)
Agents and Services
Business Process Analysis Worksheets and Guidelines
Business activities andassociated authorized roles
See BTTT-8.3-Charge-Customer-Credit
Constraints Valid sales orderConfirmed Shipped product
Requesting Partner Type Retailer
Requesting Activity Role ChargeCredit
Responding Partner Type Credit Authority
Responding Activity Role CreditService.ChargeCredit
Form: Business Transaction Transition Table
Form Id BTTT-8.3-Charge-Customer-Credit
From Activity From Role Document To Activity To Role GuardCondition
START N/A N/A RequestCreditCharge
Retail.ChargeCredit
NONE
RequestCreditCharge
Retail.ChargeCredit
ChargeCredit ProcessCreditCharge
CreditAuthority.CreditService
NONE
ProcessCreditCharge
CreditAuthority.CreditService
ConfirmCredit RequestCreditCharge
Retail.ChargeCredit
NONE
RequestCreditCharge
Retail.ChargeCredit
N/A END N/A Message(ConfirmCredit).Status=RECEIVED
RequestCreditCharge
Retail.ChargeCredit
N/A CONTROL-FAILED
N/A Message(ConfirmCredit).Status =NOT-RECEIVED
C.4.4 BT-8.4-Create-Vendor-Purchase-Order
Form: Business TransactionForm Id BT-8.4-Create-Vendor-Purchase-Order
Identifier btid:ean.1234567890128:FirmCustomerSalesOrder$1.0
Description Given a multi-vendor / single product relationship, Retailer needs tosend a DSVendor a Purchase Order REQUEST, which will need tobe responded back (with confirmed allocated product to cover thePO) by the DSVendor.
Business Process Analysis Worksheets and Guidelines
Pattern Business Transaction (per UMM patterns)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.4-Create-Vendor-Purchase-Order
Constraints Valid Sales order
Valid customer credit check
Requesting Partner Type Retailer
Requesting Activity Role Inventory Buyer
Requesting ActivityDocument
Purchase Order Request
Responding Partner Type DSVendor
Responding Activity Role Seller
Responding ActivityDocument
Purchase Order Acknowledgement
START
Create Purchase Order<<CommercialTransactionActivity>>
Purchase Order Request
END CONTROL-FAILED
Process Purchase Order
Firm Purchase Order Acknowledgment
[ Order.Status<>REJECTED ]
[ Order.Status=REJECTED ]
CustomerServ ice:RespondingRoleInv entoryBuyer:RequestingRole
Figure 1-24, <<BusinessTransaction>> PurchaseOrderRequest
Business Process Analysis Worksheets and Guidelines
Form: Business Transaction Transition Table
Form Id BTTT-8.4-Create-Vendor-Purchase-Order
From Activity From Role Document To Activity To Role GuardCondition
START N/A N/A CreatePurchaseOrder
InventoryBuyer
NONE
CreatePurchaseOrder
InventoryBuyer
PurchaseOrderRequest
ProcessPurchaseOrder
CustomerService
NONE
ProcessPurchaseOrder
CustomerService
FirmPurchaseOrderAcknowledgement
CreatePurchaseOrder
InventoryBuyer
NONE
CreatePurchaseOrder
InventoryBuyer
N/A END N/A Order.Status<>REJECTED
CreatePurchaseOrder
InventoryBuyer
N/A CONTROL-FAILED
N/A Order.Status=REJECTED
C.4.5 BT-8.5-Vendor-Inventory-Report
Form: Business TransactionForm Id BT-8.5-Vendor-Inventory-Report
Identifier btid:ean.1234567890128:VendorInventoryReport$1.0
Description Regular periodic notification, unsolicited, from the DSVendor to theRetailer, containing Available to Promise On-Hand inventory.
Pattern Notification (per UMM pattern specifications)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.5-Vendor-Inventory-Report
Constraints Only send product inventory which has been agreed to be madeconsumer available per agreement from the Product CatalogExchange negotiation pattern.
Requesting Partner Type DSVendor
Requesting Activity Role Inventory Buyer
Business Process Analysis Worksheets and Guidelines
Requesting ActivityDocument
Inventory Report
Responding Partner Type Retailer
Responding Activity Role Inventory Buyer
Responding ActivityDocument
On-hand Product availability
START
END
CONTROL-FAIL
Report Inventory<<NotificationActivity>>
Inventory Report
Process Inventory Report
[ Message(" Inventory Report").State=RECIEVED ]
[ (Message("Inventory Report").State<>RECIEVED) OR (InventoryReport. Item().Quantity < Agreement.Item().SafetyStockLevel) ]
Inv entoryBuyer:ResponsidngRoleCustomerServ ice:Reques tingRole
Figure 1-25, <<BusinessTransaction>> VendorInventoryReport
Form: Business Transaction Transition Table
Form Id BTTT-8.5-Vendor-Inventory-Report
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE ReportInventory
DSVendor.CustomerService
NONE
ReportInventory
DSVendor.CustomerService
InventoryReport
ProcessInventoryReport
Retailer.InventoryBuyer
NONE
ReportInventory
DSVendor.CustomerService
NONE END N/A Message(“InventoryReport”).State
Business Process Analysis Worksheets and Guidelines
=RECIEVED
ReportInventory
DSVendor.CustomerService
NONE CONTROL-FAILED
N/A Message(“InventoryReport”).State<>RECEIVEDORInventoryReport..Item().Quatntity<Agreement.Item().SafteyStockLevel
C.4.6 BT-8.6-Request-Inventory-Report
Form: Business TransactionForm Id BT-8.6-Request-Inventory-Report
Identifier btid:ean.1234567890128:RequestInventoryReport$1.0
Description Query Response dialogue where the Retailer requests theDSVendor for the current Avaialable to Promise position of aproduct; or series of products.
Pattern Query / Response (per UMM pattern specirfications)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.6-Request-Inventory-Report
Constraints See BT-8.5-Vendor-Inventory-Report
Requesting Partner Type Retailer
Requesting Activity Role Inventory Buyer
Requesting ActivityDocument
On-hand Available to Promise Product Availability Request
Responding Partner Type DSVendor
Responding Activity Role Customer Service
Responding ActivityDocument
on-hand Available to Promise report
Business Process Analysis Worksheets and Guidelines
Inventory Information Query Response
START
QueryVendorInventory<<QueryResponseActivity>>
END
[ Message(InventoryInformationQueryResponse).Status =RECEIVED ]
CONTROL-FAILED
[ Message(InventoryInformationQueryResponse).Status=NOT-RECEIVED ]
Inventory Information Query
Process Inventory Information Query
CustomerService:RespondingRoleInventoryBuyer:RequestingRole
Figure 1-26, <<BusinessTransaction>> RequestInventoryReport
Form: Business Transaction Transition Table
Form Id BTTT-8.6-Request-Inventory-Report
From Activity From Role Document To Activity To Role GuardCondition
START N/A N/A QueryVendorInventory
InventoryBuyer
NONE
QueryVendorInventory
InventoryBuyer
InventoryInformationQuery
ProcessInventoryInformationQuery
CustomerService
NONE
ProcessInventoryInformationQuery
CustomerService
InventoryInformationQueryResponse
QueryVendorInventory
InventoryBuyer
NONE
QueryVendorInventory
InventoryBuyer
N/A END N/A Message(InventoryInformationQueryResponse).Status
Business Process Analysis Worksheets and Guidelines
=RECEIVED
QueryVendorInventory
InventoryBuyer
N/A CONTROL-FAILED
N/A Message(InventoryInformationQueryResponse).Status=NOT-RECEIVED
C.4.7 BT-8.7-Shipment-Notification
Form: Business TransactionForm Id BT-8.7-Shipment-Notification
Identifier btid:ean.1234567890128:FirmCustomerSalesOrder$1.0
Description Arrangement of carriage by the DSVendor towards a TransportCarrier; who is expected to physically ship the product direct to theCustomer.
Pattern Business Transaction (per UMM pattern specifications)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.7-Shipment-Notification
Constraints Customer Ship To details must be accurate
Requesting Partner Type DSVendor
Requesting Activity Role Shipper
Requesting ActivityDocument
Shipment Instruction (UN/CEFACT EDIFACT IFTMIN D01)
Responding Partner Type Transport Carrier
Responding Activity Role Customer Service
Responding ActivityDocument
Electronic copy of a Bill of Lading (UN/CEFACT EDIFACT IFTMCSD01)
Business Process Analysis Worksheets and Guidelines
CONTROL-FAILED
START
Create Shipment Instruction<<BusinessTransactionActivity>>
ShipmentInstruction
END Process ShipmentInstruction
Bill OfLading
[ ShipmentInstruction.Status=ACCEPTED ]
[ (TransportManifest.Status=INVALID-SHIP-TO) OR (Message("ShipmentInstruction").Status=NOT-ACKNOWLEDGED ]
Carrier:RespondingRoleShipper:RequestingRol
Figure 1-27, <<BusinessTransaction>> ShipmentInstruction
Form: Business Transaction Transition Table
Form Id BTTT-8.7-Shipment-Notification
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE PrepareShippingInstruction
DSVendor.Shipper
NONE
PrepareShippingInstruction
DSVendor.Shipper
ShipmentInstruction
ProcessShipmentInstruction
TransportCarrier.CustomerService
NONE
ProcessShipmentInstruction
TransportCarrier.CustomerService
Bill Of Lading ProcessShipmentInstruction
DSVendor.Shipper
NONE
ProcessShipmentInstruction
DSVendor.Shipper
NONE END NOT-APPLICABLE
Message(“BillOfLading”).State=RECIEVED
ProcessShipmentInstruction
DSVendor.Shipper
NONE CONTROL-FAILED
NOT-APPLICABLE
Message(“BillOfLading”).State<>RECEIVED
Business Process Analysis Worksheets and Guidelines
24
C.4.8 BT-8.8-Confirm-Shipment
Form: Business TransactionForm Id BT-8.8-Confirm-Shipment
Identifier btid:ean.1234567890128:FirmCustomerSalesOrder$1.0
Description DSVendor informs the Retailer that the Customer’s product hasbeen shipped to the Customer; and thus the conditions of the POhave been fulfilled.
Pattern Notification
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.8-Confirm-Shipment
Constraints � Product must actually be shipped
� DSVendor must return a Transport Carrier trackingnumber; for customer service.
Requesting Partner Type DSVendor
Requesting Activity Role Shipper
Requesting ActivityDocument
Advance Ship Notice (UN/CEFACT EDIFACT DESADV D01)
Responding Partner Type Retailer
Responding Activity Role Customer Service
Responding ActivityDocument
NONE
24 DSVendor.Shipper may get an emial or phone calls stating that the goods will not be shipped.
Business Process Analysis Worksheets and Guidelines
START
Confirmation of Pickup<<NotificationActivity>>
Advance ShipNoticeEND
CONTROL-FAILED
Process Advance ShipNotice
[ Message("AdvanceShipNotice").Status=DELIVERED ]
[ Message("AdvanceShipNotice").Status<>DELIVERED ]
CustomerService:RespondingRolShipper:RequestingRol
Figure 1-28, <<BusinessTransaction>> ConfirmShipment
Form: Business Transaction Transition Table
Form Id BTTT-8.8-Confirm-Shipment
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE Confirmationof Pickup
Shipper NONE
Confirmationof Pickup
Shipper Advance ShipNotice
ProcessAdvance ShipNotice
Retailer.CustomerService
NONE
Confirmationof Pickup
Shipper NONE END NOT-APPLICABLE
Message(“Advance ShipNotice”).State=RECEIVED
Confirmationof Pickup
Shipper NONE CONTROL-FAILED
NOT-APPLICABLE
Message(“Advance ShipNotice”).State<>RECEIVED
Business Process Analysis Worksheets and Guidelines
C.4.9 BT-8.9-Product-Offering
Form: Business TransactionForm Id BT-8.9-Product-Offering
Identifier btid:ean.1234567890128:ProductOffering$1.0
Description DSVendor offers product details to the Retailer, where the Retaileris expected to either accept the DSVendor’s product for consumersale or reject the product; perhaps because of unacceptableproduct terms and conditions.
Pattern Request / Confirm (per UMM pattern specifications)
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.9-Product-Offering
Constraints Valid products for consumer sale by Retailer
Requesting Partner Type DSVendor
Requesting Activity Role Catalog Publishing
Requesting ActivityDocument
Product Catalog Offering (ANSI X.12 832 4010 version)
Responding Partner Type Retailer
Responding Activity Role Merchandising
Responding ActivityDocument
Product Catalog Acceptance (often proprietary format responsedocument)
Business Process Analysis Worksheets and Guidelines
START
Submit Product Catalog Offering
<<RequestConfirmActivity>>
END
[ ProductCatalogAcceptance.Status= ACCEPTED-AS-IS ]
CONTROL-FAILED
[ ProductCatalogAcceptance.Status= REJECTED ]
Product Catalog Process Product
Catalog
Product Catalog Acceptance
Retailer:RespondingRoleCatlogPublishing:RequestingRole
Figure 1-29, <<BusinessTransaction>> ProductOffering
Form: Business Transaction Transition Table
Form Id BTTT-8.9-Product-Offering
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE SubmitProductCatalogOffering
CatalogPublishing
NONE
SubmitProductCatalogOffering
CatalogPublishing
ProductCatalog
ProcessProductCatalog
Retailer.Merchandising
NONE
ProcessProductCatalog
Retailer.Merchandising
ProductCatalogAcceptance
SubmitProductCatalogOffering
CatalogPublishing
NONE
SubmitProductCatalogOffering
CatalogPublishing
NONE END NOT-APPLICABLE
ProductCatalogAcceptance.Status=ACCEPTED-AS-IS
SubmitProductCatalog
CatalogPublishing
NONE CONTROL-FAILED
NOT-APPLICABLE
ProductCatalogAcceptance.Status=REJE
Business Process Analysis Worksheets and Guidelines
Offering CTED
C.4.10 BT-8.11-Present-Invoice
Form: Business TransactionForm Id BT-8.11-Present-Invoice
Identifier btid:ean.1234567890128:PresentInvoice$1.0
Description This is the vendor’s invoice to the retailer for products and servicesshipped to customer.
Pattern Notification
Agents and Services
Business activities andassociated authorized roles
See BTTT-8.11-Present-Invoice
Constraints � The invoice shall only be sent after confirmed shipment
� The invoice shall reflect the confirmed shipment
Requesting Partner Type DSVendor
Requesting Activity Role Payee
Requesting ActivityDocument
Invoice
Responding Partner Type Retailer
Responding Activity Role Payor
Responding ActivityDocument
NONE
Business Process Analysis Worksheets and Guidelines
START
PresentInvoice<<NotificationActivity>>
Invoice
END
CONTROL-FAIL
Process Invoice
[ Message("Invoice").State=RECIEVED ]
[ (Message("Invoice").State<>NOT-RECIEVED) OR (ThreeWayMatch(Invoice).State=VALID) ]
PayorPayee
Figure 1-30, <<BusinessTransaction>> PresentInvoice
Form: Business Transaction Transition Table
Form Id BTTT-8.11-Present-Invoice
From Activity From Role Document To Activity To Role GuardCondition
START NOT-APPLICABLE
NONE PresentInvoice
Payee NONE
PresentInvoice
Payee Invoice ProcessInvoice
Payor NONE
PresentInvoice
Payee NONE END NOT-APPLICABLE
Message(“Invoice”).State=RECEIVED
PresentInvoice
Payee NONE CONTROL-FAILED
NOT-APPLICABLE
Message(“Invoice”).State<>RECEIVEDORThreeWayMatach(Invoice).State=VALID
Business Process Analysis Worksheets and Guidelines
C.5 Business Information Description
C.5.1 Purchase Order
C.5.1.1 Purchase Order Business Information Context
Form: Business Information ContextForm Id: BIC-10.1-Purchase-Order
Industry Retail
Business Process BPUC-5.4-Purchase-Order-Management
BC-8.4-Create-Vendor-Purchase-Order
BT-8.4-Create-Vendor-Purchase-Order
Product NOT-APPLICABLE
Physical Geography/Conditions /Region
Temporal
Geo-Political Legislative/Regulatory/ Cultural
Application Processing
Business Purpose /Domain
Partner Role
Service Level (profiles – notpreferences.)
Virtual marketplace
Info. Structural Context
Contracts/ Agreements
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es96
Cop
yrig
ht ©
ebX
ML
2001
. All R
ight
s Re
serv
ed.
C.5
.1.2
C
D-9
.1-O
rder
1
Form
: Con
tent
Des
crip
tion
Form
Id:
CD
-9.1
-Ord
er
Elem
ent/C
ompo
nent
Nam
eO
ccur
sDa
taTy
peFi
eld
Wid
thSe
man
tic D
escr
iptio
nNo
tes
Ord
er H
eade
r1
N/A
The
Ord
er H
eade
r con
tain
s th
e he
ader
info
rmat
ion
of th
e or
der
Ord
er D
etai
l0.
.1N
/ATh
e O
rder
Det
ail c
onta
ins
the
line
item
and
pack
age
deta
ils o
f the
Ord
er.
Ord
er S
umm
ary
0..1
N/A
The
Ord
er S
umm
ary
cont
ains
the
sum
mar
y in
form
atio
n of
the
orde
r, ty
pica
llyto
tals
of n
umer
ical f
ield
s
2
C.5
.1.3
C
D-#
.#-O
rder
-Sum
mar
y3
Form
: Con
tent
Des
crip
tion
Form
Id:
CD
-9.2
-Ord
er-S
umm
ary
Elem
ent/C
ompo
nent
Nam
eO
ccur
sDa
taTy
peFi
eld
Wid
thSe
man
tic D
escr
iptio
nNo
tes
Num
ber O
f Lin
es0.
.1In
tege
rN
umbe
r Of L
ines
iden
tifie
s th
e nu
mbe
r of
line
item
s.
Tota
l Tax
0..1
Mon
etar
y Va
lue
N/A
Tota
l Tax
con
tain
s th
e to
tal t
ax a
mou
nt fo
rth
e O
rder
.
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es
Tota
l Am
ount
0..1
Mon
etar
y Va
lue
N/A
Tota
l Am
ount
con
tain
s th
e to
tal p
rice
for
the
entir
e O
rder
.
Tran
spor
t Pac
kagi
ng T
otal
s0.
.1Tr
ansp
ort P
acka
ging
Tot
als
is a
sum
mar
yof
tran
spor
t and
pac
kagi
ng in
form
atio
n if
inclu
ded
in th
e O
rder
.
Sum
mar
y N
ote
0..1
Strin
gSu
mm
ary
Not
e co
ntai
ns a
ny fr
ee fo
rm te
xtfo
r the
Ord
er S
umm
ary.
Thi
s el
emen
t may
cont
ain
note
s or
any
oth
er s
imila
rin
form
atio
n th
at is
not
con
tain
ed e
xplic
itlyin
the
anot
her s
truct
ure.
You
sho
uld
not
assu
me
that
the
rece
iving
app
licat
ion
isca
pabl
e of
doi
ng m
ore
than
sto
ring
and/
ordi
spla
ying
this
info
rmat
ion
4
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es
C.5
.2
Con
tent
Map
ping
5
[If w
e fe
el s
o am
bitio
us, w
e ca
n us
e th
e AN
SI X
12 4
010
map
ping
s av
aila
ble
at h
ttp://
ww
w.x
cbl.o
rg/x
cbl3
0/M
appi
ng/s
mg.
htm
l]6
Thes
e fo
rms
SHO
ULD
be
com
plet
ed.
This
info
rmat
ion
is ve
ry im
porta
nt a
s it
show
s th
at th
e do
cum
ents
hav
e a
basis
in e
xistin
g st
anda
rds.
7Fu
rther
mor
e, th
e in
form
atio
n w
ill be
use
d to
cre
ate
docu
men
t tra
nsfo
rmat
ions
. St
anda
rds
to m
ap to
incl
ude
EDIF
ACT,
X12
, xC
BL, R
oset
taN
et, a
nd8
othe
r sta
ndar
ds s
uch
as O
BI.
Use
XPA
TH a
nd X
SLT
nota
tion
for r
efer
encin
g XM
L el
emen
ts a
nd d
escr
ibin
g th
e m
appi
ngs.
If a
new
doc
umen
t9
sche
ma
is cr
eate
d to
fulfil
the
cont
ent r
equi
rem
ents
spe
cifie
d in
the
Doc
umen
t Con
tent
Des
crip
tion
form
s, th
en a
set
of C
onte
nt M
appi
ng fo
rms
shou
ld10
be c
ompl
eted
for t
hat s
chem
a (th
e co
mpo
nent
nam
es in
the
form
s ar
e sim
ply
requ
irem
ents
for i
nfor
mat
ion)
11
For e
ach
Con
tent
Des
crip
tion
form
, com
plet
e a
Doc
umen
t Con
tent
Map
ping
form
for e
ach
stan
dard
to b
e cr
oss-
refe
renc
ed.
12
C.5
.2.1
C
M-1
1.1-
Ord
er-S
umm
ary
13
Form
: Con
tent
Map
ping
Form
Id:
CM
-11.
1-O
rder
-Sum
mar
y
Cont
ent D
escr
iptio
n Fo
rm Id
CD
-11.
1-O
rder
-Sum
mar
y
Stan
dard
ANSI
X12
850
Vers
ion
4010
Elem
ent/C
ompo
nent
Nam
eM
appi
ng/T
rans
form
atio
nNo
te
Num
ber O
f Lin
es85
0:S:
CTT
:010
:CTT
:01:
354:
Tota
l Tax
NO
T U
SED
Tota
l Am
ount
Vario
us (8
50:S
:CTT
:020
:AM
T:02
:782
:, et
c.)
Tota
l am
ount
is a
com
plex
stru
ctur
e th
atin
clude
s th
ings
like
refe
renc
e cu
rrenc
y, ta
rget
curre
ncy,
and
rate
of e
xcha
nge.
For
an
exam
ple
map
ping
see
xC
BL.o
rg).
Do
map
ping
DR
AFT
Busin
ess
Proc
ess
Anal
ysis
Wor
kshe
ets
and
Gui
delin
es
in a
sep
arat
e ta
ble.
Tran
spor
t Pac
kagi
ngTo
tals
Vario
usTr
ansp
ort p
acki
ng to
tals
is a
com
plex
stru
ctur
e.D
o m
appi
ng in
a s
epar
ate
tabl
e.
Sum
mar
y N
ote
850:
S:C
TT:0
10:C
TT:0
2:34
7:
14
Business Process Analysis Worksheets and Guidelines
Business Process Analysis Worksheets and Guidelines
Copyright © ebXML 2001. All Rights Reserved.
Appendix D Disclaimer15
The views and specification expressed in this document are those of the authors and are not16necessarily those of their employers. The authors and their employers specifically disclaim17responsibility for any problems arising from correct or incorrect implementation or use of this18design.19
Appendix E Contact Informat ion20
Business Process Project Team21Business Process/Core Components (CC/BP) Analysis Team Lead22 Name: Brian Hayes23 Company: Commerce One24 Street: 4440 Rosewood Drive25 City, State, ZIP/Other: Pleasanton, CA26 Nation: USA27 Phone: +1 (925) 788-630428 EMail: [email protected]
30Editors31
32 Name: Charles Fineman33 Company: Arzoon34 Street: 1950 Elkhorn Court35 City, State, ZIP/Other: San Mateo, CA 9440336 Phone: +1 (650) 357-605237
EMail: fineman@arzoon3839
Name: Brian Hayes40 Company: Commerce One41 Street: 4440 Rosewood Drive42 City, State, ZIP/Other: Pleasanton, CA43 Nation: USA44 Phone: +1 (925) 788-630445
EMail: [email protected]
Name: Jennifer Loveridge48 Company: Nordstrom.com49 Street:50 City, State, ZIP/Other: Seattle, WA51 Nation: USA52 Phone:53
EMail: [email protected]
Name: David Welsh57 Company: Nordstrom.com58 Street:59 City, State, ZIP/Other: Seattle, WA60 Nation: USA61 Phone: +1 (206) 215-729362
EMail: [email protected]
Business Process Analysis Worksheets and Guidelines
Copyright Statement65Copyright © ebXML 2001. All Rights Reserved.66
This document and translations of it may be copied and furnished to others, and derivative works67that comment on or otherwise explain it or assist in its implementation may be prepared, copied,68published and distributed, in whole or in part, without restriction of any kind, provided that the69above copyright notice and this paragraph are included on all such copies and derivative works.70However, this document itself may not be modified in any way, such as by removing the copyright71notice or references to ebXML, UN/CEFACT, or OASIS, except as required to translate it into72languages other than English.73
The limited permissions granted above are perpetual and will not be revoked by ebXML or its74successors or assigns. This document and the information contained herein is provided on an "AS75IS" basis and ebXML DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING76BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN77WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY78OR FITNESS FOR A PARTICULAR PURPOSE.79
80
Page: 6[F1]p5, s4.1 I was thinking for a moment that it would be nice if thesubject of the document (worksheets and guidelines) got mentionedearlier than the fourth paragraph. But, I won't make the suggestion:the subject is mentioned on the title of the document.
Page: 12[F2]Good Enough?[F3]grrr… cant get rid of this note �Page: 30[F4]What goes here?