Back to eRA home page 2002 Initiatives
Listed alphabetically by business area


Business Area Project Goal
Budget Management   eRA/NBS Financials
  • Analyze, design and develop the integration with the NBS system. The progress of this effort will depend upon the progress made by the NBS working group. It is necessary that eRA work with this group as early as possible in the NBS requirements phase to ensure the successful integration of both systems.
Budget Management   Grants Payment FBS Module
  • Analyze, design and develop a Grants Payment module. This will include standard reports and possibly some other workflow processes that aid in the ability for the IC budget offices to management the grant payment/commitment/ obligation process.
Budget Management Grants Payment FBS Module Cross-cutting Initiatives
  • FSR System Integration (Cross-cutting Initiative). Provide programming support for the integration of the FSR system into the Grants management module. The initial development effort is part of the J2EE development effort identified under the NIH Commons.
  • No-cost Extension Module Integration (Cross-cutting Initiative Commons/ GM and maybe Program). This would allow grantee institutions to notify us of automatic no-cost extensions via the Commons. At the IMPAC II side, build notification functionality, as well as the ability to “accept” the data (e.g., new project/budget end date) from the grantee.
Committee Management Additional Redesign Features
  • Administration module
  • Conference planning for Advisory Committees held at NIH
  • Chartering process
  • Build business rules to automatically archive data from OLTP to IRDB
Committee Management CM Portal
  • Design the CM portal.
Data Integrity Contract Data (R&D)
  • Analysis and design the migration of datasets on contract data from the DCIS and Datawarehouse.
Data Integrity Data Quality
  • Improve quality (accuracy, matching/association of names between files) of personal data, degrees, profiles, addresses in IRDB and OLTP.
  • Prepare for electronic receipt of people data.
  • Analyze and suggest changes in policy and business processes throughout the user community to improve data quality.
  • Document areas, procedures, modules involving personal data may require changes to architecture involving personal data.
  • Analyze and implement changes to IMPAC II database and software to effect solutions to identified data integrity problems.
Data Integrity Information Management Module
  • Analyze, design and develop a module that replaces the functionality performed by the legacy IPF, to include necessary business process re-engineering (BPR).
  • Analyze, design and develop a module that replaces the functionality performed by the legacy process to allow the OER Quality Assurance the capability of updating data records in IMPAC II, this would include necessary business process re-engineering (BPR).
Data Integrity Population Tracking
  • Complete the development of the client/server version. This project was under-funded in FY01 and requires additional funds to complete.
Data Integrity Population Tracking v.2
  • Design a J2EE, Web-based Population Tracking module.
Data Integrity Stem Cell Tracking
  • Analyze, design and develop the infrastructure needed to support the collection of stem cell research data as requested by DHHS.
Electronic Council Book ECB/CAM Enhancements
  • Develop support for expedited early council concurrence.
  • Implement ongoing enhancements (identified by the Steering Committee) and maintenance.
  • Relocate/rehost the Council Administration Module (CAM) from RTP (NIEHS) to the CIT data center.
Electronic Council Book Scientific Coding/Query and Reports
  • Enhancements to QVR:
    • Develop and provide selected reports (based on work done by Carol Martin’s group).
    • Design and implement “Grant Folders” (includes PI and Grant histories).
    • Provide additional functionality for output and queries.
    • Provide access to IC coding data.
    • Develop QVR functionality to access the XCDB.
Electronic Council Book Scientific Coding/Query and Reports
  • Coding Extension Systems:
    • Modify existing “STARS” applications to use a single STARS Central Data Base (SCDB).
    • Coding Extension Systems: Design and implement an eXtension Central Data Base (XCDB) that incorporates SCDB data as well as that of other existing Coding Extension systems (e.g., the NCI system developed by Jim Seach). Determine and implement enhancements needed to make the NCI coding system viable for NIH-wide use (e.g., an enterprise coding system).
eRA Interface to the Extramural Community Federal Commons
  • Coordinate NIH and Federal Commons:
    • Enable the eRA Commons to authenticate extramural users via Federal Commons authentication services.
    • Enable the submission of grant funding opportunity synopses to the government-wide repository for grant funding opportunities (FedBizOps).
    • Enable receipt of financial status reports as data streams from the Federal Commons.
    • Enable submission of notice of grant award data streams through the Federal Commons.
    • Coordinate Federal Commons Helpdesk facilities with eRA Helpdesk facilities.
