Company Level Econ Models and ELTs
Use Cases:
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.
Technical Walkthrough:
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 page. Highlights include Create, Delete and CSV Import/Export. All Econ Assumptions except for Fluid Model and Emission can have Company Level Models. General 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 project. Company Level ELTs can also be created directly while inside the Capex or Expense assumptions.
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:
Making a change to a company model will most likely impact multiple projects/scenarios/users.
Company Level ELTs can reference the Standard Headers and Company Level Custom Headers.
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.
CLMs are Archive/Restore and Sharecode compatible.
Any CLMs that are assigned inside a project will be converted to project models upon archive and sharecode. The model name will be suffixed if the name is already taken inside the project. When restored these will remain as project models to preserve the snapshot that was archived. ComboCurve 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.
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.
If you do this, you will need to save and reassign any Company Level Escalation, Depreciation and ELTs as its own project model first.
CLMs will not be supported through the API upon initial release.
It is however, planned to be developed in the near future
CLMs can be utilized inside Project Scenario Lookup Tables.
Company Level Scenario Lookup Tables are not compatible with CLMS at this time.
The Link to ECL functionality that exists in the Dates model does not exist for Company Level Dates models.
Commonly Asked Questions:
Q: Is it possible to convert existing project level models to company models?
A: There are multiple ways to accomplish this:
From scratch in the UI (copy paste or manual input)
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
Through the External API