Challenge Project

Making packages talk

Putting data required for correct handling on the box in a globally standardised way independent of Sender, Carrier or Receiver

⛶  Fullscreen ↓  Download 📂 Demo

Demo Link http://synccode.eu-central-1.elasticbeanstalk.com

Challenge

📎 Making Packages Talk - UPU Hackathon - short.pdf

In e-Commerce the flow of a package is nearly always Business-to-Business-to-Consumer. The Consumer orders something on-line. The e-Merchant (Seller) then sends the ordered items in a package (or packages) to the Consumer (Buyer). This package may then be carried by multiple different transporters (postal and/or non-postal). Ultimately, the package may then be delivered to the location of the Consumers choice (often the home).

Problem:

Currently, each transporter needs to receive a data-set in advance of the package being handed over to him/her. In general, each transporter will have its own requirements related to structure of the data set (and contents). All too often, each transporter also insists on their own format for the label affixed to the package (leading to relabelling along the journey of the package). *Moreover, each transporter may insist on using its own (proprietary) identifier for the package. * This creates a lot of confusion when communicating about the progress of delivery of the goods ordered transported in the package/s.

For:

The sending e-Merchant as well as the Consumer (hopefully receiving the package and the goods s/he ordered) both desire to be able to consistently track where the Goods Sold/Bought are. Because of the issues mentioned above, it is difficult for the e-Merchant to provide the Consumer with that tracking information (because the transporters involved have troubles providing the necessary feedback about the package). Furthermore, the **proprietary information exchanges as well as the relabelling adds (unnecessary) cost and time ** to the end-to-end process of transporting the package from Seller to Buyer. This affects the transporters mostly, but also the Seller and Buyer, because the transporters will include those additional costs into their charges one way or another. The Scan4Transport standard provides a globally standardised way to include structured data into a 2D barcode.That enables any party reading the 2D barcode structured according to the standard to correctly interpret the data encoded in the 2D barcode regardless of the party that created the 2D barcode (according to the standard).

Goal:

  1. As a minimum, it would be good to show that the 2D barcodes can act as “fall-back” for lack of prior information exchanges. So reading a barcode and correctly interpreting the contents (and showing this in a screen (mobile phone or browser) to a user.
  2. The user, should then be able to access the latest/additional information from a remote application (via the Web) based on the above mentioned standards. This may be a basic display on a Web-browser or retrieval via an API and showing that within a self-built App on the Mobile Device.
  3. The third “layer” would be that the operator may log an Event with a remote application (e.g., confirmation of delivery, hand-over to next transporter). This may be done via a Web-browser, an API directly to the remote Application and/or posting the Event to an EPCIS application (as described in the UN/CEFACT standard Integrated Track and Trace for Multi-Modal Transportation as a good way to easily exchange Event-Information among disparate systems).

It would be fantastic if more than one hacking team would work on this challenge and each one would focus on (parts of) the above scenario to show that a package carrying the same label with the same 2D barcode may easily be processed by different software. That would prove interoperability of these standards. The Hackathon may also provide valuable learnings related to shortcomings in the standards (e.g., ambiguity in how to interpret them when converting them into software implementations.

Challenge Owner:

Jaco Voorspuij

scan4track

This content is a preview from an external site.
 

Event finished

Edited (version 88)

24.06.2023 12:43 ~ Alqahtanighadah

Share

We're ready!

24.06.2023 12:30 ~ Vygantas

0.0.6-SNAPSHOT (@vygkaz)

fixed form data (@Andris Smolovskis)

Preparing for demo

24.06.2023 12:13 ~ Vygantas

Launch

Edited (version 79)

24.06.2023 12:06 ~ Alqahtanighadah

Prototype

Edited (version 77)

24.06.2023 12:05 ~ Alqahtanighadah

0.0.5-SNAPSHOT (@vygkaz)

Added default form values (@Andris Smolovskis)

Prototype

Edited (version 72)

24.06.2023 11:26 ~ Vygantas

Sketching

0.0.4-SNAPSHOT (@vygkaz)

Run app without DB (@Andris Smolovskis)

Fixed sting sscc value (@Andris Smolovskis)

Added sscc input (@Andris Smolovskis)

Updated location (@Andris Smolovskis)

added missing date field (@stasysr)

Fixed action buttons (@Andris Smolovskis)

Swithced to H2 (@Andris Smolovskis)

check fer events (@stasysr)

added date time format (@stasysr)

Edited (version 69)

24.06.2023 09:47 ~ Vygantas

Sketching

Edited (version 67)

24.06.2023 09:44 ~ Vygantas

barcode styling (@stasysr)

Edited (version 64)

24.06.2023 09:39 ~ Vygantas

Sketching

Repository updated

24.06.2023 09:38 ~ loleg

Edited (version 60)

24.06.2023 09:37 ~ loleg

added sscc field (@stasysr)

fixed header (@stasysr)

Fixed issues (@Andris Smolovskis)

added missing params to barcode (@stasysr)

24.06.2023 09:01 ~ Vygantas

Sketching

added new mapping (@stasysr)

Fixed issues (@Andris Smolovskis)

added new mapping (@stasysr)

Fixed issues in arcel registration (@Andris Smolovskis)

Merge branch 'master' of https://github.com/vygkaz/scan4track (@stasysr)

added mapping and value check (@stasysr)

Fixed issues in arcel registration (@Andris Smolovskis)

fixing barcode (@stasysr)

Initial barcode page (@Andris Smolovskis)

Added buttons submitting (@Andris Smolovskis)

fixed order form (@stasysr)

latest changes (@stasysr)

Added new order inputs (@stasysr)

Merge branch 'master' of https://github.com/vygkaz/scan4track (@stasysr)

Modified order page (@stasysr)

Fixed Order saving (@Andris Smolovskis)

Merge branch 'master' of https://github.com/vygkaz/scan4track (@stasysr)

Challenge

Event started

 
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the UN System Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

Creative Commons LicenceThe contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.