Group IT BS EDI presentation

1. Group IT BS EDI presentation

2. Agenda • Group IT BS EDI organization • - Relation to Local IT • - EDI requests for Group IT – entrance gates (BS EDI, EAS EDI, BRM) • - How is BS EDI organized? • - What is the difference between BS EDI and other BS development teams? • - Procedures that ensures EDI deliveries (review and estimate, re-estiamte dev & QA, deploy, invoice) • EDI platform strategy • - Building new EDI platform – why? • - GIS upgrade project • - EDI consollidation project • EDI closer to business strategy • - Checklist for Local IT • - Technical workshop in November 2011 • - Cooperation manual • 1339 excel importer – release • - Characteristics of DSV CSV CL format • - File specifications & layout • - Test possibilities

3. Group IT BS EDI organizationRelation to Local IT Group IT Local IT BD&E IT • Road • Air & Sea • Road • Air & Sea • Solutions

4. Group IT BS EDI organization EDI requests for Group IT Customizedsetups Standard setups /Errors BS EDI development EAS support Project involving more than 1 team BRM (via Remedy) (via IT Help)

5. Group IT BS EDI organization BS EDI organization EDI Changecoordinator EDI Architect EDI Section Manager EDI specialists Road EDI QA IBM RSC developoment team, India EDI specialists Air & Sea EDI specialists Solution

6. Group IT BS EDI organization BS EDI organization • Road • Claus Jønck • Annika Eneroth • Wilgert Janssen • Jens Loldrup (1/11) IBM RSC developoment team, India EDI Changecoordinator Freja Margry EDI Section Manager Mette Nummelin EDI QA Cecilia Axmin EDI Architect Lars Karred Larsen EDI Specilists • Air&Sea • Hans M Nielsen • Nadine Tack Haldrup (1/10) • Simeek Kanakasan • Solution • Bo Henriksen • Pankaj Sachdeva • Henrik B Olsen Project Manager Ganesh QA technicalcoordinator Deepa Technical adviser Parivesh Developers:Ventkatesh, Prem, Junaid, Simeek, Sumalya, Sujoy

7. Group IT BS EDI organization Procedures thatensures EDI deliveries Incident & Change Management

8. Group IT BS EDI organization Procedures thatensures EDI deliveries Estimationprocess • Firstquality check of RFC for all mandatory informations • Daylifollow up onincomingCRQ’s for estimation • Changecoordinator forwards CRQ’s to primaryresponsible for specific business area • Primaryresponsible do a rough estiamteon the requestedsetupbasedon the informations available in RFC • Primaryresponsiblereturnwithestimate to changecoordinatorwithin 48 hours • Changecoordinatorsendsestimate and planningdetails to requester and updates Remedy accordingly

9. Group IT BS EDI organization Procedures thatensures EDI deliveries Development & QA process The strategy with this process is to strengthen the development and set standard for the DSV Group IT Business Service EDI application development and thereby raise the quality of the application developments that are implemented in DSV production environments.

10. Group IT BS EDI organization Procedures thatensures EDI deliveries Development & QA process

11. QA & Deploy flow Monday Tuesday Wednesday Thursday Friday Group IT BS EDI organization Procedures thatensures EDI deliveries Deployprocess 09.00 Deadline for correcteddoc. upload to Sharepoint 09.00 BS EDI deployreview 11.00 EAS EDI & BS EDI Deployapproval 12.00 Feedback to EDI team Time for doc/file correction 14.00 Feedback to EDI team 12.00 Deadline for UAT Approval for deploy oncomingMonday 16.00 Deadline for upload to Deploy 18.00 – 22.00 Deploy window

12. Group IT BS EDI organization Procedures thatensures EDI deliveries Invoiceprocess The Invoicing flow consists of 7 phases that continuously repeat themselves in an overlapping cycle of two months. Below the sequence of the 7 phases are illustrated:

13. Questions?

14. EDI platform strategyBuilding new EDI platform – why? GENTRAN Interface Cargo Link GIS Other App.

