ESIDEL12 Shipping cycle - eurofer.org cycle... · ESIDEL – Shipping cycle 1 Shipping Cycle By...

122
ESIDEL (European Steel Industry Data Exchange Language) Shipping cycle Version 1.0 by EDIFER «XML Business Group» December 2003

Transcript of ESIDEL12 Shipping cycle - eurofer.org cycle... · ESIDEL – Shipping cycle 1 Shipping Cycle By...

ESIDEL(European Steel Industry Data Exchange Language)

Shipping cycle

Version 1.0

by EDIFER «XML Business Group»December 2003

ESIDEL – Shipping cycle

1

Shipping Cycle

By EUROFER - EDIFER working group ‘E-commerce and XML’ Creation date: 01 December 2003

Last update:

Reference: ESIDEL-2003-006(Shipping cycle v1.0).doc

Version: 1.0

ESIDEL – Shipping cycle

2

Table of contents 1. Shipping cycle definition 5 1.1. Scope........................................................................................................................................5 1.2 Processes ..................................................................................................................................6 1.3. Use case: shipping cycle .........................................................................................................7 2. Business Process Definition – Selection of goods process 8 2.1. Scope........................................................................................................................................8 2.2. Process definition.....................................................................................................................8 2.3. Principles..................................................................................................................................9 2.4. Use case: selection of goods process ....................................................................................10 2.5. Activity diagram – selection of goods process ......................................................................12 2.6. Activity diagram – Alternative selection of goods process ...................................................13 2.7. Business collaboration – Selection of goods process ............................................................14

2.7.1. Business collaboration – Selection of goods on request ....................................................14 2.7.2. Business collaboration – Selection of goods on regular basis ...........................................18

2.8. Business transactions and authorized roles – Selection of goods process .............................21 2.8.1. Business transactions and authorized roles – Goods ready for despatch request ..............21 2.8.2. Business transactions and authorized roles – Goods ready for despatch inventory...........22 2.8.3. Business transactions and authorized roles – Instruction to despatch ...............................23

3. Business Process Definition – Despatch & receiving process 24 3.1. Scope......................................................................................................................................24 3.2. Process definition...................................................................................................................25 3.3. Principles................................................................................................................................26 3.4. Use case: Despatch & receiving process: direct shipping between supplier and customer – transport service ordered by the supplier........................................27

3.4.1. Use case: Ordering transport services................................................................................28 3.4.2. Activity diagram – ordering transport services..................................................................29 3.4.3. Business collaboration – ordering transport services.........................................................30 3.4.4. Business transactions and authorized roles – Ordering transport services ........................32 3.4.5. Use case: Despatch of goods..............................................................................................33 3.4.6. Activity diagram – Despatch of goods (activity between supplier and carrier).................34 3.4.7. Business collaboration – Despatch of goods .....................................................................35 3.4.8. Business transactions and authorized roles – Despatch of goods ......................................40 3.4.8.1. Business transactions and authorized roles – Transport documents and Proof of collection .......................................................................................................................40 3.4.8.2. Business transactions and authorized roles – Despatch document ................................41 3.4.9. Use case: Goods in transit.................................................................................................42 3.4.10. Activity diagram – goods in transit (transport status)....................................................43 3.4.11. Business collaboration – goods in transit.......................................................................44 3.4.12. Business transactions and authorized roles – Goods in transit ......................................49 3.4.12.1. Business transactions and authorized roles – Transport status report........................49 3.4.12.2. Business transactions and authorized roles – Pre-arrival notification .......................50

ESIDEL – Shipping cycle

3

3.4.13. Use case: Goods delivered .............................................................................................51 3.4.14. Activity diagram – goods delivered (proof of delivery) ................................................52 3.4.15. Business collaboration – goods delivered......................................................................53 3.4.16. Business transactions and authorized roles – Goods delivered......................................57 3.4.16.1. Business transactions and authorized roles – Proof of delivery.................................57 3.4.16.2. Business transactions and authorized roles – Receiving advice ................................58

3.5. Use case: Despatch & receiving process: direct shipping between supplier and customer – transport service ordered by the customer ......................................59 3.6. Use case: despatch & receiving process: indirect shipping between supplier and customer by using a third party warehouse .......................................................61

3.6.1. Use case: Goods delivered in warehouse...........................................................................67 3.6.1.1. Activity diagram – goods delivered (proof of delivery) ................................................68 3.6.1.2. Business collaboration – goods delivered at warehouse................................................69 3.6.1.2. Business transactions and authorized roles – Inventory movement to report of received goods................................................................................................72 3.6.2. Use case: Despatch of goods warehouse - customer..........................................................73 3.6.2.1. Activity diagram – despatch of goods (inventory of despatched goods).......................74 3.6.2.2. Business collaboration – goods despatched to the customer .........................................75 3.6.2.3. Business transactions and authorized roles – Inventory report of despatched goods ...........................................................................................................77 3.6.3. Use case: Goods delivered by customer ............................................................................78

3.7. Use case: Despatch & receiving process: indirect shipping between supplier and customer by using the customer consignment stock .........................................80

3.7.1. Use case: Usage of goods...................................................................................................83 3.7.2.1. Activity diagram - Usage of the goods of the consignment stock .................................84 3.7.2.2. Business collaboration – Inventory of outgoing goods..................................................85 3.7.2.4. Business transactions and authorized roles – Inventory movement of outgoing goods.........................................................................................87

3.8. Use case: Despatch & receiving process: indirect shipping between supplier and customer by using an external warehouse controlled by the supplier...............88

3.8.1. Use case: Despatch of goods warehouse – customer controlled by supplier.....................94 3.8.1.1. Activity diagram – despatch of goods (despatch confirmation) ....................................95 3.8.1.2. Business collaboration – Despatch confirmation...........................................................96 3.8.1.3. Business transactions and authorized roles – Despatch confirmation ...........................98

3.9. The stock inventory of the goods in a warehouse..................................................................99 3.9.1. Use case: Inventory report process ....................................................................................99 3.9.2. Activity diagram – Inventory report process ...................................................................101 3.9.3. Business collaboration – Inventory report process ..........................................................103 3.9.3.1. Business collaboration – Inventory report on request..................................................103 3.9.3.2. Business collaboration – Inventory report on regular basis.........................................105 3.9.4. Business transactions and authorized roles – Inventory report process...........................107 3.9.4.1. Business transactions and authorized roles – Request Inventory report......................107 3.9.4.2. Business transactions and authorized roles – Inventory report....................................108

ESIDEL – Shipping cycle

4

4. Business Process Definition – Certificate/Quality report 109 4.1. Scope....................................................................................................................................109 4.2. Process definition.................................................................................................................109 4.3. Principles..............................................................................................................................109 4.4. Use case: Certificate/Quality report process........................................................................110 4.5. Activity diagram – Certificate/Quality report process.........................................................112 4.6. Activity diagram - Alternative Certificate/Quality report process.......................................113 4.7. Business collaboration - Certificate/Quality report process ................................................114

4.7.1. Business collaboration – Certificate/Quality report on request .......................................114 4.7.2. Business collaboration – Certificate/Quality report on regular event..............................117

4.8. Business transactions and authorized roles – Certificate/Quality report process ................119 4.8.1. Business transactions and authorized roles – Cerificate/Quality report request ..............119

4.8.2. Business transactions and authorized roles – Certificate/Quality report .............................120

ESIDEL – Shipping cycle

5

1. Shipping cycle definition 1.1. Scope In the shipping cycle it is foreseen to transmit between the supplier, customer, carrier and third parties, the relevant information concerning the selection of goods to be delivered by the customer, the preparation of the shipment of goods, the shipment and the receiving of the goods. It is also possible to transmit in the shipping cycle, between the supplier and the customer the certificate/quality report concerning the goods. To simplify the understanding the parties involved are limited to three or four parties, based on the different shipping processes. The parties involved are customer, supplier, carrier and warehouse. In the total Trade business each of the parties can have more than one role. For the Shipping cycle the customer can act as the customer, the consignee and the ordering company. The supplier covers the roles of the seller, the sales agent or sales organisation, manufacturer and consignor. The partners involved in the shipping cycle are not limited to supplier and customer but involves also the carrier responsible for doing the transport and if applicable also warehouses. As a consequence the information exchange is not limited to the exchange of information between the supplier and the customer, but exists also between the carrier, warehouse and the supplier, customer. The electronic information exchanges between the supplier, customer and warehouse are done by using trade messages. The electronic information exchanges with the carrier are done by using transport messages. In the different processes presented in this document both information flows are presented. The processes for the shipping cycle are general with respect to any terms of delivery, mode and means of transport. Depending on the mode of transport, some other transport messages shall be added to support the transport process. More detailed information specific for the particular modes of transport can be found in the final report of the Multi Industry Scenarios for Transport (MIST) group. In this document the scenarios are provided with the different modes of transport.

ESIDEL – Shipping cycle

6

1.2 Processes

The shipping cycle is divided in three processes:

- The Selection of goods process This process supports the selection of goods by the customer by the exchange of information concerning the goods ready for despatch, the instruction to despatch.

- The Despatch & Receiving process This process supports the exchange of information concerning the despatch advice and the reception of the goods.

- The Certificate/Quality report process This process supports the exchange of the information of the Certificate/Quality report of the goods.

Selection of goods

Certificate/Quality report

Basic information

Basic information

Langage d ’échange des filières acier

European Steel Exchange

Language

SchedulingSchedulingOrdering Ordering

ShippingShipping

Invoicing Invoicing PaymentPayment

Despatch & Receiving

ESIDEL – Shipping cycle

7

1.3. Use case: shipping cycle The use case for the shipping cycle shows which Business collaboration use cases are used to compose the process:

- The treatment of the selection of goods process - The treatment of the despatch & receiving process - The treatment of the certificate/quality report process

For each of the Business collaboration use case a description is provided in this chapter. Use case diagram – shipping cycle

Shipping cycle

Selection of goods process

Shipping cycle

CustomerSupplier

CustomerSupplier

Figure 1 Use Case Diagram – Shipping cycle

Certificate/ Quality report

process

Warehouse Carrier

Despatch & receiving process

ESIDEL – Shipping cycle

8

2. Business Process Definition – Selection of goods process 2.1. Scope

The selection of goods process will be used to allow the customer to select out of the goods ready for delivery at the supplier, the goods to be delivered by the supplier. The same process can be used to allow the customer to arrange the transport of the goods and to inform the supplier about the pick up of the selected goods.

In the selection of goods process it is foreseen to transmit the relevant information between the supplier and the customer concerning:

- The request to receive a list of the goods ready for despatch. - The goods ready for despatch, when the customer is responsible for organising the

transport or when he decides on which goods can be shipped by the supplier. - The despatch instruction for the requested goods, when the customer is responsible for

organising the transport or when he decides on which goods are to be shipped by the supplier.

2.2. Process definition The Selection of goods process can be used under two different conditions agreed between the supplier and the customer. Both parties agreed that the transportation of the goods is the responsibility of the customer. Under this condition the supplier has to inform the customer when the goods are ready in the warehouse of the supplier. This information can be sent on the request of the customer or can be provided on a regular basis or predefined condition, such as a certain quantity or the completion of one or several orders. Depending on the mode and means of transport, the available quantity of goods, the customer shall organise a transport to collect the goods by the supplier. Once the transport service is ordered, the customer shall inform the supplier about the transportation organised and the goods selected for the means of transport. The supplier needs this information to prepare the consignment of the goods in function of the mode and means of transport, the foreseen arrival date of the means of transport and the identified goods. Both parties agreed that the transportation of goods should not be initiated by the supplier, but that the delivery of goods will be steered by the customer, based on his own production planning. Under this condition the supplier has to inform on a regular basis the customer about the goods ready in the warehouse. Based on this own production planning, the customer shall identify goods to be delivered. On this instruction received from the customer, the supplier shall order the transport service. Based on the agreement between the parties, the goods ready for despatch can be reported as a balance of all available goods, or as a movement being the additions and subtractions of the goods made available or removed in a certain time/period. To support the Selection of goods process the following four messages have been developed:

- The goods ready for despatch request - The goods ready for despatch (balance) - The goods ready for despatch (movement) - The instruction to despatch.

ESIDEL – Shipping cycle

9

The customer or customer’s agent can initiate a request for an inventory of goods ready for despatch to the supplier or supplier’s agent, asking for information on the current status of placed order(s). This request is either directly transmitted or forwarded by an “electronic work environment’ to the supplier. Upon receipt of the goods ready for despatch request, the supplier or supplier’s agent will send to the customer or customer’s agent the goods ready for despatch balance or movement. This inventory is either directly transmitted or forwarded by an “electronic work environment” to the customer. The goods ready for despatch balance or movement can also be sent by the supplier or supplier’s agent at a regular interval or event as agreed between the two parties without initiating a goods ready for despatch request. The customer or customer’s agent can request the delivery of goods ready for despatch by sending the instruction to despatch. 2.3. Principles The supplier has the obligation to respond with the goods ready for despatch balance or movement to the goods ready for despatch request.

ESIDEL – Shipping cycle

10

2.4. Use case: selection of goods process The use case for the selection of goods process has the following business transactions:

- Place a goods ready for despatch request - Provide a goods ready for despatch balance or movement - Provide an instruction to despatch.

Use case diagram – selection of goods process

Selection of goods

process

Goods ready for despatch

request

Selection of goods

Customer Supplier

Instruction to

despatch

CustomerSupplier

Figure 2 Use Case Diagram – Selection of goods process

Goods ready for despatch

(balance – movement)

ESIDEL – Shipping cycle

11

Use case description – selection of goods process Business process name

Selection of goods process

Identifier EUROFER: Selection of goods process Actors Customer,

Supplier Description The customer recognises a need to know the actual situation of the goods ready for the

despatch at the supplier. The supplier receives the request and responds with the goods ready for despatch balance or movement. The customer recognises the need of goods and generate an instruction to despatch to inform the supplier of a collection of goods organised by customer, or giving instruction to the supplier to organise a delivery.

Pre-condition Customer’s orders have been placed with the supplier. Post-condition The supplier prepares the consignment and initiates the despatch & receiving process. Scenario

Starts when customer recognises the need to be informed about the goods ready for despatch: - Customer raises and sends the goods ready for despatch request containing the

parameters for the selection of one or more order lines, to the supplier. - Supplier receives the goods ready for despatch request. - Supplier generates the goods ready for despatch balance or movement, giving the actual

situation of the goods ready for despatch of one or more order lines, to the customer. - Customer receives the goods ready for despatch balance or movement. - The customer recognises the need of goods in order to supply his own production line.

In function of the mode and means of transport he make a selection of the goods to be delivered.

- In the case that the customer is responsible for the ordering of the transport service, he will generate an instruction to despatch to inform the supplier about the collection of goods.

- In the case that the supplier is responsible for the ordering of the transport service, the customer will generate an instruction to despatch to instruct the supplier to organise a despatch of the selected goods.

- Supplier receives the instruction to despatch. The cycle of requesting goods ready for despatch inventory and sending the goods ready for despatch might be executed multiple times.

Alternative scenarios

The supplier may also provide a goods ready for despatch balance or movement to the customer at a predefined regular interval or event and not necessarily in response to the goods ready for despatch request.

