Transcript Common Data Elements

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
Agenda
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
•
•
•
•
•
•
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
Government
for the 21st
Century
Strategic Direction:
E-Government
• In March 2000, in approving its Digital
Economy Strategy, the Ontario Government
approved electronic government as a priority
Doing
Business
Differently
Infrastructure
• The plan is to demonstrate leadership by
example in electronic government and more
specifically, electronic service delivery
4
Our People
The E-Government Context
Government
for the 21st
Century
Doing
Business
Differently
Citizen Engagement
Integrated Service
Delivery (ISD)
Enabling two-way public
interaction
Providing Ontario services over the
counter and electronically to
individuals and businesses
Sectoral Reform
Using I&IT to drive and enable
sectoral reform
Electronic Service Delivery (ESD)
Providing services electronically to our clients
Corporate Systems and Enablers
Infrastructure
Enterprise Resource (HR and Financial) Systems and
e-commerce processes
Common I&IT Infrastructure
Underlying technology to support both enterprise-wide and business
specific applications
5
Our People
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
Strategic Vision and 2003 Target for
Electronic 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
Implications in Ontario
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Bottom-line….
Government
for the 21st
Century

All levels of government are working
hard on using I&IT to improve the
services they provide to their clients
Doing
Business
Differently

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
Infrastructure
8
Our People
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
But what does this mean
to Information and
Information Technology
(I&IT)?
9
Our People
Going “E” By 2003 means...
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
But Not With Just Technology
Government
for the 21st
Century
Doing
Business
Differently
• 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
Infrastructure
• These interchanges will based on
eXtensible Markup Language (XML)
11
Our People
XML - A Definition
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Government
for the 21st
Century
Doing
Business
Differently
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 EGovernment
• 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
But Why XML?
Government
for the 21st
Century
• 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:
Doing
Business
Differently
Infrastructure
– 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
Government
for the 21st
Century
Doing
Business
Differently
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:
Infrastructure
– 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
Benefits of XML
• Short Term
Government
for the 21st
Century
Doing
Business
Differently
– 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 reengineering
• Long Term
Infrastructure
– 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
Basic Assumptions for Using XML
Government
for the 21st
Century
• Transformations from standardized messaging
language to program-ready data is the responsibility
of the program owner
• XML must support multiple service providers
Doing
Business
Differently
• XML solution must delivers complete transactions
• Online presentation is not part of the transaction
definition schema
Infrastructure
• XML Services must comply with W3C
17
Our People
Government
for the 21st
Century
Doing
Business
Differently
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
Our People
Government
for the 21st
Century
Doing
Business
Differently
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
18
19
Our People
Integrated Information Project
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Government
for the 21st
Century
Doing
Business
Differently
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
Benefits of CDEModel
People use same
meaning of words
Government
for the 21st
Century
People
communicate well
Reuseable data
model
components
Doing
Business
Differently
Generic and
standard data
model
Save time &
money in system
life cycle, and
improve service
delivery
Reuseable
application
components
Easy integration
of systems
Infrastructure
Data model for
Common Data
Elements
Repository
Single
authoritative
source for
common data
22
Our People
Government
for the 21st
Century
Doing
Business
Differently
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
Government
for the 21st
Century
Government Information
Context Model
Context Information Model
Business Sectors
Responsible Government
Stew ardship
Infrastructure, Resources,
and Environmental Wellbeing
Information
Groupings
Doing
Business
Differently
Vibrant Communities
Economic
Competitive Ontario
Social
Responsibility
Learning, Wellness, and
Self-Reliance
Safe and Just Social
Environment
Infrastructure
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
Government
for the 21st
Century
From Context to Conceptual
Model
Core
Businesses
(C6-Why)
provide
framew ork
for
Goals and
Strategies
(C6-Why)
GO
Organizations
(C4-Who)
define
nature of
responsible for
Rules
(C6-Why)
administer
Programs
(C2-How)
define
terms of
Resources
(C1-What)
fund
constrain
delivery of
Doing
Business
Differently
Business
Cycles
(C5-When)
provided
at
trigger
delivery of
Business
Events
(C5-When)
Locations
(C3-Where)
address
provided
by
impact
Needs
(C6-Why)
experienced
by
Infrastructure
found at
Services
(C2-How)
determine
timing of
Partners
(C4-Who)
Stakeholders
(C4-Who)
are involved
as
Clients
(C4-Who)
deliver
services as
receive
services as
Individuals
(C4-Who)
Organizations
(C4-Who)
25
Our People
Identification of Common Elements
Government
for the 21st
Century
Core
Businesses
(C6-Why)
provide
framework
for
Goals and
Strategies
(C6-Why)
GO
Organizations
(C4-Who)
define
nature of
responsible for
Rules
(C6-Why)
administer
Programs
(C2-How)
define
terms of
Resources
(C1-What)
fund
constrain
delivery of
Doing
Business
Differently
Business
Cycles
(C5-When)
Locations
(C3-Where)
provided
at
trigger
delivery of
Business
Events
(C5-When)
found at
Services
(C2-How)
determine
timing of
address
provided
by
impact
Needs
(C6-Why)
experienced
by
Partners
(C4-Who)
are involved
as
Clients
(C4-Who)
deliver
services as
Infrastructure
Stakeholders
(C4-Who)
receive
services as
Individuals
(C4-Who)
Organizations
(C4-Who)
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.
Logical Data Model of Common
Data Elements
Our People
Government
for the 21st
Century
ORGANIZATION MEMBERSHIP
ADMIN UNIT MEM BERSHIP
* MEMBERSHIP STAR T DATE
o MEM BER SHIP EN D D ATE
* MEMBERSHIP STAR T DATE
o MEM BER SHIP EN D D ATE
in
PARTY
includes
member of
# PAR TY SEQ ID
* PARTY TYPE
o PR EFERRED OFFIC IAL LAN GU AGE TYPE
This example is a
data model of the
common data
elements
associated with
“Individuals” and
“Organizations”.
in
member of
INDIVIDUAL
INFORMAL GROUP MEM BERSHI
P
# MEM BER SHIP START D ATE
o MEM BER SHIP EN D D ATE
includes
includes
belongs to
o
o
o
o
o
o
o
o
o
o
o
o
o
OFFICIAL FIRST N AME
OFFICIAL MIDD LE N AME
OFFICIAL LAST NAME
PR EFERRED GIVEN NAME
PR EFERRED MID DLE IN ITIALS N AME
PR EFERRED LAST NAME
HON OR IFIC TYPE
SU FFIX NAME
FORMER LAST NAME
BIRTH DATE
DEATH D ATE
MAR ITAL STATUS TYPE
GEND ER TYPE
divided into
INFORMAL GROUP
in
o GROUP N AME
belongs to
includes
includes
Doing
Business
Differently
ROLE TYPE
LEGAL ORGANIZATION
# ROLE TYPE
* ROLE N AME
* ROLE D ESC
*
*
o
o
o
o
describes
REGISTRATION N UMBER
LEGAL NAME
BU SINESS N AM E
BU SINESS R EGISTRATION STATUS TYPE
AC TIVITY CLASSIFIC ATION CODE
AC TIVITY DESC
divided
includes
ADMINISTRATIVE ORGANIZATION UNIT
divided into
into
NON-GO ORG ADMIN
UNIT
NON-GO ORGANIZATION
belongs to
o AD MIN UN IT NAME
belongs to
divided into
type of
belongs to
PARTY ROLE
divided into
# STAR T DATE
o EN D DATE
role played by
GO ORGANIZATION
involved as
involved in
from
involved in
* COMMON ENGLISH NAME
o COM MON FR ENC H N AME
* ENGLISH ABBR
o FR ENC H ABBR
DEPARTMENT
divided into
belongs to
* DEPAR TMEN T ENGLISH N AME
o DEPARTMENT FR ENCH N AME
* DEPAR TMEN T ENGLISH ABBR
o DEPARTMENT FR ENCH ABBR
belongs to
to
PARTY RELATIONSHIP
# RELATIONSHIP STAR T DATE
o RELATIONSHIP EN D D ATE
Infrastructure
type of
describes
RELATIONSHIP TYPE
# RELATIONSHIP TYPE
* RELATIONSH IP NAME
* RELATIONSH IP DESC
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.
26
27
Our People
Government
for the 21st
Century
Doing
Business
Differently
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
Service Delivery Mark-up
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Government
for the 21st
Century
Doing
Business
Differently
How CDEs and XML deliver
E-Government services
Alana Boltwood
Infrastructure
30
Our People
How CDEs and XML deliver
E-Government services
Government
for the 21st
Century
CDEModel
Implemented as
Implemented as
CDESchema
(XML datatypes)
Doing
Business
Differently
Infrastructure
Ontario Service
Description Markup
Language schema
Describes
Shown to users as
Data model for
Transaction
Building Block
Defines user
interface of
Defines user
interface of
Common
Component
Called by
Service
Transaction
31
Our People
Levels of CDE Model
Government
for the 21st
Century
• Government Information Context
• Conceptual: Business understanding
Doing
Business
Differently
Infrastructure
• Logical: Standard template for system
design (requires further transformation for
RDBMS implementation)
32
Our People
CDEM Subject Areas
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Conversion to XML Schemas
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
34
Our People
Transaction Building Blocks
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Governance and Plans
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Government
for the 21st
Century
Next Steps
Doing
Business
Differently
Infrastructure
37
Our People
Presentation Layer
XML Services Layer
OPS Programs
Cluster A
XML Instance of Service Data
Government
for the 21st
Century
Fax
Content Management
SDML
(Service Delivery
Businesses
Markup Language)
Call Center
Future
Service
Delivery
Devices
XML Messaging
Infrastructure
Counter
Environment
Navigation &
Searching
Forms Management
Programs & Services
Catalogue/Directory
Domain
Specific
Schemas
CDEM
(CDE Model)
Schemas
CDEM
(CDE Model)
(CDE Repository)
Integrated Services
Context Management
Cluster C
Cluster D
CDER
XML Definition of Service
XML Messaging
Citizens
Internet
Cluster B
Defined Service
Cross Site/Program
Doing
Business
Differently
Employees
Within the enterprise
Common
Components
38
Our People
Next Steps
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
Questions? Feedback?
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
Corporate Architecture Branch
Management Board Secretariat
[email protected]
416-327-4108
[email protected]
416-327-0313
[email protected]
416-327-6771
Our People
Government
for the 21st
Century
Appendix material
Doing
Business
Differently
Infrastructure
41
Our People
Original Common Data Elements
Government
for the 21st LOCATION
Century




