Business-Centric MethodologyFor Enterprise Agility & Interoperability

Business-Centric MethodologyFor Enterprise Agility & Interoperability

Mike LubashDFAS XML Team LeadDOD Finance and Accounting XML Community MangerEmerging TechnologiesMike.Lubash@DFAS.mil

2AgendaAgenda

Past Future

Understandingthe Challenge

Today’sApproach

11Momentum Doctrine for Agility

and Interoperability

Doctrine for Agility and Interoperability

Environment

Agility Model Information Architecture

22

OperationalView

OpportunitiesOpportunities

Paradigm Shift

3 Environment: Understanding the Challenge

1-3.

Seman

tics

4. Fra

mewor

ks ar

e com

plex

5. Tak

e bac

k the s

teerin

g whee

l

6. One S

ize do

esn’t

fit al

l

7. In

form

ation

is P

ower

8. Bra

in D

rain

para

lysis

Symptoms

Ineffective communication of requirements

Non-reliable information - Integrity/Quality

Extending individual efforts to common is painful

Convoluted processes

Inability to upgrade system

Don’t 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

Delay in system implementation

Cost overruns for a project

Root Causes

4Environment: Today’s Approach Leading Methodologies

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

5Environment: Today’s Approach Traditional View of Interoperability

Physical

Data Link

Network

Transport

Session

Presentation

Application

Source: Open System Interconnection

OSI Model

Provides different services to the applications

Converts the information

Handles problems which are not communication issues

Provides end to end communication control

Routes the information in the network

Provides error control between adjacent nodes

Connects the entity to the transmission media

Interconnection

6Environment: Momentum

7

Business Lines Transformation

Federal Enterprise Architecture

DoD Architecture Framework

NASCIOAdaptive Enterprise Architecture

Agile Enterprise

ImplementationImplementation

Netcentricity

Doctrine for

Agility &

Interoperability

Roadmap for going forward and provide traceability from vision to implementation

ArchitectureArchitecture

Getting to the Future - Obtaining our Objectives

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

· Can’t wait for a perfect solution

· Continuous integration process

9

Information Architecture*

Navigation

Products / Services

Enabling Technologies

Interfaces

Vocabularies

Content

Paradigm Shift Handle an Ever Changing Enterprise

High

Low

Stability

Agility Model

High

Low

* includes a Thesaurus to align vocabularies with business concepts

Physical

Data Link

Network

Transport

Session

Presentation

Application

OSI Model

Interconnection

Volatility

10

Information Architecture*

Navigation

Products / Services

Enabling Technologies

Interfaces

Vocabularies

Content

Paradigm Shift Handle an Ever Changing Enterprise

High

Low

Stability

Agility Model

High

Low

* includes a Thesaurus to align vocabularies with business concepts

Need to build on solid base, manage and communicate well, if not, above layers become unstable; our critical foundation which to architect - and our costliest to change !

Some of our artifacts are more stable than others...

… a layered model helps in costing, understanding, and leveraging unique qualities of various information architecture components

Volatility

11

Information Architecture

Navigation

Products / Services

Enabling Technologies

Interfaces

Vocabularies

Content

Supporting Information Architecture

High

Low

Stability

Agility Model

Source: Lubash Pyramid

Information Architecture

Enables the management of critical Enterprise information artifacts

12

Source: BusinessCentricMethodology.com

Methodology

Str

ateg

ic T

actic

al

Information Architecture

Enables the management of critical Enterprise information artifacts

BCM ModelApplying Constraints in Layers Where Appropriate

13

Business Drivers: Model / Process / Constraints

Contract – Collaboration Partner Specific Constraints

• Business Goals

• Frameworks & Standards

• Legacy

• Authoritative Sources

Templates

Templates provide context for declaration of constraints and choices

Methodology

BCM Templates

14

Business Drivers: Model / Process / Constraints

Contract – Collaboration Partner Specific Constraints

• Business Goals

• Frameworks & Standards

• Legacy

• Authoritative Sources

Templates

Templates provide context for declaration of constraints and choices

Information

form

The difference between data and information is context. Therefore, data must be put in form for context to be learned.

System of linked ‘forms’ & simple graphics ie. wizards

BCM Templates

15

ImplementationTemplates

Tem

plat

e-dr

iven

Tem

plat

e-dr

iven

Operational View - Interoperability Artifacts in Motion

16

ImplementationTemplates

Tem

plat

e-dr

iven

Tem

plat

e-dr

iven

Operational View - Interoperability Artifacts in Motion

17

CommunicationTemplates

Operational View - Interoperability Artifacts in Motion

18Opportunities: Afforded to an Agile Enterprise

Doing Business Differently1. 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

SemanticInteroperability

PragmaticInteroperability

Abstraction

Meta- Metadata

Metadata

Data

