Changes since Execute 21.1.317

Schema Changes

  • Several tables beginning with the name COSTWELL or COSTWELLCAT have been added to support the Rystad integration. 21.1.319 #358130
  • The ACCOUNTS and ACCOUNTS_H tables have a new COSTWELLCAT field to allow mapping accounts to Cost Well Categories. 21.1.319 #358130
  • A COSTWELL field has been added to the AFE and the AFE_H tables. This field is inactive by default. 21.1.319 #358130
  • A COSTWELL field has been added to the PROJECT and the PROJECT_H tables. This field is inactive by default. 21.1.319 #358130

Features️

  • Execute now integrates with Rystad Energy to bring their world-wide, industry data directly into the AFE and Capital Budgeting (Projects) workflow. A “Cost Well” entity has been added to serve as a capital-focused template for a well. AFEs and Projects linked to a Cost Well can display validation messages if the estimates or capital for project activities doesn’t align with the benchmark data in the Cost Well. #integration #well #afe #budget 21.1.319 #358130

    Rystad Integration

    The Rystad integration requires a subscription to Rystad Energy but there is no additional licensing required for Execute.

    At a high level, the integration allows Execute to:

    1. Query capital data from Rystad and load that data to a Cost Well entity (or a document if we’re using Execute lingo!)

    The input parameters used for the query and the resulting costs are written to tables on the Cost Well. The costs are organized in categories that we refer to as Cost Well Categories.

    1. For an AFE, the GL accounts are mapped to Cost Well Categories. Then, you can link a Cost Well to your AFE and validation messages appear if the AFE’s estimate is under or exceeds the costs in the Cost Well.

    1. For a Project, Cost Well Categories are mapped to project activity types. By linking a Cost Well to a Project, validation messages are displayed if your costs do not align with the mapped cost well category.

    This doesn’t replace the current detailed estimation process that our customers use today. This isn’t authoring the estimate. The goal is context and confidence, not replacing engineering judgment.

Enhancements

  • A sample plugin and xslt file for the integration with Quorum Cost Accounting has been added to the plugins repository. #integration #afe #plugins 21.1.319 #357564
  • A new alphabetical filter bar has been added to the Configuration page, making it easier for users to find specific configuration items. #ui 21.1.319 #357589
  • In the Quorum balloting server, once a partner submits an “Approved” response, they can no longer clear it. If the approval was submitted by mistake, the partner must contact the ballot operator to have the ballot resent and their response cleared. #ui #balloting 21.1.318 #356538

Bugs

  • Fixed an issue where some file attachments would fail to appear, due to a file being locked. A service restart would be required to bring them back and no errors were shown on the Attachments tab to indicate that there was a problem. Now an error message is displayed on the Attachments tab and further information regarding the locked file can be found in the server log or the support package. . #attachments 21.1.319 #358257
  • Resolved an error when generating a forms package per partner, when the forms are configured to print only for certain partners. #forms 21.1.319 #353941
  • Workflow diagrams will now generate if a task name in a sub-workflow, or the sub-workflow name, includes an ampersand (’&’). #workflow #ui 21.1.319 #356452
  • Field paths displayed on the Required Fields tab in the Discipline configuration page now include the slashes. #ui 21.1.319 #349687
  • Fixed an issue where the application’s built-in emails were failing. #email 21.1.319 #358794
  • Addressed a performance issue when loading Wells using the spreadsheet loaders. #well #loader #performance 21.1.319 #356132
  • Fixed an issue where data selectors would not load data to select. #ui #integration 21.1.318 #357323
  • Fixed an issue where the Send to Partners modal had a very narrow column for the list of selectable forms. #ui #balloting 21.1.318 #357243
  • Fixed date parsing error when setting the Out of Office period when the date format on the server is set to display days first. #api #system 21.1.318 #355591
  • Fixed the searching and sorting in the tasks grid of a workflow definition. #workflow #ui 21.1.318 #357326
  • Reverted the data tables library change from version 21.1.317. #system #ui 21.1.318
Ready to update?
  • For Quorum-hosted Aucerna Execute environments, email an upgrade request to Execute Support.
  • For on-prem instances of Execute:
    • Always ensure you have a recent backup of your Execute database before updating.
    • Download the installer from the Client Portal.