IT Service Specification Synchronicity

1. www.oasis-open.org IT Service Specification Synchronicity Carl Mattocks OASIS BCM TC,co-Chair ebXMLRegistry Semantic Content SC, co-Chair ITIL Knowledge Application Consultant, MetLife

2. IT Service Specification Focal Points • Reduce unneeded risk by providing proven techniques that enable a service oriented architecture and support enterprise agility and interoperability. • Allow business people the choice to think and communicate in business terms • Help 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

3. Business Goals of Deploying a Standard • Reduce Dependency on Proprietary Solutions • Decrease Time-to-Market • Decrease Expenditure on Analysis • Decrease Development Cost • Reuse Component Interfaces • Utilize Knowledge from Community of Practice • Increase Ease of Vendor Interaction

4. Benefits of Employing IT centric Service Standard • Reduction of IT Costs • Improved Quality of IT Service • Improve Alignment with Process Partners • Service that meets Business, Customer and User demands • Happier Auditors

5. Formal Specification of a Shared Conceptualization • Operational Data specification • Info Processing described with Templates & Controlled Vocabulary Terms • Ontological Concepts specification • Definition of notions embedded in vocabulary terms and template structure • Representation Language specification • Used by authors to write ontologies

6. User Interface - Presentation Apps Web Browser Email Client Telephone Wireless Front-End Assurance DCR Registry Repository Workflow Access Enterprise Information Services Layer - EISL SOA DCW DCD Exchange Collaboration Gateway Service Management Business Applications Back-End Financial Budget Management Configuration Management Capacity Management Release Management Incident / Problem Management Agent Warehouse Agent Agent

7. Collaboration Partner Agreements- CPA Templateengine Contract BP Specification Schema BPSS Process Collaboration Partner Profiles - CPP Content Assembly Mechanism - CAM Workflow XForms Messages Artifact relationships Specifications Schema Presentation Rules Events Roles MotivationTime People Directory Services Nouns Verbs Transport Routing, Packaging Data/CodesServices/Functions Network Core Components WSDL MSHSOAP Source: BCM Semantic Interoperability Standards Stack (OASIS- CAM , BCM , SAML, ebSOA, BPEL …………………. ) eFolder Templates: Organizing and Orchestrating Loosely coupled applications (ebXML, WS) ACORD

8. 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

9. 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