For Enterprise Agility

1
For Enterprise Agility Interoperability
Mike Lubash DFAS XML Team Lead DOD Finance and
Accounting XML Community Manger Emerging
Technologies Mike.Lubash_at_DFAS.mil
2
Agenda
Agenda
Part I Vision
Environment
1
Paradigm Shift
2
Part II Implementation
3
Moving Enterprise Forward
4

Layers Detailed
3
Agenda
Agenda
Part I Vision
Past
Future
Doctrine for Agility and Interoperability
Environment
1
Momentum
Understanding the Challenge
Todays Approach
4
Environment Understanding the Challenge
Symptoms
Ineffective communication of requirements Non-reli
able information - Integrity/Quality Extending
individual efforts to common is
painful Convoluted processes Inability to upgrade
system Dont have the information Customer
dissatisfaction due to not meeting needs Unable
to measure effectiveness of the Enterprise Unable
to go from vision to implementation Scope-creep De
lay in system implementation Cost overruns for a
project
5
Environment Understanding the Challenge
Root Causes
5. Take back the steering wheel
4. Frameworks are complex
6. One Size doesnt fit all
8. Brain Drain paralysis
7. Information is Power
1-3. Semantics
Symptoms
Ineffective communication of requirements Non-reli
able information - Integrity/Quality Extending
individual efforts to common is
painful Convoluted processes Inability to upgrade
system Dont have the information Customer
dissatisfaction due to not meeting needs Unable
to measure effectiveness of the Enterprise Unable
to go from vision to implementation Scope-creep De
lay in system implementation Cost overruns for a
project
6
Environment Understanding the Challenge
Root Causes Defined
1. Semantics 2. Semantics 3. Semantics
4. Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all
7. Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
7
Environment Todays Approach
Leading Methodologies
Initiative Initiative Initiative Brief Strong Points
C4ISR - DoD Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance Establish common architecture terms and definitions Implement a common approach for architectures Strengthen architecture policy and guidance Define and use levels of interoperability Build architecture relationships with other DoD processes Manage DoD architectures http//www.c3i.osd.mil/org/cio/i3/AWG_Digital_Library/ Provides for architecture alignment via products, Includes narratives, demonstrated success in DoD agencies, aligns closely with previous Federal approach
UMM UN/CEFACT Modeling Methodology ebXML adopted based on configuring the Unified Process methodology developed by the Rational Corporation (UML) to meet UN/CEFACT needs for modelling business processes in addition to objects. http//www.gefeg.com/tmwg/n090r10.htm Continues with modeling, development of language for communication, Registry
MDA Model Driven Architecture built on the solid foundation of well-established OMG standards, including Unified Modeling Language (UML) http//www.omg.org/mda/ Seperates business from technology, graphical
RUP Rational Unified Process ..engineering processes that provide you with guidance to streamline your team's development activities http//www.rational.com/products/rup Proven in many developments, graphical
IDEF Integrated Definition sixteen methods, from IDEF0 to IDEF14 (and including IDEF1X), are each designed to capture a particular type of information through modeling processes. IDEF methods are used to analyze the model, create a model of a desired version of the system, and to aid in the transition from one to the other. http//www.idef.com/ graphical representations of various systems
ECIMF E-Commerce Integration Meta-Framework for designing and implementing integration bridges between currently incompatible systems. http//www.ecimf.org/ Addresses linguistics
OAGIS Open Applications Interoperability Specification Content for business software interoperability via BODS http//www.OpenApplications.org Language, patterns, ERP perspective, ebXML support
X12 ANSI Electronic Data Interchange EDI - recent added 'slotting' concept with XML http//www.disa.org Standards with modularity
8
Environment Todays Approach
Existing Mechanisms
         
9
Environment Todays Approach
Traditional View of Interoperability
OSI Model
Application
Provides different services to the applications
Presentation
Converts the information
Session
Handles problems which are not communication
issues
Transport
Interconnection
Provides end to end communication control
Network
Routes the information in the network
Data Link
Provides error control between adjacent nodes
Physical
Connects the entity to the transmission media
Source Open System Interconnection
10
Environment Momentum
NetCentric
Source DONCIO
11
Getting to the Future - Obtaining our Objectives
Implementation
Business Lines Transformation
Agile Enterprise
Netcentricity
Architecture
Federal Enterprise Architecture
DoD Architecture Framework
NASCIO Adaptive Enterprise Architecture
12
Doctrine for Agility and Interoperability
         

• Business First
• Shifting power to the users customer and
  business experts, e.g. self-service
• Provide traceability from business vision to
  implementation (and status)
• Managing information assets to ensure
  visibility, accessibility, interoperability, and
  understandability through metadata
• Semantic-driven technology neutral context
  supported by classifications, ontology and
  patterns for semantic alignment
• Moving the semantics from applications to the
  infrastructure layer
