Development of the
This presentation is the property of its rightful owner.
Sponsored Links
1 / 30

Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture PowerPoint PPT Presentation


  • 68 Views
  • Uploaded on
  • Presentation posted in: General

Development of the Chesapeake Bay Program’s Enterprise Architecture 2010 Baseline Configuration 2010 Target Architecture. Nancie L. Imler TreCom Systems Group, Inc. [email protected] CHALLENGES. Over 100 Partners within the CB Watershed

Download Presentation

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

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Development of theChesapeake Bay Program’s Enterprise Architecture2010 Baseline Configuration2010 Target Architecture

Nancie L. Imler

TreCom Systems Group, Inc.

[email protected]


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

CHALLENGES

Over 100 Partners within the CB Watershed

Partners execute the core-mission business functions

Culture of the Program has existed for twenty-five years

Data support is distributed across the Partnership

Jurisdictions have their own mandates

Bay Program has no authorization authority

Reporting is burdensome

Bay Program internal organization not hierarchical

Change and upheaval the last 3-4 years, including multiple audits and an executive order

Jurisdictional resources declining, both financial and human

Program has a high political profile

  • The Bay Program is an excellent candidate

  • For alignment TO the “fea” framework


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

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.


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Partners

Have Responsibilities

Strategic Layer

Performance Layer

Desired Results

Measures

Metrics

Goals

Strategies

Make Decisions

Perform Actions

Business Layers

Lines of Business

Business Sub-Functions

Business Processes

Technology Layer

Request Information

Hardware

Services Layer

Generate/Change Information

Data Input

Discovery

Display

Tools

Infrastructure

Data Layer

Have Attributes

Meta Data

Dictionary

Quality

Content

Baseline Configuration


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

  • Environmental Health Goals

  • Water Quality

  • Habitat and Lower Food Web

  • Fish and Shellfish

Manage Fisheries

Sustainably Goal

Strategic Layer

Restore and Protect

Habitat Goal

Restoration Goals

Protect and Restore

Water Quality Goal

Desired Results

Desired Results

Desired Results

Desired Results

Topic

Areas

Topic

Areas

Topic

Areas

Desired Results

Topic

Areas

Topic

Areas

Desired Results

Topic

Areas

Desired Results

Topic

Areas

Environmental Activities

Environmental Activities

Strategies

Environmental Activities

Environmental Activities

Environmental Activities

Strategies

Strategies

Strategies

Strategies

Strategies

Environmental Activities

Maintain Healthy

Watersheds Goal

Foster Stewardship

Goal

Enhance Partnering

Leadership, Management Goal

Baseline


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Performance Layer

Baseline


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Business Layer

Chesapeake Registry Data Call

Health and Restoration Data Call

Information Management

WIPs and TMDLs

Monitoring

Modeling

Science and Technical

Grants Management

Registration Activity Data Call

Baseline


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Services Layer

  • Services 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


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Data Layer

  • Guidelines 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


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Technology Layer

  • Technology 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


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

FEA Performance Reference Model

Partners

Have Responsibilities

Strategic Layer

Performance Layer

Desired Results

Measures

Metrics

Goals

Strategies

Make Decisions

Perform Actions

Business Layers

Lines of Business

Business Sub-Functions

Business Processes

Technology Layer

Request Information

FEA Business Reference Model

Hardware

Services Layer

Generate/Change Information

Data Input

Discovery

Display

Tools

FEA Service Component Reference Model

FEA Technical Reference Model

FEA Data Reference Model

Infrastructure

Data Layer

Have Attributes

Meta Data

Dictionary

Quality

Content

Target Architecture

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

FEA BRM Hierarchy

Business Area

SEGMENT (Line of Business)

Business Area

Segment (LoB)

S

Sub-Function 1

Sub-Function 2

Sub-Function

Process 1

Start

Processes

End

Process 2

Services

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


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

(108) Environmental Management

(109) General Science and

Information

LoB within the CBP’s Core-Mission Areas

(117) Natural Resources

CBP

(202) Knowledge Creation and

Management

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

(108) Environmental Management

(109) General Science and

Information

(207) Transfers States & Local Gov’ts

(305) Public Affairs

(401) Administrative Management

(404) Information & Tech Mgt

(301) Controls and Oversights

(205) Federal Financial Assistance

(303) Legislative Relations

(304) Planning and Budgeting

(117) Natural Resources

(202) Knowledge Creation and

Management

LoB within the CBP’s Business and Enterprise Services

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

RESOURCE

INFORMATION

PROCESSES

EVENT

OUTPUT

BUSINESS PROCESS

Business Process Models

for each LOB

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.

Target


The cbp s brm and recommendations

The CBP’s BRM and Recommendations

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

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

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

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

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

  • Prepare for climate change processes.

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

  • Identify authoritative data sources for all the CB processes.

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

  • 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


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Strategic Outcomes

Mission and Business Results

Services for Citizens

Support Delivery of Services

Management of Government Resources

Customer Results

Partner Benefits, Service Coverage

Timelines and Responsiveness

Service Quality and Accessibility

Processes and Activities

Financial, Productivity

Timeliness, Quality

Security and Privacy