Doing
Business
Differently
Infrastructure
Address
Area
Geo-spatial
Mobile
GO ORGANIZATION
(OPS)
CLIENT
(Recipient)
PARTNER
(Provider)






















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
42
Our People
Defining Data Elements for Sharing
Government
for the 21st
Century
Comparative Example
Free Definition
Name
Location
Smith, John
123 Albert Street Sarnia
John Smith
Doing
Business
J Smith
Differently
Fixed Definition
Name
John
Smith
Location
123
Albert
Street
Albert Street North Sarnia
123 Albert Street
Free definitions make input
variable and limit use and sharing
Infrastructure
information
Common Data Elements can be
used to structure data to make
sharing and use of information
more effective and efficient
Sarnia
43
Our People
LOCATION DESCRIPTION
o LOC ATION TYPE
o DATA QU ALITY D ESC
VIRTUAL LOCATION DESC
Government
o TEC HN OLOGY TYPE
for the 21st
Century
TELECOMM NUMBER
o
o
o
o
o
COUNTR Y CODE
AREA CODE
LOC AL N UMBER
EXTEN SION NU MBER
SPEC IAL IN STRU CTIONS D ESC
Building Block
Example
Building Blocks
Daytime Phone Number
AreaCode + LocalNumber + ExtensionNumber
CDEM
Doing
Business
Differently
CountryCode = 1 (North America), TimeType = Day,
TechnologyType = Telephone
used for
International Home Phone Number
usage of
PARTY LOCATION ROLE
o CONTACT PU RPOSE TYPE
o DELIVER Y TYPE
Infrastructure
o TIME TYPE
o SEASON TYPE
o PER MANEN CY TYPE
o VALID FR OM DATE
o VALID TO DATE
o OFFICE NAME
CountryCode + AreaCode + LocalNumber
ContactPurposeType = Personal, TechnologyType = Telephone
Business Fax Number
CountryCode + AreaCode + LocalNumber
ContactPurposeType = Business, TechnologyType = Fax
44
Our People
What’s in a building block
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• 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
CDEM content
Government
for the 21st
Century
Doing
Business
Differently
Infrastructure
• Some draft models follow. None have been
approved yet as a Government of Ontario
standard, and some are still being
researched.
Our People
46
Party
(Logical)
Government
for the 21st
Century
ORGANIZATION MEMBERSHIP
ADMIN UNIT MEM BERSHIP
* MEMBERSHIP STAR T DATE
o MEM BER SHIP EN D D ATE
* MEMBERSHIP STAR T DATE
o MEM BER SHIP EN D D ATE
in
PARTY
includes
member of
# PAR TY SEQ ID
* PARTY TYPE
o PR EFERRED OFFIC IAL LAN GU AGE TYPE
in
member of
INDIVIDUAL
INFORMAL GROUP MEM BERSHI
P
# MEM BER SHIP START D ATE
o MEM BER SHIP EN D D ATE
includes
includes
belongs to
o
o
o
o
o
o
o
o
o
o
o
o
o
OFFICIAL FIRST N AME
OFFICIAL MIDD LE N AME
OFFICIAL LAST NAME
PR EFERRED GIVEN NAME
PR EFERRED MID DLE IN ITIALS N AME
PR EFERRED LAST NAME
HON OR IFIC TYPE
SU FFIX NAME
FORMER LAST NAME
BIRTH DATE
DEATH D ATE
MAR ITAL STATUS TYPE
GEND ER TYPE
divided into
INFORMAL GROUP
in
o GROUP N AME
belongs to
includes
includes
ROLE TYPE
LEGAL ORGANIZATION
# ROLE TYPE
* ROLE N AME
* ROLE D ESC
*
*
o
o
o
o
Doing
Business
Differently
describes
REGISTRATION N UMBER
LEGAL NAME
BU SINESS N AM E
BU SINESS R EGISTRATION STATUS TYPE
AC TIVITY CLASSIFIC ATION CODE
AC TIVITY DESC
divided
includes
ADMINISTRATIVE ORGANIZATION UNIT
divided into
into
NON-GO ORG ADMIN
UNIT
NON-GO ORGANIZATION
belongs to
o AD MIN UN IT NAME
belongs to
divided into
type of
belongs to
PARTY ROLE
divided into
# STAR T DATE
o EN D DATE
role played by
involved as
involved in
from
involved in
GO ORGANIZATION
*
o
*
o
COMMON ENGLISH NAME
COM MON FR ENC H N AME
ENGLISH ABBR
FR ENC H ABBR
DEPARTMENT
divided into
belongs to
*
o
*
o
DEPAR TMEN T ENGLISH N AME
DEPARTMENT FR ENCH N AME
DEPAR TMEN T ENGLISH ABBR
DEPARTMENT FR ENCH ABBR
belongs to
to
PARTY RELATIONSHIP
Infrastructure
# RELATIONSHIP STAR T DATE
o RELATIONSHIP EN D D ATE
type of
describes
RELATIONSHIP TYPE
# RELATIONSHIP TYPE
* RELATIONSH IP NAME
* RELATIONSH IP DESC
Within GO Organization, Non-GO Organization,
Admin Org Unit and Party Role there are subtypes
not shown.
47
TELECOMMUNICATION ADDRESS
Our People
TELECOMMUNICATION TYPE
# COM MUNICATION TYPE COD E
* COMMUN ICATION TYPE DESC
INTERNET ADDRESS
PARTY
# INTERN ET ADDR ESS SEQ ID
* UR L D ESCRIPTION
o URL NU MERIC DESC RPTION
# PAR TY SEQ ID
* PARTY TYPE
o PR EFERRED OFFIC IAL LAN GU AGE TYPE
describes
TELEPHONE ADDRESS
described by
reachable in
#
*
*
o
o
TELEPH ON E SEQ ID
AREA C OD E
TELEPHONE N UMBER
ALPHANU MERIC TELEPHONE N UMBER
EXTEN SION NUM BER
# STAR T DATE
o EN D DATE
located at
ROLE TYPE
# ROLE TYPE
* ROLE N AME
* ROLE D ESC
ADDRESS GROUP
available at
ADDRESS GROUP TYPE
described by
# AD DR ESS GROUP SEQ ID
* ADD RESS GR OU P NAME
describes
# AD DR ESS GROUP TYPE CODE
* ADD RESS GR OU P TYPE D ESC
available for available for
ADDRESS/ COMM UNICATION USAGE
#
o
o
*
o
o
o
composed of
STAR T DATE
EN D DATE
TIME PER IOD TYPE CODE
EFFECTIVE DATE
EXPIR Y DATE
INVALID ADD RESS IN DIC ATOR
INVALID ADD RESS DATE
part of Canadian Address
location for
available at
available at
described by
LOCATION ADDRESS
COUNTRY
# COU NTR Y CODE
* COUN TRY N AME
* TELECOMM COUN TRY C ODE
# AD DR ESS SEQ ID
o DIR ECTION S COMMENT
contains
mailing location for
lies in
CANADIAN AND USA ADDRESS
describes
o AD DITIONAL ADD RESS INFORMATION COMMENT
physical location for
#
o
*
*
STR EET TYPE C OD E
LANGUAGE C OD E
STREET TYPE NAME
VALID CAN AD A IN DIC ATOR
CIVIC ADDRESS
included in
STREET
additional typed in US only by
# STR EET SEQ ID
* STREET NAME
described by
STREET DIRECTION TYPE
typed by
described by
COU NTR Y SUBDIVISION COD E
COUN TRY SUBD IVISION TYPE
COUN TRY SUBD IVISION NAME
SEQUEN CE NU MBER
secondary info for
PHYSICAL CIVIC ADDRESS
ADDRESS UNIT
# UNIT SEQ ID
* UN IT D ESC RIPTION
secondary info for
described by
* ROUTE SERVIC E ID
describes
#
*
*
o
main info for
MAILING CIVIC ADDRESS
ROUTE CIVIC ADDRESS
# STR EET DIR EC TION TYPE CODE
* STREET DIRECTION TYPE NAME
ROUTE SERVICE TYPE
o DIR ECTION PREFIX/SU FFIX C OD E
* CIVIC N UMBER
o CIVIC NU MBER SUFFIX
typed by
describes
included in
describes
MAILING ROUTE CIVIC ADDRES
S
PHYSICAL ROUTE CIVIC
ADDRESS
o DIR ECTION PREFIX/SU FFIX C OD E
* CIVIC N UMBER
o CIVIC NU MBER SUFFIX
ADDRESS UNIT DESIGNATOR TYPE
# UNIT DESIGN ATOR TYPE C OD E
* UN IT D ESIGNATOR TYPE DESC
* VALID CAN AD A IN DIC ATOR
US ROUTE ADDRESS
* BOX ID
CAN ROUTE ADDRESS
describes
# ROU TE SERVICE TYPE C ODE
* ROUTE SERVIC E TYPE NAME
* VALID CAN AD A IN DIC ATOR
COUNTRY SUBDIVISION
# AD DR ESS ROLE CODE
# TEMPORARY IND ICATOR
* ROLE D ESC
o BILIN GUAL IND ICATOR
* MAILING COD E
typed by
describes
ADDRESS/ COMM UNICATION ROLE
NON-SURVEY ADDRESS
describes
STREET TYPE
deliv. responsibility of
o SITE ID
o COM PAR TMEN T ID
described by
responsible for
DELIVERY INSTALLATION
contains
lies in
# DELIVER Y INSTALLATION SEQ ID
* DELIVERY IN STALLATION AREA NAME
o DELIVER Y INSTALLATION QUALIFIER NAME
MAILING GENERAL DELIVERY ADDRESS
contains
US GENERAL DELIVERY
ADDRESS
CAN GENERAL DELIVERYdeliv. responsibility of
ADDRESS
responsible for
described by
DELIVERY INSTALLATION TYPE
describes
# DELIV INSTALL TYPE CODE
* DELIV INSTALL TYPE N AME
responsible for
contains
URBAN UNIT
# URBAN UN IT SEQ ID
* UR BAN U NIT N AME
contains contains
lies in
MAILING POST OFFICE BOX ADDRESS
contains
* POST OFFICE BOX ID
CONCESSION/ PLAN
part of
deliv. responsibility of
# CON CESSION/ PLAN SEQ ID
* CONC ESSION/ PLAN N UMBER
US PO BOX ADDRESS
CAN PO BOX ADDRESS
part of
GEOGRAPHIC
TOWNSHIP
# GEO TOWNSH IP SEQ ID
* GEO TOWN SHIP N AME
divided in
divided in
divided in
part of
main info for
part of
LOT/ PART
# LOT/ PAR T NU MBER
part of
at
ONTARIO PHYSICAL SURVEY ADDRESS
location of
INTERNATIONAL ADDRESS
* ADD RESS LIN E 1
o AD DR ESS LINE 2
o AD DR ESS LINE 3
o MAILIN G C ODE
Infrastructure
lies in
PHYSICAL INTERNATIONAL
ADDRESS
lies in
US MILITARY "STATE"
# MILITARY "STATE" C OD E
* MILITAR Y "STATE" NAME
type of
describes
EMAIL ADDRESS
Doing
Business
Differently
PARTY ROLE
role played by
located at
used by
# EMAIL ADD RESS
Government
for the 21st
Century
involved as
OVERSEAS US MILITARY ADDRESS
* DELIVERY ADD RESS LIN E
* MILITAR Y DESIGNATION CODE
* ZIP C ODE
MAILING INTERNATIONAL
ADDRESS
Address
(Logical)
48
Service Operation, Motivation,
Time (Conceptual)
Our People
MOTIVATION
SERVICE
delivered as
Government
for the 21st
Century
constrain delivery of
RULE
instance of
constrained by
STATUTE
REGULATION
SERVICE DELIVERY
EVENT
triggers
PUBLIC SERVICE
triggered by
FINANCIAL
TRANSACTION
AGREEMENT
EA PROGRAM
CONTRACT
define terms of
regulated by
BUSINESS RULE
INTERNAL SERVICE
x
BUSINESS EVENT
triggered by
x
AGENT OF CHANG impact
E
affected by
trigger delivery of
groups
CORE BUSINESS
belongs to
framework for
part of
accomplished by
PUBLIC GOAL
PROGRAM GOAL
includes
specified by
aligns with
OUTCOME GOAL
x
x
STRATEGY
used to achieve
Doing
Business
Differently
BUSINESS CYCLE
scheduled by
defines
determine timing of
IMPACT GOAL
x
x
is to satisfy/address
PERFORMANCE METRIC
part of
measures
evaluated by
PROCESS
satisfied/addressed by
NEED
SERVICE PROCESS
broken down into
x
part of
experienced by
ORG OPERATION PROCESS
benefits
delivered through
owned by
PARTY ROLE
RESOURCE M ANAGEMENT
PROCESS
has a vested interest in
experiences
receives
accountable for
STAKEHOLDER
Infrastructure
TARGET GROUP
includes
CLIENT
SERVICE OWNER
belongs to
includes
GOVERNOR
INTERESTED
PARTY
COLLABORATOR
PARTNER
SUPPLIER
belongs to
accountable to
x
CLIENT AGENT
AGENT
PARTY
involved as
role played by
x
SERVICE DELIVERY CHANNEL
OTHER PARTY
ROLE
broken into
49
CDEM 1.5: Geographic Areas
Our People
GEOGRAPHIC AREA
o
*
o
*
o
o
Government
for the 21st
Century
OFFICIAL NAME
COMMON ENGLISH NAME
COMMON FR ENC H N AME
GEO AREA TYPE
BOUN DAR Y FILE
MAP IMAGE
THREE-D GEO AREA
SURFACE AREA
CONTINENT
COUNTRY
x
x
o
o
o
o
ISO C OD E
FLAG IMAGE
INTERN ET COUN TR Y DOMAIN
TELECOMM COUNTR Y CODE
divided into
COUNTRY SUBDIVISION
o ISO C OD E
contains
part of
POSTAL CITY
part of
US STATE
OTHER SUBDIVISION
* STATE COD E
* SUBD IVISION TYPE
CANADIAN PROVINCE
* PROVINC E CODE
* SUBD IVISION TYPE
* STATCAN C OD E
ONTARIO RIDING
divided into
OTHER
PROVINCE
part of
CAN POSTAL 1ST
LET TER
o FIRST LETTER C OD E
CAN POSTAL FSA
divided into
AREA
part of
o FSA C OD E
part of
divided into
defined as
ADMINISTRATIVE REGION
ADMINISTRATIVE REGION TYPE
o AD MIN REGION TYPE N AME
o AD MIN REGION TYPE AU THOR ITY
o AD MIN REGION TYPE D ESC
x
x
x
x
a
x
FEDERAL ELECTORAL DISTRICT
x
o FED ID
x
made up of
x
x
x
x
x
ONTARIO MUNICIPALITY
x
x
SURVEY COUNTY
x
x
x
x
UPPER TIER
MUNICIPALITY
x
SURVEY TOWNSHIP
Infrastructure
x
x
o LOT N UMBER
x
CENSUS DIVISION
CENSUS AREA
o CENSU S DIVISION ID
o CENSU S AREA ID
o CENSU S AREA TYPE
x
x
x
CENSUS SUBDIVISION
x
o CENSU S SUBDIVISION ID
x
x
SURVEY CONCESSION
x
x
x
LOWER TIER
MUNICIPALITY
x
SURVEY LOT
o LDU CODE
ONTARIO
x
x
Doing
Business
Differently
CAN POSTAL LDU
divided into
AREA
x
SINGLE TIER
MUNICIPALITY
o CONCESSION N UMBER
x
x
ENUMERATION AREA
o EA ID
forms
x
CONSOL M UNIC
SERVICE MGM T ARE
A
part of