DATA REQUIREMENTS

Just Export Your Data — We Handle the Rest

VeriOps automatically detects signal columns and cleans common formatting issues. Export from your historian or monitoring system and upload — no special formatting required.

Supported Formats

CSV, WAV, NPY, MAT

Minimum Duration

30 minutes of signal data

One-Time Healthy Sample

Set up once per equipment

Where Does VeriOps Data Come From?

VeriOps analyzes time-series sensor data from your existing industrial systems. You likely already have this data — it just needs to be exported.

Data Historians

Most plants store years of sensor data in historians. Export the relevant time range to CSV.

  • OSIsoft PI / AVEVA PI
  • Honeywell PHD
  • AspenTech InfoPlus.21
  • GE Proficy Historian

Vibration Monitoring Systems

Dedicated vibration systems capture high-frequency data. Export waveform or time-series data.

  • SKF @ptitude / Microlog
  • Emerson AMS / CSI
  • Bently Nevada System 1
  • Pruftechnik VIBSCANNER

SCADA / DCS Systems

Control systems log process variables. Export trend data for the equipment in question.

  • Emerson DeltaV
  • ABB 800xA
  • Siemens PCS 7
  • Rockwell PlantPAx

Portable & Manual Collection

Handheld data collectors and manual exports work fine — just ensure sufficient duration.

  • Route-based vibration collectors
  • Portable accelerometers
  • Data logger exports
  • MATLAB/Python processed data

Real-World Example

Here's how a reliability engineer at a refinery would use VeriOps to evaluate a suspect bearing.

Scenario: FCC Main Air Blower Bearing

Operations reported increased noise during startup

ONE-TIME SETUP
1

Register Equipment with Healthy Sample

The engineer registers the bearing in VeriOps and uploads 30+ minutes of healthy sample data from March 2024 — right after the last bearing replacement when the equipment was running smoothly.

Healthy Sample: March 15, 2024 • Tag: 103-MAB-VIB-001 • 60,480 samples
✓ Healthy sample stored with equipment profile
EACH DECISION (30+ MIN RECENT DATA)
2

Export Recent Data

When operations reports a concern, the engineer exports recent data (30+ minutes) from PI DataLink (tag: 103-MAB-VIB-001).

Recent Data: Last 2 hours • 10-second intervals • CSV format
3

Upload and Request Decision

Upload just the recent data — VeriOps automatically uses the stored healthy sample for comparison.

✓ Recent data validatedHealthy sample: using stored profile
4

Receive Decision

VeriOps compares recent data against the stored healthy sample and returns:

S1Early Degradation Detected• MED confidence

"Energy distribution has shifted toward higher harmonics compared to healthy sample. Degradation is currently reversible. Recommend monitoring at 7-day intervals. No immediate action required."

Outcome

The engineer has a defensible basis to continue operation with increased monitoring — not an alarm to react to, but a decision they can justify to their plant manager.

Supported File Formats

Upload directly from your data system. VeriOps automatically detects signal columns and ignores metadata like timestamps, status fields, and quality flags.

.csv

CSV

Recommended

Comma or tab-separated values — the most common export format

We auto-detect signal columns. Date/time, status, and text columns are automatically ignored.

.wav

WAV

Audio waveform files from vibration sensors

Standard PCM format. Sample rate preserved from file metadata.

.npy

NPY

Recommended

NumPy binary format for pre-processed data

Fastest processing. Ideal for programmatic uploads.

.mat

MAT

MATLAB data files

v7.3 HDF5 format or earlier. Variable names should be descriptive.

Data Quality Checks

VeriOps automatically checks data quality during upload. Most exports from industrial systems pass without issue. If there's a problem, we'll tell you exactly what needs to be fixed.

RequirementThresholdIf Failed
Duration≥ 30 minutesREFUSE
Sample Count≥ 1,800 samples (at 1 Hz)REFUSE
Sampling Rate1 Hz – 100 kHzREFUSE
Missing Values≤ 5% of samplesREFUSE
Invalid Values (NaN/Inf)0 allowedREFUSE
Flatline Detection≤ 60 identical consecutive samplesREFUSE
Clipping Detection≤ 1% of samples at railREFUSE

