UC Davis IT Standards Repository

UC Davis IT Standards Repository (Work in Progress)

Standard

Summary

Applicability

Further Information

Work Flow

UC Davis establishes middleware standards in order to foster interoperability, sharing, and reuse of application software within UCD, as well as with UCD's business and academic partners around the world.  These standards also create a more uniform and integrated environment from an end-user's point of view, as well as enabling a common platform for policy compliance. This document establishes the Kuali Enterprise Workflow (KEW) component of Kuali Rice as a standard for applications that require work flow services.
  • Effective Date: DRAFT
  • Review Cycle: 12 months
  • Last Review:
  • Prerequisite Standards:  Network Protocols, Identity Management

Enterprise: Required
Administrative: Recommended
Other: Optional

/wiki/spaces/UCDK/overview

Service Bus

UC Davis establishes middleware standards in order to foster interoperability, sharing, and reuse of application software within UCD, as well as with UCD's business and academic partners around the world.  These standards also create a more uniform and integrated environment from an end-user's point of view, as well as enabling a common platform for policy compliance. This document establishes the Kuali Service Bus (KSB) component of Kuali Rice as a standard for applications that require a service bus.
  • Effective Date: DRAFT
  • Review Cycle: 12 months
  • Last Review:
  • Prerequisite Standards:  Network Protocols, Identity Management

Enterprise: Required
Administrative: Recommended
Other: Optional

/wiki/spaces/UCDK/overview

Network Protocols

In order for systems to interoperate, they must share a common set of network protocols.  This document establishes a standard for network level communication over UC Davis's network, which is required but not sufficient for interoperability. Other standards will further refine the selection of network protocols to achieve full interoperability for specific services.  Currently, IPv4 is required for compliance, but planning should start to support IPv6.

De facto

 

Telecommunications Infrastructure and Cabling

This document contains the Telecommunications Standards for use by the campus project managers, consultants and telecommunications design professionals who are involved in telecommunications projects on the UC Davis campus. This manual shall be used as a guide for projects providing telecommunications infrastructure and cabling, including inside and outside plant cable, wireless networks, in-building radio systems, broadband video, audio-visual and network systems. Work may include new and renovated buildings, as well as, the upgrading and/or the addition of cabling infrastructures and electronic equipment.

De facto

Communications Resources Web Site

Applicability

The Applicability column describes the manner in which this standard applies to systems of various scopes that are managed by UC Davis, either directly or by an agreement with some other entity.  The following terms are used for this description:

  • Enterprise - Systems that provide core services or manage institutional data that are critical to the UC Davis community.
  • Administrative - Systems that provide services or manage data that are used by significant segments of the UC Davis community, such as colleges or departments.
  • Other - All other systems that provide service to members of the UC Davis community.
  • De facto - A specification that has been in common use at UC Davis but has not been the subject of the formal standard setting process.
  • Required - Compliance with this standard is required.  Non-compliance may adversely affect other systems.
  • Recommended - Compliance with this standard is recommended. Non-compliance may adversely affect this system.
  • Optional - Compliance with this standard is optional.  Non-compliance has no significant, or even a positive, effect.