wangdx25/oil047_sample

OIL-047 — Synthetic Field Operations Dataset (Sample) (TsFile)

Apache TsFile version of xpertsystems/oil047-sample.

Overview

A schema-identical preview of OIL-047, the XpertSystems.ai synthetic daily field operations intelligence dataset for upstream + midstream oil & gas operations. The full product covers ~12,000 fields × 1,825 days (5-year horizon). This sample is HF-sized (60 fields × 120 days) covering all 13 product tables.

• Tables: 13 TsFile table(s), 75,768 rows in total.
  • alarm_events: 1,127 rows, 2020-01-01 00:01:00 → 2020-04-29 18:11:00 (UTC)
  • crew_operations: 11,309 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.102000 (UTC)
  • equipment_master: 300 rows, 1970-01-01 00:00:00 → 1970-01-01 00:00:00.299000 (UTC)
  • equipment_runtime: 18,111 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.156000 (UTC)
  • field_master: 60 rows, 2020-01-01 00:00:00 → 2020-01-01 00:00:00.059000 (UTC)
  • inspection_observations: 297 rows, 2020-01-02 00:00:00 → 2020-04-29 00:00:00.001000 (UTC)
  • logistics_tracking: 2,575 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.022000 (UTC)
  • maintenance_activities: 489 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.002000 (UTC)
  • operational_labels: 7,200 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.059000 (UTC)
  • operational_logs: 16,336 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.139000 (UTC)
  • pipeline_operations: 5,702 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.050000 (UTC)
  • production_reports: 7,200 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.059000 (UTC)
  • tank_inventory: 5,062 rows, 2020-01-01 00:00:00 → 2020-04-29 00:00:00.035000 (UTC)

Schema (TsFile structure)

alarm_events.tsfile

• Time (INT64, milliseconds) — the source event_time column.
• TAG: none — the table is stored as a single device.
• FIELD (9): alarm_id (string), field_id (string), alarm_type (string), severity_level (string), acknowledgment_time_minutes (double), cleared_time_minutes (double), scada_source (string), escalated (int64), related_downtime_hours (double)

crew_operations.tsfile

• Time (INT64, milliseconds) — the source activity_date column.
• TAG: none — the table is stored as a single device.
• FIELD (9): crew_activity_id (string), field_id (string), crew_id (string), role (string), deployment_status (string), shift_hours (double), fatigue_score (double), safety_observation_count (int64), handover_delay_minutes (double)

equipment_master.tsfile

• Time (INT64, milliseconds) — synthetic row index over the stable source order; this table has no clock column.
• TAG: none — the table is stored as a single device.
• FIELD (7): equipment_id (string), field_id (string), equipment_type (string), equipment_age_years (double), nameplate_capacity (double), baseline_health_score (double), critical_equipment (int64)

equipment_runtime.tsfile

• Time (INT64, milliseconds) — the source runtime_date column.
• TAG: none — the table is stored as a single device.
• FIELD (11): runtime_id (string), equipment_id (string), field_id (string), equipment_type (string), runtime_hours (double), idle_hours (double), utilization_rate (double), health_score (double), vibration_index (double), temperature_c (double), energy_consumption_kwh (double)

field_master.tsfile

• Time (INT64, milliseconds) — the source created_date column.
• TAG: none — the table is stored as a single device.
• FIELD (14): field_id (string), field_name (string), operator (string), region (string), country (string), asset_type (string), operational_status (string), asset_age_years (int64), baseline_oil_bpd (double), baseline_gas_mcfpd (double), baseline_water_bpd (double), criticality_score (int64), remote_operation_level (int64), scada_enabled (int64)

inspection_observations.tsfile

• Time (INT64, milliseconds) — the source inspection_date column.
• TAG: none — the table is stored as a single device.
• FIELD (8): inspection_id (string), field_id (string), inspection_type (string), finding_type (string), risk_level (string), corrective_action_required (int64), days_to_close (int64), inspector_id (string)

logistics_tracking.tsfile

• Time (INT64, milliseconds) — the source shipment_date column.
• TAG: none — the table is stored as a single device.
• FIELD (8): shipment_id (string), field_id (string), shipment_type (string), delivery_status (string), delay_hours (double), distance_miles (double), transport_mode (string), cost_usd (double)

maintenance_activities.tsfile

• Time (INT64, milliseconds) — the source maintenance_date column.
• TAG: none — the table is stored as a single device.
• FIELD (10): workorder_id (string), field_id (string), maintenance_type (string), priority (string), planned_duration_hours (double), actual_duration_hours (double), completion_status (string), parts_delay_hours (double), maintenance_cost_usd (double), root_cause_code (string)

