Tag Archives: eGC1

March 2011 SAGE Maintenance Release

The UW Box Number is Now a Required Field

When a user chooses the Organization Code Receiving Funding, the UW Box Number will be automatically populated. Users can still edit the field as needed.

0

This section displays the total cost sharing from all UW sources (personnel and non-personnel), third party sources and Unrecovered Facilities & Administration (F&A) costs. This amount is automatically calculated by SAGE.

Total Cost Sharing section

0

Cost sharing occurs when the research grant does not pay for all allowable expenses (personnel, tuition, equipment or services). For detailed information on cost sharing, see the GCA Cost Sharing Page or  GIM 21 Cost Share on Sponsored Programs.

When applicable, the PI or department must complete and submit the eGC1 Cost Sharing Addendum to OSP at the time of award. If OSP has not received this form before they send the Funding Action to GCA, then GCA will set up the account with restricted 02 status. GCA will block any related advance budget requests.

0

The Total Costs (Direct + F&A) are calculated and displayed automatically by SAGE for the 1st Period and Total (All Periods).

total project costs section

2

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.)

Subcontracts section

Names 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.

1

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).

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.

1

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 disable 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.

 

0

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 2019 Spring Round 2020
Begin: 01/15/2018 Begin: 06/15/2020
End: 01/15/2019 End: 06/15/2021

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

0

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

certify and route page assurance statement for the principal investigator

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.