EDI WhatNext

7/29/2019 EDI WhatNext

1/40

Rawlins EDI Consulting 1

Future EDI - What comes after

X12 and EDIFACT?

Michael C. Rawlins


2/40


Tools


3/40


What comes after X12 and

EDIFACT? Where are we now?

Defining What to exchange

New ways How to do it

Pioneers


4/40


Where are we now?

Systems evolution

How we do it now


5/40


Evolution of Applications

Custom

Development

Packaged

Applications

Batch On-Line Interactive

Stand Alone Interfaced IntegratedComponentized


6/40


Evolution of Business

Systems

Stand Alone

Systems

LANS, WANS,

VANS

Internet

Mainframes

and Minis

PCs Distributed

Computing

Client/

Server

Network

Computing


7/40Rawlins EDI Consulting 7

How We Do It Now

Senders EDI

Software

Receivers EDI

Software

Senders

BusinessApplication

ExportProgram

Receivers

BusinessApplication

ImportProgramExport

File

EDIEDI EDI ImportFile

X12 or

EDIFACTInterchange

Batch, Custom Interfaces, VANs



What

Functional Requirements

Open-edi and OO-edi

Other OO Analysis Approaches

Dictionary or Repository Based Approaches

Non-Functional Requirements


9/40



From Open-edi to OO-edi

Open-edi

Reference

Model

Reference Guide

Next Generation

of UN/EDIFACT

OO-edi

Standards

Report Draft

Report


11/40



Open-edi Key Concepts

Separate What from How

Business Operational View (BOV) - What

Functional Service View (FSV) - How

Scenario - Defines:

Roles

Information to be exchanged

Characteristics of the exchange


13/40


14/40


Why OO-Analysis?

Traditional Analysis

Processing

Data

?

OO Analysis

Object Class

Processing:

Methods

Data:

Attributes


15/40


OO-edi Outline

Develop Open-edi using OO techniques

BOV (What) Only

Object Modeling via UML

Focus on application vendors, not end users


16/40


Future OO-edi Standards

Standards will define:

Standard object classes

Interactions among objects

Scenarios will specify:

Roles

Objects and methods

Services required of FSV


17/40


Object Management Group

Cross-Industry Consortium

Responsible for CORBA standard

Defining Common Business Objects

Developing Electronic Commerce

Architecture


18/40


Microsoft

Partnering with application vendors

Developing industry based solutions

Notable examples:

Value Chain Initiative

Insurance


19/40


20/40


Non-Functional

Requirements

Quality or System Requirements, Goals

Examples

Trading Partner Mandates

Low Cost

Reliability

Modifiability and Flexibility

Tradeoffs


21/40


Impact of Non-Functional

Requirements

Can Determine Success or Failure

Will Dictate How


22/40


Example:

The Analysis Process

Completeness Cost

OO-edi

X12

BEACON


23/40


24/40


25/40


Why Objects?

Human

Resources

Shop

Floor

Without Objects

HumanResources

ShopFloor

With Objects


26/40


EDI by Distributed Objects

OMGs

CORBA

Microsoft

DCOM

Java RMI

Senders

ApplicationReceivers

ApplicationMiddleware

Middleware

Internet


27/40


OO-edi Implementation

Receivers


Senders


Internet

OO-edi Repository

OO-edi

Server

OO-edi

Server


28/40


BSI

Senders BSI

Server

Receivers BSIServer

Senders

BusinessApplication

ExportProgram

Receivers

BusinessApplication

ImportProgramExport

FileEDIBSI BSI Import

File

BSIInterchange


29/40


BSI Vs. X12

Receivers BSI

Server

BSI

BSIInterchange

ImportFile

Sender SpecificBSI Specification,

from Sender

Receivers

GenericBSI Specification

for Import File

Receivers X12

Software

EDI

X12Interchange

ImportFile

X12 TransactionSet Tables,Dictionaries

Trading PartnerSpecific Mapping

Commands

X12 Inbound BSI Inbound


30/40


XML - eXtensible Markup

Language

Derived from SGML

Web and Document Centric

More powerful than HTML

Template document types

Data tags:

19981101


31/40


XML for EDI

Use XML formats and tools for EDI

Primary Implementations:

Web based X12 or EDIFACT

Browser based Exchanges

Application to Application


32/40


XML for EDI via Browser

Catalog Purchasing

ZX-3111

World Wide Widgets


33/40


XML/EDI via Applications

Senders

BusinessApplication

XMLGenerator

XML

Mapper

Receivers

BusinessApplication

XMLParser

XML

Mapper

XML

Standard

Document Type

Definition


34/40


XML/EDI Development

XML/EDI Group

X12 XML/EDI

EDIFACT XML/EDI

Open Financial Exchange (OFX)

Open Trading Protocol (OTP)

Proprietary - SAP and others


35/40


Pioneers

Network Management Forum

ACORD


36/40


37/40


ACORD ObjX

Industry: Insurance

Purpose: Exchange information among

agents and insurers

What: Defined by object modeling

How: Microsofts COM/DCOM now, Java

and OMGs CORBA later


38/40


39/40


40/40

For More Information

www.metronet.com/~rawlins/future.html

[email protected]

?

Date post:	14-Apr-2018
Category:	Documents
Upload:	shaharhr1
View:	216 times
Download:	0 times

EDI WhatNext

Documents