• Objective not standard language - but instead
  standard reusable mechanisms to better negotiate
  differences
• Capture rationale for pragmatic interoperability
  Templates and models to define what not how
• Its not just technology people are key asset

• Multi-Faceted Architecture
• Function-centric not system or entity
• Choice Web (human), data, process, services
• Modular and layered to address complexity
  leverage open initiatives such as XML
• Service-oriented loosely coupled interfaces
• Wrap legacy systems with services
• Provide structure for business patterns
• Defer physicalization as long as possible
• Strong Business Case
• Clear defined goals with success metrics
• Supported by proof of principles
• 1, 2, 5 and 10 year migration strategy
• Cant wait for a perfect solution
• Continuous integration process

13
Agenda
Agenda
Part I Vision
Environment
1
BCM
2
Paradigm Shift
Opportunities
Agility Model
Information Architecture
Operational View
14
Paradigm Shift Handle an Ever Changing
Enterprise
OSI Model
Agility Model
Content
Application
Low
High
Vocabularies
Presentation
Volatility
Stability
Interfaces
Session
Enabling Technologies
Transport
Interconnection
Products / Services
Network
Navigation
Data Link
Information Architecture
Physical
Low
High
includes a Thesaurus to align vocabularies with
business concepts
Source Adapted from Semantic Studios
15
Supporting 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
Source Lubash Pyramid
16
BCM ModelApplying Constraints in Layers Where
Appropriate
Information Architecture
Methodology
Enables the management of critical Enterprise
information artifacts
Tactical
Strategic
Source BusinessCentricMethodology.com
17
BCM Templates
Templates
Methodology
Contract Collaboration Partner Specific
Constraints

• Legacy

• Frameworks Standards

Business Drivers Model / Process / Constraints

• Business Goals

• Authoritative Sources

Templates provide context for declaration of
constraints and choices
18
Operational View - Interoperability Artifacts in
Motion
Implementation
Templates
Template-driven
19
BCM Templates for Effective Communication
Technology Service View IT aspects of business
transactions
1. Improving communication between business
domain experts (what) and technologist (how)
to maximize new exciting opportunities.
2. Using the same template mechanism to
communicate with our collaboration partners
Business Operational View Domain aspects of
business transactions
20
BCM Templates Workflow Viewpoint
The Templates are going to prompt for the same 6
questions, at different layers, from different
points of view (with each view being from a
dominate question)
Where / Who
Where / Who
Where / Who
21
Opportunities Afforded to an Agile Enterprise

• Few Examples
• 1. Pragmatic as well as Semantic
  Interoperability via Templates
• 2. Collaborative Business - via Templates and
  aligned ontologies
• 3. New and simpler mapping methods for
  interoperability
• 4. New ways of doing business i.e. Web Services
• 5. Supporting Communities of Interest (CoI)

22
Opportunities Afforded to an Agile Enterprise
1. Pragmatic Semantic Interoperability
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
23
Opportunities Afforded to an Agile Enterprise
2. Metrics for Interoperability
         
 
Poor Integration
Good Integration
Collaboration Partner 1
Traditional Contract
Contract driving Templates
Collaboration Partner 2
Aligned Ontology
Separate Ontologies
Semantics, Semantics, Semantics
Source Lubash Pyramid
24
Opportunities Afforded to an Agile Enterprise
3. Providing Options for Interoperability
Mapping (Option 1)
Template (Option 2)
App
App
Domain
Std
Trans
Trans
Map
IC
Populated Templates
Instance
IC
Instance
Specific
Baseline Specification
Across Domain
Trans
Map
Registry Target
App
App
What is harder? Sending or Receiving?
25
Opportunities Afforded to an Agile Enterprise
4. Trend Toward Service-Oriented Architectures
SHIFT
SHIFT
Hub n Spoke
Service Oriented (SOA)
Ad Hoc
Centralized data processing only Virtual
Pt.-to-Pt. Physical Artifacts Broker-based
Metadata Strategy Reuse High Central
End-to-End Tracking Yes, Central Integration at
Broker Lookup Info Must publish to
Broker Mapping Two or more Bandwidth Required
Highest Computing Central Big Iron Impact of
Changes High Pt.-to-Pt. Real-time No
Technology Solution
Central Distributed data processing Common
Pt.-to-Pt. Mechanism Logical Physical
Artifacts Enterprise Metadata Strategy Reuse
Much Opportunity End-to-End Tracking
Services Integration at Point of Use Lookup Info
Kept at Domain Mapping Once Bandwidth Required
Lowest Computing Distributed Load Impact of
Changes Low Pt.-to-Pt. Real-time Yes Business
Solution
Distributed data processing Simple
Pt.-to-Pt. Physical Artifacts No Metadata
Strategy Reuse Little Opportunity End-to-End
Tracking Low Integration at Point of Use Lookup
Info Kept at Domain Mapping Only Once Bandwidth
Required Lowest Computing Distributed
Load Impact of Changes Low Pt.-to-Pt. Real-time
Yes Immediate Solution
Business-Centric Methodology becomes ever more
critical
26
Opportunities Afforded to an Agile Enterprise
5. Supporting Communities of Interest - CoI
Domains

