1

For Enterprise Agility & Interoperability

OASIS BCM Technical CommitteeOASIS 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

• LandscapeLandscape

• ApproachApproach

• ImplementationImplementation

• AdoptionAdoption

– Learning the Terrain– Understanding Today’s 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– Mission Summary

4

Learning the TerrainLearning the Terrain Understanding Today’s SolutionsUnderstanding Today’s Solutions Paradigm ShiftParadigm Shift

LandscapeLandscape

5

Learning the Terrain

… 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?

… customer’s 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 Source: eProcess Solutions

It is helpful to look back in time…

6

Understanding Today’s Solutions

• Enterprise Architecture - a New Beast Requiring New Ideas - software approaches are only part of the solution

- ETL and EAI technologies aren’t 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

SHIFTSHIFT SHIFTSHIFT

Hub n’ Spoke Service-Oriented (SOA)Ad Hoc

Source: eProcess Solutions

7

• Traditional Approach– ETL– EAI– Data warehouse– B2B + electronic commerce

• New Holistic Approach– Service Oriented Architecture– Business-centric– Leverage XML

Paradigm Shift

8

Foundation of BCMFoundation of BCM BCM LayersBCM Layers Information ArchitectureInformation Architecture BCM TemplatesBCM Templates

Declarative Component OperationsDeclarative Component Operations

Foundation of BCMFoundation of BCM BCM LayersBCM Layers Information ArchitectureInformation Architecture BCM TemplatesBCM Templates

Declarative Component OperationsDeclarative Component Operations

ApproachApproach

9

The Foundation of BCM

Voca bula r ie s

Ev e nts

W orkflow

W ordprocessor

Spreadsheet

Outliner

Da ily P roc edures P e r iod-E nd P roc edures F inanc ia l Repor t ing P roc edures

W ork O rder

PrepareSource

DocumentPost

Journals ,Ledg ers

PrepareJournalVoucher

Journal Voucher

Post G eneralLedg er

Journal Voucher

O btain AccountBalances for

W orksheet

W orksheet

PrepareT ria l

Balance

T rial Balance

Analyze A ccountBalances. Prepare

Adjusting E ntriesand Adjusted T rial

Balance

Journal VoucherPostG eneral

Ledg er

Journal VoucherAdjustableT rial Bar

PrepareF inancial

S tatem ents

F inanc ialS tatem ents

O btain Post

C lo s in g T ria lBalance

Post C los ing T B

J.V . F ile

Journal VoucherPostG eneral

Ledg er

Journal Voucher

Prepare

C lo s ingEntries andPost to GL

Tabulations

Artifacts

Exam ples:PowerpointGraphics toolHTML fram es

Models

Co lla bora tionA gre e m e nt ( CPA )

Pattern(s)

Com m unity ofInterest

Docum e nts

Rule s

Transactions

Exam ples:Graphics toolCASE toolStructure Tool

Exam ples:WordOpen OfficeDocum ent tool

Exam ples:ExcelLotusHTML tables

Collaboration

Cla ss ifi ca tions

Vocabularies

Exam ples:RegistryLotus NotesHTML / PortalsGroove

Step 2 :

Build Templates with Familiar Business Tools

Eve n tsR u le s

T ran sa ctionT ran sa ction

Sch e maSch e ma

C o n tra ctC o n tra ctA g reem en t P a ttern

W o rk f lo wW o rk f lo wM o d elin g &B u sin ess P a ttern s

req u est

p ro ce ss

req u est

p ro ce ss

respo n se

p ro ce ss

re je ct

a cce p tp ro p ose

co u n te r

E x cha n g eE x cha n g e

S p e cif ica tio nS p e cif ica tio nM o d el & S ch em a s

N o u ns

Ve rb sT ran sp o rt

R o le sC o n ce p tC o n ce p tR eg istry

Tem

plat

eT

empl

ate --

driv

endr

iven

B u s in e s s G o a lsB u s in e s s G o a lsG o a l P a ttern

CAM templateAssemb ly

C o n te xt

Step 3 :

Deploy with DeclarativeComponent Operations

Business Layer

Conceptual Layer

Business Drivers: Model / Process / ConstraintsTarget Constructs & Patterns Target Constructs & Patterns

