LÆFAN / Buyer's guide

Practical buyer's guide

Choosing a museum environmental monitoring system.

A practical checklist for comparing hardware, software, support and long-term evidence without reducing the decision to sensor accuracy alone.

WHAT TO COMPARE
  • Collection context
  • Sensor & logger compatibility
  • Calibration & reference checks
  • Alerts & response
  • Data ownership & migration
  • Reporting & evidence
  • Support & training
  • Hosting & deployment

Start with the outcome

What should the system help the collections team know or do?

Before comparing radio protocols or logger specifications, define the monitoring questions: which spaces matter, which parameters matter, how staff respond to excursions, what evidence is needed later and what existing history must be retained.

01

Collection context

Can different spaces have different expectations?

A display case, archive store and historic room may need different monitoring logic. Avoid systems that force one estate-wide threshold where the collection context is more nuanced.

  • Can limits or expectations vary by room or case?
  • Can temporary exhibitions or loans have their own context?
  • Can the system explain why an environment is flagged?
02

Existing equipment

What can you keep?

Most museums already have loggers, sensors and years of historical data. Replacement costs should be justified by genuine benefit, not by a closed software ecosystem.

  • Can existing logger files be imported?
  • Which connected sensors and gateways are supported?
  • Can manual readings remain part of the record?
03

Calibration & sensor quality

How is sensor confidence evidenced?

Look beyond a simple calibrated/not-calibrated badge. The system should retain certificates, due dates and the history behind any correction or reference check.

  • Can calibration certificates be retained?
  • Can calibration due dates be monitored?
  • Can a non-calibrated sensor be field-compared without falsely being labelled calibrated?
04

Alerts

What happens after the notification?

An email is not an investigation record. Look for persistence, acknowledgement, escalation and a retained response.

  • Can short-lived excursions be handled differently from sustained ones?
  • Are sensor failures distinct from environmental excursions?
  • Can the investigation and recovery be retained?
05

Reporting & evidence

Can someone understand the graph six months later?

Reports are stronger when they retain the context that generated them, including the profile, excursions, checks and response.

  • Are PDF and data exports available?
  • Can temporary loan periods be reported separately?
  • Is the audit trail retained?
06

Migration & data ownership

Can you bring your history in and take your data out?

Environmental records can be valuable over many years. Avoid a system where useful history is trapped or migration becomes impractical.

  • How is existing history imported?
  • What happens if you later change supplier?
  • Can raw and corrected values remain traceable?
07

Deployment & security

What does museum IT actually need to provide?

Understand local appliances, outbound connectivity, data hosting and support boundaries before procurement.

  • Is an on-site appliance required?
  • Are inbound firewall rules needed?
  • Where is the data hosted?
08

Support, training & lifecycle

Who helps after installation?

Monitoring systems last longer than a procurement exercise. Support, calibration, training and documentation should be considered part of the solution.

  • What support route is provided?
  • How are software and appliances maintained?
  • Can staff training and handover be included?

Shortlist scorecard

A simple way to compare suppliers.

Collection-specific profilesExisting-data migrationCalibration historyAlert investigation workflowLoan/exhibition monitoringManual observationsData exportSupport & trainingUK deployment requirementsEvidence & audit trail

Compare LÆFAN against your requirements

Bring us your existing monitoring setup.

We can work through the equipment, history, rooms, reporting and support requirements you already have.