Proposed Future for the ECB, CAM, & QVR Electronic Council Book (ECB) Council Administration Module (CAM) Query/View/Report (QVR) eRA Project Team July 23, 2002

Characteristics Common to ECB, CAM, and QVR Written in Cold Fusion Web interface Minimal effort to transition to J2EE Use IMPAC II IDs and passwords 2225 unique users in 2002 “Top 10” usage: NCI, NIAID, NIDDK, NINDS, NICHD, NIMH, NIDA, NIGMS, NIA, NIEHS Developed in close collaboration with the ECB/QVR steering committee Committee consensus determined functions, priorities, and user interface Design/development model: Iterative rapid response

Brief Profile: ECB (Electronic Council Book) Developed as a Web-based application in 1996 Widely used today  Average sign-on/workday: 210 (varies widely with Council activity)  Average uses/workday: 400  Used by 21 different ICs  “Top 10” for 2002: NIGMS, NIEHS, NIDCD, NICHD, NEI, NCRR, NIAMS, NIDCR, NINR, NIDDK  Critical for council rounds  Used extensively by council members (up to 45 uses/day)  Used in council meetings Relatively mature and “feature stable,” but needs access to Grant Images

Brief Profile: CAM (Council Administration Module) Provides IC control over council functions provided by ECB  Used by selective IC individuals to administer council functions Developed primarily by NIEHS with some participation by ECB/QVR development team Early Council Concurrence feature is now being used by NIEHS – Others are interested

Brief Profile: QVR (Query/View/Report) Developed in 2001 A “spin-off” of the ECB to permit additional NIH staff capabilities without complicating the ECB user interface Usage is growing rapidly  Average uses/workday: 1,150  About 300% increase in usage since January 2002  Average sign-on/workday: 265  Used by 26 different ICs  “Top 10” for 2002: NINDS, NIGMS, NICHD, NIDDK, NIAMS, NIA, NCI, NIDA, NIEHS, NIAID

Specific Activities & Timeline ( Where we’ve been)

Proposed Directions (Based on Available Resources and eRA Management Objectives) Move ECB, CAM, and QVR into a maintenance and currency upgrade mode Work with eRA developers and architect to transition functions into J2EE-compliant applications Discontinue current ECB, CAM, and QVR when their functional replacements have been introduced and accepted by the user community

Proposed Direction: ECB Maintenance and currency upgrades until replaced (anticipated during FY2003)  eRA Helpdesk provides end-user support continue as now  CIT provides software support, maintenance, and currency upgrades [no major enhancements] continue as now  CIT provides hosting environment, hardware, system administration, and infrastructure (servers, 7x24 monitoring, etc.) continue as now

Proposed Direction: ECB (continued) Maintain functional currency only AAdd application images Work with eRA management structure to transition ECB functionality into reengineered eRA applications and technical architecture Bottom Line: Provide a stable ECB system and work with eRA analysts/developers/managers to transition its functions into the eRA structure. After a successful transition, eliminate the ECB.

Proposed Direction: QVR Maintenance and currency upgrades until replaced (anticipated in FY2003)  Work with eRA Helpdesk to transition end-user support change from now  CIT provides software support, maintenance, and currency upgrades [no major enhancements] continue as now  Cit provides hosting environment, hardware, system administration, and infrastructure (servers, 7x24 monitoring, etc.) continue as now

Proposed Direction: QVR (continued) Defer/Omit most requested functional enhancements (consider as candidates for IC-Specific Data application)  Provide the following minor enhancements: Application images Subproject data Work with eRA management structure to transition QVR functionality into reengineered eRA applications and technical architecture

Proposed Direction: QVR (continued) Bottom Line: Following two minor enhancements, provide a stable QVR system and work with eRA analysts/developers/managers to transition its functions into the eRA structure. After a successful transition, eliminate the QVR.

Proposed Direction: CAM There are two components of the CAM: 1. Administrative functions for the ECB/QVR  Same direction/timeline as the transition of the ECB/QVR 2. Early Council Concurrence  Direction: To be determined

Funding The ECB, QVR, and CAM are currently hosted, managed, maintained, and supported independently of other eRA applications. The cost of most “Kessler Model” components [ Project Management, Operations, Communications and Outreach, Architecture, Quality Assurance & Configuration Control, Technology Infrastructure (i.e., components of the Kessler Model)] are included in the funding requirements for the ECB, QVR, and CAM.

Funding (continued) Funding for FY2003:  Provide ECB, QVR, and CAM (as previously described) $250,000.  Work with eRA to transition ECB, QVR, and CAM administrative functions $100,000

Thank You