Tag: water distribution

Expanding the power of the Attribute Assistant

Here at Esri, we always try to help one another out.  Well the Local Government team asked if we could expand the functionality of the Attribute Assistant and make a series of construction tools to help with address data management workflows; and we obliged.  We came up with some pretty cool new rules for the attribute assistant and some interesting construction tools that will be used to streamline address maintenance workflows.  Even though these have been designed for managing address information, you may find them very helpful.  Let’s first take a look at these new attribute assistant rules.
The first rule we needed to create was CASCADE_ATTRIBUTE.  This rule will allow you to make a change to an attribute in a table or layer and push that new attribute value to every feature that contains the value. So in the address world, we have implemented a Master Street Name table.  Say a road was renamed, we can go into the table, change the road name, and the rule will open up the Road Centerline layer and make that change to every road with the old name, then open up the Site Address Point Layer and update the road name as well.  Pretty cool, huh?
The second rule we created was VALIDATE_ATTRIBUTE_LOOKUP.  This rule will validate an attribute change against a look up table or layer.  Let’s look out how you would use this in address land.  If I created a new road and I want to make sure the road name matches a road in the Master Street Name table, I can set this rule up to monitor my Street Name field and check that value against the Master Street Name table.  The cool thing about this rule is all I have to do is enter a piece of the road information.  If it finds more than one record in the street name table, it presents a prompt, where you can select any of the matching values.  How is that for data validation?
I also mentioned we are working on some new construction tools.  These are still in development, but here is what we are working towards.  One tool will allow the user to click a reference point, in our case, an address point that represents the location on the centerline of which the address is derived, create this point if it does not exist, then create a series of site address points with information from that reference point or the centerline underneath it.  So basically, you can create a series of points all with information from source point.  The second is a tool to draw a new road and split any intersecting roads and prorate their address information.
If you want to try the new rules out, as well as a few other enhancements, we have posted a beta of the tools on the forum.
Mike from the Water Team

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | 2 Comments

Another round of updates – Infrastructure Editing Template

Hope everyone on the east coast made it through the hurricane ok. We lost power for a few days here at the Water Team headquarters in the Philadelphia area. The down time allowed us to crank out another release of the IET. We spend the time working on tools to help you move assets from proposed to in-service, in-service to abandoned, etc.
One new tool you will see came from a UC request and thought it would be a good start for this toolset. This tool allows you to reassign all connected assets to a main to a new main. Very simple, select the main that is going to be abandoned, select the new main, and all taps, laterals, valves, etc are moved over to the new main.
We also added a new rule to the Attribute Assistant – MOVE_FEATURE. This rule monitors a field and when that value of the field matches what is listed in the value info, the feature is either copied or moved to the target feature class.
Lastly we are working on a python script to move feature also. This script looks at the selected features, copy’s them to a target featureclass and sets the source features name in a field. We might look at building an ArcObjects tool to do the something similar, but expose a few more options in the configuration files. Maybe the python script can load the same config file.
Not only did we add a few new tools, but we also made a bunch of internal bug fixes and enhancements to improve the stability and functionality of the toolset.
Thanks for you feedback on the last weeks post. Please keep it coming.



Posted in Water Utilities | Tagged , , , , , , , , , , , , | Leave a comment

What do you want out of an Abandonment Toolset?

If you have not noticed, we have been making a lot of improvements to the Infrastructure Editing Template or IET as some of you have been calling it.  We have been working through the enhancment requests that we recieved at the UC and have released most of them through the Water Utilities Forum Beta Thread.  We have one very important improvement left that we need your help on.  We are looking to build a set of tools to help bring infrastructure from a proposed status to an in-service status and tools to move features from in-service to an abandon status.

Here are the tools we are thinking of so far.

1:  A Geoprocessing script or model to change the status of selected features.

2:  A Geoprocessing script or model to move a feature from one feature class to another and update some attributes.

3:  A tool to select an existing line, select a new line and move all features to the new line(taps and laterals)

4:  A tool to select two locations on a line, junctions or edges, split the line if required, run a trace between them and copy or cut each feature to a new feature class.

Would the above toolset allow you to manage the life cycle of your assets better?  If not, what are we missing?  Should we add any additional steps to these tools?

 Please let us know through the forum entry on this topic linked below.




Mike Miller

