The Power of Spatially Enabled Enterprise Addressing Systemsmedia.govtech.net/GOVTECH_WEBSITE/EVENTS...The Power of Spatially Enabled Enterprise Addressing Systems 3 Purpose Purpose

GTC Southwest 2008

William HollandCEO

GeoAnalytics, Inc.

The Power of Spatially Enabled Enterprise Addressing Systems


2

Presentation Overview AgendaPresentation Overview Agenda

• Introduction and Purpose

• Problem Statement and Concepts

• Solution Architecture

– Organization

– Process

– Data

– Technology

• Case Study: Orange County, Florida

• Questions and Answers / Discussion

• Introduction and Purpose

• Problem Statement and Concepts

• Solution Architecture

– Organization

– Process

– Data

– Technology

• Case Study: Orange County, Florida

• Questions and Answers / Discussion


3

Purpose Purpose

• Provide an understanding of the issues and opportunities drivingthe need for better street address management and use

• Discuss concepts and best practices for implementing an enterprise address system

• Illustrate one solution approach

• Provide an understanding of the issues and opportunities drivingthe need for better street address management and use

• Discuss concepts and best practices for implementing an enterprise address system

• Illustrate one solution approach


4

What is an Address?What is an Address?

• Mailing

– Recognized by US Postal Service for delivery of mail (Includes post office boxes)

• Physical/Situs

– Physical structure or location (such as parcel, building, meter, cell tower, pier)

• Geographic

– Is described by a set of real world coordinates

• Theoretical

– Address ranges that may exist along street centerlines or edges

• Mailing

– Recognized by US Postal Service for delivery of mail (Includes post office boxes)

• Physical/Situs

– Physical structure or location (such as parcel, building, meter, cell tower, pier)

• Geographic

– Is described by a set of real world coordinates

• Theoretical

– Address ranges that may exist along street centerlines or edges


5

Addresses in a Spatial Information ContextAddresses in a Spatial Information Context

PermitPermitor Offenseor Offense

FacilityFacilityTraceTrace

Public SafetyPublic SafetyIncidentIncident

Election DistrictElection DistrictLand UseLand Use Census UnitCensus Unit FloodplainFloodplain

ZoningZoning Jurisdiction Jurisdiction BndBnd Tax DistrictTax District

FacilityFacility ParcelParcel AddressAddress

Street CenterlineStreet CenterlinePLSSPLSS HydrographyHydrography Building FootprintBuilding Footprint

OrthophotographyOrthophotography PlanimetricPlanimetric TopographyTopography

Geodetic Control NetworkGeodetic Control Network

FrameworkLayers

SupplementalLayers

Base MapFeatures

BusinessEvents

1

Loca

tes

>

Has > 1

determines >*

*1

11

1

Has

><

Link

ed t

o *< Influences *

1

< Li

nked

to

**Linked to >1*

< Uses

*

Street Centerline

Address


6

Who Uses Address InformationWho Uses Address Information

• Planning

• Building

• Zoning

• Code Enforcement

• Public Works

• Engineering

• Assessment

• Planning

• Building

• Zoning

• Code Enforcement

• Public Works

• Engineering

• Assessment

• Economic Development

• Public Safety

• Fire Department

• Law Enforcement

• Human Services

• Public Health

• Voter Registration

• 311/Customer Care

• Economic Development

• Public Safety

• Fire Department

• Law Enforcement

• Human Services

• Public Health


• 311/Customer Care

• GIS

• IS \ MIS

• Corrections

• Administration

• Environmental Protection

• Taxation and other Billing Authorities

• Customer Information Systems

• GIS

• IS \ MIS

• Corrections

• Administration

• Environmental Protection

• Taxation and other Billing Authorities

• Customer Information Systems


7

How and Which address Type to Use?How and Which address Type to Use?

Public

• 9-1-1 Public Safety Response

• Tax Bills

• Rezoning Notifications

• Utility Billing/Services


• Property Appraisal/Assessment

• Emergency Management

