ERA OneView Gateway to eRA. 2 Agenda Business Case Business Case Functional Case Functional Case...

19
eRA OneView eRA OneView Gateway to eRA Gateway to eRA

Transcript of ERA OneView Gateway to eRA. 2 Agenda Business Case Business Case Functional Case Functional Case...

eRA OneVieweRA OneView

Gateway to eRAGateway to eRA

2

AgendaAgenda

Business CaseBusiness Case Functional CaseFunctional Case PrototypePrototype Technical CaseTechnical Case TimelineTimeline

3

Business Case: Simplifying The Business Case: Simplifying The Grant ProcessGrant Process Workflow begins with eReceiptWorkflow begins with eReceipt Downstream Processing – electronic instead of Downstream Processing – electronic instead of

paperpaper eRA View should be consistenteRA View should be consistent

LoginLogin NotificationNotification Managing requestsManaging requests

Support Different ProcessesSupport Different Processes OPDIVSOPDIVS ICsICs Workload ManagementWorkload Management

eRequests – One Infrastructure for processing eRequests – One Infrastructure for processing Whether Application, Correction, Change of PI, Whether Application, Correction, Change of PI, Regardless of user, PI to SO to SRA to PO to GS to Regardless of user, PI to SO to SRA to PO to GS to

PI/SOPI/SO

4

Business Case: OneView Business Case: OneView SolutionSolution

OneView is an integrated approach to OneView is an integrated approach to initiate and process all eRA transactions initiate and process all eRA transactions electronicallyelectronically

eRA Single Login: Same view for all users eRA Single Login: Same view for all users across all eRA applicationsacross all eRA applications

Workflow: Single interface to initiate and Workflow: Single interface to initiate and process a request with HHS and Grantee process a request with HHS and Grantee Community Community

eNotification: Single method for notification eNotification: Single method for notification of actions/events throughout eRA of actions/events throughout eRA

5

Dependencies on OneViewDependencies on OneView

eSubmissions for electronic CorrectionseSubmissions for electronic Corrections eCGAP RR (currently has their own) eCGAP RR (currently has their own) OPDIVsOPDIVs CommonsCommons Grants ManagementGrants Management Training ActivitiesTraining Activities

Note:Note: Without a Centralized Workflow Without a Centralized Workflow Solution each business area will need to Solution each business area will need to build a customized solution.build a customized solution.

6

Business Case: HistoryBusiness Case: History

eRA Portal Prototype 2001eRA Portal Prototype 2001 eRA Project Team Retreat 2003 – Hot topics: eRA Project Team Retreat 2003 – Hot topics:

(Workflow, SSO, eNotification)(Workflow, SSO, eNotification) Single Sign On Initiative Priority 2004Single Sign On Initiative Priority 2004 OMB memorandum “e-Authentication Guidance OMB memorandum “e-Authentication Guidance

for federal agencies” (M04-04 dated December for federal agencies” (M04-04 dated December 16, 2003). 16, 2003).

Workflow Tool Evaluation & Elaboration 2004Workflow Tool Evaluation & Elaboration 2004 GM/OneView task order awarded April, 2005GM/OneView task order awarded April, 2005 ACR/ARA (eRequest) task order awarded Sept., ACR/ARA (eRequest) task order awarded Sept.,

20052005

7

Business Case: Advocate Business Case: Advocate SupportSupport Project Team approved proposed solution on Project Team approved proposed solution on

Feb. 9Feb. 9thth 2005. 2005. eRA teams are working closely with User eRA teams are working closely with User

Groups (OPDivs, R&R, SRAs, POs, GM, Groups (OPDivs, R&R, SRAs, POs, GM, Grantees) who have invested time and energy Grantees) who have invested time and energy in defining requirements for the following:in defining requirements for the following: ACR & ARAsACR & ARAs Commons Electronic RequestsCommons Electronic Requests GM & PGM internal approval processingGM & PGM internal approval processing

User Groups are engaged in identifying User Groups are engaged in identifying upstream & downstream processing upstream & downstream processing requirements to support electronic grant requirements to support electronic grant applications.applications.

8

Business Case: Current StatusBusiness Case: Current Status

OneView in Test now (SSO, Workflow OneView in Test now (SSO, Workflow infrastructure, eNotifications)infrastructure, eNotifications)

User Admin in Test now to support User Admin in Test now to support SSO SSO

Jan. ’06 OneView & User Admin Jan. ’06 OneView & User Admin Release to Production Release to Production

Jan. ’06 ACR User Pilot in StageJan. ’06 ACR User Pilot in Stage Feb. ‘06 GM, Closeout & Checklist Feb. ‘06 GM, Closeout & Checklist

integration with OneView.integration with OneView.

9

Business Case: Future NeedsBusiness Case: Future Needs

’’06 - Integrating all J2EE Applications with 06 - Integrating all J2EE Applications with OneViewOneView

’’06 - Defining other types of eRequests06 - Defining other types of eRequests ’’06 – ‘07 – Developing other eRequests06 – ‘07 – Developing other eRequests ’’06 - Supporting Administration Tool Upgrade 06 - Supporting Administration Tool Upgrade

(User Admin Module) on the critical path(User Admin Module) on the critical path ’’06 - Internal Routing and Approvals (GM & 06 - Internal Routing and Approvals (GM &

PGM)PGM) ’’06 – VOL (Org Hierarchy) 06 – VOL (Org Hierarchy) ’’07? - Integrating with NIH SSO07? - Integrating with NIH SSO

10

Functionality: SolutionsFunctionality: Solutions

