Architecture-Driven Enterprise Integration for Federal and State Governments

Tom Mowbray, PhDChief Software Architect

Keane Federalmowbray@keane.com(703)848-7371 (office)(703)568-9209 (cell)(703)848-7602 (fax)

September 23, 2003

Lessons learned from recent experiences architecting:•DoD Enterprise Resource Planning IT•DoD Enterprise Supply Chain IT•DoD Enterprise Workflow IT•DoD Enterprise Data Warehouse IT•State Enterprise Resource Planning IT•State Enterprise Customer Service IT•State Enterprise Social Service IT•State Corrections IT•State First Responder IT

we get IT done 2

Outline

• Enterprise & Solution Architectures

• Enterprise System Lifecycle

• Envisioning Phase

– What envisioning achieves

– Business process reengineering (BPR) results

– Role of IT Solution Architecture

– Key lessons learned in IT envisioning

– IT Architecture Tradeoffs

• Conclusions

we get IT done 3

Solutions Comprising Enterprise ArchitectureSolution Architectures are actionable plans within EA

Customer Service Solution Architecture

Back Office Solution ArchitectureHR, Finance, Accounting, Budgeting, Procurement, Comm/IT, Property/Assets, Enterprise DW

Cross-Agency Business Mission Solution ArchitecturesSupply Chain Management, Cross-Agency Case Management, Manufacturing, etc.

Agency Solution Architectures

Enterprise Architecture: Roll-up of Architectures

we get IT done 4

Enterprise Solution Architecture LifecycleTypical Enterprise Solution for 50K employees has modest cost throughout lifecycle when properly planned & managed

1000X100X10X1XRelative Cost of Mistakes

64%35%1%Small Fraction of 1%

Percent Total Cost of Ownership

15 years30 months9 months3 monthsTypical Duration

1040155Typical Team Size

80%80%20%20%IT Skill Mix

20%20%80%80%Business Skill Mix

Operations & Maintenance

Implementation & Transition

Requirements & COTS Selection

Business & IT Envisioning

PHASES ->

Solu

tion

Team

we get IT done 5

Envisioning Phase: Transform Problems into SolutionsEnvisioning is lowest cost & highest benefit architecture phase

BEFORE•Business Problems

•IT Limitations•Rogue Projects

•Under-funded IT•Disillusionment

•Cynicism

AFTER•Known Root Causes•Business Process Solutions•IT Architecture Solution•Implementation Plan•Cost Benefit Justification•IT Cost & Materials•Business and IT Rationale•Optimism•Buy In => Funding

Emerging Hypothesis/Transform SessionsValue-AddedInformationGathering

FosterSolution

Buy-In

Build COTS Market AwarenessIncorporate Best Practices

AS IS ROADMAP VISIONtransformed by which realizes

we get IT done 6

Target Business Process, Plan, and Cost BenefitsSystem pays for itself through business process improvements

CustomerContact

2.0AutomatedResponse

Data SourceData SourceKnowledge

ManagementBase

ServiceDelivery

Data SourceData SourceAgency DeliverySystems

5.0Close

6.0CustomerFeedback

end

* Directory* Services and Agencies* FAQs* Scripts

end

3.0ServiceRequest

4.0Non ServiceRequest

* Information* Complaints* etc.

Data SourceData SourceKnowledge

ManagementBase

Level 1 - Future Customer ServiceFlow

DecisionData Source

TerminatorTrigger Out of ScopeDefinedProcess

1.0Receive Customer

Contact

Real Example: Business SolutionReal Example: Business SolutionReal Example: Business Solution

Sample: To-Be Business Processes Sample: Implementation Plan Timeline

we get IT done 7

Business Reengineering View of ITClassic BPR view of IT resolves few technology questions

Customer Interaction Channels

Agency A

Fax Web eMailTelephone Mail Walk-in Direct

KnowledgeManagement

Customer Service Process and Standards

Customer Service Training

Centralized Knowledge Management

Enterprise Systems Management

Agency AAgency A

Tier 2CSR

Tier 3Staff

Tier 1- EnterpriseCSR60-80%60-80%

20-40%20-40%

AgencyDelivery

Application Integration

AgencyDelivery

AgencyDelivery

Customer Data

Warehouse

Measurement & Reporting

CSO

CSO Telephony& Technology

Process

Key

Technology

Personnel

Customer

Lifecycle Management

Real Example: Business SolutionReal Example: Business SolutionReal Example: Business SolutionSample: Business-centric View of IT Solution

we get IT done 8

Enterprise Customer Service IT Architecture ViewIT architecture planning adds value and credibility to BPR

Real Example: IT SolutionReal Example: IT SolutionReal Example: IT Solution

Sample: IT-centric view of IT Solution

we get IT done 9

LegacyModule

Dependencies

Assessing Legacy IT EnvironmentBusiness processes are overwhelmed by legacy IT complexity

Sample: Enterprise Legacy Systems

RCAS

SAV

REALM

PRS

SAM

RAMMICAP

EXPRESSSHOPPRO

Pipeline Tracking

D087 (WSMIS)

D036

D043

D043A

D043B

D046

D071

D086

D143C

CatalogingSystems

MP&E PRPS

RMS (D072 & D040)

RSSP

RequirementsSystems

D220

D169

D155

D064

D023K(Ammo)

Provisioning Systems

D035A

D035B

RAMP

SSSC

D035ED035J

D035K

D035L

D035T

D035W (Marine Corps Interface)

D035

Equipment ManagementC001 (AFEMS)

D039 (CERC)

IPMS

MASS