Implementation Layer

Physical - Message & PresentationPhysical - Message & Presentation

Extension Layer

Contract -Collaboration Partner Specific Constraints

Pub

lish

Baseline Specification per CoIBaseline Specification per CoI

Concepts in OntologyConcepts in Ontology

Business Goals

Frameworks & Standards

Legacy

Authoritative Sources

1

2

3

4

Step 1 :

Use Layers to Define Business Needs

While Referencing the Information Architecture

10

Business Layer

Conceptual Layer

Business Drivers: Model / Process / Constraints

Target Constructs & Patterns Target Constructs & Patterns

Implementation Layer

Physical - Message & PresentationPhysical - Message & Presentation

Extension Layer

Contract -Collaboration Partner Specific Constraints

Pub

lish

Baseline Specification per CoIBaseline Specification per CoI

Concepts in OntologyConcepts in Ontology

Business Goals

Frameworks & Standards

Legacy

Authoritative Sources

Str

ateg

ic T

actic

al

Simplification Through BCM Layers

1

2

3

4

11

Deriving the set of business needs and context from each information layer

Holistic Approach = Layers + Information Architecture

Specific Ontology Navigation

Content Rendering

Transaction Handling

Business Processes

Collaboration Agreements, MOA

Codelist subsetting Services; Transaction Processing

Communities of Interests- CoI

11

22

33

44

55

66

778899

10 10

11 11

Source: eProcess Solutions

12

Information Architecture

Navigation

Products / Services

Enabling Technologies

Interfaces

Vocabularies

Content

Re-Inventing Your Information Architecture

High

Low

Stability

Agility ModelInformation Architecture

Enables the management of critical Enterprise information artifacts

Information Pyramid

13

Build Templates Using Familiar Tools

Voca bula r ie s

Ev e nts

W orkflow

W ordprocessor

Spreadsheet

Outliner

Da ily P roc edures P er iod-E nd P roc edures F inanc ia l Report ing P roc edures

W ork O rder

PrepareSource

DocumentPost

Journals,Ledg ers

PrepareJournalVoucher

Journal Voucher

Post G eneralLedg er

Journal Voucher

O btain AccountBalances for

W orksheet

W orksheet

PrepareT ria l

Balance

T rial Balance

Analyze A ccountBalances. PrepareAdjusting E ntries

and Adjusted T rialBalance

Journal VoucherPostG eneralLedg er

Journal VoucherAdjustableT rial Bar

PrepareF inancial

S tatem ents

F inancialS tatem ents

O btain PostC lo s in g T ria l

Balance

Post C losing T B

J.V . F ile

Journal VoucherPostG eneralLedg er

Journal Voucher

PrepareC lo sing

Entries andPost to GL

Tabulations

Artifacts

Exam ples:PowerpointGraphics toolHTML fram es

Models

Co lla bora tionA gre e m e nt ( CPA )

Pattern(s)

Com m unity ofInterest

Docum e nts

Rule s

Transactions

Exam ples:Graphics toolCASE toolStructure Tool

Exam ples:WordOpen OfficeDocum ent tool

Exam ples:ExcelLotusHTML tables

Collaboration

Cla ss ifi ca tions

Vocabularies

Exam ples:RegistryLotus NotesHTML / PortalsGroove

14

Action Event

InformationRuleWhatWhy

How When

Where / Who Where / Who

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

Action Event

InformationRuleWhatWhy

How When

Action Event

InformationRuleWhatWhy

How When

BCM Templates – Workflow Viewpoint

15Semantic

Interoperability

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

Templates - Role and Functions

16

     

 Operational View Declarative Components of Interoperability

Eve n tsR u le s

T ran sa ctionT ran sa ction

Sch e maSch e ma

C o n tra ctC o n tra ctA g reem en t P a ttern

W o rk f lo wW o rk f lo wM o d elin g &B u sin ess P a ttern s

req u est

p ro ce ss

req u est

p ro ce ss

respo n se

p ro ce ss

re je ct

a cce p tp ro p ose

co u n te r

E x cha n g eE x cha n g e

S p e cif ica tio nS p e cif ica tio nM o d el & S ch em a s

N o u ns

Ve rb sT ran sp o rt