• Institutional communicates and navigates
  Enterprise via ontology
• Expedient through discovery and use via CM Search

Ontology
Composite
System
Persistence
Expedient
CM Service
CoI
Create
Message
Search Results
Registry
Search
Service
Using History-of-Use Filtering to leverage
relationships between users and Enterprise
artifacts
Navigation
Viewports / Capabilities
Source http//www.CollaborativeMemory.com
27
Summary
         

• Present an methodology for agility
  interoperability that
• 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.
28
Agenda
Agenda
Part I Vision
Environment
1
2
Paradigm Shift
Part II Implementation
3
Moving Enterprise Forward
CoI
Tactics
Plans
Strategy
Infrastructure
29
Strategy to Moving the Enterprise ForwardBrown
Fields Piggyback on Hot Button Initiatives
Agility Model
Content
Low
Vocabularies
Stability
Interfaces
Enabling Technologies
Products / Services
Portal Effect
Navigation
Opportunity!
Information Architecture
High
includes a Thesaurus to align vocabularies with
business concepts
30
Strategy to Moving the Enterprise ForwardGreen
Fields Natural Development Process
Project Start
Design
Develop Test
Deploy

• Design Stage
• Concepts defined and authoritative sourced
• Requirements and rationale detailed
• Target constructs identified
• Classify Concepts and Targets
• If not using Target constructs for physical
  exchange, provide Implementation Guide(s)
• Physical XML Schemas, XML Instance examples, XSL
  implemented
• Design Review (DR)

• Final Stage
• Modifications incorporated from test
• Final Review (FR)
• Comments incorporated from Final Review
• Registered

• Preliminary Stage
• Define business context
• Determine ROI
• Use Case scenarios
• Sequence diagrams to flush out number of
  transactions and rough cut business objects
• Research prior work, identify business concepts
  and sources
• Develop rationale for solution approach
• Preliminary Design Review (PDR)

Metadata management plays a role
31
Strategy to Moving the Enterprise
ForwardInformation Architecture with XML
technology
         
 
Collaboration Partner Agreements- CPA
Collaboration Partner Profiles - CPP
5
Contract
Workflow
4
BP Specification
Process
XForms
Specifications Schema
3
Content Assembly Mechanism - CAM
Messages
Artifact relationships
Motivation Time People
2
Presentation
Rules
Events
Roles
Directory Services
Data/Codes Services/Functions
Network
1
MSH/SOAP
Verbs
Transport Routing, Packaging
Nouns
Core Components
WSDL
Source Lubash Pyramid
32
Strategy to Moving the Enterprise Forward
Legacy Transactions
Contract
Middle Out Transitioning
Physical
Technology Model / Constraints
Implementation Layer
Baseline Specification
Mappings
Publish
Architecture Products
Alias
Extension Layer
Design Products
Reuse - Compound Constructs
Legacy Model / Stores
Business Drivers Model / Process / Patterns /
Constraints
Target Constructs
Business Layer
Business rules / Patterns / etc.
Context
Communities of Interest
Concepts
Alias
Ontology - Classification - Taxonomy
- Thesaurus
Conceptual Layer
Business Goals
Frameworks Standards
33
Strategy to Moving the Enterprise
ForwardDelivering Business Value
Alignment
Register
Phase 1
Phase 2
Relationships
Registered Entity
Best Value
1
2
3
4
5
6
Collect
Connect
Communicate
Correlate
Contract / Choose
Catalog
34
Infrastructure to Move the Enterprise
ForwardMajor Supporting Services / Components
Index / Clustering
Federated

• Thesaurus
• Classifications

Visualization Tools
Workflow
Ontology

• Taxonomy
• Semantic Network

Rules/Mapping Engine
Template Processor
35
Infrastructure to Move the Enterprise Forward
Collaboration Mechanisms
Information Enabling
Major Infrastructure Services / Components

• Shared URLs (Favorites / Bookmarks)
• Intelligent Filters Dynamic Channeling
• Issues and Risk Mitigation
• Coexistence
• Conference / Thread Tracking
• Presentations / Whiteboards

Group Leveraging

• Shared Services / Applications

Function Sharing

• Contacts
• Events
• Project
• Customer / Help, etc.

Information Sharing
(Portal, etc.)
36
Moving the Enterprise Forward - Tactics
Build with existing infrastructure and have 1, 2,
5, 10 year plan

• Planning
• Develop - Project workplan
• - Metadata management plan
• - Knowledge management plan
• - Transition plan
• Set in place policy for Enterprise

