The Order Fulfillment Process Model

Download Report

Transcript The Order Fulfillment Process Model

Y
A W L
Appendix A
The Order Fulfillment Process
Model
Marcello La Rosa
Stephan Clemens
Arthur ter Hofstede
a university for the
real world
R
© 2009, www.yawlfoundation.org
Y
Overview
Y
1. Process domain
2. Organizational model
3. Process nets
4. Conclusions
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
2
Process domain
Y
• Inspired by the VICS industry standard (Voluntary Interindustry Commerce Solutions: www.vics.org)
• Logistics domain: this reference model can be used by
large organizations that need to interact with suppliers
and logistics providers
• Goal: emit a purchase order and deliver the order items
to the customer
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
3
Organizational model
Y
Fictitious organization “Genko Oil company”, featuring four
departments:
– Order Management Department
– Supply Department including Warehouse
– Carrier Department
– Finance Department.
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
4
Process participants
Y
Genko Oil
CEO
Order
Management
Department
Supply
Department
Don Vito
Corleone (dvc)
Finance
Department
Carrier
Department
Head of OD
Fredo Corleone
(fc)
Head of SD
Tom Hagen (th)
Head of CD
Kay Adams (ka)
Head of FD
Virgil ‘The Turk’
Sollozzo (vs)
Assistant Head
of OD
Tom Hagen (th)
SD clerk
Carlo Rizzi (cr)
CD clerk
Peter Clemenza
(pc)
FD clerk
Captain
McCluskey (cmc)
OD clerk
Michael Corleone
(mc)
Carmine Marino
(cm)
Sal Tessio (st)
Joe Lucadello (jl)
Stefano
Clemenza (sca)
Don Carmine
Cuneo (dcc)
Jaggy Jovino (jj)
Mama Corleone
(mac)
Arturo de Ofstede
(ao)
Billy Van Arsdale
(bva)
Marcello
La Rosa (mlr)
Emilio Barzini
(eb)
Momo Barone
(mb)
Sonny Corleone
(sc)
Johnny Fontaine
(jf)
Warehouse
Vincent ManciniCorleone (vmc)
Head of
Warehouse
Connie Corleone
Rizzi (ccr)
Warehouse
clerk
Jack Woltz (jw)
Carmine Cuneo
(cc)
Joe Lucadello (jl)
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
5
Overall net
Y
Three main phases:
• Ordering
• Logistics, including:
Ordering
– Carrier Appointment
– Freight in Transit
– Freight Delivered
possible deadlock:
avoided by the
Flow Predicates
• Payment
real
Carrier
Appointment
R
Y
A W L
[order preparation
timed out]
[else]
Freight in Transit
Each (sub-)phase is captured
by a YAWL composite task.
a university
for the
© 2009,
www.yawlfoundation.org
world
[order not approved or
timed out]
[else]
Payment
Freight Delivered
6
Assumptions
Y
In order to keep the model manageable, the following
simplifying assumptions were made:
• an order does not lead to more than one shipment
• orders from different clients may be combined into a
single shipment
• a single package only occupies a fraction of a truck
and can correspond to one of a fixed number of sizes
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
7
Ordering subnet
Y
• Deals with the creation,
modification and approval
of a Purchase Order.
deferred allocation
Create Purchase
Order
• Modification and final
confirmation of the
Purchase Order can be
done within a given
timeframe (3 days).
Approve
Purchase Order
[order
approved]
Modify
Purchase Order
Confirm
Purchase Order
runtime filter:
Pile task
to single
participant
delegation
[order not
approved]
Order
Timeout
order not
confirmed
JavaFaces
custom form
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
8
Carrier Appointment subnet (fragment)
Deals with:
• preparation of Route Guide
• estimation of Trailer Usage
(within 5 days)
Automated task
Prepare Route
Guide
• Transportation Quote
[Truck-Load (TL)]
• Shipment Notice
(not shown)
real
Estimate Trailer
Usage
Prepare
Transportation
Quote
• arrangement of Delivery
and Pickup Appointments
(not shown)
a university
for the
© 2009,
www.yawlfoundation.org
world
Y
[Less than Truck-Load
(LTL)]
Carrier
Timeout
Allocation
Dynamically
strategy:
set
Timeout
Round Robin
(on starting)
by least frequency
order preparation
took too long
[Single Package (SP)]
3 types of carrier usage: TL, LTL, SP
determine different shipment costs
R
Y
A W L
9
Freight in Transit subnet
Y
Starts after the freight
has been picked up and
shipped
Issue Trackpoint
Notice
Concerned with:
• tracking the order
delivery progress
• handling client inquiries
[more
Trackpoints]
[else]
Log Trackpoint
Order Entry
MI task: one instance
for each order entry
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
Initiate Shipment
Status Inquiry
the freight is physically
delivered
Create
Acceptance
Certificate
10
Payment subnet
Y
In parallel to Freight in Transit
payment for the
shipment
Two components:
• shipment payment
– pre-paid
– non pre-paid
• freight payment
Retain
familiar
Update
Shipment
Payment Order
payment for the
freight
Issue Shipment
Invoice
[else]
[Invoice required]
[pre-paid shipments]
[else]
Issue Shipment
Remittance
Advice
Issue Shipment
Payment Order
Produce Freight
Invoice
Approve
Shipment
Payment Order
[s. order not approved]
[s. order approved]
customer notified of the payment,
customer makes the payment
Process
Shipment
Payment
Privileges:
Chain execution
of work items for
Account Manager
real
a university
for the
© 2009,
www.yawlfoundation.org
world
[payment incorrect due
to underpayment]
[payment correct]
[payment incorrect
due to overcharge]
issue Debit
Adjustment
Issue Credit
Adjustment
customer notified of the
payment, customer makes
the payment
R
Process Freight
Payment
Y
account settled
A W L
11
Freight Delivered subnet
Y
After the freight has been delivered
Allows clients to:
• request a Return
of Merchandise
• lodge a Loss or
Damage Claim
within a timeframe
(specified in the
Shipment Notice)
real
a university
for the
© 2009,
www.yawlfoundation.org
world
Lodge a request
for Return
Merchandise
Authorize Return
Merchandise
[return authorized]
[return not
authorized]
Return
Management
R
Y
A W L
Dynamically set
Timeout (on enablement)
Claims
Timeout
deadline for
return or claim
expired
Lodge Loss or
Damage Claim
Report
Authorize Loss
or Damage
Claim
[claim not
authorized]
[claim authorized]
Loss or Damage
Management
12
Conclusions
Y
• Complex process inspired by a real industry standard
• Exploits a number of advanced YAWL functionalities for
defining the process control-flow, data and resource
perspectives
• Specification files and documentation available in each
YAWL distribution, under folder ‘[YAWL Installation
folder]/misc/examples/orderfulfillment/’
real
a university
for the
© 2009,
www.yawlfoundation.org
world
R
Y
A W L
13