Public

• 9-1-1 Public Safety Response

• Tax Bills

• Rezoning Notifications

• Utility Billing/Services


• Property Appraisal/Assessment

• Emergency Management

Commercial

• Customer Relationship Management

• Work Order/Asset Management

• Service Delivery

• Supply Chain and Route Optimization

• Market Planning and Analysis

• Site Location

• Financial Management

Commercial

• Customer Relationship Management

• Work Order/Asset Management

• Service Delivery

• Supply Chain and Route Optimization

• Market Planning and Analysis

• Site Location

• Financial Management

Parcel Address

Billing Address

Occupant Address

Owner Address

Facility Address


8

Address Management – The Traditional WayAddress Management – The Traditional Way


9

Why an Enterprise Addressing System?Why an Enterprise Addressing System?

The Problem StatementThe Problem Statement

Addressing Conventions and StandardsAddressing Conventions and Standards

• Primary versus alternate street names

• Abbreviations

• N:N address to parcel relationships

• Corner addresses

• Actual versus theoretical address ranges

• Defining location

• More….

• Primary versus alternate street names

• Abbreviations

• N:N address to parcel relationships

• Corner addresses

• Actual versus theoretical address ranges

• Defining location

• More….

206

Jones St.

Does this lot get a number?

Is this on Jones or Second?

and what is the number?

100 - 199 Hwy 206

100 - 199 Jones St.

Is the range 3500 - 3508 or 3500 - 3599?

Is Avenue abbreviated Ave or Av?

Do both parcels get the same PIN?

Is it Hwy or State Road or Highway, etc.?

Can each house get a different address on the same parcel?

Locally Known As McKay Road


11

Property level

Building level

Door level

Representation of Situs Address LocationRepresentation of Situs Address Location


12

Multiple Address GridsMultiple Address Grids


13

Islands of Address Data and Business FunctionalityIslands of Address Data and Business Functionality

Public Works

Assessment/Taxation

Planning & Zoning

Different Address Custodians – Supporting Differing Business Functions

911/Public Safety


14

Challenges and IssuesChallenges and Issues

• Lack of communication

• “Disconnected”, independent, duplicate address databases

• Repetition of work

• Undocumented maintenance processes

• Lack of communication

• “Disconnected”, independent, duplicate address databases

• Repetition of work

• Undocumented maintenance processes


15


• Use of hardcopy maps for address maintenance

• Parcel and address mapping not synchronized

• Quality control on address data creation

• Inter-departmental versus inter-jurisdictional coordination

• Currency of address data in different systems

• Use of hardcopy maps for address maintenance

• Parcel and address mapping not synchronized

• Quality control on address data creation

• Inter-departmental versus inter-jurisdictional coordination

• Currency of address data in different systems


16


• Liability

– Political – Bad decisions based on incorrect data

– Legal – Potential civil liability where there is injury to person or property

• Lack of addressing standards

– Street naming conflicts

– Non-standard abbreviations for street names

– Consistent enforcement

• Liability

– Political – Bad decisions based on incorrect data

– Legal – Potential civil liability where there is injury to person or property

• Lack of addressing standards

– Street naming conflicts

– Non-standard abbreviations for street names

– Consistent enforcement


17


• Emphasis on parcel specific addresses

– Does not recognize other types of addresses (ranges, construction trailer in ROW, phone booth, lift station, meter)

• No maintained relationship between address ranges and situs addresses

• Data not fit to related ranges and parcels

• In the end, there are many problems, many opportunities

• Emphasis on parcel specific addresses

– Does not recognize other types of addresses (ranges, construction trailer in ROW, phone booth, lift station, meter)

• No maintained relationship between address ranges and situs addresses

• Data not fit to related ranges and parcels

• In the end, there are many problems, many opportunities


18

A Solution ApproachA Solution Approach

Spatially Enabled Enterprise Address SystemSpatially Enabled Enterprise Address System


19

Solution To The ProblemSolution To The Problem

• An Enterprise Addressing System that is:

– Designed to address relevant departmental business interests

– Automated

– Standardized

– Transactionally maintained and current

– Coordinated

– Interoperable for internal and external uses

– Accessible to all systems and users

• An Enterprise Addressing System that is:

– Designed to address relevant departmental business interests

– Automated

– Standardized

– Transactionally maintained and current

– Coordinated

– Interoperable for internal and external uses

– Accessible to all systems and users


20

Address System ComponentsAddress System Components

ENTERPRISE

OrganizationOrganizationTechnologyTechnology

DataDataProcessProcess

911/D

ispat

ch

911/D

ispat

ch

Wor

k Ord

er M

gmt

Wor

k Ord

er M

gmt

Prope

rty A

ppra

isal

Prope

rty A

ppra

isal

ApplicationsApplications

System System ComponentsComponents

Prope

rty R

ezon

ing

Prope

rty R

ezon

ing


21

Enterprise Address System ConceptEnterprise Address System Concept

User Side

Business SystemsTax

Real Property

911/CAD

Sheriff/RMS

Permits & Inspection

Human Services

GIS

Web PublicationWeb Lookup

Reports

Maintenance Side

CommonMaintenance

Interface

Zoning

911

GIS

Replication

DB

Validation DB

Municipalities

Data TransferServices

Enterprise Enterprise Address DatabaseAddress Database


22

Enterprise Address System ConceptEnterprise Address System Concept

Business SystemsMAINTAIN

Address Data Maintenance

Workflow

Spatial Data Maintenance

Workflow

CITY OF MADISON

OTHERJURISDICTIONS

Enterprise Address System

DATABASE

Enterprise Data Repository

DATABASE

DCIMap

Geocoding Service

Address or Street Name

Lookup

MSAG

ArcIMS Map Services

Application Services

Tax/RPL

Land & Water Resources

Health & Social

Services

Records Management

System

9-1-1 Dispatch

Public

Pull

US

AG

E

Data Publication

Data Validation

Exposed Functionality

System InterfaceQC and Upload

Data Packaging

Maintenance System

SERVICES

USE

MAINTAIN

MANAGE

Street Intersection

Voter Registration

Emergency Management

Structure Data Maintenance

Workflow

External

Business Data

Parcel Data Maintenance

Workflow

Dane County, WI


23

Organizational Considerations and Requirements

Organizational Considerations and Requirements


24

Organizational ConsiderationsOrganizational Considerations

• Who are your custodians versus users of address data?

– Responsibilities

– Authorities

– Accountabilities

• Policies

– Addressing policies and procedures?

– Is there established addressing ordinance?

• Who are your custodians versus users of address data?

– Responsibilities

– Authorities

– Accountabilities

• Policies

– Addressing policies and procedures?

– Is there established addressing ordinance?


25

Organizational ConsiderationsOrganizational Considerations

• System governance?

• How do you coordinate processes and workflows?

• Is there an EAS champion at the top?

• Are the stakeholders committed?

• System governance?

• How do you coordinate processes and workflows?

• Is there an EAS champion at the top?

• Are the stakeholders committed?


26

Formal Address System GovernanceFormal Address System Governance

Forum

Palm BeachCounty

EPW

Public Safety

PZB

Municipalities

GIS - PAC

Project ManagementTeam (PMT)

ASIG

EAS Custodians &Users

Users

ISS / CWGIS

AddressingCoordination

Function

Community Resource

Coordination

ReportingRecommendations

StrategiesPolicyPrioritiesObjectivesResources

ObjectivesStandardsResources

PerformanceReporting,

Recommendations

PerformanceReporting,

Issues

Feedback

EAS GovernanceEntities

EAS TechnicalAdministration


27

Collaborative CustodianshipCollaborative Custodianship

Signage

Primary Participants


28

Collaborative CustodianshipCollaborative Custodianship

Enterprise Addressing(Core Custodial Components)

Municipalities

Intrado Corp.

Property Appraiser

Parcel Mapping

