Service territories
Group locations into recognizable operating areas and regional planning scopes.
Territories & geofencing
Flowtlas combines reusable operational territories with geofencing for configured subjects and trusted position sources, keeping planning scope and spatial events distinct.
The operational problem
A service territory groups locations for responsibility and planning. A geofence evaluates position updates against a spatial boundary and records what occurred.
Flowtlas keeps both concepts available without assuming that a drawn boundary automatically restricts every route or that every position source is trusted.
Product capability
Group locations into recognizable operating areas and regional planning scopes.
Configure geofence geometry for supported operational zone types.
Evaluate updates from registered, trusted position sources for supported subjects.
Record entry, exit, dwell and speed-exceeded events with configured retention.
Practical workflow
Create the territory or geofence required by the operation.
Use a supported subject type and configured position source.
Compare trusted updates with the configured geometry.
Inspect retained entry, exit, dwell or speed events.
Operational benefits
In practice
A configured vehicle position source reports that a supported subject entered a customer-site geofence and remained there long enough to meet the dwell rule.
The resulting events support operational review. They do not by themselves prove that every service task was completed; completion evidence is handled separately.
Questions
No. A territory groups operational scope, while a geofence evaluates positions against spatial geometry.
The platform defines entry, exit, dwell and speed-exceeded events for configured subjects and sources.
No. Planning restrictions depend on the jobs, resources and rules supplied to the planning workflow.
Work with operational context