Manitoba's Enterprise Architecture

A Framework for Managing Information Communication

Technologies for the Province of Manitoba

Dan KerrDirector

ICT ArchitectureProvince of Manitoba

David PrimmerChief Information OfficerProvince of Manitoba

Creating an ICT environment where technology is used to

achieve province wide objectives that support the government’s commitment to promote citizen

centric services to the direct benefit of Manitoba’s citizens

and businesses.

Goals for ICT

• More Accessible Government

• Support and Align

• Leverage Resources

• Protect Information

• Collaborate and Share

• Innovation and Economic Development

• Support Communities

Manitoba – At the Forefront of Innovation

Why we plan and need standards

Influences

Enterprise ArchitectureOutcomes

• Develop enterprise-wide standards, directions and processes based on industry generic standards and products where practical and possible.

• Implementation flexibility (application & Infrastructure) and protect Manitoba against unexpected changes in vendor strategies and capabilities.

• Implement content and knowledge management frameworks that address the creation, capture, maintenance, accessibility, dissemination, and use of information.

• Facilitate implementation in all areas of Government

Applies to?

• Manitoba Government All Departments, SOA’s and staff

• Vendors and contractors providing services and components to government (same as security policies apply today)

• Approach is extended to other public sector organizations

Current ICT Environment• 13,270 Users• 12,951 Email Accounts• 10,741 Desktop/Laptops• 3,123 Printers• 400+ Application Servers• 3000+ Departmental Applications

Application Development: Microsoft, Websphere, Oracle, Power Builder, +Distributed, Variety of Technologies

Centralized IT ServicesFile, Print, messaging, Security, Desktop, PDN

Hosted environmentsWebsphere, Internet, SAP, Citrix

EA Structure6 Domain Architectures

Guide ICT systems and service life cycles Guide ICT systems and service life cycles

that support program deliverythat support program delivery

EA Components• Security Architecture – Describes how ICT architectures are to be

designed to ensure that the government is protecting its information and IT system assets.

• Privacy Architecture – Describes how ICT systems must manage information that the government collects in order to comply with regulations and legislation.

• Data & Information Architecture - Describes how information collected is managed, and shared by applications.

• Application & Integration Architecture – Describes the architectures for the integration, development, and use of applications across government.

• Technical Architecture – Describes the design, selection, and implementation of the ICT hardware and software platforms and WAN/LAN network.

• ICT Service Management Architecture - Supports other ICT architectures by describing how ICT services and systems will be delivered and managed.

How was it developed?

• Cross Departmental working teams

• Industry input

• Based on best practices

• Modeled after similar jurisdictions

EA Document Structure

• Guiding Principles

• Goals

• Applied Principles

• Components/Elements

• Models

• Standards

• Links to appropriate repository information Decisions Technical Topics

Guiding Principals• Accommodate rapid change to government

programs and services.

• Facilitate legitimate access to information while providing strict control over the collection, management and security of this information.

• Support and encourage dialogue between citizens and government.

• Promote the accessibility and integration of government services by providing an enterprise view of services that cross organizational boundaries.

• Align with the program planning and delivery requirements of the government.

• Facilitate access to government services with a goal of “anywhere at any time.”

Applying the Guiding Principles• Build applications using open, portable, web-

enabling technology

• Re-use existing components & infrastructure

• Enterprise-wide standards and processes based on generic standards and products

• Use content and knowledge management frameworks

• Facilitate multi-channel access to services

• Integrate applications and implement data standards

• Apply appropriate technology and training

• Align investment decisions based on priorities

• Ubiquitous and consistent delivery of information systems to users

Implications• Change in scope of projects• Player in larger group - part of a team• Changes process, thinking, approach• Your work will impact others• Increased inter-dependencies• Reduce technologies and products• Provide models to work from• Selective introduction of new technologies and

approaches• Focus on solutions• No need to start from scratch• Collaboration and Consistency

What’s in it?

ASSETS

Vulnerabilities Threats

Risk

Countermeasures

Residual Risk

Acceptance

• Common terms

• Definitions

• Models

• Principles

• Standards

User Interface / Device Tier

Presentation Tier

Application Tier

Information Model Tier

browser J2MESwing, AWT

JSP Servlets

EJB session beans

browserWindows CE .Net

ASP.Net

.Net Managed Class

EJB entity beans

ADO.Net

Windows client

J2EE Componentry .Net Componentry

