70 likes | 208 Views
A Context for Enterprise Applications. Christine E. Haile CIO University at Albany. Attributes. Mission-critical process Volume – number of users Utilization – frequency of use Complexity – range and depth of functionality Lifecycle = 10-15 years. Enterprise Applications The Big 4.
E N D
A Context for Enterprise Applications Christine E. Haile CIO University at Albany
Attributes • Mission-critical process • Volume – number of users • Utilization – frequency of use • Complexity – range and depth of functionality • Lifecycle = 10-15 years
Enterprise ApplicationsThe Big 4 • Library systems • Student information • Financial and HR • Course-management • ….. • Research proposals, facility-management, donor/advancement, et al.
The Good Old Days • Convert/carry-forward the data from old to new • Ensure transactions (=functionality) get done • Get it running in production • And maybe, a few customizations • Web-enable it
Today – all that, plus • 24x7, redundancy, DR/BC • Security and privacy of data • Embed it in the portal • Data access policies • Integration across multiple apps • Across enterprise apps • With dept’l apps
Buy, build or borrow? • Campus fit and culture • Budget culture for staff and contracts • 80% of costs are post-implementation • Commercial products • Vendors, products, industries • Community-, open-source development • An emerging possibility
Today’s case • 3-yr, horizon • Be strategic • Range of issues to consider • From policy, to tactical…. • Present a case for investment