Tag Archives: eGC1

You will need to list separately each institution subcontracting with the UW in this section. The object code for subcontracts is 03-62. This is displayed automatically by SAGE. (Do not include subcontract amounts in the 03 totals of the eGC1 Budget section above.)

E G C one subcontracts sectionNames must be unique; if listing more than one subcontract with the same institution, differentiate them (e.g., “UCLA 1”, “UCLA 2”). Calculate and enter the appropriate amounts for each subcontract.

Use the Add Subcontract link to save the current entry and add another row.

Use the Delete link to remove a row.

SAGE calculates and displays the Subcontracts Subtotal amounts based on the entries in the Subcontracts table. You will also see the subtotal of all subcontracts for the first budget period and the total for all budget periods.

See the financial system Object Codes, and GIM 7 Sponsored Program Subaward Administration for more details.

You can enter any other necessary Object Codes not listed in the eGC1 Budget section above or break out items by specific Object/Sub-Object Codes where desired. Common examples include office rent (03-80), in-patient care costs (03-27) and tuition and fees (03-19).

E G C one other object codes section

Enter the proper FAS Object Code or Sub-Object Code and description (see the financial system object codes list for options), and the appropriate amounts for the 1st Period and Total columns. Select Add Object Code to save the entry and add another row.

Use Delete on the far right to remove a row.

Do not list amounts in this section if you have already included them in any of the totals in the eGC1 Budget section above.

Pop-up windows are separate browser windows that open from a single web site. This can occur when the user clicks on a button or link within a web page, or when a web page automatically opens other windows. SAGE uses pop-up windows, for example, on the eGC1 Certify & Route page to display eGC1 errors in a separate window, to display the eGC1 in a printer friendly format, and for displaying other information that needs to be printed. To use these features in SAGE, you must configure your browser

  • to either temporarily disallow or turn off pop-up blocking – or –
  • to allow pop-up windows from SAGE.

Open a new browser window and without navigating anywhere, complete the directions in the Pop-Up Blocker guide for the type of computer and browser that you use.

 

For RRF grant applications, the “Dates Requested” should be given the following standard values:

Fall Round Spring Round
Begin Date January 15 of next year June 15 of the current year
End Date Start date plus one year Start date plus one year
Example Fall Round 2022 Spring Round 2023
Begin: 01/15/2021 Begin: 06/15/2023
End: 01/15/2022 End: 06/15/2024

Please refer to the Instructions for Preparing an RRF Proposal for more details.

The PI Assurance Statement appears on the eGC1 Certify & Route page when the PI is editing the eGC1, as shown in the following image.

e g c 1 P I assurance statement

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.

If this is a multiple PI application, I understand that if I am the eGC1 PI, my approval of the eGC1 indicates I have obtained written assurances from external PIs named in this application that include this Non-UW Multiple PI Assurance Statement.

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.

If the PI approves the eGC1 when it is routing, the Assurance Statement will display in the approval dialog as part of that approval.

Our federal sponsors requested we include an Assurance Statement. Principal Investigators must certify to the truth and accuracy of all sponsor application contents, acknowledge that penalties could apply if wrong-doing is found, and accept responsibility for scientific conduct and submission of project reports for funded projects.

PI approval of this eGC1 and application in SAGE is equivalent to, and may replace, their signature on the sponsor face page.

Application PI

A UW Application PI is added to an eGC1 approval graph when the eGC1 is created. Just like UW PIs, the UW Application PI provides their assurance via approval of an eGC1.

UW Multiple PIs

UW Multiple PIs are added to an eGC1 approval graph when the eGC1 is created. Just like UW PIs, UW Multiple PIs provide their assurance via approval of an eGC1.

Non-UW Application or Multiple PI

The eGC1 PI is responsible for securing and retaining a Multiple PI Assurance Statements from any Non-UW Multiple PIs or Application PI in their local unit files.

Review instructions and the Non-UW Multiple PI Assurance Statement (PDF).

Direct questions related to this statement to your OSP Administrator.

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.

e g c 1 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.

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.

E G C one 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.

This article covers both UW and non-UW Multiple PIs.

UW Multiple PI

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

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.

P I approval with assurance statement

Non-UW Multiple PI

In most cases a non-UW multiple PI will not have a UW NetID. Therefore, the certification will be handled manually following the Non-UW Multiple PI Assurance Statement Instructions described below. Note: the eGC1 PI is responsible for securing and retaining assurance statements for non-UW Multiple PIs in their local files.

If the Non-UW person has an “affiliate” NetID, they can be added to the PI, Personnel, & Organizations page of the application.  SAGE will not include them on the approval graph,  but you could add them to the graph as an ad hoc approver and give them access to SAGE with a non-PI researcher ASTRA role.

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.
  • If you create an Advance Budget Request for the eGC1 (with or without a connected budget), the Advance Preparer(s) and any others assigned access to the Advance will also be listed in the Access section of the eGC1’s page.

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.

Top