15. EDI platform strategyBuilding new EDI platform – why? • EDI platform and architecture not up to date • Still implementing setups across 2 platforms (one of them 10 years old and unsupported) • Very complex designs and not easy to maintain and support • Demand for more complex EDI setups from business/customers

16. EDI platform strategy GIS upgradeproject • Objectives • The objective of the project will be to facilitate the implementation of SI and the framework from ITAC onto a new infrastructure setup. • The new setup will provide an EDI-platform that is stable and easy manageable. • Benefits Expected • Use up-to-date technology • DB will run on supported versions (not requiring extended support) • Ensure the application is supported by the supplier • Infrastructure compliant with a Gold SLA level • Enhanced visibility to aid the support functions • Better utilization of the business processes • New platform will be ready by end February 2012

17. EDI platform strategy EDI consollidationproject(in the proces of approval) • Whyconsollidate? • The standard messages that we are aiming to bring in front in a sales situation are out dated and not able to meet the level of communication types, file- and message types that the customers are using today. • Also the speed of the implementations is longer as they are build and maintained across two platforms – oldest platform is unsupported and un-documented. • EDI platform maintenance has been down prioritized for several years due to business deliveries. • Benefit: BS EDI will be able to process up to 50% more setups/changes compared to the current flow with the same resource pool as we have today. • Furthermore we will be able to … • Meet customer and business demands • Improve time to deliver • Heighten quality of deliveries • Improve support and maintenance effectiveness

18. Questions?

19. EDI closer to business strategyChecklist for Local IT Workshop between BS EDI, ITDK and ITSE August 26 2011 Purpose with this workshop was to align expectations in the process of developing EDI setups and get united in the process of lifting the quality of the outcome. The outcome of this workshop will become generic material for all Local IT’s when requesting EDI developments. • EDI wish to improve: • Effectiveness in the way EDI resources are working, based on a better informative basis (RFC) • The speed of delivery of EDI developments • Better communication with Local IT/business • Outcome: • Checklist/Instruction on what information that should be provided when requesting an EDI development (new setup/change) Timeplan: Pilot period at ITDK and ITSE until November 1st 2011 Review and 2nd pilot untill end November 2011 Rolloutbegining December 2011

20. EDI closer to business strategyTechnical workshop in November 2011 • Purpose: • Train Local IT all around Europe in DSV EDI standards • Ensure that everyone is aware of the process of requesting as well as the internal working procedures that has been set up to guarantee qualitative developments for your customers. • Local IT sets the agenda… • We wish to listen to your daily challenges EDI wise and cover up as many subjects as possible • As we are in the process of shaping new EDI platform we kindly ask for your view on the future EDI platform • Workshop in DK November 3rd – 4th 2011

21. EDI closer to business strategyCooperation manual • Purpose • To alignexpectations in the cooperationbetweenLocal IT and BS EDI / EAS EDI. • Currently in process of creation and aligningwith Solution. • Content • Meeting structure • Communicationstructure • RequestingChange/Newsetup • Reportingissues in production, Fix onfail, urgentchangerequest • Group IT BS EDI adminstructure (Remedy, Clarity) • Reporting from Group IT BS EDI • Estimation model and estimateapproval • Addedhours for resumingCRQ’s • Overall prioritization of Road/Air&SeaCRQ’s • Deploy of EDI changes • Requestingdeployoutside normal DeployWindow • Invoicing • Escallation procedure • Cooperationprocess flow

22. EDI closer to business strategyChecklist for Local IT Workshop between BS EDI, ITDK and ITSE August 26 2011 Purpose with this workshop is to align expectations in the process of developing EDI setups and get united in the process of lifting the quality of the outcome. The outcome of this workshop will become generic material for all Local IT’s when requesting EDI developments. • EDI wish to improve: • Effectiveness in the way EDI resources are working, based on a better informative basis (RFC) • The speed of delivery of EDI developments • Better communication with Local IT/business • Outcome: • Checklist/Instruction on what information that should be provided when requesting an EDI development (new setup/change) Timeplan: Pilot period at ITDK and ITSE until November 1st 2011 Review and 2nd pilot untill end November 2011 Rolloutbegining December 2011

