- Academics & Research
- Security & Privacy
- Accounts & Access
- Get Help
The project list contains the current work in progress. For more information about the projects, contact the project manager.
A La Carte Service Creation and Implementations
The goal of this project is to create and release several new end user computing services: Windows platform as a service, Mac platform as a service, MPrint platform as a service, iOS platform as a service, Engineering consulting and development as a service, Desktop Support consulting and development as a service. These new services are designed to meet campus needs with at-scale, flexible, and self-managed end user computing products and services in order to lower overall service cost and empower unit IT on focus differentiating technology.
Backstage Content Migration - Summer 2017
A small project effort that includes 2017 interns to move Backstage content to a new format. This project is only expected to last the summer.
BYOD Core Capabilities
This project is part of the Bring Your Own Device (BYOD) program. The BYOD trend on campus has been increasing and presents opportunities and challenges that need to be addressed in order to meet the evolving technology needs of faculty, staff and students. This project focuses on increasing faculty, staff, and student productivity by Enabling and optimizing core applications, such as printing and access to U-M storage, on personal devices.
Campus Wide WiFi Upgrade
Students, faculty, staff, and administrators agree that current WiFi networks are inconsistent and insufficient to meet the demands of an increasingly mobile and collaborative learning environment.
The University of Michigan IT Executive Council has been asked to consider an additional $24.4 million WiFi Network upgrade project including 275 academic, research, administrative and residence hall buildings on the Ann Arbor campus. This effort continues progress to provide consistent coverage in facilities where the majority of teaching, learning, research, and work occurs across campus.
The 275 buildings that have been recommended by ITS for upgrades to their WiFi netowrks are listed in priority order. The actual order that buildings are upgraded, however, has to do with many factors such as when the building is available for construction activity and when the building may be undergoing renovations. Each building is subject to final CIO and Provost office approval when a more detailed building evaluation and construction cost estimate is completed.
In answer to this concern, the University of Michigan Provost has approved three capital investment projects. These projects are to provide one-time funding for WiFi network upgrades. This effort will establish pervasive connectivity in libraries, public-facing university buildings, residence halls and academic spaces critical to our student services and academic missions.
Campus WiFi Upgrade Projects are significant initiatives designed to bring the network to a consistent standard of coverage, capacity, and capability. Achieving these standards will permit our students, faculty, and staff to teach, learn, and work anytime and anywhere in these facilities. Upgrades will also deliver a consistently positive WiFi experience for our prospective students, parents, alumni, and guests.
Not included in these projects are funding to improve networks in the University of Michigan Health System, U-M Dearborn, and U-M Flint campuses.Improved user experience;
Consistent coverage provided;
Increased capacity with more access points and more spectrum;
Device location information to enable future applications provided;
Service based on factors such as the user, the device, the location of the device or the service being used provided; and
Improved the ability to diagnose user access issues
In total, this project will affect 458 buildings in Ann Arbor, 171 of which are classroom, research or administrative buildings. The remainder are housing (253) and athletics (34). The secondary proposal is to provide on-going funding to ITS to upgrade the Wi-Fi electronics every five years.
DART - Move DART Non-Production to Azure
Move the non-production environments for DART into Azure.
DART-Phase 2 Grateful Patient Integration
Complete analysis of the UMHS newly developed Grateful Patient system, identify means of data integration with DART, and implement solution.
Develop CUI Compliance Strategy
Develop a controlled unclassified information (CUI) compliance strategy. Develop in partnership with University of Michigan Office of Research (UMOR), Michigan Medicine Compliance, Office of General Counsel (OGC), and Information Assurance a compliance program to support the university’s CUI compliance through the delivery of policy, process, security templates and training. Develop a CUI Public Cloud Strategy, and proof of concept, that maps out the technical and financial requirements including architecture, performance, roles and responsibilities, workflows, IT security controls, and costs. Includes collaboration with the implementation of Yottabyte Research Cloud (YBRC) for CUI Compliance and associated systems.
Develop Michigan IT Staff Development Program
Develop a new program to provide professional and skill development for all 2700 Michigan IT professionals.
Develop sys continuity plans for critical infra
This initiative will identify and classify ITS critical core infrastructure systems, and re-architect these systems to be highly available and resilient. The goal is for systems to able to maintain their capacity and production workloads, even in the event of small-scale faults or a large-scale disaster. We will develop options to increase the resiliency of these systems and propose improvements under the guidance of ITS senior leadership after weighing the scope, risk, and costs of the alternatives.
DIG - Implement Container Platform
The focus of the DIG (Digital Innovation Greenhouse) - Pilot Container Service project (aka Platform as a Service) was to examine the landscape of management tiers, recommend one, and begin to support DIG applications on the recommended software. Red Hat's Open Shift has been recommended to ISO management. This new request is to implement OpenShift, and hand off to the DevOps team.