OPERATIONAL IT COMMITTEE MEETING AGENDA WEDNESDAY, MAY 23, 2012 3:00 4:00 p.m. FAC 228D

Similar documents
RESEARCH AND EDUCATIONAL TECHNOLOGY COMMITTEE MEETING AGENDA Thursday, May 17, :00-9:00 a.m. FAC 228D

I. Administrative Systems Master Plan Update (Mary Knight)

Task Force Charter. Mobile Strategy Document Version 3.0 Chief Information Officer, ITS Last Edited December 17, 2012.

How To Write A System Replacement Plan

OPERATIONAL IT COMMITTEE MEETING AGENDA Wednesday, September 26, :00 p.m., FAC 228D

Project Charter. VoIP Plan Task Force Document Version 3 Prepared by Sandra Germenis, ITS Last Edited October 19, VoIP Plan Task Force

RESEARCH AND EDUCATIONAL TECHNOLOGY COMMITTEE MEETING AGENDA Thursday, April 18, :00-9:15 a.m. FAC 228D

IT Architecture and Infrastructure Committee

VoIP Deployment Committee Charter

Project Charter. UT Web Infrastructure Project Document Version 9.0 Prepared by John Lovelace & David Moss Last Edited March 13, 2012

Project Charter. Identity & Access Management Strategy. Executive Summary. Business Need and Background. Document Version 1.

Project Charter. Office Migrations Document Version 2.0 Prepared by Sabina Winters, ITS Last Edited February 19, 2015

STRATEGIC IT ACCOUNTABILITY BOARD (SITAB) AGENDA WEDNESDAY, JUNE 15, :30 3:30 p.m. STARK LIBRARY

DESIGN BUILD TEST TRAIN/DEPLOY MAINTENANCE

CASI Project Charter. Centralized Authentication System Implementation. Executive Summary. Business Need and Background

OPERATIONAL IT COMMITTEE MEETING AGENDA Wednesday, February 27, :00 4:00 p.m., FAC 228D

NIST Cloud Computing Program Activities

II. Apps Contract Overview (Catherine Camillone, Julienne VanDerZiel)

OPERATIONAL IT COMMITTEE MEETING AGENDA Wednesday, July 25, :00 4:00 p.m. FAC 228D

Project Report and Recommendations

DESIGN BUILD TEST TRAIN/DEPLOY MAINTENANCE

DESIGN BUILD TEST TRAIN/DEPLOY MAINTENANCE. This project is part of the Identity and Access Management Roadmap.

Gartner, Inc. DIR-SDD-2042

1 ERP_GEUPD (Group Upgrade) Project Charter Version 1.4 Prepared by Cooper Henson, ITS Last Edited November 15, 2012

OPERATIONAL IT COMMITTEE (OIT) MEETING NOTES WEDNESDAY, JANUARY 27, 2010

Introduction and Purpose... 2 Scope... 2 Auxiliary units Part-Time, Temporary faculty/staff, Volunteer, Contractor and Student Assistants...

ARCHITECTURE)&)INFRASTRUCTURE)COMMITTEE)MEETING)AGENDA)) Friday,)April)11,)2014) 9:00) )10:30)AM) FAC)228D!!!! I.!9:00!!9:15!IT!Shared!

III. 9:35-9:50 Retirement of Web Space- Communication Plan Endorse (Dave Moss)

Project Charter. Secure Message System Upgrade

Calendaring and Strategy Recommendation Summary

LDAP Authentication Configuration Appendix

Integrating Project Management and Service Management

GOVERNMENT USE OF MOBILE TECHNOLOGY

STRATEGIC IT ACCOUNTABILITY BOARD AGENDA Tuesday, July 30, :00 5:00 p.m. STARK LIBRARY

Custom Development Methodology Appendix

SCT Event Driven Appendix (LDI Event Integrator)

Department of Administration Portfolio Management System 1.3 June 30, 2010

Information Technology IT Support

DATA CENTERS AND SERVERS

Audit of the Test of Design of Entity-Level Controls

We have made significant progress during the past few years in these areas.

Audit of the Data Center Consolidation Initiative at NARA. OIG Draft Audit Report No May 10, 2012

