When you are logged in to SAGE, but have not been actively using the system for 40 minutes, you will see a dialog message indicating that your session will expire in 5:00 minutes. The dialog will continue to count down the time. You have the option to click “Keep Working” to re-activate your session.
If you do not click “Keep Working”, then when the time count reaches zero (0) minutes, your session will expire. Your browser will be redirected to a “session expired” page from which you can log back in to the system you were using. Any unsaved data at the time your session expires will be cleared.
The SAGE system has always timed out after 45 minutes of inactivity. We have now made the timeout more visible so you know that your session has expired, instead of sending you to the tasklist with no explanation.
The following image shows the session timeout dialog, with the time remaining until expiration and the instruction to click “Keep Working” if you want to continue to stay logged in.
Campus research teams and related central offices use the SAGE Suite electronic research administration system to manage application proposals and related items. The suite is comprised of three components that access the shared SAGE Suite database.
- SAGE: System to Administer Grants Electronically – used by campus researchers and administrators
- SPAERC: Sponsored Projects Administration & Electronic Research Compliance – used by the Office of Sponsored Programs (OSP)
- SERA: System for Electronic Research Accounting – used by Grants and Contract Accounting (GCA)
- FIDS: Financial Interest Disclosure System – used by researchers designated as investigators and integrates with SAGE
The following set of tables gives a high-level overview of who uses each of the different components, and describes the possible actions and the why and/or when.
SAGE: System to Administer Grants Electronically
WHO: Campus research administrators, Principal Investigators, campus reviewers, compliance reviewers
||WHY / WHEN
|Create SAGE Budgets
||Centralizes data gathering for salaries, benefits, F&A rates. It can be connected to an application, which automatically populates the eGC1 budget data on the Budget & Fiscal Compliance page. Any changes to the budget will update in real time when the eGC1 Budget & Fiscal Compliance page is viewed.
In addition, if your eGC1 is a Grant Runner application using the RR Detailed Budget form, your budget data will be mapped into the form.
|Create applications (standard or Grant Runner)
||Required for all sponsored research. The standard eGC1 pages of the application are, in effect, an approvals routing cover letter for the proposal. It is used only by the UW and does not go to the sponsor.
A Grant Runner application includes, in addition to the standard eGC1 pages, the sponsor forms for NIH. It is submitted system-to-system by OSP.
|Approve routing applications
||Used by the Principal Investigator, Multiple-PI, Application PI, academic reviewers (division, department, dean) and compliance reviewers (human subjects, animal use, EH&S, etc.) to view and approve the application. At each approval, a PDF snapshot of the application is captured and attached to the eGC1 on the Approvals History & Comments page. Copies of the attachments are also captured.
Administrators and reviewers have the option to return the application to the research team for changes. They can also add other reviewers (as individuals or a group) to the approval flow. These are referred to as “ad hoc” reviewers (approvers or watchers).
|Request an advance budget number for awards
||Used when the research proposal is being awarded by the sponsor, but the actual award has not yet arrived. It requests GCA to set up a budget account in the financial system so the research team can start spending the anticipated award money. The preparer completes the request in SAGE, then GCA processes it in SERA.
Applications are initially considered ineligible for an advance, by default. The eGC1 preparer must use the Advanced Budget Eligibility tool to request that OSP mark the application as eligible so that an advance request can be created.
|Create subaward requests for awarded applications
||Used when a research proposal has been awarded and part of the award needs to go to the subrecipients (subcontractors) that the UW research team will be collaborating with. For a new award, a “new” subaward request (SA) is created along with its parent subaward (SC). For an ongoing award, a “modification” request would be created within the existing subaward (SC).
SPAERC: Sponsored Projects Administration & Electronic Research Compliance
WHO: Office of Sponsored Programs (OSP)
||WHY / WHEN
|Review and approve applications
||OSP reviews the information on the eGC1, such as the sponsor proposal information and compliance questions, after all campus reviewers have approved. When OSP approves the application, they place it into a new or existing Cycle.
|Add Approved applications to a Cycle
||A Cycle holds a “competing segment” for a research team/project/sponsor combination. It’s a container to keep applications, their related advances, funding actions, admin actions, and subawards together. One cycle can be “related” to another, so that more than one segment is associated.
A Cycle is automatically deleted when the last item in it is removed.
|Create various types of Administrative Actions as needed
||Administrative Actions document various related agreements, adjustments and/or changes, and the finalization of a research project. These actions all appear in the project’s cycle, associated to their appropriate parent item.
Note that all actions (including Funding Actions) start as “unidentified” ones, with a prefix of AA. They are then converted to the specific type needed.
- Non-Award Agreement (NAA) records a generic agreement not pertaining to funding.
- Pre-Award Notification (PAN) records a change to the proposed project before the sponsor awards funding.
- Post-Award Change (PAC) records changes to the project after the sponsor awards the funding.
- Close Out (CO) records the tracked activities to terminate a project upon completion of the research.
|Create Funding Actions (FA) for awards
||When an application is awarded by the sponsor, OSP creates a Funding Action as a child of the application. Depending on answers to certain compliance questions, there may be automatic “holds” applied.
Once the FA is completed (and all holds are cleared), it is trasmitted to SERA for GCA to establish a budget in the financial system (if not already done via Advance Request).
||OSP reviews the subaward requests, and negotiates the contract with the subrecipient. The request moves through several statuses until, when the agreement is “fully executed” the request becomes Active. It is automatically “Expired” once the End Date is passed.
SCs and FAs can have a many-to-many relationship. The system enforces that all related FAs and SCs must be within the same cycle.
SERA: System for Electronic Research Accounting
WHO: Grant & Contract Accounting (GCA)
||WHY / WHEN
|Process Advance Budget Number Requests
||Received from the research team, this allows the team to spend award money before the actual award arrives. GCA adds a budget number to the ADV and sets up that budget in the financial system. As part of completing the ADV, the system sends a notification to the requesters.
|Process Funding Actions
||Received from OSP. GCA adds a budget number, if needed, and sets up the budget in UW financial system. As part of completing the FA, the system sends a notification to the requesters, and the first-level reviewers for the organization code receiving funding.
|Process Post-Award Changes
||Received from OSP. Not all types of PACs are sent on to GCA. As part of completing the PAC, the system sends a notification to the requesters.
|Create “Other” items
||Created as needed for various budgetary processes. These items only appear in SERA.
FIDS: Financial Interest Disclosure System
WHO: Any research personnel designated as an “Investigator” on the PI, Personnel, & Organizations page of the eGC1.
||WHY / WHEN
|Create a Financial Interest Disclosure for an eGC1
A disclosure for a CoMotion tech transfer agreement or IRB approval
Complete an Annual Update disclosure
|Investigators are required to disclose any significant financial interests (SFI) such as salary, equity, sponsored travel, etc., that might, or might appear to, bias their research.
An investigator must complete a disclosure for each eGC1, whether or not there are SFI that apply, before the proposal can be marked as Ready-to-Submit = Yes.
The disclosures are reviewed by the SFI Reviewer, in the central Office of Research, who determines if there is a potential for a Financial Conflict of Interest (FCOI). The review occurs at the time of award (just-in-time).
Annual Updates: All investigators are required to review and update their SFI at least once a year. The “year” is calculated from the date of the last disclosure created. Investigators are notified by email 45 days prior, and again at 15 days prior, to the end of that year’s time.
Full details on using FIDS can be found in its User Guide.
Note: only a UW NetID is needed to access FIDS.
This component of SAGE (System to Administer Grants Electronically) is an electronic workflow to route eGC1s for approval by associated departments, colleges, compliance offices, and the Office of Sponsored Programs.
SAGE – the System to Administer Grants Electronically – is the web-based system used by faculty, researchers, administrators and staff.
You can stay up-to-date on changes in SAGE (and FIDS) by subscribing to our Office of Research Information Services (ORIS) News.
The core SAGE system allows you to carry out several tasks.
- SAGE Budget helps you create an accurate budget for your grant proposal. It auto-populates data from the payroll and financial systems, helps you select proper rates, and calculate totals automatically. You can connected a budget to a standard or Grant Runner eGC1 to populate budget data.
- eGC1 Forms are the electronic Grants and Contracts forms you use to route your grant proposal through the University’s internal compliance process.
- Grant Runner applications combine the eGC1 and sponsor forms for some NIH funding opportunities requiring SF424 R&R forms, including Modular, Detailed and Subaward Budgets. With the click of a button, OSP can electronically submit your application via Grants.gov to the sponsor.
- Approvals is the electronic routing engine that stages eGC1s for approval by associated departments, colleges, compliance offices, and the Office of Sponsored Programs.
- Advances creates an online request form for an advance budget number.
- Subawards submits a request for a new subaward or a modification of an existing one.
The text version of the page has an Approval Flow Details section instead of the graph. It consists of a table listing the units and individuals who need to approve or watch this application.
The table columns are:
- Rule Type: The reviewer, and when applicable, their affiliated unit.
- Approval Status: Waiting Approval, En Route, etc. See the Approval Statuses article for more details.
- Acted On By: The name of the person who approved or watched the application.
- Date: The date and time the approval or watched status changed.
- View Reviewers: Click to display the Reviewer Details for this role, which includes the reasons for this reviewer.
The following image shows an example of this section.
This is the visual graph of approvers and watchers. The graph begins on the left with the PI and ends on the right with the Office of Sponsored Programs (OSP). Directly under the PI node, is a node for the Preparer/Owners.
If there is an Application PI, that node is immediately to the right of the PI. If there are one or more Multiple PIs, they will follow the PI or the Application PI, if there is one. The Multiple PIs are displayed one below the other. Note that if the Multiple PI is a non-UW person, they will not appear on the approval flow.
The top line of nodes on the graphical version generally are the reviewers associated with the organization receiving funding. The order of other nodes is not fixed.
There is a Legend on the page that defines what the colors of the nodes mean.
- You Are Here (thick dark border on a node) indicates your node on the graph
- Watching (color white) indicates that none of the watchers for this “node” has marked it as Watched
- Watched (color light gray) indicates that one of the watchers for this node has marked it as Watched
- En Route (color light purple) indicates that the associated reviewers have not yet been notified
- Waiting Approval (color medium purple)indicates the associated reviewers have been notified
- Approved (color light green) indicates an approver has approved the application
- Returned (color light pink) indicates that a either a campus or OSP approver returned the application to the preparers for changes
Each node lists the person or unit reviewing, the role (for example: Div Reviewer), and the status.
In the example image below, the nodes in green have been approved, and they display the first initial and last name of the approver. The outlined node is the one for this approver and shows a status of “Waiting Approval”. The node for OSP has a status of “En Route”.
- Click on the name of the node’s unit to open the Reviewer Details page which lists persons authorized to review for this role. This data comes from ASTRA.
- Click on the “Owner/Preparer” node to display a list of persons who are owners of the eGC1, or have been assigned access to it. Contact the appropriate owner with questions related to the eGC1.
This initial section explains your relationship to this application.
||This approval status is based on you or your role and the current routing status of the eGC1.
|Your action options
||Based on your status with this eGC1, this field displays what actions you may take.
|Reason for your review
||This is the reason(s) you or your organization needs to approve this eGC1.
Approvers (other than the PI) can only approve an eGC1 which is in Routing status. If you do not see the Approve or Return buttons, check the eGC1s status on the My Approvals page. The PI can approve an eGC1 in Composing status by completing it, or in Routing status by using the Approve button.
- Use the Approve button to indicate your approval of this application. You can optionally include a note which will display on the History & Comments page.
- Use the Return button to return the application for modification; the PI and owners will be notified by email of the return, and the email will include your return comments. Comments are required and will display on the History & Comments page.
Use the Add Comment link to include a note, independent of your approval, which will display on the History & Comments page.
Use the Add Approver or Add Watcher link to include an additional approver or watcher in the approval flow. See the Add An Ad Hoc Reviewer article for the steps to do this.
View eGC1 Options
The View eGC1 link opens the application in a new window, in a read-only mode. This allows you to review the details of the application.
The View Attachments link opens a new window and displays a list of all the attachments for this eGC1.
View Printable eGC1
The PDF link opens a new window that displays a printer-friendly copy of the entire application.
This section lists selected fields from the eGC1 to help you confirm that you are viewing the correct item (eGC1 Application Details). The data fields include:
- eGC1 Number
- Full Application Title
- PI Name
- Org Code Receiving Funding
- Sponsor Deadline
- OSP Due Date
- Ready To Submit response