Presentation on theme: "Manitoba's Enterprise Architecture A Framework for Managing Information Communication Technologies for the Province of Manitoba Dan Kerr Director ICT Architecture."— Presentation transcript:
Manitoba's Enterprise Architecture A Framework for Managing Information Communication Technologies for the Province of Manitoba Dan Kerr Director ICT Architecture Province of Manitoba David Primmer Chief Information Officer Province of Manitoba
Creating an ICT environment where technology is used to achieve province wide objectives that support the governments commitment to promote citizen centric services to the direct benefit of Manitobas 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
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 q All Departments, SOAs 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
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, 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
Whats in it? Common terms Definitions Models Principles Standards User Interface / Device Tier Presentation Tier Application Tier Information Model Tier browserJ2ME Swing, AWT JSPServlets EJB session beans browser Windows CE.Net ASP.Net.Net Managed Class EJB entity beans ADO.Net Windows client J2EE Componentry.Net Componentry
Application Classification Enterprise Departmental Personal IMPACTIMPACT RISKRISK Class 2 Class 3 Public Class 1 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 Readiness Class 3 Class 2 System Environment Grid Development TestingProduction Class 1 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 APPLICATION CLASSIFICATION
Standards & Lifecycle The 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 Retirement Containment Baseline Generic Specification IndustryProtocol CustomProduce
Types of Standards Industry Generic Custom These may be further qualified into: q Products q Protocols q Specifications Emerging Retirement Containment Baseline Generic Specification Industry Protoco l Custom Produc e
DomainSub-DomainStandards Class BaselineContainmentRetirementEmerging Application Server Web Application Manager Industry Product 1/2 IBM WebSphere Oracle Forms Server   None Identified Tomcat; jBOSS; MS.NET Enterprise ASP.NET Application Server TP MonitorIndustry Product 1/2 WebSphere Application Server Microsoft Transaction Server; IBM CICS; IMS None Identified.Net Enterprise Services Application Server Web ServerIndustry Product 1/2 IBM HTTP Server; Apache MS IISNone Identified Application Server Web ServerIndustry Product 2 ApacheMS IISNone 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 q Apache, MySQL, Linux, Eclipse Service Oriented Architecture
Central Services ServerSupport Transformation - The Future Multiple environments technologies, supports
Channels Portal Presentation Personalization Electronic Service Delivery E-CommerceHelp Desk CRM Case Management Document Management Imaging Document Handling Security Services Digital Rights Mgmt Security Protocols Single Sign on PKI Threat & Intrusion Identification Integration & Collaboration Services Metadata Enterprise Appn Integration Collaboration Workflow Web Services Application Services Software Devt Tools Process Modeling Component Repository Knowledge Management e-Learning Corporate Knowledge Content Management Data Warehouse/Mart IT Service Management Infrastructure Management Key Performance Indicators Decision Support Systems Infrastructure Services Networks Central Storage File Print Email Wireless Desktops Servers ERP/SAP Financial Mgmt HR Management Manitobas 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 Processs & 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 20052007
Manitoba Information and Communications Technologies QUESTIONS http://www.gov.mb.ca/est/mict/index.html