# Presentation: 787534

## “OneView”
for IMPACII Coordinators
February 17, 2005

**“****OneView”**
**for IMPACII Coordinators**
**February 17, 2005**

## Facts 

- Over 2,000 Grantee Institutions Registered in the Commons
**95% of all awarded applications (2002-2004)**
- 50,000 Grantees Registered
**66% of PIs receiving an award have a Commons Account (55% of ALL PIs) **
- 1040 JITs Submitted in 2004 (18%)
- 5360 eSNAPs Submitted (20%)

## Commons to IMPACII Logon Trend

## 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)**

**Notes:**
Combines all J2EE eRA applications into a single system
Reduces GM Redesign Risk 
Allows us to define Workflow/eRequests for all of eRA ( Not just 901s) 
Provides Program functionality with nominal effort
Leverages Investment in eNotification (without integration, eNotification is mostly ineffective) 
Allows delivery of GM functionality independent of Kumaran deployment
Allows support of authentication from outside systems (NLM, NCRR)  
Fixes problematic custom security services in Commons Internal J2EE Apps 
Fixes eSNAP, JIT, Closeout which are currently problematic because of lack of integration with internal staff...  
Consolidates Workflow into a single initiative, Adding significant functionality without significant development (Coding an eRequest for 901s, Pre Award Changes, Other Prior Approval, eCGAP Corrections is the same). 
Lessens scope/risk of GM redesign by implementing workflow items earlier in the development lifecycle  
Sets up foundation up for TA/xTrain integration.

## Demo of One View

- _[http://erawebdev.od.nih.gov/ui/](http://erawebdev.od.nih.gov/ui/)_
- Select OneView

## 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)

**Notes:**
A single login page enabling access to all era applications, depending upon privilege.  Initially, Grants Management, Program, Closeout, and Commons will share this common login and menu structure but other applications will be supported as they are converted from client/server to web based technologies.
A common location for notification events specific to an eRA user, such as a GMS, SRA, SO, or PI.  Many events will be recorded and displayed to an eRA user, within the single login page.  A partial list of notification events include:
Assignments of Institute, Scientific Review Group and Council.
Release of Scores, Summary Statement, NGA, and Award.
Notifications to approve, route, or process an electronic request such as an eSNAP, 901, Change of Institution, Verification of Manuscript Submission in PubMed, or Request for an Extension.   
An historical record of all notification events.  Building upon the existing grant application status, events such as the ones listed above will be recorded and associated with the grant application and become available to the public record.  An ancillary benefit of this will be accurate reporting on such things as average time interval of IC assignment and SRG assignment by IC.  
A standard infrastructure and User Interface for the initiation and processing of all requests electronically end to end.  Electronic submissions and approvals will be performed in the same manner and share the same code and use the same interface regardless of where the request originates and who finally approves the request.  Additionally, the list of individuals and their contact information will be available for all to see, significantly reducing the occurrence of reaching the wrong individual either within HHS or at the grantee institution.  Electronic requests delivered in 2005 will include:
The Extension of existing Commons requests to include PO and GS approvals for Just in Time, eSNAP, and Closeout requests.
Implementation of most Other Prior Approvals requests such as Change of Institution, Change of PI, Request for Additional No Cost Extension, Administrative Supplement, etc.    
Introduction of Internally Initiated 901 Requests such as Change of Institute. 
Implementation of eCorrections to support modifications post application submission through the Exchange.    
The completion of all electronic requests will be stored online and available to all in the grant folder.  

## Transactions Supported in One-View

- 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_

## One-View 2006 Goals

- Declaration that all requests be done online/electronically
- HHS OPDIVs fully integrated into Commons
- 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.

**Notes:**
The declaration that all requests in the Commons be performed electronically.  With over 95% of grantee institutions and more the 67% of PIs registered in the Commons at the end of 2004, HHS has the ability to declare that we no longer accept paper requests for requests available in the Commons. 
OpDiv Integration in the Commons is difficult because of the unique business requirements of each of these agencies (i.e. FSR transactions go to several accounting systems).  By implementing a standard method to route these types of requests, the implementation cost of HHS agencies in the Commons will be greatly reduces and can be accomplished in 2006.  
Introduction of Organizational Hierarchies to support more flexible approvals.  The electronic requests deployed in 2005 use roles already defined in eRA (i.e. PI, PO, GS, and SRA).  This will not support all requests, particularly 901 and internal Grants Management workflow required in future phases of those initiatives.  Instead, a new structure to define permissions will be available to meet these business requirements.  
The extension of requests to complete GM, TA and 901 initiatives as well as perform data element changes for electronic submissions.  By defining a standard method and technical infrastructure in 2005, these initiatives will be much easier and less costly to accomplish in 2006. 
The conversion efforts begun in 2004 will show great return in 2006.  As each application is converted the users of that application will be able to login into all of eRA instead of a particular module.  Although the specific module interface will be the same as the client server application, each converted system will have the benefit of notification events and an entry point into electronic request processing.  Therefore, as Receipt and Referral, Peer Review and Committee Management are converted, their users will see electronic requests for change of council, IC assigned, etc.  This functionality will greatly enhance their overall experience with eRA with limited investment until those applications can be fully reengineered.  

## Status

- Included in GM Redesign Task Order but this is not a GM Task
**Other Prior Approvals for 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)