R o le sC o n ce p tC o n ce p tR eg istry

Tem

plat

eT

empl

ate --

driv

endr

iven

B u s in e s s G o a lsB u s in e s s G o a lsG o a l P a ttern

CAM templateAssemb ly

C o n te xt

17

StructureChoices

StructureChoices

ContextValues

ContextValues

RequiredContent

Structure

RequiredContent

Structure

AssemblyProcessorAssemblyProcessor Content

ReferencesContent

References

1

Payload / RenderingPayload / Rendering

2

AssemblyStructureAssemblyStructure

Payload AssemblyPayload

Assembly

3

ApplicationDatabase

ApplicationDatabase

RegistryComponents

RegistryComponents Conceptual

Logical

Physical

Template Driven Declarative ComponentsExample: Payload Assembly

Vocabulary nouns,and

Industry Dictionaries

Vocabulary nouns,and

Industry Dictionaries

Re-usable Business Information

components

Re-usable Business Information

components

Note: OASIS CAM reference model

18

Becoming NetCentricBecoming NetCentric Service-Oriented ArchitectureService-Oriented Architecture Communities and DomainsCommunities and Domains Managing Context - Choice PointsManaging Context - Choice Points

Becoming NetCentricBecoming NetCentric Service-Oriented ArchitectureService-Oriented Architecture Communities and DomainsCommunities and Domains Managing Context - Choice PointsManaging Context - Choice Points

Implementation Implementation

19

Becoming netCentric

Source: DONCIO

NetCentric

NetCentric

20

Backup for side: 25

Business Applications and Functions

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

Finance Account HRProjectMgmt

Procure

User Interface - Presentation

22CommonExchangeSOAP-basedEnvelope HTTP

11

Common ServicesWeb Services

DCW

Registry

DCDSO

AService Oriented Architecture (SOA)

Warehouse

21

Aligning Classifications and Understanding e.g. DUNS, UNSPSC, NSN, Part Number, Address, Weight, Width …

Then creating Multiple Facets or combination of characteristics

Communities and DomainsCollaborating with your Partners

Arlington

Indy

Denver

Cleveland

Pensacola

Columbus

Location

X

Code

Identifer

Angle

Date

Mass

Area

Classword

X

Mil Pay

Civilian Pay

Commercial Pay

Accounting

...

…

X

Location

Bus

ines

s Li

ne

Class

word

Business Line

Concept

Business Outcome - rapid search and discovery by faceted selections

22

• 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

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

Context - Understanding

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 don’t 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 ComplexIf-then-do Decision Agents

Implementation

Choice Pt.

25

Context - Managing Via Choice Points (con’t)

• 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

Business Drivers: Model / Process / Constraints

Contract – Collaboration Partner Specific Constraints

Business Goals

Legacy systems

Authoritative Sources

Applying to constructing BCM Templates…

26

Holistic ApproachHolistic Approach Planning and FacilitationPlanning and Facilitation Resources and Existing workResources and Existing work Mission SummaryMission Summary

Holistic ApproachHolistic Approach Planning and FacilitationPlanning and Facilitation Resources and Existing workResources and Existing work Mission SummaryMission Summary

AdoptionAdoption

27

Holistic Approach Critical Build-out

• CPA / MoU• BPM

Business Process

Architecture

Business Transactions Technology

Integration/Program Execution

Compliance & TestingImplementation Training

• Information =Context + Data• Semantic Services

• Extensible stores •Extensible interfaces

• Information Architecture• Choice Points

• Business First• Templates

• Extension Layer• Declarative

• Implementation Layer• Content Assembly Mechanism

CAM

• NetCentric approach• Registry

• Contracts • Communication- Business-to-Business-Business-to-Technical

Architecture

Business Transactions Technology

Integration/Program Execution

Compliance & TestingImplementation Training

• Information =Context + Data• Semantic Services

• Extensible stores •Extensible interfaces

• Information Architecture• Choice Points

• Business First• Templates

• Extension Layer• Declarative

• NetCentric approach• Registry

• Contracts • Communication- Business-to-Business-Business-to-Technical

• CPA / MoU• BPM

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!Thank You!

http://BusinessCentricMethodology.comhttp://www.oasis-open.orghttp://eprforum.org