presenters name presenters title affliation december 2002 email@address.com presenters name...
Post on 14-Dec-2015
241 Views
Preview:
TRANSCRIPT
Presenters NamePresenters Title
AffliationDecember 2002Email@address.com
Presenters NamePresenters Title
AffliationDecember 2002Email@address.com
ebXML News, Implementations, Developments and more
ebXML News, Implementations, Developments and more
Contents Contents
• Deployment Landscape
• ebXML Today
• Latest Specification Developments
• ebXML in the marketplace - vendor products
• ebXML projects - deployments, funding, and pathfinder work
• Summary
SpeakerHint
This presentation contains extensive materials, you should tailor this to your audience and the amount of time available
Deployment LandscapeDeployment Landscape
Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness
Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness
The CIO nightmareThe CIO nightmare
• What standards do I choose?
• How do I build significant ROI for my organization?
• Can I leverage my existing systems?
• What resources are available to deploy my solution?
• What are my partners doing?
• How much of this is real?
• How do I avoid being in a vendor revolving doors strategy?
• What if I just build it my way and ignore everyone else?
Identifying the NeedsIdentifying the Needs
• What are you trying to build anyway?
• Better EDI system?
• Reach SME partners more effectively?
• eMarketplace solution?
• Next generation XML system and network?
• Open eGovernment systems?
• Integration of major corporations applications?
• Common industry collaboration and vocabularies?
SpeakerHint
You can tailor this list to suit your audience and their industry
• People accept that a digital world is coming and are adjusting their work habits accordingly:
– Virtual presentations and meetings
– All digital documents and transactions
– Digital photographs, voices, sound, and signatures (UPS, Radio Shack, Home Depot, Best Buy and more).
• Shared factor – naturally multi-lingual.
• Vast gulf between First World and Third World.
The Challenge of ChangeThe Challenge of Change
Business ChallengesBusiness Challenges
• In determining operational needs there are three levels and areas to include: – The first level is the overall operational
approach to solving large enterprise level interactions,
– then enterprise to small business interactions, – and small business to small business
interactions.
Affordable InfrastructureAffordable Infrastructure• For a large enterprise this translates into:
– Reducing the headcount of staff needed
– Decreasing the effort to migrate to implementation versions
– Lowering the necessary specialty skills to instead enabling general business staff (costs, productivity, customers).
• For small business it means:
– Being able to support multiple large partners diverse requests for information interchanges
– Supporting a single technology base
– Linking the interchange to your applications.
Electronic Business TechnologiesElectronic Business Technologies
1990 1995 2000 2005 2010
RPC / WebServices
ebXML
WebeCommerce
EDI
Support Delivery of ServicesLegislative ManagementBusiness Management of InformationIT ManagementPlanning and Resource AllocationRegulatory Management
Controls and OversightPublic AffairsInternal Risk Management and MitigationFederal Financial Assistance
Services to Citizens
Public Asset ManagementMarketable Asset ManagementDefense & Nat’l Security Ops*Diplomacy & Foreign RelationsDisaster ManagementDomestic EconomyEducationEnergy ManagementInsurancePublic HealthRecreation & National ResourceSocial ServicesR&D Science
Regulated Activity ApprovalConsumer SafetyEnvironmental ManagementLaw EnforcementLegalRevenue CollectionTrade (Import/Export)TransportationWorkforce Management
Internal Operations/Infrastructure
Human Resources Admin
Inter-Agency Intra-Agency
Financial ManagementSupply Chain Management
Human Resources Admin
Financial ManagementSupply Chain Management
Support Delivery of ServicesLegislative ManagementBusiness Management of InformationIT ManagementPlanning and Resource AllocationRegulatory Management
Controls and OversightPublic AffairsInternal Risk Management and MitigationFederal Financial Assistance
Services to Citizens
Public Asset ManagementMarketable Asset ManagementDefense & Nat’l Security Ops*Diplomacy & Foreign RelationsDisaster ManagementDomestic EconomyEducationEnergy ManagementInsurancePublic HealthRecreation & National ResourceSocial ServicesR&D Science
Regulated Activity ApprovalConsumer SafetyEnvironmental ManagementLaw EnforcementLegalRevenue CollectionTrade (Import/Export)TransportationWorkforce Management
Internal Operations/Infrastructure
Human Resources Admin
Inter-Agency Intra-Agency
Financial ManagementSupply Chain Management
Human Resources Admin
Financial ManagementSupply Chain Management
STANDARDS STANDARDS
AUTHORATATIVE
SOURCE PRIORITY
e-Business Roadmape-Business Roadmap
PRINCIPLES & RULESPRINCIPLES & RULES
OBJECTIVESOBJECTIVES
MODELS
MODELS
ONTOLOGY ONTOLOGY
REQUIREMENTSREQUIREMENTS
RISK MANAGEMENTRISK MANAGEMENTRISK MANAGEMENTRISK MANAGEMENT
RATIONALERATIONALERATIONALERATIONALE
Business
Why is the engagement being undertaken? What are your organization's primary motivations and business drivers?
Functional
What will your system do? What information will it provide?
Technical
How will your system be realized with IT components?
Implementation
With what specific products and other components will your system be implemented? In what organization? According to what plan?
Reference Views
AS IS
MIGRATION
TO BE
For each reference view
Technology ArchitectureTechnology
Applications
Business Architecture
Reference Models
Reference Framework Data
Process
• XML, by itself, does not solve interoperability problems yet
it is an important tool for doing so.
• XML does not provide semantics.
• XML by itself is not the magic bullet.
• What we really need is a consistent set of methods for
building interoperable eBusiness systems using XML –
“railroads and telephony”.
XML itself is not enoughXML itself is not enough
Solving the right problemSolving the right problem
• Web services:– interactive point-to-point unrestricted transactions– internal backend system sockets
• ebXML:– secure, reliable business-to-business exchanges– metadata alignment, consistent vocabularies, registries– open eBusiness architecture, business process engineering
• W3C XML:– wire formats, syntax parsing, security, storage and retrieval– middleware plumbing, web service plumbing
Standards FocusStandards Focus
• OASIS– ebXML technology specifications– Web service technology specifications– Industry XML vocabularies– Registry technology specifications
• CEFACT– ebXML architecture specifications – UMM / UML– Migration of UN/EDIFACT to UMM world– Business Process alignment
• Industry Standards Groups– Local vocabularies for vertical industry use
Standards Focus (more)Standards Focus (more)
• ISO– International standard tables and measures
– Registry technology specifications
• OMG– Programming language technology
• EAN/ UCC / CEN / DISA and others– Cross-industry integration
• Is there overlap and confusion of mission? YES!
CCSDCEFACT
BPSSCEFACT
UMM/UML
XML
UN/EDIFACT
UBL
OAG BODs
ContentAssembly
Standards Chemistry Standards Chemistry M
arke
t Ado
ptio
n
Open Standardization
Proprietary JCV Consortia SDO
SGMLISO
XMLW3C
SOAP v1.1 SOAP v1.2W3C
UDDI v3UDDI.org
WSDL v1.2W3C
eb MS v2OASIS
WSDL v1.1
UDDI v3xOASIS
eb Reg v2OASIS
Traction
Standing
ebXML spec’s
web services
Lower costs and reduced errors.
Greater efficiency of processes.
Drive consistent business conduct.
Increase speed of deployment.
Improve inventory controls.
Reduce risk for businesses.
Provide investment protection.Key:
Champion awareness and recognition of the value of standards.
The first step is knowledge.
Reap the Benefits of StandardsReap the Benefits of Standards
ebXML TodayebXML Today
Mission, focus and componentsMission, focus and components
ebXML AdoptionebXML Adoption
NorthAmerica
Europe Asia
Government
Commercial
Industries
Q4 - 2002
ebXML HistoryebXML History
• Begun as 18-month initiative in November 1999
• V1.0 Specifications delivered on schedule in May 2001
• Developed in an open process by more than 2000 participants representing 100 organizations in 150 countries
• Facilitation meetings held in N.America, Europe and Japan
• Development and deployment of the specifications is continuing within OASIS and CEFACT with support from NIST, UCC/EAN, EU and more.
ebXML – Why and How?ebXML – Why and How?
• Computers are quicker and more reliable than people (in processing data), and offer potential business ROI
• Mature organisations process their information electronically and reap very significant competitive and production benefits
• Information exchange & accounting between organisations is:– largely still paper / fax based– dictated by regulation or large customers– great once you get it working and stable electronically– cost savings and availability via internet as delivery medium– international need to enable global trade and opportunities– eCommerce / Web revolution well underway (e.g. eBay+)
Challenges of e-business todayChallenges of e-business today
• XML initiatives underway for specific industriesXML initiatives underway for specific industries– attempts at verbatim translation of EDI to XML
• Consensus required on common requirementsConsensus required on common requirements• No core infrastructure meansNo core infrastructure means
– IncompatibilityIncompatibility– Reinvention the norm Reinvention the norm – Segregated pockets of communicationSegregated pockets of communication
Traditional EDITraditional EDI
Each arrow is a project
Distributers
Manufacturers
Shippers
XMLXML
More than 400 initiatives
HR-XML
EHD
xCat
UBL
Rosettanet
OTAIATA
cXML
E-construct
Ford
SMDG
AIAGGCI
OBI
Boeing
Opentrans
Odette
xCBL
HL7
Acord
CIDX
xBRL Wal-mart
agXML
VICS
SWIFT
Togaf
Bolero
Each arrow is a product
Profile
Profile
Profile
Profile
Profile
Profile
Profile
Profile
ebXML
ebXML automates business partner connectionacross industry boundaries
ebXML Approach – Business CentricebXML Approach – Business Centric
Organisation(s)Industry / ServiceBusiness processContext factors
Transaction interchangesInformation detailsMessaging details
Each participant needs to specify their own: Each participant needs to specify their own:
‘‘Who, What, Why and How?’Who, What, Why and How?’
CPPA
BPSSContent AssemblyXML content structure(s)Core components + RegistryCPP + ebMS
Business TermsBusiness Terms ebXML parlanceebXML parlance
ebXML Business ProfileebXML Business Profile
Own Capabilities andRequirements totrading partners
OrganisationBusiness process
InformationTechnology
ebXML ProfileebXMLRegistry
ebXML Profile matchingebXML Profile matching
ebXML Profile 1 ebXML Profile 2
ebXML Agreement
RequirementsAlignment
App.1 App.2
Runtime communication
ebXML Profile ComponentsebXML Profile Components
Technology Integration
Business Integration
VerbsVerbs
Motivation Time People
MessagesMessages
RulesRules EventsEvents
ProcessProcess
RolesRoles
Specifications Schema
Workflow
Contract
Secure contentdelivery
Secure contentdelivery
Directory Services
Collaboration PartnerProfiles
Collaboration PartnerProfiles
2
1
3
4
5
Presentation
Collaboration PartnerAgreements
Collaboration PartnerAgreements
Artifact relationships
AssembliesAssemblies
BP SpecificationBP Specification
NounsNouns
Data/Codes Services/Functions Network
XFormsXForms
ebMS/SOAPebMS/SOAP
Registry Taxonomy
Web ServicesWeb Services
Collaboration PartnerAgreements
Collaboration PartnerAgreements
MessagesMessages
Collaboration PartnerProfiles
Collaboration PartnerProfiles
RulesRules
EventsEvents
ProcessProcess
RolesRoles
5
4
2
1
VerbsVerbsNounsNouns
Secure ContentDelivery
Secure ContentDelivery
MessagesMessages
VerbsVerbs
NounsNouns
2
3
1
4
2
To/From
Partner
Deployment Flows / ComponentsDeployment Flows / Components
Content Payload
Templates
Transform
Registry
Messaging
Adaptors
BP engine
ebXML /WS
Assembly
Example – GM Bulk Used CarsExample – GM Bulk Used Cars
Bulk Buying
Business Process
Specifications(BPSS)
Trading PartnerAgreement
(CPA)Specifies Bulk Buying
Business Process
Check Vehicle AvailabilityDealer LocationVehicle HistorySubmit PO
DTDs
Contains
Contains
Business Transactions
XML Message Structures
General Motors
<<BinaryCollaboration>>
Bulk UsedCar Buyers
SpeakerHint
You can change the context here to yourown project
Example – Bulk Used Cars - DealersExample – Bulk Used Cars - Dealers
DealerLocation Activity
DealerLocator
Map To
PurchaseRequest Activity
DealerLocator
Map To
VehicleHistory Activity
DealerLocator
DealerLocator
AvailableVehicle Activity
Map To
Map To
PurchaseApproval Activity
Map To [Business Error]
e.g., Map DealerLocation Activity to the DealerLocator Web service Business Analysts
map B2B Transactions to the services available in Back-end systems
Conceptual
SpeakerHint
You can change the context here to yourown project
Script into BPSS definitionsScript into BPSS definitions
<<BusinessTransactionActivity>>Vehicle Purchase Request Activity
PurchaseRequest Activity
<<BusinessTransactionActivity>>
AvailableVehicle Activity
[Business Error]
<<BusinessTransactionActivity>>
DealerLocation Activity
<<BusinessTransactionActivity>>VehicleHistory Activity
VehicleHistory Activity
<<BusinessTransactionActivity>>VehiclePurchase Approval Activity
PurchaseApproval Activity
The B2B Collaboration may be composed of several business transactions
The resulting sequence is captured in a BPSS
Business Transactions
Conceptual
Physical
SpeakerHint
You can change the context here to yourown project
DB
Legacy
Apps
COTSApps
Legacy
Apps
J2EE Application
Server Container
Orchestration Services
EJBBusinessServices
Syst
em
s In
terf
ace
ebXML
MSH
ebXML
Process
Server
ebXML
BSI
Apps
B2B—Tradin
g Partne
r
CPA BPSS
J2EE Web
Container
ebXML
SOAP
Business Process
Collaboration
DMZ
Internal Firewall
EJBBusinessServices
Inte
rnet
Example Deployment - GMExample Deployment - GM
SpeakerHint
This deployment model shows the ebXML components, you can adapt this to your own implementation context.
Deployment Issues - Information QualityDeployment Issues - Information Quality
• For eBusiness - vital to ensure low-cost interoperability
• Accounting – mandatory for accuracy and verification
• US Gov – critical for homeland security integration
• Globally – meeting the challenges of a secure reliable electronic marketplace
SpeakerHint
You can addcontext here to yourown project, and change the priority to those from your user commuity
XMLbusiness information
Schema
Delivery Assembly
Schema: Content structure definitionandsimple content typing
Content Assembly: Business logic forcontent structure decisions andexplicit rules to enforce content,and interdependencies, with business exchange context, and content definition UID references
ebXML Secure Authenticated Delivery and Tracking: ebXML Messaging system, envelope format and payload with exchange source profile (CPP) controls
UID content referencing systemensures consistent definition usage
UID
Registry/Dictionary
(and long-term consistency)(and long-term consistency)
XML Information Exchange QualityXML Information Exchange Quality
Comprehensive Messaging DeliveryComprehensive Messaging Delivery Web Services + ebXML
Type Request/response Collaboration
Communication RPC-style synchronous communication between tightly coupled services, Document-style asynchronous communication between loosely coupled services
Synchronous, asynchronous communication
Business Service Interface description WSDL
CPP, CPA(WSDL within CPP, with CPA also)
Protocol and Formats SOAP, XML ebXML Message Service (over SOAP), XML, BPSS (as "business" protocol)
Content Standards None Recommended Standards (e.g. OAGI BODs, EDIFACT, UBL)
How to find business partners
UDDI Registry ebXML Registry(UDDI Registry may point to an ebXML Registry or Registry objects (e.g. CPA))
With thanks to Alan Kotok from his recent article : http://www.webservices.org/index.php/article/articleview/451/1/22/
ebXML in the marketplaceebXML in the marketplace
Vendor productsVendor products
UCC ebXML Interoperability CertificationUCC ebXML Interoperability Certification
• Eleven vendors:
XML Global Fujitsu
Sun Microsystems Sybase
bTrade Sterling Commerce
WebMethods Cyclone Commerce
Mercator Excelon
TIBCO
• Full list of other ebXML vendors available from:-
• http://www.ebxml.org/implementations/
Partner Profile
Partner Profile
Implementation GuideImplementation Guide
Implementation Layer
Extension Layer
Business Layer
MappingsMappings
ConceptsConcepts
Conceptual Layer
Frameworks & StdsFrameworks & Stds
Transaction / Presentation • Collaboration Partner Specifics• Elements vs Attributes • Length, Datatyping and Masking• Routing & Packaging• Service Parameters• Framework Envelope - eg. X12 slots
Requirements • Identify business rules / patterns• Scope; atomics & constructs• Structure: Resolution / Indenture• Workflow / process identification• Mandatory vs Optional • Sub-setting Codelists
Semantics• Define Business Context• Use Case and Sequence Diagrams• Identify Authoritative Sources• Register/Link Source Concepts• Register Internal Concepts• Assign Classification• Place into organization’s ontology
Outreach • Role-Process Identification • Standards & Framework Adoption• Qualifier to Object Breakout• Thesaurus Assignment• Interchange Mapping
Target ConstructsTarget Constructs
PhysicalPhysical
Community of Interest
Business Drivers: Model / Process / Patterns / Constraints
Technology Model / Constraints
LegacyLegacy
Str
ateg
ic T
actic
al Pub
lish
Reuse
Alias
Business Goals
Reuse -CompoundConstructs
‘Service’Agreement‘Service’
Agreement
ContextContext
- concept
- linking
- construct
Vendor Challenge – Implementing Business-Centric Approach
SpeakerHint
See presentation slide notes.
ebXML projectsebXML projects
Deployments, funding, and pathfinders todayDeployments, funding, and pathfinders today
SpeakerHint
This section can be customized to youraudience. Additional project details can be found from the JMT website: http://www.ebxml.org/ebxml_jmt/index.htm/#documents
US GovernmentUS Government
• CDC – lightweight ebXML client developed and being UCC certified• Homeland Security• NIST – OAG test-bed• DARPA – Advanced Supply Chain• CIO Council – Registry• DFAS – Information Agility
– Addresses– Invoices
• FDIC – MDR with intelligent mapping project
Canadian GovernmentCanadian Government
• PWGSC – Registry – base implementation path finder
• PWGSC - EDI transformation using ebXML approach - evaluation
• XML in Ontario (XiO) – In Phase 2 through March 2003, evaluating tools to use ebXML Reg/Rep for prototype implementation – committed to ebXML.
• EDAT – e-Forms Domain Architecture - In 2002, integrated MS BizTalk environment with a Registry and ebXML adapter.
European ebXMLEuropean ebXML
• CEN/ISSS
• EAN
• CEN / eBIS Vendor forum - project began in September – to demonstrate implementations in Europe using ebXML
• SEEM initiative for eCommerce
• Industry - Steel 24x7 Open eXchange
• GM demonstrated their ebXML system with web service integration at AIAG, Detroit - 25th Sept’02
• Covisint – endorsed ebXML
• STAR – ebXML messaging pathfinder implemented and delivered
• AIAG – working from X12 base
• OAG - Vendor challenges using automotive payloads and business processes
• Straw poll in Detroit – 50% of new projects now using OAG V8 XML
AutomotiveAutomotive
IndustryIndustry
• Australia
– State of Victoria (Sydney)
– Utility Supply – Gas and Electric Distribution
– In production – 100,000 ebXML messaging transactions daily.
• USA - State of Texas
– Electric distribution – with power suppliers
– Using ebXML messaging for daily transactions
• DISA X12 – DRIVE Registry using GoXML
– OTA and IFX
• OAG – implementing Registry
– OAGIS V8.0 schemas
– Vendor challenges
• UCCNet ebMS certification
• OAG - RosettaNet – ebXML migration
Industry GroupsIndustry Groups
Latest Specification Developments
Latest Specification Developments
Upcoming capabilities and extensionsUpcoming capabilities and extensions
Content Assembly Mechanism (CAM)Content Assembly Mechanism (CAM)
• Legacy payloads can be used “as is”• Supports vocabulary alignment and multi-lingual
element tags• Minimizes overhead in payload itself – can be just
simple structure• Provides ability to do automated mapping• OASIS TC – scheduled to deliver complete
specifications in July, 2003
Upcoming Registry DevelopmentsUpcoming Registry Developments
• ebXML V3.0 enhancements - partner discovery / extended content management services
• Delivering on eBusiness web services - with critical federated model
• Allows open industry and government deployments worldwide
• Allows building collaborating communities
Registry v 3.0Registry v 3.0
• Cooperating Registry Model
– Allows linking multiple ebXML registries together
– Loosely-coupled federation approach
• Local operators have autonomy over their own registry
• Can make several small registries appear as one single large registry
– Supports direct accessing via URI (REST approach)
– Built using the existing V2.0 Registry components
– Event notification mechanism
Example DeploymentExample Deployment
STAR RegistrySTAR Registry
Federation Server
Federation Server
OAG RegistryOAG Registry
Content Classification
OAG BOD's
DataDictionary
Element Definitions
Transaction Assembly
STAR Assemblies
DataDictionary
Element Definitions
Transaction Assembly
STAR BPS
OAG staffapprove
One View to UserOrganizations
Request FederationMake AssociationsSynch User GroupsLocal content control
STAR staff
Extending ebXML Registry Extending ebXML Registry
Collaboration
ProtocolProfile (CPP)
1..
SupportedBusinessProcess(BPS)
<<References>>
DTDs /Schemas DTDs /
Schemas
INPUT/OUTPUTDTDs & Schemas
<<references>>
1..
WSDL
BindingInfoCAM templates
CAM templates
Physical Payloads
1..
<<References>>
Leveraging UDDI work within OASISLeveraging UDDI work within OASIS
CollaborationProtocol
Profile (CPA / CPP)
tModel
INPUT/OUTPUTDTDs & Schemas
WSDL
BindingInfo
UDDI Registry
ebXMLRegistry
CoreComp.
CoreComp.
CoreComp.
CoreComp.
Start here
Classifications
BPS Catalog
CAM templates
INPUT/OUTPUTDTDs & Schemas
CAM templates
UBL project
ebXML Registry VisionebXML Registry Vision
“A semantic registry is the key foundation block upon
which global electronic business exchanges will be
built”.
SummarySummary
Adopting ebXML - roadmap for implementersAdopting ebXML - roadmap for implementers
PlanningPlanning
• Incremental adoption of components and operational maturity
• Plan 1 year, 2 year and 5 years out.
• Issues, implementation criteria, ROI, support, interoperability, XML.
• Schema neutral content assembly.
• Separation of business semantics from XML mechanics.
• Web services and discovery.
SpeakerHint
You can add your own project experiencehere and provide first hand reporting.
Implementing ebXML roadmapImplementing ebXML roadmap
Existing Integration New Deployment
1 Install messaging Install messaging
2 Create partner delivery details Create partner delivery details
3 Document business process Agree on business process
4 Migrate existing payloads to new delivery
Make assembly definitions
Select payload standards
Make assembly definitions
Map to applications
Build payload content
4 Adopt Business Process automation - BPSS Adopt Business Process automation - BPSS
5 Cross reference assembly to registry dictionary
Cross reference assembly to registry dictionary
6 Publish details to registry Publish details to registry
I N C
R E
A S
I N G
M A
T U
R I T
Y
Some ebXML selection metricsSome ebXML selection metrics
• B2B or large A2A Environments— extending or integrating enterprise systems, or when loosely coupled messaging is desirable
• Need Reliable Messaging— when enterprise services perform updates, insert, or deletes to the underlying data model, reliable messaging becomes critical
• Security is a Concern—when different security profiles and requirements exist between trading partners
• High scalability requirements—ebXML’s loosely coupled messaging architecture allows for horizontal scalability, queuing, and clustering
• Want to Leverage Industry Standards—XML grammars, business process modelling and trading partner agreements
Main ebXML conceptsMain ebXML concepts
• Business Processes – defined as models in UMM, scripted in XML
• Business Messages – content agnostic - exchanged using ebMS
• Trading Partner Agreement – specifies parameters for businesses to interface with each other – expressed in XML
• Messaging Layer – moves the actual XML data between trading partners – ebMS
• Core components – library of pre-defined business vocabulary artifacts
• Collaboration Registry - Provides a “container” for process models, vocabularies, assembly templates, partner profiles + discovery.
Continuing ebXML WorkContinuing ebXML Work
• Latest Specifications; available at http://www.ebxml.org
• Infrastructure work continuing at OASIS
– Messaging
– Collaborative Partner Agreements (CPA)
– Interoperability, Implementation, Conformance
– Registry / Assembly
• Conceptual / Process related work continuing at UN/CEFACT
– Business Process
– Core Components
– Modelling / UMM
““Information systems have the potential to transform the Information systems have the potential to transform the Government and the services it provides to the public.Government and the services it provides to the public.
But without consistent policies and standards to underpin But without consistent policies and standards to underpin those systems it will not be possible to work together to those systems it will not be possible to work together to
deliver ‘joined up’ services.”deliver ‘joined up’ services.”RT Hon Ian McCartney MP, Minister of State, UK Cabinet OfficeRT Hon Ian McCartney MP, Minister of State, UK Cabinet Office
““Never plan further than 24 months out. Everything Never plan further than 24 months out. Everything is going to be so different by then, why do it?”is going to be so different by then, why do it?”
Number One of Gartner’s Top 10 E-Business Imperatives; www.gartner.comNumber One of Gartner’s Top 10 E-Business Imperatives; www.gartner.com
““It is clear that ebXML will soon become the standard for It is clear that ebXML will soon become the standard for all global trade. By implementing ebXML, GCI takes all global trade. By implementing ebXML, GCI takes
advantage of the excellent work that’s being advantage of the excellent work that’s being accomplished to streamline many EDI processes and accomplished to streamline many EDI processes and remove waste and redundancy from supply chains.”remove waste and redundancy from supply chains.”
Industry Groups Support ebXMLIndustry Groups Support ebXML
The Open Healthcare Group
Find out more
http://www.ebXML.org
Thank you!
Find out more
http://www.ebXML.org
Thank you!
top related