IT Operational Oversight Committee. Project Title IT Hardware/Software Training for Staff. May 25, 2012

SharePoint 2013 Project Charter

LGS Project Management Methodology

Integrated Technology Plan (FY10 FY12)

The University of North Texas at Dallas Policy Manual

Scientific Cores/Service Centers Administrative Manual. Responsible Office: Associate Provost for Research. Introduction

DESKTOP SUPPORT SERVICE LEVEL AGREEMENT

Windows 7 IMPLEMENTATION PLAN. Version 1.3

PUBLIC HEARING TO DISCUSS TUITION AND FEE PLANS

Scope of Work Microsoft Infrastructure Upgrade

CODE: E.003 Financial Services BUDGET AND BUSINESS PLANNING POLICY. 1.2 The essential activities covered by this policy include:

CENG Information Technology Services University of North Texas

IUanyWare and Teaching & Learning

[BSU Mobile] [Version Number 1.2] Project Charter. Bridgewater State University Information Technology. BSU Mobile. Project ID:

PROGRAM DESIGN. Our design process, philosophy and values.

Service Level Agreement

INSTRUCTIONAL TECHNOLOGY STANDING COMMITTEE Penny Rice, Chair

IUanyWare, IU Box, & Your Courses Part 1: Productivity, Efficiency, & Quality

Request for Expressions of Interest On a contract to perform: Renewal of Information Technology Strategic Plan

Admissions Marketing Plan Assessments

Crosswalk Between Current and New PMP Task Classifications

Network for Change and Continuous Innovation 2014 National Conference. Enabling Effectiveness: Using Governance and Technology to Drive Improvement

Department of Audit and Compliance. Quality Self-Assessment

UQ BLACKBOARD IMPLEMENTATION PROJECT JUNE 2004 JULY Change Management and Communication Plan

Global Headquarters: 5 Speen Street Framingham, MA USA P F

Version Date Description Author(s) 1.0 2/17/2014 Initial SLA Created ITC Administration

ARCHITECTURE & INFRASTRUCTURE COMMITTEE MEETING AGENDA FRIDAY, December 14, :00 10:30 AM FAC 228D

Service Level Agreement Between: Computing and Informational Technology And The Finance and Business Operations Division

Information Technology Governance Accountability Report OCTOBER 2014

STRATEGIC IT ACCOUNTABILITY BOARD AGENDA Wednesday, December 19, :00 3:00 p.m. STARK LIBRARY

The University of Western Ontario Arthur Labatt Family School of Nursing. MScN Thesis Guidelines

UF ONLINE ANNUAL REPORT Submitted July 21, 2014 by the Advisory Board for UF Online

Educators Workshop in Solar Energy, Energy Auditing and Lighting Technologies

Division of Academic Affairs Technology Fee Project Proposal 2014

Goucher College Help Desk Service Level Agreement

Iowa State University Proposal for HR-01 ISU HR Operating Model

The Game Changers in Online Learning Series

Information Technology Services (ITS) Update

Office of Budget and Financial Planning

Request for Proposals

IT Project: System Implementation Project Template Description

Project Management Professional (PMP) Examination Content Outline

Project Charter EMI Outreach July 25, OE Project Charter. 1.0 July 25, 2011 Draft w/ VC Denton comments included /02/2011 Proofed/edited

INFORMATION TECHNOLOGY SERVICES TECHNICAL SERVICES Program Review

NET+ INFRASTRUCTURE AND PLATFORM SERVICES PORTFOLIO STATUS & UPDATE

WASC Accreditation Visit March 2009

Company A Project Plan

State of Minnesota. Enterprise Security Program Policy. Office of Enterprise Technology. Enterprise Security Office Policy. Version 1.

OVERVIEW. We seek consultative services that would deal with the following objectives:

Cloud Consultancy for Schools. Professional Cloud Adoption Consultancy services for the UK education sector.

Hardware and Asset Management Program

UITS Strategic Plan. Annual Review and Progress Report. October 2015

Information Technology Strategic Plan and Review Colorado State University Pueblo

IT Cost Reduction. Doing More with Less. Anita Ballaney, Vishwanath Shenoy, Michael Gavigan. Strategic IT cost reduction - Doing More with Less

