Operational asset layers
Structure facilities, equipment, monitoring points and defined operational areas as separate layers. Use stable asset identifiers so a map selection opens the correct source record and related measurements.
GIS dashboard
development.
Location context.
For connected operations.
Give distributed assets and monitoring events a shared geographic context. Hitelecom scopes custom GIS dashboards around your site register, location sources and operating workflow: find the relevant point, inspect its uploaded data, review its event history and pass the record to the responsible team. An agreed Hitelecom Cloud or customer-platform integration can provide online monitoring data and configured threshold notifications. Map functions, data sources and access are defined for each project.
MapsAgreed geographic contextSpecify layers, coordinates and usage rights
DataLocation-linked recordsMap identifiers, timestamps and quality
WorkflowDefined operator actionsAgree filters, roles and event handling
Engineering focus
An operational map.
With a defined data model.
A useful operational map connects geographic position with trustworthy records and a clear next action. Define the layers and interactions around the team using the map, from a control-room overview to a mobile site visit.
Coordinates and location quality
Document coordinate reference systems, location sources, update timestamps and available quality indicators. Keep surveyed positions, estimated positions and last-reported mobile locations distinguishable.
Linked measurements and history
Select a point to view available measurements, units, timestamps and historical records. Connect Hitelecom Cloud or an agreed customer source through documented identifiers and authorized interfaces.
Search, filters and map summaries
Scope asset search, status filters, layer controls and agreed geographic summaries. Define how filtering changes map symbols, lists and counts so users see the same record set across the dashboard.
Events in their geographic context
Place received threshold alarms and other agreed events at their mapped asset or location. Distinguish active, acknowledged and historical events according to the source workflow and user role.
Tracks and area-based rules
Where suitable location records exist, scope track views, zone entry/exit or proximity checks. Define location uncertainty, boundary behavior and event timing; these functions do not improve the underlying positioning accuracy.
Field and control-room workflows
Tailor map selection, detail panels and record handoff to desktop or mobile use. A mobile view can prioritize site information and inspection links rather than reproducing every control-room panel.
Deployment, licensing and access
Specify the map service, tile/data rights, hosting arrangement, authentication and permission boundaries. Agree API usage, data retention, source-code delivery and third-party costs before implementation.
Project planning
Start with coordinates. Finish with clear decisions.
Map appearance, data interpretation and operating responsibilities should be specified together.
01↗
Define the operating geography
List the areas, assets and users the map must support. Review coordinates, boundary data and location quality before choosing the base map and operational layers.
- Project inputs
- Coverage · Coordinate reference · Asset register · Location quality · Map rights
02↗
Define the record and event contract
Review sample data for asset identity, measurements, timestamps, quality, event status and history. Specify missing, duplicate, delayed and out-of-order record handling.
- Project inputs
- API samples · Identity mapping · Time semantics · Event states · Retention
03↗
Verify the map workflow
Choose representative sites, events, permissions and mobile tasks. Agree how map, lists, counts and record handoff should behave with that dataset and target devices.
- Project inputs
- User scenarios · Layer rules · Target devices · Acceptance dataset · Handover
Applications
Distributed assets. Location-aware workflows.
Twelve application areas show how site locations, monitoring records and operating workflows can be combined. Each task includes its data inputs, proposed output and acceptance check; source quality and map rights determine the implementation scope.
12 application areas / 36 project tasks
Illustrative environments, not evidence of customer installations. Project suitability is assessed against the agreed requirements.
01Water distribution and pumping networks3 +
Give distributed water-service assets a consistent geographic reference without confusing map connectivity with a validated hydraulic model.
Pressure-monitoring district view
+
Review uploaded pressure readings by the mapped monitoring points and the distribution areas defined by the operator.
- Required inputs
- Point coordinates, area boundaries and pressure records.
- Scope & outputs
- District filters with linked point measurements and trends.
- Acceptance checks
- Filtered map, list and counts show the same point set.
- Engineering considerations
- District boundaries and pressure reference come from the owner.
Distributed pump-station events
+
Locate the pumping station associated with a received event and open its available condition records.
- Required inputs
- Station register, equipment IDs and event source data.
- Scope & outputs
- Station event map with source-linked detail panels.
- Acceptance checks
- A test event selects the correct station and source record.
- Engineering considerations
- The map is not a pump control or dispatch authority.
Field inspection site handoff
+
Pass a selected valve, meter or monitored facility reference to the agreed field inspection workflow.
- Required inputs
- Asset locations and authorized inspection-system links.
- Scope & outputs
- Asset detail with the agreed inspection handoff.
- Acceptance checks
- The receiving record retains the selected asset identifier.
- Engineering considerations
- Site access instructions remain maintained by the asset owner.
02Drainage, rivers and catchment monitoring3 +
Organise drainage assets and environmental observations within the geographic areas used by the responsible operating team.
Drainage-point exception map
+
Locate received level or water-leak events around drainage structures and monitored low points.
- Required inputs
- Drainage register, point locations and event definitions.
- Scope & outputs
- Location-linked events with recent measurement history.
- Acceptance checks
- A sample level event resolves to its mapped sensing point.
- Engineering considerations
- An observed level is not a flood forecast.
Catchment observation comparison
+
Compare available rain and water-level records across the stations assigned to a catchment area.
- Required inputs
- Catchment boundaries, station coordinates and time-series data.
- Scope & outputs
- Catchment selection with synchronized observation panels.
- Acceptance checks
- Chosen time periods and source units agree across panels.
- Engineering considerations
- Station placement affects the representativeness of comparisons.
Inspection coverage review
+
Display inspection dates and unresolved source records for the drainage assets in a selected area.
- Required inputs
- Asset IDs, inspection dates and agreed record statuses.
- Scope & outputs
- Area-based inspection layer with record links.
- Acceptance checks
- Displayed coverage totals match the accepted input records.
- Engineering considerations
- Inspection completeness is distinct from infrastructure condition.
03Solar, wind and distributed energy sites3 +
Navigate a regional portfolio while preserving the connection between each site, asset register and received operating information.
Regional site-status overview
+
Filter renewable-energy sites by received event status, monitoring availability or the owner’s operating region.
- Required inputs
- Site coordinates, regional boundaries and source-state definitions.
- Scope & outputs
- Regional map with linked site lists and status counts.
- Acceptance checks
- An agreed filter produces matching map and summary results.
- Engineering considerations
- Displayed status follows the source system’s defined meaning.
Tower and station measurement map
+
Locate monitored towers, inverter stations or supporting equipment and open the available condition records.
- Required inputs
- Asset locations, sensing-point IDs and measurement data.
- Scope & outputs
- Asset details with uploaded readings and history.
- Acceptance checks
- A selected asset retains the correct point identity and units.
- Engineering considerations
- Condition records do not automatically diagnose a fault.
Maintenance-area planning view
+
Group selected service records geographically for review by the responsible regional team.
- Required inputs
- Open service references and assigned operating areas.
- Scope & outputs
- Area-filtered service list with authorized record links.
- Acceptance checks
- Users see only records within their agreed area permissions.
- Engineering considerations
- Optimized routing is a separate analytical scope.
04Telecom towers and remote equipment sites3 +
Put remote site identity, location and available monitoring data in one geographic investigation path.
Tower-site condition investigation
+
Find the site associated with a tilt, environmental or enclosure event and review its source readings.
- Required inputs
- Tower register, point assignments and received monitoring records.
- Scope & outputs
- Tower detail panel with event and trend references.
- Acceptance checks
- A known site event opens its matching measurement source.
- Engineering considerations
- Sensor installation and orientation govern interpretation.
Site communication-status review
+
Distinguish sites with current uploads from those whose reported data is delayed or unavailable.
- Required inputs
- Upload timestamps, site identities and stale-data policy.
- Scope & outputs
- Freshness layer and filtered site list.
- Acceptance checks
- A delayed test record appears in the agreed stale state.
- Engineering considerations
- A missing upload alone does not identify the failure cause.
Contractor visit context
+
Provide authorized visitors with a selected site reference, access notes and the agreed inspection link.
- Required inputs
- Site documents, contractor roles and visit-system references.
- Scope & outputs
- Role-limited site information and inspection handoff.
- Acceptance checks
- Restricted site details remain inaccessible to unassigned users.
- Engineering considerations
- Map access does not authorize physical entry.
05Road, rail and tunnel corridors3 +
Use corridor references and monitored locations together so teams can find the source point behind a received observation.
Corridor monitoring-point lookup
+
Find a monitored point using its asset identifier, chainage or approved geographic position.
- Required inputs
- Corridor alignment, chainage reference and point register.
- Scope & outputs
- Searchable monitoring layer with location details.
- Acceptance checks
- A test point resolves to the agreed corridor reference.
- Engineering considerations
- Coordinate and chainage transformations need a defined reference.
Bridge and tunnel event location
+
Display received movement, vibration or environmental events at their mapped structure or technical facility.
- Required inputs
- Structure inventory, event IDs and point coordinates.
- Scope & outputs
- Structure event map with traceable source records.
- Acceptance checks
- The selected event links to its correct structure and point.
- Engineering considerations
- The dashboard does not certify transport infrastructure safety.
Section-based inspection review
+
Review source inspection records by corridor section and link users to the selected finding.
- Required inputs
- Section boundaries, inspection register and access rules.
- Scope & outputs
- Section filters with document or work-order links.
- Acceptance checks
- Section totals reconcile with the supplied inspection dataset.
- Engineering considerations
- Engineering priorities remain the responsible owner’s decision.
06Construction, slopes and temporary works3 +
Keep measurement points and work-area boundaries aligned as a construction site or monitoring plan changes.
Work-zone monitoring overview
+
Group tilt, vibration or environmental points by the work zones defined for the project.
- Required inputs
- Work-zone boundaries, point register and available channels.
- Scope & outputs
- Zone-selectable monitoring map with source readings.
- Acceptance checks
- The chosen zone returns its agreed monitored point set.
- Engineering considerations
- Zone changes require controlled updates to the data model.
Slope and embankment point context
+
Locate monitoring points and their reference documents along a defined slope or embankment project.
- Required inputs
- Surveyed point locations and installation-reference documents.
- Scope & outputs
- Point map with history and installation-record links.
- Acceptance checks
- Users can trace each displayed point to its source location.
- Engineering considerations
- A point trend is not a stability assessment.
Monitoring-plan revision review
+
Track the geographic effect of added, moved or retired monitoring points in an agreed plan revision.
- Required inputs
- Versioned point schedules and effective-date records.
- Scope & outputs
- Revision comparison with point-state identification.
- Acceptance checks
- The accepted revision reproduces its documented active point set.
- Engineering considerations
- Historical locations must not be silently overwritten.
07Logistics yards, ports and mobile assets3 +
Relate receiving locations, operational zones and reported asset positions using the identity and timing of each source record.
Yard asset-location lookup
+
Find a container, trailer or reusable asset using its last available reported position and identity.
- Required inputs
- Asset IDs, position records and location-quality fields.
- Scope & outputs
- Searchable asset map with last-report details.
- Acceptance checks
- Selected identity, timestamp and location match the input record.
- Engineering considerations
- Last reported location is not a guaranteed current position.
Zone-entry and exit review
+
Scope area events for mobile assets where the available positioning data supports the required zone rules.
- Required inputs
- Licensed zone boundaries, track samples and rule definitions.
- Scope & outputs
- Agreed zone-event view with source-position references.
- Acceptance checks
- Representative boundary cases follow the accepted rule behavior.
- Engineering considerations
- Uncertainty and upload intervals affect boundary-event interpretation.
Dwell and visit-record context
+
Review recorded asset visits or agreed dwell calculations within selected yards or terminal areas.
- Required inputs
- Timestamped positions and visit/aggregation definitions.
- Scope & outputs
- Area-based visit history with traceable calculation inputs.
- Acceptance checks
- Test visits reproduce the documented calculation rules.
- Engineering considerations
- Calculated dwell depends on missing-data and time-gap rules.
08Cold-chain routes and delivery locations3 +
Show where received condition records were associated with a shipment, vehicle or handling location.
Shipment condition-and-location review
+
Review uploaded temperature records alongside the available shipment identity and location history.
- Required inputs
- Shipment IDs, temperature records and position sources.
- Scope & outputs
- Shipment map with time-aligned condition history.
- Acceptance checks
- A chosen record retains its source time, unit and location.
- Engineering considerations
- Separate record clocks and sample intervals need reconciliation.
Delivery-point exception context
+
Locate the reported handling point associated with a shipment condition exception or source event.
- Required inputs
- Delivery locations, event references and handling timestamps.
- Scope & outputs
- Delivery-point event panel and linked source records.
- Acceptance checks
- A sample exception opens its corresponding handling reference.
- Engineering considerations
- The map does not establish product disposition or compliance.
Route-history investigation
+
Display received route positions and selected stops for an agreed investigation period.
- Required inputs
- Position history, route identifiers and retention permissions.
- Scope & outputs
- Time-filtered tracks with recorded stop references.
- Acceptance checks
- Displayed track points match the accepted source dataset.
- Engineering considerations
- Gaps must remain visible rather than inventing a travelled path.
09Agricultural land and irrigation districts3 +
Organise field observations by the parcels, irrigation zones and managed facilities relevant to the farm operator.
Field and parcel monitoring map
+
Review available soil or local weather records against their assigned field parcels.
- Required inputs
- Parcel boundaries, sensor locations and measurement units.
- Scope & outputs
- Parcel selection with point readings and history.
- Acceptance checks
- Selected parcels show only their agreed observation points.
- Engineering considerations
- Point measurements do not establish full-field conditions.
Irrigation-asset location view
+
Locate monitored irrigation tanks, pumps or control equipment and open the available operating records.
- Required inputs
- Irrigation asset register and agreed source interfaces.
- Scope & outputs
- Asset layer with linked condition and service details.
- Acceptance checks
- A source equipment record resolves to the correct map asset.
- Engineering considerations
- Irrigation control is a separately scoped function.
Inspection and seasonal-record context
+
Review observations or service references by growing area and the selected operating period.
- Required inputs
- Area IDs, inspection records and seasonal date definitions.
- Scope & outputs
- Area-based record filters with source-document links.
- Acceptance checks
- The selected period reproduces its agreed record selection.
- Engineering considerations
- Agronomic recommendations require a separate analytical basis.
10Environmental observation networks3 +
Connect sampling locations and station records with traceable map layers and measurement definitions.
Air and weather station network
+
Locate observation stations and inspect the uploaded measurements available at each point.
- Required inputs
- Station register, coordinates and channel definitions.
- Scope & outputs
- Station map with measurement and freshness panels.
- Acceptance checks
- Each displayed channel retains its original source and units.
- Engineering considerations
- Representativeness depends on site exposure and sensor placement.
Water-sampling location records
+
Associate sample or monitoring records with the relevant river, reservoir or discharge location.
- Required inputs
- Sampling-point IDs, coordinates and laboratory/source references.
- Scope & outputs
- Sampling map with source-linked historical records.
- Acceptance checks
- Users can trace a displayed result to its sampling reference.
- Engineering considerations
- A map view is not regulatory monitoring certification.
Area-based event investigation
+
Review received threshold events within an agreed environmental management area and time window.
- Required inputs
- Area boundaries, event definitions and record timestamps.
- Scope & outputs
- Spatial and temporal filters with traceable event details.
- Acceptance checks
- Map, list and exported selection reconcile for the test window.
- Engineering considerations
- Notifications depend on the configured receiving-system workflow.
11Campuses and public-facility portfolios3 +
Give facility teams a shared view of where monitored buildings, equipment and service records belong.
Building-portfolio monitoring map
+
Filter monitored buildings by use, operator region or received environmental event state.
- Required inputs
- Building footprints, ownership fields and event sources.
- Scope & outputs
- Building layers with shared filters and condition panels.
- Acceptance checks
- Filtered building totals agree with the accepted asset register.
- Engineering considerations
- Aggregations need explicit rules for multi-point buildings.
Outdoor utility and lighting assets
+
Locate monitored lighting poles, water-service points or other outdoor assets using the approved register.
- Required inputs
- Asset coordinates, category definitions and source point IDs.
- Scope & outputs
- Searchable facility-asset layer with record drill-down.
- Acceptance checks
- The selected asset opens its correct measurement or service source.
- Engineering considerations
- Installed measurement functions vary with each device.
Mobile maintenance visit information
+
Provide a mobile user with the selected facility’s approved details and inspection handoff.
- Required inputs
- Facility documents, mobile tasks and user-role definitions.
- Scope & outputs
- Mobile-focused detail panel with authorized source links.
- Acceptance checks
- Agreed field tasks remain usable on the target devices.
- Engineering considerations
- Offline operation requires an explicit caching and security scope.
12Parks, tourism and heritage estates3 +
Locate monitored public environments and maintenance assets while controlling access to sensitive facility information.
Heritage-building monitoring locations
+
Find the building or external point associated with a received environmental or movement observation.
- Required inputs
- Building register, point coordinates and monitoring references.
- Scope & outputs
- Estate map with building-level source-record links.
- Acceptance checks
- Each displayed observation maps to its accepted building reference.
- Engineering considerations
- Condition interpretation belongs to the responsible specialist.
Park equipment and environmental stations
+
Review the locations and received records of monitored poles, equipment or environmental stations across a park.
- Required inputs
- Park boundaries, asset register and available station data.
- Scope & outputs
- Category-filtered map with timestamped observations.
- Acceptance checks
- A selected category returns the agreed monitored asset set.
- Engineering considerations
- The map does not imply coverage of unmonitored areas.
Visitor-area maintenance context
+
Link reported service issues to the relevant visitor area and approved maintenance workflow.
- Required inputs
- Visitor-area boundaries and authorized issue-record interfaces.
- Scope & outputs
- Area-based issue view with responsible-team references.
- Acceptance checks
- A test issue opens the correct source record and area.
- Engineering considerations
- Public and internal views need separate information permissions.
Scope & specifications
Project scope. Geography and data together.
Define these items in the project statement of work; this service has no universal fixed specification.
| Service type | Custom geographic dashboard and agreed data integration |
|---|---|
| Coverage and reference | Geographic coverage, coordinate systems and location sources |
| Base maps and layers | Selected provider, permitted usage, attribution and licence costs |
| Source data | Agreed APIs, file inputs, identities, units and timestamps |
| Functions | Views, filters, search and event workflows expressly included in scope |
| User access | Authentication, roles and data permissions agreed per deployment |
| Hosting and operation | Deployment environment, map access and operating responsibilities |
| Verification | Representative locations, records and documented acceptance scenarios |
| Deliverables and rights | Build, documentation and source-code terms as contracted |
| Maintenance | Map-provider changes, data updates and support terms agreed separately |
Integration & handover
From data review. To an operational map.
Confirm how the dashboard will be delivered and maintained.
Review geographic inputs
Inspect sample coordinates, layers and API records before confirming map functions.
Build and verify workflows
Implement the agreed map interactions and test records, permissions and missing-data behaviour.
Document operation
Handover the contracted application and mapping configuration, including licence and maintenance responsibilities.
FAQ
Answers for
your project.
Resolve the technical scope, interfaces and acceptance conditions before committing to a deployment.
What distinguishes a GIS dashboard from a general monitoring dashboard?
A GIS dashboard makes geographic location and operational layers part of the investigation workflow. It connects selected assets or areas with measurements, events and source records; the map, lists and summaries should follow the same data selection.
Can fixed sensors and mobile assets appear on the same map?
They can be scoped as separate layers with their own location sources and timestamp rules. A surveyed sensor position and a last-reported mobile location should remain distinguishable to the user.
Does the dashboard improve positioning accuracy?
No. Accuracy comes from the positioning, survey or other location source. The project defines coordinate transformations and how available quality indicators, uncertainty and stale records are represented.
Can it use our existing map service and asset layers?
They can be reviewed for supported interfaces, coverage, coordinate reference systems, access control and usage rights. Map tiles, commercial services and third-party datasets retain their licence and commercial conditions.
Can Hitelecom Cloud data be used?
An agreed integration can provide uploaded monitoring data and configured threshold events from Hitelecom Cloud. Asset identity, point coordinates, channel definitions, units and timestamps are mapped to the dashboard’s layers.
Can the map display historical routes and condition records?
Where authorized history is available, a project can scope time-filtered tracks and linked measurements. Retention, clock alignment, missing records and any interpolation or aggregation rules are defined before implementation.
Are geofences and dwell-time calculations standard features?
They are project options rather than universal inclusions. Suitable position data, licensed boundaries, uncertainty handling, entry/exit rules and calculation semantics must support the intended use.
How are map alarms and notifications handled?
Events may be received from an existing monitoring platform or generated by an expressly scoped rules service. The project identifies threshold ownership, event status, notification recipients and any acknowledgement or downstream handoff.
Can the map work on a phone or without connectivity?
Mobile layouts are designed around the selected field tasks and target devices. Offline maps or cached records require a separate decision on licensing, storage, data freshness, synchronization and access security.
Can different customers or contractors see different sites?
Access can be scoped by organization, region, site or role. Test the permitted map layers, detail records, exports and source-system links with representative user accounts before acceptance.
What information is needed for a quotation?
Share the coverage area, asset register, sample coordinates, source API or record samples, map preference, user roles and desired workflows. Include expected dataset sizes, retention, target devices and the proposed deployment environment.
What documents and source rights are handed over?
The contract defines the application build, configuration, layer schema, interface mapping, acceptance records and deployment instructions to be delivered. Source-code rights, map licences, third-party costs and support responsibilities are agreed explicitly.
Discuss your project
Define your requirements.
Build the right scope.
Share the sites, geographic layers and records you want to bring together. Include map preferences and sample data so the project scope can be assessed.
sales@hitelecom.cn ↗