• Develop Information Architecture
• Put in place collaboration mechanisms
• Document/automate metadata management procedures
• Develop first cut taxonomies

• Communication
• Develop Communities of Interest - CoI
• Set-up help line for internal contacts
• Education and facilitation

• Apply Methodology
• Leverage hot button initiatives portal efforts
  to derive organizations ontology
• Harvest or federate current Enterprise
  information
• Complete initial best practice Templates for
  identified high payback area
• Collaboration with ongoing Enterprise
  Architecture initiatives
• Apply methodology to proof-of-principles and new
  developments

37
Agenda
Agenda
Part I Vision
Environment
1
2
Paradigm Shift
Part II Implementation
3
Moving Enterprise Forward
4

Implementation
Layers Detailed
Products
Artifacts
Extension
Deliverables
Business
Conceptual
38
BCM Review Key Characteristics

• I. Layered Approach
• Manage artifacts and constraints strategically
• Semantic Interoperability
• Lexical alignment at Conceptual Layer
• Identify Authoritative Sources
• Use/Map of business Target Constructs
• II. Pragmatic Interoperability
• Through the use of Templates
• Assist in communication
• III. Unique Identifier (UID)
• Online visibility
• Allows methodology to be adopted after
  development ( legacy systems) through UIDs
• IV. New approach to building information
  infrastructure

39
BCM - Layers Detailed
- concept - linking - construct
Contract
Physical

• Transaction / Presentation
• Collaboration Partner Specifics

• Mandatory vs Optional
• Elements vs Attributes
• Length, Datatyping and Masking
• Routing Packaging
• Service Parameters

Technology Model / Constraints
Implementation Layer
Tactical
Baseline Specification
Mappings

• Outreach
• Role-Process Identification
• Standards Framework Adoption
• Qualifier to Object Breakout
• Thesaurus Assignment
• Interchange Mapping

Publish
Alias
Extension Layer
Reuse - Compound Constructs
Business Drivers Model / Process / Patterns /
Constraints
Target Constructs
Legacy

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Business Layer
Context
Communities of Interest
Strategic
Concepts
Alias

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Conceptual Layer
Business Goals
Frameworks Standards
40
Conceptual Layer Drivers
- concept - linking - construct
Concepts
Conceptual Layer
Business Goals
Frameworks Standards
Business Goals
Align ambiguous, competing, and conflicting
drivers to Enterprise goals
Vision Statement
Targets, Measures Assessments
Balanced Scorecard
Goal Patterns
Policies
Performance Agreements
Strategic Plans
Architectures
41
Conceptual Layer Drivers
Implementation
Extension
Business
Conceptual
Frameworks and Standards
Align frameworks standards selection to
Enterprise goals

• Some initiatives are
• complete frameworks
• small focused areas

Horizontal Standards (all industries)

• Standards are
• sanctioned bodies
• consortiums
• few companies

Vertical Standards
(specific industries)
Many standards overlap and are duplicative
42
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Define Business Context
From Business Goals to concepts, constructs, and
communication

• Business Case Analysis (BCA)
• Align with Balanced Scorecard - are we
  addressing the Enterprises needs?
• Identify overall issues - prepare problem
  statement(s)
• Feasibility, Risk, Cost Benefit
• Understand organizational drivers (pain,
  opportunity) from each stakeholders perspective
• Determine success and performance metrics
• Define what is in and out of scope prepare
  scope statement
• Research pattern base for leveraging prior
  efforts
• Coordinate with other project planning tasks
• Timeline Decision? Link Now vs Link Later
  
• Link Now Use BCM Templates as best practice
  guidance throughout development
• Link Later Fast Track where time overrides
  costs, expedite align UIDs after the fact
• Expose for collaboration
• Begin iterative process

You Are Here
From Cost Issues To Business Advantage
Results Customer Best Value
43
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Use Case
Sequence Diagrams

• Players and objects in time sequence
• Happy and Sad Paths

• Describe scenarios
• Diagram and/or paragraph form

44
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Identify Authoritative Sources
Business Concept Definition

• Who is the subject matter experts?
• e.g. Address USPS

• Business Concepts Template
• Agree on definitions
• Alias with sources / derived
• Search Registry

Order of Authority Preference per your Community
Depending on life-cycle of initiative

• Established - Accept
• Early - Collaborate

Provides for lexical alignment to help understand
our business semantics
45
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Concepts Registration
Make artifacts visible and accessible with a
degree of trust

• Register/Link to Authoritative Source Concepts

• Register/Store Internal Concept

Trust
UID
Register
Register
Repository
Store
UID
46
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Classification Assignment

• e.g. DUNS
• Multiple Facets or combination of characteristics

Location
Classword
Location
Business Line
Arlington Indy Denver Cleveland Pensacola Columbus
X
Code Identifer Angle Date Mass Area
X
Mil Pay Civilian Pay Commercial
Pay Accounting ...
X
Concept
Business Line
Classword
47
Conceptual Layer Tasks