23. Questions?

24. DSV CL CSV Shipment information EDI setup28th of September 2011, Brøndby By Cecilia Axmin, Group IT 27/09 2011

25. Agenda Characteristics of DSV CL CSV format. File layout Test possibilities Requesting a set-up Documentation location Questions

26. Characteristics of EDI CL CSV Shipment information to CargoLink DSV CL CSV Shipment information standard setup, using the DSV implementation guideline for DSV CL CSV Shipment information, in PDF and excel format. (look at Netmoves, Group). Customer assumed to e-mail the file in to DSV’s edi broker GIS. In GIS technically the DSV CL CSV file will be converted in to the DSV standard (IFTMIN S93A) and forwarded to Gentran. (Default setup in place) Setup to be requested as usual via Incident in Remedy. EDI GIS Gentran CargoLink e-mail DSV CL CSV format Std CL format Customer Std flow DSV CL CSV ÍFTMIN S93A

27. DSV CL CSV Shipment information's • Shippers reference unique identifier used as well for consolidation. • Delivery instructions information's • Transport information's – Product, Speed, Type • Insurance information's • Consignee address information's • GOODS information's – Weight , Number of parcels, package type, volume, loading meters, height, length, with, goods description, shipping mark, • Consignor address information's

28. DSV CL CSV file layout • Header - Information's for file identification reasons • RowtagID – Headline information's • CONSIGNMENT– Information connected to the individual shipment information • ex below part of the file layout

29. Interesting things to know • All columns mandatory even if no value entered. • File to be saved as .CSV If saved as excel format file will fail as can not be identified. • Field lengths – Headlines has one field lengths and the records in the consignment information has their own. IF these are exceeded the file will fail in translation. • Insurance – all information's needed for CargoLink to get updated. • Consolidation – Only goods row information consolidated. Address information's needed even if consolidation only on goods row information. • NOT intended to be used for dangerous goods.

30. DSV CL CSV Shipmentspecificationname DSV CSV CL File template 3 March 2011.csv

31. Testing possibilities • Possible to test with the Test partner setup available in test environment. • E-mail address to GIS preproduction (test). clcsv@b2b-test.dsv.net • The partner set up is CLCV on CargoLink test environment(Q). • The test setup with partner CLCV is setup towards multiaccount so if testing using the above partner there needs to be created Profiles on Gentran to point towards correct CargoLink account. • TestpartnerID in the CSV file is TESTCLCSV • Recommendation to request X hours from GRIT BS EDI, for support on first setup. To get assistance with locating files going in error and explanation as to why. • File template is available to be used.

32. Requesting a setup • Fill in the standard request form. For creating a setup on Gentran. • The setup on GIS is already in place. Same e-mail address to be used on GIS for all the setups. • Different communication then a CRQ is needed to be sent in requesting the use of the standard map DSV_CSV_in CL_mp but with customer specific communication set up. • Mail standard request form to Remedy or create the incident in Remedy.

33. Standard request form for EDI setups

34. Documentation placement Netmoves

35. Documentation placement DSV Central

36. Questions ? ? • ? ? ? ? ? ? ?

37. Profile structure – IFTMIN booking • Structure • PPPPMPBBBBBCCCCC • Where • PPPP = partner in EDI and CargoLink • M = mode (A,S or R) • P = product (groupage(std) parcel, full laod ) • BBBBB = Bookingoffice (or ”LOC+5” from Eservice) • CCCCC = ISO country code of delivery (plus hubs in case DK and SE)

38. Gentran, Multiaccount for import flowAssign CargoLink account to PROFILIN

39. Profile in example – IFTMIN booking

40. Profile in example – IFTMIN booking

41. The end Any ?