1 / 26

Dan Kerr Director ICT Architecture Province of Manitoba

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.

vin
Télécharger la présentation

Dan Kerr Director ICT Architecture Province of Manitoba

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. 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.

  3. 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

  4. Why we plan and need standards

  5. Influences

  6. 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

  7. 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

  8. 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 Current ICT Environment

  9. EA Structure6 Domain Architectures Guide ICT systems and service life cycles that support program delivery

  10. 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.

  11. How was it developed? • Cross Departmental working teams • Industry input • Based on best practices • Modeled after similar jurisdictions

  12. EA Document Structure • Guiding Principles • Goals • Applied Principles • Components/Elements • Models • Standards • Links to appropriate repository information • Decisions • Technical Topics

  13. Guiding Principals • Accommodaterapid change to government programs and services. • Facilitatelegitimate access to information while providing strict control over the collection, management and security of this information. • Support and encouragedialogue between citizens and government. • Promotethe accessibility and integration of government services by providing an enterprise view of services that cross organizational boundaries. • Alignwith the program planning and delivery requirements of the government. • Facilitate access to government services with a goal of “anywhere at any time.”

  14. 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

  15. 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

  16. User Interface / Device Tier browser J2ME Swing, AWT browser Windows CE .Net Windows client Presentation Tier ASP.Net JSP Servlets Application Tier EJB session beans .Net Managed Class Information Model Tier EJB entity beans ADO.Net J2EE Componentry .Net Componentry What’s in it? • Common terms • Definitions • Models • Principles • Standards

  17. Public Enterprise Class 1 Class 2 R I S K I M P A C T Departmental Class 3 Personal Application Classification Based onRisk & Impact

  18. Class 1 Class 1 Class 1 APPLICATION CLASSIFICATION Class 2 Class 2 Class 3 Service Level Metrics Response Time Metrics Failover and Recovery Tests Unit testing Naming and Coding Standards Code Metrics Function, System, Regression, Load, Stress, Performance, User Acceptance System Deployment Readiness Development Testing Production System Environment Grid Classification & Standards • Class 1 uses Class 1 technology, support, languages, infrastructure etc. • Class 2&3 – Class 2, 3 as appropriate

  19. Standards & Lifecycle STANDARDS Industry Protocol Generic Specification Baseline Technologies Containment Retirement LIFECYCLE Emerging Custom Produce 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.

  20. STANDARDS Industry Protocol Generic Specification Custom Produce Baseline Technologies Containment Retirement LIFECYCLE Emerging Types of Standards • Industry • Generic • Custom These may be further qualified into: • Products • Protocols • Specifications

  21. 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

  22. Support Server Central Services Transformation - The Future Multiple environments technologies, supports

  23. Manitoba’s ICT Services Map Channels Application Services Portal Knowledge Management Presentation Personalization Document Management Software Dev’t Tools Electronic Service Delivery e-Learning Process Modeling Imaging E-Commerce Help Desk Corporate Knowledge Component Repository Document Handling CRM Case Management Content Management Security Services IT Service Management Data Warehouse/Mart Digital Rights Mgmt Single Sign on Threat & Intrusion Identification Infrastructure Management Security Protocols PKI ERP/SAP Key Performance Indicators Integration & Collaboration Services Financial Mgmt Metadata Collaboration Web Services Decision Support Systems HR Management Enterprise App’n Integration Workflow Infrastructure Services Email Desktops Networks File Wireless Servers Central Storage Print

  24. Governance, Direction & ICT Strategy Departmental ICT Planning Internal Focus, Standardization Reduce Costs, Link to business Departmental Focused ICT Shared Corporate Infrastructure ICT Organization Consolidation Service Organization 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 Heterogeneous, Variety of Technologies Standardized File, Print, Email, PDN Infrastructure & Network VPN, SAN, Server Consolidation Virtual, Hosted Apps, Standards Based ICT Roadmap 1997 2005 2007 2003 Outward focus, Service Quality, Integrated Del

  25. Manitoba Information and Communications Technologies QUESTIONS http://www.gov.mb.ca/est/mict/index.html

More Related