Quality gate failures result in refusal

VeriOps does not guess or interpolate. If your data fails quality checks, no decision will be issued. This is not an error — it protects decision integrity.

Healthy Sample Requirements

A healthy sample is reference data from when equipment was running well. No healthy sample = no decision.

One-Time Setup Per Equipment

When you register equipment in VeriOps, you upload a healthy sample once. This healthy sample is stored with your equipment profile and used for all future decisions — no need to re-upload healthy sample data each time.

One-timeHealthy sample upload during setup
→
Each decisionUpload recent data only

Valid Healthy Sample Criteria

  • Collected after maintenance, when equipment was running smoothly
  • Same equipment, same operating conditions
  • Minimum 30 minutes duration
  • Passes all data quality requirements
  • Collected within 12 months (or after major maintenance)

Healthy Sample Freshness

< 6 months

Current

6-12 months

Acceptable

> 12 months

Stale (refresh recommended)

When to Update Healthy Sample

Update your stored healthy sample from the Equipment settings page after:

  • Major maintenance or overhaul (new healthy state)
  • Component replacement (bearing, seal, etc.)
  • Healthy sample older than 12 months
  • Operating condition changes (new speed, load profile)

Equipment-Specific Data

Bearings

PRODUCTION

Signal type: Vibration (acceleration)

Recommended rate: 10 kHz or higher

Channels: Horizontal and/or vertical axis

What we evaluate: Energy distribution, impulsiveness, periodicity changes

Compressors

PRODUCTION

Signal type: Vibration and/or pressure

Recommended rate: 1 kHz or higher for vibration

Channels: Bearing proximity, discharge pressure

What we evaluate: Stability patterns, surge indicators, valve health

Oil & Gas Wells

PRODUCTION

Signal type: Process signals (pressure, temperature, flow)

Recommended rate: 1 Hz minimum for process data

Channels: TPT (downhole P/T), PDG, choke position

What we evaluate: Flow stability, hydrate risk, scaling trends

Turbines

PRELIMINARY

Signal type: Vibration (bearing proximity)

Recommended rate: 10 kHz or higher

Note: Decisions capped at MED confidence until full validation complete.

What You Do Need

We handle formatting automatically, but there are a few things we can't fix for you:

At least 30 minutes of data

Shorter periods lack enough evidence for reliable decisions

A healthy sample for comparison

We need to know what "normal" looks like for your equipment

Working sensor (not frozen/flatlined)

A stuck sensor gives us no usable information

Signal within sensor range (not clipped)

Saturated signals lose important peak information

Clear Feedback on Any Issues

If something's wrong with your data, VeriOps tells you exactly what the problem is and how to fix it. No cryptic error messages — just clear guidance on what's needed.

Smart CSV Parsing

Just export your data as-is. VeriOps automatically handles common formatting from industrial systems.

We Automatically Handle

Date and time columns (ignored)
Status/quality flag columns (ignored)
"N/A", "NULL", "-" as missing values
Mixed numeric/text columns (text ignored)
Headers with any naming convention
Comma or tab delimiters

Example: Typical Historian Export

This is what a real PI DataLink export looks like — and it works fine:

Timestamp,103-MAB-VIB-001,103-MAB-VIB-001_Status,Quality
2024-01-15 10:30:00,0.0234,Good,192
2024-01-15 10:30:10,0.0241,Good,192
2024-01-15 10:30:20,N/A,Bad,0
2024-01-15 10:30:30,0.0238,Good,192
...

VeriOps detects: "103-MAB-VIB-001" as the signal column. Timestamp, Status, and Quality columns are automatically ignored. The "N/A" value is treated as a missing sample.

Ready to evaluate your data?

Upload your dataset and receive a defensible operational decision.

Get Started FreeSee How It Works