Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration...

30
Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems Group, Inc. [email protected]

Transcript of Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration...

Page 1: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Development of theChesapeake Bay Program’s

Enterprise Architecture2010 Baseline Configuration

2010 Target Architecture

Nancie L. Imler

TreCom Systems Group, Inc.

[email protected]

Page 2: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

THE BAY PROGRAM IS AN EXCELLENT CANDIDATEFOR ALIGNMENT TO THE “FEA” FRAMEWORK

1. Over 100 Partners within the CB Watershed2. Partners execute the core-mission business

functions3. Culture of the Program has existed for twenty-five

years4. Data support is distributed across the Partnership5. Jurisdictions have their own mandates6. Bay Program has no authorization authority7. Reporting is burdensome8. Bay Program internal organization not hierarchical9. Change and upheaval the last 3-4 years, including

multiple audits and an executive order10.Jurisdictional resources declining, both financial and

human11.Program has a high political profile

CH

ALL

EN

GES

Page 3: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

A simplified method was used to record the baseline

configuration based on FEA architectural layers;

these layers were then aligned to FEA models for

recommendations within the Target EA.

Page 4: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Baseline Configuration

Performance Layer

Business Layers

Data Layer

GoalsDesired Results Strategies

Technology Layer

Services Layer

Have Responsibilities

Strategic Layer

Make Decisions

Perform Actions

Request Information

Generate/Change Information

Have Attributes

Measures Metrics

Lines of Business

Business Sub-Functions

Business Processes

Data Input Discovery Display

Meta Data Dictionary Content Quality

Hardware

Tools

Infrastructure

Partners

Page 5: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Strategic Layer

Environmental Health Goals•Water Quality•Habitat and Lower Food Web•Fish and Shellfish

Manage FisheriesSustainably Goal

Restore and ProtectHabitat Goal

Protect and RestoreWater Quality Goal

Maintain Healthy Watersheds Goal

Foster Stewardship Goal

Enhance Partnering Leadership, Management Goal

Restoration GoalsTopicAreas

TopicAreas

TopicAreas

TopicAreas

TopicAreas

TopicAreas

Desired Results

Desired Results

Desired Results

Desired Results

Desired Results

Desired Results

Strategies

Strategies

Strategies

Strategies

Strategies

Strategies

Environmental Activities

Environmental Activities

Environmental Activities

Environmental Activities

Environmental Activities

Environmental Activities

TopicAreas

Desired Results

Baseline

Page 6: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Performance LayerFocus Ecosystem HealthPerformance Measurement System

Health Index and Indicators

Performance Measures

Environmental Health measurements depicted in specific representations of environmental impacts that is relevant, quantifiable, and documented.

Focus Restoration of the Ecosystem

Performance Measurement System

Restoration Index and Indicators

Performance Measures

Restoration measurements depicted in specific representations of capacity, process, or outcome that is relevant, quantifiable, and documented; Realistic Annual Targets (RAT); Two-Year Milestones

Baseline

Page 7: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Business Layer

Chesapeake Registry Data Call

Registration Activity Data Call

Health and Restoration Data Call

WIPs and TMDLs Monitoring

Modeling

Information Management

Science and Technical

Grants Management

Baseline

Page 8: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Services LayerServices exist throughout the Partnership and have been identified as to:

• Software application systems that are specific to a business function.

• Software application components that are common enabling as they are reusable and can span multiple processes.

• Data-wrapped web services exposing CBP data for reference and consumption by other software applications, tools, and/or users, usually intended for machine-to-machine interaction but can also be used directly by users, depending on the interfaces developed.

• Technology products leveraged by software application systems or other common enabling services, including networking and telecommunications, data quality, security, collaboration, and discovery.

• Technology tools which are software applications available for use with minimal support and responsibility from the owner, including customized COTS products or licenses to reusable applications such as web content; geospatial; metadata; modeling and simulation; map; Extract, Transform and Load (ETL); analytics; web service publishing; and various utilities.

Baseline

Page 9: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Data LayerGuidelines and Policies

• Data, information, and document deliverables requirements• Deliverable serving vs. submission policy• Locational data policy• Map coordinate datum policy• Map coordinate projection guideline• Metadata policy• Common station names guideline• Common data dictionary guideline• Common database design guideline• Calendar date policy• Common method codes guideline• Numeric data reporting guideline• Interagency Taxonomic Information System (ITIS) biological

