1

UCD Kuali Rice Road Map

David WalkerCurtis Bray

Hampton SublettInformation & Educational Technology

University of California, Davis

2

Overview

Background on Kuali Rice UC System-wide Activity Elements of the road map Current State Implementation Phases Discussion

3

Background on Kuali Rice

Rice components are the “glue” that tie the pieces of an enterprise application together

• KNS – Kuali Nervous System

• KEW – Kuali Enterprise Workflow

• KEN – Kuali Enterprise Notification

• KSB – Kuali Service Bus

• KIM – Kuali Identity Management

4

Background on Kuali Rice con’t

5

UC System-wide Activity

• IT Architecture Group (ITAG)– UC campus IT architect group under

the auspices of the IT Leadership Council (ITLC)

• Currently assessing Rice– Advice to individual campuses

– Applicability for multi-campus applications

– Initial work complete by end of February, 2009

6

Elements of the Road Map

Requirements addressed / services offered

UCD standards implemented

UCD standards utilized

Production and development platforms provided,

Support provided (consulting, documentation, toolkits, etc.)

Anticipated impacts

Expected lifetime

Financial support model

Community input

(As yet) unresolved issues

7

Current State

• IET/OOA partnership to deliver Kuali-based applications. Rice is part of this.

• Development Platform– Code development on personal systems

– A development integration server is available

• Two campus user groups– Project management

– Technology

8

First Production Release (Q3, 2009)

• Targets MyInfoVault deployment

• KEW, KSB, KNS, KIM offered as UCD services

– Java and at least some web services interfaces

• Assuming establishment of a campus standard, enterprise applications that use workflow and/or service bus will move to implement interfaces to KEW and KSB

9

First Production Release (cont.)

• KIM will utilize Mothra's IdM infrastructure

• IET to provide integration, Q/A, staging, and production platforms for Rice

– Application platforms not included

• General support for developers provided by IET and UCD user groups

– Electronic mail

– Wiki

– Kuali-provided documentation

10

First Production Release (cont.)

• One year notice of future changes that impact backward compatibility

• IET will provide financial support for Rice services

• Community input from the Rice working groups, as well as TIF, DTC, etc.

11

Later Releases

• Second Production Release (Q1, 2010)– Targets Kuali Coeus (KC), eDocLite, and

applications from colleges and departments

• Third Production Release (Q3, 2010)– Targets Kuali Financial System (KFS)

12

Discussion