Instantly find mistakes in your ARIES forecasts with Pod2's Validator
Pod2's Validator saves you time, money, frustration and prevents multi-million dollar mistakes from slipping through the cracks.
Mistakes happen. You're spending too much time finding and fixing them, and you're probably missing some.
Don't you have better things to do?
What people are saying
“The Validator tool has been a key link in our outlook process. It's proven invaluable at catching the errors that end up in Aries. It's replaced multiple Spotfire and Excel check tools and cut our forecast validation times by at least 4 hours a cycle.”Bari GbosiDevelopment Planner, Ensign Natural Resources
“Just rocked my world finding errors in one of our databases. Seriously it helped QC production forecast lines better than anything I've ever had.”Reserves Manager
“If we would have had this a year ago, it would've solved a lot of our problems.”Reservoir Team Lead
“The only downside is that it found a whole lot of things that we need to clean up.”Reserves Engineer
“I like how it has an actual explanation, and not just 'Error on line 701'.”Team Lead
“We've had to fix zero things the last two cycles because it forced us to correct all the busts.”Planner
Start improving your forecasts right away with a free two week trial.
How much is your existing process costing you?
Estimate how much these mistakes at your company are already costing you. Most companies spend at least a few days per month on QC or trying to identify where problems originally occurred.
You're spending $30,000 per year on this and risking $1,000,000 in value.
Fast and easy ARIES quality control
Whether your QC approach is 38 Access queries, SQL processes, sense checks, or hope, the Validator can make it faster, easier, and identify problems you didn't know you had.
Here's how it works:
- 1Connect to your ARIES DB
- 2Pick your project and scenario (or qualifiers)
- 3Click 'Validate'
That's it. In seconds, you'll have a filterable, copyable, list of potential problems to fix.
Check out the 137 different validation checks the Validator can take care of for you. We're adding more every week.
From this
To this
Prevent more errors, faster, with the Pod2 Validator.
What you get
Increased confidence in forecasts
Previously undiscovered value or expenses
Improved forecast accuracy
Accelerated quality control
Better valuations than your competitors
More time to focus on what's important
Fix your forecasts today
Sign up for a free two week trial to QC your database right away.
Pricing
Prices depend on the total number of wells in the ARIES projects that the Validator will be used with.
There are three tiers of subscriptions, and each subscription is assigned to a single person. Monthly and yearly subscriptions are available, with a 10% discount applied if the yearly option is chosen.
Lite
$100/month or $1080/year
Up to 1,000 wells per run
Standard
$300/month or $3240/year
Up to 5,000 wells per run
Super
$500/month or $5400/year
Up to 10,000 wells per run
Please contact us to discuss high-volume pricing options (projects with more than 10,000 wells, many subscriptions, or something else).
Frequently asked questions
Doesn't ARIES have error checking built-in?
Absolutely! ARIES has some error checking that happens during calculation.
But this error checking doesn't catch everything, and even common mistakes like missing forecasts or over-defined forecasts (too few unknowns) are not caught by ARIES.
Because of this, many companies have created their own QC process to validate ARIES inputs outside of ARIES.
The calculations in ARIES also can take a significant amount of time to run, so checking for errors across an entire ARIES project could take a long time.
In contrast, the Validator takes seconds to run, and performs many useful validation checks that aren't included in ARIES itself. This allows you to fix problems quickly, prior to waiting for a full ARIES run to complete.
What do you do with my ARIES data?
Nothing.
Pod2's Validator runs locally on your computer. It reads from your ARIES database the same way ARIES does, analyzes it, and gives you the results.
We don't extract or alter your data in any way.
Can't you do this with SQL queries?
You can definitely perform QC checks using SQL queries. Many companies currently do this.
However this usually involves a manual process of running queries, then combining query results into a summary, and afterwards verifying problems individually. Queries have to be created by somebody comfortable working directly with SQL. These queries can get very complicated, especially if you're using multiple qualifiers in a scenario, or validating economics expressions.
This is all possible, but it also this takes up valuable time. Pod2's Validator can save you that time.
Queries also tend to be created only after the same mistakes were made multiple times. Instead, the Validator could help you to take a proactive approach and catch these mistakes instantly.
Getting past IT hurdles is a pain, can you help?
We'll make it easy. We'll communicate directly with your IT and take care of this for you. We have experience working with IT departments of all sizes.
What does Pod2's Validator check?
Currently the Validator checks economic inputs for the following:
- Cannot load lookup table
- Cannot load macro value
- Cannot load sidefile
- Characteristic time out of range
- Continue line without line to continue from
- Date contains day
- Date earlier than framework base date
- Date earlier than product start date
- Decline rate has wrong sign
- Decline rate out of range
- Economic loss method different than expected
- Expense uses start line from previous section
- Exponent out of range
- Expression has too many entries
- Extra lookup parameters provided
- Extra spaces in Show ID
- Final decline rate cutoff rate out of range
- Forecast is over-defined
- Forecast is under-defined
- History stream column missing
- Hyperbolic or harmonic forecast inclines
- Hyperbolic or harmonic not followed by exponential
- Incomplete expression
- Interest too high
- Invalid characteristic time
- Invalid cumulative volume
- Invalid decimal year date
- Invalid decline rate
- Invalid economic loss delay
- Invalid economic loss interest
- Invalid economic loss method
- Invalid economic loss minimum life
- Invalid economic loss overhead
- Invalid economic loss present worth rate
- Invalid expense
- Invalid expense ceiling
- Invalid expense cutoff
- Invalid expense escalation
- Invalid expense unit
- Invalid exponent
- Invalid final ratio
- Invalid forecast cutoff
- Invalid forecast final rate
- Invalid forecast initial rate
- Invalid forecast method
- Invalid initial ratio
- Invalid interest
- Invalid interest fraction
- Invalid investment amount
- Invalid investment method
- Invalid investment point
- Invalid label date
- Invalid life absolute date
- Invalid life duration
- Invalid life origin
- Invalid list date
- Invalid list units
- Invalid list value
- Invalid lookup parameter
- Invalid macro name
- Invalid macro operation
- Invalid ownership change point
- Invalid ownership escalation
- Invalid ownership phase
- Invalid ownership unit
- Invalid payout stream
- Invalid price
- Invalid price ceiling
- Invalid price cutoff
- Invalid price escalation
- Invalid price phase
- Invalid price unit
- Invalid ratio correlation
- Invalid ratio endpoint
- Invalid section
- Invalid slash date
- Invalid start date
- Invalid start date delay
- Invalid stream arithmetic cutoff
- Invalid stream arithmetic limit
- Invalid stream arithmetic limit unit
- Invalid stream arithmetic operator
- Invalid stream arithmetic source
- Invalid stream definition table alias
- Invalid stretched exponential decline start date
- Invalid unit
- Investment unit contains thousands prefix
- List line too long
- Lookup column contains invalid number
- Lookup column contains value without type
- Lookup interpolation value too high
- Lookup interpolation value too low
- Lookup line has less answers than required
- Lookup line has more answers than required
- Lookup line used default row
- Lookup match instruction contains space
- Lookup table does not contain a matching row
- Macro does not have a value
- Major phase doesn't have a forecast
- Major phase is not the first forecast
- Major phases do not match
- Missing abandonment line
- Missing loss line
- Multiple loss lines
- Net revenue interest larger than working interest
- Not enough lookup parameters provided
- Ownership unit does not match required unit
- Phase has history but no forecast
- Phase production defined multiple times
- Price ends too early
- Price starts too late
- Prior cumulative volume greater than ultimate gross recovery
- Producing well starts after effective date
- Producing well with investments
- Production without price
- Project property does not exist in database system
- Propnum has long text data type
- Ratio denominator has no production
- Ratio line before independent phase
- Ratio numerator starts before ratio denominator
- Ratio segments have different correlations
- Segments overlap
- Sidefile section empty
- Sloped ratio with life duration
- Special character in Show ID
- Undeveloped well has missing book date for SEC 5 year rule expiry
- Undeveloped well starts after SEC 5 year rule expiry
- Undeveloped well without investments
- Unknown final ratio
- Unknown initial ratio in first segment
- Unknown lookup table name
- Unknown phase name
- Unknown sidefile name
- Unknown start date
- Unknown table alias
- Wrong units for phase type
- Zero working interest and non-zero net revenue interest
This list grows constantly and we're currently prioritizing a list of QC checks to add next, so please let us know if there are other checks that would be useful to you.