An estate of buildings that are nothing like each other, modelled without compromise

How deep does the estate tree go?

There is no imposed level. A location references its parent location and its child locations: the structure is self-referencing, so you can descend from regional directorate to site, to building, to floor, to room, as deep as your estate requires.

The full estate tree is returned in a single call, with or without meters depending on an organisation setting. One search bar finds a site, a meter or a sensor — on an estate of several hundred points, that is what replaces remembering where things were filed.

Can the same estate be read under two different groupings?

Yes, and it is a modelling choice rather than a display trick. Two trees coexist: one geographic and one functional, exposed as two distinct navigation groups. Property navigates by location, the operational side by functional grouping, over the same data.

Each site is then qualified on three independent dimensions: its category, its typology and free-form tags. These reference lists — categories, typologies, energies, units, sensor types, site parameters — are administered by you, with no involvement from Softee.

How do you record floor area, headcount or a target per site?

Through a set of site parameters that you define: you create your own fields — floor area, headcount, year of construction, target — then enter them in bulk in a grid. You are not tied to a fixed schema that decided on your behalf which attributes a building has.

A site’s address is geocoded to latitude and longitude, which feeds two things: the map view of the estate, from which a site’s detail opens, and the link to a weather station, which is what makes climate correction possible. Geocoding goes through Nominatim / OpenStreetMap.

And the single meter feeding three buildings?

This is the case most monitoring spreadsheets cannot hold, and it is handled by three distinct mechanisms depending on the nature of the problem.

What does reporting at estate scale look like?

A matrix and a ranking. The sites × indicators matrix gives one row per site — with its category and typology — one column per indicator and the unit of each: this is the view that answers “which of my forty buildings are out of line”.

The estate summary adds the ranking of the best- and worst-performing sites in kWh/m², performance by energy, the energy mix, and a year N / N−1 / N−2 table carrying each site’s target and the estate total. All of it switches between a rolling twelve months and the calendar year.

What this page does not claim

• No maximum number of sites, meters or measurement points. Nothing in the code bounds or proves a volume, so we publish no capacity figure — and we do not draw the opposite argument either: the absence of a bound in the code is not evidence that the product holds a given load.
• No automatic import of your existing model. Set-up goes through an onboarding workbook validated as a dry run, described on the data collection page. There is no import that would infer your tree from an arbitrary spreadsheet.