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.
Once GCA has processed the Advance Budget Number Request, SAGE will notify you by email. This email is sent to the Principal Investigator (PI), the Administrative Contact listed on the advance, and the Administrative and Pre-Award Budget Contacts on the related eGC1.
There are four versions of the email, one for each type of request:
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.
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 Eligibility Tool takes you through a series of questions to assess all compliance areas and determine if you can request an advance budget number. If, based on the answers you provide, the tool determines the eGC1 is eligible, the tool emails the results to OSP. They will then confirm the information provided and remove the eligibility block.
An Advance Budget Number Request is made for a specific eGC1. You must be an owner of the eGC1, or have either Read/Write or Read-Only access, to create an advance. The owners of an eGC1 are the PI, Administrative Contact, Pre-Award Budget Contact, eGC1 Preparer, and Budget Preparer (if the eGC1 has a linked budget).
If your only access to an eGC1 is through the Global Edit ASTRA role, then you need to add yourself to the eGC1 first. Open the eGC1 (from the Approvals tab) and use the Contacts & Access page to assign yourself direct access (or change the preparer or a contact, if appropriate). You can then create an advance.
The steps to do this are:
Find and open the eGC1 on the Approvals tab
Go to the Contacts & Assign Access page
Click the Add Another User link in the Access section
Proof of commitment on the part of the Sponsor. For example, a subaward commitment letter or a federal or state sponsor’s fundable score.
An agreed amount of money to request as advance funding.
A time period for the Advance Budget Number. You can request an Advance Budget for no more than 6 months.
A designated contact person and box number for questions and communications from GCA.
The number of the associated eGC1.
The signature of the Chair or Dean of your department, guaranteeing all advance funding.
The PI or Department Administrator is responsible for monitoring advance budget expenditures. They must notify GCA within 10 working days prior to the end date of the advance budget if the award is still pending. In this situation, you have the option to request:
A Supplement to increase the amount of funding available on the existing Advance Budget.
An Extension to extend the availability of an existing Advance Budget Number for an additional three months. Note: An Advance Budget cannot exceed a total of 12 months.
The process for requesting a renewal, supplement, or extension is similar to requesting a new Advance. In addition to the standard information, however, you will also need to know your Advance Budget Number.
The department chair or dean must ensure the research team meets all compliance requirements for all expenditures made on an Advance Budget Number, per GIM 9 Advance Budget Numbers.
Once OSP marks the application as eligible for an advance, the system sends an email notification to the research team. The email is sent to the PI, Administrative Contact, Pre-Award Budget Contact, and eGC1 Preparer.
The email subject is “Advance Budget Request Eligibility” and the text of the message is “Your eGC1 A[number] is now eligible for an advance budget request. Please log into SAGE when you are ready to create the advance budget request.”