Uploaded By: Derek Keats
- Slide 1
- Slide 2
- Slide 3
- Slide 4
- EA Definition
- EA Defines...
- Why EA is relevant to HEIs?
- What is the business
- Reality for many...
- Slide 10
- Silos in the institution
- Slide 12
- Slide 13
- Slide 14
- Slide 15
- Slide 16
- Slide 17
- Slide 18
- Slide 19
- Slide 20
- Slide 21
- Slide 22
- Slide 23
- EA channels
- Slide 25
- Slide 26
- Slide 27
- Slide 28
- Slide 29
- Slide 30
- Alignment of strategy...
- Slide 32
- Slide 33
- Slide 34
- Slide 35
- Slide 36
- Slide 37
- Slide 1 - Towards an Enterprise Architecture for Wits In the context of the new StudentInformation System programme
- Slide 2 - Brief history Mainframe → oracle Financial austerity “Saving the institution” This is NOT about Oracle! Not even Oracle Student System...
- Slide 3 - Confronting our brutal facts Wits currently has very little governance regarding implementation of IT supported processes, IT projects, or IT acquisition within the various silos of the institution This results in Mismatch between institutional process and IT tools Mismatch between expectations within institutional silos and what we can support Data islands, data amoebae, data corruption 'Projects' that slip through the cracks Operations managed as projects Projects managed as operations Wasting of financial and human resources Repetitive repetition fatigue syndrome! Almost no support for academic computing beyond 'shared-by-all' services
- Slide 6 - Enterprise architecture defines the nature of what we call the operations (the business) of the institution the information necessary to operate the institution the technologies necessary to support the institution's operations, the change processes necessary for implementing new processesand technologies in response to the changing needs of the institution
- Slide 8 - What is the institution?
- Slide 9 - Reality for many institutions?
- Slide 10 - Reality for many institutions?
- Slide 11 - Silos in the institution (Wits)
- Slide 12 - Silos in the institution
- Slide 13 - Silos in the institution
- Slide 14 - Silos in the institution
- Slide 15 - Silos in the institution
- Slide 16 - Silos in the institution
- Slide 17 - Federated system
- Slide 19 - For the Wits, EA defines Architecture of institutional processes Including their federated & uncertain components Processes and governance mechanisms for integration across silos In line with existing governance mechanisms Aligned to the institution, not the other way around Application architecture aligned to our aspirations as a top higher education institution Including leveraging our own potential for innovation (TIPS) Technology architecture that is aligned to the application architecture Leading edge practice, managed risk
- Slide 20 - Aligning
- Slide 21 - Aligning
- Slide 22 - Agile EA
- Slide 24 - EA as steps or concurrent channels Executive and management buy-in to the concept Development of EA strategy Alignment to institutional vision and strategy Build EA into organization and governance Provide for monitoring mechanisms e.g. Maturity model and scorecard Create and align roles and responsibilities Marketing and communications plan Implementation through programmes and projects Technical infrastructure Academic Information Management System
- Slide 26 - Programme A group of related projects managed in a coordinated way to achieve benefits and control not available by managing them individually Sanghera, P. 2008. Fundamentals of Effective Program Management: A Process Approach Based on the Global Standard. J. Ross Publishing Inc, 356 pp. A system that manages the life cycle of students within Wits is too big to be treated as a project, there are many projects within it Many of the initiatives that will address academic computing are also programme scale
- Slide 28 - This is just anexample
- Slide 29 - Which approach?
- Slide 30 - Which approach
- Slide 31 - Alignment of strategy and capability
- Slide 32 - Some legacy challenges affected Data integrity Institutional process & application alignment Agile end user interface design Directionality of IT expenditure Synergy Vendor Lock-in and inflexible processes Long-term (future proofing our IT systems) Support for the core business of Wits!
- Slide 33 - Key questions How do we develop, support and enable academic and and research computing that fosters agility and innovation and creates synergy among research computing infrastructure? What is a sensible subset of what is possible?
- Slide 35 - Academic & research support Create an academic and research computing section in CNS Manager, project manager, admin support funded centrally Services provided by additional staff based on cost-recovery Technical cost recovery e.g. shared hosting solutions
- Slide 36 - Next steps Development of EA strategy Alignment to institutional vision and strategy Mapping of EA roles to institutional roles(e.g. Enterprise Architect → DVC:KIM) Mapping of EA governance to University governance Design technical and application architecture Academic computing opportunities and business model The need for programme management of the academic information management system makes this urgent