Enterprise architecture

We make IT decisions and select solutions that provide the most benefit to the broadest range of UW–‍Madison and its constituents.

Importance

To maximize the use of limited campus resources we balance the desire for new information technology versus the value of potential investments. Good stewardship lessens opportunity costs, lessens support costs, and increases the ability to change.

In practice

Multiple factors will be considered when making IT decisions and selecting solutions, such as: total cost of ownership, opportunity costs, strategic alignment, and operational sustainability. Some areas may need to waive their specific preferences to benefit campus, though this principle must not prevent any area from performing tasks and activities.

We deliver IT solutions that can be readily adapted to our changing environment.

Importance

Our world is constantly changing. Our IT solutions and processes should be adaptable and resilient to appropriately respond to higher education and technology changes whether they arise from policy, constituent needs, or other types of changes.

In practice

How adaptable a solution needs to be and how easily a solution can accommodate changes will be a factor in IT solution delivery. This will be based on how IT solutions support business activities and how constituents interact and rely upon IT.

We deliver solutions that leverage existing campus-supported IT.

Importance

Using campus-supported IT infrastructure better assures IT systems and data are secure, reliable, accessible, scalable, and supported. Campus supported solutions provide better economies of scale, familiarity, and resource use.

In practice

Solutions will be evaluated for their ability to use existing campus-supported IT infrastructure and platforms such as Identity and Access Management (IAM), Learning Management System (LMS), Integration Infrastructure (Interop), Constituent Relationship Management (CRM), Enterprise Resource Planning (ERP), and Financial Systems (SFS). Acquisition of IT solutions that cannot use or require significant customization to use our IT infrastructure will be discouraged.

When selecting an IT solution, we will use campus supported solutions before we acquire something new, and we acquire solutions before we develop them.

Importance

Functionally duplicative solutions incur real, non-trivial costs to manage, operate, support, integrate, and secure, and can create inconsistent user experiences. Campus-supported solutions enable economies of scale, simplified management, increased security, and a more consistent user experience.

In practice

Existing campus-supported solutions should be evaluated before looking for new solutions. Campus areas should not develop solutions for their own use which are similar/duplicative of existing campus supported solutions. If we ever choose to build custom solutions, it will be in areas where we can bring unique value that is difficult to find in the marketplace. A high threshold exists before deciding to buy instead of reuse and to build instead of buy.

We will deliver IT solutions that conform to IT industry standards and best practices to promote interoperability for data, applications, usability, and technology.

Importance

The IT industry is becoming more standards based. Following IT standards and best practices is vital to enable system interoperability and collaborative work, promotes quality and reliability, and allows adaptable and efficiently supported solutions.

In practice

Solutions that use common IT industry standards and support best practices are strongly preferred over those that do not.

An Enterprise Architecture (EA) role is to understand and convey how the UW campus and various IT puzzle pieces fit together, along with providing options on how to improve information technology use. Collaborative planning with EA helps align your efforts with the Campus’s vision, direction, and strategic pillars. A short conversation will jointly determine what, if any, collaboration with EA is appropriate. Contact us at enterprise-arch@office365.wisc.edu as early as possible to get the most benefit for both your area and campus.

Contact EA as early as possible if any of the following may apply:

• Uncertain if there is an existing solution that could do the job.
• A new or meaningful change to a campus IT service or capability.
• Investigating a technology space or how a technology fits in at UW.
• Includes a change to UW’s IT landscape or a complex system design.
• UW has not previously done some material aspects of the effort (e.g., technology approach, project nature, scale, degree of risk).
• Creating a strategy or roadmap may help achieve a successful outcome.
• Might require a new or updated IT policy, technical standard, or best practice.
• Affects multiple departments, UW System, or multiple campuses.
• Impact on or interaction with an existing system, including accessing or transferring data.
• Includes a formal procurement process (e.g., RFI, RFP, RFB, simplified bid).