Remarks The customer and the supplier should agree to use the goods ready for despatch balance or the goods ready for despatch movement. Eurofer recommends to use the goods ready for despatch balance as the response to the goods ready for despatch request. When both parties agreed to provide the goods ready for despatch on a predefined interval, the balance or movement message can be used, but it is more common to use the goods ready for despatch balance.

ESIDEL – Shipping cycle

12

2.5. Activity diagram – selection of goods process Figure 3. Business domain activity diagram – Selection of goods process Activity diagram description – Selection of goods process The customer raises and sends the goods ready for despatch request containing one or more selection criteria for the orders for which a goods ready for despatch is required to the supplier. When the supplier receives the goods ready for despatch request, he selects the relevant orders and raises the corresponding goods ready for despatch balance or movement. As a result the supplier sends a goods ready for despatch balance or movement to the customer. Once the customer receives the goods ready for despatch balance or movement, he checks if goods are needed for his own production. If no goods are needed, the business process ends. If goods are needed and based on the delivery conditions agreed, the customer shall organise the transport service to collect the goods by the supplier, or he shall select the needed goods. As a result of both processes he send an instruction to despatch to the supplier. Once the supplier receives the instruction to despatch, the business process ends and the supplier shall initiate the despatch & receiving process.

Start of Selection of goods process

Raises a goods ready for dispatch request

Receives Goods ready for dispatch balance/movement

Receives goods ready for despatch request

Provides Goods ready for

despatch balance:movement

Goods ready for despatch request

Supplier Customer

Goods ready for despatch

balance/movement

End of Selection of goods process

Delivery of goods

Yes

No

Organise transport or select goods Receives Instruction

to despatch Instruction to

despatch

Start the despatch & receiving process

ESIDEL – Shipping cycle

13

2.6. Activity diagram – Alternative selection of goods process Figure 4. Business domain activity diagram – Alternative selection of goods process Activity diagram description – Alternative selection of goods process Based on an agreement with the customer, the supplier raises at a regular interval are event a goods ready for despatch balance or movement (most common) for the customer. As a result the supplier sends a goods ready for despatch balance or movement to the customer. Once the customer receives the goods ready for despatch balance or movement, he checks if goods are needed for his own production. If no goods are needed, the business process ends. If goods are needed and based on the delivery conditions agreed, the customer shall organise the transport service to collect the goods by the supplier, or he shall select the needed goods. As a result of both processes he send an instruction to despatch to the supplier. Once the supplier receives the instruction to despatch, the business process ends and the supplier shall initiate the despatch & receiving process.

Start of Selection of goods process

Receives Goods ready for dispatch balance:

movement

Provides Goods ready for

despatch balance/ movement

Supplier Customer

Goods ready for despatch

balance/movement

End of Selection of goods process

Delivery of goods

Yes

No

Organise transport or select goods Receives Instruction

to despatch Instruction to

despatch

Start the despatch & receiving process

ESIDEL – Shipping cycle

14

2.7. Business collaboration – Selection of goods process

The business collaboration specifies for each of the abovementioned activity diagrams the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

2.7.1. Business collaboration – Selection of goods on request

Business Collaboration

Identifier EUROFER: Selection of goods on request

Description The customer raises and sends a goods ready for despatch request containing one or more selection criteria for the orders for which a goods ready for despatch is required to the supplier. When the supplier receives the goods ready for despatch request, he selects the relevant orders and raises the corresponding goods ready for despatch balance or movement. As a result the supplier sends a goods ready for despatch balance or movement to the customer. When the customer receives the goods ready for despatch balance or movement, he checks the need to receive some of the goods for his own production. If there is no need of goods the business process ends. If there is a need, he will organise the transport services to collect the goods are he will only select the needed goods. As a result of this activity he raises and sends an instruction to despatch to the supplier. Once the supplier receives the instruction of despatch, the business process ends and the supplier will initiate the Despatch & receiving process.

Partner Types Customer Supplier

Authorized Roles Customer Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the customer sends the goods ready for despatch request message

• Terminal: the customer receives the goods ready for despatch balance or movement or the supplier receives the instruction of despatch message.

Scope To request the goods ready for despatch, with the aim to organise the collection of goods at the supplier are to select goods to be despatched by the supplier.

Boundary Not defined yet

Constraints The customer shall have full traceability of his request message and the instruction to despatch message to make sure it has been received. Failing this technical acknowledgement, the customer shall re-issue his request message or instruction to despatch message.

ESIDEL – Shipping cycle

15

In a business collaboration agreement between the customer and the supplier, the way of using the Selection of goods process can be described. The following transactions concerning the Selection of goods can be specified as:

-1. The customer generates the goods ready for despatch request to receive a goods ready for despatch, the supplier has to give an acknowledge of receipt of the goods ready for despatch request. The supplier sends the goods ready for despatch balance or movement to the customer. The customer acknowledges the receipt of the goods ready for despatch balance or movement to the supplier. The customer generates an instruction to despatch to instruct the supplier about the despatch of goods, the supplier has to give an acknowledge of receipt of the instruction to despatch.

-2. The customer generates a goods ready for despatch request to receive a goods ready for despatch, and the supplier responds directly with the goods ready for despatch balance or movement.

The customer generates an instruction to despatch to instruct the supplier about the despatch of goods. No acknowledgement messages are used between the parties.

In the Business collaboration agreement the three transactions are split in two Business transaction activity graph. The first is dealing with the request and the response to cover the goods ready for despatch request, balance or movement. The second is dealing with the notification to cover the instruction to despatch.

Part 1 of the Business collaboration: Selection of goods / goods ready for despatch request Figure 5. Business transaction activity graph – Selection of goods / goods ready for despatch request

Goods ready for despatch request

Place request for a goods ready for despatch

[CONTROLFAIL]

[SUCCESS]

Process goods ready for despatch request

Goods ready for dispatch balance/

movement

Supplier Customer

START

END

ESIDEL – Shipping cycle

16

Form: Business Transaction Transition Table

From Id EUROFER: Selection of goods / goods ready for despatch request From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Place request for a

goods ready for despatch

Customer NONE

Place request for a goods ready for despatch

Customer Goods ready for despatch request

Process goods ready for despatch request

Supplier NONE

Process goods ready for despatch request

Supplier Goods ready for despatch balance or movement

Place request for a goods ready for despatch

Customer NONE

Place request for a goods ready for despatch

Customer N/A SUCCESS N/A Goods ready for despatch balance or movement received

Place request for a goods ready for despatch

Customer N/A CONTROLFAIL N/A Goods ready for despatch balance or movement not received

Part 2 of the Business collaboration: Selection of goods / instruction to despatch Figure 6. Business transaction activity graph – Selection of goods / instruction to despatch

Instruction to despatch

Place an instruction to despatch goods

[CONTROLFAIL]

[SUCCESS]

Process Instruction to despatch

Supplier Customer

START

END

ESIDEL – Shipping cycle

17

Form: Business Transaction Transition Table

From Id EUROFER: Selection of goods / instruction to despatch From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Place an

instruction to despatch goods

Customer NONE

Place an instruction to despatch goods

Customer Instruction to despatch

Process instruction to despatch

Supplier NONE

Place an instruction to despatch goods

Customer N/A SUCCESS N/A Instruction to despatch received

Place an instruction to despatch goods

Customer N/A CONTROLFAIL N/A Instruction to despatch not received

ESIDEL – Shipping cycle

18

2.7.2. Business collaboration – Selection of goods on regular basis

Business Collaboration

Identifier EUROFER: Selection of goods on regular basis

Description Based on the agreement with the customer, the supplier raises on regular interval or event a goods ready for despatch balance or movement. As a result the supplier sends a goods ready for despatch balance or movement to the customer. When the customer receives the goods ready for despatch balance or movement, he checks the need to receive some of the goods for his own production. If there is no need of goods the business process ends. If there is a need, he will organise the transport services to collect the goods or he will only select the needed goods. As a result of this activity he raises and sends an instruction to despatch to the supplier. Once the supplier receives the instruction of despatch, the business process ends and the supplier will initiate the Despatch & receiving process.

Partner Types Customer Supplier

Authorized Roles Customer Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: agreement between the customer and the supplier.

• Terminal: the customer receives the goods ready for despatch balance or movement or the supplier receives the instruction of despatch message.

Scope The customer has an agreement with the supplier, to send him a goods ready for despatch balance or movement on a regular basis, with the aim to organise the collection of goods at the supplier are to select goods to be despatched by the supplier.

Boundary Not defined yet

Constraints The customer has the agreement with the supplier, to send him a goods ready for despatch balance or movement.

In a business collaboration agreement between the customer and the supplier, the way of using the Selection of goods on regular basis process can be described. The following transactions concerning the Selection of goods can be specified as:

-1. The supplier sends the goods ready for despatch balance or movement (most common) to the customer. The customer acknowledges the receipt of the goods ready for despatch balance or movement to the supplier. The customer generates an instruction to despatch to instruct the supplier about the despatch of goods, the supplier has to give an acknowledge of receipt of the instruction to despatch.

-2. The supplier sends the goods ready for despatch balance or movement. The customer generates an instruction to despatch to instruct the supplier about the despatch

of goods. No acknowledgement messages are used between the parties.

ESIDEL – Shipping cycle

19

In the Business collaboration agreement the two transactions are split in two Business transaction activity graph. The first is dealing with the notification to cover the goods ready for despatch request and balance or movement. The second is dealing with the notification to cover the instruction to despatch.

Part 1 of the Business collaboration: Selection of goods / goods ready for despatch reporting Figure 7. Business transaction activity graph – Selection of goods / goods ready for despatch reporting

Form: Business Transaction Transition Table From Id EUROFER: Selection of goods / goods ready for despatch reporting From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Goods ready for

despatch reporting Supplier NONE

Goods ready for despatch reporting

Supplier Goods ready for despatch balance/ movement

Process goods ready for despatch balance/ movement

Customer NONE

Goods ready for despatch reporting

Supplier N/A SUCCESS N/A Goods ready for despatch balance/ movement received

Goods ready for despatch reporting

Supplier N/A CONTROLFAIL N/A Goods ready for despatch balance/ movement not received

Goods ready for despatch balance/

movement

Process goods ready for despatch balance/movement [CONTROLFAIL]

[SUCCESS]

Goods ready for despatch reporting

Supplier Customer

START

END

ESIDEL – Shipping cycle

20

Part 2 of the Business collaboration: Selection of goods / instruction to despatch Figure 8. Business transaction activity graph – Selection of goods / instruction to despatch

Form: Business Transaction Transition Table From Id EUROFER: Selection of goods / instruction to despatch From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Place an

instruction to despatch goods

Customer NONE

Place an instruction to despatch goods

Customer Instruction to despatch

Process instruction to despatch

Supplier NONE

Place an instruction to despatch goods

Customer N/A SUCCESS N/A Instruction to despatch received

Place an instruction to despatch goods

Customer N/A CONTROLFAIL N/A Instruction to despatch not received

Instruction to despatch

Place an instruction to despatch goods

[CONTROLFAIL]

[SUCCESS]

Process Instruction to despatch

Supplier Customer

START

END

ESIDEL – Shipping cycle

21

2.8. Business transactions and authorized roles – Selection of goods process The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

2.8.1. Business transactions and authorized roles – Goods ready for despatch request

Business Transaction

Description The Goods ready for despatch request is used to request a goods ready to despatch balance or movement.

Pattern Request/Response

Business activities and associated authorized roles

See EUROFER: goods ready for despatch request

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer

Initiating/Requesting Activity Document

Goods ready for despatch request

Responding Partner Type Supplier

Responding Activity Role Supplier

Responding Activity Document Goods ready for despatch balance or movement

Business document

- GOODS READY FOR DESPATCH REQUEST See EUROFER Message Guideline INVENTORY REQUEST

- GOODS READY FOR DESPATCH See EUROFER Message Guidelines GOODS READY FOR DESPATCH (BALANCE) and GOODS READY FOR DESPATCH (MOVEMENT)

ESIDEL – Shipping cycle

22

2.8.2. Business transactions and authorized roles – Goods ready for despatch inventory

Business Transaction

Description The Goods ready for despatch balance or movement is used to report information on the goods ready for despatch.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: goods ready for despatch balance or movement

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier

Initiating/Requesting Activity Role

Supplier

Initiating/Requesting Activity Document

Goods ready for despatch balance or movement

Business document

- GOODS READY FOR DESPATCH See EUROFER Message Guidelines GOODS READY FOR DESPATCH (BALANCE) and GOODS READY FOR DESPATCH (MOVEMENT)

ESIDEL – Shipping cycle

23

2.8.3. Business transactions and authorized roles – Instruction to despatch

Business Transaction

Description The Instruction to despatch is used to instruct the supplier about the goods to be despatched.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: instruction to despatch

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer

Initiating/Requesting Activity Document

Instruction to despatch

Business document

- INSTRUCTION TO DESPATCH See EUROFER Message Guideline INSTRUCTION TO DESPATCH

ESIDEL – Shipping cycle

24

3. Business Process Definition – Despatch & receiving process 3.1. Scope

The despatch & receiving process will be used to support the delivery of goods from the supplier to the customer. Prior to the delivery, the customer and the supplier have to agree upon the delivery conditions and the way the transportation of goods is organised. In function of the common practice used between the customers’ community and the Steel industry, one of the following delivery processes can be used:

- Direct shipping between the supplier and the customer, transport ordered by the supplier, - Direct shipping between the supplier and the customer, transport ordered by the

customer, - Indirect shipping between the supplier and the customer by using a third party

warehouse - Indirect shipping between the supplier and the customer by using the customer

consignment stock - Indirect shipping between the supplier and the customer by using an external warehouse

controlled by the supplier.

In the despatch & receiving process it is foreseen to transmit the relevant information between the supplier and the customer concerning:

- The information about a shipment and the consignment (goods) being despatched by the supplier.

- The report of the shipment and goods received by the customer. In the despatch & receiving process it is foreseen to transmit the relevant information between the warehouse and the customer or supplier concerning:

- The information about the shipment and the consignment (goods) being despatched by the supplier to the warehouse.

- The report of the goods receiving by the warehouse. - The delivery instruction or the despatch instruction for the delivery of goods from the

warehouse to the customer. - The report of the goods delivered by the warehouse to the customer. - The information about the shipment and the goods being despatched by the warehouse to

the customer. In the despatch & receiving process it is foreseen to transmit the relevant information between the carrier and the customer, supplier or warehouse concerning:

- The ordering of transport services, starting with the transport booking request to the carrier and a confirmation of the transport booking from the carrier to the transport ordering party.

- Depending of the mode of transport and legal obligations the supplier shall provide the carrier with a shipping advice, a waybill or a goods invoice.

- The information about the collection of the goods by the carrier. - The status of the transport and the foreseen arrival date. - The information about the delivery of the goods by the carrier.

ESIDEL – Shipping cycle

25

