Modernizing*EDI:**Best*Prac5cesfor** …edit&master&/tle&style& Modernizing*EDI: ... Establish...

All Content © 2014 EXTOL Interna6onal, Inc. presented by

Click to edit master /tle style Modernizing EDI: Best Prac5ces for Project Planning, Migra5on, and Opera5ons

Jim O’Leary Jeff Inns VP Product Strategy VP Customer and Product Infrastructure EXTOL EXTOL


Classic versus Modern EDI

Modern EDI: +  More applica6on, service, data endpoints +  XML, spreadsheet, complex files, other +  End-‐to-‐end process automa6on +  Synchronous, real-‐6me response +  Managed file transfer, governed access +  Self-‐serve visibility and excep6on alerts +  Modeling and configura6on, not coding

All Content © 2013 EXTOL Interna6onal, Inc. 2

Suppliers / Service Providers Customers Cloud / SaaS Applica/ons & Services

External Loca/ons, Partners, and Services

Enterprise Applica/ons Enterprise Data

Data Warehouse

Opera/onal Data

Business Intelligence

On-‐premise Applica/ons, Services, and Data

Your Business

Classic EDI: •  External partner + simple data endpoints •  Simple inbound and outbound processes •  Batch-‐oriented processing •  Standard EDI documents plus flat files •  Coded integra6on with applica6ons •  Ungoverned file transfer and access •  IT-‐dependent repor6ng and audi6ng


Key Issues for Planning and Migra5on

•  What informa6on should you capture before modernizing?

•  How can a project repository save 6me and reduce cost?

•  How does paWern reuse facilitate migra6on and onboarding?

•  How can automa6on amplify reuse benefits?

•  Which policies prevent problems downstream?


Profile: EXTOL Interna5onal

•  Provider of business integra6on soYware and services since 1989 •  800 Customers in Transporta6on, Logis6cs, Distribu6on, CPG, Food,

Apparel, Industrial Manufacturing, Health Care, Pharmaceu6cals

•  How we’re different: •  One solu6on for all integra6on needs

•  Faster, simpler implementa6on and opera6ons without sacrificing power

•  Unmatched customer service and support

4


EDI Moderniza5on Op5ons

1.  Do nothing and live with the consequences 2.  Augment legacy solu6on(s):

•  Assume an EDI “happy path” and code the excep6ons •  Add point tools and manage mul6ple solu6ons •  Engage service(s) to add isolated capabili6es

3.   Migrate to a “Modern EDI” solu/on

All Content © 2013 EXTOL Interna6onal, Inc.

5


Why Migrate?

Maintain and coordinate one skill set and resource pool for all integration projects

! Fewer hand-offs, delays ! Higher skills availability ! Higher productivity ! Lower training costs ! More predictable delivery

!


EDI Moderniza5on Phases

Planning Enumerate goals and constraints Establish project infrastructure and policies Inventory legacy system Perform gap analysis based on current and anticipated use cases Choose an implementation model Identify supplemental resource needs Select modern EDI solution Define roles and assign personnel Train planning and migration staff Choose a modernization strategy Define integration architecture Establish project schedule

Planning

Migration Develop templates and other reusable, shared objects Define scope and target for upcoming sprints Gather inputs to upcoming sprints Perform migration / implementation sprint Deploy and go live with new integrations

Migration

Ongoing Operations Assess status and outcomes continuously Refine plans and best practices as you gain experience Capture metrics and maintain visibility to stakeholders Exploit templates when onboarding new partners Conduct post-project review

Ongoing Operations

…


Planning Best Prac5ce: Assign Clear Roles and Responsibili5es

Architect Project Lead Gatherer Planner Designer

• Analyze required integration processes

• Conduct Proof of Concept

• Install / Configure tools and middleware

• Maintain Communication• Stakeholders• Team• Trading Partners

• Issue status updates

Builder Tester Deployer Operator

• Gather specifications• Gather test data• Create repository• Analyze data

• Create test andoperations plans

• Verify infrastructure plan(hardware, VM/OS, communications, etc.)

• Research base configurations

• Design base configurations

• Build base configurations• Deploy base

configurations• Conduct unit tests

• Execute plan• Verify unit testing• Create archives

• Promote archive• Notify users

• Monitor applications• Handle exceptions• Execute operations

plan

Key: Internal Role/ActivityOutsourced Role/ActivityShared Role/Activity

Trainer

• Create documentation• Present documentation• Deliver training


















plan


Trainer


Example:


















plan


Trainer



Planning Best Prac5ce: Use a Project Repository

Planning Ongoing Operations

Project Repository

Mapping Tables

Sample Applica/on

Data

EDI Sample Data

Document Metadata

Applica/on Interface Specs Goals and

Constraints

Project Schedules

Trading Partner Specs

•  Secure •  Multi-user •  Versioned •  Managed

Migration


Planning Best Prac5ce: Perform a Mul5-‐level Gap Analysis

Current capabilities Current and future needs

Classic EDI Tools and Practices

IT Department

Classic EDI Processes

Map

Partner Communi-

cations Database Insert

Document

Document

Classic EDI Infrastructure

Transfor- mation

Communi- cations

Partner management Activity

reporting Auditing

