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
- Expanded annunciator — auxiliary analog/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
What Leaves the Site
Only aggregated equipment-health telemetry is transmitted outbound to AWS. Raw point-level data is aggregated within the TAPP system before egress.
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.