eRA Interface to the Extramural Community   iEdison Redesign
  • Complete the migration to J2EE platform. Complete elaboration, construction and testing and deployment of the next version of IEdison. Successfully integrate at least five additional federal agencies into the iEdison system.
  • Implement full integration of iEdison into the Federal Commons.
  • Integrate final invention certification (final invention report) into eRA Close-Out Module.
eRA Interface to the Extramural Community NIH Commons Enhancements
  • Implement enhancements to Accounts Administration, Profiles (IPF and PPF).
  • Include X-Train and Status (Commons Version 1 modules).
  • Update the Status module to support increased usage by other modules (X-Train and E-SNAP).
eRA Interface to the Extramural Community NIH Commons
  • Complete FSR System including requirements analysis, system design/development (including Commons Integration), testing, training (NIH & Grantee user-community), piloting to full deployment. Aligned with Commons due to the J2EE effort. (Part of FY2001 funded priority 5B, requirements analysis was just begun in late FY2001.)
eRA Interface to the Extramural Community NIH Commons Cross-Cutting Initiatives
  • No-cost Extension Module Integration (Cross-cutting Initiative Commons/GM and maybe Program). Analysis, Design and Development. This would allow grantee institutions to notify us of automatic no-cost extensions via the Commons. At the IMPAC II side, build notification functionality, as well as the ability to “accept” the data (e.g., new project/budget end date) from the grantee.
  • Population Tracking Module Integration (Cross-cutting Initiative) – Provide for the integration of the collection of clinical research study population data through the Commons.
eRA Interface to the Extramural Community e-SNAP
  • Analyze, design and develop Electronic Non-Competing Award Process (e-SNAP).
eRA Interface to the Extramural Community CGAP
  • Analyze, design and develop Competitive Grant Application (CGAP) (datastream submission).
ERA Interface to the Extramural Community CRISP on the Web: Enhanced Functionality
  • Incorporate CRISP Thesaurus functionality into retrieval engine. Implement Thesaurus Feedback page/link to allow for the submission of user suggestions for terminology changes and/or additions.
  • Add the ability to search using multiple Boolean operators for singular (i.e., Epilepsy) or compound terms (i.e., HIV infection).
  • Add “exclude” functionality. Users will be able to exclude terminology from queries (i.e., Brain neoplasm but not chemotherapy).
eRA Interface to the Extramural Community   CRISP Plus: Scientific Code API
  • Incorporate IC specific scientific codes into CRISP Plus via API to provide flexibility for ICs to choose between their coding and CRISP Plus codes for reporting.
eRA Interface to the Extramural Community   CRISP Plus: Automatic Indexing Accommodation
  • Implement the ability to extract the Title, Abstract, and Specific Aims from IMPAC II in the required format for DRD’s Automated Indexing System (DRDAIS).
Grants Management Closeout System Completion
  • Complete Closeout System. Begun in FY2001 (priority 12.1) with the requirements analysis phase complete. FY2002 goals include architecture analysis, system design/development (including Commons Integration), testing, training, piloting and deployment.
Grants Management Grants Management Redesign
  • GM Redesign. As one of the oldest IMPAC II products in production, the GM system is ripe for a face-lift. The redesign would incorporate current industry standards to all existing screens, including providing a Web-based version for the first time. Basic functionality remains efficient.
Grants Management Grants Management Portal
  • GM Portal. Begin discussion/analysis of designing a GM portal.
Grants Management Cross-Cutting Initiatives
  • E-App Integration (Cross-cutting Initiative). While some basic functionality exists in GM to view electronically received and/or scanned applications, we need to evaluate if this is the best way to handle the process. Also need to modify T-5 Receipt Screen to automatically populate E-SNAP receipt date. Maybe some type of notification on this screen as well. Outside of GM, broader, cross-cutting issues that need to be addressed include developing some type of notification system/process for both the GMS and PO.
  • Customizable Checklists (Cross-cutting Initiative ICO/PO/GM). Upgrade links to PO Comments, PO Worksheet, PO Signature Notes. Also deal with educating user community for this new concept.
  • No-cost Extension Module Integration (Cross-cutting Initiative Commons/ GM and maybe Program). This would allow grantee institutions to notify us of automatic no-cost extensions via the Commons. At the IMPAC II side, build notification functionality, as well as the ability to “accept” the data (e.g., new project/budget end date) from the grantee.
  • Business Office E-mailing Initiative (Cross-cutting Initiative). Requested by Dr. Baldwin. The desire is for each of our grantees to establish a single point-of-contact that NIH can use to disseminate significant events or requests for information, i.e., Financial Conflict of Interest plans.
  • FSR System Integration (Cross-cutting Initiative). Provide programming support for the integration of the FSR system into the Grants management module. The initial development effort is part of the J2EE development effort identified under the NIH Commons.
  • Electronic 901 Module Integration (Cross-cutting Initiative). Provide programming support for the integration of the electronic 901 module into the Grants management module. The initial development effort is part of the development effort identified under Receipt & Referral.
