sage release plan overview system to administer grants electronically
DESCRIPTION
SAGE Release Plan Overview System to Administer Grants Electronically. Monthly Research Administrators Meeting Jennifer Dobbelaere January 14, 2010. Agenda. SAGE Suite: Release Plan Overview SAGE Suite: Individual Projects SAGE Suite Release Plan Questions?. Background. - PowerPoint PPT PresentationTRANSCRIPT
ORIS
SAGE Release Plan OverviewSystem to Administer Grants Electronically
Monthly Research Administrators MeetingJennifer DobbelaereJanuary 14, 2010
ORISAgenda
• SAGE Suite: Release Plan Overview• SAGE Suite: Individual Projects• SAGE Suite Release Plan• Questions?
ORISBackground
• Developed SAGE Suite Release Plan in support of the Research Roadmap vision
“Create an outstanding climate for research by making it easier for campus to manage research administration and compliance, providing personalized service for faculty and staff involved”
• SAGE needs reshaping to help achieve the Research Roadmap vision and support a dynamic and fluid research administration process
ORISBackground (con’t)
• Reshaping SAGE to support a dynamic and fluid research administration process includes:– Integrating research administration and compliance
processes, providing routing and notifications, enabling compliance with sponsor and UW business rules
– Reducing duplicate and redundant data entry while managing information throughout the grant lifecycle
– Collecting all necessary research administration data to provide notifications and generate accurate, timely reports
ORISResearch Roadmap Vision:Personalized Service
Manage research life cycle
Proactive conciergeservice
Integrated processeswith parallel processing
Integrated information and guidelines
Automated notifications and routing of required tasks
Integrated dataPersonalized to individual
needs
• Reduce administrative burden• Save time looking for information• Reduce confusion• Increase time available for
research and mentoring students• Improve understanding of and
ability to meet compliance requirements
• Make it easier to pursue new opportunities
ORISSAGE Projects
• Adobe Forms B• SAGE Budget II & New Look• SAGE Budget III• SAGE Budget Quattro• Subcontract Module I• Electronic Sponsored Programs (eSP)
ORISAdobe Forms B
• Timing: Deployed in December 2009; communication at November MRAM and via Grants eNewsletter
• Enhancement to GrantRunner that support the new Grants.gov/NIH Adobe Forms B form changes
• Enhancement to provide submission status for Adobe submissions for Grants.gov/NIH applications
• Modify GrantRunner performance site location to enable accurate reporting of location to Grants.gov/NIH
ORISSAGE Budget II & New Look
• Enhancements to SAGE budget – Create sub-budgets (including the ability to split F&A rates),
subcontracts and fabrication budgets– Import existing budgets Refresh budget data
• Enhancements to usability for SAGE, SPAERC and SERA – Revised form layout with clear path to completion– In-context help and revised help text– Alignment with SAGE Budget usability– New ASTRA role to support appropriate access to eGC1s
• Timing: March 2010 deployment scheduled; after NIH deadlines
ORISSAGE Budget III
• Enhancements to SAGE Budget to integrate with GrantRunner– Allows creation of NIH R01, R03, or R21 with modular or detailed
budgets (excluding subcontracts) within the SAGE Budget and submitted via GrantRunner to Grants.gov
• Modify SAGE Budget to input full Grants.gov detailed budgets
• Timing: September 2010 deployment scheduled
ORISSAGE Budget Quattro
• Enhancements to SAGE budget that support mandatory use– Inclusion of proposed cost share– Various outputs to support sponsor requirement formats– Excel outputs that include formulas and calculations– Ability to set target or limit amounts
• Enable business process improvements by sharing information between SAGE budget and eGC1
• Enable easier re-use of information for renewals and resubmissions
• Timing: Iterations in 2011
ORISSubcontract Module I
• Enhancements to SPAERC and SERA, potentially SAGE– Entry and storage of additional subcontract data in the system– Interface between SAGE database and FIN database to automate
tracking and updating of subcontract process
• Enable business process improvements via process automation, creating data fields for OSP and eliminating manual data entry performed by GCA
• Timing: June/July 2010 deployment scheduled; confirming opportunities to reduce timeline
ORIS Electronic Sponsored Program (eSP)
• Create or rebuild web-based tool for OSP to gather data from electronic proposals and set up awards to faculty/staff– Proposal record that houses all necessary data required for grant
proposals to be approved, submitted and awarded– Proposal processing mechanism to gather data and create a project
record as the first step in the award process– Award management system to administer awards from setup to
closeout, integrating SAGE budget, allowing for budget revisions, integrating research compliance systems required for award compliance, integrating financial systems necessary to distribute award funding to sponsored research budgets
• Timing: Iterations in 2011
ORISSAGE Suite Release Plan
Qtr 2 2010
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Qtr 3 2010 Qtr 4 2010 Qtr 1 2011 Qtr 2 2011Qtr 1 2010
SAGE Suite Release PlanFiscal Year 2010-2011
eSP
Production Support
Go Live March 2010
SAGE Budget II / New Look / RefactorAnalysis & Design
Development
Test
Learning/Communication
Adobe Forms B
Test
Req/Analysis
Subcontract Module IAnalysis & Design
Data Conversion (duration and impact under review)
Learning/Comm
Test
DevelopmentGo Live
July 2010
Go Live by Dec 8th 2009
SAGE Budget III
Development
TestAnalysis & Design
Go Live Sept 2010
SAGE Budget QuattroPlanning & Requirements
Planning & Requirements
Go LiveTBD 2011
Go Live TBD 2011
Rotation 2 Rotation 3 Rotation 4 Rotation 5Rotation 1
Iterative releases
Iterative releases
Learning/Comm
Plan/Req
Development
Plan/Req Plan/Req Lng/Comm Learning/Comm
ORISQuestions?