EMS Software Saves Schedulers at the University of Oregon
Overall Satisfaction with EMS Software
The University of Oregon is preparing to use EMS Software for event and class scheduling across our entire campus. Initial users will include the registrar's office, scheduling and event services, our alumni center and our business school; we hope to roll it out to additional departments within the next couple of years. This application and anticipated integration with other software will help aggregate our school's activities in a single source for better communication of information to customers and use by risk management services.
Pros
- The graphic user interface is well-designed and intuitive, which promotes productivity.
- It provides workflow functionality for schedulers and service providers to efficiently relay event details and status.
- The user-defined fields add the ability to customize reservation and space records to better meet campus business needs.
Cons
- Bookings contain a limited number of standard time fields (event start, event end, setup time, teardown time); more options here are desirable.
- Resource records are not as robust as some of the other areas, and could benefit from additional standard and user-defined fields.
- Applying blackouts to spaces (to prevent bookings during certain times) appears to be a challenge: we believe it can be done, but the process doesn't seem to be straightforward.
- We have barely begun implementation of this product, so I am not in a position to address the ROI piece.
- I can say that many campus partners are elated with the prospect of using this software as a replacement for previous software that they felt to be inferior.
- I believe the long-term impact of EMS Software on the UO will be positive, although it is too early to call out specifics.
As I previously hinted, our campus chose EMS Software because we felt it better met our needs in terms of flexibility for both academic and non-academic scheduling and contained superior functionality and ease of use for a variety of user types (pro staff, faculty, students, community members, etc.). Another factor that prevailed was the positive attitude of EMS personnel and willingness to provide expanded answers to followup questions during the evaluation process. Our selection team felt very confident we would have a good, honest working relationship with the vendor.
Using EMS Software
250 - Users of the product are both department schedulers of campus spaces and resources and faculty/staff who have need for places to hold meetings, workshops, presentations, etc. The software captures single- and multi-date bookings for a variety of different activities sponsored by student organizations, campus departments and non-affiliated entities using campus facilities.
10 - In-house support for this product falls into two general categories: functional and technical. Functional support personnel need to be familiar with the software's design and capabilities, and also with how various elements are configured. Technical support personnel need similar knowledge, along with insight into back-end operations. Because our school's instance is cloud-hosted, there is less need for in-house technical support. Typical problem troubleshooting involves replicating a user's issue, then using knowledge of the product's functionality to make corrections or modifications to achieve the outcome the user expects or desires.
- Entering and tracking space and resource bookings.
- Reporting on data stored in the software (weekly event schedule, daily room setup list, etc.)
- Invoicing events to capture revenue.
- We are starting to build a centralized system of record that can be used campus-wide to aid with public safety and emergency management matters.
- Integration of event data with digital signage.
- Integration with Outlook for a simplified user experience.
Evaluating EMS Software and Competitors
Yes - This product replaced R25 and 25Live, which are CollegeNET products. The main driver for replacing the old software was changes the vendor made that phased out the thick client (R25 - which was quirky but usable) and forced customers to use its web-based client (25Live - an inferior product we tested and didn't like). Other factors included aggressive/argumentative customer support and the poor reputation CollegeNET had developed on our campus over the past 10 years. Those leading the project felt we needed better software and good vendor relations to successfully bring all campus entities onboard.
- Product Features
- Product Usability
- Product Reputation
- Positive Sales Experience with the Vendor
Probably the most-important factor that led us to choose EMS software was a combination of product features and usability. We required software with a straightforward user interface that people at all skill levels could instantly employ to build events, book spaces, assign resources and share this information with others via different platforms. EMS offered a robust desktop client for power users and web application for simple bookings; we purchased both to serve the varied needs (and anticipated future needs) on our campus.
I would have made the process more rigorous by requiring product demos to be more in-depth and would have stipulated that we have the ability to have a trial use of each vendor's product for a period of time so that we could evaluate its merits and drawbacks beyond quick observation and conjecture that occurs during fast-paced presentations.
Comments
Please log in to join the conversation