• Semantics
• Business Context
• Use Case and Sequence
• Authoritative Sources
• Business Concept Definition
• Concepts Registration
• Classification Assignment
• Ontology Placement

Implementation
Extension
Business
Conceptual
Ontology Placement
Place concepts in ontology base
"Meaningful learning involves the assimilation of
new concepts and propositions into existing
cognitive structures"

• Navigation
• Clarity - provides foundation areas
• Support near alignment
• Extensible extend later if required
• Multiple faceted taxonomies
• Domain(s) Discipline
• Information Architecture
• Business Line

?
most
?
Stability
Prof. Joseph D. Novak Cornell
University 1960s
least
?
Ontology Taxonomies Thesaurus
Classifications Codelists Schemas
Models, etc.
48
Conceptual Artifacts
         
 
If you cant agree at this level, you cant do
business
The power of the Conceptual Layer is having the
artifacts unconstrained
Motivation Time People
2
Rules
Events
Roles
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Shift from Data Management to Metadata Management
Source Lubash Pyramid (Note rows 1 2 equate
to Zachmans columns)
49
Conceptual Artifacts Products
 
Motivation Time People
2
Rules
Events
Roles
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Source Lubash Pyramid (Note rows 1 2 equate
to Zachmans columns)
50
Agenda
Agenda
Part I Vision
Environment
1
2
Paradigm Shift
Part II Implementation
3
Moving Enterprise Forward
4

Implementation
Layers Detailed
Products
Artifacts
Extension
Deliverables
Business
Conceptual
51
Business Layer
- concept - linking - construct
Business choices drive the Enterprises Agility
and Interoperability
Reuse - Compound Constructs
Business Drivers Model / Process / Patterns /
Constraints
Target Constructs

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Business Layer
Context
Communities of Interest
Concepts
Tradeoff
EAI - database structures for all requirements
generalized structure with nominal constraints
B2B messages with maximum constraints
For mechanisms this relationship is reversed
EAI mechanisms are a subset of B2B mechanisms
52
Business Layer Tasks
Implementation

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Define Business Rules
Define rules, business logic in a declarative
manner
Business rules e.g. triggers, email
Identify business events and response outcomes
Collection Methods

• Static Analysis
• Extract
• Interactive Sessions

53
Business Layer Tasks
Implementation

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Capture Business Patterns
Identify or reuse business patterns
Knock Knock
Business pattern - the business nature in
specific context in order to understand and
abstract best practices, or capture the essence
of repeatable processes for reuse.
54
Business Layer Tasks
Implementation

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Atomics and Constructs in Exchange Scope -
independent - dependent
From previously identified messages, identify
exchanged objects
SEQUENCE
TARGET CONSTRUCT
Relationships
Attributes
object
security
Attributes
55
Business Layer Tasks
Implementation

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Structure Resolution / Indenture
- what is included in
constructs? - use
concatenated or atomic?
Determine how to house artifacts and at what
resolution level
Option 1 Separate constructs, all switching in
ontology
Option 2 Single construct, partial switching in
construct
56
Business Layer Tasks
Implementation

• Requirements
• Business rules / patterns
• Atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Workflow / Process Identification
Define the message flow and control states
between applications or collaboration partners
57
Business Layer Tasks
Implementation

• Requirements
• Identify business rules / patterns
• Scope atomics constructs
• Structure Resolution / Indenture
• Workflow / process identification
• Mandatory vs Optional
• Sub-setting Codelists

Extension
Business
Conceptual
Focus on Attribute Details
Determine what are the attributes
mandatory/optional and domains for each state of
the business object
Mandatory vs Optional
Sub-setting Codelists

• of requirements/parties increases the
  probability that an element becomes optional -
  constraints simplify the message!

Published Set e.g. EDI Standards
Superset Subset
Collaboration Partner or Industry Specific
58
Business Layer Artifacts
         
 
Connect concepts with constraints
Target Constructs Concepts Constraints
Workflow
4
Related to messages in multi-party workflow
Process
Specifications Schema
3
Messages
Motivation Time People
2
Rules
Events
Roles
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Position to share workflow with Collaboration
Partners
Source Lubash Pyramid
59
Business Layer Artifacts Products
         
 
Workflow
4
Process
Specifications Schema
3
Messages
Motivation Time People
2
Rules
Events
Roles
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Source Lubash Pyramid
60
Agenda
Agenda
Part I Vision
Environment
1
2
Paradigm Shift
Part II Implementation
3
Moving Enterprise Forward
4

Implementation
Layers Detailed
Products
Artifacts
Extension
Deliverables
Business
Conceptual
61
Extension Layer
- concept - linking - construct
Baseline Specification
Supporting heterogeneous trading partner
environments within existing capability while
moving to the future.

