ARIES Imports - Currently Unsupported Items 

1. Across sections 
   
1. ARIES DB must have at least one valid Scenario and Input Settings
2. Import of Group Economics – must be manually rebuilt
3. Import of Incrementals - must be manually rebuilt
4. Discounting - only exact match is ARIES Monthly = CC Yearly (N=1) w/ mid-month 
5. MB, MMF volume limits – these are imported but may get transformed to dates or times
6. Escalations:  PC and PE are supported and some custom escalations may be supported but more complicated models may need to be remodeled.
7. Canadian Economics and International Fiscal Models not supported
8. Incorrect syntax and some partially filled lines whether ARIES gives an error or not.
2. Section 2 – Misc 
   
1. START keyword with ENDDATE is supported but DELAY is not supported
2. NOADD - use streams to calc and then zero them out 
   
3. P(S), RISK - Weighting & Risking of cases via these keywords although this is usually an easy remodel
   
3. Section 3 – ARIES Modeler (no support) 
   
4. Section 4 – Production 
   
1. Rate and ratio in one forecast or 2+ separate forecast lines for the same product 
2. WELLS & WLS are supported in CC Risking as “Wells” key but CC does not distinguish between Oil, Gas, Inj or other wells – they get added together as a single well count.
3. Custom phases are not imported but can be remodeled in CC.  CC imports only OIL, GAS, WTR, NGL and CND Yields. 
4. CPX - Exponential decline when reserves and life are known 
5. SED - Stretched Exponential Decline 
6. LIN & LOG CUM not supported in CC - treated as LIN & LOG TIME 
7. FILEXL, LOADXL, XL - external Excel or text file 
8. FILE - Outside files (e.g., “.A” price files) must be zipped together and can be uploaded with the ARIES database.
9. Over-defined lines may be interpreted differently in CC than ARIES
5. Section 5 – Prices (Nothing significant) 
   
1. Water revenue (PRI/WTR) or revenue from other custom phases can be remodeled in CC using Custom Streams
2. Complex combinations of additive and multiplicative differentials may not retain the same order of operations
   
6. Section 6 – Expenses 
   
1. Switching time series by two different methods (Date then Rate) 
   
2. Multiple tax models - will have to be added manually
   
3. ABAN and SALV and PLUG will import to Capex in CC
7. Section 7 – Ownership 
   
1. LSE/OWN is handled but combines ORRI into a single NRI 
   
2. REVOWN - Use a different ownership to calculate payout than modeled entity 
   
3. SSR - Sliding Scale Royalties 
   
4. Custom stream-based reversion triggers (such as removing expenses or prod taxes from payout calc)
   
8. Section 8 – Investments 
   
1. Esoteric items like MIX or tax treatment (manual remodel)
   
9. Section 9 – Overlays
   
1. Many transforms are supported, especially if they are simple selections in CC .  Anything using user defined work streams or complex, multi-line transforms are not.
   

1. Overall
   
1. Access Compact & Repair must be run on all exported databases
2. Projects will initially appear empty in ARIES and must be re-queried and saved in ARIES (Sort, Select, Total or F4)
3. Group Economics must be manually rebuilt because ARIES cannot allocate from the Group to the Well level.
4. Incrementals export but can vary largely due to construction, may be manually rebuilt
5. Well Collections – will export to ARIES but require the user to select “Exclude Group Members” in ARIES SST
6. Discounting - only exact match is ARIES Monthly = CC Yearly (N=1) w/ mid-month 
7. Discount table entries - ARIES warns if they are not in ascending order. It also uses the discount table for iteration so be thoughtful when creating this in CC.
8. Volume-based time-series triggers may be evaluated differently in CC vs ARIES.
9. Historical Production - Extreme amount of production data lines (>3MM or so) can cause failure to export and must be done separately and imported after-the-fact in ARIES. Only Oil, Gas & Water export to the AC_PRODUCT and AC_DAILY tables currently. It is possible to fill these in after exporting via csv.
10. Character limits - Long header names used in Data Snaps and ELT names will be truncated to ARIES maximums (20 characters) 
11. Embedded Lookup Tables (ELTs)
    
1. ARIES can’t do LOOKUPs (ELTs) with more than ~50 LT columns (it supports ELTs with up to ~5000 rows)
2. ELTs with lookup names greater than 20 characters.  ARIES does not read beyond character 20 so this can cause uniqueness problems.  CC now truncates and auto-numbers match items beyond the character limit to preserve uniqueness.  This will alter match nomenclature with _01 _02 etc.
2. General Options
   
