6 Steps to Transition Govt ICT effectiveness
2 likes797 views
The document discusses strategies for developing an effective government ICT strategy. It outlines six key pillars and provides a six step process to define goals, standards, policies and procedures to implement strategies. It emphasizes defining metrics to measure success and analyzing metrics to continually improve processes and strategies.
6 Steps to Transition Govt ICT effectiveness
- 2. Trends and Directions Data Security and Access How can I automate collaboration and still protect sensitive data? What is the best way to provide controlled, remote access to centrally managed information? Fiscal Management How can we maximize revenue collections without increasing taxes/Permit fees? What work processes can be automated to reduce costs? Increasing Accountability How can I improve tracking and reporting of public funds? What is the best way to enforce proper approval and document key decisions / awards? Citizen Centricity What is the best way to improve responsiveness to citizen demands? How should cases be distributed to improve workload and consistency of outcomes? Constituents Suppliers Citizen Services Governance, Risk and Compliance Performance Management Shared Services Risk Management Benchmarking Case Management Self-service demand eInclusion Identify Management Privacy protection
- 3. Six Pillars of Government ICT Strategy
- 4. 6 Steps to Successful ICT Strategies 6 1. Define Goals and Strategies 3. Define Metrics 5. Analyze and Improve Existing Processes 4. Put ICT Strategies in Place 2. Define Standards, Policies, Procedures Around Financial, Portfolio, Project, Service, etc These 6 steps allow a company to incrementally develop and mature their overall SOA and thus business goals 6. Refine and Go to the Next Level
- 5. Steps to Enable Transition to iGovernment Automate Policy and Operation Processes Citizen-Centric 360 o View Analytics to Increase Efficiency and Transparency Federated & Master Data & Record Management Enterprise-Grade Service Delivery Platform Transform policy and operational processes to achieve holistic outcomes 1 Secure, multi-channel, single view of program enrollee or prospect across all programs 2 Analytics to ensure closed-loop feedback, continuous improvement across all programs 3 Ensure complete and accurate information across the integrated program lifecycle 4 Create a fully governed infrastructure to leverage and extend legacy systems as shared services 5
- 6. Shared Services vs. Centralized Services Consolidation New Location Re-engineering SLAs Performance Mgmt. Service/Cost Transparency End-to-End Process Lack of Clarity Declining Customer Service Exceptions Increase Shadow Cost Increase CENTRALIZATION SHARED SERVICES RANGE OF BENEFITS Shared Services Centralized Services ERP Current State Example: Central Agency processes invoices / vouchers and payments for agencies: 2 day processing expectation No written metrics or measurement = Inconsistency in delivery timeframe & enterprise costs increase to provide service Target State Example: Shared Service Center processes invoices / vouchers and payments for participating agencies: Written processing timeline guarantee! Metrics, SLAs and customer focus Measured Performance Consistent, timely delivery
- 7. Transitioning To Reference Architecture Vision Architectural Principles Application Specific Data Peer–To-Peer Integration Functionality Workflow Security Enterprise Shared Infrastructure Enterprise Information SOA & EDA Infrastructure Enterprise Service Repository Aggregations & Summaries Master & Reference Data Operational Data Enterprise Business Processes Enterprise Business Services Standardized Industry Processes Data Integration Business Rules Business Services Identity & Access Management Data Security Security Business Rules Industry Reference Architecture Virtualization Dedicated Infrastructure Retain as Legacy / Replace / Retire Legacy Applications Open Standards Unified Method Modernisation Methodology Mainframe Migration Enterprise Method Process Integration Application Integration Architecture Grid Computing
- 8. Goals & Strategies Business and IT Goals ICT Strategy Existing Capabilities IT Roadmap Journey Management 1
- 9. Create Standards, Policies & Processes Communicate 2 Policies Create Manage Issues: Decision Rights Input Rights Exception Management Executives Developers Architects Administrators IT Managers Business Analysts Feedback & Monitor Enterprise Architects Governance Board
- 10. Define Metrics for Success Why Measure ? Ensure Business Goals Deliver ICT Strategy What to Measure ? standards, compliance, # of projects adhering to processes, # of reference architectures, usability of reference architectures, # of exceptions, # of services created, # of reusable services, service reuse metrics, etc How to Measure ? What can be automated? What can be easily captured? 3
- 11. Put Mechanisms in Place 1. Decision, Policies, Processes 4 Blueprints & Patterns Financial Portfolio People Operations Projects Technology Architecture Service Usage Fees Service Funding Model Projects Applications Platform Funding Business Services Roles & Responsibilities Service Ownership EA Group Service & Process Owners Service Lifecycle Gov Shared Artifacts Capacity Planning Enforce Service Levels Enforce Policies Strategic SOA Platform Shared Foundation Srvcs Enforce Platform Decisions Reference Architectures Architectural Standards DRIVEN BY EXECUTIVES Information Data Standards Data Quality Data Ownership
- 12. Put Mechanisms in Place 2. Mechanisms Vision for Strategy Endorsed by Sr Officials Force Behavioral Change Ensure Participation of Appropriate People Awareness Communication & Collaboration Center of Excellence Roles and Responsibilities Financial, Portfolio, People, Architecture, Projects, Technology, etc Education Strategies Processes (Automated) Capture and Report on Metrics Administration, Monitoring and Enforcement Exceptions Handling Mechanisms Upward Communication when Policies are not followed 4
- 13. Analyze and Improve Metrics on ICT Process Itself Metrics on Progress of Goals and Roadmap How Often are People Going off the Path? Do they Tell us When they do? Do we need to change restrictive policies? Do we need to have stricter enforcement? What do you do with the Information? Make Decisions Create Feedback Loop 5
- 14. Refine and Go to the Next Maturity Level ICT Strategies, Goals, Objectives Met for this ICT Maturity Level level Refine ICT Strategies, Goals, Objectives for Current Maturity Level Create New ICT Strategies, Goals, Objectives for next ICT Maturity Level 6
- 15. Consolidated Information Architecture Low ROI Efficiency and Effectiveness Data Program Process Information Access Technology Infrastructure OIA Enablement Processes Access Data Technology Infrastructure Govt ICT Roadmap Data Design Enterprise Portal Upgrade/Port to for Targeted Databases Process Design Enterprise Data Repository Shared Services High Availability Knowledge Management Program Int’gn Govt Data Hub Consolidate H/W (production) Process Execution Balanced Scorecard & Metrics Consolidated Management Current Process Definitions Identify Databases Single Sign-on Consolidate H/W (backup) Citizen Centric Collaborate Across Channels
Editor's Notes
- #7: Transition from Centralization to Full Value of Shared Services: Many organizations stop at ERP implementation, leaving value behind and decreasing the likelihood of sustainability and scalability Centralized: Benefits of centralization recede due to lack of shared accountability for performance and increase in shadow cost over time
- #9: Don’t forget to mention - Participation from Executives - if you are starting out
- #10: give examples of these policies When you are doing your first POC projects, you don’t think of these things off the bat. If you want enterprise scale, you should do this stuff at some point
- #12: Driven by executives? Talk about analogy of speed, speedometer, speed limits, police, etc. how do you ensure WSDL Compliance How will you actually govern policies and standards The group may define the standards, but you need governance around it Deviations
- #13: Talk about analogy of speed, speedometer, speed limits, police, etc. how do you ensure WSDL Compliance How will you actually govern policies and standards The group may define the standards, but you need governance around it Deviations
- #16: Highlight Dependencies mentioned by Guy (to our advantage) - + plus take into account business cycle issues, hw renewals etc that Guy talked about) Moving towards Consolidation streams Guy talked about _> which you’re recall leads towards Grid conducive model of enterprise architecture