3.2. Process definition The Despatch & receiving process is the mechanism by which information is provided on the despatch of goods, the reception of the goods, the ordering and follow-up of the transport services between the place of loading (shipping from location) and the place of unloading (shipping to location). To provide information to the customer or warehouse of the despatch of goods at the moment of departure, allows the customer or warehouse to prepare the reception of the goods. Providing information about the reception of the goods allows the supplier to check the correct arrival of the despatch goods and can be used as a trigger to build the invoice to the customer. Each despatch & receiving process mentioned in chapter 3.1. consists of the following processes. In some of these despatch & receiving processes, the following processes can appear more than one time due to the fact that the delivery of goods from the supplier to the customer in done is several steps by using external warehouses. The ‘Ordering of transport services’ process starts by a booking request from the supplier, customer or warehouse to the carrier, to instruct the carrier to transport goods from a location to another location. This information will be followed by a confirmation of the booking request from the carrier. The ‘Despatch of goods’ process starts with the collection of the goods by the carrier and depending on the mode of transport and legal obligations the supplier shall provide the carrier with a shipping advice, a waybill or the goods invoice. As a proof of collection of the goods, the carrier has to provide to the supplier a signed waybill. At the moment the goods are leaving the shipping from location, the supplier or the warehouse shall inform the warehouse or the customer about the goods despatched by means of a despatch advice or a packing list. Remark: Two different documents are in use in the European steel industry to inform the

customer about the goods despatched. The first is the usage of the despatch advice giving the details of a consignment starting from the point of view of the goods or articles. The second way is the packing list giving the details of a consignment from the point of view of the equipments used for the transportation, the handling units and the packages used to despatch the goods are articles. Based on an agreement between the supplier and the customer one of the documents are both documents will be provided by the supplier.

In the ‘Goods in transit’ process the carrier has the possibility to inform the supplier, customer and or warehouse about the precise status of the transport or unexpected exceptions. This reporting can be done as a master reporting by exception or based on ad-hoc request for follow-up information. The carrier can inform the receiver of the goods (customer or warehouse) about the foreseen arrival date, so that the party involved can prepare and arrange the reception of the goods. The ‘Goods delivered’ process starts with the reception of the transport and the receiving party shall provide to the carrier a signed waybill, confirming the received goods and if relevant the damage report. As a proof that the goods are delivered to the receiving party, the carrier shall send a copy of the signed waybill to the ordering party (supplier or warehouse). Once the party has received the goods, he will check these goods with the goods advised in the despatch advice or packing list. The receiving party will send to the supplier or warehouse the confirmation of the reception of the goods according to the despatch advice or packing list or shall advice only on the received goods.

ESIDEL – Shipping cycle

26

Remark: In the process definitions references is made for the collection of goods and the

reception of the goods to a signed document named waybill. In the future based on new technologies the carrier shall be able to replace this paper document by an electronic exchange of information

3.3. Principles For each of the Despatch & receiving process mentioned a specific use case is presented to explain the interaction of the involved transactions.

ESIDEL – Shipping cycle

27

3.4. Use case: Despatch & receiving process: direct shipping between

supplier and customer – transport service ordered by the supplier

The use case for the despatch & receiving process has the following processes and business transactions:

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery Receiving advice.

Use case diagram – despatch & receiving process: direct shipping between supplier and customer

- transport service ordered by the supplier

Despatch & receiving process

Ordering transport services

Despatch & receiving

CustomerSupplier

Goods in transit

Customer

Supplier

Figure 9 Use Case Diagram – Despatch & receiving process: direct shipping between supplier and customer – transport service ordered by supplier

Carrier

Despatch of goods

Goods delivered

ESIDEL – Shipping cycle

28

3.4.1. Use case: Ordering transport services The use case for the ordering transport services process has the following business transactions:

- The transport booking request - The transport booking confirmation.

Use case diagram – ordering transport services

Ordering transport services

Transport booking request

Ordering transport services

Supplier Carrier

Transport booking

confirmationSupplier

Figure 10 Use Case Diagram – Ordering transport services

Carrier

ESIDEL – Shipping cycle

29

Use case description – ordering transport services Business process name

Ordering transport services

Identifier EUROFER: ordering transport services Actors Supplier,

Carrier Description The transport ordering party (supplier) recognises a need to order a transport to despatch

goods and send a transport booking request to the carrier. The carrier receives the request and responds with a transport booking confirmation to advice the transport ordering party (supplier) about his possibilities to execute the despatch.

Pre-condition There is a need to deliver goods to the customer. Post-condition The transport ordering party shall, based on the response, contact another carrier or shall

prepare the consignment to be collected by the carrier. Scenario

Starts when there is a need to despatch goods from a shipping from location (supplier) to a shipping to location (customer): - The transport ordering party raises and sends a transport booking request to a carrier. - The carrier receives a transport booking and evaluates if he is able to do the requested

transport. - The carrier generates a transport booking confirmation to inform the transport ordering

party about his possibilities to execute the transport. - The transport ordering party receives the transport booking confirmation and based on

the information received, he can contact another carrier or he shall start to prepare the despatch of the goods.

Alternative scenarios

Remarks 3.4.2. Activity diagram – ordering transport services Figure 11. Business domain activity diagram – Ordering transport services

Start of Ordering transport services

Receives Transport booking confirmation

Receives a Transport booking request

Provides a Transport booking

confirmation

Transport booking request

CarrierTransport ordering party (supplier)

Transport booking confirmation

End of Ordering transport services

Raises a Transport booking request

ESIDEL – Shipping cycle

30

Activity diagram description – ordering transport services The transport ordering party (supplier) raises and sends a transport booking request to the carrier to execute a delivery of goods. When the carrier receives the transport booking, he investigates the requirements of the transport ordering party and based on his finding he raises the transport booking confirmation. As a result the carrier sends a transport booking confirmation to the transport ordering party (supplier). Once the transport ordering party received the transport booking confirmation, the process ends. 3.4.3. Business collaboration – ordering transport services The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Business Collaboration

Identifier EUROFER: Ordering transport services

Description The transport ordering party (supplier) raises and sends a transport booking to the carrier, containing the transport requirements to support a despatch of goods. When the carrier receives the transport booking request, he evaluates the request and raises the corresponding transport booking confirmation. As a result the carrier sends a transport booking confirmation to the transport ordering party (supplier). Once the transport ordering party (supplier) received the transport booking confirmation, the process ends.

Partner Types Transport ordering party (Supplier) Carrier

Authorized Roles Transport ordering party Carrier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport ordering party sends the transport booking request

• Terminal: the transport ordering party receives the transport booking confirmation

Scope To order transport services to the carrier for the despatch of goods.

Boundary Not defined yet

Constraints The transport ordering party shall have full traceability of his request message to make sure it has been received. Failing this technical acknowledgement, the transport ordering party shall re-issue his request message

ESIDEL – Shipping cycle

31

In a business collaboration agreement between the transport ordering party and the carrier, the way of using the Ordering transport services process can be described. The following transactions concerning the ordering transport services can be specified as:

-1. The transport ordering party generates a transport booking request to inform about a transport needed to despatch goods, the carrier has to give an acknowledge of receipt of the transport booking request. The carrier sends a transport booking confirmation to the transport ordering party. The transport ordering party acknowledges the receipt of the transport booking confirmation to the carrier.

-2. The transport ordering party generates a transport booking request to inform about a transport needed to despatch goods, and the carrier responds directly with the transport booking confirmation. No acknowledgement messages are used between the parties.

Figure 12. Business transaction activity graph – Ordering transport services

Form: Business Transaction Transition Table From Id EUROFER: Ordering transport services From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Recognise

transport requirements

Transport ordering party

NONE

Recognise transport requirements

Transport ordering party

Transport booking request

Process transport booking request

Carrier NONE

Process transport booking request

Carrier Transport booking confirmation

Recognise transport requirements

Transport ordering party

NONE

Recognise transport requirements

Transport ordering party

N/A SUCCESS N/A Transport booking request accepted

Recognise delivery requirements

Transport ordering party

N/A CONTROLFAIL N/A Transport booking request rejected

Transport booking request

Recognise transport requirements

[CONTROLFAIL]

[SUCCESS]

Process transport booking request

Transport booking confirmation

Carrier Transport ordering party (supplier)

START

END

ESIDEL – Shipping cycle

32

3.4.4. Business transactions and authorized roles – Ordering transport services The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

Business Transaction

Description The ordering transport services is used to request transport services for the despatch of goods.

Pattern Request/Response

Business activities and associated authorized roles

See EUROFER: Ordering transport services

Constraints Not defined yet

Initiating/Requesting Partner Type

Transport ordering party (supplier)

Initiating/Requesting Activity Role

Transport ordering party

Initiating/Requesting Activity Document

Transport booking request

Responding Partner Type Carrier

Responding Activity Role Carrier

Responding Activity Document Transport booking confirmation

Business document

- TRANSPORT BOOKING REQUEST EUROFER decided not to develop for the moment the Message Guideline for the transaction

- TRANSPORT BOOKING CONFIRMATION EUROFER decided not to develop for the moment the Message Guideline for the transaction

ESIDEL – Shipping cycle

33

3.4.5. Use case: Despatch of goods The use case for the despatch of goods process has the following business transactions:

- The shipping advice or waybill - The proof of collection - The despatch advice and, or packing list.

Use case diagram – despatch of goods

Despatch of goods

Transport document (shipping

advice/waybill)

Despatch of goods

Supplier

Carrier

Proof of collection Supplier

Figure 13 Use Case Diagram – Despatch of goods

Carrier

Customer

CustomerDespatch advice

and, or packing list

ESIDEL – Shipping cycle

34

Use case description – despatch of goods Business process name

Despatch of goods

Identifier EUROFER: despatch of goods Actors Supplier,

Carrier Customer

Description The transport ordering party (supplier) recognises a need to despatch goods and send the contracted carrier the necessary transport documents depending on the mode of transport and legal obligations. The carrier receives the transport documents and collects the goods at the shipping from location. As a proof of collection of the goods, the supplier receives from the carrier the signed transport document. At that moment or on the departure of the means of transport the supplier will send a despatch advice and, or a packing list to the customer.

Pre-condition There is a need to deliver goods to the customer. Post-condition The despatched goods are transported to the shipping to location. Scenario

Starts when there is a need to despatch goods from a shipping from location (supplier) to a shipping to location (customer) and the transport booking is confirmed: - The supplier raises and sends the transport documents required for the means of

transport and the legal obligations to a carrier. - The carrier receives a transport documents and shall collect the goods at the shipping

from location, as a proof of collection he will send a signed transport document to the supplier.

- The supplier generates a despatch advice and, or a packing list to inform the customer about the transport and the goods despatched (consignment).

- The customer receives the despatch advice and, or packing list and based on the information received, he can organise the reception of the goods.

Alternative scenarios

Remarks 3.4.6. Activity diagram – Despatch of goods (activity between supplier and carrier)

Start of Despatch of goods

Receives Proof of collection

Receives the Transport documents

Provides Proof of collection (signed

transport document)

Transport documents

CarrierSupplier

Transport booking confirmation

End of step 1 of Despatch of goods

Raises the Transport documents

Collection of the goods

ESIDEL – Shipping cycle

35

Activity diagram – despatch of goods (activity between supplier and customer) Figure 14. Business domain activity diagram – Despatch of goods Activity diagram description – despatch of goods The supplier raises and sends to the carrier the relevant transport documents in function of the mode of transport and the legal obligations. When the carrier receives the transport documents and in function of the requested despatch date, the carrier will collect the goods at the shipping from location. As a result of the collection he will provide to the supplier a signed transport document as proof of collection. When the goods are leaving the shipping from location the supplier will inform the customer of the transport and the consignment by sending a despatch advice and, or packing list. Once the received the despatch advice or the packing list, the process ends. 3.4.7. Business collaboration – Despatch of goods

The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Start of step 2 of Despatch of goods

Receives the Despatch adviceand,

or Packing list

Despatch advice and, or Packing list

CustomerSupplier

End of Despatch of goods

Raises the Despatch advice and, or

Packing list

ESIDEL – Shipping cycle

36

Business Collaboration

Identifier EUROFER: Despatch of goods (step 1)

Description The supplier raises and sends the relevant transport documents to the carrier. When the carrier receives the transport documents, he shall collect the goods in function of the despatch date requested. As a result of the collection of the goods the carrier sends a signed transport document to the supplier as proof of collection of the goods. Once the supplier received the proof of collection, step 1 of the process ends.

Partner Types Supplier Carrier

Authorized Roles Supplier Carrier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport is ordered

• Terminal: the goods are transported from the shipping from location

Scope To collect the goods at the shipping from location.

Boundary Not defined yet

Constraints

Business Collaboration

Identifier EUROFER: Despatch of goods (step 2)

Description Once the transport leaves the shipping from location the supplier sends a despatch advice and, or a packing list to the customer to inform him of the despatch goods. Once the customer received the despatch advice and, or packing list, the process ends.

Partner Types Supplier Customer

Authorized Roles Supplier Customer

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport has left the shipping from location.

• Terminal: the goods are transported to the shipping to location

Scope To despatch of goods from the shipping from location.

Boundary Not defined yet

Constraints

ESIDEL – Shipping cycle

37

In a business collaboration agreement between the supplier and the carrier, the way of using the despatch of goods process can be described. The following transactions concerning the despatch of goods can be specified as:

-1. The supplier generates and sends the transport documents to the carrier, needed to transport the goods, the carrier has to give an acknowledge of receipt of the transport documents. When the goods are collected at the shipping from location, the carrier sends a proof of collection to the supplier. The supplier acknowledges the receipt of the proof, of collection to the carrier.

-2. The supplier generates and sends the transport documents to the carrier, needed to transport the goods.

When the goods are collected at the shipping from location, the carrier sends a proof of collection to the supplier. No acknowledgement messages are used between the parties.

In a business collaboration agreement between the supplier and the customer, the way of using the despatch of goods process can be described. The following transactions concerning the despatch of goods can be specified as:

-1. The supplier generates and sends the despatch advice and, or packing list to the customer to inform about the despatched goods, the customer has to give an acknowledge of receipt of the despatch advice and, or packing list.

-2. The supplier generates and sends the despatch advice and, or packing list to the customer to inform about the despatched goods. No acknowledgement messages are used between the parties.

Part 1 of the Business collaboration: Despatch of goods / transport documents – proof of collection

Figure 15. Business transaction activity graph – Despatch of goods (step 1)

Transport documents

Organise despatch of goods

[CONTROLFAIL]

[SUCCESS]

Organise collection and transport

Proof of collection

Carrier Supplier

START

END

ESIDEL – Shipping cycle

38

Form: Business Transaction Transition Table

From Id EUROFER: Despatch of goods (step 1) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Organise despatch

of goods Supplier NONE

Organise despatch of goods

Supplier Transport documents

Organise collection and transport

Carrier NONE

Organise collection and transport

Carrier Proof of collection

Organise despatch of goods

Supplier NONE

Organise despatch of goods

Supplier N/A SUCCESS N/A Collection done and transport underway

Organise despatch of goods

Supplier N/A CONTROLFAIL N/A Collection an transport rejected

Part 2 of the Business collaboration: Despatch of goods / despatch advice – packing list Figure 16. Business transaction activity graph – Despatch of goods (step 2)

Despatch advice or Packing list

Produce Despatch document

[CONTROLFAIL]

[SUCCESS]

Process Despatch document

Customer Supplier

START

END

ESIDEL – Shipping cycle

39

Form: Business Transaction Transition Table

From Id EUROFER: Despatch of goods (step 2) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce despatch

document Supplier NONE

Produce despatch document

Supplier Despatch advice and, or Packing list

Process despatch document

Customer NONE

Produce despatch document

Supplier N/A SUCCESS N/A Despatch document received

Produce despatch document

Supplier N/A CONTROLFAIL N/A Despatch document not received

ESIDEL – Shipping cycle

40

3.4.8. Business transactions and authorized roles – Despatch of goods

The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

3.4.8.1. Business transactions and authorized roles – Transport documents and Proof of collection

