Plan.
Bring together the project’s geographical information and define routes and work areas.
The map is part of the project. Connect routes, work areas and documentation to the same reality as planning and delivery.
GEO starts with a simple idea: a point can represent a cabinet or inspection point. A line can represent a utility route. An area can represent a work zone or reinstatement.
Planned and actual geometry are kept separate, making it possible to understand both the intention and what was actually completed.
Schematic illustration of the workflow, not a screenshot of the map service.
Bring together the project’s geographical information and define routes and work areas.
Connect work orders and tasks to the location where the work will happen.
Track completed work, geometry and supporting records in the project.
Understand the difference between plan and outcome to support reviews and next steps.
Groundworks, civil engineering, electrical networks, water, construction and property also involve work areas, quantities and documentation. GEO’s structure is based on project geometry and work activities.
Show us your maps, drawings and geographical files. During the demo, we review the formats and workflows supported in the current version.
GEO development focuses on importing geographical information, field workflows and the link between planning and actual execution. Support for formats such as KML and CAD/GIS is confirmed for each version and delivery.
No external map service is loaded in this page’s illustration. It demonstrates the GEO concept, not a verified production environment.
Tell us how you work. We show Lillox around your projects, your roles and what you want to get a better handle on.
A personal walkthrough with Mikael Venevi.
We agree on scope, onboarding and pricing together.