Common services occupy the middle ground of the university’s service portfolio. These services are broadly used across several colleges or departments but may or may not be adopted, funded, or governed at the university-wide level. Common services are typically shared by multiple units, supported through collaborative models, and offer flexibility to meet diverse functional needs.

In terms of mission alignment, Common services generally support a single university mission, such as academic, administrative, research, or health care, across many units. For example, a service may be widely used in support of academic operations but not essential to administrative or clinical functions. While some Common services may eventually transition into Core or evolve toward more specialized use, this classification reflects their current state and user base rather than their trajectory. Lifecycle movement is a valid concept within the broader CCU framework, but it is not a defining trait of the Common category.

Characteristics of a Common service

  • Shared usage: Common services are used by multiple colleges or administrative units but may not be adopted or funded at the campus level.
  • Adaptable by design: These services support a variety of functional needs and can be tailored to different use cases across departments.
  • Collaborative funding models: Licenses and costs are often shared across groups, with central support leveraged when economies of scale can be achieved.
  • Distributed support approach: While central IT may assist with onboarding or integration, operational support typically comes from local IT units or departmental staff.

Identifying Common services

  • Used by multiple departments, colleges, or administrative units but not universally adopted at the campus level.
  • Supports key departmental or collegiate functions and may be critical to specific operations, even if not centrally managed.
  • Typically funded through a cooperative model, where units pool resources to license and maintain the service.
  • Not always included in centrally packaged software offerings. Often acquired or implemented through distributed IT channels.
  • Usually involves a centrally negotiated license, though not always adopted campus wide.  
  • May be integrated with campus systems such as Single Sign On or institutional data sources, depending on scope and use. 

Examples of Common services

Common services may have multiple instances or feature variations across units due to business specific needs.

  • Calendar cloud platforms (e.g., Calendly, Microsoft Bookings, Acuity Scheduling). These platforms allow for shared scheduling and coordination across departments and non-university participants.
  • Statistical software packages (e.g., SAS, SPSS, R, GraphPad Prizm). These are used for data analysis and research across various academic departments.
  • Salesforce. This Customer Relationship Management (CRM) development platform is used for a variety of data-driven tasks such as communication campaigns, data-driven visualizations, workflows, and event delivery. Salesforce is an example of a service moving through Common toward Core.

Other widely used systems such as ICON, MAUI, Digital Signage, Gradescope, RDSS, and Dispatch represent more complex cases. While many of these align with characteristics of Common services, their classification may vary based on evolving usage patterns, governance structures, and funding models. These examples highlight the need for ongoing review and refinement of CCU classifications.