Business Transaction

Description The proof of collection.

Pattern Notification/Response

Business activities and associated authorized roles

EUROFER: Despatch of goods (step 1)

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier

Initiating/Requesting Activity Role

Supplier

Initiating/Requesting Activity Document

Transport document

Responding Partner Type Carrier

Responding Activity Role Carrier

Responding Activity Document Proof of collection

Business document

- TRANSPORT DOCUMENT EUROFER decided not to develop for the moment the Message Guideline for the transaction

- PROOF OF COLLECTION EUROFER decided not to develop for the moment the Message Guideline for the transaction

ESIDEL – Shipping cycle

41

3.4.8.2. Business transactions and authorized roles – Despatch document

Business Transaction

Description The despatch document.

Pattern Notification

Business activities and associated authorized roles

EUROFER: Despatch of goods (step 2)

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier

Initiating/Requesting Activity Role

Supplier

Initiating/Requesting Activity Document

Despatch advice and, or Packing list

Business document

- TRANSPORT DOCUMENT See EUROFER Message Guidelines DESPATCH ADVICE and PACKING LIST

ESIDEL – Shipping cycle

42

3.4.9. Use case: Goods in transit The use case for the goods in transit process has the following business transactions:

- The transport status request - The transport status report - The pre-arrival notice.

Use case diagram – goods in transit

Goods in transit

Goods in transit

Carrier

Supplier

Transport status report Carrier

Figure 17 Use Case Diagram – Goods in transit

Supplier

Customer

CustomerPre-arrival

notice

Transport status request

ESIDEL – Shipping cycle

43

Use case description – goods in transit Business process name

Goods in transit

Identifier EUROFER: goods in transit Actors Supplier,

Carrier Customer

Description During the transportation of the goods between the shipping from location to the shipping to location, the carrier can be asked, by the supplier or customer, for a report about the precise status of the transport or about unexpected events. The request can be explicit or can be part of a general agreement in which conditions for automatic reporting are specified. During the transport the carrier can inform the supplier or customer about the precise status of the transport or unexpected facts. The carrier can inform the customer about the foreseen arrival date at the shipping to location.

Pre-condition There is a need to have information about the status of the transport or to be informed about the foreseen arrival date.

Post-condition The despatched goods are arrived at the shipping to location. Scenario

Starts when there is a need to receive the exact status of the transport or to know the foreseen arrival date: - The interested party (supplier or customer) raises and sends the transport status request

to the carrier. - The carrier receives a transport status request. - The carrier generates a transport status report giving the actual status of the requested

transport. - The requesting party receives the transport status report. - The carrier raises and sends a pre-arrival notice to the customer. - The customer receives the pre- arrival notice.

Alternative scenarios

The carrier may also provide the transport status report to the interested party based on conditions specified in the transport contract.

Remarks The alternative scenario is not further specified in detail. 3.4.10. Activity diagram – goods in transit (transport status)

Start of Goods in transit

Receives Transport status report

Receives the Transport status

request

Provides Transport status

report

Transport status request

CarrierSupplier / Customer

Transport status report

End of step 1 of Goods in transit

Raises the Transport status request

ESIDEL – Shipping cycle

44

Figure 18. Business domain activity diagram – Goods in transit Activity diagram description – Goods in transit The interested party (supplier or customer) raises and sends to the carrier the transport status request to receive information about the correct status of one or more transports. When the carrier receives the transport status request, he selects the relevant transports and raises the corresponding transport status report. As a result the requesting party (supplier or customer) receives the transport status report. When the carrier is able to provide a foreseen arrival date, he raises and sends to the customer the pre-arrival notification. Once the customer received the pre-arrival notification, the process ends. 3.4.11. Business collaboration – goods in transit

The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Start of step 2 of Goods in transit

Receives the Pre-arrival notification

Pre-arrival notification

CustomerCarrier

End of Despatch of goods

Raises the Pre-arrival notification

ESIDEL – Shipping cycle

45

Business Collaboration

Identifier EUROFER: Goods in transit (step 1)

Description The interested party (supplier or customer) raises and sends a transport status request containing one or more selection criteria for the transports. When the carrier receives the transport status request, he selects the relevant transports and raises the corresponding transport status report. As a result the carrier sends the transport status report to the requesting party. Once the requesting party received the transport status report, step 1 of the process ends.

Partner Types Interested party (Supplier, Customer) Carrier

Authorized Roles Supplier, Customer Carrier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport is underway between the shipping from location and the shipping to location

• Terminal: the goods are arrived at the shipping to location

Scope To report on the transport status.

Boundary Not defined yet

Constraints

Business Collaboration

Identifier EUROFER: Goods in transit (step 2)

Description When the carrier is able to provide with a certain degree of correctness, he raises and sends a pre-arrival notification to the customer. Once the customer received the pre-arrival notification, the process ends.

Partner Types Carrier Customer

Authorized Roles Carrier Customer

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport is underway between the shipping from location to the shipping to location.

• Terminal: the transport is arrived at the shipping to location

Scope To inform about the foreseen arrival date.

Boundary Not defined yet

Constraints

ESIDEL – Shipping cycle

46

In a business collaboration agreement between the supplier/customer and the carrier, the way of using the goods in transit process can be described. The following transactions concerning the despatch of goods can be specified as:

-1. The supplier/customer generates and sends the transport status request to the carrier, the goods, the carrier has to give an acknowledge of receipt of the transport status request. The carrier sends a transport status report to the supplier/customer. The supplier/customer acknowledges the receipt of the transport status report.

-2. The supplier/customer generates and sends the transport status request to the carrier, and the carrier responds directly with the transport status report.

In a business collaboration agreement between the carrier and the customer, the way of using the pre-arrival notification can be described. The following transactions concerning the pre-arrival notification can be specified as:

-1. The carrier generates and sends the pre-arrival notification to the customer, the customer has to give an acknowledge of receipt of the pre-arrival notification.

-2. The carrier generates and sends the pre-arrival notification to the customer. No acknowledgement messages are used between the parties.

Part 1 of the Business collaboration: Goods in transit / transport status Figure 19. Business transaction activity graph – Goods in transit (step 1)

Transport status request

Place a request for a transport status

[CONTROLFAIL]

[SUCCESS]

Process Transport status request

Transport status report

Carrier Supplier/Customer

START

END

ESIDEL – Shipping cycle

47

Form: Business Transaction Transition Table

From Id EUROFER: Goods in transit (step 1) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Place a request for

a transport status Supplier/ Customer

NONE

Place a request for a transport status

Supplier/ Customer

Transport status request

Process transport status request

Carrier NONE

Process transport status request

Carrier Transport status report

Place a request for a transport status

Supplier/ Customer

NONE

Place a request for a transport status

Supplier/ Customer

N/A SUCCESS N/A Transport status report received

Place a request for a transport status

Supplier/ Customer

N/A CONTROLFAIL N/A Transport status report not received

Part 2 of the Business collaboration: Goods in transit/ pre-arrival notification Figure 20. Business transaction activity graph – Goods in transit (step 2)

Pre-arrival notification

Produce Pre-arrival notification

[CONTROLFAIL]

[SUCCESS]

Process Pre-arrival notification

Customer Carrier

START

END

ESIDEL – Shipping cycle

48

Form: Business Transaction Transition Table

From Id EUROFER: Goods in transit (step 2) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce pre-arrival

notification Carrier NONE

Produce pre-arrival notification

Carrier Pre-arrival notification

Process pre-arrival notification

Customer NONE

Produce pre-arrival notification

Supplier N/A SUCCESS N/A Pre-arrival notification received

Produce pre-arrival notification

Supplier N/A CONTROLFAIL N/A Pre-arrival notification not received

ESIDEL – Shipping cycle

49

3.4.12. Business transactions and authorized roles – Goods in transit

The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

3.4.12.1. Business transactions and authorized roles – Transport status report

Business Transaction

Description The transport status report.

Pattern request/Response

Business activities and associated authorized roles

See EUROFER: Goods in transit (step 1)

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier Customer

Initiating/Requesting Activity Role

Supplier Customer

Initiating/Requesting Activity Document

Transport status request

Responding Partner Type Carrier

Responding Activity Role Carrier

Responding Activity Document Transport status report

Business document

- TRANSPORT STATUS REQUEST EUROFER decided not to develop for the moment the Message Guideline for the transaction

- TRANSPORT STATUS REPORT EUROFER decided not to develop for the moment the Message Guideline for the transaction

ESIDEL – Shipping cycle

50

3.4.12.2. Business transactions and authorized roles – Pre-arrival notification

Business Transaction

Description The Pre-arrival notification.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Goods in transit (step 2)

Constraints Not defined yet

Initiating/Requesting Partner Type

Carrier

Initiating/Requesting Activity Role

Carrier

Initiating/Requesting Activity Document

Pre-arrival notification

Business document

- PRE-ARRIVAL NOTIFICATION EUROFER decided not to develop for the moment the Message Guideline for the transaction

ESIDEL – Shipping cycle

51

3.4.13. Use case: Goods delivered The use case for the goods delivered process has the following business transactions:

- The proof of delivery - The receiving advice.

Use case diagram – goods delivered

Goods delivered

Goods delivered

Customer

Carrier

Receiving advice Customer

Figure 21 Use Case Diagram – Goods delivered

Carrier

Supplier

Supplier

Proof of delivery

ESIDEL – Shipping cycle

52

Use case description – goods delivered Business process name

Goods delivered

Identifier EUROFER: goods delivered Actors Customer

Carrier Supplier

Description This process starts with the reception of the transport and the customer shall provide to the carrier a signed waybill, confirming the received goods and if relevant the damage report. As a proof that the goods are delivered to the customer, the carrier shall send a copy of signed waybill to the supplier. Once the customer has received the goods, the customer will check these goods with the goods advised in the despatch advice or packing list. The customer will send the supplier the confirmation of the reception of the goods according the despatch advice or packing list, or advice only on the received goods.

Pre-condition There is a need to have information about the reception of the transport and the goods. Post-condition The goods received are accepted by the customer. Scenario

Starts when there is a need to receive information about the reception of the transport and the received goods: - The customer raises and sends the proof of delivery to the carrier to confirm the

reception of the transported goods at the shipping to location. - The carrier receives the proof of delivery. - The customer raises and sends the receiving advice to the supplier to confirm the

received goods or the mention discrepancies between the received goods and the announced goods in the despatch advice or packing list.

- The supplier receives the receiving advice.

Alternative scenarios

Remarks 3.4.14. Activity diagram – goods delivered (proof of delivery)

Start of Goods delivered

Receives the Proof of delivery

Proof of delivery

CarrierCustomer

End of step 1 of goods delivered

Raises the Proof of delivery

ESIDEL – Shipping cycle

53

Activity diagram – goods delivered (receiving advice) Figure 22. Business domain activity diagram – Goods delivered Activity diagram description – Goods delivered The customer raises and sends to the carrier the proof of collection to confirm the received goods and if relevant a damage report. The customer raises and sends to the supplier the receiving advice to confirm the received goods and the discrepancies between the received goods and the announced goods in the despatch advice or packing list. 3.4.15. Business collaboration – goods delivered

The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Start of step 2 of Goods delivered

Receives the Receiving advice

Receiving advice

SupplierCustomer

End of goods delivered

Raises the Receiving advice

ESIDEL – Shipping cycle

54

Business Collaboration

Identifier EUROFER: Goods delivered (step 1)

Description The customer raises and sends a proof of delivery to the carrier to confirm the goods received with the transport. Once the carrier received the proof of delivery, step 1 of the process ends.

Partner Types Customer Carrier

Authorized Roles Customer Carrier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport has been received at the shipping to location

• Terminal: the goods are accepted by the customer

Scope To report on the received goods to the carrier.

Boundary Not defined yet

Constraints

Business Collaboration

Identifier EUROFER: Goods delivered (step 2)

Description The customer raises and sends a receiving advice to the supplier to inform about the goods received and the discrepancies between the goods received and announced in the despatch advice or packing list. Once the supplier received the receiving advice, the process ends.

Partner Types Customer Supplier

Authorized Roles Customer Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport and the goods are received by the customer

• Terminal: the goods are accepted by the customer

Scope To report on the goods received to the supplier.

Boundary Not defined yet

Constraints

ESIDEL – Shipping cycle

55

In a business collaboration agreement between the customer and the carrier, the way of using the proof of delivery can be described. The following transactions concerning the proof of delivery can be specified as:

-1. The customer generates and sends the proof of delivery to the carrier. The carrier has to give an acknowledge of receipt of the proof of delivery.

-2. The supplier/customer generates and sends the proof of delivery to the carrier. No acknowledgement message is used between the parties.

In a business collaboration agreement between the customer and the supplier, the way of using the receiving advice can be described. The following transactions concerning the receiving advice can be specified as:

-1. The customer generates and sends the receiving advice to the supplier, the supplier has to give an acknowledge of receipt of the receiving advice.

-2. The customer generates and sends the receiving advice to the supplier. No acknowledgement message is used between the parties.

Part 1 of the Business collaboration: Goods delivered / proof of delivery Figure 23. Business transaction activity graph – Goods delivered (step 1)

Proof of delivery

Produce Proof of delivery

[CONTROLFAIL]

[SUCCESS]

Process Proof of delivery

Carrier Customer

START

END

ESIDEL – Shipping cycle

56

Form: Business Transaction Transition Table

From Id EUROFER: Goods delivered (step 1) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce proof of

delivery Customer NONE

Produce proof of delivery

Customer Proof of delivery Process proof of delivery

Carrier NONE

Produce proof of delivery

Customer N/A SUCCESS N/A Proof of delivery received

Produce proof of delivery

Customer N/A CONTROLFAIL N/A Proof of delivery not received

Part 2 of the Business collaboration: Goods delivered/ receiving advice Figure 24. Business transaction activity graph – Goods delivered (step 2)

Form: Business Transaction Transition Table From Id EUROFER: Goods delivered (step 2) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce receiving

advice Customer NONE

Produce receiving advice

Customer Receiving advice Process receiving advice

Supplier NONE

Produce receiving advice

Customer N/A SUCCESS N/A Receiving advice received

Produce receiving advice

Customer N/A CONTROLFAIL N/A Receiving advice not received

Receiving advice

Produce Receiving advice

[CONTROLFAIL]

[SUCCESS]

Process receiving advice

Supplier Customer

START

END

ESIDEL – Shipping cycle

57

3.4.16. Business transactions and authorized roles – Goods delivered

The goal of the Business transactions is to identify the individual transactions that implement the operations of a business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

3.4.16.1. Business transactions and authorized roles – Proof of delivery

Business Transaction

Description The proof of delivery.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Goods delivered (step 1)

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer

Initiating/Requesting Activity Document

Proof of delivery

Business document

- PROOF OF DELIVERY EUROFER decided not to develop for the moment the Message Guideline for the transaction

ESIDEL – Shipping cycle

58

3.4.16.2. Business transactions and authorized roles – Receiving advice

Business Transaction

Description The Receiving advice.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Goods delivered (step 2)

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer

Initiating/Requesting Activity Document

Receiving advice

Business document

- RECEIVING ADVICE See EUROFER Message Guideline RECEIVING ADVICE

ESIDEL – Shipping cycle

59

3.5. Use case: Despatch & receiving process: direct shipping between

supplier and customer – transport service ordered by the customer

The use case for the despatch & receiving process has the following processes and business transactions:

