GADS3_Attachment_J_6_Final.pdf

Attachment J-6: GADS Functional System Requirements for Operations and Maintenance

Order/ ID System Acronym

Functional Area The System Shall….

Level of

Importance

Overview The IMPAC II Database Consolidation (IDC) system centralizes all DERT data from IMPAC II into a single NIEHS database repository via an automated process.

Critical

1 IDC Database Maintain data in the same type of database as the data of origin (IMPAC II): an Oracle 11G database consisting of foundation, access and performance, interface and application‐ level tiers.

Critical

2 IDC Database Include a foundation tier for core and non‐core tables and store the data at the most granular level. Critical

3 IDC Database Use the access and performance tier to transform the data into different logical or physical representations that the Government needs to meet NIEHS application access and navigation needs.

Critical

4 IDC Database Use the interface tier as the bridge between the IDC tables and the NIEHS application/end users. Provide the needed public synonyms and views in the interface tier.

Critical

5 IDC Database Use the application tier for those NIEHS applications which access the IDC data repository and download process. Critical

6 IDC

Standard Extraction, Transformation, and Load (ETL) process

Load data through the "extraction, transformation, and load " (ETL) process, nightly. Process, validate, and cleanse data received from the IRDB source database (Oracle 11G). Load the data into core and non‐core tables in the foundation tier.

Manage the process through stored procedures. Complete the process within two hours of process initiation.

Critical

7 IDC Ad‐hoc ETL Process Perform ad‐hoc ETL processes in case the Government needs to refresh the IDC on an as‐needed basis. Critical

8 IDC Backup/Redundancy Approach Utilize a two‐database approach to minimize loading risk. Store the active, most recent data in one set of tables and store inactive data in a second set of tables, which shall serve as a backup in case of load failure. Use the active table set to delete, cleanse, and load the data with the extraction transformation and load (ETL) process.

Critical

9 IDC Maintenance Include an historic partition where older data resides (maintained on a quarterly and annual basis). Critical

10 IDC Import Import NCI data for use in HITS. Critical

11 IDC Performance Ensure speed and performance of system is strong ‐ review and update architecture periodically to maximize performance.

(Optimize performance of the Oracle database, review SQL statements, reconfigure architecture.)

Critical

12 IDC Maintenance Maintain list of IDC Dependencies, especially re timing for Scheduled Tasks. Critical

Overview The Grants Funding Decision Tool (GFDT) supports DERT in managing external grants by providing transparency into the funding decision‐making process, tracking funding plans, and performing council‐related processes.

Critical

13 GFDT Import Import all NIEHS grant applications and grant financial data nightly from the IDC. Provide the ability to download from the IDC on demand as needed.

Critical

14 GFDT Application List

Provide the ability to display, sort, filter, and export any/all applications within a fiscal year. Support a robust display, sort, and filter options. Support NIEHS' need to prevent the display of applications from those in conflict with them, where appropriate. Provide links to pertinent application information. Provide the ability to download selected data to Excel or PDF format. Provide the ability to sort applications in consideration for funding as needed and to create a pdf of those documents.

Critical

15 GFDT Application status logging Keep and display a log of application status codes from application to award. Critical

GFDT

IDC

Attachment J-6 | Page 1

System Acronym

Functional Area The System Shall….

Level of

Importance

16 GFDT Administrative tools

Support administrative tools such as: manage users; edit the NIH Grant activity groups and mechanisms; edit the FOA/PA/PARs and the meetings list; manage financial attributes, budgets, and payline; manage Common Accounting Numbers (CANS) used and CAN associations by activity and PCC codes; manually add secondary applications from IDC;

manually update the data from the IDC as needed; notify the referral coordinator when a PCC code is empty and needs attention.

Critical

17 GFDT Search for applications Provide the ability to search within the GFDT for applications based on type code, mechanism, institute, application serial number, support year, suffix code, and/or PI first name and/or last name.

Critical

18 GFDT Funding Plan Workflow

Create a funding plan and circulate it through a multi‐step, multi‐reviewer workflow. Allow reviewers/signers to view all documentation associated with each application. Track application status through time and display it within the system.

