For Enterprise Agility

1
For Enterprise Agility Interoperability
OASIS BCM Technical Committee
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
Agenda

• Landscape
• Approach
• Implementation
• Adoption

• Learning the Terrain
• Understanding Todays 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

4
Landscape

• Learning the Terrain
• Understanding Todays Solutions
• Paradigm Shift

5
Learning the Terrain
It is helpful to look back in time
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? customers 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
6
Understanding Todays Solutions

• Enterprise Architecture - a New Beast Requiring
  New Ideas
• - software approaches are only part of
  the solution
• - ETL and EAI technologies arent 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

7
Paradigm Shift

• Traditional Approach
• ETL
• EAI
• Data warehouse
• B2B electronic commerce
• New Holistic Approach
• Service Oriented Architecture
• Business-centric
• Leverage XML

8
Approach

• Foundation of BCM
• BCM Layers
• Information Architecture
• BCM Templates
• Declarative Component Operations

9
The Foundation of BCM
10
Simplification Through BCM Layers
Implementation Layer
Contract - Collaboration Partner Specific
Constraints
4
Physical - Message Presentation
Tactical
Legacy
Extension Layer
Publish
3
Frameworks Standards
Baseline Specification per CoI
Business Layer
Business Drivers Model / Process / Constraints
2
Target Constructs Patterns
Strategic
Conceptual Layer
Business Goals
1
Concepts in Ontology
Authoritative Sources
11
Holistic Approach Layers Information
Architecture
Deriving the set of business needs and context
from each information layer
12
Re-Inventing Your Information Architecture
Information Architecture
Agility Model
Enables the management of critical Enterprise
information artifacts
Content
Low
Vocabularies
Stability
Interfaces
Enabling Technologies
Products / Services
Navigation
Information Architecture
High
Information Pyramid
13
Build Templates Using Familiar Tools
14
BCM Templates Workflow Viewpoint
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
Where / Who
Where / Who
15
Templates - Role and Functions
In addition to rationale, the Templates house the
concepts, context, and constraints
Wisdom Knowledge Information Data
Synthesize Knowledge
Human Intelligence
Abstraction Meta- Metadata Metadata Data
Templates

• Classification
• Ontology
• Patterns

Add Experience
Constraint
Context
Add Structure
Concept
Instance
Semantic Interoperability
16
Operational View Declarative Components of
Interoperability
         
 
17
Template Driven Declarative ComponentsExample
Payload Assembly
Re-usable Business Information components
Registry Components
Vocabulary nouns, and Industry Dictionaries
Physical
Conceptual
Application Database
Structure Choices
1
Required Content Structure
2
3
Payload Assembly
Assembly Processor
Assembly Structure
Content References
Context Values
Payload / Rendering
Logical
Note OASIS CAM reference model
18
Implementation

• Becoming NetCentric
• Service-Oriented Architecture
• Communities and Domains
• Managing Context - Choice Points

19
Becoming netCentric
NetCentric
Source DONCIO
20
Service Oriented Architecture (SOA)
Warehouse
21
Communities and DomainsCollaborating with your
Partners
Aligning Classifications and Understanding

• e.g. DUNS, UNSPSC, NSN, Part Number, Address,
  Weight, Width
• Then creating Multiple Facets or combination of
  characteristics

Location
Location
Classword
Business Line
X
Mil Pay Civilian Pay Commercial
Pay Accounting ...
X
Arlington Indy Denver Cleveland Pensacola Columbus
X
Code Identifer Angle Date Mass Area
Concept
Business Line
Classword
Business Outcome - rapid search and discovery by
faceted selections
22
Context - Understanding

• 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 15681 the parts of a discourse
that surround a word or passage and can throw
light on its meaning2 the interrelated
conditions in which something exists or occurs
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 dont look outside their
purview
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
Choice Pt.
Implementation
25
Context - Managing Via Choice Points (cont)

• 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

Applying to constructing BCM Templates
Contract Collaboration Partner Specific
Constraints
Legacy systems
Business Drivers Model / Process / Constraints
Business Goals
Authoritative Sources
26
Adoption

• Holistic Approach
• Planning and Facilitation
• Resources and Existing work
• Mission Summary

27
Holistic Approach Critical Build-out
28
Planning And Facilitation
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
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
OASIS- Business-Centric Methodology

• Thank You!

http//BusinessCentricMethodology.com http//www.
oasis-open.org