nomenclature policy

Data Quality Guidelines• Quality Assurance Management Plan• Geospatial Data Quality Assurance Plan• Data Security Guidelines

Baseline

Page 10: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Technology LayerTechnology Support

• Wide Area Network• Local Area Network• CB Data Center Servers• Desktop Configuration and Management Support• CIMS Wireless Network• CIMS Virtual Private Network• Intranet• Technical Infrastructure to Support Collaboration• IT Asset Management• Infrastructure Support for Service Oriented Architecture• IT Infrastructure Support for Geospatial Analysis

Security

Baseline

Page 11: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Performance Layer

Business Layers

Data Layer

GoalsDesired Results Strategies

Technology Layer

Services Layer

Have Responsibilities

Strategic Layer

Make Decisions

Perform Actions

Request Information

Generate/Change Information

Have Attributes

Measures Metrics

Lines of Business

Business Sub-Functions

Business Processes

Data Input Discovery Display

Meta Data Dictionary Content Quality

Hardware

Tools

Infrastructure

Partners FEA Performance Reference Model

FEA Business Reference Model

FEA Service Component Reference ModelFEA Technical Reference Model

FEA Data Reference Model

Target Architecture

Target

Page 12: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Business Area SEGMENT (Line of Business)

Sub-Function 1 Sub-Function 2

Process 2Process 1Start End

Business Area

Segment (LoB)S

Processes

Services

FEA BRM Hierarchy

Sub-Function

50 agencies implement

federal drug control

strategies

29 agencies administer

541 clean air, water, and

waste programs

13 agencies administer 342 federal economic

development-related

programs

12 agencies administer

more than 35 food safety

laws

11 agencies administer 90

early childhood programs

Particularly hits “home” because of the executive order and federal agencies’ missions

Page 13: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

(108) Environmental Management

(109) General Science and Information

(117) Natural Resources

(202) Knowledge Creation and

Management

LoB within the CBP’s Core-Mission Areas

CBP

•023: Environmental Monitoring and Forecasting

•024: Environmental Remediation

•025: Pollution Prevention and Control

(108) Environmental Management

•026: Scientific and Technological Research and Innovation

(109) General Science and Innovation

•056: Water Resource Management

•057: Conservation, Marine and Land Management

•059: Agriculture Innovation and Services

(117) Natural Resources

•069: Research and Development

•070: General Purpose Data and Statistics

•071: Advising and Consulting

•072: Knowledge Dissemination

(202) Knowledge and Management

Target

Page 14: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

(108) Environmental Management

(109) General Science and Information

(117) Natural Resources

(202) Knowledge Creation and Management

LoB within the CBP’s Business and Enterprise

Services(3

04) P

lan

nin

g a

nd

B

ud

getin

g

(305) P

ub

lic A

ffairs

(207) Tra

nsfe

rs S

tate

s &

Local G

ov’ts

(303) L

eg

isla

tive

Rela

tion

s

(205) F

ed

era

l Fin

an

cia

l A

ssis

tan

ce

(301) C

on

trols

an

d

Overs

igh

ts

(401) A

dm

inis

trativ

e

Man

ag

em

en

t

(404) In

form

atio

n &

Tech

M

gt

Target

Page 15: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

•080: Federal Grants (Non-State)

(205) Federal Financial Assistance

•087: Formula Grants

•088: Project/Competitive Grants

(207) Transfers to States and Local Governments

•091: Corrective Action

•092: Program Evaluation

•093: Program Monitoring

(301) Controls and Oversight

•097: Legislation Tracking

•098: Legislation Testimony

•099: Proposal Development

•100: Congressional Liaison Operations

(303) Legislative Relations•101:

Budget Formulation

•103: Enterprise Architecture

•104: Strategic Planning

•105: Budget Execution

•107: Management Improvement

•259: Budget and Performance Integration

(304) Planning and Budgeting

•108: Customer Services

•109: Official Information Dissemination

•110: Product Outreach

•111: Public Relations

(305) Public Affairs

•120: Help Desk Services

(401) Administrative Management

•136: System Development

•137: Lifecycle/Change Management

•138: System Maintenance

