Geo SCADA Mapping: Best for WMS, Not Rich Mimics

After commissioning, operators gain live geographic context around site assets without maintaining map-image backgrounds by hand. Use Geo SCADA mapping for location-aware views and WMS overlays, while retaining a conventional mimic wherever operators need dense labels, custom symbols, multicolor state encoding, or one-click navigation.

Approach comparison

Before anything else, confirm what the display must communicate. Geo mapping and a mimic containing static PNG map sections solve different problems. The deciding question is whether geographic context or rapid status recognition has priority.

Select a Geo map when live environmental context, geographic queries, mobile-worker position, or low-maintenance base maps drive the use case. Keep the mimic when operators must identify station type and detailed state at a glance. For water and wastewater systems, a hybrid design is usually the strongest choice: use the Geo map for rain radar, catchments, access context, and regional asset selection; open the existing site mimic for detailed control and diagnosis.

Recommended display architecture

1. Retain the operational mimic. Keep custom symbols, station-number labels, communications indications, state colors, legends, and direct navigation that operators already use. Confirm that the mimic remains the authoritative detailed status display before proceeding.
2. Add a regional Geo map. Place each applicable asset by assigning its Location at the site level. Confirm that every commissioned site appears at the intended geographic position.
3. Add operational overlays. Configure the required WMS sources for rain radar, catchments, fire danger, hotspots, or geology. Confirm that each layer aligns with the base map at multiple zoom levels.
4. Use map symbols as selectors and alarm indicators. Do not try to reproduce a dense mimic inside each map icon. Confirm that icon color, flashing behavior, tooltip content, and navigation expose enough information to choose the next action.
5. Open the detailed site view from the map. Configure and test the available Default View and Alarm View paths. Do not move on until the operator can reach the correct display from every representative site type.

This division avoids forcing five or more operational categories into three generic shapes. It also separates two different visual tasks: the map answers “where is the asset and what surrounds it?”, while the mimic answers “what state is the station in and what must the operator do?”

Location-data preparation

Location quality controls every downstream result. Assign geographic data to the highest reusable object that represents a physical place, normally the site. Equipment beneath that site can inherit the operational context without creating multiple overlapping map points.

1. Inventory the objects that represent physical sites and identify any existing coordinates stored in database parameters.
2. Define one coordinate source of record. Where a mature ClearSCADA database already holds coordinates in parameters, migrate or map those values into the native Location property instead of maintaining two editable copies.
3. Check coordinate order, sign, and physical placement against a known base map. A syntactically valid coordinate can still place an asset in the wrong region.
4. Assign locations to a small pilot containing each station type and geographic condition.
5. Query the database by location and inspect the plotted results. Do not proceed to bulk population until the query result and map position agree.
6. Apply the same method to the remaining sites, then identify missing, duplicated, or visibly clustered points.

Native locations make geographic querying and map placement part of the object model rather than a convention hidden in custom parameters. They also create the relationship needed to place environmental layers and mobile users in the same geographic frame.

Symbol and tooltip design

Map symbols have less visual bandwidth than mimic objects. Build the map around that constraint instead of compressing every station state into one icon.

A separate thematic map can present a different operational question. A zone-metering view, for example, can emphasize flowmeters and pressure meters, with tooltip values for flow rate, daily totalized flow, and current, minimum, and maximum pressure. This is more legible than making one regional map carry every alarm, hydraulic value, and station category.

Base-map and WMS selection

Choose the base map for the operator's task. Satellite imagery supports visual recognition of terrain and facilities. Topographic mapping adds landform context. Road and land-plot detail helps dispatch and access planning at higher zoom levels. Geo SCADA deployments can use sources such as ArcGIS Online, Bing Maps, or OpenStreetMap where organizational network policy and source availability permit them.

WMS overlays add the information that a static mimic map cannot maintain efficiently. Water and wastewater applications can combine asset locations with rain radar and water-catchment outlines to judge which reservoirs, pump stations, or service areas may be affected by incoming weather. Fire-danger and hotspot layers can support planning for remote asset access. Geology layers can add soil or water-table context when assessing areas susceptible to flash flooding.

1. List the operational decision the layer must support, such as dispatch during heavy rain or access during a fire-danger period.
2. Select a WMS source that covers the asset region and publishes the required layer.
3. Confirm that the control-room network can reach the service. If internet access is restricted, resolve the approved network or internally hosted service path before map configuration.
4. Add one layer at a time and check its geographic alignment, visibility, update behavior, and readability.
5. Test the layer at the zoom levels operators will use. Do not move on until site symbols remain distinguishable over the overlay.
6. Record the layer owner and operational purpose so a failed or retired service can be identified quickly.

Visualization and analytics boundary

A displayed WMS raster is operational context, not automatically a process input. Showing forecast rain over a catchment helps an operator assess risk, but calculating expected infiltration flow requires programmatic access to raster values, a defined catchment, a rainfall-to-inflow model, and process-specific calibration.

The discussed Geo SCADA implementation did not provide the requested server-side programmatic access to WMS raster results. Do not build an automatic pump-down strategy around pixels visible only in the client. Route analytic requirements through a data source that exposes numerical rainfall values or raster access suitable for computation, then validate the derived inflow estimate independently before connecting it to control logic.

Commissioning and operator acceptance

1. Test placement. Select known sites near recognizable roads, boundaries, or terrain. Confirm that each icon appears at the correct physical position.
2. Test missing data. Remove or invalidate a pilot location using the approved test method. Confirm that bad location data is detectable and does not silently present a believable but incorrect point.
3. Test status behavior. Apply representative alarm, communications, and power states. Confirm exactly which conditions affect map color and flashing, and which remain visible only on the detailed mimic.
4. Test tooltip values. Compare the site name, access information, alarm count, telemetry health, and power health against the live database.
5. Test navigation. Right-click representative icons and open Default View and Alarm View. Confirm that each action reaches the intended object.
6. Test overlays. Enable and disable every WMS layer, inspect alignment at several working zoom levels, and confirm that the layer timestamp or source status is visible wherever freshness affects an operational decision.
7. Test network loss. Block or otherwise simulate loss of the approved map-service path. Confirm that operators can identify the unavailable layer and continue using site mimics without mistaking stale context for current data.
8. Test user location. Where ViewX on a location-aware device or the MobileApp plots personnel, confirm user consent, the operational purpose, who can see the position, and when collection stops.
9. Run an operator scenario. Present a regional weather or access event and have the operator identify affected sites, inspect tooltip status, and open the detailed mimic. Accept the design only when the task is faster or clearer than the previous workflow.

FAQ