• Outreach
• Role-Process Identification
• Standards Framework Adoption
• Thesaurus Assignment
• Interchange Mapping
• Qualifier to Object Breakout

Extension Layer
Legacy
Target Constructs
Frameworks Standards
62
Extension Layer Tasks - Who / How
Implementation

• Outreach
• Role-Process Identification
• Standards Framework Adoption
• Thesaurus Assignment
• Interchange Mapping
• Qualifier to Object Breakout

Extension
Business
Conceptual
Role-Process Identification
From previous defined Use Cases, align partner
Communities of Interest - COI to baseline
specification.
Business Layer
Extension Layer
Implementation Layer
Collaboration Partner specific
Want to find the sweet spot in understanding
and developing the baseline specification per COI
by including as many partners as possible but
without stretching COI to become complex
63
Extension Layer Tasks - What
Standards Framework Adoption

• Thesaurus Assignment
• Interchange Mapping
• Qualifier (typing) to Object Breakout
  (explicit vs. code)

Collaboration Partner 1
Collaboration Partner 2
Business (Logical)
64
Agenda
Agenda
Part I Vision
Environment
1
2
Paradigm Shift
Part II Implementation
3
Moving Enterprise Forward
4

Layers Detailed
Implementation
Products
Artifacts
Extension
Deliverables
Business
Conceptual
65
Implementation Layer
- concept - linking - construct
Tailor Collaboration Partner Specifics
Technologist develop interchanges and user
interfaces using 1 Target Constructs or 2
Baseline Specifications with supporting products
within partner constraints.
Contract
Physical

• Transaction / Presentation
• Collaboration Partner Specifics

• Mandatory vs Optional
• Elements vs Attributes
• Length, Datatyping and Masking
• Routing Packaging
• Service Parameters

Technology Model / Constraints
Implementation Layer
Baseline Specification
Mappings
66
Implementation Layer CAM Template
ltMapStructuregt ltRulesgt
ltMapRule output"Product List" input"_at_PARENT()"
path"" /gt ltMapRule output"name"
input"Qrt/Product/Item_at_name" /gt
ltMapRule outputmadeby" input"Qrt/Product/Item_at_
made" /gt ltMapRule
output"value" input"Qrt/Product/Item_at_value" /gt
ltMapRule output"sold"
input"Qrt/Product/Item_at_sold" /gt
ltMapRule output"Product List" input"_at_ENDPARENT()
" /gt lt/Rulesgt lt/MapStructuregt
ltCAMgt ltAssemblyStructure/gt
ltPartnerUseContext/gt ltContentReference/gt
ltDataValidations/gt lt/CAMgt
Content Assembly Mechanism
67
Ontology Providing Interpretation Support
allowing for Enterprise-level crosswalks and
light transactions
(Physical)
XML Instance /Content
XML Instance / Content
Data
ltPartNumbergt 999 ltColorgt Black
ltPartNogt 999
Machine-to-Machine
Schema or CAM Template
ltELEMENT namePartNumber
ltdcidentifergt DFAS.PartNum
Schema or CAM Template
ltELEMENT namePartNo ltdcidentifergt
DFAS.PartNum
Business (Logical)
Collaboration Partner 1
Collaboration Partner 2
Registry
DFAS.PartNum
X12
PartNo
EDIFACT
PartNumber
Color
68
Implementation Layer Artifacts
         
 
Collaboration Partner Agreements
Collaboration Partner Profiles
5
Contract
Contract is the formalization and linking of
supporting pyramid Templates
Workflow
4
Process
Specifications Schema
3
Messages
Artifact relationships
Motivation Time People
2
Presentation
Rules
Events
Roles
Directory Services
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Source Lubash Pyramid
69
Implementation Layer Artifacts Products
         
 
Collaboration Partner Agreements
Collaboration Partner Profiles
5
Contract
Workflow
4
Process
Specifications Schema
3
Messages
Artifact relationships
Motivation Time People
2
Presentation
Rules
Events
Roles
Directory Services
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Source Lubash Pyramid
70
Summary
71
Root Causes / Tasks
Root Causes
5. Take back the steering wheel
4. Frameworks are complex
6. One Size doesnt fit all
8. Brain Drain paralysis
7. Information is Power
1-3. Semantics
Tasks
Templates for pragmatic interoperability
(general) Business Goals Define Business
Context Use Case Sequence Diagrams Authoritative
Source Business Concept Definition Registration Cl
assification Ontology Placement Define Business
Rules Capture Business Patterns
72
Root Causes / Tasks
Root Causes
5. Take back the steering wheel
4. Frameworks are complex
6. One Size doesnt fit all
8. Brain Drain paralysis
7. Information is Power
1-3. Semantics
Tasks
Atomic Constructs in Exchange Scope Structure
Resolution / Indenture Workflow / Process
Identification Focus on Attribute
Details Baseline Specification Role-Process
Identification Standard Framework Adoption Map
Library UID based (general) Layering of
Constraints (general) Delay XML Physicalization
(general) NetCentric Visibility, accessibility,
understandability
73
Summary
         

