ACM (1) Acumatica (1) Adobe XML Data Package (XDP) (1) agility (2) Archimate (1) Audit File Logistics (1) AZURE (1) B2MML (1) BIM (1) blockchain (3) BPM (11) BPMN (21) BPMN2 (1) Bruggenbouwer (2) Business Ecosystem (1) Business Leadership (10) CCTS (5) CDBC (1) CDE (1) CEN/BII (1) Change Management (6) cloud computing (5) CMMN (1) composable architecture (6) Consultancy (16) CRM (2) crypto (1) customs (1) D365 BC (1) D365 FSCM (16) DAM (5) data mapper (1) data mapping tool (3) data pools (4) DE&I (3) Design Thinking (1) desktop tools (1) Digital Leadership (21) Digital Manufacturing (1) Digital Thread (1) digital transformation (6) Digital Twin (1) DMN (3) DOM (1) DSDM (6) e-Business (18) e-Commerce (10) e-Factureren (3) e-Fulfillment (1) e-Invoicing (34) e-Ordering (2) e-Procurement (11) eclipse (6) Economics (1) EDI (10) EDIFACT (10) electronic data interchange (21) enterprise service bus (8) Environment (1) ERP (94) ESG (3) ETIM (3) European Commission (11) Fashion (2) flexibility (1) Food & Beverage (1) Government (3) GS1 (3) HR-XML (9) Hybrid Work (1) IDEAS (2) IIoT (2) Infor (1) Innovation (1) Interoperability-Frameworks (8) IoT (1) ISA-95 (1) Kwartiermaker (1) Legal (1) Leiderschap (4) MACH (8) mashups (1) MBEE (2) MES (3) metaverse (1) mind mapping (1) modeling frameworks (1) MOM (3) multi-tenancy (1) NetSuite (5) NEWS (5) NFT (1) nimbleness (1) O2C (1) Office Open XML (OOXML) (1) OMS (1) Open Document Format (ODF) (1) open source (2) Open Supply Hub (1) Overheid (5) PEPPOL (6) PIM (10) PLM (15) Politics (1) Portfolio Management (1) Prince2 (4) Process Mining (1) Process Modeling (17) Project Management (22) PropelPLM (2) Prosci ADKAR (3) Ramco (1) resilience (2) Retail (8) robustness (1) Rootstock (2) Salesforce (2) SAP (12) Security (1) service-oriented technologies (2) SITG (2) Smart Industry (2) Social (1) Supply Chain (31) Sustainability (14) Technology (1) ToolsGroup (5) UBL (12) UDEF (8) UN/CEFACT (6) Unified Commerce (5) Unit4 (1) Wholesale (3) WMS (8)

EDI implementation from Initiation to Go-Live

For those considering (or already started) implementing EDI here are some friendly advices.

"EDI is not something you (should) do overnight"

"Your Business should adapt to e-Business"

Your B2B or ERP solution provider will say "we will relieve you from all concerns"

Read one of my other posts (in Dutch) about this relieve "Wij nemen u alle technische en functionele uitdagingen ( lees: problemen) uit handen en zorgen dat het goed komt"

The approach that works and embeds EDI into daily business practice

In a typical Order-to-Cash (O2C) process there are 4 business documents exchanged:
- Purchase Order
- Purchase Order Acknowledgement
- Advanced Ship Notice
- Invoice

Additionally master data can be exchanged / synchronized between trading partners on a regular basis containing:
- Product information
- Price data
- Product characteristics e.g. weights
- Address locations

[Want to know more about master data, read "Supply Chain collaboration - the battle for data".]

The best scenario for implementing EDI business documents with partners consists of a phased-based approach. The overall goal of this approach is to realize a complete and smooth exchange of all agreed business documents and data.

During each phase in the implementation scenario one business document is fully implemented. The implementation phases will overlap to ensure a continuous implementation process.

Phase 0: contains master data alignment
• product information (GTIN – UPC)
• geographic locations (GLN – UPC)
• price data
• product characteristics

Phase 1: implementation of order & order response

Phase 2: contains implementation of shipping notification

Phase 3: contains implementation of invoice

Requirements analysis & agreement phase

Before starting the implementation phases there is a requirements analysis and agreements phase during which following activities are performed:

1. Gather and analyze the EDI requirements (documents, data and process steps)
2. Agree upon the business documents, the data exchanged and alignment of process steps
3. Agree upon the communication protocol used
4. Agree upon the implementation scenario

5. Estimate the impact on a technical level (registration and processing of data)
6. Estimate the impact on a business level (working instructions for order entry, invoicing and shipment)

The joint deliverables of this phase are:
- EDI Trading Partner Data Sheet
- EDI Message Specifications
- Agreed communication protocol
- Agreed list of business documents, data exchanged and process steps
- Agreed implementation scenario

The internal deliverables of this phase are:
- Technical impact: overview of issues and resolutions
- Business impact: enhanced working instructions

Implementation phases

For each agreed business document the implementation will go through 3 stages:
- Setup & test
- Parallel processing
- Consolidate

To be successful the implementation of EDI need to be managed on a day-to-day basis and requires availability of several specialists: EDI Message expert, ERP integration and process experts and B2B Service Provider.

Setup & Test Stage

Technical activities:
- Setup the connection with the EDI environment of the customer
- Implement transformation mappings at B2B Service Provider
- Test the connectivity with EDI environment of the customer
- Verify the syntax and semantics of the EDI message(s) exchanged

Business activities:
- Validate the document created in ERP and check the working instructions
- Agree upon procedures for handling and monitoring the exchange of the business document

- B2B message mapping delivery
- EDI connection both test and production
- Agreed upon internal working instructions and external procedures

Parallel stage

During the parallel phase both business partners will check the completeness and correctness of the EDI-message for a period of 1 month.

EDI documents are leading during this phase. Non-EDI documents are exchanged until both business partners are completely satisfied that the EDI system is performing well.

Consolidate Stage

During the consolidate stage it is important to gather all issues reported and measures taken and come to an agreement with the customer about the way forward.

Organize a User Acceptance Meeting (UAM) with representatives of the customer and the internal organization. During this meeting finalize the list of issues reported and decide whether or not / when the message can go into operation. After the GO/NO Go decision start with the setup of the operational environment (master data, EDI connectivity, working instructions, …)

As a last step before going live inform the organization formally when the EDI message will be taken into operation and what is expected of all people involved.

Deliverables are:
- User Acceptance Document
- Updated issue and resolution list
- Working EDI and ERP environment
- Adapted working instructions

Operation phase

Activities to be performed are:
- Monitor communications to ensure EDI documents continue to flow
- Respond to inquiries from business partners as issues arise
- Report on business partner activity
- Make updates to translation maps and/or communication protocols as new documents are added

Deliverables are:
- Updated issue- and priority list
- Performance overview report
Number of messages received / sent
Number of issues reported and solved
Number of changes requested and performed

My focus areas are business processes, business information systems (ERP, CRM, BPM, ...) and integration of business processes and systems over the boundaries of companies AND not to forget Open Source business applications.

If you have an opinion about the implementation or use of EDI then do not hesitate to react. If you agree with the fundamentals then share it with others.

Tags: e-Business, e-Invoicing, e-Procurement, e-Commerce, EDI

No comments:

Post a Comment