Grants Management Grant Management Enhancements
  • High Priority Enhancements. Throughout the year, GM Lead Users prioritize enhancements, reprioritizing as new ones are suggested. Those enhancements that have been flagged as high priority include such things as: 1) providing “Help Text” for all business rules; 2) analyzing PDF format for NGAs generation and storage; 3) Modifying the way we store GM Comments; 4) automating printing of Phase III Clinical Trial footnote.
  • Other Miscellaneous Enhancements to Improve System Functionality. About 20 or so other enhancements have been given Medium or Low priority. These include such items as: 1) One-stop Shopping/Portal concept—Providing direct links to Animal and Human Assurances lists, IEdison, PMS, etc.; and 2) Providing a direct link to other IMPAC II applications; e.g., Grant Update Module, so users won’t need to enter a separate IMPAC II Module.
  • System Changes to Accommodate non-NIH Agencies. NIOSH and AHRQ currently use IMPAC I, ATRS and IAS. The GM system in IMPAC II, including the NGA report, will need to be revised to accommodate these other agencies and their business rules. This will be vital to turn off IMPAC I.
IC Technical Perspective APIs
  • Analyze, design and develop APIs (Application Program interfaces) for the ICs to be able to download applications.
Infrastructure IRDB
  • Get all OLTP business data into the IRDB.
  • Create topic-centric views of the data.
  • Reduce or eliminate table joins.
  • Create summary tables. Maintain concurrency with the OLTP.
  • Update TechView documentation.
  • Provide training through HRDD.
Infrastructure Sunset IMPAC I functionality
  • Type 5 creations in IMPAC II.
  • Type 6 creations in IMPAC II.
  • Type 7 creations in IMPAC II.
  • Forward and Reverse Bridges.
  • Common Mailers.
Infrastructure Single Logon
  • Analyze, design and develop the ability of providing a single logon id for IMPAC II modules.
Paperless Business Practices (Scanning) CD Ordering
  • Analyze, design and develop the functionality of being able to order CDs directly on-line in IMPAC II.
Paperless Business Practices (Scanning) Scanning Infrastructure
  • Provide the infrastructure for all grant applications to be scanned and available to the NIH community via IMPAC II. This includes: BPR to provide a structured approach to capturing the paper documents into the electronic format and the storage requirements to house the images electronically submitted from scanning initiatives (current file room records) of the ICs. The plan is to provide the storage for an IC that makes the decision to, and pays for, the scanning of grants (applications and progress reports only) currently in their file rooms.
Paperless Business Practices (Scanning) Text Searching
  • Analyze, design and develop aggregate text searching for all grant applications.
Paperless Business Practices (Scanning) Scanning: Advanced Features
  • Analyze, design and develop context-sensitive screens so that users could better work with images so as to be able, for example, to capture data directly from the application and incorporate into checklists. There is a need for side-by-side images.
Receipt & Referral Receipt and Referral Enhancements
  • Continue to implement and refine autoassign workflow rules to accommodate recurring review activities that are handled by SEPs.
  • Analyze business processes to achieve improvements in data quality without loss of high productivity, particularly the person search and identification process.
Receipt & Referral Cross-cutting Initiatives
  • E-App Integration (Cross-cutting Initiative)to view electronically received and/or scanned applications, we need to evaluate if this is the best way to handle the process.
  • Analyze, design, develop and implement an electronic 901s module.
  • Develop and implement electronic ARAs (Awaiting Receipt of Application notices) for communication among ICs, DRR and CSR.
Reporting QuickView Enhancements
  • Support for searching for dual assignments, wild cards and additional criteria such as state and human subjects code.
  • Ability to print and/or copy the NGA from the Budget screen.
  • Ability to query historical data as well as current data.
  • Hit list enhancements: additional report fields; ability to export to Excel.
Reporting Reporting Enhancements
  • Have all query and reporting tools/systems have the ability to allow all users to be able to retrieve data from history and frozen (PUB) files as well as from current files.
  • Ability to export all existing reports to a downloadable ASCII-delimited file.
Review Internet-assisted Review
  • Deploy Internet-assisted review (based on the NIAID review model.)
