“Organizational Hierarchies” and ““OneView” for ePUG February 9, 2005

1. “Organizational Hierarchies” and ““OneView” for ePUG February 9, 2005

2. Organizational Hierarchies Organizational Hierarchies in eRA is a method to define system privileges based upon a hierarchical structure. It provides users the ability to: • Setup a Hierarchy Structure • Assign Permissions within that Structure • Assign Grants (or People) to Departments (Enhances Assignment Module) • However, it is up to the specific business module to utilize the capabilities of Organizational Hierarchies

3. Demo on Organizational Hierarchies http://erawebdev.od.nih.gov/ui/VirtualOrganizationLayers/index.htm

4. Status on Org Hierarchies • Developed in Commons for Grantees in 2005 • Included in GM Redesign and eCGAP and eRequest Task Orders in late 2005/2006 • More Reading – Request For Comments for grantees at: http://era.nih.gov/UI/Commons/Organization_Hierarchies_in_Commons_Request_for_Comments.pdf

5. One-View

6. One-View • One View is an integrated approach to initiate and process all eRA transactions electronically. It consists of three primary parts: • Single Login for all eRA applications – Including Commons • Single method for notification of actions/events (i.e. eNotification) • Single interface to initiate and process a request, regardless of context (within HHS and Grantee Community)

7. Why One-View • PI/SO/Program Official/Grants Specialist/SRA Require Same View • HHS OpDivs into Commons Difficult until Full Work-Flow deployed • Workflow does not end at SO Submission to NIH (it begins there) • Estimated 10% Error Rate on externally initiated transactions such as eSnap, JIT, and soon Closeout (Fixes require Paper Process) • GM/Program/CGAP/TA/e901/Commons require: • One Login to eRA • Approval Chains spanning multiple modules

8. Demo of One View http://erawebdev.od.nih.gov/ui/ Select OneView

9. One-View 2005 Objectives • Single login for eRA (External and Internal) • Single login includes eNotification events • Email • UI Display of Event (Acknowledge/Process) • Web Service Through Exchange (Really 2006) • Historical record of notification events (probably available in Grant Folder) • Standard method for requests and transactions (Internal/External)

10. Administrative Supplement Carryover (of Un- obligated Balances) Change of Dual IC(s) Change of Institution Change of PI Change of Primary IC (901) Change in Scope Change in Status of Key Personnel Closeout Final Invention Statement Closeout Final Progress Report Closeout FSR eCorrection, Full Replacement eCorrection, Addendum eSNAP eSubmission Approval Fellowship Activation JIT Project Extension Retention of Research Grant Funds Other Prior Approvals will have Policy and Instructions Transactions Supported in 2005

11. One-View 2006 Goals (Affecting External Community) • Declaration that all requests be done online/electronically • HHS OPDIVs fully integrated into Commons • Redo Delegation!!! • Expand Org Hierarchies/Flexible Permissions in GM/PGM/901 and then eRA. • Include One View for xTrain through to HHS (i.e. TA) • Increase the number of electronic requests supporting all of eRA and fully automate existing ones.

12. Status • RFC being drafted for March 1 to address Workflow • Included in GM Redesign Task Order but this is not a GM Task • Other Prior Approvals bridge Commons/GM/PGM users • eCorrections bridge RR/Commons users • 901s bridge RR/Commons/Peer Review/CM users • Workflow Requirements finalized in March 2005 (Policy, ePUG, CWG, GMAC) • Require ePUG representatives to validate requirements to ensure we get it right