S t a t e I n f o r m a t i o n T e c h n o l o g y A g e n c y

Government Wide Enterprise Architecture (GWEA)

An Overview of GWEA and MIOS to

the e-Documentation XML Workshopby

Willie NeedhamChief Enterprise Architect

June 2008

22

Agenda

GWEA MotivationGWEA Strategic IntentMinimum Interoperability Standards (MIOS)Conclusion

“By the time a man realizes that maybe his father was right, he usually has a son who thinks he's wrong.”

- Charles Wadsworth

33

GWEA Motivation “Everything should be made as simple as possible, but not simpler.”

- Albert Einstein.

44

Government ICT House of Values*Se

curit

y

Inte

rope

rabi

lity

Redu

ced

Dupl

icat

ion

Econ

omie

s of

Sca

le

Digi

tal I

nclu

sion

Lower Cost Increased ProductivityCitizen Convenience

Government Wide Enterprise Architecture* From e-Government Policy, SITA Regulations & SITA Act (amended)

Outcomes

Objectives

Method

55

Mandated Services to Government*

Transversal Systems (Act)

Standards & Certification (Reg 4.2 & 4.3)

IS Convergence Strategy (Reg 4.1.1)

Disaster Recovery Strategy (Reg 4.1.2)

IS Inventory(Reg 4.6)

ICT Research Plan

(Reg 4.4)

… and Services as per BA

(Reg 5)

Private Telecoms Network (Act)

Manage ICT Procurement(Reg 7.4, 8.2, 10.2, 10.12, 11.1)

* From SITA Act (amended) & SITA Regulations

“7.(6) The Agency [SITA] –(a) must set standards regarding-

(i) the interoperability of information systems subject to the approval of the Minister; and

(ii) a comprehensive information systems security environment for departments, subject to the approval of the Minister and the Minister of Intelligence;”

66

SITA Operating Model (Abridged)

TRAIN

SUPPORT

MAINTAIN

DESIGN & IMPLEMENT

SpecialProjects

StrategicProjects

Departmental Application

Maintenance

Transversal Training & Functional Support

Departmental Training & Functional Support

Government-WideEnterprise

Architecture

TransversalProjects

Transversal Application

Maintenance

NGN Support Hosting & Service Centres

Convergent Systems Support

LAN & End-User Device Support

DIRECT & GOVERN

MUST MAY

Departmental Enterprise

Architecture

Serv

ice

Man

agem

ent

Info

rmat

ion

Syst

em S

ecur

ity

Proc

urem

ent S

ervi

ces

Res

earc

h &

Dev

elop

men

t

COMMON SERVICES

77

Regulatory drivers* Chapter 1, Part III.E [Planning]

A head of department shall establish- an information plan that supports the processes and objectives of the

department. an information technology plan that supports the information plan; and an operational plan that enables the implementation of the information

technology plan and information management. Chapter 5, Part II [e-Government Interoperability]

Comply with Minimum Interoperability Standards (MIOS) for: every part of any new information system developed or acquired for the

public service or any upgrade of any existing information system in the public service; and

every legacy system that is part of electronic service delivery in the public service.

* Public Service Regulations, 2001 (as amended)

88

Office of Gov CIO Priorities 08/09 Information Management

Enterprise Information Architecture (Data Standards, Inventory of IM Initiatives, Shared services and interoperability …)

Service Management Implement COBIT, ITIL process across public sector …

IT infrastructure & application services Develop Government Wide Enterprise Architecture to

promote coherence, standardisation, eliminate duplication and leverage ICT spend.

Integrated Finance Management System (IFMS) Next Generation e-Government system

* Extract from Office of the Government CIO Plan, Dec 2007

99

GWEA Strategic Intent“You cannot paint the 'Mona Lisa'

by assigning one dab each to a thousand painters.” - William Frank Buckley Jr.

1010

EnterpriseArchitecture

BusinessArchitecture

DataArchitecture

ApplicationArchitecture

ICTArchitecture

EA Evolution / Revolution?1990 2000 2010

PerformanceManagement

InformationManagement

ICT & STDManagement

ICT

ResourceManagement

OPS

ProcessManagement

SoftwareManagement

ITGovernance

CorporateGovernance

1111

Architecture in Context*

Business Architecture

Business Integration

TechnicalDesign

IS/ICTArchitecture

Build

Component Verification

IS/ICT Integration

* From Forsberg & Moozand ISO 15288

Buy

TOGAF / MIOS ISO12207 (SDLC) ITIL

COBIT

PhasesProcessesGovernance

IEEE1471 (EA Definition) ISO15704 (Capability Model)

ISO14258 (GERAM FW)

Architecture / Planning Design / Development Production Operation

1212

An EA Capability (“Function”) EA Process

