GWEA Framework Yields Success at Ekurhuleni Metropolitan Municipality
3 likes•46,318 views
The document outlines the approach of the Ekurhuleni Metropolitan Municipality towards managing city operations and processes, detailing the city process model and various operational processes. It includes statistics on the population and household demographics, as well as insights on enterprise architecture principles aiding in the city's systemic organization and automation efforts. The report also highlights future goals including enhanced online services and customer engagement strategies.
GWEA Framework Yields Success at Ekurhuleni Metropolitan Municipality
- 1. The Open Group “Managing, Enabling and Operating the city, 1 process at a time.” By: Vuyani Zwane Applications Manager: Projects and Solution Delivery
- 2. 1. Introduction – EKURHULENI METROPOLITAN MUNICIPALITY 2. City Process Model 3. Manage the City 4. City Operations 5. City Enablers 6. Automation 7. EMM Enterprise Architecture Principles 8. City Process Model 9. EMM Levels of Enterprise Architecture 10. Foundation Architecture 11. Common Reference Architecture (CORA) 12. Technical Reference Architecture 13. Future 14. Acknowledgements INDEX
- 3. EKURHULENI METROPOLITAN MUNICIPALITY Total Population = 3 200 000 Residential Customers = 583 000 Indigent = 211 420 Total Households = 900 000 Business = 21 000 Industrial/Commercial = 13 000 Institutional = 44 000 Other 4 200
- 4. CITY PROCESS MODEL Master MMMaaasssttteeerrr SSSSyyyysssstttteeeemmmmssss PPPPllllaaaannnn ((((2222000011113333 –– 2222000011116666)))) AAAAsssssssseeeessssssssmmmmeeeennnntttt AAAApppppppprrrrooooaaaacccchhhh
- 5. Processes modelled = 16 Main Processes 54 Sub-processes • City Planning (Rezoning) • Economic Development (Investment Desk) MANAGE THE CITY
- 6. CITY OPERATIONS Processes modelled = 14 Main Processes 83 Sub-processes • Unified Command Centre • Health and Social Development (Indigent) • CRM (Workforce Management) • Energy (Operational Maintenance)
- 7. CITY ENABLERS Processes modelled = 10 Main Processes 60 Sub-processes • Supply Chain Management • Asset Management (fleet) • H.R. Management • Real Estate Management
- 8. AUTOMATION Processes Automated and/or Enhanced = 10 • Indigent Management (Registration / Deregistration • Application for Rezoning • Application for Building Plan • Application Round Collection (Waste Management)
- 9. AUTOMATION 2000 1500 1000 500 0 Application Count Oct- 13 Indigent App Count Nov- 13 Dec- 13 Jan- 14 Feb- 14 Mar- 14 Apr- 14 May- 14 Jun- 14 Jul-14 App Count 467 513 135 322 565 685 785 937 1086 1557 40 30 20 10 0 Rezoning App Count Apr-14 May-14 Jun-14 Jul-14 Application Count Apr-14 May-14 Jun-14 Jul-14 App Count 17 9 34 36 25 20 15 10 5 0 Application Count Building Plan App Count Oct- 13 Nov- 13 Dec- 13 Jan- 14 Feb- 14 Mar- 14 Apr- 14 May- 14 Jun- 14 Jul-14 App Count 21 12 3 10 0 10 0 0 6 0
- 10. EMM Enterprise Architecture Principles Enterprise Architecture EEEnnnttteeerrrppprrriiissseee AAArrrccchhhiiittteeeccctttuuurrreee PPPPrrrriiiinnnncccciiiipppplllleeeessss GGGGlllloooobbbbaaaallll AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee PPPPrrrriiiinnnncccciiiipppplllleeeessss BBBBuuuussssiiiinnnneeeessssssss AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee PPPPrrrriiiinnnncccciiiipppplllleeeessss IIIInnnnffffoooorrrrmmmmaaaattttiiiioooonnnn////DDDDaaaattttaaaa AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee PPPPrrrriiiinnnncccciiiipppplllleeeessss IIIInnnnffffoooorrrrmmmmaaaattttiiiioooonnnn SSSSyyyysssstttteeeemmmmssss////AAAApppppppplllliiiiccccaaaattttiiiioooonnnnssss AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee PPPPrrrriiiinnnncccciiiipppplllleeeessss TTTTeeeecccchhhhnnnnoooollllooooggggyyyy AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee PPPPrrrriiiinnnncccciiiipppplllleeeessss
- 11. CITY PROCESS MODEL Master MMMaaasssttteeerrr SSSSyyyysssstttteeeemmmmssss PPPPllllaaaannnn ((((2222000011113333 –– 2222000011116666)))) AAAAsssssssseeeessssssssmmmmeeeennnntttt AAAApppppppprrrrooooaaaacccchhhh
- 12. EMM Levels of Enterprise Architecture SSSSttttrrrraaaatttteeeeggggiiiicccc AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee provides an organizing framework for direction setting at an executive level. ((((EEEEMMMMMMMM EEEEnnnntttteeeerrrrpppprrrriiiisssseeee SSSSttttrrrraaaatttteeeeggggiiiicccc AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee)))) SSSSeeeeggggmmmmeeeennnntttt AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee provides an organizing framework for operation and development of architecture roadmaps at Cluster level. ((((eeee.g. CCCCoooorrrrppppoooorrrraaaatttteeee CCCClllluuuusssstttteeeerrrr,,,, SSSSoooocccciiiiaaaallll CCCClllluuuusssstttteeeerrrr,,,, IIIInnnnffffrrrraaaassssttttrrrruuuuccccttttuuuurrrreeee CCCClllluuuusssstttteeeerrrr)))) GGGGrrrroooowwwwtttthhhh aaaannnndddd DDDDeeeevvvveeeellllooooppppmmmmeeeennnntttt SSSSeeeeggggmmmmeeeennnntttt AAAArrrrcccchhhhiiiitttteeeeccccttttuuuurrrreeee)))) Capability Architecture provides an organizing framework for change activity and the development of architecture roadmaps at a capability or project level. (UCC Architecture, Digital City, ERP etc.)
- 13. Foundation Architecture Reference : Government Wide Enterprise Architecture (GWEA)
- 14. Common Reference Architecture (CORA)
- 16. ANTICIPATED TECHNICAL AAANNNTTTIIICCCIIIPPPAAATTTEEEDDD TTTEEECCCHHHNNNIIICCCAAALLL FFFFUUUUTTTTUUUURRRREEEE VVVVIIIIEEEEWWWW
- 17. ANTICIPATED TECHNICAL AAANNNTTTIIICCCIIIPPPAAATTTEEEDDD TTTEEECCCHHHNNNIIICCCAAALLL FFFFUUUUTTTTUUUURRRREEEE VVVVIIIIEEEEWWWW Lessons Learnt Set an architecture vision. Stick to it. An architecture board is not a policing function (NO BEAUROCRACY). Maintain a(SOA) services catalogue. THE TOOL IS NOT ARCHITECTURE. Customer engagement is key (BPM Forum). Architecture on Demand. Develop principles with supportive standards. Stick to them. Architecture validation is good but hard to institutionalise (Legacy applications, supply chain, etc.). Speak the same language.
- 18. FUTURE Online Services Real Time Dashboards / Reports Mobile Applications System Integration
- 19. 1. EMM – ICT-CIO: KIRUBEN PILLAY 2. EMM – MANAGEMENT INFORMATION SYSTEMS DIVISIONAL HEAD: LAZARUS SIKHWETHA 3. EMM – ICT-MANAGEMENT INFORAMTION SYSTEMS DEVELOPMENT TEAM 4. EMM – ICT DEPARTMENT ACKNOWLEDGEMENTS