1. “Aggregation Date” must be the same date used in the Date Model for “As of Date” for all cases
3. Reserve Category
   
1. Models in CC create an RSV_CAT header in ARIES with the interpreted acronyms. If another header is desired for export, this can be transferred after export manually.
4. Ownership and Reversion
   
1. CC reversions are evaluated in parallel (any can trigger first in any order). ARIES design of complex reversions can be difficult.
2. Selections in Dates for Prod Data Resolution can affect product-based reversion timing
3. CC and ARIES treat NPI differently.
5. Dates
   
1. All cases must have the same “As of Date” 
2. “Discount Date” = “As of Date” for all cases
3. Major/minor phase cut offs – ARIES will not run economics past the end of the major phase forecast. CC will allow minor phases to "carry" the well even after the end of the major phase forecast. Some edit of MAJOR @M.MAJOR is needed.
4. Cutoff methods - Some cutoff methods in CC do not have an ARIES analog and thus will produce incorrect cutoff timing. Some ARIES cutoff methods do not allow Minlife, ECL Delay, OPNET, etc and interactions can occur.
6. Forecast
   
1. ARIES requires a forecast in order to run and will not run beyond the end of the “major phase” forecast.  Exporter will create zero-rate forecasts when needed.
2. Project or Company Custom Streams are not exported.  These can be exported separately from Forecasting module later.
3. Hyperbolic Incline – ARIES does not have this.   Exporter approximates these with exponential segments.
4. Always export with “Include Zero Forecast”
5. CC evaluates forecasts daily while ARIES 
6. ARIES is monthly resolution and CC is daily.   Exports have two options to realign forecasts somewhat.  See the KB on Force Forecast History Match and Export Also As Volumes.  
7. Pricing
   
1. Start Price Deck from no more than 1 year before “As of Date” - excessive historical price data can cause errors in ARIES due to line limits. 
2. Long monthly price decks will be averaged to annual prices after the first 5 years.
8. Differentials
   
1. Start Diff Deck from no more than 1 year before “As of Date” - excessive historical Diff data can cause errors in ARIES due to line limits.
2. Long monthly Diff decks will be averaged to annual prices after the first 5 years.
9. Stream Properties
   
1. Loss/Flare -These affect the Gross volumes in CC but not in ARIES and can result in a mismatch on Gross volumes between CC and ARIES while Shrunk/Net volumes match.
2. Unshrunk BTU – ARIES has no analog for this so math is done on the value with reference to @M.UBTU
10. Capex
    
1. Abandonment delay will not export if it is in an ELT
2. Paying/Earning - ARIES has no good way to accept this so math must be done with @Macros reference to the multiplier or via INVWT or the exporter will calculate the resulting value and set it as the input value in ARIES
11. Expenses
    
1. PA Impact Fee for Horizontals and Verticals will be exported as a “Simple” fee.
2. Key or time series based on “Total Fluid” - ARIES does not have this
3. Based on “BOE”- ARIES does not have this
4. “% of Total Rev” Expenses – ARIES doesn’t allow stream math on total rev for expenses, only phase rev
5. “Deduct Before Sev” and “Deduct Before Ad Val” require extensive overlay math and are not handled by the exporter
6. 100% WI – work differently in ARIES for cutoff and reversion timing
7. While the Shrink and Calculation options in CC are very convenient, there is no direct analog in ARIES.  As a result, exporter will create sometimes very complicated overlay math upon export to ARIES.  This may result in the creation of custom phases (e.g., P08 to P15) and overlay math in an attempt to avoid interactions between the limited number of available ARIES keywords/streams.  This can become very complicated and can require extensive manual remodeling in ARIES. 
12. Production Taxes
    
1. Shrinkage Condition and Calculation method can result in complex overlay math in ARIES and may require manual remodeling
13. Operations
    
1. Curtailment is currently not supported but soon will be
14. Actual or Forecast
    
1. Some sections will cause LOAD lines in ARIES that reach the line limit
15. Risking - (Nothing Significant)
    
16. Escalations
    
1. No export of escalations is currently supported, must be manually rebuilt
17. DD&A
    
1. Must be created and maintained in both programs separately