Example Temperature Monitoring Standard Operating Procedure

Use this editable example as a starting point for a controlled procedure covering temperature monitoring, calibration, alerts, user access, incident records, and audit reporting.

Example Template — Review Before Use

This page is an example only. It is not an approved SOP for any specific organisation, site, product, regulatory framework, or monitoring installation.

Copy and revise the content to match your equipment, operating limits, escalation process, staff responsibilities, document-control system, validation requirements, and record-retention policy. The final procedure should be reviewed and approved through your organisation's quality management process before it is issued or used for training.

Document ID [SOP-TEMP-001]
Version [1.0]
Effective date [DD Month YYYY]
Review date [DD Month YYYY]
Document owner [Role or department]
Approved by [Name and role]
Applicable site [Site or department]
Controlled copy location [Document system or path]

1 - Purpose

This SOP defines the routine operation and administration of a cloud-connected temperature monitoring system using Telemetry2U. Its purpose is to support consistent monitoring, timely response to alarms, controlled configuration changes, reliable record keeping, and traceable review of temperature events.

The organisation should replace this example purpose with a statement that identifies the monitored products, rooms, equipment, or processes and the quality or regulatory objective the monitoring system supports.

2 - Scope

This procedure applies to:

  • Temperature and humidity sensors installed at the nominated site.
  • LoRaWAN gateways and associated internet connections used to transfer monitoring data.
  • Telemetry2U user accounts, dashboards, reports, alerts, annotations, and audit records.
  • Staff responsible for system administration, monitoring, alarm response, quality review, and maintenance.

Record excluded systems, locations, or processes here: [List exclusions or enter “None”].

3 - Responsibilities

System Owner

Maintains the approved system configuration, authorises significant changes, confirms that user access remains appropriate, and coordinates technical support.

Quality or Compliance Representative

Reviews calibration and verification records, assesses excursions and deviations, confirms required records are retained, and approves the controlled SOP.

Authorised Users

Monitor assigned devices, respond to alerts, enter complete annotations, protect their account credentials, and report faults or unexplained data promptly.

4 - Equipment and System

The following equipment list reflects one example deployment and must be updated to match the installed hardware and approved configuration.

Example Field Equipment

  • Dragino LHT65N temperature and humidity sensor.
  • Dragino LTC-LT/SI RTD temperature sensor.
  • Dragino LPS8N LoRaWAN gateway.
  • [Add installed buffers, probes, power supplies, and accessories]

Monitoring Software

Telemetry2U is a cloud-based monitoring interface available through https://telemetry2u.com from an authorised internet-connected device. The approved account configuration may include dashboards, alert rules, notification groups, reports, audit reports, annotations, scheduled jobs, and user-access controls.

System Data Flow

Sensors measure temperature or related conditions and transmit data to a LoRaWAN gateway. The gateway forwards the received data through its internet connection to the platform, where authorised users can review current values, historical records, alerts, annotations, and reports.

5 - Calibration and Verification

5.1 - Initial Calibration

Temperature sensors should be calibrated or verified by a competent laboratory at the points required by the application. Where NATA-accredited calibration is required, confirm that the selected laboratory's scope of accreditation covers the measurement and range.

Calibration certificates and associated device records should be retained in the approved document system. Where the platform's document or calibration functions are used, authorised users may also make certificates available through the relevant administration pages.

5.2 - Periodic Verification

Perform periodic in-situ verification at a frequency justified by risk, historical stability, manufacturer guidance, and regulatory or quality requirements. A typical verification compares the installed sensor with a suitable reference thermometer at or near the normal operating temperature.

Define the acceptance tolerance, stabilisation time, method, authorised personnel, and response to an out-of-tolerance result before the verification is performed.

5.3 - Temperature Sensor Buffers

Where appropriate, place the sensing probe in a suitable thermal buffer to reduce short-duration changes caused by door opening or automatic defrost cycles. The buffer should represent the thermal response of the monitored product or process without concealing a genuine excursion.

Record the approved buffer type, fill material, volume, probe position, and any validation or comparison used to justify it: [Insert site-specific buffer details].

6 - Data Integrity and Compliance Controls

Where the organisation requires electronic-record and electronic-signature controls, enable and configure the relevant Telemetry2U features as part of the validated system configuration. Access should be role-based, significant changes should require authorised credentials where configured, and audit records should be reviewed according to the approved quality process.