Application Classification

Enterprise

Departmental

Personal

IMPACT

RISK

Class2

Class3

Public

Class1

Based on Risk & Impact

Classification & Standards

• Class 1 uses Class 1 technology, support, languages, infrastructure etc.

• Class 2&3 – Class 2, 3 as appropriate

System Deployment ReadinessSystem Deployment Readiness

Class 3

Class 2 Class 2

System Environment GridDevelopment Testing Production

Class 1 Class 1 Class 1

Unit testingNaming and Coding StandardsCode Metrics

Function, System, Regression, Load, Stress, Performance, User Acceptance

Service Level MetricsResponse Time MetricsFailover and Recovery TestsA

PP

LIC

AT

ION

CL

AS

SIF

ICA

TIO

N

Standards & LifecycleThe relationship between standards categories, the life cycle of standards and the technologies that are organized within the cube.Baseline - technologies and processes that are currently

in use and endorsed.Emerging - technologies and processes that may meet

long-term strategic direction and may or may not be integrated into the target architecture.

Containment - technologies and processes that should only be targeted for limited investment (e.g. maintenance)

Retirement - technologies and processes that have targeted for retirement from production and should not be included in current or future development.

Emerging

RetirementContainment

BaselineGeneric Specification

IndustryProtocol

Custom Produce

Types of Standards

• Industry

• Generic

• Custom

These may be further qualified into: Products Protocols Specifications

Emerging

RetirementContainment

BaselineGeneric Specification

IndustryProtocol

CustomProduce

Domain Sub-Domain Standards

Class Baseline Containment Retirement Emerging

Application Server

Web Application Manager

Industry Product

1/2

IBM WebSphere

Oracle Forms Server[1]

None Identified

Tomcat; jBOSS; MS .NET EnterpriseASP.NET

Application Server

TP Monitor Industry Product 1/2

WebSphere Application Server

Microsoft Transaction Server; IBM CICS; IMS

None Identified

.Net Enterprise Services

Application Server

Web Server Industry Product 1/2

IBM HTTP Server; Apache

MS IIS None Identified

None Identified

Application Server

Web Server Industry Product

2

Apache MS IIS None Identified

None Identified

Key Directions

• Moving to J2EE and Microsoft .NET application environments for new development

• Maintaining Notes, PowerBuilder• Common application development

environment, tools• Open Source where appropriate

Apache, MySQL, Linux, Eclipse

• Service Oriented Architecture

Central ServicesServerSupport

Transformation - The Future

Multiple environments technologies, supports

Channels

PortalPresentation Personalization

Electronic Service DeliveryE-Commerce Help Desk

CRMCase

Management

DocumentManagement

Imaging

Document Handling

Security Services

Digital Rights Mgmt

Security Protocols

Single Sign on

PKI

Threat & IntrusionIdentification

Integration & Collaboration ServicesMetadata

Enterprise App’nIntegration

Collaboration

Workflow

Web Services

ApplicationServices

Software Dev’tTools

Process Modeling

Component Repository

KnowledgeManagement

e-Learning

Corporate Knowledge

Content Management

Data Warehouse/MartIT ServiceManagement

InfrastructureManagement

Key PerformanceIndicators

Decision SupportSystems

Infrastructure ServicesNetworks

Central Storage

File

Print

Email

Wireless

Desktops

Servers

ERP/SAPFinancial Mgmt

HR Management

Manitoba’s ICT Services Map

ICT Roadmap

Organization Departmental Focused ICT

Shared Corporate Infrastructure

ICT Organization Consolidation

Service Organization

Architectural Direction

Solution Based Architecture

Desktop Arch, Security (IPC)

Enterprise Architecture

Service Oriented Architecture

Application Dev & Management

Departmental Focus & Access

BSI, ESM & Departmental Focus

Shared Standardized Process’s & Tools

Centres of Excellence

Infrastructure & Network

Heterogeneous, Variety of Technologies

Standardized File, Print, Email, PDN

VPN, SAN, Server Consolidation

Virtual, Hosted Apps, Standards Based

Governance, Direction & ICT Strategy

Departmental ICT Planning

Internal Focus, Standardization

Reduce Costs, Link to business

Outward focus, Service Quality, Integrated Del

1997 2003 2005 2007

Manitoba Information and Communications Technologies

QUESTIONS

http://www.gov.mb.ca/est/mict/index.html