BPWS Print

Business Process Analysis Worksheets
and Guidelines
Procedures for Developing Business Processes in ebXML
v1!
Business Process "ea#
1! May $!!1
(This document is the non-normative version formatted for printing, July 2001)
Copyright !"C#$%CT and &%'(', 2001) %ll *ights *eserved)
+usiness ,rocess Team -ay 2001
This document and translations of it may .e copied and furnished to others, and derivative /or0s that comment on
or other/ise e1plain it or assist in its implementation may .e prepared, copied, pu.lished and distri.uted, in /hole
or in part, /ithout restriction of any 0ind, provided that the a.ove copyright notice and this paragraph are included
on all such copies and derivative /or0s) 2o/ever, this document itself may not .e modified in any /ay, such as .y
removing the copyright notice or references to e.3-4, !"C#$%CT, or &%'(', e1cept as re5uired to translate it
into languages other than #nglish)
The limited permissions granted a.ove are perpetual and /ill not .e revo0ed .y e.3-4 or its successors or assigns)
This document and the information contained herein is provided on an 6%' ('6 .asis and e.3-4 7('C4%(-'
%44 8%**%!T(#', #3,*#'' &* (-,4(#7, (!C47(!9 +T !&T 4(-(T#7 T& %!: 8%**%!T:
T2%T T2# '# &$ T2# (!$&*-%T(&! 2#*#(! 8(44 !&T (!$*(!9# %!: *(92T' &* %!: (-,4(#7
8%**%!T(#' &$ -#*C2%!T%+(4(T: &* $(T!#'' $&* % ,%*T(C4%* ,*,&'#)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2 of ;;
"able of %ontents
1Status of this Document...............................................................................................................7
2ebXML Participants....................................................................................................................8
3Introduction..................................................................................................................................9
3.1Summary.................................................................................................................................9
3.2Audience...............................................................................................................................10
3.3Related documents................................................................................................................10
3.4Document conventions.........................................................................................................11
Desi!n "b#ecti$es.......................................................................................................................12
4.1Goals/objectives/reuirements/!roblem descri!tion............................................................12
4.2"#e analo$y..........................................................................................................................13
4.3%aveats and assum!tions.....................................................................................................14
%&or'sheet (ased )na*+sis "$er$ie,.......................................................................................1%
&.1'asic $uidelines (or (illin$ out )or*s#eets...........................................................................1+
<)1)1$ocus on pu.lic .usiness processes)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1=
<)1)2The *#% ontology)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1=
<)1)>se the /or0sheets in the order that ma0es the most sense for you)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1=
<)1)?The /or0sheets can .e used for pro@ects of various scopes))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1A
<)1)<Thin0 ho/ /ill people use /hat you construct)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1A
<)1)=*e-use is one of the primary goals of e.3-4))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1A
<)1)A!ote on optional fields in the /or0sheets)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1A
<)1)B!um.er your /or0sheets)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))1B
&.2,or*s#eets to metamodel ma!!in$......................................................................................19
-(usiness Process Identification and Disco$er+........................................................................21
+.1Goals....................................................................................................................................21
+.2Guidelines.............................................................................................................................22
=)2)12o/ does one decide ho/ .ig to ma0e the various groupings at this levelC))))))))))))))))))))))))))))))))))))))))))))))22
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age > of ;;
=)2)28hat is the .oundary of the .usiness areaC)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))22
+.3,or*s#eets............................................................................................................................23
=)>)1+usiness reference model))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))2>
=)>)2+usiness area)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))2>
=)>)>,rocess area)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))2?
=)>)?(dentify .usiness processes))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))2<
7(usiness Process .*aboration....................................................................................................2-
-.1Goals....................................................................................................................................2+
-.2,or*s#eet.............................................................................................................................2+
8.conomic .*ements....................................................................................................................28
..1Goals....................................................................................................................................2.
..2Guidelines.............................................................................................................................2.
..3,or*s#eets............................................................................................................................29
9(usiness /o**aboration..............................................................................................................31
9.1Goals....................................................................................................................................31
9.2,or*s#eets ...........................................................................................................................32
10(usiness 1ransactions and )uthori2ed 3o*es ......................................................................3
10.1Goals..................................................................................................................................34
10.2Guidelines...........................................................................................................................34
10)2)1se transaction patterns)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))>?
10)2)27etail transaction activities only if necessary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))>?
10.3,or*s#eets..........................................................................................................................3&
11(usiness Information Description..........................................................................................37
11.1Goals..................................................................................................................................3-
11.2Guidelines...........................................................................................................................3-
11.3,or*s#eets..........................................................................................................................3.
11)>)1+usiness information conte1t))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))>B
11)>)27ocument content description)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))>;
11)>)>Content mapping))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))>;
1.(usiness Process Identifier 4amin! Scheme..........................................................................1
2.1he Porter 5a*ue /hain...........................................................................................................3
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ? of ;;
3.Drop Ship Scenario .6amp*e...................................................................................................%
'usiness !rocess identi(ication and discovery/ 'R011.01direct1to1customer1dro!1s#i!1retail1
model.........................................................................................................................................4-
+usiness areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?B
7irect to customer retail process areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<0
$inancial process areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<?
Customer-order-management .usiness process summaries))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<<
Customer order fulfillment .usiness process summaries))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
Dendor inventory management processes summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
,roduct catalog e1change .usiness processes summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
,ayment .usiness process summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<A
'usiness !rocess elaboration....................................................................................................&-
+,C-<)1-$irm-sales-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<A
+,C-<)2-Customer-credit-in5uiry))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<B
+,C-<)>-Customer-credit-payment))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<B
+,C-<)?-,urchase-order-management)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<;
+,C-<)<-'hip-goods)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=0
+,C-<)=-(nventory-management))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=0
+,C-<)A-'ales-product-notification)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=1
+,C-<)B-,resent-invoice))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=2
'usiness collaboration and economic events............................................................................+2
+C-=)1-Create-customer-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=2
+C-=)2-Chec0-customer-credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=?
+C-=)>-,rocess-credit- payment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=<
+C-=)?-Create-vendor-purchase-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))==
+C-=)<-'hipment-instruction))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=B
+C-=)=-Confirm-shipment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=;
+C-=)A-Dendor-inventory-reporting))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A1
+C-=)B-*e5uest-inventory-report))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A2
+C-=);-'ales-product-offering))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A?
+C-=)10-(nvoice-presentment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A<
'usiness transactions and aut#ori2ed roles..............................................................................--
+T-B)1-$irm-customer-sales-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))AA
+T-B)2-Chec0 customer credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))AB
+T-B)>-Charge-customer-credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A;
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age < of ;;
+T-B)?-Create-vendor-purchase-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B0
+T-B)<-Dendor-inventory-report)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B2
+T-B)=-*e5uest-inventory-report))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B>
+T-B)A-'hipment-notification)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B<
+T-B)B-Confirm-shipment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B=
+T-B);-,roduct-offering))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))BB
+T-B)10-,resent-invoice))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));0
'usiness in(ormation descri!tion..............................................................................................91
,urchase order)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));1
Content mapping))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));?
.Disc*aimer..................................................................................................................................9-
%./ontact Information.................................................................................................................97
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age = of ;;
1 &tatus of this Docu#ent
This document specifies an e.3-4 Technical *eport for the e+usiness community)
7istri.ution of this document is unlimited)
The document formatting is .ased on the (nternet 'ocietyEs 'tandard *$C format)
This versionF
httpF""///)e.1ml)org"specs".p8')pdf
4atest versionF
httpF""///)e.1ml)org"specs".p8')pdf
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A of ;;
$ ebXML Participants
+usiness ,rocess ,ro@ect Team Co-4eads
,aul 4evine Telcordia
-arcia -c4ure -c4ure--oynihan, (nc)
8e /ould li0e to recogniGe the follo/ing for their significant participation to the development of
this document)
#ditors
Charles $ineman %rGoon)
+rian 2ayes Commerce &ne)
Jennifer 4overidge !ordstrom)com)
8illiam #) -cCarthy -ichigan 'tate niversity
7avid 8elsh !ordstrom)com)
Contri.utors
Jim Clar0 (nternational Center of &.@ect Technology)
*andy Clar0 +a0er 2ughes, (nc)
+o. 2augen 4ogistical 'oft/are)
4arissa 4ey.ovich Ditria
!ita 'harma !etfish Technologies)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B of ;;
' (ntroduction
3.1 Summary
The primary goal of the e.3-4 effort is to facilitate the integration of e-.usinesses throughout
the /orld /ith each other) To/ards this end much of the /or0 in e.3-4 has focused on the
notion of a pu.lic processF the .usiness process(es) .y /hich e1ternal entities interact /ith an e-
.usiness) The specification and integration to such pu.lic processes has long .een recogniGed as
a significant cost to such .usinesses) (n order to reduce this cost e.3-4 is recommending the
use of +usiness 4i.raries) The principle goals of these li.raries are toF
a)) ,romote reuse of common .usiness processes and o.@ects
.)) ,rovide a place /here companies and standards .odies could place the specifications of their
pu.lic processes /here appropriate trading partners could access them)
(n order to realiGe these goals, a lin$ua (ranca needed to .e leveraged so that all users of this
repository could understand /hat each other are specifying) The e.3-4 community has decided
to use as its lin$ua (ranca the semantic su.set of the -- -etamodel, specified .y the
!"C#$%CT -odeling -ethodology in the !0;0 specification)
The -- His targeted primarily at personnel 0no/ledgea.le in modeling methodology /ho
facilitate .usiness process analysis sessions and provide modeling support) (t also serves as a
chec0list for standardiGed models /hen a previously specified .usiness process is contri.uted to
!"C#$%CT for inclusion and incorporation as a standard .usiness process model)I J--K
This document contains several /or0sheets that guide analysts to/ards -- compliant
specifications of their .usiness processes) 8e have tried to provide tools for users regardless of
/hether /eEre /or0ing on .ehalf of a standards .ody or an individual company) $urthermore,
/e provide a variety of scenarios guiding ho/ one might go a.out filling out these /or0sheets
(e)g) top-do/n vs) .ottom up)) The -- can .e used as a reference for understanding the
details of the underlying -etamodel and -- methodology)
7ifferent degrees of rigor are re5uired /ithin these /or0sheets) %s /e approach the lo/er level,
certain elements and organiGation of the specification are re5uired to meet the re5uirements of
the e.3-4 technical frame/or0) %t higher levels there is a good deal of latitude a.out the /ay
concepts are grouped) (n many cases, things such as assumptions and constraints /ill .e
specified in natural language rather then in a formal one)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ; of ;;
3.2 Audience
8e do not e1pect the users of these /or0sheets to .e e1perts in .usiness modeling, ho/ever it is
e1pected that they are su.@ect matter e1perts in their respective areas of practice) They should
have detailed 0no/ledge of the inter-enterprise .usiness processes they use to communicate /ith
their trading partners)
This document could also .e used .y industry e1perts to help e1press their sectors .usiness
processes in a form that is amena.le to the goals of the e.3-4 registry and repository)
&f course, soft/are vendors that are supplying tools (modeling and other/ise) in support of the
e.3-4 frame/or0 /ill find useful information /ithin)
3.3 Related documents
Je.C!T3TK eb304 %once!t 1 %onte5t and Re16sability o( %ore %om!onents) Dersion 1)0?) 11
-ay, 2001) e.3-4 Core Components ,ro@ect Team)
Je.*(-K eb304 Re$istry 7n(ormation 0odel) Dersion 1)0 11 -ay 2001) e.3-4 *egistry
,ro@ect Team)
Je.*'K eb304 Re$istry Services) Dersion 1)0 11 -ay 2001) e.3-4 *egistry ,ro@ect Team)
Je.T%K eb304 "ec#nical Arc#itecture S!eci(ication) Dersion 1)0)? 1= $e.ruary 2001) e.3-4
Technical %rchitecture ,ro@ect Team)
J.p&D#*K 'usiness 8rocess and 'usiness 7n(ormation Analysis 9vervie)) Dersion 1)0) 7ate 11
-ay 2001) e.3-4 +usiness ,rocess ,ro@ect Team
J.p,*&CK eb304 %atalo$ o( %ommon 'usiness 8rocesses) Dersion 1)0) 7ate -ay 11, 2001)
e.3-4 +usiness ,rocess ,ro@ect Team
J,DCK -ichael #) ,orter, %om!etitive Advanta$e/ %reatin$ and Sustainin$ Su!erior
8er(ormance, 1;;B, 2arvard +usiness 'chool ,ress)
J*#%K 9uido 9eerts and 8illiam)#) -cCarthy 6%n %ccounting &.@ect (nfrastructure $or
Lno/ledge-+ased #nterprise -odels,6 (### (ntelligent 'ystems M Their %pplications (July-
%ugust 1;;;), pp) B;-;?
J'C&*K Su!!ly %#ain 9!erations Re(erence model, The 'upply Chain Council
(httpF""///)supply-chain)org")
J--K 6:/%;<A%" 0odelin$ 0et#odolo$y) C#$%CT"T-89"!0;0*;)1) !"C#$%CT
Technical -odeling 8or0ing 9roup)
3.4 Document conventions
The 0ey/ords -'T, -'T !&T, *#N(*#7, '2%44, '2%44 !&T, '2&47, '2&47
!&T, *#C&--#!7#7, -%:, and &,T(&!%4, /hen they appear in this document, are to .e
interpreted as descri.ed in *$C 211;)
2eretofore, /hen the term 0etamodel is used, it refers to the -- e-+usiness ,rocess
-etamodel as defined in J--K)
) Design *b+ectives
4.1 Goals/objectives/requirements/problem description
e.3-4 .usiness processes are defined .y the information specified in the -- e-+usiness
,rocess -etamodel (hereafter referred to as the H-etamodelI)) The -etamodel specifies all the
information that needs to .e captured during the analysis of an electronic commerce .ased
.usiness process /ithin the e.3-4 frame/or0) e.3-4 recommends the use of the
!"C#$%CT -odeling -ethodology (--) in con@unction /ith the -etamodel) The --
provides the prescriptive process (methodology) to use /hen analyGing and defining a .usiness
process)
The e.3-4 +usiness ,rocess 8or0sheets are a set of .usiness process design aids, to .e used
/ith the -- as a reference) (t is intended that the /or0sheets .e e1tensi.le to meet specific
.usiness needs) %n e.3-4 .usiness process, that is defined .ased on the -- -etamodel,
/ill sufficiently reflect all the necessary components of a .usiness process and ena.le its
registration and implementation as part of the e.3-4 compliant electronic trading relationship)
The 8or0sheet .ased approach that provides an easier /ay of applying the -- and the --
-etamodel)
The intent of the /or0sheets (or a .usiness process editor
?
) is to capture all the .its of
information that are re5uired to completely descri.e a .usiness process so that it can .e
registered, classified, discovered, reused and completely drive the soft/are)
To develop company .usiness processes for an e.3-4 compliant electronic trading relationship,
use the -- as a reference guideline plus the e.3-4 +usiness ,rocess 8or0sheet to create the
necessary .usiness process models) These are the recommended steps for using the e.3-4
+usiness ,rocess 8or0sheets
1) % .usiness need or opportunity is identified and defined .efore using these procedures)
2) % $ocus ,ro@ect Team, usually representing a multifunctional set of e1perts from (T,
.usiness process o/nership and .usiness process e1perts needed to /or0 out the .usiness
process using the e.3-4 +usiness ,rocess 8or0sheet)
>) sing the e.3-4 +usiness ,rocess 8or0sheets, the $ocus ,ro@ect Team /ill .e a.le to
develop an e.3-4 +usiness ,rocess 'pecification that can .e revie/ed and verified .y the
.usiness) (n addition, all necessary information to populate the e.3-4 -etamodel /ill .e
made availa.le to ena.le an e.3-4 trading relationship)
4
A group of ebXML contributors are working on a prototype of an editor that uses wizards to guide the user through the construction
of a UMM compliant Business Process.
7i!ure 819 &or'sheets )rchitectura* /onte6t
4.2 !e analo"y
The follo/ing analogy is useful in understanding the role of the 8or0sheets and other
documentation and tools to the e.3-4 +usiness ,rocess Colla.oration -etamodel and the
!"C#$%CT -odeling -ethodology)
Item :nited States Interna* 3e$enue Ser$ice ;I3S< 1a6
S+stem
eb304 'usiness 8rocess %ollaboration 0etamodel
6:/%;<A%" 0odelin$ 0et#odolo$y)
#ntire ta1 code
8or0sheets and Templates (*' $orms
-ethodology 9uidelines (*' (nstruction +oo0lets
+usiness ,rocess #ditor Tool 'uite
*epository of +usiness ,rocess 'pecifications, Core
Components, etc)
'omething li0e Tur.oTa1 and other soft/are pac0ages for
preparing personal or .usiness ta1 forms /here these
pac0ages /ould have on-line access"search of all your ta1
and ta1 related records and the Ta1 code)
(n order to actually specify a .usiness process all /e really need is the 8or0sheets and
Templates
<
) 2o/ever, in order to ensure that /e fill in the forms properly /e /ill need to have a
set of instructions that augment the templates and provide some of the rationale .ehind the
templates)
A template is a document or file ha!ing a preset format that is used as a starting point for de!eloping human"readable !ersions of
the business process specifications so that the format does not ha!e to be recreated each time it is used.
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1> of ;;
Bro,ser
Public and Private -egistries. Public and Private -egistries.
/ Business Processes / Business Processes
/ Docu#ent and %o#ponent / Docu#ent 0 %o#ponent
Do#ain Libraries Do#ain Libraries
/ %ore %o#ponent Libraries / %ore %o#ponent Libraries
/ %ollaboration Protocol Profiles / %ollaboration Protocol Profiles
Worksheets
4.3 #aveats and assumptions
This document is non1normativeO the documents identified a.ove should .e considered the
authority on the definitions and specifications of the terminology used herein) This document is
intended to .e an application of those principals and technologies)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1? of ;;
1 Worksheet Based Analysis *vervie,
%s stated a.ove, the purpose of this document is to provide /or0sheets that guide the user
through the construction of a -- compliant specification of their .usiness processes) The
follo/ing diagram sho/s mapping from the /or0sheets to the high level components of the
--) !ote, the document definition /or0sheet is currently not included in the set of
/or0sheets)
&or'sheets :MM Metamode* 5ie,
7i!ure %829 "$er$ie, of mappin! from &or'sheets to Metamode*
The e1pectation is that after the /or0sheets have .een completed, there /ill .e sufficient
information to mechanically produce a -etamodel .ased specification of the modeled .usiness
process(es)) The /or0sheets given a.ove areF
(usiness 3eference Mode* P se this to define the Hframe of referenceI of the rest of the
/or0sheets) This provides definitions of terms and, perhaps, canonical .usiness processes (e)g)
J'C&*K
=
)
(usiness Process Identification and Disco$er+ P se this to do an inventory of the .usiness
processes) This is really @ust a set of high-level use cases merely to identify the e1istence of
#
$efines plan% source% make and deli!er business areas in their &upply 'hain (perations )eference *&'()+ model
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1< of ;;
Business Process
,dentification and $isco!ery
Business (perations Map
Model
Business )eference Model
Business )e-uirements .iew
Model
Business &er!ice .iew
Model
Business /ransaction .iew
Model
Business 'ollaboation
'onstruction
Business Process 0llaboration
Business /ransaction
$efinition
Business ,nformation
$efinition
processes and the sta0eholders /ithout going into detail)
(usiness Process .*aboration P These /or0sheets are used to flesh out the .usiness processes)
This identifies the actual actors as /ell as pre and post conditions for the .usiness process)
(usiness /o**aboration Definition P (n these /or0sheets /e define the economic events that
ta0e place to fulfill the .usiness process) This is /here one defines the system .oundaries and the
protocols that govern the flo/ of information)
(usiness 1ransaction Definition P These /or0sheets are more technically oriented than the
others (/hich have a decidedly more HmodelingI orientation)) %t this stage one defines the
actual activities and authoriGed parties /ithin the organiGation that initiate these transactions)
(usiness Information Definition P (n these /or0sheets one defines the contents of the
information field /idths, data types, descriptions, re5uirement tracea.ility and, perhaps, the
additional conte5t (Je.C!T3TK) necessary to construct the document from the Core
Components su.system)
$.1 %asic "uidelines &or &illin" out 'or(s!eets
111 2ocus on public business processes
8hile these /or0sheets could .e used to model any 0ind of .usiness process, the focus of the
e.3-4 effort is to ma0e trading partner integration easier, cheaper, and ro.ust) Therefore the
e1pectation is that the primary focus /ill .e on !ublic faces of your .usiness processes)
11$ "he -3A ontology
The -- and e.3-4 groups are recommending the use of the *esource-#conomic #vent-
%gent &ntology for the formaliGation of .usiness colla.orations),lease refer to J+,%&K and
J*#%K for further information on this topic
A
and associated /or0sheets)
11' 4se the ,orksheets in the order that #akes the #ost sense for you
$or the purposes of this document /e proceed from the top-level step (+usiness *eference
-odel) do/n to the lo/est-level step (+usiness Transaction)) (t is important to note, ho/ever,
that these /or0sheets can .e filled out in /hatever order ma0es the most sense from the userEs
perspective) $or e1ample, a person /ho is trying to retrofit an e1isting document .ased standard
(e)g) #7($%CT) might /ant to start .y filling in the +usiness Transaction 7efinition /or0sheets
(perhaps only specifying trivial definitions for the higher level /or0sheets)) % person loo0ing to
formaliGe the definitions for an entire industry may very /ell start from the +usiness *eference
-odel /or0sheet)
1
2orksheets will be made a!ailable in a future !ersion of this document.
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1= of ;;
11) "he ,orksheets can be used for pro+ects of various scopes
%lthough the -etamodel has definite re5uirements on )#at o.@ects need to .e present to
comprise a complete specification, it says little a.out the scope of /hat those specifications
represent) $or e1ample, if you are only trying to model a specific interaction /ith one of your
trading partners, you do not need to include a complete 'usiness Re(erence 0odel for your entire
industry, @ust include the parts that are directly relevant for the interaction you are modeling)
'imilarly, if you are @ust doing a small set of interactions for your company, you might choose to
have the 'usiness Area or 8rocess Area @ust .e your o/n company)
111 "hink ho, ,ill people use ,hat you construct
%s you fill in these /or0sheets please 0eep in mind ho/ the generated -- specification /ill
.e used .y a user of the repository) The t/o principal uses envisioned areF
To determine if a given colla.oration is appropriate for reuse (or at least is a close enough
match for su.se5uent gap analysis)
To .e used as an on1line im!lementation $uide) % potential trading partner (or a >
rd
party on
their .ehalf) could e1amine the pu.lic processes"colla.orations you provide and construct an
integration plan)
This means trying to use industry /ide terms (or at least +usiness *eference -odel terminology)
to increase the comprehensi.ility and specificity) )
115 -e/use is one of the pri#ary goals of ebXML
%s stated a.ove, the hope is that users /ill develop models that are reusa.le .y others) To/ards
that end, it is intended that the 8or0sheets .e used in con@unction /ith a .ro/ser that lets the
user search .usiness process li.raries for items that have already .een defined) The items (e)g)
.usiness processes, .usiness colla.orations, document schemas, etc)) can .e referenced (re-used
as is) or copied to the /or0sheets and changed as needed) &ver time, .usiness process catalogs
/ill .ecome populated /ith a sufficiently large num.er of .usiness processes) 8hen this
happens, the analysis processes /ill often .ecome a matter of validating pre-defined .usiness
processes against re5uirements)
116 7ote on optional fields in the ,orksheets
'ome of the /or0sheets contain entries that are la.eled as optional for e.3-4) These are
attri.utes that appear in the -- .ut are not re5uired as part of the e.3-4 'pecification
'chema
)
These are typically .usiness o.@ective"@ustification topics) 8hile these are o.viously
very important aspects of any modeling endeavor, e.3-4 is oriented to/ards e5!osin$ an
organiGationEs pu.lic processes to their trading partners) %dvertising that organiGations
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1A of ;;
@ustifications for such interfaces could potentially pu.liciGe strategic information that said
organiGation /ould prefer to 0eep private)
B
118 7u#ber your ,orksheets
#ach of the /or0sheets has an entry for a <orm 7D) This (7 can .e used to reference one form
from another) (n addition, if you use an outline num.ering scheme, it /ill .e easy for the reader
to determine parent-child relationships .et/een elements of the model (of course, if you do a
.ottom up approach this /ill .e significantly harder to do up frontQ))
The recommended format isF
R<orm "y!eS-R:umberS-RDescri!tionS
8here R<orm "y!eS is
(3M for 'usiness Re(erence 0odel
() for 'usiness Area
P) for 'usiness 8rocess Area
(PS for 'usiness 8rocess Summary
(P:/ for 'usiness 8rocess 6se %ase
.. for #conomic #1change
.) for #conomic %greement
(/ for 'usiness %ollaboration
(/P1 for 'usiness %ollaboration 8rotocol "able
(1 for 'usiness "ransaction
(111 for 'usiness "ransaction "ransition "able
(I/ for 'usiness 7n(ormation %onte5t
/D for %ontent Descri!tion
/M for %ontent 0a!!in$
R:umberS is, perhaps, an outline entry num.er
3
/here has been discussion on pri!ate !s. public repositories where some or all aspects of the model are stored in a restricted
access repository.
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1B of ;;
RDescri!tionS is some descriptive name)
,lease see the e1ample in the %ppendi1 for an illustration of this in practice)
$.2 )or(s!eets to metamodel mappin"
The follo/ing diagram s0etches out a more detailed mapping from the 8or0sheets -odel to the
-etamodel defined .y the --) The leftmost column is the selection of the main elements that
the 8or0sheets need to specify or edit) The rightmost column sho/s significant -etamodel
elements) The middle column is the other elements that are part of the 8or0sheets) They are the
same as the -etamodel elements of the same name)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 1; of ;;
Business Process
(Use Case)
B(M
Model
Business Area
Model
Process Area
Model
B).
Model
Business 'ollaboration
Protocol
(Activity Graph)
B/.
Model
Business/ransaction
Acti!ity
(Action State)
Business/ransaction
(Activity Graph)
Business Process
,dentification
Business
)eference Model
Business Area
Process Area
Business
'ollaboration
Worksheet
Model
Meta#odel
Partner /ype
Authori4ed
)ole
Business Acti!ity
$ocument 0n!elope
Use 'ase
(Use Case)
(Collaboration)
Business $ocument
'horeography "
states% transitions% etc.
Business Actor
Business $ocument
Business Process
0laboration
Business Process
(Use Case)
Use 'ase
(Use Case)
$ifferent path for
single transaction
collaborations.
5 Business Process (dentification and Discovery
*.1 Goals
The first set of /or0sheets helps the user .egin formaliGe the domain they are trying to model
processes in) The first stage in the methodology is to identify the Htop levelI entities and
organiGing concepts in the domain)
B P , d e n t i f i c a t i o n a n d
$ i s c o ! e r y
B ( M
B u s i n e s s P r o c e s s
U s e ' a s e
B ( M
M o d e l
B u s i n e s s A r e a
M o d e l
P r o c e s s A r e a
M o d e l
B u s i n e s s P r o c e s s
, d e n t i f i c a t i o n
B u s i n e s s
) e f e r e n c e M o d e l
B u s i n e s s A r e a
P r o c e s s A r e a
7i!ure -839 (usiness Process Identification and Disco$er+ &or'sheet to Metamode* Mappin!
%t this stage /e define terminology and identify the participants as /ell as /hich .usiness
processes those players interact /ith) To 5uote the --, at this stage in the model the goal is
toF
To understand the structure and dynamics of the .usiness domain,
To ensure that all users, standards developers and soft/are providers have a common
understanding of the .usiness domain,
To understand the daily .usiness in the .usiness domain independent of any technical
solution,
To create categories to help partition the .usiness domain that ena.les an iteration plan to
complete the model,
To structure the model in the form of a +usiness &perations -ap (+&-),
To capture the @ustification for the pro@ect,
To identify the sta0eholders concerned /ith the modeled domain, some /ho /ill .e
independent of the processes /ithin the domain)
The modeling artifacts that correspond to the -- areF
+usiness %rea J,ac0ageK
,rocess %rea J,ac0ageK
,rocess(es) Jse CasesK
*.2 Guidelines
5$1 9o, does one decide ho, big to #ake the various groupings at this level:
*eferring .ac0 to the primary guidelines, thin0 a.out /hat you are trying to communicate) (f you
are more focused on identifying the pu.lic processes, then thin0 a.out grouping them .y partner
type or, perhaps .y the area of your .usiness these partners interact /ith) (f you are trying to
formaliGe an entire .usiness sector, determine the arc#ety!es (patterns) that are prevalent in that
sector and group them .y .usiness function area) These are @ust rules of thum. and this is still
largely an HartI) Leep in mind your potential audience and thin0 /hat /ould ma0e the most
useful organiGation for them)
The activity diagrams in this /or0flo/ /ill li0ely discover more refined .usiness process use
cases) The +usiness &perations -ap (+&-) -etamodel allo/s a .usiness process to .e
represented .y more refined .usiness processes) !&T#F %t the point /here the .usiness process
can not .e .ro0en do/n into more child .usiness processes, the parent .usiness process can .e
called a .usiness colla.oration use case as specified in the *e5uirements /or0flo/)
5$$ What is the boundary of the business area:
%ccording to the J--K the follo/ing guidelines are to .e used in defining a .usiness areaF
The .usiness area can .e defined .y the sta0eholders that have direct or immediate indirect
influence on the .usiness domain) % sta0eholder is defined as someone or something that is
materially affected .y the outcome of the system .ut may or may not .e an actor) %ctors are
sta0eholders that are involved in the .usiness process and are thus part of the .usiness model)
The .usiness area can .e defined .y the information passing into or out of the .usiness
domain) 8here possi.le, the domain .oundaries should .e chosen so that a .usiness
transaction is logically or organiGationally initiated and concluded /ithin them)
The .usiness area can .e defined .y 0ey .usiness entity classes) (i)e), things that are
accessed, inspected, manipulated, processed, e1changed, and so on, in the .usiness process)
*.3 )or(s!eets
The e1amples given in the follo/ing /or0sheets more or less come from the hypothetical
.usiness process descri.ed in section B)? of J.p,*&CK)
5'1 Business reference #odel
&ften times it is useful to define a Hframe of referenceI for the .usiness processes .eing
identified) This frame of reference might define .asic terms accepted .y the given industry
segment) $or e1ample the 'C&* model defines a frame of reference for supply chain) D(C'
defines a frame of reference for trading partners in the retail industry) (t also might .e a more
horiGontal vie/ such as the ,orter Dalue Chain J,DCK (see ta.le %ppendi1 +))
7orm9 Describe (usiness 3eference Mode*
7orm ID J,rovide an (7 for this form so other forms can reference it (T<)1)B)K
(usiness 3eference Mode*
4ame
J,rovide a name for the reference model) :ou can use an e1isting reference
model such as the 'upply Chain Council or the ,orterEs Dalue Chain or create
your o/n name)K 7&TC&- 7*&, '2(, *#T%(4 -&7#4
Industr+ Se!ment J,rovide the name of the industry segment that this .usiness applies to) 'earch
the .usiness process li.rary for a list of possi.le industry segments) (f the
industry segment does not e1ist, then provide an appropriate name"la.el for the
industry segment)K *etail)
Domain Scope J,rovide a high level statement that encapsulates the scope of all the .usiness
areas)K &nline catalog, distri.ution center, delivery, .illing)
(usiness )reas J4ist the .usiness areas /ithin the scope) % .usiness area is a collection of
process areas) % process area is a collection of .usiness processes) :ou may
/ish to refer to the e.3-4 Catalog of +usiness ,rocesses that provides a list of
normative categories that may .e used as .usiness areas)K &rder -anagement,
%*)
"ptiona* for ebXML
(usiness =ustification J,rovide the .usiness @ustification for the collection of .usiness processesK
7efine more efficient on-line retailer"vendor interaction)
5'$ Business area
%s mentioned in the guidelines section, there are no hard and fast rules for ho/ to divide up the
model into different .usiness areas) &ne suggestion is to group .usiness processes according to
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2> of ;;
the primary .usiness function) :ou might consider using the ,orter Dalue Chain J,DCK
classification scheme (see %ppendi1 +))
7orm9 Describe (usiness )rea
(usiness )rea 4ame J,rovide a name for the .usiness area) This should .e listed in the +usiness
%reas section of at least one +usiness *eference -odel)K
7irect to Customer *etail
Description J% .rief summary of this functional area) K
Scope J,rovide a high level statement that encapsulates the scope of all the .usiness
areas) The scope of the .usiness area must .e /ithin the scope of the
encompassing .usiness reference model) Typically the scope of the .usiness
area /ill .e more constrained or limited than the scope of the .usiness reference
model)K &nline catalog, order placement, distri.ution center, delivery, .illing)
(oundar+ of the (usiness
)rea
J7escri.e the .oundary of the .usiness area) This defines the entities that
interact in this .usiness areaO actors, organiGations, possi.ly systemsK Customer,
*etailer, 7'Dendor, Carrier, Credit %uthority)
3eferences J%ny e1ternal supporting documentation)K D(C', 'C&*
/onstraints J(dentify any constraints on the process areas (and, thus, .usiness processes)
/ithin this .usiness area)K 1) Completely automated system) 2) 8e. .ro/ser
limitations) >) 7omestic orders only
Sta'eho*ders J(dentify the practitioners that care a.out the definition of this .usiness area) %t
this level, this is li0ely to .e some participants in an industry group (perhaps a
standards .ody or an enterprise)) These are the people /ho /ill define the
+*D)K Customer, *etailer, 7'Dendor, Carrier, Credit %uthority)
Process )reas J4ist the process areas /ithin the scope) % process area is a collection of
.usiness processes) :ou may /ish to refer to the e.3-4 Catalog of +usiness
,rocesses that provides a list of normative process groups that may .e used as
process areas)K Customer Commitment, &rder fulfillment, +illing, (nventory
-anagement)
"ptiona* for ebXML
"b#ecti$e J7escri.e the o.@ective of this .usiness area)K To deliver a product to a customer
in a timely efficient manner)
(usiness "pportunit+ J7escri.e the .usiness opportunity addressed .y this .usiness area)K
5'' Process area
Typically a .usiness reference model /ould define a canonical set of process areas (see the
,orter or 'C&* reference models for e1amples)) % process area consists of a se5uence of
processes that are com.ined to form the Hvalue chainI of the given .usiness area)
7orm9 Describe Process )rea
Process )rea 4ame J,rovide a name for the process area) This should .e listed in the ,rocess %reas
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2? of ;;
section of at least one +usiness %rea)K &rder $ulfillment
"b#ecti$e J7escri.e the o.@ective of this process area)K To deliver the goods ordered to the
customer)
Scope J,rovide a high level statement that encapsulates the scope of all the .usiness
areas) The scope of the .usiness area must .e /ithin the scope of the
encompassing .usiness reference model) Typically the scope of the process area
/ill .e more constrained or limited than the scope of the corresponding .usiness
area)K To fulfill customerEs order using the third party supplier for a drop ship
delivery)
3eferences J#1ternal supporting documentation)K
(oundar+ of the Process )rea J7escri.e the .oundary of the process area) The communicating services)K
*etailer and third party vendor)
J(ssueF 2o/ is this different than 'copeCK
/onstraints J(dentify any constraints on the .usiness processes /ithin this process area)K
(nventory availa.ility) &n time delivery) 'ystem constrain)
Sta'eho*ders J(dentify the practitioners involved in this process area) =uestion/ is t#is a
subset o( t#ose listed in t#e 'usiness Area>)K *etailer, Third party vendor
(usiness Processes J4ist the .usiness processes /ithin the scope of this process area) :ou may /ish
to refer to the e.3-4 Catalog of +usiness ,rocesses that provides a normative
list of .usiness processes)K -anage ,urchase &rder)
"ptiona* for ebXML
(usiness "pportunit+ J7escri.e the .usiness opportunity addressed .y this process area)K
5') (dentify business processes
$or each .usiness process in the process area fill in the follo/ing /or0sheet) % suggested rule of
thum. for the appropriate granularity for a .usiness process is that it is the smallest e1change of
signals .et/een sta0eholders that has an identifia.le economic value (cref) J*#%K)) :ote t#at
t#is is not al)ays a!!ro!riate since ?ne$otiation@ could be a valid business !rocess but it
doesnAt really result in an economic conseuence.
+e sure to validate the information in the process area against the encompassing .usiness area)
$or e1ample, validate that the scope of the process area is /ithin the scope of its .usiness area)
7orm9 Identif+ (usiness Process
(usiness Process 4ame J,rovide a name for the .usiness process) :ou may /ish to refer to the e.3-4
Catalog of +usiness ,rocesses J.p,*&CK that provides a suggested set of
commonly used .usiness processes)K -anage ,urchase &rder
Process )rea J% process area is a group of .usiness processes) Complete a ,rocess %rea
form)K &rder $ulfillment
(usiness )rea J% .usiness area group together related process areas) Create a +usiness %rea
form)K 7irect to Customer *etail
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2< of ;;
6 Business Process 3laboration
+.1 Goals
%t this stage /e .egin to move from re5uirements analysis to design analysis) Consider the
follo/ing diagramF
Business
Process
0laboration
B).
B).
Model
Business Process
*Use 'ase+
Business Process
0laboration
Business Actor Business Actor
7i!ure 789 Mappin! from business processes to the (35
% .usiness process is a use case that is used to gather re5uirements a.out .usiness processes)
(nputs to the .usiness process must .e specified in the preconditions and outputs from the
.usiness process must .e specified in the post-conditions)
+.2 )or(s!eet
&ne of these is filled out for each .usiness process) +usiness process can .e nested) :ou should
use /hatever organiGation ma0es sense for your purposes (though you might /ant to thin0 in
terms of reuse /hen considering possi.le decompositions))
7orm9 (usiness Process :se /ase
(usiness Process 4ame J,rovide a name for the .usiness process) This should .e a name identified on
the form H(dentify +usiness ,rocessI and on a H7escri.e ,rocess %reaI form) (f
you are starting /ith this form, you may /ish to refer to the e.3-4 Catalog of
+usiness ,rocesses that provides a normative list of .usiness processes)K -anage
,urchase &rder)
Identifier JThis is a uni5ue identifier that follo/s the +usiness ,rocess (dentifier !aming
'cheme) This can .e provided /hen the .usiness process description is
su.mitted to a .usiness process li.rary) 'ee %ppendi1 % for a more detailed
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2= of ;;
discussion)K .pidFean)12>?<=AB;012BF-anage,urchase&rderU1)0
)ctors J4ist the actors involved in the use case)K *etailer, Dendor
Performance >oa*s J% specification of the metrics relevant to the use case and a definition of their
goals) !on-functional re5uirements may .e a source of performance goals) $or
each performance goal, provide a name of the performance goal and a .rief
description of the performance goal)K
Preconditions J,reconditions are constraints that must .e satisfied starting the use case)K 1)
Dalid 'ales &rder 2) Dalid Dendor *elation
(e!ins &hen J7escri.e the initial event from the actor that starts a use case)K 'ales &rder
Dalidation (e1pressed as events)
Definition J% set of simple sentences that state the actions performed as part of the use case)
(nclude references to use cases at e1tension points)K % valid ,urchase &rder
placed .y retailer /ith the vendor and a ,& %c0 is received from the vendor)
.nds &hen J7escri.e the condition or event that causes normal completion of the use case)K
,& %c0no/ledged returned to retailer)
.6ceptions J4ist all e1ception conditions that /ill cause the use case to terminate .efore its
normal completion)K 1) ,& *e@ected ($ailure state of a process) 2) 4ate ,&
ac0no/ledged
Postconditions J,ost-conditions are states that must .e satisfied ending the use case)K 1) Dalid
,& 2) %llocated ,roduct
1raceabi*it+ JThese are the re5uirements covered (as sho/n in %nne1 ?, se Case
'pecification Template, in the --))K 6,*7-$&&-=)<)?6 (meaning ,roduct
*e5uirements 7ocument for $&& pro@ect"solution, re5uirement =)<)?))
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2A of ;;
8 3cono#ic 3le#ents
,.1 Goals
These /or0sheets develop the economic elements of .usiness processes as ela.orated in the
*#% ontology J*#%K) The intent is to conform to the specific modeling elements of the
+usiness *e5uirements Die/ (+*D) of the --) !ot all .usiness processes include economic
e1changes as defined .y *#%, so the use of these /or0sheets /ill occur in only a portion of
.usiness processes and .usiness colla.orations) The semantics of legal o/nership and 9%%,
(generally accepted accounting principles) financial reporting depend upon correct modeling and
understanding of the +*D elements in this section)
,.2 Guidelines
There are t/o /or0sheets in this section) These /or0sheets model the follo/ing economic
entitiesF #conomic #vents, #conomic *esources, ,artner Types, +usiness #vents, %greements,
#conomic Contracts, and Commitments) +uilding an #conomic #1change model /ith these
elements normally involves specification of t/o matching components of a mar0etplace
e1change) $or e1ampleF
% shipment (economic event) of goods (economic resource)
.et/een a supplier and a customer (partner types) occurs) This is
normally follo/ed .y a payment (economic event) involving cash
(economic resource) .et/een the same t/o parties (partner types))
This shipment for cash might have .een preceded .y 5uotes and
pricing e1changes (.usiness events)) The shipment might also .e
governed .y a purchase order (agreement or economic contract))
This purchase order (economic contract) might specify the
e1pected types of goods (economic resource types) and the
e1pected dates of the shipments and payments (commitments))
The first /or0sheet specifies the items for an economic e1change, /hile the second specifies the
economic primitives for the agreement that might govern that e1change) !ot all economic
e1changes are governed .y agreements or contracts, so the second /or0sheet /ill .e used less
fre5uently) 8here necessary, space has .een provided for cross-references .et/een economic
e1changes and the agreements that govern them) (t is also possi.le for agreements to recursively
reference other agreements) +usiness Colla.orations as defined in the ne1t section of /or0sheets
might correspond to an entire economic e1change, an economic event, or a .usiness event)
Colla.orations may also correspond to agreements or economic contracts)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2B of ;;
,.3 )or(s!eets
7orm9 .conomic .6chan!e
.conomic .6chan!e 4ame J,rovide a name for the e1change (li0e Hcash purchaseI or Hcredit ac5uisition
of servicesI)K
Identifier JThis is a uni5ue identifier that follo/s the +usiness ,rocess (dentifier
!aming 'cheme)K
Initiator 3esource 7*o,
Initiator .conomic .$ent ;s< J,rovide the .usiness name for the economic event (shipment, service,
payment, etc))K
Initiator .conomic 3esource;s< J7escri.e the goods or services (inventory, transportation, cash, etc)) to .e
e1changed)K
Initiator Supp*+in! Partner
1+pe
J7escri.e the party /ho supplies the economic resource)K
Initiator 3ecei$in! Partner
1+pe
J7escri.e the party /ho receives the economic resource)K
Initiator .6ception .$ents J7escri.e the events that constitute the e1ceptions to the e1pected e1change
and e1plain their conse5uences (incomplete shipment or disallo/ed payment,
etc)))K
1erminator 3esource 7*o,
1erminator .conomic .$ent;s< J,rovide the .usiness name for the economic event (shipment, service,
payment, etc))K
1erminator .conomic
3esource;s<
J7escri.e the goods or services (inventory, transportation, cash, etc)) to .e
e1changed)K
1erminator Supp*+in! Partner
1+pe
J7escri.e the party /ho supplies the economic resource
1erminator 3ecei$in! Partner
1+pe
J7escri.e the party /ho receives the economic resource)K
1erminator .6ception .$ents J7escri.e the events that constitute the e1ceptions to the e1pected e1change
and e1plain their conse5uences (incomplete shipment or disallo/ed payment,
etc)))K
"$era** .conomic .6chan!e
.nab*in! (usiness .$ents J7escri.e the .usiness events that normally accompany this economic
e1change and that ena.le its operation ($or e1ampleF 5uery availa.ility,
supply catalog information, and chec0 credit might all precede a shipment of
goods for cash))K
4orma* 1erms of Sett*ement J7escri.e normal settlement arrangements (payment upon receipt, etc)))K
3eco!nition of /*aim J7escri.e /hether or not an incomplete (unre5uited) state of the e1change
needs to .e e1plicitly recogniGed /ith a claim (li0e an invoice))K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age 2; of ;;
4eed for /ontract or
)!reement
J(ndicate /hether or not this e1change is to .e governed .y an economic
agreement or contract) (f necessary, complete the ne1t /or0sheet)K
7orm9 .conomic )!reement
.conomic )!reement 4ame J,rovide a name or a specific identifier for the agreement that usually governs
the economic e1change from the lin0ed /or0sheet)K
Identifier JThis is a uni5ue identifier that follo/s the +usiness ,rocess (dentifier
!aming 'cheme)K
Lin'ed &or'sheet for
.conomic .6chan!e
J,rovide the Identifier for the governed economic e1change (as identified in
prior /or0sheet))K
>o$ernin! .conomic
)!reement ;?i!her "rder<
J7escri.e and provide Identifier for any longer term agreement that governs
the operation of this specific (shorter-term) agreement)K
>o$erned .conomic )!reement
;Lo,er "rder<
J7escri.e and provide Identifier for any shorter term agreement that are
governed .y the operation of this specific (longer-term) agreement)K
.conomic /ontract J7escri.e /hether or not this agreement meets the conditions for an
enforcea.le legal contract)K
Parties to the .conomic
)!reement
J(dentify the ,artner Types resonsi.le for the esta.lishment of the agreement)K
.stab*ishin! .$ent J(dentify the +usiness #vent /hich esta.lishes this agreement)K
.nab*in! (usiness .$ents J7escri.e the set of +usiness #vents that ena.led the esta.lishment of this
agreement (from the negotiation pattern for e1ample))K
Initiator /ommitment;s< 7escri.e the nature of the initiating commitment for the governed e1change
(for e1ampleF ship inventory according to a certain schedule))K
Initiator 3esource 1+pes J7escri.e the #conomic *esource Types for the initiating commitment and
pro@ected 5uantities if appropriate)K
Initiator Partner 1+pe J(dentify the ,artner Type responsi.le for the initiating commitment in the
governed e1change)K
1erminator /ommitment;s< J7escri.e the nature of the terminating commitment for the governed
e1change (for e1ampleF su.mit payment /ithin >0 days of receipt))K
1erminator 3esource 1+pes J7escri.e the #conomic *esource Types for the terminating commitment and
pro@ected 5uantities if appropriate)K
1erminator Partner 1+pe J(dentify the ,artner Type responsi.le for the terminating commitment in the
governed e1change)K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >0 of ;;
; Business %ollaboration
-.1 Goals
These /or0sheets develop the +usiness *e5uirements Die/ (+*D) of a process model)
Business
'ollaboration
B).
Partner /ype
Business 'ollaboration Use 'ase
Use Case
Collaboration
'horeography "
states% transitions% etc.
Business /ransaction Use 'ase
Use Case
Partner /ype
7i!ure 98%9 Mappin! from (usiness /o**aboration to (35
The follo/ing items are specifiedF
The .usiness colla.oration protocols that tie economic events together
The system .oundaries .et/een /hich the protocols flo/
The input and output triggers of these colla.orations
The roles and constraints associated /ith the colla.oration
The purpose of the ,artner Colla.oration 8or0sheets isF
HV to capture the detailed user re5uirements, specified .y the
sta0eholders, for the .usiness-to-.usiness pro@ect) V This
/or0flo/ develops the +usiness *e5uirements Die/ (+*D) of a
process model that specifies the use case scenarios, input and
output triggers, constraints and system .oundaries for .usiness
transactions (+Ts), .usiness colla.oration protocols (+C,s) and
their interrelationships)I (J--, >)1K)
The modeling artifacts to .e identified areF
+usiness Transactions Jse CaseK
+usiness Colla.oration Jse CaseK
+usiness Colla.oration se Case Jse Case *ealiGation, %ctivity 7iagramK
#conomic Conse5uences of +usiness Colla.orations
-.2 )or(s!eets
7etail the information in the ta.le .elo/ for each .usiness colla.oration) !ote that it may ma0e
sense to use -4 diagrams to convey some of this information)
7orm9 (usiness /o**aboration
Identifier JThis is a uni5ue identifier that follo/s the +usiness ,rocess (dentifier !aming
'cheme) This can .e provided /hen the .usiness process description is
su.mitted to a .usiness process li.rary) 'ee %ppendi1 % for a more detailed
discussion)K
Description J,rovide a descriptive overvie/ of the colla.oration)K
Partner 1+pes JThis is a list of entities that participate in the colla.oration) These participants
e1change the events that form the colla.oration)K
)uthori2ed 3o*es JThese are the roles that a partner must .e authoriGed to play to issue specific
transactions in the colla.oration (.y sending certain signals))K
Le!a* Steps@3eAuirements J(f any step in the colla.oration has any legal standing, it should .e captured
here)K
.conomic /onseAuences J(f any step in the colla.oration has and economic conse5uence, it should .e
captured here)K
Initia*@1ermina* .$ents J4ist the events that initiate this colla.oration and ho/ it terminates)K
Scope J'pecify the set of .usiness actions this colla.oration encapsulates)K
(oundar+ J'pecify the systems and users that communicate /ith each other over he course
of this colla.oration)K
/onstraints J'pell out any special constraints that are relevant to this colla.oration (e)g)
.usiness scenario, pre-conditions))K
7orm9 (usiness /o**aboration Protoco* 1ab*e
7orm Id J,rovide an (7 for this form so other forms can reference it (T<)1)B)K
Identifier J#nter the (dentifier from the associated +usiness Colla.oration form)
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
1o (usiness
)cti$it+
3espondin!@
3ecei$in! Partner
1+pe
1ransition /ondition
J'T%*T for the
first activity or the
name of
originating
.usiness activity)K
J,artner type name
or !&T-
%,,4(C%+4#)K
J!ame of
destination
.usiness activity)K
J,artner type name
or !&T-
%,,4(C%+4#)K
J% .oolean e1pression
defining or descri.ing the
condition for the transition
or !&!#)K
J!ame of an
activity)K
!&T-
%,,4(C%+4#
'CC#'' !&T-
%,,4(C%+4#
condition for the
transition)K
J!ame of an
activity)K
!&T-
%,,4(C%+4#
$%(4*# !&T-
%,,4(C%+4#
condition for the
transition)K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >> of ;;
1! Business "ransactions and Authori<ed -oles
1..1 Goals
The goal of this /or0sheet is to identify the individual transactions that implement the /or0flo/
of a +usiness Colla.oration) % transaction is made up of several activities and each activity has
an aut#ori2ed role that the signaler must have in order to initiate that activity)
The modeling artifacts generated as a result of this /or0sheet is the +usinessTransaction
%ctivity 7iagram) $ill out one /or0sheet for each transaction in the colla.orations
1..2 Guidelines
1!$1 4se transaction patterns
The -- has defined several transaction patterns that should .e used to define .usiness
transactions) +y the use of these patterns one can .e assured that the transaction is legally
.inding in accordance /ith current glo.al and regional legal /ritings (see -- for further
details))
These patterns have intrinsic semantics (e)g) property-values such as non-repudiation and
authoriGation) associated /ith them) (f you choose to .ase the transaction on one of these
patterns you do not have to repeat the property values here (although you may /ish to do so that
all information is specified in one place)) 2o/ever if you do not .ase the transaction on an
-- pattern, descri.ed the property values in the +usiness Transaction ,roperty Dalues form)
!ote that if you do not follo/ a prescri.ed pattern, the .usiness transaction may not comply /ith
generally accepta.le legally .inding transaction semantics) (f you /ish to HoverrideI the
semantic property-values, use the +usiness Transaction ,roperty Dalues form and 0eep in mind
that /hen you change the property values, the pattern may no longer .e applica.le) (n this case,
you should not specify a pattern name) 7o not provide values for !on-*epudiation &f *eceipt
and *ecurrence for *esponding +usiness %ctivity (this is specified .y the --))
1!$$ Detail transaction activities only if necessary
The transaction patterns defined in the -- should .e sufficient to cover most .usiness cases)
2o/ever, it may .e necessary or desira.le to descri.e the .usiness transaction activity in terms
of the allo/a.le transitions .et/een the activities) %n -- compliant activity diagram (-4)
can .e created or a +usiness Transaction Transition Ta.le can .e used to convey the same
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >? of ;;
information) *efer to the e1amples in %ppendi1 C, to see ho/ +usiness Transaction activity
diagrams are represented in +usiness Transaction Transition Ta.le forms)
1..3 )or(s!eets
7orm9 (usiness 1ransaction
Description J,rovide a descriptive overvie/ of this transaction)K
Pattern J(f you have chosen to follo/ one of the canonical transaction patterns in the
--
;
(or else/here) denote it here) (f not and you have special semantics (as
mentioned a.ove), descri.e them here)K
(usiness acti$ities and
associated authori2ed ro*es
J4ist each activity (along /ith its initiator) and the role re5uired to perform that
activityK
/onstraints J%ny constraints should .e listed here)K
Initiatin!@3eAuestin! Partner
1+pe
J,artner type from colla.oration)K Customer
Initiatin!@3eAuestin!
)cti$it+ 3o*e
JThese are the roles that a partner must .e authoriGed to play to issue specific
transitions in the transaction (.y sending certain signals))K +uying Customer
)cti$it+ Document
J7ocument initiating the transaction) -ight reference a standard document (e)g)
an 312 document)) K 'ales &rder
3espondin! Partner 1+pe J'ee a.ove)K &n-line *etailer
3espondin! )cti$it+ 3o*e J'ee a.ove)K Customer 'ervice
3espondin! )cti$it+
Document
J'ee a.ove)K Confirmation email
Complete the follo/ing property-values for re5uesting .usiness activities and responding
.usiness activities if they differ from the default values defined in the -- transaction patterns)
:ou may /ish to copy the values from the -- as a convenience to the readers)
7orm9 (usiness 1ransaction Propert+ 5a*ues
1
i
m
e

t
o

)
c
'
n
o
,
*
e
d
!
e

3
e
c
e
i
p
t
1
i
m
e

t
o

)
c
'
n
o
,
*
e
d
!
e

)
c
c
e
p
t
a
n
c
e
1
i
m
e

t
o

P
e
r
f
o
r
m
)
u
t
h
o
r
i
2
a
t
i
o
n

3
e
A
u
i
r
e
d
4
o
n
8
r
e
p
u
d
i
a
t
i
o
n

o
f

"
r
i
!
i
n

a
n
d

/
o
n
t
e
n
t
4
o
n
8
3
e
p
u
d
i
a
t
i
o
n

o
f

3
e
c
e
i
p
t
3
e
c
u
r
r
e
n
c
e
3eAuestin!
(usiness
)cti$it+ JtimeK JtimeK JtimeK
Jtrue or
falseK
Jtrue or
falseK
Jtrue or
falseK J/hole num.erK
5
&ee chapter 4 in 6UMM7.
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >< of ;;
3espondin!
(usiness
)cti$it+ JtimeK JtimeK JtimeK
Jtrue or
falseK
Jtrue or
falseK
!&T-
%,,4(C%
+4#
!&T-
%,,4(C%+4#
,rovide a +usiness Transaction Transition Ta.le if needed) 'ee guidelines section H7etail
Transaction %ctivities &nly (f !ecessary)I
7orm9 (usiness 1ransaction 1ransition 1ab*e
7rom )cti$it+ 7rom 3o*e Document 1o )cti$it+ 1o 3o*e >uard /ondition
J!ame of the
HfromI
activity) The
0ey/ord
'T%*T shall
.e used for the
first activity)K
J%
*e5uesting"(ni
tiating %ctivity
*ole or !&T-
%,,4(C%+4#
) !&T-
%,,4(C%+4#
is to .e used
/hen the $rom
%ctivity is
'T%*T)K
J7ocument
name or
!&!#)K
J!ame of the
destination
activity or
0ey/ord #!7
or 0ey/ord
C&!T*&4-
$%(4#7)K
J% *esponding
%ctivity *ole or
!&T-
%,,4(C%+4#)K
defining or descri.ing
the condition for the
transition or !&!#)K
J!ame of the
last activity
.efore the
#!7 stateK
J%ppropriate
role name)K
!&!# #!7 !&T-
%,,4(C%+4#
J#1pression of the
guard condition)K
J!ame of the
last activity
.efore the
C&!T*&4-
$%(4#7
state)K
J%ppropriate
role name)K
!&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4#
J#1pression of the
guard condition)K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >= of ;;
11 Business (nfor#ation Description
11.1 Goals
The goal of this set of /or0sheets is to identify the information re5uirements for the .usiness
documents specified in the .usiness transactions)
11.2 Guidelines
The first step in specifying .usiness documents in a .usiness process and information model, is
to attempt to reuse .usiness information o.@ects in a +usiness 4i.rary) (f an e1isting .usiness
document cannot .e found then, domain components from 7omain 4i.raries and core
components from the Core 4i.rary can .e used) ntil the +usiness 4i.rary is .uilt up, or
imported from a credita.le source, core components are li0ely to .e referred to fre5uently, to
first add to the repertoire of .usiness information o.@ects in the +usiness 4i.rary, and second, to
create .usiness documents)
The steps for completing these /or0sheets are as follo/sF
a)) 'ee /hat attri.utes are availa.le in .usiness information o.@ects in the availa.le +usiness
4i.raries that can .e used in a .usiness document)
.)) (f .usiness information o.@ects /ith appropriate attri.utes as re5uired for .usiness documents
are not availa.le, ne/ .usiness information o.@ects must .e created)
c)) 4oo0 for re-usa.le information components in the .usiness li.rary and the Core 4i.rary as
candidates for .usiness information o.@ect attri.utes) Ta0e conte1t into account, as specified
in the .usiness process and information models) #1tend e1isting .usiness information
o.@ects, domain components, and core components as re5uired)
d)) %dd the ne/ attri.utes to e1isting .usiness information o.@ects, or introduce ne/ .usiness
information o.@ects through a registration process that manages changes to the +usiness
4i.rary)
e)) se the ne/ attri.utes, no/ in the +usiness 4i.rary, as needed in creating the .usiness
documents)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >A of ;;
11.3 )or(s!eets
11'1 Business infor#ation conte=t
The +usiness (nformation Conte1t form is provided as convenience for aggregating conte1tual
values that effect the analysis of .usiness information) (t is intended that this information .e
o.tained from other forms) $or e1ample, (ndustry 'egment is specified in the +usiness
*eference -odel form) (f there is no value for an entry, enter !&T-%,,4(C%+4# or !&!#
/hich ever is appropriate)
7orm9 (usiness Information /onte6t
7orm Id9 J,rovide an (7 for this form so other forms can reference it (T<)1)B)K
Industr+ Se!ment
(usiness Process
Product
Ph+sica* >eo!raph+
@/onditions @3e!ion
>eo8Po*itica* Le!is*ati$e@
3e!u*ator+@ /u*tura*
)pp*ication Processin!
(usiness Purpose @Domain
Partner 3o*e
Ser$ice Le$e* ;profi*es B not
preferences.<
/ontracts@)!reements
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >B of ;;
11'$ Docu#ent content description
7escri.e each element or group of elements in the document) 4ogically related elements can .e placed in separate forms ($or
e1ample, a document may have logically three parts, a header, .ody, and summary) The .ody may have further logical partitioning)))
,ossi.le values for &ccurs includeF 1 (one instance), 0))1 (Gero on one instance), 0))W (Gero or more instances), 1))W (one or more
instances), or n))m (n to m instances /here n is less than m)) (nformation HloopingI is specified through appropriate occurs values)
,ossi.le values for 7ata Type include primitive data types P such as integer, string, date-type P or a $orm (d of another Content
7escription $orm) *eferencing another Content 7escription $orm (d represents information hierarchy and nesting) (f you happen to
0no/ the name of a reusa.le component from an domain li.rary or the Catalog of Core Components, then you -%: reference it) The
'emantic 7escription '2%44 .e stated in .usiness terms and '2%44 .e unam.iguous)
7orm9 /ontent Description
.*ement@/omponent 4ame "ccurs Data
1+pe
7ie*d
&idth
Semantic Description 4otes
J,rovide a name for the element"component)
$or e1ample, H&rder 'ummaryI or H(ssued
7ate)IK
11'' %ontent #apping
These forms '2&47 .e completed) This information is very important as it sho/s that the documents have a .asis in e1isting
standards) $urthermore, the information /ill .e used to create document transformations) 'tandards to map to include #7($%CT,
312, 1C+4, *osetta!et, and other standards such as &+() se 3,%T2 and 3'4T notation for referencing 3-4 elements and
descri.ing the mappings) (f a ne/ document schema is created to fulfil the content re5uirements specified in the 7ocument Content
7escription forms, then a set of Content -apping forms should .e completed for that schema (the component names in the forms are
simply re5uirements for information)
$or each Content 7escription form, complete a 7ocument Content -apping form for each standard to .e cross-referenced)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age >; of ;;
Copyright e.3-4 2001) %ll *ights *eserved)
7orm9 /ontent Mappin!
/ontent Description
7orm Id
J,rovide the identifier of the associated Content 7escription formK
Standard J!ame of the standard) $or e1ample, !"#7($%CTK
5ersion J'tandard version num.er) $or e1ample, 7)01%K
.*ement@/omponent
4ame
Mappin!@1ransformation 4ote
J#nter element"component
name from corresponding
Content 7escription formK
J-apping or transformation) (f the element"component is a comple1
structure, this entry should reference the appropriate Content
-apping form)K
J%ny useful mapping notes)K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?0 of ;;
1 Business Process (dentifier 7a#ing
&che#e
(t is recommended that the naming scheme, +usiness (dentifier !aming 'cheme, descri.ed in
this appendi1 .e applied to uni5uely identify significant o.@ects of an e.3-4 compliant
.usiness model) These o.@ects directly relate to the layers of the -- -etamodel) 'pecifically
the +usiness &perations -ap (+&-) /ith a +usiness ,rocess (dentifier naming 'cheme
(+,(!'), the +usiness *e5uirements Die/ /ith a +usiness Colla.oration (dentifier 'cheme
(+C(!') and the +usiness Transaction Die/ /ith a +usiness Transaction (dentifier 'cheme
(+T(!'))
% +,(!' naming scheme format is defined .y F
.pidFRagencySFRagency-idSFR.usiness-process-nameSURma@or-version-num.erS)Rminor-
version-num.erS
% +C(!' naming scheme format is defined .y F
.cidFRagencySFRagency-idSFR.usiness-colla.oration-nameSURma@or-version-num.erS)Rminor-
version-num.erS
% +T(!' naming scheme format is defined .y F
.tidFRagencySFRagency-idSFR.usiness-transaction-nameSURma@or-version-num.erS)Rminor-
version-num.erS
8here
b!id is the fi1ed string H.pidI indicating the entire identifier is a .usiness process identifier)
bcid is the fi1ed string H.cidI indicating that the entire identifier is a .usiness colla.oration
identifier)
btid is the fi1ed string H.tidI indicating that the entire identifier is a .usiness transaction
identifier)
a$ency identifier or name of the agency that o/ns the agency-ids and must be a !*oba**+
uniAue identifier) $or e1ample, 7!' and #%!)
a$ency1id identifer of the organiGation that o/ns the .usiness process and must be a
!*oba**+ uniAue identifier) :o ot#er entity SBA44 use t#e a$ency identi(ication o( anot#er
entity.
-a@or and minor version num.ers are each integers and need to respect any specific *egistry
%uthority conventions defined)
The .usiness-process-name, .usiness-colla.oration-name, .usiness-transaction-name should .e
descriptive names) (t is recommended that the descriptive name .e in camel-case) The names
must not contain spaces, periods, colons, or dollar signs) The organiGation or agency-id that
o/ns the .usiness transaction '2%44 .e responsi.le for guaranteeing that the identifier is
uni5ue))
Dalid e1amples of .usiness processes using the identifier naming scheme includeF
.tidFean)12>?<=AB;012BF7istri.ute&rder'tatusU1)0
.pidFicannFmy)comF!e/+usiness,rocessU2)0
8ith respect to the e.3-4 *egistry (nformation -odel specification
10
the definition is as
follo/sF
(PI4S 3e!istr+ Information Mode*
.pid #1trinsic&.@ect)o.@ectType
.cid #1trinsic&.@ect)o.@ectType
.tid #1trinsic&.@ect)o.@ectType
agency &rganiGation)name
agencyid &rganiGation)uuid
.usiness-process-name #1trinsic&.@ect)name
.usiness-colla.oration-name #1trinsic&.@ect)name
.usiness-transaction-name #1trinsic&.@ect)name
ma@or-version-num.er #1trinsic&.@ect)ma@orDersion
minor-version-num.er #1trinsic&.@ect)minorDersion
%n #1trinsic&.@ect is a special type of -anaged&.@ect (one that goes through a defined life
cycle)O the e1trinsic o.@ect is not re5uired for the core operation of a registry) %n &rganiGation
is defined as an (ntrinsic&.@ectO it is core to the function of a registry)
89
'ref 6eb),M7 and 6eb)&7.
$ "he Porter >alue %hain
The follo/ing ta.le sho/s the categories of the ,orter Dalue Chain J,DCK and ho/ they map to
#conomic #lements concepts) This is included as an aid to help users formaliGe their
classification of the elements of a .usiness process specification)
4ormati$e
/ate!or+
4ormati$e Sub8
/ate!or+
3esource inf*o,s
C outf*o,
Ma#or t+pes of
e$ents
.conomic )!ents C
3o*es
,rocurement +id 'u.mission
Contract
!egotiation
,urchase &rder
,reparation
*eceiving
-oney
*a/ materials
$acilities
'ervices
Technology
,ayments
,urchase
,urchase &rders
,rice Nuotes
Contract
!egotiation
+uyer
'eller
Dendor
Cashier
2uman *esources 2iring
Training
,ayroll
-anagement
,ersonnel
7eployment
-oney
,urchased training
materials
,urchased .enefit
pac0ages
Cash ,ayments
%c5uisition of la.or
Training
#mployee
'tudent
+eneficiary
Transportation 4oading
'hipping
,ac0aging
*a/ -aterials
7elivered *a/
-aterials
-anufactured
9oods
7elivered -anufact)
9oods
'hipment
8arehousing Tas0s
-aterial 2andling
Truc0ing
+uyer
Dendor
4ogistics 8or0er
Truc0er
-anufacturing ,roduct
7evelopment
,roduct 7esign
%ssem.ly
Nuality control
$acilities M
Technology
4a.or
*a/ -aterials
$inished 9oods
-anufacturing
&peration
*a/ -aterial (ssue
-anufacturing Jo.
$actory 8or0er
'upervisor
NC (nspector
-ar0eting M 'ales %dvertising se M
Campaigning
-ar0eting
-anagement
'ales Calling
4a.or
%dvertising 'ervice
7elivered 9oods
,roduct 'ervices
Cash
Cash ,ayment
Customer (nvoice
'ale &rder
,rice Nuotes
Contract
Customer
'alesperson
Cashier
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?> of ;;
4ormati$e
/ate!or+
4ormati$e Sub8
/ate!or+
3esource inf*o,s
C outf*o,
Ma#or t+pes of
e$ents
.conomic )!ents C
3o*es
Customer Credit
-anagement
!egotiation
Customer 'ervice %fter 'ales 'ervice
8arranty
Construction
4a.or
,urchased 'ervices
,roduct 8arranties
and 'ervices
'ervice Call
,roduct *epair
'ervice Contract
Customer 'ervice
%gent
Customer
$inancing 4oan -anagement
'toc0 'u.scriptions
and 'ales
7ividend ,olicy

Cash
+onds
'toc0s
7erivative
(nstruments
(nterest ,ayments
'toc0 'u.scriptions
7ividend
7eclarations
Cash *eceipts
'toc0holders
+ond2olders
(nvestment +ro0ers
$inancial -anagers
%dministration %ccounting
$inancial *eporting
#1ecutive
-anagement
#mployee 4a.or #mployee 'ervice
-anagement
,ro@ects
-anagers
Cler0s
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?? of ;;
' Drop &hip &cenario 3=a#ple
This appendi1 provides an e1ample of the /or0sheet-.ased analysis for a .usiness reference
model, H7irect to Customer 7rop 'hip *etail)I (n many cases, -- -4 diagrams are
provided) %s /ith the rest of this document, it is /or0 in progress) (t is our hope that you find
this information helpful in understanding ho/ you can ma0e these /or0sheets /or0 for you)
7orm 4umber 7orm 1+pe
1)X Top level of +usiness *eference -odel F defines the Hframe of referenceI of all /or0sheets)
2)X +usiness ,rocess %rea F $orm that defines the scope of the .usiness area
>)X +usiness ,rocess (dentification and 7iscovery F $orms that inventory all .usiness processes)
?)X +usiness ,rocess 'ummary !ame form
<)X +usiness ,rocess #la.oration F $orms used to descri.e the .usiness processes and identify
actors as /ell as pre and post conditions for the .usiness processes) (use cases)
=)X +usiness Colla.oration 7efinition F define the economic events that ta0e place to fulfill the
.usiness process, including system .oundaries and the protocols that govern the flo/ of
information)
A)X Colla.oration Transitions
B)X +usiness Transaction 7efinition F $orms that defines the actual activities and authoriGed
parties /ithin the organiGation that initiate these transactions)
;)X Content"document definition
10)X +usiness information conte1t
11)X Content mapping
/odel #ontents
1.(usiness Process Identifier 4amin! Scheme..........................................................................1
2.1he Porter 5a*ue /hain...........................................................................................................3
3.Drop Ship Scenario .6amp*e...................................................................................................%
'usiness !rocess identi(ication and discovery/ 'R011.01direct1to1customer1dro!1s#i!1retail1
model.........................................................................................................................................4-
+usiness areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?B
7irect to customer retail process areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<0
$inancial process areas))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<?
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?< of ;;
Customer-order-management .usiness process summaries))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<<
Customer order fulfillment .usiness process summaries))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
Dendor inventory management processes summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
,roduct catalog e1change .usiness processes summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=
,ayment .usiness process summaries)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<A
'usiness !rocess elaboration....................................................................................................&-
+,C-<)1-$irm-sales-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<A
+,C-<)2-Customer-credit-in5uiry))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<B
+,C-<)>-Customer-credit-payment))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<B
+,C-<)?-,urchase-order-management)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<;
+,C-<)<-'hip-goods)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=0
+,C-<)=-(nventory-management))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=0
+,C-<)A-'ales-product-notification)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=1
+,C-<)B-,resent-invoice))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=2
'usiness collaboration and economic events............................................................................+2
+C-=)1-Create-customer-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=2
+C-=)2-Chec0-customer-credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=?
+C-=)>-,rocess-credit- payment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=<
+C-=)?-Create-vendor-purchase-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))==
+C-=)<-'hipment-instruction))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=B
+C-=)=-Confirm-shipment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=;
+C-=)A-Dendor-inventory-reporting))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A1
+C-=)B-*e5uest-inventory-report))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A2
+C-=);-'ales-product-offering))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A?
+C-=)10-(nvoice-presentment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A<
'usiness transactions and aut#ori2ed roles..............................................................................--
+T-B)1-$irm-customer-sales-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))AA
+T-B)2-Chec0 customer credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))AB
+T-B)>-Charge-customer-credit))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))A;
+T-B)?-Create-vendor-purchase-order))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B0
+T-B)<-Dendor-inventory-report)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B2
+T-B)=-*e5uest-inventory-report))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B>
+T-B)A-'hipment-notification)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B<
+T-B)B-Confirm-shipment)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))B=
+T-B);-,roduct-offering))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))BB
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?= of ;;
+T-B)10-,resent-invoice))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));0
'usiness in(ormation descri!tion..............................................................................................91
,urchase order)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));1
Content mapping))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));?
.Disc*aimer..................................................................................................................................9-
%./ontact Information.................................................................................................................97
%usiness process identi&ication and discovery0 %R/11..1direct1to1
customer1drop1s!ip1retail1model
Direct "o %usto#er Drop &hip -etail .
"ransaction and Physical Goods 2lo, *vervie,
'ustomer
(rder
0ntry
$&.endor
)etailer
Bank
B$B &erver
B$B
&erver
'redit Authority
1
?

B
"
/
P
r
o
d
u
c
t
/
*
f
f
e
r
i
n
g
'? B"/2ir#/%usto#er/
&ales/*rder
$
?

B
"
/
>
e
n
d
o
r
/
(
n
v
e
n
t
o
r
y
/
-
e
p
o
r
t
)? B"/%heck/
%usto#er/%redit
1
?

B
"
/
%
r
e
a
t
e
/
>
e
n
d
o
r
/
P
u
r
c
h
a
s
e
/
*
r
d
e
r
/ransport
5? B"/&hip#ent/
7otification
6
?

B
"
/
%
o
n
f
i
r
#
/
&
h
i
p
#
e
n
t
5b?Physical Delivery
of Goods
8? B"/%harge/
%usto#er/%redit
;
?

B
"
/
P
r
e
s
e
n
t
/
(
n
v
o
i
c
e
7otes. &e@uencing is appro=i#ate "ransactions 1 0 $ can occur #ultiple ti#es and in parallel to the
other transactions

7i!ure 118-9 Direct 1o /ustomer 3etai* 1ransaction and Ph+sica* >oods 7*o, "$er$ie,
7orm9 (usiness 3eference Mode*
7orm Id +*--1)0-7irect-To-Customer-7rop-'hip-*etail--odel
(usiness 3eference Mode*
4ame
7(*#CT T& C'T&-#* 7*&, '2(, *#T%(4 -&7#4
Industr+ Se!ment *etail
Domain Scope (nternet retail, catalog, distri.ution center, delivery, .illing)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?A of ;;
(usiness )reas 7irect To Customer *etail
$inance
"ptiona* for ebXML
(usiness =ustification 7efine more efficient on-line retailer"vendor interaction) *educe inventory
carrying costs)
$irect /o 'ustomer
)etail
::BusinessArea;;
<inance
::BusinessArea;;
7i!ure 11879 DD(usiness"perationsMapEEDirect 1o /ustomer Drop Ship 3etai*
%usiness areas
BA"=.9"$irect"to"customer"retail
7orm9 (usiness )rea
7orm Id +%-2)0-7irect-to-Customer-*etail
(usiness )rea 4ame 7irect to Customer *etail
Description This is a demonstrative .usiness process model, to illustrate e.3-4 .usiness
process modeling, and .ased on actual .usiness practice conventions today)
'ee Y&.@ectiveE section .elo/ in this form)
Scope (nternet .ased retail, mail order catalog, direct to customer product fulfillment
logistics, single piece product delivery from a distri.ution center to an end
customer)
)rea
Customer
*etailer
7irect 'upply *etail Dendor (7'Dendor)
Transport Carrier
Credit %uthority
3eferences #%! (nternational
9lo.al Commerce (nitiative
D(C'
'C&*
Hmy company typical Dendor Compliance -anualI
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?B of ;;
/onstraints (nternet .ased retail customer service system
8e. .ro/ser limitations)
7omestic customer orders only
Sta'eho*ders Customer
*etailer
Transport Carrier
Credit %uthority
Process )reas Customer &rder -anagement
Customer &rder $ulfillment
Dendor (nventory -anagement
,roduct Catalog #1change
"ptiona* for ebXML
"b#ecti$e To deliver a commercial product directly to a customer, in a timely and efficient
manner directly from a product supply source, /ith an online (nternet retailer
ta0ing the customer order and providing direct customer service management)
(usiness "pportunit+ *educe retailer inventory carrying costs) 'horten the supply chain from a
domestic vendor to a domestic customerO thus save trees, energy and lives)
7ote The +usiness %rea diagram (.elo/) sho/s all the process areas in this .usiness area)
$irect /o 'ustomer )etail
'ustomer (rder
Management
::ProcessArea;;
'ustomer (rder
<ulfillment
::ProcessArea;;
.endor ,n!entory
Management
::ProcessArea;;
Product 'atalog
0>change
::ProcessArea;;
7i!ure 11889 DD(usiness)reaEEDirect to /ustomer 3etai*
BA"=.8"<inacial
7orm9 (usiness )rea
7orm Id +%-2)1-$inacial
(usiness )rea 4ame $inacial
Description
Scope
)rea
*etailer
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ?; of ;;
3eferences
/onstraints
Sta'eho*ders *etailer
Process )reas ,ayment
"ptiona* for ebXML
"b#ecti$e
(usiness "pportunit+
Payment
::ProcessArea;;
7i!ure 11899 DD(usiness)reaEE 7inance
Direct to customer retail process areas
PA"?.8"'ustomer"order"management
7orm9 (usiness Process )rea
7orm Id ,%->)1-Customer-&rder--anagement
Process )rea 4ame Customer &rder -anagement
"b#ecti$e Ta0e a sales order from an (nternet .ased customer
Dalidate a customerEs a.ility to pay for product upon delivery
Ta0e payment from a customerEs credit card after a product has .een
delivered directly to a customer
Scope $ulfill customer orders using a >rd party supplier for drop ship (customer
direct) delivery)
3eferences Hmy company Dendor &perations Compliance -anualI
(oundar+ of the Process )rea
/onstraints Customer promise of product availa.ility most li0ely true at a vendor
location /hen a customer order is accepted .y the retailer)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <0 of ;;
Customer must have sufficient credit to eventually pay for the product after
the product has .een shipped)
Sta'eho*ders Customer
*etailer
Credit %uthority
(usiness Processes $irm 'ales &rder
Customer Credit (n5uiry
Customer Credit ,ayment
"ptiona* for ebXML

'ustomer
*from Actors+
<irm &ales (rder
::BusinessProcess;;
'ustomer 'redit ,n-uiry
::BusinessProcess;;
)etailer
*from Actors+
'reditAuthority
*from Actors+
'ustomer 'redit Payment
::BusinessProcess;;
7i!ure 118109 DDProcess)reaEE/ustomer "rder Mana!ement
PA"?.="'ustomer"order"fulfillment
7orm Id ,%->)2-Customer-&rder-$ulfillment
Process )rea 4ame Customer &rder $ulfillment
"b#ecti$e %llo/ a retailer to instruct a direct supply vendor to deliver (/ithin specific
delivery times) specific product to a specific customer)
Scope
3eferences Hmy company Dendor Compliance &perating -anualI
(oundar+ of the Process )rea %ctivities directly pertaining to the registration of firm customer sales orders,
and credit payment of delivered customer sales orders)
/onstraints &n hand product allocation to a customer order .y a vendor immediately
after processing a retailerEs purchase order)
&n time product delivery from vendor to customer)
(mmediate notification .y a vendor to a retailer of a direct to customer
product deliveryO /ith customer service details)
7'Dendor
Transport Carrier
Customer
(usiness Processes ,urchase &rder -anagement
'hip 9oods
"ptiona* for ebXML
)etailer
*from Actors+
Purchase (rder Management
::BusinessProcess;;
$&.endor
*from Actors+
/ransport'arrier
*from Actors+
&hip @oods
::BusinessProcess;;
7i!ure 118119 DDProcess)reaEE/ustomer "rder 7u*fi**ment
PA"?.?".endor"in!entory"management
7orm Id ,%->)>-Dendor-(nventory--anagement
Process )rea 4ame Dendor (nventory -anagement
"b#ecti$e To allo/ a direct supply vendor to report Havaila.le on-handI inventory to a
retailer)
Scope
/onstraints (nventory, .y product 'L identification, is Havaila.le on-handI /ithin the
direct supply vendorEs inventory management system)
7'Dendor
(usiness Processes (nventory -anagement
"ptiona* for ebXML
$&.endor
*from Actors+
,n!entory Management
::BusinessProcess;;
)etailer
*from Actors+
7i!ure 118129 DDProcess)reaEE5endor In$entor+ Mana!ement
PA"?.4"Product"catalog"e>change
7orm Id ,%->)?-,roduct-Catalog-#1change
Process )rea 4ame ,roduct Catalog #1change
"b#ecti$e To maintain an accurate catalog (list) of a vendorEs products, in a retailerEs
.usiness operating systemO especially as vendorEs products are introduced to the
mar0et or e1isting products re5uire updated product specifications .et/een the
vendor and the retailer)
Scope
/onstraints #1istence of a valid .usiness operating relationship .et/een a specific
vendor and a retailer, such that products offered .y a vendor can .e in turn
offered to an end customer .y the retailer)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <> of ;;
7'Dendor
(usiness Processes 'ales ,roduct !otification
"ptiona* for ebXML
$&.endor
*f rom Actors+
&ales Product Aotification
::BusinessProcess;;
)etailer
*f rom Actors+
7i!ure 118139 DDProcess)reaEEProduct /ata*o! .6chan!e
2inancial process areas
PA"?."Payment
7orm Id ,%->)<-,ayment
Process )rea 4ame ,ayment
"b#ecti$e $or the vendor to invoice the retailer for goods shipped and services provided)
Scope The scoped is defined .y the follo/ing .usiness processesF
,resent (nvoice
/onstraints Dalid .usiness relationship
7'Dendor
(usiness Processes ,resent (nvoice
"ptiona* for ebXML
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <? of ;;
$&.endor
*f rom Actors+
Present ,n!oice
::BusinessProcess;;
)etailer
*f rom Actors+
7i!ure 11819 DDProcess)reaEE Pa+ment
#ustomer1order1mana"ement business process summaries
BP&"4.8"<irm"sales"order
7orm9 (usiness Process Summar+
7orm Id +,'-?)1-$irm-'ales-&rder
(usiness Process 4ame $irm 'ales &rder
Identifier .pidFean)12>?<=AB;012BF$irm'ales&rderU1)0
Process )rea Customer &rder -anagement
(usiness )rea 7irect to Customer *etail
BP&"4.="'ustomer"credit"in-uiry
7orm Id +,'-?)2-Customer-Credit-(n5uiry
(usiness Process 4ame Customer Credit (n5uiry
Identifier .pidFean)12>?<=AB;012BFCustomerCredit(n5uiryU1)0
BP&"4.?"'ustomer"credit"payment
7orm Id +,'-?)>-Customer-Credit-,ayment
(usiness Process 4ame Customer Credit ,ayment
Identifier .pidFean)12>?<=AB;012BFCustomerCredit,aymentU1)0
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age << of ;;
#ustomer order &ul&illment business process summaries
BP&"4.4"Purchase"order"management
7orm Id +,'-?)?-,urchase-&rder--anagement
(usiness Process 4ame ,urchase &rder -anagement
Identifier .pidFean)12>?<=AB;012BF,urchase&rder-anagementU1)0
Process )rea Customer &rder $ulfillment
BP&"4."&hip"goods
7orm Id +,'-?)<-'hip-9oods
(usiness Process 4ame 'hip 9oods
Identifier .pidFean)12>?<=AB;012BF'hip9oodsU1)0
Process )rea Customer &rder $ulfillment
3endor inventory mana"ement processes summaries
BP&"4.#",n!entory"management
7orm Id +,'-?)=-(nventory--anagement
(usiness Process 4ame (nventory -anagement
Identifier .pidFean)12>?<=AB;012BF(nventory-anagementU1)0
Process )rea Dendor (nventory -anagement
4roduct catalo" e5c!an"e business processes summaries
BP&"4.1"&ales"product"notification
7orm Id +,'-?)A-'ales-,roduct-!otification
(usiness Process 4ame 'ales ,roduct !otification
Identifier .pidFean)12>?<=AB;012BF'ales,roduct!otificationU1)0
Process )rea ,roduct Catalog #1change
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <= of ;;
4ayment business process summaries
BP&"4.3",n!oice"presentment
7orm Id +,'-?)B- ,resent-(nvoice
(usiness Process 4ame ,resent (nvoice
Identifier .pidFean)12>?<=AB;012BF,resent(nvoiceU1)0
Process )rea ,ayment
(usiness )rea $inance
%usiness process elaboration
%46#1$.112irm1sales1order
7orm Id +,C-<)1-$irm-'ales-&rder
(usiness Process 4ame $irm 'ales &rder
Identifier .pidFean)12>?<=AB;012BF$irm'ales&rderU1)0
)ctors Customer
*etailer
Performance >oa*s %ccept a firm customer sales order for a product, and promise the customer
a delivery time at total sales amount including all ta1es /ithin seconds after
the customer has made a product choice and given relevant personal detailsO
ie) /hile customer is online)
Preconditions Dalid customer details (name, address, credit card)
Dalid product details (product 'L details)
(e!ins &hen Customer completes all personal identity data for *etailer)
Customer successfully selects valid product to .e purchased and specifies
valid product 5uantity)
Customer accepts terms of sale)
Definition *etailer needs to validate customerEs credit limit /ith a Credit %uthority,
and if enough credit is availa.le to cover the product to .e purchased, the
*etailer /ill accept the Customers firm sales order)
.nds &hen Dalid customer sales order is created in *etailerEs .usiness operating
system)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <A of ;;
.6ceptions Customer fails internal credit chec0O ie) fraud)
Customer delivery needs violate *etailers standard terms of sale)
Postconditions Dalid customer sales order)
Customer is notified of positive sale, and can e1pect delivery /ithin
promised delivery time)
1raceabi*it+ !ot %pplica.le
%46#1$.21#ustomer1credit1inquiry
7orm Id +,C-<)2-Customer-Credit-(n5uiry
(usiness Process 4ame Customer Credit (n5uiry
Identifier .pidFean)12>?<=AB;012BFCustomerCredit(n5uiryU1)0
)ctors *etailer
Credit %uthority
Performance >oa*s *etailer e1pects the Credit %uthority to perform a credit card chec0 for a
specified sales amount and in seconds)
Preconditions Customer credit card details 0no/n)
Total sales price, including ta1es, 0no/n)
(e!ins &hen *etailer can present .oth all customer credit card details and a re5uested
total credit amount to .e chec0ed against this customer)
Definition *etailer re5uests Credit %uthority to authoriGe the total sales amount against
the customerEs credit amount)
The Credit %uthority responds to the *etailer /ith either a positive or
negative credit report on the customer)
.nds &hen Credit %uthority returns either a positive or negative Customer report)
.6ceptions Credit %uthority fails to respond to *etailer /ithin an accepta.le period)
Postconditions Customer has a reserved credit cash e5ual to the total purchase amount
authoriGed to the *etailer for a 2? hour period)
%46#1$.31#ustomer1credit1payment
7orm Id +,C-<)>-Customer-Credit-,ayment
(usiness Process 4ame Customer Credit ,ayment
Identifier .pidFean)12>?<=AB;012BFCustomerCredit,aymentU1)0
)ctors *etailer
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <B of ;;
Credit %uthority
Performance >oa*s *etailer e1pects Credit %uthority to positively charge the CustomerEs credit
for the total sales amount immediately upon re5uest)
Preconditions Confirmed shipment, .y Dendor, of purchased product direct to Customer)
(e!ins &hen Dendor confirms to *etailer that the specified product prescri.ed on the
current updated version of a 7'DendorEs purchase order has .een actually
shipped to the specified customer)
Definition Credit %uthority ma0es a credit charge against the CustomerEs account, on
.ehalf of the *etailer)
Credit %uthority reports, to *etailer, the status of the credit charge)
.nds &hen Credit %uthority reports .ac0 to the *etailer that the customerEs credit has
.een charged for the total sales amountO and thus credited to the *etailerEs
account)
.6ceptions Credit %uthority reports to *etailer that the customerEs credit account cannot
.e charged /ith total sales price)
Postconditions Credit %uthority transfers total sales amount from the CustomerEs account to
the *etailerEs account)
%46#1$.414urc!ase1order1mana"ement
7orm Id +,C-<)?-,urchase-&rder--anagement
(usiness Process 4ame ,urchase &rder -anagement
Identifier .pidFean)12>?<=AB;012BF,urchase&rder-anagementU1)0
)ctors *etailer
Dendor
Performance >oa*s 7'Dendor returns a ,& %c0no/ledgment to the *etailer /ithin ? hours of
receipt of the ,urchase &rder)
Preconditions Dalid Customer sales order /ith *etailer)
Dalid *etailerP7'Dendor relationO ie) terms and conditions)
(e!ins &hen *etailer has created a valid ,urchase &rder *e5uest)
Definition pon receiving a ,urchase &rder *e5uest, the 7'Dendor does a product
allocation to the ,& against availa.le inventory and returns a positive ,&
%c0no/ledgment to the *etailer)
.nds &hen Dalid positive ,& %c0no/ledgment returned from the 7'Dendor to the
*etailer)
.6ceptions 7'Dendor does not return any ,& %c0no/ledgment
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age <; of ;;
7'Dendor returns a negative ,urchase &rder %c0no/ledgement
Postconditions 7'Dendor has allocated correct product to fill ,urchase &rder
7'Dendor has created all correct instructions for its /arehouse management
system to pic0, pac0 and ship)
%46#1$.$1S!ip1"oods
7orm Id +,C-<)<-'hip-9oods
(usiness Process 4ame 'hip 9oods
Identifier .pidFean)12>?<=AB;012BF'hip9oodsU1)0
)ctors 7'Dendor
Transport Carrier
Performance >oa*s Transport Carrier informs 7'Dendor /ithin seconds of ,& pic0up, and
7'Dendor registers ,& transport trac0ing num.er /ithin its .usiness
operating system /ithin seconds)
Preconditions ,& has .een pic0ed, pac0ed and is ready to .e shipped)
(e!ins &hen 7'Dendor informs Transport Carrier of a ,& needing to .e delivered to a
specific Customer address)
Definition 7'Dendor manifests ,& /ith Transport Carrier
Transport Carrier registers transport, chec0s Hship toI details and assigns a
trac0ing num.er for the shipment)
.nds &hen Transport Carrier confirms ,& pic0up to 7'Dendor and .egin of ordered
goods delivery to Customer)
.6ceptions Transport Carrier detects that H'hip ToI address is invalid)
Transport Carrier fails to confirm ,& pic0up)
Postconditions Carrier assigns Transport trac0ing num.er to ,urchase &rder and informs
7'Dendor of trac0ing num.er)
%46#1$.*17nventory1mana"ement
7orm Id +,C-<)=-(nventory--anagement
(usiness Process 4ame (nventory -anagement
Identifier .pidFean)12>?<=AB;012BF(nventory-anagementU1)0
)ctors *etailer
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =0 of ;;
7'Dendor
Performance >oa*s &nce a day, the 7'Dendor reports their Havaila.le on-handI inventory to the
*etailer)
Preconditions Dalid .usiness agreement)
(e!ins &hen *epeating event, occurs unsolicited from 7'Dendor to *etailer)
Definition 7'Dendor reconciles Havaila.le on-handI inventory and reports only
product availa.ility for those products /hich are agreed upon .et/een
*etailer and 7'Dendor)
.nds &hen *etailer has received a valid Havaila.le on-handI inventory report from
7'Dendor)
.6ceptions !o Havaila.le on-handI inventory report received)
*eported product 5uantiry on hand /ith 7'Dendor is less than any prior
agreed 'afety 'toc0 level /ith *etailer)
Postconditions *etailers .usiness operating system has recorded ne/ Havaila.le on-handI
inventory .y product)
%46#1$.+1Sales1product1noti&ication
7orm Id +,C-<)A-'ales-,roduct-!otification
(usiness Process 4ame 'ales ,roduct !otification
Identifier .pidFean)12>?<=AB;012BF'ales,roduct!otificationU1)0
)ctors *etailer
7'Dendor
Performance >oa*s !one
Preconditions Dalid 7'Dendor P *etailer .usiness relationship
(e!ins &hen (nitial start of the .usiness relationship, for all related products)
8henever 7'Dendor has a product specification change or addition that
applies to the *etailer)
Definition 7'Dendor initiates a product specification re5uest to Hoffer for saleI the
*etailer)
*etailer either accepts product offer, or re@ects the offer)
.nds &hen *etailer responds to 7'Dendor acceptance or re@ection of product offer for
sale)
.6ceptions !one
Postconditions &n product acceptance, *etailer can register product for sale to Customers)
%46#1$.,14resent1invoice
7orm Id +,C-<)B-,resent-(nvoice
(usiness Process 4ame ,resent (nvoice
Identifier .pidFean)12>?<=AB;012BF,resent(nvoiceU1)0
)ctors 7'Dendor
*etailer
Performance >oa*s
Preconditions Dalid 7'Dendor P *etailer .usiness relationship
Corresponding ,urchase &rder /as accepted
*elated %dvance 'hipment !otification /as sent
(e!ins &hen 8henever 7'Dendor /ants to invoice the *etailer for goods shipped)
Definition
.nds &hen
.6ceptions
Postconditions
%usiness collaboration and economic events
%#1*.11#reate1customer1order
7orm Id +C-=)1-Create-Customer-&rder
Identifier .cidFean)12>?<=AB;012BFCreateCustomer&rderU1)0
Description The customer enters a sales order using on-line store-front application)
Partner 1+pes Customer
*etailer
)uthori2ed 3o*es
Le!a* steps@reAuirements
.conomic conseAuences
Initia*@termina* e$ents
Scope
(oundar+
/onstraints

<A,LU)0
&/A)/
<irm'ustomer&ales(rder
::Business/ransactionActi!ity;;
&U''0&&
6 Business/ranaction*B<irm'ustomer&ales(rderB+.&tateC0A$ 7
6 Business/ranaction*B<irm'ustomer&ales(rderB+.&tateC'(A/)(L"<A,L0$ 7
-etailer %usto#er
7i!ure 1181%F DD(usiness/o**aborationProtoco*EE /reate/ustomer"rder
!ote that in this .usiness colla.oration protocol, there is only one .usiness transaction activity
and the Customer (partner type) initiates it) The *etailer, although sho/n in the diagram for
completeness, does not initiate any .usiness transaction activity)
7orm Id +C,T-A)1-Create-Customer-&rder
Identifier .cidFean)12>?<=AB;012BFCreateCustomer&rderU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
(usiness )cti$it+ 3espondin!@
3ecei$in! Partner
1+pe
'T%*T Customer Create &rder *etailer !&!#
Create &rder !&T-
%,,4(C%+4#
'CC#'' Customer +usinessTranaction(6$irm
Customer'ales&rder6))'tat
eZ#!7 K
Create &rder !&T-
%,,4(C%+4#
$%(4*# Customer +usinessTranaction(6$irm
Customer'ales&rder6))'tat
eZC&!T*&4-$%(4#7 K
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age => of ;;
%#1*.21#!ec(1customer1credit
7orm Id +C-=)2- Chec0-Customer-Credit
Identifier .cidFean)12>?<=AB;012BF Chec0CustomerCreditU1)0
Partner 1+pes *etailer
Credit %uthority
)uthori2ed 3o*es *etailer
Credit %uthority Credit 'ervice
Le!a* steps@reAuirements !one
.conomic conseAuences %s the result of the credit chec0, the customerEs availa.le credit is reduced .y the
total sales amount for a period of 2? hours)
Initia*@termina* e$ents (nitial - Dalid customer
Terminal P Customer .ad credit causes Credit %uthority chec0 to fail)
Scope Credit %uthority provides necessary information to retailer to continue
processing order)
(oundar+ 'ystems include F
Credit %uthority service)
7'Dendor customer order entry system
/onstraints !one

&/A)/
'heck'ustomer'redit
&U''0&&
<A,LU)0
6 Business/ransaction*B'heck 'ustomer 'reditB+.&tateC0A$ 7
6 Business/ransaction*B'heck 'ustomer 'reditB+.&tateC'(A/)(L"<A,L0$ 7
%reditAuthorit y -etailer
7i!ure 1181-9 DD(usiness/o**aborationProtoco*EE /hec'/ustomer/redit
!ote that there is only one initiated activity, Chec0CustomerCredit, in this colla.oration)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =? of ;;
7orm Id +C,T-A)2- Chec0-Customer-Credit
Identifier .cidFean)12>?<=AB;012BFCustomerCreditChec0U1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer Chec0 Customer
Credit
Credit %uthority
Chec0 Customer
Credit
!&T-%,,4(C%+4# 'CC#'' *etailer +usinessTransaction(HC
hec0 Customer
CreditI))'tateZ#!7
Chec0 Customer
Credit
!&T-%,,4(C%+4# $%(4*# *etailer +usinessTransaction(HC
hec0 Customer
CreditI))'tateZC&!T*
&4-$%(4#7
%#1*.314rocess1credit1 payment
7orm Id +C-=)>-,rocess-Credit- ,ayment
Identifier .cidFean)12>?<=AB;012BF,rocessCredit,aymentU1)0
Credit %uthority
)uthori2ed 3o*es *etailer)%ccounts *eceiva.le
Credit %uthority 'ervice
Le!a* steps@reAuirements 'ale of goods has ta0en place
.conomic conseAuences *etailer receives payment

Customer actually gets charged
Initia*@termina* e$ents (nitial P ,roducts are .eing delivered (in-route) or have .een delivered)
Terminal P *etailer receives payment
Scope Credit %uthority credits customerEs credit, only after product(s) have .een
shipped (or are .eing shipped) to customer)
Credit %uthority payment system
/onstraints 7'Dendor must confirm that shipment of product direct to customer has ta0en
place)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =< of ;;

<A,LU)0
&/A)/
'harge'ustomer'redit
&U''0&&
6 Bysiness/ransaction*B'harge 'ustomer 'reditB+.&tateC0A$ 7
6 Bysiness/ransaction*B'harge 'ustomer 'reditB+.&tateC'(A/)(L"<A,L0$
7
%reditAuthorit y -etailer
7i!ure 118179 DD(usiness/o**aborationProtoco*EE Process/reditPa+ment
7orm Id +C,T-A)>-Credit-Card-,ayment
Identifier .cidFean)12>?<=AB;012BFCreditCard,aymentU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer Charge Customer
Credit
Credit %uthority !&!#
Charge Customer
Credit
!&T-
%,,4(C%+4#
'CC#'' *etailer +ysinessTransaction(6Cha
rge Customer
Credit6))'tateZ#!7
Charge Customer
Credit
!&T-
%,,4(C%+4#
$%(4*# *etailer +ysinessTransaction(6Cha
rge Customer
Credit6))'tateZC&!T*&4
-$%(4#7
%#1*.41#reate1vendor1purc!ase1order
7orm Id +C-=)?-Create-Dendor-,urchase-&rder
Identifier .cidFean)12>?<=AB;012BFCreateDendor,urchase&rderU1)0
7'Dendor
)uthori2ed 3o*es *etailer)(nventory+uyer
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age == of ;;
7'Dendor)Customer'ervice
Le!a* steps@reAuirements Confirmed ,& %c0no/ledgment implies a .inding agreement .et/een *etailer
and 7'Dendor, per conditions of an e1isting .usiness relation and a specific
open ,urchase &rder)
.conomic conseAuences (ntent to purchase product is made e1plicit
7'Dendor allocates on-hand inventory to cover ,& 'L 5uantity for
immediate direct shipment to customer
Initia*@termina* e$ents Dalid sales order e1ists
,urchase &rder response
Scope Chec0ing 7'Dendor on-hand inventory to determine if a ,urchase &rder can .e
accepted or re@ected)
*etailer ,urchase &rder -anagement system
7'Dendor Customer &rder #ntry system
/onstraints Timely response /ithin ? hours of su.mitting ,& *e5uest

6 Business/ransaction*B'reate .endor Purchase
(rderB+.&tateC'(A/)(L"<A,L0$ 7
&/A)/
'reate.endorPurchase(rder
::Business/ransactionActi! ity ;;
&U''0&&
<A,LU)0
6 Business/ransaction*B'reate
.endor Purchase
(rderB+.&tateC0A$ 7
6 .endorList.&tateCA("M()0".0A$()& 7
D&>endor -etailer
7i!ure 118189 DD(usiness/o**aborationProtoco*EE /reate5endorPurchase"rder
7orm Id +C,T-A)?-Create-Dendor-,urchase-&rder
Identifier .cidFean)12>?<=AB;012BFCreateDendor,urchase&rderU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer Create Dendor 7'Dendor 'ales&rder)'tatusZD%4(
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =A of ;;
,urchase &rder 7
Create Dendor
,urchase &rder
!&T-
%,,4(C%+4#
'CC#'' *etailer +usinessTransaction(6Cre
ate Dendor ,urchase
&rder6))'tateZ#!7
Create Dendor
,urchase &rder
!&T-
%,,4(C%+4#
Create Dendor
,urchase &rder
*etailer +usinessTransaction(6Cre
ate Dendor ,urchase
&rder6))'tateZC&!T*&4
-$%(4#7
Create Dendor
,urchase &rder
!&T-
%,,4(C%+4#
$%(4*# *etailer Dendor4ist)'tateZ!&-
-&*#-D#!7&*'
%#1*.$1S!ipment1instruction
7orm Id +C-=)<-'hipment-(nstruction
Identifier .cidFean)12>?<=AB;012BF'hipment(nstructionU1)0
Partner 1+pes 7'Dendor
Transport Carrier
)uthori2ed 3o*es 7'Dendor)'hipper
Transport Carrier)Customer 'ervice
Le!a* steps@reAuirements Dendor declares goods of carriage to carrier)
(noteF for this e1ample /e are using domestic shipments only)
.conomic conseAuences !one
Initia*@termina* e$ents (nitial P 'uccessful Create Dendor ,urchase &rder .usiness colla.oration)
Terminal P Transport Carrier provides vendor /ith transport manifest)
Scope ,ertains to arrangement of physical transport per prior agreement .et/een
*etailer and Transport Carrier)
7'Dendor /arehouse management " transport planning system)
Transport Carrier manifesting " +ill of 4ading document management
system)
/onstraints #lectronic shipment manifesting only
Timely product pic0up .y transport carrier
7'Dendor must use a pre-approved Transport Carrier as specified .y
*etailer /ithin +usiness 7ocument details)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =B of ;;

&/A)/
&hipment,nstruction
6 Business/ransaction*B'reate .endor Purchase (rderB+.&tateC0A$ 7
&U''0&&
<A,LU)0
6 Business/ransaction*B&hipment ,nstructionB+C0A$ 7
6 Business/ransaction*B&hipment ,nstructionB+C'(A/)(L"<A,L 7
"ransport%arrier D&>endor
7i!ure 118199DD(usiness/o**aborationProtoco*EE ShipmentInstruction
7orm Id +C,T-A)<-'hipment-(nstruction
Identifier .cidFean)12>?<=AB;012BF'hipment(nstructionU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin!
Partner 1+pe
3ecei$in! Partner
1+pe
1ransition
/ondition
'T%*T 7'Dendor 'hipment(nstruction TransportCarrier !&!#
'hipment(nstruction !&T-
%,,4(C%+4#
'CC#'' !&T-%,,4(C%+4# +usinessTransaction(
6'hipment
(nstruction6)Z#!7
'hipment(nstruction !&T-
%,,4(C%+4#
$%(4*# !&T[%,,4(C%+4# +usinessTransaction(
H'hipment
(nstructionI)ZC&!T
*&4-$%(4
%#1*.*1#on&irm1s!ipment
7orm Id +C-=)=-Confirm-'hipment
Identifier .cidFean)12>?<=AB;012BFConfirm'hipmentU1)0
7'Dendor
)uthori2ed 3o*es *etailer)Customer 'ervice
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age =; of ;;
7'Dendor)(nventory -anagement
Le!a* steps@reAuirements 7'Dendor declares customer shipment to *etailer

*etailer agrees to .e .illed .y 7'Dendor for original purchase price on the
,urchase &rder %cceptance)
(for this scenario, 7'Dendor provides free shipping to customers)
.conomic conseAuences ,oint of sale .et/een 7'Dendor and *etailer)
Initia*@termina* e$ents (nitial P 7'Dendor notifies *etailer of shipment
Terminal P 7'Dendor receives Transport Carrier shipping instruction)
Scope !otification of customer shipment .y 7'Dendor)
(oundar+ 'ystems includeF
7'Dendor ,& -anagement system
7'Dendor $inancial system
7'Dendor (nventory -anagement system
*etailer ,& -anagement system
*etailer $inancial system
*etailer Customer 'ervice -anagement system
/onstraints *etailer must receive %vanced 'hipping !ote (%'!) as confirmation of product
shipment to customer in a timely fashion, and no later than ? hours of physical
product shipment from the 7'DendorEs distri.ution point)

&/A)/
'onf irm&hipment
6 Business'ollaboration*B&hipment ,nstructionB+.&tateC0A$ 7
&U''0&&
<A,LU)0
6 Business/ransaction*B'onfirm&hipmentB+.&tateC
0A$ 7
6 Business/ransaction*B'onf irm&hipmentB+.&tateC'(A/)(L"<A,L 7
D&>endor -etailer
7i!ure 118209 DD(usiness/o**aborationProtoco*EE /onfirmShipment
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A0 of ;;
7orm Id +C,T-A)=-Confirm-'hipment
Identifier .cidFean)12>?<=AB;012BFConfirm'hipmentU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer Confirm'hipment 7'Dendor !&!#
Confirm'hipment !&T-
%,,4(C%+4#
'CC#'' !&T-
%,,4(C%+4#
+usinessTransaction(HCon
firm'hipmentI))'tateZ#!
7
Confirm'hipment !&T-
%,,4(C%+4#
$%(4*# !&T-
%,,4(C%+4#
+usinessTransaction(HCon
firm'hipmentI))'tateZC&
!T*&4-$%(4
%#1*.+13endor1inventory1reportin"
7orm Id +C-=)A-Dendor-(nventory-*eporting
Identifier .cidFean)12>?<=AB;012BFDendor(nventory*eportingU1)0
7'Dendor
)uthori2ed 3o*es *etailer)*e5uestor
7'Dendor)*eporter
Initia*@termina* e$ents (nitial P (nventory physically e1ists
Terminal P *etailer receives inventory position report)
Scope The 7'Dendor is reporting a latest stage of %vaila.le to ,romise .ut ma0es no
/arranty that /hen the *etailer places a ,&, there /ill .e availa.le product to
cover the ,&) *ather forecasting should .e used to cover at least sufficient safety
stoc0)
*etailer inventory management systems
7'Dendor inventory " sales management systems
/onstraints 7aily reporting .y 7'Dendor) &nly affected products, as a result of the Catalog
#1change process are to .e reported .y the 7'DendorO and no other products are
to .e included) 7'Dendor reports product availa.ility .y num.er of 'LEs,
versus a gross classification of Yavaila.le or not availa.leE)

&/A)/
&U''0&&
<A,LU)0
.endor,n!entory)eport
6 Business/ransaction*B.endor,n!entory)eportB+.&tateC0A$
7
6 Business/ransaction*B.endor,n!entory)eportB+.&tateC'(A/)(L"<A,L0$
7
D&>endor -etailer
7i!ure 118219 DD(usiness/o**aborationProtoco*EE 5endorIn$entor+3eportin!
7orm Id +C,T-A)A-Dendor-(nventory-*eporting
Identifier .cidFean)12>?<=AB;012BFDendor(nventory*eportingU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer Dendor(nventory*
eport
7'Dendor !&!#
Dendor(nventory*
eport
!&T-
%,,4(C%+4#
'CC#'' !&T-
%,,4(C%+4#
+usinessTransaction(H(nv
entory*eportI))'tateZ#!
7
Dendor(nventory*
eport
!&T-
%,,4(C%+4#
$%(4*# !&T-
%,,4(C%+4#
+usinessTransaction(H(nv
entory*eportI))'tateZC&
!T*&4-$%(4#7
%#1*.,1Request1inventory1report
7orm Id +C-=)B-*e5uest-(nventory-*eport
Identifier .cidFean)12>?<=AB;012BF*e5uest(nventory*eportU1)0
7'Dendor
)uthori2ed 3o*es *etailer)(nventory -anagement
7'Dendor)(nventory " Customer 'ervice -anagement
Initia*@termina* e$ents 'ee +C-=)A-Dendor-(nventory--anagement
Scope 'ee +C-=)A-Dendor-(nventory--anagement
(oundar+ 'ee +C-=)A-Dendor-(nventory--anagement
/onstraints 'ee +C-=)A-Dendor-(nventory--anagement

&/A)/
&U''0&&
<A,LU)0
)e-uest,n!entory)epor
t
6 Business/ransaction*B)e-uest,n!entory)eportB+.&tateC0A$
7
6 Business/ransaction*B)e-uest,n!entory)eportB+.&tateC'(A/)(L"
<A,L 7
D&>endor -etailer
7i!ure 118229 DD(usiness/o**aborationProtoco*EE 3eAuestIn$entor+3eport
7orm Id +C,T-A)B-*e5uest-(nventory-*eport
Identifier .cidFean)12>?<=AB;012BF*e5uest(nventory*eportU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T *etailer *e5uest(nventory
*eport
7'Dendor !&!#
*e5uest(nventory
*eport
!&T-
%,,4(C%+4#
'CC#'' !&T-
%,,4(C%+4#
+usinessTransaction(H*e5
uest(nventory*eportI))'tat
eZ#!7
*e5uest(nventory
*eport
!&T-
%,,4(C%+4#
$%(4*# !&T-
%,,4(C%+4#
+usinessTransaction(H*e5
uest(nventory*eportI))'tat
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A> of ;;
eZC&!T*&4-$%(4
%#1*.-1Sales1product1o&&erin"
7orm Id +C-=);-'ales-,roduct-&ffering
Identifier .cidFean)12>?<=AB;012BF'ales,roduct&fferingU1)0
*etailer
)uthori2ed 3o*es *etailer)-erchandising
7'Dendor)'ales
Le!a* steps@reAuirements 7'Dendor /arrants that products offered for consumer sale are valid and legal)
.conomic conseAuences !one, unless prior .usiness agreements of minimum sales 5uantities are
applica.le)
Initia*@termina* e$ents (nitial P 7'Dendor sends *etailer valid product specifications
Terminal P *etailer receives valid product specifications)
Scope %t start of a relationship, the 7'Dendor /ill offer a full list of all products that
may .e offered for consumer sale .y the *etailer)
7'Dendor inventory management systems
*etailer inventory management systems
/onstraints &nly products intended for consumer resale are offered .y the 7'Dendor to the
*etailer) (i)e) !o spamming the *etailer))
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A? of ;;

6 Business/ransaction*BProduct(fferingB+.&tateC'(A/)(L"<A,L 7
&/A)/
&U''0&&
<A,LU)0
Product(ff ering
6 Business/ransaction*BProduct(fferingB+.&tateC0A$ 7
-etailer D&>endor
7i!ure 118239 DD(usiness/o**aborationProtoco*EE Sa*esProduct"fferin!
7orm Id +C,T-A);-'ales-,roduct-&ffering
Identifier .cidFean)12>?<=AB;012BF'ales,roduct&fferingU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in!
Partner 1+pe
'T%*T 7'Dendor ,roduct&ffering *etailer !&!#
,roduct&ffering !&T-
%,,4(C%+4#
'CC#'' !&T-
%,,4(C%+4#
+usinessTransaction(H,ro
duct&fferingI))'tateZ#!7
,roduct&ffering !&T-
%,,4(C%+4#
$%(4*# !&T-
%,,4(C%+4#
+usinessTransaction(H,ro
duct&fferingI))'tateZC&
!T*&4-$%(4
%#1*.1.17nvoice1presentment
7orm Id +C-=)10-(nvoice-,resentment
Identifier .cidFean)12>?<=AB;012BF(nvoice,resentmentU1)0
*etailer
)uthori2ed 3o*es *etailer),rocess,ayment
7'Dendor),rocess,ayment
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A< of ;;
Le!a* steps@reAuirements
.conomic conseAuences
Initia*@termina* e$ents
Scope
(oundar+
/onstraints

&/A)/
&U''0&&
<A,LU)0
Present,n!oice
::Business/ransactionActi!ity;
;
6 Business/ransaction*BPresent,n!oiceB+.&tateC0A$ 7
6 Business/ransaction*BPresent,n!oiceB+.&tateC'(A/)(L"<A,L 7
-etailer D&>endo
r
7i!ure 11829DD(usiness/o**aborationProtoco*EE In$oicePresentment
7orm Id +C,T-A)10-(nvoice-,resentment
Identifier .cidFean)12>?<=AB;012BF(nvoice,resentmentU1)0
7rom (usiness
)cti$it+
;1ransaction<
Initiatin! Partner
1+pe
3ecei$in! Partner
1+pe
'T%*T 7'Dendor ,resent (nvoice *etailer !&!#
,resent (nvoice 7'Dendor 'CC#'' !&T-
%,,4(C%+4#
+usinessTransaction(H,res
ent(nvoiceI))'tateZ#!7
,resent (nvoice 7'Dendor $%(4*# !&T-
%,,4(C%+4#
+usinessTransaction(H,res
ent(nvoiceI))'tateZC&!T
*&4-$%(4
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A= of ;;
%usiness transactions and aut!ori8ed roles
%1,.112irm1customer1sales1order
7orm Id +T-B)1-$irm-Customer-'ales-&rder
Identifier .tidFean)12>?<=AB;012BF$irmCustomer'ales&rderU1)0
Description *egister customer demand for specific product to .e fulfilled)
Pattern +usiness Transaction
/onstraints Dalid Customer
Dalid ,roduct
Dalid Dendor
3eAuestin! Partner 1+pe Customer
3eAuestin! )cti$it+ 3o*e +uying Customer
3eAuestin! )cti$it+
Document
'ales &rder
3espondin! Partner 1+pe *etailer
3espondin! )cti$it+ 3o*e Customer 'ervice
3espondin! )cti$it+
Document
Confirmation email
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age AA of ;;

'(A/)(L"<A,L0$
&/A)/
$ata 0ntry
::'ommercial/ransactionActi! ity ;;
&ales (rder D
EttpPost
0A$ Process &ales
(rder
'onf irmation
D 0mail
6 &ales(rder.&tatusCA''0P/0$ 7
6 &ales(rder.&tatusC)0F0'/0$ 7
%usto#er&ervice.-esponding-ole Buying%usto#er.-e@uesting-ole
7i!ure 1182%9 DD(usiness1ransactionEE 7irm/ustomerSa*es"rder
%1,.21#!ec( customer credit
7orm Id +T-B)2-Chec0 Customer Credit
Identifier .tidFean)12>?<=AB;012BFChec0CustomerCreditU1)0
Description 8ith complete customer details, including a total sales amount, chec0 the
customerEs credit a.ility to eventually pay for product once drop shipped from
the vendor)
Pattern *e5uest"*esponse
'ee +TTT-B)2- Chec0-Customer-Credit
/onstraints Dalid .usiness agreement /ith vendor
Dalid customer details
3eAuestin! Partner 1+pe *etailer
3eAuestin! )cti$it+ 3o*e Customer 'ervice
3eAuestin! )cti$it+
Document
Credit Chec0 (typically a proprietary document)
3espondin! Partner 1+pe Credit %uthority
3espondin! )cti$it+ 3o*e Credit 'ervice
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age AB of ;;
3espondin! )cti$it+
Document
Credit Chec0 *esponse
7orm Id +TTT-B)2- Chec0-Customer-Credit
'T%*T !&T-
%,,4(C%+4#
!&!# *e5uest Chec0
Credit
*etailer)Custom
er'ervice
!&!#
*e5uest Chec0
Credit
*etailer)Custom
er'ervice
Credit Chec0
*e5uest
,rocess Credit
Chec0
Credit%uthority
)Credit'ervice
!&!#
,rocess Credit
Chec0
Credit%uthority
)Credit'ervice
Credit Chec0
*esponse
*e5uest Chec0
Credit
*etailer)Custom
er'ervice
!&!#
*e5uest Chec0
Credit
*etailer)Custom
er'ervice
!&!# #!7 !&T-
%,,4(C%+4#
CreditChec0*esponse)'
tatusZ9&&7-C*#7(T
*e5uest Chec0
Credit
*etailer)Custom
er'ervice
!&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4#
CreditChec0*esponse)'
tatusZ+%7-C*#7(T
%1,.31#!ar"e1customer1credit
7orm Id +T-B)>-Charge-Customer-Credit
Identifier .tidFean)12>?<=AB;012BFChargeCustomerCreditU1)0
Description 9iven all customer details, plus total sales amount .ased on product actually
shipped .y 7'Dendor, do a charge on the customerEs credit)
'ee +TTT-B)>-Charge-Customer-Credit
/onstraints Dalid sales order
Confirmed 'hipped product
Partner 1+pe
*etailer
)cti$it+ 3o*e
%ccounts *eceiva.le
Document
Charge Credit *e5uest
3espondin! Partner 1+pe Credit %uthority
3espondin! )cti$it+ 3o*e Credit %uthority 'ervice
3espondin! Document Charge Credit *esponse
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age A; of ;;
7orm Id +TTT-B)>-Charge-Customer-Credit
'T%*T !"% !"% *e5uestCre
ditCharge
*etail)ChargeCre
dit
!&!#
*e5uestCreditC
harge
*etail)Charge
Credit
ChargeCredit ,rocessCre
ditCharge
Credit%uthority)
Credit'ervice
!&!#
,rocessCreditC
harge
Credit%uthorit
y)Credit'ervic
e
ConfirmCred
it
*e5uestCre
ditCharge
*etail)ChargeCre
dit
!&!#
*e5uestCreditC
harge
*etail)Charge
Credit
!"% #!7 !"% -essage(ConfirmCredit))
'tatus Z*#C#(D#7
*e5uestCreditC
harge
*etail)Charge
Credit
!"% C&!T*&4
-$%(4#7
!"% -essage(ConfirmCredit))
'tatus Z!&T-*#C#(D#7
%1,.41#reate1vendor1purc!ase1order
7orm Id +T-B)?-Create-Dendor-,urchase-&rder
Description 9iven a multi-vendor " single product relationship, *etailer needs to send a
7'Dendor a ,urchase &rder *#N#'T, /hich /ill need to .e responded .ac0
(/ith confirmed allocated product to cover the ,&) .y the 7'Dendor)
'ee +TTT-B)?-Create-Dendor-,urchase-&rder
/onstraints Dalid 'ales order
Dalid customer credit chec0
3eAuestin! )cti$it+ 3o*e (nventory +uyer
3eAuestin! )cti$it+
Document
,urchase &rder *e5uest
3espondin! Partner 1+pe 7'Dendor
3espondin! )cti$it+ 3o*e 'eller
3espondin! )cti$it+
Document
,urchase &rder %c0no/ledgement
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B0 of ;;

&/A)/
'reate Purchase (rder
::'ommercial/ransactionActi!ity;;
Purchase (rder
)e-uest
0A$
'(A/)(L"<A,L0$
Process
Purchase (rder
<irm Purchase (rder
Acknowledgment
6 (rder.&tatus:;)0F0'/0$ 7
6 (rder.&tatusC)0F0'/0$ 7
%usto#er&ervice.-esponding-ole (nventoryBuyer.-e@uesting-ole
7i!ure 1182-9 DD(usiness1ransactionEE Purchase"rder3eAuest
7orm Id +TTT-B)?-Create-Dendor-,urchase-&rder
7rom
)cti$it+
7rom 3o*e Document 1o )cti$it+ 1o 3o*e >uard /ondition
'T%*T !"% !"% Create
,urchase
&rder
(nventory+uyer !&!#
Create
,urchase
&rder
(nventory+uyer ,urchase &rder
*e5uest
,rocess
,urchase
&rder
Customer'ervice !&!#
,rocess
,urchase
&rder
Customer'ervice $irm ,urchase
&rder
%c0no/ledgement
Create
,urchase
&rder
(nventory+uyer !&!#
Create
,urchase
&rder
(nventory+uyer !"% #!7 !"% &rder)'tatusRS*#J#
CT#7
Create
,urchase
&rder
(nventory+uyer !"% C&!T*&4-
$%(4#7
!"% &rder)'tatusZ*#J#C
T#7
%1,.$13endor1inventory1report
7orm Id +T-B)<-Dendor-(nventory-*eport
Identifier .tidFean)12>?<=AB;012BFDendor(nventory*eportU1)0
Description *egular periodic notification, unsolicited, from the 7'Dendor to the *etailer,
containing %vaila.le to ,romise &n-2and inventory)
Pattern !otification
'ee +TTT-B)<-Dendor-(nventory-*eport
/onstraints &nly send product inventory /hich has .een agreed to .e made consumer
availa.le per agreement from the ,roduct Catalog #1change negotiation pattern)
Partner 1+pe
7'Dendor
)cti$it+ 3o*e
(nventory +uyer
)cti$it+ Document
(nventory *eport
3espondin! )cti$it+ 3o*e (nventory +uyer
3espondin! )cti$it+
Document

&/A)/
0A$
'(A/)(L"<A,L
)eport ,n!entory
::AotificationActi!ity;;
,n!entory
)eport
Process ,n!entory
)eport
6 Message*B,n!entory )eportB+.&tateC)0',0.0$ 7
6 *Message*B,n!entory )eportB+.&tate:;)0',0.0$+ ()
*,n!entory)eport.,tem*+.Guantity : Agreement.,tem*+.&afety&tockLe!el+ 7
(nventoryBuyer.-esponsidng-ole %usto#er&ervice.-e@uesting-ole
7i!ure 118279 DD(usiness1ransactionEE 5endorIn$entor+3eport
7orm Id +TTT-B)<-Dendor-(nventory-*eport
'T%*T !&T-
%,,4(C%+4
#
!&!# *eport
(nventory
7'Dendor)Cu
stomer'ervice
!&!#
*eport
(nventory
7'Dendor)Cu
stomer'ervice
(nventory
*eport
,rocess
(nventory
*eport
*etailer)(nvent
ory+uyer
!&!#
*eport
(nventory
7'Dendor)Cu
stomer'ervice
!&!# #!7 !"% -essage(H(nventory
*eportI))'tateZ*#C(#D
#7
*eport
(nventory
7'Dendor)Cu
stomer'ervice
!&!# C&!T*&4-
$%(4#7
!"% -essage(H(nventory
*eportI))'tateRS*#C#(
D#7 &*
(nventory*eport))(tem())
NuatntityR%greement)(te
m())'aftey'toc04evel
%1,.*1Request1inventory1report
7orm Id +T-B)=-*e5uest-(nventory-*eport
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B> of ;;
Identifier .tidFean)12>?<=AB;012BF*e5uest(nventory*eportU1)0
Description Nuery *esponse dialogue /here the *etailer re5uests the 7'Dendor for the
current %vaiala.le to ,romise position of a productO or series of products)
Pattern Nuery " *esponse (per -- pattern specirfications)
'ee +TTT-B)=-*e5uest-(nventory-*eport
/onstraints 'ee +T-B)<-Dendor-(nventory-*eport
3eAuestin! )cti$it+ 3o*e (nventory +uyer
3eAuestin! )cti$it+
Document
&n-hand %vaila.le to ,romise ,roduct %vaila.ility *e5uest
3espondin! Partner 1+pe 7'Dendor
3espondin! )cti$it+
Document
on-hand %vaila.le to ,romise report

,n! entory ,nf ormation
Guery )esponse
&/A)/
Guery .endor,n! entory
::Guery )esponseActi! ity ;;
0A$
6 Message*,n! entory,nf ormationGuery)esponse+.&tatus
C)0'0,.0$ 7
'(A/)(L"<A,L0$
6 Message*,n! entory,nf ormationGuery)esponse+.&tatusCA(/")0'0,.0$ 7
,n! entory ,nf ormation
Guery
Process ,n! entory
,nf ormation Guery
%usto#er&ervice.-esponding-ole (nventoryBuyer.-e@uesting-ole
7i!ure 118289 DD(usiness1ransactionEE 3eAuestIn$entor+3eport
7orm Id +TTT-B)=-*e5uest-(nventory-*eport
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B? of ;;
'T%*T !"% !"% NueryDendor(
nventory
(nventory+uyer !&!#
NueryDendor(
nventory
(nventory+uyer (nventory
(nformatio
n Nuery
,rocess
(nventory
(nformation
Nuery
Customer'ervice !&!#
,rocess
(nventory
(nformation
Nuery
Customer'ervice (nventory
(nformatio
n Nuery
*esponse
NueryDendor(
nventory
(nventory+uyer !&!#
NueryDendor(
nventory
(nventory+uyer !"% #!7 !"% -essage((nventory(n
formationNuery*esp
onse))'tatus
Z*#C#(D#7
NueryDendor(
nventory
(nventory+uyer !"% C&!T*&4-
$%(4#7
!"% -essage((nventory(n
formationNuery*esp
onse))'tatus Z!&T-
*#C#(D#7
%1,.+1S!ipment1noti&ication
7orm Id +T-B)A-'hipment-!otification
Description %rrangement of carriage .y the 7'Dendor to/ards a Transport CarrierO /ho is
e1pected to physically ship the product direct to the Customer)
'ee +TTT-B)A-'hipment-!otification
/onstraints Customer 'hip To details must .e accurate
3eAuestin! Partner 1+pe 7'Dendor
3eAuestin! )cti$it+ 3o*e 'hipper
3eAuestin! )cti$it+
Document
'hipment (nstruction (!"C#$%CT #7($%CT ($T-(! 701)
3espondin! Partner 1+pe Transport Carrier
3espondin! )cti$it+
Document
#lectronic copy of a +ill of 4ading (!"C#$%CT #7($%CT ($T-C' 701)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B< of ;;

'(A/)(L"<A,L0$
&/A)/
'reate &hipment ,nstruction
::Business/ransactionActi! ity ;;
&hipment
,nstruction
0A$ Process &hipment
,nstruction
Bill (f
Lading
6 &hipment,nstruction.&tatusCA''0P/0$ 7
6 */ransportManif est.&tatusC,A.AL,$"&E,P"/(+ () *Message*B&hipment
,nstructionB+.&tatusCA(/"A'HA(2L0$@0$ 7
%arrier.-esponding-ole &hipper.-e@uesting-ol
e
7i!ure 118299 DD(usiness1ransactionEE ShipmentInstruction
7orm Id +TTT-B)A-'hipment-!otification
'T%*T !&T-
%,,4(C%+4#
!&!# ,repare
'hipping
(nstruction
7'Dendor)'hip
per
!&!#
,repare
'hipping
(nstruction
7'Dendor)'hip
per
'hipment
(nstruction
,rocess
'hipment
(nstruction
TransportCarrie
r)Customer'ervi
ce
!&!#
,rocess
'hipment
(nstruction
TransportCarrie
r)Customer'ervi
ce
+ill &f
4ading
,rocess
'hipment
(nstruction
7'Dendor)'hip
per
!&!#
,rocess
'hipment
(nstruction
7'Dendor)'hip
per
!&!# #!7 !&T-
%,,4(C%+4#
-essage(H+ill &f
4adingI))'tateZ*#C(#
D#7
,rocess
'hipment
(nstruction
7'Dendor)'hip
per
!&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4#
-essage(H+ill &f
4adingI))'tateRS*#C#
(D#7
11
%1,.,1#on&irm1s!ipment
7orm Id +T-B)B-Confirm-'hipment
88
$&.endor.&hipper may get an emial or phone calls stating that the goods will not be shipped.
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B= of ;;
Description 7'Dendor informs the *etailer that the CustomerEs product has .een shipped to
the CustomerO and thus the conditions of the ,& have .een fulfilled)
'ee +TTT-B)B-Confirm-'hipment
/onstraints ,roduct must actually .e shipped
7'Dendor must return a Transport Carrier trac0ing num.erO for customer
service)
3eAuestin! )cti$it+ 3o*e 'hipper
3eAuestin! )cti$it+
Document
%dvance 'hip !otice (!"C#$%CT #7($%CT 7#'%7D 701)
3espondin! )cti$it+
Document
!&!#

&/A)/
'onf irmation of Pickup
::Aotif icationActi!ity ;;
Ad! ance &hip
Aotice
0A$
'(A/)(L"<A,L0$
Process Ad! ance &hip
Aotice
6 Message*BAd! ance&hipAoticeB+.&tatusC
$0L,.0)0$ 7
6 Message*BAd! ance&hipAoticeB+.&tatus:;$0L,.0)0$ 7
%usto#er&ervice.-esponding-ol
e
&hipper.-e@uesting-ol
e
7i!ure 118309 DD(usiness1ransactionEE /onfirmShipment
7orm Id +TTT-B)B-Confirm-'hipment
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age BA of ;;
7rom
)cti$it+
7rom 3o*e Document 1o )cti$it+ 1o 3o*e >uard /ondition
'T%*T !&T-
%,,4(C%+4#
!&!# Confirmation
of ,ic0up
'hipper !&!#
Confirmation
of ,ic0up
'hipper %dvance
'hip !otice
,rocess
%dvance 'hip
!otice
*etailer)Custome
r'ervice
!&!#
Confirmation
of ,ic0up
'hipper !&!# #!7 !&T-
%,,4(C%+4#
-essage(H%dvance 'hip
!oticeI))'tateZ*#C#(D
#7
Confirmation
of ,ic0up
'hipper !&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4#
-essage(H%dvance 'hip
!oticeI))'tateRS*#C#(
D#7
%1,.-14roduct1o&&erin"
7orm Id +T-B);-,roduct-&ffering
Identifier .tidFean)12>?<=AB;012BF,roduct&fferingU1)0
Description 7'Dendor offers product details to the *etailer, /here the *etailer is e1pected to
either accept the 7'DendorEs product for consumer sale or re@ect the productO
perhaps .ecause of unaccepta.le product terms and conditions)
Pattern *e5uest " Confirm
'ee +TTT-B);-,roduct-&ffering
/onstraints Dalid products for consumer sale .y *etailer
3eAuestin! )cti$it+ 3o*e Catalog ,u.lishing
3eAuestin! )cti$it+
Document
,roduct Catalog &ffering (%!'( 3)12 B>2 ?010 version)
3espondin! )cti$it+ 3o*e -erchandising
3espondin! )cti$it+
Document
,roduct Catalog %cceptance (often proprietary format response document)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age BB of ;;

