Transcript Government Challenges & the Drivers for Change

Manitoba's Enterprise Architecture
A Framework for Managing Information
Communication Technologies for the
Province of Manitoba
David Primmer
Chief Information Officer
Province of Manitoba
Dan Kerr
Director
ICT Architecture
Province 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 Architecture
Outcomes
• 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 Services
File, Print, messaging, Security, Desktop, PDN
Hosted environments
Websphere, Internet, SAP, Citrix
EA Structure
6 Domain Architectures
Guide ICT systems and service life cycles
that 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, webenabling 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?
• Common terms
• Definitions
• Models
User Interface / Device Tier
browser
• Principles
• Standards
Swing,
AWT
J2ME
browser
Windows
CE .Net
Presentation Tier
JSP
ASP.Net
Servlets
Application Tier
ASSETS
EJB
session
beans
Vulnerabilities
.Net Managed
Class
Threats
Information Model Tier
Risk
EJB
entity
beans
J2EE Componentry
Countermeasures
Residual Risk
Acceptance
ADO.Net
.Net Componentry
Windows
client
Application Classification
Based on
R
I
S
K
Risk & Impact
Class
1
Enterprise
Class
2
Public
Class
3
Departmental
Personal
I
M
P
A
C
T
Classification & Standards
Class 1
APPLICATION CLASSIFICATION
• Class 1 uses
Class 1
technology,
support,
languages,
infrastructure
etc.
• Class 2&3 –
Class 2, 3 as
appropriate
Class 1
Class 2
Class 1
Class 2
Class 3
Unit testing
Naming and
Coding
Standards
Code Metrics
Function,
System,
Regression,
Load, Stress,
Performance,
User
Acceptance
Service Level
Metrics
Response Time
Metrics
Failover and
Recovery Tests
System Deployment Readiness
Development
Testing
Production
System Environment Grid
Standards & Lifecycle
The relationship between
standards categories, the life cycle
of standards and the technologies
that are organized within the cube.
Custom
Industry
Generic
Produce
Protocol
Specification
Baseline
Containment
Retirement
Emerging
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.
Types of Standards
Custom
•
Industry
•
Generic
•
Custom
Industry
e
Generic
l
Specification


Products
Protocols
Specifications
Protoco
Baseline
Containment
Retirement
Emerging
These may be further qualified into:

Produc
Sub-Domain
Standards
Web
Application
Manager
Industry
Product
Application
Server
TP Monitor
Industry
Product
Application
Server
Web Server
Industry
Product
Application
Server
Web Server
Industry
Product
Baseline
Containment
Retirement
IBM
WebSphere
Oracle Forms
Server[1]
None
Identified
Tomcat;
jBOSS;
MS .NET
Enterprise
ASP.NET
WebSphere
Application
Server
Microsoft
Transaction
Server; IBM
CICS; IMS
None
Identified
.Net
Enterprise
Services
IBM HTTP
Server;
Apache
MS IIS
None
Identified
None
Identified
Apache
MS IIS
None
Identified
None
Identified
1/2
Application
Server
Class
Domain
Emerging
1/2
1/2
2
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
Transformation - The Future
Multiple environments
technologies, supports
Support
Server
Central Services
Manitoba’s ICT
Services Map
Channels
Application
Services
Software Dev’t
Tools
Portal
Presentation
Personalization
Document
Management
Electronic Service Delivery
Process Modeling
e-Learning
E-Commerce
Help Desk
Imaging
CRM
Case
Management
Document Handling
Component
Repository
Knowledge
Management
Corporate Knowledge
Content Management
Security Services
IT Service
Management
Digital Rights Mgmt
Single Sign on
Infrastructure
Management
Security Protocols
PKI
Data Warehouse/Mart
Threat & Intrusion
Identification
ERP/SAP
Key Performance
Indicators
Integration & Collaboration Services
Metadata
Decision Support
Systems
Financial Mgmt
Collaboration
Web Services
Enterprise App’n
Integration
HR Management
Workflow
Infrastructure Services
Email
Desktops
Networks
File
Wireless
Servers
Central Storage
Print
ICT Roadmap
1997
Governance, Direction
& ICT Strategy
Organization
Departmental ICT
Planning
Departmental
Focused ICT
Architectural
Direction
Solution Based
Architecture
Application Dev &
Management
Departmental Focus &
Access
Infrastructure &
Network
Heterogeneous, Variety
of Technologies
2005
2003
Internal Focus,
Standardization
Shared Corporate
Infrastructure
Desktop Arch,
Security (IPC)
Reduce Costs, Link
to business
ICT Organization
Consolidation
Enterprise
Architecture
BSI, ESM &
Departmental Focus
Shared Standardized
Process’s & Tools
Standardized File,
Print, Email, PDN
VPN, SAN, Server
Consolidation
2007
Outward focus, Service
Quality, Integrated Del
Service Organization
Service Oriented
Architecture
Centres of
Excellence
Virtual, Hosted Apps,
Standards Based
Manitoba Information and Communications Technologies
QUESTIONS
http://www.gov.mb.ca/est/mict/index.html