XML Email S/FTP/S Modern EDI Life Cycle Tools and Practices

Event

Schedule

Spread-‐ sheet

Business Process

AS2 Data base

Flat File

MFT

Appli-‐ ca/on

Web Service

Monitor Modern EDI Integra/on Model

IT Department Business Depts

Map

Partner Communi-

cations Database Insert

Document

Document

Modern EDI Infrastructure

Transfor- mation

Adapters

Partner management

Activity monitoring

Auditing / diagnosis

Application integration

Data integration

Process automation

Real-time integration

Web Services

Classic EDI System Modern EDI System

Integration Architecture

Integration Deliverables

Skills and Best Practices


Addi5onal Planning Best Prac5ces

•  Iden6fy opportuni6es to streamline and refactor business processes in ways that exploit the strengths of the modern EDI solu6on you choose

•  Establish clear Test and Produc6on promo6on policies

•  Consider trading partner size / importance, rela6onship status, complexity, competence, and change history when planning your migra6on sequence


Migra5on Best Prac5ce: Iden5fy Reuse Opportuni5es Early

Project Repository

Migration Planning

Partner-‐ Specific

Key: PaXern-‐ Specific

Partner Metadata, EDI Sample

Data

Partner Endpoints

Events, Schedules

SLAs, Opera/ons

Reqs Document Defini/ons

Legacy Maps, Mapping History

Pre-‐built Adapters, PaXern Analysis

Integra/on PaXern Analysis

Document Metadata, Sample Data

Standards

Map Templates, Dic/onaries, PaXerns

Adapter Templates

Process Templates

Project Templates

Ongoing Operations


Migra5on Best Prac5ce: Amplify Reuse Benefits by Exploi5ng Automa5on, Where Possible

•  Packages (e.g., Inbound Orders, Outbound Ship Notices)

•  Business Processes •  Input / Output Adapters •  Data Transformation maps •  Source / Target Document Schemas •  Other (variables, globals, etc.) •  Shared objects (e.g., Notifications)

Customer A Project

Example: Use Automated Tooling to Generate and Customize Projects

Customer B Project

Customer C Project

…

Customer Z Project

Project Generator

“EDI Customer” Project Template

Partner Spreadsheet

Customize •  Mapping changes •  Adapter settings •  Events / schedules

Test •  Connections •  Diff outputs •  Other

Deploy


Project C

Migra5on Best Prac5ce: Migrate and Onboard in Short, Manageable Sprints

Project Repository

Customize Maps

Customize Adapter Settings

Configure Events and Schedule Activations

Deploy Project

Test and Verify Results

Project B Project A

• Endpoints • Schemas • Maps • Adapters

• Processes • Events • Schedules • etc.

Shared Objects • Templates • Common sub-‐processes • etc.

Generate Project(s) from Template(s)

(next sprint)


Addi5onal Migra5on Best Prac5ces

•  Conduct a full life cycle dry run at the beginning of the Migra6on phase to iden6fy and resolve process and policy issues

•  Avoid “go-‐live” events prior to weekends and holidays

•  Employ vendor services as appropriate to shorten the learning curve, mi6gate risk, and reduce 6me to value


Ongoing Opera5ons Best Prac5ce: Standardize Excep5on Handling and Manage by Excep5on

Project A Project B Project C … Project Z

Common Exception

Processing and Notification

Process

Business Departments

EDI / IT Staff Customers / Suppliers /

Service Providers


Ongoing Opera5ons Best Prac5ce: Reuse Migra5on Templates When Onboarding New Partners

Project C

Project Repository

Customize Maps

Customize Adapter Settings

Configure Events and Schedule Activations

Deploy Project

Test and Verify Results

Project B

New Partner Project • Endpoints • Schemas • Maps • Adapters

• Processes • Events • Schedules • etc.

Shared Objects • Templates • Common no/fica/on process • Common adapters

Generate Project(s) from Template(s)


Addi5onal Ongoing Opera5ons Best Prac5ces

•  Delegate rou6ne repor6ng and inquiries to business departments

•  Establish log reten6on policy based on industry, document type, and partner inquiry paWerns

•  Develop and document processes for rou6ne backups and disaster recovery

•  Conduct periodic review of excep6on-‐handling and no6fica6on prac6ces


EXTOL Simplifies EDI Moderniza5on

Suppliers / Service Providers Customers Cloud/SaaS Applica/ons & Services

EXTOL Business Integrator

Dashboard / Reporting / Activity Monitoring

External Loca/ons, Partners, and Services

Enterprise Applica/ons Windows / Linux / VMware Enterprise Data

On-‐premise Applica/ons, Services, and Data

Data Warehouse

Opera/onal Data

Business Intelligence

Design-time Studio

Integration-as-a-Service option

Repository

•  Migra&on

•  Onboarding


Ques5ons?

Contact:

Website: www.extol.com Email: [email protected] Phone: +1 (570) 628-5500

20

I N T E R N A T I O N A L

Date post:	11-Mar-2018
Category:	Documents
Upload:	duongthuan
View:	220 times
Download:	3 times

Modernizing*EDI:**Best*Prac5cesfor** …edit&master&/tle&style& Modernizing*EDI: ... Establish...

Documents