Posted in Water Utilities | Tagged , , , , , , , , , , , | Leave a comment

The Water Development Lab

Been a while since we posted anything on updates to the templates, but that’s because we’ve been busy doing some updates.  A lot of good things are in the works.  We’ve heard from many users that migrated their production environment over to ArcGIS 10 in the last few months and as part of that migration are deploying the templates.  So their organizations are building new workflows and modifying old ones to take advantage of the templates.  We’ve gotten some very useful feedback from these users and the below are some of the results of that feedback.

New fields in the Dynamic Value Table

GENERATE_ID TableYou all have asked and we listened.  We are restructuring the Generate ID table to have two columns, Sequence Name and Sequence Value.  Each row will represent a sequence value. 

RUNORDER – This will allow to you specify the order the rules are processed.  The previous extension processed the rules in the order of the fields.  This caused issue when trying to chain together steps.  The runorder is more of a hierarchy, so numbers can be repeated.

ON_MANUAL – Users have asked for a way to only run certain rules when I click a button.  The on_change button is great, but does not allow for only manual rules.  There will be a button to fire on_manual rules.

Modified Rules – We have updated a few rules, below are the changes.





These rules now have a value method that for lines you can choose to get the centroid, start or end coordinate.

C – Extract the coordinate value from the centroid

S – Extract the coordinate value from the Start

E – Extract the coordinate value from the End

JUNCTION_ROTATION – New option to list the diameter field.                              

New Rules –  To many details to mention, but we will have detail info in the doc.











New Trace

We are working on redoing the trace to allow it to be exposed to web applications better, as part of this, we are adding a secondary isolation trace function.  This will temporary set all valves as inoperable, run the trace from the trace point and return the results.

Operational Viewer

We are anxiously awaiting the release of the Flex 2.3 viewer.  We this release, we will update the Operational dashboard to run on this release.

Citizen Engagement

Ne new version of the applications allow your customer to submit a service request as well as share information with them.  Coming Soon.



Update – You can find all beta releases on the Forum – http://forums.arcgis.com/threads/20000-Beta-Versions

Posted in Water Utilities | Tagged , , , , , , , , , , | 3 Comments

Esri's Team Water/Wastewater Meeting 2011

This year’s meeting was held at the Orlando Utilities Commission, Pershing Facility.
We had a great turnout this year and I would like to thank all of the attendees. I know that travel budgets continue to be tight. Participants this year included Hamton Roads Sanitation District, Charleston Water System, Orlando Utilities Commission, Woolpert, Esri Canada, St. Johns River Water Management District, Global Water, Collier County Public Utilities, Trimble, American Flow Control, City Works, DHI, and Wachs Water Services.    
A big thank you to Trimble and Wachs Water Services for sponsoring breakfast and lunch!
We will be posting the presentations and the agenda from this meeting in the near future!

Posted in Water Utilities | Tagged , , , , , , , , , , | Leave a comment

Infrastructure Mobile Map

Last week, not only did we release the Editing template for ArcGIS 10, we also released the Mobile Map template for ArcGIS 10.  This template is designed to show a utility how to replace their paper maps with a digital map.  ArcGIS mobile technology allows you to build a cache (different than a tiled cache used in ArcGIS Server) of your data to take into the field and work completely disconnected.  At any time you do have a connection, you can pull down updates or push up changes you have made in the field.

ArcGIS Mobile 10 has some significant changes that we were able to incorporate into this release of the template.  The most important is the ability to use tiled cached basemaps.

In the screen shot above, you can see a new window that lets the field crews easily toggle between their operational data and their basemaps.  It also distinguishes between online basemaps, maps that are streaming down from ArcGIS Server, and local basemaps, tiled caches deployed to the machine.

Not only did we add support for basemaps, we also included two basemaps designed for the field crews, one for day and one for night.  We really think you are going to like these maps and they will provide a great starting point when you want to define your own field basemaps. We also extended the template to utilize the new client side SDC based geocoding.  So now you can perform a true geocode, completely disconnected.  Not only did we provide a way to geocode, but also an integration with ArcLogistics Navigator.  From the Identify panel or workorder panel, you pass the location of the asset to ArcLogistics Navigator.  Navigator will pop up, route you to the location and disappear once you arrive.  Really showing how ArcGIS Mobile can be the mobile data terminal for you field crews. 

