Post-Award Implementation Team Roles Responsibilities 2232018 Does not include clinical trials Process Inventory: Post-Award 2 After discussion, evaluation and ranking with the DAs and General Administration Implementation Team,
"Post-Award Implementation Team* Roles &" is the property of its rightful owner. Permission is granted to
download and print the materials on this website for personal, non-commercial use only, and to display it
on your personal computer provided you do not modify the materials and that you retain all copyright
notices contained in the materials. By downloading content from our website, you accept the terms of this
agreement.
Presentation Transcript
01
Post-Award Implementation Team* Roles & Responsibilities
2/23/2018 *Does not include clinical trials<br>
02
Process Inventory: Post-Award 2 After discussion, evaluation and ranking with the DA’s and General Administration Implementation Team, Huron will be assisting in the redesign of the following processes with the functional redesign lead and team members. These processes and design teams have been approved by the Drive Team leads.<br>
03
Roles and Responsibilities – New Account Review 3<br>
04
Roles and Responsibilities – New Account Review 4<br>
05
Roles and Responsibilities – New Account Review 5 *Required documentation list to be developed.<br>
06
Roles and Responsibilities – New Account Review 6 Business day timeliness should be based on average trends over a period defined by the governance committee<br>
07
Roles and Responsibilities – New Account Set-up 7 GMS to confirm all materials received by OSPA “Ideal” Account Set-up Timeline
For a typical project – timelines vary by project type PADR Generated GMS schedules kickoff meeting with PI
(Covers checklist of Key items) GMS enters details in grant database GMS initiates any necessary equipment purchases
-no later than 30 days out Notice of Award Received 10 days 13 days 14 days 16 days 30 days GMS initiates Sub-award (if necessary) GMS initiates and helps facilitate all personnel actions<br>
08
Roles and Responsibilities – Account Maintenance 8<br>
09
Roles and Responsibilities – Account Maintenance 9<br>
10
Roles and Responsibilities – Account Maintenance 10<br>
11
Roles and Responsibilities – Account Maintenance 11<br>
12
Roles and Responsibilities – Account Maintenance 12<br>
13
Roles and Responsibilities – Account Maintenance 13 DRAFT FOR DISCUSSION PURPOSES ONLY<br>
14
Roles and Responsibilities – Account Maintenance 14<br>
15
Roles and Responsibilities – Account Close Out 15<br>
16
Roles and Responsibilities – Account Close Out 16 DRAFT FOR DISCUSSION PURPOSES ONLY<br>
17
Roles and Responsibilities – Account Close Out 17<br>
18
Roles and Responsibilities – Account Close Out 18<br>
19
Roles and Responsibilities – Account Close Out 19 GMS coordinates close out meeting with PI and DA with enough time to review balances, projections, no cost extensions, and future plans
PI Requests extensions RFS reviews and submits final financial report and closes project Account Close Out Timeline
For a typical NIH project – timelines vary by project type GMS checks payroll end dates, sub award status, and notifies lab/PI to request final purchases GMS ensures spending has stopped and liquidates any possible PO’s GMS makes any necessary budget/allocation corrections, gathers any final invoices
GMS reminds PI of final report submission end dates GMS ensures all changes are made before RFS locks the account PI submits Final Research Progress Performance Report and final technical reports 90 days 30 days 7 days Project End Date 30 days 60 days 90 days 120 days<br>
20
Service Level Commitment Overview The standards for performance will be grounded in Service Level Commitments (SLC). These represent an agreed upon service expectation, for those receiving service and those providing service. 20 The purpose of the SLC is to:
Clarify roles and responsibilities
Define the services and support that will be provided, as well as the performance standards that can be expected
Provide an overview of mutual requirements and expectations for processes
Define how performance will be measured to mitigate future operational risk (e.g. capacity overload)
Outline the escalation process to provide appropriate and timely channels to resolve service disputes<br>
