Collect
Read a live sensor, poll a local gateway, accept a connected source or import historical logger data.
Identity and observed timestamp stay with the reading.From measurement to environmental record
A reading arrives one way. Its meaning comes from everything around it.
LÆFAN keeps acquisition separate from interpretation. A Zigbee sensor, imported Tinytag file or weather reference can all enter by different routes, then join the same location, profile and evidence model.
01 · SOURCESensors & loggersZigbee · BLE · UniFi · files
→02 · ROUTEEdge · central · importKeep provenance intact
→03 · CONTEXTPlace & expectationLocation · profile · campaign
→04 · EVIDENCEAlert · response · historyA record that still makes sense later
The LÆFAN flow
Five steps, with a clear job at each one.
The platform does not make the collector responsible for conservation decisions, and it does not make the central server pretend every device is connected in the same way.
Normalise
Convert the source into a common measurement record while retaining where it came from.
Source provenance is not thrown away.Place
Associate the reading with a sensor, monitoring point, room, case, store or other location context.
Cases and rooms can also be related to each other.Interpret
Apply the relevant Environmental Profile, campaign or monitoring context centrally.
The same sensor history can be interpreted correctly as context changes.Retain evidence
Keep excursions, acknowledgements, investigations, spot samples and reports alongside the history.
Operational faults remain separate from environmental excursions.Different routes in
Use the route that suits the source.
ON SITELocal collector
Zigbee or Bluetooth LE
Sensor→LÆFAN Edge→LÆFAN
Useful where the source needs local collection on the museum network. Edge collects and buffers; the main platform remains the system of record.
CENTRALConnected source
Weather reference or UniFi
Source/API→LÆFAN
Where a source can be reached centrally, there is no reason to route it through an Edge appliance just for architectural symmetry.
HISTORICALData import
Tinytag TTD / CSV
Logger file→Import mapping→LÆFAN
Standalone logger history can join the same sensor and location record without pretending it was continuously connected.
A deliberate boundary
Local acquisition. Central interpretation.
What stays local
- Hardware and LAN access
- Protocol-specific collection
- Short-term resilient buffering
- Collector health and diagnostics
- Secure outbound forwarding
HTTPS→outbound
What stays central
- Environmental Profiles
- Locations and relationships
- Excursion and alert logic
- Campaigns and Monitoring Plans
- Reports and long-term evidence
Why that matters
The acquisition route can change without rewriting the collection model.
If an organisation replaces a standalone logger with a connected sensor, the underlying conservation context should not have to be reinvented. LÆFAN keeps device integration separate from the locations, profiles and evidence that give the data meaning.
EXAMPLERoman Gallery
- Place
- First Floor · Main Site
- Profile
- General Display
- Current source
- Zigbee RH/T sensor
- Previous history
- Imported logger readings
One environmental history, even though the acquisition method changed.