CAMA Database

MSAG1

4

PSAPs2

3

Public Works

Public Safety

Planning/Zoning

Clerk

5Legal Records (inc. Plats)

Secondary Participants


29

Process Considerations and Requirements

Process Considerations and Requirements


30

Process ConsiderationsProcess Considerations

• Has the organization documented and approved addressing workflows?

• What are the key address activities?

– Development

– Maintenance

– Production

– Business use

• Who are the primary (core) and secondary participants?

• What are the baseline and goal metrics?

• Has the organization documented and approved addressing workflows?

• What are the key address activities?

– Development

– Maintenance

– Production

– Business use

• Who are the primary (core) and secondary participants?

• What are the baseline and goal metrics?


31

Workflows Mapping – Plat AddressingWorkflows Mapping – Plat Addressing


32

Workflows Mapping – Single AddressingWorkflows Mapping – Single Addressing

Non-Parcel Features

• Meter

• Lift Station

• Light Pole


33

Data Considerations and RequirementsData Considerations and Requirements


34

Data ConsiderationsData Considerations

• What address types are required?

• How are different addressing forms and formats reconciled?

• What is the requisite data quality – consistency, resolution, and timeliness?

• What is the data relationship between the different addresses and the processes that use them?

• Do you have a data model to meet multiple business needs?

• What address types are required?

• How are different addressing forms and formats reconciled?

• What is the requisite data quality – consistency, resolution, and timeliness?

• What is the data relationship between the different addresses and the processes that use them?

• Do you have a data model to meet multiple business needs?


35


• Maintenance

– Data model standard?

• URISA,

• NENA,

• US National Grid, etc.

– All data within ArcSDE geodatabase?

– What degree of normalization?

– ArcSDE versioning?

– History – Tabular and Spatial? ArcSDE or custom?

• Maintenance

– Data model standard?

• URISA,

• NENA,

• US National Grid, etc.

– All data within ArcSDE geodatabase?

– What degree of normalization?

– ArcSDE versioning?

– History – Tabular and Spatial? ArcSDE or custom?


36


• Publication

– Consumer user needs?

– Business analytics?

– Performance metrics?

– Transaction – Database or custom?

• Publication

– Consumer user needs?

– Business analytics?

– Performance metrics?

– Transaction – Database or custom?


37

SiteSiteAddressAddress

Primary Primary Street NameStreet Name

Alternate Alternate Street NameStreet Name

Theoretical Theoretical RangeRange

Street Street CenterlineCenterline

Zip Code Zip Code BoundaryBoundary

Place Place NamesNames

AddressAddressTypesTypes

X,Y LocationX,Y Location

ParcelParcel

BuildingBuilding

CityCityNameName

City City BoundaryBoundary

Zip CodeZip Code

MSAG MSAG RangesRanges

Address Data Model ComponentsAddress Data Model Components


38

Resources for Standards and GuidelinesResources for Standards and Guidelines

• United States Postal Service (USPS)

– (http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf)

• US Census Bureau (www.census.gov)

• National Emergency Number Association (NENA) (www.nena.org)

• URISA (www.urisa.org)

• Federal Geographic Data Committee

– (FGDC) (www.fgdc.gov)

• United States Postal Service (USPS)

– (http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf)

• US Census Bureau (www.census.gov)

• National Emergency Number Association (NENA) (www.nena.org)

• URISA (www.urisa.org)

• Federal Geographic Data Committee

– (FGDC) (www.fgdc.gov)


39

Technology Considerations and Requirements

Technology Considerations and Requirements


40

Technology ConsiderationsTechnology Considerations

• Are your addressing systems:

– Interoperable with other business information systems?

– Coordinated to minimize data discrepancies

– Accessible to remote offices, and governmental and private sector partners?

– Compliant with existing IS standards?

• Is there a business need for web-based tools for enhanced access?

• Are your addressing systems:

– Interoperable with other business information systems?

– Coordinated to minimize data discrepancies

