Home

Tag Archives: Application

Campus needs to use a sponsor that’s not listed. What steps need to be taken?

When a user searches for a sponsor to add to their eGC1, the following text always displays. It includes the steps the user should follow.

Not finding the sponsor you are looking for?

We recommend you try your search again using single words, abbreviations, or alternate spellings. A partial search term such as “American” or “Americ” will return all sponsors whose names contain that term. You can also search on common acronyms, such as “NIH.”

If you cannot find the sponsor you are looking for, please follow the Sponsor Request Instructions below:

Sponsor Request Instructions

    1. Select “Request Sponsor.”
    2. Navigate to the Sponsor Request form in a separate browser tab.
    3. Fill in the form, and then select “Submit.”
    4. Leave the Sponsor blank until the new sponsor is added in order to route your eGC1.

You will receive an email confirming the new sponsor is now available. Return to your eGC1, search again for that sponsor and select it.

The Request Sponsor button displays below the instructions.

Place an Application or Action on Hold

You can add holds to Applications, Funding Actions, or any type of Admin Action. You can also modify or remove existing holds whether added manually or automatically by the system.

There are two categories of hold reasons: Non-Compliance and Compliance.

Non-Compliance hold reasons are:

  • For Check
  • Other (Campus)
  • Other (Sponsor)
  • Pending Fully Executed Agreement
  • Pending Notice to Process/Activation Notice
  • PI Signature
  • Revised Budget

Compliance hold reasons are:

  • Administrative Support
  • Cost Share
  • Export Control
  • F&A
  • Federal Flow-Through
  • IACUC Approval
  • IRB Approval
  • SFI/FCOI
  • PHS Training

Automatic Holds

  • Applications: If there is an Export Control watcher on the approval flow, when the application reaches In OSP status, the system will automatically add an Export Control compliance hold. Manually added holds on Applications do not enforce any process rules.
  • Actions: The system will automatically place some compliance holds on Funding Actions and Post-Award Changes. See the section on Automatic Holds for further details.

Add a Hold

  1. On the left navigation menu, select Add/Modify Hold
  2. In the dialog window that opens, check one or more hold reason boxes. The dialog window is shown in the following image for a Funding Action.

add or modify holds

    1. Enter any optional OSP notes about the holds
    2. Click Save to complete the process.

Note: When you open the Add/Modify Hold dialog window after the first time, you will see an expandable bar below the list of holds titled “Previous OSP Note Hold Reason Comments.” Click on the bar to expand the section.  A table displays that shows the date entered, the comment, and who the comment was entered by. The same information also displays under the OSP Notes tab. Clicking the bar again will hide the table. This section is shown expanded in the above image.

A yellow “On Hold” banner will display at the top of the item’s details page. The following image shows the banner on a Funding Action.

on hold banner

Modify or Remove a Hold

  1.  Select Add/Modify Hold to open the dialog window
  2. Adjust the selected hold reasons
  3. Add an optional comment
  4. Click Save

If you clear all of the check boxes, the item will no longer be on hold and the banner and tasklist icons will no longer display.

December 2015 Maintenance Release

December 15, 2015

New Features

Allow deletion of subcontract actions beyond most recent

OSP can now delete any Subcontract Action, not just the most recent, as long as the Subcontract Action is in “Pending” status.

Provide OSP staff with ability to alter eGC1 status

All OSP staff now have the ability to reset eGC1s that had been accidentally set to “Approved”, “Denied by Sponsor”, or “Permanently Withdrawn” back to active statuses. Approved eGC1s can be reset to “In OSP” status, and “Denied” can be reset to “Approved”.  If an eGC1 reached “In OSP” or “Approved” status prior to being “Permanently Withdrawn”, then OSP can reset it back to either of those statuses.  eGC1s that are “Permanently Withdrawn” while in “Routing” status cannot be reset to an active status, but can still be copied.

eGC1 Assignment Rules

Assignment Factors

When a SAGE user completes an eGC1 for the first time and moves it into Routing status, the system assigns the eGC1 to a group/team and to a person who is the Administrator or GCC. There are a number of factors that contribute to the assignment.