&/A)/
&ubmit Product 'atalog
(ff ering
::)e-uest'onf irmActi! ity ;;
0A$
6 Product'atalogAcceptance.&tatusC
A''0P/0$"A&",& 7
'(A/)(L"<A,L0$
6 Product'atalogAcceptance.&tatusC )0F0'/0$ 7
Product
'atalog
Process Product
'atalog
Product 'atalog
Acceptance
-etailer.-esponding-ole %atlogPublishing.-e@uesting-ole
7i!ure 118319 DD(usiness1ransactionEE Product"fferin!
7orm Id +TTT-B);-,roduct-&ffering
'T%*T !&T-
%,,4(C%+4
#
!&!# 'u.mit
,roduct
Catalog
&ffering
Catalog,u.lis
hing
!&!#
'u.mit
,roduct
Catalog
&ffering
Catalog,u.lis
hing
,roduct
Catalog
,rocess
,roduct
Catalog
*etailer)-erch
andising
!&!#
,rocess
,roduct
Catalog
*etailer)-erch
andising
,roduct
Catalog
%cceptance
'u.mit
,roduct
Catalog
&ffering
Catalog,u.lis
hing
!&!#
'u.mit
,roduct
Catalog
&ffering
Catalog,u.lis
hing
!&!# #!7 !&T-
%,,4(C%+4
#
,roductCatalog%cceptan
ce)'tatusZ%CC#,T#7-
%'-('
'u.mit
,roduct
Catalog
&ffering
Catalog,u.lis
hing
!&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4
#
,roductCatalog%cceptan
ce)'tatusZ*#J#CT#7
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age B; of ;;
%1,.1.14resent1invoice
7orm Id +T-B)10-,resent-(nvoice
Identifier .tidFean)12>?<=AB;012BF,resent(nvoiceU1)0
Description This is the vendorEs invoice to the retailer for products and services shipped to
customer)
'ee +TTT-B)10-,resent-(nvoice
/onstraints The invoice shall only .e sent after confirmed shipment
The invoice shall reflect the confirmed shipment
3eAuestin! )cti$it+ 3o*e ,ayee
3eAuestin! )cti$it+
Document
(nvoice
3espondin! )cti$it+ 3o*e ,ayor
3espondin! )cti$it+
Document
!&!#

