it service specification synchronicity
DESCRIPTION
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. IT Service Specification Focal Points. - PowerPoint PPT PresentationTRANSCRIPT
www.oasis-open.org
IT Service Specification Synchronicity
Carl MattocksOASIS BCM TC,co-Chair ebXMLRegistry Semantic Content SC, co-ChairITIL Knowledge Application Consultant, MetLife
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
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
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
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
Service Management Business Applications
Assurance
Access
Gateway
Workflow
Exchange
Bac
k-E
nd
En
terp
rise
In
form
atio
n
Ser
vice
s L
ayer
-
EIS
LF
ron
t-E
nd
DCR
Collaboration
AppsWeb
BrowserEmailClient
Telephone Wireless
FinancialBudget
Management
Configuration Management
Release Management
Capacity Management
Incident / Problem
Management
User Interface - Presentation
DCW
Registry Repository
DCDSO
A
Warehouse
Agent
Agent
Agent
Motivation Time People
Specifications Schema
Workflow
Contract
Directory Services
Presentation
Artifact relationships
Data/Codes Services/Functions Network
Source: BCM
Core Components
Core Components WSDLWSDL
XFormsXForms
TransportRouting, Packaging
TransportRouting, Packaging
Collaboration Partner
Agreements- CPA
Collaboration Partner
Agreements- CPA
MSHSOAP
MSHSOAP
MessagesMessages
RolesRoles
Collaboration Partner
Profiles - CPP
Collaboration Partner
Profiles - CPP
NounsNouns
EventsEvents
Templat
e engine
RulesRules
VerbsVerbs
Content Assembly Mechanism - CAM
Content Assembly Mechanism - CAM
BP Specification Schema
BPSS
BP Specification Schema
BPSSProcessProcess
Semantic Interoperability Standards Semantic Interoperability Standards StackStack
((OASIS- CAM , BCM , SAML, ebSOA, BPEL …………………. )OASIS- CAM , BCM , SAML, ebSOA, BPEL …………………. )
eFolderTemplates:
Organizing and Orchestrating
Loosely coupled applications
(ebXML, WS)
ACORD
www.oasis-open.org
Conceptual Layer
Business Layer
Extension Layer
Implementation Layer
Identify Demo / Solution CoI’s Specific Requirements
External Alignment: Stds, Specs & Frameworks
Baseline Architecture for Business Artifacts for Stds
Perform Industry Survey of Leading Practices
Baseline Architecture for Required Technologies for Stds
Net-based Collateral
Training / Education
Change Mgmt Activities
Implementation
Determine Tactics: Use Case / Scope / Transition
.
Project Mgmt: Cost / Schedule / Risks, etc.
Design & Development (Integration/Programming)
Requirements Test Plan, Data, & Testing
Deploy
Lower Semantic Alignment
Identify Authoritative Sources
Identify Business Concepts / Atomics
Business Object Identification
Develop/Add to Terms Service
Patterns
Discover/Define Services
Reporting Requirements
Identify Form/Transaction
Recognize Business Model
Business Process
Define Workflow/Choreography
Define Roles & Security
Define Events/Triggers
Develop Guidelines / Alignments - Maps
Describe Scenarios & Interface Types
Outreach
Identify Like/Exact Terms
Enterprise Architecture Fit / Compliance
Property
Location
Person
Publish
Address
Service
HomeWork
Part of
Is A
Terms Service
• Concept• SKOS • OWL
Stds, Specificationsand Frameworks
Transaction
BaseBase
Identify Community of Interest (CoI)
Channel
Condition (Rule)
Alignment - Maps
Identify Stakeholders
Business Case Analysis
Feasibility, Risk, Cost Benefit
Determine Scope: In Scope / Out of Scope
List Success Metrics Per Stakeholder
Vision Statement
Pinpoint Challenges / Issues
Identify Initiative Champions
Solution Envisioning
Context
Collaboration
Services
Link
Self-Synchronization
MetaLink
Publish
Ontology
Business Objects
Form
Develop Playbook
PhasedDemonstrations
Brochures - Press
Collaboration - Collection
Documentation
Communication
Develop Concept Operations
Baseline Capability Inventory
Define Concept
Add/Converge/Link Ontologies
Codify/List Concepts
Define Slice & Dice (Filter) Tactics
Dashboard Loaders
Identify Facets (Classification)
Define Value-chain Visibility Strategy
Business Intelligence
Dashboard Setup & Security
Include Facet in Navigation Framework
Semantic Alignment
Identify Event Condition (Rule)
Attribute; Mandatory vs. Optional
Appendix B: Terms Alignment
Codelist Sub/Superset
Physical – Content AssemblyTraining
Memorandum of Understanding (CPP/A) Appendix A: Interface Specification
Interface (Publish/Subscribe, etc)
Develop/Join COP (wiki, etc.)
Assumptions Assertion Evaluation
Determine (Meta) Link Opportunities
Exceptions & Notifications
Feedback – Lessons Learned
Draft Initiative Brochure Per Community
Service Operation Support
Story
Derive Community Requirements
How do you know the initiative is done?
BCM Checklist:Operability - Interoperability
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
OASIS BCM TC Work Status