Kuali Research Administration Cornell IT Forum June 11, 2008 Dan Dwyer - Director of Research Admin IT Bryan Hutchinson - KRA Development Manager Andy Slusar - KRA Project Manager

KRA At Cornell KRA Overview KRA at Cornell KRA Functionality and Release Schedule KRA Technical Architecture and Tools Implementing KRA Questions

Kuali Foundation

What is KRA? Cradle-to-grave research administration system, providing the functional equivalence MIT’s Coeus: –Preaward (proposals, budgets, Grants.gov) –Postaward (contracts, grants, negotiations, report tracking, subcontracting) –Compliance (IRB, IACUC, COI, etc)

Guiding Principles Identify “best of breed” solutions from among partners as base for each module, KRA is based on the COEUS system Develop Common Kuali User Interface Leverage Kuali Rice architecture and development standards (nervous system, enterprise notification, enterprise workflow and service bus) Functional Councils and the Subject Matter Experts Drive Functionality and Scope Kuali Technical Council (KTC) governs Technical Standards across all Kuali Projects Maximize commonality of business practices Make configurable as much as possible given time and resource constraints

Kuali Integration Team Members from all Kuali projects Identifies “touch-points” across products to resolve duplication and provide benefits to schools who use more than one Kuali product Examples: –KFS Object Codes / KRA proposal budgeting –KRA Award /KFS Account Create & Budget Load –Kuali Identity and Organization Management

Full Time Dedicated Development Teams Dedicated Functional Resources Built for 24X 7 reliability and built to be scalable for use by the largest institutions Intensive QA/Testing process Structured and well documented governance process Extensive functional and technical documentation Partner Institutions dedicated to the success of Kuali Commercial Affiliates available to provide expertise Kuali Community Source

KRA Partner Schools

KRA AT CORNELL

Cornell Local Kuali Organization

KRA FUNCTIONALITY AND RELEASE SCHEDULE

KRA Release 1.0 – July 2008 Proposal and Budget Development –Proposal/Budget creation –Institutional rates/hierarchies –Template proposals to use again –Proposal Routing/Approvals using Workflow Grants.gov S2S submission –Find Grants.gov opportunities right from KRA –Submit without PureEdge/Adobe for the majority of applications

KRA Release 2.0 – August 2009 Awards –Award details –Cost sharing –Indirect cost –Payment schedule –Approved equipment & foreign travel –Award closeout –Money and end dates

KRA Release 2.0 – August 2009 Awards –Award Budget –Contacts –Award Templates –Special Reviews –Investigator Credit Split –Notice of Award –Data feed & integration with financials

KRA Release 2.0 – August 2009 IRB –Submission of protocols (new, continued, amended) –Recording IRB deliberations –IRB notifications –IRB meeting agendas and minutes –Protocol and training queries –Special reviews & other committees –Human Subjects Training records –Committee creation and scheduling –Batch correspondence and correspondence generation

KRA Release 2.0 – August 2009 Conflict of Interest –Faculty, staff, and students disclosure –Tracking of disclosures, reviews and decisions –Separate financial disclosure information Confidential Non-confidential –Allow for uniqueness of state laws regarding COI different –Training Requirements

KRA Release 3.0 – September 2010 Negotiations –Record actions of Negotiations Phone/ conversations Attachments –Management reporting Track status of negotiations/# of items in negotiation –Link with proposal development (when it exists)

KRA Release 3.0 – September 2010 Report Tracking –Automatic generation of reporting deliverables and status Financial Technical Patent reporting –Submission status

KRA Release 3.0 – September 2010 Subcontracts –Subcontract detail –Funding sources –Amount information –Subcontract closeout and correspondence –Contacts –Subrecipient monitoring (A-133) –Invoice routing and approval

KRA Release 3.0 – September 2010 Animal Care and Use – First Release –Submission of protocols (new, continued, amended) –Recording IACUC deliberations –IACUC notifications –IACUC meeting agendas and minutes –Protocol and training queries –Special reviews & other committees –Committee creation and scheduling –Batch correspondence and correspondence generation

KRA Release 3.0 – September 2010 Animal Care and Use – Enhancements –Inspections –Animal Census –Procurement – Requisition –Receiving and cage card management –Regulatory/Non-regulatory Reporting – OLAW (Annual Report); USDA (Annual report); AAALAC-I (Annual Report) –Training and Educational Requirements –Post-approval monitoring

KRA Release 4.0 – October 2011 Biosafety –Submission of Memorandum of Understanding (MOU) on biological materials, including select agents –Submission of MOU amendments and renewals –Review of the MOU –Production of IBC minutes –Monitoring of approved MOU –Reporting of non-compliance –Facilities inspection

KRA Release 4.0 – October 2011 Export Control Chemical Safety/Chemical Inventory Functionality to be determined

KRA Look and Feel

KRA TECHNICAL ARCHITECTURE AND TOOLS

KRA Architecture

KRA Building Blocks Kuali Toolbox –Open Source Tools Struts - UI OJB/JPA - Persistence Spring - Services –Rice builds upon and extends functionality Struts - Mitigates common issues (POJO forms, Formatting,…) OJB - DAO w/ Object Hierarchy; No custom code for POJO persistence

About Kuali Rice Software Development Simplified –Unified development platform –Diverse functional requirements Service Oriented Architecture (SOA) Integration of Kuali Applications Integration of existing Enterprise Applications Versions and include multiple enhancements focusing on KRA requirements

Rice Components

KRA Development Process Shared collaboration tools Confluence wiki JIRA bug tracking KRA Developer mailing list PolyCom video-conferencing Breeze / Adobe Connect - online collaboration Skype - text / voice / video chat

KRA Development Process Development Toolbox –Eclipse –Junit / Httpunit –Jetty –Cvs –Maven Shared Tools –Bamboo –Fisheye

KRA Development Process Clear expectations for KRA Developers documented in Confluence –Code Reviews –Coding Standards –Documentation Standards –Tool usage –Unit Tests Regular meetings –Weekly 1-on-1 –Weekly Code Reviews –Bi-weekly team meetings –Periodic Face-to-Face meetings

IMPLEMENTING KRA

Implementing KRA Rice components necessary for KRA will be included out of the box –To run Rice services centrally (ex: KEW), the implementing institution will have to plan and do more implementation work Main Configuration Points –Workflow (KEW) Configuration –Person / Group (KIM) information –AuthN / AuthZ (KIM)

Implementing KRA Data Migration / Interfaces –KRA is SOA - implement your own implementations as necessary –Main Data Migration / Integration points will be documented Still to Come –Implementation Guide –KRA Packaging and Documentation for Release 1.0 –KRA Test Drive –Support Model

Technical Competencies for KRA Implementation Straight Implementation –Enterprise Java –Apache Web Server –Tomcat –DBA (Oracle or MYSQL) For customization –Struts –OJB/ORM –Spring –Kuali Rice –XML

For Further Information –General Foundation information –Articles open/community source –Information on the existing Kuali Projects –General KRA Information –Cornell specific KRA Information

Questions?