– Accessible to remote offices, and governmental and private sector partners?

– Compliant with existing IS standards?

• Is there a business need for web-based tools for enhanced access?


41


• Maintenance Environment?

• Publication Environment?

• Technology Choices

– ArcGIS Desktop ArcMap Extension?

– ArcGIS Server?

– Integrated Reporting?

– Reporting Tool?

• Maintenance Environment?

• Publication Environment?

• Technology Choices

– ArcGIS Desktop ArcMap Extension?

– ArcGIS Server?

– Integrated Reporting?

– Reporting Tool?


42


Monitor &Monitor &ManageManage

Profile &Profile &QuantifyQuantify

Cleanse,Cleanse,Validate,Validate,ImproveImprove

Integrate & Integrate & OrganizeOrganize

Enrich & Enrich & Value AddValue Add

EnterpriseEnterpriseDataData

Master Data Management

Adapted from DataFlux®


43

EAS Strategy Case StudyEAS Strategy Case Study

Orange County, FloridaOrange County, Florida


44

Orange County ALADIN AddressingOrange County ALADIN Addressing

• Key Requirements

– Multi-Departmental custodians (911, Zoning, GIS; ~30 individuals)

– Fees calculated for addresses and some new street names, and grouped by business process

– Data history; transactional history by business process

– Legacy situs and centerline migration, and cleansing

– Three (3) levels of Sub-Address (building, level, unit)


– Multi-Departmental custodians (911, Zoning, GIS; ~30 individuals)

– Fees calculated for addresses and some new street names, and grouped by business process

– Data history; transactional history by business process

– Legacy situs and centerline migration, and cleansing

– Three (3) levels of Sub-Address (building, level, unit)


45



– Street name reservation; enforce unique street names

– Map-centric workflow; spatially derive address, zipcode, jurisdiction and mailing city from situs point location.

– Pre-Addressing of plats and commercial site plans

– Parcel Number not required; derive from map when available


– Street name reservation; enforce unique street names

– Map-centric workflow; spatially derive address, zipcode, jurisdiction and mailing city from situs point location.

– Pre-Addressing of plats and commercial site plans

– Parcel Number not required; derive from map when available


46



– Address type and subtype attributes

– Real-time access to new addresses for Building and Utilities permitting

– Address validation web service

– Automated ETL processes to shared repository

– Significant business intelligence and report requirements –requiring SAS technology integration


– Address type and subtype attributes

– Real-time access to new addresses for Building and Utilities permitting

– Address validation web service

– Automated ETL processes to shared repository

– Significant business intelligence and report requirements –requiring SAS technology integration


47

Orange County, FL Conceptual EAS ArchitectureOrange County, FL Conceptual EAS Architecture


48

Orange County, FL Process ArchitectureOrange County, FL Process Architecture


49

Orange County, FL Process WorkflowOrange County, FL Process Workflow


50

Database ComponentsDatabase Components


51

Mailing Tables

Parcel Table

Building Tables

Range Table

Street Name Tables

Address Tables

EAS Spatial Tables

Address_No

PK Address_ID LONG

Address_No TEXT(10)Alpha_Ext TEXT(4)

FK1 Range_ID LONGFK2 Situs_Geometry_ID LONGFK3 ZipCode_ID LONGFK4 Jurisdiction_ID LONG

Postal_Area_ID LONGFK5 State_ID LONGFK6 Street_Name_ID LONGFK7 Country_ID LONG

Mailing_Flag CHAR(3)Status TEXT(10)Date_Entered CHAR(10)Date_Changed CHAR(10)

Street_Name

PK Street_Name_ID LONG

Street_Name TEXT(32)FK2 Prefix_ID LONGFK1 Suffix_ID LONGFK3 Pre_Dir_ID CHAR(10)

Status TEXT(10)Street_Type CHAR(256)Date_Entered DATETIMEDate_Changed DATETIME

Suffix

PK Suffix_ID LONG

Suffix TEXT(10)

Prefix

PK Prefix_ID LONG

