Follow the Five Patterns of Business to a Successful GIS

Deploying solutions to support all five patterns insures that your organization will get the maximum ROI from your GIS.
[Note:  This is latest post in our series about Managing GIS.]
If you have been following the development of the ArcGIS platform, you may already be familiar with the “five patterns of business.”  They are:

These five patterns are common to all organizations.  If you are an ArcGIS platform user, then it is important that you understand these patterns, because they are driving the development of the platform.  Because these five patterns are common to all organizations, and Esri can provide a location platform that supports all of them, any organization can get the benefits of GIS in just about everything they do.
The ArcGIS platform is designed to support all of these patterns.  If you own the platform (ArcGIS for Desktop, ArcGIS for Server, ArcGIS Online), then in order to get the maximum return on investment (ROI), you should deploy solutions to support all five of the patterns.  (For more on ArcGIS as a platform, see this companion blog post in our Managing GIS series.)

The “five patterns of business” are common to all organizations, and the ArcGIS platform supports them all.
An interesting observation is that as you move from left to right across the different patterns shown above, the potential ROI increases while the software cost per user decreases.  This means there is more potential ROI in the three patterns on the right side, so you should be prioritizing your work there.
Let’s review each of the patterns briefly.

An Example of a Five Pattern Solution

In order to make the vision of a sustainable, complete, and integrated GIS across the enterprise a reality, it is critical to be proactive in implementing the established vision.  (For more about this, see this companion blog post in our Managing GIS series.)
It is important to constantly look for opportunities to implement solutions across all five patterns during daily operations.  An example of this would be if someone requested a map of the community showing all of the foreclosures.  Under normal circumstances, that map would be made and delivered to the customer and that may be the end of the involvement of GIS with that project.  In that example, the GIS solution has stopped with the Data Management pattern.
A better alternative would be to inquire why the map is needed, in order to try to discover the business need behind the request.  This may lead to additional opportunities for implementing GIS solutions across all of the five patterns.
For instance, under the Planning & Analysis pattern, the foreclosure information could be analyzed to see if there are concentrations of foreclosures, or a correlation between foreclosure locations and the locations of crime and/or code violations.  The foreclosure locations may also be negatively affecting property values in the surrounding areas.  This additional intelligence can really help make a difference in the community on multiple levels and help make better decisions.
For the Field Mobility pattern, the foreclosure information could be very useful for code and law enforcement officers in the field.  If code enforcement officers knew which homes on a block were foreclosures, they could slow down to see if there are any code violations.  If law enforcement officers knew which homes on a block are foreclosures, they could slow down to see if there are any criminal activities going on.  This access to critical data in the field can increase efficiency and level of service as well as allow for more proactive actions.
For the Operational Awareness pattern, providing direct access to the data via an easy-to-use web interface helps maximize the value and associated benefits.  City staff could query, select, analyze, and print the data to help them answer questions, solve problems, and support collaboration.
For the Constituent Engagement pattern, if the data was made accessible to the public, it could also create value.  If citizens in a neighborhood knew where the foreclosures in their neighborhood were located, they could help keep an eye on them as part of their neighborhood watch program.  They may even help keep up the properties to insure their property values are not negatively affected.  Homeowner associations would know who to contact regarding payments of dues and violations of deed restrictions.  The real estate industry could also find value in direct and easy access to foreclosure data in a spatial context.  Solutions like this help reinforce transparency and accountability and increase efficiency and level of service.  A mobile solution could be implemented that allows citizens to verify/falsify foreclosures.  This real-time input and interaction from the public will bring value and increased efficiency and level of service.

How to Implement Five Pattern Solutions

It used to be that you needed lots of resources (time, money, and talent) to implement solutions across all five patterns.  That is no longer the case, as there are many Commercial Off-The-Shelf (COTS) solutions available.  (See this blog post for more on Creating a Sustainable GIS.)
An easy way to plan to deploy GIS solutions across all five patterns for all departments of an organization is to create and maintain a matrix like this example for a city, where we have rows for each department, and columns for each pattern:

Then as we deploy solutions, we simply check off the boxes.  For most existing GIS departments, they have already deployed solutions for Data Management and Planning & Analysis.

So the goal would be to check off the remaining empty cells in the matrix.  The most sustainable way of doing that is with COTS applications.

So follow the five patterns of business to sustainably build a mature, successful, robust GIS that supports all of your departments and their business.  This will bring you the highest ROI on your GIS investment and allow you to take advantage of all of the capabilities of the ArcGIS platform.

Next Article

The Science of Where for Sustainable Development Webinar Series

Read this article