UC Ref Group Mar09


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • UC Ref Group Mar09

    1. 1. ‘ Extended’ Reference Group meeting 26 March 2009
    2. 2. Agenda <ul><li>Welcome, new meeting format – Ché Broekman </li></ul><ul><li>IPTel Update – Sylvie Isabelle </li></ul><ul><li>Carrier, Mobility and Billing – Jenny Connolly </li></ul><ul><li>Desktop Lifecycle Services – Deborah Tapping </li></ul><ul><li>Identity and Access Management – Terry Brennan </li></ul><ul><li>Close </li></ul><ul><li>Lunch </li></ul>
    3. 3. IPTel Project Update Sylvie Isabelle
    4. 4. Carrier, Mobility, and Billing Projects Updates Jenny Connolly
    5. 5. Carrier Update <ul><li>10,500 lines (centrally managed service and Archives) churned to Optus </li></ul><ul><ul><li>3,000 lines identified owners </li></ul></ul><ul><ul><li>2,500 lines unidentified owners </li></ul></ul><ul><ul><ul><li>(many transferred to TAFEs etc.) </li></ul></ul></ul><ul><li>Further churning awaiting Billing System (CAAB) implementation </li></ul><ul><ul><li>identified & University owned lines </li></ul></ul><ul><li>Unidentified owners – cancellation process in place </li></ul><ul><li>Non-university account holders – transfer ownership </li></ul>
    6. 6. Carrier Update <ul><li>Frame audits to identify additional (unknown) lines </li></ul><ul><li>Numbers to be ported once Optus infrastructure in place </li></ul><ul><ul><li>dependent on fibre works – due later in year </li></ul></ul><ul><li>All University services identified and on a single account </li></ul><ul><li>Billing for centrally managed services will be through Billing system (CAAB) </li></ul><ul><li>Bills for locally managed services will continue to be sent to departments for payment </li></ul><ul><li>Transitioning to IPTel includes services clean up </li></ul><ul><ul><li>review and consolidation of lines </li></ul></ul><ul><ul><li>move to centrally managed billing service </li></ul></ul><ul><ul><li>activity will be in line with staged IPTel transition </li></ul></ul>
    7. 7. Billing Project Update <ul><li>Solution build completed </li></ul><ul><li>AD and Themis integration completed </li></ul><ul><li>CADS data imported into AD </li></ul><ul><li>Back-office CAAB implementation due 6th April </li></ul><ul><ul><li>Includes cut-over from CADS </li></ul></ul><ul><ul><li>No change to departmental staff processes </li></ul></ul><ul><li>CAAB upgrade due 4th May </li></ul><ul><ul><li>Functionality includes self-service bill information via web reporting </li></ul></ul>
    8. 8. Billing Project Update cont. <ul><li>Call records from PABX and IPTel currently being captured </li></ul><ul><ul><li>parallel processing with CADS </li></ul></ul><ul><li>Retrospective bill processing and Themis feeds available from January for IPTel </li></ul><ul><li>CADS data used for PABX bill processing to March </li></ul><ul><li>CAAB used for PABX and IPTel bill processing from April onwards </li></ul>
    9. 9. Mobility Coverage Update <ul><li>Location and appearance of Optus towers identified </li></ul><ul><li>Optus drop-in sessions held in February </li></ul><ul><li>Fibre works set to commence </li></ul><ul><ul><li>Awaiting Optus agreement in place </li></ul></ul><ul><li>Tower construction to be completed mid year </li></ul><ul><li>Optus recommendation </li></ul><ul><ul><li>halt all bulk transitioning until new infrastructure installed, given the assessment of Parkville campus </li></ul></ul>
    10. 10. Mobility Transitioning <ul><li>Remediation due for completion mid year </li></ul><ul><li>Bulk transitions will recommence at this stage </li></ul><ul><li>Operational requests (new phones) now managed via the Service Desk </li></ul><ul><li>Caveats about coverage are communicated prior to any service being added centrally </li></ul><ul><ul><li>request form, website </li></ul></ul><ul><li>Overseas usage – valuable information on website </li></ul>
    11. 11. Unified Telecoms <ul><li>Questions? </li></ul>
    12. 12. Desktop Lifecycle Services Project Deborah Tapping
    13. 13. Project Rationale <ul><li>Cost containment - RDM </li></ul><ul><li>Whole of University approach </li></ul><ul><li>Leverage off University’s buying power </li></ul><ul><li>Consolidation of printer, photocopier, fax machines & scanners </li></ul><ul><li>Standardisation of Desktop Hardware and Desktop Build – O/S, SOEs </li></ul><ul><li>Streamline, automate and centralise processes </li></ul>
    14. 14. Project Objectives <ul><li>To create an aggregated model which will: </li></ul><ul><li>Centralise and streamline the procurement, tracking, configuration, deployment and disposal of Desktops </li></ul><ul><li>Implement a University wide Managed Print Service focusing on MFDs – Parkville only </li></ul><ul><li>Standardise desktop builds – O/S and SOEs </li></ul><ul><li>Design and deploy Thin Clients / Virtual Desktops </li></ul>
    15. 15. Project Workstreams <ul><li>4 Workstreams </li></ul><ul><li>Desktop Procurement – 1st Phase Dec 2009 </li></ul><ul><li>Printer/MFD Procurement using Managed Print Services (MPS) – Dec 2009 </li></ul><ul><li>Desktop Build – Dec 2010 </li></ul><ul><li>Thin Client / Virtualisation – Dec 2010 </li></ul><ul><li>NB : Approval to proceed to Business Case on first phase of Workstream 1 and to Discovery & Design of Workstream 2 </li></ul>
    16. 16. Project Overview
    17. 17. Workstream 1 - Desktop Procurement <ul><li>First Phase - By December 2009 </li></ul><ul><li>Enable Desktop procurement using the Victorian Government Purchasing Board </li></ul><ul><li>Tender for Macs to ensure premium vendor </li></ul><ul><li>All machines to leave factory with Base O/S </li></ul><ul><li>Second Phase – By December 2010 </li></ul><ul><li>Online procurement & tracking processes </li></ul><ul><li>Integration with Themis and Remedy </li></ul><ul><li>Centralised IS Procurement Team </li></ul><ul><li>All machines to be configured with Configuration Management Tool (i.e. Altiris) </li></ul>
    18. 18. Workstream 1 - Desktop Procurement <ul><li>Victorian Government Purchasing Board </li></ul><ul><li>PC & Notebook Equipment Panel </li></ul><ul><li>Can choose to purchase from one vendor or the entire Panel </li></ul><ul><li>Panel established in April 2006 for 3 years – up for review. Current vendors: </li></ul>
    19. 19. Workstream 2 - Managed Print Services <ul><li>Approval to proceed to Design & Discovery </li></ul><ul><li>Currently 2,182 staff printers </li></ul><ul><li>Rationalise number of printers - increase employee to printer ratio from 4:1 to 20:1 </li></ul><ul><li>Eliminate personal desktop printers and install MFDs </li></ul><ul><li>Investigate MPS options available </li></ul><ul><li>Offers significant reductions in cost and energy consumption </li></ul><ul><li>Can support multi-vendor environment in initial stages </li></ul>
    20. 20. Workstream 2 – Managed Print Services <ul><li>Case Study – Road Traffic Authority, NSW </li></ul><ul><li>Reduced devices from 2,100 to 750 </li></ul><ul><li>Resulted in savings of $4 million over 5 years </li></ul><ul><li>Decreased the print costs per FTE from $463 to $347 (based on 6,900 FTEs) </li></ul>
    21. 21. Workstream 3 – Desktop Build <ul><li>To commence after Procurement work </li></ul><ul><li>Standardisation of SoEs across UoM </li></ul><ul><li>Each SOE Build Model will include the Base Application (OS), Core Applications and Extended Applications. </li></ul><ul><li>Implementation of a Desktop Management solution (i.e. Altiris) </li></ul><ul><li>Standardisation of deployment processes and reduced Desktop support costs </li></ul>
    22. 22. Workstream 4 – Thin Client / Virtualisation <ul><li>Requirements analysis </li></ul><ul><li>Business analysis to understand cost and environmental impacts </li></ul><ul><li>Tender for an appropriate supplier(s) </li></ul><ul><li>Pilot using Library – 300 PCs </li></ul>
    23. 23. Conclusion <ul><li>Change Management component </li></ul><ul><li>Working Groups – need volunteers </li></ul><ul><li>Feedback is important </li></ul><ul><li>Questions? </li></ul><ul><li>Contact: Deb Tapping or Jo Cusack </li></ul>
    24. 24. Identity & Access Management Project Terry Brennan http://go.unimelb.edu.au/sa6
    25. 25. Overview <ul><li>What is Identity and Access Management </li></ul><ul><li>Why are we proposing an upgrade </li></ul><ul><li>Drivers and benefits </li></ul><ul><li>Scope of the project </li></ul><ul><li>Schedule </li></ul><ul><li>Budget </li></ul><ul><li>Questions </li></ul><ul><li>Contacts </li></ul>
    26. 26. What is Identity and Access Management? <ul><li>‘ The right access for the right people at the right time’ </li></ul><ul><li>Who are you? – Identification </li></ul><ul><li>How do we know? – Authentication </li></ul><ul><li>What access are you allowed? – Authorisation & Access </li></ul><ul><li>Is information about you and your transactions secure? – Privacy, security </li></ul>
    27. 27. Right access, right people … ?
    28. 28. Why upgrade? <ul><li>ARS system developed 15 years ago and enables registration for key systems including Themis, Merlin and LMS. </li></ul><ul><li>Risks and constraints  </li></ul><ul><ul><li>Aging technology </li></ul></ul><ul><ul><li>Design complexity </li></ul></ul><ul><ul><li>Difficult to retain knowledge and skills for system support </li></ul></ul><ul><ul><ul><li>single points of failure </li></ul></ul></ul><ul><ul><li>Barriers to delivering future benefits and improvements: </li></ul></ul><ul><ul><ul><li>single sign on', on-line employee on-boarding and improved processes for student on-line registrations </li></ul></ul></ul><ul><ul><li>Exposure to sophisticated security threats also lends weight to a replacement of the current infrastructure </li></ul></ul><ul><li>IT Architectural drivers </li></ul><ul><li>Business and strategic drivers </li></ul>
    29. 29. Current state
    30. 30. Drivers & Benefits - 1 Source: Gartner, Id#G00152051, 2007
    31. 31. Drivers and benefits - 2
    32. 32. One university’s experience <ul><li>Activity numbers </li></ul><ul><li>Accounts </li></ul><ul><ul><li>1812 Prof Staff </li></ul></ul><ul><ul><li>4566 Faculty staff </li></ul></ul><ul><ul><li>59064 Students </li></ul></ul><ul><ul><li>7944 Applicants </li></ul></ul><ul><ul><li>1095 Other </li></ul></ul><ul><li>500-1500 changes per day (more at semester starts) </li></ul><ul><li>Average provisioning time – 30-60 mins </li></ul><ul><li>Return on Investment </li></ul><ul><li>More than 13,000 staff hours recovered annually </li></ul><ul><li>Implementation of IDM resulted in 3 Year Cost Savings or Avoidance of $1.7M </li></ul><ul><li>40% Reduction in Account-Related Help Desk Calls </li></ul><ul><li>On-boarding time reduced from days to hours. Enrolments previously were cut-off 10 days prior to term, now are able to be accepted up to the day of the first class. </li></ul><ul><li>Better customer service and enrolment revenue </li></ul>
    33. 33. Drivers, benefits and objectives <ul><li>Reduce/eliminate access breaches, e.g. student labs </li></ul><ul><li>Support for multi-factor authentication </li></ul><ul><li>Integration with smart card technologies </li></ul><ul><li>Role based authorisation & access </li></ul><ul><li>Proactive event monitoring, reporting, auditing </li></ul>Improved security <ul><li>Reduce/eliminate compliance breaches – IT security, copyright, privacy </li></ul><ul><li>Improve / introduce proactive auditing capability </li></ul><ul><li>Reduce support risk of multiple point to point solutions on legacy infrastructure </li></ul><ul><li>Reduce risk to reputation </li></ul><ul><li>Meet compliance and privacy requirements by better auditing and tracking features </li></ul>Improved compliance / risk reduction <ul><li>Improved productivity with speedier user provisioning </li></ul><ul><li>Improved integration with enterprise applications facilitating role based authorisation. </li></ul><ul><li>Reduce support risk / overhead of multiple point to point solutions on legacy infrastructure </li></ul><ul><li>Increased web self-service capability, increasing quality & reducing load on central functions </li></ul><ul><li>Improved directory services & search capability: consolidated LDAP-based directories, single staff/student AD </li></ul><ul><li>Support for fee-for-service/billing per user </li></ul><ul><li>Opportunities to participate in collaborative activities, e.g. via NCRIS initiatives requiring federated identity support </li></ul><ul><li>Opportunities to improve business processes, e.g. simplified identity administration via distributed automated role based provisioning </li></ul>Reduce costs / improve efficiency & capability <ul><li>Enhanced user experience, e.g..seamless IT environment using single or reduced signon (RSO/SSO) </li></ul><ul><li>Speedier user provisioning – 0 days </li></ul><ul><li>Enhanced delivery capability for collaborative research, teaching and knowledge transfer activities by supporting federated identity initiatives e.g. Shibboleth support </li></ul><ul><li>University ID for life- e.g. for alumni management </li></ul><ul><li>Shared services / RDM support </li></ul>Strategic alignment, e.g.service delivery improvements impacting MSSM, Research & Teaching, Knowledge transfer, RDM Objectives Business Driver
    34. 34. Current state
    35. 35. Future state?
    36. 36. Scope
    37. 37. Scope - 2 <ul><li>Overarching IdM architecture </li></ul><ul><li>IdM requirements and solution design </li></ul><ul><li>Select, procure, implement IdM solution </li></ul><ul><li>Re-engineer existing Id data management processes </li></ul><ul><li>Improve system interfaces and interoperability via SOA approach </li></ul><ul><li>Restructure directory services and management </li></ul><ul><li>RSO / SSO </li></ul><ul><li>Business process and workflow improvement </li></ul><ul><li>Support for federated IdM - e.g. Shibboleth </li></ul><ul><li>Review IdM policies and practices </li></ul><ul><ul><li>Access management </li></ul></ul><ul><ul><li>Authentication </li></ul></ul><ul><ul><li>Authorisation </li></ul></ul><ul><ul><li>Privacy </li></ul></ul>
    38. 38. Schedule
    39. 39. Overall schedule – high level
    40. 40. Organisation – Draft only
    41. 41. Budget <ul><li>Investigation and implementation are expected to take approximately 18-24 months and will require project funds of approximately $3 million. </li></ul>
    42. 42. Questions?
    43. 43. Contact / Information points <ul><li>https://wiki.ea.unimelb.edu.au/display/IDMProject/IdM_Home </li></ul><ul><li>OR </li></ul><ul><li>http://go.unimelb.edu.au/sa6 </li></ul><ul><li>OR </li></ul><ul><li>[email_address] </li></ul><ul><li>Terry Brennan, Project Manager, ext 42724 </li></ul><ul><li>Frank Gomizel, Senior Business Analyst, ext 40338 </li></ul>
    44. 44. © Copyright The University of Melbourne 2008 Thank You Please stay and have some lunch