Modify approval path if signers are in conflict with the application. Group applications together into unique funding plans as needed (e.g., R13/U13).

Critical

19 GFDT

Specials Nomination Workflow (aka PO Workflow)

Enable Program Staff to nominate an application for funding, initiate the approval process, upload/input documentation and fill in fields to justify the nomination of the special action. Route the nomination through various roles (branch chief, deputy division director, grants managment staff). Link documentation to the application record and make accessible to all users.

Critical

20 GFDT Atypical Actions Workflow

Provide the ability to identify, prioritize, and approve applications requested for co‐ funding by other ICs or other potential application funding opportunities that present themselves outside of the typical workflow. Once approved, the applications should be incorporated into the list of remaining special applications and allow them to be processed along with the other applications considered for funding.

Critical

21 GFDT Program plan workflow Enable Program Staff to view applications associated with an RFA, select those in the payline and route the program plan for approval to Branch Chiefs, and other leadership. Provide a dashboard for program planning. Send reminder emails related to program planning.

Critical

22 GFDT Staff Summary Statements Route documentation needed for specific Council review actions (including Applicants >$1M; foreign applications, high program priority, low program priority, and supplement requests >150K).

Critical

23 GFDT Intent to Pay/Not to Pay letters Provide a dashboard that allows the Deputy Director to send out emails to the contact Principal Investigator of an application to notify them of our intention to pay/not to pay the application they submitted.

Important

24 GFDT

NGA Clearance ‐ Manage applications

Display financial information to a select group of users regarding all newly awarded grants to provide a checkpoint that they have been dispersed properly.

Critical

25 GFDT Email Notifications Send reminders for upcoming or overdue actions. Important

26 GFDT

Monitor Common Account Numbers

Monitor Common Account Numbers (CAN) and alert FMB staff when new numbers are issued (former called CAN Monitoring).

Critical

27 GFDT Reports Allow users to easily export reports, e.g., for funding plans. Ensure that reports are easily accessible. Important

28 GFDT Role Based Access Provide system Roles to tailor UX features and workflow routing: Administrator, Branch Chief, Council Coordinator, DERT Director, DERT Deputy Director, Financial Management Branch, Grants Management Officer, Institute Director, Office of Extramural Research Approver, Program Officer, Read Only. Provide 'single signon' access to users.

Critical

29 GFDT Maintenance GFDT‐Specific maintenance: year‐end task list closeout, Fiscal Year Rollover. NOATS closeout/rollover support (annual). Critical

30 GFDT Information letters Track information letters that must be reviewed by the Council, including the ability to identify required letters, upload documents, fill out forms, and circulate for appoval.

Critical

Attachment J-6 | Page 2

System Acronym

Functional Area The System Shall….

Level of

Importance

Overview

The Supplement Operations System (SOS) manages workflows for processing administrative supplements. It is a Cold Fusion 2016‐based system using an Oracle 11G database and "petri‐net" open source to manage workflows. The system processes supplements, documenting assessment, priority, and final decisions. The system enables users to import data, upload new documents, input justifications, assess merit, prioritize, create pay plans, route for signature, and create analytic reports.

Critical

31 SOS Role Based Access

Provide the following system roles: Administrator, Branch Chief, Committee Chair, Committee Member, Deputy Director, Division Director, Financial Management Branch, Grants Managment Monitor, Grants Management Officer, Grants Management Specialist, Human Subjects Manager, Program Officer, Reviewer, Read Only, Supplement Manager. Provide 'single sign on' access to users.

Critical

32 SOS Importer Import data from the IDC daily. Critical

33 SOS Reconcile applications Reconcile applications submitted via email box and grants.gov to ensure there is no duplication, i.e., that there is one record per supplement application.

Critical

34 SOS UI/UX Search, Filter, Display, organize supplements in the system (custom to do list, separate list for committee, utilities, etc.) Critical

35 SOS Annual Maintenance Annual review of lists with to archive inactive dropdown options Important

36 SOS Supplement Review Workflow

