1. 1 For Enterprise Agility & Interoperability OASIS BCM Technical Committee

2. 2 BCM in a Nutshell Reduce the cost of doing business by making e- Business more accessible Improve the time to market for new business solutions through information agility Reduce the cost of ownership for community, industry groups / governments Restoring the balance – the business solution and customers direct how the information technology serves

3. 3 Agenda LandscapeLandscape ApproachApproach ImplementationImplementation AdoptionAdoption –Learning the Terrain –Understanding Today’s Solutions –Paradigm Shift –Foundation of BCM BCM Layers Information Architecture BCM Templates –Declarative Component Operations –Becoming NetCentric –Service Oriented Architecture (SOA) –Communities and Domains –Context – Managing via Choice Points –Holistic Approach –Planning and Facilitation –Resources and Existing Work –Mission Summary

4. 4  Learning the Terrain  Understanding Today’s Solutions  Paradigm Shift Landscape

5. 5 Learning the Terrain … requirements have been documented … with the architecture completed to varying levels of resolution. … subject matter experts have met to define their processes and data … components are procured for the solution that best match the architecture … transition plans are in place and everyone is ready to pilot and implement … the need for change has been communicated to all stakeholders Now what? … customer’s begin to see capabilities that fit their needs … the team learns if interoperability was designed in properly … if the proposed infrastructure supports stakeholder collaboration … if semantics of the business are being managed or not … if ‘standardizations’ were selected correctly, based on the right CoIs We learn if we were asking the right questions Source: eProcess Solutions It is helpful to look back in time…

6. 6 Understanding Today’s Solutions Enterprise Architecture - a New Beast Requiring New Ideas - software approaches are only part of the solution - ETL and EAI technologies aren’t enough - lack of context control mechanisms We need an Holistic Approach to Reduce Risk - provide Business-Centric Methodology… …focus on enterprise agility and interoperability - address root causes and not just symptoms - build for choice, change, and growth SHIFT Hub n’ Spoke S ervice- O riented (SOA) Ad Hoc Source: eProcess Solutions

7. 7 Traditional Approach –ETL –EAI –Data warehouse –B2B + electronic commerce New Holistic Approach –Service Oriented Architecture –Business-centric –Leverage XML Paradigm Shift

8. 8  Foundation of BCM  BCM Layers  Information Architecture  BCM Templates  Declarative Component Operations  Foundation of BCM  BCM Layers  Information Architecture  BCM Templates  Declarative Component Operations Approach

9. 9 The Foundation of BCM Step 2 : Build Templates with Familiar Business Tools Step 3 : Deploy with Declarative Component Operations Step 1 : Use Layers to Define Business Needs While Referencing the Information Architecture

10. 10 Business Layer Conceptual Layer Business Drivers: Model / Process / Constraints Target Constructs & Patterns Implementation Layer Physical - Message & Presentation Extension Layer Contract - Collaboration Partner Specific Constraints Publish Baseline Specification per CoI Concepts in Ontology Business Goals Frameworks & Standards Legacy Authoritative Sources Strategic Tactical Simplification Through BCM Layers 1 2 3 4

11. 11 Deriving the set of business needs and context from each information layer Holistic Approach = Layers + Information Architecture Specific Ontology Navigation Content Rendering Transaction Handling Business Processes Collaboration Agreements, MOA Codelist subsetting Services; Transaction Processing Communities of Interests - CoI 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 11 Source: eProcess Solutions

12. 12 Information Architecture Navigation Products / Services Enabling Technologies Interfaces Vocabularies Content Re-Inventing Your Information Architecture High Low Stability Agility Model Information Architecture Enables the management of critical Enterprise information artifacts Information Pyramid

13. 13 Build Templates Using Familiar Tools

14. 14 ActionEvent Information Rule What Why HowWhen Where / Who The Templates are going to prompt for the same 6 questions, at different layers, from different points of view – Action / Event / Rule / Context / Information / Links Where / Who ActionEvent Information Rule What Why HowWhen ActionEvent Information Rule What Why HowWhen BCM Templates – Workflow Viewpoint

15. 15 Semantic Interoperability Pragmatic Interoperability Abstraction Meta- Metadata Metadata Data In addition to rationale, the Templates house the concepts, context, and constraints Classification Ontology Patterns Wisdom Knowledge Information Data Add Structure Add Experience Synthesize Knowledge Templates Concept Context Instance Constraint Human Intelligence Templates - Role and Functions

16. 16 Operational View Declarative Components of Interoperability

