Utility Networks - Enterprise Deployment

1977
5
Jump to solution
05-01-2017 07:32 AM
LanceCole
MVP Regular Contributor

With the separation of utility networks into separate schemas from the local government model how is it best to deploy this to an enterprise environment?  We are a small city with existing GIS data for water, storm and sewer that we are getting ready to move these items to a managed networks for each.  With ESRI removing this data from the LGIM and creating separate GDB and schemas, has a deployment guide, best practice or whitepaper been published?  Should the utility data be maintained in a separate SDE geodatabase from the core LGIM data?

0 Kudos
1 Solution

Accepted Solutions
HowardCrothers
Esri Contributor

There is no one size fits all answer.  The best approach could depend on factors like what you are trying to accomplish and your system architecture, so some things to keep in mind.

If you're going to deploy more ArcGIS for Water Utility configurations than it will be less deployment work if you are using the WaterUtilities.gdb schema.  But keep in mind, that schema will evolve over time.  Only update your schema to support deploying more configurations.  Don't upgrade your schema every time waterutilites.gdb or the LGIM is updated.   

As to whether you should put the LGIM schema and the WaterUtilities.GDB schema in one geodatabase or separate geodatabases, not knowing more about your implementation (other than a small city) hard to determine if it will have a measurable impact.  Keeping them separate gives you more modularity however there will be more overhead.

View solution in original post

5 Replies
George_Thompson
Esri Frequent Contributor

Here is a Whitepaper that may help with some information: Esri Utility Network Pro 

--- George T.
LanceCole
MVP Regular Contributor

George,

Thanks for the quick reply.  The whitepaper "The Road Ahead for Network Management" is a great overview of what is forthcoming in network management. I am looking for information that goes a little deeper.  Currently we have a single SDE geodatabase that is roughly based upon a very early schema version of LGIM.  We are going to migrate this data over to the newest version of the LGIM as well as create networks for water, storm and sewer systems.  Should we continue to maintain this on a single SDE database, break the database into two or more databases such as - LGIM core data and a separate database(s) for networks, etc.

Currently we are only utilizing the ArcGIS desktop environment with a single ArcGIS Server running an informational website but are planning on establishing an ArcGIS Portal and expanding into ArcGIS Pro using the numerous readily available resources. 

0 Kudos
George_Thompson
Esri Frequent Contributor

I am not sure if there is something out yet. I would guess that there will be a lot more information coming out in the next few months.

--- George T.
0 Kudos
HowardCrothers
Esri Contributor

There is no one size fits all answer.  The best approach could depend on factors like what you are trying to accomplish and your system architecture, so some things to keep in mind.

If you're going to deploy more ArcGIS for Water Utility configurations than it will be less deployment work if you are using the WaterUtilities.gdb schema.  But keep in mind, that schema will evolve over time.  Only update your schema to support deploying more configurations.  Don't upgrade your schema every time waterutilites.gdb or the LGIM is updated.   

As to whether you should put the LGIM schema and the WaterUtilities.GDB schema in one geodatabase or separate geodatabases, not knowing more about your implementation (other than a small city) hard to determine if it will have a measurable impact.  Keeping them separate gives you more modularity however there will be more overhead.

LanceCole
MVP Regular Contributor

I received a phone call from ESRI Utilities Team regarding this question.  As Howard pointed out above there is not a one size fits all answer, however, the utilities team did have some excellent input.  The basis for separating the water data from the LGIM core is for future direction of utility networks.  With the proposed release of utility networks in the first quarter of 2018, there will be a need to eventually separate the data as the deployment continues to evolve over the next few years.  Our plan is to move our water, sewer and storm data onto a separate geodatabase and into geospatial networks.  This is the first major change to our LGDM schema in almost eight years and positions us to migrate to utility networks in the future once the new networks are well established. 

0 Kudos