Budgeting and Planning Process

Solutions Master Data Governance Model and Mechanism

Academic Year Administrative Assessment Report The Office of Human Resources

The purpose of this document is to define the Change Management policies for use across UIT.

Transcription:

OPERATIONAL IT COMMITTEE MEETING AGENDA WEDNESDAY, MAY 3, 01 3:00 4:00 p.m. FAC 8D I. Cloud File Sharing Task Force Recommendations (Ryan Baldwin) II. UDC Printer Repair Transition to Campus Store (Michael Cunningham) III. Funding Scenarios (Brad Englert)

Cloud File Sharing Document Version 1.1 Joe Howe Cloud File Sharing Task Force Chair Last Edited April 1, 01 Task Force Charter Cloud File Sharing Executive Summary The purpose of the task force is to accelerate the requirements analysis, review, and large scale pilot implementation of the Box solution provided via the Internet Net+ service offering. The task force will also provide requirements and analysis to inform future reviews of cloud file sharing services. Business Need and Background The use of cloud-based file sharing services such as Dropbox has increased significantly over the past 3 years. With features like synchronization of files to multiple computers, sharing files with others via shared folders or web links, and integration with mobile software, it is easy to see why this type of service has grown in popularity so quickly. The use of these services for University business can and in some circumstances does violate existing policies that govern the use and protection of the University s data. In late 011, Box and internet announced plans to offer a hosted cloud file sharing service focused on higher education for the technology, security, and contract language. This effort has continued to progress and will be available very soon. An informal pilot was already underway on the UT campus. Project Description The task force will define the requirements needed to provide a cloud-based file sharing service to the UT campus that also complies with existing University policies. Next, the group will coordinate the evaluation of the Box service for campus, comparing it to the requirements. The final document will also serve as the framework for other cloud file sharing services investigated by campus. The effort will be supported by guidelines and best practices derived from campus, business, research, and teaching use cases and industry trends. The task force will incorporate anticipated resources, budgets, infrastructure, and workforce needs of campus into the process. 1

Cloud File Sharing Document Version 1.1 Task Force Goals The goals of the task force are: Identify Use Cases and Requirements Identify use cases and requirements for UT and cloud-based file sharing on campus Benchmark current efforts at other leading universities focused on early adopters of Box Review of Box and Similar Services Systemic review of the Box service based on UT requirements including gathering specific feedback on Box from key technical and non-technical users Basic review of other leading cloud file sharing services based on UT requirements Provide final report with recommendation including Box assessment and framework for reviewing potential options in the future Resources, Support and Future Options Draft resources, budgets, infrastructure, and support needs to offer a cloud based file sharing service Identify best practices and future trends for use of cloud-based file sharing in the classroom, in research, in business operations, and engaging in campus life Schedule and Milestones Milestone/Deliverable Identify use cases and requirements for cloud-based file sharing on campus Benchmark current efforts at other leading universities, focused on the early adopters of Box Systemic review of the Box service based on UT requirements including gathering specific feedback on Box from key technical and non-technical users Basic review of other leading cloud file sharing services based on UT requirements Provide final report with recommendation including Box assessment and framework for reviewing potential options in the future Draft resources, budgets, infrastructure, and support needs to offer a cloud based file sharing service Identify best practices and future trends for use of cloud-based file sharing in the classroom, in research, in business operations, and engaging in campus life Target Date 3/30/1 4/13/1 4/13/1 4/13/1 4/0/1 4/0/1 5/4/1 Scope The task force will work to quickly assess the UT use cases and requirements for a cloud file sharing service, coordinate a hands-on review of the Box service and identify resources required to pilot the Task Force Charter