Management and Innovation

Human Capital

Technology

Technology Costs

Quality Assurance

Information and Data

Reliability and Availability

Effectiveness

Other Fixed Assets

  • CB Performance Reference Model and Recommendations

  • Provide accessibility and understanding through terminology services.

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

  • Document the partnership’s Strategic Plan

  • Record gaps for indicators and metrics as identified by GITs

  • Conduct Strengths, Weaknesses, Opportunities and Threats (SWOT) analysis for each desired result in the Core Mission LoB.

  • Expand CB performance accountability to include metrics for the Customer Results Measurement Area.

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

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

  • Modify the Chesapeake Registry to serve as the performance accountability system by:

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

Distinguishing between planned and executed activities;

Recording metrics for the strategic and activity levels;

Creating activity transaction records linking Chesapeake Registry activity records with environmental data sets to assess effectiveness of strategy;

Including “outputs” in the data call for Partner environmental activities; and

Modifying Chesapeake Registry’s physical architecture to support metrics.

  • Designating strategic goals as health or restoration goals;

  • Adding desired results;

  • Adding strategies;

  • Linking environmental activities to one or more strategies;

  • Indicating priority strategies and priority geographical areas;

  • Categorizing strategy records as short-term or long-term;

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

  • CB Performance Reference Model and Recommendations

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

  • Performance at many levels

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

  • Connecting sources and measures

Environmental Impacts

HRA Framework

Environmental Outcomes

Activities

Measures

RATS and Milestones

Topic Areas

Goals

Measures

Strategies

Desired Results

CAP Framework

Goal Type

Threats

FY Measures

Prioritized Strategy or Geo Area

Contributing Factors

Ecological Attributes

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

Grantor or Funder

Grantor or Funder

Grantor or Funder

Grantor or Funder

Planned

Activity

Planned Activity

Executed Activity

Executed Activity

Chesapeake Registry

Parent Record

Child Records

Tracking funding and planned/implemented activities

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

CB Service Reference Model

and Recommendations

Access and Delivery Channels

Business

Process

Performance

Measures

Service

Types

Customer Services

Process Automation Services

Business Management Services

Cross-Cutting Service Areas

(i.e., Search, Security)

Common Services

Digital Asset Services

Service

Components

Business Analytical Services

Back Office Services

Service Layers

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

CB Service Reference Model

and Recommendations

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

  • Identify SRM service domains applicable to CB Services.

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

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

  • Build services based upon business priorities.

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

  • Consider a metadata management tool.

  • Obtain skill sets required for SOA.

  • 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).

  • Maintain interest in information exchanges with other federal agencies.

  • Migrate from network node services to the Web.

  • Implement an Enterprise Service Bus.

  • Leverage standard federal government services.

  • Ensure services available are utilized.

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

CB Data Reference Model

and Recommendations

Target


Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

CB Data Reference Model

and Recommendations

  • Understand the DRM structures.

  • Document a community vocabulary for each LoB.

  • Utilize the EPA Web Taxonomy.

  • Model reference code sets in the Registry for Environmental Applications and Data (READ).

  • Establish data governance.

  • Ensure conformance to the American National Standard Institute and American Society for Quality Control.

  • Commit to implement data best management practices such as:

    • Classify data sensitivity and adhere to the National Privacy Program;

    • Develop data security guidelines;

    • Define data stewardship roles;

    • Continue to use the CB data standards process;

    • Develop data cleansing rules;

    • Minimize duplication;

    • Implement data version control;

    • Determine authoritative sources;

    • Document business rules within rules-based engines;

    • Define data exchange protocol;

    • Define the process to determine metadata definitions and utilize a repository;

    • Facilitate sharing by reuse, including mapping data to services;

    • Build and maintain a data lifecycle process; and

    • Continue to ensure backup and recovery. 

  • Participate in Open Government through data.gov website

  • Target


    Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

    CB Technology Reference Model

    and Recommendations

    Service

    Access and Delivery

    - Mobile, Wireless, Web

    Access Channels

    - Internet, Intranet, Extranet

    Delivery Channels

    - Section 508, Privacy, Security

    Service Requirements

    - HTTP, HTTPS, WAP, TCP/IP

    Service

    Framework

    Component Architecture

    Security

    - SOAP, XML, UDDI, WSDL

    Service Interface /

    Interoperability

    Service Transport

    Presentation / Interface

    Business Logic

    Data Interchange

    Service

    Platforms

    Data Management

    - J2EE, Windows .NET

    Service Platforms

    Target


    Cb technology reference model and recommendations

    CB Technology Reference Model

    and Recommendations

    • Identify standards and technologies within the service areas.

    • Implement server virtualization.

    • Explore Server Hosted Virtual Desktop.

    • Expand ChesapeakeStat beyond Phase I.

    • Utilize the Audit Report on the Improved Management Practices to Increase the Use of Exchange Network.

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

    • Prioritize next exchange – WQX or ICIS PS and DMR

    • Develop a CBP Technology Roadmap.

    Target


    Development of the chesapeake bay program s enterprise architecture 2010 baseline configuration 2010 target architecture

    What’s Next??

    Transition/Sequence Plan


  • Login