Our People Government for the 21st Century Doing Business Differently Infrastructure eGovernment:...

Our People

Government for the 21st Century

Doing Business Differently

Infrastructure

eGovernment:Enabling Electronic Service Delivery

with XML and Common Data Elements

Presented to IRMAC, Jan. 16, 2002

Dave Wallace & Alana Boltwood

Office of the Corporate Chief Strategist

Management Board Secretariat

Government of Ontario

2

Our People



Infrastructure

Agenda

• The Challenges of E-Government• Why XML?• Ontario’s Approach to Derive XML

Standards• Common Data Elements• Putting It All Together• Next Steps

3

Our People



Infrastructure

Strategic Direction: E-Government

• In March 2000, in approving its Digital Economy Strategy, the Ontario Government approved electronic government as a priority

• The plan is to demonstrate leadership by example in electronic government and more specifically, electronic service delivery

4

Our People



Infrastructure

Electronic Service Delivery (ESD)

Providing services electronically to our clients

Common I&IT Infrastructure

Underlying technology to support both enterprise-wide and business specific applications

Integrated Service Delivery (ISD)

Providing Ontario services over the counter and electronically to individuals and businesses

Sectoral ReformUsing I&IT to drive and enable

sectoral reform

Enterprise Resource (HR and Financial) Systems and e-commerce processes

Corporate Systems and Enablers

Citizen Engagement

Enabling two-way publicinteraction

The E-Government Context

5

Our People



Infrastructure

Strategic Vision and 2003 Target forElectronic Service Delivery (ESD)

VISION• Improve service quality to Ontario’s people and

businesses by implementing client-focused, integrated, accessible and cost-effective electronic services by the OPS

2003 TARGET• Increase Ontarians’ satisfaction with government

services by becoming a world leader in delivering services on-line (for purposes of ESD target, on-line includes all electronic channels)

6

Our People



Infrastructure

Implications in Ontario

• We know we have much to do to provide leadership for Ontario’s success in the global Digital Economy– E-Business (e.g. removal of barriers/supportive

environment)– E-Government (e.g. sectoral transformation,

ESD, internal admin., digital democracy)– individual, business, sector, institutional

readiness– high technology sectors/R&D– information infrastructure

7

Our People



Infrastructure

All levels of government are working hard on using I&IT to improve the services they provide to their clients

We all must work together to that common goal

We also need to share experiences and learn from each other about best practices in e-government and ESD

Bottom-line….

8

Our People



Infrastructure

But what does this mean to Information and Information Technology (I&IT)?

9

Our People



Infrastructure

Going “E” By 2003 means...• Business transformation projects must be

delivered

• Time to Market is critical

• Collaboration and commitment are key success factors

• Quality, effective results are essential to meet the government’s vision for 2003...

10

Our People



Infrastructure

But Not With Just Technology• E-Government and ESD cannot succeed

without a “common language”

• Ontario’s strategy is dependent on Information Management (IM) as the basis of interchanges with our clients - the public, other governments and with private industry

• These interchanges will based on eXtensible Markup Language (XML)

11

Our People



Infrastructure

XML - A Definition• XML is a set of rules, guidelines and

conventions for designing text formats for such data, in a way that produces files that are easy to generate and read (by a computer)

• XML text formats are unambiguous, avoiding common pitfalls such as lack of extensibility, lack of support for internationalization/localization, and platform-dependency

12

Our People



Infrastructure

Leading Edge IM is Counting on XML