&/A)/
Present,n!oice
::AotificationActi!it y;;
,n!oice
0A$
'(A/)(L"<A,L
Process
,n!oice
6 Message*B,n!oiceB+.&t ateC)0',0.0$ 7
6 *Message*B,n!oiceB+. &tat e:;A(/")0',0.0$+ ()
*/hree2ayMatch*, n!oice+. &tateC.AL,$+ 7
Payor Payee
7i!ure 118329 DD(usiness1ransactionEE PresentIn$oice
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;0 of ;;
7orm Id +TTT-B)10-,resent-(nvoice
'T%*T !&T-
%,,4(C%+4
#
!&!# ,resent
(nvoice
,ayee !&!#
,resent
(nvoice
,ayee (nvoice ,rocess
(nvoice
,ayor !&!#
,resent
(nvoice
,ayee !&!# #!7 !&T-
%,,4(C%+4
#
-essage(H(nvoiceI))'t
ateZ*#C#(D#7
,resent
(nvoice
,ayee !&!# C&!T*&4-
$%(4#7
!&T-
%,,4(C%+4
#
-essage(H(nvoiceI))'t
ateRS*#C#(D#7 &*
Three8ay-atach((nv
oice))'tateZD%4(7
%usiness in&ormation description
4urc!ase order
Purchase order business information conte>t
7orm9 (usiness Information /onte6t
7orm Id9 +(C-10)1-,urchase-&rder
Industr+ Se!ment *etail
(usiness Process +,C-<)?-,urchase-&rder--anagement
+C-B)?-Create-Dendor-,urchase-&rder
+T-B)?-Create-Dendor-,urchase-&rder
Product !&T-%,,4(C%+4#
Ph+sica* >eo!raph+ @/onditions
@3e!ion
!orth %merica
>eo8Po*itica* Le!is*ati$e@
3e!u*ator+@ /u*tura*
!&T-%,,4(C%+4#
)pp*ication Processin! !&T-%,,4(C%+4#
(usiness Purpose @Domain 'ee +,C-<)?-,urchase-&rder--anagement
Partner 3o*e (nventory +uyer
Customer 'ervice
Ser$ice Le$e* ;profi*es B not
preferences.<
!&T-%,,4(C%+4#
/ontracts@)!reements H-y +usiness %greement 8ith -y DendorI
'$"5.8"(rder
7orm
Id9
C7-;)1-&rder
1+pe
7ie*d
&idth
&rder 2eader 1 !"% The &rder 2eader contains the header
information of the order
&rder 7etail 0))1 !"% The &rder 7etail contains the line item and
pac0age details of the &rder)
&rder 'ummary 0))1 !"% The &rder 'ummary contains the summary
information of the order, typically totals of
numerical fields
'$"I.I"(rder"summary
7orm
Id9
C7-;)2-&rder-'ummary
1+pe
7ie*d
&idth
!um.er &f 4ines 0))1 (nteger !um.er &f 4ines identifies the num.er of
line items)
Total Ta1 0))1 -onetar
y Dalue
!"% Total Ta1 contains the total ta1 amount for
the &rder)
Total %mount 0))1 -onetar
y Dalue
!"% Total %mount contains the total price for the
entire &rder)
Transport ,ac0aging Totals 0))1 Transport ,ac0aging Totals is a summary of
transport and pac0aging information if
included in the &rder)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;> of ;;
Copyright e.3-4 2001) %ll *ights *eserved)
'ummary !ote 0))1 'tring 'ummary !ote contains any free form te1t
for the &rder 'ummary) This element may
contain notes or any other similar
information that is not contained e1plicitly
in the another structure) :ou should not
assume that the receiving application is
capa.le of doing more than storing and"or
displaying this information
#ontent mappin"
7ote (f /e feel so am.itious, /e can use the %!'( 312 ?010 mappings availa.le at httpF""///)1c.l)org"1c.l>0"-apping"smg)html
These forms '2&47 .e completed) This information is very important as it sho/s that the documents have a .asis in e1isting
standards) $urthermore, the information /ill .e used to create document transformations) 'tandards to map to include #7($%CT,
312, 1C+4, *osetta!et, and other standards such as &+() se 3,%T2 and 3'4T notation for referencing 3-4 elements and
descri.ing the mappings) (f a ne/ document schema is created to fulfil the content re5uirements specified in the 7ocument Content
7escription forms, then a set of Content -apping forms should .e completed for that schema (the component names in the forms are
simply re5uirements for information)
$or each Content 7escription form, complete a 7ocument Content -apping form for each standard to .e cross-referenced)
'M"88.8"(rder"summary
7orm9 /ontent Mappin!
7orm Id9 C--11)1-&rder-'ummary
/ontent Description 7orm Id C7-11)1-&rder-'ummary
Standard %!'( 312 B<0
5ersion ?010
.*ement@/omponent 4ame Mappin!@1ransformation 4ote
!um.er &f 4ines B<0F'FCTTF010FCTTF01F><?F
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;? of ;;
Total Ta1 !&T '#7
Total %mount Darious (B<0F'FCTTF020F%-TF02FAB2F, etc)) Total amount is a comple1 structure that includes
things li0e reference currency, target currency,
and rate of e1change) $or an e1ample mapping
see 1C+4)org)) 7o mapping in a separate ta.le)
Transport ,ac0aging Totals Darious Transport pac0ing totals is a comple1 structure)
7o mapping in a separate ta.le)
'ummary !ote B<0F'FCTTF010FCTTF02F>?AF
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;< of ;;
) Disclai#er
The vie/s and specification e1pressed in this document are those of the authors and are not
necessarily those of their employers) The authors and their employers specifically disclaim
responsi.ility for any pro.lems arising from correct or incorrect implementation or use of this
design)
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;= of ;;
1 %ontact (nfor#ation
%usiness 4rocess 4roject eam
Core Components"+usiness ,rocess (CC"+,) %nalysis Team 4ead
!ameF +rian 2ayes
CompanyF Commerce &ne
'treetF ???0 *ose/ood 7rive
City, 'tate, \(,"&therF ,leasanton, C%
!ationF '%
,honeF ]1 (;2<) ABB-=>0?
#-ailF .rian)hayes^C4%lumni)net
#ditors
!ameF Charles $ineman
CompanyF %rGoon
'treetF 1;<0 #l0horn Court
City, 'tate, \(,"&therF 'an -ateo, C% ;??0>
,honeF ]1 (=<0) ><A-=0<2
#-ailF fineman^arGoon
!ameF +rian 2ayes
CompanyF Commerce &ne
'treetF ???0 *ose/ood 7rive
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;A of ;;
City, 'tate, \(,"&therF ,leasanton, C%
!ationF '%
,honeF ]1 (;2<) ABB-=>0?
#-ailF .rian)hayes^C4%lumni)net
!ameF Jennifer 4overidge
CompanyF !ordstrom)com
'treetF =00 niversity 'treet, 'te) =00
City, 'tate, \(,"&therF 'eattle, 8%
!ationF '%
,honeF
#-ailF Jennifer)4overidge^!ordstrom)com
!ameF 8illiam #) -cCarthy
niversityF -ichigan 'tate niversity
'treetF !2A0 !orth +usiness Comple1
City, 'tate, \(,"&therF #ast 4ansing, -(
!ationF '%
,honeF ]1 (<1A) ?>2-2;1>
#-ailF mccarth?^msu)edu
!ameF 7avid 8elsh
CompanyF !ordstrom)com
'treetF =00 niversity 'treet, 'te) =00
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;B of ;;
City, 'tate, \(,"&therF 'eattle, 8%
!ationF '%
,honeF ]1 (20=) 21<-A2;>
#-ailF 7avid)8elsh^!ordstrom)com
+usiness ,rocess %nalysis 8or0sheets and 9uidelines ,age ;; of ;;

BPWS Print

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BPWS Print

Încărcat de

Drepturi de autor:

Formate disponibile

Business Process Analysis Worksheets

.conomic conseAuences *etailer receives payment

Le!a* steps@reAuirements 7'Dendor declares customer shipment to *etailer

S-ar putea să vă placă și