FAQ Overview:
ComboCurve can be a super powerful tool, however with its vast functionality sometimes hitting a brick wall during a workflow can happen. In this document we will go through commonly asked questions and issues users run into and ways to fix them. The organization of this document will broken up into the main sections of the software.
The Following Sections will be Covered:
- Maps
- Sharecode
- Data Import
- Forecasts
- Type Curve
- Lookup Tables
- Scenarios
Maps:
I am trying to import a shapefile and I am getting an error?
There are a few things to check off the list when importing a shapefile:
- File contains a .dbf, .prj, .shp and .shx2. All file names are the same
- All file names don't contain special character like an % sign
- File folder is zipped
If you want to confirm the file is working and to check the shapefile you can drop it in
https://mapshaper.org/
Sharecode:
How do I import a sharecode given to me?
To import a sharecoded project simply navigate to the projects tab in the right menu, then at the top there is an option to import project. Once you paste in the code and give the project a name, it will prompt you to header match. For most sharecoded projects just click the map suggested button since these are projects coming from ComboCurve to ComboCurve, the headers will be the same. However always double check to see if there are any project or company project headers associated with your project. If there are custom headers right under the sharecode and project name imputs when you first create the import, select advanced sharecode instead. All advanced sharecode does is matches the custom headers over into the new project.
How do I send my project to another ComboCurve User?
To share a snapshot of your current project to another ComboCurve user we will need to create a sharecode for the project. To do this in the project you wish to share at the top there will be an tab called "Sharing". In here you can create or delete sharecodes related to just this project. It is also important to note you can select dates for this sharecode to expire on it own. Note: Everything in the project will share over (models, scenarios, forecast, type curves, etc.)
Data Import:
I am trying to import updated production data, but they are showing a new wells?
In ComboCurve there are 3 identifiers that must match in order for a well to match an existing well.
1. ChosenID
2. Scope
3. Datasource
Going through each first with troubleshooting ChosenID make sure when you do your header matching that the header you choose to create the ChosenID's are the same or are the ChosenID header itself. For example if existing wells were created using API 14 as the unique identifier ComboCurve has an algorithm that will result in the same ChosenID if created again based on the same API 14. If the updated data has a column for ChosenID already just match that column.
For Scope, Scope has two options: Company or Project level. If you are in a project full of company level wells you will not be able to update these wells existing production. You will have to perform a Company level import but beware this updates these wells across the entire environment. I saver option is to go into the project wells page withing the environment and using the Operations drop down, change all the wells from company to project level then import again. This will essentially copy the wells from the company level and allow you to update them via import without changing the Company level well. Converting company level wells to project level just in your project.
Lastly and probably the most commonly overlooked is Datasource. Datasource is just a categorical value assigned to wells via import. The goal of this value is to allow the user to have the same well in a project but different variations of it based on where it was imported from for comparison. When you import it is important to check what Datasource your existing wells are set to, and on import make sure the Datasource is set to the same value. This way ComboCurve knows you are trying to updated those existing wells.
Odds are if the button is greyed out then there is a problem with the file. Make sure the file is a .csv file unzipped and that the file is not too large. The maximum size file we can handle importing is limited by the maximum rows allowed in Excel.
I am uploading daily production data but my excel is way too large, and I cant even open the file in Excel?
In the event that you have a production file that is way too large to even open. Open the excel file as a .txt and split the excel up into smaller files. Then import each of these files separately.
I have checked all 3 identifiers but my wells still are showing up as new wells?
This is commonly due to two things with one being a straight forward missed step and the other being a little more complicated. The easy one is that the user needs to make sure to check on the last step that the "Wells Import Mode" is set to Update Existing. This way you can see only the wells on the right side of the screen that ComboCurve identifies as existing and is matching. The harder one is there is something wrong with the excel file, open the excel file and make sure the main ChosenID identifiers line up with what you would expect.
I am trying to update production for existing wells but a few of my wells are showing up as new, while others are showing up as existing?
This is almost always a problem with the Datasource. Sometimes we have wells in a project with different data sources, so when we try to import new updated production data to the entire database we can only choose one Datasource at a time. So for the initial import we will see the existing wells are the ones who match the Datasource we have selected for that import, while the wells showing up as new have a different Datasource.
This is an easy fix though, which we do by doing two import. The first import make sure the " Wells Import Mode" is set to Update Existing. When set to Update Existing this will ignore the wells it is identifying as new wells and only update the ones it sees as existing. To import the remaining wells, simply do another import but this time change the Datasource to the other one and make sure to set "Wells Import Mode" again to Update Existing. This way now all wells are updated and now duplicate wells were created.
There is another option though that may be easier and that is changing the wells with a different data source to all have the same in the Project Wells tab via the Operations drop down menu. This way when you import all the wells will have the same Datasource and two imports is not required.
I have accidentally imported a bunch of duplicate wells, is there a way to easily delete the duplicates?
Yes there is! To delete a bunch of duplicate wells that were imported on accident simply go to the project wells tab and add the header "Import Date". Then delete all of the wells that were imported on that date.
Forecasts:
I have ran an auto forecast on my wells, but the forecast doesn't appear on the graph once complete?
When a forecast doesn't show up after running an auto forecast there are two possible issues: we don't have the forecast turned on to show or we have an issue with our auto forecast parameters. Starting with the easiest make sure in the Streams dropdown menu that the forecasts are checked on.
The more complicated issue is that our fit parameters are causing an issue however there are a few things to check. First make sure that the date of the Peak Preference you have selected falls withing the range put in the Zero Forecast range. This range is the days from today's date to go back and look at the data. Typically if we have really old well data this is the issue, the historical production data falls out of this range and our auto fit does not pick it up. The next fit parameter that could be causing an issue would be in the Filtering section. The entire goal of this section is to remove data as outliers so if these values are too strong we could be removing all of our data. So check these values and make sure they are not too harsh for the data set you are trying to encompass. Lastly I would check the Low Data forecast section, this sections purpose is to exclude wells who have few historical data points. So if your wells only have like 2-3 data points, the issue most likely resides with the value set here.
Why is my custom stream not showing up?
If you have a custom stream and you are not seeing it on your forecast graphs there are two things to check. The first is in Forecast Options and the Stream Management tab to make sure the custom stream is enabled. The next is the Streams dropdown which toggles what data is populated on the chart. Both of these you will find in the tabs right above the forecast charts next to the blue Run Forecast button.
This is typically an issue with those headers not being filled out for that well. Search for that well in the Project Wells page, add the header you are referring to and make sure that a value exists for that header. Secondly if they still do not show up try logging out and relogging in or refreshing the page. Sometimes these values can take a little bit to populate and won't show if the page isn't refreshed. If none of these work and the values still don't populate reach out to support. We have seen some weird one off bugs related to this feature where a forecast might've been imported from another source or project and the header values exist but can't be referenced from the forecast section at a data storage level.
Make sure the header you are adding is a company level header, as of right now we do not permit project level headers in the forecast section. If you do find that you have a project level header and need to add/filter to it on the forecast page, make a new company level header and copy the value over to it.
How do I delete a segment in the Manuel Forecast page?
This may sound like a lot of clicks, but that is intentional. We want to make it harder to delete segments because deleting a segment is irreversible. To delete a segment first click on it on the editing graph to the right. Next click delete on your keyboard. Now the segment will be deleted and you can save the forecast without this segment.
Why can't I run a Ratio Forecast for Gas and Water?
In order to run a ratio forecast you must also run a base forecast. So for example you will also need to run a forecast for oil and have it set to base, while Gas and Water are set to ratio.
How do I change all my wells to Monthly or Daily data resolution quickly?
Download the forecast parameters excel sheet and look for a data resolution column. Here change the word Monthly to Daily or vice versa, save. And then import these forecast parameters back into ComboCurve.
Type Curves:
I have ran a type curve fit but I don't see it on my graphs?
In the setting icon on that graph make sure that "Background Wells Only" is toggled off. This is a really helpful feature when you want to zoom in to just your rep wells and maybe exclude a well.
When I run a Type Cure Fit it just errors out?
If your Type Curve keeps running into error every time you run it. First try making sure Align Peaks is toggled on, sometimes our rep wells have a lot of build up data and not having Align Peaks turned on can give the algorithm a hard time.
Why is my Type Curve failing to get a Fit Percentile?
When this happens check if your P90 Fit goes to zero much earlier than the P50/P10. Adjust your fit parameters and rerun the fit.
Lookup Tables:
General note: If lookup tables are not working correctly it is almost 90% due to missing header information or missing models being referenced. Check all headers and make sure all models exist and the names in the lookup table match exactly.
I have applied a Type Curve Lookup table as my wells Forecast, but my Scenario is failing?
Since the wells have their forecasts applied through a Type Curve Lookup Table you will have to do a few more clicks to find the issue. More than likely the Type Curve Lookup Table is not matching to these wells. There are a few things to make sure to check:
1. Make sure the Type Curve Names in the Lookup table match Type Curve Exist and the names are exactly the same
2. Make Sure whatever headers you are matching to in the Lookup table exist in the Project Wells tab for theses wells
3. Lastly while it sounds silly it happens often. Check the Type Curves you are matching too and make sure there is a Type Curve Fit actually saved
I have a Type Curve applied to wells via a Lookup Table which is normalized on PLL, but my PUD wells all show the same PLL?
This is a simple fix, make sure the option in the Type Curve lookup table for Normalization is set it Yes. If this doesn't work make sure the well you are applying the Type Curve too has whatever header (in this case PLL) is filled out. If the PUD wells don't have an assigned PLL, no normalization will be applied.
Scenarios
I have a well that is showing no production when I run the Scenario?
A well can show no production in the Scenario for multiple reasons. To start go to the dates section and set the Cut Off to No Cut Offs. This option will no matter the quality of the well run until the end of econ life. If you turn on No Cut Offs and see production now, then you know the issue resides in the models that affect economic performance. So for example maybe you have an error in Pricing where Oil is only like $5/BBL instead of $50/BLL or maybe you have an added zero to an expense/CAPEX. Also make sure if you have ownership values for WI and NRI that are very small, make sure the Lease NRI is set to a value in between 75-85%, this is a ComboCurve calculation situation just needed for Cut Off Purposes.
If you run No Cut Offs and see no production still then you know there must be an issue with Ownership/Forecast/Dates. These are all independent and will all need to be checked. Starting with Ownership make sure that your NRI isn't 0, it happens more than you think either by mistyping or a bad import. Next make sure that the well has a forecast assigned and that the forecast makes sense, you can quickly check in Scenarios by using the Modular Forecasting option to view this wells forecast. Lastly Dates, start in General Options and make sure the Aggregation Date is set to a date before your wells Production or at least before you As of Date. The Aggregation date is the date that tells ComboCurve when to start intaking Production Data for calculation. Next make sure your As of Date is either the same or after the Aggregation date. If you As of Date is before the Aggregation Date then you will see a section of zero production data in the range of dates between the two. The As of Date is the date to which the economic run starts.
Why is my EUR different than the EURs shown in the Forecast page?
Dates, Dates, Dates. The EUR in the forecast page runs for a different length than that of the economics ran in scenario's. Make sure to check the aggregation date, As of Date, FPD selection, Cut Offs, and econ life. Odds are one or a combination of these are causing the econ to run longer or shorter than that of the stock forecast thus resulting in different EURs.
Why am I not seeing CAPEX on my wells?
Odds are the setting in Dates called Cash Flow Prior to as Of Date is set to no. Change this value to yes which allows CAPEX values to start before the actual start date of the given econ run. This typically happens when you have a wells CAPEX hit days before the FPD, but just so happens the As of Date is either the FPD or a date after that CAPEX hits and thus without the option set to yes these values won't appear.
What do the color dots stand for next the models?
The color dots indicate how a model was created. Green is for project level assigned models, Orange is for unassigned, Blue is for lookup table assigned, and lastly purple for unique assigned (odds are purple are imported models).
How do I create a Qualifier and what is a Qualifier?
Think of a Qualifier as a saved folder containing all the models assigned to those wells. For example for one of my Qualifiers I want all my wells to have one forecast, then another Qualifier have a different forecast. Doing this allows the user to switch between different assigned models for an economic assumption quickly and easily. To create a Qualifier go to the top of a column in the Scenario table the Qualifier that exists before any are created is labeled Default. Next to the word Default click the 3 dots and select the Create Qualifier button and give it a name. Once you create it you will notice all of you models goes to none, don't be alarmed all the models that were applied were saved under that Default Qualifier from before. To add models to the new Qualifier simply just assign the models as you wish to the individual wells and it will update as you go.
Can I run multiple Qualifiers at once?
Yes you can! This is important for sensitivity analysis when comparing different changes in economic models for a group of wells and comparing the differences. To run multiple it is easy, when you click Run Scenario in the menu at the top there is a tab called Combos. Here you can create different Combo aka different economic runs and select which Qualifiers you want for each. When you then run the scenario with the different combos it will run economics for each combo.