Overview

Water SCADA Processor

The Water SCADA Processor solution is a configuration of ArcGIS GeoEvent Server to expose and to generate reports of SCADA information in an ArcGIS Organization.

This solutions provides:

  • Map services for pumps, tanks, flow meters, daily tank changes and daily flow summary
  • Limited view into historical data
  • Real time calculations

Requirements

Water SCADA Processor requires specific technical experience and software.

Requirement Description
Experience
  • Modifying JSON files
  • Publishing GIS services
  • Authoring maps
  • Configuring GeoEvent Services
Software
Map authoring
  • ArcMap (Standard or Advanced) 10.2.1, 10.3, 10.4, 10.5
  • Portal for ArcGIS 10.4, 10.5
  • ArcGIS Online
GeoEvent services
  • ArcGIS Enterprise (Standard or Advanced) 10.5
    • ArcGIS GeoEvent Server
  • ArcGIS for Server (Standard or Advanced) 10.3, 10.4
    • ArcGIS GeoEvent Server
Map Service Hosting
  • ArcGIS Online
  • ArcGIS Enterprise (Standard or Advanced) 10.5
  • ArcGIS for Server (Standard or Advanced) 10.3, 10.4
    • Portal for ArcGIS

What you get

When you download Water SCADA Processor, you'll find the following in the zip file:

Directory Item Description
Application A Python 2.7 script to automatically create the required services, maps, and apps in your organization. These scripts utilize the Automated Setup & Reporting tools.
Maps and GDBs SCADA.gdb A sample geodatabase with the schema to store the SCADA information.
DailyFlowSummary.mxd A map document used to publish the daily flow data.
FlowMeters.mxd A map document used to publish the flow meter data.
PumpData.mxd A map document used to publish the pump data.
TankLevels.mxd A map document used to publish the tank level data.
DailyTankChange.mxd A map document used to publish the daily tank level data.
Icons Icons for the services, maps, and apps.
External Data Folder used to store the SCADA export files.

What's new

Below are the release dates and notes for Water SCADA Processor.

Date Description
February 2016
May 2015
  • Latest versions of the ArcREST tools
    • ArcREST Helper is now included with ArcREST
  • Config file schema changes
    • PublishData added to PublishingDetails section to allow the user to quickly bypass this entire section
    • EnableEditTracking & Capabilities parameters in FeatureServices has been replaced with the Definition section
December 2014
  • Latest versions of the ArcREST and ArcREST Helper tools
  • Config files schema changes
    • FeatureService section to FeatureServices
    • Login info only defined in the GlobalLoginInfo file
    • EnableEditTracking parameter added to FeatureServices section
    • UpdateItemContent changes to UpdateService in MapDetails
    • Portal in login section changed to Orgurl
    • ExistingService change to ExistingServices
    • ExistingServices ReportResult tag changes to FeatureClass
    • ReplaceTag added to section
    • ReplaceInfo Section now uses the following three parameters, SearchString, ReplaceString and ReplaceType
August 2014
  • First release of Water SCADA Processor

Known issues

  • This solution uses the Intersect geoprocessing tool. If you have line features in the same layer that overlap (for example, in a 3d view the line would look like a "Z") and using a field other than Shape Length for reporting, the results will be incorrect.
  • If you are using a field other than Shape Length to calculate a report summary and your data is being split by your reporting district, the results will be incorrect as this field is not being adjusted by the percentage that record falls into the reporting zone.
  • The automated setup utilizes ArcREST, which does not support application and enterprise logins.
  • When publishing to Portal for ArcGIS, the Hosting Server must use an ArcGIS Data Store as a managed geodatabase.
  • When publishing to Portal for ArcGIS with an ArcGIS Data Store Hosting Server, field names will be auto converted to lowercase. The tools will update the maps created, but apps are not updated to handle this conversion.
  • The script is delivered using relative paths. To use this without changing to absolute paths, you need to have python.exe as the default file extension for .py files and the path to Python in your systems path variable.

Get started with the Water SCADA Processor

Top