Single Point of Entry to all eRA ApplicationsSingle Point of Entry to all eRA Applications One step closer to integrate with NIH SSOOne step closer to integrate with NIH SSO Integrated Home Page and Menu structureIntegrated Home Page and Menu structure Uniform Look and FeelUniform Look and Feel Immediate Access to assigned Action items Immediate Access to assigned Action items

and Notifications and Notifications Uniformed and Centralized way to submit Uniformed and Centralized way to submit

and process electronic requestsand process electronic requests

11

Functionality: Solutions Functionality: Solutions (Cont.)(Cont.) Increased communications and content Increased communications and content

management of it – eNotificationmanagement of it – eNotification Support of existing and upcoming electronic Support of existing and upcoming electronic

processesprocesses Retirement of paper-based processesRetirement of paper-based processes Better Workload management Better Workload management Increased data mining abilities for various Increased data mining abilities for various

processes and identification of bottlenecksprocesses and identification of bottlenecks OPDIVs supportOPDIVs support Centralized Rules for Validation and ProcessingCentralized Rules for Validation and Processing

12

Functionality: DemonstrationFunctionality: Demonstration

13

eRA SSOeRA SSO Single point of entry into eRA applicationsSingle point of entry into eRA applications First step to eventually integrate with NIH SSOFirst step to eventually integrate with NIH SSO Facilitates easier and manageable deployments Facilitates easier and manageable deployments

(e.g. easily separate IAR and Commons)(e.g. easily separate IAR and Commons) Centralized Menu integrates applications based Centralized Menu integrates applications based

on the user permissionson the user permissions Authentication is outside the application code – Authentication is outside the application code –

industry best practicesindustry best practices Removes overhead-intensive authentication Removes overhead-intensive authentication

process – will help reduce the database and process – will help reduce the database and LDAP loadLDAP load

Provides a more flexible approach for Provides a more flexible approach for implementing authorizationimplementing authorization

User can continue to use same userid/password User can continue to use same userid/password for both C/S and SSO applicationsfor both C/S and SSO applications

14

eRA WorkfloweRA Workflow Removes the inconsistent workflows out of the Removes the inconsistent workflows out of the

application codeapplication code Makes the actual applications light weightMakes the actual applications light weight Reduces new design and development cost - in time and Reduces new design and development cost - in time and

resourceresource Performance & Ease of UsePerformance & Ease of Use

Focuses the user work on the event based processes rather than Focuses the user work on the event based processes rather than expensive (database) searchesexpensive (database) searches

ManageabilityManageability Changes to the workflow does not require significant application Changes to the workflow does not require significant application

changes (reducing the maintenance)changes (reducing the maintenance) Configurable workflow provides flexibility to adopt changes in Configurable workflow provides flexibility to adopt changes in

business processesbusiness processes Centralized management of process definitions and its Centralized management of process definitions and its

implementationimplementation Seamless integration in and out of eRA applications enabled by Seamless integration in and out of eRA applications enabled by

SSOSSO Scalable and abstracted solutionScalable and abstracted solution

Designed to migrate to other and emerging technologiesDesigned to migrate to other and emerging technologies Vertically and Horizontally scalable middle-tierVertically and Horizontally scalable middle-tier

Standard based business rules implementationStandard based business rules implementation Easier changes in the business rules as the NIH policies changeEasier changes in the business rules as the NIH policies change

15

OneView requirements don’t fit OneView requirements don’t fit

current technical current technical implementationimplementation

CommonsLog In

LDAP Authentication

IPF

FrameWork...

applicationlevel menu

GMLog In

DB Authentication

FrameWork...

applicationlevel menu

era Services

Grant FolderGrantSnapshotReport

FrameWork

IAR

FSR

Other...

eNotification

Packaged Together

Use URL call

URL CustomAuthentication

16

Planned implementation meets Planned implementation meets

OneView requirementsOneView requirements

Commons

Log In SSOCentralized

Authentication

FrameWork…

Centralized MenuWorkflow

Business RulesIntelligence

An Application(GM)

OneView

FrameWork…

Centralized MenuWorkflow

Business RulesIntelligence

FrameWork…

Centralized MenuWorkflow

Business RulesIntelligence

Project Schedule - 2005 Timeline

1/1/2005 12/31/2005

12/0509/0507/05 11/05

ACR Pilot to Test

02/05

Requirements Gathering: SSO Workflow ACR/ARA

04/05

OneView to Test

OneView Task Order

Prototype: SSO Workflow

ACR Task Order

OneView Dev Starts

User Admin to Test Support SSO

10/05

ACR Dev Starts

OneView Production

User Admin Production Support SSO

Project Schedule - 2006 Timeline

1/1/2006 1/1/2007

01/06

Phase 1: Integration w/ OneView GM Closeout IC Admin Checklist PGM

05/0604/06

Phase 3: Integration w/ OneVIew IC Admin Crisp Plus ICSTORe POP Tracking

07/06 01/07

NIH SSO

Other eRequestsStart Development

ACR User Pilot

Phase 2:Integration w/ OneVIew Peer Review Receipt & Referral Committee Management

ACR Task 3:Iteration 1 to Test Workflow Track Request User Admin ACR Notifications

ACR Task 3: Iteration 2 to Test ARAs Other Types of ACRs

06/06

ACR Deployed to Prod

08/06

ACR Enhancements Mass Requests Reporting

GM/PGM Internal routing Approval process VOL

19

The Bottom LineThe Bottom Line

Are we going paperless?Are we going paperless? Multiple task orders are dependent Multiple task orders are dependent

on the OneView workflow on the OneView workflow functionalityfunctionality

Current architectures does not Current architectures does not support integration with NIH Single support integration with NIH Single SignonSignon

"This is the vision for eRA that I've "This is the vision for eRA that I've been looking for."been looking for."