•139: IT Infrastructure Maintenance

•140: Information Security

•141: Record Retention

•142: Information Management

•262: Information Sharing

•263: System and Network Monitoring

(404) Information and Technology Management

Target

Page 16: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

ENVIRON-MENTAL MGT108

GENERAL SCIENCE AND INNOVATION109

NATURAL RESOURCES117

KNOWLEDGE CREATION AND MGT202

FEDERAL FINANCIAL ASSISTANCE205

TRANSFERS TO STATES207

CONTROLS & OVERSIGHT301

LEGISLATIVERELATIONS303

PLANNING AND BUDGETING304

PUBLIC AFFAIRS305

ADMINISTRATIVE MANAGEMENT401

INFORMATION & TECHNOLOGY MGT404

023Environmental Monitoring & Forecasting

026Scientific and Technological Research and Innovation

056Water Resource Mgt

069Research and Development

080 Federal Grants(Non-States)

087Formula Grants

091Corrective Action

097Legislation Tracking

101Budget Formulation

108Customer Services

120Help Desk Services

136System Development

024Environmental Remediation

057Conservation, Marine and Land Mgt

070General Purpose Data and Statistics

088Project/Competitive Grants

092Program Evaluation

098Legislation Testimony

03 Enterprise Architecture

109Official Information Dissemination

137Lifecycle/Change Management

025Pollution Prevention/ Control

059 Agriculture Innovation and Services

071Advising and Consulting

093Program Monitoring

099Proposal Development

104:Strategic Planning

110Product Outreach

138System Maintenance

072Knowledge Dissemination

100Congressional Liaison Operations

105: Budget Execution

111Public Relations

139IT Infrastructure Maintenance

107 Management Improvement

140Information Security

259Budget and Performance Integration

141Record Retention

142Information Management

262Information Sharing

263 System and Network Monitoring

GITs 1-6, MB, PSC, EC

GITs 1-5

GIT6 STAC STAR

Chesapeake Bay Commission/States/EPA

Communications Office

Target

Page 17: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

INFORMATION RESOURCEPROCESSES

OUTPUTBUSINESS PROCESSEVENT

Models are utilized to avoid: • Strategy rarely driven down into the organization• Business architecture insufficiently defined• Different operating models across projects• Investments determined by budgeting factors and not planning• Projects driven by technology and not what the business needs• Benefits not tracked back to business cases• Change not impacted across the organization• Business processes not documented, analyzed, or adjusted• Projects not adjusted• Project forecasting inadequate or incomplete.

Business Process Models for each LOB

Target

Page 18: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

The CBP’s BRM and Recommendations

1. Validate the Target EA’s proposed definition of CBP’s Core-Mission LoB and sub-functions.

2. Validate the Target EA’s proposed definition of CBP’s Business Service and Enterprise Service LoB and sub-functions.

3. Validate the alignment of the LOB responsibilities with CB roles.

4. Validate the alignment of the Bay processes with the sub-functions.

5. Identify and communicate gaps across all the LoB, sub-functions, and processes.

6. Prepare for climate change processes.

7. Plan solutions using EPA’s EA Segment Reports (EASR).

8. Identify authoritative data sources for all the CB processes.

9. Examine the business processes for opportunities to use the National Environmental Information Exchange Network (NEIEN).

10. Modify the CBP’s governance to include its Communications Office and the Federal Office Directors in the governance chart; address confusion with multiple operational units providing direction; create a project management office within the Scientific, Technical Analysis and Reporting (STAR) unit; and increase the responsibility of the CBP’s Information Steering Committee.Target

Page 19: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Mission and Business ResultsServices for Citizens

Support Delivery of ServicesManagement of Government

Resources

Customer ResultsPartner Benefits, Service Coverage

Timelines and ResponsivenessService Quality and Accessibility

Processes and ActivitiesFinancial, Productivity

Timeliness, QualitySecurity and Privacy

Management and Innovation

Human Capital TechnologyTechnology CostsQuality Assurance

Information and DataReliability and

AvailabilityEffectiveness

Other Fixed Assets

Strategic OutcomesCB Performance

Reference Model and

Recommendations1. Provide accessibility and understanding through terminology services.

2. Acknowledge possible future integration of Federal and CB partnership strategies into one coordinated strategy with a shared list of strategic outcomes.

