Skip to main content

ETRN scenario

This section covers the interaction scenarios between the integration, LSS.Monitor and the ETRN (electronic consignment note) operator.

For more complex interaction cases, contact the implementation team for advice on the implementation.

ETRN titles can be uploaded at any moment: when the wave is created or through the data update fact.

The last uploaded title is shown in the performer's mobile application and is considered current. The current QR code .gif and the ETRN in .pdf format can also be uploaded to the mobile device.

The logistician can also see all statuses in the Monitor web interface.

caution

The performer's mobile application does not prevent demands from being completed without a current title set.

Tracking and timely uploading of ETRN titles and QR codes for the transportation is the responsibility of the integration.

Step by step​

Basic scenario T1, T2, T3, T4​

For the scenario below, we assume that:

  • The wave is uploaded, launched and sent for execution, and it contains no signed ETRN.
  • The integration module is subscribed to this wave.
  • The integration module holds a qualified electronic signature key used to sign documents with the ETRN operator.

How to subscribe to changes correctly is described in the document.

The wave can be uploaded with already signed ETRN: order:key.cargo.invoice.waybill.status = T1.

StepActionInitiatorInteraction
1.The Integration module polls the ETRN operator for signed T1 ETRN.Integration moduleIntegration module → ETRN operator
2.The Integration module creates facts on the Monitor server side for every order that received T1.Integration moduleIntegration module → Monitor server side
3.The Monitor server side applies the facts to the wave. The data is loaded into the Mobile application, where the T1 status is shown.Monitor server sideMonitor server side → Mobile application
4.At loading, the performer sets the DEMAND_DONE status for the PICKUP. The Mobile application sends the loading fact to the server.Mobile applicationMobile application → Monitor server side
5.The Monitor server side applies the facts to the wave and notifies the Integration module about the new facts via the subscription.Monitor server sideMonitor server side → Integration module
6.The Integration module downloads the required facts for the orders and passes the T2 status to the ETRN operator.Integration moduleIntegration module → ETRN operator
7.The ETRN operator confirms the signing of T2. The Integration module exports the ETRN in .pdf format and the QR code for the transportation, then generates a fact for the order with the T2 title and links to the documents.Integration moduleIntegration module → Monitor server side
8.The Monitor server side applies the facts to the wave. The data is loaded into the Mobile application: the T2 status is shown and the accompanying documents become available for download.Monitor server sideMonitor server side → Mobile application
9.The Integration module polls the ETRN operator for signed T3 ETRN.Integration moduleIntegration module → ETRN operator
10.The Integration module creates facts on the Monitor server side for every order that received T3.Integration moduleIntegration module → Monitor server side
11.The Monitor server side applies the facts to the wave. The data is loaded into the Mobile application, where the T3 status is shown.Monitor server sideMonitor server side → Mobile application
12.At unloading, the performer sets the DEMAND_DONE status for the DROP. The Mobile application sends the unloading fact to the server.Mobile applicationMobile application → Monitor server side
13.The Monitor server side applies the facts to the wave and notifies the Integration module about the new facts via the subscription.Monitor server sideMonitor server side → Integration module
14.The Integration module downloads the required facts for the orders and passes the T4 status to the ETRN operator.Integration moduleIntegration module → ETRN operator
15.The ETRN operator confirms the signing of T4. The Integration module generates a fact for the order with the T4 title.Integration moduleIntegration module → Monitor server side

Important: this article will be extended once the methods supporting the T7 and T8 titles are implemented.

Redirection scenario T7​

Performer replacement scenario T8​