In addition to rationale, the Templates house the concepts, context, and constraints

• Classification• Ontology• Patterns

Wisdom

Knowledge

Information

Data

Add Structure

Add Experience

SynthesizeKnowledge

Templates

Concept

Context

Instance

Constraint

HumanIntelligence

Opportunities: Afforded to an Agile Enterprise 1. Pragmatic & Semantic Interoperability

20

     

 

Poor Integration

Traditional Contract

Good Integration

Aligned Ontology

Semantics, Semantics, Semantics

CollaborationPartner #1

CollaborationPartner #1

CollaborationPartner #2

CollaborationPartner #2

Source: Lubash Pyramid

Opportunities: Afforded to an Agile Enterprise 2. Metrics for Interoperability

Separate Ontologies

Contractdriving

Templates

21

Mapping (Option 1)

TransStd

Trans

App

App

InstanceInstanceICIC

MapMap

MapMap

AcrossDomain

Domain

Specific

Trans

App

InstanceInstance

App

Template (Option 2)

Registry

Target

ICIC

Opportunities: Afforded to an Agile Enterprise 3. Providing Options for Interoperability

Baseline

Specification

PopulatedTemplates

What is harder? Sending or Receiving?

22 Opportunities: Afforded to an Agile Enterprise 4. Trend Toward Service-Oriented Architectures

SHIFTSHIFT SHIFTSHIFT

Hub n’ Spoke Service Oriented (SOA)Centralized data processing only

Virtual Pt.-to-Pt.Physical Artifacts

Broker-based Metadata Strategy Reuse: High Central

End-to-End Tracking: Yes, CentralIntegration at Broker

Lookup Info: Must publish to BrokerMapping: Two or more

Bandwidth Required: HighestComputing: Central; Big Iron

Impact of Changes: HighPt.-to-Pt. Real-time: No

Technology Solution

Central & Distributed data processing Common Pt.-to-Pt. Mechanism

Logical & Physical ArtifactsEnterprise Metadata Strategy

Reuse: Much OpportunityEnd-to-End Tracking: Services

Integration at Point of UseLookup Info: Kept at Domain

Mapping: OnceBandwidth Required: LowestComputing: Distributed Load

Impact of Changes: LowPt.-to-Pt. Real-time: Yes

Business Solution

Ad HocDistributed data processing

Simple Pt.-to-Pt.Physical Artifacts

No Metadata Strategy Reuse: Little OpportunityEnd-to-End Tracking: LowIntegration at Point of Use

Lookup Info: Kept at DomainMapping: Only Once

Bandwidth Required: LowestComputing: Distributed Load

Impact of Changes: LowPt.-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

Using History-of-Use Filtering to leverage relationships between users and Enterprise artifacts

Ontology

Composite

• Institutional communicates and navigates Enterprise via ontology

• Expedient through discovery and use via CM Search

Viewports / Capabilities

CM Service

Sear

ch

Create

Domains

Source: http://www.CollaborativeMemory.com

Search

Results

Registry

Persistence

24Opportunities: Afforded to an Agile Enterprise

Doing Business Differently1. 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

25Moving the Enterprise Forward - Tactics

Build with existing infrastructure and have 1, 2, 5, 10 year plan

Apply Methodology• Leverage ‘hot button’ initiatives; portal efforts to derive organization’s 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

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

Infrastructure to Move the Enterprise ForwardMajor Supporting Services / Components

Rules/Mapping Engine

WorkflowOntology

•Taxonomy•Semantic Network

TemplateProcessor

•Thesaurus •Classifications

Federated

Visualization Tools

Index / Clustering

Personal Development - Information Architect

TasksTasks InfrastructureInfrastructure

Skills for Meeting a Demand of an Emerging Profession as an Information Architect• Database -> Document or Database <- 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 Te c

hn

i qu

es

G

UI

Lin

kin

g

C

on

tai n

ers

28

EAIEAIEAIEAI

Scope: Setting the Tone

Phase 2: XML DefinitionsPhase 2: XML Definitions Phase 2: XML DefinitionsPhase 2: XML Definitions

Phase 3:Phase 3: Vendor ImplementationsVendor Implementations Phase 3:Phase 3: Vendor ImplementationsVendor Implementations

Phase 1: MethodologyPhase 1: Methodology-- Specification – Vision-- Template Examples-- Switching & Linking of Templates-- Information Architecture

InteroperabilityInteroperability

EAIEAIEAIEAI

Taking the BCM to OASIS for Feedback, Extension and Consensus

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

http://www.dfas.info

Mike LubashDFAS XML Team LeadDOD Finance and Accounting XML Community MangerEmerging TechnologiesMike.Lubash@DFAS.mil

31Our Story, and we are sticking to it

BCM Overview

33BCM Infrastructure Conops

34Search 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