Users must not share accounts or passwords. Each person should use an individual account so that configuration changes, annotations, acknowledgements, and signatures can be attributed correctly.

Access and Change Control

Assign only the roles needed for each person's duties. Review access periodically and remove access promptly when a user's responsibilities change or employment ends.

Audit and Record Review

Retain relevant audit reports, annotations, calibration records, and approval evidence. Define who reviews these records, how often review occurs, and how discrepancies are investigated.

7 - Operating Procedure

The system may be supplied with users, dashboards, alert rules, notification groups, and reports already configured. Authorised users should follow the controlled steps below when changes are required.

7.1 - Managing the LoRaWAN Gateway

End users should not change network-server, radio, or gateway settings outside the approved configuration. The following administrative fields may be available to authorised users:

  1. Open Gateway and Network > Add / Edit LoRaWAN Gateways and select Edit beside the required gateway.
  2. Update the approved gateway name in the Description field if required.
  3. Confirm the approved offline-notification delay and notification group. The previous example used five minutes; replace this with the validated value for the site.
  4. To review connectivity, open Gateway and Network > View Gateway Status and check the Last Receive Time and other status information.
  5. If the gateway is offline, follow the approved site troubleshooting process. Where power cycling is authorised, disconnect power for the approved period before reconnecting it.
  6. Escalate persistent faults through the organisation's approved support channel or the platform support contact page.

7.2 - Managing Temperature Sensors

  1. Open Nodes and Devices > Add / Edit End Devices and select Edit beside the required node or sensor.
  2. Update the approved sensor name in the Description field if required.
  3. Confirm the approved offline-notification delay and notification group. The previous example used 65 minutes; the correct value should account for the normal reporting interval and acceptable detection delay.
  4. If a sensor is offline, follow the model-specific reconnection procedure. Record the approved reset method here: [Insert device-specific procedure].
  5. Where the installed sensor supports local data logging, confirm how records are stored during an outage and how they are recovered after communications return.
  6. To send an approved device command, open Nodes and Devices > Send Downlink Command, select the node and command, then select Send. Confirm the result after the next uplink.

7.3 - Inviting New Users

  1. Open the User Maintenance index in the administration area and select Create New User.
  2. Complete the approved user details. Enter alert phone numbers in international format, including the country code.
  3. Select Create after checking the entered information.
  4. The user receives an invitation to set a password and verify their details. Do not assume the user can view sensor data until access has been assigned under Section 7.4.
  5. Instruct the user to review their profile and notification contact details after signing in.

7.4 - Configuring User Access and Permissions

  1. Open the User Maintenance index in the administration area and select User Access for the required user.
  2. Assign only the approved roles under User Roles.
  3. Under Node Access Control, select the sensors the user is authorised to view. Confirm how any broad access role, such as All Nodes, affects these selections.
  4. Select Save.
  5. Record or approve the access change according to the organisation's access-control process.

7.5 - Managing Notification Groups

  1. Open Add / Edit Notification Groups in the administration area.
  2. Select Create a New Notification Group for a new group, or select Edit beside an existing group. Enter an approved group name and select Save.
  3. Select Members for the notification group.
  4. Select the users who should receive alerts and the permitted delivery methods.
  5. Set the approved day range for each recipient.
  6. Set the approved time range for each recipient.
  7. Select Save and test the escalation path where required.

7.6 - Configuring Alerts

  1. Open Add / Edit Alerts and Conditions in the administration area.
  2. Select Create New Alert Group or select Edit beside an existing group.
  3. Set the alert group's Active state.
  4. Enter an approved Description and active time range.
  5. Under Include Notification Groups, select the approved recipients and confirm whether recovery notifications are required.
  6. Add each monitored node required by the alert group.
  7. For each condition, select the Input, Comparison, and validated Threshold.
  8. Set the required number of Consecutive Readings.
  9. Set the approved Minutes Between Alerts.
  10. Confirm the condition's Send on Recovery and Active settings.
  11. Select Save.
  12. Test the alert, notification, recovery, and escalation workflow according to the approved commissioning or change-control protocol.

7.7 - Adding Annotations to Alert Events

  1. Open the Reports page.
  2. Select the relevant node and locate the alert or recovery record.
  3. Select the warning or annotation control associated with the record.
  4. Enter a factual annotation describing the event, investigation, action taken, result, and any linked deviation or maintenance record.
  5. Select Save.
  6. Edit an annotation only in accordance with the organisation's record-correction process.