• Present an methodology for agility
  interoperability that
• 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.
74
Thank you
Authors Mike Lubash - Defense Finance and
Accounting Service Bruce Peat - eProcess
Solutions David RR Webber - eProcess Solutions
Contributors Eric Okin - Defense Finance and
Accounting Service Kit C.J. Lueder - The MITRE
Corporation Charlie Clark - Engineering,
Management Integration, Inc.
http//BusinessCentricMethodology.com
75
Agenda
Agenda
Part I Vision
Past
Future
Doctrine for Agility and Interoperability
Environment
1
Momentum
Understanding the Challenge
Todays Approach
BCM
2
Paradigm Shift
Opportunities
Agility Model
Information Architecture
Operational View
Part II Implementation
3
Moving Enterprise Forward
CoI
Tactics
Plans
Strategy
Infrastructure
4

Implementation
Layers Detailed
Products
Artifacts
Extension
Deliverables
Business
Conceptual
Backup for side 3
76
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Semantics, Semantics, and Semantics are the top
three challenges for interoperability.
Interoperability or integration efforts are about
making information from one system syntactically
and semantically accessible to another system.
Syntax problems involve format and structure. An
example is converting the representation of data
from numeric to a character string. These
conversions are well known and the problems
documented. Many standard data sources, such as
databases and applications can export XML for
data transformation using code-free mapping
tools. The accessibility of the information, or
transport problem has been reduced to routine
engineering tasks due to widespread investment in
messaging infrastructures. Semantics relate to
the understanding and integrity of the
information. To put even greater emphasis on the
challenge, the Gartner Group stated, Only 5
of the interface is a function of the middleware
choice. The remaining 95 is a function of
application semantics.
Backup for side 6
77
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Frameworks are complex and conceptual - many
times provides conceptual differences to working
approaches e.g. understanding and relying on
classes in an object-oriented system. In
addition, to the adoption hurdle problem, at
times frameworks are duplicative and
contradicting with multiple levels.
Backup for side 6
78
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Failure of business managers to take back the
steering wheel and are not eager to accept
responsibility for even the what objectives
much less than the how details. Due to tool
immaturity integration development has required
technical know how which excluded the business
practitioners. Today top-down techniques have
exhibited impedance mismatch with current
programmers tools (bottom-up) with no
automated solution that addresses development
from business goals to the physical
implementation well.
Backup for side 6
79
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
One size doesnt fit all - Understanding the
critical difference between (1)
decontextualization of data Standards and (2)
Conceptual-adaptive alignment. Standardized
data provides for inflexibility which leads to a
plethora of standards creating the Tower of
Babel. Where as adopting a minimalist
methodology built upon shared business concepts
is simpler, doable, without expensive overhead
which Tower of Babel syndrome brings to the
Enterprise. Experience tells us that (1)
one-size architectures dont work, (2) one-size
process models dont work, (3) one-size data
model doesnt work, and (4) one-size transaction
standards dont work.
Backup for side 6
80
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Information is power - thus interoperability
requirements become skewed and outputting
information becomes the driver, not a template
driven exchange from the receivers input. In
typical situations, the organization receiving
the information is just plain glad to obtain it,
and takes is in any form possible, dealing with
the integration issues. The better model
certainly would be where the receiver drives the
exchange and the exchange is based on aligned
concepts.
Backup for side 6
81
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Brain drain paralysis - Without knowledge
retention, it is very difficult to determine
impact of any effort to modernize in some
cases, there does not exist a baseline. For
successful eGov, the ability to perform impact
analysis is one of the prime challenges. Adding
new information or making changes to database
structures can have multiple effects. One change
can ripple across an entire Enterprise. If data
values are calculated from one another, based on
one another, tied to one another evaluating the
effects of change can get very complicated very
fast. Efforts on Y2K have given visibility into
systems, and keen insight on the scope of the
problem and provided government with a lesson
learned, but probably will too be forgotten.
Backup for side 6
82
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture

• Funding for integration infrastructure - Funding
  and goals are to business lines and IT with very
  few independent integration tools/team
  initiatives interoperability though a prime
  challenge for the Enterprise isnt funded as
  such. Acquiring integration infrastructure
  capability is seldom funded properly as their
  success outcomes are intangible and difficult to
  measure. Ironically, these integration projects
  typically are funded through application projects
  via business lines or IT departments, of which
  integration between these two groups which
  typically their lack of communication is the
  source much of todays problems. Should our
  federal government appoint an Interoperability
  Facilitator as well as an e-Gov Director?

