Figure 1: SCM Pilot Use Case Diagram

The full business scenario performs the following real-world use case deployed in the Spanish Demostration Center of IT applied into Logistics (www.cdlogistica.es/en): 1) A customer buys some product in the shop or e-commerce; 2) An out-of-stock is triggered and an order is sent to the manufacturer; 3) The manufacturer composes the order; 4) The order is delivered by a transport to a wharehouse; 5) The warehouse receives the freight, prepares the quantity required and stock the rest; 6) The parcel is sent by transport to the shop, and; 7) The shop receives the parcel, verifies it and fill in the gaps in the shelf.

The SAUT includes this logic behavior for each SUT: 1) Material Supplier: It manufactures a list of pre-configured products; There’s a minimum order size; It manages all transportation activities (it knows when an order is finished according to events received). 2) Warehouse: There’s a list of products on the shelves; There’s a limited space for each product; It manages inbound planned and received quantity; It manages outbound planned and sent quantity; There are only some days when transportation can pick-up products. 3) Transportation: It manages pick-up appointments with Warehouse (try again if proposal is rejected by origin); It manages drop-off appointments with Point of Sale (try again if proposal is rejected by destination); It triggers events to Material Supplier in case of errors when trying to pick-up or drop-off freights. 4) Point of Sale: There’s a list of products on the shelves; There’s a minimum stock per product, when it’s out of stock, an order and delivery use case is automatically triggered; There are only some days when transportation can drop-off products; It manages the status of each order as well as the planned and received quantity. As we have a GS1 LIM compliant scenario, SUT components interchange messages according to GS1 LIM specification. This way, the complexity of data types is great (on average more than 30 parameters per message), so that for a first proof of concept in order to facilitate the adoption of modeling techniques by pilot partners as well as to minimize the complexity for technical partners, a simplified version of SAUT has been developed. The SimpleSAUT reference implementation maintains the same logic but it reduces the complexity of message parameters, losing the GS1 LIM compliance.

As this pilot is in fact a test-bed service infrastructure, the deployment can be extensively configurable on demand. This way, the tester can deploy from all components in the same machine to every service in a different machine. All modules are configurable by their own files. There is an instance of the Logistics SAUT deployed in the public machine midassaut.itainnova.es (or midassaut.ita.es) with IP address 193.144.226.15 with the latest version of all components. The cloud version includes the installation of the usage-based monitor, provided by UGOE, which includes 1 monitor and 12 proxies, as it’s shown in the next Figure:

Figure 1: Logistics SAUT Deployment in the cloud