• W3C XML schema Standards (http://www.w3.org/XML/)

• US, UK and EU have developed or are developing IM based interoperability frameworks for E-Government

• Private Sector Standards nearing maturing for:– Business to Consumers (Customer Profile, name &

addressing, etc…)

– Business to Businesss (Invoices, Purchase Orders, Contracts, etc…)

• Next generation interoperability standards emerging; for example, ebxml is setting standard for seamless electronic business through XML

13

Our People



Infrastructure

But Why XML?• XML provides the “language” for the Common “I” in

Common Information & Information Technology (I&IT)

• Setting standards for common data elements and common meta data now will:– enable enterprise wide integration and navigation in the future– Prevent to time consuming and costly efforts of retrofitting

existing applications to comply to corporate standards– Enable both Microsoft and JAVA based components to

interoperate and thereby reduce technology risks– Lay the foundation for future service delivery and program

specific extensions to the provinces IM framework

• XML is ready for prime time

14

Our People



Infrastructure

Why XML (continued)• The province has several lines of business. Health, Education,

Transportation…• Each of these “communities of interest” has significant XML

standards development initiatives underway. • If the province is to:

– Retain the capacity to have an enterprise view of its information and transaction offerings,

– Establish a scalable foundation upon which individual ministries can “build out” the standards to meet there specific needs,

– Implement a standards based interface between programs & “Service Providers”

• The Province must:– Set a bare minimum set of corporate content and context management

standards– Set standards for common data elements that are used across the OPS– Set standards for inter-system messaging – Move beyond standardized elements to standardized documents

15

Our People



Infrastructure

Benefits of XML• Short Term

– Define data messaging standards for the province’s Common I & IT gateway

• Medium Term– Provide an standards based means for capturing, classifying

and transforming data– Establish application independent data– Establish device and platform independent solutions– Provide a standards based transformation engine for re-

engineering

• Long Term– Enable ‘plug and play’ where government transactions and

information delivery can be dynamically assembled to meet the context of the client

– Provide Customers choice in how, when and where they interact with government

16

Our People



Infrastructure

Basic Assumptions for Using XML• Transformations from standardized messaging

language to program-ready data is the responsibility of the program owner

• XML must support multiple service providers

• XML solution must delivers complete transactions

• Online presentation is not part of the transaction definition schema

• XML Services must comply with W3C

17

Our People



Infrastructure

Messaging Mark-up• Govtalk in the UK and EBXML in the private sector are

establishing interoperability frameworks for the B2B and public sector environment by establishing transformation solutions between existing standards and hoping that common data standards will emerge through the development of on-line service delivery applications

• These interoperability efforts are enabled by moving to one level of abstraction in the document type definitions (establishing generic schemas) and conducting XSLT transformations between systems

• Ontario has different approach - using Common Data Elements (CDE) across the systems of the provincial government, which will allow common data to be re-purposed across transactions as well as profile driven proactive information and transactions services

18

Our People



Infrastructure

IM is Critical to Meeting the Challenges of ESD

• Data and information are seen as corporate assets in the Ontario Government, with custodianship in program areas

• Ontario’s Enterprise Architecture has standardized definitions of common data elements (CDE) which have been developed to foster sharing and re-use when appropriate

• The XML schema of Common Data Elements is key to Ontario’s ESD strategy

19

Our People



Infrastructure

Integrated Information Project

• The Integrated Information Project will help the government of Ontario manage the information it gathers efficiently and in compliance with privacy legislation. It will also enhance information sharing across government which will improve decision-making and contribute to improved services.

20

Our People



Infrastructure

Integrated Information Project: Common Data Elements Model

• Identify data that is “common” across ministries

• Develop a conceptual framework for these elements

• Establish standard definitions• Create template for system design• Build XML schemas based on CDEModel

21

Our People



Infrastructure

Benefits of CDEModel

Save time &money in system

life cycle, andimprove service

delivery

Generic andstandard data

model

People use samemeaning of words

Peoplecommunicate well

Reuseableapplication

components

Reuseable datamodel

components

Easy integrationof systems

Data model forCommon Data

ElementsRepository

Singleauthoritativesource for

common data

22

Our People



Infrastructure

Approach for Developing Common Data Elements

• A government oriented contextual enterprise information model has been created that has:

a generic conceptual data model that is applicable to all government computer applications;

subject areas that are common;a formal information taxonomy;core common data elements.

23

Our People



Infrastructure

Government Information Context Model

Stewardship

Economic SocialResponsibility

Context Information Model

Infrastructure, Resources,and Environmental Well-

being

Vibrant Communities

Learning, Wellness, andSelf-Reliance

Safe and Just SocialEnvironment

Competitive Ontario

InformationGroupings

Responsible Government

Business Sectors

All the information and data used by a government can be classified into one of three context areas and then further

classified into specific information groupings.

24

Our People



Infrastructure

CoreBusinesses

(C 6-W hy)

Rules(C 6-W hy)

prov idef ramew ork

f or

Goals andStrategies(C 6-W hy)

def inenature of

Programs(C 2-How)

def ineterms of

f und

Services(C 2-How)

addres s

Clients(C 4-W ho)

Partners(C 4-W ho)

Stakeholders(C 4-W ho)

Locations(C 3-W here )

GOOrganiz ations

(C 4-W ho)

res pon-s ib le f or

admin is ter

Resources(C 1-W hat)

f ound at

prov idedat

c ons tra indeliv ery o f

BusinessCycles

(C 5-W hen)

BusinessEvents

(C 5-W hen)

determinetiming of

tr iggerdeliv ery o f

prov idedby

impac tNeeds

(C 6-W hy)

ex per ienc edby

Individuals(C 4-W ho)

Organiz ations(C 4-W ho)

are inv o lv edas

deliv ers erv ic es as

rec eiv es erv ic es as

From Context to Conceptual Model

25

Our People



Infrastructure

Identification of Common Elements

CoreBusinesses

(C6-Why)

Rules(C6-Why)

provideframework

for

Goals andStrategies(C6-Why)

definenature of

Programs(C2-How)

defineterms of

fund

Services(C2-How)

address

Clients(C4-Who)

Partners(C4-Who)

Stakeholders(C4-Who)

Locations(C3-Where)

GOOrganizations

(C4-Who)

respon-sible for

administer

Resources(C1-What)

found at

providedat

constraindelivery of

BusinessCycles

(C5-When)

BusinessEvents

(C5-When)

determinetiming of

triggerdelivery of

providedby

impactNeeds

(C6-Why)

experiencedby

Individuals(C4-Who)

Organizations(C4-Who)

are involvedas

deliverservices as

receiveservices as

A conceptual data model defines the high level

entities and the type of relationships between

them. Any public sector computer application can use this model to begin

design and development. Entities hi-lighted in red are common and thus

form the basis for defining common data elements.

26

Our People



Infrastructure

Logical Data Model of Common Data Elements

ROLE TYPE# ROLE TYPE* ROLE NAME* ROLE DESC

INFORMAL GROUP MEMBERSHIP# MEMBERSHIP START DATEo MEMBERSHIP END DATE

PARTY ROLE# START DATEo END DATE

PARTY RELATIONSHIP# RELATIONSHIP START DATEo RELATIONSHIP END DATE

RELATIONSHIP TYPE# RELATIONSHIP TYPE* RELATIONSHIP NAME* RELATIONSHIP DESC

ORGANIZATION MEMBERSHIP* MEMBERSHIP START DATEo MEMBERSHIP END DATE

ADMIN UNIT MEMBERSHIP* MEMBERSHIP START DATEo MEMBERSHIP END DATE

PARTY# PARTY SEQ ID* PARTY TYPEo PREFERRED OFFICIAL LANGUAGE TYPE

ADMINISTRATIVE ORGANIZATION UNIT

INDIVIDUALo OFFICIAL FIRST NAMEo OFFICIAL MIDDLE NAMEo OFFICIAL LAST NAMEo PREFERRED GIVEN NAMEo PREFERRED MIDDLE INITIALS NAMEo PREFERRED LAST NAMEo HONORIFIC TYPEo SUFFIX NAMEo FORMER LAST NAMEo BIRTH DATEo DEATH DATEo MARITAL STATUS TYPEo GENDER TYPE

INFORMAL GROUPo GROUP NAME

LEGAL ORGANIZATION* REGISTRATION NUMBER* LEGAL NAMEo BUSINESS NAMEo BUSINESS REGISTRATION STATUS TYPEo ACTIVITY CLASSIFICATION CODEo ACTIVITY DESC

NON-GO ORGANIZATION

DEPARTMENT* DEPARTMENT ENGLISH NAMEo DEPARTMENT FRENCH NAME* DEPARTMENT ENGLISH ABBRo DEPARTMENT FRENCH ABBR

GO ORGANIZATION* COMMON ENGLISH NAMEo COMMON FRENCH NAME* ENGLISH ABBRo FRENCH ABBR

NON-GO ORG ADMINUNITo ADMIN UNIT NAMEbelongs to

divided into

belongs to

divided into

belongs to

divided into

in

includes

includes

belongs to

type of

describes

from

involved in

to

involved in

type of

describes

role played by

involved as

belongs to

divided into

belongs to

divided into

belongs to

divided into

includes

member of

in

includes

includes

member of

in

includes

This example is a data model of the common data elements associated with “Individuals” and “Organizations”.

Development of a full logical data model of all common data elements produces the standardized definitions and relationships needed to facilitate effective sharing and integration of common data.

27

Our People



Infrastructure

Service Delivery Infrastructure Management Logical Model

• CDE and common components will form the foundation of the ESD infrastructure for the Ontario Government

• CDE will be the basis for service delivery markup

• The service delivery information management logical model is the blueprint for the project

28

Our People



Infrastructure

Service Delivery Mark-up• In order to build channel independent services ESD will need

standardized service delivery components driven by XML• These components will define:

– Prompts for questions asked

– Service and field specific help

– Links to related decision support materials and enabling legislation

– Contact information for alternative channels

– Service level expectations

– Context to which the service is relevant

– Connections to existing business rules and validations

– Customer interaction logic

– Links to or interoperability with related transactions from other programs/jurisdictions

Our People



Infrastructure

How CDEs and XML deliver E-Government services

Alana Boltwood

30

Our People



Infrastructure

How CDEs and XML deliver E-Government services

ServiceTransaction

CDEModel

Ontario Service Description Markup Language schema

CDESchema(XML datatypes)

Common Component

Transaction Building Block

Implemented as

Implemented as

Data model for

Shown to users as

Defines user interface of

Called by

Describes

Defines user interface of

31

Our People



Infrastructure

Levels of CDE Model

• Government Information Context

• Conceptual: Business understanding

• Logical: Standard template for system design (requires further transformation for RDBMS implementation)

32

Our People



Infrastructure

CDEM Subject Areas

• Party: individual, organization; party roles (client, partner, stakeholder, employee, etc.)

• Addresses and geography• Finance: accounts, transactions• Service Operation: program, service,

transaction, process• Motivation: goal, strategy, client need, law,

contract, performance metric• Time: business event, business cycle• Resources

33

Our People



Infrastructure

Conversion to XML Schemas

• CDE logical model is implemented as XML Schema datatypes– Party, Address, Finance in CDESchema– Service Operation, Motivation, Time in

Ontario Service Description Markup Language (OSDML)

• Rules established for the conversion, via a metamodel

OSDML-Identification.pdf

34

Our People



Infrastructure

Transaction Building Blocks

• Common Data Elements Model is a logical model template for system design

• Need a set of “building blocks” for application user interfaces, based on CDEM

• Building blocks are generic pieces of a form (electronic or paper)

• Examples: Person name; organization name; home phone number; business fax number; mailing address; email address; birthdate; height & weight

35

Our People



Infrastructure

Governance and Plans

• Research each subject area• Ministry representatives review CDEM and

XML schemas• Approval as an Ontario Government

architecture standard• Share model and schemas with other

governments, via Public Sector CIO Council

Our People



Infrastructure

Next Steps

37

Our People



Infrastructure

Presentation Layer

Internet

Call Center

Counter Environment

Fax

Future Service Delivery Devices

Businesses

Citizens

Employees

OPS ProgramsCluster A

Cluster B

Cluster C

Cluster D

XML Services Layer

Common Components

CDER(CDE Repository)

CDEM(CDE Model)

CDEM(CDE Model)

Schemas

Domain Specific

Schemas

SDML(Service Delivery

Markup Language) Defined Service

Forms Management

Cross Site/Program

Navigation & Searching

Content Management

Integrated Services

Programs & Services Catalogue/Directory

Context Management

XM

L M

essaging

XM

L M

essaging Within the enterprise

XML Definition of Service

XML Instance of Service Data

38

Our People



Infrastructure

Next Steps

• In order to implement the services delivery logical model in a timely fashion, concurrent streams will be done

• The development plan calls for coordinated:– Communications– Proof of concept development– Schema development– Transformations development– Registry/repository development– Training

39

Our People



Infrastructure

Questions? Feedback?

Corporate Architecture Branch

Management Board Secretariat

[email protected]

416-327-4108

[email protected]

416-327-0313

[email protected]

416-327-6771

Our People



Infrastructure

Appendix material

41

Our People



Infrastructure

LOCATION GO ORGANIZATION(OPS)

CLIENT(Recipient)

PARTNER(Provider)

Address Area Geo-spatial Mobile

Ministry Cluster Agency Board Office Commission Council Institution Foundation Association Center Administrative Authority Sector

Employee Person Group Private Sector Public Sector

Person Group Private Sector Public Sector

Original Common Data Elements

42

Our People



Infrastructure

Comparative Example Free Definition Fixed DefinitionName Location Name Location

Defining Data Elements for Sharing

123 Albert Street SarniaSmith, John

Albert Street North Sarnia

123 Albert Street

John Smith

J Smith

SmithJohn 123 Albert Street Sarnia

Common Data Elements can be used to structure data to make sharing and use of information

more effective and efficientFree definitions make input

variable and limit use and sharing information

43

Our People



Infrastructure

Building Block Example

Daytime Phone Number

AreaCode + LocalNumber + ExtensionNumber

CountryCode = 1 (North America), TimeType = Day, TechnologyType = Telephone

International Home Phone Number

CountryCode + AreaCode + LocalNumber

ContactPurposeType = Personal, TechnologyType = Telephone

Business Fax Number

CountryCode + AreaCode + LocalNumber

ContactPurposeType = Business, TechnologyType = Fax

PARTY LOCATION ROLEo CONTACT PURPOSE TYPEo DELIVERY TYPEo TIME TYPEo SEASON TYPEo PERMANENCY TYPEo VALID FROM DATEo VALID TO DATEo OFFICE NAME

LOCATION DESCRIPTIONo LOCATION TYPEo DATA QUALITY DESC

VIRTUAL LOCATION DESCo TECHNOLOGY TYPE

TELECOMM NUMBERo COUNTRY CODEo AREA CODEo LOCAL NUMBERo EXTENSION NUMBERo SPECIAL INSTRUCTIONS DESC

usage of

used for

Building Blocks

CDEM

44

Our People



Infrastructure

What’s in a building block

• Prompts (English, French) for entire BB and each element/attribute in the BB

• 1 or more CDEM entities• Restrictions: selection of attributes, default

values for non-selected attributes• Extensions (additional attributes)• Attribute length, datatype, optionality,

ordering• Actions

45

Our People



Infrastructure

CDEM content

• Some draft models follow. None have been approved yet as a Government of Ontario standard, and some are still being researched.

46

Our People



Infrastructure

Party (Logical)


INFORMAL GROUP MEMBERSHIP# MEMBERSHIP START DATEo MEMBERSHIP END DATE


PARTY RELATIONSHIP# RELATIONSHIP START DATEo RELATIONSHIP END DATE

RELATIONSHIP TYPE# RELATIONSHIP TYPE* RELATIONSHIP NAME* RELATIONSHIP DESC

ORGANIZATION MEMBERSHIP* MEMBERSHIP START DATEo MEMBERSHIP END DATE

ADMIN UNIT MEMBERSHIP* MEMBERSHIP START DATEo MEMBERSHIP END DATE


ADMINISTRATIVE ORGANIZATION UNIT

INDIVIDUALo OFFICIAL FIRST NAMEo OFFICIAL MIDDLE NAMEo OFFICIAL LAST NAMEo PREFERRED GIVEN NAMEo PREFERRED MIDDLE INITIALS NAMEo PREFERRED LAST NAMEo HONORIFIC TYPEo SUFFIX NAMEo FORMER LAST NAMEo BIRTH DATEo DEATH DATEo MARITAL STATUS TYPEo GENDER TYPE

INFORMAL GROUPo GROUP NAME

LEGAL ORGANIZATION* REGISTRATION NUMBER* LEGAL NAMEo BUSINESS NAMEo BUSINESS REGISTRATION STATUS TYPEo ACTIVITY CLASSIFICATION CODEo ACTIVITY DESC

NON-GO ORGANIZATION

DEPARTMENT* DEPARTMENT ENGLISH NAMEo DEPARTMENT FRENCH NAME* DEPARTMENT ENGLISH ABBRo DEPARTMENT FRENCH ABBR

GO ORGANIZATION* COMMON ENGLISH NAMEo COMMON FRENCH NAME* ENGLISH ABBRo FRENCH ABBR

NON-GO ORG ADMINUNITo ADMIN UNIT NAMEbelongs to

divided into

belongs to

divided into

belongs to

divided into

in

includes

includes

belongs to

type of

describes

from

involved in

to

involved in

type of

describes

role played by

involved as

belongs to

divided into

belongs to

divided into

belongs to

divided into

includes

member of

in

includes

includes

member of

in

includes

Within GO Organization, Non-GO Organization, Admin Org Unit and Party Role there are subtypes not shown.

47

Our People



Infrastructure

Address (Logical)



ADDRESS GROUP TYPE# ADDRESS GROUP TYPE CODE* ADDRESS GROUP TYPE DESC

ADDRESS GROUP# ADDRESS GROUP SEQ ID* ADDRESS GROUP NAME

ADDRESS UNIT DESIGNATOR TYPE# UNIT DESIGNATOR TYPE CODE* UNIT DESIGNATOR TYPE DESC* VALID CANADA INDICATOR

LOCATION ADDRESS# ADDRESS SEQ IDo DIRECTIONS COMMENT

ADDRESS UNIT# UNIT SEQ ID* UNIT DESCRIPTION

COUNTRY# COUNTRY CODE* COUNTRY NAME* TELECOMM COUNTRY CODE

COUNTRY SUBDIVISION# COUNTRY SUBDIVISION CODE* COUNTRY SUBDIVISION TYPE* COUNTRY SUBDIVISION NAMEo SEQUENCE NUMBER

TELECOMMUNICATION TYPE# COMMUNICATION TYPE CODE* COMMUNICATION TYPE DESC

TELECOMMUNICATION ADDRESS

CONCESSION/ PLAN# CONCESSION/ PLAN SEQ ID* CONCESSION/ PLAN NUMBER

URBAN UNIT# URBAN UNIT SEQ ID* URBAN UNIT NAME

STREET DIRECTION TYPE# STREET DIRECTION TYPE CODE* STREET DIRECTION TYPE NAME

STREET TYPE# STREET TYPE CODEo LANGUAGE CODE* STREET TYPE NAME* VALID CANADA INDICATOR

DELIVERY INSTALLATION TYPE# DELIV INSTALL TYPE CODE* DELIV INSTALL TYPE NAME

DELIVERY INSTALLATION# DELIVERY INSTALLATION SEQ ID* DELIVERY INSTALLATION AREA NAMEo DELIVERY INSTALLATION QUALIFIER NAME

ROUTE SERVICE TYPE# ROUTE SERVICE TYPE CODE* ROUTE SERVICE TYPE NAME* VALID CANADA INDICATOR

STREET# STREET SEQ ID* STREET NAME

GEOGRAPHICTOWNSHIP# GEO TOWNSHIP SEQ ID* GEO TOWNSHIP NAME

ADDRESS/ COMMUNICATION ROLE# ADDRESS ROLE CODE# TEMPORARY INDICATOR* ROLE DESC

ADDRESS/ COMMUNICATION USAGE# START DATEo END DATEo TIME PERIOD TYPE CODE* EFFECTIVE DATEo EXPIRY DATEo INVALID ADDRESS INDICATORo INVALID ADDRESS DATE

LOT/ PART# LOT/ PART NUMBER


US MILITARY "STATE"# MILITARY "STATE" CODE* MILITARY "STATE" NAME

EMAIL ADDRESS# EMAIL ADDRESS

TELEPHONE ADDRESS# TELEPHONE SEQ ID* AREA CODE* TELEPHONE NUMBERo ALPHANUMERIC TELEPHONE NUMBERo EXTENSION NUMBER

INTERNET ADDRESS# INTERNET ADDRESS SEQ ID* URL DESCRIPTIONo URL NUMERIC DESCRPTION

CANADIAN AND USA ADDRESSo ADDITIONAL ADDRESS INFORMATION COMMENT

INTERNATIONAL ADDRESS* ADDRESS LINE 1o ADDRESS LINE 2o ADDRESS LINE 3o MAILING CODE

OVERSEAS US MILITARY ADDRESS* DELIVERY ADDRESS LINE* MILITARY DESIGNATION CODE* ZIP CODE

NON-SURVEY ADDRESSo BILINGUAL INDICATOR* MAILING CODE

ONTARIO PHYSICAL SURVEY ADDRESS

MAILING INTERNATIONALADDRESS

PHYSICAL INTERNATIONALADDRESS

MAILING GENERAL DELIVERY ADDRESS

ROUTE CIVIC ADDRESS* ROUTE SERVICE ID

MAILING POST OFFICE BOX ADDRESS* POST OFFICE BOX ID

CIVIC ADDRESSo DIRECTION PREFIX/SUFFIX CODE* CIVIC NUMBERo CIVIC NUMBER SUFFIX

PHYSICAL CIVIC ADDRESS

US PO BOX ADDRESS

MAILING ROUTE CIVIC ADDRESS

MAILING CIVIC ADDRESS

PHYSICAL ROUTE CIVICADDRESSo DIRECTION PREFIX/SUFFIX CODE* CIVIC NUMBERo CIVIC NUMBER SUFFIX

CAN PO BOX ADDRESS

CAN GENERAL DELIVERYADDRESS

US GENERAL DELIVERYADDRESS

US ROUTE ADDRESS* BOX ID

CAN ROUTE ADDRESSo SITE IDo COMPARTMENT ID

role played by

involved as

described by

describes

secondary info for

main info for

described by

describes

part of Canadian Address

composed of

described by

describes

described by

describes

typed by

describes

typed bydescribes

typed by

describes

deliv. responsibility of responsible for

location of

at

part ofdivided in

described by

included in

described by

included in

described by

describes

lies in

contains

lies in

contains

lies in

contains

reachable in

location for

available for

located at

described by

describes

available at

mailing location for

available at

physical location for

available at

used by

part of

divided in

available for

located at type of

describes

deliv. responsibility of

responsible for

deliv. responsibility of

responsible for

additional typed in US only by

describes

part of

contains

part of

divided in

part of

contains

lies in

contains

lies in

contains

secondary info for

main info for

48

Our People



Infrastructure

Service Operation, Motivation, Time (Conceptual)

PARTY

BUSINESS CYCLE

SERVICE

BUSINESS EVENT

MOTIVATION

SERVICE DELIVERYEVENT

PARTY ROLE

EA PROGRAM

FINANCIALTRANSACTION

PERFORMANCE METRIC

PROCESS

SERVICE DELIVERY CHANNEL

TARGET GROUP SERVICE OWNER

STAKEHOLDER

PROGRAM GOAL

OTHER PARTYROLE

RULE

RESOURCE MANAGEMENTPROCESS

AGENT OF CHANGE CORE BUSINESS

NEED

PUBLIC GOAL

STRATEGY

INTERNAL SERVICE

SERVICE PROCESS

ORG OPERATION PROCESS

PUBLIC SERVICE

GOVERNOR

INTERESTEDPARTY

SUPPLIER

CLIENT

COLLABORATOR

CLIENT AGENT

BUSINESS RULE

OUTCOME GOAL

STATUTE REGULATION

IMPACT GOAL

AGREEMENT

PARTNER

AGENT

CONTRACT

determine timing of

scheduled by

trigger delivery of

triggered by

role played by

involved as

instance of

delivered as

define terms of

regulated byx

x

accountable to

x

benefits

receives

part of

includes

accountable for

owned by

x

has a vested interest in

constrain delivery of

constrained by

triggers

triggered by

delivered through

x

broken down into

part of

x

x part of

broken into

measures

evaluated by

x

definesused to achieve

x

is to satisfy/address

satisfied/addressed by

aligns with

specified by

belongs to

groups

framework for

accomplished by

impact

affected by

includes

belongs to

belongs to

includes

experienced by

experiences

49

Our People



Infrastructure

GEOGRAPHIC AREAo OFFICIAL NAME* COMMON ENGLISH NAMEo COMMON FRENCH NAME* GEO AREA TYPEo BOUNDARY FILEo MAP IMAGE

THREE-D GEO AREA

SURFACE AREA

CENSUS DIVISIONo CENSUS DIVISION ID

ADMINISTRATIVE REGION TYPEo ADMIN REGION TYPE NAMEo ADMIN REGION TYPE AUTHORITYo ADMIN REGION TYPE DESC

ADMINISTRATIVE REGION

CENSUS SUBDIVISIONo CENSUS SUBDIVISION ID

ENUMERATION AREAo EA ID

POSTAL CITY

ONTARIO MUNICIPALITY

CENSUS AREAo CENSUS AREA IDo CENSUS AREA TYPE

SURVEY COUNTY

SURVEY TOWNSHIP

SURVEY CONCESSIONo CONCESSION NUMBER

CONTINENT COUNTRYo ISO CODEo FLAG IMAGEo INTERNET COUNTRY DOMAINo TELECOMM COUNTRY CODE

COUNTRY SUBDIVISIONo ISO CODE

CAN POSTAL 1STLETTERo FIRST LETTER CODE

CAN POSTAL FSAAREAo FSA CODE

CAN POSTAL LDUAREAo LDU CODE

ONTARIO RIDING

SURVEY LOTo LOT NUMBER

FEDERAL ELECTORAL DISTRICTo FED ID

US STATE* STATE CODE* SUBDIVISION TYPE

SINGLE TIERMUNICIPALITY

LOWER TIERMUNICIPALITY

CANADIAN PROVINCE* PROVINCE CODE* SUBDIVISION TYPE* STATCAN CODE

OTHER SUBDIVISION

UPPER TIERMUNICIPALITY

CONSOL MUNICSERVICE MGMT AREA

ONTARIO

OTHERPROVINCE

x

x

x

x

part of

contains

x

x

x

x

x

x

xx

xx

x

x

part of

divided into

part of

divided into

part of

divided into

x

x

x x

x

x

x

x

part of

divided into

x

x

x

xx

x

part of

divided into

defined as

a

forms

made up of

x

x

x

x

xx

x

x

x

x

CDEM 1.5: Geographic Areas

Our People Government for the 21st Century Doing Business Differently Infrastructure eGovernment:...

Documents

Transcript of Our People Government for the 21st Century Doing Business Differently Infrastructure eGovernment:...