3. Document the partnership’s Strategic Plan4. Record gaps for indicators and metrics as identified by GITs5. Conduct Strengths, Weaknesses, Opportunities and Threats (SWOT) analysis for

each desired result in the Core Mission LoB.6. Expand CB performance accountability to include metrics for the Customer Results

Measurement Area.7. Expand CB performance accountability to include metrics for the Processes and

Activities Measurement Area.8. Expand CB performance accountability to include metrics for the Technology

Measurement Area.9. Modify the Chesapeake Registry to serve as the performance accountability system

by:

A. Designating strategic goals as health or restoration goals;B. Adding desired results;C. Adding strategies;D. Linking environmental activities to one or more strategies;E. Indicating priority strategies and priority geographical areas;F. Categorizing strategy records as short-term or long-term;

G. Expanding Chesapeake Registry to include the Health and Restoration Assessment framework;

H. Distinguishing between planned and executed activities;I. Recording metrics for the strategic and activity levels;J. Creating activity transaction records linking Chesapeake Registry activity records

with environmental data sets to assess effectiveness of strategy;K. Including “outputs” in the data call for Partner environmental activities; andL. Modifying Chesapeake Registry’s physical architecture to support metrics.

Target

Page 20: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Actions

Behavior

ProcessOutputs Input

PerformanceMeasures

Activity Integration

Plan

Evaluation of Targets and Milestones

Strategy

Strategic Plan

Environmental Impacts

Environmental Outcomes

PSC and MB

Goals, Desired Results

GIT

Partner

Human and Financial Capital,

Technology, Data,

Science, Other Assets

Modification of Goals/Desired

Results

EComparison

ROI

CB Performance Reference Model and

Recommendations

Target

Page 21: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Protect and Restore WQ

Reduced Loads Ag Lands &

Animal Operations

Reduced Loads Streamside &

Ttidal Shoreline Riparian Areas

Reduced Loads Onsite and

Septic Systems

Reduced Loads Developed

Lands

Reduced Sediment

Loads Streambank

and Tidal Shorelines

Reduced Loads Air Emissions

Reduced Loads M&I

WasteWater

Reduced AMD Impacts on

Streams

Chemical Contaminants

Reduced Chemical

Loads

High amount of N Discharged

High amount of P Discharged

Population Growth – high

volume of water for treatment

Old treatment processes and

technology

Indicator

Quantify the process to cap

loads from non-significant

facilities

Number of

Reduced Pounds

of N

Determine Facility

Upgrade schedule for significant facilities

Number of

Reduced Pounds

of N

Issue annual N&P caps in

NPDES renewal

cycle

Number of

Reduced Pounds

of N*

Seek to fund nutrient

reduction upgrades or

secure nutrient credits

Number of

Reduced Pounds

of N*

EPA ICISAnnual Data

Call

Measurement Record by Year

Measurement

Record by Year

2007 – 100 lbs2008 – 170 lbs2009 – 250 lbs

2007 – 5000 lbs2008 – 17000 lbs

2009 – 2500000 lbs

Method toMonitor

Measurement

Record

Activity 2*

Activity 1*

Activity 2*

Activity 1*

collect nutrient monitoring data of bay significant facilities for purpose of reporting to Bay Program.

for bay significant facilities, develop and initiate a process to establish action level nutrient permit limits

PENNVEST: Loans and grants for wastewater projects

VA DEQ/Ches Bay Program: Water Quality Improvement Fund Point Source Program - provides State cost-share for the design and installation of nutrient reduction technology at publicly owned treatment works .

Legand

GOALDesired ResultsThreatContribFactor

Strategy

Perf

orm

an

ce a

t m

an

y

levels

Target

Page 22: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Environmental Impacts

Environmental Outcomes

HRA Framework

RATS and Milestones

Desired ResultsGoals Topic Areas

Goal Type

CAP Framework

Threats

Contributing Factors

Activities

Strategies

Prioritized Strategy or Geo Area

Measures

Measures

FY Measures

Ecological Attributes

TargetCon

necti

ng

sou

rces a

nd

m

easu

res

Page 23: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Grantor or Funder

Grantor or Funder

Grantor or Funder

PlannedActivity

Planned Activity

Executed Activity

