Operational map layers
Display relevant operational and external GIS information together.
Mapping, geofencing & tracking
Put operational information on the map
MMOPS mapping uses an extensible OpenLayers-based workspace for operational features, saved shapes, geofences, asset locations and route-related workflows.
Mapping, geofencing & tracking
Who it is for
Built around the operation, not a disconnected app
Operations that need spatial context around sites, assets, transport routes, zones, stockpiles, facilities and work areas.
Draw & edit features
Create polygons, circles, rectangles, images and custom operational shapes.
Geofences
Store operational zones and use them in location-aware workflows.
Asset tracking context
Display asset positions and connect them with operational records where tracking is configured.
Saved shapes
Maintain reusable shapes globally or by organisation / client context.
Routing integration
Use the map as the visual workspace for routing and route-assessment services.
Connected workflow
How the information flows
MMOPS is designed so operational records can move through the business instead of being captured repeatedly in separate systems.
Load relevant base / GIS layers
Draw or load operational features
Store geofences and feature properties
Overlay assets / routes
Use spatial events in operational workflows
MMOPS platform
Related capabilities
The value of MMOPS is that these functions can share the same people, assets, projects, organisations and operational records.
Common questions
Mapping & Geofencing FAQs
Does MMOPS use OpenLayers?
The MMOPS mapping workspace is built around OpenLayers and is extended for operational requirements.
Can custom shapes and geofences be stored?
Yes. The mapping design supports saved operational features and geofencing workflows.
Main Menu Systems • Perth, Western Australia
See how MMOPS fits your operation
We can tailor a demonstration around the processes you actually run, including the surrounding MMOPS modules and integrations.