Other Miscellaneous Enhancements and Bug Fixes

Roll Forward

In Enersight 2.17, we have reintroduced the ability to manually change the Project Start Year to a date in the future without running the Roll Forward wizard. The behavior is the same as previous versions of Enersight and allows you to avoid the schedule manipulation that occurs during Roll Forward. Note that using this process still requires substantial manual manipulation of inputs to align with the new Project Start Year.

In terms of the Roll Forward wizard, when a project is rolled forward, the last value in a time series table is now copied to the new periods that have been added to the table as part of the roll forward process, reducing the amount of manual adjustment required for time series tables after rolling forward.

UI Updates

In our continuing journey to modernize the look and feel of Enersight, we have updated many of the modal dialogs with a modern style. We've also added more informative 'action' text to many of the buttons to make sure it's clear what will happen with a specific choice.

We have also changed the way you cancel a calculation. Previously this was accomplished using a common keyboard shortcut, Ctrl + C, which led to accidental cancellations. Now there is a 'Cancel Calculation' button that asks you to confirm before canceling.

OData Reports

  • The capability to return grouped data via OData Reports to Excel and PowerBI when 'Show Asset Detail' is checked has been added. Previously, this returned an error in these applications.
  • In some cases, ReportDataArray endpoints were only returning a subset of requested data columns when requesting data using Excel or PowerBI. This has been fixed.
  • We fixed an issue with some PDSs returning data offset by a year if the PDS Start Date did not match the PDS Reporting Date.
  • Some configurations of scalar data in report headers was causing the ReportDataScalar endpoint to fail when requesting data using Excel or PowerBI. This has been fixed.
  • When Daily data was requested from OData Reports in previous versions, the day in the Date field was not correct. All dates were the first day of the month. The correct day is now included in the Date field.

Network Solver Enhancements and Fixes

  • In the V3.1 solver negative Oil and NGL shrinkage at Facilities is now supported. Production will be increased appropriately when shrinkage is negative, but note that this is not the case for Fuel/Flare Shrinkage or ByProduct Extractions due to the more complex interactions of Gas products.
  • In the V3.0 and V3.1 Solvers, timesteps that returned an infeasible solution will now reiterate without the global minimum rate of take, well minimum rate of take, or well minimum rate to find a feasible solution. Note that this may change existing results in cases where some timesteps previously returned infeasible values (indicated by a warning in the calculation log, e.g., Current best solution is not optimal Time Step 115, Aug 2032).
  • A bug was fixed where solver V3.1 removed network diamond structures with a constraint on the base of the diamond and this constraint was ignored. Similarly, in networks with two diamond structures with the same target node, if the target node had a constraint it was not being respected. This has also been fixed.

Risk Scripting and Script Scenario Changes

In Enersight 2.17 we have included three powerful new risk scripting commands that allow you to replace an entire Well List, Resource Definition, or update an existing User Data Table allowing for much more robust manipulation of models using script commands. This functionality leverages Enersight's document upload feature in that you upload an Excel file with the inputs for the modified Well List/Resource Definition/User Data Table and reference that file in the script command. More info and examples can be found here: Script Scenarios

We have also added a command that allows you to clear a User Data value (or set it back to the default value if 'blank' is not an option for that user data type) has been added. The command UserData:Clear will revert doubles and integers to 0, clear strings and dictionary entries, and set dates to the default project start date. This is available in both Script Scenarios and in Risk Scripting.

Related Bug Fixes

  • When converting a script scenario to a permanent scenario, activity duration for scheduled activities are now updated based on the value in the Activity:Duration command. Previously these durations were not saved when converting a script scenario to a permanent scenario.
  • If a risk script command references a User Data field that doesn't exist and this command is part of a set of commands in the same group, the entire group of commands will fail with an error indicating the invalid User Data reference.

Miscellaneous Enhancements

  • We've added new reporting function, @CustomRollupProduct, that will report a Custom Calculated value that 'follows' a particular product through the network. A limitation of the existing CustomRollup() reporting function is that it ignores pipeline splits and values reported at facilities after a product is split are incorrect. The new function reports values that respect the pipeline splits of the product specified in the function arguments. This will be useful for emissions reporting in complex networks where the values currently reported at nodes after pipeline splits are not taking product splits into account.
  • Two new Fixed Data Type has been added to the function editor: Downtime Local and Downtime. Downtime Local reports the downtime due to Scheduler Well List shut ins (i.e., the Well List column 'Shut In Production At These Wells') as well as OFI shut ins from a scheduled activity distance halo in the advanced settings on a drilling step. Downtime reports the combined downtime from all downtime events.
  • The frequency of login sessions timing out has been reduced, resulting in the user having to clear Enersight cookies less frequently. On the Enersight login screen you may have seen the message 'Your login session timed out. Please restart.' if the browser was left idle. With this change, this will occur less often, streamlining the login process.
  • The maximum number of cores available for concurrent scenario calculations has been increased to 6. This only applies if there are sufficient available Risk Scripting cores licensed by your company, otherwise the maximum number of concurrent scenario calculations remains at 3.
  • For clients using SAML authentication, we have added the ability for our support team to specify the application version selected by default on the login screen, preventing users from accidentally logging into the new release until you have completed your UAT/sanctioning process. This default selection can be updated to the newest release upon request once this process is complete.
  • In anticipation of the BC Government possibly delaying the implementation of the 2024 Royalty Framework we have added the option to change the Start Date of the new framework. When legislation is finalized, Enersight will be updated as necessary, but this will allow for flexibility in the meantime.
  • Logging has been added when an Integration License is released to better enable tracking of these Licenses.

