Sensing Layer
IIoT · drones · satellite · wearables · SCADA · ERP · EMR · external feeds
The data ingestion layer. Every data source LinkedTIERRA can ingest — unified into a single data model that feeds the AI Engine and Stakeholder Layer. The Sensing Layer does not produce intelligence. It produces clean, timestamped, contextually labeled data for everything above it to reason over.
What it does.
IIoT and physical sensors
BlueMaestro WBGT ground stations, industrial temperature sensors, humidity monitors, pressure sensors. BLE, LoRaWAN, WiFi, Modbus RTU — protocol-agnostic ingestion.
Aerial and satellite
DJI + FLIR drone thermal imagery processed via GeoTIFF pipeline → CloudFront CDN → Leaflet render. Landsat 8/9 Band 10 via USGS EarthExplorer API. MODIS, Sentinel-2 in roadmap.
Wearable physiological
WBGT, heart rate, skin temperature, EDA (electrodermal activity), accelerometer (fall detection), GPS location. BLE 5.0 and ANT+ protocols. 30-second sync intervals.
Enterprise system connectors
SCADA, OPC UA, Modbus TCP, ERP (SAP, Oracle, MS Dynamics), CMMS (Maximo, Fiix), HRIS, EMR (Epic, Cerner via FHIR R4). OAuth 2.0, API key, SAML 2.0 auth.
External data feeds
NOAA weather, USGS water and elevation, 311 call data, satellite commercial imagery, real-time environmental APIs. Contextual data that makes operational data meaningful.
How it powers ecosystems.
WBGT ground sensors, drone FLIR thermal imagery, Landsat satellite, wearable physiological, SCADA/BMS integration, NOAA weather context
Wearable fall detection and physiological, home motion/door/temp sensors, GPS location, FHIR EMR integration, pharmacy Rx feeds
Satellite imagery (Landsat, Sentinel), elevation data (USGS), 311 call datasets, environmental monitoring APIs, custom CSV upload pipelines
Current state + roadmap.
Pure infrastructure layer — never a customer-facing product. Customers see alerts, insights, and dashboards. The Sensing Layer is what makes those outputs trustworthy.
Advising organizations on instrument selection, placement, calibration, and integration for specific operational contexts — formalized as a standalone service offering.