Features
The in-depth page, for environmental and information technology evaluators.
Web portal
What carries the authorizations, the work plan and the proof of compliance.
01 · Authorizations
Each authorization carries its versions, its dates and its linked requirements. The version in force is locked and any change creates a new version, so you always know which condition applied on which date.
02 · Requirements
A requirement knows its regulatory source, its threshold, its frequency and the stations that serve it. Assisted extraction, mandatory human validation.
03 · Tasks and campaigns
Requirements generate recurring tasks or one-off campaigns, each with an owner and a due date. Four views of the same plan.
04 · Map and inventories
Stations, wells, outfalls and zones on a map linked to the requirements. Click a point to see its measurements and its status.
05 · Dashboards
By site, by zone, by due date. The figures come from measurements already entered; nobody rebuilds a spreadsheet the night before the filing.
06 · Events and declarations
A spill reported from the field starts the regulatory clock, opens the corrective tasks and feeds the declaration.
Mobile app
What the technician uses at the measurement point, wearing gloves, with or without a network.
01 / 06
Zones, layers and measurement points are downloaded before the round. The technician sees where they are, what they need to record and why.
Basemaps, satellite view and layers by sector: what is useful in the field, nothing more.
02 / 06
All the site's biodiversity observations: plant and animal species, counts, plots and campaigns, filterable by group and by status.
Species with special status stand out on their own, and each observation keeps its position, its photos and its history from one campaign to the next.
03 / 06
Group, species, count, habitat, position and photos: the observation is entered according to the campaign protocol, at the exact point where it is made.
Offline, it is queued and syncs as soon as the network returns.
04 / 06
Campaigns and the recurring tasks generated by the requirements land directly in the technician's list.
Each task carries its due date, its sector and the form that completes it.
05 / 06
The form expects the right answer format: numeric value, choice, list, free text, photo or signature.
The station ID, date, time and position fill themselves in.
06 / 06
Stations, wells, outfalls and infrastructure: each entity carries its attributes and its reading history.
One button shows the entity on the map, so you can head there.
The full cycle
The calculation engine
Monthly averages, composite samples, instantaneous values, loads, percentiles and conditional criteria are applied according to each regime's own rule. Room remains for the client's own algorithms, when the calculation goes beyond the standard framework. Every result keeps a trace of the data and the rule that produced it, so your team can check it before signing it.
Field and reporting
Offline entry at the measurement point, sync when the network returns, then the templates expected by the authorities are filled in. No re-entry in between.
Security and data
Multi-region storage.
No mixing between environments.
On a need-to-know basis.
Restores are tested.
Conducted outside the development team.
The process is under way; certification has not been obtained.
The data belongs to the client, in standard formats, retrievable with no dependence on the vendor.