- Process: Despatch of goods - Transaction: Shipping advice

Waybill Proof of collection Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery Receiving advice.

Use case diagram – despatch & receiving process: direct shipping between supplier and customer

- transport service ordered by the customer

Despatch & receiving process

Despatch & receiving

CustomerSupplier

Goods in transit

Customer

Supplier

Figure 25 Use Case Diagram – Despatch & receiving process: direct shipping between supplier and customer – transport service ordered by customer

Carrier

Despatch of goods

Goods delivered

ESIDEL – Shipping cycle

60

Remark: The use case for the direct shipping between supplier and customer when the

transport services are ordered by the customer is very close to the use case mentioned in chapter 3.4 when the transport services are ordered by the supplier.

The business process ‘ordering transport services’ is not present in this case, because this process is a standalone process between the customer and the carrier, carried before the despatch & receiving process is started. The ordering transport service process will be part of the business process ‘Selection of goods’ and will fit normally between the Goods ready for despatch and the Instruction to despatch (see chapter 2.3). As all the other processes are the same as in chapter 3.4, please refer to the information provided in chapter 3.4 for the activity diagrams, business collaborations and business transactions.

ESIDEL – Shipping cycle

61

3.6. Use case: despatch & receiving process: indirect shipping between supplier and customer by using a third party warehouse Remark: Not to repeat for the indirect shipping process, the use case, the activity diagram, the business collaborations and the business transactions already described in previous chapters or in the Scheduling cycle, Eurofer decided to specify in detail the use case diagram and to highlight and to describe in detail the difference between the presented process and the direct shipping process between the supplier and the customer. The differences are marked with an ‘*’ and, or put in red. This process is used in the European automotive industry on request of the customer, to reduce their own stock of steel products and to guarantee a just in time delivery. In this case the supplier is responsible for the movement of the goods to the warehouse, based on the delivery schedule received from the customer. The goods at the third party warehouse are still the ownership of the supplier. The customer is responsible for the movement of the goods from the warehouse to the customer. In this shipping process the warehouse is acting as a service provider on behave of the supplier and the customer. To make it easy to understand this process has been divided in two steps. The first step is the shipping of the goods from the supplier to the warehouse organised by the supplier. The second step is the shipping of the goods from the warehouse to the supplier on request of the customer. In the first step the following processes and business transactions are addressed:

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery * Inventory of received goods at the warehouse.

ESIDEL – Shipping cycle

62

In the second step the following processes and business transactions are addressed: * - Process: Delivery instructions * - Transaction: Delivery just in time

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection Despatch advice and, or packing list

* Inventory of despatched goods. - Process: Goods in transit

- Transaction: Transport status Pre-arrival notification

- Process: Goods delivered - Transaction: Proof of delivery

* Inventory of received goods at the customer

ESIDEL – Shipping cycle

63

Use case diagram – despatch & receiving process: indirect shipping between supplier and

Customer by using a third party warehouse (step 1)

For the despatch of the goods from the supplier to the third party warehouse, the same process is used as specified in chapter 3.4. In this process the role of the customer is taken over by the third party warehouse. The only difference is situated in the Goods delivered process, where the business transaction ‘Receiving advice’ is replaced by the business transaction ‘Inventory movement’ from the warehouse to the supplier and a copy to the customer, to report on the received goods.

Despatch & receiving process

Despatch & receiving

WarehouseSupplier

Goods in transit

Warehouse

Supplier

Figure 26 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by using a third party warehouse (step1)

Carrier

Despatch of goods

Goods delivered

Ordering transport services

Customer

ESIDEL – Shipping cycle

64

Use case description – despatch & receiving process supplier – warehouse Business process name

Despatch & receiving process supplier – warehouse (step 1 of indirect shipping)

Identifier EUROFER: Despatch & receiving process supplier - warehouse Actors Supplier,

Carrier Warehouse, Customer

Description The transport ordering party (supplier) recognises a need to despatch goods to the third party warehouse. The supplier orders a transport service to the carrier, and the carrier transports the goods from the supplier to the third party warehouse. During the transport the carrier can inform the supplier and warehouse on the transport status. Once the transport is done, the warehouse should inform the supplier and the customer of the goods delivered to the warehouse.

Pre-condition There is a need to deliver goods to the third party warehouse. Post-condition The warehouse shall wait for further delivery instructions to deliver the received goods to

the customer. Scenario

Starts when there is a need to despatch goods from a shipping from location (supplier) to a shipping to location (warehouse). The use case is composed of the following processes: Process 1: Ordering transport services - This process is carried out between the supplier and the carrier and is the same as

described in chapter 3.4.1 Process 2: Despatch of goods - This process is carried out between the supplier, the warehouse and the carrier. It is the

same process as described in chapter 3.4.5. but the role of the customer is taken by the warehouse

Process 3: Goods in transit - This process is carried out between the carrier, the supplier and the warehouse. It is the

same process as described in chapter 3.4.9. but the role of the customer is taken by the warehouse.

Process 4: Goods delivered - Being different from the process described in chapter 3.4.13. the details of this process

are presented in chapter 3.6.1. starting with the use case diagram. Alternative scenarios

Remarks

ESIDEL – Shipping cycle

65

Use case diagram – despatch & receiving process: indirect shipping between supplier and

Customer by using a third party warehouse (step 2)

For the despatch of the goods from the warehouse to the customer, the same process is used as specified in chapter 3.4 with in front the Delivery instructions process described in the Scheduling cycle (Just in time process). In the Delivery instructions process the transactions are carried out between the customer and the warehouse acting in the role of the supplier. In the four other processes as shown in the use case diagram, the warehouse is now acting in the role of the supplier. A difference is situated in the Despatch of goods process, where the business transaction ‘Inventory movement’ is added to inform the supplier about the good despatched from the warehouse to the customer. Another difference is situated in the Goods delivered process, where the business transaction ‘Receiving advice’ is replaced by the business transaction ‘Inventory movement’ from the customer to the warehouse to inform about the goods received.

Despatch & receiving process

Despatch & receiving

CustomerWarehouse

Goods in transit

Customer

Warehouse

Figure 27 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by using a third party warehouse (step2)

Carrier

Despatch of goods

Goods delivered

Ordering transport services

Supplier

Delivery instructions

ESIDEL – Shipping cycle

66

Use case description – despatch & receiving process warehouse - customer

Business process use case

Business process name

Despatch & receiving process warehouse - customer (step 2 of indirect shipping)

Identifier EUROFER: Despatch & receiving process warehouse – customer Actors Supplier,

Carrier Warehouse, Customer

Description The customer recognises a need to receive goods from the third party warehouse. The customer raises to the warehouse Delivery instructions, to specify the goods to be delivered from the warehouse. Based on the agreement between the customer and the warehouse the warehouse or the customer shall orders a transport service to the carrier. The carrier transports the goods from the third party warehouse to the customer. When the goods left the warehouse, the warehouse has the obligation to inform the supplier about the goods despatched to the customer. During the transport the carrier can inform the customer and warehouse on the transport status. Once the transport is done, the customer should inform the warehouse of the goods delivered to the customer.

Pre-condition There is a need to deliver goods to the customer. Post-condition The goods delivered are accepted by the customer. Scenario

Starts when there is a need to despatch goods from a shipping from location (warehouse) to a shipping to location (customer). The use case is composed of the following processes: Process 1: delivery instructions - This process is carried out between the customer and the warehouse and is the same as

described in the document ‘Scheduling cycle’ under the chapter ‘Business process definition – just in time delivery process

Process 2: Ordering transport services - Based on the agreement between the customer and the warehouse, the responsibility of

organising the transport can be dedicated to the warehouse or to the customer. Depending on this responsibility the Ordering transport services process is carried out between the carrier and the warehouse or the customer. This process is the same as described in chapter 3.4.1

Process 3: Despatch of goods - This process is carried out between the warehouse, the customer, the carrier and the

supplier. The supplier is only involved in this process to receive the information of the goods despatched from the warehouse to the customer. Being different from the process described in chapter 3.4.5. the details of this process are presented in chapter 3.6.2.

Process 4: Goods in transit - This process is carried out between the carrier, the customer and the warehouse. It is

the same process as described in chapter 3.4.9. but the role of the supplier is taken by the warehouse.

Process 5: Goods delivered - Being different from the process described in chapter 3.4.13. the details of this process

are presented in chapter 3.6.3. starting with the use case diagram. Alternative scenarios

Remarks

ESIDEL – Shipping cycle

67

3.6.1. Use case: Goods delivered in warehouse The use case for the goods delivered process has the following business transactions:

- The proof of delivery - The inventory of received goods at the warehouse.

Use case diagram – goods delivered in warehouse

Goods delivered

Goods delivered

Warehouse

Carrier

Inventory of received goodsWarehouse

Figure 28 Use Case Diagram – Goods delivered in warehouse

Carrier

Supplier

Supplier

Proof of delivery

Customer

Customer

ESIDEL – Shipping cycle

68

Use case description – goods delivered in warehouse Business process name

Goods delivered in warehouse

Identifier EUROFER: goods delivered in warehouse Actors Warehouse

Carrier Supplier

Description This process starts with the reception of the transport and the warehouse shall provide to the carrier a signed waybill, confirming the received goods and if relevant the damage report. As a proof that the goods are delivered to the warehouse, the carrier shall send a copy of signed waybill to the supplier. Once the warehouse has received the goods, the warehouse will check these goods with the goods advised in the despatch advice or packing list. The warehouse will send the supplier the inventory movement to confirm the reception of the goods.

Pre-condition There is a need to have information about the reception of the transport and the goods. Post-condition The goods received are accepted by the warehouse. Scenario

Starts when there is a need to receive information about the reception of the transport and the received goods: - The warehouse raises and sends the proof of delivery to the carrier to confirm the

reception of the transported goods at the shipping to location. - The carrier receives the proof of delivery. - The warehouse raises and sends the inventory movement to confirm the received goods

to the supplier and the customer. - The supplier and the customer receive the inventory report of the received goods.

Alternative scenarios

Remarks 3.6.1.1. Activity diagram – goods delivered (proof of delivery)

Start of Goods delivered

Receives the Proof of delivery

Proof of delivery

CarrierWarehouse

End of step 1 of goods delivered

Raises the Proof of delivery

ESIDEL – Shipping cycle

69

Activity diagram - goods delivered (inventory of received goods) Figure 29. Business domain activity diagram – Goods delivered at warehouse Activity diagram description – Goods delivered The warehouse raises and sends to the carrier the proof of collection to confirm the received goods and if relevant a damage report. The warehouse raises and sends to the supplier the inventory movement to confirm the received goods. 3.6.1.2. Business collaboration – goods delivered at warehouse The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships. Only the business collaboration between the warehouse and the supplier is detailed below because it is different from the collaboration specified in chapter 3.4.15

Start of step 2 of Goods delivered

Receives the Inventory movement

(received goods)

Inventory movement

(received goods)

Supplier &

Customer

Warehouse

End of goods delivered

Raises the Inventory movement

(received goods)

ESIDEL – Shipping cycle

70

Business Collaboration

Identifier EUROFER: Goods delivered in warehouse (step 2)

Description The warehouse raises and sends an inventory movement to the supplier to inform about the goods received. Once the supplier received the inventory movement, the process ends.

Partner Types Warehouse Supplier Customer

Authorized Roles Warehouse Supplier Customer

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the transport and the goods are received by the warehouse

• Terminal: the goods are accepted by the warehouse

Scope To report on the goods received to the supplier.

Boundary Not defined yet

Constraints

In a business collaboration agreement between the warehouse and the supplier, the way of using the inventory movement to report of received goods can be described. The following transactions concerning the inventory movement can be specified as:

-1. The warehouse generates and sends the inventory movement to report of received goods to the supplier, the supplier has to give an acknowledge of receipt of the inventory movement.

-2. The warehouse generates and sends the inventory movement to report of received goods to the supplier. No acknowledgement message is used between the parties.

ESIDEL – Shipping cycle

71

Part 2 of the Business collaboration: Goods delivered/ inventory report Figure 30. Business transaction activity graph – Goods delivered to warehouse (step 2)

Form: Business Transaction Transition Table From Id EUROFER: Goods delivered to warehouse (step 2) From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce inventory

movement (received goods)

Warehouse NONE

Produce inventory movement (received goods)

Warehouse Inventory movement (received goods)

Process Inventory movement (received goods)

Supplier NONE

Produce inventory movement (received goods)

Warehouse N/A SUCCESS N/A Inventory movement received

Produce inventory movement (received goods)

Warehouse N/A CONTROLFAIL N/A Inventory movement not received

Inventory movement

(received goods)

Produce Inventory movement (received goods)

[CONTROLFAIL]

[SUCCESS]

Process Inventory movement (received goods)

Supplier Warehouse

START

END

ESIDEL – Shipping cycle

1

3.6.1.3. Business transactions and authorized roles – Inventory movement to report of received goods

Business Transaction

Description The Inventory movement to report of received goods.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Goods delivered at warehouse (step 2)

Constraints Not defined yet

Initiating/Requesting Partner Type

Warehouse

Initiating/Requesting Activity Role

Warehouse

Initiating/Requesting Activity Document

Inventory movement

Business document

- INVENTORY MOVEMENT TO REPORT ON RECEIVED GOODS See EUROFER Message Guideline INVENTORY MOVEMENT

ESIDEL – Shipping cycle

2

3.6.2. Use case: Despatch of goods warehouse - customer The use case for the despatch of goods process has the following business transactions:

- The shipping advice or waybill - The proof of collection - The despatch advice and, or packing list - The inventory of despatched goods.

This is the same use case as described in chapter 3.4.5. Only the business transaction ‘Inventory of despatched goods’ is added and is detailed below. Use case diagram – despatch of goods warehouse – customer

Despatch of goods

Transport document (shipping

advice/waybill)

Despatch of goods

Supplier

Carrier

Proof of collection Warehouse

Figure 31 Use Case Diagram – Despatch of goods warehouse - customer

Carrier

Customer

CustomerDespatch advice

or packing list

Warehouse

Inventory despatched

goods

Supplier

ESIDEL – Shipping cycle

3

Use case description – despatch of goods warehouse - customer Business process name

Despatch of goods warehouse – customer

Identifier EUROFER: Despatch of goods warehouse – customer Actors Warehouse,

Carrier Customer, Supplier

Description The transport ordering party recognises a need to despatch goods and send the contracted carrier the necessary transport documents depending on the mode of transport and legal obligations. The carrier receives the transport documents and collects the goods at the shipping from location. As a proof of collection of the goods, the warehouse receives from the carrier the signed transport document. At that moment or on the departure of the means of transport the warehouse will send a despatch advice and, or a packing list to the customer. When the goods are despatched from the warehouse, the warehouse will send an inventory movement to report on the despatched goods to the supplier.

Pre-condition There is a need to deliver goods from the warehouse to the customer. Post-condition The despatched goods are transported to the shipping to location. Scenario

Starts when there is a need to despatch goods from a shipping from location (warehouse) to a shipping to location (customer) and the transport booking is confirmed: - The warehouse (or customer) raises and sends the transport documents required for the

means of transport and the legal obligations to a carrier. - The carrier receives a transport documents and shall collect the goods at the shipping

from location, as a proof of collection he will send a signed transport document to the warehouse.

- The warehouse generates a despatch advice and, or a packing list to inform the customer about the transport and the goods despatched (consignment).

