Page 18 - Campus Technology, October/November 2018
P. 18
CLOUD COMPUTING
GAMECHANGER
One of the key advantages of moving to a cloud-based environment is the agility this brings to the delivery of ap- plications. Because software updates happen automati- cally in the cloud, institutions no longer have to spend a lot of time and resources in deploying them. But this advan- tage is lost if IT staff are still locked into the old mindset of developing highly customized applications by creating a number of extensions and unique configurations.
If you’ve made several modifications to your software over the years, take some time to evaluate which of these is worth preserving in your new cloud environment, Corb recommended — and which you can live without. “In my ex- perience, a number of these customizations were personal preferences,” he said. “If challenged, they couldn’t stand up.”
STAFF EXPERTISE MUST EVOLVE
The skill sets involved in shifting from an environment of cus- tomization to one of configuration must change as well, Corb observed. Instead of a cadre of software engineers who cus- tomize application source code,, institutions will need busi- ness process analysts and systems integrators: people who understand how to make various systems communicate and
RETHINKING HOW TECHNOLOGY IS USED IN EDUCATION
exchange information in real time.
The role of IT managers must evolve as well. “Modern
IT managers are doing a tremendous amount of contract management, because they are dealing with many cloud vendors,” Corb explained. “They are doing a great deal of integration and vendor management. They become much more of a technology-savvy business person, rather than the other way around.”
NO NEED TO GO IT ALONE
Working with a proven cloud provider who is responsive to your institution’s needs and who serves as a full part- ner in your cloud migration project can help you manage this change effectively.
“You want there to be a relationship that goes beyond the transaction itself,” Corb said. “At the end of the day, the cloud is simply an implementation detail. If I’m a registrar or a dean, it shouldn’t matter where the code is executing. It’s more about: Did we listen to everyone’s voices, and did we effectively lead them through this change? Did we capture their requirements appropriately and determine the right solution to help them? Those are the things that matter the most.”
PRODUCED BY: SPONSORED BY:
For more information, please visit:
Oracle.com/higher-education
rangizzz/Shutterstock