District of columbia citywide enterprise architecture
This presentation is the property of its rightful owner.
Sponsored Links
1 / 17

District of Columbia Citywide Enterprise Architecture PowerPoint PPT Presentation


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

District of Columbia Citywide Enterprise Architecture . Tom Mowbray, Keane Federal Systems DC OCTO Enterprise Architect April 13, 2005 [email protected] [email protected] (202)727-9580. The EA Challenge Key EA Principles EA Framework To-Be EA Process As-Is EA Process EA Notation

Download Presentation

District of Columbia Citywide Enterprise 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


District of columbia citywide enterprise architecture

District of ColumbiaCitywide Enterprise Architecture

Tom Mowbray, Keane Federal Systems

DC OCTO Enterprise Architect

April 13, 2005

[email protected]

[email protected]

(202)727-9580


Outline

The EA Challenge

Key EA Principles

EA Framework

To-Be EA Process

As-Is EA Process

EA Notation

EA Views

EA Governance

Lessons Learned

Outline

ACRONYMS

ARB ::= Architecture Review Board

BPR ::= Business Process Engineering

CONOPS ::= Concept of Operations

EA ::= Enterprise Architecture

OCTO ::= Office of the CTO

SMP ::= Services Modernization Program

  • SERVICES MODERNIZATION PROGRAMS

  • Administrative (ASMP)

  • Customer (CSMP)

  • Education (EdSMP)

  • Enforcement (ESMP)

  • Financial (FSMP)

  • Human (HSMP)

  • Motorist (MSMP)

  • Property (PSMP)

  • Transportation (TSMP)


The district s ea challenge

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

Agency Systems

The District’s EA Challenge

9 Multi-Agency Services Modernization Programs (SMP)

ASMP

CSMP

ESMP

EdSMP

FSMP

HSMP

MSMP

PSMP

TSMP

Undocumented, Isolated Proejects

68 Agencies, Need Transparency

380+ Legacy Systems

Strong Disincentives to Share, Need for Data Integrity


Key ea principles octo s architecture philosophy is focused on results

RESULTS DRIVEN – Tactically Implementation Oriented

Architecture results should be simple, practical, feasible, and useful

VISUAL

Priority for visual architecture models

SELF-CONTAINED

Docs must be self-explanatory and standalone

BEST PRACTICES

Use best practices of BPR and EA

FACT-BASED and ACTIONABLE

Generate rigorously engineered information that is actionable

LONG TERM VIEW WITH SHORT TERM BENEFITS

Define target architecture and cost benefits

Show long term architectural fit; Conduct Benefits Realization

Key EA PrinciplesOCTO’s Architecture Philosophy is Focused on Results

Overall: Information Transparency Breeds Behavioral Correction


Dc enterprise architecture framework dc eaf

DC Enterprise Architecture Framework (DC-EAF)

SMP Concepts of Operations

To-Be


To be ea process

To-Be EA Process

Understand the Problem,

Define Business Solution

Devise Target Architectures,

Craft Transformation Plans,

Initiate Cost-Benefits Realization


Process for to be concept of operations

Process for “To Be” Concept of Operations

Process Improvement Planning

Strategic Implementation Planning

Project:

Root Causes

& Best Practices

(i.e. Business Conops)

Approx 2 MBA X 4-6 weeks

Natural Role for Team of MBA/Business Analysts

Identifies

Scope of

Project: Business Operating Model

(i.e. Program Planning)

Approx 2 MBA/Agency X 12-14 Weeks

Business

Solution

Drives

Business

Priorities

Determine

Solution

Direction

Natural Role for BPR Group

Technical

Solution

Enables

SubProject: IT Architecture Envisioning

Approx 1 Arch X 8-12 Weeks

Natural Role for Enterprise Architecture Team

  • District Experiences with “To Be” Process: ASMP, CSMP, ESMP, HSMP

  • Cost of Concept of Operations is approx ½ Percent of Development Cost

  • Resulting Business Case: Cost-Benefits of Exceed Development Cost with Strong Stakeholder Buy-In/Ownership

Best Practices Combination of BPR and EA


To be conops 3x5 matrix

“To Be” CONOPS 3X5 Matrix

EXECUTIVE PERSPECTIVE

BUSINESS/PROGRAM PERSPECTIVE

GENERAL PERSPECTIVE


Arb milestone 1 conops checklist

ARB Milestone 1: CONOPS Checklist

CV-1

CV-2

CV-3

CV-4

CV-5

CV-6

CV-7

CV-8

CV-9

CV-10

CV-11

We have many real examples of these deliverables


District of columbia citywide enterprise architecture

“As Is” Enterprise Architecture Process

