Skip to main content

Stimulus360 One Year Later

It's hard to believe that a year has passed since we created the Stimulus360 solution for Microsoft. When the American Recovery and Revitalization Act (ARRA) passed last year, few could forecast the impact on state and local government. The program was unprecedented in scope and pace, and required state, county, city and federal governments to quickly design and implement systems to track the funding and make information on grants available to citizens.

As it turns out, probably no solution was more widely adopted for ARRA tracking than Microsoft Stimulus360. In its first year, Microsoft Stimulus360 was adopted by over twenty governments across the country, including six states (AZ, CA, IL, MO, MS, WI), cities including DC, San Francisco, and Seattle, and large counties such as Harris County (TX), Los Angeles County (CA), and Cook County (IL). All together, governments using Stimulus360 account for over 100 million of the U.S. population and 2,000 grants worth billions of dollars.

What were the lessons learned?

1. The time has come for hosted solutions in government. We learned a great deal about hosting Dynamics CRM in the past year. Offering a hosted solution saved us and our clients several times. Without the hosting option, it would have been difficult to serve smaller customers, and hosting made it much faster and easier to make changes to Stimulus360.
2. The federal government can move quickly when motivated. The pace of ARRA funding really was impressive, and many of the rules and policies had to be worked out on the fly.
3. Flexibility is paramount, even for complex line of business systems. The Microsoft Dynamics CRM platform in particular helped us respond as reporting requirements were changed by federal agencies.
4. Partnering helps projects in many ways. We were fortunate to find teaming partners across the country to extend our geographic reach and provide complimentary technical skills. Working alone, InfoStrat could not have reached nearly as many customers.

We expect that some of the principles used in ARRA will expand to other government grants, and there is no visible slowing of government transparency efforts.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do