Miscellaneous Bug Fixes

  • When an invalid resource was specified in a Well List, the error in the calculation log did not indicate which well had the issue. The calculation log messaging has been improved to provide the name of the well.
  • In previous versions of Enersight, having a Report Group with PropID and using Group by Flow Path resulted in no assets being returned in the report. In 2.17, Group by Flow Path works as expected when PropID is included in an associated Report Group.
  • In some cases, the 'Use Historical Production' Scenario option was causing production to increase unexpectedly after rolling forward. This has been fixed.
  • When copying a scenario, you are now prevented from performing other actions while the copy is occurring. In some cases, projects were becoming corrupted during long copy operations and this will help prevent the message 'Project cannot be saved. A newer version of the project exists in the database.'
  • An issue with CSV import for BC and Alberta Royalties has been fixed. When importing into fields with a function in previous versions, the function would not be overwritten as expected.
  • In User Data tables, pasting scalar values into a field with a function resulted in the field reading NaN (not a number). This has been fixed.
  • After saving a project to PDS, if the project was then deleted from the top menu (Project > Delete Project) an apologies page was displayed. This has been corrected and the project is now deleted as expected.
  • When a Rate Acceleration Factor was applied to CO2 and the Project Option 'Decline Rate-Accelerator Factors Change Reserves' was checked, the reported Gas Decline on the Production tab was incorrect. This has been corrected.
  • In some projects, if a Script Scenario was renamed and the Gantt Chart was opened immediately after this change, the Gantt chart would not populate with data. This has been fixed.
  • When the Project Option 'Decline Rate-Accelerator Factors Change Reserves' is checked, the option below, 'Allow Rate Factors to Decouple Product Timing', was implicitly selected but this was not reflected in the UI. The second checkbox remained unchecked. Now, the second checkbox is checked, making it clearer what the expected behavior will be.
  • Potential SQL injection threat was mitigated in one of the admin utilities.
  • In some cases an integration license would not get abandoned correctly, preventing a user from obtaining a license on login. This has been fixed.
  • In many of the input modals, clicking the X at the top right of the modal resulted in a delay before the modal closed, while pressing Cancel closed the modal immediately. Clicking the X now closes the window immediately as well.
  • In previous versions of Enersight, functions using @MonthStep or @DayStep in extraction inputs were being calculated incorrectly due to the wrong date being passed during the function evaluation. This has been corrected, but may lead to changes in values being extracted.

2.17 Hotfix Changes

  • The Export to Cloud Storage functionality has been enhanced to allow exports to Azure Blob Storage and Amazon S3 Cloud storage.

  • Enabling 'Auto-refresh' on the Reports tab now immediately refreshes the selected report.

  • The script command DrillingProgram:WellList has been renamed to WellList:Replace to better align with UserDataTable:Replace and Resources:ReplaceAll. Existing projects using the command DrillingProgram:WellList will still calculate as expected.

  • The script command WellList:Replace (formerly DrillingProgram:WellList) can now be used to replace a Scenario Well List. Simply leave the second argument (Drilling Program) blank to target the Scenario Well List. Note that it is not recommended to have both a Scenario Well List and Drilling Program Well Lists in the same scenario, as this can lead to unexpected results.

  • New API endpoints have been added to enable automation of replacing a Well List, Resource Definitions, and User Data Table values in risk scripting runs.

  • Error detection and messaging for the script command DrillingProgram:WellList has been improved. When there are column header mismatches, the calculation log will now indicate the first mismatch detected to enable easier correction.

  • OData4 caching enhancements have been made with the aim to improve the stability of the OData4 service.

  • A regression bug has been fixed where a Resource was not saved to the project after being manually copied.

  • A regression bug has been fixed that was causing Script Scenarios and Risk Script runs to exit early under certain circumstances. If a run had a user data field that was not present for all asset types, this was seen as an error by the scripting engine and the run was canceled. Now Enersight correctly checks all asset types for a User Data Field before determining that it does not exist.

  • The modal that appears when the network connection is lost now closes automatically when the connection is restored, which was the behavior of the old style modal in prior versions of Enersight.

  • If multiple resources specified in a Drilling Program was not found during calculation in 2.17, the calc log only recorded an error for the first instance. This has been reverted to record an error for all instances of a resource not being found.

  • A regression bug was fixed where new PlanningSpace integration keys could not be saved.