Rawlins EDI Consulting1 Future EDI - What comes after X12 and EDIFACT? Michael C. Rawlins.
-
Upload
jerome-lyons -
Category
Documents
-
view
229 -
download
5
Transcript of Rawlins EDI Consulting1 Future EDI - What comes after X12 and EDIFACT? Michael C. Rawlins.
Rawlins EDI Consulting 1
Future EDI - What comes after X12 and EDIFACT?
Future EDI - What comes after X12 and EDIFACT?
Michael C. RawlinsMichael C. Rawlins
Rawlins EDI Consulting 2
ToolsTools
Rawlins EDI Consulting 3
What comes after X12 and EDIFACT?What comes after X12 and EDIFACT? Where are we now?Where are we now? Defining “What” to exchangeDefining “What” to exchange New ways “How” to do itNew ways “How” to do it PioneersPioneers
Rawlins EDI Consulting 4
Where are we now?Where are we now?
Systems evolutionSystems evolution How we do it nowHow we do it now
Rawlins EDI Consulting 5
Evolution of ApplicationsEvolution of Applications
CustomDevelopment
PackagedApplications
Batch On-Line Interactive
Stand Alone Interfaced Integrated “Componentized”
Rawlins EDI Consulting 6
Evolution of BusinessSystemsEvolution of BusinessSystems
Stand AloneSystems
LANS, WANS,VANS
Internet
Mainframesand Minis
PCs DistributedComputing
Client/Server
NetworkComputing
Rawlins EDI Consulting 7
How We Do It NowHow We Do It Now
Sender’s EDISoftware
Receiver’s EDISoftware
Sender’sBusiness
Application
ExportProgram
Receiver’sBusiness
Application
ImportProgramExport
FileEDIEDI EDI Import
File
X12 orEDIFACTInterchange
Batch, Custom Interfaces, VANsBatch, Custom Interfaces, VANs
Rawlins EDI Consulting 8
“What”“What”
Functional RequirementsFunctional Requirements Open-edi and OO-ediOpen-edi and OO-edi Other OO Analysis ApproachesOther OO Analysis Approaches Dictionary or Repository Based ApproachesDictionary or Repository Based Approaches
Non-Functional RequirementsNon-Functional Requirements
Rawlins EDI Consulting 9
Defining FunctionalityDefining Functionality
Functional Functional Requirements = Requirements = Processing and Processing and DataData
Standards = Standards = Codified Functional Codified Functional RequirementsRequirements
Processes
Documents
Data
Rawlins EDI Consulting 10
From Open-edi to OO-ediFrom Open-edi to OO-edi
Open-ediReference
Model
Reference Guide“Next Generationof UN/EDIFACT”
OO-ediStandards
Report DraftReport
Rawlins EDI Consulting 11
Open-edi DefinitionOpen-edi Definition
““The application to application exchange of The application to application exchange of any predefined and structured data for any predefined and structured data for business purposes without human business purposes without human intervention and without prior agreement”.intervention and without prior agreement”.
Rawlins EDI Consulting 12
Open-edi Key ConceptsOpen-edi Key Concepts
Separate “What” from “How”Separate “What” from “How” Business Operational View (BOV) - “What”Business Operational View (BOV) - “What” Functional Service View (FSV) - “How”Functional Service View (FSV) - “How” Scenario - Defines:Scenario - Defines:
RolesRoles Information to be exchangedInformation to be exchanged Characteristics of the exchangeCharacteristics of the exchange
Rawlins EDI Consulting 13
Evolution of Analysis TechniquesEvolution of Analysis Techniques
Napkins NarrativeText
StructuredAnalysis
Informationand ProcessModeling
ObjectModeling
Rawlins EDI Consulting 14
Why OO-Analysis?Why OO-Analysis?
Traditional Analysis
Processing
Data
?
OO Analysis
Object Class
Processing:“Methods”
Data:“Attributes”
Rawlins EDI Consulting 15
OO-edi OutlineOO-edi Outline
Develop Open-edi using OO techniquesDevelop Open-edi using OO techniques BOV (“What”) Only BOV (“What”) Only Object Modeling via UMLObject Modeling via UML Focus on application vendors, not end usersFocus on application vendors, not end users
Rawlins EDI Consulting 16
Future OO-edi StandardsFuture OO-edi Standards
Standards will define:Standards will define: Standard object classesStandard object classes Interactions among objectsInteractions among objects
Scenarios will specify:Scenarios will specify: RolesRoles Objects and methodsObjects and methods Services required of FSVServices required of FSV
Rawlins EDI Consulting 17
Object Management GroupObject Management Group
Cross-Industry ConsortiumCross-Industry Consortium Responsible for CORBA standardResponsible for CORBA standard Defining Common Business ObjectsDefining Common Business Objects Developing Electronic Commerce Developing Electronic Commerce
ArchitectureArchitecture
Rawlins EDI Consulting 18
MicrosoftMicrosoft
Partnering with application vendorsPartnering with application vendors Developing industry based solutionsDeveloping industry based solutions Notable examples:Notable examples:
Value Chain InitiativeValue Chain Initiative InsuranceInsurance
Rawlins EDI Consulting 19
Dictionaries andRepositoriesDictionaries andRepositories
BSR - ISO Basic Semantic RepositoryBSR - ISO Basic Semantic Repository UDEF - CALS Universal Data Element UDEF - CALS Universal Data Element
FrameworkFramework BEACON - ICARIS Project “Object BEACON - ICARIS Project “Object
Nexus”Nexus”
Rawlins EDI Consulting 20
Non-FunctionalRequirementsNon-FunctionalRequirements
““Quality” or “System” Requirements, GoalsQuality” or “System” Requirements, Goals ExamplesExamples
Trading Partner MandatesTrading Partner Mandates Low CostLow Cost ReliabilityReliability Modifiability and FlexibilityModifiability and Flexibility
TradeoffsTradeoffs
Rawlins EDI Consulting 21
Impact of Non-Functional RequirementsImpact of Non-Functional Requirements
Can Determine Success or FailureCan Determine Success or Failure Will Dictate “How”Will Dictate “How”
Rawlins EDI Consulting 22
Example:The Analysis ProcessExample:The Analysis Process
Completeness Cost
OO-ediX12BEACON
Rawlins EDI Consulting 23
“How”“How”
ObjectsObjects Distributed ObjectsDistributed Objects OO-edi ImplementationOO-edi Implementation BSIBSI XMLXML
Rawlins EDI Consulting 24
Standards!Standards!
Standards!!Standards!!
Standards!!!Standards!!!
Rawlins EDI Consulting 25
Why Objects?Why Objects?
HumanResources
ShopFloor
Without Objects
HumanResources
ShopFloor
With Objects
Rawlins EDI Consulting 26
EDI by Distributed ObjectsEDI by Distributed Objects
OMG’s OMG’s CORBACORBA
Microsoft Microsoft DCOMDCOM
Java RMIJava RMI
Sender’sApplication
Receiver’sApplication
Middleware
Middleware
Internet
Rawlins EDI Consulting 27
OO-edi ImplementationOO-edi Implementation
Receiver’sApplication
Middleware
Sender’sApplication
Middleware
Internet
OO-edi Repository
OO-ediServer
OO-ediServer
Rawlins EDI Consulting 28
BSIBSI
S e n d e r’s B S IS e rv e r
R e c e iv e r’s B S IS e rv e r
S e n d e r’sB u s in e s s
A p p lic a tio n
E x p o rtP ro g ra m
R e c e iv e r’sB u s in e s s
A p p lic a tio n
Im p o rtP ro g ra mE x p o rt
F ileE D IB S I B S I Im p o rt
F ile
B S IIn te rc h a n g e
Rawlins EDI Consulting 29
BSI Vs. X12BSI Vs. X12
Receiver’s BSIServer
BSI
BSIInterchange
ImportFile
Sender SpecificBSI Specification,
from Sender
Receiver’sGeneric
BSI Specificationfor Import File
Receiver’s X12Software
EDI
X12Interchange
ImportFile
X12 TransactionSet Tables,Dictionaries
Trading PartnerSpecific Mapping
Commands
X12 Inbound BSI Inbound
Rawlins EDI Consulting 30
XML - eXtensible Markup LanguageXML - eXtensible Markup Language
Derived from SGMLDerived from SGML Web and Document Centric Web and Document Centric More powerful than HTMLMore powerful than HTML
Template document types Template document types Data tags:Data tags:
<SHIP_DATE>19981101</SHIP_DATE><SHIP_DATE>19981101</SHIP_DATE>
Rawlins EDI Consulting 31
XML for EDIXML for EDI
Use XML formats and tools for EDIUse XML formats and tools for EDI Primary Implementations:Primary Implementations:
Web based X12 or EDIFACTWeb based X12 or EDIFACT Browser based ExchangesBrowser based Exchanges Application to ApplicationApplication to Application
Rawlins EDI Consulting 32
XML for EDI via Browser XML for EDI via Browser
Catalog Purchasing
<Part_Number>ZX-3111</Part_Number>
<Vendor>World Wide Widgets</Vendor>
Rawlins EDI Consulting 33
XML/EDI via ApplicationsXML/EDI via Applications
Sender’sBusiness
Application
XMLGenerator
XMLMapper
Receiver’sBusiness
Application
XMLParser
XMLMapper
XML
StandardDocument Type
Definition
Rawlins EDI Consulting 34
XML/EDI DevelopmentXML/EDI Development
XML/EDI GroupXML/EDI Group X12 XML/EDIX12 XML/EDI EDIFACT XML/EDIEDIFACT XML/EDI Open Financial Exchange (OFX)Open Financial Exchange (OFX) Open Trading Protocol (OTP)Open Trading Protocol (OTP) Proprietary - SAP and othersProprietary - SAP and others
Rawlins EDI Consulting 35
PioneersPioneers
Network Management ForumNetwork Management Forum ACORDACORD
Rawlins EDI Consulting 36
NMF CIGPNMF CIGP
Industry: Telecommunications Industry: Telecommunications Purpose: Exchange operations information Purpose: Exchange operations information
between carriersbetween carriers What: Defined by object modelingWhat: Defined by object modeling How: Common Interconnection Gateway How: Common Interconnection Gateway
Platform supporting many technologiesPlatform supporting many technologies
Rawlins EDI Consulting 37
ACORD ObjXACORD ObjX
Industry: InsuranceIndustry: Insurance Purpose: Exchange information among Purpose: Exchange information among
agents and insurersagents and insurers What: Defined by object modelingWhat: Defined by object modeling How: Microsoft’s COM/DCOM now, Java How: Microsoft’s COM/DCOM now, Java
and OMG’s CORBA laterand OMG’s CORBA later
Rawlins EDI Consulting 38
What Next?What Next?
Many emerging technologiesMany emerging technologies Standards lagging behindStandards lagging behind Babble, Esperanto, or BabbleFish?Babble, Esperanto, or BabbleFish?
?
Rawlins EDI Consulting 39
What to Do?What to Do?
Identify your Requirements, particularly Identify your Requirements, particularly Non-Functional RequirementsNon-Functional Requirements
Start planning strategyStart planning strategy Standards - monitor, participateStandards - monitor, participate Talk with application vendorsTalk with application vendors
?
Rawlins EDI Consulting 40
For More InformationFor More Information
www.metronet.com/~rawlins/future.htmlwww.metronet.com/~rawlins/future.html [email protected]@metronet.com
?