- The customer receives the despatch advice and or packing list and based on the information received, he can organise the reception of the goods.

- The warehouse generates a inventory movement to report on the despatched goods to inform the supplier of the goods shipped to the customer.

Alternative scenarios

Remarks 3.6.2.1. Activity diagram – despatch of goods (inventory of despatched goods) Figure 32. Business domain activity diagram – Inventory of despatched goods

Start of Inventory of despatched goods

Receives the Inventory movement

(dispatched goods)

Inventorymovement

(dispatched goods)

SupplierWarehouse

End of Inventory of despatched goods

Raises the inventory movement

(despatched goods)

ESIDEL – Shipping cycle

4

Activity diagram description – Inventory of despatched goods The warehouse raises and sends to the supplier the inventory movement to inform about the goods shipped to the customer. 3.6.2.2. Business collaboration – goods despatched to the customer The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Business Collaboration

Identifier EUROFER: Goods despatched to the customer

Description The warehouse raises and sends an inventory movement to the supplier to inform about the goods despatched to the customer. Once the supplier received the inventory movement, the process ends.

Partner Types Warehouse Supplier

Authorized Roles Warehouse Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the goods are despatched from the warehouse to the customer

• Terminal: Inventory movement received by the supplier

Scope To report on the goods despatched from the warehouse to the customer.

Boundary Not defined yet

Constraints

In a business collaboration agreement between the warehouse and the supplier, the way of using the inventory movement to report on despatched goods can be described. The following transactions concerning the inventory report can be specified as:

-1. The warehouse generates and sends the inventory movement to report on the despatched goods to the supplier, the supplier has to give an acknowledge of receipt of the inventory report.

-2. The warehouse generates and sends the inventory movement to report on the despatched goods to the supplier. No acknowledgement message is used between the parties.

ESIDEL – Shipping cycle

5

Figure 33. Business transaction activity graph – Inventory of despatched goods

Form: Business Transaction Transition Table From Id EUROFER: Inventory of despatched goods From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce inventory

movement (despatched goods)

Warehouse NONE

Produce inventory movement (despatched goods)

Warehouse Inventory movement (despatched goods)

Process Inventory movement (despatched goods)

Supplier NONE

Produce inventory movement (despatched goods)

Warehouse N/A SUCCESS N/A Inventory movement received

Produce inventory movement (despatched goods)

Warehouse N/A CONTROLFAIL N/A Inventory movement not received

Inventory movement

(despatched goods)

Produce Inventory movement (despatched goods)

[CONTROLFAIL]

[SUCCESS]

Process Inventory movement (despatched goods)

Supplier Warehouse

START

END

ESIDEL – Shipping cycle

6

3.6.2.3. Business transactions and authorized roles – Inventory report of despatched goods

Business Transaction

Description The Inventory movement to report on despatched goods.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Inventory of despatched goods

Constraints Not defined yet

Initiating/Requesting Partner Type

Warehouse

Initiating/Requesting Activity Role

Warehouse

Initiating/Requesting Activity Document

Inventory movement

Business document

- INVENTORY MOVEMENT TO REPORT ON DESPATCHED GOODS See EUROFER Message Guideline INVENTORY MOVEMENT

ESIDEL – Shipping cycle

7

3.6.3. Use case: Goods delivered by customer The use case for the goods delivered process has the following business transactions:

- The proof of delivery - The inventory of received goods by the customer.

This is the same process as used for the Goods delivered at the warehouse specified in chapter 3.6.1. Only the roles of the parties involved have changed due to the fact that the customer is now the receiving party. Use case diagram – goods delivered by the customer

Goods delivered

Goods delivered

Customer

Carrier

Inventory of received goodsCustomer

Figure 34 Use Case Diagram – Goods delivered by customer

Carrier

Warehouse

Warehouse

Proof of delivery

ESIDEL – Shipping cycle

8

Use case description – goods delivered by customer Business process name

Goods delivered in warehouse

Identifier EUROFER: Goods delivered by customer Actors Customer

Carrier Warehouse

Description This process starts with the reception of the transport and the customer shall provide to the carrier a signed waybill, confirming the received goods and if relevant the damage report. As a proof that the goods are delivered to the customer, the carrier shall send a copy of signed waybill to the warehouse. Once the customer has received the goods, the customer will check these goods with the goods advised in the despatch advice or packing list. The customer will send the warehouse the inventory movement to confirm the reception of the goods.

Pre-condition There is a need to have information about the reception of the transport and the goods. Post-condition The goods received are accepted by the customer. Scenario

Starts when there is a need to receive information about the reception of the transport and the received goods: - The customer raises and sends the proof of delivery to the carrier to confirm the

reception of the transported goods at the shipping to location. - The carrier receives the proof of delivery. - The customer raises and sends the inventory movement to confirm the received goods. - The warehouse receives the inventory movement of the received goods.

Alternative scenarios

Remarks

ESIDEL – Shipping cycle

80

3.7. Use case: Despatch & receiving process: indirect shipping between supplier and customer by using the customer consignment stock

Remark: Not to repeat for the indirect shipping process, the use case, the activity diagram, the business collaborations and the business transactions already described in previous chapters, Eurofer decided to specify in detail the use case diagram and to highlight and to describe in detail the difference between the presented process and the direct shipping process between the supplier and the customer. The differences are marked with a ‘*’ and, or put in red. This process is used by the automotive industry on request of the customer, to reduce their own stock of steel products and to guarantee a just in time delivery. In this case the supplier is responsible for the movement of the goods to the warehouse, based on the delivery schedule or the delivery just in time messages received from the customer. The goods at the consignment stock are still the ownership of the supplier. The customer is responsible for the movement of the goods from the consignment stock to the customers’ warehouse or production line. Based on the customers’ production need, the customer will take the goods out of the consignment stock. To make it easy to understand this process has been divided in two steps. The first step dealing with the shipping of the goods from the supplier to the consignment stock at the customer organised by the supplier. The second step explains the usage of the goods by the customer. In the first step the following processes and business transactions are addressed:

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery * Inventory of received goods at the warehouse.

In the second step the following processes and business transactions are addressed: * - Process: Usage of the goods of the consignment stock * - Transaction: Inventory of the outgoing goods

ESIDEL – Shipping cycle

81

Use case diagram – despatch & receiving process: indirect shipping between supplier and

customer by using the customer consignment stock (step 1)

For the despatch of the goods from the supplier to the customer consignment stock, the same process is used as specified in chapter 3.4. The only difference is situated in the Goods delivered process, where the business transaction ‘Receiving advice’ is replaced by the business transaction ‘Inventory of received goods’ from the customer to the supplier.

Despatch & receiving process

Despatch & receiving

CustomerSupplier

Goods in transit

Customer

Supplier

Figure 31 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by using the customer consignment stock (step1)

Carrier

Despatch of goods

Goods delivered

Ordering transport services

ESIDEL – Shipping cycle

82

Use case description – despatch & receiving process supplier – customer consignment stock Business process name

Despatch & receiving process supplier – customer consignment stock (step 1 of indirect shipping)

Identifier EUROFER: Despatch & receiving process supplier – customer consignment stock Actors Supplier,

Carrier Customer

Description The transport ordering party (supplier) recognises a need to despatch goods to the customer consignment stock. The supplier orders a transport service to the carrier, and the carrier transports the goods from the supplier to the customer. During the transport the carrier can inform the supplier and customer on the transport status. Once the transport is done, the customer should inform the supplier of the goods delivered to the customer consignment stock.

Pre-condition There is a need to deliver goods to the customer consignment stock. Post-condition The customer shall receive instructions to move the goods out of the consignment stock to

the customers’ warehouse or the production line. Scenario

Starts when there is a need to despatch goods from a shipping from location (supplier) to a shipping to location (customer consignment stock). The use case is composed of the following processes: Process 1: Ordering transport services - This process is carried out between the supplier and the carrier and is the same as

described in chapter 3.4.1 Process 2: Despatch of goods - This process is carried out between the supplier, the customer and the carrier. It is the

same process as described in chapter 3.4.5. Process 3: Goods in transit - This process is carried out between the carrier, the supplier and the customer. It is the

same process as described in chapter 3.4.9. Process 4: Goods delivered - This process is carried out between the customer, the carrier and the supplier. Its is the

same process as described in chapter 3.6.1 but the role of the warehouse is taken over by the customer.

Alternative scenarios

Remarks

ESIDEL – Shipping cycle

83

3.7.1. Use case: Usage of goods Use case diagram – despatch & receiving process: indirect shipping between supplier and

customer by using the customer consignment stock (step 2)

For the reporting of the usage of goods a new process is used by the customer, to inform the supplier of the goods taken out of the consignment stock.

Usage of goods

Usage of goods

CustomerSupplier

Customer Supplier

Figure 35 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by using the customer consignment stock (step2)

Inventory of outgoing goods

ESIDEL – Shipping cycle

1

Use case description – despatch & receiving process – usage of goods of the consignment stock Business process name

Despatch & receiving process – usage of goods of the consignment stock (step 1 of indirect shipping)

Identifier EUROFER: Despatch & receiving process – usage of goods of the consignment stock Actors Supplier,

Customer Description The customer recognises a need to use for his own production line goods available in the

consignment stock. The customer takes out the needed goods and informed the supplier of the outgoing goods of the consignment stock.

Pre-condition There is a need to use goods available in the consignment stock. Post-condition The supplier can invoice the goods taken out by the customer of the consignment stock. Scenario

Starts when there is a need to use goods available in the consignment stock: - The customer raises and sends an inventory movement of outgoing goods to the

supplier to report on the goods taken by the customer.

Alternative scenarios

Remarks 3.7.2 Outgoing goods 3.7.2.1. Activity diagram - Usage of the goods of the consignment stock Figure 36. Business domain activity diagram – Usage of the goods of the consignment stock Activity diagram description – Inventory of outgoing goods The customer raises and sends to the supplier the inventory movement to inform about the goods used by the customer.

Start of Usage of the goods

Receives the Inventorymovement

(outgoing goods)

Inventory movement

(outgoing goods)

SupplierCustomer

End of Usage of the goods

Raises the inventory movement

(outgoing goods)

ESIDEL – Shipping cycle

2

3.7.2.2. Business collaboration – Inventory of outgoing goods The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Business Collaboration

Identifier EUROFER: Inventory of outgoing goods

Description The customer raises and sends an inventory movement of outgoing goods of the consignment stock to the supplier to inform about the goods used by to the customer. Once the supplier received the inventory movement, the process ends.

Partner Types Customer Supplier

Authorized Roles Customer Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the goods of the consignment stock are used by the customer

• Terminal: Inventory movement received by the supplier

Scope To report on the goods used by the customer.

Boundary Not defined yet

Constraints

In a business collaboration agreement between the customer and the supplier, the way of using the inventory movement of outgoing goods can be described. The following transactions concerning the inventory movement can be specified as:

-1. The customer generates and sends the inventory movement of outgoing goods to the supplier, the supplier has to give an acknowledge of receipt of the inventory movement.

-2. The customer generates and sends the inventory movement of outgoing goods to the supplier. No acknowledgement message is used between the parties.

ESIDEL – Shipping cycle

3

Figure 37. Business transaction activity graph – Inventory of ougoing goods

Form: Business Transaction Transition Table From Id EUROFER: Inventory of outgoing goods From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce inventory

movement (outgoing goods)

Customer NONE

Produce inventory movement (outgoing goods)

Customer Inventory movement (outgoing goods)

Process Inventory movement (outgoing goods)

Supplier NONE

Produce inventory movement (outgoing goods)

Customer N/A SUCCESS N/A Inventory movement received

Produce inventory movement (outgoing goods)

Customer N/A CONTROLFAIL N/A Inventory movement not received

Inventory movement

(outgoing goods)

Produce Inventory movement (outgoing goods)

[CONTROLFAIL]

[SUCCESS]

Process Inventory movement (outgoing goods)

Supplier Customer

START

END

ESIDEL – Shipping cycle

4

3.7.2.3. Business transactions and authorized roles – Inventory movement of outgoing goods

Business Transaction

Description The Inventory movement to report on outgoing goods.

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Inventory of outgoing goods

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer

Initiating/Requesting Activity Document

Inventory movement

Business document

- INVENTORY MOVEMENT TO REPORT ON OUTGOING GOOGS See EUROFER Message Guideline INVENTORY MOVEMENT

ESIDEL – Shipping cycle

88

3.8. Use case: Despatch & receiving process: indirect shipping between supplier and customer by using an external warehouse controlled by the supplier

Remark: Not to repeat for the indirect shipping process, the use case, the activity diagram, the business collaborations and the business transactions already described in previous chapters or in the Scheduling cycle, Eurofer decided to specify in detail the use case diagram and to highlight and to describe in detail the difference between the presented process and the direct shipping process between the supplier and the customer. The differences are marked with a ‘*’ and, or put in red. This process is used in the European automotive industry for strategic reasons, allowing short delivery time to the customer. In this process the supplier is responsible for the movement of goods to the external warehouse, based on the order or the delivery instructions of the customer. The goods in the external warehouse are still the ownership of the supplier. On request of the customer to deliver the goods; the supplier will arrange the shipping of goods from the warehouse to the customer. Therefore he has to inform the warehouse keeper about the goods to be shipped. Based on the service contract, the supplier or the warehouse is responsible for the ordering of the transport services. To make it easier to understand this process has been divided in two parts, the first dealing with the shipping process from the supplier to the warehouse, the second explains the shipping process from the warehouse to the customer The shipping process from the supplier to the warehouse is completely the same process as described as first step in chapter 3.6. In the first step the following processes and business transactions are addressed:

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery Inventory of received goods at the warehouse.

ESIDEL – Shipping cycle

89

In the second step the following processes and business transactions are addressed: * - Process: Delivery instructions * - Transaction: Delivery just in time * - Process: Despatch instructions * Instruction to despatch

- Process: Ordering of transport services - Transaction: Transport booking request

Transport booking confirmation - Process: Despatch of goods

- Transaction: Shipping advice Waybill Proof of collection

* Despatch confirmation Despatch advice and, or packing list

- Process: Goods in transit - Transaction: Transport status

Pre-arrival notification - Process: Goods delivered

- Transaction: Proof of delivery Receiving advice

ESIDEL – Shipping cycle

90

Use case diagram – despatch & receiving process: indirect shipping between supplier and

Customer by using an external warehouse controlled by the supplier (step 1)

For the despatch of the goods from the supplier to the external warehouse, the same process is used as specified in chapter 3.4. In this process the role of the customer is taken over by external warehouse. The only difference is situated in the Goods delivered process, where the business transaction ‘Receiving advice’ is replaced by the business transaction ‘Inventory of received goods’ from the warehouse to the supplier. In fact it is the same process as detailed in chapter 3.6 - step 1, but the customer do not receive from the warehouse the inventory of received goods at the warehouse.

Despatch & receiving process

Despatch & receiving

WarehouseSupplier

Goods in transit

Warehouse

Supplier

Figure 38 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by external warehouse (step1)

Carrier

Despatch of goods

Goods delivered

Ordering transport services

ESIDEL – Shipping cycle

91

Use case description – despatch & receiving process supplier – warehouse Business process name

Despatch & receiving process supplier – warehouse controlled by supplier (step 1 of indirect shipping)

Identifier EUROFER Despatch & receiving process supplier – warehouse controlled by supplier Actors Supplier,

Carrier Warehouse

