From a license in house architecture to the implementation of SaaS for B2B collaborative EDI

From a license in house architecture to the implementation of SaaS for B2B collaborative EDI

EDI supporting Business Processes Order to Cash (main flows : sales orders, deliveries, invoices, returns) Planning to manufacturing (main flows : transactional data) Purchase to Pay (main flows : Purchase order, deliveries good receipts) Finance (main flows : bank statements, remittance advice) Master data exchange with most of partners

Previous architecture VMI Retailers SAP Main ERP EDI in numbers 150 changes per year 4,5 million EDI messages per year Approx. 100 partners 5 different methods (as2, edifact, ftp, rfc, sftp) Approx. 300 maps LAN/VAN/Internet Printing Manufacture WMS EAI systems Banks Key: Internal systems External systems

Saas architecture Incoming flows ERP EDI VAN P2P Exchange Interco B2B provider Unstructured Mail PDF Scanning OCR Fax Web Users SCM G e n e r i x C o l l a b o r a t i v e N e t w o r k CRM Legacy Customer IS Integration Translation control Routing Transport KPI, report Monitoring Alarms ECM CFE B2B Portal WEB-EDI Roll out G e n e r i x Business process Management C o l l a b o r a t i v e N e t w o r k Customer IT system EDI VAN P2P Exchange Interco B2B provider Unstructured Mail PDF Outgoing flows Desktop publishing Fax, SMS Web Users

SLA & Contract Mgt SaaS perimeter Helpdesk, maintenance, & professional services Incident Mgt Change Mgt Scalability Mgt Security Mgt EDI Managed Service All in one collaborative platform Performance Mgt Disponibility Mgt Catalogue of Services Infrastructure Cloud Generix Gouvernance / Service Management

Escalation process Level 1, 2 & 3 SaaS Organization Monitoring Operation Technical Office 24x24 Incident Manager Support Technical Office Method, standards, tools Design Office Design Office Collaboration Multientreprise SCM, sales Change Manager, Service Manager

Migration Key aspects Key results from Generix survey on MIGRATION OF EDI/B2B SOLUTIONS TO SAAS Migrations are most often sought out to increase agility, improve the quality of exchanged data and to meet business needs. Migration time varies according to the companies, but is often less than twelve months. CIOs are on the front line of initiating projects. ROI is positive but remains difficult to evaluate. Objectives set before the migration are achieved. The benefits can be seen in various areas: SLA levels, agility, ramp-up support, data security, cost reduction, etc. Cost reduction with regard to internal architecture is significantly likely. The lack of commitment from business units, integration with the existing IS, and a lack of the appropriate internal expertise are the main constraints. 7 24/11/2016

Saas Benefits Chain of actors simplified as Generix deals directly with trading partners No change of software Maps copied in specie Scalable Latest technology and functionality Expert support Improved message stats and reporting On shore support In house team focus on core business

Some risks and mitigation Migration is like a house moving, move only the necessary items : Most of the time if the EDI system has been set up in the 90 s it is more likely that the business has changed and EDI flows as well. So It is essential to assess the scope of the project by identifying the inactive partners and flows. Never underestimate connectivity : Connectivity between trading partners is vital and can easily take longer than expected, so connectivity with the different partners need to be assessed and set up at the early stage of the project in order to avoid delays. New processes need to be set up with Generix : For the migration and daily business, processes (who does what?) need to be set up and skill gaps assessed. 9 24/11/2016

Some risks and mitigation Communication is key with B2B projects : Communication with Trading Partner is essential in order to synchronise the migration of communications and flows at the same time. Avoid migrating and changing the EDI set up at the same time : It is not easy to track changes and progress on a moving target. Freeze any EDI change if possible during the migration. Or at least put a robust change control process in place. 10 24/11/2016

Some risks and mitigation Use standards as much as possible : Using standards in communication, set up and formats can save time and money. Adopt a realistic planning for the migration : Depending on the number of trading partners to migrate and the complexity of each partner (volume of messages, communication, criticality etc ) establish a realistic planning. Avoiding a big bang which could be a recipe for disaster in EDI. 11 24/11/2016

Reporting and Governance A range of dashboards and indicator management processes applied to files content (Invoice/Orders amount, product price, partners ID, etc. ) can be supplied. Dashboards are rolled out as standard for governing exchanges, managing of SLA and incident indicators. Specific dashboards can be created for compliance with the process of user companies or for the management of business indicators. 12 24/11/2016

Questions 13 24/11/2016

14 24/11/2016