"eGovernment Enabling Electronic Service Delivery with XML and"
Our People Government for the 21st Century eGovernment: Enabling Electronic Service Delivery with XML and Common Data Elements Doing Business Differently Presented to IRMAC, Jan. 16, 2002 Dave Wallace & Alana Boltwood Infrastructure Office of the Corporate Chief Strategist Management Board Secretariat Government of Ontario 2 Our People Agenda • The Challenges of E-Government Government for the 21st Century • Why XML? • Ontario‟s Approach to Derive XML Doing Standards Business Differently • Common Data Elements • Putting It All Together • Next Steps Infrastructure 3 Our People Strategic Direction: E-Government Government for the 21st Century • In March 2000, in approving its Digital Economy Strategy, the Ontario Government approved electronic government as a priority Doing Business Differently • The plan is to demonstrate leadership by example in electronic government and more Infrastructure specifically, electronic service delivery 4 Our People The E-Government Context Government for the 21st Century Citizen Engagement Integrated Service Delivery (ISD) Enabling two-way public Providing Ontario services over the interaction counter and electronically to individuals and businesses Doing Business Sectoral Reform Differently Using I&IT to drive and enable sectoral reform Electronic Service Delivery (ESD) Providing services electronically to our clients Corporate Systems and Enablers Enterprise Resource (HR and Financial) Systems and Infrastructure e-commerce processes Common I&IT Infrastructure Underlying technology to support both enterprise-wide and business specific applications 5 Our People Strategic Vision and 2003 Target for Electronic Service Delivery (ESD) Government for the 21st VISION Century • Improve service quality to Ontario‟s people and businesses by implementing client-focused, integrated, accessible and cost-effective electronic Doing services by the OPS Business Differently 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 Infrastructure includes all electronic channels) 6 Our People Implications in Ontario • We know we have much to do to provide Government for the 21st Century leadership for Ontario‟s success in the global Digital Economy – E-Business (e.g. removal of barriers/supportive Doing Business environment) Differently – E-Government (e.g. sectoral transformation, ESD, internal admin., digital democracy) – individual, business, sector, institutional Infrastructure 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 Infrastructure We also need to share experiences and learn from each other about best practices in e-government and ESD 8 Our People But what does this mean to Information and Government for the 21st Information Technology Century (I&IT)? Doing Business Differently Infrastructure 9 Our People Going “E” By 2003 means... • Business transformation projects must be Government for the 21st Century delivered • Time to Market is critical • Collaboration and commitment are key Doing success factors • Quality, effective results are essential to Business Differently meet the government‟s vision for 2003... Infrastructure 10 Our People But Not With Just Technology Government • E-Government and ESD cannot succeed for the 21st Century without a “common language” • Ontario‟s strategy is dependent on Doing Business Information Management (IM) as the basis Differently 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 • XML is a set of rules, guidelines and Century conventions for designing text formats for such data, in a way that produces files that are easy to generate and read (by a Doing computer) Business Differently • XML text formats are unambiguous, avoiding common pitfalls such as lack of Infrastructure extensibility, lack of support for internationalization/localization, and platform-dependency 12 Our People Leading Edge IM is Counting on XML Government • W3C XML schema Standards for the 21st Century (http://www.w3.org/XML/) • US, UK and EU have developed or are developing IM based interoperability frameworks for E- Government Doing Business Differently • Private Sector Standards nearing maturing for: – Business to Consumers (Customer Profile, name & addressing, etc…) – Business to Businesss (Invoices, Purchase Orders, Contracts, etc…) Infrastructure • Next generation interoperability standards emerging; for example, ebxml is setting standard for seamless electronic business through XML 13 Our People But Why XML? • XML provides the “language” for the Common “I” in Government for the 21st Common Information & Information Technology (I&IT) Century • Setting standards for common data elements and common meta data now will: Doing – enable enterprise wide integration and navigation in the future Business Differently – 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 Infrastructure specific extensions to the provinces IM framework • XML is ready for prime time 14 Our People Why XML (continued) • The province has several lines of business. Health, Education, Transportation… Government for the 21st • Each of these “communities of interest” has significant XML Century standards development initiatives underway. • If the province is to: – Retain the capacity to have an enterprise view of its information and transaction offerings, Doing – Establish a scalable foundation upon which individual ministries can Business Differently “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 Infrastructure 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 – Define data messaging standards for the province‟s Government for the 21st Common I & IT gateway Century • Medium Term – Provide an standards based means for capturing, classifying and transforming data – Establish application independent data Doing Business – Establish device and platform independent solutions Differently – Provide a standards based transformation engine for re- engineering • Long Term – Enable „plug and play‟ where government transactions and Infrastructure 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 • Transformations from standardized messaging Government for the 21st language to program-ready data is the responsibility Century 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 Messaging Mark-up • Govtalk in the UK and EBXML in the private sector are establishing interoperability frameworks for the B2B and public Government for the 21st sector environment by establishing transformation solutions Century between existing standards and hoping that common data standards will emerge through the development of on-line service delivery applications Doing Business • These interoperability efforts are enabled by moving to one level Differently of abstraction in the document type definitions (establishing generic schemas) and conducting XSLT transformations between systems • Ontario has different approach - using Common Data Elements Infrastructure (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 IM is Critical to Meeting the 18 Challenges of ESD Government for the 21st • Data and information are seen as corporate assets Century in the Ontario Government, with custodianship in program areas Doing • Ontario‟s Enterprise Architecture has standardized Business Differently definitions of common data elements (CDE) which have been developed to foster sharing and re-use when appropriate Infrastructure • The XML schema of Common Data Elements is key to Ontario‟s ESD strategy 19 Our People Integrated Information Project • The Integrated Information Project will Government for the 21st Century help the government of Ontario manage the information it gathers efficiently and in compliance with Doing Business privacy legislation. It will also enhance Differently information sharing across government which will improve decision-making and contribute to Infrastructure improved services. 20 Our People Integrated Information Project: Government for the 21st Common Data Elements Model Century • Identify data that is “common” across ministries Doing Business • Develop a conceptual framework for these Differently elements • Establish standard definitions • Create template for system design Infrastructure • Build XML schemas based on CDEModel 21 Our People Benefits of CDEModel People use same People Government meaning of words communicate well for the 21st Century Reuseable data model components Doing Save time & Business Generic and Reuseable money in system Differently standard data application life cycle, and model components improve service delivery Easy integration of systems Infrastructure Data model for Single Common Data authoritative Elements source for Repository common data 22 Our People Approach for Developing Common Data Elements Government for the 21st Century • A government oriented contextual enterprise information model has been created that has: a generic conceptual data model that is Doing Business Differently applicable to all government computer applications; subject areas that are common; Infrastructure a formal information taxonomy; core common data elements. 23 Our People Government Information Context Model Context Information Model Business Sectors Government Responsible Gov ernment for the 21st Century Stewardship Inf rastructure, Resources, Inform ation and Env ironmental Well- being Groupings Doing Vibrant Communities Business Differently Learning, Wellness, and Economic Social Self -Reliance Responsibility Saf e and Just Social Competitiv e Ontario Env ironment 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 From Context to Conceptual Model Core Goals and GO Government Businesses provide framew ork Strategies Organizations for for the 21st (C6-Why) (C6-Why) (C4-Who) Century define nature of respon- administer sible for Rules define Programs (C6-Why) terms of (C2-How) Resources (C1-What) fund constrain delivery of Services found at Business determine (C2-How) Cycles Doing (C5-When) timing of Business provided at Locations trigger (C3-Where) Differently delivery of Business address Events provided by (C5-When) impact Needs (C6-Why) Stakeholders experienced Partners (C4-Who) by (C4-Who) are involved Organizations Clients as (C4-Who) Infrastructure (C4-Who) deliver services as receive services as Individuals (C4-Who) 25 Our People Identification of Common Elements Government Core Goals and GO for the 21st Businesses provide framework for Strategies Organizations (C6-Why) (C6-Why) (C4-Who) Century define nature of respon- sible for administer A conceptual data model Rules (C6-Why) define terms of Programs (C2-How) defines the high level Resources constrain delivery of fund (C1-What) entities and the type of Business determine Services (C2-How) found at relationships between Cycles timing of Doing Business (C5-When) trigger provided at Locations (C3-Where) them. Any public sector Differently Business delivery of address computer application can Events provided (C5-When) Needs (C6-Why) by impact use this model to begin experienced Stakeholders (C4-Who) design and development. Partners by (C4-Who) Entities hi-lighted in red are involved Organizations Clients (C4-Who) deliver as (C4-Who) are common and thus services as Infrastructure receive services as form the basis for defining Individuals (C4-Who) common data elements. 26 Our People Logical Data Model of Common Data Elements ORGANIZATION MEMBERSHIP ADMIN UNIT MEMBERSHIP * MEMBERSHIP START DATE * MEMBERSHIP START DATE o MEMBERSHIP END DATE o MEMBERSHIP END DATE This example is a Government in includes includes in for the 21st PARTY data model of the # PARTY SEQ ID member of member of Century * PARTY TYPE o PREFERRED OFFICIAL LANGUAGE TYPE INDIVIDUAL o o OFFICIAL FIRST NAME OFFICIAL MIDDLE NAME common data o OFFICIAL LAST NAME INFORMAL GROUP MEMBERSHI P o o o o o PREFERRED GIVEN NAME PREFERRED MIDDLE INITIALS NAME PREFERRED LAST NAME HONORIFIC TYPE SUFFIX NAME elements # MEMBERSHIP START DATE o FORMER LAST NAME associated with includes o MEMBERSHIP END DATE o BIRTH DATE belongs to o DEATH DATE o MARITAL STATUS TYPE o GENDER TYPE “Individuals” and divided into INFORMAL GROUP in o GROUP NAME belongs to “Organizations”. includes includes includes Doing ROLE TYPE # ROLE TYPE * ROLE NAME LEGAL ORGANIZATION * * REGISTRATION NUMBER LEGAL NAME ADMINISTRATIVE ORGANIZATION UNIT * ROLE DESC o BUSINESS NAME Business o o o BUSINESS REGISTRATION STATUS TYPE ACTIVITY CLASSIFICATION CODE ACTIVITY DESC divided into divided into Differently describes NON-GO ORGANIZATION belongs to NON-GO ORG ADMIN UNIT o ADMIN UNIT NAME belongs to divided into type of belongs to PARTY ROLE # START DATE divided into o END DATE role played by GO ORGANIZATION DEPARTMENT involved as * COMMON ENGLISH NAME * DEPARTMENT ENGLISH NAME o COMMON FRENCH NAME o DEPARTMENT FRENCH NAME belongs to * ENGLISH ABBR divided into * DEPARTMENT ENGLISH ABBR o FRENCH ABBR o DEPARTMENT FRENCH ABBR involved in involved in belongs to from to PARTY RELATIONSHIP # RELATIONSHIP START DATE o RELATIONSHIP END DATE Infrastructure type of describes Development of a full logical data model of all common RELATIONSHIP TYPE # RELATIONSHIP TYPE * RELATIONSHIP NAME * RELATIONSHIP DESC data elements produces the standardized definitions and relationships needed to facilitate effective sharing and integration of common data. 27 Our People Service Delivery Infrastructure Management Logical Model • CDE and common components will form the Government for the 21st Century foundation of the ESD infrastructure for the Ontario Government Doing Business Differently • CDE will be the basis for service delivery markup Infrastructure • The service delivery information management logical model is the blueprint for the project 28 Our People Service Delivery Mark-up • In order to build channel independent services ESD will need Government standardized service delivery components driven by XML for the 21st Century • These components will define: – Prompts for questions asked – Service and field specific help – Links to related decision support materials and enabling legislation Doing – Contact information for alternative channels Business Differently – 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 Infrastructure programs/jurisdictions Our People Government for the 21st Century How CDEs and XML deliver Doing E-Government services Business Differently Alana Boltwood Infrastructure 30 Our People How CDEs and XML deliver E-Government services Government for the 21st CDEModel Century Implemented as Implemented as CDESchema (XML datatypes) Doing Business Ontario Service Shown to users as Differently Description Markup Data model for Language schema Transaction Defines user interface of Building Block Common Defines user Describes interface of Component Infrastructure Called by Service Transaction 31 Our People Levels of CDE Model • Government Information Context Government for the 21st Century • Conceptual: Business understanding Doing Business Differently • Logical: Standard template for system design (requires further transformation for RDBMS implementation) Infrastructure 32 Our People CDEM Subject Areas • Party: individual, organization; party roles Government for the 21st Century (client, partner, stakeholder, employee, etc.) • Addresses and geography Doing • Finance: accounts, transactions Business Differently • Service Operation: program, service, transaction, process • Motivation: goal, strategy, client need, law, Infrastructure contract, performance metric • Time: business event, business cycle • Resources 33 Our People Conversion to XML Schemas • CDE logical model is implemented as Government for the 21st Century XML Schema datatypes – Party, Address, Finance in CDESchema – Service Operation, Motivation, Time in Doing Business Ontario Service Description Markup Differently Language (OSDML) • Rules established for the conversion, via Infrastructure a metamodel 34 Our People Transaction Building Blocks • Common Data Elements Model is a logical Government for the 21st Century model template for system design • Need a set of “building blocks” for application user interfaces, based on CDEM Doing Business Differently • Building blocks are generic pieces of a form (electronic or paper) • Examples: Person name; organization Infrastructure name; home phone number; business fax number; mailing address; email address; birthdate; height & weight 35 Our People Governance and Plans • Research each subject area Government for the 21st Century • Ministry representatives review CDEM and XML schemas Doing • Approval as an Ontario Government Business Differently architecture standard • Share model and schemas with other governments, via Public Sector CIO Council Infrastructure 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 Fax for the 21st Content Management Century SDML (Service Delivery Businesses Markup Language) Within the enterprise Cluster B Call Center Defined Service Cross Site/Program Domain Citizens Navigation & Specific XML Messaging Searching XML Messaging Counter Schemas Environment Doing Cluster C CDEM Business (CDE Model) Differently Employees Internet Forms Management Schemas CDEM (CDE Model) Programs & Services Catalogue/Directory Cluster D Future CDER Service XML Definition of Service (CDE Repository) Delivery Infrastructure Devices Integrated Services Common Components Context Management 38 Our People Next Steps • In order to implement the services delivery Government for the 21st Century logical model in a timely fashion, concurrent streams will be done Doing Business Differently • The development plan calls for coordinated: – Communications – Proof of concept development – Schema development Infrastructure – Transformations development – Registry/repository development – Training 39 Our People Questions? Feedback? Government for the 21st Century Corporate Architecture Branch Management Board Secretariat Doing email@example.com Business Differently 416-327-4108 firstname.lastname@example.org 416-327-0313 Infrastructure email@example.com 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 GO ORGANIZATION CLIENT PARTNER Century (OPS) (Recipient) (Provider) Address Ministry Employee Person Area Cluster Person Group Geo-spatial Agency Group Private Sector Mobile Board Private Sector Public Sector Doing Office Public Sector Business Commission Differently Council Institution Foundation Association Center Administrative Authority Infrastructure Sector 42 Our People Defining Data Elements for Sharing Government for the 21st Comparative Example Century Free Definition Fixed Definition Name Location Name Location Smith, John 123 Albert Street Sarnia John Smith 123 Albert Street Sarnia John Smith Doing Albert Street North Sarnia Business J Smith Differently 123 Albert Street Common Data Elements can be used to structure data to make sharing and use of information more effective and efficient Free definitions make input variable and limit use and sharing Infrastructure information 43 Our People LOCATION DESCRIPTION Building Block o LOCATION TYPE o DATA QUALITY DESC VIRTUAL LOCATION DESC Example Government o TECHNOLOGY TYPE for the 21st Century TELECOMM NUMBER o COUNTRY CODE Building Blocks o AREA CODE o LOCAL NUMBER o EXTENSION NUMBER o SPECIAL INSTRUCTIONS DESC Daytime Phone Number AreaCode + LocalNumber + ExtensionNumber CDEM Doing Business CountryCode = 1 (North America), TimeType = Day, Differently TechnologyType = Telephone used for International Home Phone Number usage of CountryCode + AreaCode + LocalNumber PARTY LOCATION ROLE ContactPurposeType = Personal, TechnologyType = Telephone o CONTACT PURPOSE TYPE Infrastructure o DELIVERY TYPE o TIME TYPE o SEASON TYPE o PERMANENCY TYPE Business Fax Number o VALID FROM DATE o VALID TO DATE CountryCode + AreaCode + LocalNumber o OFFICE NAME ContactPurposeType = Business, TechnologyType = Fax 44 Our People What‟s in a building block • Prompts (English, French) for entire BB and Government for the 21st Century each element/attribute in the BB • 1 or more CDEM entities Doing • Restrictions: selection of attributes, default Business Differently values for non-selected attributes • Extensions (additional attributes) • Attribute length, datatype, optionality, Infrastructure ordering • Actions 45 Our People CDEM content • Some draft models follow. None have been Government for the 21st Century approved yet as a Government of Ontario standard, and some are still being researched. Doing Business Differently Infrastructure 46 Our People Party ORGANIZATION MEMBERSHIP * MEMBERSHIP START DATE o MEMBERSHIP END DATE in includes ADMIN UNIT MEMBERSHIP * MEMBERSHIP START DATE o MEMBERSHIP END DATE includes in (Logical) PARTY # PARTY SEQ ID * PARTY TYPE o PREFERRED OFFICIAL LANGUAGE TYPE member of INDIVIDUAL member of o OFFICIAL FIRST NAME o OFFICIAL MIDDLE NAME o OFFICIAL LAST NAME o PREFERRED GIVEN NAME Government INFORMAL GROUP MEMBERSHI o o o PREFERRED MIDDLE INITIALS NAME PREFERRED LAST NAME HONORIFIC TYPE for the 21st P # MEMBERSHIP START DATE includes o o SUFFIX NAME FORMER LAST NAME o MEMBERSHIP END DATE o BIRTH DATE Century belongs to o o DEATH DATE MARITAL STATUS TYPE o GENDER TYPE divided into INFORMAL GROUP in o GROUP NAME belongs to includes includes includes ROLE TYPE LEGAL ORGANIZATION ADMINISTRATIVE ORGANIZATION UNIT # ROLE TYPE * REGISTRATION NUMBER * ROLE NAME * LEGAL NAME * ROLE DESC o BUSINESS NAME o BUSINESS REGISTRATION STATUS TYPE Doing o o ACTIVITY CLASSIFICATION CODE ACTIVITY DESC divided into divided into Business describes NON-GO ORGANIZATION NON-GO ORG ADMIN UNIT Differently belongs to o ADMIN UNIT NAME belongs to divided into type of belongs to PARTY ROLE # START DATE divided into o END DATE role played by GO ORGANIZATION DEPARTMENT involved as * COMMON ENGLISH NAME * DEPARTMENT ENGLISH NAME o COMMON FRENCH NAME o DEPARTMENT FRENCH NAME belongs to * ENGLISH ABBR divided into * DEPARTMENT ENGLISH ABBR o FRENCH ABBR o DEPARTMENT FRENCH ABBR involved in involved in belongs to from to PARTY RELATIONSHIP # RELATIONSHIP START DATE Infrastructure o RELATIONSHIP END DATE type of Within GO Organization, Non-GO Organization, Admin Org Unit and Party Role there are subtypes describes RELATIONSHIP TYPE not shown. # RELATIONSHIP TYPE * RELATIONSHIP NAME * RELATIONSHIP DESC TELECOMMUNICATION ADDRESS 47 Our People INTERNET ADDRESS # INTERNET ADDRESS SEQ ID * URL DESCRIPTION PARTY # PARTY SEQ ID * PARTY TYPE involved as PARTY ROLE # START DATE o END DATE o URL NUMERIC DESCRPTION o PREFERRED OFFICIAL LANGUAGE TYPE role played by TELECOMMUNICATION TYPE located at type of describes # COMMUNICATION TYPE CODE TELEPHONE ADDRESS located at * COMMUNICATION TYPE DESC used by described by # TELEPHONE SEQ ID * AREA CODE describes * TELEPHONE NUMBER o ALPHANUMERIC TELEPHONE NUMBER o EXTENSION NUMBER ROLE TYPE reachable in # ROLE TYPE * ROLE NAME * ROLE DESC EMAIL ADDRESS available at available for available for # EMAIL ADDRESS ADDRESS GROUP described by ADDRESS GROUP TYPE # ADDRESS GROUP SEQ ID # ADDRESS GROUP TYPE CODE * ADDRESS GROUP NAME describes * ADDRESS GROUP TYPE DESC ADDRESS/ COMMUNICATION USAGE # START DATE o END DATE composed of o TIME PERIOD TYPE CODE * EFFECTIVE DATE o EXPIRY DATE o INVALID ADDRESS INDICATOR o INVALID ADDRESS DATE Government location for part of Canadian Address LOCATION ADDRESS available at available at described by COUNTRY for the 21st # COUNTRY CODE * COUNTRY NAME * TELECOMM COUNTRY CODE contains lies in # ADDRESS SEQ ID o DIRECTIONS COMMENT mailing location for CANADIAN AND USA ADDRESS Century o ADDITIONAL ADDRESS INFORMATION COMMENT physical location for describes ADDRESS/ COMMUNICATION ROLE describes NON-SURVEY ADDRESS # ADDRESS ROLE CODE STREET TYPE o BILINGUAL INDICATOR # TEMPORARY INDICATOR # STREET TYPE CODE * MAILING CODE * ROLE DESC o LANGUAGE CODE * STREET TYPE NAME * VALID CANADA INDICATOR typed by CIVIC ADDRESS main info for o DIRECTION PREFIX/SUFFIX CODE MAILING CIVIC ADDRESS ADDRESS UNIT included in STREET * CIVIC NUMBER secondary info for describes # UNIT SEQ ID # STREET SEQ ID o CIVIC NUMBER SUFFIX described by * UNIT DESCRIPTION * STREET NAME PHYSICAL CIVIC ADDRESS additional typed in US only by secondary info for describes typed by described by included in STREET DIRECTION TYPE # STREET DIRECTION TYPE CODE ROUTE CIVIC ADDRESS describes * ROUTE SERVICE ID * STREET DIRECTION TYPE NAME MAILING ROUTE CIVIC ADDRES S ADDRESS UNIT DESIGNATOR TYPE # UNIT DESIGNATOR TYPE CODE describes PHYSICAL ROUTE CIVIC * UNIT DESIGNATOR TYPE DESC typed by ADDRESS US ROUTE ADDRESS * VALID CANADA INDICATOR o DIRECTION PREFIX/SUFFIX CODE * BOX ID described by * CIVIC NUMBER o CIVIC NUMBER SUFFIX CAN ROUTE ADDRESS deliv. responsibility of ROUTE SERVICE TYPE describes o SITE ID # ROUTE SERVICE TYPE CODE o COMPARTMENT ID Doing COUNTRY SUBDIVISION # COUNTRY SUBDIVISION CODE * ROUTE SERVICE TYPE NAME * VALID CANADA INDICATOR described by responsible for DELIVERY INSTALLATION contains Business * * o COUNTRY SUBDIVISION TYPE COUNTRY SUBDIVISION NAME SEQUENCE NUMBER lies in MAILING GENERAL DELIVERY ADDRESS # DELIVERY INSTALLATION SEQ ID * DELIVERY INSTALLATION AREA NAME o DELIVERY INSTALLATION QUALIFIER NAME described by describes DELIVERY INSTALLATION TYPE # DELIV INSTALL TYPE CODE * DELIV INSTALL TYPE NAME Differently contains US GENERAL DELIVERY ADDRESS CAN GENERAL DELIVERY deliv. responsibility of ADDRESS responsible for responsible for contains URBAN UNIT # URBAN UNIT SEQ ID lies in * URBAN UNIT NAME MAILING POST OFFICE BOX ADDRESS contains contains contains * POST OFFICE BOX ID CONCESSION/ PLAN part of # CONCESSION/ PLAN SEQ ID deliv. responsibility of * CONCESSION/ PLAN NUMBER US PO BOX ADDRESS CAN PO BOX ADDRESS part of divided in GEOGRAPHIC divided in TOWNSHIP # GEO TOWNSHIP SEQ ID divided in part of * GEO TOWNSHIP NAME main info for LOT/ PART at ONTARIO PHYSICAL SURVEY ADDRESS part of # LOT/ PART NUMBER location of part of INTERNATIONAL ADDRESS * ADDRESS LINE 1 o ADDRESS LINE 2 o ADDRESS LINE 3 Infrastructure o MAILING CODE PHYSICAL INTERNATIONAL MAILING INTERNATIONAL Address lies in ADDRESS ADDRESS lies in US MILITARY "STATE" # MILITARY "STATE" CODE OVERSEAS US MILITARY ADDRESS * MILITARY "STATE" NAME * DELIVERY ADDRESS LINE * MILITARY DESIGNATION CODE * ZIP CODE (Logical) 48 Our People Service Operation, Motivation, Time (Conceptual) MOTIVATION SERVICE delivered as SERVICE DELIVERY Government RULE constrain delivery of instance of EVENT triggers FINANCIAL constrained by TRANSACTION for the 21st STATUTE REGULATION AGREEMENT PUBLIC SERVICE triggered by Century CONTRACT define terms of EA PROGRAM BUSINESS RULE regulated by INTERNAL SERVICE x BUSINESS EVENT x triggered by AGENT OF CHANG trigger delivery of impact E groups CORE BUSINESS affected by belongs to framework for part of accomplished by PUBLIC GOAL PROGRAM GOAL specified by includes aligns with x x OUTCOME GOAL STRATEGY BUSINESS CYCLE used to achieve defines scheduled by determine timing of Doing IMPACT GOAL x Business PERFORMANCE METRIC x measures part of Differently is to satisfy/address evaluated by PROCESS satisfied/addressed by broken into NEED SERVICE PROCESS broken down into x part of experienced by ORG OPERATION PROCESS benefits delivered through owned by RESOURCE MANAGEMENT PROCESS PARTY ROLE has a vested interest in experiences receives accountable for STAKEHOLDER includes Infrastructure TARGET GROUP CLIENT SERVICE OWNER x belongs to SERVICE DELIVERY CHANNEL includes INTERESTED COLLABORATOR accountable to GOVERNOR PARTY x PARTNER SUPPLIER CLIENT AGENT belongs to AGENT PARTY OTHER PARTY involved as ROLE role played by 49 Our People CDEM 1.5: Geographic Areas GEOGRAPHIC AREA o OFFICIAL NAME * COMMON ENGLISH NAME o COMMON FRENCH NAME THREE-D GEO AREA * GEO AREA TYPE o BOUNDARY FILE o MAP IMAGE SURFACE AREA Government CONTINENT COUNTRY COUNTRY SUBDIVISION for the 21st x o o ISO CODE FLAG IMAGE divided into o ISO CODE contains POSTAL CITY x o INTERNET COUNTRY DOMAIN part of part of Century o TELECOMM COUNTRY CODE US STATE * STATE CODE OTHER SUBDIVISION * SUBDIVISION TYPE CANADIAN PROVINCE CAN POSTAL 1ST CAN POSTAL FSA CAN POSTAL LDU * PROVINCE CODE divided into LETTER divided intoAREA divided intoAREA * SUBDIVISION TYPE OTHER o FIRST LETTER CODE o FSA CODE o LDU CODE * STATCAN CODE PROVINCE part of part of part of ONTARIO RIDING ONTARIO x x divided into defined as part of ADMINISTRATIVE REGION TYPE ADMINISTRATIVE REGION x o ADMIN REGION TYPE NAME x o ADMIN REGION TYPE AUTHORITY o ADMIN REGION TYPE DESC x x a CONSOL MUNIC Doing FEDERAL ELECTORAL DISTRICT x x SERVICE MGMT ARE A o FED ID Business x Differently made up of x x x x x ONTARIO MUNICIPALITY x x x x SURVEY COUNTY UPPER TIER CENSUS DIVISION CENSUS AREA x MUNICIPALITY x o CENSUS DIVISION ID o CENSUS AREA ID o CENSUS AREA TYPE x x x x x x x SURVEY TOWNSHIP LOWER TIER CENSUS SUBDIVISION Infrastructure x x MUNICIPALITY x x o CENSUS SUBDIVISION ID x x x x SINGLE TIER SURVEY LOT SURVEY CONCESSION MUNICIPALITY o LOT NUMBER x o CONCESSION NUMBER x x ENUMERATION AREA o EA ID forms