1 / 15

AARNet Enterprise Architecture

AARNet Enterprise Architecture. EA Symposium 1-2 November 2006. AARNet - Background . 1989 – Origin of the Internet in Australia 2000 – Started operating as a company - 38 Universities & CSIRO 2004 to 2006 - Build AARNet3 network – 35 staff, $30M turnover

aric
Download Presentation

AARNet Enterprise Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AARNet Enterprise Architecture EA Symposium 1-2 November 2006

  2. AARNet - Background • 1989 – Origin of the Internet in Australia • 2000 – Started operating as a company - 38 Universities & CSIRO • 2004 to 2006 - Build AARNet3 network – 35 staff, $30M turnover • 2007+ Enable customers to meet their business objectives

  3. Method for Review • Identify & Segment Stakeholders • Model the Business Processes • Analyse • Stakeholders vs. Process • Process vs. Systems • Identify Priority Projects • Develop Systems Architecture After spending some time with David Bedwell (CSU), I took the following approach: People Process Technology

  4. I originally started too low-level…

  5. Process Recommendations 1. Service Development. Refine the process of defining and developing new services and allocate overall responsibility for a “Product” life-cycle to an individual. 2. Service Support. The increasing number and diversity of services under support will demand more formalised processes and thorough documentation. Selective adoption of ITIL processes are recommended through to 2010. Key staff could attend introductory ITIL training in 2007 to start the ball rolling. 3. Organisational separation of Service Development and Service Support. Organisational separation will promote a more rigorous handover process, from Development to Support and put support in the hands of staff with the appropriate aptitude and skills. 4. Customer quotation and contracts. A defined work-flow for approval of any offers that are put to customers needs to be put in place. 5. Security Management. With AARNet increasingly offering services beyond Internet connections, there is a duty of care to safeguard the confidentiality and integrity of customer data. The development of security policy and basic operational procedures are recommended, in alignment with the ITIL framework.

  6. Analyse Process Value to Stakeholders

  7. Analyse Process vs. Systems

  8. Prioritisation of System Projects

  9. System Recommendations 1. Initiate system projects in the following priority areas: a. Business Performance Management / Reporting b. Asset / Configuration Management c. Improve function of Finance One d. Contract Management e. Document Management (with workflow) • Website (intranet / external) content management system 2. Spread-out system projects and use pilots to mitigate risk and maximise user adoption. A costed Project Proposal should be used as the first step in initiating a project.

  10. KPIs and Dashboard - Core

  11. KPIs and Dashboard - Enabling

More Related