What is it?
The Enterprise Architecture (EA) is akin to a city plan that lays out the street network, power grids and water system. It is the overarching framework for all computers, systems and information management that delivers the Government of Ontario programs and services electronically. The architecture will:
- set the standards for managing information and information technology
- identify technologies that work together and those that do not
- point out new opportunities presented by the common I&IT infrastructure
- contribute to I&IT security
- promote consistency in I&IT management and support
Why is it needed?
EA is the foundation for planning, coordinating and implementing information management and information technology across government. It will ultimately benefit taxpayers by helping the government:
- improve communications between business and IT stakeholders inside and outside the government
- upgrade access to information
- provide fully integrated customer-centred service delivery
- create an open, standard I&IT environment that is easy to maintain and to expand
- identify opportunities for business change
- gauge emerging technology on a timely basis
- establish productive relationships with vendors and partners
- shape an effective planning and management framework for all other I&IT architectures
- streamline and drive down administration costs
EA is making information technology a business and management tool that OPS employees can use to:
- plan and scope out projects and programs
- approach business and technical solutions using a common language and a common format
- determine what is needed by using gap analysis
- leverage resources
- link planning, policy planning and IT architecture
EA will also give the Corporate CIO, the Corporate Chiefs and the cluster CIOs the big picture on:
- the level of integration between IT and programs
- the level of alignment in the nine infrastructure projects
How is the Enterprise Architecture Used?
|
Centre of Excellence Projects - furthering the development of consistent, usable architecture and designs (progress updated regularly to Information Technology Executive Leadership Council [ITELC]) |
| FIS Project - underpinning in RFP, solution development and use of common infrastructure (e.g. common data elements) |
| Integrated Service Delivery (ISD) for Individuals - basis for conceptual architecture/Request for Procurement (RFP) I&IT requirements, tool to ensure vendor compliance to OPS standards |
| Land Resource Cluster (LRC) Water Program - basis of fundamental business re-engineering to meet priorities |
| Common Components and Common Data Elements development with clusters |
| Tools, education and shared experiences - promotion of re-use to clusters |
| Architecture governance - ensuring consistent, well-designed (heavy on re-use) and timely I&IT solutions through a comprehensive architecture review process that is a shared responsibility of corporate and clusters. |
How is it progressing?
The architecture is a "living architecture" that will be refined over time to ensure it is always business driven and aligned with important and emerging I&IT industry trends. The project plan has two main phases: conceptual architecture, which is completed, and logical/physical architecture, which is an ongoing refinement process. (Logical architecture refers to the relationship between different elements; physical architecture covers the selection of hardware and network equipment.)
| Activities to Date |
| Developed fundamental architectural principles and processes |
| Selected structured framework (Zachman) and process (MetaGroup) to guide further architectural development |
| Implementation of federated architecture and Information Technology Executive Leadership Council (ITELC) governance |
| Documented basic conceptual and logical models |
| Engaging business and program delivery staff in the EA process by demonstrating the business value of the EA |
| Working with key projects across the OPS |
| Working with partners in private industry, federal government, municipalities, provinces and states |
| Conceptual-level enterprise I&IT architecture approved by senior management |
| Privacy design principles approved |
| Data warehouse strategy approved |
| Next level refinement to set the framework for detailed project architectures and evolving architectures across the government |
| Refinement of logical/physical architecture |
What's coming up?
| Common Data Elements and standardized Extensible Markup Language (XML) schemas will be the lexicon to transfer information between the OPS and external partners/clients |
| Common Components will optimize the processing of payments, authentication and registration |
| Service definitions identify the opportunities for business re-engineering and to highlight where common data elements and components can be used in I&IT solutions |
| Continued communication sessions, such as the Architecture Open Houses & cluster sessions, to underline the use of the EA |
| Centre of Excellence Projects to investigate new innovations and opportunities. |
Where is it going?
Corporate and cluster architecture programs are continuing to actively consult with government business leaders to ensure their work meets diverse needs. It is also consulting with the broader public sector and industry associations to make sure the EA project takes into account industry and technology directions and is useful to all sectors that link with the Government of Ontario.
FAQ