Backup for side 6
83
Root Causes
1. Semantics, Semantics, and Semantics 4.
Frameworks are complex (and conceptual) 5.
Failure of business managers to take back the
steering wheel 6. One size doesnt fit all 7.
Information is power 8. Brain drain
paralysis 9. Funding for integration
infrastructure 10. Culture
Culture - Human nature survival instincts for
positioning in lieu of collaboration leads to
anarchy and balkanization. In fact, outcomes
typically are not measured on the whole success
metrics need to be viewed across traditional
boundaries, with business goals and
responsibilities aligned and traceable from the
out to in. The human element must be kept in
mind with any proposed system. Report cards need
to bring back the category of work well with
others and rewarded accordingly. Sometimes just
getting the right people in the room does wonders
for interoperability, trust and sharing.
Interoperability will not be achieved if real
problems are not confronted, we have learned
interoperability starts with people first.
Keeping this in mind, eGov systems need to do
whatever is technically possible to 1 reduce
the politics of knowledge and its influence of
power, 2 provide incentives to share, 3
provide collaboration tools with trust
mechanisms, and 4 functions to share semantics
of the business artifacts. Without a roadmap, the
business users (goals) become disenfranchised, an
intolerable effect that reduces business agility.

Backup for side 6
84
Environment Todays Approach BCM
Complements with Value-Add
Initiative Initiative Initiative Brief Strong Points BCM Value-Add
C4ISR - DoD Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance Establish common architecture terms and definitions Implement a common approach for architectures Strengthen architecture policy and guidance Define and use levels of interoperability Build architecture relationships with other DoD processes Manage DoD architectures http//www.c3i.osd.mil/org/cio/i3/AWG_Digital_Library/ Provides for architecture alignment via products, Includes narratives, demonstrated success in DoD agencies, aligns closely with previous Federal approach Information Architecture, interoperability solution, conceptual alignment, rationale capture, traceabiity, scaleable
UMM UN/CEFACT Modeling Methodology ebXML adopted based on configuring the Unified Process methodology developed by the Rational Corporation (UML) to meet UN/CEFACT needs for modelling business processes in addition to objects. http//www.gefeg.com/tmwg/n090r10.htm Continues with modeling, development of language for communication, Registry Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics
MDA Model Driven Architecture built on the solid foundation of well-established OMG standards, including Unified Modeling Language (UML) http//www.omg.org/mda/ Seperates business from technology, graphical Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics
RUP Rational Unified Process ..engineering processes that provide you with guidance to streamline your team's development activities http//www.rational.com/products/rup Proven in many developments, graphical Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics
IDEF Integrated Definition sixteen methods, from IDEF0 to IDEF14 (and including IDEF1X), are each designed to capture a particular type of information through modeling processes. IDEF methods are used to analyze the model, create a model of a desired version of the system, and to aid in the transition from one to the other. http//www.idef.com/ graphical representations of various systems Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics Provides declarative templates, Addresses linguistics
ECIMF E-Commerce Integration Meta-Framework for designing and implementing integration bridges between currently incompatible systems. http//www.ecimf.org/ Addresses linguistics Target Constructs with outreach mechanism
OAGIS Open Applications Interoperability Specification Content for business software interoperability via BODS http//www.OpenApplications.org Language, patterns, ERP perspective, ebXML support provides non-standard option
X12 ANSI Electronic Data Interchange EDI - recent added 'slotting' concept with XML http//www.disa.org Standards with modularity provides non-standard option
Business-Centric Methodology Complements
Backup for side 7
85
Discover, Align, eBusiness
source ebXML
Backup for side 10
86
Information Architecture Artifacts for
Interoperability
         
 
5
Contract
Ontology set of relationships, includes a
Thesaurus to align vocabularies with business
concepts
Workflow
4
Process
Specifications Schema
3
Messages
Artifact relationships
Motivation Time People
2
Presentation
Rules
Events
Roles
Directory Services
Data/Codes Services/Functions
Network
1
Verbs
Transport Routing, Packaging
Nouns
Source Lubash Pyramid
Backup for side 15
87
BCM Model - Constraints Defined in Layers
Implementation Layer
Contract - Collaboration Partner Specific
Constraints
Physical - Message Presentation
Tactical
Legacy
Extension Layer
Publish
Frameworks Standards
Baseline Specification per CoI
Business Layer
Business Drivers Model / Process / Constraints
Target Constructs Patterns
Strategic
Conceptual Layer
Business Goals
Concepts in Ontology
Authoritative Sources
Backup for side 16
88
Operational View Interoperability Artifacts in
Motion
         
 
reject
counter
Contract Agreement Pattern
accept
propose
Workflow Modeling Business Patterns
response
Template-driven
process
Business Goals Goal Pattern

Specification Model Schemas
Schema

Exchange
Concept Ontology
Verbs
Roles
Transport
Nouns
Rules
Events
Backup for side 18
89
Service-Oriented Architecture Reference Model
User Interface - Presentation
Apps
Web Browser
Email Cli