{"id":"bc4edc97-053c-43ff-b777-310a495cfd0d","task":"Ingest IoT cold-chain temperature telemetry from a Sensitech or Emerson Connect Plus logger via API and detect excursions in real time","domain":"sensitech.com","steps":["Authenticate with the Sensitech TempTale Cloud API or Emerson Connect Plus API using API key in the Authorization header; retrieve the list of active loggers associated with your shipment batch","Subscribe to or poll the telemetry endpoint for each logger device ID; each reading includes a device ID, timestamp in UTC, temperature value in degrees Celsius, humidity if equipped, and a sequence number for gap detection","Apply your product-specific temperature limits (e.g. 2-8°C for refrigerated pharmaceuticals, -25°C to -15°C for frozen) as configurable alert thresholds per shipment lane; store thresholds with the shipment record not globally","On each telemetry ingest, compare the reading against the applicable threshold; if outside range, record an excursion start event with the reading timestamp, device ID, and temperature value; continue tracking until the reading returns within range to capture excursion duration","Calculate the cumulative out-of-range duration for each excursion event; compare against the product's Maximum Permissible Excursion (MPE) from the product master; trigger a chain-of-custody hold event and notify QA if MPE is breached","Log every telemetry reading immutably with ingestion timestamp, logger sequence number, and calculated status (IN_RANGE, EXCURSION); use sequence number gaps to detect missed readings and raise a data-gap alert"],"gotchas":["Logger clocks can drift relative to network time; timestamps from the logger may lag real wall-clock time by minutes; always store the logger-reported timestamp separately from the server ingestion timestamp and use the logger timestamp for excursion duration calculations","Some loggers buffer readings internally when out of cellular range and upload in bulk when connectivity is restored; bulk uploads with historical timestamps can appear as sudden excursions that actually occurred hours earlier; your excursion detection must use the reading timestamp, not ingestion timestamp","Threshold violations that last fewer than 15 minutes are typically not clinically significant for pharmaceutical products; configuring zero-tolerance on single readings generates excessive false-positive alerts that cause QA teams to ignore real excursions"],"contributor":"waymark-seed","created":"2026-06-13T17:29:53.560Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:26.626Z"},"url":"https://mcp.waymark.network/r/bc4edc97-053c-43ff-b777-310a495cfd0d"}