GHT: Glass House Technologies
GHT service / Operational systems

Environmental monitoring

Sensors that notice trouble and know whom to tell

Sensors, placement, gateways, power, network, timestamps, thresholds, persistence, alerts, acknowledgement, escalation, retention, and maintenance, assembled as one monitoring system.

What you should have at closeoutCondition data with known units and location, tested thresholds, working alert and escalation paths, stale-data detection, and maintenance records.
References3 reviewed
Last updated2026-08-20
Overview

What Environmental monitoring includes

Environmental monitoring is a chain: measurand, sensor, placement, sampling, gateway, timestamp, transport, storage, threshold, alert, acknowledgement, escalation, action, and record. A dashboard alone does not create an operational response.

Sensors should be placed for the protected process rather than convenience. Required accuracy, calibration, mapping, validation, redundancy, and record controls vary by use; regulated or safety-critical environments need discipline-specific requirements.

Question to answer before designWhich condition requires action, how long must it persist, who responds, and how will the sensor and alert path be tested?
Common situations

This service may fit when:

  • Equipment or product damage is discovered after the condition has passed
  • Alerts are frequent, ignored, misrouted, or lack acknowledgement and escalation
  • Sensors are mounted where installation is easy rather than where risk occurs
  • No one tracks calibration, batteries, gateway health, time, or last successful test
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Measure

Condition, range, accuracy, location, sensor, calibration assumption

02

Collect

Sampling, gateway, time, network, power, buffer, health state

03

Interpret

Units, threshold, persistence, hysteresis, trend, stale or invalid data

04

Respond

Notification, acknowledgement, escalation, action, work record, retention

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Protected asset or process, condition, range, accuracy, location, time, and consequence
  • Normal variation, thresholds, persistence, hysteresis, schedule, and rate of change
  • Sensor environment, mounting, calibration, battery, gateway, network, power, and time source
Design decisions

What those findings determine

  • Sensor model: Choose from accuracy, environment, wiring, power, update rate, battery, and maintenance.
  • Threshold: Use the simplest rule that detects risk without generating unowned noise.
  • Response: Automation should never imply a response unless completion is independently recorded.
Closeout records

What you should receive

  • Condition, threshold, response, and ownership matrix
  • Sensor, placement, gateway, network, power, and data-flow plan
  • Baseline, threshold rationale, and configuration record

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Define condition and consequence

    Identify what is protected, measured condition, range, accuracy, location, time sensitivity, persistence, consequences, response owner, maintenance, and record need.

    EvidenceCondition-response matrix, site observations, current incidents, measurement requirements, and ownership list.
  2. 02

    Design measurement and alerting

    Select sensors, placement, mapping, gateways, network, power, time, sampling, thresholds, hysteresis, persistence, notifications, acknowledgement, escalation, and retention.

    EvidenceSensor and gateway plan, data-flow diagram, threshold rationale, alert matrix, maintenance schedule, and validation method.
  3. 03

    Install and baseline

    Label and place sensors, configure units and timing, establish users and routes, compare readings where appropriate, and observe normal variation before final thresholds.

    EvidenceAsset and placement photos, configuration record, baseline trend, comparison observations, and alert contacts.
  4. 04

    Exercise condition and failure

    Safely simulate or test threshold, persistence, alert, acknowledgement, escalation, sensor loss, low battery, gateway loss, power loss, stale data, recovery, and reporting.

    EvidenceEnd-to-end alert samples, timestamps, acknowledgement and escalation record, stale-data alarm, recovery result, and owner runbook.
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
Sensor modelTypical approach: Wireless battery sensorMore demanding conditions: Wired or industrial sensor through a managed gatewayWhat determines the choice: Choose from accuracy, environment, wiring, power, update rate, battery, and maintenance.
ThresholdTypical approach: Fixed high and low limitMore demanding conditions: Persistence, hysteresis, schedule, rate-of-change, or correlated conditionWhat determines the choice: Use the simplest rule that detects risk without generating unowned noise.
ResponseTypical approach: Email or app notificationMore demanding conditions: Acknowledgement, escalation, work order, or approved control interfaceWhat determines the choice: Automation should never imply a response unless completion is independently recorded.
EvidenceTypical approach: Current value and trendMore demanding conditions: Quality, calibration, event, acknowledgement, action, and audit recordWhat determines the choice: Match evidence controls to operational, contractual, and regulatory need.
Before design

What we need to know

  • Protected asset or process, condition, range, accuracy, location, time, and consequence
  • Normal variation, thresholds, persistence, hysteresis, schedule, and rate of change
  • Sensor environment, mounting, calibration, battery, gateway, network, power, and time source
  • Recipients, acknowledgement, escalation, after-hours coverage, response target, and work ownership
  • Data units, quality, retention, export, privacy, integration, reporting, and maintenance
At closeout

What you should receive

  • Condition, threshold, response, and ownership matrix
  • Sensor, placement, gateway, network, power, and data-flow plan
  • Baseline, threshold rationale, and configuration record
  • End-to-end condition, stale-data, communication, power, escalation, and recovery evidence
  • Asset list, maintenance and calibration assumptions, alert runbook, and reporting guide
Equipment examplesSee relevant hardwareView details
Best fit

When this service makes sense

  • Network rooms, warehouses, healthcare support areas, facilities, utilities, and industrial spaces
  • Conditions with a defined threshold and response owner
  • Sites that can support representative placement and maintenance
  • Multi-site teams that need consistent naming, alerts, and retained evidence
Before we commit

What we verify first

  • Monitoring does not by itself control the condition or guarantee that a person responds
  • Accuracy, calibration, placement, sampling, drift, condensation, interference, batteries, and connectivity affect data quality
  • Regulated storage, clinical, food, industrial, environmental, or safety applications can require validated procedures and records beyond general facility monitoring
  • Coverage windows, response targets, and escalation are contract- and owner-specific and must be documented explicitly
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Where should temperature sensors be placed?

At representative risk locations determined by the protected equipment or process, airflow, heat sources, doors, exterior surfaces, vertical gradients, and known hot or cold zones, not simply beside the gateway.

How are nuisance alerts reduced?

Validate placement and sensor health, observe a baseline, then set rational limits with persistence, hysteresis, schedules, maintenance alerts, ownership, acknowledgement, and escalation.

Does monitoring include an after-hours response?

Only when the contract and owner procedure state the coverage window, recipients, acknowledgement, escalation, response target, authority, and fallback. A sensor subscription alone does not define a response service.

Standards and referencesReview the source materialView details