Skip to end of metadata
Go to start of metadata
This is the home of the Kuali Ready Project space.

Project Governance

Project Charter

Kuali Ready Project Charter

Project Board

Chair: Shell Waggener, UC Berkeley
Project Board Roster:







Shel Waggener

UC Berkeley

Associate Vice Chancellor and CIO



Ken Wozniak


Asst. V.P., Administrative Information Services



Mark Bruhn

Indiana University

Associate Vice President, Public Safety and Institutional Assurance



Bob Cook

University of Toronto

Chief Information Office



Matt Coombs

San Joaquin Delta College

Director of Systems Development



Mike Corn

University of Illinois

Chief Privacy and Security Officer




California State University



Grace Crickette

University of California

Chief Risk Officer




University of British Columbia



David Kahle


VP for Information Technology and Chief Information Officer



Ron Rash

Pennsylvania State University

Senior Director


Functional Council

Chair: Paul Dimond, UC Berkeley
Functional Council Roster:

Roster - KR Functional Council.docx

Project Manager

Gianni Carlo Contardo, UC Berkeley

Subscriber Information

Subscription Types & Rates

  • Non-Kuali Foundation Member: $11,000/yr
  • Kuali Foundation Member (25% off): $8,000/yr
  • Sponsored Non-Kuali Foundation Member (50% off): $5,500/yr
  • Sponsored Kuali Foundation Member (62.5% off): $4,000/yr

Eligibility Guidelines For Sponsoring and Sponsored Organizations

  • "Sponsored Member" subscriptions are intended to promote continuity planning across entire systems of higher education and utilize economies of scale.
  • Generally speaking, a "Sponsoring Organization" will be the top (or higher level) management entity in the governance structure of a higher education system.  This categorization is primarily intended for university systems, not for individual universities, colleges, or campuses, or other types of institutions or professional associations.
  • Entities directly affiliated with a "Sponsoring Organization", e.g. universities, colleges, laboratories, etc., are eligible to register as a "Sponsored Member".
  • When subscribing as a Sponsored Member, the subscribing entity will use a single instance of the Kuali Ready service.
  • Kuali Ready is designed for use as a single-entity service, and a single “instance” of the service will be furnished to a single institutional entity upon payment of a single subscription fee.  In this context, "instance" is a term used to reference the software service environment used by a common set of end users.  We recognize that the organizational structure of institutions of higher education varies widely; hence we will furnish a single instance of Kuali Ready, in return for a single subscription fee, for use at multiple campuses within a university provided the following holds true:  that the Sponsored Member is an accredited university (or other type of institution of higher eduction) and the Sponsoring Organization is an accredited university system (or other system-wide governing body).  Both entities (the Sponsored Member and the Sponsoring Organization) must be accredited by a recognized accrediting agency.  In the United States, accredited agencies are those that appear on the list published by the U.S. Secretary of Education.
  • All other cases would be handled on a case-by-case basis.   In such cases, the scope of authority and executive decision making responsibility resides with the Kuali Ready Project Board.

Subscriber Lists

Hosting Institutions

Kuali Ready - U.S. Alternate (Failover) Site Estimates



General Availability (GA) Checklist

Kuali Ready Release Process

Kuali Ready Software Product Enhancement Release Schedule

Kuali Ready does not use a time-based release cycle (i.e., a regular release cycle based on a set time period). Rather, Kuali Ready implements a feature-based release cycle. This allows us to focus on planning a functionality\feature bundle that adds value to the product and delivers excellent overall quality. Although the exact time and schedule between releases will vary using this approach, we anticipate that the time interval between releases will be from 6-9 months.

High Level Overview of the Kuali Ready Product Enhancement Release Process

  • Product enhancement requests may be submitted by any Kuali Ready subscriber.
  • All product enhancement requests are reviewed and prioritized by the Kuali Ready Functional Council, which is the entity responsible for planning and defining the product vision. A candidate release proposal is prepared by the Functional Council.
  • A technical assessment will then be performed to determine the complexity, cost, resources, and time required to develop, test, and deploy the proposed enhancements.
  • Once a concrete proposal is in place, the recommended bundle of product enhancements will be reviewed by the Kuali Ready Project Board, which is the entity with the authority to allocate the funds in the Development Bank to future enhancements of the Kuali Ready service.
  • A release date will be announced to the Kuali Ready community after the product enhancement bundle has been reviewed and approved by the Kuali Ready Project Board.

Kuali Ready Maintenance Releases

  • Maintenance releases are intended to resolve reported noncritical bugs (i.e. bug fixes) that have been identified within a General Availability (GA) release. They are not intended to introduce new features and functionality, nor is there expected to a loss of existing features and functions.
  • New maintenance releases will contain all previous bug fixes.
  • Production deployment of maintenance releases will be done during non-business hours
  • Functional owners at subscribing institutions will be notified by the service support team one week in advance of scheduled maintenance.

Kuali Ready Critical Defect Fixes

  • “Showstopper” or “blocker” bugs are critical problems that make the service unusable to our subscribers and for which there is no workaround.
  • Such issues take priority over existing release planning efforts. These fixes are considered highest priority and will be addressed immediately by the Kuali Ready development team.
  • Critical patches are applied as needed and may affect service availability. Notification to functional owners at subscribing institutions and coordinating the application of these patches will be done by the Kuali Ready service support team. Subscribing institutions will be notified as soon as realistically possible.

Product Collateral


An online copy of the Kuali Ready Release Manual v2.00 is available online at:

Kuali Ready Release Manual

Copy of Kuali Ready Release Manual in MS Word format:

Kuali Ready Release Manual v200.doc

Copy of Kuali Ready Getting Started Manual in MS Word format:

Getting Started with Kuali Ready.doc


URMIA Insights - October 2010

UC Ready and the Development of a Tool to Assist Administrative Efficiency When Faced With Disaster



EDUCAUSE - October 2010

Continuity Planning: The Berkeley Tool Becomes "Kuali Ready"

Educause-Oct 15-2010.pptx

Introduction to Kuali Ready


Business Processes

Kuali Ready Onboarding Process


Kuali Ready Customer Support Process


Updated Version - July 2011


Project Board Meeting Information

Meeting Minutes

July 28, 2010


September 24, 2010


November 11, 2010 - Kuali Days


Presentation from Project Board meeting at Kuali Days:


January 7, 2011


February 25, 2011


March 7, 2011


April 29, 2011 - Kuali Community Workshop


Functional Council Meeting Information

Kickoff Meeting Presentation - September 15-16, 2010

KR Functional Council Sept 15 2010.ppt


Kuali Ready Demo Site

  • No labels