We made a bunch of other changes and enhancements, so please, try it out.  We included an installer that will lay down the application, sample mobile cache and the night and day basemaps.  As always, we included all the source code.  So if you are starting  to develop in ArcGIS Mobile, there is a lot of great code that you can borrow or use in your projects.

Thanks, and let us know what you would like to see in the next release of this template on Ideas.arcgis.com. 

Posted in Water Utilities | Tagged , , , , , | 2 Comments

Release of the Editing template for ArcGIS 10 – Part 2

Attribute Assistant

The attribute assistant has some significant changes for ArcGIS 10.  When you download it, you will not find the installer that you might be used to.  You will just see a simple ArcGIS Add-in.  This should help you deploy this extension to your organization.  We also modified some of the existing functions and added a few new ones.  The table below discus’s the different methods for this extension.

Value Method Value Info Details Requirements
GET_ADDRESS_USING_ARCGIS_SERVICE Url to a Geocoding service This method preforms a reverse geocode.  The default service is the ArcGIS.com geocoding service.  You can specify your own. String Field
TIMESTAMP None Stores current date and time. Date or String Field

W – stores full windows login name as domainusername

U – stores just the windows usernameD – stores the connected database user for the edit session  If you leave VALUE_DATA blank, it will store the database user name if available otherwise store full windows login.

Stores current user name. String Field
LAST_VALUE None Repeats the last value used for a field.  
X_COORDINATE None Stores the X coordinate in database units  
Y_COORDINATE None Stores the Y coordinate in database units  
LATITUDE None Stores the Y coordinate projected to WGS84 decimal degrees.  
LONGITUDE None Stores the X coordinate projected to WGS84 decimal degrees.  
FIELD Field Name Copies one field to another field in the same feature.  

A  - if you enter an A it will store the rotation using an arithmetic rotation.

If you leave VALUE_DATA blank, it will store the rotation using a geographic rotation.

Stores a rotation angle for a junction feature based on connected edge features by storing a rotation angle in the specified field.  Requires geometric network.  Target must be a point feature class that participates in the geometric network as a simple junction.  Requires ArcEditor or ArcInfo.   
LENGTH None Stores calculated length of line feature.   
SET_MEASURES If you leave ValueInfo blank, it will calculate the Ms starting with zero and ending with the length of the line.   If you enter a P for ValueInfo, it will calculate the Ms starting with zero and ending with 100. Populates the M coordinates in a line which enables using Add Route Events to point and line events dynamically along line features Requires a line with M’s turned on
TO_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the start of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
TO_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the end of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 

<FieldName>| <optionalSequenceWidth>| <optionalFormatString>[seq]


Increments a column in an unversioned table and stores that newly incremented value. Uses an unversioned table that is typically called GenerateId (change in AttributeAssistant.config) to store and increment unique sequence numbers.     



<Layer Name> |<Layer Field Name>|<Sequence Field Name from GenerateID Table>| |optionalSequenceWidth|[id]optionalFormatString[seq]<any order of ID and SEQ> 


The result would look look like GRID5-0002, if the grid you intersected ID was 5 and the next number in the table was 2.

This tool requires you create fields in the Generate ID table that are a combination of the GRIDIDX(the Sequence Field Name) and the Grid ID. So the tools looks at the interesected grid, gets the ID from it, combines it with the <Sequence Field Name from GenerateID Table> to look for a field in the Generate ID table to get an seq for that grid. Say the grid you created a feature in was 5, you need a field called GRIDIDX5 in the generate ID table. 