EA Development Process EA Logic (Framework of Models) EA Methods (e.g. Techniques, Notation,

Principles, Trade-offs) EA People

Roles & Responsibilities (RACI Contracts) Competencies Governance structures

EA Information System Planning & Modelling Software Data Repository ICT Infrastructure

EA Products GWEA Reference Models / Blueprints / Plans Interoperability Standards

Process

People Technology

Blueprints &Standards

1313

EA Process (TOGAF)*EA Framework &

PrinciplesValidateRequirement at

every phase

IdentifyPROJECT INITIATIVES

DevelopIMPLEMENTATION

Roadmap

EnsurePROJECT Compliance

to Architecture

DevelopBUSINESS

Architecture

DevelopDATA & APPLICATION

Architectures

DevelopICT INFRASTRUCTURE

Architectures

AS-IS,TO-BE &

GAPS

KeepArchitecture up to date

Define EA Scope, Vision, Drivers and

Baseline

* Accepted by the GITOC EA Committee in Nov 2007

1414

EA Logic (Concept)ICT

ArchitectureApplication Architecture

Business Architecture

Data Architecture

Services

Service Reference Model

Network Distribution

Organisation

Processes

Performance

Distribution

InformationService Interfaces

Computation Model

Synchronisation

Security

ICT Reference Model

Database / Storage

Governance Software Standards ICT Standards

Data Reference Model

Data Flow

Data Standards

… … … …

Data Logic Service Logic

Integrated EA Blueprint & Programmatic View

1515

GWEA Governance StructureMinister

PSA

SITA Exec

Gov CIO

GITOCouncil

EAComm

ISS

e-Gov

PROJ

Procure

KIM

IFMS

OSS

GITO

DeptEA

Gov WideEA

42 Departments 9 Provinces

Other GITO Council Committees

NationalDepartment

1616

Government Departments, Bodies & Clusters

GWEA Reference Model concept

Shared

Non-Shared

ICT

Infra

stru

ctur

eIS

Core

Common /Transversal

IS /

ICT

Dept EA / Master Systems Plans

IFMS, e-GOV, GIS, ECM, Cluster IS, …

NGN, Data Centres, Service Man, Security, …

Business Process/Service Ref Model

1717

GWEA Priorities

Improve GWEA Framework v1.0Develop EA Handbook for Gov Depts.Develop GWEA Reference Models / Blueprints Improve Minimum Interoperability StandardsValidate Departmental/Project EA BlueprintsEstablish an EA Centre of Excellence.

1818

Interoperability and MIOS"It is astonishing what foolish things one can temporarily believe

if one thinks too long alone." - John Maynard Keynes

1919

Interoperability levels*

* Tolk, Andreas. “Beyond Technical Interoperability – Introducing a Reference Model for Measures of Merit for Coalition Interoperability.

Technical interoperabilitytechnical issues of linking computer systems and services.

Semantic Interoperabilityensuring that the precise meaning of exchanged information between different kind of Information Systems .

Organisational interoperabilitythe state where the organisational components are able to perform seamlessly together.

“IS/ICT Space”MIOS

FOCUS AREA

“Cognitive Space”ORG LEADERSHIP

FOCUS AREA

2020

MIOS v4.1 Status XML as a Standard

XML (Extensible Mark-up Language) is the cornerstone of the Government data presentation and integration strategy; but XML alone is not sufficient.

Need to add XML data schemas for use throughout the public sector. Future version of MIOS (v5.0) will include

Technical Reference Model (TRM) as reference and classification schema for all interoperability standards.

Government sector/cluster specific data interoperability standards Add a rationale to comply (applicability clauses). Implementation guidelines Improve the MIOS development process and responsibilities.

Review Process and Frequency Annual basis through the GITOC Standing Committee on Architecture with

due process of consultation.

2121

Conclusion National XML Standards prospective benefits:

Improve the interoperability maturity level among government Information Systems;

Enable e-Government programmes to proceed more effectively and efficiently;

Set a standard by which to certify the acquisition of Government Information Systems;

Whilst observing the following principles: Collaborative process among Departmental stakeholders (architects,

software engineers and managers) to strengthen collective ownership at GITOC level;

Maintain a balance between rigor and innovation (“Goldie Locks Tale”); Must be certifiable; Must be manageable in its through-life of existence; and Open & freely available to public and private entities to ensure transparency

and competitive bidding.

2222

Thank YouDankie

SiyabongaKe a lebohaSiyathokoza

Willie NeedhamChief Enterprise Architect (GWEA)Strategic Services

State IT Agency (Pty) Ltd459 Tsitsa St. ErasmuskloofPretoria, South AfricaE-mail: willie.needham@sita.co.zaTel: +27 (12) 482 2774Web: www.sita.co.za