11. A Governance perspective “ Sometimes when I consider what tremendous consequences come from little things… I am tempted to think there are no little things.” - Bruce Barton
12.
13. Government ICT House of Values* * From e-Government Policy, SITA Regulations & SITA Act (amended) Security Interoperability Reduced Duplication Economies of Scale Digital Inclusion Lower Cost Citizen Convenience Increased Productivity ICT Planning (GWEA) -> ICT Acquisition -> ICT Operations ICT Value Principles Means/Services
28. Departmental Engagement Model CIO/GITO ICT Planning & Governance DEPARTMENT 1 2 3 4 … 5 6 7 Internal Service Agreements/Contracts Procurement & Development ICT Operation & Support SITA Business Agreement & Service Level Agreements (SITA ACT) EA Services Procurement & Development Services ICT Infrastructure Services INDUSTRY Transversal Contracts
29. EA In Government “ All models are wrong, but some are useful” George Box, Edward Deming
31. EA Context * From Forsberg & Mooz and ISO 15288; Corporate Governance not shown Architecture / Planning Design / Development Production / Operation GWEA / MIOS ISO 12207 (SDLC) ITIL / ISO 20000 COBIT / ISO 38500 Buy Business Architecture Technical Design Build IS/ICT Architecture Business Integration Component Verification IS/ICT Integration ICT Ops Buss Ops Business Design & Dev (e.g. OD, Srv Dev) ENTERPRISE ARCHITECTURE CAPABILITY SYSTEM ACQUISITION CAPABILITIES (Solution Architecture, Project Management, Procurement, Solution Development, Integration) ICT OPERATION CAPABILITIES PUBLIC SERVICE CAPABILITIES PUBLIC SERVICE DEVELOPMENT CAPABILITIES
32.
33. GWEA Framework INTEROPERABILITY CONSISTENCY ALIGNMENT Purpose The minimum standard by which to use an Enterprise Architecture approach to develop and construct National and Departmental ICT Plans and Blueprints Technology Architecture Views (D) Application Architecture Views (C2) Business Architecture Views (B) Data Architecture Views (C1) Organisation Structure Model Application Reference & Standards Model Business Process Model Business Function/Service Model Business Performance Model Business Information Model Application Distribution Model Technology/Network Distribution Model Technology Platform Model Technology Reference & Standards Model Data Reference & Standards Model Data Security Model Data Gap Application Gap Technology Gap Data-Application Model Application Stakeholder Model Opportunities & Solution (E) and Implementation Plan (F) Views (Programmatic Views) Business Gap Preliminary (P) & Vision (A) Views EA Org Model EA FW EA Request EA Principles EA Vision EA SOW Comm Plan Business Roadmap Data Roadmap Application Roadmap Technology Roadmap Consolidated Roadmap & Transition Architecture Implementation and Migration Plan Implementation Governance Model
34. EA Planning concept Government Departments, Bodies & Clusters Departmental Plans/Blueprints IFMS, e-Gov, GIS, e-Natis, e-HR, NISIS, Who-Am-I, LURITS… NGN, Data Centres, Help Desk, Security, … Business Services Core Services Common Services Shared Non-Shared ICT Infrastructure Information Systems Core Common / Transversal Resource Management Services (“Backend”) Public Services (“Front-End”)
35.
36.
37. MIOS v4.1 Composition* OPEN STANDARDS from IETF, ISO, W3C, OASIS, ITU-T, ANSI, IEEE, ECMA, ETSI * Minimum Interoperability Standards (MIOS) v4.1, DPSA, Aug 2007 Category Component (Standards) Connectivity Web/Internet (HTTP) E-Mail (SMTP, MIME, IMAP, S/MIME) Directory & Naming (X.500 and DNS) Network (FTP, TCP/IP, TLS) Security (e.g. RC4, RSA, AES, ) Web Services (SOAP, WSDL, UDDI) Internet Conferencing (H.323, SIP) Mobile Phones (WAP2, GPRS, SMS, MMS) Data Interoperability Meta-Data (XML, XSL) Data Security (SAML) PKI (X.509) Modelling (UML, XMI) Ontology (OWL) Geospatial (GML) Information Access & Content Standards Web/Hypertext (HTML, XHTML, JavaScript) Office Documents (UTF-8, ODF, CSV, PDF) Still images and Video (JPEG, PNG, TIFF, MPEG) File Compression (TAR, ZIP, GZIP) Relational DB Access (SQL-93) Meta-Data Content Management (Dublin Core) Syndication (RSS)
38. Challenges & Conclusion “ Sometimes when I consider what tremendous consequences come from little things… I am tempted to think there are no little things.” - Bruce Barton
42. Thank You Dankie Siyabonga Ke a leboha Siyathokoza Willie Needham Chief Enterprise Architect Strategic Services State IT Agency (Pty) Ltd Pretoria, South Africa Tel: 012 482 2774 [email_address] www.sita.co.za
43.
44.
Hinweis der Redaktion
Where there is ‘integration’ of systems within government the most prevalent form through the exchange of batch files. There are very very few instances of more sophisticated integration. [go through points] Looking at the current situation it becomes clear that at present Government’s IT infrastructure and thinking simply does not reflect the everyday necessity for the exchange of information or the integration of business processes across agencies
As reiterated by the Deputy-President’s comments, technology has critical enabling role to play in helping the poorest of the poor, but in this case, it is proving to be more of a barrier than anything else as it is simply reinforcing the rigid, siloed nature of government functions. One cannot look at government functions within departments in isolation when striving to help citizens and deliver quality services. You need to consider the end-to-end processes e.g. SASSA grant application processing might take 3 days, but gathering evidence stakes 2 years This is a simple example, but there are literally hundreds of processes impacting all areas of Government where the disconnected of Government affects the everyday lives of citizens, for instance: Processing of court cases Processing of adoption cases Registration and compliance of companies and individuals in economic activity imposing unnecessary costs to doing business
Departmental planning still in silo’s – lead to duplications Multiple, Fragmented Departmental Plans and Systems Regulation does not prescribe “cluster business plans” it is extremely difficult to “plan/develop cluster/transversal systems” Common/Transversal systems planning requires interdepartmental co-operation and strong lead department and funding model to succeed.
Mathematical definition is just an elegant way of writing 1+1= 2