Having a group "AOR" is a very useful way to deal with Grants.gov
reporting.  Do those who do this have all delegated AOR's submit under
the name of one of the institutions authorized signing officials? Or
just have one email address for everyone.  You can get emails with a
single email for multiple AORs, but only the submitting AOR can check
on status in the Grants.gov archive. I would like to see a Grants.gov
fix to allow any AOR at an institution have access to status of ALL
applications.  This could be a permission granted by the eBIZPOC when
authorizing a person to be an AOR.

Also, it is the name of the submitting AOR what shows up as the
signing official?  What do you put in the section for the
Institutional Official at the bottom of page 2 of the face page.  If
someone named other than this official submits then there is a
discrepancy between the official named and the person submitting.
Some agencies have objected to this.

A second problem with one group or address for all AORs occurs when an
institution is submitting many applications.  We do 50-100 per month,
not counting corrections.  Our grants officers complained that it was
too difficult to sort out their mail from that of others on the staff.
 This is especially true given the cryptic G.g messages.  I have
asked them to put the application filing name in each message but they
cannot seem to do that.  Thus I created work group "AORs" consisting
of a couple grants officers and their support staff.  Each group has
one log in and one password.  Thus anyone in the group can submit and
check the status of the application.  Moreover, each group gets just
its own messages.  The tricky part is having all applications be from
the institutional official.

If an application has internal approval according to the institution's
own business rules, does it matter who actually "mails" the
application, or in this case pushes the submit button?

Bob Beattie
University of Michigan

Quoting Kellie Dyslin <xxxxxx@WPO.CSO.NIU.EDU>:

> Ditto, and each staffer is responsible for checking and pulling the
> messages related to the proposals they submit. We also do not send
> all of the announcements to the PI, unless they request that we do.
> But we do keep a record of them in the proposal file.
>
>>>> Marta Torruella <xxxxxx@MAIL.ROCKEFELLER.EDU> 7/21/2008 12:13 PM >>>
> What we did early on to avoid such a problem is use a general email address
> for at least one of the AOR email addresses on the SF424.  All the Grants
> Specialists have access to this same email address as well.  This way when
> an email re status of any kind comes from Grants.gov or the Commons we all
> get it.
>
> Marta I. Torruella, CRA
> Associate Director
> Sponsored Research and Program Development
> The Rockefeller University
> 1230 York Avenue, Box 82
> New York, NY 10065
> (Founders Hall, Room 301)
> Tel: 212-327-8175; Fax: 212-327-8400
> xxxxxx@rockefeller.edu
>
>
>
> -----Original Message-----
> From: Research Administration List [mailto:xxxxxx@hrinet.org] On Behalf Of
> Burchell valldejuli
> Sent: Monday, July 21, 2008 10:12 AM
> To: xxxxxx@hrinet.org
> Subject: Re: [RESADM-L] grants.gov auto email notification emails
>
> I bring this up because we had a very unusual situation this past Friday. A
> PI was resubmitting an R01. The original PA was closed so the Program
> Officer at NIDA provided (in writing) a different PA to use. We submitted
> and it threw a FATAL error. Neither the PI nor I knew as we don't get the
> notifications.
>
> This situation is an example of how important it is for AOR/SO to keep on
> top of the grants.gov notifications and communicate with those of us who may
> need to respond.
>
> The good news is that the Program Officer was very apologetic at NIDA's
> error. Provided yet a different PA. We re did the package over the weekend
> and will meet today's 5 pm deadline.
>
>
> ======================================================================
> Instructions on how to use the RESADM-L Mailing List, including
> subscription information and a web-searchable archive, are available
> via our web site at http://www.hrinet.org (click on "Listserv Lists")
> ======================================================================
>
>
> ======================================================================
> Instructions on how to use the RESADM-L Mailing List, including
> subscription information and a web-searchable archive, are available
> via our web site at http://www.hrinet.org (click on "Listserv Lists")
> ======================================================================
>
>
> ======================================================================
>  Instructions on how to use the RESADM-L Mailing List, including
>  subscription information and a web-searchable archive, are available
>  via our web site at http://www.hrinet.org (click on "Listserv Lists")
> ======================================================================
>

======================================================================
 Instructions on how to use the RESADM-L Mailing List, including
 subscription information and a web-searchable archive, are available
 via our web site at http://www.hrinet.org (click on "Listserv Lists")
======================================================================