LÆFAN / Deployment

Deployment without turning the museum into an IT project

Keep local collection local. Keep the environmental record central.

LÆFAN is deployed per organisation. Where a source needs local network, radio or hardware access, LÆFAN Edge provides a small acquisition layer rather than putting another full application server inside the museum.

MUSEUMSensorsLocal gatewaysBuilding systems
→
ON SITELÆFAN EdgeCollect · buffer · forward
→
LÆFANEnvironmental recordContext · alerts · evidence

The deployment model

Use Edge only where it earns its place.

Some sources need an appliance on the museum network. Others do not. LÆFAN deliberately supports both routes.

EEDGE NEEDED

Local systems or network access

Use LÆFAN Edge when environmental data needs to be collected locally from supported devices, gateways or building systems on the museum network.

  • Zigbee and Bluetooth LE
  • Tinytag Connect as the collector is developed
  • Modbus/CAN and later local protocols
CNO EDGE REQUIRED

Central source or file import

Do not add an Edge appliance where the source can be collected centrally or imported safely through the application.

  • Reference weather sources
  • Supported connected APIs
  • Tinytag TTD / CSV and mapped CSV

LÆFAN Edge

A managed local collector, not a second LÆFAN server.

MANAGED APPLIANCESupplied as part of the LÆFAN deploymentThe client only needs to provide the agreed network, power and source access. Internal appliance design remains managed by Beyond1066.
01

Connect

Connect to the supported local source and collect its readings.

02

Normalise

Package the measurement with source identity, observed time and the information needed by central ingestion.

03

Buffer

Keep a durable short-term queue if the main server cannot be reached, then retry without changing the observed timestamp.

04

Forward

Send data to LÆFAN over a secure outbound connection and report collector/appliance health.

Network boundary

No inbound Edge firewall rule is part of the normal design.

The museum appliance initiates the connection out to the main LÆFAN platform. Local source credentials stay with the collector where practical, while the central platform receives normalised readings and health information.

✓

Outbound connectionNo requirement to expose the Edge appliance to the public internet for routine collection.

✓

Small attack surfaceEdge is not a general remote terminal or second copy of the application.

✓

Source credentials kept narrowCollectors only need the access required for their source.

TYPICAL FLOW
Local sensor / gatewayLAN / radioLÆFAN Edge
HTTPS outbound
LÆFAN serverclient-specific deploymentEnvironmental record

Exact network design and security controls are agreed for the client environment rather than assumed by a marketing page.

When the internet goes away

Keep collecting. Catch up when connectivity returns.

10:02Normal collectionReadings forwarded to LÆFAN
→
10:17Connection unavailableEdge keeps readings in its local queue
→
10:43Connection restoredQueued readings are forwarded with original observed times

The Edge buffer is resilience for collection, not a substitute for the central long-term environmental database.

What museum IT needs to know

The deployment conversation should be straightforward.

01

Network routeCan the required local source be reached from the proposed Edge network segment?

02

Outbound accessCan Edge reach the LÆFAN service over the agreed secure outbound route?

03

Source accessWhat approved credentials or local access does LÆFAN Edge need for the source?

04

Power & placementWhere will the managed appliance be installed and powered?

05

Support boundaryWho owns the source system, museum network and LÆFAN appliance respectively?

Deployment is client specific.

The diagrams describe the intended LÆFAN architecture, not a promise that every museum network is identical. Final firewall, identity, backup, update and recovery arrangements should be agreed against the organisation's own IT policies and the sources being connected.

Fit it to what you already have

See which sources need Edge, which connect centrally and which arrive by import.

Open Integration CheckerTalk through deployment