Prefix TEXT(10)

Alias_Name

PK Alias_Name_ID LONG

Alias_Name TEXT(25)FK1 Prefix_ID LONGFK2 Suffix_ID LONGFK3 Pre_Dir_ID CHAR(10)

Range

PK Range_ID LONG

Theoretical_From TEXT(10)Theoretical_To TEXT(10)Actual_From TEXT(10)Actual_To TEXT(10)Odd_Even CHAR(10)

FK1 Range_Geometry_ID LONG

PID_X_Address

PK PID_Address LONG

FK1 Address_ID LONGFK2 Parcel_System_ID LONG

Parcel_Number

PK P_ID LONG

Parcel_ID TEXT(254)Date_Entered DATETIMEDate_Changed DATETIME

Building

PK Building_ID LONG

Building_Identifier TEXT(10)Building_Description TEXT(256)Status TEXT(10)Date_Entered DATETIMEDate_Changed DATETIMEDate_Retired CHAR(10)

Range_X_Alias

PK Range_Alias_ID LONG

FK2 Range_ID LONGFK1 Alias_Name_ID LONG

Situs_Geometry

PK Situs_Geometry_ID LONG

Situs_Geometry VARBINARY(0)

Range_Geometry

PK Range_Geometry_ID LONG

Range_Geometry VARBINARY(0)

Postal_Area_Geometry

PK Postal_Area_Geom_ID LONG

Area_Name TEXT(25)Area_Geometry VARBINARY(0)

Jurisdiction_Geometry

PK Jurisdiction_Geom_ID LONG

Jurisdiction_ID LONGJurisdiction_Name TEXT(25)Jurisdiction_Geometry VARBINARY(0)

Zip_5_Geometry

PK Zip_5_Geom_ID LONG

Zip_5 TEXT(5)Zip_5_Geometry VARBINARY(0)

ZipCode

PK ZipCode_ID LONG

ZipCode TEXT(5)ZipCode_Ext TEXT(4)

Jurisdiction

PK Jurisdiction_ID LONG

Jurisdiction_Name TEXT(25)

Bldg_Unit

PK Unit_ID LONG

FK1 Building_ID LONGUnit_Identifier TEXT(256)

FK2 Unit_Type_ID LONGBldg_Seq LONGLocation_Description TEXT(256)Status TEXT(10)

Bldg_X_Add

PK Bldg_Add_ID LONG

FK1 Building_ID LONGFK2 Address_ID LONG

Direction

PK Direction_ID LONG

Direction TEXT(10)Dir_Abbrev TEXT(10)

State

PK State_ID LONG

State_Name TEXT(25)State_Abbrev TEXT(2)

Country

PK Country_ID LONG

Country TEXT(25)

Building_Footprint

PK Building_Footprint_ID LONG

Building_ID LONGBuilding_Geometry VARBINARY(0)

Unit_Type

PK Unit_Type_ID LONG

Unit_Type TEXT(10)

Other Spatial Tables (Relate by location)

Bus_System_X_Add

PK System_X_Add_ID LONG

FK1 Address_ID LONGSource_ID LONGSource_Name TEXT(256)Bus_System_Name_ID TEXT(256)

Bus_System_Name

PK Bus_System_Name_ID CHAR(10)

FK1 System_X_Add_ID LONGBus_System_Name CHAR(10)

Comprehensive EAS Data ModelComprehensive EAS Data Model


52Situs AddressSitus Address

Street NameStreet Name

EAS SpatialEAS SpatialAddress RangeAddress Range

Core Address TablesCore Address Tables


53

BuildingsBuildings

ParcelsParcels

Parcel and Building RelationshipsParcel and Building Relationships


54

LocationLocation--based Spatial Relationshipsbased Spatial Relationships

Additional FeaturesAdditional Features


55

Additional FeaturesAdditional Features

Mailing Address SupportMailing Address Support


56

Orange County, FL EAS Input ArchitectureOrange County, FL EAS Input Architecture