operational_labels.tsfile

• Time (INT64, milliseconds) — the source label_date column.
• TAG: none — the table is stored as a single device.
• FIELD (10): label_id (string), field_id (string), operational_risk (double), downtime_probability (double), production_loss_probability (double), maintenance_need_probability (double), alarm_storm_probability (double), optimization_score (double), rare_event_flag (int64), recommended_action (string)

operational_logs.tsfile

• Time (INT64, milliseconds) — the source activity_date column.
• TAG: none — the table is stored as a single device.
• FIELD (10): log_id (string), field_id (string), shift_id (string), activity_type (string), activity_duration_minutes (int64), operator_id (string), completion_status (string), handover_quality_score (double), response_delay_minutes (double), notes_code (string)

pipeline_operations.tsfile

• Time (INT64, milliseconds) — the source operation_date column.
• TAG: none — the table is stored as a single device.
• FIELD (9): pipeline_operation_id (string), field_id (string), pipeline_id (string), pressure_level_psi (double), flow_rate_bph (double), temperature_c (double), linepack_variance (double), integrity_watch_flag (int64), pigging_due_days (int64)

production_reports.tsfile

• Time (INT64, milliseconds) — the source report_date column.
• TAG: none — the table is stored as a single device.
• FIELD (11): production_id (string), field_id (string), weather_condition (string), oil_volume_bbl (double), gas_volume_mcf (double), water_volume_bbl (double), downtime_hours (double), uptime_hours (double), utilization_rate (double), production_efficiency (double), report_status (string)

tank_inventory.tsfile

• Time (INT64, milliseconds) — the source record_date column.
• TAG: none — the table is stored as a single device.
• FIELD (8): tank_record_id (string), field_id (string), tank_id (string), inventory_level_bbl (double), tank_capacity_bbl (double), fill_percentage (double), transfer_status (string), quality_hold (int64)

Conversion notes

• One TsFile per source CSV (13 tables); each table is stored as a single device, so the rig / well / tank / equipment / sensor identifiers stay ordinary FIELDs.
• Time = the table's own clock column as INT64 milliseconds (event timestamps, sample or inspection dates, and daily record dates). The clock columns used here are activity_date, created_date, event_time, inspection_date, label_date, maintenance_date, operation_date, record_date, report_date, runtime_date, shipment_date.
• Tables with no clock column (equipment_master) use a synthetic row index over their stable source order as Time.
• No column is dropped. Rows that share a timestamp are ordered by a 1 ms step in stable source order, so daily tables keep their exact calendar day.

Usage

Read this dataset with the Java SDK. It is written with the zstd compressor. The Apache TsFile Java SDK reads every compressor, but the Python SDK (pip install tsfile) implements only UNCOMPRESSED, SNAPPY, GZIP and LZ4; opening this file with it yields no rows.

Read a converted file with the Apache TsFile Java SDK (org.apache.tsfile:tsfile):

import org.apache.tsfile.file.metadata.IDeviceID;
import org.apache.tsfile.read.TsFileReader;
import org.apache.tsfile.read.TsFileSequenceReader;
import org.apache.tsfile.read.common.Path;
import org.apache.tsfile.read.expression.QueryExpression;
import org.apache.tsfile.read.query.dataset.QueryDataSet;
import org.apache.tsfile.write.schema.MeasurementSchema;

import java.util.ArrayList;
import java.util.List;

String path = "alarm_events.tsfile";
try (TsFileSequenceReader sequenceReader = new TsFileSequenceReader(path);
     TsFileReader reader = new TsFileReader(sequenceReader)) {
    // Devices are enumerated as IDeviceID objects. Tables with TAG columns
    // have multi-segment device ids that cannot be rebuilt from their string
    // form, so always use getAllDevices() rather than getAllDeviceIds().
    for (IDeviceID device : sequenceReader.getAllDevices()) {
        List<Path> paths = new ArrayList<>();
        for (MeasurementSchema schema : reader.getMeasurement(device)) {
            String name = schema.getMeasurementName();
            if (name != null && !name.isEmpty() && !name.equalsIgnoreCase("Time")) {
                paths.add(new Path(device, name, true));
            }
        }
        QueryDataSet dataSet = reader.query(QueryExpression.create(paths, null));
        while (dataSet.hasNext()) {
            System.out.println(dataSet.next());
        }
    }
}

Source & license

• Original dataset: xpertsystems/oil047-sample
• Source card title: OIL-047 — Synthetic Field Operations Dataset (Sample)
• License: cc-by-nc-4.0 (as declared by the original dataset).