This SAGE update introduces to you easier collaboration with the Office of Sponsored Programs (OSP), more subaward status transparency and a refreshed user interface.
If you are a Subaward Preparer, you are able to:
- Withdraw a subaward request with “In OSP” status
- Cancel a subaward request either “In OSP” or “Withdrawn” status.
OSP can return subaward requests that are “In OSP” or “OSP Assigned” status and will include an return comment so you can revise and resubmit.
For better transparency, a history of changes and comments now displays on your subaward.
You can track the following types of events and comments from the Subaward Overview and within each Subaward Request:
- Status Changes (includes returns with explanations and related comments)
- Ad hoc OSP comments to you about a subaward
- OSP Assignment changes
- Changes to attachments
- Changes to OSP Assignment Date, Issue Date, and Fully Executed Date
The Subaward Overview page allows you to either view a comprehensive list of events for all related subaward requests, or filter to see only those for a particular request.
Ease of Use
Subawards refreshed design makes it easier for you to find the information that matters most.
Two new sections on the Subaward Overview Page:
- Request In Process – This section helps you quickly identify the current request being worked on. This section includes requests that have not reached Active status (i.e. Composing, In OSP, OSP Assigned, Withdrawn, Returned, or Issued).
- Processed Requests – This section includes any requests your items that have been processed for this subaward (i.e. Active, Expired, or Canceled).
You and OSP now share the same interface, which makes it easier for collaboration on subaward development.
My Subawards Task List
The “Latest Request Status” column helps you easily identify the status of requests that are still in process.
Your subaward requests in either “Returned” or “Withdrawn” status also have an arrow icon next to the status to help you identify those requiring action.
Grant Runner: PHS Assignment Request Form
The new PHS Assignment Request Form, introduced with the Forms-D changes, is now available in Grant Runner. This new form will be available to all applications in progress as well as new Grant Runner applications where applicable.
SAGE Budget: Update to Tuition Inflation Rate Default Value
The default tuition inflation rate in SAGE Budget has been changed from 10% to 3%, to provide a more realistic figure and reduce the need for manual overwrites.
FIDS: Suppress annual SFI disclosure overdue email
At the request of the Office of Research, the third and final reminder email sent to investigators that have not submitted an SFI disclosures for 365 days will no longer be sent. This final email cc’ed all related principal investigators which caused confusion/frustration.
Error with Attaching Budgets to an eGC1
An issue was resolved which was causing an error when users were attempting to connect SAGE Budgets to an eGC1 under a certain set of circumstances.
Investigator status reverting to Yes on Connect of Budget
An issue was resolved which was causing the investigator flag on the eGC1 personnel list to revert to YES when a user connected a SAGE Budget to an eGC1.
Personnel role selection changes and investigator flags
An issue is resolved which was occurring when a user changed the role type on personnel from one where Investigator status was automatically defaulted to YES (such as PI or Co-PI), to a role where they should be able to designate YES or NO (such as Mentor). The system was not displaying the YES/NO option in these cases until the screen was refreshed. It will now display the correct investigator options in real time.
Object Code 38 (Unallocated) costs in SAGE Budget not itemized in NIH export
An issue has been resolved so that costs in object code 38 (Unallocated) will now be itemized under Other Direct Costs in the SAGE Budget Excel export that matches the NIH Detailed Budget form format.
The new Subawards section in SAGE marks a change in both business process and system usage.
- All subaward intake actions managed through Ariba
- Subaward intake initiates through SAGE, provides OSP the ability to issue agreements at an earlier stage
- Procurement setup & invoicing for subawards continues to initiate through Ariba
An Outgoing Subaward Workflow Diagram is available for your reference.
New in SAGE: Subawards
For this initial release, the following new capabilities and features are available to campus users through SAGE:
- Create a new subaward request and submit to OSP
- Create a new modification request and submit to OSP
- Search/View subaward requests and current status from My Subawards tasklist
- View a detailed summary of all subaward modification history
- Help documentation available through the “?” icons
Important ASTRA Permissions
Users must have the “SAGE Subaward Preparer” role to create new subaward and modification requests. ASTRA: Who Can Authorize me?
Outgoing Subaward Resources
Over the next few months additional releases will provide other functionality, such as:
- returns and resubmit capability
- visibility to OSP comments and hold details
Based on your feedback, enhancements will be prioritized following this initial release.
A New OAW Compliance Question for Significant Protocol Changes
A new compliance question, AC-1-D, has been added to identify grants that will require a Significant Change at the time of submission. An answer is required if the Animal Use question AC-1 is answered “Yes”.
A few textual enhancements (for existing compliance questions) were made to allow OAW to process the grants more efficiently, and they include:
- Removing the facility name and location of the work to be done on the AC-1-A for UW work
- Requesting the 3-year approval date range
- Updating electronic document submission contact info.
Sub-Object Codes 05-47 and 05-48 Added to Sage Budget for Grandfathered Awards
Effective July 1, 2016, UW’s equipment capitalization threshold will increase from $2,000 to $5,000. This change applies to all competing proposals submitted to sponsors on or after May 1, 2016. The following changes were made in Sage Budget to accommodate this threshold change:
- Two new object codes will be added to (05) Supplies and Materials to allow grandfathered awards to continue to use the old threshold for non-capitalized equipment:
- 05-47 Non-Capitalized Equipment ($2,000-$4,999) – Grandfathered Awards
- 05-48 Non-Capitalized Equipment – M&E Tax Exempt ($2,000-$4,999) – Grandfathered Awards
- These two new object codes will be excluded from F&A calculation when using the following cost bases for budgets associated with grandfathered awards:
- Exclude 05-47 and 05-48 form Total Direct Costs less Equipment & Tuition (TDC less E&T)
- Exclude 05-47 and 05-48 from Modified Total Direct Costs (MTDC)
- The following object code descriptions will be updated as listed below to reflect the new threshold of $5,000:
- 05-40 Non-Capitalized Equipment (less than $5,000)
- 05-41 Non Capitalized Equipment –M&E Tax Exempt ($200 – $4,999)
- The following object code descriptions will be updated as listed below to reflect their INACTIVE status upon 4/1/2016:
- 06-10 Inactive – Computing Equipment ($2,000-$4,999)
- 06-12 Inactive – Computing Equipment – M&E Tax Exempt ($2,000-$4,999)
- 06-90 Inactive – Other Equipment (Non-computing) ($2,000-$4,999)
- 06-92 Inactive – Other Equipment (Non-computing) – M&E Tax Exempt ($2,000-$4,999)
Personnel with an Invalid NetID will not be selectable
With this change, all active staff in the Person Web Service will continue to show in the results on staff search, but those without NETIDs will not be selectable, and users will see a note indicating that the NETID must be established before the person can be selected. Allowing personnel without NETIDs to be selected as personnel caused errors on the personnel list afterward.
Grant Runner Forms-D Implementation
Grants.Gov will be updating its systems to FORMS-D, for all applications submitted for due dates on or after May 25, 2016. The Grant Runner forms that will be updated to comply with FORMS-D requirements are identified below. There may be some application packages which include both a FORMS-C and a FORMS-D as options, and in this case users will be prompted in SAGE to select the appropriate one based on the due date. Per NIH, FORMS-C application packages will be set to expire after the May 7, 2016 AIDS due date.
Update of PHS 398 Cover Page Supplement to Forms-D
For Grants.Gov FORMS-D, users will notice the following changes applied to the Grant Runner Coverage Page Supplement form:
- A new “Vertebrate Animals” section, which includes questions on euthanization and use of AVMA guidelines.
- Removal of the PD/PI section
- Removal of the Disclosure Permission section
- The ability to add Program Income information for 10 budget periods (previously 5)
- Re-ordering of fields to accommodate the new additions and removals
Update of PHS 398 Research Plan to Forms-D
For Grants.Gov FORMS-D, users will notice the following changes applied to the Grant Runner PHS 398 Research Plan form:
- New “Data Safety Monitoring Plan” attachment
- New “Authentication of Key Biological and/or Chemical Resources” attachment
Creation of a New PHS Inclusion Enrollment Form for Forms-D
For Grants.Gov FORMS-D, users will notice a new form called “PHS Inclusion Enrollment Report” in Grant Runner. This single form will replace the 2 separate forms in FORMS-C applications (Cumulative Inclusion and Planned Enrollment Report). With the Forms D changes, users will notice some additional fields to identify the type of reporting being done (“Delayed Onset Study?”, “Enrollment Type?”, “Existing Data Set or Resources?”) When “Delayed Onset Study” is marked YES, the remainder of the form will be disabled, per form rules.
Store activity type code for Grant Runner Applications
In order to aid in the analytics of Grant Runner usage, the SAGE system will begin to retrieve and store the Activity Type code from Grants.Gov, as we are retrieving submission status information.
Error when Inactivating Advances
An issue that was causing users to receive an error when trying to discard advances has been fixed.
eGC1 Permanently Withdrawn status change by user
SAGE users can now permanently withdraw eGC1s that are in “Withdrawn” or “Returned” status. Previously, only OSP could mark eGC1s as “Permanently Withdrawn”. This will provide SAGE users with a way of quickly removing eGC1s from their tasklist that are no longer being considered for submission to a sponsor.
eGC1 Denied by Sponsor status change by user
SAGE users can now mark “Approved” eGC1s as “Denied by Sponsor” and attach related documentation. Previously, only OSP could set eGC1s as “Denied by Sponsor”. This will provide SAGE users with a quick way of clearing eGC1s from their tasklists that are no longer being considered by sponsors, and improve the accuracy of proposal data.
Continue reading »
New Features, Changes and Bug Fixes
- A new multi-select Country field has been added to the eGC1, to track where international work will be performed. This field will be visible to users only when they answer “YES” to the question of whether work will be performed internationally. This country-level data will be used in reporting and analytics.
- The Sponsored Program Activity Type field on the eGC1 and FA was amended to allow users without a mouse to utilize the drop down control with keyboard alone. This change supports making the SAGE application more accessible. The expand/collapse capability in the drop down is also removed, since this was causing some confusion with users. The list of selectable options will be fully expanded, within their respective categories, making for a more intuitive user experience.
- Bug Fix: An issue that was causing eGC1 approval snapshots to not display attachments that had newer versions uploaded after the snapshot was taken has been fixed so that all point-in-time versions of attachments display in approval snapshots.
SAGE Reporting Update
The Subaward Status Report will be located in the BI Portal and will replace the existing static report found on the OSP website. This version will be near real-time (data refreshed nightly), giving campus more timely information on the status of their pending subawards, and will alleviate the time consuming preparation done by OSP in posting the current static report.
Note: This report will be available in the days following the SAGE release.
EHS-2 Compliance Question Update
The EHS-2 question on the Compliance Questions and Explanations pages of the eGC1 has been updated on all new eGC1s created after the September 2015 release.
Updated logic for the display of the HS-1-B Compliance Question Explanation
The HS-1-B question on the Compliance Explanations page of the eGC1 will now display under the additional condition of a Contract that is utilizing Just-In-Time human subjects approval.
Compliance question HS-1-B was not displaying/hiding in real time, when Project Type = Contract
Conditional questions and instructional text in the Human Subjects section of the Compliance Explanations page of the eGC1 now update in real-time when the eGC1 is for a Contract.
Prevent multiple RegIDs for the same person from being entered into SAGE
When a user is erroneously assigned multiple RegIDs at the University, it has caused problems with accessing their FIDS information. A change has been made to disallow multiple RegIDs for the same person in the SAGE database. Upon logging into SAGE, the user will receive an error that is also recorded in the SAGE Suite error log. This error will alert the SAGE team to take the necessary action to resolve the issue with UW IT.
Grant Runner Validation Update on Detailed Budget
A validation was added to the Grant Runner detailed budget form to disallow zero entries in the “other” cost field. This will help mitigate submission errors.
Older FAs in SERA have problems opening
An issue that had prevented Funding Actions that predated the creation of the Authorized Action field from being opened in SERA has been fixed.
Overview: Sponsored Program Activity Revisions
The majority of the July maintenance release is focused on updating the way sponsored program activities are defined and clustered in SAGE on both the eGC1 and on Funding Actions. Prior to these changes, the “Funding Purpose” field on the eGC1 and the “Type of Award” field on the Funding Action tracked different but similar values. This causes confusion for consumers of the data and challenges in reporting to federal sponsors, since neither field aligns cleanly with the categories used for federal reporting.
With the below changes, the eGC1 and FA activity types will be brought into alignment with each other, and with the federal reporting categories. Additional fields are also being added to extend automation of reporting further.
Continue reading »
Grant Runner: Update Detailed Budget Roles to Free Text
On the Grant Runner detailed budget forms (project and subaward budgets) the key persons role type has been converted from a drop-down list to an open text box, to allow users to enter a wider range of other roles not previously listed. For example, users can now enter “Consortium PI” on the subaward budgets, or any other role type necessary.
Grant Runner: Round budget indirect totals to whole number
NIH Guidelines ask for detailed budget figures to be entered as whole dollars. In the indirect cost section of the detailed budget, where the total was automatically calculated based on rates and base amounts, cents were included without allowing users the ability to change the figure to a whole number. With this update, the indirect cost totals on the project and subaward detailed budgets and the modular budget forms will be rounded to the nearest whole dollar.
Provide visibility to missing investigator emails (201633)
In order to ensure attention is drawn to situations where an investigator may not receive a disclosure notification email, due to a missing email address, the PI & Personnel page of the eGC1 is being updated to display available email addresses. The available email address will display for everyone listed on the PI & Personnel page, and when one isn’t available a message of “Email Address Unlisted” will display in its place.
In addition, if a disclosure notification fails to send to an investigator due to no email address being available, then the eGC1 Preparer will be sent an email they can forward to the investigator.
Require Email and Phone Number for eGC1 Preparer (206089)
In order to ensure that eGC1 preparers receive key email notifications generated from SAGE and SPAERC, including the newly added email above which forwards disclosure notifications when investigators cannot be reached by email, the Preparer’s phone number and email address are now required on the eGC1.
PI entry erroneously cleared
Under certain circumstances during the updating of a PI on the eGC1, the entry was not saving correctly, resulting in the PI entry being blanked out and at times causing an error that the user could not resolve. This fix corrects the issue, allowing PI changes to be saved appropriately.
FCOI JIT Email Update
The primary contacts on the eGC1 will now only receive the FCOI JIT email once, rather than anytime the contacts listed on the eGC1 change.
Grant Runner Detailed Budget Implementation
The Grants.Gov RR Detailed Project Budget form will be made available in Grant Runner. This form supports the NIH SF 424 research opportunities where funding greater than $250,000 per period is being requested. With the addition of this form, users will be able to utilize Grant Runner for a much wider range of opportunities, taking advantage of the streamlining and time savings that Grant Runner is known for.
Key Features Include:
- Pre-filled data on the institution, project start and end dates
- Summary view of period totals, with expand capability to view/edit details
- On screen highlighting and messages to assist in identifying and correcting errors that lead to submission problems
- Auto-calculations of sub-totals and totals, with totals refreshing with each new entry
- Easy to read cumulative budget summary section at bottom
- Copy previous period feature (see separate listing for detail)
Continue reading »
Grant Runner Check for Package Errors Page Print Issue
An issue that was causing users to receive an error when attempting to print the Check for Form Package Errors page in Grant Runner has been fixed.
- An issue in FIDS that caused disclosure notifications to be sent to investigators who had already completed a primary eGC1 disclosure has been fixed. Investigators will only receive notifications if they have not already been sent one and if they have not already completed a primary disclosure for that eGC1.
Grant Runner Error Message Corrections
A few minor corrections were needed for some of the validation messages.
- The error message associated with the Congressional District on the Performance Sites form was not fully displayed in the summary of error list at the top of the form.
- A pop-over message was inadvertantly showing when it should not have been for item 10 on the Research Plan form.
- Error messages associated with the attachments for the Other Project Information form were not clearing after the errors were resolved until the form was refreshed.
Grant Runner Read-Only View Display Issue
The income budget periods section of the Cover Page Supplement form was inadvertently being hidden in the read-only view.
Grant Runner Conditional Attachment Issue
On the Grant Runner Research Plan form, when the Application Type changed from Resubmission to New, and the user had already uploaded the Introduction to Application attachment, that attachment was appearing in the submission even though it was no longer required due to the type change. This scenario is unlikely to occur much if at all, but the fix assures that the conditionally-required attachment will not be submitted if the application type changes to one where this attachment is not applicable.
eGC1 Abstract & RFA/RFP Data Required
- On the eGC1 Abstract & RFA/RFP page, the RFA/RFP Number, Funding Announcement Title, and Funding Announcement URL will now be required. For Grant Runner applications, the URL will be defaulted, but users can edit as necessary.
Grant Runner Design Enhancements
Grant Runner Accordions for Section Breaks
Expandable accordions have been implemented, to allow users to see a more streamlined view of the form data. They are primarily used:
- When a section of data is read-only, standard information that the user does not need to pay as much attention to. The SF 424 organization information is an example.
- Where users might want to see a summary view of larger collections of data within a form. Modular Budget, Key Persons Expanded, and Performance Sites forms are examples of forms where summary data is presented in accordions, with ability to expand to view more details.
Wherever accordions are used, users will also see an “expand all/collapse all” link for quick “open/close” of accordions.
For SPAERC views, all accordions will be open by default, per OSP’s request.
Grant Runner Validation Changes
Across the entire Grant Runner form set, validation improvements have been made to add clarity and provide a better user experience. Updates include:
- Required fields with missing data will be highlighted with a red border, for easy identification
- Additional popover help text will display as the user is moving through fields, to guide users with detail of errors or omissions needing to be fixed before completion.
- A “Show Form Errors” feature link was added at the top of each form, to allow users to see all remaining errors on a given form at one time, with the guiding popover help text.
- The “Show Form Errors” feature will also display a summary list at the top of the form of all errors/omissions found.
- Where errors are found within an expandable accordion section, the user will see a red icon (exclamation point) to indicate an error that might at times be hidden from their view.
This release also incorporates more of the NIH-specific requirements that exceed Grants.gov requirements, for a more comprehensive list of errors that are expected to cause problems on submission. Note that there is still work to be done to more fully incorporate NIH requirements, especially those that are activity type-specific. Future releases will be targeted for continued work in NIH requirements and error identification.
On a final note, users will continue to be able to see the entire list of errors across all forms, using the ‘Check for Form Package Errors’ link on the left navigation menu.
Grant Runner Infrastructure Improvements
The Grant Runner section of SAGE has been updated to a more modern infrastructure. This will allow ORIS to more easily maintain and support the forms, and offers opportunities to improve the speed by which new forms can be incorporated into the system. This applies to only those applications using Form Set C.
Grant Runner: Key Person Expanded Update
The Key Persons Expanded form incorporates the new expandable accordion, which allows the user to see a high level summary of the persons included, while expanding to see each person’s full detail.
This form will also now default the zip code (based on the box number) for the PD/PI and for any other persons added through use of the UW Directory “person lookup” feature.
Grant Runner: Modular Budget Updates
The Modular Budget form includes the new accordion feature which displays summary information for each budget period when closed, and exposes full period detail when expanded.
Additional updates to this page include:
- Validation of budget start and end dates against project start and end dates, to alert users when budget periods fall outside of the project period range.
- Validation of period start and end dates to assure they do not overlap with a prior period.
Grant Runner: Other Project Information Updates
The Other Project Information page will now hide from the user’s view any questions that are not applicable, because they are conditioned upon another question’s yes/no answer. This is to reduce confusion over when questions are expected to be answered.
Grant Runner: Performance Site Updates
The Performance Sites form incorporates the new expandable accordion, which allows the user to see a high level summary of the sites included, while expanding to see each site’s full detail. The user will also be provided with better help text for the congressional district field.
Grant Runner: PHS 398 Research Plan Updates
The Introduction to Application attachment (item 1) will only display when the eGC1 Application Type is a Resubmission or Revision. This is to reduce confusion over when the attachment is to be used.
Grant Runner: SF 424 Updates
The SF 424 form incorporates some new design elements to provide a more streamlined user experience.
- Expandable accordions are used to initially hide from view the details of the standard read-only organization information on this form, so that users can more easily focus on the required entry fields.
- Sections are re-ordered slightly, to make for a more intuitive, logical flow.
Additional enhancements/updates to this form include:
- The “Total Federal Funds Requested” field will be defaulted based on the modular budget totals, to keep these numbers in sync
- The “Total Federal and Non-Federal Funds” field will now be auto-calculated
- Added informational text to read-only fields that are editable in the main eGC1 sections (e.g. Application Details, PI information)
- Various UW contact ZIP Codes will now be defaulted, based on the box number provided in the address
- Fixed a bug related to the length of the opportunity title
- Fixed a bug related to CFDA number not displaying
Grant Runner: Wizard Detail Manager Eliminated
User feedback indicated that the Wizard Detail Manager feature of Grant Runner was confusing and an additional burden to users, since the information editable through that section was data the users were accustomed to editing elsewhere for standard eGC1s. This feature will be removed from Grant Runner, and the affected data will be editable in the eGC1 instead.
- Application title, start and end dates, application type, and organization code are editable on the Details page.
- PI Details are editable on the PI and Personnel page.
- Opportunity information is incorporated on the Abstract & RFA/RFP page.
SAGE eGC1s and Approvals Search Enhancements
Users will see a few new search features available to them, on the eGC1 and Approvals task lists.
- Users will now be able to jump more directly to a particular eGC1 from their My eGC1s or My Approvals pages, using a new eGC1 search field located on the task lists.
- Users can now search in My Approvals by personnel name. Search results will include all eGC1s for which they are an approver or watcher, where the chosen person is listed on the PI & Personnel page regardless of role type.
- The PI Name field has been added back to the My eGC1s Advanced Search tool, to allow users to quickly enter all or part of a PI’s name and initiate a search. This feature was removed in January, when the Personnel Search feature was added, but by user request, both fields will now be available for those that like the speed of being able to quickly find eGC1s by PI name.
- When a user performs an Advanced Search from the My eGC1s task list, they will be able to export their search results to Excel.
Addition of University District Building to Location List
- The University District Building has been added to the off campus locations list found on the FG-2 compliance explanations section of the eGC1. It will now be easier for eGC1 Preparers to select that building when projects are eligible for the location designation of “off campus”, and will no longer need to enter the location address.
Suppression of HSD JIT and GIM 19 notifications for ATF and Industry Sponsored Clinical Trail eGC1s
- Human Subjects Just-In-Time email notifications and GIM 19 deadline email notifications will no longer be sent to contacts for eGC1s that are after-the-fact or industry sponsored clinical trials.
Updated handling when a user attempts to remove themself from an eGC1 or Budget
- When a user removes themself from an eGC1 or budget, they will now receive a warning, alerting them that their access to that eGC1 or budget may be affected. When a user removes their last access to an eGC1 or budget, they will now be redirected back to their task list.
- On the eGC1’s Cost Sharing page, a small bug was causing an error when attempting to enter in data into the Third Party Cost Sharing fields for the first time. This has been fixed.
- At times a 99 error would occur when editing an eGC1 where a budget was linked to multiple eGC1s and one of the eGC1s was in Denied or Permanently Withdrawn status. This has been fixed.
Grant Runner Infrastructure Changes for better Supportability
- This Grant Runner release is focused primarily on infrastructure changes that will allow ORIS to better maintain this component of SAGE into the future, and to more rapidly expand the system to include new forms. These changes will be mostly transparent to users, aside from a few minor tweaks to look and feel.
Grant Runner – Disabling of the checkbox for optional forms while editing
- To prevent unintended errors and confusion, the optional forms check box will be disabled (cannot uncheck it) while the user has that form open for editing. This forces the user to close out of the form completely before they can take the action of unchecking the form and thereby removing it from the submission.
Grant Runner – Re-ordering of Mandatory Forms
- With the release of the form C changes, Grant Runner mandatory forms appear in a less-than-ideal order for users. We are bundling into this release the re-ordering of the forms, so that the SF 424 is always the first mandatory form shown.
Additional FG-3 compliance question validation for RRF eGC1s
- eGC1s that have Royalty Research Fund (RRF) as the sponsor will display a validation error if question FG-3, the question about F&A cost reimbursement, on the Compliance Questions page is marked as ‘Yes’. RRF requires FG-3 to always be marked as ‘No’, so this validation error is intended to ensure that the eGC1 preparer selects the correct response prior to completing the eGC1.
Increase character limit in “Reason” field when adding Approvers and Watchers
- The “Provide a reason” field when adding an Approver or Watcher on the Approval Flow Screen has been increased from 250 characters to 1000. Department and School reviewers who add additional Approvers and Watchers like to include detailed instructions in that comment box and needed a higher character limit.
We now will show all recipients on the TO line of SAGE auto-generated email notifications.
- SAGE users will be able to see all persons who received the same Auto-generated SAGE email on the TO: line of the email. This was a frequent request from campus through our help desk and survey responses.
Inadvertent sending of disclosure notifications
- Fixed the system to prevent investigators from receiving disclosure notifications when an old awarded eGC1 is opened. The system will now only trigger disclosure notifications when there is an investigator change made to the eGC1 (addition of an investigator or change of personnel to an investigator role).
HSD JIT email notifications are supressed for RRF eGC1s
- Human Subjects Just-In-Time emails will no longer be sent to the owners of eGC1s where the Royalty Research Fund (RRF) is the sponsor. RRF is an internal UW sponsor and operates differently than external sponsors. Unique characteristics of RRF opportunities include shorter application/review/award timelines and the lack of “fundable score” notifications. These unique characteristics therefore made the Human Subjects JIT email irrelevant and confusing for the owners of the eGC1.
New clarifying message displayed when clicking on Investigator Disclosure History and FIDS Profile is not yet established
- If an Investigator has never completed a disclosure in FIDS, or does not have any disclosure history for the past 12 months, a new user-friendly message stating there is no history will display when the Investigator Disclosure History link is clicked.
New error message displayed when you have attachment upload errors due to hidden or invalid characters in file name
- A new error message will display in SAGE if you attempt to upload eGC1 attachments with invalid characters in the file name. To correct this issue, rename the file on your computer by directly typing in the characters before attempting to upload it in SAGE.
Changes were made to several of the Grant Runner forms with the new Form Set C version.
- Performance Sites: You may now list up to 300 sites.
- PHS398 Checklist: This form will no longer be in the set. Its fields were moved to the PHS398 Cover Page Supplement.
- PHS398 Cover Page Supplement: You may now enter up to 200 stem cell lines. The fields from the Checklist form were moved to this form.
- PHS398 Research Plan: The Planned Enrollment and Cumulative Inclusion Enrollment attachments will become their own new online forms.
- RR Key Person Expanded: You may now add up to 100 key persons.
- RR SF424: There is a new, required field for Change/Corrected applications, “Previous Grants.gov Tracking ID.” The Cover Letter attachment will be moved to this form.
- Cumulative Inclusion Enrollment: This is a new, optional form where you can enter enrollment data directly. This form replaces the corresponding attachment on the Research Plan.
- Planned Enrollment: This is a new, optional online form where you will be able to enter enrollment data directly. This form replaces the corresponding attachment on the Research Plan.
- Cover Letter: The form will no longer appear; its attachment will be added to the RR SF424 form.
Notification dates were added to the PI & Personnel page.
- To help administrators know when to follow up with investigators, the PI & Personnel Page now displays the date when each investigator was notified by SAGE email to create a disclosure for an eGC1 and when the eGC1 reaches the Just in Time (JIT) phase.
- We fixed several bugs related to PI Assurance so that PI Assurance values will be retained and displayed appropriately. We also corrected all of the eGC1s that were affected by the bugs.
In SAGE Budget, we revised how calculations are made for salary distributions.
- In the March 2013 release, we revised salary calculations to include additional earn types. We found a few rare cases where SAGE Budget lists inaccurate salaries when the salary distributions have not yet been entered into the HR database. We have now revised SAGE Budget to account for the distributions which are not in the database.
We updated our tools’ styles.
To ensure that our tools have a more consistent look and are easier to maintain, we made some changes in our code. In some newer browsers, you may notice slightly different colors, rounded corners, and other minor changes. The changes were made in the following tools:
- SAGE – System to Administer Grants Electronically
- FIDS – Financial Interest Disclosure System
- SPAERC – Sponsored Projects Administration & Electronic Research Compliance (for OSP)
- SERA – System for Electronic Research Accounting (for GCA)
SAGE Budget: Preliminary Benefit Rates are now available to users of SAGE Budget.
- GIM 3 has been updated to display both current benefit rates and preliminary benefit rates for future budgeting as they become available.
- SAGE Budget will use the correct rate based on the period start date and whether the user has opted to use current and preliminary rates or current-only rates.
- Budget preparers can use a global update feature to update their budgets quickly when preliminary rates become available each year.
- The period entry page for a given person will indicate whether the rate being used is current or preliminary for that period.
An ASTRA information page will display instead of an error message at sign in.
- When you attempt to log in to SAGE without the required ASTRA role, SAGE will display a list of people in your unit who can authorize access to SAGE. You able to choose an authorizer and send him or her a message to request access to SAGE.
Designated Subcontract Actions (SA) attachments are viewable in SAGE.
- Subcontracts Actions (SA) attachments will now be viewable in the Related Documents section of the Attached Documents page if the SA is in Active or Closed-Out status and if the type of attachment is not a To/From Communication.
EH&S has a new compliance question: “Will the project involve scientific diving?”
- Anyone diving under the University of Washington’s auspices must have current certification as a University of Washington Scientific Diver and adhere to the standards set forth in the UW’s Diving Safety Manual. EH&S will contact you to assist in meeting Diving Safety Program requirements prior to diving.
New Features in SAGE
- SAGE Budget: In the Salaries and Wages section of the Worksheet, additional earn types such as administrative supplements are selected by default, but users may deselect them.
- eGC1: Related disclosures are now displayed in the Compliance Details column in the Personnel section, on the PI & Personnel page.
- eGC1: The Environmental Health and Safety (EH&S) Department revised their compliance questions. The changes were made to reflect regulatory and EH&S program updates.
- The Advance Budget Number Request form signature disclaimer was modified to show new wording.
- The Ready to Submit (RTS) field on the Certify & Route page is now required on all eGC1’s.
- Users will be unable to withdraw the eGC1’s once RTS is answered “Yes” and the eGC1 is at “In OSP” status. They will have to request that OSP return it.
- A new message will display informing users which OSP person is handling their application in case they need to contact OSP for a correction and return of the eGC1.
- On the eGC1’s PI &Personnel Page, FIDS Disclosure Review and FCOI statuses now display in the Compliance Details column.
These changes were made as a result of introducing the new Financial Interest Disclosure System (FIDS) which integrates with SAGE.
On the eGC1 PI & Personnel page:
- eGC1 Preparers can select Investigator status.
- Disclosure notifications to investigators to complete a disclosure in FIDS can now be sent.
- Each investigator’s SFI status will display based on the information in FIDS.
- The PHS FCOI training status will display.
- The FIDS disclosure status will display.
- Changes may be made to the PI or personnel after the eGC1 has been approved by OSP.
- The history of any post-approval PI or personnel changes will be displayed.
On the Certify & Route page:
- An eGC1 cannot be completed until all investigators have received disclosure notifications.
- The Ready to Submit question cannot be answered as “Yes” until all investigators have completed their disclosures in FIDS.
- The Security and Export compliance questions have been revised, and a new one has been added concerning access to classified national security information. Answering “Yes” to the new question will generate a new Security Reviewer approver node on the approval graph.
- The SAGE Budget export now contains data formatted to simplify data entry for the SF424 forms. You will find this information following the usual export data.
- When adding an ad hoc approver or watcher, a new validation checks for any mismatch between the Role chosen and the level of the associated organization code.
- When OSP marks an eGC1 as eligible for an Advance Budget Review, the eGC1 owners will automatically receive an email message.
- When users look up personnel, the results will contain the employee identification number. This will allow users to quickly differentiate between personnel with similar names.
- You may now delete an eGC1 sooner. You must have read/write access, it has been more than six months since the eGC1 has been completed, and the eGC1 is in Withdrawn or Returned status.
- If you create new budget and complete all of the steps until you reach the access page where you add and remove an admin/budget contact, you will see the full budget navigation instead of the wizard.
- Hyphenated names now display properly.
- Advance budget is marked as ineligible when a user copies an older eGC1.
- Budget and eGC1 Preparers, formerly known as Creators, may be updated by anyone with Read/Write access. This allows you control who gets notifications for an eGC1.
- Users can enter or update access information once, and it will display on the centralized access page shared by both an eGC1 and its connected SAGE Budget.
- Users with global edit access for an eGC1 will also have read/write access to the connected budget.
- A validation message will be displayed if a user attempts to add a person a second time on the eGC1 PI and Personnel page.
- All new approval snapshots will be in PDF format; the HTML option has been removed.
- Personnel from older eGC1s who showed up as duplicate owners will now be displayed once.
- The new School of Medicine compliance sub question, HS-1-B, will generate a message to let you know what type of Clinical Research Budget & Billing Support Office (CRBB) review is needed. This question is triggered only for eGC1s which involve the use of human subjects, and will appear once the Project Type and HSD Application type are selected.
- Human Subjects compliance question HS-2 now displays in the SAGE Approval Application Summary when the research involves the use and/or creation of human embryonic stem cells.
- SAGE users will be required to select or specify an organizational code which ends in fewer than four zeros.
- When an eGC1 with any EH&S compliance question answered “yes” is funded, EH&S will be notified.
- Fixed the PAC notifications so that all Pre-Award Budget Contacts, eGC1 Creators, and Administrative Contacts will now receive Post-Award Change (PAC) email notifications.
- The F&A checkbox displays correctly when the F&A rates are customized at the period level in SAGE Budget.
SAGE Budget: When a line item is deleted from the budget worksheet, the page refreshes to reflect the change. However, if a budget has Targets & Limits enabled, the F&A values displayed are not immediately updated. The next time the page is refreshed, the displayed F&A values will be correct, and the Total Project Costs will include the F&A change.
New Budget Features
- Budget period naming conventions have been enhanced to include the most common period names.
- Budgets built in SAGE can now be connected to an eGC1, so that any updates made to the budget automatically display on the budget page of the connected eGC1.
- Budgets in SAGE route with the eGC1 they’re connected to and anybody with access to eGC1 will also have access to the budget.
- The worksheet in SAGE Budget displays the eGC1 number and status of connected eGC1s.
- Fiscally responsible departments can now be specified on the setup screen for sub budgets.
- New Budget Edit Numbers in the Budget History enable users to see when a budget has been revised and to read comments associated with those changes.
- OSP Administrator/Coordinator now has read access to Budgets built in SAGE.
- SAGE saves all changes to budget and assigns a unique Budget Edit number and timestamp to versions created at critical points in workflow, such as at submission or approval.
- Users can access a read-only view of a budget at a specific point in time from the Budget History and copy, print, or export it to Excel.
- Users can access an Excel version of a connected budget from the eGC1 Attachments page under Connected Budget Data.
- Users with the appropriate permissions can view or withdraw the eGC1 and budget from the Budget History tab.
- Ability to define lines that automatically adjust their amounts to make selected total match target amount.
- Ability to enable/disable fixed fee on APL budget
- Ability to see sub-budget information for awards where proposal includes an associated SAGE Budget.
- Added ability to modify Administrative and Pre-Award Budget contacts regardless of eGC1 status
- Budget title field width reduced to better match maximum characters allowed
- Error when opening Targets and Limits auto-adjusting entries with read-only access.
- Cascade non-salary line items when a period is added
- When a user adds TBD personnel to a sub budget, the salary that is created in the setup screen is not transferring to the period set up. The first period starting monthly salary should match the value defined on line setup, instead it is $0.
- Corrected TBD personnel starting monthly salary on sub budget not copying to periods
- Changes to how dates are calculated in SAGE Budget may cause a discrepancy between effort months and period length in a select number of budgets. Each of the affected budgets has a salary line item where the number of effort months originally calculated does not match the number of effort months that the current date calculation produces. This means that the effort months in the budget period now exceed the period length.
- Symptom: When you click through salary details, you will see the following error message when you attempt to tab off the affected period: “Effort Months cannot exceed the number of months in the period (there are currently x months in this period). To increase the effort months, you will need to lengthen the period at the Periods tab.”
- Changing period dates flips academic/summer months on salary lines
- Period months incorrect when period start and end dates are in months of different durations (e.g. 28, 30, 31 days)-Current production issue discovered during Budget 2.2 user acceptance testing. When creating a period that has dates that start/end mid-month in months with a different number of days, the period months on salary lines may be calculated as a whole number where a user may otherwise expect them to be. For example: a period starting on 1/16/2011 and ending on 4/15/2011, period months comes out to 3.0161.
- In a Grant Runner application that has been withdrawn or returned for updates, if an Appendix file is added immediately after updating the Research Strategy file, the Appendix file will appear in the Strategy section.
- The Advanced Search for Approvals has two issues. First, if both the Date Approved After and Before fields are used to set a date range, the system will not return any results. Using just one date fields works correctly. Second, if a very large number (such as an org code) is mistakenly entered in the eGC1 Number field, an error (99) will occur.
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.