Professional Documents
Culture Documents
Our institution invests IT Institutional leadership Our institution has a clear The institution has a Principled master data
resources in scalable has a shared and documented roadmap formal data strategy designations and
technologies, with a focus understanding of our to transform outdated which articulates the steps associated metadata are
on long-term flexibility collective “technical debt” legacy infrastructure to to be taken to better agreed upon among
over near-term demands. and the costs associated meet modern IT needs. leverage data, and names campus stakeholders and
with IT’s integration those responsible for then effectively
maintenance efforts. executing those steps. communicated to users.
During the procurement We have clear IT protocols IT maintains a robust and We create and regularly We actively monitor for
process, our institution regarding integration total up-to-date inventory of all update clear, institution- anomalous data in master
ensures that all vendors’ cost analysis which are integration assets wide definitions for data systems and take
technical standards (e.g., well understood and including tools, platforms, commonly used terms steps to identify and
platforms, protocols, etc.) uniformly applied to and interfaces. (e.g., "student”) in a remediate the underlying
are leveraged and can be incoming projects. location easily accessible causes.
supported on campus. to all stakeholders.
Our IT department Integration work is a Integration staff use a IT leverages enterprise Integration developers are
organizes integration staff discrete and differentiated common toolset with architecture expertise at encouraged, and
as an integration service, service provided to established patterns to the business, application, supported, to deepen their
rather than assigning consumer groups internal develop new interfaces for and technical levels to knowledge of available
them to system-specific to IT, across campus, and campus systems. guide technology solution tools and propose
teams. external to the decisions. adoption of new
organization. technologies.
The developers who work Integration consumers IT professionals and IT staff (and distributed
Our integration tools
on integrations focus and developers have clear campus leadership have a partners) work closely
promote workflow
exclusively on integration lines of communication common goal of with campus constituents
automation, minimal
efforts and are not regarding service supporting cross-campus to increase the technical
coding, and reduction of
responsible for other kinds agreements and capabilities with shared sophistication of
rework.
of development. expectations. assets and applications. integration practices
across the institution.
Page 1 Page 2
Asset Standardization
Transformation Coming into Focus
You’ve targeted an end state, and institutional leaders are invested in progress.
Management and Automation
51-70 Clear ownership for integration and enterprise initiatives means that policies and
procedures are documented and shared with campus, and new investments are
geared towards developing the technical architecture and digital capabilities.