Reasoning & math
AuraScore 83/100

Freight Corridor Fuel Variance Breakdown

Analyze telematics and payload variables to mathematically explain fuel consumption anomalies on freight lanes.

Use this template when evaluating heavy-vehicle telematics against benchmark fuel targets to isolate operational vs environmental consumption drivers. It guides fleet managers through a structured quantitative factor decomposition.

Template

Role: Lead Fleet Operations Research Analyst with fifteen years of experience in heavy transport telemetry and mathematical fuel modeling.

Context

  • Target Fleet Unit: {{fleet_identifier}}
  • Evaluation Lane: {{corridor_name}}
  • Benchmark Standard: {{target_fuel_consumption_rate}}
  • Observed Log Data: {{logged_telematics_data}}
  • Operational Ratios: {{payload_and_deadhead_metrics}}
  • External Factors: {{ambient_weather_conditions}}

Task

Produce a rigorous quantitative variance analysis explaining the delta between baseline and observed fuel burn, isolating driver behavior, idling, terrain, and payload weight variables into discrete mathematical contributions.

Method

  1. Reconcile recorded distance and fuel consumption against the baseline standard {{target_fuel_consumption_rate}}.
  2. Normalize fuel consumption data for total freight weight and deadhead mileage from {{payload_and_deadhead_metrics}}.
  3. Calculate the thermal and aerodynamic drag penalty driven by {{ambient_weather_conditions}}.
  4. Isolate excessive idle burn time from engine operating hours in {{logged_telematics_data}}.
  5. Compute speed-band distributions and identify aggressive acceleration penalties on {{corridor_name}}.
  6. Aggregate total gallons burned and allocate variance across mechanical, operational, and environmental buckets.
  7. Formulate a final sensitivity score indicating key operational risk factors for {{fleet_identifier}}.

Constraints

  • MUST express all variances in absolute gallons and percentage deviations.
  • MUST NOT attribute unexplained variance to sensor error without mathematical justification.
  • Keep total baseline calculations explicit and reproducible.
  • Analysis must highlight the single largest controllable cost driver.

Output format

  • Executive Summary (max 100 words)
  • Quantitative Factor Decomposition Table (Factor, Baseline, Actual, Delta Gallons, % Impact)
  • Operational Root-Cause Analysis (3 paragraphs)
  • Corrective Action Levers (ordered by expected return)

Self-review

  • Are all 6 contextual variables explicitly accounted for in the calculations?
  • Do individual variance components sum mathematically to total observed delta?
  • Are MUST/MUST NOT criteria strictly observed in the narrative?
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

research-analysis
research-reasoning-math
transport-logistics
fleet
logistics
telematics