1. Transport XML project 2006.11.24 Flemming Moller Hansen

2. Mission To create a collection of XML specifications/messages (Transport order, Status reporting and invoicing etc.). The specifications must cover domestic and cross-border transport for all modes of transport (Road, Rail, Sea and Air or combinations of these). The specifications must cover the complete multimodal transportation proces as well as unimodal transportation from request for transport to final delivery of cargo and invoicing for all services included. The specifications must include information for the needed legal aspects for the various modes of transport.

3. Mission continued The specifications must cover the current rules/demands for terror protection, dangerous goods requirements and trace of commodities before and after the transport. The specifications must secure better coordination and cooperation between the various modes of transport. Use the ebXML standard as basis. To give Denmark a leading role using ICT solutions

4. Project groups (planned) Steering group Scenario group Message group Technic and communication group Legal & security group Awareness group

5. Messages in proposal Prebooking Booking Transport order domestic Transport order international Status including POD (Proof of delivery) Advice Invoicing Statistics

6. Source Use of UN/CEFACT Core Component to secure the international aspect. Create ”new” Core Component if needed. Use existing set of codes. Create ”new” codes if needed.

7. Overview XML messages

8. Overview Overview a

9. Actual messages phase 1 & 2 Phase 1 >Enquiry >Enquiry response >Transport order >Transport order response Phase 2 (not planned yet) >Transport status >Invoicing

10. Actual status Basis >Core Component 1.0. >Submission from TBG2-3 included. >Identification of additional danish requirements. ”Complete master” created in XMLSpy. Current model matched/updated with IFTMIN requirements from a number of transportation companies. Workshop mid november (Debate of IFTMIN requirements against our current model). Identification of extra requirements.

11. Actual status continued ”Current model” update including extensions in process. EXCEL document match/update planned ASAP. Creation of the individual messages from the updated model planned ASAP.