Live Drilling
  • Introduction
  • FAQ
  • what's new
    • Latest releases
      • Wells 5
      • LiveRig 5
      • LiveRig 4
      • WITSML Store
    • Operations in Time by Depth Chart
    • Unit Sets
      • Per-Asset Units
      • Unit Conversion
      • Dashboard Configuration
      • Force Follow Asset Units
    • Well casing shoe schematic
    • Wells correlation
    • FFT spectrum
    • Pressure Tests
      • Configuration
      • Automated Standard Pressure Tests
      • Manual Pressure Test
      • LOT/FIT
    • Rig State detection
    • BOP Schematic
      • BOP status register
    • Signal Processing
      • Moving Average
  • Data Flow
    • Introduction
    • Data Ingestion
    • Data Normalization
      • Clock Synchronization
      • Normalized events schema
      • Data indexes and enrichment
      • Unit conversion
      • Auto-Switch
  • Physical Models
    • Introduction
      • Structure of the functions
      • Validation
    • General Equations
      • Static Data Dependencies
      • Pipes Functions
    • Trajectory
      • Introduction
      • Static Data Dependencies
      • Pipes Functions
    • Hydraulic
      • Introduction
      • Static Data Dependencies
      • Pipes Functions
    • Torque and Drag
      • Introduction
      • Static Data Dependencies
      • Pipes Functions
    • Hole Cleaning
      • Introduction
      • Static Data Dependencies
      • Pipes Functions
    • Surge and Swab
      • Introduction
      • Static Data Dependencies
      • Pipes Functions
    • Thermal
      • Introduction
    • Volume Tracker
      • Introduction
      • Pipes Functions
  • Basic Features
    • Charts
      • Channels Charts
        • Temporal Channels Chart
        • Channel Value Chart
        • Depth Channels Chart
        • Data navigation
          • Span Control
      • Rig Allocation Gantt Chart
    • Unit sets
      • Configuration changes on unit sets
      • Depth unit changes
      • Personal units sets
    • Permission schema
    • Import/Export Well
    • Add-ons
  • Static Data
    • Assets
      • Assets Structure
    • Well
      • Introduction
      • Well Schema
      • Well Units
      • Regions, fields and countries
      • Well Design Overview
      • Objectives
    • Intervention
      • Introduction
      • Intervention Schema
      • Intervention Types
      • Scenarios
      • Runs
      • Completion and Abandonment
      • Drilling Section Schema
    • Rig
      • Introduction
      • Rig Schema
      • Physical models configuration
    • Pipes functions
    • REST API Examples
  • Administration
    • High Frequency Data
      • WITSML Null Values
      • Unit Management Tools
      • WITS Custom Mapping
    • Data Normalization
      • Data Management
        • Event Settings
        • Channels Management
      • Data normalization templates
      • Data normalization templates prioritization
      • Auto-Switch
    • Standard Identifiers
    • Static Data
      • Regions, fields and countries
      • Intervention Types
  • LiveRig Collector
    • Introduction
    • Getting Started
    • Connecting to Intelie Live
    • Security
    • Local data storage
    • Data transmission and recovery
    • Monitoring
    • Remote Control
      • APIs
        • /testSourceEndpoint
        • /storeConfiguration
        • /getFromStore
        • /backlog-sync
      • Sources
        • MQTT Topics
        • OPC Requests
        • WITSML Backlog Sync
        • WITSML Object Explorer
        • WITSML Requests
      • Properties
    • HA Deployment
    • Protocols
      • WITSML
      • WITS
      • OPC-DA
      • OPC-UA
      • MODBUS
      • MQTT
      • CSV
      • RAW
    • Protocol conversion
    • Configuration
      • liverig.properties
      • sources.xml
      • store.json
      • modbus.json
      • mqtt.json
      • Configuring an OPC-UA source
      • Multiple event types for WITSML sources
      • Certificate-based authentication for WITSML HTTPS sources
    • LiveRig Collector Appliance
    • Command line Interface (CLI)
  • LIVE EDGE
    • Collector Reader
  • Integrations
    • Introduction
    • WITSML Store
    • REST Output
    • REST Input
    • WellView
    • OpenWells
    • Python
  • DEVELOPER
    • Identified Curves
    • Hidden Units
  • DEPRECATED
    • WITSML Output
    • LiveRig 3.x / 2.x
      • 3.5.0
      • 3.4.0
      • 3.3.0
      • 3.2.0
      • 3.1.0
      • 3.0.0
      • 2.29.0
Powered by GitBook
On this page
  • Examples
  • Example 1
  • Example 2
  • Example 3
  • Example 4

Was this helpful?

  1. Data Flow
  2. Data Normalization

Auto-Switch

PreviousUnit conversionNextIntroduction

Last updated 5 years ago

Was this helpful?

Auto-Switch selects the best input channel for each normalized channel. Intelie LIVE platform analyzes every one of those channels configured and create an individual status, that represents the data quality of that channel.

Every 20 seconds, the highest priority input channel with good status will be selected for each normalized channel.

A channel with priority 1 has a higher priority than a channel with priority 2.

The priority must be unique

Auto-Switch engine only selects input channels with a priority defined.

To create this data quality measurement several metrics are taken into account, one of them is availability. To be considered as available, a channel must be transmitting for more than restored ms and without any gap greater than gap ms.

Both parameters, gap and restored, can be changed in the and affect all assets. By default gap has the value 120000ms (2 minutes), and restored is equal to 120000ms (2 minutes)

Examples

The asset configuration bellow will be used in all subsequent examples. gap and restored are equals to 1

Example 1

In this example, the input channel with priority 1( ABC ) is available all the time, so there's no change made by the Auto-Switch and the normalized channel is created using the data from ABC.

Example 2

Here ABC doesn't have data between 4 and 4.5, however, no change is made. Since gap is 1, ABC is considered available at this point. Because of that, the normalized channel reflects what happened with ABC and has a data gap between 4 and 4.5.

The minimun value for gap and restoredis 20000 ms (20 seconds)

Example 3

Channel ABC has a gap between 4 and 7. Here the Auto-Switch engine selects XYZ as a substitute at the time 5. Again, between 4 and 5, ABC is considered available because gap is 1.

At 7, ABC is recovered and once again there is data. Auto-Switch waits restored to select ABC as the main channel, which occurs at 8.

The normalized channel reflects ABC at the time 0-5 and 8-12. Between 5 and 8 the channel XYZ is used.

Example 4

Channel ABC has a gap between 4 and 7. Here the Auto-Switch engine selects DEF as a substitute at the time 5. Again, between 4 and 5, ABC is considered available because gap is 1. XYZ isn't available since 4.

At 6, XYZ is recovered and once again there is data. Auto-Switch waits restored to select XYZ as the main channel, which occurs at 7. The same happens with ABC at 7, and at 8 it's chosen.

The normalized channel reflects ABC at the time 0-5 and 8-12. Between 5 and 6 the channel DEF is used. XYZ is used from 7 to 8.

system configuration
Input channels prioritized