You have been preparing a business case to convince the business about the benefits of deploying a complete ArcGIS Enterprise in the organisation. You are fully convinced about the business benefits of a brand new ArcGIS Enterprise with all its components can bring to your company. You put a business case together, organised a meeting with the execs, carefully tailoring the message to your audience and touché!, they saw the value and approved the project - it's never that easy, anyway....-
You were fully convinced about the business benefits the deployment of an Enterprise ArcGIS could bring to the company and you were able to deliver the message to them! Now you got your funding and the project starts.
After a long and sometimes tedious process of gathering requirements, organising meetings with each of the stakeholders of the project, workshops, preparing demos and preparing an internal marketing campaign to convince the business about the benefits of the future Enterprise GIS, you finally reach the technical stages of the project...Now it is time to design the system, test it and deploy it.
But wait, don't forget to calculate capacity. It will help you to understand the IT infrastructure where your Enterprise GIS will be deployed. We need to have enough IT resources to run such an enteprise solution and be able to support the load imposed by all the workflows identified during the requirements phase, otherwise, we will end up having a great system that won't perform within valid performance values which means, your Enterprise could end up being that GIS thing that no one use.
Ok, capacity planning is crucial then, let's estimate how much resources we need to support the load imposed by the workflows identified in the requirements analysis phase and, let's estimate the load the system will get the second year....I know the company has plans to recruit more people and a new office is going to be opened in another state.
[..Estimating future capacity is always hard, especially when the solution is exposed to the public or is planned to be used in the emergency services sector when you don't actually know when the load will increase exponentially nor how long the load will stay there, anyway...the purpose of this post is not to discuss capacity...we can probably do it in a future post...]
We have done everything. All the parts are put together. The system is deployed and we are sure we have enough resources to support the load. What can be wrong?
The new Enterprise GIS is published and it is a success!.....you received good comments and all looks positive. More and more people is using the platform, it's becoming a big success.....users are discovering new ways to use the platform that I have not covered during the requirements analysis phase...that is great I think, but wait a second....what are the implications of that "success".......what are they doing! am I going to have enough capacity? is the system going to support the new load? for how long? are my services well configured? do I need to reconfigure them? if so, how much? how many more instances do I need to put to this map service that is becoming very popular? more instances...then, do I need more CPU?....am I reaching max capacity?....
In my workshops when I'm explaining how crucial is to carefully monitor the enterprise I always use an analogy between a Formula 1 car and an Enterprise GIS.
Each team design a F1 car at the beginning of the season and evolve the car during the year. The F1 teams never stop monitoring the performance of the car, fine tuning each component and changing some of them. It's a living thing, that needs to adapt to constantly changing conditions, it needs to adapt to each race and to the changing conditions during each race. So what would you think it would happen if a team design a car at the beginning of the season and use that car during the whole season without monitoring anything?
In an Enterprise GIS we need to apply the same principle. The conditions will change and we will need to be able to anticipate to those changes and react as soon as we can to adapt the system to the new conditions - more load is coming due to an unexpected use of the system, for example.
It is not the strongest of the species that survives [..........]. It is the one that is most adaptable to change.
There are many tools in the market that allow monitoring an IT system. There are not many specifically design to monitor a GIS Enterprise. There is only one designed and developed by esri that allow you to monitor all the system components that can have an impact on the performance on you ArcGIS Enterprise. It is called System Monitor 3 -
(user: esridemo , password: esridemo) , and it is great by the way.
If you need more information about System Monitor 3, please use the following contact form