Integration Workflow Improvements

New integration capabilities have been introduced to allow improved interactions between our Aucerna products and your other data sources streamlining your data import workflows. These capabilities are designed to help keep the complexity of Enersight in Enersight and avoid making these interfaces and your workflows harder than they need to be for all users.

• The first category of features is associated with introducing Clone Based Workflows where existing details in your Enersight model are available for reuse when importing data. Specifically, rather than Enersight creating new wells from a blank template on import, you will now be able to optionally reference an asset that would be cloned then have the specified imported changes applied to it if the well didn’t exist yet. Similarly, as a part of this, we will be enabling Rate Acceleration Factors to be optionally retained when updating your production set inputs. These two capabilities allow for Val Nav (or your other chosen source of production input information) to do an update of the details it knows and cares about, without you having to layer on additional uploads and QA/QC to ensure that all ‘general’ functions are applied to all wells etc. or build exhaustive repositories of inputs containing all the complexity from Enersight to support your Function based inputs requirements.
• The second group of features is associated with adding support for ‘unschedule’ capabilities between Aucerna Execute and Enersight so that the ownership of an activity between the two applications can flow back and forth, not just participate in a one-time transfer from Enersight through to Execute. Specifically, this feature will enable you to convert static tasks and wells back to dynamic should the currently locked in dates and/or resources no longer be appropriate and may be enacted directly within Enersight as well via an ‘unschedule’ action performed via the Gantt, via Schedule Data or via the Assets > Static Assets menu dropdown.


Click image to expand or minimize.

• Adding Production Set Inheritance options within Enersight so that once well activities are owned by Execute and made static, the well can still be linked to a type curve. This makes updating the production inputs much easier, as you can retain a type curve and inheritance structure and not have to manually duplicate this data many times for all the wells for which you don’t have any extra information yet on but are owned by Execute (or generally locked in within your model as static with wellcount 0 or -1) and so wouldn't be updated during normal processes.


Click image to expand or minimize.