ComboCurve: Project Structure Best Practices

Project Structure Best Practices

Project structure varies by company type, size, and workflow. Please consult your dedicated Customer Success Engineer to discuss your specific use case.

Background - Company Vs Project Level Data and Well Limits

In ComboCurve, there are two data scope options: Company Level and Project Level.

Company Level

1. Company-level wells are displayed on the company page in ComboCurve and can be added to any project.
2. Accessible to all users and can be added to multiple projects.
3. Supported by CSV import, ComboSync, REST API, and Data Shares.
4. Wells imported to the company level are assigned a consistent INPT ID that remains the same across all projects.

Project Level

1. Accessible only within the project they were added to.
2. Wells imported to the project level are assigned a unique INPT ID, meaning they will only be recognized within that specific project.
3. Supported by CSV import, REST API, PHDWIN import, and Aries import.
4. For Aries and PHDWIN database imports, upload directly to the project level.

Maximum Well Limits

1. 50,000 wells per project
2. 25,000 wells per forecast set
3. 25,000 wells per scenario
4. 75,000 combo well limit (e.g., if a scenario has 25,000 wells, the user can run 3 combos)
   

Best Practices

Operators / Minerals

Company vs. Project Level

1. We recommend loading both private and public data for AOIs to the company level.
2. Private and public data can be blended before uploading, or the data source column can be used for front-end filtering to distinguish between the two datasets.
1. Example: Source = Internal for private data; Source = IHS / Enverus / Other for public data.
3. Using ComboSync, REST API, or Data Share capabilities eliminates the need for manual data imports.
4. If using manual data uploads, we recommend updating public data approximately once a month and private data at your preferred cadence. Save and reuse data mappings to streamline future imports.

Project Structure

1. Projects are typically organized by asset or area.
2. Common project setup:
1. Asset Master Project
1. Contains company-level internal wells.
2. Contains final/approved forecasts, type curves, and economics.
3. Information from area working projects is shared to the master project.
4. Archive regularly to maintain snapshots after major updates
5. Typically managed by 1–2 admins; most engineers have viewer-only access.
2. Asset Working Projects
1. Contains company-level internal and public wells within the AOI.
2. This is the primary project where day-to-day engineering work is completed.
3. Forecasts and type curves from this project feed into the master project for budget and reserves updates.

Banks / A&D Focused Shops / Auditors / Midstream

Company vs. Project Level

1. We recommend loading public data for AOIs to the company level. We recommend keeping the company-level well count below 1 million wells for optimal performance.
   
2. Using ComboSync, REST API, or Data Share capabilities eliminates the need for manual data imports.
3. If using manual data uploads, we recommend updating public data approximately once a month or at your preferred cadence. Save and reuse data mappings to streamline future imports.
4. For Aries and PHDWIN database imports, upload directly to the project level.

Project Structure

1. Projects are typically organized by evaluation or engagement.
   
2. Common project setup:
   
1. Evaluation-Specific Projects
1. The data scope (company vs. project level) depends on the evaluation type.
2. Example: A&D Focused: Each project represents a different evaluation
3. Example: Auditors & Banks: Each project represents a different client
4. Contains basin forecasts, type curves, and economics.
2. Basin Study Projects
1. Contains company-level public data wells within an AOI.
2. Contains basin forecasts, type curves, and economics.
3. Basin study projects are typically used to supplement evaluations within a specific AOI.

Additional Tips

1. Company-level econ models and embedded lookup tables can be used to standardize economic assumptions and reduce the number of repeat project-level models.
2. Shapefiles can be uploaded at either the project or company level.
3. Forecasts, lookup tables, type curves, econ models, and scenarios can be shared across projects.

• Related Articles

• ComboCurve: Forecast User Manual

  Forecast User Manual Forecast Module How to create a new forecast Creating a forecast in ComboCurve will follow the same basic steps as creating any object within a module on the platform. This process will begin by either being on the project ...

• 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: Forecast (Economic Assumption)

  Forecast (Economic Assumption) Forecasts are not interactive in the Scenario page but reside in the Forecast or Type-Curve modules in CC (Navigated by the project landing page or via the hamburger icon at the top-left of any screen) . Once created ...

• ComboCurve: Project Custom Headers and Project Custom Streams

  Project Custom Headers Creating Project Custom Headers Outside of the company level, the user can create project level custom headers. The user can navigate to the project wells page of the project of interest and locate the "Custom Columns" tab. The ...

• 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 ...