Cloud File Sharing Document Version 1.1 service on a larger scale. This information will also be useful in future reviews of cloud file sharing services In Scope Items that are in scope include multi-year budget projections, anticipated security measures, anticipated infrastructure requirements and resources, anticipated workforce requirements. Existing UT services like Webspace will also be considered in the use case review. Out of Scope Out of scope items include transitioning/decommissioning Webspace, identifying funding options, coordinating the actual implementation of a service and performing in depth reviews of other options besides Box. Some of these may require convening a new group to focus on that issue. In addition, the best practices and guidelines work from the Cloud Computing Best Practices Task Force will be leveraged where possible. The functions already assigned to that group will be out of scope for this task force. Task Force Management and Governance The cloud-based file sharing strategy falls under the auspices of the Architecture and Infrastructure Committee. Role Name(s)/Title(s) Responsibilities Executive Sponsor(s) Brad Englert/Chief Information Officer Project Manager Technical Lead Project Team Information Security Officer Stakeholder(s) Ryan Baldwin/AIC Committee Chair Project Facilities and Resources To develop the cloud-based file sharing strategy, the following resources will be necessary: Meeting and interview space that is available on a regularly scheduled basis Time from faculty, students, and staff for surveys and interviews Time from faculty, students, staff of peer institutions for selected and targeted interviews Survey development tools (e.g. Survey Station UT s survey service) Web posting space for sharing collaboration documents Impact Analysis Impact analysis will be developed in tandem with the work of this task force. Task Force Charter 3

Cloud File Sharing Document Version 1.1 Assumptions Assumptions will be developed in conjunction with the work of this task force. Constraints The project will be time bound. Interviews with targeted members of our peer institutions and a survey of the representative population and their uses, and best practices will be used to make a generalized strategy for campus. Risks The largest risk for the project will be getting good data in a limited amount of time. Focus must be maintained on the goals of this task force and not on the numerous other components of the final implementation and endless possibilities. Due to the short time frame, it is critical to have a good information and feedback gathering plan, targeting the right people with the right questions. Revision History Version Date Description V 1 /8/01 Initial draft completed V 1.1 3/14/01 Revised draft, focused on current Box opportunity Signatures Name Role Signature Date Ryan Baldwin AIC Chair and Infrastructure R&E Committee Member AIC Committee Member BSC Committee Member Cam Beasley (or his delegate) William Green (or his delegate) Pei Chen (or her delegate) Undergraduate Student Graduate Student Research Infrastructure Business Information Security Networking Systems Student Student Task Force Charter 4

Cloud File Sharing Task Force Summary of Recommendation The Cloud File Sharing Task Force recommends moving quickly forward with the Box service via Internet for both individual allocations and departmental folders. In order to spur rapid adoption, the Box offering should offer substantial benefits over other incumbent solutions such as Dropbox. To reduce the startup cost, Box should be approached about a reduced contract for the first year while UT develops and promotes the service. Negotiations with Box should address accessibility concerns, enterprise authentication challenges and user feature gaps. Once a Box solution is in place the existing Webspace service should be actively decommissioned In addition to a Box solution, the upcoming Google Drive offering for higher education should be watched closely as a potential solution to augment Box, especially for undergraduate students. Background The use of cloud-based file sharing services such as Dropbox has increased significantly in an ad-hoc fashion across campus. The use of these services for University business can and in some circumstances does violate University policies. Over the last year, two potential cloud based solutions to this predicament have developed - Box (via Internet) and Google Drive (to be released as part of UT s Google Apps for Education). In March, the Architecture and Infrastructure Committee launched the Cloud File Sharing Task Force to (1) Identify Use Cases and Requirements, () Review of Box and Similar Services, and (3) Identify Resources, Support and Future Options. Box is a mature company offering enterprise cloud file sharing with competitive features like mobile access, sync, and collaboration. The Internet agreement provides reduced pricing, robust security, and a university focused contract. Drivers of Change 1. Current use of Unapproved Services by many faculty and staff potentially involving sensitive data. UT file sharing services like Webspace are cumbersome and lack modern features Challenges and Opportunities 1. Accessibility Box is aware of gaps and is working on fixing them but has not made significant progress.. Enterprise Integration a few challenges have been identified with using the authentication mechanisms offered by Box. Integration appears feasible but will require planning, effort, and possibly adjustments by Box. 3. Rapid Timeline Staging for a Fall 01 launch, even a soft launch, provides a short timeframe for developing the support processes and provisioning interfaces needed for deployment to individuals and departments. 4. Current use of Dropbox Many at UT have already started using Dropbox and appear pleased with the service. Any UT offering should have comparable features and space. 5. Uncertainty of Google Drive The availability and cost of Google Drive make it worth evaluating as details emerge. There are still significant questions with use of the Google Drive including security, accessibility compliance, enterprise management, scaling storage allocations, and usage by departments 5/10/01 Additional Background, details and findings are available in the Cloud File Sharing Task Force Report