Review Cross-cutting Initiatives
  • E-App Integration (Cross-cutting Initiative). While some basic functionality exists in GM to view electronically received and/or scanned applications, we need to evaluate if this is the best way to handle the process. Also need to modify T-5 Receipt Screen to automatically populate e-SNAP receipt date. Maybe some type of notification on this screen as well. Outside of GM, broader, cross-cutting issues that need to be addressed include developing some type of notification system/process for both the GMS and PO.
  • CD Production (Cross-cutting initiative). Provide programming support for the ability of compact disk production through the Review module.
Review Review Portal
  • Develop a Review portal.
Scientific Program Management Program Module Development
  1. Analyze, design and develop and deploy the Program module.
Scientific Program Management DEA module
  • Analyze, design and develop a DEA module, parsing out the appropriate functions from the existing ICO module.
Scientific Program Management Electronic 901 Integration
  • Electronic 901 Module Integration (Cross-cutting Initiative): Provide programming support for the integration of the electronic 901 module. The initial development effort is part of the development effort identified under Receipt & Referral.
Scientific Program Management GUM Enhancements
  • Provide modifications as needed to the Grants Update Module (GUM)
Scientific Program Management Program Portal
  • Develop and deploy the Program portal.
Scientific Program Management Cross-cutting Initiatives
  • E-App Integration (Cross-cutting Initiative). While some basic functionality exists in ICO to view electronically received and/or scanned applications, we need to evaluate if this is the best way to handle the process. Also need to modify T-5 Receipt Screen to automatically populate E-SNAP receipt date. Maybe some type of notification on this screen as well. Outside of GM, broader, cross-cutting issues that need to be addressed include developing some type of notification system/process for both the GMS and PO.
  • Customizable Checklists Integration (Cross-cutting Initiative ICO/PO/GM). Upgrade links to PO Comments, PO Worksheet, PO Signature Notes. Also deal with educating user community for this new concept.
  • Electronic 901 Module Integration (Cross-cutting Initiative). Provide programming support for the integration of the electronic 901. The initial development effort is part of the development effort identified under Receipt & Referral.
  • ARAs (Awaiting Receipt of Application notices) Integration (Cross-cutting Initiative). for communication among ICs, DRR and CSR.
  • No-cost Extension Module Integration (Cross-cutting Initiative Commons/ GM and maybe Program). This would allow grantee institutions to notify us of automatic no-cost extensions via the Commons. At the IMPAC II side, build notification functionality, as well as the ability to “accept” the data (e.g., new project/budget end date) from the grantee.
Training Activities SITS Redesign
  • Analyze alternatives of continuing SITS as a standalone module or redesigning it as a common module accessed from other IMPAC II business areas.
  • Provide better integration with the enterprise application: use of common Persons module; look and feel; budget/award process; ability to track career outcomes for SITS supportees.
Training Activities TA/Payback Enhancements
  • Redesign APAC to eliminate snap-out mailers to streamline the mail notification process.
  • Perform general/non-specific maintenance/enhancement of the TA/Payback system. Some changes will be related to streamlined processing of payback documents.
  • Develop requirements for automated proxy termination in the case of old appointments.
  • Develop requirements for OFM interface to Payback module.
  • Incorporate field of training (FOT) and new race/ethnicity classifications into TA module.
Training Activities X-Train Enhancements
  • Upgrade X-Train 1.5 to include Fields of Training and new race/ethnicity classification scheme.
  • Activate termination components of X-Train for those without payback obligations.
  • Develop email notification to Program Directors at 12 months after last appointment seeking reappointment information or termination.
  • Develop email utility to notify TA users that X-Train appointments have been received.
  • Develop email utility to notify Program Directors that X-Train appointments have been processed and accepted or rejected.
Training Activities X-Train 2.0
  • Develop requirements/design/deploy X-Train version 2.0 to run in Commons version 2.0:
    • Integrate X-Train with Commons Person Module.
    • Adapt X-Train for use with K12 awards and other non-NRSA institutional training programs.
    • Adapt X-Train to collect information on graduate and postdoctoral research assistants.
User Support Improve Documentation
  • Create searchable/interactive Web versions of all user documentation. Currently, documentation is in PDF only.
  • Procure and deploy new documentation software (that incorporates version control, etc.) to better track changes.
User Support Commons Publicity
  • Support Commons Version 2.0 with major publicity push for V2 deployment in May 02. We need to get grantees on board. There will be newsletters, direct e-mailings and participation at national and regional eRA, NCURA, SRA and other meetings.
User Support User Administration Module
  • Redesign the Users Administration Module (UA).
User Support Enhance User Admin Module
  • Redesign UA to be used for IQR module users (enhancement).