1. www.oasis-open.org BCM (Business Centric Methodology) Technical CommitteeDefining methods to acquire interoperable e-business information systems within communities of interest Mike Lubash (co-Chair) US DoD Carl Mattocks (co-Chair) MetLife David Webber (Sec.) Individual Member Eric Okin US DoD Neil Wasserman Individual Member Hans Aanesen Individual Member Sally St. Amand Individual Member

2. BCM Focal Points • Approach for reducing unneeded risk by providingproven techniques that enable a service oriented architecture and support enterprise agility and interoperability. • Allows business people the choice to think and communicate in business terms • Helps managers communicate precisely their business goals among heterogeneous partners as well as layering the appropriate steps that must be applied for a project to succeed • Complements existing Specifications • Architectures e.g. Zachman (EA), Service-Oriented Architectures (SOA) • Frameworks e.g. Federal Architecture Reference Models, US DoD Architecture Framework • IT Service Management best practice, e.g. ISO 20000, COBIT • OASIS Standards e.g. SAML, UBL, WS-Reliability, ebXML Messaging, ebXML Registry, UDDI, XACML

3. BCM Guideline Essentials • Conceptual layer improves the understanding of the semantics by aligning the terminology of the business and uncovers the real meaning of the business vocabulary • Business layer develops an understanding of the core business goals that the “preferred” business objects must accomplish and constrains them according to defined business processes and patterns • Extension layer provides outreach for mapping the Target Constructs to the desired industry consortiums, standard bodies, and internal legacy system formats • Implementation layer provides in-depth technical requirements analysis of the selected framework

4. ImplementationLayer . Implementation Semantic Alignment Solution Envisioning Memorandum of Understanding (CPP/A) Appendix A: Interface Specification Self-Synchronization Form Identify Event  Condition (Rule) Project Mgmt: Cost / Schedule / Risks, etc. Transaction Collaboration Appendix B: Terms Alignment Determine Tactics: Use Case / Scope / Transition Identify Initiative Champions Context Base Design & Development (Integration/Programming) Attribute; Mandatory vs. Optional MetaLink Phased Demonstrations Requirements  Test Plan, Data, & Testing Codelist Sub/Superset Link Interface(Publish/Subscribe, etc) Deploy Services How do you know the initiative is done? Physical – Content Assembly Training Publish Feedback – Lessons Learned Extension Layer Condition (Rule) Outreach External Alignment: Stds, Specs & Frameworks Communication Alignment - Maps Identify Community of Interest (CoI) Training / Education Perform Industry Survey of Leading Practices Channel Stds, Specifications and Frameworks Identify Demo / Solution CoI’s Specific Requirements Net-based Collateral Develop/Join COP (wiki, etc.) Baseline Architecture for Business Artifacts for Stds Change Mgmt Activities Draft Initiative Brochure Per Community Baseline Architecture for Required Technologies for Stds Collaboration - Collection Work Derive Community Requirements Develop Guidelines / Alignments - Maps Brochures - Press Home Documentation Is A Business Layer Business Case Analysis Business Process Business Intelligence Business Objects Vision Statement Define Value-chain Visibility Strategy Reporting Requirements Publish Identify Stakeholders Identify Facets (Classification) Define Events/Triggers Pinpoint Challenges / Issues Include Facet in Navigation Framework Identify Form/Transaction Service Assumptions  Assertion Evaluation Define Slice & Dice (Filter) Tactics Business Object Identification Address Feasibility, Risk, Cost Benefit Dashboard Loaders Discover/Define Services List Success Metrics Per Stakeholder Dashboard Setup & Security Define Roles & Security Determine Scope: In Scope / Out of Scope Exceptions & Notifications Define Workflow/Choreography Part of Conceptual Layer Story Lower Semantic Alignment Ontology Describe Scenarios & Interface Types Identify Business Concepts / Atomics Person Develop Concept Operations Identify Authoritative Sources Service Operation Support Define Concept Location Identify Like/Exact Terms Patterns Develop/Add to Terms Service Recognize Business Model Property Add/Converge/Link Ontologies BCM Checklist: Operability - Interoperability • Concept • SKOS • OWL Develop Playbook Codify/List Concepts Baseline Capability Inventory Terms Service Determine (Meta) Link Opportunities Enterprise Architecture Fit / Compliance www.oasis-open.org

5. OASIS BCM TC Work Status • V1 Standard May 2006 • SC Work • ERP / e-Folders • Norwegian Electronic Process work • Home Healthcare services and Building and Construction Maintenance • New Work • BCML • Framing language that will use 'service bridges' to ensure information used by one SOA artifact is accurately communicated to the other BCM layers • BCMO • Ontology for eBusiness that resides in the Concept layer to ensure semantic synchronicity across all BCM layers