Organization Code Receiving Funding: OSP uses the List/Edit OSP Administrators admin tool to associate organization codes with specific groups/teams within OSP.

  • Roll-Up of Organization Codes: When a SAGE user completes an eGC1 with an organization code receiving funding that has no group association, SPAERC steps up the organization code hierarchy to find a higher-level code that does have an associated group. Then, based on the logic below, the system assigns the eGC1 to a member of that group.
    • For example, a sub-division level code with no group, will roll up to the division level; a division level code with no group will roll up to the department level. See IT Connect’s page on Organization Codes for details on levels.
  • Failover: If the system cannot find a group for the eGC1’s organization code or its roll up codes, then the assignment is to the Failover Team. That team can reassign the eGC1 to the appropriate group, and add the organization code to the correct group via the admin tool.

Re-Completed eGC1s: When a campus user re-completes a withdrawn or returned eGC1, the system may change the group/team assignment in response to changes made in the eGC1. However, the system does not update the original person assigned (with the one exception being if the sponsor changes from, or to, RRF). This ensures that the recompleted eGC1 returns to the same OSP staff person for follow-up, rather than disappearing from that person’s tasklist due to an automatic reassignment. If the changes warrant assigning the eGC1 to another OSP person, you can manually reassign it (see Reassign an Item). Note: Manual reassignments only change the person, not the group. The only time a group changes is in response to changed data on a withdrawn or returned eGC1, upon re-completion.

Assignment Logic

The following set of rules determine the eGC1’s initial assignment to the group/team and person.

Conditions Assignment
RRF

Primary sponsor is the Royalty Research Fund

 RRF reviewers
NSF

Primary sponsor is the NSF (National Science Foundation)

 GCC (Grant & Contract Coordinator) role for the org code receiving funding
IPA/JPA

Sponsored Program Activity Type = IPA/JPA/Staff Assignment

 GCC (Grant & Contract Coordinator) role for the org code receiving funding
Clinical Trials

  • Sponsored Program Activity Type = Clinical Trial – Non-Federal Sponsors
  • And Sponsor Type is Private Industry or Foreign Private Industry
 Contracts Intake (Team C Administrator)
Certain federal primary sponsors where:

  • Application Type is either a Non-Competing Renewal or a Non-Competing Supplement
  • And the total amount requested is $2 million or less
  • And the primary sponsor or parent sponsor is DoED, DHHS, or ONR
 GCC (Grant & Contract Coordinator) for the org code receiving funding
Non-Award Agreements

Application Type = Non-Award Agreement (new) or  Non-award Agreement (continuation)

 Contracts Intake (Team C Administrator)
After-the-Fact

  • Sponsor Type = Private Industry or Foreign Private Industry
  • And After the Fact = Yes
 Contracts Intake (Team C Administrator)
All other conditions Administrator role for the org code receiving funding

May 2013

May 5, 2013

  • OSP Notes for returning an item to GCA will be a required field.
  • A new date can be added to the tasklist called assigned to date. This will allow you to track when new items are added to your list.
  • Only users with the Subcontracts Role will be able to create a subcontract shell. General users will no longer be able to add a subcontract shell within an FA.
  • Subcontracts formerly assigned to Verenice Bendana (Barbosa) and Judy Yoshioka will be moved to e-shelf.
  • One additional question has been added to the eGC1 Security Compliance Questions. Approval workflow was added for Security Review when the preparer answers “Yes” to the new question. An automatic hold will apply when the preparer answers “Yes” to any of the Security questions. The new workflow process will apply to only newly created eGC1s at the time of release.
  • Budget number and prior budget number field validation has been placed to allow only numeric and dash in these fields.
  • Advance Budget Request will always be blocked until OSP allows the Advance Budget Request to go through. GIM updates, process updates and procedures are still being vetted.

Planned Bug Fixes:

  • The error message color block for Subcontracts page validation will be corrected to fully cover all the error text in color.
  • Status Checker will no longer display HTML code.
  • Pending Sponsor and Pending Flow Through Sponsor will not be allowed on approval of Applications or FA’s.