Project Creation

Projects are created in a specific time zone and coordinate system. Key information such as the direction of SHmax can be entered and referenced throughout the project as Project Azimuth. The project azimuth is used to display analysis output, such as offset pressure analysis.

Data Loading

Well geometry, geological information, time series, completion data and diagnostic data are uploaded through the Data Loader with previews available to guarantee that each step is properly followed.

Data specific time zone and the coordinate system can be specified and converted to the project time zone and reference system to arrive at the same reference system. In addition to primary data, vendor interpretation results can be loaded.

Monitor Sensor Data

Pressure and Temperature, and largely any suite of timestamped values, can be loaded.

Well Geometry

ORCHID is a georeferenced platform where the user can define the well head information and a given coordinate system. Deviation surveys can be loaded to create a 3D object. Information such as stage location and start and stop time, as well as ISIP are loaded as CSV files.

Fracture/Completion

Users can upload fracture height, length azimuth and asymmetry. Timestamped fracture sets are also supported. Pressure, rate (slurry and/or clean, with AVF) and proppant concentration (downhole and/or surface) can be loaded as a single file, or a batch of stage data.

Geology

Geological information loads may include horizons and well-horizon intersection markers, lease lines, fault traces, geobodies and well logs.

Data QC

Before analysis, Time Synchronization issues are corrected to avoid, for example, misinterpretation of max dP. The treatment data, stage start and stop time, and the ISIP can easily be updated and a consistent approach through stages and wells applied.

Treatment Data

Data sources can be diverse and not synchronized with one another. In order to correct the treatment data, manual time correction or algorithmic auto-correlation can be applied between a reference time series and the treatment data.

Stage Start and Stop

Stage start and stop time are recorded manually in a field observer report. Start and stop times can be manually or algorithmically corrected to ensure that attribute within Data Frames are correctly computed.

Channel Sync

In rare cases where pressure, rate and proppant become out of sync, the user can manually correct a channel against another.

ISIP

ISIP can be manually or algorithmically picked on the primary treatment data or on additional time series such as well head pressure measurement.

Monitor Sensor

Timeseries (pressure or temperature) can be visualized against the pumping time of stages and shifted in time if needed.

Tracer Analysis

Tracer injection and recovered data are displayed in the 3D viewer or as a table to enable the understanding of most probable path of chemicals through the fractured reservoir. Injected Tracer amount and the stage to which chemicals have been pumped as well as the recovered amount in a specific well can be loaded and plotted into a bar chart and referenced in the 3D Viewer where the recovered amount is represented by a sized hexagon, colored by tracer type.

Offset Pressure Analysis

Pressure differential between the offset pressure and the user defined baseline (leak-off curve) are manually picked through multiple stages and multiple wells. Fracture Driven Interaction (FDIs) are classified between poro-elastic deformation and fluid migration to allow the user to understand the severity and the risk related to parent-child or child-child interaction. Pressure derivatives can be computed and used as a proxy to first-response and/or direct fluid interactions. Attributes, such as volume-to-pick or distances are automatically computed through the Data Frame and can be graphically represented in the data table or in 2D/3D Viewers.

Monitor Sensor Data

The QC time series viewer lets the user understand the added pressure over the duration of the job. Pressure from various gauges such as surface, downhole, multiple MDs of different wells can be compared. Stages that see interference become obvious and can be isolated for further analysis.

Fracture Driven Interactions (FDI) magnitude can easily be extracted in the Leak-off Observation Editor. The user can set the reference line and compute the pressure differential on a stage basis. Not only primary data but also filtered and derivative data can be used to create observations such as first-response and frac hits.

Microseismic Analysis

Microseismic interpretation workflows typically include computation of the P90 dimension of a microseismic cloud per stage. These attributes, and more, are extracted through Data Frames and can be represented as a table. Microseismic event locations can be grouped per attribute including well, stage, and formation flag. These are represented individually per set in any 2D or 3D viewer. ORCHID offers a visual interpretation tool to help derive fracture dimensions from the microseismic data.

Log Integration

A histogram in depth can help the user understand frac asymmetry and preferential growth. And since this analysis is done in the Depth Analysis Tool, well log information can be integrated into the interpretation.

Fiber Data

DAS and DTS data can be uploaded individually or be concatenated in a continuous database file, through the ORCHID application, prior to be loaded into a project. Supported formats follow the PRODML DAS standard.

Fiber Data Analysis

A continuous SQLite database for interpretation of DAS, DTS or pressure data is created along with a catalogue of events, visualized in 2D or 3D viewers. Interpretation is made easier with the creation of a log based on the visible range of depth and time of the fiber data represented in the waterfall plot.

Data Frames

All loaded information, from geometry to diagnostic and completion data is used to extract added value through data frames: a list of attributes computed in the background and useful for data analysis that is specific to each object (data). All observations, microseismic event, pressure and fiber observations will for example have a calculation of pumped volume to the observation timestamp. Data Frames can be represented into pivot, grid, and pivot plot panels.

Data Frame Fusion

All these data frames, given a common criterion (or set of criteria) can be joined by a specific operation (inner join, outter-join, ...). The common information can then be extracted, and a new data frame can be created. For example, a user can extract the ISIP or Average pump rate from a completion Data frame and fuse it to the magnitude of a pressure-based observation.

Visualization

2D Viewers (Basemap, Tripanel) and 3D Viewer can be used to represent results of diagnostic data interpretation. Also stage markers can be customized to represent certain completion attributes. Logs of loaded or computed attributes, can be displayed along the well bore. Analysis results (observations) can be represented together with geological information, well logs and faults.