Construction Site IoT Telemetry Database Selection Matrix
Evaluate time-series database candidates for continuous jobsite sensor telemetry, heavy machinery tracking, and site safety alerting.
Use this template when selecting or auditing time-series databases for active construction jobsite monitoring. It delivers a structured scoring matrix tailored to sensor density, network latency, and retention requirements.
Role: Construction IoT Data Engineer specializing in jobsite telemetry, crane monitoring, and heavy asset time-series pipelines.
Context
- Site Operator: {{site_operator_name}}
- Ingestion Throughput: {{telemetry_data_volume}}
- Sensor Telemetry Payload: {{sensor_payload_schema}}
- Data Retention Requirement: {{retention_policy_window}}
- Field Connectivity Profile: {{edge_connectivity_profile}}
- Safety Alert SLA: {{alert_latency_sla}}
Task
Develop a comparative time-series database evaluation matrix to select the best storage and aggregation engine for heavy equipment and environmental jobsite sensors.
Method
- Profile the ingestion burst rate for {{site_operator_name}} based on {{telemetry_data_volume}}.
- Analyze {{sensor_payload_schema}} for compression efficiency and column-family suitability.
- Evaluate edge-to-cloud synchronization under conditions defined by {{edge_connectivity_profile}}.
- Test continuous aggregation and query response times against {{alert_latency_sla}}.
- Measure data downsampling and automated tiering behavior for {{retention_policy_window}}.
- Score candidate engines on write availability, partition pruning, and disk footprint.
- Compile the consolidated decision matrix with ranked outcomes.
Constraints
- MUST include time-series compression ratios for {{sensor_payload_schema}}.
- MUST NOT select architectures unable to meet {{alert_latency_sla}} during disconnects.
- Comparison matrix must assess at least 3 production-grade time-series engines.
- All engine scores must be justified in cell annotations.
Output format
- Section 1: Telemetry Architectural Baseline (max 100 words).
- Section 2: Time-Series Database Evaluation Matrix (Markdown table with columns: Candidate Engine, Ingestion Throughput, Compression Efficiency, Edge Sync Resilience, Alert Latency, Downsampling Ease, Overall Fit Score 1-10).
- Section 3: Implementation Roadmap Matrix (3 milestones with timeline and critical path).
Self-review
- Confirm all 6 variables are referenced in technical requirements.
- Check that the matrix includes specific time-series metrics.
- Ensure MUST and MUST NOT rules are strictly validated in the scoring.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.