Data & Telemetry
This page answers one question: what data does TAPP actually collect and send? It describes the categories of telemetry TAPP gathers, not individual register maps or point-level lists.
What TAPP Collects
All data is equipment performance telemetry. No process recipes, no control logic, no personally identifiable information, no customer business data.
Equipment controller data (all read-only). The exact points depend on the equipment. A boiler is the most instrumented case; chillers, water chemistry controllers, and other control systems expose their own analogous performance and state data. Typical categories for a boiler:
- Combustion & firing — firing rate, setpoint vs. actual, flame signal, O₂, CO₂, excess air, efficiency, flue and supply-air temperatures, actuator positions, fan and VSD speed
- Operational state & runtime — burner phase, manual/auto mode, startup counter, hours run, fuel throughput and volumes
- Faults, alarms, and lockout history
- Load controller — process values, setpoint, output %
- Feedwater — drum level %, setpoint, steam and water flow, output
- Additional annunciation — auxiliary analog and digital inputs, alarms, draft, totalized flows
- VSD — frequency, RPM, current, power, fault codes
Wireless sensor data (all read-only). Applied to tanks, motors, pumps, and other rotating or process equipment:
- Vibration
- Temperature
- Pressure
- Current
- Analog signals — 0–10 V and 4–20 mA inputs
- Pulse and frequency inputs
- Discrete digital inputs — run status, position, and similar state signals
What Leaves the Site
Equipment-health telemetry is transmitted outbound to AWS at the system’s collection interval. This includes point-level readings — the values TAPP reads from equipment controllers and wireless sensors are transmitted as measured, so that trending, diagnostics, and fault analysis are performed against the actual data rather than a summary of it.
What does not leave the site is anything outside that telemetry scope: no control logic, no process recipes, no equipment configuration, no network traffic, no files, and no personnel or business data. TAPP transmits equipment measurements and nothing else.
What TAPP Does Not Collect
- No process recipes or production formulas
- No control commands or setpoint writes
- No customer personnel information
- No network traffic or IT system data
Storage
All data is stored in AWS (US region). Sub-processor: Amazon Web Services. Data is encrypted in transit using TLS and encrypted at rest using AWS-managed keys. TAPP does not replicate customer data outside the United States.