Description The transport ordering party (supplier) recognises a need to despatch goods to the external warehouse. The supplier orders a transport service to the carrier, and the carrier transports the goods from the supplier to the external warehouse. During the transport the carrier can inform the supplier and warehouse on the transport status. Once the transport is done, the warehouse should inform the supplier of the goods delivered to the warehouse.

Pre-condition There is a need to deliver goods to the external warehouse. Post-condition The warehouse shall wait for further delivery instructions to deliver the received goods to

the customer. Scenario

Starts when there is a need to despatch goods from a shipping from location (supplier) to a shipping to location (warehouse). The use case is composed of the following processes: Process 1: Ordering transport services - This process is carried out between the supplier and the carrier and is the same as

described in chapter 3.4.1 Process 2: Despatch of goods - This process is carried out between the supplier, the warehouse and the carrier. It is the

same process as described in chapter 3.4.5. but the role of the customer is taken by the warehouse

Process 3: Goods in transit - This process is carried out between the carrier, the supplier and the warehouse. It is the

same process as described in chapter 3.4.9. but the role of the customer is taken by the warehouse.

Process 4: Goods delivered - Being different from the process described in chapter 3.4.13. the details of this process

are presented in chapter 3.6.1. starting with the use case diagram. Notice, that no copy of the inventory report of received goods is send to the customer.

Alternative scenarios

Remarks

ESIDEL – Shipping cycle

92

Use case diagram – despatch & receiving process: indirect shipping between supplier and

Customer by using an external warehouse controlled by the supplier (step 2)

For the despatch of the goods from the warehouse to the customer, the same process is used as specified in chapter 3.4 with in front the Delivery instruction process described in the Scheduling cycle (Just in time process) and followed by the despatch instruction process. In the Delivery instruction process the transactions are carried out between the customer and the supplier. In the Despatch instruction process the supplier informs the warehouse about the goods to be shipped to the customer and the shipping conditions by using the Instruction to despatch. In the four other processes as shown in the use case diagram, the warehouse is now acting in the role of the supplier. A difference is situated in the Despatch of goods process, where the business transaction ‘Despatch confirmation’ is added to inform the supplier about the good despatched from the warehouse to the customer.

Despatch & receiving process

Despatch & receiving

CustomerWarehouse

Goods in transit

Customer

Warehouse

Figure 39 Use Case Diagram – Despatch & receiving process: indirect shipping between supplier and customer by using an external warehouse (step2)

Carrier

Despatch of goods

Goods delivered

Ordering transport services

Supplier

Despatch instructions

Delivery instructions

ESIDEL – Shipping cycle

93

Use case description – despatch & receiving process warehouse - customer Business process name

Despatch & receiving process warehouse - customer controlled by the supplier (step 2 of indirect shipping)

Identifier EUROFER.2002/004: Despatch & receiving process warehouse – customer controlled by the supplier

Actors Supplier, Carrier Warehouse, Customer

Description The customer recognises a need to receive goods from the supplier. The customer raises to the supplier Delivery instructions, to specify the goods to be delivered. As the requested delivery of the customer can be met with goods in the external warehouse, the supplier will raises and sends Instruction to despatch to the warehouse. Based on the agreement between the supplier and the warehouse the warehouse or the supplier shall orders a transport service to the carrier. The carrier transports the goods from the third party warehouse to the customer. When the goods left the warehouse, the warehouse has the obligation to inform the supplier about the goods despatched to the customer. During the transport the carrier can inform the customer and warehouse on the transport status. Once the transport is done, the customer should inform the supplier of the goods received.

Pre-condition There is a need to deliver goods to the customer. Post-condition The goods delivered are accepted by the customer. Scenario

Starts when the customer identifies the need to receive goods ordered. The use case is composed of the following processes: Process 1: delivery instructions - This process is carried out between the customer and the supplier and is the same as

described in the document ‘Scheduling cycle’ under the chapter ‘Business process definition – just in time delivery process

Process 2: despatch instructions - This process is carried out between the supplier and the warehouse and is the same as

described in the chapter 2.3 limited to the Instruction to despatch. Process 3: Ordering transport services - Based on the agreement between the supplier and the warehouse, the responsibility of

organising the transport can be dedicated to the warehouse or to the supplier. Depending on this responsibility the Ordering transport services process is carried out between the carrier and the warehouse or the supplier. This process is the same as described in chapter 3.4.1

Process 4: Despatch of goods - This process is carried out between the warehouse, the customer, the carrier and the

supplier. The supplier is only involved in this process to receive the confirmation of the despatch of the goods despatched from the warehouse to the customer. Being different from the process described in chapter 3.4.5. the details of this process are presented in chapter 3.8.1.

Process 5: Goods in transit - This process is carried out between the carrier, the customer and the warehouse. It is

the same process as described in chapter 3.4.9. but the role of the supplier is taken by the warehouse.

Process 6: Goods delivered - This process is carried out between the customer, the carrier and the supplier and is the

same as described in the chapter 3.4.13. Alternative scenarios

Remarks

ESIDEL – Shipping cycle

94

3.8.1. Use case: Despatch of goods warehouse – customer controlled by supplier The use case for the despatch of goods process has the following business transactions:

- The shipping advice or waybill - The proof of collection - The despatch confirmation. - The despatch advice and, or packing list

This is the same use case as described in chapter 3.4.5. Only the business transaction ‘Despatch confirmation’ is added and is detailed below. Use case diagram – despatch of goods warehouse – customer controlled by supplier

Despatch of goods

Transport document (shipping

advice/waybill)

Despatch of goods

Supplier

Carrier

Proof of collection Warehouse

Figure 40 Use Case Diagram – Despatch of goods warehouse – customer controlled by supplier

Carrier

Customer

Customer

Despatch advice or

packing list

Warehouse

Despatch confirmation

Supplier

ESIDEL – Shipping cycle

95

Use case description – despatch of goods warehouse - customer Business process name

Despatch of goods warehouse – customer controlled by the supplier

Identifier EUROFER: despatch of goods warehouse – customer controlled by the supplier Actors Warehouse,

Carrier Customer, Supplier

Description The transport ordering party recognises a need to despatch goods and send the contracted carrier the necessary transport documents depending on the mode of transport and legal obligations. The carrier receives the transport documents and collects the goods at the shipping from location. As a proof of collection of the goods, the warehouse receives from the carrier the signed transport document. At that moment or on the departure of the means of transport the warehouse will send a despatch confirmation to the supplier. Based on the despatch confirmation the supplier will send a despatch advice and, or a packing list to the customer.

Pre-condition There is a need to deliver goods from the warehouse to the customer. Post-condition The despatched goods are transported to the shipping to location. Scenario

Starts when there is a need to despatch goods from a shipping from location (warehouse) to a shipping to location (customer) and the transport booking is confirmed: - The warehouse (or supplier) raises and sends the transport documents required for the

means of transport and the legal obligations to a carrier. - The carrier receives a transport documents and shall collect the goods at the shipping

from location, as a proof of collection he will send a signed transport document to the warehouse.

- The warehouse generates a despatch confirmation to inform the supplier of the goods shipped to the customer based on the despatch instruction received from the supplier.

- The supplier generates a despatch advice and, or a packing list to inform the customer about the transport and the goods despatched (consignment).

- The customer receives the despatch advice or packing list and based on the information received, he can organise the reception of the goods

Alternative scenarios

Remarks 3.8.1.1. Activity diagram – despatch of goods (despatch confirmation) Figure 41. Business domain activity diagram – Despatch confirmation

Start of confirmation of the despatch

Receives the despatch confirmation

Despatch confirmation

SupplierWarehouse

End of confirmation of the despatch

Raises the despatch confirmation

ESIDEL – Shipping cycle

96

Activity diagram description – Despatch confirmation The warehouse raises and sends to the supplier the despatch confirmation to inform about the goods shipped to the customer. 3.8.1.2. Business collaboration – Despatch confirmation The business collaboration specifies for the abovementioned activity diagram the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

Business Collaboration

Identifier EUROFER: Despatch confirmation

Description The warehouse raises and sends a despatch confirmation to the supplier to inform about the goods despatched to the customer. Once the supplier received the despatch confirmation, the process ends.

Partner Types Warehouse Supplier

Authorized Roles Warehouse Supplier

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the goods are despatched from the warehouse to the customer

• Terminal: Despatch confirmation received by the supplier

Scope To confirm the despatch of goods as requested by the supplier in the despatch instructions.

Boundary Not defined yet

Constraints

In a business collaboration agreement between the warehouse and the supplier, the way of using the despatch confirmation can be described. The following transactions concerning the despatch confirmation can be specified as:

-1. The warehouse generates and sends the despatch confirmation to the supplier, the supplier has to give an acknowledge of receipt of the despatch confirmation.

-2. The warehouse generates and sends the despatch confirmation to the supplier. No acknowledgement message is used between the parties.

ESIDEL – Shipping cycle

97

Figure 42. Business transaction activity graph – Despatch confirmation

Form: Business Transaction Transition Table From Id EUROFER: Despatch confirmation From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Produce Despatch

confirmation Warehouse NONE

Produce Despatch confirmation

Warehouse Despatch confirmation

Despatch confirmation

Supplier NONE

Produce Despatch confirmation

Warehouse N/A SUCCESS N/A Despatch confirmation received

Produce Despatch confirmation

Warehouse N/A CONTROLFAIL N/A Despatch confirmation not received

Despatch confirmation

Produce Despatch confirmation

[CONTROLFAIL]

[SUCCESS]

Process Despatch confirmation

Supplier Warehouse

START

END

ESIDEL – Shipping cycle

98

3.8.1.3. Business transactions and authorized roles – Despatch confirmation

Business Transaction

Description Despatch confirmation

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Despatch confirmation

Constraints Not defined yet

Initiating/Requesting Partner Type

Warehouse

Initiating/Requesting Activity Role

Warehouse

Initiating/Requesting Activity Document

Despatch confirmation

Business document

- DESPATCH CONFIRMATION See EUROFER Message Guideline DESPATCH ADVICE

ESIDEL – Shipping cycle

99

3.9. The stock inventory of the goods in a warehouse This process is used in the European steel industry to receive on agreed time intervals or on request of the supplier, a stock inventory of the goods in the warehouse. The information can be either Be a full inventory or an inventory of a certain product or order. The process comprises the request for an inventory report for full stock or for one or several orders and the Inventory report of the goods in stock. An “electronic work environment (Electronic market place)” may be used as intermediaries to request and distribute the inventory report. To support the stock inventory process the following two messages have been identified:

- Inventory request - Inventory report.

The controlling parties (supplier, or even customer) can initiate a request for an inventory report to the warehouse, asking for information on the goods stored at the warehouse. This request is either directly transmitted or forwarded by an “electronic work environment” to the warehouse. Upon receipt of an inventory request, the warehouse will send to the requesting party an inventory report, reporting on the goods in the warehouse. This report is either directly transmitted or forwarded by an “electronic work environment” to the requesting party. The inventory report can also be sent by the warehouse on regular interval as agreed between the two parties without initiating an inventory request. 3.9.1. Use case: Inventory report process The use case for the order status process phase has the following business transaction:

- Place an inventory request - Provide an inventory report

Use case diagram – Inventory report process

Inventory report

Place inventory request

Inventory report

Supplier Warehouse

Inventory report

Supplier Warehouse

Figure 43 Use Case Diagram – Inventory report process

ESIDEL – Shipping cycle

100

Use case description – inventory report process Business process name

Inventory report process

Identifier EUROFER: Inventory report process Actors Supplier,

Warehouse Description The supplier recognises a need to know the current status of the goods in stock in the

warehouse from the warehouse keeper. The warehouse receives the request and responds with the inventory report.

Pre-condition Supplier has put goods in a warehouse. Post-condition Supplier takes knowledge of the actual status of the goods in the warehouse. With this

knowledge the supplier can synchronise its own information system of the stock or can generate an instruction to despatch to the warehouse.

Scenario

Starts when supplier recognises need to have the current status of goods in the warehouse from the warehouse keeper: - Supplier raises and sends an inventory request containing the parameters for the

selection of all the goods or the goods for one or more order lines, to the warehouse. - Warehouse receives an inventory request. - Warehouse generates an inventory report giving the actual situation the all goods in the

warehouse of for one or more order lines, to the supplier. - Supplier receives the inventory report. The cycle of requesting inventory report and sending inventort report might be executed multiple times.

Alternative scenarios

The warehouse may also provide an inventory report to the supplier at a predefined regular interval and not necessarily in response to an inventory s request.

Remarks

ESIDEL – Shipping cycle

101

3.9.2. Activity diagram – Inventory report process Figure 44. Business domain activity diagram – Inventory report process Activity diagram description – Inventory report process The supplier raises and sends an inventory request containing one or more selection criteria for the orders for which an inventory report is required to the warehouse. When the warehouse receives the inventory request, he selects the relevant goods for the selection criteria and raises the corresponding Inventory report information. As a result the warehouse sends an inventory report to the supplier. Once the supplier received the Inventory report, the scenario ends.

Start of Inventory report process

Raises an Inventory request

Receives Inventory report

Receives Inventory request

Provides Inventory report

Inventory request

Warehouse Supplier

Inventory report

End of Inventory report process

ESIDEL – Shipping cycle

102

Activity diagram - Alternative inventory report process

Figure 45. Activity Diagram – Alternative inventory report process Activity diagram description – Alternative inventory report process Based on an agreement with the supplier, the warehouse raises at a regular interval an Inventory report for the supplier. As a result the warehouse sends an inventory report to the supplier. Once the supplier received the Inventory report, the scenario ends.

Start of Inventory report process

Receives Inventory report Provides

Inventory report

Warehouse Supplier

Inventory report

End of Inventory report process

ESIDEL – Shipping cycle

103

3.9.3. Business collaboration – Inventory report process

The business collaboration specifies for each of the above mentioned activity diagrams the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

3.9.3.1. Business collaboration – Inventory report on request

Business Collaboration

Identifier EUROFER: Inventory report request

Description The supplier raises and sends an inventory report request containing one or more selection criteria for the orders for which an inventory report is required to the warehouse. When the warehouse receives the inventory report request, he selects the relevant goods for the selection criteria and raises the corresponding Inventory report information. As a result the warehouse sends an inventory report to the supplier. Once the supplier received the Inventory report, the scenario ends.

Partner Types Supplier Warehouse

Authorized Roles Supplier Warehouse

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the supplier sends the inventory report request message

• Terminal: the supplier receives the inventory report

Scope To request the inventory report of a defined selection.

Boundary Not defined yet

Constraints The supplier shall have full traceability of his request message to make sure it has been received. Failing this technical acknowledgement, the customer shall re-issue his request message

ESIDEL – Shipping cycle

104

In a business collaboration agreement between the supplier and the warehouse, the way of using the Request for an Inventory report scenario can be described. The following transactions concerning the Inventory report can be specified as:

-1. The supplier generates an Inventory report request to receive an Inventory report. The warehouse has to give an acknowledge of receipt of the Inventory report request.

The warehouse sends an inventory report to the supplier. The supplier acknowledges the receipt of the inventory report to the warehouse.

-2. The supplier generates an Inventory report request to receive an Inventory report, and the warehouse responds directly with the Inventory report. No acknowledgement messages are used between the parties.

Figure 46. Business transaction activity graph – Inventory report request

Form: Business Transaction Transition Table From Id EUROFER: Inventory report request From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Place request for