UDC Printer Repair Center Transition / Closure Proposal Executive Summary and Recommendation The UDC has operated a repair service for student lab printers and departmentally owned printers. With the transition of Lab Printer responsibility to User Services in 01, and the declining requests for repair in general, it is not deemed feasible to maintain an operation of this nature. The Campus Store currently offers an equivalent alternative for repair on the campus. The recommendation is to close the UDC Printer Repair Service and refer any existing and future business to the Campus Computer Store. Student Lab Printers The ITS managed student lab printers are at various locations across campus and enable students to print their documents from their own computers. There are other locations managed by departments and colleges, and are not considered part of this analysis. Student lab printer repair is now managed by ITS User Services. These printers are typically repaired by Dell within their warranty program. Department Printers Department owned printer repair has continued to be offered by UDC. In general, these printers are older and no longer under any warranty. The number of repairs performed by the repair shop continues to decline every year and the service is no longer cost effective. We have used this opportunity to distribute the once full time technician duties to other areas of need within UDC. Printer Repair Totals by Fiscal Year 400 300 00 100 0 335 157 116 FY 07-08 FY 08-09 FY 09-10 FY 10-11 FY 11-1 Year to Date 38 Customers by Usage FY11-1 (YTD) Other (1 Repair) Liberal Arts Instructional Technology Psychology, Liberal Arts Mechanical Engineering Educational Psychology Chemical Engineering Pharmacy LBJ School McCombs 3 4 6 15 0 4 6 8 10 1 14 16

Campus Computer Store The Campus Computer Store currently offers a centrally located, service equal to the UDC service offering. A review shows they have certified technicians on staff and are capable of repairing most printers. They are also Dell warranty certified. Transfer of the additional workload will not exceed their capacity or capability. The store has comparable rates and is currently engaged in the Printer Repair service for faculty and staff. In addition, it has the capability to offer services to students a service that UDC could not provide. The store will accept UT Procards or a purchase order for payment. Cost to transition to the store for ITS and other Campus users is nearly neutral. SERVICE UDC Printer Repair Service Cost * Campus Computer Store Cost Diagnostic Fee $35.00 $30.00 Pickup and Delivery Fee $5.00 $30.00 Hourly Rate $55.00 $75.00 Technician Trip Charge (Onsite) $46.00 $15.00 per hour *Rates have not been reviewed since September 1, 008 UDC Printer Service Shut Down Plan April 4, 01 Review with ITS Senior Staff May 1, 01 Develop communication plan announcing the decision and methods to engage the Campus Store o ITS o Campus May 11, 01 Obtain ITS Governance Approval (Architecture & Infrastructure Committee May 3, 01 Obtain ITS Governance Approval (Operational Information Technology Committee) May 4, 01 Notify the Campus Computer Store Manager of the planned change and timing. May 5, 01 Meet with UDC Staff to inform them of the planned change. Notify Campus. June 1, 01 Stop receiving walk-in requests at the UDC Printer Repair June 15, 01 Complete any remaining work in progress Aug 31, 01 Stop receiving contract work at UDC Printer Repair Sept 19, 01 Complete any remaining work in progress

IT Governance Continuum of Funding Options Locally Funded Aggregate Funding to Reduce Costs Aggregate + Partial Central Common Good Subsidy In-Kind Echo 360 CrashPlan for General Use Adobe Connect Encryption Software Computer Aided Design Apple Education Licensing Program Bevo Ware 1) Survey Station Media Site Help Desk ) imodules CrashPlan for Faculty Webspace Blackboard Austin Exchange Pending Requests 1) Replace Survey Station with enterprise Qualtrics license; Engineering and Business want this to be Common Good ) Development and Texas Exes fund; Development wants Common Good funding for imodules 3) Cloud file sharing; request for Box to be Common Good Page 1of 1 May 17, 01, Version.0