Transforming the Role of Technology in Research and Education Institutions

In attempting to better position themselves, CIOs from the HiED community came together in 2010 to establish and express to cloud service providers a consistent set of expectations around business, legal, and security terms as well as providing guidance on commonly acceptable technical integration requirements, particularly on identity management and to leverage community assets such as the Internet2 R&E Network and community developed middleware. This initiative represents a sea-change in how decisions around technology acquisition are approached and describes a new pathway for the R&E community to engage with service providers at scale.  

Whether for on premise or external cloud services, data security keeps all of us up at night. a CIO's professional career can be significantly and adversely impacted on by any form of security failure. The challenge of course is the relative immaturity of our collective understanding of how best to balance the distribution of responsibility for security failures and how far is far enough when it comes to investments in and payments for security protections. In particular, R&E institutions have to strike a rather delicate balance between a protecting institutional constituencies and maintaining a healthy creative and academically open environment for discovery and learning–areas where risk tolerances and failure rates are often high.  

The financial sustainability of legacy technology offerings is another major area of concern. We likely passed the sustainability threshold at the beginning of this decade. We are keeping the lights on, but as the spread between cost-effective cloud solutions and legacy on-premise solutions continues to grow, the increasing opportunity cost of continuing inefficient solutions makes CIOs appear insensitive and apologists for technology stacks that out of date. With successive budget cuts to HiED over the past two-three decades, further exaggerated during the global recession, there is simply not enough money available to fund continuing operations of legacy systems–and even funding the transition to new technologies is increasingly out of reach. I have often heard the counter that ‘… we don’t need to fix what is not broken…’, but that ignores the reality that no one would seriously consider implementing legacy technologies if the slate were wiped clean.  

The 'high-anxiety' nightmare scenario for HiED CIOs is the political and budgetary battle over retaining the legacy mindset of highly customized solutions in the face of multi-tenant, shared services and the associated requirement for standardization. CIOs are being asked to make the argument that decades of painfully arrived at idiosyncratic processes and practices have no describable value in improving educational outcomes, that there is no research or business value in differentiation based on how an IT service is provisioned, and that the inefficiencies and distractions such empty differentiation cause are damaging to our institutions.   

To meaningfully migrate ourselves out of confluence of concerns over security and the politics of change, it is essential to cultivate and foster greater collaboration between and among institutions and service providers. We simply cannot afford the financial costs of bad outcomes–and simply put, neither side of the market can afford to work without the benefit of the other party's ability to mitigate against unknown (and unanticipated) risk. Service providers to HiED need to hear consistent messages from our community and that means the research and education sector needs to develop a more consistent and coherent voice. The consequences of failing to do so effectively and at the right scale are frankly quite concerning.