17. 17 Structure Choices Structure Choices Context Values Context Values Required Content Structure Required Content Structure Assembly Processor Assembly Processor Content References Content References 1 Payload / Rendering Payload / Rendering 2 Assembly Structure Assembly Structure Payload Assembly 3 Application Database Application Database Registry Components Registry Components Conceptual Logical Physical Template Driven Declarative Components Example: Payload Assembly Vocabulary nouns, and Industry Dictionaries Vocabulary nouns, and Industry Dictionaries Re-usable Business Information components Re-usable Business Information components Note: OASIS CAM reference model

18. 18  Becoming NetCentric  Service-Oriented Architecture  Communities and Domains  Managing Context - Choice Points  Becoming NetCentric  Service-Oriented Architecture  Communities and Domains  Managing Context - Choice Points Implementation

19. 19 Becoming netCentric Source: DONCIO NetCentric

20. 20 Backup for side: 25 Business Applications and Functions Assurance Access Gateway Workflow Exchange Back- End Enterprise Information Services Layer - EISL Front- End DCR Collaboration Apps Web Browser Email Client TelephoneWireless Finance AccountHR Project Mgmt Procure User Interface - Presentation 2 2 Common Exchange SOAP-based Envelope HTTP 1 1 Common Services Web Services DCW Registry DCD SOA Service Oriented Architecture (SOA) Warehouse

21. 21 Aligning Classifications and Understanding e.g. DUNS, UNSPSC, NSN, Part Number, Address, Weight, Width … Then creating Multiple Facets or combination of characteristics Communities and Domains Collaborating with your Partners Arlington Indy Denver Cleveland Pensacola Columbus Location X Code Identifer Angle Date Mass Area Classword X Mil Pay Civilian Pay Commercial Pay Accounting... … X Location Business Line Classword Business Line Concept Business Outcome - rapid search and discovery by faceted selections

22. 22 Context is the pervasive driver to effective engineering Providing and managing context is needed to drive dynamic process configuring and control Knowing context is needed to ensure accurate information capture, packaging and delivery Qualifying context is key to ensuring correct relationships between partners in a collaboration Lack of context control mechanisms is the most prominent reason why legacy e-Business systems are difficult and complex to extend and support Date: circa 1568 1 : the parts of a discourse that surround a word or passage and can throw light on its meaning 2 : the interrelated conditions in which something exists or occurs Context - Understanding

23. 23 Context - Sample Types Community of Interest determination Business agreement context Business agreement roles Classification of artifacts context Process selection context Process tracking context Transaction context Exception handling context Decisions context Rules context Choices tend to be one off and embedded in code, rather than an approach from a strategic viewpoint – people don’t look outside their purview

24. 24 Context - Managing Via Choice Points Context Actions can be viewed as a decision tree or series of cascading Choice Points that have: –inputs through the assertion of facts –the operation of rules and constraints –that determine the outcome(s) from available choices. Context ranges from the very simple – “if then do” style, to event handlers, to complex decision agents that operate on sets of dynamic facts. Simple Complex If-then-do Decision Agents Implementation Choice Pt.

25. 25 Context - Managing Via Choice Points (con’t) Allows Templates, documents, and exchange decisions based on set of options - built declaratively Allows inputs to determine outcomes based on rules Choice Points can call other choice points Delivers loose-coupling, but with predeterministic tracking Business Drivers: Model / Process / Constraints Contract – Collaboration Partner Specific Constraints Business Goals Legacy systems Authoritative Sources Applying to constructing BCM Templates…

26. 26  Holistic Approach  Planning and Facilitation  Resources and Existing work  Mission Summary  Holistic Approach  Planning and Facilitation  Resources and Existing work  Mission Summary Adoption

27. 27 Holistic Approach Critical Build-out

28. 28 Planning And Facilitation

29. 29 Resources and Existing Work Working with selected Communities of Interest (CoI) Defense Finance and Accounting Service (US DoD) eprXML (Norway) OASIS eGov Liaison with OASIS TCs to refine requirements and implementation model Public release of technical specification Prototype using available tools Demonstration using selected business scenarios

30. 30 Mission Summary Interoperable Agile Information for e-Business … addresses the root cause rather than just symptoms of our integration problems by providing semantic and pragmatic interoperability is business-centric; shifting power to the business experts; managing Enterprise artifacts and governance through Communities of Interests (CoI) provides visibility, accessibility, understandability, using open declarative mechanisms that allow for mass customization of diverse vocabularies and models within heterogeneous environments insulates business from the high rate of change of technology by dividing the problem into multiple levels and applying constraints properly to reduce complexity and promote reuse provides for Enterprise agility and prepares the Enterprise for new opportunities in doing business A tactical-only solution is a waste of money – we need to adopt an Enterprise solution that addresses business context and people.

31. 31 OASIS- Business-Centric Methodology Thank You! http://BusinessCentricMethodology.com http://www.oasis-open.org http://eprforum.org