Semantic Annotation for Process Models: - Department of Computer ...

204 APPENDIX F. ANALYSIS OF EXEMPLAR STUDIES
some cases. For the example of "Create delivery", the goal algorithm deduces two
hard goals Delivery Date is Determined with weight ’1.0’ and Delivery Date is
Determined with weight ’0.06’. Delivery Date is Determined is not selected because
of low weight. Delivery is Processed is further checked in the goal ontology
and its parts Delivery is Scheduled and Delivery Terms are Generated are considered
more precise than Delivery is Processed in the goal annotation of "Create
delivery". Nine soft goals are also returned but only two goals with weight ’1.8’ (Ensure
Full Delivery and Ensure Full Shipment) are selected by an annotator.
In PM B1 , "get the order to supplier" can be regarded as a phase of the activity
ontology Schedule Product Deliveries from SCOR. Because there are three kinds
of items receiving, they are respectively checked in sub-Activities of the activity "check
items". Therefore, three sub-Activities all achieves Sourced Product are Verified.
The procedure of "check imported items" is a little more complicated compared with
the other two kinds of items receiving because it includes issuing deficit protocols and
an invoice to insurance company. "Check imported items" are depicted with a serial of
sub-Activities such as "issue the deficit protocol", "issue an invoice to insurance company",
etc. Those negatively satisfy the soft goal Reduce Verification Costs. The
consignment can simplify the check and item receiving procedure, so it positively satisfies
Reduce Verification Costs. Issuing invoices are steps of "Authorize Supplier
Payment", and "issue an export invoice" are to authorize payment to suppliers. The
soft goal of Process Invoice Without Error will be risked by the invoice issue procedures.
In the context of the TelCo use case, "store items to Orbit" is the way of
Transfer Product and the result of the procedure is an Available Inventory.
PM A starts the process from the order inquiry from the client, whilst PM B2 begins
with the existing orders but the orders are managed and edited during the delivery
process. It is hereby observed that the sequence of the Activities of PM B2 does not
comply with the sequence of the SCOR DELIVER. The first Activity "Consolidate orders"
accomplishes the same task as D1.4 Consolidate Orders. As the descriptions of
the TelCo case, the "Consolidate orders" is executed by a computational software SEN
which can Reduce Order Processing Costs and Reduce Order Processing Time.
"Check stock" in PM B2 is more general compared with "Check delivery items" and
"Check availability of delivery items" in PM A so that no specific goals are annotated to
"Check stock". Although both PM A and PM B2 have the Activity "Credit control" and
they are both phase_of D1.2 Receive Enter and Validate Order, they are not exactly
same. "Credit control" in PM A deals with the capital assets but in PM B2 it
is just kind_of ED.3 Manage Deliver Information. Delivery protocol is treated as
Delivery Terms and "Generate delivery protocol" of PM B2 is similar to "Create delivery"
of PM A . They are also the way of ED.3 Manage Deliver Information. However,
the delivery protocol in PM B2 is mainly focus on the agreed delivery date so
that Improve Deliver to Customer Delivery to Date Performance and Improve
Deliver to Customer On Time Delivery Performance are selected as the goal annotation
for "Generate delivery protocol". "Send items" serves in both "Deliver items
to franchisees" and "Deliver items to shops" and should be specified as kind_of D1.12
Ship Product if they are using different ways to ship product. The items delivered to
shops are retail product so "Deliver items to shops" is phase_of D4 Deliver Retail
Product not D1 Deliver Stocked Productas "Deliver items to franchisees". Since