an inventory report Supplier NONE

Place request for an inventory report

Supplier Inventory report request

Process inventory report request

Warehouse NONE

Process inventory report request

Warehouse Order status Report

Place request for an order status

Supplier NONE

Place request for an inventory report

Supplier N/A SUCCESS N/A Inventory report received

Place request for an inventory report

Supplier N/A CONTROLFAIL N/A Inventory report not received

Inventory report request

Place request for an inventory report

[CONTROLFAIL]

[SUCCESS]

Process inventory report request

Inventory report

Warehouse Supplier

START

END

ESIDEL – Shipping cycle

105

3.9.3.2. Business collaboration – Inventory report on regular basis

Business Collaboration

Identifier EUROFER: Inventory reporting

Description Based on an agreement with the supplier, the warehouse raises at a regular interval an Inventory report for the supplier. As a result the warehouse sends an inventory report to the supplier.

Partner Types Supplier Warehouse

Authorized Roles Supplier Warehouse

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: agreement between the supplier and the warehouse

• Terminal: the supplier receives the inventory report

Scope To give the supplier a regular situation of the goods in the warehouse.

Boundary Not defined yet

Constraints The supplier has an agreement with the warehouse, to send him an inventory report on a regular basis.

In a business collaboration agreement between the supplier and the warehouse, the way of using the Inventory reporting scenario can be described. The transactions concerning the Inventory reporting are limited to the inventory report send by the warehouse to the supplier and the supplier acknowledges the receipt of the inventory report to the warehouse.

ESIDEL – Shipping cycle

106

Figure 47. Business transaction activity graph – Inventory reporting

Form: Business Transaction Transition Table From Id EUROFER: Inventory report From Activity From Role Document To Activity To Role Guard

Condition START N/A N/A Inventory

reporting Warehouse NONE

Inventory reporting

Warehouse Inventory report Process inventory report

Supplier NONE

Inventory reporting

Warehouse N/A SUCCESS N/A Inventory report received

Inventory reporting

Warehouse N/A CONTROLFAIL N/A Inventory report not received

Inventory report

Inventory reporting

[CONTROLFAIL]

[SUCCES

Process Inventory report

Supplier Warehouse

START

END

ESIDEL – Shipping cycle

107

3.9.4. Business transactions and authorized roles – Inventory report process

The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

3.9.4.1. Business transactions and authorized roles – Request Inventory report

Business Transaction

Description The Request Inventory report is used to request an Inventory of certain goods at the warehouse

Pattern Request/Response

Business activities and associated authorized roles

See EUROFER: Inventory report request

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier

Initiating/Requesting Activity Role

Supplier

Initiating/Requesting Activity Document

Inventory report Request

Responding Partner Type Warehouse

Responding Activity Role Warehouse

Responding Activity Document Inventory report

Business document

- INVENTORY REPORT REQUEST See EUROFER Message Guideline INVENTORY REQUEST

- INVENTORY REPORT See EUROFER Message Guideline INVENTORY BALANCE

ESIDEL – Shipping cycle

108

3.9.4.2. Business transactions and authorized roles – Inventory report

Business Transaction

Description The Inventory report is used to report information on the goods in the warehouse

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Inventory report

Constraints Not defined yet

Initiating/Requesting Partner Type

Warehouse

Initiating/Requesting Activity Role

Warehouse

Initiating/Requesting Activity Document

Inventory Report

Business document

- INVENTORY REPORT See EUROFER Message Guideline INVENTORY BALANCE

ESIDEL – Shipping cycle

109

4. Business Process Definition – Certificate/Quality report 4.1. Scope

The Certificate/Quality report process will be used to provide to the customer the certificates and the test reports giving the product details, the chemical, mechanical and other properties as specified in the type of certificate or inspection documents requested by the customer at the Order.

The practice today is, that a certificate/quality report is sent automatically by the supplier at the moment of the despatch of the goods to the customer, or the despatch of goods to the warehouse without initiating a request. Some of the customers have made an agreement with their steel suppliers to provide the Certificate/Quality report when the goods are produced and ready for despatch by the supplier. To use in the future more and more an “electronic work environment” can lead to the need to provide also the certificate/quality report on request of the customer. 4.2. Process definition

The Certificate/Quality report process is the mechanism by which certificates and inspection reports of the goods are requested and provided between the business parties. The process comprises the request for a certificate/quality report for the goods of one or several orders and the certificate/quality report giving the chemical, mechanical and other properties of the goods of one or several orders. An "electronic work environment (Electronic market place)" may be used as intermediaries to request and distribute the certificate/quality report.

To support the Certificate/Quality report process the following two messages have been developed: - Certificate/Quality report request - Certificate/Quality report.

The customer or customer’s agent can initiate a request for a certificate/quality report to the supplier or supplier’s agent, asking for a certificate or an inspection report of existing goods. This request is either directly transmitted or forwarded by an "electronic work environment" to the supplier. Upon receipt of a certificate/quality report request, the supplier or supplier’s agent will send to the customer or customer’s agent a certificate/quality report, reporting information on the chemical, mechanical and other properties of the requested goods. This report is either directly transmitted or forwarded by an "electronic work environment" to the customer.

4.3. Principles

The supplier or supplier’s agent has the obligation to respond with a certificate/quality report to a certificate/quality report request initiated by the customer or customer’s agent.

ESIDEL – Shipping cycle

110

4.4. Use case: Certificate/Quality report process The use case for the certificate/quality report process phase has the following business transaction:

- Place a certificate/quality report request - Provide a certificate/quality report

Use case diagram – certificate/quality report process Certificate/

Quality report

Place Certificate/Quality

report request

Quality data sheet Customer Supplier

Certificate/ Quality report

Customer Supplier

Figure 48 Use Case Diagram – Certificate/Quality report process

ESIDEL – Shipping cycle

111

Use case description – certificate/quality report process Business process name

Certificate/Quality report process

Identifier EUROFER: Certificate /Quality report process Actors Customer,

Supplier Description The Customer recognises a need to receive a certificate or an inspection report of the goods

from the supplier. The Supplier receives the request and responds with the certificate/quality report.

Pre-condition The goods are produced by the supplier and released for the customer and the Certificate or Inspection report type is specified in the Order.

Post-condition Customer takes knowledge of the information provided in the certificate/quality report. Scenario

Starts when customer recognises need to receive the certificate or inspection report from the supplier: - Customer raises and sends a certificate/quality report request containing the parameters

for the selection of the goods of one or more order lines, to supplier. - Supplier receives a certificate/quality report request. - Supplier generates a certificate/quality report giving the product information and the

test results of the selected goods to the customer. - Customer receives the certificate/quality report. The cycle of requesting certificate/quality report and sending the certificate/quality report might be executed multiple times.

Alternative scenarios

The supplier may also provide a certificate/quality report to the customer at predefined events (shipping of goods) not necessarily in response to a Certificate/Quality report request.

Remarks

ESIDEL – Shipping cycle

112

4.5. Activity diagram – Certificate/Quality report process Figure 49. Business domain activity diagram – Certificate/Quality report process Activity diagram description – Certificate/Quality report process The customer raises and sends a certificate/quality report request containing one or more selection criteria for the goods for which a certificate/quality report is required to the supplier. When the supplier receives the certificate/quality report request, he selects the relevant goods and raises the corresponding certificate/quality report information. As a result the supplier sends a certificate/quality report to the customer. Once the customer received the certificate/quality report, the scenario ends.

Start of Certificate/Quality report process

Raises a Certificate/

Quality report request

Receives Certificate/ Quality report

Receives certificate/quality

report request

Provides Certificate/Quality

report

Certificate/Quality report request

SupplierCustomer

Certificate/ Quality report

End of Certificate/Quality report process

ESIDEL – Shipping cycle

113

4.6. Activity diagram - Alternative Certificate/Quality report process Figure 50. Activity Diagram – Alternative certificate/quality report process Activity diagram description – Alternative certificate/quality report process Based on an agreement with the customer, the supplier raises at a regular event a certificate/quality report for the customer. As a result the supplier sends a certificate/quality report to the customer. Once the customer received the certificate/quality report, the scenario ends.

Start of Certificate/Quality report process

Receives Certificate: Quality report Provides

Certificate/ Quality report

SupplierCustomer

Certificate/ Quality report

End of Certificate/Quality report process

ESIDEL – Shipping cycle

114

4.7. Business collaboration - Certificate/Quality report process

The business collaboration specifies for each of the above mentioned activity diagrams the input and output triggers, constrains and system boundaries for the business transactions, business collaboration protocols and their interrelationships.

4.7.1. Business collaboration – Certificate/Quality report on request

Business Collaboration

Identifier EUROFER: Certificate/Quality report request

Description The customer raises and sends a certificate/quality report request containing one or more selection criteria for the goods for which a certificate/quality report is required to the supplier. When the supplier receives the certificate/quality report request, he selects the relevant goods and raises the corresponding certificate/quality report information. As a result the supplier sends a certificate/quality report to the customer. Once the customer received the certificate/quality report, the scenario ends.

Partner Types Customer Supplier

Authorized Roles Customer (Customer’s agent, Buyer or Buyer’s agent) Supplier (Supplier’s agent, Seller or Seller’s agent)

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: the customer sends the certificate/quality report request message

• Terminal: the customer receives the certificate/quality report

Scope To request the certificate/quality report of a defined selection of existing goods between the customer and the supplier.

Boundary Not defined yet

Constraints The customer shall have full traceability of his request message to make sure it has been received. Failing this technical acknowledgement, the customer shall re-issue his request message

ESIDEL – Shipping cycle

115

In a business collaboration agreement between the customer and the supplier, the way of using the Certificate/Quality report request scenario can be described. The following transactions concerning the Certificate/Quality report can be specified as:

-1. The customer generates a certificate/quality report request to receive a certificate/quality report. The supplier has to give an acknowledge of receipt of the certificate/quality report request. The supplier sends a certificate/quality report to the customer. The customer acknowledges the receipt of the certificate/quality report to the supplier.

-2. The customer generates a certificate/quality report request to receive a certificate/quality report, and the supplier responds directly with the certificate/quality report. No acknowledgement messages are used between the parties.

Figure 51. Business transaction activity graph – Certificate/Quality report request

Certificate/Quality report request

Place request for a Certificate/Quality report

[CONTROLFAIL]

[SUCCESS]

Process certificate/Quality report request

Certificate/Quality report

Supplier Customer

START

END

ESIDEL – Shipping cycle

116

Form: Business Transaction Transition Table

From Id EUROFER: Certificate/Quality report request From Activity From Role Document To Activity To Role Guard Condition START N/A N/A Place request for a

certificate/ quality report

Customer NONE

Place request for a certificate/quality report

Customer Certificate/Quality report request

Process certificate/quality report request

Supplier NONE

Process certificate/quality report request

Supplier Certificate/Quality report

Place request for a certificate/quality report

Customer NONE

Place request for a Certificate/quality report

Customer N/A SUCCESS N/A Certificate/Quality report received

Place request for a certificate/quality report

Customer N/A CONTROLFAIL N/A Certificate/Quality report not received

ESIDEL – Shipping cycle

117

4.7.2. Business collaboration – Certificate/Quality report on regular event

Business Collaboration

Identifier EUROFER: Quality data sheet reporting

Description Based on an agreement with the customer, the supplier raises at a regular event a Certificate/Quality report for the customer. As a result the supplier sends a certificate/quality report to the customer.

Partner Types Customer Supplier

Authorized Roles Customer (Customer’s agent, Buyer or Buyer’s agent) Supplier (Supplier’s agent, Seller or Seller’s agent)

Legal Steps/Requirements None

Economic Consequences None

Initial/Terminal Events • Initial: agreement between the customer and the supplier

• Terminal: the customer receives the certificate/quality report

Scope To give the customer a certificate/quality report at a predefined event.

Boundary Not defined yet

Constraints The customer has an agreement with the supplier, to send him a certificate/quality report on a regular basis.

In a business collaboration agreement between the customer and the supplier, the way of using the Certificate/Quality report scenario can be described. The transactions concerning the Certificate/Quality report process are limited to the certificate/quality report send by the supplier to the customer and the customer acknowledges the receipt of the certificate/quality report to the supplier.

ESIDEL – Shipping cycle

118

Figure 52. Business transaction activity graph – Quality data sheet reporting

Form: Business Transaction Transition Table From Id EUROFER: Certificate/Quality report From Activity From Role Document To Activity To Role Guard Condition START N/A N/A Certificate/Quality

reporting Supplier NONE

Certificate/Quality reporting

Supplier Certificate/ Quality report

Process Certificate/Quality report

Customer NONE

Certificate/Quality reporting

Supplier N/A SUCCESS N/A Certificate/Quality report received

Certificate/Quality reporting

Supplier N/A CONTROLFAIL N/A Certificate/Quality report not received

Certificate/Quality report

Certificate/Quality reporting

[CONTROLFAIL]

[SUCCESS]

Process Certificate/Quality report

Supplier Customer

START

END

ESIDEL – Shipping cycle

119

4.8. Business transactions and authorized roles – Certificate/Quality report

process The goal of the Business transactions is to identify the individual transactions that implement the operations of the business collaboration. A transaction is made up of several activities and each activity has an authorized role in order to initiate that activity.

4.8.1. Business transactions and authorized roles – Certificate/Quality report request

Business Transaction

Description The certificate/quality report request is used to request a certificate/quality report of certain goods

Pattern Request/Response

Business activities and associated authorized roles

See EUROFER: Certificate/Quality report request

Constraints Not defined yet

Initiating/Requesting Partner Type

Customer

Initiating/Requesting Activity Role

Customer (Customer’s agent, Buyer or Buyer’s agent)

Initiating/Requesting Activity Document

Certificate/Quality report Request

Responding Partner Type Supplier

Responding Activity Role Supplier (Supplier’s agent, Seller or Seller’s agent

Responding Activity Document Certificate/Quality report

Business document

- CERTIFICATE/QUALITY REPORT REQUEST See EUROFER Message Guideline CERTIFICATE/QUALITY REPORT REQUEST

- CERTIFICATE/QUALITY REPORT See EUROFER Message Guideline CERTIFICATE/QUALITY REPORT

ESIDEL – Shipping cycle

120

4.8.2. Business transactions and authorized roles – Certificate/Quality report

Business Transaction

Description The certificate/quality report is used to report product information and test results of existing goods

Pattern Notification

Business activities and associated authorized roles

See EUROFER: Certificate/Quality report

Constraints Not defined yet

Initiating/Requesting Partner Type

Supplier

Initiating/Requesting Activity Role

Supplier (Supplier’s agent, Seller or Seller’s agent)

Initiating/Requesting Activity Document

Certificate/Quality report

Business document

- CERTIFICATE QUALITY REPORT See EUROFER Message Guideline CERTIFICATE/QUALITY REPORT

ESIDEL – Shipping cycle

121

All information provided in this documentation is provided "as is" without any warranties of any kind including warranties of accuracy, fitness for a particular purpose, or non-infringement or intellectual property. EUROFER shall not be held responsible for any errors or any loss resulting from any use of this document or the specification herein. The materials contained in this document may be copied provided that ALL copies retain the copyright and any other proprietary notices contained on the materials. No material may be modified, edited or taken out of context such that its use creates a false or misleading statement or impression as to the positions, statements or actions of the publisher. 2003 EUROFER. All rights reserved. All countries