7.8 - Creating and Editing Audit Reports

  1. Open Audit Maintenance > Add / Edit Audit Reports.
  2. Select Create Audit Report or select Edit beside an existing report.
  3. Enter the approved Site Name, Report Name, and Time Zone.
  4. Select the information that must be included in the report.
  5. Add each required node using Add Node.
  6. Select the relevant Sensor Input and enter the approved upper and lower chart limits.
  7. Select Save.
  8. Generate and review a sample report after creating or materially changing the configuration.

7.9 - Emailing Audit Reports Automatically

  1. Open Audit Maintenance > Create Audit Report Schedule.
  2. Complete a new schedule, or open an existing schedule for editing.
  3. Enter an approved job Description.
  4. Select the required Notification Group.
  5. Select the audit report under Item to Run.
  6. Configure Run Frequency, Run On, and Run at Time using the site's approved time zone and reporting schedule.
  7. Select Enabled, then select Create. Confirm successful delivery at the next scheduled run.

7.10 - Managing Dashboards

  1. Open the Dashboard page after signing in.
  2. Select the required dashboard using Dashboard Name.
  3. Users with the approved dashboard-editing role may create, rename, or delete dashboards and toggle editing mode.
  4. Use the Company Wide setting only where the dashboard is intended for all authorised company users.
  5. Check widget names, units, inputs, limits, and layout before the dashboard is released for use.

7.11 - Copying a Dashboard to Another User

  1. Open the Copy Dashboard page in the administration area.
  2. Select the source dashboard in the first Dashboard Name field.
  3. Select the destination user under Person.
  4. Enter the approved dashboard name in Destination name.
  5. Select Save.
  6. Ask the destination user to review the copied dashboard and confirm access to each displayed node.

8 - Alarm, Outage, and Deviation Response

Replace the example workflow below with the organisation's approved response process, including escalation time limits and responsibility for product or process disposition.

Acknowledge

Confirm receipt of the alert and identify the affected sensor, location, and monitored asset.

Assess

Check the current reading, recent trend, equipment condition, reference indication, and local circumstances.

Act and Escalate

Take the approved corrective action and escalate when limits, response times, or product-risk criteria are exceeded.

Document and Review

Enter a complete annotation and create any required deviation, maintenance, investigation, or disposition record.

Communication or Power Outage

  • Confirm whether the fault affects one sensor, one gateway, the local network, or the wider service.
  • Use an approved independent check when required to confirm the monitored condition during the outage.
  • Do not assume that buffered or locally logged data is available unless the installed device has been verified to support it.
  • Review recovered records after service returns and investigate any unexplained gaps.
  • Document the event and any impact on monitored products or processes.

9 - Records and Retention

Retain the records required by the organisation's quality, contractual, and regulatory obligations. These may include:

  • Approved SOP versions, change history, approvals, and training records.
  • Sensor and gateway inventories, serial numbers, installation details, and configuration records.
  • Calibration certificates, verification results, offsets, and out-of-tolerance assessments.
  • Alert records, annotations, investigations, deviations, and corrective actions.
  • Audit reports, electronic signatures, scheduled-report evidence, and review records.
  • User-access approvals and periodic access-review evidence.
  • Maintenance, replacement, outage, and data-recovery records.

Approved retention period: [Insert period and governing policy].

Approved record location: [Insert system, folder, or document repository].

10 - Training and Review

  • Train each user before granting access needed to perform controlled tasks.
  • Record training against the approved SOP version.
  • Provide refresher training after significant process, system, role, or interface changes.
  • Review the SOP at the nominated interval and after significant incidents or changes.
  • Confirm that screenshots, menu names, alert limits, support paths, and device instructions remain current.
Prepared by [Name, role, signature, date]
Reviewed by [Name, role, signature, date]
Approved by [Name, role, signature, date]

11 - References and Supporting Guidance

Platform Quick Guide Review the main account, navigation, monitoring, and administration workflows. Administration Help Configure users, access, alerts, notification groups, nodes, gateways, and calibration records. Audit Report Help Create, download, schedule, review, and digitally sign audit reports where enabled. Reports and Annotations Review sensor records, alert events, recoveries, annotations, and period statistics. Calibration Instructions Review the existing temperature calibration and verification guidance before adapting this template. 21 CFR Part 11 Guidance Review the platform controls and organisational responsibilities relevant to electronic records and signatures.