Retail SupplySBSS/ILS-S (D002A)

we get IT done 10

Leverage Best Practices, Standards, and GuidelinesTailor powerful ideas to strengthen and validate the solution

• Industry best-practices avoid costly reinvention• Survey the processes and technologies of comparable enterprises• Existing standards & guidelines capture key solution concepts• Experienced domain IT experts validate approach & estimates• Provide independent guidelines for follow-on, e.g. implementors• Examples: OMB BRM/TRM, FEAF/DODAF, BMEA/FLE, SCOR,

NASCIO IJIS, J2EE Core Patterns, Microsoft Enterprise Solution Patterns, IBM E-Business Patterns, etc.

Source: Supply Chain Council (Keane is a member).Sample: Best Practices Reference Model

we get IT done 11

Architectural Tradeoffs: Functions, Hardware, SoftwareSolid architecture decision-making is key to solution success

IBM

IMA ACEDS

CFSA FACES

Data General DMH eCura

FSA APSIS

RSA

OCC ProLaw

latigid

YSA Lotus Notes

IBM

MPDMPD

HEWLETTPACKARD

DCHA IBM

DCPS SDCPS SE

MRDDA MCIS

CFSAPC

DHSPC

MPDPC

DCHAPC

MHDPC

OCCPC

DCPSPC

DCPSDataMart

OCCDataMart

DHSDataMart

EOMPC

DMHDataMart

DCHADataMart

CFSADataMart

MPDDataMart

Family CourtData Mart

IBM

DOH

DOH

DOHDataMart

IBM

IMA ACEDS

CFSA FACES

Data General DMH eCura

FSA APSIS

RSA

OCC ProLaw

latigid

YSA Lotus Notes

IBM

MPD WALESMPD WAACIS

HEWLETTPACKARD

DCHA IBM

DCPS SIDCPS SET

MRDDA MCIS

EnterpriseApplicationIntegration

Servers

Inter-AgencyNotifications

WebService

Person & FamilyIdentification

WebService

FSAPC

CFSAPC

MRDDAPC

YSAPC

IMAPC

MPDPC

DCHAPC

DMHPC

OCCPC

DCPSPC

RSAPC

Cross-AgencyCase DataWarehouse

Service

IBM

DOH

DOHPC

AgencyData Marts

Sample: Decentralized IT Architecture Sample: Centralized IT Architecture

we get IT done 12

Assessing Market, Technology, and Should-CostsArchitecture match to COTS components impacts feasibility

MarketingHype

0%10%20%30%40%50%60%70%80%90%

100%

DesiredAchievable

MinimumAcceptable

Average ERPProduct

Averaqe CRMProduct

Factor: COTS Functional Match

0%

20%

40%

60%

80%

100%

120%

0 1 2 3 4 5 6 7

Reference Accounts

Rela

tive

Pric

e

Factors: COTS Market & Budget Estimation

INNOVATORTechnologies

EARLYADOPTER

Technologies

EARLYMAINSTREAMTechnologies

LATEMAINSTREAMTechnologies

LAGGARDTechnologies

Factor: Technology Maturity

Factor: COTS Fact vs. FictionId

eal R

ipen

ess

[1]

[1] A. Halingten, J. C. Verville, Acquiring Enterprise Software: Beating the Vendors at Their Own Game, Prentice Hall, 2001

we get IT done 13

Explain Key Technologies to Stakeholder ChampionsState-of-art technologies enhance solution’s benefits

FlatFiles

Scheduler Program Scheduler Program

ExtractionProgram

TransferProgram

TransferProgram

DB UploadProgram

EAIOperations &Maintenance

Tool

EAIRules

DevelopmentTool

COTSEAI

Adapter

COTSEAI

Adapter

ApplicationData Source

System

ApplicationData Source

System

ApplicationDatabase Application

Database

COTSEAI

Server

BatchLoading

Sample: Legacy Batch Transfers Sample: Enterprise Application Integration

24 Hour Latency Zero LatencyExchange

FlatFiles

ExtractionProgram

TransferProgram

TransferProgram

DB UploadProgram

Scheduler Program Scheduler Program

COTSEAI

AdapterCOTS

EAIAdapter

COTSEAI

Server

we get IT done 14

Conclusion: Enterprise Solution Architecture BenefitsSolution architecture yields benefits in every lifecycle phaseEnvisioning sets the strategy & guidelines for follow-on success

Envisioning Phase Selection Phase

Maintenance PhaseImplementation Phase

•Implementation Roadmap•Program Credibility•Fundability•Fact-based Budgeting•Feasibility Validation•Stakeholder Buy-In

•COTS Product Selections•Deployment Architecture•Technology Requirements•COTS Validation•In-Depths Plans•Skills Requirements

•System Implementation•Interface Specifications•Test Specifications•Requirements Satisfaction•Future Reqts Flexibility•Interoperability•Risk Reduction

•IT Strategic Maneuverability•Fact-Based Change Decisions•Preserved System/User Qualities•Up-to-Date Specifications

•Preserves System Investment

we get IT done 15

Enterprise Resource Planning IT Architecture ViewExample of Back Office Solution Architecture

Real Example: IT SolutionReal Example: IT SolutionReal Example: IT Solution

we get IT done 16

Enterprise Data Warehouse IT Architecture ViewExample of Enterprise Data Warehouse Solution Architecture

Real Example: IT SolutionReal Example: IT SolutionReal Example: IT Solution

we get IT done 17

Agency Solution Architecture ViewAgency architecture supports enterprise interoperability

Real Example:Real Example:Real Example:IT SolutionIT SolutionIT Solution