Example:replace(([FROMMH] & “-” & [TOMH]),”MH-”,”")

Stores the results of an expression.   

Optionally enter one of the letters below to format the GUID as desired.

N – GUID  with no special characters – length 32 D – GUID with dashes – length 36 B - GUID with dashes and braces – length 38 P – GUID with dashes and parenthesis  - length 38 default – GUID with dashes and braces – length 38 Leave the ValueInfo Field blank to get the default GUID format.  Example: {3F2504E0-4F89-11D3-9A0C-0305E82C3301}

Stores a new GUID.  The target field must be a field type string field and must be long enough to store the desired format of GUID.

<Layer Name>,<Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|DIAMETER

Gets a value from an intersecting feature in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   

<Layer Name>,<Layer Name>,..|Label

Example: FiveMeterSurface|Elevation:

Gets a value from an intersecting raster cell in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   

<Layer Name>, <Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|FACILITYID

Gets a value from an intersecting feature in the specified layer and reports the distance along the line.  You can specify any number of layers to look for by listing them with commas between their names.   
NEAREST_FEATURE <Layer Name>,<Layer Name>..|<Field Name>|<Search Distance>

Example: wMeter,sLateralPoint|ACCOUNT|100 

Gets a value from the nearest feature in the specified layer.   

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | Leave a comment

Release of the Editing template for ArcGIS 10

We are happy to announce the release of the Infrastructure Editing Template for ArcGIS 10.This new release takes advantage of some of the great additions to ArcGIS 10.  You will find a new datamodel which encompasses many new layers.  You will also see an updated symbol set, a symbol set designed to be overlaid on imagery, topographic, and parcel basemaps.&nbsp; The editing map document was updated to show you have to set up feature templates.  You will see how we reordered, highlighted and set some fields to read only, as well as hide a few.  We think you will like the new data model, symbology and the new mxd.  Now on to the tools!

We migrated the Editing and Reporting toolbars and the Attribute Assistant to ArcGIS 10 Add-ins.  Not only did we upgrade them to ArcGIS 10, but included a series of bug fixes, config changes and new functions, which all came from your suggestions, so please keep the feedback coming.  Lets breakdown the Add-In’s and discuss the changes.

Desktop Editing Toolbar – Changes and New Tools

The first thing you might notice is the Add Laterals icons are missing, but there is a new one that sort of looks like it.  We compressed the Add Lateral tools into one function that looks at the selected features and compares them to the config file and generates laterals from them.  This allows you to generate many types of laterals at once.  To the right of it, there is a new tool, Connect Closest.  This tool will connect a series of points, say a row of manholes, with a line, such as a sewer main.  If we look to the left you will see a a large red button with a ! in it.  This is simple layer inspector.  It looks at a feature class and lets you step through each feature one at a time.  Real handy for reviewing those redlines or field notes.  If we keep moving left, you will see an icon with a line and 123 in it.  This tool allows you to quickly calibrate a line that is M enabled.  Should help you plot your CCTV data on your sewer.  Next is the Merge Geometric Network Features, an ArcScript that has been around a while, so we thought we add it to the toolbar.  I agree, the icon looks like it is breaking features apart.  We will see if we can change this to something more meaningful.  On the far right, is a new tool included with the Attribute Assistant.  This tool triggers the change event for all selected features.  So you can manually fire out the Attribute Assistant rules.  The last new tool on the toolbar is the Incremental Network Loader.  You can find out about the new tool here

Desktop Reporting Toolbar – Changes and New Tools

We mainly enhanced the existing tools.  We had a bunch of request to return the edges of a trace in the selection set, so we added another trace button below each trace that does just this.  There is a new way to run the Isolation trace, in batch.  The Summary Isolation trace will loop through all selected water mains and run an isolation trace for each.  The results are stored into a feature class which you will find in the Capital Planning dataset.  I warn you against running this on all your mains, it takes a while(don’t worry, the tool warns you to if you make the mistake on clicking it without a selection set).  A new tool that we are all excited about is the Profile Graph tool.  This tool lets you pick two manholes, runs a find path trace between them, intersects the result with an elevation surface and plots the manholes, mains and elevation onto a graph for you.  We think you will really like this tool.  There is a known issue right now though.  When the chart opens, you have to turn off the manholes in the chart properties, then uncheck automatic from the left axis.  You can then turn the manholes back on.  The last tool on the toolbar, Attribute Transfer Loader, was a request from a user who was transferring data using the attribute transfer tools.  If you ever used these tools, you know you had to set them up each time you opened ArcMap.  You can now set up the mapping in the config and load it to the attribute transfer dialog.  

Desktop Tools – Config File Changes

If you changed the config file for 9.3.1, you will need to move these changes into the new config file.  You will see in the new config, we reworked a lot of the entries in a nested xml structure.  This allowed us to include some new options and load the config file faster.  For example, the Add Laterals Tools.  This was a long series of entries and you were limited to the 3 types we exposed.  Now you will see you can use these tools on any number features.  Here is a screen shot.

Also, you will see that there is an xml array that defines the points along.  We had a lot of request to allow the option to add more than one point along the line.  With this xml array, you can have it add any number of points along the line, I left a sample in the config to show how to do this, notice it is commented out. 

Desktop Tools – Construction Tools

You will also find an installer for a set of construction tools.  These construction tools call some of the functions on the toolbar and expose some new functions.  These new tools should further speed up editing and creating new assets with ArcGIS.  Note: at the moment, the construction tools and the toolbar use the same config, but they each have their own copy.  We are looking into how to share one config between them. 

Let’s take a detailed look at them.  

                Screen shot of the new construction tools for points and lines.


For lines, there is one new tool, Create a line with end points.  This tool will end two points at the end of the line you sketch.  The config file controls will points get added to what line.  So you need to modify the config to list the line layer and the ending point layer.  Using the new xml config file, you can specify any number of layers for this to work on.

For points, there are a number of new tools.  Some are samples that come with ArcGIS, some are new tools we added, let’s start at the top.  The Points along a line at is a great sample that comes with in the Developer Kit.  A great sample for creating a series of points at an interval.  Next is a custom tool, Add a connection and the lateral.  This tool does the same thing that the Add Lateral tool does on the toolbar, but this one lets you create the point and immediately connect it to the main.  The Create a point and line tool does the same thing Connect Closest tool does, but this does it as you click.  Imagine you are creating manholes.  Each time you drop one, it searches for the closest manhole and adds the main.  The last construction tool is the Add a point and split an intersecting line tool.  This does exactly what it says, split the line that you click on.

We are very happy and proud with this template for ArcGIS 10.  Let us know if you have any issues or any suggestions.   In the next blog, we will talk about some changes in the Attribute Assistant.

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | 9 Comments

Role Based Web Applications for Water Utilities


For the past few years we’ve been talking about role based web GIS applications as a best practice at water, wastewater and stormwater utilities.  Basically, this means providing web based GIS applications (GIS maps & functionality in a web browser) to water utility staff tailored to their role at the utility. 

For example, you may have a different browser based web GIS application for each department at a utility (customer service, engineering, operations, etc).  Also you may have different web applications (or additional functionality) for each department based on a staff hierarchy (managers see more data than others). 

The idea is that staff at a water utility should see information in a way that is relevant to their duties and role.  A customer service rep should see information that helps them interact with the rate payers in a more meaningful (and faster) way, such as where work is occurring, where there are open service requests and work orders and who is currently out of service.  A CSR should also have the ability to analyze and interact with the map in a way that helps them perform their job better, such as zoom to a customer location to see what is happening near them, do analysis such as how far is the nearest fire hydrant for insurance purposes, etc.  What a CSR doesn’t need is all of the detail of the utility network and the ability to view maintenance history, but that is the information that someone in engineering or operations needs.

Over 5 years ago (and a few generations of ESRI technology ago – ArcIMS, yep I said it) customers were often creating “monolithic” web applications – basically creating one web mapping application for the entire utility to use.  You’ve probably seen these in action (and hopefully replaced yours if you had one).  Monolithic web GIS apps typically grew out of an application for a single department (usually the first department to use GIs) or as browser for all of an organizations spatial data.

At some utilities these once slim and trim applications became bloated with data layers and functionality.  Every time a new spatial dataset was developed or new functionality was requested that was specific to a department or sometimes to one user it was put into the web application.  So what you ended up with was a mapping application that had too many data layer and too many functions and ended up being neither simple to use nor intuitive.  Worst of all they became hard to upgrade or migrate to a new versions because there was too much custom code.  Because these bloated sites became so packed full of data and functions some GIS managers did not want to modernize their web applications out of fear of user backlash.  I’ve heard comments ranging from “we have so many people using this application that we can’t possible upgrade it without disrupting everyone” and “I have so much custom code in here” to “it took me so long to train people to use this web application that I don’t want to replace it”.  If you’ve had to invest inordinate amounts of time in training people to use your web applications, that may be a good indication that it’s too bloated.    So in an effort to serve everyone with a single app, the cartography got worse, the map became more crowded, the app became harder to use and you got stuck in a version of technology.

So why is a role based web application a best practice?  Well certainly it avoids the pitfalls of a monolithic application.  But beyond that, a role based web application allows you to take full advantage of a fundamental tenant of the “Geographic Approach” for water utilities – that you can share a single authoritative source of information (your multiuser geodatabase) through a common application (ArcGIS Server) around the utility in a way that makes GIS a part of the normal work routine of staff because GIS fits the way they do their work – it fits their role. 

How do you share a single authoritative source of data to different roles using ArcGIS Server?  The key is that you are publishing just a manageable handful of map services that power all of your role web applications.  You have your base mapping services (probably more than 1 – including a topographic base, a street base map and an imagery base map – maybe even multiple imagery base maps).  The topographic and street base maps are cached and your imagery is served up as service from the Imagery Extension for ArcGIS Server.  Of course you can also use hosted content from ArcGIS.com for your base maps.  So what you have is a common looking set of base maps that everyone in the utility uses.  So the base maps look the same for all of your role based dashboards.  The utility’s base map layers help give the same familiar look and feel to all of your role based web applications.

You’ll then have at least 1 map service (maybe a few depending on the complexity of your infrastructure and the needs of specific roles) for your distribution and/or collection systems.  If you’re a combined utility you might have a dynamic map service of your water network and a dynamic map service of your wastewater network.  Of course you could cache the map services for your utility networks, but we think the business value of having dynamic map services of your utility networks that can show changes in real time outweigh performance gains from caching your utility network.  In other words, architect your GIS system to ensure that you can support dynamic map services for your utility networks.

You’ll also have a dynamic map service (or services) for “operational data”.  For those that haven’t seen the term before operational data is data that is related to the operations of your utility.  It’s the locations of customer calls, work orders, unassigned service requests, vehicles, CIP project, etc. 

So as you’re deploying role based web applications you’re using your utility’s base maps with combinations of your network maps services and operational data map services.  If necessary you’ll make some map services that show certain data layers or symbolize data a specific way based on roles. 

Keep in mind that the map is just one part of a role based GIS application.  You’ll also have the user interface and functionality.  In general, the same basic UI should be used for all of your role based web apps and then tailored to each role.  Of course if a role needs a different UI (maybe even a different client such as a JavaScript if you typically use Flex) you can deploy that for a specific role using the same map services that power your other role based web apps. 

So again using the example of a web based mapping application for a customer service representative, the user interface should be set up for fast navigation so CSRs can interact quickly with the map.  So a role based application for a CSR may have start with a text entry box that drives action based off an address, cross streets, a customer’s name, phone number or account number.  A role based application for someone in operations may provide may drive map action by allowing users to enter an asset ID, an address or by zooming around the map with navigation tools.

Functionality may include spatial analysis (geoprocessing) tailored to the job role and included in the web application as simple button.  For example a CSR may have a few buttons in their web application that determine how far the nearest fire hydrant is from a caller (a common request from home insurance companies) or could buffer a location and list all of the service requests as well as current and planned work near the caller.  Someone in operations doesn’t need the hydrant distance tool and might need functions such as a valve isolation trace.

A few other thoughts on role based GIS web application.  Role based doesn’t mean that every permutation of department and responsibility needs their own web application. There is a lot of commonality between map presentation needs per role that are satisfied by your base map services and your utility network map services.  From our experience most of the differences between the needs of roles are for an additional few data layers (or for a few data layers to be symbolized or labeled differently), slight tweaks to the user interface and in different analysis tasks.  Also some roles need the ability to edit data.  Editing in a web application at water utilities is usually constrained to adding redlines, change asset attributes or adding operations data such as leak locations. 

If you want to see these concepts in practice then download (or take a look at again) the Water Utilities Operations Dashboard.

Have any thoughts on role based web applications? Feel free to share them.

Posted in Water Utilities | Tagged , , , , , , , , , , , , | 1 Comment

Partners using the templates

A while ago we ask you to share your stories with the templates.  We got some great feedback from our users.  So many people are using the data, models, cartography, and sample apps to build and design their system.  I ran into GISi at the BPC and found out that not only are users enjoying the templates, but so are our partners.  If you are a partner, implementer, integrator and you are using the templates, we are also looking for your experience. 

GISi shared a press article with us talking about how they implemented ArcGIS Mobile and the Mobile Map Template in the City of Marietta, GA. 




Posted in Water Utilities | Tagged , , , , , , , , , , , , , | Leave a comment