BusinessCentric Methodology For Enterprise Agility

1
Business-Centric MethodologyFor 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
Past
Future
Doctrine for Agility and Interoperability
Environment
1
Momentum
Understanding the Challenge
Todays Approach
2
Paradigm Shift
Opportunities
Agility Model
Information Architecture
Operational View
3
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
4
Environment Todays Approach
Leading Methodologies
5
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
6
Environment Momentum
7
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
8
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

9
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
10
Paradigm Shift Handle an Ever Changing
Enterprise
Agility Model
Content
Low
High
Vocabularies
Volatility
Stability
Interfaces
Enabling Technologies
Products / Services
Navigation
Information Architecture
Low
High
includes a Thesaurus to align vocabularies with
business concepts
11
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
12
BCM ModelApplying Constraints in Layers Where
Appropriate
Information Architecture
Methodology
Enables the management of critical Enterprise
information artifacts
Tactical
Strategic
Source BusinessCentricMethodology.com
13
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
14
BCM Templates
Templates
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
15
Operational View - Interoperability Artifacts in
Motion
Implementation
Templates
Template-driven
16
Operational View - Interoperability Artifacts in
Motion
Implementation
Templates
Template-driven
17
Operational View - Interoperability Artifacts in
Motion
Communication
Templates
18
Opportunities Afforded to an Agile Enterprise
Doing Business Differently 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)
Enterprise You

• Moving the Enterprise Forward
• Infrastructure to Move the Enterprise Forward
• Personal Development - Information Architect
• OASIS BCM TC

19
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
20
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
21
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?
22
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
23
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
Navigation
Using History-of-Use Filtering to leverage
relationships between users and Enterprise
artifacts
Viewports / Capabilities
Source http//www.CollaborativeMemory.com
24
Opportunities Afforded to an Agile Enterprise
Doing Business Differently 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)
Enterprise You

• Moving the Enterprise Forward
• Infrastructure to Move the Enterprise Forward
• Personal Development - Information Architect
• OASIS BCM TC

25
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

26
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
27
Personal Development - Information Architect
Tasks
Infrastructure

• Skills for Meeting a Demand of an Emerging
  Profession as an Information Architect
• Database -gt Document or Database lt- Document
• eXtensible Markup Language (XML)
• Information organization and structures
• Faceted Classification / Indexing / Cataloging /
  Searching
• Semantic Networks concepts, business rules,
  ontologies and taxonomies
• References, Relationships, Communities of
  Interest
• Navigation and Visualization
• Principles of user-centered iterative design
• How to put on the Web JavaScript, VBscript,
  Java/Active Server Pages (JSP/ASP), etc.
• Developing for Choice Aspect-Oriented
  Programming (AOP), Framing, Context-based
  switching
• Declarative vs programmatic controls for
  knowledge management
• Collaborative tools for infrastructure
  management Plan, Organize, Resource, Direct, and
  Control

Techniques GUI
Linking Containers
28
Scope Setting the Tone
Taking the BCM to OASIS for Feedback, Extension
and Consensus
EAI
Interoperability
EAI
Phase 3 Vendor Implementations
Phase 2 XML Definitions
Phase 1 Methodology
-- Specification Vision -- Template
Examples -- Switching Linking of Templates --
Information Architecture
Business
User
29
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.
30
Thank you
Mike Lubash DFAS XML Team Lead DOD Finance and
Accounting XML Community Manger Emerging
Technologies Mike.Lubash_at_DFAS.mil
http//www.dfas.info
31
Our Story, and we are sticking to it
32
BCM Overview
33
BCM Infrastructure Conops
34
Search for the Solution
When asked what single event was most helpful in
developing the theory of relativity, Albert
Einstein is reported to have answered, Figuring
out how to think about the problem.
Source Wilbur Schramm William Porter, Men,
Women, Messages and Media Understanding Human
Communication