Initiatives/Futures

April 11, 2008

Moving toward a National Web-based Grants System

In late March, NIH issued a Sources Sought Notice (SSN) looking for info on a Web-based solution capable of handling electronic submission proposals for the complex mechanisms.  These are funding mechanisms such as Program Projects which have not been converted to PureEdge or Adobe and are still submitted on paper using the PHS398 forms.

Cayuse responded enthusiastically to the SSN this week because it is aligned perfectly with what we do: eliminate paper and downloadable forms from the grants process. 

My humble personal opinion is that the PDF-based approach is an interim solution.  People collaborate and do business on the Web, and the Web is the way Grants.gov has to go. It's also how Cayuse424 works today, by the way. I'm happy to see NIH taking a serious look at leveraging this technology more fully.

April 09, 2008

Subawards.com is here!

We launched Subawards.com on Wednesday, April 9. This is a 100% Web-based approach to creating subcontract budgets for federal grant applications. We've designed this first release to benefit primarily the existing Cayuse424 community, but we have larger ambitions.

The federal grant community needs a Web-based work environment for the preparation and submission of grant proposals. Subawards.com provides a free, powerful, flexible way to do one part of the process: collaborate on budget proposals. Check it out.

February 22, 2008

A Good Idea in Oregon

An Oregon-wide research initiative is gaining traction, as reported in the Portland Business Journal.

An ambitious education plan that could turn Portland into a research and development powerhouse is likely to cost hundreds of millions of dollars.

Cayuse intends to support this effort by making our Web-based software broadly available within Oregon. Our solution offers a competitive advantage to any organization that applies for federal research funds. We want to see that advantage work for us here in our home state. We're in talks with some key players, and expect to have more news about this soon.

January 29, 2008

Government ponders Software as a Service (SaaS)

The government is evolving its approach and understanding of the best ways to provide services to its customers, both internal and external. In this recent FCW article, The Office of Management and Budget mentions SaaS as one option the government considers, and makes note that SaaS is gaining widespread commercial acceptance. Cayuse took the Web-based SaaS approach from the outset of designing our proposal platform.

The move to focus on services also includes using software-as-a-service providers, Evans added. Software as a service is a concept that focuses on a private-sector vendor providing a platform and application that many different companies or agencies use. The application can be modified to meet their needs, but the platform remains the same. Users also can buy it through a subscription or by a per-use model.


 

August 30, 2007

FFATA Up-date

By Bob Beattie

I was hoping to get an update on Dave's FFATA questions of July 5, 2007, so I asked these follow up questions on the Grants.gov S2S listserv.

  • What are the changes to the formsets required by FFATA??
  • What will be the timing of these changes?

As a reminder of what the law requires, a web site where OMB is seeking input on the process mentions the following items:

  1. the name of the entity receiving the award;
  2. the amount of the award;
  3. information on the award including transaction type, funding agency, title, etc;
  4. the location of the entity receiving the award;
  5. a unique identifier of the entity receiving the award.

The full text of the law gives more detail.

In response to my questions, the NSF representative to the SF 424 Forms Families & FFATA Implementation Subcommittee gave a very nice update of what forms changes would be needed. Luckily, most of these are already contained in the SF424R&R and it is the SF424 family that would get the most changes.

  • DUNS - Required;
  • Parish (this would be a global change everywhere that "County" appears in a SF 424 forms family);
  • Project/Performance Site Congressional Districts;
  • Areas Affected by Project (Continuation from SF 424 Cover Page);
  • Congressional Districts of Areas Impacted by the Program/Project (Continuation from SF 424 Cover Page)

Can we assume that the DUNS number can just be take from the application itself? Since this part of the law, and thus the database, is not concerned with sub-awards we should assume that there is only 1 DUNS number -- that of the recipient organization. "Parish" might just be added to the field now called "County" and that field becomes a required one. The Project Performance Site Congressional District(s) are also on the SF424.

The field "Areas Affected by Project" is currently ill defined. The NIH Guide on the SF424R&R says this:  "List only the largest political entities affected by the project (for example, state, counties, cities)."

Is this supposed to mean the TYPE of entity, or the NAME of the entity? As far as the FFATA requirements are concerned, why does the type of entity matter? Moreover, the law does not require name(s) of the places affected by the project. Rather the law requires "the location of the entity receiving the award and the primary location of performance under the award, including the city, State, congressional district, and country."

There can be quite a substantial difference between the place of performance and the places affected by a project. This same logic can be applied to the data element "Congressional Districts of Areas Impacted by the Program/Project."  The law is not asking for this. The law seeks to help people understand where grant and contract money goes, not where it has impact. Where the project money goes is easy to determine, where the project has impact is not so easy to identify, especially for research projects.

Moreover, the crucial problem I see with the approach of the SF 424 Forms Families & FFATA Implementation Subcommittee is that it is seeking to obtain the required information at the proposal stage. Many more proposals are submitted than are accepted. There are often changes between what is proposed and what is eventually funded. I would suggest that any new data needed for the FFATA be collected at the award stage, not at the proposal stage.

In summary, leave the Grants.gov forms alone. Let the System-to-System developers keep working with what they have now. There will be a Federal Register call for comments on all of this soon (look to a future blog entry with the URL). I urge people to consider all the work that will be needed for both data not required by the law and changing the forms. I suggest that people comment that the process of FFATA compliance should be relegated to the award stage in the grants management process.

July 06, 2007

FFATA details mean changes ahead

Those of you who witnessed the June 19th FFATA webcast hosted at HUD may be interested in what this means for the applicant community. (Sadly this good presentation was marred by the lack of call-in participation due to technical difficulties. You can give your feedback here.)

This is how FFATA works in the simple: the Federal agencies will connect their back office systems to a big public searchable database starting this year. This means that all of the information will be coming from agency systems. Some information, however, will originate with your applications to Grants.gov. Here is a link to what OMB wants to see in this database.

We emailed in our questions during the presentation, which were answered promptly during the meeting:

    To comply with FFATA:

    Will there be changes to the SF-424RR formset? If so, when?

    Will there be changes to the SF-424 formset? If so, when?

The answers were, yes, we don’t know, yes, we don’t know, respectively. For the applicant community this means that the base forms will change. These changes have a wide variety of implications for the System-to-System developer community, as we will need to release changes to the software to accommodate the new forms (what S2Sers would describe as “new XML schema” as for the SF-424RR.)

Finally, there continues to be the ongoing conflicts of schedule between the freeze of forms changes caused by the changeover to Adobe and the mandatory changes to the forms caused by FFATA this year. Not quite a perfect storm…