ComboCurve: Company Level Econ Guide

ComboCurve: Company Level Econ Guide

Company Level Econ Models and ELTs  (CLMs)

Purpose

  • Allows standardization and management of economic assumptions across an organization. 

  • Helps ensure the right economic assumptions for critical workflows, such as reserves, are being used across all teams and projects by providing 1 unified place to manage these models 

  • Saves time and reduces repetition from project initiation to evaluation by removing the need to make or import the same models into every project. 



Who Can Create CLMs

Econ Model Administrators and Administrators can create Company Level Econ Models



How To Create CLMs


To access go to the Company page.



From the Company Page, Administrators will now see 2 new tabs: Econ Models and Lookup Tables




Inside the Econ Models tab a user can perform all options as normal at the Project Econ Models pageHighlights include Create, Delete and CSV Import/Export.  



All Econ Assumptions except for Fluid Model and Emission can have Company Level ModelsGeneral Options models have also been added to the Econ Assumptions top bar so they can be created and managed in the same dialog other models are created at the Company Level.



Embedded Lookup Tables are created and managed on the Lookup Table tab and this tab behaves the same as the Embedded Lookup Tab inside a projectCompany Level ELTs can also be created directly while inside the Capex or Expense assumptions.   




Applying Company Level Models

Once a Company Level Model (CLM) is created, it can be utilized across all projects.  There is a new Company Tab when assigning models to single wells or a group of wells.  Company Level Models can be saved as project or unique models to bring them down to the project level and allow updates at the project level.  




When a Company model is assigned to a well there is a new icon to differentiate it from project models.   




Technical Specifications 


Creating/Updating/Deleting

  • Company Level Models can only be created, updated and deleted by Administrators and only in the Company Econ Model Tab.  

  •  Making a change to a company model will most likely impact multiple projects/scenarios/users. 

    Headers

  • Company Level ELTs can reference Standard Headers and Company Level Custom Headers

  • Headers not referenceable: Chosen ID, INPT ID, Aries ID, API14, etc.   
    Headers not referenceable: Chosen ID, INPT ID, Aries ID, API14, etc.  
     

    • This to reduce creating a lookup with too many rows to manage with a potentially large company well list. 


Sharecode abilities

  • CLMs are Archive/Restore and Sharecode compatible.   

    • Any CLMs that are assigned inside a project will be converted to project models upon archive and sharecodeThe model name will be suffixed if the name is already taken inside the projectWhen restored these will remain as project models to preserve the snapshot that was archivedComboCurve ONLY will only perform this action on CLMs that were used in the project. Other CLMs that exist during that time will not be included in the archive or sharecode.  This ensures that clients who are utilizing CLMs are not unintentionally share coding economic assumptions they do not wish to share with a third party.

Project Level/Unique Models

  • CLMs can be named the same as Project or Unique models.   

    • This is intentional functionality designed to prevent a user/project from blocking a very common or desirable name for an econ model (70 Flat for example).  HOWEVER: 

      • CSV Import/Export Changes:  The model type column now supports “Company” as an option. If there is a CLM that matches the name in the export then it will assign the company model.  If a user has company level escalations, depreciations or ELTs that are assigned INSIDE another econ model with the same name there will be no way of identifying if they intended to assign the Company or Project Escalation/Depreciation/ELT.  Therefore: 

      • Company Level Escalations, Depreciations, and ELTs cannot be assigned to Project or Unique models.  Company assigns to Company, Project assigns to Project.  This is due to the naming methodology described above.

    • A user cannot edit a CLM inside a project, they can choose to save the CLM as a Project or Unique Model to be able to edit at a Project Level.   

      • If you do this, you will need to save and reassign any Company Level Escalation, Depreciation and ELTs as its own project model first.   

Scenario Lookup Tables

  • CLMs can be utilized inside Project Scenario Lookup Tables.

  • Company Level Scenario Lookup Tables are not compatible with CLMs at this time.

ECL in Dates

  • The link to ECL functionality that exists in the Dates Model does not exist for Company Level Dates Models.

API abilities

  • CLMs will not supported through the API upon initial release. It is however, planned to be developed in the near future.


Commonly Asked Questions 

Q: Is it possible to convert existing project level models to company models? 

A: There are multiple ways to accomplish this:  

  1. From scratch in the UI (copy paste or manual input) 

  1. Export the project model, change Model type to Company in the csv and rename model to desired name, CSV Import on the Company Econ Model Tab 

  1. Through the External API 

 


    • Related Articles

    • ComboCurve: Scenario Tooltip Overview Article

      Scenario Tooltip Overview Article Scenario Page (Overview of Main Screen) Top Left Hamburger Icon - to navigate to all CC sections Green Scenario Name - Quick navigation to the project landing page Top Right Guy Icon - Change name, password or log ...
    • ComboCurve: Company Custom Headers and Company Custom Streams

      Company Custom Headers Company Custom headers can be created at the company level under the custom columns tab. Inside the custom columns tab you will see that two options, well headers and production steams. Clicking on well headers allows the user ...
    • ComboCurve: Expenses

      Expenses See the Scenario Tooltip Overview Article for all assumptions and modeling concepts Key Key's allow the user to select which type of expense the would like to model. These key's can be stream specific or a fixed expense. Category Category's ...
    • ComboCurve: Differentials

      Differentials Options See the Scenario Tooltip Overview Article for all assumptions and modeling concepts 1st, 2nd, and 3rd differentials can be used to model increases or reductions in realized product pricing relative to basis (NYMEX). These can be ...
    • ComboCurve: Group Permissions

      Overview Group Permissions allows administrators to create groups and assign user roles to those groups to quickly and effectively manage user access to projects. The purpose is to allow companies to better manage users in their environment. For a ...