Building Your EDI Modernization Roadmap

Transcription

1 Simplify and Accelerate e-business Integration Building Your EDI Modernization Roadmap

2 Background EDI Modernization Drivers Lost revenue due to missing capabilities or poor scorecard ratings High error rates in order processing, exception handling, and shipping Slow, expensive, and labor-intensive partner onboarding and ongoing changes Replacement of or major upgrades to platforms and core applications Mounting costs of licensing, maintaining, training, and using multiple middleware systems

3 EDI Modernization Options 1. Do nothing (and deal with the consequences) 2. Optimize for the happy path and address exceptions by coding 3. Add point tools and manage a hybrid environment 4. Engage a service to replace or augment the classic EDI environment 5. Migrate to an on-premise or cloud-based Modern EDI solution

4 Key Issues 1. What is modern EDI and why is it important? What classic EDI assets do you need to migrate or recreate when moving to a modern solution? What are the core tasks and capabilities needed for EDI modernization and classic EDI migration? What additional factors are critical to EDI modernization success? Simplify and Accelerate e-business Integration

5 Profile: EXTOL International Provider of business integration software and services since Customers in Transportation, Logistics, Distribution, CPG, Food, Apparel, Industrial Manufacturing, Health Care, Pharmaceuticals Customer project categories: EDI and other Business-to-Business integration Internal data and application integration Cloud services integration How we re different: One solution for all integration needs Faster, simpler implementation Unmatched customer service and support 5

6 Representative EXTOL Customers 6

8 Classic vs. Modern EDI Classic EDI: Standard EDI document syntax and semantics Mix of communications over VANs and direct connections Coded integration with applications and data Asynchronous, batch-oriented interactions IT-dependent, forensic management and reporting Isolation from other integration activities Modern EDI: Diverse range of standard and proprietary electronic documents Mix of point-to-point, VAN, and mediated communications over the Internet Configured, plug-in integration, aided by intelligent automation Mix of asynchronous batch and synchronous, near real-time interactions Management by exception via dashboards, alerts, self-serve reporting Part of a larger framework that includes data, application, and cloud integration 8

10 EDI Modernization Impacts 3 Main Asset Areas Classic EDI System Tools and Processes Document Map Connection Partner EDI Object Library Workflow EDI Infrastructure Services: Syntax analysis and routing Acknowledgement generation and reconciliation Enveloping and de-enveloping Reprocessing and resending Data transformation and validation Communications and interfacing Control number management Logging, auditing, and reporting Selecting a modern EDI solution begins here. Infrastructure Services

11 EDI Modernization Impacts 3 Main Asset Areas Classic EDI System Tools and Processes Document Map Connection Partner EDI Object Library Workflow EDI Infrastructure Services Configured EDI processes and objects: Workflows Partner profiles Document definitions and validation rules Data transformation maps Connections to external and internal resources Coded interfaces and called routines Legacy EDI migration planning begins here. Infrastructure Services

12 EDI Modernization Impacts 3 Main Asset Areas Classic EDI System Tools and Processes Document Map Connection Partner EDI Object Library Workflow Infrastructure Services EDI Infrastructure Services Configured EDI processes and objects Design-time Tools and Processes: Partner profile definition Source / target document definition Data transformation mapping Connection / interface adapter definition Workflow definition Testing / auditing Monitoring / reporting Runtime Tools and Processes: Resource monitoring, alerting, and management Analysis and reporting Maintenance and upgrading Legacy EDI migration strategy begins here.

13 EDI Modernization Impacts Classic EDI System Tools and Processes Document Map Connection Partner EDI Object Library Workflow Infrastructure Services Life Cycle Practices Migration Effort Integration Capabilities Document Map Modern EDI System Connection Repository Tools and Processes Partner Workflow Event Spreadsheet Notification S/FTP/S Adapter Infrastructure Services Database Monitor XML Document AS2 Adapter File System Monitor Flat File Web Service Business Process Schedule

15 13 Steps to EDI Modernization # Task Details and Options 1 Catalog EDI infrastructure services Document baseline EDI requirements and required enhancements 2 Inventory configured EDI objects Document partners, interfaces, document types, maps, workflows, etc. including custom code 3 Profile life cycle tools and processes EDI implementation / maintenance, s chedules, events, workloads, required service levels, exception - handling, scheduled downtime, backups, etc. 4 Perform gap analyses (3 areas) Based on current and anticipated use cases 5 Choose a modernization strategy 1. Stabilize legacy system and apply modern solution as add / change requirements surface 2. Phase - in modern solution by replacing legacy EDI implementation, partner - by - partner 3. Replace partner - facing and last - mile integration layer services separately 4. Replace legacy system with modern solution en masse 6 Establish modernization timeline Including target dates for milestones below 7 Identify supplemental resource needs External assistance needs for planning, implementation, etc. 8 Select modern EDI solution target Based on fit to current and anticipated use cases, deployment preference, implementation assistance needed, support, etc. 9 Train planning and migration staff Ensure understanding of best practices for new solution 10 Identify process improvement areas Identify design - time and runtime process improvement opportunities that exploit capabilities of new solution 11 Define architecture and reuse strategy Workflow patterns, adapters, base maps, error - handling and notifications, etc. 12 Follow migration roadmap in project sprints 13 Cut - over to production (usually in stages ) Migrate / recreate EDI objects, including documentation, testing, check - in Partner connections, resource monitors, reports, schedules, operating procedures, etc.

16 Metadata and Reuse are the Keys to EDI Migration Legacy EDI Assets Maps Metadata / Sample Data Assets Mapping dictionaries (e.g., spreadsheets) Mapping patterns Base maps Reuse Assets Documents Partners EDI standards metadata External document metadata Electronic document examples Enveloped EDI data examples Existing document schemas Existing partner profiles Connections Workflows Existing adapters Adapter templates Existing processes Process templates The migration value of classic EDI library metadata is limited, due to lack of standardization and legal exposure

17 Classic EDI Migration Project Sprint Sample EDI Data Metadata / Sample Data Document Partner Dictionaries / Patterns Base Maps Map Connection Workflow Adapter Templates Process Templates

18 EXTOL Simplifies EDI Modernization and Migration External Locations, Partners, and Services Customers Suppliers / Service Providers Cloud/SaaS Applications & Services Integration Studio Design-time Tools EXTOL Business Integrator Dashboard / Reporting / Activity Monitoring Enterprise Applications Windows / Linux / IBM i / VMware Operational Data Data Warehouse Enterprise Data Business Intelligence On-premise Applications, Services, and Data 18

19 Product Demo: EXTOL Business Integrator Sample EDI Data EDI Provisioning Assistant Document Schema Generators Metadata / Sample Data Document Partner Map Connection Workflow Smart Mapping + Map Reuse Dictionaries / Patterns Base Maps Adapter Configurators + Adapter Reuse Adapter Templates Process Templates Process Modeler + Process Reuse EBI Auditor EXTOL Dashboard

21 EDI Modernization Success Factors Leverage baseline metrics on error rates, chargebacks, returns, exception-handling time, auditing time, onboarding time, etc. Invest sufficient time on legacy system inventory, development of object templates, and reuse strategy Look for automated tools that can generate integration deliverables from metadata and reusable base objects, to cut time and errors Understand and exploit the differences between the legacy and modern EDI solutions Employ vendor services as appropriate to shorten your learning curve and reduce time to production 21

22 Q&A Contact: Website: Phone: +1 (201)