Territories & geofencing

Connect Service Areas with Trusted Position Events

Flowtlas combines reusable operational territories with geofencing for configured subjects and trusted position sources, keeping planning scope and spatial events distinct.

The operational problem

Planning areas and live spatial events solve different problems

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

Territories and geofence events in one operational model

01

Service territories

Group locations into recognizable operating areas and regional planning scopes.

02

Spatial zones

Configure geofence geometry for supported operational zone types.

03

Position evaluation

Evaluate updates from registered, trusted position sources for supported subjects.

04

Event history

Record entry, exit, dwell and speed-exceeded events with configured retention.

Practical workflow

From spatial configuration to reviewable events

  1. 1

    Define the area

    Create the territory or geofence required by the operation.

  2. 2

    Register the subject

    Use a supported subject type and configured position source.

  3. 3

    Evaluate positions

    Compare trusted updates with the configured geometry.

  4. 4

    Review events

    Inspect retained entry, exit, dwell or speed events.

Operational benefits

Benefits of explicit spatial operations

  • Reusable service-area definitions
  • Traceable spatial events
  • Configurable subject and source types
  • Clear separation between planning scope and event detection

In practice

Example: arrival and dwell at a service site

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

Frequently asked questions

Is a territory the same as a geofence?

No. A territory groups operational scope, while a geofence evaluates positions against spatial geometry.

Which geofence events are supported?

The platform defines entry, exit, dwell and speed-exceeded events for configured subjects and sources.

Do zones automatically restrict route planning?

No. Planning restrictions depend on the jobs, resources and rules supplied to the planning workflow.

Work with operational context

See how Flowtlas can support your operational setup.

Back to top