Copyright © Open Applications Group, Inc. All rights reserved OAGIS Project Definition High Volume OAGIS – EXI subgroup Kurt Kanaskie – Merck July 8, 2009

Copyright © Open Applications Group, Inc. All rights reserved Agenda Proposed Scope Key Deliverables Summary –Position Paper –Sequence Diagrams –Proof of Concept Business Workflows Workgroup Members Planned Schedule Assumptions, Dependencies, and Issues Outside Resources Required Next Steps Questions

Copyright © Open Applications Group, Inc. All rights reserved Proposed Scope Develop a High Volume solution for OAGIS. The majority of existing High Volume interfaces have been developed as point-to-point. However, we believe the given benefits, of implementing canonicals within the messaging space, apply equally to ETL. We believe the software tools, currently used to implement High Volume, cannot maintain required performance levels using current XML text format as the canonical. Therefore, the proposed High Volume canonical standard, will be based on the emerging W3C standard Efficient XML Interchange (EXI). A Position Paper and proof of concept using EXI standard will be demonstrated using existing application solutions.

Copyright © Open Applications Group, Inc. All rights reserved Key Deliverables Summary 2 simple sequences 2 High Volume Nouns 2 High Volume BODs XML to EXI encoding/decoding Direct EXI encoding/decoding via XSLT HRPayroll SyncPersonnel PurchasingStores ShowPurchaseOrder XML text instances Encode Decode EXI Format Instances XSLT Encode Decode XML text instances

Copyright © Open Applications Group, Inc. All rights reserved Business Workflows Sequence 1: –HR sends personnel changes to Payroll Sequence 2: –Purchasing sends all Purchase Orders, for a specific time period, to Stores Note: Both flows follow an ETL pattern due to potential for mass volume transfers.

Copyright © Open Applications Group, Inc. All rights reserved ETL BODs (and Nouns) to be added SyncPersonnel ShowPurchaseOrder

Copyright © Open Applications Group, Inc. All rights reserved Workgroup Members Nigel Thompson, Michelin – Project Leader Kurt Kanaskie, Merck – Subgroup Leader Wendy Dodds, ADP Mike Torrone, ADP Mike Rowell, Oracle Paul Kiel, xmlHelpline David Connelly, OAGI – guidance

Copyright © Open Applications Group, Inc. All rights reserved Planned Schedule TBD 1st Draft delivery February st Review March nd Public Review and Vote in April 2009 Publication of limited High Volume standard by May 2009

Copyright © Open Applications Group, Inc. All rights reserved Assumptions, Dependencies and Issues (TBD) Assumptions –Adequate interest within the OAGIS community. –Sufficient staffing. –Appropriate tooling is available. –Limited scope is acceptable. –Consensus on BOD/Noun content can be reached. Dependencies –High Volume canonical formats will be based on OAGIS 9.3. –Upgrades anticipated for subsequent OAGIS releases. –ETL canonical format complexity will be constrained by the capability of current ETL implementation tools. Issues –Need to decide upon approach and tooling to generate the High Volume canonical format.

Copyright © Open Applications Group, Inc. All rights reserved Outside Resources Required None known at this time

Copyright © Open Applications Group, Inc. All rights reserved Next Steps (TBD) Decision on Work Group by Architecture Council and Policy Board –Approved/not Approved? –Issuance of Work Group IP signoff form Announcement via ? Call for additional Team Members Schedule Meeting –Conference Call – when ? –Face to Face – not needed Set up Yahoo Group Assign OAGi Architect Liaison ?

Copyright © Open Applications Group, Inc. All rights reserved Questions? * This is the time to address any questions not asked during the presentation.

Copyright © Open Applications Group, Inc. All rights reserved Canonicals for ETL Project Definition Signature Page By signing this Project Definition you are agreeing to make a contribution to this Working Group The scope of the contribution is constrained to the scope definition in this Project Definition. The complete definition of a contribution and the terms under which the contribution are made is described in the OAGi Intellectual Property Policy, which is available on our web site here: This page is to be ed or faxed to OAGi staff Fax Authorized Signature Name Printed Organization Name Date