1. Upgrade Conundrum
Presented by: Adrian Smith, Director of Administrative and Enrollment Systems
Metropolitan College of New York
June 17, 2015
PCNEAT 2015: It’s New York Sweet

2. What is there to discuss?
PCNEAT 2015: It’s New York Sweet

3. Sometimes the we are out of balance!
PCNEAT 2015: It’s New York Sweet

4. Why stay on your current version?
There isn’t anything on the newest version we need.
Testing and rollout activities take too long.
PCNEAT 2015: It’s New York Sweet

5. Why stay on your current version?
We customize Self-Service and those customizations must be reapplied during each upgrade.
“Better the devil you know than the devil you don't know” –Unknown
PCNEAT 2015: It’s New York Sweet

6. Why stay on your current version?
What are your reasons?
PCNEAT 2015: It’s New York Sweet

7. Why upgrade? Technical currency updates Defect corrections
New features (?)
PCNEAT 2015: It’s New York Sweet

8. Why upgrade?
What are your reasons?
PCNEAT 2015: It’s New York Sweet

9. Why upgrade?
Ellucian PowerCampus Product Support Lifecycle
PowerCampus provides application support for the most current release along with the most current prior minor release. Patches that have been delivered to these versions are considered a release.
Effective June 2015, the releases being supported are and 8.6.1
PCNEAT 2015: It’s New York Sweet

10. Let’s look at history - 2013 PCNEAT 2015: It’s New York Sweet 8.3.0
8.3.0
8.4.0
8.5.0
8.6.0
2012
December
2013
January
February
March
8.3.1
April
May
June
July
8.3.2
August
September
October
November
PCNEAT 2015: It’s New York Sweet

11. Let’s look at history - 2014 PCNEAT 2015: It’s New York Sweet 8.3.0
8.3.0
8.4.0
8.5.0
8.6.0
2014
January
February
March
8.3.3
April
8.4.1
May
June
8.3.4
8.4.2
8.5.1
July
August
8.4.3
8.5.2
September
October
November
December
8.4.4
8.5.3
PCNEAT 2015: It’s New York Sweet

12. Let’s look at history - 2015 PCNEAT 2015: It’s New York Sweet 8.3.0
8.3.0
8.4.0
8.5.0
8.6.0
2015
January
February
March
8.4.5
8.5.4
April
May
June
8.5.5
8.6.1
PCNEAT 2015: It’s New York Sweet

13. How do we address the concerns we have identified?
There isn’t anything on the newest version we need.
Be active in the user community engaging Ellucian. Every version should have something that your institution sees as valuable.
PCNEAT 2015: It’s New York Sweet

14. How do we address the concerns we have identified?
Testing and rollout activities take too long.
Develop a testing plan that places the responsibility on the department heads. Encourage there involvement and listen to their concerns.
Ellucian has restructured Self-Service and Database upgrade activities to minimize pain during upgrades. Engage Ellucian and share your ideas for improving the process further.
PCNEAT 2015: It’s New York Sweet

15. How do we address the concerns we have identified?
We customize Self-Service and those customizations must be reapplied during each upgrade.
As mentioned, the process has improved greatly within the past year.
PCNEAT 2015: It’s New York Sweet

16. How do we address the concerns we have identified?
“Better the devil you know than the devil you don't know” –Unknown
Stay aware of version releases and monitor eCommunities. There is likely a school that upgrades before you and will likely share their experience if you ask.
PCNEAT 2015: It’s New York Sweet

17. Finding your campus balance
PCNEAT 2015: It’s New York Sweet

18. Finding your campus balance
PCNEAT 2015: It’s New York Sweet

19. Recommendation
Pick one upgrade window a year and rally your institution around staying ‘close’ to current.
Discuss your upgrade concerns with your Ellucian Client Partner. They are your advocate.
PCNEAT 2015: It’s New York Sweet

20. Questions and Comments
Adrian Smith
Director of Administrative and Enrollment Systems
Metropolitan College of New York
PCNEAT 2015: It’s New York Sweet