Data cleaning
AuraScore 81/100

Plant Asset Condition Sensor Drift Remediation Protocol

Identify, de-noise, and recalibrate creeping sensor drift and historian compression artifacts in predictive maintenance data.

Deploy this template when asset health indicators, vibration baselines, or thermal readings show systematic drift, compression loss, or calibration decay that harms predictive maintenance models.

Template

Role: Lead Reliability Data Scientist specializing in rotating equipment condition monitoring and industrial telemetry signal conditioning.

Context

  • Critical asset class: {{equipment_class}}
  • Observed signal deterioration: {{anomaly_noise_profile}}
  • Baseline operational window: {{calibration_baseline_window}}
  • Historian compression configuration: {{historian_compression_algo}}
  • Target prognostic architecture: {{failure_prediction_model}}

Task

Develop an advanced data cleansing and signal de-biasing report that corrects baseline drift, historian swinging-door compression distortion, and environmental noise in telemetry for {{equipment_class}}, ensuring unbiased feature inputs for {{failure_prediction_model}}.

Method

  1. Characterize the mathematical decay signature of {{anomaly_noise_profile}} against the historical reference established in {{calibration_baseline_window}}.
  2. Analyze distortion artifacts introduced by {{historian_compression_algo}} (e.g., slope interpolation errors, suppressed high-frequency harmonics) during transient asset states.
  3. Formulate an adaptive baseline recalibration model using dynamic temperature and operational load compensation vectors.
  4. Design a drift-detection and subtraction algorithm (e.g., rolling polynomial trend removal, empirical mode decomposition) to normalize decaying sensor baselines.
  5. Establish outlier filtering logic that discriminates between mechanical shock events (true precursors) and instrumentation electrical spikes.
  6. Construct synthetic reconstructed waveforms for over-compressed periods using state-space estimation or Gaussian process regression.
  7. Validate that cleaned feature distributions (RMS, kurtosis, peak-to-peak) meet stationarity and signal-to-noise requirements for {{failure_prediction_model}}.

Constraints

  • MUST distinguish between actual mechanical degradation trends and sensor transducer drift.
  • MUST NOT apply smoothing filters that suppress critical high-frequency bearing fault frequency harmonics.
  • Cleansed data outputs MUST remain traceable back to raw, uncorrected historian values.
  • Algorithmic overhead must be suitable for batch execution within standard maintenance analysis windows.

Output format

Generate a technical data sanitization report structured into:

  1. Sensor Degradation & Compression Audit (max 200 words)
  2. Drift Identification & Baseline Modeling (mathematical formulation & parameters)
  3. De-noising and Harmonic Preservation Strategy (filter design specifications)
  4. Compression De-aliasing Protocol (reconstruction method for historical data)
  5. Pre- and Post-Cleansing Feature Validation (tabular comparison of key metrics)
  6. Model Ingestion Governance (guidelines for retraining {{failure_prediction_model}})

Self-review

  • Does the protocol prevent the accidental removal of genuine mechanical failure signals?
  • Are the effects of {{historian_compression_algo}} explicitly modeled and counteracted?
  • Does baseline normalization incorporate varying operating conditions (e.g., speed and load)?
AuraScore breakdown
81/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 efficiency5/10 · Thin

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.

data-analytics
data-cleaning
manufacturing-industrial
predictive-maintenance
sensor-drift
signal-processing