Transcript ebXML Today
ebXML News, Implementations, Developments and more Presenters Name Presenters Title Affliation December 2002 [email protected] Contents Speaker Hint • Deployment Landscape • ebXML Today • Latest Specification Developments This presentation contains extensive materials, you should tailor this to your audience and the amount of time available • ebXML in the marketplace - vendor products • ebXML projects - deployments, funding, and pathfinder work • Summary Deployment Landscape Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness The 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 Needs • What are you trying to build anyway? Speaker Hint • Better EDI system? • Reach SME partners more effectively? • eMarketplace solution? • Next generation XML system and network? You can tailor this list to suit your audience and their industry • Open eGovernment systems? • Integration of major corporations applications? • Common industry collaboration and vocabularies? The Challenge of Change • 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. Business 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 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 Technologies RPC / Web Services ebXML Web eCommerce EDI 1990 1995 2000 2005 2010 e-Business Roadmap Regulated Activity Approval Consumer Safety Environmental Management Law Enforcement Legal Revenue Collection Trade (Import/Export) Transportation Workforce Management Support Delivery of Services Legislative Management Business Management of Information IT Management Planning and Resource Allocation Regulatory Management Inter-Agency Human Resources Admin Human Resources Admin Process Data Applications Reference Views Technology Architecture Technology Business Functional Technical Implementation Why is the engagement being undertaken? What are your organization's primary motivations and business drivers? What will your system do? What information will it provide? How will your system be realized with IT components? With what specific products and other components will your system be implemented? In what organization? According to what plan? Controls and Oversight Public Affairs Internal Risk Management and Mitigation Federal Financial Assistance Internal Operations/Infrastructure Financial Management Supply Chain Management Reference Framework Reference Models Services to Citizens Public Asset Management Marketable Asset Management Defense & Nat’l Security Ops* Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resource Social Services R&D Science Business Architecture Intra-Agency Financial Management Supply Chain Management For each reference view OBJECTIVES REQUIREMENTS MODELS STANDARDS PRINCIPLES & RULES ONTOLOGY RATIONALE AUTHORATATIVE SOURCE PRIORITY AS IS MIGRATION TO BE RISK MANAGEMENT XML itself is not enough • 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”. Solving 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 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) • 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! Standards Chemistry Traction XML W3C SOAP v1.2 W3C Market Adoption SOAP v1.1 WSDL v1.2 W3C WSDL v1.1 UDDI v3 UDDI.org eb MS v2 BPSS OASIS CEFACT CCSD OAG BODs eb Reg v2 CEFACT OASIS UMM/ UDDI v3x Content UML OASIS UBL Assembly UN/EDIFACT Proprietary JCV Consortia XML SGML ISO SDO Open Standardization Standing Reap the Benefits of Standards 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. ebXML Today Mission, focus and components ebXML Adoption Q4 - 2002 Government Commercial Industries North America Europe Asia ebXML 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? • 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 today • XML initiatives underway for specific industries – attempts at verbatim translation of EDI to XML • Consensus required on common requirements • No core infrastructure means – Incompatibility – Reinvention the norm – Segregated pockets of communication Traditional EDI Distributers Manufacturers Shippers Each arrow is a project XML agXML Boeing cXML Togaf OBI IATA OTA Rosettanet CIDX GCI xCBL UBL HL7 SWIFT xBRL Bolero SMDG EHD Odette VICS AIAG HRXML Walmart Open trans Acord Econstruct Ford xCat More than 400 initiatives ebXML automates business partner connection across industry boundaries Profile Profile Profile Profile ebXML Profile Profile Profile Profile Each arrow is a product ebXML Approach – Business Centric Each participant needs to specify their own: ‘Who, What, Why and How?’ Business Terms Organisation(s) Industry / Service Business process Context factors Transaction interchanges Information details Messaging details ebXML parlance CPPA BPSS Content Assembly XML content structure(s) Core components + Registry CPP + ebMS ebXML Business Profile Organisation Business process Information Technology Own Capabilities and Requirements to trading partners ebXML Registry ebXML Profile ebXML Profile matching ebXML Profile 1 ebXML Profile 2 Requirements Alignment App.2 App.1 ebXML Agreement Runtime communication ebXML Profile Components Collaboration Partner Agreements Collaboration Partner Profiles 5 Contract Business Integration 4 BP Specification Registry Taxonomy Workflow Process XForms 3 Specifications Schema Messages Assemblies 2 Motivation Rules Technology Integration 1 Data/Codes Nouns Time Events Services/Functions Verbs People Web Services Roles Network Secure content delivery ebMS/SOAP Deployment Flows / Components 4 Collaboration Partner Profiles 5 Collaboration Partner Agreements Registry 2 2 Rules Transform Content 3 Messages BP engine 4 Process Messages Nouns Verbs 1 Partner Events Adaptors Assembly To/From Nouns Payload 1 Secure Content Delivery Messaging 2 Templates Verbs Roles ebXML / WS Example – GM Bulk Used Cars <<BinaryCollaboration>> Bulk Buying General Motors Bulk Used Car Buyers Trading Partner Specifies Agreement (CPA) Business Process Specifications (BPSS) Bulk Buying Business Process Contains Business Transactions Speaker Hint You can change the context here to your own project Check Vehicle Availability Dealer Location Vehicle History Submit PO Contains XML Message DTDs Structures Example – Bulk Used Cars - Dealers Conceptual DealerLocator DealerLocator Map To Speaker Hint AvailableVehicle Activity Map To DealerLocation Activity DealerLocator e.g., Map DealerLocation Activity to the DealerLocator Web service Map To VehicleHistory Activity PurchaseRequest Activity Map To PurchaseApproval Activity DealerLocator Map To [Business Error] You can change the context here to your own project Business Analysts map B2B Transactions to the services available in Back-end systems Script into BPSS definitions Conceptual AvailableVehicle Activity <<BusinessTransactionActivity>> DealerLocation Activity <<BusinessTransactionActivity>> VehicleHistory Activity <<BusinessTransactionActivity>> VehicleHistory Activity PurchaseRequest <<BusinessTransactionActivity>> Activity You can change the context here to your own project The B2B Collaboration may be composed of several business transactions The resulting sequence is captured in a BPSS Vehicle Purchase Request Activity PurchaseApproval <<BusinessTransactionActivity>> Activity VehiclePurchase Approval Activity [Business Error] Business Transactions Physical Speaker Hint Example Deployment - GM Apps ebXML ebXML SOAP EJB Business Services Internal Firewall MSH J2EE Web Container CPA Speaker Hint ebXML Proces s Server Business Process Collaboratio n EJB Business Services Systems Interface ebXML BSI DMZ Internet B2B— Tradin g Partne r Orchestration Services J2EE Application Server Container COTS Apps Legac y Apps BPSS This deployment model shows the ebXML components, you can adapt this to your own implementation context. Legac y Apps DB Deployment 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 You can add Speaker Hint context here to your own project, and change the priority to those from your user commuity XML Information Exchange Quality ebXML Secure Authenticated Delivery and Tracking: (and long-term consistency) ebXML Messaging system, envelope format and payload with exchange source profile (CPP) controls Delivery Assembly Content Assembly: Schema: Content structure definition and simple content typing Schema XML Business logic for content structure decisions and explicit rules to enforce content, and interdependencies, with business exchange context, and content definition UID references Registry/ business information Dictionary UID content referencing system ensures consistent definition usage UID Comprehensive Messaging Delivery Web Services + ebXML Type Request/response Collaboration Communication RPC-style synchronous communication between tightly coupled services, Documentstyle asynchronous communication between loosely coupled services Synchronous, asynchronous communication CPP, CPA (WSDL within CPP, with CPA also) Business Service Interface description WSDL 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 marketplace Vendor products UCC 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/ Vendor Challenge – Implementing Business-Centric Approach - concept - linking - construct Strategic Business Drivers: Model / Process / Patterns / Constraints Frameworks & Stds Business Goals Conceptual Layer Alias Concepts Context Community of Interest Business Layer Reuse Compound Constructs Target Constructs See presentation slide notes. Technology Model / Constraints Partner Profile ‘Service’ Agreement Mappings Extension Layer • • • • • Outreach Role-Process Identification Standards & Framework Adoption Qualifier to Object Breakout Thesaurus Assignment Interchange Mapping • • • • • • Transaction / Presentation Collaboration Partner Specifics Elements vs Attributes Length, Datatyping and Masking Routing & Packaging Service Parameters Framework Envelope - eg. X12 slots Implementation Guide Implementation Layer Physical • • • • • • Requirements Identify business rules / patterns Scope; atomics & constructs Structure: Resolution / Indenture Workflow / process identification Mandatory vs Optional Sub-setting Codelists Legacy Reuse Publish Tactical Speaker Hint 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 ebXML projects Deployments, funding, and pathfinders today Speaker Hint This section can be customized to your audience. Additional project details can be found from the JMT website: http://www.ebxml.org/ebxml_jmt/index.htm/#documents US 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 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 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 Automotive • 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 Industry • 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 Industry Groups • 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 Latest Specification Developments Upcoming capabilities and extensions 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 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.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 Deployment One View to User Organizations Request Federation Make Associations Synch User Groups Local content control Federation Server OAG Registry Content Classification STAR Registry OAG BOD's STAR Assemblies STAR BPS Data Dictionary Data Dictionary Element Definitions Transaction Assembly STAR staff Element Definitions Transaction Assembly OAG staff approve Extending ebXML Registry Collaborat ion Protocol Profile (CPP) 1.. <<References>> 1.. Supported Business Process (BPS) <<references>> WSDL <<References>> CAM templates CAM templates DTDs / Schemas 1.. DTDs / Schemas Physical Payloads Binding Info INPUT/ OUTPUT DTDs & Schemas Leveraging UDDI work within OASIS Start here Collaboration Protocol Profile (CPA / CPP) tModel UDDI Registry WSDL CAM templates ebXML Registry Classifications Binding Info BPS Catalog INPUT/ OUTPUT DTDs & Schemas CAM templates INPUT/ OUTPUT DTDs & Schemas Core Comp. UBL project Core Comp. Core Comp. Core Comp. ebXML Registry Vision “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”. Summary Adopting ebXML - roadmap for implementers Planning • Incremental adoption of components and operational maturity • Plan 1 year, 2 year and 5 years out. Speaker Hint • Issues, implementation criteria, ROI, support, You can add your own interoperability, XML. project experience • Schema neutral content assembly. here and provide first hand reporting. • Separation of business semantics from XML mechanics. • Web services and discovery. Implementing ebXML roadmap INCREASING 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 Select payload standards Make assembly definitions Make assembly definitions MATURITY 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 Some 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 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 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 Government and the services it provides to the public. But without consistent policies and standards to underpin those systems it will not be possible to work together to deliver ‘joined up’ services.” RT Hon Ian McCartney MP, Minister of State, UK Cabinet Office “Never plan further than 24 months out. Everything is going to be so different by then, why do it?” Number One of Gartner’s Top 10 E-Business Imperatives; www.gartner.com “It is clear that ebXML will soon become the standard for all global trade. By implementing ebXML, GCI takes advantage of the excellent work that’s being accomplished to streamline many EDI processes and remove waste and redundancy from supply chains.” Industry Groups Support ebXML The Open Healthcare Group Find out more http://www.ebXML.org Thank you!