Skip to main content

6 Things to Look for in Grant Management Software

Source:USASpending.gov

My company InfoStrat has been working on government grant management since 1998, and we have seen and responded to a number of solicitations for grant management software.  This post summarizes what grantors are looking for in a software package, highlighting some recent trends that have emerged in this market.

Here are the top characteristics desired in a grant management software package:
  1. Compatibility with the enterprise architecture of the customer.  Most customers prefer to buy software that is compatible with what they already own in order to simplify support.  We see RFPs that specify the database, for instance, as Microsoft SQL Server or Oracle to be compatible with reporting tools already in use.
  2. Flexibility to meet grant program requirements and respond to changes in requirements. There is no such thing as one-size-fits-all for grants.  A highway grant from the Department of Transportation is quite different from a neighborhood protection grant from a local police department.  Customers want the product to match their process rather than to change their business process to fit the product.  Specific grant programs and even federal guidelines for all grants are evolving.  Customers know that they may need to incorporate new data elements and create new reports to remain in compliance.  The most dramatic instance of this was in the American Recovery and Reinvestment Act of 2009 (ARRA), also know as the Stimulus, which created new metrics and reporting standards for grants.  In 2014, OMB announced uniform guidance which included accounting, audit, and administrative policies. 
  3. Ability to run on a government cloud.  This is a recent trend but has been picking up momentum.  Customers are asking for products which meet federal and other security certifications such as NIST and FedRAMP. 
  4. Integration with a grantee portal. Customers want to allow prospective grantees to research their grants online and submit their applications, view the status of applications, and submit post-award reports through a web portal.  They do not want to rely on custom coding of the portal but prefer web services to connect the portal with the grant system and allow content changes through configuration rather than custom HTML.
  5. Integration features and capabilities. Grant systems do not operate in a vacuum, so customers want the ability to link to an accounting system to issue payment requests and track payment status.  They also are seeking integration with other products such as Microsoft Office, email systems, and document management systems. 
  6. Vendor stability. The grant software marketplace has been fragmented, and some companies have written products for a specific type of grant.  Customers are concerned about the viability of small companies because of their narrow market and the chance of acquisition and discontinuation of the product as the industry consolidates. Government agencies do not tend to favor startups because they are less likely to be around for the full life of the product. This preference points toward software vendors that lead the industry and have demonstrated longevity. 

Popular posts from this blog

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Dynamics 365 for Government Contractors (GovCon) Frequently Asked Questions (FAQ)

One of InfoStrat's most popular solutions is Dynamics 365 for Government Contractors (GovCon).



Here are some answers to frequently asked question on this solution:
Can I add new fields to the solution?  -- Yes, the solution is fully customizable and you can add your own new fields to any form, view or report.Does Dynamics 365 for GovCon work on mobile devices?  -- Yes, Microsoft offers mobile apps for all the most popular platforms including iPhone, iPad, and Android phone and tablets.Does Dynamics 365 connect with bid data systems such as Deltek and Onvia?  -- Some information services, such as Onvia, offer integration with Dynamics 365.  Others require third party solutions such as the InfoStrat integration with Deltek GovWin IQ.What do customers typically customize for their unique requirements? -- Not all contractors follow the same steps in the capture process.  Most clients will tailor the business process to add or remove steps in order to match their sales methodology.  Of…

Getting the Most from Dynamics CRM Online -- Synchronous v Asynchronous Workflows

This video shows highlights from the InfoStrat March 2015 seminar "Getting the Most Out of Dynamics CRM Online" presented by Dmitri Riz, the leader of the InfoStrat Dynamics CRM practice.  This is the second part of a series of blog posts.  The first is Benefits and Cloud Thinking.



In order to make your CRM workflows perform best, you need to understand the difference between synchronous and asynchronous workflows so you can choose which is appropriate for your applications.



Synchronous workflows are a new feature that was introduced in Dynamics CRM 2013.  Unlike asynchronous workflows which are sent to a queue, synchronous workflows execute in a single transaction. 

This means you can eliminate the need for many plug-ins which were created for previous versions of Dynamics CRM.

You may want to disable synchronous workflows during import operations, because they will could be triggered by each new record and significantly slow down the import process.