Chesapeake Registry

Grantor or Funder

Executed Activity

Parent Record Child Records

Tracking funding and planned/implemented activities

Target

Page 24: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Customer Services

Process Automation Services

Business Management Services

Digital Asset Services

Business Analytical Services

Back Office Services

Com

mon

Serv

ices

Cro

ss-C

utt

ing

Serv

ice A

reas

(i.e

., S

earc

h,

Secu

rity

)

ServiceTypes

Service Layers

Service Components

PerformanceMeasures

BusinessProcess

Access and Delivery Channels

CB Service Reference Model and Recommendations

Target

Page 25: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

1. Conduct segment-level analysis for a list of existing or potential services.

2. Identify SRM service domains applicable to CB Services.

3. Develop an enterprise service inventory or catalog using service domain and type.

4. Examine the use EPA’s Reusable Component Services (RCS) as an alternative to a CB-unique catalog.

5. Build services based upon business priorities.

6. Ascertain baseline architecture and sequence plan to support Service Oriented Architecture (SOA).

7. Consider a metadata management tool.

8. Obtain skill sets required for SOA.

9. Realize SOA through web services by promoting the NEIEN as a model of SOA best practices and conforming to OMB’s request to utilize the National Information Exchange Model (NIEM).

10. Maintain interest in information exchanges with other federal agencies.

11. Migrate from network node services to the Web.

12. Implement an Enterprise Service Bus.

13. Leverage standard federal government services.

14. Ensure services available are utilized.

CB Service Reference Model and Recommendations

Target

Page 26: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

FEA DRMFEA DRM

CB Data Reference Model and Recommendations

Target

Page 27: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

1. Understand the DRM structures.2. Document a community vocabulary for each LoB.3. Utilize the EPA Web Taxonomy.4. Model reference code sets in the Registry for Environmental

Applications and Data (READ).5. Establish data governance.6. Ensure conformance to the American National Standard Institute

and American Society for Quality Control.7. Commit to implement data best management practices such as:

A. Classify data sensitivity and adhere to the National Privacy Program; B. Develop data security guidelines; C. Define data stewardship roles; D. Continue to use the CB data standards process; E. Develop data cleansing rules; F. Minimize duplication; G. Implement data version control; H. Determine authoritative sources; I. Document business rules within rules-based engines; J. Define data exchange protocol; K. Define the process to determine metadata definitions and utilize a repository; L. Facilitate sharing by reuse, including mapping data to services; M. Build and maintain a data lifecycle process; and N. Continue to ensure backup and recovery. 

8. Participate in Open Government through data.gov website

CB Data Reference Model and Recommendations

Target

Page 28: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

ServiceFramework

ServicePlatforms

ServiceAccess and

Delivery

Service Platforms

Serv

ice Inte

rface

/

Inte

ropera

bili

ty

Security

Presentation / Interface

Business Logic

Data Management

Data Interchange

Component Architecture

Serv

ice T

ran

sport

Service Requirements

Delivery Channels

Access Channels - Mobile, Wireless, Web

- Internet, Intranet, Extranet

- Section 508, Privacy, Security

- HTTP, HTTPS, WAP, TCP/IP

- J2EE, Windows .NET

- SOAP, XML, UDDI, WSDL

CB Technology Reference Model and Recommendations

Target

Page 29: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

1. Identify standards and technologies within the service areas.

2. Implement server virtualization.3. Explore Server Hosted Virtual Desktop.4. Expand ChesapeakeStat beyond Phase I.5. Utilize the Audit Report on the Improved

Management Practices to Increase the Use of Exchange Network.

6. Implement the Non Point Source Best Management Practices (NPS BMP) schema by end of calendar year 2010.

7. Prioritize next exchange – WQX or ICIS PS and DMR8. Develop a CBP Technology Roadmap.

CB Technology Reference Model

and Recommendations

Target

Page 30: Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture Nancie L. Imler TreCom Systems.

Target Architecture

Target Description Technology Forecast Transformation Roadmap

Transition Architecture

Transition Plan IT Project Management EA Guide

Baseline ArchitectureBaseline Description of

Strategy and Performance Business Architecture Data Architecture Services and Technology

Management

Program Plan Guidance Communications Strategic Plan

What’s Next??Transition/Sequence Plan