6/4/04

6/18/04

  • Information

  • Architecture

  • Day

  • X-Brief

  • X-Linkage

  • Business

  • Architecture

  • Day

  • X-Brief

  • X-Linkage

One-on-One

Information

Modeling

Sessions

One-on-One

Business Arch

Modeling

Sessions

EA FY05

Kickoff

Meeting

7/2/04

7/16/04

  • Application

  • Architecture

  • Day

  • X-Brief

  • X-Linkage

One-on-One

Application Arch

Modeling

Sessions

  • Infrastructure

  • Architecture

  • Day

  • X-Brief

  • X-Linkage

One-on-One

Infrastructure

Modeling

Sessions

8/6/04

  • Next Year…

  • EA FY06 Kickoff (October 2005)

  • X-Brief FY05 “As Built” Models

  • FY05 Lessons Learned

Review, Publicize, Finalize


Ea notation conventions

MODELING PRINCIPLES

Simple

Pragmatic

Useful

Self Explanatory

In Laymans’ Terms

Priority Driven

Shows Relationships

Readable Constraints

Visio 2000 (5 Facet UML)

Holistic View of SMP’s and Common Services

EA Notation Conventions

Example Information Object

General Incident Information

Bold Object Name

(Abbreviation)

General incident information is common header data on many MPDC forms, including: system generated case numbers, party identification, and incident locations.

Current View

Object Definition

(free text)

BV-ESMP MPDC Event

Business Processes

AV-ESMP Records Management System

Application Modules

NV-ESMP RMS Production DB Server

NV-ESMP RMS Backup DB Server

Infrastructure

Components

Always show UML facets in same order Current View then Business (BV), Information (IV), Appliacation (AV), Infrastructure (NV)


District of columbia citywide enterprise architecture

Sample

Enterprise

Information

Architecture

Model

STRICTLY PRELIMINARY DRAFT 6/1/2004


Enterprise architecture posters

Summary Business Enterprise Architecture

Business Processes and Relationships

Summary Information Enterprise Architecture

Information Categories and Relationships

Summary Application Enterprise Architecture

Application components/modules and relationships

Summary Infrastructure Enterprise Architecture

Server and network components

Installed software packages

Enterprise Architecture Posters

Focus is on SMPs and components they depend upon


Architecture trace ability to business goals

Architecture Trace-ability to Business Goals

Mayors Citywide Strategic Goals

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

MPDC Scorecard Goals

OCTO Scorecard Goals

CFSA Scorecard Goals

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

Goal

ASMP

HSMP

ESMP


Sample infrastructure architecture view

MODEL ELEMENTS

Server Systems

LAN/WAN Network Components

Storage Servers

Network Connections

LEVEL OF DETAIL (for Citywide EA)

All Production SMP-related Server Boxes

All Production SMP-related Network Boxes

Major Production LAN/WAN components used by (or interfaced to) SMP’s

Installed Software Packages and Versions

Sample Infrastructure Architecture View

SAMPLE MODEL

SAMPLE MODEL

The actual EA models are PROTECTED CRITICAL INFRASTRUCTURE INFORMATION (PCII)


Architecture review board process assuring it quality through milestone peer reviews

CONOPS

Study

Go / No-Go

Selection Phase

Development Phase

Deploy

Operations Phase

Architecture Review Board ProcessAssuring IT Quality Through Milestone Peer Reviews

Milestone 1

System

Concept

Readiness

Validate

Architecture

RFP

Milestone 2

Construction

Readiness

RFP

RFP

Milestone 3

Operational

Readiness

RFP

Verify Design

with Architecture

Design

Reviews

Tactical Arch.

Changes

Verify Implementation

with Architecture

RFP

Critical Architecture Decisions

Tactical Arch.

Changes

Tactical Arch.

Changes

Important Architecture Decisions

IT Systems Planning and Development Phase Advisory Services


Conclusions lessons learned

Key purpose of EA: Launch Migration to SOA Common Services

Successful in Documenting and Prioritizing the Services through the EA

Sparked Creation of New IT Business Unit for Common Services & Oversight

Information Transparency Breeds Corrective Behavior

Architecture requirements are becoming self-reinforcing through EA experience – Infrastructure Resilience, Use of Common Services Licenses,…

Governance is Communications

ARB Reviews Promote Many to Many Communications/Sharing of Expertise

Discover new enterprise licenses / common service opportunities most every time ARB meets

Plan for the consequences of architecture success

New investment for platforms, operations, training, support for new enterprise license “Common Service” technologies

Excellent development and operations phase management is required to realize architecture plans

There are 25 concurrent EA-related initiatives in progress

Conclusions: Lessons Learned


  • Login