Use a workflow methodology to route applications through the review process. Support the upload of supporting materials, review and justify budget, prioritize for committee review. Include reviews by program and grants management staff, assignment to meeting date, review by committee for funding recommendation. Generate funding plans. Support the addition of approved applications to funding plans for review by budget, grants management, branch chiefs and DERT leadership. Collate justifications, recommendations and comments (including rejections) for a final award/non‐award file..

Allow rejection paths at any point within the workflow, requiring a reason for rejection and creating a final non‐award file.

Critical

37 SOS Supplement types Enable users to identify one of three specific workflows as the application is added to the interface (we call this a "path). One of many supplement "types" is assigned to each application for various tracking purposes. Support multiple Supplement types; up to 10 new types (following an existing path) are added annually.

Critical

38 SOS Provide alerts Send email alerts to affected staff as applications are processed about status changes or actions needed. Critical

39 SOS Reports Provide needed reports including: basic, budget mechanisms, committee summary, committee worksheets, director's, diversity, funding plan reports, PI history, process metrics, and user status.

Important

40 SOS Utilities Provide needed utilities including the submission of a budget, user accounts, electronic submissions, the management of applications over $500K, reminders, management of emails, surrogates, meeting dates, and to‐do lists.

Critical

41 SOS

Automate status changes in

IMPAC II

Interact directly with IMPAC II using web‐services to "accept" the application and enable its processing in SOS. Interact directly with IMPAC II using web‐services to "complete" the Supplement application process (final award, or non‐award files, to eGRANTS) and to update the application status to either "activate" or "not funded"

Critical

SOS

Attachment J-6 | Page 3

System Acronym

Functional Area The System Shall….

Level of

Importance

Overview The High Impacts Tracking System (HITS) provides the knowledge management repository and reporting tool for grant outputs and impacts. The system supports information processing from a wide variety of data calls and analyses conducted by PAB and DERT, as well as the IMAT program from the National Cancer Institute

Important

42 HITS Role Based Access Provide the following system roles: Program Officer, System Administrator, Tag Administration, Tag only. Provide administrative utility to manage users. Ensure NCI users area ble to access HITS without the use of VPN if they are using the NIH LAN. Provide single sign on access.

Important

43 HITS Architecture Maintain a six tier infrastructure, consisting of Client, Presentation, Processing, External System, Data and Security. Organize data around "projects" and their "subprojects," which may consist of one or more funded annual "grant applications" (as definded by the APPLID field in IMPAC II)". A project is a collection of applications with the same Activity Code, Institute Code and Serial Number, as tracked in the NIH IMPAC II database. Ensure that data (Tags, documents, grant data) for subprojects are shown rationally and consistently through both the interface and the reporting module. Support a pilot project that collects and displays data needed for systematically tracking translational research stories.

Important

44 HITS Importer Import a basic set of grant data nightly from the IDC. The HITS data set consists of grants funded since 2012. Application documents are imported using the eRA document webservice. Portfolio codes are imported nightly from the Grants Coding Database. Enable NCI IMAT program to import all relevant grant data (including the new IMPAC II document service) for IMAT RFAs (specified) via the IDC.

Important

45 HITS Search Provide a single interface to search all types of data in HITS, e.g., Grant Data, Document content, Portfolio Codes, and Tags.

"Smart" searches should be enabled to help the user navigate quickly to what is desired (e.g. type‐ahead fields, "like" searches, partial word searches, etc.).

Important

46 HITS Display/UI/UX Display search results in a grid, based on the type of information searched and according to user preferences. Ensure results can be exported to excel. Hyperlink results in the grid, allowing the user to open details in new tabs. Display number of results found and search parameters. Display all information related to the project on a single page, with collapsible sections.

Ensure the interface defaults to a view that is tailored to the user's institute (NIEHS or NCI).

Important

47 HITS Tags Enable users to create project "tags" that are systematically structured to provide relevant information to the type of tag that is being applied to the project. Maintain a special role who can edit and create new tags. (For scale, approximately 70 of these qualitative tags exist in the system today.)

Important

48 HITS Tags Connect uploaded docs to tags. Important

49 HITS Report Enable user to export anything in the system either in detail or aggregated formats. Fashion search filters for reports after those on the main search page and customize to the type of report delivered. Maintain nine existing reports in currently produced as Excel or Word files. Provide reports that automatically update to include new tags added using the tagging administration interface.

Important

50 HITS Document upload Enable the user to upload PDF documents associated with specific programs or grants (display, search, report on the content and metadata of those documents)

Important

51 HITS NCI Project Extend all HITS functionality to the Innovative Molecular Analysis Technologies (IMAT) program at the National Cancer Institute (NCI).

Important

52 HITS NCI Greensheets Enable NCI's IMAT program to import grant data in the NCI Greensheets program directly into the HITS database nightly via API. Ensure the NCI Greensheets data are searchable, displayed, and part of reports.

Important

53 HITS Help/Tool tips Provide easy to understand user guides, system documentation and on screen help to users via tool tips. Important

54 HITS Utilities Provide utilities to add new users, change user roles, save searches, load existing searches, and load lists of grants. Important

HITS

Attachment J-6 | Page 4

System Acronym

Functional Area The System Shall….

Level of

Importance

Overview TRIPS is a new (FY2018 launch) system that enables users to manage travel budgets, enter, review, prioritize, estimate costs, and ultimately authorize expenditures on government travel in DERT.

Important

55 TRIPS Database Provide all travel related information to those who need it in a transparent way. Ensure the basic unit of analysis for the system is a "trip". Note: all data are input by users, none is imported from other systems and no files are uploaded.

Important

56 TRIPS

Role Based Access

Provide the following system Roles (read/write permissions and display differ for many of these in workflows):

Administrator, Division Director [inactive], Administrative Officer, Division AO, Branch Chief, Team Lead, Travel Planner, Traveler. Manage users based on their NIH Employee Database (NED) status. Organize approval hierarchy based on supervisory and branch relationships in NED.

Important

57 TRIPS Navigation Organize informtation across six tabs: My Trips, Planned Trips, Actual Trips, Reports, Administration, Help. Default to the current fiscal year on all screens. Users may select other FYs as needed.

Important

58 TRIPS "My Trips" Data Entry and Display

Provide a dashboard for each traveler that shows their own requested trips in a grid. Columns include TripID, Event Title, Travel Type, Travel Dates, Location, Trip Cost, Registration Cost, Traveler Planned Priority, Trip Status and Actions. Display visual status indicator. Enable traveler actions: add new trip (planned or ad hoc), copy trip, recall trip (reset the approval workflow), cancel trip.

Important

59 TRIPS Trips Detail Page Display details of trip. Track status changes and comments in a log at the end of the page. Enable travelers to add comments.

Add entered comments to the log, ordered by data entry date. Allow comments to be exported.

Important

60 TRIPS "Planned Trips" Workflow Enable division‐wide budget planning during budget preparation period (typically August, September, October). Enable collection of limited trip information (dates, location, priority, rough cost estimate, expected CAN) from travelers and travel planners to allow Branch Chiefs to establish a full fiscal year of travel budget. Enable AOs to begin, lock, unlock and relock the planning period. Ensure that when AOs lock the planning period, all planned trips become "actual" trips. Ensure that trips entered during the planning phase can be converted to an actual trip before the Division is locked, if formal approval is needed. Enable rejection or rework requests that reset the workflow.

Important

61 TRIPS "Planned Trips" Display Provide a dashboard to display planned trips and budgeting data by branch or team. Include a budget grid that automatically calculates expected and actual expenditures by CAN (branch, reimbursible, unassigned) and priority (high, medium, low, unfunded) for both trips and registration fees. Provide counts and total budgets for each category. Include a searchable, sortable trip grid that summarizes individual trip data for the branch or team and links to the trip detail page.

Important

62 TRIPS "Actual Trips" Workflow Provide an approval process for travelers to request travel approval, travel planners to calculate a detailed cost estimate, and supervisors (Branch Chiefs and Team Leads) to approve the travel (i.e. assure funds are available and provide supervisory permission to travel). Produce the Travel Request Form (TRF), a signed document that is used to authorize travel planners to create Travel Orders. (Travel Orders are created manually in a separate system.) Step the user through data collection forms logically and in a way that indicates progress. Enable rejection or rework requests that reset the workflow.

Important

63 TRIPS "Actual Trips" Display Provide a dashboard to display actual trips and budeting data by branch or team. Include a budget grid that automatically calculates expected and actual expenditures by CAN (branch, reimbursible, unassigned) and approval status (approved, pending, traveler cancelled, disapproved, unfunded) for both trips and registration fees. Provide counts and total budgets for each category. Include a searchable, sortable trip grid that summarizes individual trip data for the branch or team and links to the trip detail page.

Important

TRIPS

Attachment J-6 | Page 5

System Acronym

Functional Area The System Shall….

Level of

Importance 64 TRIPS "Actual Trip" Scratch Pad Enable travel planners to create a detailed cost estimate using established formulas and costing parameters. Collect needed information from the traveler or the planner. Auto populate certain fields in the scratch pad and allow travel planners to edit. Calculate certain fields automatically. Include both summary data and detailed scratch pad data in the TRF.

Important

65 TRIPS Registration fee tracking Provide the ability to track registrations and fees associated with travel and to add non‐travel expenses into TRIPS so that branch chiefs can manage their registration budgets.

Important

66 TRIPS Special circumstances Handle special circumstances: Ensure that specific information is collected and specific routing is followed for local, domestic, international, domestic sponsored, and domestic international trip types. Ensure that reimbursable CAN budgets can be easily managed by Supervisors. Enable supervisors to move trips to another branch if the other branch will be paying for the trip. Ensure that both supervisors approve any trips that are moved.

Important

67 TRIPS Reports Produce standard reports for users: Planned Report; Actual Report; Actual compared to Planned Report; Moved travel report (i.e. when a trip for a person in my branch is being paid by another branch; Trip details report (including history and comments); Traveler report.

Important

68 TRIPS Automated emails Send action needed and reminder emails when trips change status during any of the work flows. Important

69 TRIPS Invitational Travlers Enable travel planning for non DERT employees (the travel planner enters data that the traveler would normally enter).

Support invitational travlers in both planned and actual planning periods.

Important

70 TRIPS Utilities Enable Administrative Officers (AOs) to add new Branches and CANs, assign people to Branches, assign budgets to CANs (allocate), assign reimbursable CANs to multiple Branches, set budgets for "POTS" costs, and view CAN allocations. Enable supervisors with "teams" to sub allocate budgets to the Team Leads and ensure these supervisors only see trips for their direct reports. Enable travel planners to add and manage invitational travelers.

Important

71 TRIPS Manage AO approval and Voucher data

Until AO and Voucher approval workflows are developed, if a trip status is "TRF complete", enable data entry on the trips detail page to allow tracking and reporting.

Important

Overview The Partnerships for Environmental Public Health Resource Center (PEPHRC) is a secure repository for NIEHS grantees and their collaborators who are part of the PEPH Network. Materials created by participants within the PEPH Network are stored in the PEPHRC.

Important

72 PEPHRC Role Based Access

Enable user login via federal government email address, federated university ID, or Google or PayPal id (social/open id).

Restrict access to ensure that only people associated with PEPH‐participating institutions, programs, and projects can upload or edit materials. Manage various user roles: Administrator, User I (view & download, edit profile), User II (User I permissions plus submit/edit materials). Identify users as a PI, a POC (point of contact) or neither. Associate users with NIEHS Grants.

Important

73 PEPHRC

Find materials, people, programs, and institutions

Enable quick and easy access to materials, people, programs, and institutions. Facilitate user assessment of the search results' relevance.

Important

74 PEPHRC Download materials Provide the ability to easily download materials or retrieve materials from grantee websites. Important

75 PEPHRC

"Like" and comment on materials

Provide the ability for users to "like" and comment on materials they have viewed, downloaded, or used and alert users when materials submitted have been downloaded, liked, or commented on.

Important

76 PEPHRC Upload materials Enable quick and easy submission of materials. Important

PEPHRC

Attachment J-6 | Page 6

System Acronym

Functional Area The System Shall….

Level of

Importance

77 PEPHRC Manage materials (workflow) Allow administrators to create, remove, and modify accounts, projects, materials, program information, and lists of expertise and interests. Enable administrators to review, comment, approve, and/or reject submitted materials to ensure that all materials in the PEPHRC have passed a screening process and have met certain requirements.

Important

78 PEPHRC

Find and connect with other users

Enable users to find others to discuss items of common interest, using audience, expertise, institutions, and programs. Important

79 PEPHRC

Highlight and promote materials and news

Facilitate system administrators' ability to highlight specific materials, programs, news, and relevant discussion threads from the PEPH listserv. Display highlighted/featured items prominantly.

Important

80 PEPHRC Edit account information Provide a way for users to edit their account information. Important

81 PEPHRC Homepage Provide a home page where users can view listserv discussion, highlighted/featured materials and displayed news. Important

82 PEPHRC Generate Reports Provide a tool for the administrators to generate reports. Important

Overview Who We Fund is a publicly available website that displays active grant portfolio along with publications and program officer information.

Important

83 Who We Fund Import Import the data needed from the IDC and PubMed on a regularly scheduled basis. Important

84 Who We Fund Search Filter and search by science topic, state and other key words. Important

85 Who We Fund Display

Display a listing of grants by category (identified based on PCC code) and the list of publications associated with each grant.

In the list include the principal investigator (PI), institution name, grant number, and program officer assigned to the grant.

Enable end‐users to select the grant title to get further information on the grant, or the program officer name to find contact information for that program officer, or the list of publications to get further information on the publication.

Important

86 Who We Fund Reports Enable the user to export lists to MS Excel, Word, and Adobe Acrobat. Hyperlink WWW based information. Important

Overview Support Scheduled Tasks (ST), which are a set of Cold Fusion programs designed to extract data from the IDC and send it to the intended recipients in the specific format requested. Base the Scheduled Tasks on an n‐tier architectural design model that includes four logical groupings (tiers): data tier, processing tier, presentation tier, and security tier.

Important

Scheduled Tasks

(ST)

IDC Import ST Ensure the automated task that imports fresh data into the IDC runs nightly with no errors. Important

Scheduled Tasks

(ST)

Application Assignment Automatically send an Excel spreadsheet every two weeks via email to DERT Staff with a list of applications whose Program Class Codes (PCC) have changed within the past two weeks. Alert Program Officers and Grants Management Specialists when grant applications have been assigned to them.

Important

Scheduled Tasks

(ST)

Generate Active Grantee List Send a *.txt document via email to identified staff with the first name, last name, and email address of the NIEHS Currently Active Grantees.

Supportive

Scheduled Tasks

(ST)

GM Closeout (Leadership) Scheduled Task

Send a report monthly via email to the Grants Management (GM) Leadership team listing awards that are in closeout status and which have a budget end‐date over 149 days from the current date.

Important

Scheduled Tasks

(ST)

GM Closeout Notification Scheduled Task

Send a report to the Grants Management Officer listing any award with a budget end‐date of at least 150 days that has not been closed out.

Important

Scheduled Tasks

(ST)

Grants Workload Details Scheduled Task

Send an excel spreadsheet once per month via email to the GM Leadership team with a detailed list of applications assigned to Grants Management Staff for the previous, current, and future fiscal years.

Important

Scheduled Tasks (ST)

Who We Fund

Attachment J-6 | Page 7

System Acronym

Functional Area The System Shall….

Level of

Importance

Scheduled Tasks

(ST)

Human Subjects ‐ Percentiled Unsolicited Report

Send a report via email to the human subjects specialist and the program officer assigned to the application when an investigator‐initiated application has a percentiled score within the NIEHS payline and includes human subjects.

Important

Scheduled Tasks

(ST)

Human Subjects ‐ Funded Report

Send a report via email to the human subjects specialist and the program officer assigned to the application when the application is "competing", has been marked as "to be paid," and contains human subjects.

Important

Scheduled Tasks

(ST)

Human Subjects Application Type Change

Identify any Human Subjects related applications with "type changes" and send an email to appropriate staff. Important

Scheduled Tasks

(ST)

No Progress Report Send a report via email to the Grants Management Specialist assigned to the grant when the progress report is overdue. Important

Scheduled Tasks

(ST)

Non‐completed Checklist ST Send a report to the Program Officer and Grants Management Specialist on record when the type 5 checklist (required in the IMPAC II Program Module to issue grant payments in a non‐competing grant year) is overdue.

Important

Scheduled Tasks

(ST)

Null PCC Code Scheduled Task Send a report to the Referral Coordinator designee when applications are newly assigned to NIEHS. Display applications assigned to NIEHS in the Review Module in a separate tab.

Important

Scheduled Tasks

(ST)

PCC Change Notification Send a report to the SOS Program Manager to notify her of any PCC code changes. Supportive

Scheduled Tasks

(ST)

PO Closeout Notification Notify the Program Officer assigned to the grant when the grant remains in close‐out status for a specific period of time (calculated by the system).

Important

Scheduled Tasks

(ST)

Summary Statements Scheduled Task

Send application summary statements to the Council Coordinator on a regular basis. Important

Scheduled Tasks

(ST)

Time Sensitive Notify appropriate DERT personnel when applications are submitted in response to the Time‐Sensitive Funding Opportunity Announcement (FOA).

Important

Scheduled Tasks

(ST)

Secondary Assignments Scheduled Task

Send a report to the Referral Officer designee when there are specific pre‐ designated terms in the abstract of an application that may be within the NIEHS mission boundaries.

Important

Scheduled Tasks

(ST)

Type 2 Notification Assignment Notify the Referral Officer designee of all "Type 2" applications. Important

Scheduled Tasks

(ST)

Notice of Award Send an email to the Program Officer and Grants Management Specialist of record when a new grant or supplement has been funded.

Important

Scheduled Tasks

(ST)

R35 eligiblity Provide a report on a regularly scheduled basis to help identify researchers eligible for the R35 mechanism. Important

Overview The Study Section Calendar Tool notifies staff about Study Section Review dates and assignments and provide pertinent information for each review.

Important

Study Section Calendar Tool

Role Based Access Provide the following system roles: Program Officer, System Administrator.

Important

Study Section Calendar Tool

Importer Import needed data from the IDC on a daily basis. Important

Study Section Calendar Tool

View Study Section and application information

Display a brief overview of study sections relevant to the user. Provide the ability for program program staff search and filter and sort applications by program officer, study section, date, primary, secondary, or all, to view application and study section information.

Important

Study Section Calendar Tool

Meeting coverage/coordination Allow program officers to coordinate study section meeting coverage within the tool by asking for backup and offering to cover for others.

Important

Study Section Calendar Tool

Email Notifications Notify program officers when applications in their portfolio are assigned to study section review. Notify the program officer both 30 days and five days prior to the study section review date.

Important

Study Section Calendar Tool

Attachment J-6 | Page 8

System Acronym

Functional Area The System Shall….

Level of

Importance

Overview Allow DERT staff with access to the tool to predict grant expenditures in future years based on various assumptions and scenarios.

Supportive

Budget Forecasting

Importer Enable on‐deamand import of fiscal year data from the IDC via the administrative tab. Supportive

Budget Forecasting

Budget and scenario development

Allow users to create, edit and view baseline budgets by grant mechanism and solicitation status, modify different budget and grant parameters and create "what if" scenarios in order to predict the impact of different budget scenarios on the results.

Supportive

Budget Forecasting

Calculations Provide a range of calculations that assist in predicting consequences of particular budget alternatives. Supportive

Budget Forecasting

Display Models Display budget scenarios for current year and five years into the future in thousands of dollars. Allow users to filter on mechanism, group, activity code, competing status, solicited status, and year. Allow user to expand and collapse different line items (RPG, SBIR/STTR, Centers, etc); Provide subtotals and grand totals. Enable export to MS Excel.

Supportive

Budget Forecasting

Attachment J-6 | Page 9