System Inputs


57

Orange County, FL EAS OutputArchitectureOrange County, FL EAS OutputArchitecture

ArcSDE

SASETL Server

Metadata ServerBI Server

Database Level Replication(Support for Real Time Needs)

Web Portal

Custom Reporting$

MICROSOFT

CORPORATION

Custom Reports$

MICROSOFT

CORPORATION

Address Validation Service

INFOMAP

SAS MS Office Integration

Information Map StudioOLAP Cube Studio

ETL Studio

SASWeb Report Studio;Information Delivery PortalWeb OLAP Viewer

ETLParcel Featuresand CAMA Data

ETLOther GIS

Layers

ETLSpatial and

TabularAddress Data

Spatial and Tabular Data

ArcGIS DesktopSAS ESRI Integration

Other BusinessSystems

DATA TIER

APPLICATION TIER

PRESENTATION TIER

DESKTOP

INTRANET INTERNET

Address Validation GUI

System Outputs


58

Orange County Enterprise AddressingOrange County Enterprise Addressing

ArcGIS Server Based Maintenance ApplicationArcGIS Server Based Maintenance Application


59


60


61


62


63


64


65


66


67


68


69


70


71


72


73


74


75


76


77


78


79


80


81


82


83

ImplementationImplementation


84

Partnerships Partnerships and and

CollaborationCollaboration

Managing Managing ChangeChange

Achieving Achieving

SustainabilitySustainabilityGIS and IT GIS and IT

ConvergenceConvergence

Vision, Vision, Strategy, and Strategy, and

ExecutionExecution

Challenges to EAS ImplementationChallenges to EAS Implementation


85

Strategic OutcomesStrategic Outcomes

Adapted From: The Strategy Focused Organization, Kaplan & Norton, 2001

MissionMission Business Case

Core ValuesCore Values Principles

VisionVision Policy Objective

StrategyStrategyGame planGame plan Policy Mechanisms

Gauging ResultsGauging ResultsImplementation and focusImplementation and focus Metrics and Measures of Success

TacticsTacticsWhat we need to doWhat we need to do Policy Instruments

PersonalPersonal ObjectivesObjectivesWhat I need to doWhat I need to do Individual Objectives and Actions

Delighted Customers

Effective Processes

Motivated Workforce

Implementing an EAS - StrategyImplementing an EAS - Strategy


86

Situation AssessmentSituation AssessmentSituation Assessment

Conceptual DesignConceptual DesignConceptual Design

Logical DesignLogical DesignLogical Design

Physical DesignPhysical DesignPhysical Design

ConstructionConstructionConstruction

ProductionProductionProduction

TransitionTransitionTransition

MethodologyMethodologyMethodology

ProcessProcess

ApplicationsApplications

OrganizationOrganization

TechnologyTechnology

DataData

System Components

System System ComponentsComponents

Implementing an EAS – Methodology 1Implementing an EAS – Methodology 1


87

Implementing an EAS – Methodology 2Implementing an EAS – Methodology 2

Rational Unified Process™


88

Challenges to EAS ImplementationChallenges to EAS Implementation

• Managing Change

– From Status Quo

– In Both Process and Systems

– In New Staff Skills

• Database Development and Administration

• Getting Participation and Support

– All Stakeholders

– External Partners (Development Community)

• Incremental Solutions

– Help Producers and then Users?

• Managing Change

– From Status Quo

– In Both Process and Systems

– In New Staff Skills

• Database Development and Administration

• Getting Participation and Support

– All Stakeholders

– External Partners (Development Community)

• Incremental Solutions

– Help Producers and then Users?


89

DiscussionDiscussion

William HollandCEO

GeoAnalytics

This Presentation Will Be Available At:

http://geoanalytics.com/library/


Documents

The Power of Spatially Enabled Enterprise Addressing Systemsmedia.govtech.net/GOVTECH_WEBSITE/EVENTS...The Power of Spatially Enabled Enterprise Addressing Systems 3 Purpose Purpose