Tag Archives: eGC1

Enter any information that will be helpful to campus and OSP reviewers. This may include special sponsor requirements, exceptional situations or other information that will assist reviewers in understanding your application.

additional information section

Note: On the Application Summary page and in SPAERC (OSP’s view of SAGE data), the Additional Information field (which appears on the eGC1’s Certify & Route page) is referred to as eGC1 Comments.

This section displays the grand total of all UW personnel and non-personnel cost sharing amounts for each UW unit (by organization code). The total does not include Third Party amounts.

For each unit the system displays the Organization Code, Organization Code Name, and Amount.

U W Summary by Unit section

Sometimes the University’s Facilities & Administration (F&A or indirect cost) rate is higher than the rate agreed to on an award. As a result, the University is awarded F&A Costs at lower than the negotiated rate. In this situation, the University ends up with a shortfall called “unrecovered F&A costs.” Some sponsors allow this shortfall to be applied as a cost share contribution.

If you are entering unrecovered F&A costs as cost sharing, you must complete the eGC1 Cost Sharing Addendum form. On the addendum, be sure to indicate the source of cost sharing as “unrecovered F&A costs.”

You may use Unrecovered F&A costs as a source of cost sharing if the sponsor guidelines indicate that “unrecovered F&A costs” are a valid cost sharing contribution or if prior sponsor approval is obtained. See the GCA Unrecovered Indirect Cost Page for more information.

Enter the unrecovered F&A cost amount.

unrecovered f and a costs section

UW Abstract

The eGC1 abstract should express the purpose and essence of the proposed activity in language understandable to non-specialists. Those charged with explaining the University’s research programs to the public and the state government, including the Board of Regents and the Office of News and Information, rely heavily upon the abstract. For this reason, the abstract entered on the eGC1 should be less technical than the abstract on the application submitted to the sponsor. The importance of preparing it carefully cannot be overemphasized.

The abstract field does not have a word limit.

abstract and r f a / r f p

Request for Application/Proposal or Program Announcement

For a standard eGC1, you must complete all of these fields. If a particular field is not applicable to your proposal, enter some text, such as N/A, to indicate that.

For Grant Runner applications, these fields, and the ones described below with be auto-populated with data based on the opportunity you selected.

Field Description
RFA/RFP/PA Number Enter the Request for Application (RFA), Request for Proposal (RFP), or Program Announcement (PA) number provided by the sponsor.

For Grant Runner applications, this information will be pre-populated and read-only.

Funding Announcement Title Enter the title of the funding announcement.

For Grant Runner applications, this information will be pre-populated and read-only.

Funding Announcement URL Enter the web address (URL) if the sponsor has specific information about this funding announcement on its web site.

For Grant Runner applications, this information will be pre-populated and will be editable.

Additional Fields for Grant Runner Applications Only

additional fields for grant runner application

Field Description
Competition ID The form set used for this opportunity; this information will be pre-populated and read-only.
Opening Date, Closing Date The dates for the funding opportunity selected; this information will be pre-populated and read-only.
Activity Code The Activity Code for the funding opportunity selected; this information will be pre-populated and read-only.

You may only use the Multiple PI role when specifically allowed or required by the sponsor instructions. For additional information on research team roles, review the UW Research Personnel page.

When including one or more Multiple PIs,

  • Identify the UW Contact PI as the “Principal Investigator” on the eGC1
  • List all multiple PIs on the Personnel page of the eGC1 and choose “Multiple PI” from the drop down list

If the Multiple PI is a UW person, SAGE will add the Multiple PI to the Approval Flow and send an “approval required” email notification at the appropriate time. If the person selected does not already have an ASTRA role for SAGE,  a warning message of “no access: ASTRA permissions required” will display in red once you select the Multiple PI role. You will need to give them access, so that they can approve the application.  There are two non-PI researcher ASTRA roles that could be used.

As part of the approval process, the UW Multiple PIs are required to certify the PI Assurance Statement. The image below shows the assurance statement in the approval dialog.

The statement reads:

Principal Investigator/Program Director Assurance: I certify that the statements in this eGC1 and the related sponsor application are true, complete and accurate to the best of my knowledge. I am aware that any false, fictitious, or fraudulent statements or claims may subject me to criminal, civil, or administrative penalties. I agree to accept responsibility for the scientific conduct of the project and to provide the required progress reports if a grant is awarded as a result of this application.

The approval/agreement reads:

I am the PI and I have read and agree with the PI Assurance Statement. I understand that approving this eGC1 electronically is equivalent to my signature.

example of approval box with p i assurance statement

If the Multiple PI is a non-UW person, SAGE will not add them to the approval graph. Since they have a NetID, they could be given access to SAGE and added as an ad hoc approver to the graph. The eGC1 PI is responsible for securing and retaining assurance statements for non-UW Multiple PIs in their local files.

Non-UW Multiple PI Assurance Statement Instructions

The following steps describe the paper process.

Access permissions govern what a user may see and do with a specific eGC1 (and connected budget) in SAGE.

The eGC1 Preparer, Principal Investigator (PI), Administrative Contact, and Pre-Award Budget Contact are automatically Owners of the eGC1. When you link an eGC1 and Budget, the Budget Preparer also becomes an owner of the eGC1.

Any owner, any user with Read/Write permission, or any user with the Global Edit ASTRA role for the appropriate organization codes may give Read-Only or Read/Write access to other SAGE users.

Different permission types have different access rights.

Owner Read/Write Read-Only Global Editor Approver Watcher
View Contents Yes Yes Yes Yes Yes Yes
Edit Contents Yes Yes Yes *
Assign Access Yes Yes Yes *
Delete Yes
Complete Yes Yes
Withdraw /
Re-Complete
Yes Yes Yes *
Return Yes
Add Reviewer or Watcher Yes Yes ** Yes
Add Comment Yes Yes ** Yes Yes

 

* Note: a Global Editor can edit or withdraw an eGC1 only if the editor’s span of control matches the org code of an approving unit. Global Editors access eGC1s from the My Approvals tab. Note that you cannot see eGC1s in Composing status on the My Approvals tab.

** A Global Editor cannot add reviews, watchers, or comments even if she has Read/Write assigned access to the eGC1.

To create an Advance Budget Number Request for an eGC1, you must be an owner or have been assigned access – either Read/Write or Read-Only. For Global Editors, this means you must open the eGC1 from the Approvals tab and assign yourself access (or change one of the contacts, if appropriate). Then you can create an Advance.