{ "reviewed_on": "2026-10-07", "window": "7 October 2024–7 October 2026", "scope_note": "These are reviewed research notes, including updates to existing projects, adjacent operating technologies and historical context. They are not a count of unique deployments or additions to the AI register. Older operating periods and undated sources are labeled individually. The public record does not establish complete market coverage.", "observations": [ { "id": "R1-US-03", "company": "EQT", "title": "2025 drilling/completion execution and per-foot cost performance", "category": "drilling/completions / operations efficiency", "kind": "context", "ai_role": "Unstated; do not attribute to AI or label as a specific non-AI technology.", "asset": "EQT upstream, primarily Marcellus; annual release does not provide basin-specific figures.", "stage": "Observed FY2025 operating result; records repeated in Q4 2025.", "operating_period": "FY2025 and Q4 2025", "claim": "EQT reports fastest quarterly completions pace and most lateral footage drilled in 24 and 48 hours in Q4 2025; 2025 average well cost per foot was 13% lower YoY and 6% below internal expectations.", "economics": "Average well-cost-per-foot KPI improved 13% YoY; not a dollar figure and not technology-attributed.", "baseline": "Internal expectation and year-over-year comparison are disclosed, but the release does not identify the technology or program that produced the difference, give absolute cost/foot, or adjust for well design, lateral length, basin/activity mix, or other operating changes.", "limits": "High-level management disclosure; no activity-normalized comparator, well design/geology mix, lateral length control, or attribution among crews, planning, compression, sand/water/power logistics and other factors.", "relationship": "Keep only as a benchmark/context row. It is not a named technology intervention, so a per-foot cost result cannot establish technology value.", "decision_question": "What is the activity- and design-normalized baseline behind the 13% YoY lower $/ft and 6% below plan, and which interventions caused it?", "company_key": "EQT", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "EQT Reports Fourth Quarter and Full Year 2025 Results and Provides 2026 Guidance", "publisher": "EQT", "date": "2026-02-17", "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/EQT-Reports-Fourth-Quarter-and-Full-Year-2025-Results-and-Provides-2026-Guidance/default.aspx", "locator": "‘Record Operational Efficiencies’ result near top of release", "access": "Issuer results release opened; result section reviewed", "supports": "2025 completion pace/24- and 48-hour drilling footage records and 13% YoY / 6% internal well cost per foot comparison" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-02-17", "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/EQT-Reports-Fourth-Quarter-and-Full-Year-2025-Results-and-Provides-2026-Guidance/default.aspx", "locator": "2026-02-17 release, 'Record Operational Efficiencies', lines 132-145", "access": "Issuer results release opened; result section reviewed", "supports": "Numbers and period are confirmed. This is contextual operating evidence, not a separately attributable technology initiative. The source alone cannot establish that EQT's combo-development, innovation program, or any technology caused the result." } ], "references": [ { "id": "AI-095", "relationship": "company_context" }, { "id": "AI-261", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "R1-US-03", "core_company": true, "ai_ids": [ "AI-095", "AI-261" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "FY2025 and Q4 2025" }, { "id": "R1-US-04", "company": "EQT", "title": "Electric frac fleets using EQT-produced natural gas", "category": "completions / power and fuel substitution", "kind": "new_initiative", "ai_role": "Non-AI physical power equipment as disclosed; no AI role stated. This classification describes the disclosed intervention, not every control system in the fleet.", "asset": "EQT legacy operations; basin-level deployment split not stated.", "stage": "Fleet electrification began in 2020; 2025 questionnaire reports on 2024 use/results. Treat as established 2024 operating evidence, not a newly introduced technology within 2025-2026.", "operating_period": "2024", "claim": "EQT reports 2.5 electric and 0.5 diesel frac fleets during 2024 and >24 million gallons of diesel eliminated; annual savings estimated at USD 61.15m. The same CDP table separately lists USD 7.262m investment required and <1 year payback. Keep these as issuer-reported fields; do not calculate ROI or assert that investment field is complete lifetime/fleet CAPEX.", "economics": "The $7.262m investment figure is the CDP response's 'investment required' field, not an independently reconciled full capital and lifecycle-cost bridge. EQT says implementation cost is expected to decrease as gas transport infrastructure develops.", "baseline": "Diesel fuel displacement is compared with diesel-powered frac operations. Emissions up to 70,000 tCO2e are expected/estimated versus historical diesel operation, not verified measured emissions savings. Vehicle delivery emissions were also not estimated.", "limits": "The savings/investment fields are issuer estimates, not independently controlled returns; the source does not reconcile the full cost boundary. The separate up-to-70,000-tonne CO2e avoidance is an energy-input comparison estimate, not a measured emissions outcome. Program started in 2020; source discloses 2024 results, not a 2025/2026 launch.", "relationship": "Direct power/fuel substitution with potential unit economics. The $61.15m and $7.262m questionnaire values require perimeter reconciliation; do not claim full lifecycle ROI.", "decision_question": "Do the disclosed $61.15m annual savings and $7.262m “investment required” share the same fleet, time horizon, fuel-price assumptions and complete costs (gas, power, connection, rental, maintenance)?", "company_key": "EQT", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "EQT Corporation 2025 CDP Questionnaire", "publisher": "EQT", "date": "2025 (publication date to confirm from PDF metadata)", "url": "https://esg.eqt.com/content/EQT%20Corporation%202025%20CDP%20Questionnaire.pdf", "locator": "Printed PDF p. 220, questionnaire section 7.55.2 (investment required, annual savings, payback); p. 47 energy input comparison (emissions estimate context)", "access": "Primary PDF text opened and printed page/section cross-checked in site/research/technology-scope/root-source-checks.json; screenshot attempt failed, so no visual PDF verification claimed.", "supports": "2024 fleet mix and diesel avoided; 2024 savings, investment field and payback category, with the source audit’s cost-boundary limits." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025 questionnaire, reporting year ended 2024-12-31; exact issue date not established", "url": "https://esg.eqt.com/content/EQT%20Corporation%202025%20CDP%20Questionnaire.pdf", "locator": "Printed p. 8 section 1.2 (USD); pp. 218-220 sections 7.55.1-7.55.2; row 2, lines 4873-4902", "access": "Issuer-hosted PDF opened and text searched; currency and p. 220 fields verified. Existing local source check notes screenshots failed; no visual inspection claimed.", "supports": "The previous record's numbers are source-confirmed, including USD currency and reporting period. Sharpen wording to prevent interpreting $7.262m as all-in program capex or deriving a return multiple from unlike disclosed fields." }, { "title": "Additional root primary-source check", "publisher": "EQT", "date": "Date not established", "url": "https://esg.eqt.com/content/EQT%20Corporation%202025%20CDP%20Questionnaire.pdf", "locator": "Printed pages 47 and 220; sections 3.6.1.26 and 7.55.2, row 2", "access": "Primary PDF text opened; screenshot attempt failed, so no visual PDF verification claimed.", "supports": "The 2025 response reports 2024 fleet use of 2.5 electric and 0.5 diesel fleets, about 24 million gallons of diesel avoided, and $61.15 million saved in 2024. The investment field is 7,262,000 and the reported payback category is less than one year." } ], "references": [ { "id": "AI-095", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "R1-US-04", "core_company": true, "ai_ids": [ "AI-095" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2024" }, { "id": "T10-R01-US-01", "company": "EQT Corporation", "title": "Compression investments support 2026 production-outlook increase", "category": "field compression / production optimization", "kind": "update", "ai_role": "No AI contribution disclosed. Physical compression investments are named; system pressure optimization is also cited in the operating result, without component-level detail.", "asset": "EQT Appalachian Basin producing and new wells.", "stage": "Operating compression investments; Q2 2026 reported, while the increase is to full-year guidance and therefore forward-looking.", "operating_period": "Q2 2026 results released 2026-07-21; full-year 2026 guidance updated at release.", "claim": "EQT reported 2026 production guidance raised by about 90 Bcfe, attributing it to better-than-expected benefits from compression investments that improved existing and new wells and shallowed decline rates. Full-year capital-spend guidance was reduced by $25 million, but the issuer did not provide compression-specific investment, cost savings, or a cost bridge.", "economics": "Keep the guidance uplift, $25 million guidance reduction, and compression mechanism separate. Neither figure is an isolated compression ROI or a realized cash saving.", "baseline": "Production increase is versus prior 2026 guidance; Q2 sales volume was 634 Bcfe versus 568 Bcfe in Q2 2025, a companywide YoY comparison that includes multiple drivers. The $25m is guidance reduction, not an observed technology saving.", "limits": "Issuer attribution and guidance. No compressor count, asset denominator, project capex, per-well uplift, uptime, matched baseline, or realized margin is disclosed. Do not count the $25m guidance reduction as compressor savings or add it to the full-year volume uplift.", "relationship": "Retain starter-record links as program context only; do not imply same technology or project without exact project basis.", "decision_question": "What compressor capex and operating cost, per-well production/decline response, and matched counterfactual support the ~90 Bcfe revised outlook, and how much of the $25m guidance reduction remains after separating unrelated efficiency/infrastructure effects?", "company_key": "EQT", "run": "Rounds 1–10", "disposition": "include_as_operator_update_or_context", "sources": [ { "title": "EQT Reports Second Quarter 2026 Results", "publisher": "EQT Corporation", "date": "2026-07-21", "url": "https://ir.eqt.com/investor-relations/news/news-release-details/2026/EQT-Reports-Second-Quarter-2026-Results/default.aspx", "locator": "Highlights and CEO comments, lines 126–145; Q2 results show sales volumes lines 158–164.", "access": "Issuer HTML opened", "supports": "Compression investments as stated cause of +~90 Bcfe full-year guidance; $25m full-year capex guidance reduction; >29,000-ft lateral and Q2 sales volume." } ], "references": [ { "id": "R1-US-03", "relationship": "Retain starter-record links as program context only; do not imply same technology or project without exact project basis." }, { "id": "R1-US-04", "relationship": "Retain starter-record links as program context only; do not imply same technology or project without exact project basis." } ], "review": { "verdict": "correct", "reason": "The July 21 2026 issuer release directly attributes the 2026 guidance revision to compression investment benefits. It also lists operational execution/system optimization and other factors elsewhere; this is a company guidance outcome, not an audited technology ROI.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R01-US-01", "verdict": "correct", "patch": { "claim": "EQT reported 2026 production guidance raised by about 90 Bcfe, attributing it to better-than-expected benefits from compression investments that improved existing and new wells and shallowed decline rates. Full-year capital-spend guidance was reduced by $25 million, but the issuer did not provide compression-specific investment, cost savings, or a cost bridge.", "economics": "Keep the guidance uplift, $25 million guidance reduction, and compression mechanism separate. Neither figure is an isolated compression ROI or a realized cash saving.", "existing_ids": "Retain starter-record links as program context only; do not imply same technology or project without exact project basis." }, "reason": "The July 21 2026 issuer release directly attributes the 2026 guidance revision to compression investment benefits. It also lists operational execution/system optimization and other factors elsewhere; this is a company guidance outcome, not an audited technology ROI.", "recommended_disposition": "include_as_operator_update_or_context", "sources_inspected": [ { "url": "https://ir.eqt.com/investor-relations/news/news-release-details/2026/EQT-Reports-Second-Quarter-2026-Results/default.aspx", "access": "Issuer HTML opened directly", "locator": "Release dated 2026-07-21, lines 133-141; capital-spend table at lines 391-407." } ] } ] }, "department": "Production & process operations", "group_id": "T10-R01-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Q2 2026 results released 2026-07-21; full-year 2026 guidance updated at release." }, { "id": "T20-R11-US-01", "company": "EQT Corporation", "title": "Olympus asset integration and deep Utica well-construction performance", "category": "Operating model / drilling performance", "kind": "context", "ai_role": "No AI or named proprietary technology is identified as the cause. The claim concerns organizational/operational integration and well execution; absence of a disclosed AI role does not prove none was used.", "asset": "Two deep Utica wells on assets acquired from Olympus Energy; EQT reports integration of the acquired upstream and midstream assets as a company-wide transition.", "stage": "Operating result reported after acquisition; all acquired assets reportedly operationally integrated 34 days after closing.", "operating_period": "Reported 21 October 2025 in EQT Q3 2025 results; specific well dates and the historic comparator period are not disclosed in the release.", "claim": "EQT said it achieved operational integration of all upstream and midstream assets acquired from Olympus Energy 34 days after closing, then drilled two deep Utica wells about 30% faster than Olympus' historic performance, saving $2 million per well.", "economics": "Issuer-reported savings of $2 million per well for two wells. The release does not disclose absolute days, absolute well costs, scope of included cost, or whether savings are actual cash cost reduction versus comparison estimate.", "baseline": "Olympus historical performance; the number, lateral lengths, geology, service intensity, well designs, cost boundary and date of comparator wells are not specified. No randomized or matched-well analysis disclosed.", "limits": "The result may reflect transferred operating practices, scale/integration, design, service market conditions or other factors. Do not attribute the improvement to a single technology or generalize beyond these two deep Utica wells. EQT's broader 2025 average well cost-per-foot disclosure is a separate, portfolio-level denominator.", "relationship": "No matching EQT/Olympus record found in the 51 prior observations or production-profile index during this pass. Keep separate from Diamondback Barnett record T10-R09-US-01 and cross-company cost context T10-R09-US-02; these use different assets, comparators and cost boundaries.", "decision_question": "Can EQT disclose well-level actual days and cost scope, plus matched Olympus/EQT comparator wells, to identify which transferable practices drove the reported savings and how many eligible deep Utica wells remain?", "company_key": "EQT", "run": "Rounds 11–20", "disposition": "background", "sources": [ { "title": "EQT Reports Third Quarter 2025 Results", "publisher": "EQT Corporation", "date": "2025-10-21", "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2025/EQT-Reports-Third-Quarter-2025-Results/default.aspx", "locator": "Release recent highlights, line 132; integration timing and two deep Utica wells. Per-unit disclosures and definitions at lines 264–270 are separate portfolio measures.", "access": "Directly opened primary issuer HTML; relevant line and release context inspected.", "supports": "34-day integration claim, two-well count, approximate 30% faster comparison, and $2m savings per well." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct EQT issuer release confirms operational integration of acquired Olympus assets 34 days after closing and two deep Utica wells approximately 30% faster than Olympus historic performance, with reported $2 million savings per well. The release does not provide absolute days, cost boundary or cash realization detail; original limits already state this. The evidence concerns integration and engineering execution, not a named digital/AI technology.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R11-US-01", "verdict": "confirmed", "patch": {}, "reason": "Direct EQT issuer release confirms operational integration of acquired Olympus assets 34 days after closing and two deep Utica wells approximately 30% faster than Olympus historic performance, with reported $2 million savings per well. The release does not provide absolute days, cost boundary or cash realization detail; original limits already state this. The evidence concerns integration and engineering execution, not a named digital/AI technology.", "sources_inspected": [ { "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2025/EQT-Reports-Third-Quarter-2025-Results/default.aspx", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 116–138; especially line 132 for 34 days, two wells, ~30%, $2m/well; lines 264–270 for consolidated cost definitions/context.", "date": "2025-10-21" } ], "recommended_disposition": "background" } ] }, "department": "Drilling & completions", "group_id": "T20-R11-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R15-US-02", "company": "EQT Corporation", "title": "Appalachian circular-water system reports >95% produced-water recycling in 2025", "category": "Produced-water management and infrastructure", "kind": "update", "ai_role": "No AI contribution disclosed. This is physical water handling/infrastructure and an operating practice; absence of AI mention is not evidence of no AI elsewhere in water operations.", "asset": "EQT upstream production and completions in the Appalachian Basin, supported by an approximately 245-mile integrated pipeline network; release does not allocate results by basin, pad or asset.", "stage": "Continuing operating program, with company-reported 2025 performance.", "operating_period": "Calendar 2025, disclosed July 20, 2026.", "claim": "EQT reports recycling more than 95% of produced water in 2025, attributing the ongoing result to its circular water-management strategy and approximately 245-mile integrated pipeline network.", "economics": "No produced-water volume, pipeline capital/operating cost, treatment cost per barrel, freshwater purchases avoided, disposal cost avoided or measured completion cost impact disclosed in the issuer release.", "baseline": "No 2024 comparison, formula, water-quality specification, basin/pad boundary, recycled-water barrel denominator or third-party baseline is provided in the release; the statement should remain as issuer-reported percentage without an inferred ratio definition.", "limits": "The source is a short issuer summary of its sustainability report; it does not show asset-level volumes or whether the percentage covers all produced water generated, water consumed in completions, or a specific operational subset. Do not claim the 245-mile network alone caused the rate or that the rate equals freshwater displacement. No process energy or disposal outcome is quantified.", "relationship": "No matching EQT produced-water recycling result was found in the indexed 283 production profiles or 75 prior observations. Keep separate from EQT electric-frac fleet fuel savings (prior EQT CDP observation) and broad drilling-cost-per-foot results; no causal cost bridge is disclosed here.", "decision_question": "What 2025 produced-water volume and quality was recycled, at what treatment/pipeline cost per barrel and basin, and how much freshwater, third-party disposal and completion cost did that replace on eligible EQT pads?", "company_key": "EQT", "run": "Rounds 11–20", "disposition": "include", "sources": [ { "title": "EQT Releases 2025 Sustainability Report, “Built for What’s Next”", "publisher": "EQT Corporation", "date": "2026-07-20", "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/-EQT-Releases-2025-Sustainability-Report-Built-for-Whats-Next-2026-8Z1uWdZ6uk/default.aspx", "locator": "Lines 127–143, especially 140–143 for produced-water recycling and network scope.", "access": "Directly opened primary issuer release; relevant 2025 sustainability highlights inspected.", "supports": ">95% produced-water recycling in 2025, ~245-mile network and issuer-stated relationship to circular water strategy." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct EQT issuer release confirms that more than 95% of produced water was recycled in 2025 and attributes this to its circular-water strategy and approximately 245-mile integrated pipeline network. No volume denominator, spend, freshwater/disposal counterfactual or completion-cost effect is given. This is physical water-handling infrastructure and process, not AI.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R15-US-02", "verdict": "confirmed", "patch": {}, "reason": "Direct EQT issuer release confirms that more than 95% of produced water was recycled in 2025 and attributes this to its circular-water strategy and approximately 245-mile integrated pipeline network. No volume denominator, spend, freshwater/disposal counterfactual or completion-cost effect is given. This is physical water-handling infrastructure and process, not AI.", "sources_inspected": [ { "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/-EQT-Releases-2025-Sustainability-Report-Built-for-Whats-Next-2026-8Z1uWdZ6uk/default.aspx", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 116–143; exact recycling claim at line 141.", "date": "2026-07-20" } ], "recommended_disposition": "include" } ] }, "department": "Water, emissions & energy", "group_id": "T20-R15-US-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Calendar 2025, disclosed July 20, 2026." }, { "id": "R1-US-06", "company": "EOG Resources", "title": "iSense continuous leak-detection coverage in the Delaware Basin", "category": "continuous sensing / methane monitoring", "kind": "new_initiative", "ai_role": "Not stated in this KPI disclosure; retain unclear and do not call it an AI result.", "asset": "EOG Delaware Basin central tank batteries.", "stage": "Reported as achieved at year-end 2025.", "operating_period": "As of 2025-12-31", "claim": "Coverage only. Source reports no alert precision/recall, leak repair rate, methane abatement, avoided loss, cost, or prior-year comparison.", "economics": "No cost or methane-reduction result disclosed alongside this coverage KPI.", "baseline": "Coverage metric, not an emissions reduction, leak-detection accuracy, response-time or avoided-loss result. No prior-year baseline included in headline.", "limits": "Issuer-reported coverage only. Coverage does not establish detection performance, repair completion, emission abatement or economic payback; denominator is restricted to Delaware Basin gross oil handled at central tank batteries.", "relationship": "Coverage of 99% of gross oil production at Delaware central tank batteries is a useful monitoring adoption denominator only, not well coverage, detection accuracy, or emissions reduction.", "decision_question": "What are alert precision/recall, repair closure, emissions avoided, loss prevention, and cost per covered gross-oil barrel?", "company_key": "EOG Resources", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Sustainability – 2025 Highlights", "publisher": "EOG Resources", "date": "2026 (2025 performance data)", "url": "https://www.eogresources.com/sustainability/", "locator": "2025 Highlights: iSense 99% coverage; footnote defines percentage of gross oil production at covered Delaware Basin central tank batteries as of year end", "access": "Issuer sustainability page opened; KPI and footnote reviewed", "supports": "2025 coverage and exact denominator" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026 page with year-end 2025 performance", "url": "https://www.eogresources.com/sustainability/", "locator": "2025 Highlights, iSense metric and footnote, lines 270-281", "access": "Issuer sustainability page opened; highlight and footnote reviewed", "supports": "Exact denominator and date are confirmed by the source footnote; there is no outcome beyond monitoring coverage." } ], "references": [ { "id": "AI-088", "relationship": "company_context" }, { "id": "AI-089", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "R1-US-06", "core_company": true, "ai_ids": [ "AI-088", "AI-089" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "As of 2025-12-31" }, { "id": "T20-R17-US-01", "company": "EOG Resources", "title": "EOG keeps technology decisions close to its asset teams", "category": "Operating model and technical staffing", "kind": "context", "ai_role": "No AI role is stated in the sources. EOG describes proprietary information technology and data-driven decision-making at a high level; the job posting does not identify a named software or AI workflow.", "asset": "EOG's U.S. multi-basin upstream organization; posted role located in Midland, Texas and supports drilling and exploration programs and multiple rigs.", "stage": "EOG fact sheet published March 2025; Senior Drilling Engineer position was posted 2025-10-29. The fact sheet describes company operating model; job posting describes the duties for a single open/posted role, not proof the role was filled or a measured organization-wide staffing structure.", "operating_period": "Operating-model statements published March 2025; position posted 2025-10-29.", "claim": "EOG's March 2025 fact sheet describes in-house technical expertise, proprietary information technology and self-sourced materials as supporting well performance and cost control, and describes a decentralized, non-bureaucratic structure that enables asset-level value creation and multidisciplinary collaboration. A later Senior Drilling Engineer posting lists well planning/design, AFE preparation, drilling and cost analysis, vendor performance evaluation, new-technology application, cross-functional work with geology/reservoir/completions/land/construction/regulatory teams, and daily supervisory support for multiple rigs.", "economics": "No cost, staffing headcount, software-development budget, decision-cycle time or productivity outcome is disclosed. This evidence helps identify workflow responsibility, not quantify the value of decentralization or proprietary IT.", "baseline": "No prior/alternative organizational structure or centralized-versus-decentralized performance comparator is supplied. The job posting is one role in one location, not a full org chart or staffing census.", "limits": "Corporate fact sheet language is high level. The job posting is a vacancy description and may not represent actual workload allocation, filled role, or all EOG basins. Proprietary IT is not identified by product, owner, maintenance model or AI content; do not infer AI leadership or superior readiness.", "relationship": "No matching EOG organizational/staffing record was found in the production profile index or the 75 prior observations. This is operating-model context, distinct from EOG drilling-cost result T10-R02-US-02.", "decision_question": "Which well-planning, vendor, cost and daily rig decisions are made by asset-based engineers versus centralized technical/software teams, and what proprietary applications are owned and maintained in each layer?", "company_key": "EOG Resources", "run": "Rounds 11–20", "disposition": "background", "sources": [ { "title": "EOG Resources 2024 Operations & Financial Results Fact Sheet — Sustainable Value Creation", "publisher": "EOG Resources", "date": "2025-03", "url": "https://www.eogresources.com/documents/EOG_Fact_Sheet_2025.pdf", "locator": "PDF p.1, lines 56–85: in-house expertise/proprietary IT, decentralized asset-level culture, multidisciplinary teams and data-driven decisions.", "access": "Directly opened primary issuer PDF; relevant page inspected.", "supports": "Issuer-stated operating culture and technology ownership principles; not measured outcomes." }, { "title": "Senior Drilling Engineer — Midland, TX (Job ID 10871)", "publisher": "EOG Resources Careers", "date": "2025-10-29", "url": "https://careers.eogresources.com/jobdetails.asp?apply=yes&jo_num=10871", "locator": "Lines 19–44, especially 36–37 for responsibilities and cross-functional interfaces.", "access": "Directly opened primary EOG job listing; exact posted date and duties inspected.", "supports": "One planned drilling-engineering role's stated duties and reporting/workflow interfaces; not actual hire or measured staffing." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct reopens of the fact sheet and job listing confirm in-house expertise/proprietary IT, decentralized multidisciplinary culture and the specific drilling-engineer duties (well design, AFE, cost/vendor evaluation, technology application, cross-functional interfaces and rig supervision). These are organizational/context signals without a quantified technology outcome.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R17-US-01", "verdict": "confirmed", "patch": { "stage": "EOG fact sheet published March 2025; Senior Drilling Engineer position was posted 2025-10-29. The fact sheet describes company operating model; job posting describes the duties for a single open/posted role, not proof the role was filled or a measured organization-wide staffing structure." }, "reason": "Direct reopens of the fact sheet and job listing confirm in-house expertise/proprietary IT, decentralized multidisciplinary culture and the specific drilling-engineer duties (well design, AFE, cost/vendor evaluation, technology application, cross-functional interfaces and rig supervision). These are organizational/context signals without a quantified technology outcome.", "sources_inspected": [ { "url": "https://www.eogresources.com/documents/EOG_Fact_Sheet_2025.pdf", "access": "Issuer PDF opened directly in cross-audit", "locator": "PDF page 1, lines 56–85; fact sheet date at line 86.", "date": "2025-03" }, { "url": "https://careers.eogresources.com/jobdetails.asp?apply=yes&jo_num=10871", "access": "Issuer career listing opened directly in cross-audit", "locator": "Lines 15–44; posting date and duties at lines 19, 36–44.", "date": "2025-10-29" } ], "recommended_disposition": "background" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R17-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Operating-model statements published March 2025; position posted 2025-10-29." }, { "id": "T10-R02-US-02", "company": "EOG Resources", "title": "FY2025 average well-cost decline updates the existing lateral and drilling-efficiency program", "category": "drilling and completion efficiency / lateral design", "kind": "update", "ai_role": "Issuer attributes the 2026 target to increased lateral lengths and other sustainable efficiencies, without identifying AI, a specific motor, or a single causal technology. Method mix is not disclosed.", "asset": "EOG multi-basin drilling and completion portfolio; FY2025 companywide average well costs.", "stage": "FY2025 reported outcome; 2026 cost-reduction language is a forward-looking target, not a realized result.", "operating_period": "FY2025 result published 2026-02-24; 2026 target stated in the same release.", "claim": "EOG's FY2025 average well costs decreased 7% across its multi-basin portfolio; 2026 low-single-digit reduction is guidance. The disclosure does not isolate savings from in-house motors or lateral length.", "economics": "A portfolio-average well-cost change is relevant to drilling capital productivity but is not a technology-specific cash saving, per-well dollar figure or return on the motor program. The 2026 target is a plan and should not be described as achieved.", "baseline": "FY2025 average well costs versus FY2024 average well costs, across a multi-basin portfolio; release does not provide an absolute $/well, basin/well denominator, lateral-length mix adjustment or comparable scope. The 2026 target is low-single-digit versus the FY2025 average-cost base as implied by the release.", "limits": "The reported change can reflect basin mix, lateral length, service pricing, well design and other efficiency actions. No attribution to the already-recorded in-house drilling-motor program or to AI is supported. Flat-oil production and capex are plan assumptions, not verified outcomes.", "relationship": "Update the starter EOG drilling-efficiency/lateral-length context; do not create a motor-specific causal result.", "decision_question": "Can EOG disclose basin-normalized $/well and $/lateral-foot changes, eligible well counts and the portion attributable to lateral length, motor performance, design, service pricing and other levers?", "company_key": "EOG Resources", "run": "Rounds 1–10", "disposition": "enrich_eog_context_if_exact_record_basis_is_confirmed_otherwise_background", "sources": [ { "title": "EOG Resources Reports Fourth Quarter and Full Year 2025 Results", "publisher": "EOG Resources (issuer-hosted investor PDF)", "date": "2026-02-24", "url": "https://filecache.investorroom.com/mr5ir_eogresources2/444/4Q_2025_Earnings_Press_Release.pdf", "locator": "FY2025 results / 2026 capital plan paragraphs, PDF p. 1 (issuer-hosted release).", "access": "Issuer-hosted PDF opened directly", "supports": "7% FY2025 average well-cost decline; 2026 $6.5bn capital plan, flat-oil planning case and low-single-digit average-well-cost target with longer laterals/other efficiencies." } ], "references": [ { "id": "TECH-03", "relationship": "Update the starter EOG drilling-efficiency/lateral-length context; do not create a motor-specific causal result." } ], "review": { "verdict": "confirmed", "reason": "Issuer earnings release supports the reported percentage and outlook; it supplies neither a common absolute $/well nor a technology-specific cost attribution. Treat as operator-level KPI context.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R02-US-02", "verdict": "confirmed", "patch": { "claim": "EOG's FY2025 average well costs decreased 7% across its multi-basin portfolio; 2026 low-single-digit reduction is guidance. The disclosure does not isolate savings from in-house motors or lateral length.", "relationship": "Update the starter EOG drilling-efficiency/lateral-length context; do not create a motor-specific causal result." }, "reason": "Issuer earnings release supports the reported percentage and outlook; it supplies neither a common absolute $/well nor a technology-specific cost attribution. Treat as operator-level KPI context.", "recommended_disposition": "enrich_eog_context_if_exact_record_basis_is_confirmed_otherwise_background", "sources_inspected": [ { "url": "https://filecache.investorroom.com/mr5ir_eogresources2/444/4Q_2025_Earnings_Press_Release.pdf", "access": "Issuer-hosted PDF opened directly", "locator": "FY2025 highlights and 2026 outlook, PDF p. 1-2." } ] } ] }, "department": "Drilling & completions", "group_id": "TECH-03", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "FY2025 result published 2026-02-24; 2026 target stated in the same release." }, { "id": "TECH-03", "company": "EOG Resources", "title": "Extended laterals and in-house drilling motor program", "category": "drilling engineering / cycle-time and well cost", "kind": "new_initiative", "ai_role": "non-AI drilling technology; no AI contribution disclosed", "asset": "Not disclosed", "stage": "Portfolio-wide, multi-basin average; number/share of wells using in-house motors, lateral-length distribution, and basin-level contributions are not stated.", "operating_period": "2025-02-27", "claim": "CEO says better productivity plus sustainable efficiency improvements from extended laterals and EOG's in-house drilling motor program helped lower average well costs 6% in 2024.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "The contribution of drilling motors cannot be isolated from extended laterals or other operating changes; no matched-well counterfactual disclosed.", "relationship": "Useful engineering/process comparator, but the reported 6% average well-cost reduction is bundled across longer laterals, in-house motors and productivity; motor-only causality is unsupported.", "decision_question": "What well-cost reduction is attributable to motors vs longer laterals/productivity, by basin and design, with motor adoption share and incremental motor cost?", "company_key": "EOG Resources", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "EOG Resources Reports Fourth Quarter and Full-Year 2024 Results; Announces 2025 Capital Plan", "publisher": "EOG Resources", "date": "2025-02-27", "url": "https://investors.eogresources.com/2025-02-27-EOG-Resources-Reports-Fourth-Quarter-and-Full-Year-2024-Results-Announces-2025-Capital-Plan?asPDF=", "locator": "Full-year highlights and CEO commentary", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-02-27", "url": "https://investors.eogresources.com/2025-02-27-EOG-Resources-Reports-Fourth-Quarter-and-Full-Year-2024-Results-Announces-2025-Capital-Plan?asPDF=", "locator": "2025-02-27 release, PDF p. 1 lines 49-54", "access": "Issuer-hosted earnings PDF opened; CEO commentary reviewed", "supports": "The 6% figure and bundled attribution are confirmed in the issuer release. This is useful as a bundled operating technology example only; causal contribution of the motor remains unknown." } ], "references": [ { "id": "AI-088", "relationship": "company_context" }, { "id": "AI-089", "relationship": "company_context" }, { "id": "TR-08", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "TECH-03", "core_company": true, "ai_ids": [ "AI-088", "AI-089" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025-02-27" }, { "id": "R1-US-02", "company": "Devon Energy", "title": "D&C design, simulfrac and equipment efficiency bundle", "category": "drilling/completions / equipment and process efficiency", "kind": "new_initiative", "ai_role": "AI models/agents are listed separately as flagging unproductive time and best practices. Source does not attribute D&C speed, equipment diesel displacement, simulfrac expansion, or aggregate capital reduction solely to AI.", "asset": "Multi-basin U.S. operations; Delaware mentioned for contract savings, but no per-basin D&C outcome breakdown.", "stage": "Operating program; Q4 2025 results report progress.", "operating_period": "Q4/FY2025 metrics; earlier Q4 2024 call's savings are early wins at that time", "claim": "Q4 2025 slide 12 reports design improvements/new technology drove 9% faster drilling and 21% faster completions YoY; simulfrac application increased >30% YoY across portfolio; high-graded D&C equipment displaced ~40% of diesel and yielded >$25m savings; efficiency gains drove >$250m capital reduction for 2025, >5% improvement from original outlook. These are separate program metrics; >$250m is not an isolated technology result. The $600k/well early D&C savings stated in Feb 2025 were tied jointly to drilling/completion pace, supply-chain wins, self-sourced sand and simul-frac; they concern Williston progress and are not an AI-only result.", "economics": ">$250m reported 2025 capital reduction at initiative/program level; >$25m from high-graded equipment's diesel displacement; separate early 2024 call claim $600k/well bundled D&C savings.", "baseline": "9%/21% are year-over-year rates without absolute duration, matched-well design, basin mix or counterfactual. >$250m is broad efficiency/program capital reduction; >$25m is equipment diesel displacement. Do not add these metrics or stack the earlier $600k/well figure into the 2025 total.", "limits": "Issuer earnings deck and transcript. Several initiatives and commercial/supply-chain items are bundled; no counterfactual or independent cost audit. Separate the AI-monitoring line from physical D&C changes and do not double-count component metrics against the optimization headline.", "relationship": "Material competing workflow change, but preserve as an issuer-reported bundle; no result can be assigned to one component or AI.", "decision_question": "How much of >$250m capital reduction, 9% faster drilling, 21% faster completions and >$25m diesel savings is incremental to each named initiative, net of capex and not double-counted?", "company_key": "Devon Energy", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Q4 2025 Earnings Presentation", "publisher": "Devon Energy", "date": "2026-02-17", "url": "https://investors.devonenergy.com/investors/events-presentations/event-details/2026/Q4-2025-Earnings-Presentation/default.aspx", "locator": "Slide 12, Business Optimization Initiatives and Milestones", "access": "Issuer IR presentation page verified; indexed slide text reviewed", "supports": "9% faster drilling, 21% faster completions, simulfrac +30%, >$250m efficiency capital reduction, equipment ~40% diesel displacement and >$25m saving; separate AI line" }, { "title": "Devon Q4 2024 Earnings Call Q&A Webcast Commentary Transcript", "publisher": "Devon Energy / Q4 CDN", "date": "2025-02-19", "url": "https://s2.q4cdn.com/462548525/files/doc_financials/quarterly/2024/q4/Q4-2024-DVN-Q-A-Webcast-Commentary-Transcript.pdf", "locator": "PDF p. 4, lines 164-167", "access": "Issuer-hosted transcript PDF opened", "supports": "Early $600,000 per well figure and the expressly bundled causes: D&C pace, supply chain, self-sourced sand and simulfrac" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-02-17", "url": "https://s2.q4cdn.com/462548525/files/doc_financials/quarterly/2025/q4/Q4-2025-DVN-Earnings-Presentation.pdf", "locator": "Q4 2025 presentation dated 2026-02-17, printed slide 12 / PDF p. 11; initiatives and milestones", "access": "Issuer-linked PDF opened; slide text reviewed", "supports": "The original record had the essential bundle caveat, but the source's slide layout and transcript clarify that several outcomes sit across capital efficiency, production optimization, and commercial actions. Retain as a multi-initiative operating program, not a single technology case; preserve the separate AI monitoring role." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-02-19", "url": "https://s2.q4cdn.com/462548525/files/doc_financials/quarterly/2024/q4/Q4-2024-DVN-Q-A-Webcast-Commentary-Transcript.pdf", "locator": "Q4 2024 earnings call, 2025-02-19, PDF p. 4 lines 162-167; $600k/well early savings and named bundled causes", "access": "Issuer-hosted PDF opened; relevant transcript lines reviewed", "supports": "The original record had the essential bundle caveat, but the source's slide layout and transcript clarify that several outcomes sit across capital efficiency, production optimization, and commercial actions. Retain as a multi-initiative operating program, not a single technology case; preserve the separate AI monitoring role." } ], "references": [ { "id": "AI-007", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "R1-US-02", "core_company": true, "ai_ids": [ "AI-007" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Q4/FY2025 metrics; earlier Q4 2024 call's savings are early wins at that time" }, { "id": "T10-R06-US-01", "company": "Devon Energy", "title": "Methane detection data integrated into field decision workflows, with automated repair work orders and SCADA-based AI alerts", "category": "internal data product / emissions operations workflow / decision support", "kind": "update", "ai_role": "Hybrid. Devon explicitly says it is deploying an AI program that analyzes SCADA and decision-support-center data and generates alerts for operational issues. The surrounding workflow includes continuous/emissions sensors, operator decision centers, dashboards, an automated work-order process and standard procedures. The source does not describe model type, production-control authority, or autonomous actuation; AI alerts are human action prompts as described.", "asset": "Devon operated U.S. production assets; 2024 continuous monitoring covered 46% of production, while combined OGI, aerial and continuous monitoring gave claimed coverage across 100% of production operations. New facilities in 2025 were to have monitoring devices per the issuer page.", "stage": "Operating detection and dashboard/work-order workflow in the 2024 reporting year; AI program described as being deployed, not as a fully evaluated portfolio-wide system. Carbon accounting platform was in use for emissions inventory reporting.", "operating_period": "2024 deployment and coverage reported in Devon's 2025 Sustainability Report; issuer page adds 2025 new-facility monitoring practice but is undated/current.", "claim": "The 2025 report (stating default reporting period is year ended 2024) says Devon integrates methane detection data with operating systems/decision support centers, uses an AI program analyzing SCADA and decision-support-center data to alert action on operational issues, and automated leak-repair work orders. Continuous monitoring covered 46% at year-end 2024 and combined detection methods covered 100% of production; these are coverage, not emissions-reduction results.", "economics": "The software and workflow are enabling infrastructure for faster detection, mitigation and emissions reporting. No alert precision, time-to-work-order, time-to-repair, leak recurrence, production uptime, methane mass avoided, labor-hours saved or implementation cost is disclosed; no software ROI can be calculated.", "baseline": "Monitoring coverage and platform granularity are disclosed, not before/after performance. The 46% continuous-monitoring figure and 100% combined-tech coverage are distinct; neither is a measured emissions reduction. Equipment-level versus basin-level is a reporting-resolution comparison, not proof of more accurate direct emissions measurement or cash savings.", "limits": "Do not merge emissions coverage or outcomes with EOG or Exxon. Report does not quantify repair time avoided, leaks prevented, methane volume, AI alert precision, or incremental benefit versus the non-AI workflow.", "relationship": "Exact same 2025 Devon sustainability-report URL as production records AI-249 and AI-250. Treat the SCADA/decision-support AI alert workflow as an update/enrichment of AI-249, not a new AI initiative count. AI-250 is the distinct hourly flare computer-vision workflow in the same report. Dashboard/work-order and equipment-level emissions-accounting components may be cross-functional workflow layers; their independent deployment identity is not established.", "decision_question": "What are the end-to-end metrics from sensor/model alert to verified repair—precision/recall, work-order creation and closeout time, leak recurrence and measured methane abatement—and what portion is attributable to software versus field staffing/process redesign?", "company_key": "Devon Energy", "run": "Rounds 1–10", "disposition": "update_AI_249_workflow; retain_AI_250_as_distinct_same-report_workflow; no_new_AI_count", "sources": [ { "title": "Devon Energy 2025 Sustainability Report", "publisher": "Devon Energy", "date": "2025 (exact issue date not confirmed in the PDF metadata checked)", "url": "https://dvnweb-hfhahvbraba9feev.a01.azurefd.net/assets/documents/Sustainability/DVN_2025_SustainabilityReport.pdf", "locator": "Printed pp. 9 and 15-16; PDF lines 678-700 (carbon accounting) and 1215-1258 (coverage, integration, AI alerts, dashboard, work orders).", "access": "Issuer PDF opened directly", "supports": "Internal platform and equipment-level emissions calculation; 2024 portfolio coverage; data integration to decision centers; AI status and functionality; automated work orders/SOP." }, { "title": "Reducing methane emissions", "publisher": "Devon Energy", "date": "Undated current issuer page (copyright 2026)", "url": "https://www.devonenergy.com/reducing-methane-emissions", "locator": "Lines 107-121, including 2024 coverage, 2025 new-facility practice, AI program, dashboard and automated work order description.", "access": "Issuer HTML opened directly", "supports": "Corroborates the workflow and AI function; exact publication date not established, so treated as corroboration rather than the dated annual-period source." } ], "references": [ { "id": "AI-249", "relationship": "same_workflow", "basis": "Same SCADA/decision-support AI alerting workflow and issuer report; update only." }, { "id": "AI-250", "relationship": "same_source_distinct_workflow", "basis": "Flare computer vision is a distinct workflow in the same sustainability report." } ], "review": { "verdict": "correct", "reason": "Direct PDF passage explicitly describes AI alerts from SCADA and decision support data plus monitoring dashboard and automated work-order process. Exact source identity with AI-249/250 changes duplicate treatment; same-source root check confirms it. No AI method attribution should be inferred for the methane-accounting component absent more detail.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R06-US-01", "verdict": "correct", "patch": { "relationship": "Exact same 2025 Devon sustainability-report URL as production records AI-249 and AI-250. Treat the SCADA/decision-support AI alert workflow as an update/enrichment of AI-249, not a new AI initiative count. AI-250 is the distinct hourly flare computer-vision workflow in the same report. Dashboard/work-order and equipment-level emissions-accounting components may be cross-functional workflow layers; their independent deployment identity is not established.", "claim": "The 2025 report (stating default reporting period is year ended 2024) says Devon integrates methane detection data with operating systems/decision support centers, uses an AI program analyzing SCADA and decision-support-center data to alert action on operational issues, and automated leak-repair work orders. Continuous monitoring covered 46% at year-end 2024 and combined detection methods covered 100% of production; these are coverage, not emissions-reduction results.", "dates": "2025 report filename/cover is not exact issue date; label reported operating period as 2024 and publication as undetermined unless verified separately.", "limits": "Do not merge emissions coverage or outcomes with EOG or Exxon. Report does not quantify repair time avoided, leaks prevented, methane volume, AI alert precision, or incremental benefit versus the non-AI workflow." }, "reason": "Direct PDF passage explicitly describes AI alerts from SCADA and decision support data plus monitoring dashboard and automated work-order process. Exact source identity with AI-249/250 changes duplicate treatment; same-source root check confirms it. No AI method attribution should be inferred for the methane-accounting component absent more detail.", "recommended_disposition": "update_AI_249_workflow; retain_AI_250_as_distinct_same-report_workflow; no_new_AI_count", "sources_inspected": [ { "url": "https://dvnweb-hfhahvbraba9feev.a01.azurefd.net/assets/documents/Sustainability/DVN_2025_SustainabilityReport.pdf", "access": "Issuer PDF opened directly", "locator": "Printed pp. 9, 15-16; PDF lines 1247-1261 and 2053-2061; report says default period is 2024 at printed p. 2." }, { "url": "https://www.devonenergy.com/reducing-methane-emissions", "access": "Issuer page opened directly in R06 original pass; undated/current page", "locator": "Lines 107-121 per R06 source note." } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R06-US-01", "core_company": true, "ai_ids": [ "AI-249", "AI-250" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R07-US-01", "company": "Devon Energy", "title": "2025 optimization plan identifies vendor management and analytics as value levers, without naming technology suppliers or spend", "category": "buyer signal / procurement / operating optimization", "kind": "context", "ai_role": "The production-optimization bucket cites advanced analytics; the release also says analytics and process automation had been implemented. It does not disclose AI use, a vendor/platform, or how any technology contributes to the value target.", "asset": "Devon's multi-basin U.S. operated upstream business; no basin- or asset-level allocation of plan values was disclosed.", "stage": "Plan announced 2025-04-22; by announcement the company said analytics/process automation advancements had been implemented. The $300m 2025 cash-flow uplift and $1bn annual pre-tax improvement goals were forecasts at publication, not verified outcomes in this source.", "operating_period": "Plan targeting approximately 30% of estimated improvements by year-end 2025 and remaining value by year-end 2026; full annual improvement target stated at announcement.", "claim": "Devon announced a target of $1.0bn annual pre-tax free-cash-flow improvement, including $250m production-optimization target using advanced analytics and $300m capital-efficiency target including vendor management; these are plan estimates/targets with staged timing, not audited realized tech returns.", "economics": "The $300m and $250m figures are broad target buckets, not realized savings, tech spend, supplier revenue or ROI. Total $1bn target includes commercial and corporate actions. The separate approximately $300m cash-flow uplift anticipated by year-end 2025 combined marketing agreements and implemented technology, with no technology-only allocation in this announcement.", "baseline": "No audited baseline, asset/well population, supplier-level spending or savings mechanism is supplied in this plan release. Approximately 30%/remainder are expected milestone shares of forecast improvement, not measured technology deployment percentages.", "limits": "Issuer plan announcement and forward-looking targets. No named software/service vendor, procurement process, project capex, contract duration, deployment count, individual KPI, or confirmed realization is supplied. D&C efficiency material overlaps R1-US-02; analytics/work-order workflow overlaps T10-R06-US-01. Do not add the $300m/$250m buckets to observed D&C or AI results.", "relationship": "Buyer/management-context only. Do not represent the $1.0bn target as a named technology deployment or cross-link to Devon AI-249 without a documented shared program basis. The plan's analytics/vendor-management buckets are not individual project ROI.", "decision_question": "Which vendor contracts, internal build costs and asset-level pilots sit behind the $300m capital-efficiency and $250m production-optimization buckets, and what portion of their target value was actually realized by the 2025 milestone?", "company_key": "Devon Energy", "run": "Rounds 1–10", "disposition": "background_buyer_context", "sources": [ { "title": "Devon Energy Unveils Value Enhancing Business Optimization Plan", "publisher": "Devon Energy", "date": "2025-04-22", "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Unveils-Value-Enhancing-Business-Optimization-Plan/default.aspx", "locator": "Plan pathway and category buckets, lines 42-60.", "access": "Issuer HTML opened directly", "supports": "Target buckets, descriptions of vendor management/advanced analytics, broad $1bn plan and distinction between targets and actuals." }, { "title": "Devon Energy and Coterra Energy to Combine, Creating a Premier Shale Operator", "publisher": "Devon Energy", "date": "2026-02-01", "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2026/Devon-Energy-and-Coterra-Energy-to-Combine-Creating-a-Premier-Shale-Operator/default.aspx", "locator": "Transaction benefits, lines 50-66, especially AI platform strategy and $1bn synergy target.", "access": "Issuer HTML opened directly", "supports": "AI is framed as an expected strategic platform; no vendor, deployment, budget or separate realized AI return is identified." } ], "references": [ { "id": "R1-US-02", "relationship": "Buyer/management-context only. Do not represent the $1.0bn target as a named technology deployment or cross-link to Devon AI-249 without a documented shared program basis. The plan's analytics/vendor-management buckets are not individual project ROI." }, { "id": "T10-R06-US-01", "relationship": "Buyer/management-context only. Do not represent the $1.0bn target as a named technology deployment or cross-link to Devon AI-249 without a documented shared program basis. The plan's analytics/vendor-management buckets are not individual project ROI." } ], "review": { "verdict": "confirmed", "reason": "The issuer release explicitly breaks categories and timing. Later merger AI strategy/synergy language is separate and should not be blended into the 2025 optimization-plan target.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R07-US-01", "verdict": "confirmed", "patch": { "relationship": "Buyer/management-context only. Do not represent the $1.0bn target as a named technology deployment or cross-link to Devon AI-249 without a documented shared program basis. The plan's analytics/vendor-management buckets are not individual project ROI.", "claim": "Devon announced a target of $1.0bn annual pre-tax free-cash-flow improvement, including $250m production-optimization target using advanced analytics and $300m capital-efficiency target including vendor management; these are plan estimates/targets with staged timing, not audited realized tech returns." }, "reason": "The issuer release explicitly breaks categories and timing. Later merger AI strategy/synergy language is separate and should not be blended into the 2025 optimization-plan target.", "recommended_disposition": "background_buyer_context", "sources_inspected": [ { "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Unveils-Value-Enhancing-Business-Optimization-Plan/default.aspx", "access": "Issuer HTML opened directly", "locator": "Lines 44-60." }, { "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2026/Devon-Energy-and-Coterra-Energy-to-Combine-Creating-a-Premier-Shale-Operator/default.aspx", "access": "Issuer HTML opened directly in original R07 pass", "locator": "Lines 50-66; separate merger synergy/strategy context." } ] } ] }, "department": "Production & process operations", "group_id": "T10-R07-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R16-US-01", "company": "Devon Energy / Whitson", "title": "Devon calculates daily well pressure through Snowflake and Whitson", "category": "Internal data platform and production-engineering workflow", "kind": "context", "ai_role": "No AI is attributed to the bottomhole-pressure calculation. The customer story identifies Whitson's physics-based engine/digital-twin capabilities; Snowflake is the governed data-sharing layer. Devon says unified data is intended to support separate future AI/ML use cases, including geoscience work, which are not this workflow.", "asset": "Devon's enterprise Data Hub, using time-series and wellbore-configuration data across producing wells; bottomhole pressure is surfaced in whitson+ and Devon SCADA for production and reservoir engineers.", "stage": "Described as a live daily calculation/use case at the time of the undated customer story; deployment date and present status are not stated.", "operating_period": "Undated vendor case; operating start and research-window eligibility are not established.", "claim": "Snowflake's case says Devon consolidates data from 30+ sources, gives employees access to 95% of application data, and supports more than 1,000 users and about 9 million queries per month. With Snowflake Secure Data Sharing, Devon sends time-series and wellbore-configuration data to Whitson; Whitson returns physics-based bottomhole-pressure calculations daily for 5,000+ wells. Calculations are used by production engineers to spot underperforming wells and by reservoir engineers to understand reservoir condition, site new wells and plan development.", "economics": "The story states manual calculation across >5,000 wells did not scale and that installing a $50,000 physical pressure sensor in each existing well was uneconomical/unrealistic. It gives no actual sensor count avoided, software/data-platform cost, manual labor cost, calculation error rate, production gain, or realized savings. Do not multiply the quoted sensor price by the well count as realized savings.", "baseline": "Manual derivation was the prior workflow; the page provides no time-per-calculation, calculation accuracy, intervention, well-production or matched baseline before/after data.", "limits": "Vendor-authored, undated customer story; current status/date of deployment is unknown. The 5,000+ figure is wells for which daily physics-based calculations are produced, not a documented production-uplift or model-accuracy denominator. No sensor count was avoided: $50,000 per sensor is an illustrative hardware alternative, not realized savings. Snowflake's site categorizes multiple products including AI, but this specific workflow is described as Whitson physics-based calculation via secure data sharing; no AI attribution is established.", "relationship": "No match for this specific Devon / Whitson bottomhole-pressure workflow was found in 283 production profiles or 75 prior observations. Distinct from AI-006 (Devon artificial-lift optimization) and AI-007 (drilling/completions agents); the software-platform data layer is an enabling context, not a duplicate AI deployment.", "decision_question": "When was this workflow deployed and is it still active; what are the per-well calculation cost/accuracy, engineer hours, intervention changes and production impact relative to manual or sensor measurements, and what were Snowflake/Whitson integration and recurring costs?", "company_key": "Devon Energy", "run": "Rounds 11–20", "disposition": "background", "sources": [ { "title": "Devon Energy and Whitson Collaborate to Save Time and Increase Production by Automatically Calculating Bottomhole Pressure", "publisher": "Snowflake customer story, with Devon Energy and Whitson quotations", "date": "Undated; accessed 2026-10-07", "url": "https://www.snowflake.com/en/customers/all-customers/case-study/devon-energy/", "locator": "Lines 15–20 (headline metrics), 57–65 (platform reach), 66–80 (physics-based pressure calculation and workflow), 82–85 (future AI/ML data work).", "access": "Directly opened full vendor-hosted case page; publication date not present in visible text.", "supports": "Named Devon / Whitson workflow, platform scale, two-way data-sharing mechanism, >5,000 wells, physics-based calculation, user of the output, and absence of a reported production result." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened case study confirms 30+ data sources, 95% application-data access, 1,000+ users, ~9 million monthly queries, >5,000 wells with daily pressure calculation, and engineering workflows. Vendor states a $50,000 sensor alternative was uneconomical but does not say sensors were installed or avoided in a counted number. Undated deployment and no financial/accuracy result remain key limits. No same-project canonical match found; keep as data-platform/engineering context, not AI count.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R16-US-01", "verdict": "confirmed", "patch": { "limits": "Vendor-authored, undated customer story; current status/date of deployment is unknown. The 5,000+ figure is wells for which daily physics-based calculations are produced, not a documented production-uplift or model-accuracy denominator. No sensor count was avoided: $50,000 per sensor is an illustrative hardware alternative, not realized savings. Snowflake's site categorizes multiple products including AI, but this specific workflow is described as Whitson physics-based calculation via secure data sharing; no AI attribution is established." }, "reason": "Directly reopened case study confirms 30+ data sources, 95% application-data access, 1,000+ users, ~9 million monthly queries, >5,000 wells with daily pressure calculation, and engineering workflows. Vendor states a $50,000 sensor alternative was uneconomical but does not say sensors were installed or avoided in a counted number. Undated deployment and no financial/accuracy result remain key limits. No same-project canonical match found; keep as data-platform/engineering context, not AI count.", "sources_inspected": [ { "url": "https://www.snowflake.com/en/customers/all-customers/case-study/devon-energy/", "access": "Vendor-hosted customer story opened directly in cross-audit", "locator": "Lines 15–20, 57–80; sensor alternative and daily well calculations at 71–79.", "date": "Undated page; accessed 2026-10-07" } ], "recommended_disposition": "background" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R16-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Undated vendor case; operating start and research-window eligibility are not established." }, { "id": "T20-R17-US-02", "company": "Devon Energy", "title": "Devon puts digital and operational technology under its CTO", "category": "Technology governance and operating model", "kind": "context", "ai_role": "The source mentions no AI deployment or AI-specific decision rights. The CTO scope includes OT, IT and digital functions, without describing model development or production workflow controls.", "asset": "Corporate technology and operating organizations supporting Devon's U.S. E&P portfolio.", "stage": "Leadership structure announced January 13, 2025; the announcement says Trey Lowe was promoted to SVP and Chief Technology Officer and describes his team scope.", "operating_period": "As announced 2025-01-13; no subsequent organization-chart update checked in this pass.", "claim": "Devon promoted Trey Lowe to SVP and Chief Technology Officer, while naming separate SVP roles for E&P asset management and E&P operations. The release says the CTO's team includes Devon Energy Ventures, operational technology, IT and other digital teams.", "economics": "No technology organization budget, headcount, operating KPI or financial contribution disclosed.", "baseline": "No before/after organizational comparison or explicit decision-rights map disclosed.", "limits": "A leadership release documents executive scope, not day-to-day ownership of specific systems or asset workflows. Team makeup and reporting lines may have changed since Jan. 2025; this pass did not verify current org structure. Do not treat executive centralization as proof of operating autonomy, AI adoption or improved performance.", "relationship": "No duplicate org-ownership finding was present in the 283 production profiles or 75 prior observations. Distinct from Devon's AI-006/AI-007 workflows, which document deployment use cases rather than organizational accountability.", "decision_question": "Who currently owns production software, data infrastructure, model validation and on-asset workflow change, and which decisions remain with E&P asset/operations leaders?", "company_key": "Devon Energy", "run": "Rounds 11–20", "disposition": "background", "sources": [ { "title": "Devon Energy Announces Updates to Executive Leadership Team", "publisher": "Devon Energy", "date": "2025-01-13", "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Announces-Updates-to-Executive-Leadership-Team/", "locator": "Lines 27–43, especially 35–43 for executive appointments and CTO team scope.", "access": "Directly opened primary issuer release; leadership and team scope inspected.", "supports": "Dated executive roles and stated inclusion of ventures, OT, IT and digital teams in CTO organization." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct Devon issuer release confirms January 13, 2025 leadership changes: CTO scope includes Energy Ventures, operational technology, IT and other digital teams, while E&P Asset Management and E&P Operations have separately named SVPs. This establishes formal role boundaries at announcement, not later/current staffing or outcomes.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R17-US-02", "verdict": "confirmed", "patch": {}, "reason": "Direct Devon issuer release confirms January 13, 2025 leadership changes: CTO scope includes Energy Ventures, operational technology, IT and other digital teams, while E&P Asset Management and E&P Operations have separately named SVPs. This establishes formal role boundaries at announcement, not later/current staffing or outcomes.", "sources_inspected": [ { "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Announces-Updates-to-Executive-Leadership-Team/", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 27–43; especially 35–43 for roles and CTO-team scope.", "date": "2025-01-13" } ], "recommended_disposition": "background" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R17-US-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "As announced 2025-01-13; no subsequent organization-chart update checked in this pass." }, { "id": "T10-R01-US-02", "company": "Diamondback Energy", "title": "Continuous pumping reaches first full operating quarter", "category": "completion equipment / pumping utilization", "kind": "update", "ai_role": "No AI role disclosed. Conventional completion process/equipment innovation; source provides no ML/AI attribution.", "asset": "Diamondback Permian Basin completions.", "stage": "First full quarter of continuous pumping reported in Q2 2026; management says it is operating at scale, but fleet/well denominator is not supplied.", "operating_period": "Q2 2026; release dated 2026-08-03.", "claim": "Diamondback reported average pumping time of 21.3 hours per day in its first full quarter of continuous pumping, corresponding to about 4,700 lateral feet completed per day. In the same operations paragraph, equipment cost per well fell about 14% quarter-over-quarter; the company does not expressly attribute the full cost decline to continuous pumping.", "economics": "Preserve 21.3 pumping hours/day and ~4,700 lateral feet/day as reported first-full-quarter metrics; ~14% QoQ decline is equipment cost per well, not attributed to continuous pumping alone. Flaring reduction and protected oil are attributed to gas-offload strategy, not pumping.", "baseline": "21.3 pumping hours/day and ~4,700 lateral ft/day are Q2 2026 reported averages. Equipment cost comparison is Q2 vs Q1 2026.", "limits": "Issuer-reported operating metrics; no crew/fleet count, eligible well denominator, prior pumping hours/day, stage count, well design adjustment, cash cost/ft, capital cost of custom fleets, or matched control. Commodity/pricing environment, activity and equipment mix can affect comparisons.", "relationship": "The same Q2 PDF is reused in R08 for a different chemical-EOR program passage; source reuse is not evidence of project duplication.", "decision_question": "Across how many fleets and wells was the 21.3 hours/day achieved, what was the prior/control pump-hours and $/lateral-foot baseline, and what custom equipment/integration costs were required?", "company_key": "Diamondback Energy", "run": "Rounds 1–10", "disposition": "include_as_physical_operations_update", "sources": [ { "title": "Diamondback Energy, Inc. Form 8-K, Exhibit 99.1 (Second Quarter 2026 Results)", "publisher": "Diamondback Energy", "date": "2026-08-03", "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "locator": "Q2 2026 Operational Performance, PDF p.22 / lines 719–725.", "access": "Issuer-hosted PDF opened", "supports": "First full quarter, pump-hours/day, lateral feet/day, QoQ equipment cost/well and adjacent flaring/offload statements." } ], "references": [ { "id": "TECH-05", "relationship": "The same Q2 PDF is reused in R08 for a different chemical-EOR program passage; source reuse is not evidence of project duplication." } ], "review": { "verdict": "confirmed", "reason": "Diamondback Q2 2026 Form 8-K reports the exact metrics and places distinct mechanisms in adjacent sentences. Do not credit all adjacent operational results to continuous pumping or the electrified fleet.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R01-US-02", "verdict": "confirmed", "patch": { "economics": "Preserve 21.3 pumping hours/day and ~4,700 lateral feet/day as reported first-full-quarter metrics; ~14% QoQ decline is equipment cost per well, not attributed to continuous pumping alone. Flaring reduction and protected oil are attributed to gas-offload strategy, not pumping.", "relationship": "The same Q2 PDF is reused in R08 for a different chemical-EOR program passage; source reuse is not evidence of project duplication." }, "reason": "Diamondback Q2 2026 Form 8-K reports the exact metrics and places distinct mechanisms in adjacent sentences. Do not credit all adjacent operational results to continuous pumping or the electrified fleet.", "recommended_disposition": "include_as_physical_operations_update", "sources_inspected": [ { "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "access": "Issuer-hosted PDF opened directly", "locator": "Q2 2026 Operational Performance, PDF p. 22, lines 721-725." } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R01-US-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Q2 2026; release dated 2026-08-03." }, { "id": "T20-R18-US-01", "company": "Diamondback Energy", "title": "Diamondback is still testing chemical EOR; recovery gains remain undisclosed", "category": "Enhanced oil recovery / chemical treatment", "kind": "update", "ai_role": "No AI role disclosed; the initiative is a physical surfactant-based recovery test and associated well evaluation.", "asset": "Diamondback Permian Basin producing wells; exact field, zones, injection design, well selection and treatment population are not identified in these releases.", "stage": "February 23, 2026 letter: company reports approximately $30 million invested in late 2025 on a surfactant pilot testing 60 wells, with positive results and more testing planned. August 3, 2026 Q2 call: company says a 50-well pilot program was completed in H2 2025 and a second batch was still flowing back. The available sources do not reconcile the 60-well and 50-well counts or establish whether batches overlap; no commercial deployment established.", "operating_period": "Initial pilot/investment described as late 2025; first update published 2026-02-23, latest update published 2026-08-03.", "claim": "On 2026-02-23, Diamondback said it invested approximately $30 million in late 2025 on a surfactant pilot testing 60 wells, with positive results and additional tests planned in 2026. On 2026-08-03, it said its 50-well pilot program had been completed in H2 2025 and the second batch of well tests was still flowing back, with 'encouraging' results. The sources do not state whether 60 and 50 refer to the same cohort or different phases/populations.", "economics": "Approximately $30 million is disclosed for the late-2025 pilot investment; the release does not clarify whether this is total pilot cost, product-only cost or capital plus operating cost. No incremental oil, recovery-factor uplift, treatment cost per well/barrel, decline response, payout, cash benefit or control-well comparison is disclosed.", "baseline": "No untreated control population, pre-treatment production baseline, production normalization, well count per second batch or measurement window is given. The 'positive'/'encouraging' language is qualitative issuer characterization.", "limits": "The 50-versus-60 well-count mismatch needs source clarification before using an eligible-well denominator. Flowback is an interim stage and not a recovery factor or lasting production outcome. The pilot investment cannot be translated to cost per treated well until scope is clear; no cost/benefit or scale decision can be derived. Primary operator disclosures, but no independent technical verification.", "relationship": "Longitudinal update to the earlier Diamondback chemical-EOR observation T10-R08-US-01. Preserve the February-versus-August source-vintage discrepancy in the canonical record; don't count each disclosure or pilot phase as a separate initiative without cohort clarification.", "decision_question": "Do the 50-well and 60-well counts describe one cohort or separate phases, what was included in the $30m, and what normalized oil response versus matched untreated wells persisted after flowback across each formation and treatment design?", "company_key": "Diamondback Energy", "run": "Rounds 11–20", "disposition": "enrich_existing", "sources": [ { "title": "Letter to Stockholders Issued by Diamondback Energy, Inc. (FY2025 results)", "publisher": "Diamondback Energy", "date": "2026-02-23", "url": "https://ir.diamondbackenergy.com/news-releases/news-release-details/letter-stockholders-issued-diamondback-energy-inc-10", "locator": "Lines 81–82; approximately $30m, late-2025 surfactant pilot testing 60 wells, positive results and planned additional tests.", "access": "Directly opened primary issuer HTML; exact passage inspected.", "supports": "Dated early pilot cost/count/status and stated follow-on intent; not a measured recovery outcome." }, { "title": "Form 8-K — Second Quarter 2026 Shareholder Letter", "publisher": "Diamondback Energy", "date": "2026-08-03", "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "locator": "PDF pp. 22–23; lines 726–735; completed 50-well pilot program and second-batch flowback status.", "access": "Directly opened primary issuer-hosted PDF; relevant operations passage inspected.", "supports": "Latest test stage and separately disclosed 50-well cohort wording; no quantified recovery or commercial-scale result." } ], "references": [ { "id": "T10-R08-US-01", "relationship": "Longitudinal update to the earlier Diamondback chemical-EOR observation T10-R08-US-01. Preserve the February-versus-August source-vintage discrepancy in the canonical record; don't count each disclosure or pilot phase as a separate initiative without cohort clarification." } ], "review": { "verdict": "confirmed", "reason": "Both primary sources were reopened directly. The February letter confirms ~60 wells and ~$30m investment; August 8-K says 50-well program completed H2 2025 and second batch flowing back. The mismatch remains unresolved, so retain it explicitly and do not sum the well counts or infer test-cohort size. $30m is a reported pilot investment, not a cost-per-well or demonstrated return. Same project as earlier Diamondback EOR observation T10-R08-US-01.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R18-US-01", "verdict": "confirmed", "patch": { "stage": "February 23, 2026 letter: company reports approximately $30 million invested in late 2025 on a surfactant pilot testing 60 wells, with positive results and more testing planned. August 3, 2026 Q2 call: company says a 50-well pilot program was completed in H2 2025 and a second batch was still flowing back. The available sources do not reconcile the 60-well and 50-well counts or establish whether batches overlap; no commercial deployment established." }, "reason": "Both primary sources were reopened directly. The February letter confirms ~60 wells and ~$30m investment; August 8-K says 50-well program completed H2 2025 and second batch flowing back. The mismatch remains unresolved, so retain it explicitly and do not sum the well counts or infer test-cohort size. $30m is a reported pilot investment, not a cost-per-well or demonstrated return. Same project as earlier Diamondback EOR observation T10-R08-US-01.", "sources_inspected": [ { "url": "https://ir.diamondbackenergy.com/news-releases/news-release-details/letter-stockholders-issued-diamondback-energy-inc-10", "access": "Issuer HTML opened directly in cross-audit", "locator": "Letter dated 2026-02-23, lines 74–82; ~$30m and 60 wells at line 81.", "date": "2026-02-23" }, { "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "access": "Issuer-hosted Form 8-K PDF opened directly in cross-audit", "locator": "PDF page 22, lines 726–735; 50-well completed pilot and second batch flowing back at 726–729.", "date": "2026-08-03" } ], "recommended_disposition": "enrich_existing" } ] }, "department": "Subsurface & recovery", "group_id": "T10-R08-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R08-US-01", "company": "Diamondback Energy", "title": "Diamondback’s first chemical EOR pilot leads to follow-on testing", "category": "chemical enhanced oil recovery / pilot progression and scale boundary", "kind": "update", "ai_role": "No AI role or test method disclosed in this operational status passage. Do not infer AI or assume the process is non-AI based on silence.", "asset": "Permian producing-well portfolio. First pilot comprised 50 wells; the source does not state the number or locations in the second test batch.", "stage": "Initial 50-well pilot completed in H2 2025; as of Q2 2026, second batch of well tests was flowing back. Commercial-scale deployment and the decision to invest behind the method were still prospective.", "operating_period": "Pilot completed H2 2025; second-batch flowback underway in Q2 2026; issuer disclosure dated 2026-08-03.", "claim": "Diamondback says its 50-well chemical-EOR pilot was completed in H2 2025 and a second batch of well tests was flowing back in Q2 2026, with qualitative 'encouraging' language but no quantified recovery factor or production result in the cited passage.", "economics": "No incremental oil recovery, cumulative response period, intervention cost, chemical use, production impact, decline-adjusted baseline or payout is disclosed. The source's characterization of recovery improvement as potentially high-return is forward-looking value framing, not observed project economics.", "baseline": "No control wells, untreated comparison group, pre-treatment production decline, treatment timing, eligible well inventory or sample count for the second batch disclosed. 'Encouraging' has no quantitative definition in the source.", "limits": "Issuer status disclosure only. A 50-well count establishes pilot activity, not 50 successful responses or independent statistical support. Second-batch well count and result duration are absent. No chemicals, injection method, candidate selection, pressure/interference effects, water disposal consequences or failure cases disclosed. No evidence of technical failure or abandonment is provided; the commercial/scaling stage remains unresolved.", "relationship": "Shares the Q2 filing URL with R01's continuous-pumping observation but describes a separate chemical-EOR test program; not a duplicate deployment and not an AI claim.", "decision_question": "What were the treatment design, treated and control well counts, oil-recovery uplift per well over a defined duration, chemical and intervention cost, adverse effects and gate criteria for a scaled capital commitment?", "company_key": "Diamondback Energy", "run": "Rounds 1–10", "disposition": "include_as_pilot_status_if_section_tracks_physical_methods; keep_out_of_AI_count", "sources": [ { "title": "Form 8-K for Diamondback Energy Inc. filed Aug. 3, 2026 (Q2 2026 results)", "publisher": "Diamondback Energy", "date": "2026-08-03", "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "locator": "Q2 2026 Operational Performance, PDF p. 22, paragraph on chemical EOR tests and second-batch flowback; lines 726-735.", "access": "Issuer-hosted PDF opened directly", "supports": "Completion date/status of 50-well H2 2025 pilot, follow-on second-batch flowback in Q2 2026, qualitative status, and explicit continued testing before scaled capital deployment." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct Q2 filing states pilot timing, new batch status and lack of quantified measured outcome. Preserve as pilot/flowback status, not proven commercial recovery uplift or failure.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R08-US-01", "verdict": "confirmed", "patch": { "claim": "Diamondback says its 50-well chemical-EOR pilot was completed in H2 2025 and a second batch of well tests was flowing back in Q2 2026, with qualitative 'encouraging' language but no quantified recovery factor or production result in the cited passage.", "relationship": "Shares the Q2 filing URL with R01's continuous-pumping observation but describes a separate chemical-EOR test program; not a duplicate deployment and not an AI claim." }, "reason": "Direct Q2 filing states pilot timing, new batch status and lack of quantified measured outcome. Preserve as pilot/flowback status, not proven commercial recovery uplift or failure.", "recommended_disposition": "include_as_pilot_status_if_section_tracks_physical_methods; keep_out_of_AI_count", "sources_inspected": [ { "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "access": "Issuer-hosted PDF opened directly", "locator": "Q2 2026 Operational Performance, PDF p. 22, lines 726-731." } ] } ] }, "department": "Subsurface & recovery", "group_id": "T10-R08-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Pilot completed H2 2025; second-batch flowback underway in Q2 2026; issuer disclosure dated 2026-08-03." }, { "id": "T10-R09-US-01", "company": "Diamondback Energy", "title": "Diamondback’s Barnett drilling record uses a narrower cost boundary", "category": "drilling cost / unit economics / basin-specific scale-up", "kind": "context", "ai_role": "No AI method attributed to the reported well cost; source emphasizes operational execution and speed. Do not infer AI role from parallel automation programs.", "asset": "Diamondback Barnett (north Texas) delineation/appraisal; company describes a fastest-in-company-history Barnett well in Q1 2026. Separate investor material contrasts current delineation cost with prospective full-scale development.", "stage": "Observed single-well company record in Q1 2026; full-field cost reduction is a forward-looking estimate, not yet achieved at development scale.", "operating_period": "Q1 2026 operating result disclosed 2026-05-04. Company presentation's delineation/full-development comparison was available in 2026; source presents the ~$800/ft value as an expected outcome.", "claim": "Q1 2026: one fastest-in-company-history (~18-day) Barnett well at lowest Barnett cost to date (<$400/lateral foot). Separate 2026 investor material: current delineation wells at about $1,000/ft; full-field well costs expected to fall ~20% to ~$800/ft. These represent separate well populations and stages.", "economics": "Keep <$400/ft single-well record out of the ~$1,000-to-$800 development estimate bridge. Neither reveals complete capex cost scope or eligible-population distribution; ~$800 is expected, not realized.", "baseline": "Record well compared to prior Diamondback Barnett wells; no absolute baseline or matched well details given. The full-field estimate compares ~$800/ft expected against ~$1,000/ft current delineation wells. Do not substitute the single-well <$400/ft outlier as the current cost baseline for the full-field target.", "limits": "Operator-reported; new-play delineation and full-field development have different geology, learning, pad and infrastructure scope. 'Lowest cost to date' is a single-well internal record. Q1 disclosure lacks lateral length, exact capex numerator and included cost components; full-field cost and return remain forecasts. Not proof of basin-wide economic parity without repeat wells and decline-adjusted production.", "relationship": "Adds an asset-stage/economic-eligibility boundary case, not a scalable cost-savings proof. Distinguish record-well metrics from the broader Diamondback continuous-pumping/e-fleet metrics and from the Q2 equipment-only cost-per-well change.", "decision_question": "What is the repeatable, fully loaded drilling-and-completion cost per completed lateral foot for the defined Barnett development inventory, with well count, lateral length, design, infrastructure, production type curve and facility cost included?", "company_key": "Diamondback Energy", "run": "Rounds 1–10", "disposition": "include_as_cost-denominator_context_not_savings_case", "sources": [ { "title": "Form 8-K for Diamondback Energy Inc. filed May 4, 2026 (Q1 2026 results)", "publisher": "Diamondback Energy", "date": "2026-05-04", "url": "https://ir.diamondbackenergy.com/static-files/a1520480-f925-42c2-8f51-4b4223086323", "locator": "Q1 2026 Operational Performance, PDF p. 23, lines 717-727.", "access": "Issuer-hosted PDF opened directly", "supports": "Fastest Barnett well, approximately 18 days, lowest Barnett cost to date under $400/lateral foot, plus wider company drilling/completions context." }, { "title": "Diamondback Energy Q4 2025 results / Barnett overview investor materials", "publisher": "Diamondback Energy", "date": "2026 (issuer 2026 materials; exact presentation date to verify before external citation)", "url": "https://ir.diamondbackenergy.com/static-files/69e4a842-30fe-4ce0-8b92-510ad5aff2e6", "locator": "Barnett overview / development economics: ~$1,000/ft delineation, expected ~$800/ft full development; source search-indexed in this pass, PDF body not directly opened.", "access": "Issuer-hosted document surfaced by search; body not reopened in this pass", "supports": "Separate delineation cost and full-development target; lower evidence depth than opened Q1 Form 8-K, treat as an indexed issuer lead pending direct source verification." } ], "references": [], "review": { "verdict": "correct", "reason": "Both issuer sources now opened directly. Q1 disclosure supports best-well metric; investor slide directly supports distinct delineation baseline and expected full-development cost. The original round correctly flags limits; audit upgrades source access and reinforces no single before/after comparison.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R09-US-01", "verdict": "correct", "patch": { "source_access": "The investor PDF was directly reopened in R10, upgrading the earlier indexed-only source state. Distinguish the opened Q1 result from the separate slide estimate.", "claim": "Q1 2026: one fastest-in-company-history (~18-day) Barnett well at lowest Barnett cost to date (<$400/lateral foot). Separate 2026 investor material: current delineation wells at about $1,000/ft; full-field well costs expected to fall ~20% to ~$800/ft. These represent separate well populations and stages.", "economics": "Keep <$400/ft single-well record out of the ~$1,000-to-$800 development estimate bridge. Neither reveals complete capex cost scope or eligible-population distribution; ~$800 is expected, not realized." }, "reason": "Both issuer sources now opened directly. Q1 disclosure supports best-well metric; investor slide directly supports distinct delineation baseline and expected full-development cost. The original round correctly flags limits; audit upgrades source access and reinforces no single before/after comparison.", "recommended_disposition": "include_as_cost-denominator_context_not_savings_case", "sources_inspected": [ { "url": "https://ir.diamondbackenergy.com/static-files/a1520480-f925-42c2-8f51-4b4223086323", "access": "Issuer-hosted PDF opened directly", "locator": "Q1 2026 operational performance, PDF p. 23, lines 721-724." }, { "url": "https://ir.diamondbackenergy.com/static-files/69e4a842-30fe-4ce0-8b92-510ad5aff2e6", "access": "Issuer-hosted PDF opened directly in this audit", "locator": "Barnett section, PDF p. 14, lines 795-798." } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R09-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "TECH-05", "company": "Diamondback Energy", "title": "Associated-gas microgrid and electric simul-frac", "category": "field power / completions electrification", "kind": "new_initiative", "ai_role": "Non-AI electrification/power infrastructure. Do not infer AI contribution from vendor platform descriptions.", "asset": "Not disclosed", "stage": "Q1 2026 letter says about 80% of frac fleet was electrified. Separately, sustainability/CDP disclosure describes a microgrid serving a producing field and drilling/completions, and a December 2024 agreement for four electric simul-frac fleets with approximately 200 MW of capacity.", "operating_period": "2026-05-04; 2025 disclosure", "claim": "Electrified coverage is reported; no quantified realized cost savings per well/stage or diesel-comparable baseline is disclosed. Contract capacity is not an outcome.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Separate achieved coverage from agreement/capacity; the claimed economic benefit is directional and not measured against a disclosed diesel baseline.", "relationship": "Physical microgrid and electric simul-frac change field power/fuel architecture. Separate fleet counts, gallons avoided and claimed savings; expose capex, gas opportunity cost and full system boundary as unknown.", "decision_question": "What diesel gallons, power/fuel costs, stage/day utilization and total hookup/capex support the ~80% electrified fleet claim and savings after gas/fuel logistics?", "company_key": "Diamondback Energy", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Letter to Stockholders Issued by Diamondback Energy, Inc. (Q1 2026); 2025 Sustainability/CDP disclosure", "publisher": "Diamondback Energy", "date": "2026-05-04; 2025 disclosure", "url": "https://ir.diamondbackenergy.com/news-releases/news-release-details/letter-stockholders-issued-diamondback-energy-inc-11", "locator": "Q1 letter, operating performance; sustainability/CDP PDF pp. 84, 87", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-05-04", "url": "https://ir.diamondbackenergy.com/news-releases/news-release-details/letter-stockholders-issued-diamondback-energy-inc-11", "locator": "Q1 2026 stockholder letter, electrified frac-fleet statement and directional rationale", "access": "Diamondback issuer page opened; text accessible", "supports": "This is a strong non-AI operating-technology case when the distinct denominators/statuses are kept separate. It speaks to fuel exposure and execution, but the public evidence does not quantify value capture." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025 report; agreement disclosed 2024-12", "url": "https://www.diamondbackenergy.com/static-files/faf5ab25-5ab5-4404-8c04-c7bd387ae418", "locator": "Microgrid powers producing field and drilling/completions; four-fleet/approximately 200-MW contract scope", "access": "Diamondback 2025 sustainability report PDF opened", "supports": "This is a strong non-AI operating-technology case when the distinct denominators/statuses are kept separate. It speaks to fuel exposure and execution, but the public evidence does not quantify value capture." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2024-12-13", "url": "https://voltagrid.com/diamondback-energy-halliburton-and-voltagrid-sign-agreement-for-four-electric-simul-frac-fleets-in-the-permian-basin", "locator": "Agreement to deploy four electric simul-frac fleets, approx. 200 MW", "access": "VoltaGrid partner announcement opened", "supports": "This is a strong non-AI operating-technology case when the distinct denominators/statuses are kept separate. It speaks to fuel exposure and execution, but the public evidence does not quantify value capture." } ], "references": [ { "id": "AI-045", "relationship": "company_context" }, { "id": "AI-045", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "TECH-05", "core_company": true, "ai_ids": [ "AI-045" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2026-05-04; 2025 disclosure" }, { "id": "T20-R12-US-01", "company": "Chord Energy", "title": "Chord’s first seven four-mile wells come in below their initial budget", "category": "Drilling and completion design", "kind": "new_initiative", "ai_role": "No AI contribution is disclosed for the extended-lateral design, tracer evaluation or single-run cleanout. A separate AI/ML rod-lift result in the same release is already recorded as AI-097 and is not part of this finding.", "asset": "Chord-operated Williston Basin four-mile-lateral program; seven wells turned in line in 2025, including three after the prior November update.", "stage": "Operating wells with early performance reported; first four-mile DSU development on the Toonie pad had begun fracturing and was scheduled to come online in Q1 2026 at disclosure.", "operating_period": "2025 operating results, reported 2026-02-25.", "claim": "Chord reported seven four-mile wells turned in line in 2025. Initial performance was meeting or exceeding expectations, average costs were below budget, and tracer data for all seven indicated contribution from the full lateral. The company said four-mile well costs were reduced by more than 10% versus its 2025 initial budget designs, supported by strong performance and efficient execution including single-run cleanouts.", "economics": "Reported >10% reduction versus initial 2025 budget designs; no absolute cost per well or capital amount disclosed in the cited release. This is a company-reported budget comparison, not audited realized savings or a comparison with two-mile wells. The 2025 capital figure and production result are broader portfolio data and should not be assigned to this technology.", "baseline": "Chord's initial 2025 budget designs for four-mile wells. The release does not specify design assumptions, sample selection, actual well count in the average-cost calculation, lateral-length convention or realized cost boundary.", "limits": "Early well results may be affected by reservoir quality, spacing, working interest, service prices and design changes. Tracer indication supports full-lateral contribution but is not proof of uniform production, EUR uplift or economic superiority. The source does not report a matched shorter-lateral comparator, full-cycle recovery, payback, or eligible inventory count.", "relationship": "Distinct from canonical AI-097 (AI-driven rod-lift optimization), which is a separate production workflow repeated in the same February 2026 release. No matching four-mile-lateral operating record appeared in the 51 prior observations or production profile index. Continental prior gaps T10-R01-LIMITS-03 and T10-R01-US-03 remain bounded source-search observations.", "decision_question": "For additional eligible four-mile DSUs, what are realized D&C cost per lateral foot, cycle time, production/EUR versus matched two- or three-mile wells, and the cost of tracer/cleanout changes after normalizing for location and service prices?", "company_key": "Chord Energy", "run": "Rounds 11–20", "disposition": "include", "sources": [ { "title": "Chord Energy Reports Fourth Quarter and Full-Year 2025 Financial and Operating Results, Issues 2026 Outlook and Declares Base Dividend", "publisher": "Chord Energy", "date": "2026-02-25", "url": "https://ir.chordenergy.com/2026-02-25-Chord-Energy-Reports-Fourth-Quarter-and-Full-Year-2025-Financial-and-Operating-Results%2C-Issues-2026-Outlook-and-Declares-Base-Dividend", "locator": "Operations Update, lines 210–214; reported deployment, cost and tracer scope. Lines 84–85 summarize seven wells and program outlook.", "access": "Directly opened primary issuer HTML; full relevant operating update inspected.", "supports": "Seven 2025 four-mile TILs, all-seven tracer indication, >10% below initial budget designs, and stated execution factors." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Direct February Chord release confirms seven 2025 four-mile wells, average costs below budget, >10% below initial 2025 design budgets, and tracer indication of full-lateral contribution for all seven. It says the Toonie first four-mile DSU had begun fracturing and was expected online in Q1 2026. No absolute cost or two-mile cost comparator; the original record distinguishes the budget comparison from realized savings. Chord AI-097 in the same release is artificial-lift optimization, not this completion design.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R12-US-01", "verdict": "confirmed", "patch": {}, "reason": "Direct February Chord release confirms seven 2025 four-mile wells, average costs below budget, >10% below initial 2025 design budgets, and tracer indication of full-lateral contribution for all seven. It says the Toonie first four-mile DSU had begun fracturing and was expected online in Q1 2026. No absolute cost or two-mile cost comparator; the original record distinguishes the budget comparison from realized savings. Chord AI-097 in the same release is artificial-lift optimization, not this completion design.", "sources_inspected": [ { "url": "https://ir.chordenergy.com/2026-02-25-Chord-Energy-Reports-Fourth-Quarter-and-Full-Year-2025-Financial-and-Operating-Results%2C-Issues-2026-Outlook-and-Declares-Base-Dividend", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 210–216; four-mile results at 211–214; separate rod-lift AI workflow at 215–216.", "date": "2026-02-25" } ], "recommended_disposition": "include" } ] }, "department": "Drilling & completions", "group_id": "T20-R12-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 operating results, reported 2026-02-25." }, { "id": "T20-R19-US-01", "company": "Chord Energy", "title": "Chord expands its four-mile lateral program to 26 executed wells", "category": "Extended-reach drilling and completion / completion-method innovation", "kind": "update", "ai_role": "No AI role is stated for four-mile lateral execution or trimulfrac. Chord separately mentions continuing AI artificial-lift optimization in the same August release; that is a distinct workflow and is not attributed to the four-mile program.", "asset": "Chord-operated Williston Basin; four-mile laterals and unspecified completion areas. The November 2025 release identifies Rystedt, State Line, Violet-Olson and Wheelock examples; the August 2026 update does not name the 26-well population or trimulfrac pad.", "stage": "As of early Q3 2026, Chord reported 26 total four-mile wells executed; the release separately says early program performance and costs were in line with expectations. It does not establish that all 26 were TIL or producing. The Basin's first trimulfrac completion had been executed; the source does not give a distinct well count or trimulfrac cost/savings result.", "operating_period": "2025 pilot/development and early 2026 scale-up; issuer updates published 2025-11-04 and 2026-08-05.", "claim": "Longitudinal reports describe distinct vintages: November 2025—four four-mile laterals TIL YTD, seven expected for FY2025, with the Rystedt well matching two two-mile analog production after six months and named tracer data showing full-lateral contribution; February 2026—seven four-mile wells TIL in 2025, full-lateral tracer indication across all seven, and average cost >10% below initial 2025 budget design; August 2026—26 four-mile wells executed as of early Q3, costs/early performance in line with expectations, plus the Basin's first trimulfrac completion and selective continued use planned. These measures have different cohorts and baselines; no absolute cost, normalized savings or trimulfrac-specific benefit is disclosed.", "economics": "The only quantified cost statement in the reviewed history is >10% below Chord's initial 2025 design budgets for the seven-well 2025 program. Absolute dollars, cost per lateral foot, included D&C/facilities/land/water costs, budget rebasing, the 26-well cohort cost and trimulfrac-specific savings are not disclosed. The six-month production comparison for Rystedt is early-time only and lacks matched capital and EUR data.", "baseline": "The 2025 cost claim compares average four-mile well cost against initial internal 2025 design budgets; exact well count in the average, scope and budget assumptions are not given. The Rystedt comparison uses two two-mile analog wells, but matching criteria and production normalization are not disclosed. The August 2026 'in line with expectations' baseline is unspecified.", "limits": "Population and method scope differ across disclosures: seven 2025 wells versus 26 executed by early Q3 2026, and the later release does not identify how many used trimulfrac. The releases do not state whether all executed wells are TIL, their working interest, eligible future inventory, or whether every pad can accommodate four-mile geometry. Reported early performance and budget variance are issuer claims, not independently validated causal savings. Do not compare Chord's >10% below initial budget directly with another operator's cost/foot or equipment cost/well metric.", "relationship": "Longitudinal update enriching four-mile program record T20-R12-US-01 with the later 26-well scale and first trimulfrac deployment. It also bears on the existing cross-operator metric-context observation T10-R09-US-02: Chord's percent-under-initial-budget claim cannot be added to EOG cost/well, EQT cost/foot or Diamondback equipment cost/well as a comparable savings ranking.", "decision_question": "For the next eligible four-mile DSUs, what is actual full D&C cost per completed lateral foot versus matched shorter laterals after normalizing geology, service prices, facilities, working interest and budget vintage; and what incremental cost and cycle-time effect does trimulfrac show against the prior completion design?", "company_key": "Chord Energy", "run": "Rounds 11–20", "disposition": "enrich_existing", "sources": [ { "title": "Chord Energy Reports Second Quarter 2026 Financial and Operating Results, Declares Base Dividend and Updates 2026 Outlook", "publisher": "Chord Energy", "date": "2026-08-05", "url": "https://ir.chordenergy.com/2026-08-05-Chord-Energy-Reports-Second-Quarter-2026-Financial-and-Operating-Results%2C-Declares-Base-Dividend-and-Updates-2026-Outlook", "locator": "Lines 156–161: 26 four-mile wells as of early 3Q26; capital cost and early-performance status; first basin trimulfrac and selective continuation; AI lift optimization separately noted.", "access": "Directly opened primary issuer HTML; exact operations-update passage inspected.", "supports": "Latest disclosed program scale, capital status and trimulfrac method stage; not absolute costs, matched economics or trimulfrac-specific savings." }, { "title": "Chord Energy Reports Third Quarter 2025 Financial and Operating Results, Declares Base Dividend and Issues Updated Outlook", "publisher": "Chord Energy", "date": "2025-11-04", "url": "https://ir.chordenergy.com/2025-11-04-Chord-Energy-Reports-Third-Quarter-2025-Financial-and-Operating-Results%2C-Declares-Base-Dividend-and-Issues-Updated-Outlook", "locator": "Lines 159–164: four four-mile wells YTD, seven expected FY25; Rystedt six-month production versus two two-mile analogs; named examples and execution methods.", "access": "Directly opened primary issuer HTML; exact operations-update passage inspected.", "supports": "Earlier cohort, early production comparison and execution history; does not define normalized economics." }, { "title": "Chord Energy Reports Fourth Quarter and Full-Year 2025 Financial and Operating Results, Issues 2026 Outlook and Declares Base Dividend", "publisher": "Chord Energy", "date": "2026-02-25", "url": "https://ir.chordenergy.com/2026-02-25-Chord-Energy-Reports-Fourth-Quarter-and-Full-Year-2025-Financial-and-Operating-Results%2C-Issues-2026-Outlook-and-Declares-Base-Dividend", "locator": "Operations update inspected previously in round 12, lines 210–216: seven four-mile 2025 wells; average costs >10% below initial 2025 budget designs.", "access": "Primary issuer page indexed and directly opened in round 12; not freshly reopened for this pass. Earlier directly inspected text is retained in round-12-us.json.", "supports": "Prior-period budget-variance claim and population; not later costs or a full-cost boundary." } ], "references": [ { "id": "T20-R12-US-01", "relationship": "Longitudinal update enriching four-mile program record T20-R12-US-01 with the later 26-well scale and first trimulfrac deployment. It also bears on the existing cross-operator metric-context observation T10-R09-US-02: Chord's percent-under-initial-budget claim cannot be added to EOG cost/well, EQT cost/foot or Diamondback equipment cost/well as a comparable savings ranking." }, { "id": "T10-R09-US-02", "relationship": "Longitudinal update enriching four-mile program record T20-R12-US-01 with the later 26-well scale and first trimulfrac deployment. It also bears on the existing cross-operator metric-context observation T10-R09-US-02: Chord's percent-under-initial-budget claim cannot be added to EOG cost/well, EQT cost/foot or Diamondback equipment cost/well as a comparable savings ranking." } ], "review": { "verdict": "correct", "reason": "Directly reopened Nov 2025, Feb 2026 and Aug 2026 issuer releases confirm the program sequence. August specifically says 'executed 26 total' and does not say 26 TILs; it separately reports the basin's first trimulfrac completion. Preserve this wording and avoid conflating >10% below initial design budget from the 2025 seven-well cohort with later 26-well costs 'in line with expectations.' The AI-097 rod-lift workflow is separate; this updates T20-R12-US-01, not a new project.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R19-US-01", "verdict": "correct", "patch": { "stage": "As of early Q3 2026, Chord reported 26 total four-mile wells executed; the release separately says early program performance and costs were in line with expectations. It does not establish that all 26 were TIL or producing. The Basin's first trimulfrac completion had been executed; the source does not give a distinct well count or trimulfrac cost/savings result.", "claim": "Longitudinal reports describe distinct vintages: November 2025—four four-mile laterals TIL YTD, seven expected for FY2025, with the Rystedt well matching two two-mile analog production after six months and named tracer data showing full-lateral contribution; February 2026—seven four-mile wells TIL in 2025, full-lateral tracer indication across all seven, and average cost >10% below initial 2025 budget design; August 2026—26 four-mile wells executed as of early Q3, costs/early performance in line with expectations, plus the Basin's first trimulfrac completion and selective continued use planned. These measures have different cohorts and baselines; no absolute cost, normalized savings or trimulfrac-specific benefit is disclosed." }, "reason": "Directly reopened Nov 2025, Feb 2026 and Aug 2026 issuer releases confirm the program sequence. August specifically says 'executed 26 total' and does not say 26 TILs; it separately reports the basin's first trimulfrac completion. Preserve this wording and avoid conflating >10% below initial design budget from the 2025 seven-well cohort with later 26-well costs 'in line with expectations.' The AI-097 rod-lift workflow is separate; this updates T20-R12-US-01, not a new project.", "sources_inspected": [ { "url": "https://ir.chordenergy.com/2025-11-04-Chord-Energy-Reports-Third-Quarter-2025-Financial-and-Operating-Results%2C-Declares-Base-Dividend-and-Issues-Updated-Outlook", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 159–164; especially 160–162 for four YTD/seven expected, tracer and six-month comparison.", "date": "2025-11-04" }, { "url": "https://ir.chordenergy.com/2026-02-25-Chord-Energy-Reports-Fourth-Quarter-and-Full-Year-2025-Financial-and-Operating-Results%2C-Issues-2026-Outlook-and-Declares-Base-Dividend", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 210–216; seven 2025 wells, costs vs initial budget, tracer data and separate AI lift workflow.", "date": "2026-02-25" }, { "url": "https://ir.chordenergy.com/2026-08-05-Chord-Energy-Reports-Second-Quarter-2026-Financial-and-Operating-Results%2C-Declares-Base-Dividend-and-Updates-2026-Outlook", "access": "Issuer HTML opened directly in cross-audit", "locator": "Lines 156–161; 26 executed wells, expectations, first trimulfrac and selective continuation.", "date": "2026-08-05" } ], "recommended_disposition": "enrich_existing" } ] }, "department": "Drilling & completions", "group_id": "T20-R12-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 pilot/development and early 2026 scale-up; issuer updates published 2025-11-04 and 2026-08-05." }, { "id": "R1-US-01", "company": "ConocoPhillips", "title": "Temporary fiber-optic sensing with adaptive frac-stage control", "category": "completions / fiber sensing / process control", "kind": "new_initiative", "ai_role": "Unclear/hybrid. Automation is explicit; AI is neither attributed nor ruled out. Do not call this an AI result.", "asset": "Permian unconventional completion trial", "stage": "Trial disclosed as recently completed; no broader deployment status established.", "operating_period": "Recent trial; exact date not stated", "claim": "Surface equipment adjusted stage volumes by as much as -5% to +25%. Executive says this approach could lower completion cost by $5-$15 per foot while improving recovery and reducing frac hits.", "economics": "Potential $5-$15 per lateral foot reduction; not booked/measured outcome in the disclosure.", "baseline": "No well/stage denominator, comparator, absolute volumes, or baseline cost specified. The stage-volume change is reported output; $5-$15/ft is potential benefit, not a realized saving.", "limits": "Issuer executive interview; trial size, duration, control algorithm, eligible-well share, economics and independent verification are absent. Do not infer sustained uplift or commercial rollout.", "relationship": "Shows fiber sensing plus automatic process adjustment can be an alternative to an AI narrative. Adjustment logic is undisclosed; -5%/+25% is stage-volume change, while $5–$15/ft is potential, not realized savings.", "decision_question": "On how many stages/wells was fiber deployed, and what matched-well $/ft, recovery and frac-hit changes were realized after cable/control costs?", "company_key": "ConocoPhillips", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Q&A / Nick Olds on unlocking Lower 48 results through scale, inventory and tech", "publisher": "ConocoPhillips", "date": "2026-03-24", "url": "https://www.conocophillips.com/spiritnow/story/qa-nick-olds-on-unlocking-lower-48-results-through-scale-inventory-and-tech/", "locator": "Lines 99-107: advanced diagnostics, first-of-its-kind fiber trial, autonomous stage-volume adjustments, potential cost range and distinct AI gas-lift statement", "access": "Issuer page opened; full relevant section reviewed", "supports": "Trial setup, control response magnitude, potential $/ft benefits, distinction from AI gas-lift" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-03-24", "url": "https://www.conocophillips.com/spiritnow/story/qa-nick-olds-on-unlocking-lower-48-results-through-scale-inventory-and-tech/", "locator": "Published 2026-03-24; lines 99-107, especially fiber-optic trial and potential benefits", "access": "Issuer page opened; full text reviewed", "supports": "Source confirms a recently completed first-of-its-kind Permian trial using temporary fiber-optic downhole measurements; data autonomously adjusted surface equipment and stage volumes by -5% to +25%. $5-$15/ft is expressly framed as potential benefit, not realized cost saving. No well/stage count or exact trial period is disclosed. AI gas-lift optimization appears as a separate production-side workflow in the same article." } ], "references": [ { "id": "AI-090", "relationship": "company_context" }, { "id": "AI-202", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "R1-US-01", "core_company": true, "ai_ids": [ "AI-090", "AI-202" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Recent trial; exact date not stated" }, { "id": "R1-US-05", "company": "ConocoPhillips", "title": "Canada facility digital twins for maintenance and work planning", "category": "facility visualization / maintenance execution / data integration", "kind": "new_initiative", "ai_role": "AI role not stated. Digital twin/data visualization is established; do not infer no-AI architecture from silence.", "asset": "Surmont Central Processing Facility 2 and Montney C-11-K central processing plant; broader prior implementation at Norway and Australia (APLNG) noted by company.", "stage": "Digital twin adopted for Surmont CPF2 and Montney C-11-K by May 2025. Montney then had limited functionality; SAP/document/data integration upgrade was still planned for summer 2025. Full build-out of main Canadian facilities was estimated to take until end-2026.", "operating_period": "Use cases observed/reported by May 2025", "claim": "COP says workers used the 3D digital twin to locate a hidden spool, isolate/blind it without extensive physical searching or disruptions, and avoid unnecessary downtime/production halts. This is one qualitative case; no time, cost, uptime or production amount is given.", "economics": "Potentially avoided search/maintenance delay and crane/scaffold waste; no measured amount.", "baseline": "Anecdotal task comparison to physical searches and 2D plot plans; no measured baseline or controlled comparison.", "limits": "Issuer story with qualitative user examples; adoption and economic benefit not quantified. Montney model had less functionality and integrations were still being built.", "relationship": "Retain as a bounded foundation/use case, not AI performance. Two named Canadian facilities; incomplete Montney data/content integration is a material deployment constraint.", "decision_question": "What downtime hours/barrels deferred and field labor/search cost were avoided per twin-enabled work order versus standard document search?", "company_key": "ConocoPhillips", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Visualizing success / Canada rolls out digital twins for Surmont and Montney", "publisher": "ConocoPhillips", "date": "2025-05-27", "url": "https://www.conocophillips.com/spiritnow/story/visualizing-success-canada-rolls-out-digital-twins-for-surmont-and-montney/", "locator": "Canada deployment, work use cases, hidden-spool example and build-out status", "access": "Issuer page opened; full relevant passage reviewed", "supports": "Named sites, active use, maintenance/work-planning examples, qualitative downtime avoidance, rollout limitation" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-05-27", "url": "https://www.conocophillips.com/spiritnow/story/visualizing-success-canada-rolls-out-digital-twins-for-surmont-and-montney/", "locator": "Published 2025-05-27; lines 41-79, current tasks, spool example, limitations, future integration/build-out", "access": "Issuer page opened; full article reviewed", "supports": "Primary source confirms sites and task examples. Preserve the single anecdote as qualitative evidence and the source's material limit on Montney functionality and remaining rollout work." } ], "references": [ { "id": "AI-202", "relationship": "company_context" } ], "department": "Maintenance & reliability", "group_id": "R1-US-05", "core_company": true, "ai_ids": [ "AI-202" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Use cases observed/reported by May 2025" }, { "id": "T10-R02-US-01", "company": "ConocoPhillips", "title": "Eagle Ford horseshoe wells combine two laterals in one drilling event", "category": "well architecture / drilling and completion design", "kind": "new_initiative", "ai_role": "No AI role disclosed; the disclosed intervention is physical well geometry and trajectory execution. This does not establish that no AI tools were used in planning or operations.", "asset": "Eagle Ford projects with complex, deep, faulted or irregular lease geometry; issuer describes two projects and four completed horseshoe wells.", "stage": "Completed small-scale application. Company says production was in line with expectations and comparable to standard long laterals; broader applicability was still being evaluated.", "operating_period": "Recent Eagle Ford projects described in an issuer article published 2026-05-18; exact spud/completion dates for all four wells are not specified.", "claim": "ConocoPhillips describes an Eagle Ford horseshoe-well design that joins two laterals in one drilling event. The issuer estimates $10-$15/BOE lower cost of supply versus traditional designs; test-well tracer evidence indicated production contribution along the wellbore. Broader application remains under evaluation.", "economics": "Label $10-$15/BOE as an issuer estimate, not realized project cost savings or a disclosed AFE amount; single-project test results do not establish repeatability.", "baseline": "Issuer comparison is against traditional well design / standard long laterals, but does not provide matched-well characteristics, absolute capex, date range for savings, or a detailed cost-of-supply model. Production is described as comparable and in line with expectations, not as uplifted recovery.", "limits": "Only four wells across two projects are described; source gives no individual well results, full eligible-well denominator, cost breakdown, uncertainty range or operator working-interest basis. Benefits are company-reported estimates. Deployment beyond Eagle Ford was under evaluation at publication; this is not evidence of basin-wide standardization.", "relationship": "Adds a physical well-design example beyond the existing software/AI and fleet-efficiency coverage. Distinct from Conoco's existing robotics/fiber records; appropriate as a separate operating-technology example if the site includes engineering-led cost advantage.", "decision_question": "For which lease geometries and reservoir conditions does the design beat a matched two-well/standard-long-lateral alternative after incremental trajectory, completion, intervention and production-risk costs, and has the four-well method been repeated at scale?", "company_key": "ConocoPhillips", "run": "Rounds 1–10", "disposition": "include_physical_engineering_example", "sources": [ { "title": "Value curve: Horseshoe wells expand development options", "publisher": "ConocoPhillips (SpiritNow)", "date": "2026-05-18", "url": "https://www.conocophillips.com/spiritnow/story/value-curve-horseshoe-wells-expand-development-options/", "locator": "Design and rationale paragraphs; paragraphs describing two projects/four wells, capital savings, $10-$15/BOE cost-of-supply estimate, production/tracer result, and evaluation outside Eagle Ford.", "access": "Issuer HTML opened directly", "supports": "Physical design, initial deployment scope, claimed economic comparisons, production status and still-evaluative expansion status." } ], "references": [], "review": { "verdict": "confirmed", "reason": "The source describes the design, projects, tracer result and estimate directly. There is no evidence of AI involvement; classify as physical well architecture, while avoiding claims about absence of AI in the wider workflow.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R02-US-01", "verdict": "confirmed", "patch": { "claim": "ConocoPhillips describes an Eagle Ford horseshoe-well design that joins two laterals in one drilling event. The issuer estimates $10-$15/BOE lower cost of supply versus traditional designs; test-well tracer evidence indicated production contribution along the wellbore. Broader application remains under evaluation.", "economics": "Label $10-$15/BOE as an issuer estimate, not realized project cost savings or a disclosed AFE amount; single-project test results do not establish repeatability." }, "reason": "The source describes the design, projects, tracer result and estimate directly. There is no evidence of AI involvement; classify as physical well architecture, while avoiding claims about absence of AI in the wider workflow.", "recommended_disposition": "include_physical_engineering_example", "sources_inspected": [ { "url": "https://www.conocophillips.com/spiritnow/story/value-curve-horseshoe-wells-expand-development-options/", "access": "Issuer HTML opened directly", "locator": "Paragraphs on estimated cost of supply and tracer result, lines 52-77." } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R02-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R13-US-01", "company": "ConocoPhillips", "title": "Lower 48 productivity per foot improved in 2025 as lateral length and completion-design optimization advanced", "category": "Completion design and reservoir development", "kind": "update", "ai_role": "No AI contribution is identified. Management describes ongoing basin development optimization and the use of diverters in Eagle Ford completion designs; no model or automation is named.", "asset": "ConocoPhillips Lower 48 portfolio, with named results in Delaware Basin and Eagle Ford; Eagle Ford includes Marathon-acquired acreage, now integrated into the program.", "stage": "Operating portfolio results for 2025 reported on 2026-02-05; ongoing design optimization.", "operating_period": "Calendar year 2025; disclosed during Q4 2025 earnings call on 2026-02-05.", "claim": "Preserve the year-over-year per-foot results as basin-level portfolio observations: Delaware oil productivity per foot +about 8% while average lateral length +9%; Eagle Ford oil productivity per foot +7%. Management cited Delaware spacing/stacking optimization and Eagle Ford diverter use, but also emphasized acreage quality, basin mix and inventory; the sources do not isolate a causal technology contribution or give dollar/recovery results.", "economics": "No dollar savings, well cost, incremental recovery volume or technology-specific return was disclosed. The 2026 Lower 48 capital reduction outlook is a forward plan and cannot be assigned to diverters or the productivity figures alone.", "baseline": "Management compares 2025 to 2024 basin oil productivity per foot; the transcript does not provide cohort construction, lateral-length adjustment methodology, well count, geological mix, or a matched non-diverter comparison.", "limits": "The Delaware result includes a 9% increase in average lateral length and management explicitly cites inventory quality, spacing/stacking and geographic mix as drivers. Eagle Ford productivity is a basin metric; diverter use is mentioned but not quantified or isolated. Do not infer a causal effect or convert productivity-per-foot gains into EUR or value without well-level data.", "relationship": "This is not the same well design as T10-R02-US-01 (Eagle Ford horseshoe-well pilot): it is a basin-level productivity update and describes diverters/spacing rather than the U-shaped two-lateral well architecture. Avoid combining these results without well-level linkage.", "decision_question": "Can ConocoPhillips provide basin-level matched cohorts that separate lateral-length, rock/location, diverter and spacing effects and connect each to D&C cost and full-cycle recovery?", "company_key": "ConocoPhillips", "run": "Rounds 11–20", "disposition": "background", "sources": [ { "title": "Q4 2025 ConocoPhillips Earnings Call Transcript", "publisher": "ConocoPhillips / LSEG transcript hosted on ConocoPhillips domain", "date": "2026-02-05", "url": "https://static.conocophillips.com/files/resources/cop-usq_transcript_2026-02-05.pdf", "locator": "PDF pp. 7–8; transcript lines 240–262. Management's answer on basin performance, lateral lengths, spacing/stacking and diverter completion designs.", "access": "Directly opened issuer-hosted PDF; relevant Q&A passage inspected.", "supports": "2025 Delaware +8% oil productivity/ft with +9% average lateral length; Eagle Ford +7% productivity/ft and management's mention of diverters; does not establish causal attribution." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Issuer-hosted Q4 2025 transcript directly confirms the reported percentages and practices. Keep actual 2025 basin performance separate from technology attribution: management explicitly mentions asset quality and mix, and no well cohort/control or cost bridge is disclosed. Existing wording is broadly sound; patch clarifies causal and mix boundaries.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R13-US-01", "verdict": "confirmed", "patch": { "claim": "Preserve the year-over-year per-foot results as basin-level portfolio observations: Delaware oil productivity per foot +about 8% while average lateral length +9%; Eagle Ford oil productivity per foot +7%. Management cited Delaware spacing/stacking optimization and Eagle Ford diverter use, but also emphasized acreage quality, basin mix and inventory; the sources do not isolate a causal technology contribution or give dollar/recovery results." }, "reason": "Issuer-hosted Q4 2025 transcript directly confirms the reported percentages and practices. Keep actual 2025 basin performance separate from technology attribution: management explicitly mentions asset quality and mix, and no well cohort/control or cost bridge is disclosed. Existing wording is broadly sound; patch clarifies causal and mix boundaries.", "sources_inspected": [ { "url": "https://static.conocophillips.com/files/resources/cop-usq_transcript_2026-02-05.pdf", "access": "Issuer-hosted transcript opened directly in cross-audit", "locator": "PDF page 7, lines 240–257; page 8 continues Eagle Ford completion discussion.", "date": "2026-02-05" } ], "recommended_disposition": "background" } ] }, "department": "Drilling & completions", "group_id": "T20-R13-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Calendar year 2025; disclosed during Q4 2025 earnings call on 2026-02-05." }, { "id": "TECH-02", "company": "ConocoPhillips", "title": "PD 868 modular robotic pipe handling in Montney", "category": "rig-floor robotics / drilling automation", "kind": "new_initiative", "ai_role": "non-AI robotics and programmed automation; image-based spatial recognition is described as a future goal", "asset": "Not disclosed", "stage": "One named land rig, PD 868, with use across several recent pads under a three-year Precision Drilling collaboration; not fleet-wide. Coordinates are currently manually programmed.", "operating_period": "2025-06-18", "claim": "Source confirms 105,000 m drilled without manual connections, 400,000 m tubulars handled hands-free, and ~8,400 rig-floor personnel hours eliminated.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Issuer case story; metrics are company-reported and the footprint is one named rig / several pads. No independent validation or cost conversion disclosed.", "relationship": "A named modular rig-floor robot changes physical work execution. Report hours/tasks at stated pad scope; separate future vision recognition from presently programmed automation and do not convert labor-hours into cash.", "decision_question": "How many tasks/wells/rig-days are represented, what time-at-risk or injury rate changed, and what incremental rig cost offsets ~8,400 personnel hours removed?", "company_key": "ConocoPhillips", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Enhancing safety and efficiency / Montney’s automated drilling rig", "publisher": "ConocoPhillips", "date": "2025-06-18", "url": "https://www.conocophillips.com/spiritnow/story/enhancing-safety-and-efficiency-montneys-automated-drilling-rig/", "locator": "Fast facts and technology/deployment description", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-06-18", "url": "https://www.conocophillips.com/spiritnow/story/enhancing-safety-and-efficiency-montneys-automated-drilling-rig/", "locator": "Published 2025-06-18; lines 39-50, PD 868 scope, outcome counts, programming approach and future vision goal", "access": "Issuer page opened; fast facts and deployment text reviewed", "supports": "All three headline counts and deployment boundary are confirmed. Distinguish conventional programmed robotics from future image recognition and avoid converting labor hours to cash without evidence." } ], "references": [ { "id": "AI-090", "relationship": "company_context" }, { "id": "AI-202", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "TECH-02", "core_company": true, "ai_ids": [ "AI-090", "AI-202" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025-06-18" }, { "id": "R1-LIM-04", "company": "ExxonMobil", "title": "Baytown low-carbon hydrogen plant with CCS paused; separate methane-pyrolysis demonstration remains planned", "category": "Integrated industrial/downstream-adjacent context only; not an upstream operating-tech case.", "kind": "context", "ai_role": "No AI role. The case is relevant to AI energy demand only if surfaced as a separate adjacent opportunity; it should not be counted as an AI deployment or AI-powered energy asset.", "asset": "Baytown integrated refining/chemical complex, Texas. Hydrocarbon feedstock and CO2 transport/storage link the proposal to the natural-gas value chain; it is not an upstream producing-asset deployment.", "stage": "Main low-carbon hydrogen development paused in 2025 pending market/policy conditions. Different technology, methane-pyrolysis demonstration is planned, not operating in the source. Baytown hydrogen burners have been installed/tested as a separate operating technology; this does not unpause the low-carbon hydrogen plant.", "operating_period": "Pause announced in 2025; source is ExxonMobil Advancing Climate Solutions report, published May 2026. Pre-pause figures sourced from ExxonMobil’s 2024-12-11 2030 plan; current report clarifies status.", "claim": "The main Baytown project did not proceed to investment/deployment because management judged market and policy insufficient to justify continued investment. No project capex, expected return, or sunk cost was disclosed in the source reviewed. ExxonMobil continues to engage customers/policymakers. Separate technology tests/plans should not be treated as substitutes already scaled.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Issuer explanation; no third-party economic analysis or customer offtake status disclosed in the source. The report uses corporate promotional language for remaining technologies. The potential 90% burner emissions reduction is a reported test result with no test duration, baseline conditions, or scale detail visible in the cited passage. This is a market/policy pause, not proof of technical failure of hydrogen or CCS.", "relationship": "Downstream Baytown project pause is useful only as a market/policy gate; the separate methane-pyrolysis demonstration is planned. Too far from upstream operating-tech core for feature treatment.", "decision_question": "What hydrogen offtake price/utilization, CCS capex and policy support would clear Exxon’s investment hurdle, and are burner/pyrolysis economics distinct?", "company_key": "ExxonMobil", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "2026 Advancing Climate Solutions Report", "publisher": "ExxonMobil", "date": "2026-05", "url": "https://corporate.exxonmobil.com/-/media/global/files/advancing-climate-solutions/2026/2026-advancing-climate-solutions-report.pdf", "locator": "PDF p. 19 / printed page 19: Baytown hydrogen pause and policy/market explanation; p. 19–20: burner test and separate methane-pyrolysis demo plan.", "access": "Opened; issuer report", "supports": "Pause rationale and current state; distinct burner test result and planned alternative demonstration." }, { "title": "ExxonMobil announces plans to 2030 that build on its unique advantages", "publisher": "ExxonMobil", "date": "2024-12-11", "url": "https://corporate.exxonmobil.com/news/news-releases/2024/1211_exxonmobil-announces-plans-to-2030-that-build-on-its-unique-advantages", "locator": "Baytown project pre-pause scale, 98% CO2 capture ambition and prior expected FID/startup timing.", "access": "Opened via indexed issuer material; context source", "supports": "Prior announced scale/ambition only; superseded by the 2025 pause and not a current schedule." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-05", "url": "https://corporate.exxonmobil.com/-/media/global/files/advancing-climate-solutions/2026/2026-advancing-climate-solutions-report.pdf", "locator": "PDF pp.5 and 18; lines 248–254 and 1168–1207.", "access": "issuer PDF opened", "supports": "Issuer report distinguishes the pause reason and continuing separate technology work. Good evidence of market/economics gating, poor fit for upstream technology deployment." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2024-12-11", "url": "https://corporate.exxonmobil.com/news/news-releases/2024/1211_exxonmobil-announces-plans-to-2030-that-build-on-its-unique-advantages", "locator": "Earlier plan for Baytown low-carbon hydrogen/CCS.", "access": "issuer source referenced in original record; not needed to establish current pause", "supports": "Issuer report distinguishes the pause reason and continuing separate technology work. Good evidence of market/economics gating, poor fit for upstream technology deployment." } ], "references": [ { "id": "AI-023", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "R1-LIM-04", "core_company": true, "ai_ids": [ "AI-023" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R04-US-01", "company": "ExxonMobil", "title": "Pneumatic-device replacement at acquired Pioneer Permian assets", "category": "methane mitigation / process-control hardware retrofit", "kind": "update", "ai_role": "Physical equipment/process retrofit: replacing natural-gas-driven pneumatic controls with alternatives such as air compressors, mechanical valves, electricity or nitrogen depending on site conditions. The source does not describe AI as part of the device-replacement action.", "asset": "Acquired Pioneer unconventional assets in ExxonMobil's Permian Basin operations; distinct from the company's legacy ExxonMobil assets where pneumatic devices had already been eliminated.", "stage": "More than 6,000 devices reported replaced during 2025; company goal is elimination of pneumatic devices across integrated Permian operations by 2030.", "operating_period": "2025 deployment, disclosed 2026-05-05.", "claim": "ExxonMobil says it replaced more than 6,000 pneumatic devices in acquired Pioneer Permian assets during 2025; this is part of a broader effort to remove natural-gas-driven pneumatic devices, with integrated Permian completion targeted by 2030.", "economics": "No methane volume avoided, retrofit cost, maintenance effect, or payback is reported here; do not imply measured emissions reduction for this subset.", "baseline": "Natural-gas-driven pneumatic controls are the qualitative baseline. The source does not state the Pioneer device inventory at the start of 2025, fraction of eligible devices replaced, pre/post measured methane emissions, or a matched-site comparison. The >10,000 companywide since-2023 figure has a broader scope than the 6,000 Pioneer-only 2025 figure.", "limits": "Issuer sustainability reporting. Replacement count is a deployment output, not measured methane reduction or a completed integrated-Permian program. Retrofit scope and solution mix vary by site; infrastructure replacement may have ancillary reliability benefits, but no quantified uptime/repair result is given. Do not infer compliance, economics or methane reduction from count alone.", "relationship": "Adds a dated and quantified physical methane-control retrofit absent from reviewed starter records, distinct from EOG's leak-detection coverage (R1-US-06), which detects emissions rather than preventing pneumatic venting at source.", "decision_question": "For the 6,000 Pioneer replacements, what were eligible inventory, replacement mix and capex, and what did direct before/after measurement show for methane mass, vented-gas sales, reliability and maintenance by device class?", "company_key": "ExxonMobil", "run": "Rounds 1–10", "disposition": "include_physical_methane_mitigation_example", "sources": [ { "title": "Driving reductions in methane emissions", "publisher": "ExxonMobil, Advancing Climate Solutions 2026", "date": "2026-05-05", "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "locator": "Sections 'What we've done / What we're doing' lines 78-87 and 'Replacing pneumatic devices' lines 111-120.", "access": "Issuer HTML opened directly", "supports": "Pioneer replacement count, 2025 operating year, integrated Permian 2030 target, physical substitute types and no-one-size-fits-all implementation constraint." } ], "references": [], "review": { "verdict": "confirmed", "reason": "The issuer states replacement count and date and outlines varied substitute mechanisms depending on power/access. The page supports mitigation equipment, not monitoring or AI. Its 10,000+ since-2023 total covers a broader set and must not be added to the Pioneer count.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R04-US-01", "verdict": "confirmed", "patch": { "claim": "ExxonMobil says it replaced more than 6,000 pneumatic devices in acquired Pioneer Permian assets during 2025; this is part of a broader effort to remove natural-gas-driven pneumatic devices, with integrated Permian completion targeted by 2030.", "economics": "No methane volume avoided, retrofit cost, maintenance effect, or payback is reported here; do not imply measured emissions reduction for this subset." }, "reason": "The issuer states replacement count and date and outlines varied substitute mechanisms depending on power/access. The page supports mitigation equipment, not monitoring or AI. Its 10,000+ since-2023 total covers a broader set and must not be added to the Pioneer count.", "recommended_disposition": "include_physical_methane_mitigation_example", "sources_inspected": [ { "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "access": "Issuer HTML opened directly", "locator": "'Replacing pneumatic devices,' lines 111-120; summary lines 85-88." } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 deployment, disclosed 2026-05-05." }, { "id": "T20-R15-US-01", "company": "ExxonMobil", "title": "Methane monitoring and Vantage operating outcomes update: coverage, flaring and response denominators remain incomplete", "category": "Methane sensing and field-response operations", "kind": "update", "ai_role": "Exxon describes continuous analysis and a centralized monitoring center but does not disclose whether AI/ML generates or prioritizes methane alerts, nor its role in repair decisions. Do not call the measurement/control loop AI without more detail.", "asset": "ExxonMobil-operated Permian upstream sites: continuous monitoring deployed at >400 heritage ExxonMobil key sites; monitoring at acquired Pioneer key sites is planned by end-2026. Vantage describes wider U.S. upstream scope.", "stage": "Vantage was unveiled in October 2025 and extends the COMET platform launched in 2022. Heritage operated Permian continuous-monitoring coverage exceeds 400 key sites; deployment to acquired Pioneer key sites is targeted by end-2026. More than 6,000 pneumatic-device replacements on acquired Pioneer Permian assets were reported for 2025.", "operating_period": "Company-reported results cover 2024–2025; disclosure dated 2026-05-05.", "claim": "Exxon says Vantage/COMET provides continuous methane monitoring and real-time monitoring/production management. Its May 2026 page reports more than 400 continuous-monitoring sites on heritage ExxonMobil-operated Permian assets, and separately says more than 6,000 pneumatic devices were replaced in 2025 at acquired Pioneer Permian assets. Vantage’s 2024–2025 operating highlights include >34 MMcf of flaring eliminated and >18,000 driving hours avoided; source gives no project-level counterfactual or cost attribution. The >60% methane-intensity reduction is company-wide operated-asset performance from 2016–2025, not a Vantage result.", "economics": "No monitoring-system cost, device-replacement cost, value per recovered gas volume, alert response labor, repair cost, avoided loss or payback disclosed. Flared-gas volume and travel hours are operational outputs and should not be monetized without additional assumptions.", "baseline": "Keep separate: company-wide methane-intensity baseline is 2016; Vantage flaring/driving outputs cover 2024–2025; monitoring count covers heritage sites; Pioneer replacement count covers acquired Pioneer assets in 2025.", "limits": "The source does not report alert count, source confirmation, false alarms, time-to-acknowledge, time-to-repair, closure evidence, leak volume before/after, repair success, or attribution of the 34 MMcf flaring figure specifically to Vantage alerts. It describes a monitoring layer and associated field operations but leaves the detection-to-repair chain unquantified. The 2026 report notes uncertainty in measured/estimated emissions and methodology.", "relationship": "Enrich existing Vantage / Permian operations coverage AI-022 and prior observation T10-R05-US-01. The same issuer page is a source for that record, so this is a 2026 follow-up with additional numbers and explicit measurement limits, not a new program count.", "decision_question": "For continuous-monitoring sites, how many confirmed alerts resulted in a documented repair and emissions reduction, over what time window, versus a manual-LDAR counterfactual, including false-positive and monitoring/field-response costs?", "company_key": "ExxonMobil", "run": "Rounds 11–20", "disposition": "enrich_existing", "sources": [ { "title": "Driving reductions in methane emissions", "publisher": "ExxonMobil, Advancing Climate Solutions 2026", "date": "2026-05-05", "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "locator": "Lines 82–88 (monitoring/device scope), 124–146 (detection, Vantage and reported outputs), 249–259 (measurement boundary/uncertainty).", "access": "Directly opened primary issuer page; relevant passages and footnotes inspected.", "supports": "Monitoring scope, planned Pioneer rollout, 2025 device replacements, 2024–25 flare/travel outcomes, and uncertainty/baseline boundaries." } ], "references": [ { "id": "AI-022", "relationship": "Enrich existing Vantage / Permian operations coverage AI-022 and prior observation T10-R05-US-01. The same issuer page is a source for that record, so this is a 2026 follow-up with additional numbers and explicit measurement limits, not a new program count." } ], "review": { "verdict": "correct", "reason": "The directly reopened Exxon page confirms Vantage/COMET chronology and output metrics, and the methane overview confirms the different site/device populations. The original wording's 'Permian operations' for >6,000 replacements is too broad because the primary page locates these on acquired Pioneer assets. The broad intensity result is properly not attributed to Vantage. Same program as canonical AI-022; this is enrichment, not a new AI count. No $ value or cost bridge disclosed.", "cross_audits": [ { "assignment": "round-20-global.json", "finding_id": "T20-R15-US-01", "verdict": "correct", "patch": { "claim": "Exxon says Vantage/COMET provides continuous methane monitoring and real-time monitoring/production management. Its May 2026 page reports more than 400 continuous-monitoring sites on heritage ExxonMobil-operated Permian assets, and separately says more than 6,000 pneumatic devices were replaced in 2025 at acquired Pioneer Permian assets. Vantage’s 2024–2025 operating highlights include >34 MMcf of flaring eliminated and >18,000 driving hours avoided; source gives no project-level counterfactual or cost attribution. The >60% methane-intensity reduction is company-wide operated-asset performance from 2016–2025, not a Vantage result.", "stage": "Vantage was unveiled in October 2025 and extends the COMET platform launched in 2022. Heritage operated Permian continuous-monitoring coverage exceeds 400 key sites; deployment to acquired Pioneer key sites is targeted by end-2026. More than 6,000 pneumatic-device replacements on acquired Pioneer Permian assets were reported for 2025.", "baseline": "Keep separate: company-wide methane-intensity baseline is 2016; Vantage flaring/driving outputs cover 2024–2025; monitoring count covers heritage sites; Pioneer replacement count covers acquired Pioneer assets in 2025." }, "reason": "The directly reopened Exxon page confirms Vantage/COMET chronology and output metrics, and the methane overview confirms the different site/device populations. The original wording's 'Permian operations' for >6,000 replacements is too broad because the primary page locates these on acquired Pioneer assets. The broad intensity result is properly not attributed to Vantage. Same program as canonical AI-022; this is enrichment, not a new AI count. No $ value or cost bridge disclosed.", "sources_inspected": [ { "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "access": "Issuer HTML opened directly in cross-audit", "locator": "Page dated May 5, 2026; lines 52–54, 134–153 (Vantage, outputs and limitations); lines 82–87 (heritage vs Pioneer asset/device boundaries).", "date": "2026-05-05" } ], "recommended_disposition": "enrich_existing" } ] }, "department": "Water, emissions & energy", "group_id": "T10-R05-US-01", "core_company": true, "ai_ids": [ "AI-022" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Company-reported results cover 2024–2025; disclosure dated 2026-05-05." }, { "id": "T10-R05-US-01", "company": "ExxonMobil", "title": "Vantage central operations and monitoring center at reported 22,000-site U.S. upstream scale", "category": "remote operations / monitoring, sensing and production response", "kind": "update", "ai_role": "Vantage integrates real-time monitoring and production management; the 2025 launch article does not disclose whether AI/ML determines alerts or actions, nor the degree of automated control. COMET is named as a monitoring platform; do not infer autonomous closed-loop operation from the article's future-state language.", "asset": "U.S. upstream operations across regions including the Permian, Denbury and Bakken. Issuer says >22,000 sites are monitored, >1 million b/d managed/optimized, >3 million b/d water managed/optimized and >3 Bcf/d gas monitored/directed daily.", "stage": "Vantage publicly unveiled 2025-10-10; operating 24/7 by announcement. COMET pre-existed, launched in 2022; Vantage is an expanded/renamed operating-center initiative rather than a platform developed wholly in 2025.", "operating_period": "The platform is described as operating as of 2025-10. Flaring reduction and driving-avoidance figures are explicitly for calendar 2024; uplift period is not specified.", "claim": "Vantage is reported to monitor >22,000 sites; it manages/optimizes >1 million b/d oil and >3 million b/d water, monitors/directs >3 Bcf/d gas, and reports >29,000 b/d oil uplift from field and remote production-optimization activities. Separate 2024 metrics include >20 MMcf flaring eliminated and >6,000 driving hours avoided.", "economics": "The company-reported production-uplift figure could be material, but the page gives no duration, gross/net basis, persistence, decline convention, commodity mix, intervention/capital cost or cash margin. The 2024 flaring/driving figures are distinct operational outputs and should not be monetized without fuel, emissions and response-cost baselines.", "baseline": "No pre-Vantage/control baseline or counterfactual is specified for the >29,000-b/d uplift. Vantage was unveiled in 2025 but the uplift is attributed to field and remote production optimization activities, not clearly solely to the center. Page says 22,000 sites; a later 2026 report uses 'wells' for a similar-scale coverage figure, so retain the 2025 source's unit rather than silently converting sites to wells.", "limits": "Issuer disclosure does not specify site-versus-well denominator, eligible population, matched baseline, attribution to AI versus remote/field operations, or whether the stated uplift is sustained; keep these as issuer-reported scale/outcome claims.", "relationship": "This is an update/context to canonical production record AI-022 (ExxonMobil Permian and operating-site AI); root confirms relevant source overlap. Do not add a net-new AI initiative count.", "decision_question": "How much of the 29,000-b/d uplift is durable incremental production attributable to Vantage-enabled interventions, over what measured period and well population, and what staffing, sensor, integration and field-response costs were required?", "company_key": "ExxonMobil", "run": "Rounds 1–10", "disposition": "update_AI_022_context_not_new_record", "sources": [ { "title": "Introducing Vantage: A new lens on upstream operations", "publisher": "ExxonMobil", "date": "2025-10-10", "url": "https://corporate.exxonmobil.com/who-we-are/our-global-organization/business-divisions/upstream/a-new-lens-on-upstream-operations", "locator": "Vantage overview and 'Big numbers, bigger impact,' lines 34-64.", "access": "Issuer HTML opened directly", "supports": "Launch/disclosure date, monitoring-center function, reported scale, 2024 flaring and driving outcomes, and attributed field/remote optimization production uplift." }, { "title": "Driving reductions in methane emissions", "publisher": "ExxonMobil, Advancing Climate Solutions 2026", "date": "2026-05-05", "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "locator": "Monitoring and detection section lines 124-146; near-continuous monitoring roll-out boundary lines 127-130.", "access": "Issuer HTML opened directly", "supports": "Monitoring technology layers, deployment still in progress for acquired Pioneer sites, and Vantage linkage to real-time upstream methane monitoring." } ], "references": [ { "id": "AI-022", "relationship": "This is an update/context to canonical production record AI-022 (ExxonMobil Permian and operating-site AI); root confirms relevant source overlap. Do not add a net-new AI initiative count." } ], "review": { "verdict": "correct", "reason": "The direct Vantage page reports all numbers in the same overview, while the methane page distinguishes monitoring technologies and ongoing rollout. This broad operations-center result is not an AI-only ROI claim.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R05-US-01", "verdict": "correct", "patch": { "relationship": "This is an update/context to canonical production record AI-022 (ExxonMobil Permian and operating-site AI); root confirms relevant source overlap. Do not add a net-new AI initiative count.", "claim": "Vantage is reported to monitor >22,000 sites; it manages/optimizes >1 million b/d oil and >3 million b/d water, monitors/directs >3 Bcf/d gas, and reports >29,000 b/d oil uplift from field and remote production-optimization activities. Separate 2024 metrics include >20 MMcf flaring eliminated and >6,000 driving hours avoided.", "limits": "Issuer disclosure does not specify site-versus-well denominator, eligible population, matched baseline, attribution to AI versus remote/field operations, or whether the stated uplift is sustained; keep these as issuer-reported scale/outcome claims." }, "reason": "The direct Vantage page reports all numbers in the same overview, while the methane page distinguishes monitoring technologies and ongoing rollout. This broad operations-center result is not an AI-only ROI claim.", "recommended_disposition": "update_AI_022_context_not_new_record", "sources_inspected": [ { "url": "https://corporate.exxonmobil.com/who-we-are/our-global-organization/business-divisions/upstream/a-new-lens-on-upstream-operations", "access": "Issuer HTML opened directly", "locator": "'Big numbers, bigger impact,' lines 54-64." }, { "url": "https://corporate.exxonmobil.com/publications/advancing-climate-solutions/driving-reductions-in-methane-emissions", "access": "Issuer HTML opened directly", "locator": "Monitoring deployment context, lines 124-146." } ] } ] }, "department": "Production & process operations", "group_id": "T10-R05-US-01", "core_company": true, "ai_ids": [ "AI-022" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "TECH-01", "company": "ExxonMobil", "title": "Proprietary lightweight proppant", "category": "completion-material innovation / recovery", "kind": "new_initiative", "ai_role": "Physical completion-material technology; no AI contribution is disclosed.", "asset": "Not disclosed", "stage": "Technology is in use in the Permian; issuer reports early results but gives no well count or deployment coverage.", "operating_period": "2025-12-09", "claim": "Issuer reports early results showing about 20% recovery improvement from proprietary lightweight proppant technology alone.", "economics": "Not disclosed", "baseline": "No well count, deployment share, comparator/baseline definition, measurement period, cost, or independent validation disclosed. No denominator or dollar bridge should be inferred.", "limits": "Issuer-reported early result; no denominator, baseline definition, time period, independent comparison, or deployment count disclosed.", "relationship": "Strong counterexample to AI-only framing: physical completion material with early issuer-reported ~20% recovery improvement. Keep the unreported denominator, comparator, period and economics prominent.", "decision_question": "What is the recovery uplift denominator, control population, production period, cost/ton proppant premium and net PV per well behind the early ~20% claim?", "company_key": "ExxonMobil", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "ExxonMobil raises its 2030 Plan – transformation delivering higher earnings, stronger cash flow, and greater returns", "publisher": "ExxonMobil", "date": "2025-12-09", "url": "https://corporate.exxonmobil.com/news/news-releases/2025/1209-exxonmobil-raises-2030-plan-transformation", "locator": "Upstream section, lines 64-69", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-12-09", "url": "https://corporate.exxonmobil.com/news/news-releases/2025/1209-exxonmobil-raises-2030-plan-transformation", "locator": "Upstream paragraph, lines 64–69.", "access": "issuer HTML opened", "supports": "This is the best concise counterexample to an AI-only framing because it links a physical material to a potentially material recovery KPI. Evidence is issuer-reported early result with thin technical detail." } ], "references": [ { "id": "AI-022", "relationship": "company_context" }, { "id": "AI-235", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "TECH-01", "core_company": true, "ai_ids": [ "AI-022", "AI-235" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025-12-09" }, { "id": "TECH-06", "company": "ExxonMobil", "title": "Open Subsurface Data Universe (OSDU) Data Platform", "category": "internal subsurface software and data operating model", "kind": "context", "ai_role": "OSDU is an open subsurface data foundation. AI is mentioned generically as a potential/associated application, not as the cause of the qualitative evaluation-time claim.", "asset": "Not disclosed", "stage": "Issuer describes current platform work and a qualitative reported evaluation-time benefit; broader/full operational capability remains in progress.", "operating_period": "2026-07-10", "claim": "Evaluation times were said to be dramatically shortened, but no delta, denominator, or independent validation was provided.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Issuer-reported qualitative outcome, without before/after times, asset counts or independent validation. Do not attribute it to AI.", "relationship": "OSDU is a foundation/architecture item, not AI and not an outcome. Describe in a stack map or account context only; no source proves the exact same-project link to any existing AI record.", "decision_question": "What evaluation-time delta, assets/projects evaluated, data-engineering cost and resulting decision quality/value are attributable to OSDU?", "company_key": "ExxonMobil", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "Unleashing the power of open data", "publisher": "ExxonMobil", "date": "2026-07-10", "url": "https://corporate.exxonmobil.com/locations/asia-pacific-region/ap-newsroom/2026/unleashing-the-power-of-open-data", "locator": "Guyana link and ‘Real-world wins’", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-07-10", "url": "https://corporate.exxonmobil.com/locations/asia-pacific-region/ap-newsroom/2026/unleashing-the-power-of-open-data", "locator": "OSDU platform and Guyana examples; qualitative evaluation-time statement; future fully-operational language", "access": "ExxonMobil issuer page opened; text accessible", "supports": "The source supports a data-foundation capability and qualitative workflow claim, not a quantified AI result. Existing Exxon account context already covers the enterprise data foundation, so this is enrichment rather than a new register item." } ], "references": [ { "id": "AI-072", "relationship": "company_context" }, { "id": "AI-073", "relationship": "company_context" } ], "department": "Data, people & purchasing", "group_id": "TECH-06", "core_company": true, "ai_ids": [ "AI-072", "AI-073" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "2026-07-10" }, { "id": "T10-R03-US-01", "company": "Occidental Petroleum (Oxy)", "title": "Horn Mountain gas-lift and caisson ESP projects implemented under Gulf of America 2.0", "category": "offshore artificial lift / production recovery", "kind": "new_initiative", "ai_role": "No AI role disclosed. The named interventions are down-hole gas-lift and caisson electric submersible pumps; no-AI disclosure is not proof that no digital tools were used.", "asset": "Horn Mountain platform in the Gulf of America; Oxy also reports 2025 portfolio production of 132 Mboe/d from 96 gross wells across its Gulf of America assets.", "stage": "Implemented at Horn Mountain during 2025; water-injection projects elsewhere in the GOA 2.0 program were planned for 2026/2027 and are separate.", "operating_period": "Implemented during 2025; disclosed in Oxy FY2025 Form 10-K filed in 2026.", "claim": "Oxy says the Horn Mountain gas-lift and caisson ESP projects delivered some of the highest-margin production in its portfolio. In the same discussion it reports Gulf of America production and major-equipment uptime, but does not attribute either metric to the artificial-lift projects.", "economics": "No project capital or standalone uplift quantified. Phrase 'some of the highest-margin production' as management's qualitative portfolio comparison, not a measured lift-project margin or return.", "baseline": "No pre-project production, lift method, cost or margin baseline disclosed. Portfolio production (132 Mboe/d) and equipment uptime (>99%) are context only and should not be treated as project-level uplift.", "limits": "The source names multiple projects but does not count individual installations/wells, define 'highest margin' comparator, or isolate project contribution. Reported 96 gross wells are across eight platforms and 14 active fields, not an eligible lift-project denominator. Water injection dates are plans at filing, not completed outcomes.", "relationship": "New physical upstream technology example, distinct from Oxy TECH-04 water recycling and from route-optimization AI. Appropriate in a production-technology section only with the absent project economics visible.", "decision_question": "What were the project-level incremental oil volumes, margin, lift/intervention capex, operating cost and pre-project decline profile for each Horn Mountain installation, and have Marlin/Horn Mountain injection milestones actually started?", "company_key": "Occidental", "run": "Rounds 1–10", "disposition": "include_physical_production_example_with_economics_unknown", "sources": [ { "title": "Oxy 2025 Form 10-K / Annual Report", "publisher": "Occidental Petroleum", "date": "2026-02-19", "url": "https://www.oxy.com/siteassets/documents/investors/2025-annual-report.pdf", "locator": "Management's Discussion and Analysis, Gulf of America, PDF pp. 33-34 (printed pp. 26-27), lines 1473-1497.", "access": "Issuer-hosted PDF opened directly", "supports": "2025 Horn Mountain gas-lift and caisson ESP implementations, qualitative margin description, asset-wide production/uptime context and separate future injection plans." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Oxy's 2025 10-K names downhole gas-lift and caisson ESP installations at Horn Mountain and separates future water injection. The fact supports a physical-production example with no individual project ROI.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R03-US-01", "verdict": "confirmed", "patch": { "economics": "No project capital or standalone uplift quantified. Phrase 'some of the highest-margin production' as management's qualitative portfolio comparison, not a measured lift-project margin or return.", "stage": "Implemented at Horn Mountain during 2025; water-injection projects elsewhere in the GOA 2.0 program were planned for 2026/2027 and are separate." }, "reason": "Oxy's 2025 10-K names downhole gas-lift and caisson ESP installations at Horn Mountain and separates future water injection. The fact supports a physical-production example with no individual project ROI.", "recommended_disposition": "include_physical_production_example_with_economics_unknown", "sources_inspected": [ { "url": "https://www.oxy.com/siteassets/documents/investors/2025-annual-report.pdf", "access": "Issuer-hosted 10-K PDF opened directly", "locator": "Printed pp. 26-27 / PDF pp. 33-34, lines 1484-1497." } ] } ] }, "department": "Production & process operations", "group_id": "T10-R03-US-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Implemented during 2025; disclosed in Oxy FY2025 Form 10-K filed in 2026." }, { "id": "T10-R03-US-02", "company": "Occidental Petroleum (Oxy)", "title": "Oman Block 53 artificial-lift improvement associated with lower workover-rig cost per barrel", "category": "artificial lift / production reliability and workover efficiency", "kind": "update", "ai_role": "No AI or specific lift technology disclosed; issuer management describes performance improvement, not its technical mechanism.", "asset": "Oxy-operated Oman Block 53 (Mukhaizna Field); executive cited 3,500 operated wells during the Q1 2025 call. This is distinct from the Gulf of America lift projects.", "stage": "Operating performance trend over a three-year period; disclosed in May 2025.", "operating_period": "The three years preceding 2025-05-08; exact start/end dates and annual trajectory not provided.", "claim": "Oxy management reported that Block 53 drilling cost per foot and workover-rig cost per barrel each fell 50% over the prior three years, while saying artificial-lift performance had improved significantly. This is block-level operating context; the source does not isolate the lift technology's contribution to the workover-rig cost change.", "economics": "No AI/hardware-specific cost attribution or absolute $/bbl disclosed.", "baseline": "Three years before the May 8, 2025 call; exact start/end dates and absolute costs undisclosed.", "limits": "Management-call attribution only; no specific lift equipment/process change or operational dataset is cited. Cost per barrel may change with barrel denominator as well as rig cost. Do not conflate with adjacent drilling-cost-per-foot claim or claim improved recovery without production data.", "relationship": "New issuer-reported operating KPI in an asset not represented by Oxy TECH-04. It is an update/performance disclosure, not a named hardware launch; keep in a separate evidence row from Horn Mountain offshore hardware.", "decision_question": "Was the 50% change driven by longer pump run-life, fewer interventions, lower rig day rates, more barrels per workover, or another factor—and what were annual absolute costs and production-adjusted denominators?", "company_key": "Occidental", "run": "Rounds 1–10", "disposition": "background_or_operator_performance_context", "sources": [ { "title": "Q1 2025 Occidental Petroleum Corp Earnings Call Transcript", "publisher": "Occidental Petroleum / LSEG Refinitiv transcript hosted by Oxy", "date": "2025-05-08", "url": "https://www.oxy.com/siteassets/documents/investors/quarterly-earnings/oxy1q25transcript.pdf", "locator": "PDF p. 9, remarks by Kenneth Dillon, SVP and President, International Oil and Gas Operations, lines 317-330.", "access": "Issuer-hosted transcript PDF opened directly", "supports": "Block 53 operated-well context, 50% three-year workover-rig cost-per-barrel statement, distinct drilling-cost claim and ongoing CO2 EOR pilot without quantified recovery result." } ], "references": [], "review": { "verdict": "correct", "reason": "The exact transcript passage places the artificial-lift statement next to, but does not quantify causal attribution for, the 50% workover-rig cost/bbl decline. Keep the full Block 53 3,500-well context and avoid attributing all savings to lift performance.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R03-US-02", "verdict": "correct", "patch": { "claim": "Oxy management reported that Block 53 drilling cost per foot and workover-rig cost per barrel each fell 50% over the prior three years, while saying artificial-lift performance had improved significantly. This is block-level operating context; the source does not isolate the lift technology's contribution to the workover-rig cost change.", "baseline": "Three years before the May 8, 2025 call; exact start/end dates and absolute costs undisclosed.", "economics": "No AI/hardware-specific cost attribution or absolute $/bbl disclosed." }, "reason": "The exact transcript passage places the artificial-lift statement next to, but does not quantify causal attribution for, the 50% workover-rig cost/bbl decline. Keep the full Block 53 3,500-well context and avoid attributing all savings to lift performance.", "recommended_disposition": "background_or_operator_performance_context", "sources_inspected": [ { "url": "https://www.oxy.com/siteassets/documents/investors/quarterly-earnings/oxy1q25transcript.pdf", "access": "Issuer-hosted transcript PDF opened directly", "locator": "May 8, 2025 call, PDF p. 9, lines 317-325." } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R03-US-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "The three years preceding 2025-05-08; exact start/end dates and annual trajectory not provided." }, { "id": "TECH-04", "company": "Occidental (Oxy)", "title": "DJ Basin Aggregate Recycling Facility", "category": "water / drilling-waste process innovation and logistics", "kind": "new_initiative", "ai_role": "Physical process/materials-recovery and water-recycling operation; no AI role disclosed.", "asset": "Not disclosed", "stage": "Operating DJ Basin facility and 2024 result, not a future target.", "operating_period": "2025", "claim": "Official report indexed text reports 2024 facility saved over $18 million compared with traditional commercial disposal; recycled approximately 142 megaliters (142 million liters) of water; avoided 400,000 truck-transport miles; recycled over 30,000 m3 of material.", "economics": "Not disclosed", "baseline": "$18m+ is issuer-reported avoided disposal cost against traditional commercial disposal; it is not revenue. Cost boundary, denominator and independent assurance were not available in directly opened report text.", "limits": "Issuer-reported facility result and comparison; the cited report summary does not give full cost boundary, detailed denominator, or independent assurance for the savings estimate.", "relationship": "Material water/logistics and disposal-cost alternative; keep issuer-reported 142 ML and $18m+ avoided-disposal claim provisional until underlying report page, throughput and cost boundary are verified.", "decision_question": "How does $18m+ avoided disposal cost reconcile to facility throughput, alternative disposal tariffs, capex/opex, water treatment and quality, and avoided-mile denominator?", "company_key": "Occidental", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "2025 Sustainability Report", "publisher": "Occidental Petroleum", "date": "2025", "url": "https://calciumchloride-prod.oxy.com/siteassets/documents/publications/2025-sustainability-report-web.pdf", "locator": "Aggregate Recycling Facility section", "access": "See research audit", "supports": "See cited passage" }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025", "url": "https://calciumchloride-prod.oxy.com/siteassets/documents/publications/2025-sustainability-report-web.pdf", "locator": "2025 Sustainability Report, p.63, Aggregate Recycling Facility (index result).", "access": "official issuer-hosted PDF; direct browser open returned internal error/oversize, indexed extract available; content not fully directly inspected", "supports": "Potentially strong example with cost, water and logistics KPIs. Keep all metrics as issuer-reported and explicitly flag that this audit could not inspect the PDF directly. Avoid converting 142 megaliters into barrels or implying audited net savings." } ], "references": [ { "id": "AI-153", "relationship": "company_context" }, { "id": "AI-215", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "TECH-04", "core_company": true, "ai_ids": [ "AI-153", "AI-215" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025" }, { "id": "T10-R01-GLOBAL-02", "company": "Saudi Aramco", "title": "Upstream water reuse and zero-liquid-discharge technology portfolio", "category": "water / process technology / drilling and stimulation inputs", "kind": "update", "ai_role": "The water treatment/reuse mechanisms are physical/process technologies. The report separately discusses digital discharge monitoring, but does not attribute AI to the water-reuse volume or ZLD trial; absence of disclosure is not proof no AI is used.", "asset": "Uthmaniyah and Shedgum gas plants; issuer does not assign the reported reuse volume to one named treatment unit or well program.", "stage": "Issuer describes a commercialized portfolio of water-conservation technologies and reports 2025 operating reuse; it also reports 2025 advancement of ZLD treatment/salt-recovery methods and a field trial using residual ZLD waste in drilling operations.", "operating_period": "2025; source is Aramco Sustainability Report 2025, issued in 2026.", "claim": "Around 8.3 million gallons of wastewater were recycled at Uthmaniyah and Shedgum gas plants for stimulation/drilling in 2025. The separately described ZLD technologies/trial are not stated as the source of that volume; 99% purity is a process claim, not independent water-quality verification.", "economics": "No named-technology capex/opex, water-treatment tariff, groundwater value, disposal savings, reuse yield or field-level unit cost disclosed. Portfolio's 'up to 250 million gallons per year per plant' groundwater-conservation potential for one contaminated-water fracturing-fluid technology is a stated potential, not the measured result at Uthmaniyah/Shedgum.", "baseline": "No plant-specific before/after volume, freshwater displacement denominator, water quality specification for the 8.3 million gallons, or alternative-disposal comparator reported.", "limits": "This is a bounded portfolio update rather than one isolated project: separate the 8.3 million gallons of wastewater reuse, ZLD purity claim, ZLD residual-waste trial and potential per-plant groundwater savings. Reported activity is useful upstream water/process context; do not convert it to financial ROI or attribute outcomes to ZLD without source proof.", "relationship": "Physical/process methods can compete with groundwater sourcing and disposal logistics; the source does not prove a direct AI dependency or same-project overlap.", "decision_question": "Which treatment process produced the reported site volume, what is the input/output water-quality and volume balance, and how do full treatment/disposal costs compare with freshwater and disposal alternatives?", "company_key": "Aramco", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Saudi Aramco Sustainability Report 2025", "publisher": "Saudi Aramco", "date": "2026 (2025 reporting year)", "url": "https://www.aramco.com/-/media/publications/corporate-reports/sustainability-reports/report-2025/english/2025-saudi-aramco-sustainability-report-full-en.pdf", "locator": "PDF printed pp.36-37 / opened text lines 5077-5136: 8.3 million gallons at Uthmaniyah/Shedgum; portfolio process claims; 99% purity and residual-ZLD field trial.", "access": "Official PDF opened; relevant pages and text directly reviewed.", "supports": "Site scope, 2025 reuse volume, separate technology mechanisms and boundaries." } ], "references": [ { "id": "AI-038", "relationship": "company_context", "basis": "Aramco general AI deployment portfolio, not an identified water-treatment/reuse project." }, { "id": "AI-037", "relationship": "company_context", "basis": "Aramco enterprise technology-value reporting; not a water-specific economic attribution." } ], "review": { "verdict": "correct", "reason": "Keep as an operating water/process case but separate quantified reuse volume from the ZLD trial and avoid attributing either to AI or a cost/recovery result.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R01-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Around 8.3 million gallons of wastewater were recycled at Uthmaniyah and Shedgum gas plants for stimulation/drilling in 2025. The separately described ZLD technologies/trial are not stated as the source of that volume; 99% purity is a process claim, not independent water-quality verification." }, "reason": "Keep as an operating water/process case but separate quantified reuse volume from the ZLD trial and avoid attributing either to AI or a cost/recovery result.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://www.aramco.com/-/media/publications/corporate-reports/sustainability-reports/report-2025/english/2025-saudi-aramco-sustainability-report-full-en.pdf", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "PDF printed pp.36-37 / opened text lines 5077-5136: 8.3 million gallons at Uthmaniyah/Shedgum; portfolio process claims; 99% purity and residual-ZLD field trial.", "date": "2026 (2025 reporting year)" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R01-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-038", "AI-037" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025; source is Aramco Sustainability Report 2025, issued in 2026." }, { "id": "T10-R08-GLOBAL-02", "company": "Saudi Aramco", "title": "Jubail CCS hub phase-one operating target moved from 2027 to 2028", "category": "Carbon capture and storage infrastructure / schedule change", "kind": "update", "ai_role": "No AI role disclosed; capture/transport/storage hub is industrial process and infrastructure.", "asset": "Phase 1 Jubail CCS hub, Saudi Arabia; planned industrial hub with Aramco, Linde and SLB partnership.", "stage": "Under development; issuer amended schedule to 2028, one year later than previous 2027 plan; annual capacity target up to 9 Mt CO2 (6 Mt Aramco facilities, 3 Mt external industrial facilities per 2024 sustainability report).", "operating_period": "Schedule amended 2025-09-02; latest scope/schedule confirmed in 2025 issuer update.", "claim": "Aramco’s July 2025 article (amended 2 Sep) moves Jubail CCS phase-one planned operational date from 2027 to 2028; up-to-9 Mt CO₂/year remains capacity ambition. The article does not give the schedule-change cause or evidence of a technical failure. Use 2024 report only as older stage context.", "economics": "No current project cost, delay cost or expected unit storage tariff disclosed in the reviewed article/report.", "baseline": "Schedule baseline revised from planned 2027 to 2028; capacity is a planned maximum, not installed/operating volume.", "limits": "Reason for schedule revision not disclosed in the opened article. Do not infer construction problems or technology failure from a date change. CCS hub is industrial infrastructure and not a named upstream production deployment.", "relationship": "No same initiative match identified in the production register during this round's targeted scan; report is contextual project schedule evidence. Aramco's Hawiyah-Uthmaniyah EOR (R03 context) is a separate existing operating facility, not the Jubail CCS hub.", "decision_question": "Does the 2028 timeline change upstream-to-hub sequencing or vendor/transport utilization assumptions, and what is the revised cost-to-complete and offtake commitment?", "company_key": "Aramco", "run": "Rounds 1–10", "disposition": "background", "sources": [ { "title": "Closing the loop: how Aramco is progressing towards a circular economy", "publisher": "Aramco", "date": "2025-07-15; amended 2025-09-02", "url": "https://www.aramco.com/en/news-media/elements-magazine/2025/closing-the-loop-how-aramco-is-progressing-towards-a-circular-economy", "locator": "Lines 136-140, 163", "access": "Direct issuer article opened; date and amendment found", "supports": "Capacity, 85-km tie to separate Uthmaniyah EOR facility, phase-one Jubail CCS planned capacity/date revision." }, { "title": "Saudi Aramco Sustainability Report 2024", "publisher": "Aramco", "date": "2025 publication; reports 2024", "url": "https://www.aramco.com/-/media/publications/corporate-reports/sustainability-reports/report-2024/english/2024-saudi-aramco-sustainability-report-full-en.pdf/", "locator": "PDF pp. 39, 2024 progress toward planned initiatives", "access": "Indexed primary report excerpt", "supports": "2024 phase-one agreement, 9 Mtpa capacity, share allocation, early works and EPC awards." } ], "references": [], "review": { "verdict": "correct", "reason": "Primary article supports revised schedule, not reason or performance. Retain as project timeline background, not an upstream operational technology outcome.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R08-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Aramco’s July 2025 article (amended 2 Sep) moves Jubail CCS phase-one planned operational date from 2027 to 2028; up-to-9 Mt CO₂/year remains capacity ambition. The article does not give the schedule-change cause or evidence of a technical failure. Use 2024 report only as older stage context." }, "reason": "Primary article supports revised schedule, not reason or performance. Retain as project timeline background, not an upstream operational technology outcome.", "recommended_disposition": "background", "sources_checked": [ { "url": "https://www.aramco.com/en/news-media/elements-magazine/2025/closing-the-loop-how-aramco-is-progressing-towards-a-circular-economy", "access_status": "Directly reopened primary issuer article in R10, but crawler exposed no article body; source record reports prior direct inspection", "locator": "Lines 136-140, 163", "date": "2025-07-15; amended 2025-09-02" }, { "url": "https://www.aramco.com/-/media/publications/corporate-reports/sustainability-reports/report-2024/english/2024-saudi-aramco-sustainability-report-full-en.pdf/", "access_status": "Directly reopened primary issuer article in R10, but crawler exposed no article body; source record reports prior direct inspection", "locator": "PDF pp. 39, 2024 progress toward planned initiatives", "date": "2025 publication; reports 2024" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R08-GLOBAL-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Schedule amended 2025-09-02; latest scope/schedule confirmed in 2025 issuer update." }, { "id": "T10-R09-GLOBAL-02", "company": "Saudi Aramco", "title": "2025 portfolio cost per boe is a scale benchmark, not a technology return", "category": "Portfolio unit-cost benchmark / upstream comparability", "kind": "context", "ai_role": "Report references scaled technology application as one of several drivers of low costs, alongside geology, favorable operating locations, and infrastructure/logistics. No isolated technology effect disclosed.", "asset": "Saudi Aramco operated/concession upstream portfolio; annual company-level average, not a named field or project.", "stage": "Reported actual FY2025 outcome in annual report.", "operating_period": "Year ended 2025; 2024 comparator.", "claim": "Aramco reports portfolio average upstream lifting cost $3.51/boe (2025) vs $3.53 (2024), and upstream CAPEX $8.0/boe vs $8.3. These are portfolio benchmarks influenced by geology, locations, infrastructure, depletion, fiscal discipline and technology; they do not isolate a technology contribution or compare like-for-like asset economics.", "economics": "Actual portfolio averages, not marginal cost, project break-even, technology spend, or technology ROI. Reported CAPEX per boe is not same as lifting cost and should be kept separate.", "baseline": "2024 comparator: $3.53/boe lifting and $8.3/boe upstream capex; 2025 actual: $3.51/boe and $8.0/boe.", "limits": "Aramco's reservoir/location/geology and giant integrated scale make a raw $/boe comparison with smaller offshore or unconventional projects misleading. No technology counterfactual, asset-level eligible population, or technology spending allocation is reported.", "relationship": "AI-037 is Aramco technology-value reporting context, not same-project or the basis for these unit costs. This record is a portfolio unit-cost benchmark and should not be merged into any AI ROI.", "decision_question": "Which unit-cost dimensions can be normalized across operators (lifting versus total cost versus CAPEX per boe), and which structural advantages must be controlled before attributing differences to technology?", "company_key": "Aramco", "run": "Rounds 1–10", "disposition": "background", "sources": [ { "title": "Annual Report 2025, Upstream operations", "publisher": "Saudi Aramco", "date": "2026 publication; FY ended 2025", "url": "https://www.aramco.com/-/media/publications/corporate-reports/reports-and-presentations/2025/fy/sections/ara-2025-results-english.pdf", "locator": "PDF pp. 48-49 (printed); lines 1479-1498, 1572-1607", "access": "Direct annual-report PDF opened", "supports": "Actual FY2025 and FY2024 cost metrics and company attribution to geology, infrastructure and scaled technology." } ], "references": [ { "id": "AI-037", "relationship": "AI-037 is Aramco technology-value reporting context, not same-project or the basis for these unit costs. This record is a portfolio unit-cost benchmark and should not be merged into any AI ROI." } ], "review": { "verdict": "correct", "reason": "Issuer annual report supports values and multiple-driver caveat. Useful as operating-cost context only, not technology return.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R09-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Aramco reports portfolio average upstream lifting cost $3.51/boe (2025) vs $3.53 (2024), and upstream CAPEX $8.0/boe vs $8.3. These are portfolio benchmarks influenced by geology, locations, infrastructure, depletion, fiscal discipline and technology; they do not isolate a technology contribution or compare like-for-like asset economics." }, "reason": "Issuer annual report supports values and multiple-driver caveat. Useful as operating-cost context only, not technology return.", "recommended_disposition": "background", "sources_checked": [ { "url": "https://www.aramco.com/-/media/publications/corporate-reports/reports-and-presentations/2025/fy/sections/ara-2025-results-english.pdf", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "PDF pp. 48-49 (printed); lines 1479-1498, 1572-1607", "date": "2026 publication; FY ended 2025" } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R09-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-037" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "Year ended 2025; 2024 comparator." }, { "id": "T20-R11-GLOBAL-01", "company": "Saudi Aramco / Yokogawa", "title": "Fadhili moves from an AI pilot to autonomous gas-treatment control", "category": "process control / gas treatment / reinforcement-learning control", "kind": "update", "ai_role": "Multiple coordinated agents use Yokogawa's Factorial Kernel Dynamic Policy Programming (FKDPP), a reinforcement-learning algorithm, to directly and autonomously control acid gas removal (AGR). A simulator trained agents; they were evaluated for reliability/validity and integrated into Yokogawa CENTUM VP to retain existing process-control safety functions.", "asset": "Fadhili Gas Plant, Saudi Arabia; AGR gas-treatment unit/core process.", "stage": "Yokogawa reported commissioning/implementation of multiple autonomous-control agents on 2025-10-29. The implementation was still undergoing detailed evaluation when the supplier disclosed initial results. Aramco's current undated page later says permanently adopted, but that page could not be directly fetched in this pass; do not claim a verified adoption date from it.", "operating_period": "Commissioning reported 29 October 2025; benefit measurement period not disclosed.", "claim": "Yokogawa reports initial Fadhili results of 10%-15% lower amine and steam use, about 5% lower power use, improved process stability, and significantly less operator manual intervention despite ambient-condition changes. The same release says detailed evaluation was ongoing. It describes three deployment phases, simulator training/validation, then integration with CENTUM VP before autonomous control of the AGR core process.", "economics": "No absolute chemical/steam/power quantities, prices, annualized savings, project cost, baseline duration, or return/payback are disclosed. Percentage reductions are supplier-reported initial results and not independently validated in the release. Do not multiply percentages by plant-wide utility/cost totals without system boundary and measurement data.", "baseline": "Implied pre-deployment operating usage for the Fadhili AGR system; the comparison period and normalization for throughput, feed composition, ambient conditions, or gas quality are not specified.", "limits": "This is an integrated gas-processing unit rather than upstream well/field production, but it is a consequential operator process-control analogue. Direct process control and safety-system integration are meaningful maturity details; commissioning is not proof of sustained performance. No measurement/error design, guardrails, intervention rate, independent validation, or duration supplied. Exact page now confirms AI-141 is same initiative; do not count as a new deployment.", "relationship": "Same Fadhili AGR process and exact Aramco source underlying production record AI-141, now corroborated by a dated supplier commissioning account. Update the existing record's chronology/stage and add simulator-to-control-system safety implementation detail. Existing Aramco portfolio AI-038 is company context only, not same project. No net-new initiative count.", "decision_question": "What were the baseline and post-commissioning test windows, absolute normalized amine/steam/power use per gas throughput, operator interventions and constraint violations, and what independent evaluation supports sustained autonomous control?", "company_key": "Aramco", "run": "Rounds 11–20", "disposition": "include_with_limits", "sources": [ { "title": "Aramco and Yokogawa Achieve a Major Milestone with Commissioning of Multiple Autonomous Control AI Agents at Major Gas Facility", "publisher": "Yokogawa Electric Corporation", "date": "2025-10-29", "url": "https://www.yokogawa.com/news/press-releases/2025/2025-10-29/", "locator": "Release dated 29 October 2025; paragraphs on phased AGR control implementation and preliminary reductions.", "access": "Official supplier release found through its indexed full text and 2025 press-release index; direct root open returned bot challenge. Earlier agent read a mirrored URL; official URL replaces that citation.", "supports": "Named Aramco Fadhili asset; commissioned/implemented multiple autonomous RL-control agents; staged simulator and DCS integration; initial percentage reductions and continuing detailed evaluation." }, { "title": "AI and Big Data - Oil & Gas Industry", "publisher": "Saudi Aramco", "date": "Undated current page; operating period stated October 2024-April 2025", "url": "https://www.aramco.com/en/what-we-do/energy-innovation/digitalization/ai-and-big-data", "locator": "Fadhili Gas Plant section; indexed primary search excerpt.", "access": "Search-indexed primary excerpt; direct page open timed out", "supports": "Reported rollout period, initial 10%-15% amine/steam and ~5% power reduction, permanent adoption, and ongoing suitability reviews. Not used to assert a directly verified permanent-adoption date." } ], "references": [ { "id": "AI-141", "relationship": "Same Fadhili AGR process and exact Aramco source underlying production record AI-141, now corroborated by a dated supplier commissioning account. Update the existing record's chronology/stage and add simulator-to-control-system safety implementation detail. Existing Aramco portfolio AI-038 is company context only, not same project. No net-new initiative count." } ], "review": { "verdict": "confirmed", "reason": "Directly opened Yokogawa's 2025-10-29 supplier release. It identifies multiple autonomous-control AI agents at Fadhili, commissioning/implementation, the RL-based mechanism, and initial reductions of 10–15% in amine/steam use and about 5% in power while detailed evaluation was ongoing. The finding already keeps the supplier-reported percentages provisional, notes no disclosed measurement window or denominators, and does not assert verified Aramco adoption from the undated inaccessible operator page. AI-141 is the matching profile. No correction needed. Root replaced the mirrored domain with the release on yokogawa.com. Its direct page returned a bot challenge; indexed official text and the official press-release index support the claim. No direct full-text access to that URL is implied.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R11-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly opened Yokogawa's 2025-10-29 supplier release. It identifies multiple autonomous-control AI agents at Fadhili, commissioning/implementation, the RL-based mechanism, and initial reductions of 10–15% in amine/steam use and about 5% in power while detailed evaluation was ongoing. The finding already keeps the supplier-reported percentages provisional, notes no disclosed measurement window or denominators, and does not assert verified Aramco adoption from the undated inaccessible operator page. AI-141 is the matching profile. No correction needed.", "sources_inspected": [ { "url": "https://yokogawaelectric.org/news/press-releases/2025/2025-10-29/index.html", "access": "Directly opened supplier primary HTML", "locator": "Claim-bearing passages lines 578–598 per originating record; page directly opened and title/date verified." }, { "url": "https://www.aramco.com/en/what-we-do/energy-innovation/digitalization/ai-and-big-data", "access": "No fresh direct open; originating record reports indexed primary excerpt and page-open timeout", "locator": "Adoption wording remains explicitly undated and is excluded from the deployment-date claim." } ], "recommended_disposition": "include_with_limits" } ] }, "department": "Production & process operations", "group_id": "T20-R11-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-141" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Commissioning reported 29 October 2025; benefit measurement period not disclosed." }, { "id": "R1-GL-05", "company": "ADNOC", "title": "Taurob heavy-duty inspector robot at Taweelah Gas Compression Plant", "category": "industrial robotics / sensing and hazardous inspection", "kind": "context", "ai_role": "Taurob inspection system uses LiDAR/thermal imaging; the source does not attribute its function or outcomes to AI.", "asset": "Taweelah Gas Compression Plant is a gas-processing/compression facility, not a producing upstream field.", "stage": "Inspector robot deployed and conducting routine on-site autonomous inspections in May 2026. A separate heavy-duty operator robot that lifts/grips equipment and turns valves remained planned for end-2026.", "operating_period": "ADNOC release dated 2026-05-21; operator-robot completion is a target by end-2026, not completed evidence.", "claim": "Routine inspection deployment is described, with no quantified robot-attributed outcome or cost. Keep the separately planned operator/manipulator robot and the 30% HSE Cockpit.ai incident reduction separate; neither is an outcome of the deployed Taurob robot.", "economics": "Robot capex, integration, maintenance, and cost per inspection not disclosed.", "baseline": "Hazardous human inspection is the implicit alternative; no before/after baseline disclosed.", "limits": "Single-plant deployment and capability description do not establish adoption or performance. Keep inspector robot separate from future manipulation robot and from separate AI HSE metrics. Gas compression plant is not an upstream producing asset.", "relationship": "Named robot is in service, but the asset is a gas-compression plant rather than an upstream producing field; keep adjacent and separate deployed inspection robot from planned manipulation robot.", "decision_question": "How many inspection hours/routes, callouts or exposure-hours does the deployed robot remove per year, net of integration and maintenance cost?", "company_key": "ADNOC", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "ADNOC Deploys Industry-First Heavy-Duty Robot to Strengthen Safety, Reliability and Performance", "publisher": "ADNOC", "date": "2026-05-21", "url": "https://adnoc.ae/en/news-and-media/press-releases/2026/adnoc-deploys-industry-first-heavy-duty-robot-to-strengthen-safety-reliability-and-performance", "locator": "Deployment, sensors, future operator robot, and separate HSE Cockpit.ai claim, lines 527-543", "access": "Issuer page opened; full text accessible", "supports": "Deployed robot scope, sensor payload, future robot timing, partners, and attribution boundary." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-05-21", "url": "https://adnoc.ae/en/news-and-media/press-releases/2026/adnoc-deploys-industry-first-heavy-duty-robot-to-strengthen-safety-reliability-and-performance", "locator": "Taurob robot at Taweelah Gas Compression Plant; separate heavy-duty operator robot planned for end-2026; HSE Cockpit statistic", "access": "ADNOC issuer page opened; text accessible", "supports": "This is relevant to oil-and-gas operations broadly, but only adjacent to an upstream producing-asset scope. The release combines distinct deployed and planned systems and a separate AI safety metric, creating high double-count risk without strict separation." } ], "references": [ { "id": "AI-218", "relationship": "company_context" } ], "department": "Maintenance & reliability", "group_id": "R1-GL-05", "core_company": true, "ai_ids": [ "AI-218" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "ADNOC release dated 2026-05-21; operator-robot completion is a target by end-2026, not completed evidence." }, { "id": "T10-R03-GLOBAL-02", "company": "ADNOC", "title": "Produced-water reinjection reported at Bu Hasa and Asab", "category": "Reservoir water management / pressure maintenance", "kind": "update", "ai_role": "Report says performance indicators are supported by digital surveillance and optimization tools, but does not attribute the 100% PWRI achievement to AI or name a model. Digital support and reservoir process should remain separate.", "asset": "Bu Hasa and Asab onshore operating sites; site-specific volumes and reservoir details not stated.", "stage": "Operating achievement claimed by issuer in 2025 sustainability report; broader mature-field PWRI roadmap remains in progress.", "operating_period": "2025 report; operating period for 100% achievement not separately specified.", "claim": "ADNOC states 100% produced-water reinjection at Bu Hasa and Asab. The report does not define the water-volume denominator, reporting period or cost, nor isolate digital tools as the cause.", "economics": "No named-site volumes, energy, water-treatment cost, avoided disposal cost, or production uplift disclosed in the reviewed chapter.", "baseline": "No named-site baseline or definition of the 100% denominator is provided in the accessible report text. Company-wide table reports 446 million m3 water reinjected for reservoir management in 2025 but does not link that volume specifically to PWRI at the two sites.", "limits": "Do not interpret 100% as all produced water across ADNOC or as 100% water reuse company-wide; denominator, measurement boundary, timing, and site volumes need clarification. Site achievement should not be conflated with the separate Sustainable Water Supply Project (treated seawater, still under development).", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified.", "decision_question": "Does full produced-water reinjection at two mature sites reduce make-up water and disposal costs without a countervailing injection-energy, injectivity, or water-handling penalty?", "company_key": "ADNOC", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Sustainability Report 2025: Delivering Responsibly, Upstream water management", "publisher": "ADNOC", "date": "2026 publication; reports 2025", "url": "https://reports.adnoc.ae/e/sustainability-report-2025/mjoOSdaQ33", "locator": "Chapter page 33 / printed pp. 66-67; lines 2, 4-8", "access": "Direct issuer report chapter opened", "supports": "Water table, water's upstream role, 2025 strategy, 100% PWRI at Bu Hasa and Asab, and distinction from sustainable seawater supply project." } ], "references": [ { "id": "AI-011", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." }, { "id": "AI-040", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." }, { "id": "AI-216", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." }, { "id": "AI-217", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." }, { "id": "AI-218", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." }, { "id": "AI-273", "relationship": "Only company-level AI context; no same-project duplicate identified in earlier core scan. The Sustainable Water Supply Project is a distinct adjacent infrastructure initiative and should be covered in a power/water round if its commissioning status can be verified." } ], "review": { "verdict": "correct", "reason": "Primary report supports issuer claim; preserve its bounded status without assuming a basin-wide or independently assured performance metric.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R03-GLOBAL-02", "verdict": "correct", "patch": { "claim": "ADNOC states 100% produced-water reinjection at Bu Hasa and Asab. The report does not define the water-volume denominator, reporting period or cost, nor isolate digital tools as the cause." }, "reason": "Primary report supports issuer claim; preserve its bounded status without assuming a basin-wide or independently assured performance metric.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://reports.adnoc.ae/e/sustainability-report-2025/mjoOSdaQ33", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Chapter page 33 / printed pp. 66-67; lines 2, 4-8", "date": "2026 publication; reports 2025" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R03-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-011", "AI-040", "AI-216", "AI-217", "AI-218", "AI-273" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 report; operating period for 100% achievement not separately specified." }, { "id": "T10-R04-GLOBAL-01", "company": "ADNOC", "title": "Sustainable Water Supply Project for Bab and Bu Hasa injection", "category": "Water treatment, transport and injection infrastructure", "kind": "update", "ai_role": "No AI contribution disclosed; conventional water treatment, pumping and pipeline infrastructure.", "asset": "Central seawater treatment plant at Al Mirfa, 245-km pipeline and pumping stations supplying Bab and Bu Hasa onshore fields.", "stage": "Under development/current issuer status says due to be commissioned in 2026; not verified commissioned as of this research pass.", "operating_period": "Planned commissioning 2026; forecast capacity and savings are prospective.", "claim": "ADNOC describes a designed capacity >115 million imperial gal/day (about 3.2 million bbl/day) and a project for seawater treatment/supply to Bab and Bu Hasa. Capacity and up-to-30% energy-use benefit are design/company claims; do not report as commissioned throughput or measured savings. Current source status/commissioning date should be sourced before presenting as current.", "economics": "No project CAPEX, water tariff, OPEX, pump energy baseline, savings measurement protocol, or realized energy reduction disclosed on the project page.", "baseline": "No baseline or denominator behind up-to-30% reduction disclosed; planned rather than measured.", "limits": "Issuer project page indexed, not directly opened (request timed out). Current reported schedule is 2026; treat as due/expected, not commissioning evidence. It is distinct from produced-water reinjection at Bu Hasa and Asab reported in R03.", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa).", "decision_question": "Before sanction/replication, what metered energy-per-barrel and aquifer-water displacement will the network deliver after start-up, and what tariff/availability risk sits in the TAQA partnership?", "company_key": "ADNOC", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Sustainable Water Supply Project", "publisher": "ADNOC", "date": "Undated current issuer project page; accessed 2026-10-07", "url": "https://www.adnoc.ae/en/our-projects/sustainable-water-supply", "locator": "Project overview and fast facts", "access": "Search-indexed primary page; direct open timed out", "supports": "Plant method, capacity, fields, pipeline length, 2026 expected commission, 30% energy reduction forecast and 100% clean-grid statement." } ], "references": [ { "id": "AI-011", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." }, { "id": "AI-040", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." }, { "id": "AI-216", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." }, { "id": "AI-217", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." }, { "id": "AI-218", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." }, { "id": "AI-273", "relationship": "Company-level digital and AI register entries are not this water-infrastructure project. R03 ADNOC PWRI is a different water stream and project (produced water reuse at Bu Hasa/Asab versus treated seawater supply to Bab/Bu Hasa)." } ], "review": { "verdict": "correct", "reason": "The primary project page was indexed but direct access timed out in the source pass. Retain as a planned infrastructure case with access limitation; no realized KPI.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R04-GLOBAL-01", "verdict": "correct", "patch": { "claim": "ADNOC describes a designed capacity >115 million imperial gal/day (about 3.2 million bbl/day) and a project for seawater treatment/supply to Bab and Bu Hasa. Capacity and up-to-30% energy-use benefit are design/company claims; do not report as commissioned throughput or measured savings. Current source status/commissioning date should be sourced before presenting as current." }, "reason": "The primary project page was indexed but direct access timed out in the source pass. Retain as a planned infrastructure case with access limitation; no realized KPI.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://www.adnoc.ae/en/our-projects/sustainable-water-supply", "access_status": "Search-indexed issuer project-page excerpt; direct open timed out in source pass; no independent full-page verification", "locator": "Project overview and fast facts", "date": "Undated current issuer project page; accessed 2026-10-07" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-011", "AI-040", "AI-216", "AI-217", "AI-218", "AI-273" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Planned commissioning 2026; forecast capacity and savings are prospective." }, { "id": "T10-R07-GLOBAL-01", "company": "ADNOC / SLB", "title": "SLB DrillOps-enabled Real-Time Operations Center deployed across >120 rigs", "category": "Installed supplier stack / AI-enabled drilling operations", "kind": "update", "ai_role": "Explicit: AI-powered performance insights combined with real-time operational data, analytics, dashboards and DrillOps. Reported impact should be regarded as issuer/vendor claim pending defined baselines and audit.", "asset": "ADNOC Drilling's >120-rig fleet supporting ADNOC Onshore and ADNOC Offshore, onshore and offshore assets; hosted in ADNOC UAE cloud environment.", "stage": "ADNOC announced deployed fleet-wide platform on 2026-08-04; production deployment according to issuer release.", "operating_period": "Deployment stated as of 2026-08-04; performance window and ramp dates not given.", "claim": "ADNOC reports >120 rigs and claims 30–40% lower engineering effort, 2–3x rig coverage per engineer, 4–12 hours shorter incident response, and potential avoidance of 1–2 downtime days. Measurement windows, baselines, frequency and independent validation are not disclosed; no cost/payback provided.", "economics": "No contract value, rig-level deployment cost, gross/net savings, uptime history, or savings attribution shared; performance figures are issuer claims without methodology or evaluation period.", "baseline": "Unspecified prior staffing/rig coverage and performance windows; reference to prior reporting cycles taking several days/full day of analysis is not quantified by use case.", "limits": "Fleet coverage is meaningful scale, but the listed benefit ranges need denominators and measurement definition. The 1–2 days is potential avoided downtime, not observed downtime avoided per rig. No external validation disclosed.", "relationship": "Same-project, exact same RTOC/SLB DrillOps fleet deployment already represented by AI-226 (same Aug 4 2026 issuer release). This round adds no separate initiative; retain only as source-level confirmation/context for the canonical record and do not count twice.", "decision_question": "What per-rig staffing, reporting, incident and downtime logs substantiate the savings claims, and what portion is caused by software/AI versus process redesign and centralization?", "company_key": "ADNOC", "run": "Rounds 1–10", "disposition": "enrich_existing", "sources": [ { "title": "ADNOC and SLB Deploy AI Platform Across Over 120 Drilling Rigs to Strengthen Upstream Performance", "publisher": "ADNOC", "date": "2026-08-04", "url": "https://www.adnoc.ae/en/news-and-media/press-releases/2026/adnoc-and-slb-deploy-ai-platform-across-over-120-drilling-rigs-to-strengthen-upstream-performance", "locator": "Lines 527-543; repeated release date 548-560", "access": "Direct issuer release opened", "supports": "Partner, scope (>120 rigs), deployment status, vendor product, hosted environment and reported benefit claims." } ], "references": [ { "id": "AI-226", "relationship": "Same-project, exact same RTOC/SLB DrillOps fleet deployment already represented by AI-226 (same Aug 4 2026 issuer release). This round adds no separate initiative; retain only as source-level confirmation/context for the canonical record and do not count twice." } ], "review": { "verdict": "correct", "reason": "Direct primary release reopened. Merge source/claim updates into AI-226; do not add a second deployment. Keep the specific metric-denominator caveats attached.", "cross_audits": [ { "assignment": "round-07-global.json", "finding_id": "T10-R07-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": [ "AI-226" ], "relationship": "exact same project and same dated release as canonical AI-226; duplicate discovery, not a net-new case" }, "reason": "Canonical register scan found AI-226 is the RTOC AI drilling oversight deployment across ADNOC’s 120+ rig fleet, and its exact Source_URL is the same press release reopened in this round.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local production register read", "locator": "AI-226 Company/Initiative/Source_URL/Source_date/Reported_metric" }, { "url": "https://www.adnoc.ae/en/news-and-media/press-releases/2026/adnoc-and-slb-deploy-ai-platform-across-over-120-drilling-rigs-to-strengthen-upstream-performance", "access": "direct issuer release opened", "locator": "lines 527-543" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R07-GLOBAL-01", "verdict": "correct", "patch": { "canonical_overlap": "AI-226 (ADNOC Real-Time Operations Center AI drilling oversight across ADNOC’s 120+ rig fleet). Exact same operator, platform, rollout and August 2026 announcement; this is duplicate evidence, not a second initiative.", "claim": "ADNOC reports >120 rigs and claims 30–40% lower engineering effort, 2–3x rig coverage per engineer, 4–12 hours shorter incident response, and potential avoidance of 1–2 downtime days. Measurement windows, baselines, frequency and independent validation are not disclosed; no cost/payback provided." }, "reason": "Direct primary release reopened. Merge source/claim updates into AI-226; do not add a second deployment. Keep the specific metric-denominator caveats attached.", "recommended_disposition": "enrich_existing", "sources_checked": [ { "url": "https://www.adnoc.ae/en/news-and-media/press-releases/2026/adnoc-and-slb-deploy-ai-platform-across-over-120-drilling-rigs-to-strengthen-upstream-performance", "access_status": "Directly reopened primary issuer release in R10; deployment/results release inspected", "locator": "Lines 527-543; repeated release date 548-560", "date": "2026-08-04" }, { "url": "site/dist/assets/research-data.json", "access_status": "Local production register directly searched for canonical IDs; exact IDs/titles inspected", "locator": "AI-226 (ADNOC Real-Time Operations Center AI drilling oversight across ADNOC’s 120+ rig fleet). Exact same operator, platform, rollout and August 2026 announcement; this is duplicate evidence, not a second initiative.", "date": "accessed 2026-10-07" } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R07-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-226" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Deployment stated as of 2026-08-04; performance window and ramp dates not given." }, { "id": "T20-R17-LIMITS-01", "company": "ADNOC Onshore / Jereh Oil & Gas Engineering Corporation", "title": "ADNOC’s remote-well contract shows the infrastructure around AI", "category": "buyer_budget_and_procurement", "kind": "update", "ai_role": "ADNOC says real-time field data will enable tools including AIQ RoboWell to control wells autonomously; award's stated scope is remote sensing and well-operating equipment, not an itemized AI contract.", "asset": "The EPC award names Bab, Bu Hasa and Southeast fields. The release separately says ADNOC's overall well-digitalization program is due in 2027 and will cover remote monitoring/control of over 2,000 wells; it does not allocate that entire well count to this award or only these three fields.", "stage": "Up-to-$920m EPC award announced 2024-11-05 for installation at three named fields. Overall digitalization program completion was targeted for 2027. Release identifies prior sensor/control-hardware deployments at Mender, Qusahwira and NEB; it says the private 5G network was being built and that it would enable AI tools such as RoboWell. It does not say RoboWell was already operating across the awarded fields.", "operating_period": "Award announced 2024-11-05; completion target 2027.", "claim": "ADNOC announced an EPC award worth up to $920m (AED 3.38bn) to Jereh for remote sensing and well-operating equipment at Bab, Bu Hasa and Southeast. The >2,000-well figure is the broader program target, not an explicitly itemized contract population. The announcement says data from equipment and a private 5G network under construction would enable autonomous RoboWell control. This is a material physical-infrastructure procurement signal; the award cap is not AI-only spend or realized value.", "economics": "Up to $920m announced EPC contract value (not necessarily fully spent); no separation of software, network, hardware, EPC or support cost; no AI-specific return.", "baseline": "Release identifies earlier digitalization deployment fields but gives no before/after well performance or comparable cost baseline.", "limits": "Issuer press release; total contract value includes remote sensing and well-operating equipment and EPC scope. It does not separate AI software, implementation, hardware, telecom, maintenance or other costs. The 2027 rollout is a target; fieldwide live scope and measured outcomes are not reported.", "relationship": "Related to baseline AI-273 (ADNOC Onshore / AIQ autonomous gas-lift control across 200 wells) because ADNOC names RoboWell in the same onshore well-digitalization program. The Jereh EPC scope is enabling infrastructure and a distinct award; do not attribute the AI-273 200-well deployment or outcome to these three fields absent asset-level confirmation.", "decision_question": "Which parts of the award's total contract value are addressable to software, integration, sensors, networks and service, and what evidence will qualify suppliers for the next asset tranche?", "company_key": "ADNOC", "run": "Rounds 11–20", "disposition": "retain as related infrastructure procurement update; link AI-273; do not count $920m as AI spend", "sources": [ { "title": "ADNOC Awards $920 Million Contract to Extend AI-Powered Well Digitalization Program to Cover over 2,000 Wells", "publisher": "ADNOC", "date": "2024-11-05", "url": "https://www.adnoc.ae/en/news-and-media/press-releases/2024/adnoc-awards-920-million-contract-to-extend-aipowered", "locator": "Lines 527–541", "access": "directly opened issuer announcement", "supports": "contract value and EPC contractor; named fields and remote hardware scope; target date and well count; existing deployment field names; sensor/control-room/RoboWell workflow; limits of AI price and outcome attribution." } ], "references": [ { "id": "AI-273", "relationship": "Related to baseline AI-273 (ADNOC Onshore / AIQ autonomous gas-lift control across 200 wells) because ADNOC names RoboWell in the same onshore well-digitalization program. The Jereh EPC scope is enabling infrastructure and a distinct award; do not attribute the AI-273 200-well deployment or outcome to these three fields absent asset-level confirmation." } ], "review": { "verdict": "correct", "reason": "ADNOC issuer source confirms award value, named scope, broader program target, earlier deployments and RoboWell enablement. It says network is being built and calls RoboWell a tool the infrastructure will enable, so current fieldwide autonomous operation is not established. Baseline AI-273 is a related canonical record and should be linked without conflating scope or economics.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R17-LIMITS-01", "verdict": "correct", "patch": { "asset": "The EPC award names Bab, Bu Hasa and Southeast fields. The release separately says ADNOC's overall well-digitalization program is due in 2027 and will cover remote monitoring/control of over 2,000 wells; it does not allocate that entire well count to this award or only these three fields.", "stage": "Up-to-$920m EPC award announced 2024-11-05 for installation at three named fields. Overall digitalization program completion was targeted for 2027. Release identifies prior sensor/control-hardware deployments at Mender, Qusahwira and NEB; it says the private 5G network was being built and that it would enable AI tools such as RoboWell. It does not say RoboWell was already operating across the awarded fields.", "claim": "ADNOC announced an EPC award worth up to $920m (AED 3.38bn) to Jereh for remote sensing and well-operating equipment at Bab, Bu Hasa and Southeast. The >2,000-well figure is the broader program target, not an explicitly itemized contract population. The announcement says data from equipment and a private 5G network under construction would enable autonomous RoboWell control. This is a material physical-infrastructure procurement signal; the award cap is not AI-only spend or realized value.", "economics": "Up to $920m announced EPC contract value (not necessarily fully spent); no separation of software, network, hardware, EPC or support cost; no AI-specific return.", "existing_ids": [ "AI-273" ], "relationship": "Related to baseline AI-273 (ADNOC Onshore / AIQ autonomous gas-lift control across 200 wells) because ADNOC names RoboWell in the same onshore well-digitalization program. The Jereh EPC scope is enabling infrastructure and a distinct award; do not attribute the AI-273 200-well deployment or outcome to these three fields absent asset-level confirmation." }, "reason": "ADNOC issuer source confirms award value, named scope, broader program target, earlier deployments and RoboWell enablement. It says network is being built and calls RoboWell a tool the infrastructure will enable, so current fieldwide autonomous operation is not established. Baseline AI-273 is a related canonical record and should be linked without conflating scope or economics.", "sources_inspected": [ { "url": "https://www.adnoc.ae/en/news-and-media/press-releases/2024/adnoc-awards-920-million-contract-to-extend-aipowered", "access": "direct issuer page reopened", "locator": "Lines 527–541; contract, named fields, overall well count, target date, prior deployments, network under construction and future RoboWell enablement." }, { "url": "research/technology-rounds-11-20/baseline-index.json", "access": "local baseline JSON read", "locator": "production_ai_profiles entry AI-273: ADNOC Onshore / AIQ autonomous gas-lift control across 200 producer wells." } ], "recommended_disposition": "retain as related infrastructure procurement update; link AI-273; do not count $920m as AI spend" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R17-LIMITS-01", "core_company": true, "ai_ids": [ "AI-273" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Award announced 2024-11-05; completion target 2027." }, { "id": "T10-R02-GLOBAL-01", "company": "Aker BP", "title": "HIPlog measures flow inside a multilateral well at Alvheim", "category": "completion / downhole sensing / production engineering", "kind": "new_initiative", "ai_role": "Physical measurement mechanism uses permanent small heat sources to send controlled thermal signals into production flow, read by existing temperature sensors; data calculate branch/zone production contributions. No AI contribution is disclosed; the data could support later analytics, but no such connection is reported.", "asset": "Alvheim field, Frosk Attic well 24/9-M-7; three branches with nine HIPlog stations, three per branch.", "stage": "First offshore pilot installed and measurement campaign completed; Aker BP reports signals from all branches, good measurement quality in two, and greater uncertainty in one. Repeated measurements planned over several years; it is not yet a proven production-uplift or scaled deployment.", "operating_period": "Aker BP's official news index dates the page 2026-01-01; the article says the first campaign was in November but does not state the year. Retain as 'November, year not stated in article' rather than infer a date.", "claim": "One three-branch Frosk Attic well, nine stations, initial campaign: signals and branch contributions measurable; two branches had good quality and the third had greater uncertainty associated with geometry/low rates. Repeated monitoring is planned, not yet a multi-well reliability record.", "economics": "No technology cost, intervention avoided, deferred production avoided, incremental recovery, or cash impact disclosed. The claimed mechanism may reduce information gaps without production interruption, but no economic result is yet measured.", "baseline": "No conventional production-log comparator or matched before/after branch allocation; the source positions prior measurement as difficult/impossible, without quantifying measurement performance or intervention costs.", "limits": "Single pilot well; early in well life; one of three branches has greater uncertainty; subsequent repeated measurements are needed for trend and allocation confidence. Aker BP and service provider statements are issuer/vendor claims; no independent validation located.", "relationship": "Non-AI physical sensing is an upstream measurement alternative/complement; whether AI or physics-based allocation improves interpretation is an open comparison, not an established result.", "decision_question": "Can repeated HIPlog measurements resolve branch-level allocation at low rates and awkward geometry reliably enough to change intervention or production-management decisions, and at what installed/recurring cost compared with conventional production logging?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "New technology provides better insight into wells at Alvheim", "publisher": "Aker BP", "date": "2026-01-01 (official news-index date; article body omits date)", "url": "https://akerbp.com/en/new-technology-provides-better-insight-into-wells-at-alvheim/", "locator": "Lines 85-105 method and non-interference; lines 125-139 named well, station count, first measurement and uncertainty; lines 153-157 next steps.", "access": "Official issuer page opened; full relevant text reviewed. Publication date checked in Aker BP official news index, where the item is listed as 01.01.2026.", "supports": "Mechanism, exact well scope, measurement evidence, uncertainty, and planned repeated use." }, { "title": "Aker BP news archive, page 2", "publisher": "Aker BP", "date": "Current archive; retrieved 2026-10-07", "url": "https://akerbp.com/en/news/page/2/?filter=news", "locator": "Entry 'New technology provides better insight into wells at Alvheim' dated 01.01.2026.", "access": "Official archive search-index text inspected.", "supports": "In-window publication date for the undated article body." } ], "references": [ { "id": "AI-138", "relationship": "company_context", "basis": "Aker BP AI remote-operations record at Yggdrasil; different asset and operation, no same HIPlog project link." }, { "id": "AI-269", "relationship": "company_context", "basis": "Aker BP/Cognite/NVIDIA anomaly-detection record across wells/equipment; distinct technology and no HIPlog linkage." } ], "review": { "verdict": "correct", "reason": "Aker BP directly reports pilot scope and uncertainty. This is hardware/measurement with possible downstream analytics; no AI role or economic result disclosed.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R02-GLOBAL-01", "verdict": "correct", "patch": { "claim": "One three-branch Frosk Attic well, nine stations, initial campaign: signals and branch contributions measurable; two branches had good quality and the third had greater uncertainty associated with geometry/low rates. Repeated monitoring is planned, not yet a multi-well reliability record." }, "reason": "Aker BP directly reports pilot scope and uncertainty. This is hardware/measurement with possible downstream analytics; no AI role or economic result disclosed.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://akerbp.com/en/new-technology-provides-better-insight-into-wells-at-alvheim/", "access_status": "Directly reopened primary issuer page in R10; pilot and uncertainty passages inspected", "locator": "Lines 85-105 method and non-interference; lines 125-139 named well, station count, first measurement and uncertainty; lines 153-157 next steps.", "date": "2026-01-01 (official news-index date; article body omits date)" }, { "url": "https://akerbp.com/en/news/page/2/?filter=news", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Entry 'New technology provides better insight into wells at Alvheim' dated 01.01.2026.", "date": "Current archive; retrieved 2026-10-07" } ] } ] }, "department": "Subsurface & recovery", "group_id": "T10-R02-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-138", "AI-269" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R02-GLOBAL-02", "company": "Aker BP / production-license partners", "title": "Aker BP extends reservoir contact with multilateral exploration wells", "category": "drilling engineering / multilateral and extended-reach well architecture", "kind": "new_initiative", "ai_role": "Aker BP describes a horizontal multilateral drilling method and high-quality subsurface data. The source mentions other AI tools in the broader Yggdrasil program but does not attribute the well architecture, drilling result or discovery to AI.", "asset": "Omega Alfa campaign around Yggdrasil in the Norwegian North Sea; licences 873, 873 B and 1249; wellbores 25/1-14 and sidetracks A–G drilled by Deepsea Stavanger.", "stage": "Campaign completed in August 2025; discovery volumes remain to be assessed as part of Yggdrasil development. This is an exploration result, not a producing-well performance test.", "operating_period": "Drilling began early May 2025 and ran about three months; campaign completion announced 2025-08-21/22.", "claim": "Issuer/regulator report a 45-km multi-target campaign over about three months, 40 km in reservoir, discoveries in four wellbores and one dry target (Alfa Sør); reported recoverable resource estimate is 96–134 mmboe. This is a campaign outcome, not a normalized drilling-rate/cost comparison.", "economics": "No campaign cost, well-cost comparator, days-saved benchmark, cost per target or economic value attributable to multilateral architecture disclosed. 96–134 mmboe is an issuer/regulator-reported discovery estimate, not reserves, sanction or technology-caused value.", "baseline": "No matched conventional-well campaign, reservoir exposure baseline or cost/time per prospect disclosed. The evidence demonstrates technical reach and exploration access, not a comparable unit-cost advantage.", "limits": "The campaign comprised one main well plus sidetracks A–G, not one literal borehole. Results combine geometry, geology, rig, planning and alliance execution. One target was dry and one sidetrack did not reach planned TD per regulator details. Do not convert the estimated discovery into realized production or claim the drilling method alone caused the resource outcome.", "relationship": "Physical well architecture and drilling engineering are independent from AI; subsurface data may later inform Yggdrasil concept selection, but AI contribution to drilling or discoveries is not established.", "decision_question": "Can long horizontal multilateral exploration reduce cost per target or accelerate appraisal/tie-back choice versus separate wells, after accounting for sidetrack complexity, failures and data value? What execution cost/time data are needed before replicating the architecture?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Significant oil discovery in the Yggdrasil area", "publisher": "Aker BP", "date": "2025-08-21", "url": "https://akerbp.com/en/borsmelding/significant-oil-discovery-in-the-yggdrasil-area-2/", "locator": "Lines 84-106; campaign targets, multilateral approach, drilling length/period, longest branch, resource estimate, partner/asset context.", "access": "Official issuer page opened; full relevant text reviewed.", "supports": "Engineering mechanism, campaign scale and issuer-reported discovery/uncertainty outcome." }, { "title": "Oil discovery in the Yggdrasil area (25/1-14, 25/1-14 A, B, C, D, E, F and G)", "publisher": "Norwegian Offshore Directorate", "date": "2025-08-22", "url": "https://www.sodir.no/en/whats-new/news/exploration-drilling-results/2025/oil-discovery-in-the-yggdrasil-area-251-14-251-14-a-b-c-d-e-f-and-g/", "locator": "Lines 302-323; campaign/wellbores, discovery count and volume, five-prospect description; lines 324-348 wellbore-specific results, dry target and planned-TD limit.", "access": "Official regulator page opened; relevant details directly reviewed.", "supports": "Regulator confirmation of drilling scope, resource estimate, number of discoveries and negative/failed wellbore details." } ], "references": [ { "id": "AI-138", "relationship": "company_context", "basis": "Aker BP AI remote-operations initiative references Yggdrasil, the same broad development area; it is not the Omega Alfa exploration campaign or its drilling method." }, { "id": "AI-049", "relationship": "company_context", "basis": "Aker BP/Cognite Atlas AI workflow record; no same-campaign technology attribution." } ], "review": { "verdict": "correct", "reason": "Regulator corroborates well outcomes. Keep the scale denominator and dry target visible; no matched conventional-well baseline or cost disclosed; do not attribute to AI.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R02-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Issuer/regulator report a 45-km multi-target campaign over about three months, 40 km in reservoir, discoveries in four wellbores and one dry target (Alfa Sør); reported recoverable resource estimate is 96–134 mmboe. This is a campaign outcome, not a normalized drilling-rate/cost comparison." }, "reason": "Regulator corroborates well outcomes. Keep the scale denominator and dry target visible; no matched conventional-well baseline or cost disclosed; do not attribute to AI.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://akerbp.com/en/borsmelding/significant-oil-discovery-in-the-yggdrasil-area-2/", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 84-106; campaign targets, multilateral approach, drilling length/period, longest branch, resource estimate, partner/asset context.", "date": "2025-08-21" }, { "url": "https://www.sodir.no/en/whats-new/news/exploration-drilling-results/2025/oil-discovery-in-the-yggdrasil-area-251-14-251-14-a-b-c-d-e-f-and-g/", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 302-323; campaign/wellbores, discovery count and volume, five-prospect description; lines 324-348 wellbore-specific results, dry target and planned-TD limit.", "date": "2025-08-22" } ] } ] }, "department": "Subsurface & recovery", "group_id": "T10-R02-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-138", "AI-049" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Drilling began early May 2025 and ran about three months; campaign completion announced 2025-08-21/22." }, { "id": "T10-R05-GLOBAL-01", "company": "Aker BP", "title": "Land-controlled ROV stabilizes Idun North well in one workday", "category": "Subsea remote operations / intervention", "kind": "new_initiative", "ai_role": "No AI contribution disclosed. The evidence concerns remote operating model, communications and a piloted ROV; do not tag as AI adoption.", "asset": "Idun North well, Skarv area, Norwegian Sea; Aker BP and DeepOcean; vessel Dina Star and land remote operations center (Haugesund).", "stage": "Single successful operation; Aker BP calls it the first of its kind and says it aims to repeat the operating model more often.", "operating_period": "Published 2026-06-15; actual operation date not specified.", "claim": "One Idun North well stabilization by gravel placement was controlled from Haugesund using ROV/vessel coordination. “12 hours” is the work duration compared with a traditional full offshore rotation of up to 14 days—not a matched 14-day job-duration baseline. Aker BP says this was first-of-kind and expresses qualitative lower time/cost benefits.", "economics": "Company claims lower time and cost but provides no vessel day rate, intervention cost, personnel count or net realized savings.", "baseline": "Comparison is issuer's typical full offshore rotation (up to 14 days), not a matched prior intervention; task completion reported around 12 hours.", "limits": "This is a single operation and no repeatability, intervention success rate, well integrity outcome, safety comparison, or measured cost baseline is disclosed. The vessel still had an offshore crew; key personnel and ROV operator were onshore.", "relationship": "AI IDs are company-level remote-operation context only; no same-project match identified. The 14-day comparison should not be represented as a proven cost saving or repeated production deployment.", "decision_question": "Can this remote ROV operating model be repeated on routine well-intervention scopes and reduce vessel-days while preserving intervention quality and control?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Styrte undervannsoperasjon fra land – kuttet 14 dager til 12 timer", "publisher": "Aker BP", "date": "2026-06-15", "url": "https://akerbp.com/styrte-undervannsoperasjon-fra-land-kuttet-14-dager-til-12-timer/", "locator": "Lines 86-114; Aker BP archive dates item 15.06.2026", "access": "Direct issuer page opened (Norwegian); archive listing directly/search opened", "supports": "Asset, operation, technique, 12h versus up to 14-day typical rotation, first-of-kind qualifier and intended replication." } ], "references": [ { "id": "AI-049", "relationship": "AI IDs are company-level remote-operation context only; no same-project match identified. The 14-day comparison should not be represented as a proven cost saving or repeated production deployment." }, { "id": "AI-138", "relationship": "AI IDs are company-level remote-operation context only; no same-project match identified. The 14-day comparison should not be represented as a proven cost saving or repeated production deployment." }, { "id": "AI-269", "relationship": "AI IDs are company-level remote-operation context only; no same-project match identified. The 14-day comparison should not be represented as a proven cost saving or repeated production deployment." } ], "review": { "verdict": "correct", "reason": "Direct Norwegian issuer page states the comparison explicitly. Keep remote operations/process design as non-AI unless further evidence names AI; do not convert crew rotation into 14 days of avoided work/cost.", "cross_audits": [ { "assignment": "round-05-global.json", "finding_id": "T10-R05-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-024", "AI-025" ], "added": [ "AI-049", "AI-138", "AI-269" ] } }, "reason": "AI-024/025 are ExxonMobil/Shell; replaced with Aker BP company-context IDs. None is the Idun ROV deployment.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R05-GLOBAL-01", "verdict": "correct", "patch": { "claim": "One Idun North well stabilization by gravel placement was controlled from Haugesund using ROV/vessel coordination. “12 hours” is the work duration compared with a traditional full offshore rotation of up to 14 days—not a matched 14-day job-duration baseline. Aker BP says this was first-of-kind and expresses qualitative lower time/cost benefits.", "comparison_correction": "“Up to 14 days” describes traditional full offshore crew rotation, while 12 hours describes this operation; not a matched duration comparison." }, "reason": "Direct Norwegian issuer page states the comparison explicitly. Keep remote operations/process design as non-AI unless further evidence names AI; do not convert crew rotation into 14 days of avoided work/cost.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://akerbp.com/styrte-undervannsoperasjon-fra-land-kuttet-14-dager-til-12-timer/", "access_status": "Directly reopened primary issuer page in Norwegian in R10; direct translation/exact comparison inspected", "locator": "Lines 86-114; Aker BP archive dates item 15.06.2026", "date": "2026-06-15" } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R05-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-049", "AI-138", "AI-269" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Published 2026-06-15; actual operation date not specified." }, { "id": "T10-R05-GLOBAL-02", "company": "Aker BP", "title": "Aker BP tests a resident inspection drone at Edvard Grieg", "category": "Offshore inspection robotics / remote operations", "kind": "new_initiative", "ai_role": "Issuer describes the solution as a combined robotics, AI and digital milestone but identifies autonomous navigation and sensor collection, not a specific AI model or AI-dependent function. Keep AI role as mentioned but unspecified.", "asset": "Edvard Grieg platform, Norwegian Continental Shelf; resident drone system managed by Aker Solutions from Jåttåvågen control center in Stavanger.", "stage": "First full resident-drone operation on the Norwegian shelf; evidence gathered to develop use cases toward full operational deployment.", "operating_period": "Published 2025-06-02.", "claim": "One remotely controlled offshore drone inspection at Edvard Grieg is reported as a first/demonstration and a learning milestone. No scaled operating coverage, avoided mobilizations, reliability or cost result disclosed; “AI” appears as broad milestone language without a task-specific model/function.", "economics": "No actual inspection time, offshore hours removed, failure rate, CAPEX, operating cost, or realized saving disclosed. Supplier estimate of up to 70% inspection-cost reduction appears in SPE trade press, not adopted here as realized operator value.", "baseline": "No quantified manual inspection or prior mission baseline in issuer release.", "limits": "A successful demonstration is not continuous fleet deployment. No inspection task list, coverage/completeness, image-to-work-order accuracy, weather availability, aviation safety event rate, or specific AI inference is reported.", "relationship": "Same-company AI records are not same deployment. Do not merge into AI transformation; retain as robotics demonstration with AI role unspecified.", "decision_question": "What recurring inspection task and validated defect-detection coverage are needed to move from a successful flight to an operating service with auditable economics?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Aker BP and Aker Solutions complete first remote-controlled offshore drone flight", "publisher": "Aker BP", "date": "2025-06-02", "url": "https://akerbp.com/en/aker-bp-and-aker-solutions-complete-first-remote-controlled-offshore-drone-flight/", "locator": "Lines 81-93; archive listing dated 02.06.2025", "access": "Direct issuer page and archive/search listing opened", "supports": "Named platform, resident system, shore control, sensing/navigation, demonstration stage and limited AI description." } ], "references": [ { "id": "AI-049", "relationship": "Same-company AI records are not same deployment. Do not merge into AI transformation; retain as robotics demonstration with AI role unspecified." }, { "id": "AI-138", "relationship": "Same-company AI records are not same deployment. Do not merge into AI transformation; retain as robotics demonstration with AI role unspecified." }, { "id": "AI-269", "relationship": "Same-company AI records are not same deployment. Do not merge into AI transformation; retain as robotics demonstration with AI role unspecified." } ], "review": { "verdict": "correct", "reason": "Primary issuer/vendor account describes a completed mission, not commercial-scale deployment or attributable AI outcome.", "cross_audits": [ { "assignment": "round-05-global.json", "finding_id": "T10-R05-GLOBAL-02", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-024", "AI-025" ], "added": [ "AI-049", "AI-138", "AI-269" ] } }, "reason": "AI-024/025 are ExxonMobil/Shell; replaced with Aker BP company-context IDs. None is the Edvard Grieg drone demonstration.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R05-GLOBAL-02", "verdict": "correct", "patch": { "claim": "One remotely controlled offshore drone inspection at Edvard Grieg is reported as a first/demonstration and a learning milestone. No scaled operating coverage, avoided mobilizations, reliability or cost result disclosed; “AI” appears as broad milestone language without a task-specific model/function." }, "reason": "Primary issuer/vendor account describes a completed mission, not commercial-scale deployment or attributable AI outcome.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://akerbp.com/en/aker-bp-and-aker-solutions-complete-first-remote-controlled-offshore-drone-flight/", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 81-93; archive listing dated 02.06.2025", "date": "2025-06-02" } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R05-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-049", "AI-138", "AI-269" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Published 2025-06-02." }, { "id": "T10-R05-GLOBAL-03", "company": "Aker BP", "title": "Taurob inspection robot pilot on pre-production Fenris unmanned platform", "category": "Robotics / normally unmanned facility operations", "kind": "new_initiative", "ai_role": "AI not identified in the pilot description; robot collects observations, inspection data, and supports remote operations. Lack of AI mention is not evidence that none is used.", "asset": "Fenris platform, part of Valhall PWP-Fenris project; all access via gangway from service-operation vessel; field production expected Q3 2027.", "stage": "Pre-production pilot begun after platform installation; continuation to operating phase conditional on success.", "operating_period": "Pilot initiated by May 27, 2026; production target Q3 2027.", "claim": "Fenris robot is in pre-production pilot; platform production is expected Q3 2027. Aker BP says scale-up depends on pilot results and explicitly plans evaluation of reliability/availability, usability, HSE and cost-benefit. Do not call it an in-service operating deployment or report savings.", "economics": "No mobilization avoided, costs, availability result or cost-benefit yet reported; issuer says access constraints make visits costly but gives no baseline.", "baseline": "No quantified traditional inspection time/cost or pilot metrics. Pre-production low-risk learning environment.", "limits": "Pilot only, not production performance. Future transfer to Munin/Yggdrasil or brownfields is an ambition, not evidence of replication. Pilot scope/ambition remains adjustable.", "relationship": "Same-company AI/remote operations context only; no same-project record found. Distinct from Edvard Grieg resident drone and Skarv/Idun North ROV operation.", "decision_question": "Will Fenris robot availability and workflow integration reduce vessel-supported platform visits without creating missed-anomaly or maintenance-response risk?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Robot inspections at Fenris: building tomorrow’s operations step by step", "publisher": "Aker BP", "date": "2026-05-27", "url": "https://akerbp.com/en/robot-inspections-at-fenris-building-tomorrows-operations-step-by-step/", "locator": "Lines 85-119; Aker BP archive listing dated 27.05.2026", "access": "Direct issuer page opened; archive listing search opened", "supports": "Asset stage, robot scope, access constraints, evaluation criteria, and conditional scale-up." } ], "references": [ { "id": "AI-049", "relationship": "Same-company AI/remote operations context only; no same-project record found. Distinct from Edvard Grieg resident drone and Skarv/Idun North ROV operation." }, { "id": "AI-138", "relationship": "Same-company AI/remote operations context only; no same-project record found. Distinct from Edvard Grieg resident drone and Skarv/Idun North ROV operation." }, { "id": "AI-269", "relationship": "Same-company AI/remote operations context only; no same-project record found. Distinct from Edvard Grieg resident drone and Skarv/Idun North ROV operation." } ], "review": { "verdict": "correct", "reason": "Direct issuer page confirms pilot and planned production date. It is useful as a stage/measurement-design case; not a realized result.", "cross_audits": [ { "assignment": "round-05-global.json", "finding_id": "T10-R05-GLOBAL-03", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-024", "AI-025" ], "added": [ "AI-049", "AI-138", "AI-269" ] } }, "reason": "AI-024/025 are ExxonMobil/Shell; replaced with Aker BP company-context IDs. None is the Fenris robot pilot.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R05-GLOBAL-03", "verdict": "correct", "patch": { "claim": "Fenris robot is in pre-production pilot; platform production is expected Q3 2027. Aker BP says scale-up depends on pilot results and explicitly plans evaluation of reliability/availability, usability, HSE and cost-benefit. Do not call it an in-service operating deployment or report savings." }, "reason": "Direct issuer page confirms pilot and planned production date. It is useful as a stage/measurement-design case; not a realized result.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://akerbp.com/en/robot-inspections-at-fenris-building-tomorrows-operations-step-by-step/", "access_status": "Directly reopened primary issuer page in R10; pilot/stage passages inspected", "locator": "Lines 85-119; Aker BP archive listing dated 27.05.2026", "date": "2026-05-27" } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R05-GLOBAL-03", "core_company": true, "ai_ids": [ "AI-049", "AI-138", "AI-269" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Pilot initiated by May 27, 2026; production target Q3 2027." }, { "id": "T20-R18-GLOBAL-01", "company": "Aker BP", "title": "Yggdrasil is preparing for commissioning; production remains planned for 2027", "category": "Remote offshore operating model and industrial data foundation", "kind": "update", "ai_role": "Aker BP says AI agents will be used from first production for condition-based maintenance and planning and scaled as solutions mature. As of the sources reviewed, that is a stated start-up plan; no production use or AI performance result is disclosed. Thousands of installed/expected facility sensors feed Cognite Data Fusion, with visualization and control-room workflow as enabling infrastructure, distinct from AI itself.", "asset": "Yggdrasil development, Norwegian North Sea; Hugin A/B, Munin and associated area; Aker BP operator with license partners.", "stage": "Aker BP's Feb 11 2026 call described ongoing subsea hookup, cable/pipeline installation, topside outfitting and commissioning, with start-up in 2027. A subsequent issuer report described a tour of the Stavanger integrated operations center and again said Yggdrasil would be remotely operated from there in 2027. No first production or live remote operations was reported in these sources.", "operating_period": "Aker BP Q4 2025 results-call transcript dated 2026-02-11; later control-center tour page is within the 2026 source window but does not print a publication date in its opened text (indexed as approximately May 2026). Planned operating start remains 2027.", "claim": "In the results-call transcript, Aker BP described the field's continued construction and commissioning path, including subsea spool and pipeline work, power-from-shore cable installation and preparing facilities for start-up. It says the area will start production in 2027 and be remotely operated from the Stavanger integrated operations center. The later issuer page confirms the center had been toured and repeats 2027 as the operating date. Aker BP describes thousands of sensors, Cognite Data Fusion and supplier/AI-agent data sharing; condition-based maintenance and planning agents are planned from start. This confirms stage progression toward commissioning, not realized remote-operation or AI performance.", "economics": "No Yggdrasil-specific operating-center, platform integration, sensor/data-platform, software, cybersecurity or AI cost is disclosed. Aker BP discussed investment-estimate increases for major projects, but the reviewed sources do not attribute those increases to the operating model or AI stack; no technology cost bridge or benefit is supported.", "baseline": "Prior baseline states the same program was under construction/commissioning preparation with 2027 production target. The new call gives detailed construction work and confirms the target, while the later tour establishes that the center is available for demonstration. No actual production, crew reduction, vessel-days, maintenance change or control-room operating window is given.", "limits": "Operator statements and planning disclosures; production is not yet established in these sources. Do not call center tour proof of offshore operating capability or count planned AI use as deployed. The 2027 schedule is a target and may move. Project-wide capex movement cannot be used as the cost of digital/AI components.", "relationship": "Same Yggdrasil remote-operations/data/AI program as canonical AI-138 (Aker BP); this is a dated stage update and no net-new initiative. The distinct physical/data foundation may be described separately in editorial synthesis, but keep all benefits and costs unattributed until operating evidence is reported.", "decision_question": "When first production begins, what share of operations is actually executed remotely, with what offshore crew/vessel and reliability baseline, and which condition-based maintenance or planning agents are active with measured decision quality and economics?", "company_key": "Aker BP", "run": "Rounds 11–20", "disposition": "enrich_existing_ai_138_with_future_status", "sources": [ { "title": "Aker BP Q4 2025 results call transcript", "publisher": "Aker BP", "date": "2026-02-11", "url": "https://akerbp.com/wp-content/uploads/2026/02/aker-bp-2025-q4-transcript.pdf", "locator": "PDF pages 7–8: 2027 start, commissioning activity, remote-operation center and day-one AI plans; pages 12–13 for project cost commentary context.", "access": "Issuer PDF opened directly; relevant pages reviewed", "supports": "Construction/commissioning sequence, target first production year, intended remote operating model and AI planned use; no realized production/AI outcome." }, { "title": "Demonstrated the Future of Oil and Gas Operations for the Minister of Digitalisation", "publisher": "Aker BP", "date": "2026 (page text does not print exact date; indexed as approximately May 2026)", "url": "https://akerbp.com/en/demonstrated-the-future-of-oil-and-gas-operations-for-the-minister-of-digitalisation/", "locator": "Lines 85–100: center tour, 2027 operating target, data infrastructure and prospective AI-agent scope.", "access": "Issuer HTML opened directly; full relevant text available", "supports": "Later confirmation of control-center readiness for demonstration and unchanged prospective 2027 remote-operation/AI plan." } ], "references": [ { "id": "AI-138", "relationship": "Same Yggdrasil remote-operations/data/AI program as canonical AI-138 (Aker BP); this is a dated stage update and no net-new initiative. The distinct physical/data foundation may be described separately in editorial synthesis, but keep all benefits and costs unattributed until operating evidence is reported." } ], "review": { "verdict": "confirmed", "reason": "Directly reopened Aker BP's Feb. 11, 2026 transcript and the 2026 operations-center page. The transcript explicitly says production start and remote operation are planned for 2027, details construction/commissioning work, sensors and Cognite integration, and describes AI condition-based maintenance/planning as planned from start. No live-field outcome is claimed. The record correctly links existing AI-138 and separates platform/facility foundation from AI plan; no correction needed.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R18-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened Aker BP's Feb. 11, 2026 transcript and the 2026 operations-center page. The transcript explicitly says production start and remote operation are planned for 2027, details construction/commissioning work, sensors and Cognite integration, and describes AI condition-based maintenance/planning as planned from start. No live-field outcome is claimed. The record correctly links existing AI-138 and separates platform/facility foundation from AI plan; no correction needed.", "sources_inspected": [ { "url": "https://akerbp.com/wp-content/uploads/2026/02/aker-bp-2025-q4-transcript.pdf", "access": "Directly opened Aker BP issuer PDF", "locator": "PDF p.7 lines 310–342 for construction and 2027 startup; p.8 lines 354–379 for planned remote operation, sensors, data foundation and AI plan." }, { "url": "https://akerbp.com/en/demonstrated-the-future-of-oil-and-gas-operations-for-the-minister-of-digitalisation/", "access": "Directly opened Aker BP issuer HTML", "locator": "Relevant 2026 page passages in originating record, lines 85–100; publication date is not printed in page text." } ], "recommended_disposition": "enrich_existing_ai_138_with_future_status" } ] }, "department": "Data, people & purchasing", "group_id": "T10-R06-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-138" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R06-GLOBAL-01", "company": "Aker BP", "title": "Yggdrasil prepares its data foundation for remote operations", "category": "Industrial data platform / remote operating model", "kind": "update", "ai_role": "AI is layered on top: Aker BP says agents will be used from first production for condition-based maintenance and planning and suppliers may share AI agents. Underlying foundation is sensors, Cognite Data Fusion, visualization and control/operating workflow, not itself an AI model.", "asset": "Yggdrasil development, North Sea; Hugin A, Munin and associated area; operator Aker BP with Equinor and Orlen partners.", "stage": "Construction/commissioning preparation. Yggdrasil first production/centralized operation stated for 2027; digital operations center toured in April 2026.", "operating_period": "As of 2026-04-15, planned for first production in 2027.", "claim": "Sensors/Cognite Data Fusion/integrated operations infrastructure is being prepared for future Yggdrasil production; AI agents are described as a first-production plan, not an already operating field result. Thousands of sensors are planned/being integrated; distinguish installed hardware from completed integrated operations.", "economics": "No Yggdrasil-specific data-platform or integration CAPEX, software fees, cybersecurity/IT cost, staffing baseline or realized production/maintenance benefit disclosed in this source.", "baseline": "No comparable conventional operating-model baseline; production not expected until 2027 per this source.", "limits": "Architecture and intent described by operator, not production evidence. “Without need for manual offshore operations” applies to stated operating capability/ambition and does not establish no offshore personnel or intervention. The AI start date is forward-looking and contingent on production start and solution readiness.", "relationship": "Same project and exact same source URL/date as canonical AI-138 (Aker BP AI agents for Yggdrasil remote operations, source dated 2026-02-11 in register; Aker BP newsroom archive dates article 2026-04-15). This finding emphasizes the data foundation underpinning the AI plan, but is a cross-reference/enrichment to that project, not an additional Yggdrasil deployment.", "decision_question": "What is the all-in cost and operating model to integrate sensor, historian, platform, control system, visualization and supplier access—and how will go-live prove incremental value over a staffed offshore/control-room model?", "company_key": "Aker BP", "run": "Rounds 1–10", "disposition": "enrich_existing", "sources": [ { "title": "Demonstrated the Future of Oil and Gas Operations for the Minister of Digitalisation", "publisher": "Aker BP", "date": "2026-04-15 (newsroom archive listing)", "url": "https://akerbp.com/en/demonstrated-the-future-of-oil-and-gas-operations-for-the-minister-of-digitalisation/", "locator": "Lines 85-100; archive listing dated 15.04.2026", "access": "Direct issuer page and issuer archive listing opened", "supports": "Yggdrasil data architecture, operating center, planned 2027 operation, AI-agent day-one intent and 10+ year foundation context." } ], "references": [ { "id": "AI-138", "relationship": "Same project and exact same source URL/date as canonical AI-138 (Aker BP AI agents for Yggdrasil remote operations, source dated 2026-02-11 in register; Aker BP newsroom archive dates article 2026-04-15). This finding emphasizes the data foundation underpinning the AI plan, but is a cross-reference/enrichment to that project, not an additional Yggdrasil deployment." } ], "review": { "verdict": "correct", "reason": "Same asset/program and source context as AI-138. Consolidate foundation readiness with the canonical record, preserving pre-start stage and avoiding double-counting the agents.", "cross_audits": [ { "assignment": "round-06-global.json", "finding_id": "T10-R06-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-024", "AI-025" ], "added": [ "AI-049", "AI-138", "AI-269" ] } }, "reason": "AI-024/025 are ExxonMobil/Shell; replaced with Aker BP company-context IDs. Yggdrasil data foundation is distinct from listed AI agents/use-cases.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-06-global.json", "finding_id": "T10-R06-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": [ "AI-138" ], "kind": "update", "relationship": "same Yggdrasil project and exact source URL; add foundational-stack detail to AI-138, no net-new initiative" }, "reason": "Production register AI-138 has the same Aker BP Yggdrasil AI-agent initiative and exact source URL as the 15 April 2026 release reopened in this round.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local production register read", "locator": "AI-138 Company, Initiative, Source_URL, Source_date, Implementation" }, { "url": "https://akerbp.com/en/demonstrated-the-future-of-oil-and-gas-operations-for-the-minister-of-digitalisation/", "access": "direct issuer release and archive listing opened", "locator": "lines 85-100; archive 15.04.2026" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R06-GLOBAL-01", "verdict": "correct", "patch": { "canonical_overlap": "AI-138 (Aker BP AI agents for Yggdrasil remote operations). Treat this finding as foundation/control-room context and a deployment-stage update to the same Yggdrasil program, not a separate AI initiative.", "claim": "Sensors/Cognite Data Fusion/integrated operations infrastructure is being prepared for future Yggdrasil production; AI agents are described as a first-production plan, not an already operating field result. Thousands of sensors are planned/being integrated; distinguish installed hardware from completed integrated operations." }, "reason": "Same asset/program and source context as AI-138. Consolidate foundation readiness with the canonical record, preserving pre-start stage and avoiding double-counting the agents.", "recommended_disposition": "enrich_existing", "sources_checked": [ { "url": "https://akerbp.com/en/demonstrated-the-future-of-oil-and-gas-operations-for-the-minister-of-digitalisation/", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 85-100; archive listing dated 15.04.2026", "date": "2026-04-15 (newsroom archive listing)" }, { "url": "site/dist/assets/research-data.json", "access_status": "Local production register directly searched for canonical IDs; exact IDs/titles inspected", "locator": "AI-138 (Aker BP AI agents for Yggdrasil remote operations). Treat this finding as foundation/control-room context and a deployment-stage update to the same Yggdrasil program, not a separate AI initiative.", "date": "accessed 2026-10-07" } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R06-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-138" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "As of 2026-04-15, planned for first production in 2027." }, { "id": "T20-R12-LIMITS-01", "company": "Independent academic authors; public SPE E-Challenge benchmark", "title": "Predicting pump life becomes harder on a different well", "category": "artificial_lift_model_validation", "kind": "context", "ai_role": "Gradient-boosting machine-learning models classify ESP failure and estimate remaining useful life; authors use leave-one-well-out testing to assess transfer to unseen wells.", "asset": "Public SPE E-Challenge dataset; 63 wells retained, including 17 failure wells used in the leave-one-well-out classification analysis.", "stage": "2026 research paper / benchmark evaluation only; no live operator deployment claimed.", "operating_period": "Published to IEEE Xplore 2026-08-17; conference held 2026-08-02 to 2026-08-05.", "claim": "The IEEE abstract says no evaluated remaining-useful-life regression model exceeded R² = 0.24 under leave-one-well-out validation, a test intended to better reflect generalization to previously unseen wells. The best reported classification configuration achieved AUC 0.93 and F1 0.72 on the stated benchmark. These metrics apply to different tasks; they do not prove field performance or contradict other cases without matched data and evaluation design.", "economics": "No deployment cost or economic result; research benchmark only.", "baseline": "Authors contrast leave-one-well-out validation with same-well random splits/cross-validation, which they say can overstate performance for unseen-well deployment. The indexed abstract does not disclose the corresponding same-well metric values.", "limits": "The study is independently verified only to the extent of the IEEE publisher-indexed abstract. Do not imply full paper, methods, feature engineering, confidence intervals or class-specific metrics were audited. No deployment claim.", "relationship": "Distinct from the Baker Hughes 2024 production-asset study: this is a public benchmark and an explicitly cross-well evaluation, not an operator deployment. Do not combine their metrics.", "decision_question": "Can a supplier show performance on held-out wells from the buyer's asset, with a prospective test and a decision threshold tied to avoided deferment and false-alarm/workover cost?", "company_key": "Academic research", "run": "Rounds 11–20", "disposition": "include_as_abstract-level research context; preserve access limitation", "sources": [ { "title": "Cross-Well Validated Binary Classification for ESP Failure Prediction Using Gradient Boosting", "publisher": "IEEE Xplore", "date": "2026-08-17", "url": "https://ieeexplore.ieee.org/abstract/document/11647491/", "locator": "IEEE-indexed abstract and metadata; direct publisher-page open returns HTTP 418", "access": "indexed primary abstract only; direct open failed again in R20", "supports": "LOWO evaluation, public SPE E-Challenge dataset (63 retained wells; 17 failure wells), RUL regression R² ≤0.24, best classification AUC .93/F1 .72, research-only status." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Fresh IEEE search reproduced the abstract and all stated values; direct page reopen again returned HTTP 418. Metrics and denominator are faithfully reported as distinct regression/classification tasks on a 63-well benchmark, not as operating outcomes.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R12-LIMITS-01", "verdict": "confirmed", "patch": { "sources": [ { "title": "Cross-Well Validated Binary Classification for ESP Failure Prediction Using Gradient Boosting", "publisher": "IEEE Xplore", "date": "2026-08-17", "url": "https://ieeexplore.ieee.org/abstract/document/11647491/", "locator": "IEEE-indexed abstract and metadata; direct publisher-page open returns HTTP 418", "access": "indexed primary abstract only; direct open failed again in R20", "supports": "LOWO evaluation, public SPE E-Challenge dataset (63 retained wells; 17 failure wells), RUL regression R² ≤0.24, best classification AUC .93/F1 .72, research-only status." } ], "limits": "The study is independently verified only to the extent of the IEEE publisher-indexed abstract. Do not imply full paper, methods, feature engineering, confidence intervals or class-specific metrics were audited. No deployment claim." }, "reason": "Fresh IEEE search reproduced the abstract and all stated values; direct page reopen again returned HTTP 418. Metrics and denominator are faithfully reported as distinct regression/classification tasks on a 63-well benchmark, not as operating outcomes.", "sources_inspected": [ { "url": "https://ieeexplore.ieee.org/abstract/document/11647491/", "access": "direct open failed HTTP 418; fresh search returned IEEE-indexed primary abstract", "locator": "Publisher abstract and conference/publication metadata" } ], "recommended_disposition": "include_as_abstract-level research context; preserve access limitation" } ] }, "department": "Maintenance & reliability", "group_id": "T20-R12-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Published to IEEE Xplore 2026-08-17; conference held 2026-08-02 to 2026-08-05." }, { "id": "T20-R18-LIMITS-01", "company": "Acceleware Ltd. / Emissions Reduction Alberta-supported project", "title": "RF XL’s demonstration needed more power and further qualification", "category": "enhanced_recovery_electrification", "kind": "negative_evidence", "ai_role": "No AI role; this is radio-frequency subsurface heating and electric recovery technology, included as a physical-technology comparison.", "asset": "Acceleware-owned pilot wellsite at Marwayne, Alberta; commercial-length horizontal well pair and downhole RF XL components intended for heavy oil/oil sands recovery as an alternative to SAGD steam heating.", "stage": "ERA's page header labels the funded project 'Completed' and says the initial demonstration phase concluded in 2023. Its body separately says the ERA-supported pilot was paused, upgrades remained in progress, and restart options were being investigated. The page has no precise last-updated date, so current post-2023 operating status cannot be established from it.", "operating_period": "Demonstration result reported as completed in 2023, outside the 2024-10-07 to 2026-10-07 source window; ERA page accessed 2026-10-07 but update date is not stated.", "claim": "ERA reports that the downhole RF XL system delivered significantly less than planned power because of mechanical and operational implementation issues with the drilled well and did not fully demonstrate the technology. It separately reports full-power operation of the CTI and heat transfer using a commercial-length well pair. More subsurface upgrades and wells were needed. This is incomplete system qualification and added-cost exposure, not proof RF heating is inherently infeasible or that the project was permanently canceled.", "economics": "ERA page lists project value $28.2m and funding $5m; the page does not specify currency. Additional wells are said to add significant cost, without a revised budget. Do not label the values CAD or treat the project value as loss/write-off.", "baseline": "Planned high-power system performance and commercial-scale pilot objective; no numeric planned-versus-achieved kW or production baseline is given on the opened page.", "limits": "Project-funder summary, not an independent engineering report. It gives no detailed root-cause data, test duration, reservoir response, production or cost-per-barrel result. Demonstration concluded in 2023, outside the current evidence window. The page's current status is insufficient to establish whether upgrades/restart later occurred.", "relationship": "Historical physical-technology context only; the only opened page reports a 2023 demonstration and has undated subsequent status text. Exclude from the current dated deployment/failure count unless a newer dated primary status is found.", "decision_question": "What full-scale, multiwell subsurface performance and levelized oil/recovery cost must be demonstrated before an operator accepts the technology, and what additional capital is required after the inverter subsystem is qualified?", "company_key": "Acceleware Ltd.", "run": "Rounds 11–20", "disposition": "background_only_historical; not a current-window deployment or generic technology-failure case", "sources": [ { "title": "Radio Frequency XL (RF XL) Enhanced Oil Recovery", "publisher": "Emissions Reduction Alberta", "date": "Current project page; accessed 2026-10-07; project completion reported 2023", "url": "https://www.eralberta.ca/projects/details/radio-frequency-xl-rf-xl-enhanced-oil-recovery/", "locator": "Lines 7–46", "access": "directly opened project-funder page", "supports": "project type/value/funder amount; Marwayne scope; validated inverter and well-pair elements; lower-than-planned power and mechanical/operational implementation issues; need for upgrades/additional wells/cost; uncertain future commercial status." } ], "references": [], "review": { "verdict": "correct", "reason": "ERA's funder page directly supports both subsystem success and underpowered/incomplete system demonstration. Header project status 'Completed' conflicts with body saying pilot paused and upgrades/restart in progress; distinguish completion of funded demonstration record from current pilot operation. Currency is unstated and page update date absent.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R18-LIMITS-01", "verdict": "correct", "patch": { "stage": "ERA's page header labels the funded project 'Completed' and says the initial demonstration phase concluded in 2023. Its body separately says the ERA-supported pilot was paused, upgrades remained in progress, and restart options were being investigated. The page has no precise last-updated date, so current post-2023 operating status cannot be established from it.", "operating_period": "Demonstration result reported as completed in 2023, outside the 2024-10-07 to 2026-10-07 source window; ERA page accessed 2026-10-07 but update date is not stated.", "economics": "ERA page lists project value $28.2m and funding $5m; the page does not specify currency. Additional wells are said to add significant cost, without a revised budget. Do not label the values CAD or treat the project value as loss/write-off.", "claim": "ERA reports that the downhole RF XL system delivered significantly less than planned power because of mechanical and operational implementation issues with the drilled well and did not fully demonstrate the technology. It separately reports full-power operation of the CTI and heat transfer using a commercial-length well pair. More subsurface upgrades and wells were needed. This is incomplete system qualification and added-cost exposure, not proof RF heating is inherently infeasible or that the project was permanently canceled.", "relationship": "Historical physical-technology context only; the only opened page reports a 2023 demonstration and has undated subsequent status text. Exclude from the current dated deployment/failure count unless a newer dated primary status is found." }, "reason": "ERA's funder page directly supports both subsystem success and underpowered/incomplete system demonstration. Header project status 'Completed' conflicts with body saying pilot paused and upgrades/restart in progress; distinguish completion of funded demonstration record from current pilot operation. Currency is unstated and page update date absent.", "sources_inspected": [ { "url": "https://www.eralberta.ca/projects/details/radio-frequency-xl-rf-xl-enhanced-oil-recovery/", "access": "direct funder page reopened", "locator": "Lines 13–33 (header/value/date), 37–46 (demo, underpower, pause, upgrades, restart and commercial uncertainty)." } ], "recommended_disposition": "background_only_historical; not a current-window deployment or generic technology-failure case" } ] }, "department": "Subsurface & recovery", "group_id": "T20-R18-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R19-GLOBAL-02", "company": "Airbus", "title": "Skywise aviation data platform shows large fleet reach, with limited public outcome attribution", "category": "Industry analog / connected-asset data platform and predictive maintenance", "kind": "context", "ai_role": "Skywise includes data-platform and digital solutions such as predictive maintenance; the annual report does not attribute its reach or qualitative delay/cancellation savings specifically to AI or to one predictive model.", "asset": "Commercial aviation fleet platform connecting Airbus, airlines and suppliers; Airbus reports support for over 11,900 commercial aircraft across Airbus and other OEMs, and support for approximately 54% of Airbus's in-service fleet.", "stage": "Industrialized platform with 55,000 users across Airbus functions and divisions in 2025; external-customer platform usage is described as supporting aircraft operations and maintenance.", "operating_period": "FY2025 adoption and reach; published in Airbus 2025 Board Report in February 2026.", "claim": "Airbus reports Skywise user growth of approximately 16% in 2025 to approximately 55,000 and support for more than 11,900 commercial aircraft (Airbus and other OEMs). It says the platform enables significant annual airline savings by reducing flight delays and cancellations and improves aircraft operational availability, without disclosing dollars, avoided-event denominator, platform-only versus services attribution, or a matched baseline. About 54% of Airbus's in-service fleet was supported by Skywise and related digital solutions, including Health Monitoring, Predictive Maintenance and Fleet Performance.", "economics": "No customer-specific implementation/hosting cost, annual dollar value, number of avoided delays/cancellations, benefit attribution to platform versus OEM services, or payback is disclosed in the annual report section. These claims cannot be carried over to upstream assets.", "baseline": "No flight-delay/cancellation baseline, aircraft cohort comparison or before/after window is specified. Adoption figures are scale metrics, not operating value metrics.", "limits": "Aviation is a cross-industry analogy for connected-asset platforms and adoption reach, not a comparable upstream technology deployment. Fleet count/users do not measure predictive model quality or avoided operating cost. Keep broad platform foundations distinct from AI use cases and from product-specific outcome evidence.", "relationship": "No upstream canonical record; this is an explicitly separate aviation platform analogy. Do not add to upstream deployment counts or use as an oil-and-gas ROI benchmark.", "decision_question": "For an upstream connected-asset platform, what field/asset denominator, active-user measure, operational workflow, cost base and validated before/after outcome can be disclosed beyond platform reach?", "company_key": "Airbus", "run": "Rounds 11–20", "disposition": "include_as_platform_adoption_analog_with_limits", "sources": [ { "title": "Airbus SE Report of the Board of Directors 2025", "publisher": "Airbus", "date": "2026-02 (FY2025 annual report)", "url": "https://www.airbus.com/sites/g/files/jlcbta136/files/2026-02/airbus_se_report_of_the_board_of_directors_fy_2025_1.pdf", "locator": "PDF page 42, lines 1860-1876: platform adoption, aircraft reach, fleet share and stated qualitative savings.", "access": "Issuer PDF opened directly; full relevant section available", "supports": "2025 user/aircraft counts, fleet share, platform capabilities and limits of disclosed savings." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly opened the exact Airbus FY2025 Board Report PDF issued Feb. 18, 2026. It reports ~55,000 users, >11,900 commercial aircraft supported, a ~16% user increase and ~54% of Airbus in-service fleet supported by the Skywise platform and related digital solutions. Its savings statement is qualitative and attributed broadly to Skywise support; it does not provide dollars or a denominator. The record appropriately avoids claiming AI attribution or transferring aviation economics to upstream.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R19-GLOBAL-02", "verdict": "confirmed", "patch": {}, "reason": "Directly opened the exact Airbus FY2025 Board Report PDF issued Feb. 18, 2026. It reports ~55,000 users, >11,900 commercial aircraft supported, a ~16% user increase and ~54% of Airbus in-service fleet supported by the Skywise platform and related digital solutions. Its savings statement is qualitative and attributed broadly to Skywise support; it does not provide dollars or a denominator. The record appropriately avoids claiming AI attribution or transferring aviation economics to upstream.", "sources_inspected": [ { "url": "https://www.airbus.com/sites/g/files/jlcbta136/files/2026-02/airbus_se_report_of_the_board_of_directors_fy_2025_1.pdf", "access": "Directly opened Airbus issuer PDF; exact URL verified after an initial filename mismatch", "locator": "PDF p.42 / lines 1860–1875: Skywise usage, aircraft reach, qualitative savings, related product/fleet coverage." } ], "recommended_disposition": "include_as_platform_adoption_analog_with_limits" } ] }, "department": "Maintenance & reliability", "group_id": "T20-R19-GLOBAL-02", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "FY2025 adoption and reach; published in Airbus 2025 Board Report in February 2026." }, { "id": "T10-R06-LIMITS-01", "company": "Azule Energy / SLB", "title": "Delfi reservoir platform renewal and gradual enterprise-data integration", "category": "Internal software / subsurface workflow and data integration", "kind": "update", "ai_role": "Release frames platform use as digital/software. It does not say Azule deployed AI in the described workflows or attribute a result to AI. Treat as a data/workflow foundation unless more precise evidence emerges.", "asset": "Azule Energy portfolio in Angola; disclosed use sits in reservoir organization and supports reservoir studies, modeling, simulation and well planning. No individual producing asset is identified.", "stage": "Three-year agreement to continue and expand use. It builds on two years of existing reservoir-organization use; enterprise-scale connection to broader operational-data environments is described as occurring over time.", "operating_period": "Prior Delfi use for two years by 2026-04-24 release; extension agreement reported 2026-04-24. Exact initial go-live date and expansion schedule not provided.", "claim": "SLB's 2026-04-24 release reports two years of Delfi use inside Azule's reservoir organization, followed by a three-year agreement to continue/expand. Workflow scope is reservoir studies, modeling, simulation, well planning; larger operational data integration is described as progressive ('over time'). No AI use, enterprise completion, migration cost or customer outcome is disclosed.", "economics": "No contract value, migration/implementation cost, license spend, staffing requirement, NPV, or quantified operational or subsurface performance outcome disclosed.", "baseline": "The source establishes two years of prior use in the reservoir organization before the new agreement. It does not establish how many users, assets, datasets, workflows or systems were included during those two years, nor what was replaced or retained.", "limits": "Supplier/issuer announcement, not customer-authored implementation audit. Renewal and usage duration are not proof of enterprise-wide rollout, workflow adoption depth or operational value. The phrasing 'over time' signals progressive data integration but gives no delivery milestones, sources, standards, migration burden, data-quality controls, owner/accountability, or interoperability test. No inference that the platform operates field equipment or that generative/agentic AI is in use at Azule.", "relationship": "No same-customer initiative was found in the inspected technology-scope register/baseline search. Related in concept to other enterprise data foundations and SLB digital-platform records, but project and customer evidence here is specifically Azule/Delfi. Treat as an enabling software/workflow layer, not a production technology or AI outcome.", "decision_question": "What systems and datasets are actually connected, which workflows are routinely used by asset teams, who owns data quality and change management, and what measured value justified renewal after the first two years?", "company_key": "Azule Energy", "run": "Rounds 1–10", "disposition": "include as supplier-reported renewal/adoption context; not a quantified outcome", "sources": [ { "title": "SLB Announces First-Quarter 2026 Results", "publisher": "SLB / U.S. SEC", "date": "2026-04-24", "url": "https://www.sec.gov/Archives/edgar/data/87347/000119312526174940/d111579dex99.htm", "locator": "Lines 9–36 (release date); 486–503, specifically 491–493 (Azule duration, workflows, contract and integration wording); 971–979 (forward-looking statement caveat)", "access": "Primary SEC-hosted issuer release opened directly", "supports": "Dated three-year platform agreement, two years prior use in reservoir organization, supported workflows and gradual broader integration. No customer KPI or contract value is provided." } ], "references": [], "review": { "verdict": "confirm", "reason": "Direct SEC filing review confirms exact wording/date. Data foundation/workflow software, not field operating technology. The integration wording is not proof of completed enterprise integration.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R06-LIMITS-01", "verdict": "confirm", "patch": { "claim": "SLB's 2026-04-24 release reports two years of Delfi use inside Azule's reservoir organization, followed by a three-year agreement to continue/expand. Workflow scope is reservoir studies, modeling, simulation, well planning; larger operational data integration is described as progressive ('over time'). No AI use, enterprise completion, migration cost or customer outcome is disclosed.", "canonical_overlap": "No same-customer project in inspected register; distinguish from SLB platform supplier records generally." }, "reason": "Direct SEC filing review confirms exact wording/date. Data foundation/workflow software, not field operating technology. The integration wording is not proof of completed enterprise integration.", "recommended_disposition": "include as supplier-reported renewal/adoption context; not a quantified outcome", "sources_checked": [ { "url": "https://www.sec.gov/Archives/edgar/data/87347/000119312526174940/d111579dex99.htm", "access_status": "primary issuer SEC exhibit reopened directly", "date": "2026-04-24", "locator": "lines 9–36 and 491–493" } ] } ] }, "department": "Subsurface & recovery", "group_id": "T10-R06-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R11-LIMITS-01", "company": "Baker Hughes / unnamed major Americas operator", "title": "An ESP model missed half the failed pumps in its test", "category": "artificial_lift_model_validation", "kind": "negative_evidence", "ai_role": "Ensemble combines XGBoost failure classifiers with reliability models and engineering damage rules; engineers review daily remaining-life rankings and choose interventions.", "asset": "Three unnamed Americas fields; 137 pumps in the full dataset. The failed-pump test denominator is inferred from the reported split and sensitivity.", "stage": "The authors report client-approved deployment with daily predictions for currently running ESPs after the retrospective evaluation. The paper is supplier-authored and does not provide independent operator corroboration.", "operating_period": "Paper presented October 2024; underlying pump records are historical.", "claim": "A Baker Hughes paper reports 50% sensitivity, 78% specificity and 64% balanced accuracy. Nine failed pumps were missed; five involved short circuits. Nine misses at 50% sensitivity imply 18 failed-pump test cases. The authors identify insufficient SCADA resolution as a constraint.", "economics": "One supplier-reported workover case claims $4.3m of reduced deferred production. It is not fleet-wide, recurring or net of full deployment costs.", "baseline": "The retrospective test uses the paper’s own alarm definitions. Maintenance or optimization after an alarm can change how a false alarm is classified.", "limits": "Anonymous operator, small test and supplier authorship. The paper reports subsequent deployment; this is a measured model limitation rather than evidence of abandonment. There is no prospective controlled comparison or complete cost disclosure.", "relationship": "This is a new technical limitation observation, not a separate named operator deployment; do not merge with broader supplier platform claims without evidence that they refer to the same project.", "decision_question": "What prospective sensitivity and false-alarm rate can the vendor demonstrate on a new asset using its actual installed SCADA resolution, and what incremental sensor or edge-compute cost is needed to address the short-circuit misses?", "company_key": "Baker Hughes", "run": "Rounds 11–20", "disposition": "include_qualified_model_limit; retain as a model/data limitation, not a technology-failure case", "sources": [ { "title": "An Artificial Intelligent Cutting-Edge Technology for Automated Field Production Optimization & ESP Failures Prediction (SPE-221571-MS)", "publisher": "Society of Petroleum Engineers; paper by Baker Hughes authors", "date": "2024-10-29/30", "url": "https://dam.bakerhughes.com/asset/2145a967-01f1-4ffa-8ee1-37b085e6fff1/spe-221571-ms-bkr-licensed.pdf", "locator": "PDF pp. 1–2 (scope and prior methods); pp. 4–6 (population, split, metrics, confusion matrix and performance); p. 6 (SCADA-resolution limitation); pp. 8–10 (operationalization and individual examples).", "access": "directly opened primary PDF", "supports": "conference date; anonymous operator and three assets; 137-pump population, 83-failure training set, evaluation; definitions and reported TPR/TNR/balanced accuracy; nine missed failures and five short circuits; SCADA limitation; deployment statement; single $4.3m case claim." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct full-PDF audit confirms all core claims and reveals that the test denominator should be made explicit: remaining 54 pumps after 83 training failures, including 18 failed (inferred from 9 misses at TPR .50) and 36 running. The paper's own event rules classify some intervened wells as TN, so a causal/prevented-failure caveat is material. $4.3m is a single case claim.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R11-LIMITS-01", "verdict": "correct", "patch": { "asset": "Three unnamed Americas fields; 137 ESPs total (101 failed and 36 still running). The authors say 83 of 101 failed pumps were used for model training and the remaining pumps were used for testing; this implies 18 failed pumps and 36 still-running pumps in the test set.", "claim": "The paper reports TPR 0.50, TNR 0.78 and balanced accuracy 0.64 using its stated event definitions. Nine failed-pump alarms were missed; with TPR 0.50 this implies 18 failed-pump test cases. Five of the nine misses were short circuits. The authors attribute some electrical misses to insufficient SCADA resolution. A scheduled maintenance or optimization action can cause a case to count as true negative under their definition, which affects the false-alarm metric. The retrospective test does not show a failed deployment; the paper separately says client-approved daily RUL deployment followed.", "economics": "The $4.3m claim is one supplier-reported deferred-production amount tied to a workover scheduled two weeks ahead after a detected grounded-sensor alarm; it is not fleet-wide or recurring ROI. No complete model/system cost disclosed." }, "reason": "Direct full-PDF audit confirms all core claims and reveals that the test denominator should be made explicit: remaining 54 pumps after 83 training failures, including 18 failed (inferred from 9 misses at TPR .50) and 36 running. The paper's own event rules classify some intervened wells as TN, so a causal/prevented-failure caveat is material. $4.3m is a single case claim.", "sources_inspected": [ { "url": "https://dam.bakerhughes.com/asset/2145a967-01f1-4ffa-8ee1-37b085e6fff1/spe-221571-ms-bkr-licensed.pdf", "access": "direct full primary PDF reopened", "locator": "pp. 4–6: 137 population; 83 failed pumps trained; definitions and .50/.78/.64; nine misses/five short circuits; client-approved deployment. p. 10: two-week schedule and $4.3m single-event claim." } ], "recommended_disposition": "include_qualified_model_limit; retain as a model/data limitation, not a technology-failure case" } ] }, "department": "Maintenance & reliability", "group_id": "T20-R11-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Paper presented October 2024; underlying pump records are historical." }, { "id": "AR-CNOOC-01", "company": "CNOOC", "title": "Typhoon-mode controls help keep offshore production running", "category": "Remote production continuity", "kind": "update", "ai_role": "AI supports the wider emergency-response system; the reported recovery is attributed to typhoon mode and upgraded controls, not to AI alone.", "asset": "Offshore production; passage discusses Shenhai-1 but the recovery figure is not explicitly field-specific.", "stage": "Operating system described in the 2025 interim report", "operating_period": "Cumulative operating period not specified; report published 2025-09-09.", "claim": "CNOOC reports that upgraded controls allow production during typhoons and that typhoon mode cumulatively recovered production losses exceeding 600,000 tonnes of oil equivalent.", "economics": "No project cost, cash benefit or AI-specific return disclosed.", "baseline": "The loss-estimation method and comparison events are not disclosed.", "limits": "Cumulative start date, event set and independent validation are not supplied. This is a broader control-system result; it is neither annual production nor an isolated AI gain. The sentence does not explicitly restrict that cumulative figure to Shenhai-1.", "relationship": "Further operating context for existing AI-145, not a new initiative.", "decision_question": "How much shutdown time did the upgraded controls avoid, and what part required AI rather than remote instrumentation and operating procedures?", "company_key": "CNOOC", "run": "Focused report review", "disposition": "update_existing", "sources": [ { "title": "CNOOC 2025 Interim Report", "publisher": "CNOOC Limited", "date": "2025-09-09", "url": "https://www.cnoocltd.com/english/investorrelations/reports/interimreport/202509/P020250909591355146082.pdf", "locator": "Printed p. 15 / PDF page index 15, Scientific and Technological Innovation", "access": "Full operator-hosted report opened by researcher and editor; relevant passage reviewed.", "supports": "Shenhai-1 response system and cumulative typhoon-mode recovered losses." } ], "references": [ { "id": "AI-145", "relationship": "Further same-company operating context; bundled control-system result, not an isolated AI outcome." } ], "review": { "verdict": "Admit with attribution boundary", "reason": "Editor reopened full primary report; keep broad-system production metric outside AI-specific outcome count.", "cross_audits": [] }, "department": "Production & process operations", "group_id": "AR-CNOOC-01", "core_company": true, "ai_ids": [ "AI-145" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Cumulative operating period not specified; report published 2025-09-09." }, { "id": "T20-R13-GLOBAL-01", "company": "CNOOC Limited", "title": "Enping 15-1 adds offshore CO₂ reinjection for oil recovery", "category": "offshore process technology / CO2 capture and reservoir reinjection / enhanced recovery", "kind": "new_initiative", "ai_role": "No AI is attributed to the capture, separation or injection mechanism. The disclosed technology is physical process equipment and reservoir injection; AI involvement in other Enping workflows is unknown.", "asset": "Enping 15-1, South China Sea.", "stage": "Commissioned in 2025. The earlier CCS demonstration started in 2023; this note covers the later CCUS phase.", "operating_period": "2025 commissioning; interim report published 9 September 2025.", "claim": "CNOOC’s 2025 interim report confirms that Enping 15-1’s offshore CCUS project entered operation. It combines reservoir carbon storage with oil recovery. The report does not quantify actual injection, incremental oil or operating costs.", "economics": "No project cost, cost per tonne captured or measured oil increment is disclosed in the reviewed passage.", "baseline": "No Enping-specific pre-CCUS emissions/production baseline or matched counterfactual disclosed in the directly opened interim report passage.", "limits": "The available passage confirms commissioning and the broad mechanism. It does not establish the exact startup day or performance. An earlier research source referred to Bozhong 26-6; its capacity and production forecasts belong to that other field and were removed.", "relationship": "No Enping 15-1 or CNOOC production-register match found in the checked baseline or earlier consolidated research. Earlier global research included other operators' CCUS but not this same named project. This is distinct physical infrastructure, not an AI initiative.", "decision_question": "What are measured annual capture/injection volumes, purity and uptime, incremental oil attributable to injection, monitoring/permanence requirements, and project capex/opex per net stored tonne versus the pre-injection baseline?", "company_key": "CNOOC", "run": "Rounds 11–20", "disposition": "correct_then_include_with_limits", "sources": [ { "title": "Interim Report 2025", "publisher": "CNOOC Limited", "date": "2025-09-09", "url": "https://www.cnoocltd.com/english/investorrelations/reports/interimreport/202509/P020250909591355146082.pdf", "locator": "PDF p.9 / lines 249–255 confirms commissioning of the offshore CCUS project in Enping 15-1; PDF p.15 / lines 395–433 per originating record for broader technical wording.", "access": "Directly opened CNOOC primary PDF; p.9 claim passage inspected.", "supports": "Correct Enping project identity and 2025 commissioning; does not verify Bozhong metrics or quantify Enping performance." }, { "title": "CNOOC Limited Brings On-stream Bozhong 26-6 Oilfield Development Project (Phase I)", "publisher": "CNOOC Limited", "date": "2025-02-07", "url": "https://www.cnoocltd.com/english/presscenter/pressreleases/2025/202502/t20250206_112957.html", "locator": "Lines 13–26 identifies Bozhong 26-6 and its Phase I metrics.", "access": "Directly opened CNOOC primary HTML; asset identity and metric passage inspected.", "supports": "Establishes that the originally cited 33-well and 22,300 boe/d project numbers belong to Bozhong 26-6, not Enping 15-1." } ], "references": [], "review": { "verdict": "correct", "reason": "Directly opened the linked release and found it names Bozhong 26-6, not Enping 15-1; it describes Phase I oilfield startup and its own 33 planned wells/~22,300 boe/d forecast. Separately reopened CNOOC's 2025 interim report, which directly confirms the offshore CCUS project at Enping 15-1 was commissioned. Thus the general 2025 commissioning/method direction is supportable, but the current source list, stage, date and imported design/economic figures are materially mismatched. CNOOC's actual distinction is earlier CCS commissioning in 2023 versus 2025 CCUS-to-EOR phase; the earlier CCS lifetime capacity cannot be carried into the 2025 claim without a matching source.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R13-GLOBAL-01", "verdict": "correct", "patch": { "title": "Enping 15-1 offshore CCUS commissioning confirmed in 2025; linked Bozhong development metrics belong to another asset", "asset": "Enping 15-1 platform, South China Sea. The 2025 interim report confirms the offshore CCUS project was put into operation at Enping 15-1. The Feb. 2025 release linked in the originating finding concerns Bozhong 26-6 Phase I, not Enping.", "stage": "CNOOC's 2025 interim report confirms the Enping 15-1 offshore CCUS project was commissioned/put into operation during 2025. Enping's earlier CCS demonstration was commissioned in 2023; the 2025 update is the CCUS oil-recovery phase. Do not describe this as Enping Phase I oilfield production commencing in February 2025.", "operating_period": "CCUS commissioning reported for 2025 in CNOOC's interim report dated 2025-09-09. Earlier CCS project commissioning was in 2023 (background history). Exact 2025 startup day and operating capture/injection rates are not established by the directly opened CNOOC interim excerpt.", "claim": "CNOOC's 2025 interim report says China's first offshore CCUS project was put into operation at Enping 15-1 and describes carbon-driven oil recovery and reservoir carbon sequestration. The Feb. 2025 Bozhong 26-6 release cited in the original record is a different asset; its 33 planned development wells and ~22,300 boe/d peak-production forecast must be removed from Enping's claim. The Enping-specific operating capture/injection rate and incremental oil result are not established by the directly opened interim report.", "economics": "No Enping CCUS capital, operating cost, verified capture cost per tonne or measured oil increment is established by the directly opened interim report. The ~1.5 Mt lifetime figure in the incorrect Bozhong source cannot be assigned to Enping. Any Enping-specific storage or incremental-production target must be cited to an Enping-specific primary source and kept as forecast.", "baseline": "No Enping-specific pre-CCUS emissions/production baseline or matched counterfactual disclosed in the directly opened interim report passage.", "limits": "The originating February source is a Bozhong 26-6 Phase I release, not an Enping source; remove all project design, well-count and peak-production figures derived from it. CNOOC's 2025 interim report directly confirms Enping CCUS commissioning and broad mechanism only; no quantified performance or cost result is verified here. Earlier 2023 CCS storage in a saline formation is distinct from the 2025 CCUS-to-EOR phase.", "sources": [ { "title": "Interim Report 2025", "publisher": "CNOOC Limited", "date": "2025-09-09", "url": "https://www.cnoocltd.com/english/investorrelations/reports/interimreport/202509/P020250909591355146082.pdf", "locator": "PDF p.9 / lines 249–255 confirms commissioning of the offshore CCUS project in Enping 15-1; PDF p.15 / lines 395–433 per originating record for broader technical wording.", "access": "Directly opened CNOOC primary PDF; p.9 claim passage inspected.", "supports": "Correct Enping project identity and 2025 commissioning; does not verify Bozhong metrics or quantify Enping performance." }, { "title": "CNOOC Limited Brings On-stream Bozhong 26-6 Oilfield Development Project (Phase I)", "publisher": "CNOOC Limited", "date": "2025-02-07", "url": "https://www.cnoocltd.com/english/presscenter/pressreleases/2025/202502/t20250206_112957.html", "locator": "Lines 13–26 identifies Bozhong 26-6 and its Phase I metrics.", "access": "Directly opened CNOOC primary HTML; asset identity and metric passage inspected.", "supports": "Establishes that the originally cited 33-well and 22,300 boe/d project numbers belong to Bozhong 26-6, not Enping 15-1." } ] }, "reason": "Directly opened the linked release and found it names Bozhong 26-6, not Enping 15-1; it describes Phase I oilfield startup and its own 33 planned wells/~22,300 boe/d forecast. Separately reopened CNOOC's 2025 interim report, which directly confirms the offshore CCUS project at Enping 15-1 was commissioned. Thus the general 2025 commissioning/method direction is supportable, but the current source list, stage, date and imported design/economic figures are materially mismatched. CNOOC's actual distinction is earlier CCS commissioning in 2023 versus 2025 CCUS-to-EOR phase; the earlier CCS lifetime capacity cannot be carried into the 2025 claim without a matching source.", "sources_inspected": [ { "url": "https://www.cnoocltd.com/english/presscenter/pressreleases/2025/202502/t20250206_112957.html", "access": "Directly opened; confirms source is for Bozhong 26-6", "locator": "Lines 13–26: Bozhong title, Feb. 2025 Phase I startup, planned wells, forecast and operator." }, { "url": "https://www.cnoocltd.com/english/investorrelations/reports/interimreport/202509/P020250909591355146082.pdf", "access": "Directly opened primary issuer PDF", "locator": "PDF p.9, lines 249–255: Enping 15-1 commissioning stated in 2025 interim report." }, { "url": "https://www.cnoocltd.com/english/sustainability/environmentalsocialandgovernancereports/material/2025ESGen.pdf", "access": "Primary issuer PDF direct-open failed because file exceeds retrieval limit; search-indexed excerpt only", "locator": "Indexed excerpt states May 2025 Enping 15-1 CCUS commissioning and future injection/oil-production estimates; not used to assert measured outcomes." } ], "recommended_disposition": "correct_then_include_with_limits" } ] }, "department": "Water, emissions & energy", "group_id": "T20-R13-GLOBAL-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 commissioning; interim report published 9 September 2025." }, { "id": "R1-GL-02", "company": "Canadian Natural Resources (CNRL)", "title": "Commercial-scale solvent-assisted SAGD at Kirby North", "category": "recovery / thermal process method", "kind": "new_initiative", "ai_role": "None disclosed.", "asset": "Kirby North, Athabasca oil sands, Alberta; related pilot evidence comes from Kirby South and Primrose, which are separate assets/stages.", "stage": "Commercial-scale Kirby North solvent pad continues operating in Q1 2026 per issuer May7 2026 update, reopened by root after Round3 review. Later status not checked. The separate Kirby South pilot was targeting Q2 2026 injection; actual start is not established.", "operating_period": "Evidence source: April 2025 CNRL corporate presentation, p. 54; Kirby North operation began 2024-06. Older background: Kirby South pilot reported in an undated company case study; do not treat it as the commercial-pad outcome.", "claim": ">80% is the fraction of solvent recovered, not energy savings, SOR reduction, GHG reduction, or cash savings. The 40-50% SOR and approximately $1/bbl figures are listed as expected benefits, not demonstrated Kirby North outcomes.", "economics": "Commercial pad capex, solvent purchase/recycle cost, incremental facility cost, and actual per-barrel savings not disclosed.", "baseline": "No Kirby North matched-well before/after SOR or realized cost baseline is disclosed. Keep older Kirby South pilot results separate.", "limits": "Solvent recovery fraction alone does not demonstrate net energy, emissions, production, or cash benefit. Commercial-pad monitoring was still in progress. Do not transfer the pilot outcome or stated target to Kirby North or the full asset base.", "relationship": "Commercial operating solvent-SAGD is a genuine non-AI recovery/process alternative; report >80% solvent recovery as observed and keep SOR/cost benefits as targets absent a pad-specific bridge.", "decision_question": "What is net solvent cost and cash margin per incremental barrel after solvent make-up, recovery, energy, throughput, and matched-pad SOR are included?", "company_key": "Canadian Natural Resources", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "Corporate Presentation, April 2025", "publisher": "Canadian Natural Resources", "date": "2025-04 (exact publication day not stated)", "url": "https://www.cnrl.com/content/uploads/2025/04/WView_Corp-Pres_04.pdf", "locator": "Printed p. 54, 'Technology & Innovation with Solvents: SAGD & CSS'", "access": "Issuer-hosted PDF; indexed text accessible", "supports": "Kirby North injection timing and >80% recovery reported to date; ~1/bbl and SOR reduction listed as benefits/targets; monitoring period." }, { "title": "Case Study: Solvent Enhanced Oil Recovery", "publisher": "Canadian Natural Resources", "date": "Undated web page; accessed 2026-10-07", "url": "https://www.cnrl.com/case-studies/case-study-solvent-enhanced-oil-recovery/", "locator": "Kirby South pilot; Kirby North plan; Primrose pilot description", "access": "Issuer page opened via indexed search text; publication date not established", "supports": "Mechanism and historical pilot outcomes, kept separate from commercial-scale Kirby North results." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-04 (day not stated)", "url": "https://www.cnrl.com/content/uploads/2025/04/WView_Corp-Pres_04.pdf", "locator": "Printed p.54, Kirby North solvent recovery and stated benefits", "access": "issuer-hosted PDF direct retrieval unavailable; indexed issuer text reviewed", "supports": "The commercially relevant evidence is ongoing operation and solvent recovery. The tempting economic numbers are benefits/targets. Older pilot results cannot be transferred to this pad. A later status update was not confirmed in this audit." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-05-08", "url": "https://www.cnrl.com/content/uploads/2025/05/Q125-Interim-Report.pdf", "locator": "Printed p.6, commercial-scale Kirby North pad, injection start, >80% solvent recoveries, workovers and monitoring", "access": "issuer-hosted PDF opened", "supports": "The commercially relevant evidence is ongoing operation and solvent recovery. The tempting economic numbers are benefits/targets. Older pilot results cannot be transferred to this pad. A later status update was not confirmed in this audit." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-08", "url": "https://www.cnrl.com/content/uploads/2025/08/WV_Corp-Pres_Aug.pdf", "locator": "Printed p.56; >80% solvent recovery; 40-50% SOR and ~$1/bbl listed as benefits", "access": "issuer-hosted presentation indexed text reviewed", "supports": "The commercially relevant evidence is ongoing operation and solvent recovery. The tempting economic numbers are benefits/targets. Older pilot results cannot be transferred to this pad. A later status update was not confirmed in this audit." }, { "title": "Additional root primary-source check", "publisher": "Canadian Natural Resources", "date": "Date not established", "url": "https://www.sec.gov/Archives/edgar/data/1017413/000101741325000043/a06302025q2pressrelease.htm", "locator": "Printed p.8, thermal in-situ section, lines229-230", "access": "Issuer Q2 2025 results on SEC opened; relevant full text reviewed.", "supports": "Q2 2025 issuer update confirms injection began June2024 and workovers on two well pairs were executed in Q2 2025, with production/SOR/solvent-recovery trends to be monitored." }, { "title": "Additional root primary-source check", "publisher": "Canadian Natural Resources", "date": "Date not established", "url": "https://www.cnrl.com/content/uploads/2026/05/0507-Q126-Front-End.pdf", "locator": "Printedp5 lines166-172; May7datelineonp1", "access": "Primary issuer PDF opened by root after Round3 draft review; printedp5 relevanttext reviewed.", "supports": "Q1 2026 issuer report says commercialKirbyNorthsolventSAGDpad andPrimrosesteamfloodpilot continueoperating. SeparateKirbySouthpilot targetsinjectionQ2 2026." } ], "references": [ { "id": "AI-098", "relationship": "company_context" }, { "id": "AI-279", "relationship": "company_context" } ], "department": "Subsurface & recovery", "group_id": "R1-GL-02", "core_company": true, "ai_ids": [ "AI-098", "AI-279" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R01-LIMITS-02", "company": "Canadian Natural Resources (CNRL)", "title": "Kirby North solvent SAGD remains reported operating through Q1 2026; Q2 reporting is silent on its status", "category": "thermal recovery / solvent co-injection", "kind": "update", "ai_role": "No AI role disclosed; physical reservoir/process technology.", "asset": "Kirby North commercial-scale solvent SAGD pad; distinct from Primrose steam-flood solvent pilot and Kirby South solvent/diluent pilot.", "stage": "Q1 2026 is latest explicit confirmation found for Kirby North commercial pad operation. Q2 2026 leaves Kirby North unaddressed; separate Kirby South pilot has diluent injection target Q1 2027 following strong new-well production. No current Kirby North status/performance or solvent economics disclosed.", "operating_period": "Kirby North first solvent injection June 2024. Q2/25 workovers executed on two well pairs; Q1/26 operation explicitly reconfirmed. Latest Q2/26 update reviewed omits current Kirby North status.", "claim": "The latest direct evidence found for Kirby North is “continues to operate” in Q1 2026 issuer report, not a Q2 update. Do not infer ceased operation from omission in Q2 report, or assert it continued in Q2. The Q2/26 release reports pilot-stage Kirby South target shifted to Q1/27; production performance cited is from new wells, not solvent-pilot results. The well/pad labels and solvent versus diluent terms must remain separate.", "economics": "No Kirby North realized SOR reduction, solvent recovery update, net cost savings, or GHG performance in Q1/26/Q2/26 updates reviewed. Historical >80% solvent recovery is from 2025 disclosures. Benefits of 40-50% SOR and ~$1/bbl remain targets/benefits, not demonstrated current commercial-pad outcomes.", "baseline": "No current matched-pair/control-pad baseline or full solvent purchase/recycle/steam cost disclosed.", "limits": "Do not call this a failure, successful economic scale-up, or current Q2 operating status without a newer explicit source. Preserve chronology: Q1/26 active; Q2/26 report does not restate status; Kirby South Q1/27 remains a target. Root-source-checks.json contains root’s explicit May 7 Q1 2026 source check; this task reopened that same issuer PDF and then checked the newer Q2 issuer/SEC release.", "relationship": "Status update to the existing CNRL solvent-SAGD case, not a new technology or initiative. Q1/26 confirmation supersedes Q2/25 as latest explicit Kirby North operating confirmation; Q2/26 omission must not be represented as a status change.", "decision_question": "Will CNRL disclose current pad SOR, production, solvent-recovery fraction, solvent losses/recycle cost, realized cash/steam savings and matched baseline—and does the separate Kirby South diluent pilot proceed in Q1/27?", "company_key": "Canadian Natural Resources", "run": "Rounds 1–10", "disposition": "include as update with explicit Q1/Q2 chronology", "sources": [ { "title": "2026 First Quarter Results, front-end release", "publisher": "Canadian Natural Resources", "date": "2026-05-07", "url": "https://www.cnrl.com/content/uploads/2026/05/0507-Q126-Front-End.pdf", "locator": "Printed p.5, thermal in-situ section, lines 166-172; report date p.1", "access": "Official issuer PDF opened directly", "supports": "Kirby North commercial pad and Primrose solvent steam-flood pilot continue operating; separate Kirby South pilot targeting injection in Q2/26 at that time." }, { "title": "Canadian Natural Resources Limited Announces 2026 Second Quarter Results", "publisher": "Canadian Natural Resources / SEC EDGAR Form 6-K exhibit", "date": "2026-08-06", "url": "https://www.sec.gov/Archives/edgar/data/1017413/000101741326000043/a06302026q2pressrelease.htm", "locator": "Printed p.5 / webpage lines 192-193; six months ended June 30, 2026", "access": "SEC issuer filing opened directly", "supports": "Q2/26 discloses solvent-EOR objective and Kirby South pilot target: diluent injection Q1/27 after new-well production performance; does not restate Kirby North operating status or current performance." }, { "title": "Canadian Natural Q2 2025 issuer results", "publisher": "Canadian Natural Resources / SEC EDGAR", "date": "2025-08-07", "url": "https://www.sec.gov/Archives/edgar/data/1017413/000101741325000043/a06302025q2pressrelease.htm", "locator": "Printed p.8, thermal in-situ section", "access": "Primary source available via explicit prior source check and official search result; previous Round 3 review documents Q2 workover wording", "supports": "Workovers on two Kirby North well pairs in Q2/25 and continued monitoring; source basis for historical chronology only." } ], "references": [ { "id": "R1-GL-02", "relationship": "Status update to the existing CNRL solvent-SAGD case, not a new technology or initiative. Q1/26 confirmation supersedes Q2/25 as latest explicit Kirby North operating confirmation; Q2/26 omission must not be represented as a status change." } ], "review": { "verdict": "confirm", "reason": "Q1 and Q2 issuer sources were directly reopened. The chronology, different assets and different solvent/diluent stages are handled correctly. Preserve root's source attribution in root-source-checks; do not represent Q1 status as Q2 confirmation.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R01-LIMITS-02", "verdict": "confirm", "patch": { "stage": "Q1 2026 is latest explicit confirmation found for Kirby North commercial pad operation. Q2 2026 leaves Kirby North unaddressed; separate Kirby South pilot has diluent injection target Q1 2027 following strong new-well production. No current Kirby North status/performance or solvent economics disclosed.", "failure_classification": "no failure evidence; Q2 source silence is a coverage/status gap, not evidence of cessation." }, "reason": "Q1 and Q2 issuer sources were directly reopened. The chronology, different assets and different solvent/diluent stages are handled correctly. Preserve root's source attribution in root-source-checks; do not represent Q1 status as Q2 confirmation.", "recommended_disposition": "include as update with explicit Q1/Q2 chronology", "sources_checked": [ { "url": "https://www.cnrl.com/content/uploads/2026/05/0507-Q126-Front-End.pdf", "access_status": "primary issuer PDF opened directly", "date": "2026-05-07", "locator": "printed p.5, lines 166–172: Kirby North/Primrose operating, Kirby South target then Q2/26" }, { "url": "https://www.sec.gov/Archives/edgar/data/1017413/000101741326000043/a06302026q2pressrelease.htm", "access_status": "primary issuer 6-K/SEC release opened and searched directly", "date": "2026-08-06", "locator": "printed p.5 / web lines 183–193: Kirby South diluent target Q1/27; no North update" }, { "url": "https://www.sec.gov/Archives/edgar/data/1017413/000101741325000043/a06302025q2pressrelease.htm", "access_status": "prior round/root check; historical only", "date": "2025-08-07", "locator": "printed p.8, workovers on two well pairs per R02/R03 saved audit" } ] } ] }, "department": "Subsurface & recovery", "group_id": "R1-GL-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R16-GLOBAL-01", "company": "Compañía General de Combustibles (CGC)", "title": "CGC standardizes post-acquisition enterprise systems and process governance", "category": "Enterprise applications and process governance (upstream operating foundation)", "kind": "context", "ai_role": "No AI role is disclosed. SAP Cloud ERP Private is the central ERP; SAP LeanIX inventories applications/integrations, SAP Signavio maps process workflows, SAP Enable Now supports user training, and SAP UEM tracks application adoption. These are digital foundations and change-management tools, not evidence of an AI deployment.", "asset": "Company-wide CGC enterprise systems, including the Argentine producer's upstream business acquired from Sinopec Argentina and Petrobras Argentina; not a named producing field or reservoir workflow.", "stage": "SAP customer story describes a transformation implemented and in use, with next-phase real-time process control-tower capabilities still planned. No start, go-live or completion date is disclosed in the article; its URL places it in SAP's 2025/09 asset path.", "operating_period": "Undated case-story implementation; the page itself prints no publication or go-live date. Its URL contains a 2025/09 asset path, which does not establish publication date. In-window timing is therefore unverified.", "claim": "CGC consolidated a fragmented post-acquisition application/process landscape around SAP Cloud ERP Private, documented integrations and mapped more than 100 critical processes. It reports fewer than 70 customizations, compared with a stated industry average of 550 for ERP programs of this size, and says aligned procurement workflows replaced inconsistent legacy practices. This supports system/process standardization and acquisition-integration capability, not an upstream production outcome.", "economics": "No implementation cost, recurring license/hosting spend, procurement savings, labor reduction, cycle-time change or financial return is disclosed. The planned real-time control tower is a future phase, not an achieved result.", "baseline": "Before program, acquired businesses had overlapping applications, undocumented integrations, different procurement tools/workflows and extensive customization. No quantified before count of CGC customizations, application inventory, process cycle time or normalized ERP peer denominator is supplied.", "limits": "Vendor-authored case study and executive quotation; result denominator for the 550 customization comparison is not detailed. Company-wide scope is not equivalent to field deployment. Keep in a digital-foundations register separate from AI initiative counts; a future AI story would need a distinct use case and evidence.", "relationship": "No same-project canonical record identified in the checked baseline/consolidated research. It concerns enterprise ERP/process standardization, not production AI; do not map to AI records based on company or SAP vendor overlap.", "decision_question": "What was the actual go-live and recurring cost, and did harmonized procurement, close, maintenance or field-support workflows measurably improve after the acquired E&P systems were integrated?", "company_key": "Compañía General de Combustibles (CGC)", "run": "Rounds 11–20", "disposition": "background_context_undated", "sources": [ { "title": "CGC: Harmonizing fragmented systems to drive a company culture of clarity and efficiency", "publisher": "SAP", "date": "Undated (URL path includes 2025/09; publication date not printed or verified)", "url": "https://www.sap.com/asset/dynamic/2025/09/28aaac43-227f-0010-bca6-c68f7e60039b.html", "locator": "Lines 11–25 and 41–64; process counts, customization claim, acquired-system fragmentation and vendor/customer narrative.", "access": "Directly opened SAP primary customer story.", "supports": "Undated digital/process-foundation case; does not establish 2025 publication or upstream production value." } ], "references": [], "review": { "verdict": "correct", "reason": "The SAP customer page directly supports mapped processes, fewer than 70 customizations versus SAP's stated 550 industry average, and post-acquisition system/process work. It does not print a publication or implementation date. The originating record properly says the date is inferred from the URL path, but that path is not date evidence; mark the source undated and do not claim verified in-window publication. Keep the 550 comparison vendor-stated and unnormalized, with no cost or upstream production benefit inferred.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R16-GLOBAL-01", "verdict": "correct", "patch": { "kind": "context", "operating_period": "Undated case-story implementation; the page itself prints no publication or go-live date. Its URL contains a 2025/09 asset path, which does not establish publication date. In-window timing is therefore unverified.", "sources": [ { "title": "CGC: Harmonizing fragmented systems to drive a company culture of clarity and efficiency", "publisher": "SAP", "date": "Undated (URL path includes 2025/09; publication date not printed or verified)", "url": "https://www.sap.com/asset/dynamic/2025/09/28aaac43-227f-0010-bca6-c68f7e60039b.html", "locator": "Lines 11–25 and 41–64; process counts, customization claim, acquired-system fragmentation and vendor/customer narrative.", "access": "Directly opened SAP primary customer story.", "supports": "Undated digital/process-foundation case; does not establish 2025 publication or upstream production value." } ] }, "reason": "The SAP customer page directly supports mapped processes, fewer than 70 customizations versus SAP's stated 550 industry average, and post-acquisition system/process work. It does not print a publication or implementation date. The originating record properly says the date is inferred from the URL path, but that path is not date evidence; mark the source undated and do not claim verified in-window publication. Keep the 550 comparison vendor-stated and unnormalized, with no cost or upstream production benefit inferred.", "sources_inspected": [ { "url": "https://www.sap.com/asset/dynamic/2025/09/28aaac43-227f-0010-bca6-c68f7e60039b.html", "access": "Directly opened SAP primary customer story", "locator": "Lines 11–25 for reported counts and quote; lines 41–64 for post-acquisition workflow narrative and claimed result." } ], "recommended_disposition": "background_context_undated" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R16-GLOBAL-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R01-LIMITS-03", "company": "Continental Resources", "title": "Continental’s recent asset-level operating detail remains a research gap", "category": "operator disclosure coverage", "kind": "gap", "ai_role": "Unclear; no recent dated technology deployment located. Legacy corporate materials do not establish current AI or non-AI deployment.", "asset": "Continental operated U.S. unconventional portfolio; no specific recent asset-level initiative established.", "stage": "Search gap. Current official pages describe ECO-Pad and horizontal drilling in broad/legacy terms; no recent named technology deployment with date, scale and result located.", "operating_period": "No qualifying deployment period found in official source searches for 2024-10-07 through 2026-10-07.", "claim": "Retain only as bounded search gap: official pages reviewed are broad/legacy capability pages with no dated 2024-10-07–2026-10-07 named technology outcome. No conclusion about innovation level or adoption.", "economics": "No recent source with technology-level capex, unit cost, savings or performance denominator found.", "baseline": "None; no recent specific initiative matched against a comparator.", "limits": "Bounded search of company site and targeted query phrases; no exhaustive web/regulator/technical-literature search. The operational pages may be undated and describe established capability; current page retrieval date is not a launch date.", "relationship": "Discloser coverage gap, not an initiative record. Do not add a negative conclusion to Continental’s operator profile. Requires direct company/regulator/technical evidence before any example is added.", "decision_question": "Can current company, state regulator, supplier contract or technical-conference evidence identify a 2024-2026 Continental asset deployment with method, date, scale and measured outcome?", "company_key": "Continental Resources", "run": "Rounds 1–10", "disposition": "background/gap; do not create company-negative score", "sources": [ { "title": "Oil & Natural Gas Operations", "publisher": "Continental Resources", "date": "Undated current page; accessed 2026-10-07", "url": "https://www.clr.com/operations/", "locator": "ECO-Pad/horizontal drilling overview; page has no recent dated deployment or output denominator", "access": "Official company page opened", "supports": "Longstanding technology capabilities only." }, { "title": "Horizontal Drilling", "publisher": "Continental Resources", "date": "Undated current page; accessed 2026-10-07", "url": "https://www.clr.com/operations/horizontal-drilling/", "locator": "General explanation of horizontal drilling; no recent specific project/result", "access": "Official company page opened", "supports": "Background capability; does not close recent evidence gap." } ], "references": [], "review": { "verdict": "confirm", "reason": "Both official URLs reopened; page retrieval date is not an initiative date. The gap is properly scoped and does not imply no activity.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R01-LIMITS-03", "verdict": "confirm", "patch": { "claim": "Retain only as bounded search gap: official pages reviewed are broad/legacy capability pages with no dated 2024-10-07–2026-10-07 named technology outcome. No conclusion about innovation level or adoption." }, "reason": "Both official URLs reopened; page retrieval date is not an initiative date. The gap is properly scoped and does not imply no activity.", "recommended_disposition": "background/gap; do not create company-negative score", "sources_checked": [ { "url": "https://www.clr.com/operations/", "access_status": "official operator page opened directly", "date": "undated", "locator": "40-line page; no dated initiative or quantitative result surfaced" }, { "url": "https://www.clr.com/operations/horizontal-drilling/", "access_status": "official operator page opened directly", "date": "undated", "locator": "11-line page; no recent dated asset result surfaced" } ] } ] }, "department": "Production & process operations", "group_id": "T10-R01-LIMITS-03", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "No qualifying deployment period found in official source searches for 2024-10-07 through 2026-10-07." }, { "id": "T10-R01-US-03", "company": "Continental Resources", "title": "Continental’s current public materials leave deployment questions unanswered", "category": "research coverage gap / private-company evidence", "kind": "gap", "ai_role": "Unclear; recent filings do not specify AI role for current operating programs.", "asset": "Continental Resources U.S. onshore portfolio; company became privately held in 2022 but continues to file 10-K/10-Q reports under senior-note indentures.", "stage": "No recent named technology stage verified in targeted public sources.", "operating_period": "Latest located SEC filing is FY2025 Form 10-K; company operations pages describe long-running historical methods.", "claim": "Continental’s FY2025 10-K describes its technical toolkit at a high level—3D seismic, horizontal drilling, geosteering, advanced completions, pad/row development and enhanced-recovery technologies—and states it is a private company that continues required SEC filings. Company operations pages describe ECO-Pad as a decades-old concept and advanced completions, without a recent named implementation, denominator, measured KPI or cost outcome.", "economics": "No recent initiative-specific economic result or deployment-cost denominator identified. The 10-K offers portfolio/financial disclosures, but generic technology categories cannot support a comparative technology ROI claim.", "baseline": "Not disclosed for any newly deployed initiative in sources inspected. Historical ECO-Pad and early Bakken technical milestones are outside the current publication window and are not represented as launches.", "limits": "Targeted search/access gap, not proof Continental has no current technology deployment. SEC filing page was surfaced in search index but direct open/search-within failed in this browser; CLR pages are issuer material and largely historical/generic. Private status narrows disclosure, but its debt-indentured SEC reporting remains a source to monitor.", "relationship": "Addresses the explicit missing privately held operator in the candidate universe. Adds a documented coverage gap only; do not fill with dated historical ECO-Pad narrative as if it were a 2024–2026 innovation.", "decision_question": "Can debt-issuer filings, state permits, technical conference papers or operator/vendor technical case studies identify a named 2024–2026 Continental deployment with start date, eligible asset denominator and actual unit-cost/recovery/safety outcome?", "company_key": "Continental Resources", "run": "Rounds 1–10", "disposition": "background_coverage_gap", "sources": [ { "title": "Continental Resources, Inc. Form 10-K for year ended December 31, 2025", "publisher": "Continental Resources / SEC EDGAR", "date": "2026-02-23", "url": "https://www.sec.gov/Archives/edgar/data/732834/000119312526064403/ck0000732834-20251231.htm", "locator": "SEC filing-detail page confirms filing date 2026-02-23 and links FY2025 10-K; search-indexed filing text gives private-company status and general technical capabilities. Main 10-K body direct open/search was unavailable.", "access": "SEC filing-detail index opened; 10-K body itself only search-indexed", "supports": "Private-company status and broad technology categories, not a recent technology deployment." }, { "title": "Oil & Natural Gas Operations", "publisher": "Continental Resources", "date": "Undated current website page", "url": "https://www.clr.com/operations/", "locator": "Operations page: ECO-Pad history and up to 12 wells per pad; historical/general capability language.", "access": "Issuer HTML opened; lines 17–32 show historical ECO-Pad account and current high-level capabilities", "supports": "Long-lived pad-drilling model; no current deployment date or attributable economics." } ], "references": [], "review": { "verdict": "confirmed", "reason": "The finding is negative evidence about available public materials, not a claim that Continental has no technology. Its broad 10-K capabilities and historical ECO-Pad language should not be cast as a 2024-26 launch.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R01-US-03", "verdict": "confirmed", "patch": { "source_access": "Keep SEC filing-detail page directly opened, but FY2025 10-K body only search-indexed in the original audit; issuer operations page directly opened is undated/current but historical/general. This establishes a documented search gap, not proof no deployment exists." }, "reason": "The finding is negative evidence about available public materials, not a claim that Continental has no technology. Its broad 10-K capabilities and historical ECO-Pad language should not be cast as a 2024-26 launch.", "recommended_disposition": "background_coverage_gap", "sources_inspected": [ { "url": "https://www.sec.gov/Archives/edgar/data/732834/000119312526064403/ck0000732834-20251231.htm", "access": "SEC filing-detail opened; filing body search-indexed, not directly opened in original pass", "locator": "FY2025 10-K, general capabilities; original audit notes source depth." }, { "url": "https://www.clr.com/operations/", "access": "Issuer HTML opened directly", "locator": "Operations page lines 17-32; historical/general capability language." } ] } ] }, "department": "Production & process operations", "group_id": "T10-R01-US-03", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R09-US-02", "company": "EQT Corporation / EOG Resources / Diamondback Energy / Devon Energy", "title": "Company well-cost figures need different comparisons", "category": "comparability / cost normalization / capital productivity", "kind": "context", "ai_role": "Not applicable to the arithmetic; the reported cost results are company-level outcomes and are not attributable to one AI or hardware intervention in the source evidence reviewed.", "asset": "EQT Appalachian portfolio; EOG multi-basin portfolio; Diamondback basin-specific drilling/completions and Barnett; Devon multi-basin D&C program.", "stage": "Reported FY2025 outcomes, Q1/Q2 2026 operating observations, and 2026 guidance/targets; these stages and date bases must remain labeled.", "operating_period": "FY2025 actual versus FY2024 for EOG/EQT; Q1 2026 individual-well record and Q2 2026 equipment/performance observations for Diamondback; Devon plan/2025 bundled efficiency report.", "claim": "Preserve distinct measures: EOG 7% portfolio average well-cost decline; EQT 13% average cost-per-foot decline; Diamondback Q2 ~14% equipment-cost-per-well QoQ decline, and separate one-well Barnett record; Devon's $1bn plan targets and bundled metrics. No source provides a shared cost boundary and matched eligible population.", "economics": "Do not put the percentages into one savings leaderboard. The KPI numerators differ (whole average-well cost, cost/foot, equipment-only cost/well, speed/throughput and program-level capex), while periods, basin mix and design populations differ. A usable future cross-company panel should require actual USD/gross completed lateral foot with the same cost boundary; retain completion cost and drilling cost separately, identify WI/net-gross basis, and pair with a defined eligible-well population and production/recovery outcome. Keep throughput and uptime in separate panels.", "baseline": "EOG FY2025 versus FY2024 portfolio average; EQT FY2025 versus FY2024 cost per foot; Diamondback equipment cost/well Q2 versus Q1 2026 and one-well Barnett record; Devon metrics compare year over year and broad plan versus initial guidance. These are not matched-control or common-price/current-dollar baselines.", "limits": "Issuer definitions and cost scopes do not reconcile; no same-basin matched well cohorts across operators; EOG/EQT disclosures do not offer cost numerators; well length, lateral-foot denominator, completion intensity, facilities, water/sand, workovers and service-price/mix effects are not fully controlled. Devon >$250m program capital reduction is not technology savings. Do not infer owner returns or IRR without project capex and production/cost response.", "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail.", "decision_question": "Can each issuer provide a same-basin/well-class bridge from actual well capex to cost per completed lateral foot, with drilling, completion, facilities and logistics separated and matched to the production/recovery response and eligible well count?", "company_key": "Cross-company comparisons", "run": "Rounds 1–10", "disposition": "background_methodological_note_not_initiative", "sources": [ { "title": "EOG Resources Reports Fourth Quarter and Full-Year 2025 Results; Announces 2026 Capital Plan", "publisher": "EOG Resources", "date": "2026-02-24", "url": "https://filecache.investorroom.com/mr5ir_eogresources2/444/4Q_2025_Earnings_Press_Release.pdf", "locator": "FY2025 highlights and 2026 Outlook, PDF p. 1-2, lines 7-19 and 53-62.", "access": "Issuer-hosted PDF opened directly", "supports": "7% average well-cost reduction across multi-basin portfolio and low-single-digit 2026 target tied to lateral lengths and other efficiency gains." }, { "title": "EQT Reports Fourth Quarter and Full Year 2025 Results and Provides 2026 Guidance", "publisher": "EQT Corporation", "date": "2026-02-17", "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/EQT-Reports-Fourth-Quarter-and-Full-Year-2025-Results-and-Provides-2026-Guidance/default.aspx", "locator": "Fourth-quarter and recent highlights, lines 132-134.", "access": "Issuer HTML opened directly", "supports": "13% lower 2025 average well cost per foot YoY and 6% below internal expectation." }, { "title": "Form 8-K for Diamondback Energy Inc. filed Aug. 3, 2026 (Q2 2026 results)", "publisher": "Diamondback Energy", "date": "2026-08-03", "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "locator": "Q2 2026 Operational Performance, PDF p. 22, lines 719-725.", "access": "Issuer-hosted PDF opened directly", "supports": "21.3 average pumping hours/day, ~4,700 completed lateral feet/day and ~14% QoQ equipment cost per well decline, with no causal attribution specified." }, { "title": "Devon Energy Unveils Value Enhancing Business Optimization Plan", "publisher": "Devon Energy", "date": "2025-04-22", "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Unveils-Value-Enhancing-Business-Optimization-Plan/default.aspx", "locator": "Capital efficiency and production optimization target buckets, lines 46-58.", "access": "Issuer HTML opened directly", "supports": "Plan-level bucket/target definitions; not a realized per-well technology saving." } ], "references": [ { "id": "TECH-03", "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail." }, { "id": "R1-US-02", "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail." }, { "id": "T10-R02-US-02", "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail." }, { "id": "T10-R01-US-02", "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail." } ], "review": { "verdict": "confirmed", "reason": "The reviewed sources use different measures, periods, denominators and attribution boundaries. A single percent-savings chart or technology leaderboard would be misleading; the useful finding is the normalization requirement.", "cross_audits": [ { "assignment": "round-10-global.json", "finding_id": "T10-R09-US-02", "verdict": "confirmed", "patch": { "relationship": "Synthesis/comparability instruction, not a discrete technology initiative; keep out of initiative counts and use as a chart/normalization guardrail.", "claim": "Preserve distinct measures: EOG 7% portfolio average well-cost decline; EQT 13% average cost-per-foot decline; Diamondback Q2 ~14% equipment-cost-per-well QoQ decline, and separate one-well Barnett record; Devon's $1bn plan targets and bundled metrics. No source provides a shared cost boundary and matched eligible population.", "source_access": "All four cited issuer source URLs were reopened directly during the current R09/R10 audit; no third-party cross-company normalization was found." }, "reason": "The reviewed sources use different measures, periods, denominators and attribution boundaries. A single percent-savings chart or technology leaderboard would be misleading; the useful finding is the normalization requirement.", "recommended_disposition": "background_methodological_note_not_initiative", "sources_inspected": [ { "url": "https://filecache.investorroom.com/mr5ir_eogresources2/444/4Q_2025_Earnings_Press_Release.pdf", "access": "Issuer PDF opened directly", "locator": "FY2025 result and 2026 outlook, pp. 1-2." }, { "url": "https://ir.eqt.com/newsroom/news-releases/news-release-details/2026/EQT-Reports-Fourth-Quarter-and-Full-Year-2025-Results-and-Provides-2026-Guidance/default.aspx", "access": "Issuer HTML opened directly", "locator": "FY2025 cost per foot highlight; earnings release directly inspected." }, { "url": "https://ir.diamondbackenergy.com/static-files/3edc9cca-d7ee-45e5-b420-1b2b8fab639f", "access": "Issuer PDF opened directly", "locator": "Q2 2026 operating performance, PDF p. 22, lines 721-725." }, { "url": "https://investors.devonenergy.com/investors/press-releases/press-release-details/2025/Devon-Energy-Unveils-Value-Enhancing-Business-Optimization-Plan/default.aspx", "access": "Issuer HTML opened directly", "locator": "Plan timing and buckets, lines 44-60." } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R09-US-02", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R14-GLOBAL-01", "company": "Ecopetrol S.A.", "title": "Produced-water reinjection for recovery and pressure support totals 160.6 million m3 across Colombian upstream assets", "category": "reservoir management / produced-water injection / recovery and pressure maintenance", "kind": "update", "ai_role": "No AI is attributed. The described mechanism is produced-water separation and reservoir reinjection for pressure maintenance and/or hydrocarbon recovery; analytics involvement is not specified.", "asset": "Ecopetrol upstream production assets including Castilla, Rubiales, Chichimene, Akacias and Huila Integrado; the source reports the measure at group level rather than allocating volumes by field.", "stage": "Operating 2025 water-management practice; issuer's 2026-04-24 report describes an annual result and year-over-year change.", "operating_period": "Calendar year 2025 vs 2024. The issuer's 2026-04-24 current water-management page reports the figures.", "claim": "Ecopetrol reports 161.0 million m3 of produced water reused in upstream in 2025, up 12% from 2024 and equivalent to 30.3% of produced water generated. It says the increase was mainly caused by better performance in production-water reinjection for recovery and/or pressure maintenance in named assets. Of the 161.0 Mm3 reused, 160.6 Mm3 was reinjected for those purposes.", "economics": "No field-specific incremental oil/gas, injection cost, treatment energy, water-quality threshold, or payback disclosed. This measures reinjection volume, not incremental recovered barrels; pressure maintenance and recovery are combined purposes.", "baseline": "2024 produced-water reuse volume is the percentage-growth comparison, but absolute 2024 volume and field-level comparison are not given in the cited passage. The 30.3% denominator is total produced water generated in 2025.", "limits": "Issuer aggregate for multiple assets and mature water-management mechanisms; no unique project name, field-by-field split, matched control or causally measured production uplift. Keep the 181 Mm3 total-water reuse figure separate (includes non-upstream streams) and 160.6 Mm3 recovery/pressure reinjection separate from the 283.3 Mm3 disposal injection total.", "relationship": "No same-project record located in the production AI register or prior consolidated research. This is a conventional physical reservoir/water-management practice and aggregate performance update, not an AI deployment. It adds an operating-scale and denominator reference rather than a discrete new project.", "decision_question": "For each named field, what produced-water volume and quality entered reinjection, what share supported pressure versus incremental recovery, and what incremental production, decline change, treatment/injection cost and water-disposal savings were measured against a matched baseline?", "company_key": "Ecopetrol", "run": "Rounds 11–20", "disposition": "include_with_aggregate_and_no_uplift_limits", "sources": [ { "title": "Operational efficiency in water management", "publisher": "Ecopetrol", "date": "2026-04-24", "url": "https://www.ecopetrol.com.co/wps/portal/Home/tesg/environmental/towards-water-neutrality/water%20management%20efficiency", "locator": "Page lines 227-261: date, operating totals, upstream produced-water reuse and reinjection purpose/asset list; lines 273-276 distinguish disposal injection.", "access": "Issuer HTML opened directly", "supports": "2025 actual reuse/injection volumes, year-over-year change, denominator, stated causes and named asset list." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened the 2026-04-24 Ecopetrol water-management page. It reports 161.0 million m3 of produced water reused upstream in 2025, up 12%; 30.3% of generated produced water, with 160.6 million m3 reinjected for recovery and/or pressure maintenance. The record keeps total produced-water reuse separate from the reinjection subset and does not call the volume an incremental production result. No correction needed.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R14-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened the 2026-04-24 Ecopetrol water-management page. It reports 161.0 million m3 of produced water reused upstream in 2025, up 12%; 30.3% of generated produced water, with 160.6 million m3 reinjected for recovery and/or pressure maintenance. The record keeps total produced-water reuse separate from the reinjection subset and does not call the volume an incremental production result. No correction needed.", "sources_inspected": [ { "url": "https://www.ecopetrol.com.co/wps/portal/Home/tesg/environmental/towards-water-neutrality/water%20management%20efficiency", "access": "Directly opened Ecopetrol primary HTML", "locator": "Lines 227–261: page date, total reuse and upstream reinjection quantities and purpose." } ], "recommended_disposition": "include_with_aggregate_and_no_uplift_limits" } ] }, "department": "Water, emissions & energy", "group_id": "T20-R14-GLOBAL-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Calendar year 2025 vs 2024. The issuer's 2026-04-24 current water-management page reports the figures." }, { "id": "R1-GL-01", "company": "Equinor", "title": "Hydrone R resident subsea intervention drone at Njord", "category": "robotics / subsea remote operations", "kind": "new_initiative", "ai_role": "No AI contribution disclosed.", "asset": "Njord field, Norwegian Sea; 330 metres below sea level.", "stage": "Operational trial on an operating field; 240-day continuous submersion milestone completed. This is not evidence of fleet-scale commercial rollout.", "operating_period": "Issuer article dated 2025-06-25; 240-day operating period ended 2025-01-24.", "claim": "Duration/residency milestone. Vessel/support-boat reduction is qualitative; no avoided vessel-days, uptime delta, cost or emissions result disclosed.", "economics": "Development/testing investment and per-day operating cost not disclosed.", "baseline": "Conventional comparison described qualitatively as support vessels traveling to/remaining at field and daily ROV deployment/recovery. No matched vessel-day or cost baseline disclosed.", "limits": "A record-duration trial proves subsea residency and field operation, not economics or replacement of crewed vessels across a field. Equinor still reports divers working year-round. Inspection/light maintenance scope is narrower than heavy intervention or repair.", "relationship": "Operating resident subsea robotics tests the offshore inspection/intervention workflow and vessel exposure. Trial duration is adoption evidence, not a reliability or ROI result.", "decision_question": "What vessel-days, interventions, maintenance tasks, and all-in vessel/subsea support cost did this single 240-day residency displace versus a crewed-ROV baseline?", "company_key": "Equinor", "run": "Three-round scope review", "disposition": "include", "sources": [ { "title": "A deep dive into emission cuts", "publisher": "Equinor", "date": "2025-06-25", "url": "https://www.equinor.com/magazine/a-deep-dive-into-emission-cuts", "locator": "Hydrone R sections; operating period and 240-day milestone, lines 46-65", "access": "Issuer page opened; full text accessible", "supports": "Vehicle method, Njord field use, all-electric/resident operating model, qualitative vessel substitution and exact operating dates/duration." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-06-25", "url": "https://www.equinor.com/magazine/a-deep-dive-into-emission-cuts", "locator": "Hydrone R section; continuous residency, 330 m depth, May 20 2024-Jan 24 2025 dates", "access": "official indexed text reviewed; direct page fetch timed out", "supports": "Primary issuer account supports the duration and operating method, but the headline duration is not a reliability KPI and there is no economic bridge. This is a useful physical-operations comparator only when carefully bounded." } ], "references": [ { "id": "AI-268", "relationship": "company_context" }, { "id": "TR-04", "relationship": "company_context" } ], "department": "Maintenance & reliability", "group_id": "R1-GL-01", "core_company": true, "ai_ids": [ "AI-268" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Issuer article dated 2025-06-25; 240-day operating period ended 2025-01-24." }, { "id": "T10-R05-LIMITS-01", "company": "Equinor / Saipem", "title": "Hydrone-R adds a longer operating history at Njord", "category": "Subsea robotics / inspection and light intervention", "kind": "update", "ai_role": "AI-based navigation is a supplier-declared design capability in project context; do not attribute each mission/outcome to AI.", "asset": "Njord field, Norwegian Sea; subsea inspection, drilling/production support and interventions on subsea structures under a 10-year Equinor service contract with Saipem.", "stage": "Operating under the service contract. Supplier says it has performed hundreds of missions; in late 2025 it enabled activities supporting commissioning of a Njord well. It completed a 240-day continuous seabed stay, not a year-round uptime test.", "operating_period": "Current Saipem update dated 2026-02-06 reports >500 total residency days since start and >240-day continuous stay; it describes a well commissioning activity at end-2025. Prior specific stay was 2024-05-20 to 2025-01-24 (240 days) in Equinor's June 2025 retrospective.", "claim": "Saipem reports >500 cumulative residency days, a 240-day continuous seabed stay, hundreds of Njord missions, and its claimed contribution to late-2025 well commissioning during 12.5m waves. Residency is not uptime; support to one commissioning activity is not proof all conventional ROV tasks are displaced. No availability/failure/success/cost denominator.", "economics": "No contract value, per-mission cost, avoided-vessel-day count, comparative cost, availability or verified emissions avoided disclosed. Benefits are described qualitatively.", "baseline": "A previous Equinor source reports 240 continuous days at 330 m depth before recovery. The 2026 Saipem update calls this a continuous stay/residency record; it does not state continuous active operation or uptime. Project page says both Hydrone-R and Hydrone-W are remotely controlled from Njord-A or onshore; do not conflate support from an autonomous vehicle with fully autonomous operations.", "limits": "Supplier claims only. No data on failed missions, interventions, uptime/availability denominator, faults, sensor detection/false alarms, maintenance hours, cable/docking availability, operator safety incidents or missions unsuitable for weather. The 12.5 m wave example is a bounded mission/commissioning support claim, not proof that all conventional ROV work can be displaced. Existing research already covers the 240-day milestone; this is only a later 2026 operational update.", "relationship": "Consolidated technology-scope research already contains the 240-day Njord residency; this observation is an enrichment from Saipem's 2026 source, not a new initiative. No same-project match is asserted to the different Equinor robot-inspection ML project at Sture/Mongstad.", "decision_question": "Before scaling a resident subsea robot, what independently reported mission-success, availability, intervention, maintenance, false-detection and avoided-vessel-day metrics would establish safety and full-cost advantage over conventional ROV support?", "company_key": "Equinor", "run": "Rounds 1–10", "disposition": "enrich existing R1-GL-01; no duplicate initiative count", "sources": [ { "title": "Saipem’s underwater drone Hydrone-R performs autonomous mission in the Arctic coral area in Norway", "publisher": "Saipem", "date": "2026-02-06", "url": "https://www.saipem.com/en/media/news/Saipem-s-underwater-drone-Hydrone-R-performs-autonomous-mission-in-the%20Arctic-coral-area-in-Norway", "locator": "Lines 116–126", "access": "Primary supplier release opened directly", "supports": "Named contract/site context, 500+ cumulative residency days, 240-day continuous stay, hundreds of missions, and end-2025 well-commissioning support under reported 12.5 m wave conditions." }, { "title": "The Hydrone project in the Njord Field", "publisher": "Saipem", "date": "Project page; accessed 2026-10-07", "url": "https://www.saipem.com/en/saipem-worldwide-projects/hydrone-submarine-development-njord-field", "locator": "Lines 115–185, especially 130–176", "access": "Primary supplier project page opened directly", "supports": "Contract scope, control stations, project-declared design challenges including reliability and communications, and separation between vehicle capability and demonstrated field outcomes." }, { "title": "From pioneer diving to autonomous drones", "publisher": "Equinor", "date": "2025-06-25", "url": "https://web-equinor-web-sites-prod.c2.radix.equinor.com/magazine/a-deep-dive-into-emission-cuts", "locator": "Lines 40–65 and 89–96", "access": "Primary operator article opened directly", "supports": "240-day stay from 2024-05-20 until recovery 2025-01-24; subsea operating role and distinction between residency and other claimed benefits." } ], "references": [ { "id": "R1-GL-01", "relationship": "Consolidated technology-scope research already contains the 240-day Njord residency; this observation is an enrichment from Saipem's 2026 source, not a new initiative. No same-project match is asserted to the different Equinor robot-inspection ML project at Sture/Mongstad." } ], "review": { "verdict": "correct", "reason": "Primary supplier's Feb. 2026 update is within window and materially advances existing record. It remains supplier-only evidence; no incident/failure is stated. Correct the local empty overlap field to point to canonical R1-GL-01 during consolidation.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R05-LIMITS-01", "verdict": "correct", "patch": { "canonical_overlap": "R1-GL-01 Hydrone R resident subsea intervention drone at Njord (consolidated research); this is a dated 2026 operating update, not a new initiative.", "claim": "Saipem reports >500 cumulative residency days, a 240-day continuous seabed stay, hundreds of Njord missions, and its claimed contribution to late-2025 well commissioning during 12.5m waves. Residency is not uptime; support to one commissioning activity is not proof all conventional ROV tasks are displaced. No availability/failure/success/cost denominator.", "ai_role": "AI-based navigation is a supplier-declared design capability in project context; do not attribute each mission/outcome to AI." }, "reason": "Primary supplier's Feb. 2026 update is within window and materially advances existing record. It remains supplier-only evidence; no incident/failure is stated. Correct the local empty overlap field to point to canonical R1-GL-01 during consolidation.", "recommended_disposition": "enrich existing R1-GL-01; no duplicate initiative count", "sources_checked": [ { "url": "https://www.saipem.com/en/media/news/Saipem-s-underwater-drone-Hydrone-R-performs-autonomous-mission-in-the%20Arctic-coral-area-in-Norway", "access_status": "primary supplier release reopened directly", "date": "2026-02-06", "locator": "lines 116–126" }, { "url": "https://www.saipem.com/en/saipem-worldwide-projects/hydrone-submarine-development-njord-field", "access_status": "primary supplier project page opened previously in R05", "date": "project page undated; accessed 2026-10-07", "locator": "lines 115–185: contract and listed reliability/control design challenges" } ] } ] }, "department": "Maintenance & reliability", "group_id": "R1-GL-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "R1-LIM-01", "company": "Equinor and Wisting license partners", "title": "Wisting field power concept: power from shore assessed and ruled out; gas-turbine power generation retained for concept maturation", "category": "Offshore power / field development technology selection", "kind": "context", "ai_role": "No AI evidence. This is a non-AI infrastructure/concept choice that sets the boundary for where a later AI workflow could be deployed and powered.", "asset": "Wisting discovery, Barents Sea, around 310 km north of Hammerfest; 390–418 m water depth; estimated recoverable resources just under 500 MMboe.", "stage": "Keep as early concept maturation, no FID; source indicates concept selection possible by end-2026 and FID planned end-2027.", "operating_period": "Source published 2026-06-25. Equinor references the earlier project postponement in 2022; this round uses the 2026 primary source for current status.", "claim": "Power from shore was ruled out after detailed assessment on technical complexity and cost. Equinor continues concept work around an energy-efficient gas turbine. CCS remains conditional on technology, regulatory requirements, and acceptable cost/time. Partners: Equinor 42.5%, Aker BP 27.5%, Petoro 20%, INPEX Idemitsu Norge 10%, subject to a pending partner transaction approval. No cost baseline or realized project outcome disclosed.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Operator announcement; no cost comparison, engineering study, emissions comparison, quantified schedule impact, or independent review published in this source. Wisting remains a possible development, not a sanctioned project. Do not describe electrification or CCS as failed technologies: only this project’s specific power-from-shore concept was screened out.", "relationship": "A project-specific screened alternative and complexity/cost tradeoff can inform capital decisions, but not an operating technology comparison. No exact canonical project record to enrich.", "decision_question": "What lifecycle cost/schedule/reliability/emissions study supported rejecting shore power versus gas turbine, and what cost/technical threshold could reverse the decision?", "company_key": "Equinor", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "Proposal for environmental impact assessment programme for Wisting submitted for public consultation", "publisher": "Equinor", "date": "2026-06-25", "url": "https://www.equinor.com/news/20260625-wisting-proposal-environmental-impact-assessment-programme", "locator": "Project status, power-from-shore decision, gas-turbine concept, CCS conditions, decision timeline and licensee interests; paragraphs 2–7 and facts.", "access": "Opened; issuer source", "supports": "Current concept stage; source-stated basis for ruling out power from shore; conditional CCS; project and supplier scale; licensee interests." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-06-25", "url": "https://www.equinor.com/news/20260625-wisting-proposal-environmental-impact-assessment-programme", "locator": "Project status and concept options; published EIA-programme notice.", "access": "issuer HTML opened", "supports": "Source supports the project-specific screening decision but gives no cost comparison, quantified schedule effect, or independent engineering evidence. Useful as a project option-screen example only." } ], "references": [ { "id": "AI-033", "relationship": "company_context" }, { "id": "TR-04", "relationship": "company_context" } ], "department": "Production & process operations", "group_id": "R1-LIM-01", "core_company": true, "ai_ids": [ "AI-033" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "R1-LIM-02", "company": "Equinor and Snøhvit partnership", "title": "Snøhvit Future onshore compression and Hammerfest LNG electrification", "category": "Field-life extension, compression, facility electrification and power infrastructure", "kind": "context", "ai_role": "No AI role. It is an adjacent upstream asset reliability / emissions-capex case; any AI system would need to work around live-plant construction, turnarounds, and commissioning constraints.", "asset": "Snøhvit gas development and Hammerfest LNG / Melkøya facility, Norway; infrastructure also includes a 3.2 km cable tunnel and grid upgrades by Statnett.", "stage": "Issuer-indexed Oct. 7 update says ~60% complete, compressor module installed in August 2026, schedule unchanged; compression planned 2029 and electrification 2030.", "operating_period": "Key status/cost sources published 2025-12-22 and 2026-10-07. Original PDO estimate submitted 2022; included for baseline only.", "claim": "Current estimate NOK 26.5bn (2026 value) versus NOK 13.2bn in the 2022 PDO, which Equinor restates as NOK 15.2bn in current-value terms; thus approximately NOK 11.3bn / 74% above the inflation-adjusted baseline. Cost and schedule were affected by complexity integrating into an operating LNG plant, operating challenges, weather, difficult rock in the cable tunnel, shutdowns/turnaround, and equipment inflation. 2026 update says 60% complete and timetable unchanged. Owners: Equinor 36.79%, Petoro 30%, TotalEnergies EP Norge 18.4%, Vår Energi 12%, Harbour Energy Norge 2.81%.", "economics": "Current issuer-indexed estimate NOK 26.5bn in 2026 value vs NOK 15.2bn restated 2026 value for the 2022 PDO (original nominal PDO NOK 13.2bn): +NOK 11.3bn, about +74% versus the restated baseline. Label estimate, not realized cost.", "baseline": "Not disclosed", "limits": "The emissions reduction is a forecast, not a measured result. Cost attribution is qualitative; the source does not break out the increase by cause or supplier package. Equinor says the project remains profitable, but publishes no current NPV, return threshold, or sensitivity in the cited update. Do not call this a technical failure: it is a costly, difficult live-plant integration project still progressing.", "relationship": "Material brownfield execution/capital case, but Snøhvit is LNG processing infrastructure, not upstream production. Cost escalation is project execution context, not proof of technology failure.", "decision_question": "How much of NOK 26.5bn vs NOK 15.2bn restated PDO is attributable to integration, civil works, inflation, shutdowns and scope, and what is remaining cost-to-complete / contingency?", "company_key": "Equinor", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "Updated cost estimate for the Snøhvit Future project", "publisher": "Equinor", "date": "2026-10-07", "url": "https://www.equinor.com/news/20261007-updated-cost-estimate-snohvit-future", "locator": "Cost estimate and baseline; causes; supplier work; 60% complete; purpose, dates and ownership; lines 15–45.", "access": "Opened; issuer source", "supports": "Latest cost/schedule, project maturity, qualitative drivers, supplier involvement, emissions and production purposes, and owners." }, { "title": "Status update for the Snøhvit Future project", "publisher": "Equinor", "date": "2025-12-22", "url": "https://www.equinor.com/news/20251222-status-update-snohvit-future-project", "locator": "Original change from plan, NOK 20bn+ estimate in 2025 values, one-year compression delay and operating-plant complexity; lines 19–43.", "access": "Opened; issuer source", "supports": "The 2025 intermediate schedule/cost update and quantified cause categories. Current 2026 figures supersede its current-estimate figures." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-10-07", "url": "https://www.equinor.com/news/20261007-updated-cost-estimate-snohvit-future", "locator": "Issuer news index identifies current estimate, timetable and Oct. 7 publication.", "access": "direct URL inaccessible in browser; issuer newsroom index/search snippet surfaced source text, so detailed claims not fully reopened", "supports": "The overrun is material evidence about brownfield execution and capital risk, not proof that compression or electrification technology failed. Latest Oct. 7 page could not be directly opened in this audit; its indexed issuer snippet confirms headline cost and timetable, while source details are incompletely verified." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-12-22", "url": "https://www.equinor.com/news/20251222-status-update-snohvit-future-project", "locator": "Intermediate cost/schedule update; operating facility, schedule delay, weather/tunnel/turnaround/equipment factors.", "access": "issuer HTML opened in prior source audit", "supports": "The overrun is material evidence about brownfield execution and capital risk, not proof that compression or electrification technology failed. Latest Oct. 7 page could not be directly opened in this audit; its indexed issuer snippet confirms headline cost and timetable, while source details are incompletely verified." }, { "title": "Additional root primary-source check", "publisher": "Equinor", "date": "Date not established", "url": "https://www.equinor.com/news/20261007-updated-cost-estimate-snohvit-future", "locator": "Cost/status/causes paragraphs and project facts", "access": "Primary HTML opened 7 October 2026; relevant full text reviewed.", "supports": "Cost estimate is NOK26.5bn in2026 value against original estimate adjusted to2026 NOK15.2bn. Operator says60% complete,compression2029,electrification2030;latesttimetableunchanged." } ], "references": [ { "id": "AI-033", "relationship": "company_context" }, { "id": "TR-04", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "R1-LIM-02", "core_company": true, "ai_ids": [ "AI-033" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R09-GLOBAL-01", "company": "Equinor / Snøhvit partnership", "title": "Snøhvit Future’s cost rises as compression and electrification advance", "category": "Project economics / offshore-to-onshore electrification and compression", "kind": "update", "ai_role": "No AI role in this evidence; project comprises compression at Hammerfest LNG and grid electrification infrastructure.", "asset": "Snøhvit Future / Hammerfest LNG at Melkøya, including onshore compression, grid substation, subsea cable and 3.2-km power-cable tunnel; partnership operated by Equinor.", "stage": "Construction about 60% complete as of 2026-10-07; compressor module installed Aug 2026; onshore compression planned 2029, electrification planned 2030.", "operating_period": "Cost updated 2026-10-07; emissions reduction is a future annual estimate after electrification.", "claim": "As of 7 Oct 2026, Equinor revised total Snøhvit Future project cost to NOK 26.5bn (2026 value) versus original nominal NOK 13.2bn (2022 PDO); inflation-adjusted comparison is NOK 15.2bn in 2026 value. Project reported 60% complete. Compression is planned for 2029; electrification for 2030. This is integrated project cost for production-maintaining compression plus electrification; not an abatement cost per tonne or evidence of technology failure. Emissions-cut estimate 850,000 tCO₂/year is a project forecast, not delivered reduction.", "economics": "Total integrated compression/electrification project estimate NOK26.5bn in 2026 money versus issuer inflation-adjusted PDO equivalent NOK15.2bn: about74% increase (analyst arithmetic). No split by work package, lifetime, electricity expense, preserved gas cash flow or emissions denominator sufficient for lifecycle abatement cost or technology ROI. Omit the capital-per-annual-emissions ratio from comparative exhibits.", "baseline": "2022 PDO estimate NOK 13.2bn, inflation-adjusted by Equinor to NOK 15.2bn in current value; current estimate NOK 26.5bn 2026-value. 850,000 tCO2/year is estimated future annual reduction from LNG electrification, not achieved and not full Snøhvit economics.", "limits": "Project combines production-maintenance compression and LNG plant electrification, so do not attribute total CAPEX solely to emissions abatement. Equinor names operational challenges at Hammerfest LNG, weather and difficult rock in cable tunnel; source gives project maturity (~60%) but no detailed schedule variance logic. Shareholder partnership economics differ from operator-only economics.", "relationship": "No same-project AI register entry identified. This is an integrated compression/electrification investment, and no AI use is disclosed; absence is not proof none exists.", "decision_question": "How much of the revised NOK 26.5bn supports plateau production versus electrification, and what lifetime gas value plus avoided emissions underpin the partnership's profitability claim?", "company_key": "Equinor", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Updated cost estimate for the Snøhvit Future project", "publisher": "Equinor", "date": "2026-10-07", "url": "https://www.equinor.com/news/20261007-updated-cost-estimate-snohvit-future", "locator": "Lines 15-45", "access": "Direct issuer page opened", "supports": "Current and prior estimate in comparable NOK value, project objectives, 850 kt/year expected emissions reduction, stage, schedule and execution constraints." } ], "references": [], "review": { "verdict": "correct", "reason": "Root directly verified current issuer release and 60% status. Preserve the nominal-vs-inflation-adjusted comparison and dual-purpose project boundary; avoid dividing total cost by forecast emissions or treating overruns as tech-specific.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R09-GLOBAL-01", "verdict": "correct", "patch": { "claim": "As of 7 Oct 2026, Equinor revised total Snøhvit Future project cost to NOK 26.5bn (2026 value) versus original nominal NOK 13.2bn (2022 PDO); inflation-adjusted comparison is NOK 15.2bn in 2026 value. Project reported 60% complete. Compression is planned for 2029; electrification for 2030. This is integrated project cost for production-maintaining compression plus electrification; not an abatement cost per tonne or evidence of technology failure. Emissions-cut estimate 850,000 tCO₂/year is a project forecast, not delivered reduction.", "economics_boundary": "Do not calculate cost per tonne using full integrated project cost and forecast annual emissions; scope and timing differ." }, "reason": "Root directly verified current issuer release and 60% status. Preserve the nominal-vs-inflation-adjusted comparison and dual-purpose project boundary; avoid dividing total cost by forecast emissions or treating overruns as tech-specific.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://www.equinor.com/news/20261007-updated-cost-estimate-snohvit-future", "access_status": "Direct primary URL returned internal error in R10; parent root-source-checks.json records root direct open and verification on 2026-10-07", "locator": "Lines 15-45", "date": "2026-10-07" } ] } ] }, "department": "Water, emissions & energy", "group_id": "R1-LIM-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Cost updated 2026-10-07; emissions reduction is a future annual estimate after electrification." }, { "id": "T10-R04-GLOBAL-02", "company": "Equinor", "title": "2024 partial electrification across Troll B/C, Sleipner center and Gudrun", "category": "Offshore power and emissions process", "kind": "update", "ai_role": "No AI role disclosed; grid power and platform modifications are physical infrastructure.", "asset": "Troll B and C fields/platforms; Sleipner field center; Gudrun platform, Norwegian Continental Shelf.", "stage": "Partly electrified during 2024 according to Equinor's 2024 annual-report release.", "operating_period": "During 2024; report published 20 March 2025.", "claim": "Partial electrification is reported at Troll B/C, Sleipner center and Gudrun; Equinor’s 5% year-on-year operated Scope 1+2 reduction is a portfolio result and cannot be allocated to these projects.", "economics": "No asset-level electrification CAPEX, power cost, or payback disclosed in the reviewed annual-report release.", "baseline": "Portfolio-wide operated emissions baseline is 2015; year-on-year 2024 total. No asset-level baseline or counterfactual.", "limits": "Partial electrification only; do not imply every platform load was electrified or assign the company-wide emissions decrease to this set of assets. Equinor separately stopped two early-phase electrification projects in October 2025 primarily due to high abatement costs (covered in R08/R09 context, not a same-project duplication).", "relationship": "AI-027 is company-level AI context only; no same-project record identified. Electrification is a physical operating foundation and should not be categorized as AI deployment.", "decision_question": "Which asset-level emissions/cost changes are attributable to each electrification project after grid and production-mix effects?", "company_key": "Equinor", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Equinor presents 2024 Annual report", "publisher": "Equinor", "date": "2025-03-20", "url": "https://www.equinor.com/news/20250320-integrated-annual-report-2024", "locator": "Lines 52-56", "access": "Direct issuer release opened", "supports": "Partial electrification list and operated emissions totals/change." } ], "references": [ { "id": "AI-033", "relationship": "AI-027 is company-level AI context only; no same-project record identified. Electrification is a physical operating foundation and should not be categorized as AI deployment." }, { "id": "AI-034", "relationship": "AI-027 is company-level AI context only; no same-project record identified. Electrification is a physical operating foundation and should not be categorized as AI deployment." }, { "id": "AI-035", "relationship": "AI-027 is company-level AI context only; no same-project record identified. Electrification is a physical operating foundation and should not be categorized as AI deployment." }, { "id": "AI-036", "relationship": "AI-027 is company-level AI context only; no same-project record identified. Electrification is a physical operating foundation and should not be categorized as AI deployment." } ], "review": { "verdict": "correct", "reason": "Issuer material supports sites and corporate emissions denominator. No project-level cost, utilization, uptime or reduction attribution.", "cross_audits": [ { "assignment": "round-04-global.json", "finding_id": "T10-R04-GLOBAL-02", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-027" ], "added": [ "AI-033", "AI-034", "AI-035", "AI-036" ] } }, "reason": "AI-027 is Eni, not Equinor; replaced with Equinor portfolio/use-case IDs. None are the electrification project.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R04-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Partial electrification is reported at Troll B/C, Sleipner center and Gudrun; Equinor’s 5% year-on-year operated Scope 1+2 reduction is a portfolio result and cannot be allocated to these projects." }, "reason": "Issuer material supports sites and corporate emissions denominator. No project-level cost, utilization, uptime or reduction attribution.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://www.equinor.com/news/20250320-integrated-annual-report-2024", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 52-56", "date": "2025-03-20" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-033", "AI-034", "AI-035", "AI-036" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "During 2024; report published 20 March 2025." }, { "id": "T10-R08-GLOBAL-01", "company": "Equinor", "title": "Early-phase Snorre and Halten electrification work stopped over economics", "category": "Offshore power / project cancellation", "kind": "negative_evidence", "ai_role": "No AI role; this was grid, cables and offshore platform modification engineering.", "asset": "Snorre A/B power-from-shore project and Halten-area partial electrification (Heidrun, Åsgard B, Kristin), Norwegian Continental Shelf.", "stage": "Early-phase project plans discontinued in October 2025; not an operating technology failure.", "operating_period": "Decision October 2025, disclosed in Equinor Q3 2025 results.", "claim": "Equinor stopped early-phase Snorre/Halten electrification work in October 2025 primarily because of high abatement cost. These were pre-operation capital-allocation decisions; no project-specific measured emissions/economics or evidence of technical failure is supplied.", "economics": "Decision explicitly economic; project-specific CAPEX, power tariffs, NOK/tCO2 decision threshold and sunk costs not disclosed in the Q3 release. Do not compare potential annual tonnes to realized savings.", "baseline": "No project-specific baseline emissions or achieved reduction is stated in the reviewed Q3 release; these were planned projects that did not proceed to deployment.", "limits": "Cancellation was due primarily to high abatement costs; this is not a failure of an operating electrification system. Do not label it as technical failure or infer economics beyond the stated reason.", "relationship": "Equinor AI register records are company context only; no same-project match. This is a physical electrification project cancellation, not an AI pilot failure.", "decision_question": "For proposed offshore power projects, which input costs (CAPEX, grid connection, electricity versus saved gas, policy support) pushed abatement cost over the partnerships' investment threshold?", "company_key": "Equinor", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Equinor third quarter 2025 results", "publisher": "Equinor", "date": "2025-10-23", "url": "https://www.equinor.com/news/equinor-third-quarter-2025-results", "locator": "Lines 26-35 and 87-89", "access": "Direct issuer results page opened", "supports": "Stop decision for Snorre/Halten early-phase projects and primary stated reason: high abatement costs." } ], "references": [ { "id": "AI-033", "relationship": "Equinor AI register records are company context only; no same-project match. This is a physical electrification project cancellation, not an AI pilot failure." }, { "id": "AI-034", "relationship": "Equinor AI register records are company context only; no same-project match. This is a physical electrification project cancellation, not an AI pilot failure." }, { "id": "AI-035", "relationship": "Equinor AI register records are company context only; no same-project match. This is a physical electrification project cancellation, not an AI pilot failure." }, { "id": "AI-036", "relationship": "Equinor AI register records are company context only; no same-project match. This is a physical electrification project cancellation, not an AI pilot failure." } ], "review": { "verdict": "correct", "reason": "Issuer results source supports the stated economic reason. Classify as an economics/capital-allocation stop, not a failed technology deployment.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R08-GLOBAL-01", "verdict": "correct", "patch": { "claim": "Equinor stopped early-phase Snorre/Halten electrification work in October 2025 primarily because of high abatement cost. These were pre-operation capital-allocation decisions; no project-specific measured emissions/economics or evidence of technical failure is supplied." }, "reason": "Issuer results source supports the stated economic reason. Classify as an economics/capital-allocation stop, not a failed technology deployment.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://www.equinor.com/news/equinor-third-quarter-2025-results", "access_status": "Primary result URL reopened in R10; page returned only title/limited text; source record notes direct review in R09", "locator": "Lines 26-35 and 87-89", "date": "2025-10-23" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R08-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-033", "AI-034", "AI-035", "AI-036" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Decision October 2025, disclosed in Equinor Q3 2025 results." }, { "id": "T20-R13-LIMITS-01", "company": "Equinor", "title": "Equinor’s production-efficiency figure does not isolate AI’s contribution", "category": "value_attribution", "kind": "context", "ai_role": "The report names AI and advanced machine learning across well planning, predictive maintenance and operational efficiency, but does not link a measured field result to a specific model or workflow.", "asset": "Equinor operated oil-and-gas portfolio, with ~92% production efficiency stated for the Norwegian Continental Shelf (NCS); report discusses Åsgard A and other interventions.", "stage": "2025 annual-report summary of 2025 operational work and future ambitions.", "operating_period": "2025 results; report signed 2026-03-09.", "claim": "Equinor's report asserts tangible AI value in 2025 and describes AI uses, but does not quantify an AI-specific production-efficiency contribution in the cited passage. It states that technology implementation and in-house expertise are central to sustaining ~92% NCS production efficiency; surrounding examples bundle AI/analytics with mature optimization, compressor washing, integrity logging, additive-manufactured components and online valve work. Åsgard A avoided-loss claim is attributed to a set of Next-Generation Maintenance interventions, not isolated AI.", "economics": "No AI-specific cost, savings, capital, or payback disclosed. Production-efficiency rate is a portfolio operating metric, not an AI ROI measure.", "baseline": "~92% NCS PE is company-reported; method, exact population and comparison period are not specified in the cited innovation passage.", "limits": "Corporate self-report; portfolio-level denominator and exact calculation not specified in the cited passage; diverse non-AI interventions confound attribution. Do not infer AI caused the production efficiency or Åsgard A avoided-loss outcome.", "relationship": "Contextual attribution check, not a new AI initiative or an independent measurement of operational performance.", "decision_question": "For an AI business case, can the operator identify a named workflow's eligible asset population, baseline, intervention date, production/deferment effect and incremental cost separately from routine maintenance and engineering work?", "company_key": "Equinor", "run": "Rounds 11–20", "disposition": "retain as attribution context; do not create or merge into an asset deployment", "sources": [ { "title": "Equinor 2025 Annual Report, section 2.4 Fuelling innovation", "publisher": "Equinor / SEC exhibit", "date": "2026-03-09 (report approval date)", "url": "https://www.sec.gov/Archives/edgar/data/1140625/000114062526000013/exhibit154equinor2025ann.htm", "locator": "Lines 548–556", "access": "directly opened filed annual-report HTML", "supports": "AI/ML portfolio description; ~92% production efficiency statement and its bundled attribution; non-AI examples including compressor optimization/washing, integrity technology and Åsgard A maintenance intervention; no AI-specific quantified bridge." } ], "references": [], "review": { "verdict": "correct", "reason": "The filed report directly confirms the broad AI value assertion, the ~92% PE figure, and bundled technology examples. The correct limit is no AI-specific metric/counterfactual in this passage, not an absence of AI value claims throughout Equinor's reporting.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R13-LIMITS-01", "verdict": "correct", "patch": { "claim": "Equinor's report asserts tangible AI value in 2025 and describes AI uses, but does not quantify an AI-specific production-efficiency contribution in the cited passage. It states that technology implementation and in-house expertise are central to sustaining ~92% NCS production efficiency; surrounding examples bundle AI/analytics with mature optimization, compressor washing, integrity logging, additive-manufactured components and online valve work. Åsgard A avoided-loss claim is attributed to a set of Next-Generation Maintenance interventions, not isolated AI.", "baseline": "~92% NCS PE is company-reported; method, exact population and comparison period are not specified in the cited innovation passage.", "existing_ids": [] }, "reason": "The filed report directly confirms the broad AI value assertion, the ~92% PE figure, and bundled technology examples. The correct limit is no AI-specific metric/counterfactual in this passage, not an absence of AI value claims throughout Equinor's reporting.", "sources_inspected": [ { "url": "https://www.sec.gov/Archives/edgar/data/1140625/000114062526000013/exhibit154equinor2025ann.htm", "access": "direct filed annual-report HTML reopened", "locator": "Lines 544–555; report AI claims and oil-and-gas innovation examples." } ], "recommended_disposition": "retain as attribution context; do not create or merge into an asset deployment" } ] }, "department": "Production & process operations", "group_id": "T20-R13-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "2025 results; report signed 2026-03-09." }, { "id": "T20-R16-LIMITS-01", "company": "Equinor / Microsoft; OSDU Forum documentation", "title": "OSDU still leaves implementation and data-mapping work to do", "category": "data_architecture_and_integration", "kind": "context", "ai_role": "OSDU is a data foundation aligned with later analytics/AI use; the cited operator story reports workflow/data modernization, not a measured AI result.", "asset": "Equinor enterprise subsurface data platform OMNIA, using Microsoft Azure Data Manager for Energy aligned with OSDU; OSDU External Data Services documentation applies to operator/provider ingestion patterns more broadly.", "stage": "Equinor reports platform use and hundreds of thousands of quality-controlled well logs available in cloud. OSDU EDS documentation (dated 2025-09-09) describes a standard service for metadata and external-data ingestion.", "operating_period": "Equinor customer story dated 2025-10-07; OSDU EDS documentation current as of 2025-09-09.", "claim": "Equinor/Microsoft report an OSDU-aligned Azure Data Manager configuration integrated into OMNIA and say hundreds of thousands of quality-controlled well logs are stored in cloud. The story says OSDU can be difficult to implement/maintain and on-prem instances may lack compute/scalability. OSDU EDS docs describe prior manual fetching/custom ETL and delay, and state reference mapping needs operator configuration. The evidence supports integration/implementation diligence; it does not show Equinor incurred a measured migration penalty, vendor lock-in or an exit failure.", "economics": "No actual migration cost, egress fee, measured integration labor or migration ROI is disclosed. Equinor's quoted '250 years' is a vendor-published counterfactual and not an independently audited saving.", "baseline": "Prior state described by Equinor: data silos, manual search/transfer/reporting. OSDU EDS documentation describes pre-EDS manual fetching and separate custom ETL per provider; no shared numeric time/cost baseline.", "limits": "Customer story is vendor-authored; no independent cost or availability audit. Platform implementation is cloud-specific in the described Equinor configuration; OSDU alignment alone does not establish portability, data egress rights, model portability, or vendor-neutral total cost. The OSDU documentation describes capabilities and design intent, not comparative operator performance. No actual lock-in or exit failure is established.", "relationship": "Architecture context relevant to procurement and AI data readiness; not a duplicate AI implementation record and not a vendor-lock-in incident.", "decision_question": "Does the procurement contract make data, metadata, mappings, APIs, derived features and model outputs exportable, and what are the measured transfer, egress, mapping-maintenance and replatforming costs under a vendor-exit test?", "company_key": "Equinor", "run": "Rounds 11–20", "disposition": "retain as procurement and integration context; exclude any vendor-lock-in or realized-economics score", "sources": [ { "title": "Equinor targets data efficiency and a low-carbon future with Microsoft Azure Data Manager for Energy", "publisher": "Microsoft Customer Stories (with Equinor statements)", "date": "2025-10-07", "url": "https://www.microsoft.com/en/customers/story/25408-equinor-microsoft-azure-data-manager-for-energy", "locator": "Lines 28–38, 47–59, 62–67", "access": "directly opened vendor customer story", "supports": "OSDU-aligned Azure deployment, data silos and manual work, implementation/maintenance and on-prem compute caveats, Equinor's cloud well-log scale claim and lack of implementation cost/AI outcome." }, { "title": "Business Perspective of EDS", "publisher": "OSDU Data Platform documentation, The Open Group pages", "date": "2025-09-09", "url": "https://osdu.pages.opengroup.org/platform/data-flow/ingestion/osdu-airflow-lib/business-value/", "locator": "Lines 65–87, 93–102", "access": "directly opened OSDU documentation", "supports": "pre-EDS manual fetching/custom ETL/delay; EDS scheduled and incremental ingestion; operator setup required for reference mapping; provider wrapper as an interoperability mechanism." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Both sources reopened directly. OSDU documentation explicitly describes standardizing data exchange and the EDS design approach; Microsoft customer story provides Equinor's implementation context and caveats. No unsupported lock-in or realized cost claim should be introduced.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R16-LIMITS-01", "verdict": "confirmed", "patch": { "claim": "Equinor/Microsoft report an OSDU-aligned Azure Data Manager configuration integrated into OMNIA and say hundreds of thousands of quality-controlled well logs are stored in cloud. The story says OSDU can be difficult to implement/maintain and on-prem instances may lack compute/scalability. OSDU EDS docs describe prior manual fetching/custom ETL and delay, and state reference mapping needs operator configuration. The evidence supports integration/implementation diligence; it does not show Equinor incurred a measured migration penalty, vendor lock-in or an exit failure.", "economics": "No actual migration cost, egress fee, measured integration labor or migration ROI is disclosed. Equinor's quoted '250 years' is a vendor-published counterfactual and not an independently audited saving.", "existing_ids": [] }, "reason": "Both sources reopened directly. OSDU documentation explicitly describes standardizing data exchange and the EDS design approach; Microsoft customer story provides Equinor's implementation context and caveats. No unsupported lock-in or realized cost claim should be introduced.", "sources_inspected": [ { "url": "https://www.microsoft.com/en/customers/story/25408-equinor-microsoft-azure-data-manager-for-energy", "access": "direct vendor customer story reopened", "locator": "Lines 30–38, 47–59, 62–67; includes vendor/customer assertions, OSDU implementation caveat and 250-year counterfactual." }, { "url": "https://osdu.pages.opengroup.org/platform/data-flow/ingestion/osdu-airflow-lib/business-value/", "access": "direct OSDU documentation reopened", "locator": "Lines 65–87, 93–103; manual/custom ETL, delay, EDS features, partial mapping automation and page date." } ], "recommended_disposition": "retain as procurement and integration context; exclude any vendor-lock-in or realized-economics score" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R16-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Equinor customer story dated 2025-10-07; OSDU EDS documentation current as of 2025-09-09." }, { "id": "T10-R02-LIMITS-02", "company": "Halliburton / Eni", "title": "Closed-loop surface, subsurface and managed-pressure drilling integration offshore Indonesia", "category": "drilling controls / MPD and rig equipment integration", "kind": "update", "ai_role": "automation/closed-loop orchestration confirmed; this release does not specify a machine-learning method.", "asset": "Eni deepwater exploration well offshore Indonesia; well/field name not disclosed.", "stage": "Halliburton-announced successful deployment on one deepwater exploration well; described as first full rig automation + MPD deployment in Asia-Pacific.", "operating_period": "Reported 2026-07-09; exact drilling dates and well identifier not provided.", "claim": "Halliburton says one deepwater exploration well with Eni offshore Indonesia; >15% efficiency is undefined. Preserve as supplier-reported and do not treat 'industry first' or 'scales' language as independent verification.", "economics": "No absolute rig hours, cost, NPT delta, pressure excursion statistics, or contract terms disclosed.", "baseline": "No metric definition, comparator well, time period, or efficiency denominator accompanies >15% in the press release.", "limits": "Source is Halliburton’s supplier release, though Eni is named. One well does not establish general deepwater replicability, full automation boundary, safe fallback, or failure rates. “Industry first” is provider framing. No AI-specific method in this source.", "relationship": "New dated operator deployment/update for the existing Halliburton LOGIX autonomous drilling platform (AI-016). Adds a different named offshore customer and integration boundary including MPD. Keep it as a sourced event under the existing product, not a new AI initiative.", "decision_question": "For an operator evaluating closed-loop drilling plus MPD, what were the actual controllable parameters, hold points, human override/failsafe rules, pressure excursions, uptime/NPT, and baseline behind the >15% efficiency figure?", "company_key": "Halliburton", "run": "Rounds 1–10", "disposition": "enrich AI-016; keep source metric caveat", "sources": [ { "title": "Eni and Halliburton Achieve Industry First With Closed-Loop Rig Automation in Deepwater Indonesia", "publisher": "Halliburton", "date": "2026-07-09", "url": "https://ir.halliburton.com/node/36466/pdf", "locator": "One-page official release, lines 0-20; deployment, integrated control stack, >15% efficiency claim", "access": "Official Halliburton investor PDF opened directly", "supports": "Eni/operator name, Indonesia deepwater well, surface/subsurface/MPD integration and provider-reported >15% efficiency." } ], "references": [ { "id": "AI-016", "relationship": "New dated operator deployment/update for the existing Halliburton LOGIX autonomous drilling platform (AI-016). Adds a different named offshore customer and integration boundary including MPD. Keep it as a sourced event under the existing product, not a new AI initiative." } ], "review": { "verdict": "correct", "reason": "Opened source text states one well, integrated surface/placement/downhole/MPD control stack and >15% figure. No absolute time, NPT, denominator, well name or operator-authored statement. No failure or safety incident evidence.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R02-LIMITS-02", "verdict": "correct", "patch": { "claim": "Halliburton says one deepwater exploration well with Eni offshore Indonesia; >15% efficiency is undefined. Preserve as supplier-reported and do not treat 'industry first' or 'scales' language as independent verification.", "ai_role": "automation/closed-loop orchestration confirmed; this release does not specify a machine-learning method.", "canonical_overlap": "AI-016 LOGIX platform; named Eni event updates existing platform record." }, "reason": "Opened source text states one well, integrated surface/placement/downhole/MPD control stack and >15% figure. No absolute time, NPT, denominator, well name or operator-authored statement. No failure or safety incident evidence.", "recommended_disposition": "enrich AI-016; keep source metric caveat", "sources_checked": [ { "url": "https://ir.halliburton.com/node/36466/pdf", "access_status": "primary supplier release PDF reopened directly", "date": "2026-07-09", "locator": "lines 0–17, especially lines 2–8 and 16–17" } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R02-LIMITS-02", "core_company": true, "ai_ids": [ "AI-016" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Reported 2026-07-09; exact drilling dates and well identifier not provided." }, { "id": "T10-R07-LIMITS-01", "company": "Helmerich & Payne", "title": "Private-equity-backed independents are in the buyer pool, but H&P discloses no PE-specific technology adoption", "category": "Drilling supplier commercial channel / buyer concentration", "kind": "context", "ai_role": "The filing describes H&P's drilling-technology portfolio broadly but does not identify an AI or non-AI technology purchase, feature, or result for PE-backed customers.", "asset": "H&P U.S. land drilling and North America Solutions customer base; no specific private-equity-backed operator or asset named.", "stage": "FY2025 operating/customer-mix disclosure; 144 of 223 marketed U.S. rigs were active at 2025-09-30. Of active rigs, 73 were on fixed-term contracts and 71 working well-to-well.", "operating_period": "Fiscal year ended 2025-09-30; point-in-time fleet data at 2025-09-30.", "claim": "H&P states PE-backed private operators exist in its U.S. customer segment. Its largest North America customer is unnamed and represents 18.2% ($429.4m) of North America Solutions revenue, not consolidated company revenue. 73 fixed-term and 71 well-to-well contracts are rig-count data, not buyer counts or technology procurement mix.", "economics": "Filing gives aggregate vendor revenue concentration, not technology-specific price, adoption, savings or margin. Largest North America customer revenue is not identified as PE-backed. No procurement timelines, software/equipment contracting terms, or PE-specific return data provided.", "baseline": "As of September 30, 2025, H&P had 144 active out of 223 marketed U.S. rigs, with 73 active under fixed-term contracts and 71 working well-to-well. These are rig counts, not technology adoption rates or customer counts.", "limits": "Do not present the presence of PE-backed customers as evidence H&P sells FlexRobotics or another technology to PE-backed buyers. The largest customer is not named and its ownership is unspecified. Contract mix may matter to commercial durability but filing does not state technology revenue is tied to either contract type. This establishes a buyer-segment lead, not a GTM channel success case.", "relationship": "Do not infer PE ownership for largest customer or associate any customer with FlexRobotics (AI-116) without direct project evidence.", "decision_question": "Can a supplier or PE-backed operator source identify which technologies are procured at which assets, who owns the operating budget, whether contract term changes the procurement case, and what deployment economics are shared after service pricing?", "company_key": "Helmerich & Payne", "run": "Rounds 1–10", "disposition": "background channel context; don't count as a deployment", "sources": [ { "title": "Helmerich & Payne, Inc. 2025 Form 10-K", "publisher": "Helmerich & Payne / U.S. SEC", "date": "2025-11-20; fiscal year ended 2025-09-30", "url": "https://www.sec.gov/Archives/edgar/data/46765/000004676525000071/hp-20250930.htm", "locator": "Lines 368–392 (customer mix, activity and technology generalities); 398–403 (PE-backed customer segment and largest North America customer concentration)", "access": "Primary SEC filing opened directly", "supports": "PE-backed operators are an acknowledged buyer segment, with supplier fleet/contract mix and concentration. No customer-level ownership or product-level adoption disclosure." } ], "references": [], "review": { "verdict": "confirm", "reason": "Primary FY2025 Form 10-K confirms figures and customer segment. This is only a channel context, not a tech adoption case; no failure classification applies.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R07-LIMITS-01", "verdict": "confirm", "patch": { "claim": "H&P states PE-backed private operators exist in its U.S. customer segment. Its largest North America customer is unnamed and represents 18.2% ($429.4m) of North America Solutions revenue, not consolidated company revenue. 73 fixed-term and 71 well-to-well contracts are rig-count data, not buyer counts or technology procurement mix.", "relationship": "Do not infer PE ownership for largest customer or associate any customer with FlexRobotics (AI-116) without direct project evidence." }, "reason": "Primary FY2025 Form 10-K confirms figures and customer segment. This is only a channel context, not a tech adoption case; no failure classification applies.", "recommended_disposition": "background channel context; don't count as a deployment", "sources_checked": [ { "url": "https://www.sec.gov/Archives/edgar/data/46765/000004676525000071/hp-20250930.htm", "access_status": "primary SEC Form 10-K reopened directly", "date": "FY ended 2025-09-30; filing 2025", "locator": "lines 368–392 and 398–399" } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R07-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Fiscal year ended 2025-09-30; point-in-time fleet data at 2025-09-30." }, { "id": "T20-R19-LIMITS-01", "company": "McKinsey survey of oilfield services and equipment leaders", "title": "Oilfield-service firms are scaling gen AI more slowly than they expected", "category": "industry_survey_and_market_sizing", "kind": "context", "ai_role": "Survey concerns generative AI among oilfield services and equipment (OFSE) providers; report's modeled opportunity spans generative and analytical AI in their current operations.", "asset": "Survey population: 164 executives representing integrated service providers, EPC firms, equipment manufacturers and services-focused companies across global onshore/offshore markets; company annual revenues ranged from >$50m to >$5bn.", "stage": "May 2025 survey results published April 1, 2026; adoption/self-report and modeled sector potential, not specific deployments.", "operating_period": "2023 expectation survey compared with May 2025 reported adoption; article published 2026-04-01.", "claim": "McKinsey says the May 2025 OFSE executive survey included 164 executives from providers, EPCs, equipment makers and services firms. Article text says less than 25% of companies progressed beyond pilot (lines 18–20); a separate comparison says the 2023 survey expected >70% to be piloting/scaling by 2025, whereas the 2025 report says <25% showed some use and 1% significant scale (line 52). Because definitions/wave denominators are not given in inspected text, present this as a directional reported gap, not a matched-cohort adoption decline. $12–20bn is modeled annual EBITDA potential; 65% is hypothetical allocation intent, not spend.", "economics": "$12–20bn annual EBITDA is McKinsey's potential opportunity estimate with no realized company-level denominator; 65% of survey leaders said they would prioritize digital infrastructure and AI if allocating hypothetical $1bn, which is stated preference, not approved budget.", "baseline": "Reported 2023 forecast and 2025 stage statistics are not shown with comparable wave Ns or matched definitions in article text; retain as a reported directional comparison only.", "limits": "Consulting estimate and self-reported survey; 164 executive sample is not a population census, the article text does not disclose response rate or 2023 wave N, and the modeled sector opportunity is not realized value. OFSE supplier data do not establish upstream-operator adoption.", "relationship": "Industry survey context only; do not convert into company deployment records or represent supplier survey findings as operator adoption rates.", "decision_question": "For an upstream buyer/provider GTM case, which named operating workflow and eligible population underlie the business case, what implementation and integration costs are included, and what achieved financial metric is audited after scale?", "company_key": "McKinsey", "run": "Rounds 11–20", "disposition": "retain as supplier-market context; no operator adoption rate or realized ROI claim", "sources": [ { "title": "Gen AI in the OFSE industry: Progress lags behind intent", "publisher": "McKinsey & Company", "date": "2026-04-01", "url": "https://www.mckinsey.com/industries/oil-and-gas/our-insights/gen-ai-in-the-ofse-industry-progress-lags-behind-intent", "locator": "Lines 4–25 (scope, sample, adoption and potential); lines 45–63 (investment intent and scaling barriers)", "access": "directly opened primary report page", "supports": "May 2025 survey N=164 and respondent profile; <25% beyond pilot, 1% significant scale; 2023 >70% expectation; $12–20bn potential estimate; ROI quantification and implementation cost barriers." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct report reopen confirms all numbers. Text uses both 'progressed beyond pilot' and 'showing some use' around the <25% figure; separate the two phrasings and state that the 2023/2025 comparison is directional because the inspected article does not give matched denominators/definitions. Other values are correctly qualified as potential/preference.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R19-LIMITS-01", "verdict": "correct", "patch": { "claim": "McKinsey says the May 2025 OFSE executive survey included 164 executives from providers, EPCs, equipment makers and services firms. Article text says less than 25% of companies progressed beyond pilot (lines 18–20); a separate comparison says the 2023 survey expected >70% to be piloting/scaling by 2025, whereas the 2025 report says <25% showed some use and 1% significant scale (line 52). Because definitions/wave denominators are not given in inspected text, present this as a directional reported gap, not a matched-cohort adoption decline. $12–20bn is modeled annual EBITDA potential; 65% is hypothetical allocation intent, not spend.", "baseline": "Reported 2023 forecast and 2025 stage statistics are not shown with comparable wave Ns or matched definitions in article text; retain as a reported directional comparison only.", "limits": "Consulting estimate and self-reported survey; 164 executive sample is not a population census, the article text does not disclose response rate or 2023 wave N, and the modeled sector opportunity is not realized value. OFSE supplier data do not establish upstream-operator adoption." }, "reason": "Direct report reopen confirms all numbers. Text uses both 'progressed beyond pilot' and 'showing some use' around the <25% figure; separate the two phrasings and state that the 2023/2025 comparison is directional because the inspected article does not give matched denominators/definitions. Other values are correctly qualified as potential/preference.", "sources_inspected": [ { "url": "https://www.mckinsey.com/industries/oil-and-gas/our-insights/gen-ai-in-the-ofse-industry-progress-lags-behind-intent", "access": "direct report page reopened", "locator": "Lines 16–25 (N, OFSE population, beyond-pilot and modeled value); lines 45–52 (hypothetical $1bn allocation, expectation comparator and significant-scale statistic); lines 60–63 (barriers/ROI)." } ], "recommended_disposition": "retain as supplier-market context; no operator adoption rate or realized ROI claim" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R19-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "2023 expectation survey compared with May 2025 reported adoption; article published 2026-04-01." }, { "id": "R1-LIM-03", "company": "Oil Sands Alliance members / Canadian Natural Resources as proponent", "title": "Pathways CO2 transportation network and storage hub serving oil-sands facilities", "category": "CCS infrastructure with direct upstream oil-sands emissions-intensity link", "kind": "context", "ai_role": "No AI role. Potential AI relevance is secondary: measurement, monitoring, verification, maintenance and capture-plant operations after facilities exist; not evidence of AI demand or deployment today.", "asset": "Northeast Alberta oil-sands operations, CO2 pipeline network and geologic storage hub. Canadian Natural is the proponent; five large oil-sands producers participate in the 2026 agreement (Canadian Natural, Cenovus, ConocoPhillips Canada, Imperial, Suncor).", "stage": "As of July 2026, describe as governments and Oil Sands Alliance agreeing to advance construction, with policy/fiscal framework; not as FID, completed permitting, construction completion, injection, or operating capture. May agreement itself said the trilateral MOU remained to be concluded; July announcement says an agreement was reached.", "operating_period": "2025-08 project overview; 2026-05-15 implementation agreement; 2026-07-02 Canada-Alberta announcement. All are within the window.", "claim": "Observable result is change from conditional proposal to a policy-backed agreement to advance, not technology operation. The 2026 agreement makes pipeline and Pathways construction mutually dependent and specifies carbon pricing, credits, contracts-for-difference, and other fiscal mechanisms; the federal-provincial parties state current CCUS ITC rates are extended to 2035. The old 2025 schedule was conditional on approvals and sufficient fiscal support. No realized capture or emissions result is evidenced.", "economics": "No project capex or cost-per-tonne confirmed in sources checked.", "baseline": "Not disclosed", "limits": "The latest announcement is political/industry agreement, not FID, completed permitting, EPC contract, or measured CCS operation. The 2025 overview is proponent-prepared and frames project aims. The 2026 6 Mtpa minimum in-service-by-2035 target cannot be treated as achieved. No capital cost or cost per tonne was validated in the opened primary sources. July 2026 agreement ties the CCS project to a proposed oil export pipeline; commercial and policy dependency remains material.", "relationship": "Track policy and proposed transport/storage infrastructure as an upstream capital dependency, but no operating performance, injection, or commercial outcome is established.", "decision_question": "What is sanctioned project capex, capture-by-operator spend, $/tonne delivered, financing/tax-credit dependence and pipeline/permits critical path?", "company_key": "Oil Sands Alliance members", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "Pathways Alliance: Project Overview", "publisher": "Pathways Alliance / Canadian Natural on behalf of Alliance members", "date": "2025-08", "url": "https://oilsandsalliance.ca/wp-content/uploads/2025/08/Project-Overview.pdf", "locator": "Project is proposed; each operator manages facility capture; pipeline critical path; schedule conditional on regulatory/policy/fiscal certainty; source PDF pages 2 and 18.", "access": "Opened; proponent source", "supports": "2025 planned state, infrastructure split, dependencies and conditional schedule; not independent performance evidence." }, { "title": "Implementation Agreement for the Canada-Alberta Memorandum of Understanding of November 27, 2025", "publisher": "Prime Minister of Canada / Government of Canada and Alberta agreement", "date": "2026-05-15", "url": "https://www.pm.gc.ca/en/news/backgrounders/2026/05/15/implementation-agreement-canada-alberta-memorandum-understanding", "locator": "Pathways sections 3.1–3.8: alliance participants; mutual dependence on oil pipeline; 6 Mtpa CCUS minimum by 2035; fiscal support and tax credit commitments.", "access": "Opened; government primary document", "supports": "Current formal objectives, dependency, partners and public support mechanisms." }, { "title": "Canada and Alberta advance west coast pipeline project proposal and Pathways Project Carbon Capture Initiative", "publisher": "Prime Minister of Canada / Government of Canada", "date": "2026-07-02", "url": "https://www.pm.gc.ca/en/news/news-releases/2026/07/02/canada-and-alberta-advance-west-coast-pipeline-project-proposal-and", "locator": "Announcement that the governments and Oil Sands Alliance reached an agreement to advance construction; statement of combined 16 Mtpa objective.", "access": "Opened; government primary source", "supports": "Current milestone and political framing; not evidence that FID, construction or injection has occurred." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-08", "url": "https://oilsandsalliance.ca/wp-content/uploads/2025/08/Project-Overview.pdf", "locator": "Project overview pp.1,6,18: proposed shared transport/storage network; schedule conditional on approvals/policy.", "access": "issuer/alliance PDF opened in prior round; proponent-prepared", "supports": "The new government sources strengthen evidence of policy commitment but do not establish technical performance or commercial sanction. Preserve the distinction between the proposed network, individual operator capture projects, and future emissions targets." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-05-15", "url": "https://www.pm.gc.ca/en/news/backgrounders/2026/05/15/implementation-agreement-canada-alberta-memorandum-understanding", "locator": "Sections 3.1–3.7, esp. 3.3–3.5: commitments, dependencies and emissions milestones.", "access": "government HTML opened", "supports": "The new government sources strengthen evidence of policy commitment but do not establish technical performance or commercial sanction. Preserve the distinction between the proposed network, individual operator capture projects, and future emissions targets." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-07-02", "url": "https://www.pm.gc.ca/en/news/news-releases/2026/07/02/canada-and-alberta-advance-west-coast-pipeline-project-proposal-and", "locator": "Announcement of agreement to advance Pathways; pipeline proposal referred to Major Projects Office.", "access": "government HTML opened", "supports": "The new government sources strengthen evidence of policy commitment but do not establish technical performance or commercial sanction. Preserve the distinction between the proposed network, individual operator capture projects, and future emissions targets." } ], "references": [ { "id": "AI-098", "relationship": "company_context" }, { "id": "AI-279", "relationship": "company_context" } ], "department": "Water, emissions & energy", "group_id": "R1-LIM-03", "core_company": false, "ai_ids": [ "AI-098", "AI-279" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R17-GLOBAL-01", "company": "PETRONAS Malaysia Petroleum Management (MPM)", "title": "Malaysia upstream introduces normally unattended facilities and remote/autonomous operations guideline", "category": "Operating-model standard / normally unattended offshore facilities", "kind": "context", "ai_role": "Guideline refers to remote and autonomous operations; it does not specify an AI method, model, control authority, vendor, or use of AI. Do not classify this as an AI deployment.", "asset": "Malaysia upstream sector; guideline applies across facilities and the article gives no specific field, platform, operator cohort or producing asset as deployed.", "stage": "Guideline introduced in 2025; MPM forecasts that 30% of field operations will feature NUF-RAO capabilities by 2033. No implementation date, qualification criteria, commissioned facility or rollout cohort is disclosed.", "operating_period": "Published 2025-06-20; AuDi 2025 event held 2025-04-21. Forecast horizon to 2033.", "claim": "MPM introduced a Normally Unattended Facilities with Remote & Autonomous Operations guideline, describing potential to unlock marginal fields, extend asset life and improve safety. It states CAPEX and OPEX cost cutting of up to 25% as potential and links the initiative to MPM's aspiration of sustaining 2,000 kboe/d. It anticipates 30% of field operations will have such capabilities by 2033. These are stated potentials/forecast, not actual outcomes or evidence of 2,000 kboe/d causal support.", "economics": "No realized CAPEX/OPEX savings, denominator, project cost, incremental production, emissions change or facility-level economics disclosed. Up to 25% is a potential ceiling, not an observed result.", "baseline": "No baseline operating model, staffing, visits, uptime, operating cost, emissions, or reference field cohort is supplied. The 2,000 kboe/d figure is an MPM sector aspiration, not the guideline's measured contribution.", "limits": "Issuer/regulator-like sector management release describes direction and intended benefit. The source does not define technical requirements, minimum instrumentation, communications reliability, safety-integrity boundaries, human intervention model, or evidence required for classification. Treat as policy/operating-model context and a follow-up lead, not as an operating deployment or AI case.", "relationship": "No specific NUF-RAO asset/project match was identified in checked production records. Treat the guideline as cross-operator operating-model context. It may frame future PETRONAS/Malaysia cases but does not enrich any project absent exact asset and same-project evidence.", "decision_question": "Which fields have been qualified and commissioned under this guideline, and what matched facility-level evidence supports savings, uptime, safety and emissions claims after accounting for communications, maintenance and emergency-response costs?", "company_key": "PETRONAS", "run": "Rounds 11–20", "disposition": "include_as_policy_context_not_deployment", "sources": [ { "title": "Executive Annual Dialogue (AuDi) 2025: Driving Project Excellence, Technology, Innovation, and Collaboration in Malaysia’s Oil & Gas Sector", "publisher": "Malaysia Petroleum Management, PETRONAS", "date": "2025-06-20", "url": "https://www.petronas.com/mpm/media/media-releases/executive-annual-dialogue-audi-2025-driving-project-excellence-technology", "locator": "Lines 62-75: event and publication dates, guideline, potential benefits and 2033 forecast.", "access": "Issuer HTML opened directly; full text available", "supports": "Guideline introduction and exact forecast/aspirational figures; no disclosed actual deployment result." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened PETRONAS MPM's June 20, 2025 release. It calls NUF-RAO a guideline, says up to 25% CAPEX/OPEX reduction is potential, and forecasts 30% of field operations with NUF-RAO by 2033. The record preserves these as potential/forecast and does not call this a deployment or AI use case. No correction needed.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R17-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened PETRONAS MPM's June 20, 2025 release. It calls NUF-RAO a guideline, says up to 25% CAPEX/OPEX reduction is potential, and forecasts 30% of field operations with NUF-RAO by 2033. The record preserves these as potential/forecast and does not call this a deployment or AI use case. No correction needed.", "sources_inspected": [ { "url": "https://www.petronas.com/mpm/media/media-releases/executive-annual-dialogue-audi-2025-driving-project-excellence-technology", "access": "Directly opened PETRONAS MPM primary HTML", "locator": "Lines 58–75: publication/event dates, guideline introduction, potential savings and 2033 forecast." } ], "recommended_disposition": "include_as_policy_context_not_deployment" } ] }, "department": "Production & process operations", "group_id": "T20-R17-GLOBAL-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Published 2025-06-20; AuDi 2025 event held 2025-04-21. Forecast horizon to 2033." }, { "id": "T10-R01-GLOBAL-01", "company": "Petrobras / Libra consortium", "title": "Mero Permanent Reservoir Monitoring (PRM) seabed fiber-optic seismic network", "category": "subsurface sensing / permanent 4D seismic monitoring", "kind": "new_initiative", "ai_role": "The physical system is a seabed network of optical sensors/cables acquiring seismic data over time. Petrobras separately says it will use AI with UFRJ to capture information continuously from PRM; the model, task boundary, operating state and measured incremental AI value are not specified. Do not label the sensor network itself as AI.", "asset": "Mero field, Libra block, Santos Basin, Brazil. Phase one monitors FPSOs Guanabara (Mero 1) and Sepetiba (Mero 2); phase two is for Duque de Caxias (Mero 3) and Alexandre de Gusmão (Mero 4).", "stage": "Phase one installation completed March 2026; first data collection was stated for Q2 2026. Phase two construction was ongoing in April 2026 and was expected to complete in 2027. The source does not confirm first-data receipt or reservoir-management result.", "operating_period": "Phase-one installation completed by March 2026; reporting source dated 2026-04-14.", "claim": "Phase one was completed in March 2026 (>460 km over 222 km²), with first data collection scheduled for Q2 2026; phase two (>316 km over 140 km²) was under construction for completion in 2027. The approximately US$450m is total project investment by Petrobras and Libra partners—not savings, ROI, or a proven realized PRM-only cost-benefit. Mero field production above 680 kb/d in Jan 2026 is contextual, not PRM-attributed. AI with UFRJ is a stated data-use layer, distinct from physical sensing.", "economics": "Issuer-reported total project investment of about US$450 million. No phase-specific cost, operating cost, matched production baseline, realized incremental recovery or cash benefit is given. Petrobras cites Mero average monthly production above 680,000 b/d in January 2026 as field context, not a PRM-attributed result.", "baseline": "No pre-PRM controlled comparison or production/recovery outcome; initial data collection only planned for Q2 2026 in the dated source.", "limits": "The scale and asset scope are unusually concrete, but performance is prospective. Company calls it the world's most extensive seismic-monitoring project; do not treat superlative as independently benchmarked. AI role is planned/described as continuous information capture with UFRJ, not an attributed production benefit. HISEP is a separate Mero subsea process technology and remains separately listed as GAP-HISEP-01 in the previous round.", "relationship": "New physical sensing infrastructure with a disclosed, separate AI use; no exact same-project canonical record found. This is complementary to, not a replacement for, AI and conventional reservoir interpretation.", "decision_question": "After first data arrive, does PRM change reservoir-management decisions enough to improve production/recovery or reduce intervention risk, and which measured benefit belongs to sensing, interpretation, or AI? What are full installation, maintenance and data-operations costs across the four FPSO areas?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "enrich_existing", "sources": [ { "title": "Petrobras investirá US$450 milhões no maior projeto de monitoramento sísmico mundial", "publisher": "Agência Petrobras / Petrobras", "date": "2026-04-14", "url": "https://agencia.petrobras.com.br/w/negocio/petrobras-investir%C3%A1-us-450-milh%C3%B5es-no-maior-projeto-de-monitoramento-s%C3%ADsmico-mundial", "locator": "Lines 45-50 and 61-72; phase-one completion, cable lengths/areas, asset coverage, project investment, data timing, AI/UFRJ statement.", "access": "Official page opened; relevant text directly reviewed (Portuguese).", "supports": "Asset, method, dates, scale, reported investment, planned first data/second phase and explicit AI relationship." }, { "title": "Annual Report and Form 20-F 2025", "publisher": "Petrobras", "date": "2026 (2025 filing)", "url": "https://petrobras.com.br/documents/2677942/17808296/FORM%2B20F%2B2025%2BEN.pdf/3b6371b3-900d-ae05-294d-f9acd9d8b26e?download=true&t=1777312960000&version=1.0", "locator": "Printed p.83, PRM paragraph; first seismic acquisition scheduled for 2026; network connected to Sepetiba and Marechal Duque de Caxias.", "access": "Official PDF indexed text reviewed; direct PDF open returned internal error.", "supports": "Independent current filing confirmation of PRM method and source-stated 2026 acquisition schedule." } ], "references": [ { "id": "AI-219", "relationship": "company_context", "basis": "Petrobras machine-learning well-configuration record; no evidence it is the PRM system or same project." }, { "id": "AI-220", "relationship": "company_context", "basis": "Petrobras predictive monitoring/integrated-operations-control record; no source-level PRM identity or same-project link." } ], "review": { "verdict": "correct", "reason": "Direct issuer page confirms dates, scope and wording. Separate sensor infrastructure from its planned AI/data use; first data and investment do not demonstrate recovery uplift.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R01-GLOBAL-01", "verdict": "correct", "patch": { "claim": "Phase one was completed in March 2026 (>460 km over 222 km²), with first data collection scheduled for Q2 2026; phase two (>316 km over 140 km²) was under construction for completion in 2027. The approximately US$450m is total project investment by Petrobras and Libra partners—not savings, ROI, or a proven realized PRM-only cost-benefit. Mero field production above 680 kb/d in Jan 2026 is contextual, not PRM-attributed. AI with UFRJ is a stated data-use layer, distinct from physical sensing." }, "reason": "Direct issuer page confirms dates, scope and wording. Separate sensor infrastructure from its planned AI/data use; first data and investment do not demonstrate recovery uplift.", "recommended_disposition": "enrich_existing", "sources_checked": [ { "url": "https://agencia.petrobras.com.br/w/negocio/petrobras-investir%C3%A1-us-450-milh%C3%B5es-no-maior-projeto-de-monitoramento-s%C3%ADsmico-mundial", "access_status": "Directly reopened primary issuer page in R10; relevant passages lines 45–72 inspected", "locator": "Lines 45-50 and 61-72; phase-one completion, cable lengths/areas, asset coverage, project investment, data timing, AI/UFRJ statement.", "date": "2026-04-14" }, { "url": "https://petrobras.com.br/documents/2677942/17808296/FORM%2B20F%2B2025%2BEN.pdf/3b6371b3-900d-ae05-294d-f9acd9d8b26e?download=true&t=1777312960000&version=1.0", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Printed p.83, PRM paragraph; first seismic acquisition scheduled for 2026; network connected to Sepetiba and Marechal Duque de Caxias.", "date": "2026 (2025 filing)" } ] } ] }, "department": "Subsurface & recovery", "group_id": "T10-R01-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-219", "AI-220" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Phase-one installation completed by March 2026; reporting source dated 2026-04-14." }, { "id": "T10-R01-LIMITS-01", "company": "Petrobras / Libra consortium", "title": "Petrobras plans its Mero 3 HISEP pilot for 2028", "category": "subsea process separation / produced-gas handling / emissions", "kind": "update", "ai_role": "Physical subsea separation and reinjection; no AI role disclosed. Do not infer from data systems or general automation.", "asset": "Mero 3, Santos Basin pre-salt; FPSO Marechal Duque de Caxias.", "stage": "Mero 3 FPSO began production 2024-10-30; specific Petrobras release says HISEP will be in operation from 2028. Keep HISEP as a future pilot, not broad current deployment. The 2025 20-F/business-plan passages remain indexed-only in this audit; direct PDF access was not achieved.", "operating_period": "Mero 3 FPSO first production began 2024-10-30. HISEP pilot connection/operation is scheduled for 2028 per Petrobras 2025 Form 20-F and release/planning materials.", "claim": "HISEP is a high-pressure subsea separation concept designed to separate high-CO2 gas at the seabed and reinject it, relieving topside gas-processing bottlenecks; benefits remain intended/projected. Petrobras primary project-specific sources identify HISEP as planned at Mero 3 from 2028. This conflicts with generic current English Petrobras page saying a growing number of FPSOs already use “CCUS and Hisep.” The source evidence does not establish broad HISEP deployment; likely conflation with existing CO2 reinjection/CCUS across FPSOs.", "economics": "No HISEP-specific project cost, vendor contract value, realized production uplift, avoided topside capex, emissions outcome, or unit economics established in reviewed sources. Supplier relevance is prospective: subsea separator, pumps, controls, subsea interfaces and FPSO tie-in.", "baseline": "No comparable Mero operating case without HISEP, baseline GOR/throughput constraint, or before/after metric disclosed in reviewed materials.", "limits": "Do not describe HISEP as broadly operating, already delivering emissions/production benefits, or failed. Direct PDF opening for 20-F and Business Plan failed; relevant official indexed passages were available and corroborated by an opened Petrobras newsroom release and generic official page. Preserve source-specific stage and date.", "relationship": "Adds a discrete, material future subsea-process technology case missed by the initial sample. Keep as 2028 pilot/technology lead; do not merge it into existing generic Petrobras CCUS claims or count as an operating HISEP result.", "decision_question": "Before treating HISEP as a scalable supplier or operating opportunity, what are the qualification gates, design envelope, offshore uptime, GOR/CO2 baseline, topside capacity displaced, reinjection energy, emissions boundary, capex, and date for witnessed commissioning at Mero 3?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "include as planned-pilot lead with date/access caveat", "sources": [ { "title": "Annual Report and Form 20-F 2025", "publisher": "Petrobras", "date": "2026 (reporting year 2025)", "url": "https://petrobras.com.br/documents/2677942/17808296/FORM%2B20F%2B2025%2BEN.pdf/3b6371b3-900d-ae05-294d-f9acd9d8b26e?download=true&t=1777312960000&version=1.0", "locator": "Printed p.83, Mero Field / New Technologies: pilot will connect to FPSO Marechal Duque de Caxias in 2028", "access": "Official source search-index text reviewed; direct open returned internal error", "supports": "Mero 2025 field and FPSO context; HISEP purpose; explicit 2028 pilot-connection target." }, { "title": "Petrobras 2026-2030 Business Plan (PN 2026-30)", "publisher": "Petrobras", "date": "2025-11 (plan edition; file/query metadata; exact PDF publication date not exposed in opened page)", "url": "https://canalfornecedor.petrobras.com.br/documents/d/canal-do-fornecedor/1-apresentacao_business-plan?download=true", "locator": "Indexed slide 62: “HISEP Tecnológico” at Mero 3 and first oil expected 2028", "access": "Official plan search-index text reviewed; direct open failed due large PDF", "supports": "Official forward schedule associates the technological HISEP pilot with Mero 3 / 2028." }, { "title": "Marechal Duque de Caxias FPSO starts producing in pre-salt", "publisher": "Petrobras / Agência Petrobras", "date": "2024-10-30", "url": "https://agencia.petrobras.com.br/pt/w/negocio/navio-plataforma-marechal-duque-de-caxias-comeca-a-produzir-no-pre-sal", "locator": "Lines 81-85 per prior explicit saved primary-source check in root-source-checks.json; release says Mero 3 started oil production and HISEP planned from 2028", "access": "Official issuer page and indexed source reopened; date/locator cross-checked with saved root-source-checks.json", "supports": "Separates Mero 3 FPSO operating date from HISEP start target." }, { "title": "Exploration and production: going deep to innovate", "publisher": "Petrobras", "date": "Undated current web page; retrieved 2026-10-07", "url": "https://petrobras.com.br/en/quem-somos/exploracao-e-producao", "locator": "Lines 168-171 and 239-242: broad claim that a growing number of FPSOs use CCUS and HISEP; HISEP glossary statement", "access": "Official web page opened", "supports": "Documents the broad corporate wording that conflicts with project-specific HISEP pilot timing; not relied on to substantiate active HISEP deployments." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct project-specific Petrobras release confirms 2028 and separates operating FPSO from not-yet-operating HISEP. Keep the tension with generic current webpage copy as an evidence-scope discrepancy; do not claim it proves multiple HISEP systems are operating or that HISEP failed.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R01-LIMITS-01", "verdict": "correct", "patch": { "stage": "Mero 3 FPSO began production 2024-10-30; specific Petrobras release says HISEP will be in operation from 2028. Keep HISEP as a future pilot, not broad current deployment. The 2025 20-F/business-plan passages remain indexed-only in this audit; direct PDF access was not achieved.", "evidence_grade": "Direct opened Petrobras release for 2028 stage; the cited filing/plan are still indexed excerpts, not directly inspected PDFs." }, "reason": "Direct project-specific Petrobras release confirms 2028 and separates operating FPSO from not-yet-operating HISEP. Keep the tension with generic current webpage copy as an evidence-scope discrepancy; do not claim it proves multiple HISEP systems are operating or that HISEP failed.", "recommended_disposition": "include as planned-pilot lead with date/access caveat", "sources_checked": [ { "url": "https://agencia.petrobras.com.br/pt/w/negocio/navio-plataforma-marechal-duque-de-caxias-comeca-a-produzir-no-pre-sal", "access_status": "primary issuer page opened directly", "date": "2024-10-30", "locator": "lines 81–85: FPSO first production and HISEP operation from 2028" }, { "url": "https://petrobras.com.br/en/quem-somos/exploracao-e-producao", "access_status": "primary corporate page had been opened in R01; generic text only; not relied on for HISEP stage", "date": "undated/current page", "locator": "R01 source locators 168–171, 239–242" }, { "url": "https://petrobras.com.br/documents/2677942/17808296/FORM%2B20F%2B2025%2BEN.pdf/3b6371b3-900d-ae05-294d-f9acd9d8b26e?download=true&t=1777312960000&version=1.0", "access_status": "official indexed text only; direct open previously failed", "date": "2026 (2025 reporting year)", "locator": "R01-cited printed p.83" } ] } ] }, "department": "Production & process operations", "group_id": "T10-R01-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R03-GLOBAL-01", "company": "Petrobras", "title": "Santos Basin pre-salt CO2 reinjection program scales to 24 FPSOs", "category": "Reservoir recovery / CO2 reinjection (CCUS-EOR)", "kind": "update", "ai_role": "AI contribution to the injection program or reported outcome is not disclosed in the reviewed sources; this is a physical/process technology finding, not an AI case.", "asset": "Pre-salt reservoirs of the Santos Basin; issuer reports fleet-level coverage, not field-by-field allocation.", "stage": "Operating fleet-wide program; 24 operating FPSOs equipped with capture and reinjection systems as reported for 2025.", "operating_period": "2025 result; comparison with 2024; cumulative since program start (start year not stated in this source).", "claim": "Petrobras reports 19.6 Mt CO₂ reinjected in 2025 versus 14 Mt in 2024 and cumulative >80 Mt across systems on 24 FPSOs. This is portfolio-scale physical CCUS-EOR activity; not isolated incremental recovery, emissions avoided net of lifecycle, or technology ROI.", "economics": "No per-field incremental production, cost per tonne, injection CAPEX/OPEX, or net recovery value disclosed in reviewed source.", "baseline": "Annual reinjection comparator: 14 million tonnes in 2024; 19.6 million tonnes in 2025. This is throughput growth, not an incremental oil-recovery baseline.", "limits": "Issuer-reported aggregate only; no attribution of additional barrels to CO2 vs depletion, water injection, field mix, or other interventions. CO2 reinjection is also used to avoid venting reservoir CO2. Do not treat volume growth as proof of EOR economics or net emissions benefit.", "relationship": "These are corporate AI-register context records only, not same-project duplicates. Existing Petrobras pre-salt Mero PRM research is an adjacent digital monitoring project, not this basin-wide CCUS-EOR program.", "decision_question": "What field-level evidence and cost data would be required before treating high-throughput CO2 reinjection as a repeatable, economic recovery advantage rather than emissions management plus pressure support?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "include", "sources": [ { "title": "Climate Change and Energy Transition Supplement 2025", "publisher": "Petrobras", "date": "2026 publication; reports 2025 results", "url": "https://petrobras.com.br/documents/2677942/9192383/Caderno%2Bdo%2BClima%2B2025%2Bingl%C3%AAs%2Bfinal_rev1.pdf/3809f8ca-4def-7df7-7e6e-0ee811d49a90?download=true&t=1779219386000&version=1.0", "locator": "PDF pp. 100, 114 (lines 3614-3617, 3979-3987)", "access": "Direct PDF opened", "supports": "2025 and 2024 volumes, cumulative >80 Mt, 24 FPSOs, Santos Basin and CCUS-EOR framing." }, { "title": "CCUS", "publisher": "Petrobras Agência", "date": "Undated current issuer explainer; accessed 2026-10-07", "url": "https://agencia.petrobras.com.br/pt/w/ccus", "locator": "Section on CO2 capture and reinjection; indexed issuer page", "access": "Issuer page indexed; direct text not opened", "supports": "WAG mechanism and pressure-maintenance/EOR explanation." } ], "references": [ { "id": "AI-219", "relationship": "These are corporate AI-register context records only, not same-project duplicates. Existing Petrobras pre-salt Mero PRM research is an adjacent digital monitoring project, not this basin-wide CCUS-EOR program." }, { "id": "AI-220", "relationship": "These are corporate AI-register context records only, not same-project duplicates. Existing Petrobras pre-salt Mero PRM research is an adjacent digital monitoring project, not this basin-wide CCUS-EOR program." } ], "review": { "verdict": "correct", "reason": "Issuer climate report provides throughput/installed-system scope, but no counterfactual recovery or economics. Avoid treating gross reinjection as net abatement or attributing to AI.", "cross_audits": [ { "assignment": "round-03-global.json", "finding_id": "T10-R03-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": { "removed": [ "AI-219", "AI-220", "AI-221" ], "added": [ "AI-219", "AI-220" ] } }, "reason": "AI-221 is Petrobras market-forecasting AI and removed; AI-219/220 are company-level AI context only, not this basin-wide CCUS-EOR project.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local canonical production register read", "locator": "initiatives; exact ID, Company, Initiative fields" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R03-GLOBAL-01", "verdict": "correct", "patch": { "claim": "Petrobras reports 19.6 Mt CO₂ reinjected in 2025 versus 14 Mt in 2024 and cumulative >80 Mt across systems on 24 FPSOs. This is portfolio-scale physical CCUS-EOR activity; not isolated incremental recovery, emissions avoided net of lifecycle, or technology ROI." }, "reason": "Issuer climate report provides throughput/installed-system scope, but no counterfactual recovery or economics. Avoid treating gross reinjection as net abatement or attributing to AI.", "recommended_disposition": "include", "sources_checked": [ { "url": "https://petrobras.com.br/documents/2677942/9192383/Caderno%2Bdo%2BClima%2B2025%2Bingl%C3%AAs%2Bfinal_rev1.pdf/3809f8ca-4def-7df7-7e6e-0ee811d49a90?download=true&t=1779219386000&version=1.0", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "PDF pp. 100, 114 (lines 3614-3617, 3979-3987)", "date": "2026 publication; reports 2025 results" }, { "url": "https://agencia.petrobras.com.br/pt/w/ccus", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Section on CO2 capture and reinjection; indexed issuer page", "date": "Undated current issuer explainer; accessed 2026-10-07" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R03-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-219", "AI-220" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "2025 result; comparison with 2024; cumulative since program start (start year not stated in this source)." }, { "id": "T10-R06-GLOBAL-02", "company": "Petrobras", "title": "Ativo 360 and operational-data integration described in 2025 Form 20-F", "category": "Enterprise operations platform / asset data and analytics", "kind": "context", "ai_role": "The filing explicitly positions Ativo 360 alongside predictive insights/recommendations and separately describes AI usage. Do not count the platform itself as a single AI deployment or infer which functions are AI-based absent use-case detail.", "asset": "Petrobras corporate operations; no named asset, basin or platform denominator identified in the filing excerpt.", "stage": "Described as a platform in use; extent and business-unit deployment not stated.", "operating_period": "Fiscal 2025, SEC filing date 2026-04-09.", "claim": "Ativo 360 is described in the 2025 Form 20-F as an operational-data integration platform associated with predictive insights/recommendations. The filing separately describes AI use cases but does not establish that all Ativo 360 functions are AI-based or quantify platform outcomes.", "economics": "No Ativo 360 investment, license/integration cost, deployment count, uptime/maintenance effect, or realized value disclosed in excerpt.", "baseline": "No adoption denominator or before/after comparison stated.", "limits": "SEC filing is an issuer representation, but platform-level scope, underlying product architecture, specific assets, deployment date and division between conventional analytics and AI are unspecified. Treat as context, not measurable performance.", "relationship": "These are company-level AI register records; this corporate platform disclosure is complementary and not a same-project duplicate. No source-level match to a named existing Petrobras initiative was identified.", "decision_question": "Can the company disclose the platform's deployment footprint, AI/non-AI boundary, workflow owner and audited operating outcomes without treating a shared data layer as value in itself?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "enrich_existing", "sources": [ { "title": "Petrobras Annual Report and Form 20-F 2025", "publisher": "Petrobras / U.S. Securities and Exchange Commission", "date": "Filed 2026-04-09", "url": "https://www.sec.gov/Archives/edgar/data/1119639/000129281426002168/pbrform20f_2025.htm", "locator": "Business section, Research, Development and Innovation; SEC-indexed filing excerpt (page 149 of annual report)", "access": "SEC filing and accession index searched/opened; filing content returned as indexed primary excerpt", "supports": "Ativo 360 platform description and separate AI-use examples; limits on scale/attribution." } ], "references": [ { "id": "AI-219", "relationship": "These are company-level AI register records; this corporate platform disclosure is complementary and not a same-project duplicate. No source-level match to a named existing Petrobras initiative was identified." }, { "id": "AI-220", "relationship": "These are company-level AI register records; this corporate platform disclosure is complementary and not a same-project duplicate. No source-level match to a named existing Petrobras initiative was identified." }, { "id": "AI-221", "relationship": "These are company-level AI register records; this corporate platform disclosure is complementary and not a same-project duplicate. No source-level match to a named existing Petrobras initiative was identified." } ], "review": { "verdict": "correct", "reason": "Keep software/data foundation distinct from separately named AI use cases; do not label platform itself as AI or infer causal impact.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R06-GLOBAL-02", "verdict": "correct", "patch": { "claim": "Ativo 360 is described in the 2025 Form 20-F as an operational-data integration platform associated with predictive insights/recommendations. The filing separately describes AI use cases but does not establish that all Ativo 360 functions are AI-based or quantify platform outcomes.", "canonical_overlap": "No exact duplicate confirmed in production IDs AI-138/AI-226/AI-078; retain only if production register comparison confirms no Petrobras Ativo 360 entry." }, "reason": "Keep software/data foundation distinct from separately named AI use cases; do not label platform itself as AI or infer causal impact.", "recommended_disposition": "enrich_existing", "sources_checked": [ { "url": "https://www.sec.gov/Archives/edgar/data/1119639/000129281426002168/pbrform20f_2025.htm", "access_status": "SEC filing/accession searched; indexed primary excerpt used, filing body not directly inspected in R10", "locator": "Business section, Research, Development and Innovation; SEC-indexed filing excerpt (page 149 of annual report)", "date": "Filed 2026-04-09" }, { "url": "site/dist/assets/research-data.json", "access_status": "Local production register directly searched for canonical IDs; exact IDs/titles inspected", "locator": "No exact duplicate confirmed in production IDs AI-138/AI-226/AI-078; retain only if production register comparison confirms no Petrobras Ativo 360 entry.", "date": "accessed 2026-10-07" } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R06-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-219", "AI-220", "AI-221" ], "evidence": "Indexed text or partial access", "context_only": true, "display_period": "Fiscal 2025, SEC filing date 2026-04-09." }, { "id": "T10-R09-GLOBAL-03", "company": "Petrobras", "title": "Business Plan 2025–29 publishes prospective equilibrium price and total-cost assumptions", "category": "Portfolio economics / planning denominator", "kind": "context", "ai_role": "Plan describes technology-enabled new production systems generically; no specific technology return is included in these denominators.", "asset": "Petrobras E&P 2025–2029 portfolio; pre-salt and mature-field revitalization plans, not a named individual project.", "stage": "Prospective plan assumptions, not realized results.", "operating_period": "Plan horizon 2025–2029; announced Nov 2024 (source accessed in 2026).", "claim": "Petrobras Business Plan 2025–29 (published 21 Nov 2024) stated prospective average Brent equilibrium of $28/bbl and forecast average total cost of produced oil $36.5/boe, including lifting, government participation, depreciation and depletion. These are plan assumptions/targets, not realized current costs or technology outcomes.", "economics": "Planning denominator only, no realized production/cost outcome and no technology-specific break-even. $28/bbl “equilibrium Brent” and $36.5/boe “total cost of produced oil” are differently defined measures and should not be subtracted or treated as a simple breakeven price without further reconciliation.", "baseline": "Prospective plan average for 2025–2029; not a historical cost baseline. E&P planned CAPEX $77.3bn over five years is a portfolio allocation, not technology-specific spend.", "limits": "Issuer's public plan summary does not expose field-level assumptions, fiscal treatment by asset, cost distribution, scenario sensitivities, or technology attribution. Terms differ from Aramco's lifting/capex unit-cost averages; do not make direct operator ranking from these numbers.", "relationship": "No same-project AI register record: these are corporate planning assumptions, not an initiative. Related R03 Petrobras CCUS reinjection program is a separate operating initiative and does not explain the portfolio total cost assumption.", "decision_question": "What asset-level cost deck, fiscal terms, oil-price sensitivities and recovered-barrel assumptions allow a technology proposal to be assessed against the portfolio's published planning hurdle?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "background", "sources": [ { "title": "Petrobras launches 2025–2029 Business Plan with investments of US$111 billion", "publisher": "Petrobras Agência", "date": "2024-11-21 (published before window; plan runs 2025–2029)", "url": "https://agencia.petrobras.com.br/en/w/negocio/petrobras-lanca-plano-de-negocios-2025-2029-com-investimentos-de-us-111-bilhoes", "locator": "Lines 63-80", "access": "Direct issuer page opened", "supports": "Plan horizon, portfolio allocations, equilibrium price, total cost definition, mature-field recovery target and new systems." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct issuer release supports prospective framing and denominator definition. Retain only as dated planning context; no attribution to a specific technology.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R09-GLOBAL-03", "verdict": "correct", "patch": { "claim": "Petrobras Business Plan 2025–29 (published 21 Nov 2024) stated prospective average Brent equilibrium of $28/bbl and forecast average total cost of produced oil $36.5/boe, including lifting, government participation, depreciation and depletion. These are plan assumptions/targets, not realized current costs or technology outcomes." }, "reason": "Direct issuer release supports prospective framing and denominator definition. Retain only as dated planning context; no attribution to a specific technology.", "recommended_disposition": "background", "sources_checked": [ { "url": "https://agencia.petrobras.com.br/en/w/negocio/petrobras-lanca-plano-de-negocios-2025-2029-com-investimentos-de-us-111-bilhoes", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 63-80", "date": "2024-11-21 (published before window; plan runs 2025–2029)" } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R09-GLOBAL-03", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Plan horizon 2025–2029; announced Nov 2024 (source accessed in 2026)." }, { "id": "T10-R02-LIMITS-03", "company": "Precision Drilling", "title": "Alpha digital twin detects Haynesville mud-pump motor/bearing issue before maintenance window", "category": "rig equipment reliability / predictive maintenance", "kind": "update", "ai_role": "Precision explicitly says its Digital Twin Solution uses machine-learning models to flag anomalies. This is an ML-enabled maintenance workflow, not evidence of autonomous equipment control.", "asset": "One Precision Super Triple rig in the Haynesville, U.S. onshore; customer/operator not named.", "stage": "Single rig event case published in 2025; deployed monitoring/alert and planned maintenance action. This supplements Alpha fleet coverage, not a new platform rollout.", "operating_period": "Timeline in case study shows alerts on 2025-08-31; copyright 2025.", "claim": "Precision reports continuous mud-pump equipment monitoring detected abnormal vibration; an alert led the crew to stage a replacement motor and replace it during tripping. Maintenance confirmed excessive bearing end play. Precision says the action limited downtime hours by more than 50% and avoided what could have been a significant NPT event. The case establishes a specific alert-to-work-order response and confirmed component condition, not an observed catastrophic failure prevented.", "economics": "No actual hours, cost, avoided lost production or repair cost disclosed. >50% refers to downtime hours “limited” without defining denominator or counterfactual event duration.", "baseline": "Hypothetical unplanned failure/NPT event; no measured no-alert baseline or comparable rig event.", "limits": "Vendor case study; operator and rig ID withheld. One selected success does not establish fleet false-alert rate, missed failures, model drift, incremental sensor cost or fleet-average availability impact. Bearing end play was confirmed; a full motor failure was not documented.", "relationship": "Update to existing Precision Alpha predictive-maintenance record AI-159, which already describes Alpha technology deployed across 78 rigs but had an audit gap on specific predictive-maintenance outcomes. This case adds one concrete event, but it remains vendor-authored and anonymous; do not imply it independently validates fleet-wide Alpha performance.", "decision_question": "What are the fleet-level lead-time distribution, precision/recall, false-alert and missed-failure rates, actual repair/NPT hours, sensor and support cost, and customer corroboration across the 78-rig reported footprint?", "company_key": "Precision Drilling", "run": "Rounds 1–10", "disposition": "enrich AI-159 as a vendor event; preserve counterfactual caveat", "sources": [ { "title": "Leveraging Predictive Analytics to Optimize Mud Pump Reliability with Our Digital Twin Solution", "publisher": "Precision Drilling", "date": "2025 (event 2025-08-31; copyright ©2025; exact publication day not printed)", "url": "https://www.precisiondrilling.com/wp-content/uploads/2025/09/Precision-Drilling_Digital-Twin-Case-Study_Sept-2025-1.pdf", "locator": "Printed pp.1-2; abnormal vibration, motor change during tripping, >50% downtime claim; alert timeline 2025-08-31", "access": "Official Precision PDF opened directly", "supports": "Single field event, alert/maintenance sequence, confirmed bearing condition, and vendor-reported downtime claim." } ], "references": [ { "id": "AI-159", "relationship": "Update to existing Precision Alpha predictive-maintenance record AI-159, which already describes Alpha technology deployed across 78 rigs but had an audit gap on specific predictive-maintenance outcomes. This case adds one concrete event, but it remains vendor-authored and anonymous; do not imply it independently validates fleet-wide Alpha performance." } ], "review": { "verdict": "correct", "reason": "The PDF records one anonymized Haynesville rig, real-time alert and proactive motor replacement during tripping. 'Failure averted' is a vendor counterfactual; source provides no actual failure, hours, fleet alert rate or operator corroboration.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R02-LIMITS-03", "verdict": "correct", "patch": { "failure_classification": "not a failed deployment. Source reports an abnormal-vibration event and confirmed excessive bearing end play; failure was averted per supplier case framing, not observed. The >50% downtime-hours reduction has an unspecified counterfactual/denominator.", "canonical_overlap": "AI-159 Precision Alpha; one event is enrichment only, not fleet proof." }, "reason": "The PDF records one anonymized Haynesville rig, real-time alert and proactive motor replacement during tripping. 'Failure averted' is a vendor counterfactual; source provides no actual failure, hours, fleet alert rate or operator corroboration.", "recommended_disposition": "enrich AI-159 as a vendor event; preserve counterfactual caveat", "sources_checked": [ { "url": "https://www.precisiondrilling.com/wp-content/uploads/2025/09/Precision-Drilling_Digital-Twin-Case-Study_Sept-2025-1.pdf", "access_status": "primary supplier PDF reopened directly", "date": "2025 event 2025-08-31; ©2025, exact release day not shown", "locator": "printed pp.1–2 lines 3–25, 55–67, 79–87" } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R02-LIMITS-03", "core_company": true, "ai_ids": [ "AI-159" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Timeline in case study shows alerts on 2025-08-31; copyright 2025." }, { "id": "T20-R15-LIMITS-01", "company": "Quantum Capital Group", "title": "Quantum describes a shared data and AI approach; asset-level results remain unclear", "category": "private_equity_buyer_signal", "kind": "context", "ai_role": "Sponsor says its Quantum Energy Cloud unifies portfolio data and that proprietary Quantum IQ generative AI supports information synthesis and workflow automation; operational models are described for completion design, artificial lift, base-production anomaly detection and downtime prediction.", "asset": "Quantum investment and energy portfolio; page does not name a producing asset or participating portfolio company.", "stage": "First-party sponsor-described operating platform and workflow claims; source is undated, accessed 2026-10-07. No contract or portfolio-company implementation evidence on page.", "operating_period": "Undated current page; not date-qualified to the research window.", "claim": "Quantum describes a Microsoft/Databricks-supported data platform and QIQ and lists specific upstream workflows across deal evaluation, acreage planning, production optimization and risk/compliance. These claims indicate the sponsor's stated digital operating model and possible buyer-side vocabulary. The page gives no implementation dates, participating portfolio-company names, user/well counts, spend, counterfactual or realized performance, so it cannot substantiate operational adoption or ROI.", "economics": "No technology budget, vendor contract value, implementation cost, savings or return disclosed.", "baseline": "No baseline, outcome denominator or external comparator disclosed.", "limits": "First-party marketing page; undated; sponsor-level rather than portfolio-company source; precise claims may describe aspiration or internal use at unknown scale. Do not count as a named operator deployment or treat PE sponsor as a single procurement decision-maker across portfolio companies.", "relationship": "This is the same Quantum Energy Cloud/QIQ/AI-at-Work page already represented by AI-052 in the baseline index. Use the additional qualification (undated page; no named portfolio asset, contract, denominator or independently reported result) to enrich AI-052; do not count a second initiative.", "decision_question": "Can a supplier identify the operating-company decision owner, one named portfolio asset, spend authority, data access terms and a baseline-backed pilot case before treating the sponsor platform as an addressable rollout?", "company_key": "Quantum Capital Group", "run": "Rounds 11–20", "disposition": "merge_into_existing_AI-052; do not count as a new initiative", "sources": [ { "title": "Digital at Quantum", "publisher": "Quantum Capital Group", "date": "Undated; accessed 2026-10-07", "url": "https://www.quantumcap.com/digital-mission/", "locator": "Lines 53–77 (Quantum Energy Cloud); 82–109 (QIQ, operational workflow claims and outcome language)", "access": "directly opened first-party page", "supports": "Quantum's stated platform, partner names, listed workflows and absence of asset/date/economic detail on this page." } ], "references": [ { "id": "AI-052", "relationship": "This is the same Quantum Energy Cloud/QIQ/AI-at-Work page already represented by AI-052 in the baseline index. Use the additional qualification (undated page; no named portfolio asset, contract, denominator or independently reported result) to enrich AI-052; do not count a second initiative." } ], "review": { "verdict": "correct", "reason": "Baseline index identifies AI-052 for Quantum Capital Group with the same exact digital-mission URL and a title covering QEC, QIQ and AI-at-Work. Direct re-open confirms the workflows; this R15 record is a duplicate of the existing initiative, though its implementation/evidence caveats are useful.", "cross_audits": [ { "assignment": "round-20-limits.json", "finding_id": "T20-R15-LIMITS-01", "verdict": "correct", "patch": { "existing_ids": [ "AI-052" ], "relationship": "This is the same Quantum Energy Cloud/QIQ/AI-at-Work page already represented by AI-052 in the baseline index. Use the additional qualification (undated page; no named portfolio asset, contract, denominator or independently reported result) to enrich AI-052; do not count a second initiative.", "recommended_disposition": "merge_into_existing_AI-052" }, "reason": "Baseline index identifies AI-052 for Quantum Capital Group with the same exact digital-mission URL and a title covering QEC, QIQ and AI-at-Work. Direct re-open confirms the workflows; this R15 record is a duplicate of the existing initiative, though its implementation/evidence caveats are useful.", "sources_inspected": [ { "url": "https://www.quantumcap.com/digital-mission/", "access": "direct first-party page reopened", "locator": "Lines 53–77, 82–109; page has no publication date, no named operator/asset or performance denominator." }, { "url": "research/technology-rounds-11-20/baseline-index.json", "access": "local baseline JSON read", "locator": "production_ai_profiles entry AI-052 contains same company, page URL and Quantum Energy Cloud/QIQ/AI-at-Work scope." } ], "recommended_disposition": "merge_into_existing_AI-052; do not count as a new initiative" } ] }, "department": "Data, people & purchasing", "group_id": "T20-R15-LIMITS-01", "core_company": true, "ai_ids": [ "AI-052" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "Undated current page; not date-qualified to the research window." }, { "id": "T20-R19-GLOBAL-01", "company": "Rio Tinto", "title": "Autonomous haulage system provides a mature physical-automation scale and measurement analog", "category": "Industry analog / mining autonomy and remote operations", "kind": "context", "ai_role": "The cited haulage method is autonomous vehicle navigation/control using a supervisory system, central controller and GPS routes. Rio Tinto does not identify this as an AI-specific result. Do not count as AI evidence.", "asset": "Rio Tinto Iron Ore operations, Pilbara, Western Australia; more than 130 autonomous trucks reported across iron ore operations. The page also describes autonomous rail and drilling systems, which are not combined into this finding's truck metric.", "stage": "Mature operating fleet; current issuer page says more than 130 trucks are in operation. Cost/productivity estimate dates to 2018 and is not a current-period measured result.", "operating_period": "Current fleet scale is undated on current issuer page. Per-truck estimate explicitly refers to 2018 operations.", "claim": "Rio Tinto says its Autonomous Haulage System trucks are managed by a supervisory system and central controller, follow predefined GPS courses, and track vehicle locations/speeds/directions. The company reports more than 130 trucks operating. It estimates that in 2018 each autonomous truck operated on average 700 hours more than a conventional truck and had 15% lower costs. The page does not provide the truck population, matched comparator, cost components, confidence range, or current replication of the 2018 estimate.", "economics": "The 15% cost reduction is Rio Tinto's estimated 2018 per-truck comparison; no current period, absolute unit cost, implementation capex, fleet lifecycle cost, or independent validation is given. It cannot be transferred numerically to oil and gas, where wellsite, offshore and process-control constraints differ.", "baseline": "Company comparator is conventional haul trucks, with an estimated average 700 extra operating hours per autonomous truck in 2018. The exact conventional fleet, matching, denominator and period are not stated on the page.", "limits": "Mining haulage has fixed routes, controlled operating areas and repetitive vehicle tasks; upstream wells, offshore facilities and subsurface decisions have different safety cases and workflow variability. Useful as a physical-automation qualification example and an evidence template (hours, unit costs, safety exposure), not as a forecast or ROI benchmark for oil and gas.", "relationship": "No upstream canonical record; this is an explicitly separate mining analogy. Exclude it from upstream deployment counts and any numerical cross-industry cost comparison.", "decision_question": "For an upstream physical-automation case, can the operator disclose actual task hours, matched manual baseline, safety exposure, availability, lifecycle cost and repeatability across assets at a comparable level of clarity?", "company_key": "Rio Tinto", "run": "Rounds 11–20", "disposition": "include_as_historical_nontransferable_analog", "sources": [ { "title": "Automation: Pioneering automation and robotics in mining", "publisher": "Rio Tinto", "date": "Current issuer page, no publication date shown", "url": "https://www.riotinto.com/en/mn/about/innovation/automation", "locator": "Lines 127-160; truck mechanism, fleet count and historical 2018 estimate at lines 148-151.", "access": "Issuer HTML opened directly; full relevant text available", "supports": "Operating-system/GPS mechanism, current reported fleet scale and historical per-truck hours/cost estimate." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly opened Rio Tinto's exact automation page. It reports more than 130 operating autonomous trucks and explicitly dates the 700 extra hours and 15% lower-cost estimate to 2018. The claim is an issuer estimate without detailed comparator or cost boundary; the record correctly treats it as an old mining analog, not current-period upstream ROI.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R19-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly opened Rio Tinto's exact automation page. It reports more than 130 operating autonomous trucks and explicitly dates the 700 extra hours and 15% lower-cost estimate to 2018. The claim is an issuer estimate without detailed comparator or cost boundary; the record correctly treats it as an old mining analog, not current-period upstream ROI.", "sources_inspected": [ { "url": "https://www.riotinto.com/en/mn/about/innovation/automation", "access": "Directly opened Rio Tinto primary HTML", "locator": "Lines 126–151: technology description, >130 trucks, 2018 estimates and comparator wording." } ], "recommended_disposition": "include_as_historical_nontransferable_analog" } ] }, "department": "Maintenance & reliability", "group_id": "T20-R19-GLOBAL-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R02-LIMITS-01", "company": "SLB / OQ Exploration & Production", "title": "Oman Neuro / PowerDrive well-construction results with named operator", "category": "rotary steerable drilling / directional automation / drilling equipment", "kind": "update", "ai_role": "SLB says Neuro autonomous directional drilling and AI optimization were used. Physical equipment results are tied to PowerDrive RSS and MWD; do not assign the equipment-only effect to AI independently.", "asset": "OQ Exploration & Production operations in Oman; individual fields/wells not named.", "stage": "Vendor-reported field use on four wells: three PowerDrive RSS wells and a separate PowerDrive One + MWD well.", "operating_period": "SLB reported the results in its 2026-01-23 Q4/full-year 2025 earnings release; exact well dates are not stated.", "claim": "Keep three RSS wells at up to 50% ROP and one separate PowerDrive One + MWD well at 40% ROP with reduced tripping and casing time. Attribute only as SLB's report; no average, comparator, total-well/cost effect or exact well dates. Retina imaging is present, but no separate result is assigned to it.", "economics": "No absolute drilling time, total-well duration, dollars per well, contract value or incremental tool cost disclosed. ROP increase is drilling rate for selected well sections, not a 40-50% total cost reduction.", "baseline": "Company uses a qualitative performance comparison; no reference wells, interval lengths, geology match, averaging, or denominator beyond the four named deployment counts is disclosed in the filing.", "limits": "Vendor-reported; no operator-side source or well-level data found in this pass. “Up to” is a maximum, not mean. Cannot isolate AI contribution from tool design, sensor quality, geology, BHA, execution or section selection. Do not recast Jan. 2026 reporting as launch date.", "relationship": "Update to existing SLB Neuro/PowerDrive deployment record AI-013. The brief already reports four OQ wells and the two ROP values; this research adds an equipment/control detail read and reiterates that the single vendor filing lacks operator corroboration and a usable cost bridge. Do not create a second initiative count.", "decision_question": "Can OQ validate section-level offset comparisons and connect the tool/AI result to total well time, casing quality, cost per meter, and incremental service/tool cost across a repeated campaign?", "company_key": "SLB", "run": "Rounds 1–10", "disposition": "enrich existing AI-013; do not count as new", "sources": [ { "title": "SLB Announces Fourth-Quarter and Full-Year 2025 Results", "publisher": "SLB", "date": "2026-01-23", "url": "https://investorcenter.slb.com/static-files/f65b65ce-3607-438d-a980-cb2d1af044ae", "locator": "Printed p.18 (PDF p.18), lines 683-690, Oman/OQ paragraph", "access": "Official investor PDF opened directly", "supports": "Named OQ/SLB deployment; three PowerDrive RSS wells up to 50% ROP; one PowerDrive One + MWD well 40% ROP with trip/casing-time reductions; source describes AI optimization." } ], "references": [ { "id": "AI-013", "relationship": "Update to existing SLB Neuro/PowerDrive deployment record AI-013. The brief already reports four OQ wells and the two ROP values; this research adds an equipment/control detail read and reiterates that the single vendor filing lacks operator corroboration and a usable cost bridge. Do not create a second initiative count." } ], "review": { "verdict": "correct", "reason": "Direct SLB PDF lines 683–690 corroborate the figures, product/well counts and AI-optimization language. No named fields, offsets, denominator, or monetary bridge in the source. Product/equipment and AI contribution cannot be disaggregated.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R02-LIMITS-01", "verdict": "correct", "patch": { "claim": "Keep three RSS wells at up to 50% ROP and one separate PowerDrive One + MWD well at 40% ROP with reduced tripping and casing time. Attribute only as SLB's report; no average, comparator, total-well/cost effect or exact well dates. Retina imaging is present, but no separate result is assigned to it.", "canonical_overlap": "AI-013; this is an update, not a second initiative." }, "reason": "Direct SLB PDF lines 683–690 corroborate the figures, product/well counts and AI-optimization language. No named fields, offsets, denominator, or monetary bridge in the source. Product/equipment and AI contribution cannot be disaggregated.", "recommended_disposition": "enrich existing AI-013; do not count as new", "sources_checked": [ { "url": "https://investorcenter.slb.com/static-files/f65b65ce-3607-438d-a980-cb2d1af044ae", "access_status": "primary issuer PDF reopened directly", "date": "2026-01-23", "locator": "printed pp.18–19, lines 683–690" } ] } ] }, "department": "Drilling & completions", "group_id": "T10-R02-LIMITS-01", "core_company": true, "ai_ids": [ "AI-013" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R03-LIMITS-01", "company": "SLB / Zubair Field operator (not named)", "title": "PCL digital twin and Lift IQ remote ESP power optimization", "category": "Artificial lift / production physics model", "kind": "context", "ai_role": "No AI claim in the opened source; hydraulic/electric digital twin plus engineer oversight.", "asset": "Zubair Field, Iraq; field has ESP wells powered by diesel generators. SLB notes no test separators or multiphase meters at the production facility.", "stage": "Field trial followed by operator decision to deploy the service to Zubair wells equipped with SLB ESPs; reported quantitative results are only for two analyzed wells.", "operating_period": "Specific adjustment dates shown for one well (May 3 and May 28; year not stated). Case page publication date and overall measurement period not stated.", "claim": "SLB reports model-assisted remote voltage changes on two Zubair ESP wells and lower kVA by 28%/34% without production loss; expected run-life/TCO benefits remain projected. Test infrastructure limits to roughly annual well tests; model's independent flow validation error and project economics are not reported.", "economics": "No monetary savings, power-cost baseline, implementation cost or measured run-life extension is reported. Longer ESP run life and lower total cost of ownership are stated as expected benefits, not measured outcomes.", "baseline": "Conventional tests were logistically constrained to about one per year per well. For one example well, SLB says a 25% motor-voltage reduction was estimated to reduce current from 38 A to 24 A without affecting production; change was applied in two steps and monitored.", "limits": "Evidence is an undated supplier-authored case. The measured power results cover two wells, not all Zubair wells. Model-derived real-time production estimates substitute for sparse tests; source does not disclose validation error against a contemporaneous independent flow measurement. Do not imply the expected run-life/TCO benefit was realized or that the intervention was AI.", "relationship": "No matching initiative title was found in the inspected baseline index. Treat as non-AI production-technology context; do not add as a recent launch absent a dated source. Distinct from Devon AI-006 autonomous artificial-lift optimization.", "decision_question": "For operators with sparse well testing, what independent flow-rate validation and per-well energy/cost data are required before model-guided ESP changes can be underwritten at fleet scale?", "company_key": "SLB", "run": "Rounds 1–10", "disposition": "background only; no current-window new initiative", "sources": [ { "title": "Remote ESP optimization reduces power consumption by 28% and 34% in two Iraq wells", "publisher": "SLB", "date": "Undated page; accessed 2026-10-07", "url": "https://www.slb.com/resource-library/case-study-with-navigation/al/pcl-and-lift-iq-iraq", "locator": "Lines 1891–1913 (asset and annual test constraint); 1916–1929 (model, two-well results, expected TCO); 1934 (two-step adjustment dates)", "access": "Primary page opened directly", "supports": "Named field, test infrastructure gap, digital twin/remote engineer role, quantified two-well outcome and explicit separation of measured result from expected life-cycle benefit." } ], "references": [], "review": { "verdict": "confirm", "reason": "Source was reopened. It states Zubair field, annual testing constraint, two-well measured power/temperature outcomes and run-life benefit as expected. Page is undated and supplier-authored; properly held as background/context, not a recent initiative. Ensure 28/34% refer to kVA (not kW or dollars).", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R03-LIMITS-01", "verdict": "confirm", "patch": { "kind": "context", "source_date": "undated; outside dated-deployment evidence window unless another dated source is located", "claim": "SLB reports model-assisted remote voltage changes on two Zubair ESP wells and lower kVA by 28%/34% without production loss; expected run-life/TCO benefits remain projected. Test infrastructure limits to roughly annual well tests; model's independent flow validation error and project economics are not reported.", "ai_role": "No AI claim in the opened source; hydraulic/electric digital twin plus engineer oversight." }, "reason": "Source was reopened. It states Zubair field, annual testing constraint, two-well measured power/temperature outcomes and run-life benefit as expected. Page is undated and supplier-authored; properly held as background/context, not a recent initiative. Ensure 28/34% refer to kVA (not kW or dollars).", "recommended_disposition": "background only; no current-window new initiative", "sources_checked": [ { "url": "https://www.slb.com/resource-library/case-study-with-navigation/al/pcl-and-lift-iq-iraq", "access_status": "primary supplier case page reopened directly", "date": "undated", "locator": "lines 1891–1913, 1916–1929, 1934" } ] } ] }, "department": "Production & process operations", "group_id": "T10-R03-LIMITS-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "T10-R03-LIMITS-02", "company": "SLB / unnamed South American operator", "title": "Lift IQ remote surveillance and artificial-lift intervention", "category": "Production reliability / artificial lift", "kind": "context", "ai_role": "No AI disclosed. The source attributes intervention to experienced surveillance engineers using acquisition/transmission systems and control hardware; engineers remotely changed variable-speed-drive settings.", "asset": "Mature onshore South American field with more than 230 wells using ESPs, sucker-rod pumps and hydraulic pumping units; operator not named.", "stage": "Operating remote-surveillance service; the case reports a 29-month period, but the page date is not stated.", "operating_period": "29 months; start/end calendar dates undisclosed.", "claim": "The page body says 1,195 VSD adjustments were remote (23% of total adjustments) over 29 months, with 26,141 fewer crew miles and at least 497 work-hours saved. Its headline/summary also frames 1,195 as avoided wellsite visits and 23% as fewer field visits; avoid equating remote adjustment count with avoided-trip count without clarification. No production/cost result; undated vendor page.", "economics": "No production uplift, deferred-barrel reduction, service fee, cost avoidance or ROI is quantified. Work-hour and mileage results are operational measures, not a complete economic return.", "baseline": "Field had seven active rigs and >230 artificially lifted wells, difficult downhole conditions (including gas and solids), average interwell spacing 22 miles, and staff driving >87 miles per 12-hour shift. SLB describes shutdowns, restart delays and deferred production as the prior problem, without quantifying barrels.", "limits": "Undated vendor case with unnamed customer. Counts and travel/work-hour savings are provider-reported; no operator corroboration or production/economic denominator is supplied. 23% refers to adjustments remotely implemented, not an asserted 23% reduction in visits, downtime or cost. The case shows remote human intervention and connectivity rather than AI or autonomous control.", "relationship": "Useful conventional-technology comparator for AI-led production-optimization claims; no matching initiative title found in inspected baseline index. Keep as background rather than a new AI observation.", "decision_question": "Can the operator link the travel and work-hour reductions to independently measured downtime, deferred production and total service cost before estimating economic value?", "company_key": "SLB", "run": "Rounds 1–10", "disposition": "background only with numerator caveat", "sources": [ { "title": "Production life cycle management service eliminates 1,195 wellsite visits in South American field, saving a total of 26,141 mi", "publisher": "SLB", "date": "Undated page; accessed 2026-10-07", "url": "https://www.slb.com/resource-library/case-study-with-navigation/al/lift-iq-south-america-cs", "locator": "Lines 1891–1912 (scope and operating constraints); 1916–1921 (service mechanics and 29-month measured outcomes)", "access": "Primary page opened directly", "supports": "Field scope and constraints, provider-described engineer interventions, 23% of adjustments remotely implemented, mileage and work-hours saved." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct page inspection reveals a numerator ambiguity between headline/summary and result text. The round finding itself mostly follows the detailed body and does not count 1,195 as trips, but should state the ambiguity explicitly to avoid overclaiming. No failure evidence.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R03-LIMITS-02", "verdict": "correct", "patch": { "claim": "The page body says 1,195 VSD adjustments were remote (23% of total adjustments) over 29 months, with 26,141 fewer crew miles and at least 497 work-hours saved. Its headline/summary also frames 1,195 as avoided wellsite visits and 23% as fewer field visits; avoid equating remote adjustment count with avoided-trip count without clarification. No production/cost result; undated vendor page.", "kind": "context" }, "reason": "Direct page inspection reveals a numerator ambiguity between headline/summary and result text. The round finding itself mostly follows the detailed body and does not count 1,195 as trips, but should state the ambiguity explicitly to avoid overclaiming. No failure evidence.", "recommended_disposition": "background only with numerator caveat", "sources_checked": [ { "url": "https://www.slb.com/resource-library/case-study-with-navigation/al/lift-iq-south-america-cs", "access_status": "primary supplier case page reopened directly", "date": "undated", "locator": "lines 1891–1903 headline/summary; lines 1918–1921 detailed result" } ] } ] }, "department": "Maintenance & reliability", "group_id": "T10-R03-LIMITS-02", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "29 months; start/end calendar dates undisclosed." }, { "id": "T20-R14-GLOBAL-02", "company": "Seplat Energy", "title": "Jisike associated-gas compression supplies gas-lift to producing OML 53 wells", "category": "artificial lift / associated-gas compression and utilization", "kind": "new_initiative", "ai_role": "No AI is attributed. The reported mechanism is compression of produced associated gas for gas-lift of oil wells; digital/control methods are not described.", "asset": "Jisike Field, OML 53, Nigeria. Seplat operates the block with 40% working interest; the public page reports a 6 MMscfd design-capacity associated-gas compressor station at Jisike.", "stage": "Station reported operational since August 2025. Seplat's current asset page says produced field gas is used for gas-lift of oil-producing wells. OML 53 Ohaji South AG compressor is a separate project at mechanical completion and must not be described as operating.", "operating_period": "Jisike station since 2025-08; source page currently available but has no explicit publication/update date. Seplat's 2025 results provide block production/operating context but do not isolate gas-lift response.", "claim": "Seplat says the Jisike station uses produced gas from the field for gas-lift in producing oil wells. The field also has a flow station with 15,000 bopd design capacity and the associated-gas compressor has 6 MMscfd design capacity. A separate Ohaji South compressor is projected to recover up to 10 MMscfd of associated gas for ANOH feedstock, but was only at mechanical completion in the current page; that target is not a Jisike result.", "economics": "No actual compressor throughput, incremental liquids per lifted well, avoided flaring volumes, fuel/power cost, uptime or payback is disclosed. Design capacity must not be represented as actual gas-lift volume.", "baseline": "No pre-gas-lift well production, pressure or downtime baseline is reported. The asset page gives block ownership and design capacities but no attributable operating delta.", "limits": "The issuer page is undated, though it states operation since August 2025. Gas-lift is established production engineering; the useful evidence is asset-specific implementation and produced-gas source, not novelty. No AI or automation claim. Do not combine Jisike with not-yet-operating Ohaji South gas recovery project or ANOH ramp-up metrics.", "relationship": "No same Jisike gas-lift record found in the production AI register or earlier research. Seplat's idle-well program and flare-management records, if separately present in other research, are adjacent operator context but not the same compressor/well-lift workflow. Physical engineering example only.", "decision_question": "At what actual gas rate and well population is Jisike gas-lift operating, and what incremental oil, decline/downtime change, avoided flaring, compressor power/fuel cost, uptime and netback effect has the operator measured?", "company_key": "Seplat", "run": "Rounds 11–20", "disposition": "include_with_undated_current_page_limit", "sources": [ { "title": "OML 53 | Upstream | Our operations", "publisher": "Seplat Energy", "date": "Undated current asset page; stated Jisike operating date August 2025", "url": "https://www.seplatenergy.com/our-company/our-operations/upstream/oml-53/", "locator": "Oil Operations and AG Flares Out sections, lines 91-109; operator/working-interest context lines 116-130.", "access": "Issuer HTML opened directly", "supports": "Jisike design capacity, produced-gas gas-lift mechanism, operating-since date, field/working-interest context and separate Ohaji South mechanical-completion status." }, { "title": "FY 2025 Results Investor Presentation", "publisher": "Seplat Energy", "date": "2026-02-26", "url": "https://www.seplatenergy.com/media/qo5pqfso/fy-2025-results-investor-presentation_260226-1.pdf", "locator": "Upstream performance and idle-well programme, PDF pp. 6 and 10; operating context and separate 49-well restoration metric.", "access": "Issuer-hosted PDF opened directly", "supports": "Broader Seplat FY2025 production/asset context and helps distinguish a separate idle-well restoration programme; it does not quantify Jisike gas-lift outcomes." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened Seplat's current OML 53 page. It says Jisike gas compression has operated since August 2025, names produced-gas use for gas-lift and gives a 6 MMscfd design capacity. It separately states Ohaji South compressor only reached mechanical completion. The finding keeps design capacity from actual throughput and does not conflate the projects. No correction needed.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R14-GLOBAL-02", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened Seplat's current OML 53 page. It says Jisike gas compression has operated since August 2025, names produced-gas use for gas-lift and gives a 6 MMscfd design capacity. It separately states Ohaji South compressor only reached mechanical completion. The finding keeps design capacity from actual throughput and does not conflate the projects. No correction needed.", "sources_inspected": [ { "url": "https://www.seplatenergy.com/our-company/our-operations/upstream/oml-53/", "access": "Directly opened Seplat primary asset page", "locator": "Lines 98–109 for Jisike design capacity/produced-gas gas-lift and distinct Ohaji South stage; lines 116–130 for operator/interest." } ], "recommended_disposition": "include_with_undated_current_page_limit" } ] }, "department": "Production & process operations", "group_id": "T20-R14-GLOBAL-02", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "T20-R15-GLOBAL-02", "company": "Seplat Energy / ANOH Gas Processing Company (Seplat and NGIC JV)", "title": "ANOH gas-processing and export chain starts supply, enabling four upstream wells and condensate production", "category": "midstream/process adjacency / gas treatment and evacuation supporting upstream monetization", "kind": "new_initiative", "ai_role": "No AI or digital-control role disclosed. The reported deployment is a 300 MMscfd gas-processing/export system with two 150 MMscfd trains, LPG/condensate recovery and stabilization, and a 16 MW power plant.", "asset": "Assa North–Ohaji South (ANOH) gas development, Niger Delta, Nigeria; ANOH Gas Processing Company is a Seplat/NGIC joint venture. Gas initially supplied to Indorama; upstream wells span OML 53 and OML 21.", "stage": "First gas/supply began 2026-01-16 after completion of 11 km Indorama export pipeline and regulator approval. The plant is ramping up; NLNG supply was not yet started in the cited release, and the OB3 export route remained under construction.", "operating_period": "First-gas release dated 2026-01-20; actual flows from 2026-01-16 onward. Early stabilized wet-gas production was 40–52 MMscfd and condensate production 2.0–2.5 kboepd.", "claim": "Seplat says four upstream wells that had been on standby since November 2025 were brought online to enable gas supply. The plant delivered 40–52 MMscfd processed gas directly to the Indorama petrochemical plant and produced 2.0–2.5 kboepd condensate while ramping. Design includes two 150 MMscfd trains, LPG recovery, condensate stabilization and a 16 MW power plant; designed for zero routine flares. Design capacity of 300 MMscfd is not actual throughput.", "economics": "No plant capex, gas-processing toll, well-level incremental production/cash flow, utilization, downstream sales price or return is disclosed. Seplat states the project creates distinct upstream gas-sales and JV-dividend income streams, but gives no amount in this release.", "baseline": "Four wells were on standby since Nov 2025; first gas enabled them to be brought online. No well-level pre/post production or counterfactual gas evacuation alternative is provided. Early plant throughput is far below 300 MMscfd design capacity.", "limits": "This is a large midstream process/logistics adjacency and infrastructure commissioning, not proof of a proprietary novel technology. Its upstream relevance is the practical dependency of gas development on processing and evacuation capacity. Avoid attributing all condensate/gas output solely to plant technology; reservoir production, pipeline, offtake, wells and ramp-up all matter.", "relationship": "No ANOH-specific record found in checked production AI register or earlier research. This is separate from Seplat's Jisike associated-gas compressor/gas-lift at OML 53 in T20-R14-GLOBAL-02. Different project, process stage and outcome; no AI count.", "decision_question": "As ANOH ramps, what throughput/utilization, upstream well availability and netback, condensate/LPG yield, plant energy intensity, zero-routine-flare performance, and capital/processing economics are sustained?", "company_key": "Seplat", "run": "Rounds 11–20", "disposition": "include_as_midstream_enabler_with_limits", "sources": [ { "title": "ANOH Gas Project Achieves First Gas", "publisher": "Seplat Energy", "date": "2026-01-20", "url": "https://www.seplatenergy.com/news-insights/news/anoh-gas-project-achieves-first-gas/", "locator": "First-gas, throughput, facility configuration, upstream-well, pipeline and status details, lines 82-104.", "access": "Issuer HTML opened directly", "supports": "Actual first supply and early operating rates; four standby upstream wells brought online; plant processing configuration and remaining ramp-up/logistics limits." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened the Seplat Jan. 20, 2026 first-gas release. It dates supply start to Jan. 16 after pipeline completion and regulatory approval, reports four upstream wells brought online, 40–52 MMscfd processed gas and 2.0–2.5 kboepd condensate while ramping, and distinguishes design capacity from actual throughput. The finding does not mistake a forecast, upstream-enabler, or infrastructure commissioning for an AI deployment or standalone upstream technology ROI. No correction needed.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R15-GLOBAL-02", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened the Seplat Jan. 20, 2026 first-gas release. It dates supply start to Jan. 16 after pipeline completion and regulatory approval, reports four upstream wells brought online, 40–52 MMscfd processed gas and 2.0–2.5 kboepd condensate while ramping, and distinguishes design capacity from actual throughput. The finding does not mistake a forecast, upstream-enabler, or infrastructure commissioning for an AI deployment or standalone upstream technology ROI. No correction needed.", "sources_inspected": [ { "url": "https://www.seplatenergy.com/news-insights/news/anoh-gas-project-achieves-first-gas/", "access": "Directly opened Seplat primary HTML", "locator": "Lines 82–99: article date, first-gas date, wells, early actual flow, design facilities and zero-routine-flare design." } ], "recommended_disposition": "include_as_midstream_enabler_with_limits" } ] }, "department": "Production & process operations", "group_id": "T20-R15-GLOBAL-02", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "See note for the operating period and source dates" }, { "id": "R1-GL-03", "company": "Shell", "title": "Gato do Mato / Orca FPSO and subsea development redesign", "category": "field development / facilities and subsea architecture", "kind": "context", "ai_role": "None disclosed.", "asset": "Gato do Mato project, Santos Basin, Brazil; project later renamed Orca in Shell 2025 reporting.", "stage": "Redesigned concept reached FID in March 2025; project moved into execution. FPSO construction and offshore installation are future work; production expected 2029.", "operating_period": "Shell story dated 2025-04-02; FID March 2025. Shell 2025 Annual Report reports later execution status and Orca naming.", "claim": "The +20% capacity, nearly -16% project cost, -30% topsides weight and -20% GHG-intensity figures are design estimates versus Gato 2.0, not delivered operating results. The project reached FID in March 2025 and is in execution; installation was planned for 2028.", "economics": "Percentage estimate only; source does not disclose absolute cost, estimate class or scope normalization.", "baseline": "Prior Gato 2.0 design. The source provides percentage deltas but no absolute project cost, scope normalization, estimate class, or independent assurance.", "limits": "Projected capacity, cost, weight, and emissions changes depend on execution and production ramp-up. A single project does not validate general repeatability or prove the redesign caused future realized economics. Preserve ownership changes and expected start date as time-sensitive.", "relationship": "Useful design/capital alternative context, but the disclosed FPSO/subsea savings are redesign estimates and the field is not yet producing; do not rank against operating results.", "decision_question": "What approved estimate class, absolute capex and normalized scope underpin the claimed ~16% cost reduction versus Gato 2.0, and what remains after FID?", "company_key": "Shell", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "What does it take to design a vast and complex offshore oil and gas facility?", "publisher": "Shell", "date": "2025-04-02", "url": "https://www.shell.com/news-and-insights/our-stories/what-does-it-take-to-design-a-vast-and-complex-offshore-oil-and-gas-facility.html", "locator": "Gato 3.0 redesign, co-design with Modec, and reported design deltas", "access": "Issuer page opened; full text accessible", "supports": "Engineering method, comparative projected results, vendor co-design, and project context." }, { "title": "Shell Annual Report and Accounts 2025, Strategic Report", "publisher": "Shell plc", "date": "2026-03 (report publication month; exact day not captured)", "url": "https://www.shell.com/investors/results-and-reporting/annual-report/_jcr_content/root/main/section_2113846431/link_list/links/item1.stream/1773292491081/1bb8ca77d4189274d0abd1c40bf1defe1f7b4a49/strategic-report-ar25.pdf", "locator": "Printed p. 43, project renamed Orca; FID/execution/2029 expected start; ownership", "access": "Issuer-hosted PDF search result accessible; direct open failed in this research call", "supports": "Naming chronology and expected future execution/production status." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-04-02", "url": "https://www.shell.com/news-and-insights/our-stories/what-does-it-take-to-design-a-vast-and-complex-offshore-oil-and-gas-facility.html", "locator": "Gato 3.0 redesign, projected design comparisons, FID/execution and 2028 installation plan", "access": "Shell issuer page opened; text accessible", "supports": "Shell's article is explicit that these are redesign comparisons. Use this to illustrate engineering/capital-design alternatives, not verified savings or general technology performance. Annual-report naming/ownership detail was not necessary to validate the main claim." } ], "references": [ { "id": "AI-010", "relationship": "company_context" }, { "id": "TR-05", "relationship": "company_context" } ], "department": "Production & process operations", "group_id": "R1-GL-03", "core_company": true, "ai_ids": [ "AI-010" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "See note for the operating period and source dates" }, { "id": "R1-GL-04", "company": "Shell", "title": "Sparta combines 20K equipment with managed-pressure drilling", "category": "subsea equipment / drilling and pressure management", "kind": "context", "ai_role": "No AI role disclosed; pressure monitoring/control is not described as ML.", "asset": "Sparta deepwater project, Gulf of America; high-pressure reservoirs under thick salt layers.", "stage": "Under construction; first production expected 2028.", "operating_period": "Official story published June 3, 2026.", "claim": "No operating result. Up to 90,000 boe/d is planned peak production, not achieved production; no quantified cost delta is provided.", "economics": "Project capex, incremental cost of 20K equipment, electric compression premium, and expected breakeven/capital efficiency not stated in source.", "baseline": "Shell compares pressure capacity with most deepwater platforms and cites Appomattox as earlier 15,000-psi experience; no same-reservoir alternative or economic counterfactual disclosed.", "limits": "Novel pressure envelope, salt drilling, equipment qualification, well control, construction and startup remain execution risks. Expected output is not proof of reserves or profitability. Need actual reliability and failure-mode data after commissioning.", "relationship": "Technically consequential 20K hardware and managed-pressure drilling remain under execution. No operating performance or cost is yet disclosed.", "decision_question": "What incremental capex, cost per recoverable barrel, pressure-rated equipment qualification cost, and reliability penalty support the 20K design versus conventional development?", "company_key": "Shell", "run": "Three-round scope review", "disposition": "background", "sources": [ { "title": "Sparta: unlocking energy once thought out of reach", "publisher": "Shell", "date": "2026 (web story; exact publication day not exposed in opened page)", "url": "https://www.shell.com/news-and-insights/our-stories/sparta-unlocking-energy-once-thought-out-of-reach.html", "locator": "Design pressure and output lines 34-43; MPD and high-density fluid lines 63-77", "access": "Issuer page opened; full text accessible", "supports": "Pressure class, drilling mechanism, project stage and anticipated production; no realized economics." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-06-03", "url": "https://www.shell.com/news-and-insights/our-stories/sparta-unlocking-energy-once-thought-out-of-reach.html", "locator": "Construction and planned 2028 start; 20,000-psi design, up-to-90,000 boe/d expected peak, managed-pressure drilling description", "access": "Shell issuer page opened; text accessible", "supports": "Novel pressure-rated hardware and drilling are material frontier technologies, but the item is currently a project design/execution description without cost or performance evidence." } ], "references": [ { "id": "AI-010", "relationship": "company_context" }, { "id": "TR-05", "relationship": "company_context" } ], "department": "Drilling & completions", "group_id": "R1-GL-04", "core_company": true, "ai_ids": [ "AI-010" ], "evidence": "Source text reviewed", "context_only": true, "display_period": "Official story published June 3, 2026." }, { "id": "T10-R04-LIMITS-01", "company": "Texas Pacific Land Corporation / TPWR and Transmissive Water Services", "title": "Produced-water desalination test facility: 2025 pause followed by commissioning in 2026", "category": "Produced-water treatment / desalination infrastructure", "kind": "update", "ai_role": "No AI role disclosed; this is a physical treatment process and equipment development program.", "asset": "Permian Basin produced-water treatment and reuse; Phase 2B test facility targeted at 10,000 bbl/d. No specific oil-and-gas operator customer or producing asset is named.", "stage": "The 2025 pause is historical: TPL Q2 2026 says construction complete and commissioning commenced as of 2026-06-30. Do not describe facility as currently paused or as commissioned/operating. Cumulative spend moved from $45.5m to $55.8m; Q2 filing gives $48.1m capitalized.", "operating_period": "Development over several years; cumulative spend through 2025-12-31. Filing published 2026-02-25.", "claim": "TPL reported a temporary 2025 construction pause for equipment testing and potential integration. Its Q2 2026 filing says construction was complete and commissioning had commenced by June 30, 2026. Initial design capacity is 10,000 bbl/day; throughput and commercial economics remain unreported.", "economics": "Cumulative process/equipment spend was $45.5m through 2025 and $55.8m through June 30, 2026, including $48.1m capitalized. This is cumulative development spend, not a standalone plant capital cost or unit-treatment cost.", "baseline": "TPL estimates the Permian produces >20 million bbl/d of produced water and describes injection as the incumbent disposal route. TPL's broader water segment is a separate, existing business; the desalination equipment itself is not yet identified as in commercial operation.", "limits": "Do not call the program a failed deployment: the company characterizes construction as temporarily paused for testing/equipment integration. Do not treat lab success, stated 10,000-bbl/d design capacity or H1 2026 target as facility commissioning or delivered water volumes. No current post-H1-2026 status was established in this pass; no treatment energy intensity, recovery rate, product quality test results, disposal cost avoided, capex forecast or customer economics disclosed.", "relationship": "Same project as T10-R08-LIMITS-01 and T10-R09-LIMITS-01; retain one project timeline with separate observations.", "decision_question": "What commissioning date, achieved throughput and quality, energy per barrel, full installed cost, and binding operator offtake would turn this development spend into a repeatable upstream alternative to disposal?", "company_key": "Texas Pacific Land", "run": "Rounds 1–10", "disposition": "merge status chronology with R08 TPL update; preserve 2025 observation as source-vintage detail", "sources": [ { "title": "Texas Pacific Land Corporation 2025 Form 10-K", "publisher": "Texas Pacific Land Corporation / U.S. SEC", "date": "Filed 2026-02-25; reports through 2025-12-31", "url": "https://www.sec.gov/Archives/edgar/data/1811074/000181107426000018/tpl-20251231.htm", "locator": "Lines 324–329 (process, status and spend); 1210–1213 (water service costs and R&D expense)", "access": "Primary SEC-hosted filing opened directly", "supports": "Development stage, pause reason, expected—not actual—completion date, stated test capacity, spend and R&D expense." } ], "references": [], "review": { "verdict": "correct", "reason": "2025 10-K and Q2 2026 10-Q reconcile chronology. No throughput, process acceptance, customer, unit cost or ROI reported. Do not confuse separate $55.8m tax-credit purchase with project spend.", "cross_audits": [ { "assignment": "round-08-limits.json", "finding_id": "T10-R04-LIMITS-01", "verdict": "correct", "patch": { "stage": "The temporary construction pause reported in the 2025 Form 10-K was historical; by 2026-06-30 facility construction was complete and commissioning commenced. H1 2026 completion had been a forecast, not an operating result. Cumulative spend updated from $45.5m at 2025-12-31 to $55.8m at 2026-06-30; $48.1m capitalized." }, "reason": "New issuer Q2 2026 Form 10-Q directly confirms construction completion and commissioning start, resolving the earlier status gap without establishing commercial operation or economics.", "sources_checked": [ "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm" ] }, { "assignment": "round-10-limits.json", "finding_id": "T10-R04-LIMITS-01", "verdict": "correct", "patch": { "stage": "The 2025 pause is historical: TPL Q2 2026 says construction complete and commissioning commenced as of 2026-06-30. Do not describe facility as currently paused or as commissioned/operating. Cumulative spend moved from $45.5m to $55.8m; Q2 filing gives $48.1m capitalized.", "failure_classification": "no technology failure evidenced; a 2025 construction pause for stated equipment testing/integration was followed by completion of construction." }, "reason": "2025 10-K and Q2 2026 10-Q reconcile chronology. No throughput, process acceptance, customer, unit cost or ROI reported. Do not confuse separate $55.8m tax-credit purchase with project spend.", "recommended_disposition": "merge status chronology with R08 TPL update; preserve 2025 observation as source-vintage detail", "sources_checked": [ { "url": "https://www.sec.gov/Archives/edgar/data/1811074/000181107426000018/tpl-20251231.htm", "access_status": "2025 issuer Form 10-K; source previously reopened and root-source-check directly cites p.6", "date": "2026-02-25 filing; status through 2025-12-31", "locator": "printed p.6, lines 324–329" }, { "url": "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm", "access_status": "Q2 2026 issuer Form 10-Q directly reopened", "date": "filed 2026-08-04; status through 2026-06-30", "locator": "printed p.20, lines 977–980" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Development over several years; cumulative spend through 2025-12-31. Filing published 2026-02-25." }, { "id": "T10-R08-LIMITS-01", "company": "Texas Pacific Land Corporation / TPWR and Transmissive Water Services", "title": "Produced-water desalination Phase 2B moves from construction pause to commissioning", "category": "Produced-water treatment / scale-up execution", "kind": "update", "ai_role": "No AI disclosed; physical treatment process and equipment.", "asset": "Permian Basin produced-water desalination test facility, planned initial capacity 10,000 bbl/d; no specific upstream customer/asset named.", "stage": "Construction complete and commissioning commenced as of 2026-06-30; not commissioning complete/commercial operation.", "operating_period": "Status as of 2026-06-30, in Q2 2026 Form 10-Q; filing date 2026-08-04.", "claim": "TPL's issuer filing reports construction complete and commissioning started for its 10,000-bbl/d initial-capacity facility. Cumulative spend through 2026-06-30 was $55.8m, of which $48.1m was capitalized; $10.2m was spent in H1 2026.", "economics": "Cumulative development spend increased $10.3m from the $45.5m disclosed through 2025-12-31. Spend/capitalized balance are not unit treatment cost, annualized operating cost or customer value. No price, offtake contract, revenue, cost per barrel, or avoided-disposal cost disclosed.", "baseline": "Prior status in TPL 2025 Form 10-K (through 2025-12-31): facility construction temporarily paused during 2025 for equipment testing and possible additions; H1 2026 completion was anticipated. New Q2 filing advances status to constructed/commissioning commenced.", "limits": "Do not call the earlier pause a failed technology deployment: the stated reason was further testing/equipment integration, and the later filing says construction completed. Do not call commissioning successful or infer production throughput; current source says only commissioning commenced. No effluent quality, energy consumption, uptime, process recovery rate, operating expense, environmental permit status or customer use is reported.", "relationship": "Same TPL desalination project as T10-R04-LIMITS-01 and T10-R09-LIMITS-01; merge one project timeline/economics into a single canonical record with source-vintage observations retained.", "decision_question": "Will commissioning establish sustained output at the intended quality and energy intensity, and will named operator offtake/permits and full unit costs support commercial-scale reuse or discharge?", "company_key": "Texas Pacific Land", "run": "Rounds 1–10", "disposition": "merge into T10-R04-LIMITS-01 canonical timeline; retain R08 as audit chronology only", "sources": [ { "title": "Texas Pacific Land Corporation Q2 2026 Form 10-Q", "publisher": "Texas Pacific Land Corporation / U.S. SEC", "date": "Quarter ended 2026-06-30; filed 2026-08-04", "url": "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm", "locator": "Lines 977–980 (printed page 20)", "access": "Primary issuer-hosted SEC filing opened directly", "supports": "Construction complete, commissioning commenced, capacity target and through-period development spend/capitalization." }, { "title": "Texas Pacific Land Corporation 2025 Form 10-K", "publisher": "Texas Pacific Land Corporation / U.S. SEC", "date": "Year ended 2025-12-31; filed 2026-02-25", "url": "https://www.sec.gov/Archives/edgar/data/1811074/000181107426000018/tpl-20251231.htm", "locator": "Lines 324–329", "access": "Primary SEC-hosted filing opened in prior Round 04", "supports": "Prior pause reason, original H1 2026 forecast and $45.5m year-end cumulative spend." } ], "references": [], "review": { "verdict": "correct", "reason": "Q2 filing directly confirms status, $55.8m spend and capitalization; use same evidence as R04 correction. This is a source chronology update, not a second project and not a failed technology. No realized economics.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R08-LIMITS-01", "verdict": "correct", "patch": { "relationship": "Same TPL desalination project as T10-R04-LIMITS-01 and T10-R09-LIMITS-01; merge one project timeline/economics into a single canonical record with source-vintage observations retained.", "stage": "Construction complete and commissioning commenced as of 2026-06-30; not commissioning complete/commercial operation." }, "reason": "Q2 filing directly confirms status, $55.8m spend and capitalization; use same evidence as R04 correction. This is a source chronology update, not a second project and not a failed technology. No realized economics.", "recommended_disposition": "merge into T10-R04-LIMITS-01 canonical timeline; retain R08 as audit chronology only", "sources_checked": [ { "url": "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm", "access_status": "primary issuer Form 10-Q directly opened and searched", "date": "filed 2026-08-04; quarter ended 2026-06-30", "locator": "printed p.20, lines 977–980" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Status as of 2026-06-30, in Q2 2026 Form 10-Q; filing date 2026-08-04." }, { "id": "T10-R09-LIMITS-01", "company": "Texas Pacific Land Corporation / TPWR and Transmissive Water Services", "title": "Produced-water desalination capacity and existing water sales do not yet establish replicable unit economics", "category": "Water treatment scale and unit-economics benchmark limits", "kind": "context", "ai_role": "None disclosed; physical treatment process and equipment.", "asset": "Permian Basin produced water; TPL's Phase 2B test facility has 10,000 bbl/d initial capacity. TPL is a landowner/water-services company and explicitly says it is not an oil-and-gas producer.", "stage": "Construction reported complete and commissioning commenced in Q2 2026; no achieved operating capacity or customer/throughput is reported.", "operating_period": "Q2 and six months ended 2026-06-30; filed 2026-08-04.", "claim": "Initial design capacity 10,000 bbl/day represents less than 0.05% of the issuer-stated Permian produced-water flow (>20 million bbl/day); commissioning had begun, so capacity is not treated volume. Existing Q2 water-sales gross revenue averages about $0.66/bbl; this is a separate service business, not desalination price, margin or return.", "economics": "TPL existing Q2 water sales: $39.733m revenue / 60.343m barrels = approximately $0.66 per barrel of gross segment revenue (calculated from the filing). Water service-related expenses were $11.6m for the quarter, but include treatment, transfer, purchases, repairs/maintenance, rentals and fuel across services; not allocable to the desalination project. No desalination throughput, price, energy cost, CAPEX recovery, unit operating cost, avoided injection fee or treatment margin disclosed.", "baseline": "Source separately reports current commercial water sales/volumes and new desalination design scale. Water sales volumes depended on customer demand; cost drivers and delivery-location/right-of-way expenses vary. These commercial segment values are not same-feedstock or same-process comparator data for produced-water desalination.", "limits": "Do not call the $0.66/bbl revenue proxy a desalination price or margin. Do not divide whole-segment costs by commercial water-sale volume and present as process OPEX. Basin flow denominator is rounded/issuer-estimated, and design capacity is not actual output. The 0.05% ratio describes only the initial test facility relative to basin-scale flow; it says nothing about number or economics of eligible customers, produced-water quality, treatment recovery or disposal alternative cost. No post-commissioning result yet.", "relationship": "This is an economics/scale enrichment to Round 04/08 TPL case, not a new technology record. Keep the basis clear: same company, separate existing commercial water-sales activity versus a commissioning-stage desalination project.", "decision_question": "What are commissioning throughput and yield, product-water quality, energy and consumables per barrel, full installed capital per sustained bbl/d, delivered treatment price, disposal alternative cost and contracted eligible volume at the same location?", "company_key": "Texas Pacific Land", "run": "Rounds 1–10", "disposition": "keep only as non-like-for-like denominator caution merged under TPL record", "sources": [ { "title": "Texas Pacific Land Corporation Q2 2026 Form 10-Q", "publisher": "Texas Pacific Land Corporation / U.S. SEC", "date": "Quarter ended 2026-06-30; filed 2026-08-04", "url": "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm", "locator": "Lines 977–980 (scale and project stage); 890 (not an oil/gas producer); 1149–1152 (sales/customer-demand and expense context); 1159–1183 (volumes, revenue and service expenses)", "access": "Primary issuer-hosted SEC filing opened directly", "supports": "Design capacity, basin-scale estimate, commissioning status and commercial water sales/volume/expense data; it does not report desalination economics." } ], "references": [], "review": { "verdict": "correct", "reason": "Direct Q2 filing supports the source values and operating-stage distinction. Arithmetic is transparent and directionally correct; revise '≤0.05%' to '<0.05%' because basin flow is stated as greater than 20m bbl/d. Ratios are context only, not process economics or failure evidence.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R09-LIMITS-01", "verdict": "correct", "patch": { "calculation": "10,000 bbl/d / >20,000,000 bbl/d = <0.05% of stated basin-wide flow by initial design capacity; capacity is not delivered volume. $39.733m / 60.343m bbl = about $0.66/bbl gross existing water-sales revenue for Q2/26; not treatment price/margin.", "cost_warning": "$11.6m quarter water-service expenses span treatment, transfer, water purchases, repairs/maintenance, rental and fuel; cannot allocate to desalination. TPL says it is not an oil/gas producer, and current source says commissioning only commenced.", "canonical_overlap": "Same project as T10-R04-LIMITS-01 and T10-R08-LIMITS-01." }, "reason": "Direct Q2 filing supports the source values and operating-stage distinction. Arithmetic is transparent and directionally correct; revise '≤0.05%' to '<0.05%' because basin flow is stated as greater than 20m bbl/d. Ratios are context only, not process economics or failure evidence.", "recommended_disposition": "keep only as non-like-for-like denominator caution merged under TPL record", "sources_checked": [ { "url": "https://www.texaspacific.com/investors/sec-filings/all-sec-filings/content/0001811074-26-000058/tpl-20260630.htm", "access_status": "primary issuer Form 10-Q directly reopened and searched", "date": "filed 2026-08-04; quarter ended 2026-06-30", "locator": "lines 890, 977–980, 1149–1183; printed p.20 and pp.25–26" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-LIMITS-01", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Q2 and six months ended 2026-06-30; filed 2026-08-04." }, { "id": "T10-R04-LIMITS-02", "company": "Texas Railroad Commission / Permian Basin operators", "title": "Produced-water disposal permitting now constrains pressure, volume and geologic eligibility", "category": "Water disposal / subsurface injection regulation", "kind": "context", "ai_role": "None; regulator permitting requirements and subsurface pressure/geology constraints.", "asset": "New and amended deep and shallow saltwater disposal well permit applications in the Permian Basin; additional seismicity review for wells within 25 km of a seismic event.", "stage": "New regulator guidelines effective 2025-06-01.", "operating_period": "Announced 2025-05-16; effective 2025-06-01.", "claim": "The RRC requires expanded half-mile area-of-review, geology-based maximum surface injection pressure, and reservoir-pressure-based maximum daily injection volumes. Operators must assess old/unplugged wells and show injection will not fracture confining strata.", "economics": "No quantified basin-wide cost, delay or alternative-treatment economics are supplied. The requirements can affect eligible disposal wells and available injection throughput, but no specific asset-level impact was established here.", "baseline": "RRC states area of review increased from quarter-mile to half-mile; maximum pressure and volume criteria apply to new/amended permits, while wells within 25 km of seismic events remain subject to separate seismicity review.", "limits": "This is regulator context, not evidence that a particular operator's disposal well was denied or curtailed. Avoid inferring that a specific desalination, recycling or electrification technology is economically preferred without asset-specific cost and permitting evidence.", "relationship": "Relevant infrastructure eligibility context for upstream produced-water decisions; not a technology initiative or company deployment.", "decision_question": "For a proposed water solution, what permitted injection volume, storage/takeaway capacity and treatment economics are available at the specific operating asset after applying the local rules?", "company_key": "Texas Railroad Commission", "run": "Rounds 1–10", "disposition": "include as context only where evaluating local water solution eligibility", "sources": [ { "title": "RRC Issues Enhanced Guidelines for Permian Basin Disposal Wells", "publisher": "Texas Railroad Commission", "date": "2025-05-16; effective 2025-06-01", "url": "https://www.rrc.texas.gov/news/05162025-permian-disposal-wells-guidance-release/", "locator": "Lines 41–58", "access": "Primary regulator page opened directly", "supports": "New permitting criteria, half-mile area of review, pressure/volume constraints, geologic demonstration and effective date." } ], "references": [], "review": { "verdict": "confirm", "reason": "Direct RRC notice confirms new permit criteria and effective date. No named well denial, operator-specific cost, or proof treatment technology is superior. Properly bounded as regulator context.", "cross_audits": [ { "assignment": "round-10-limits.json", "finding_id": "T10-R04-LIMITS-02", "verdict": "confirm", "patch": { "kind": "context", "failure_classification": "regulatory/geologic disposal eligibility constraint, not a technology failure or named-asset curtailment." }, "reason": "Direct RRC notice confirms new permit criteria and effective date. No named well denial, operator-specific cost, or proof treatment technology is superior. Properly bounded as regulator context.", "recommended_disposition": "include as context only where evaluating local water solution eligibility", "sources_checked": [ { "url": "https://www.rrc.texas.gov/news/05162025-permian-disposal-wells-guidance-release/", "access_status": "primary regulator page reopened directly", "date": "2025-05-16; effective 2025-06-01", "locator": "lines 41–58" } ] } ] }, "department": "Water, emissions & energy", "group_id": "T10-R04-LIMITS-02", "core_company": false, "ai_ids": [], "evidence": "Source text reviewed", "context_only": true, "display_period": "Announced 2025-05-16; effective 2025-06-01." }, { "id": "T10-R07-GLOBAL-02", "company": "TotalEnergies / Cognite", "title": "Three-year scale-up of industrial data and AI platform across operated upstream assets", "category": "Supplier partnership / data foundation and AI platform", "kind": "update", "ai_role": "Agreement bundles industrial-data foundation and AI platform. Operator specifically says the data layer unifies data and makes it AI-ready; deployment acceleration of AI is an objective, not evidence of individual AI workflows or realized value.", "asset": "All TotalEnergies-operated upstream assets globally from drilling to production; no named pilot asset or deployment sequence provided.", "stage": "Announced three-year scale-up agreement, Sep 2025; staged global rollout planned, not evidence of completed global deployment.", "operating_period": "Announced 2025-09-26; implementation period three years.", "claim": "Three-year planned scale-up across operated upstream assets; release states data unification/AI readiness and intended visualization, equipment monitoring and AI acceleration. This is an agreement/objective, not proof rollout completed or a realized result.", "economics": "No agreement value, license/integration cost, data-integration effort, operating savings, or benefit-sharing terms disclosed.", "baseline": "No starting coverage, number of sites/apps/data points, implementation milestones, or before/after operating metrics disclosed.", "limits": "Strategic supplier announcement; three-year program means full scope is future dated. “All operated upstream assets” is intended scope, not verified completion. No individual workflow result or vendor lock-in/data portability terms reported.", "relationship": "Same company initiative and vendor/platform scope as canonical AI-078: TotalEnergies industrial data and AI foundation across operated upstream, including Cognite. This Sep 2025 agreement is an earlier scope/partner announcement; AI-078 already captures later implementation detail and end-2027 target. Do not count as separate platform rollout.", "decision_question": "What sites and workflows are actually onboarded at each tranche, what is the total platform/implementation cost, and can TotalEnergies exit or port contextualized asset data and workflows?", "company_key": "TotalEnergies", "run": "Rounds 1–10", "disposition": "enrich_existing", "sources": [ { "title": "Digital Transformation: TotalEnergies and Cognite Expand Their Partnership to Scale Industrial AI", "publisher": "TotalEnergies", "date": "2025-09-26", "url": "https://totalenergies.com/newsroom/digital-transformation-totalenergies-and-cognite-expand-their-partnership-scale/?lang=eng", "locator": "Lines 31-46", "access": "Direct issuer release opened", "supports": "Parties, scope, three-year timeframe, goals, data foundation and AI positioning." } ], "references": [ { "id": "AI-078", "relationship": "Same company initiative and vendor/platform scope as canonical AI-078: TotalEnergies industrial data and AI foundation across operated upstream, including Cognite. This Sep 2025 agreement is an earlier scope/partner announcement; AI-078 already captures later implementation detail and end-2027 target. Do not count as separate platform rollout." } ], "review": { "verdict": "correct", "reason": "Direct release reopened. Merge into AI-078, which already has operator-source detail on data platform layers and later deployment targets; count program once.", "cross_audits": [ { "assignment": "round-07-global.json", "finding_id": "T10-R07-GLOBAL-02", "verdict": "correct", "patch": { "existing_ids": [ "AI-078" ], "relationship": "same platform/global upstream foundation initiative; update/context to canonical AI-078, not net-new" }, "reason": "Production register AI-078 already records the TotalEnergies industrial data and AI foundation including Cognite and later end-2027 deployment target. The Sep 2025 agreement is same initiative, earlier-stage source context.", "sources_inspected": [ { "url": "site/dist/assets/research-data.json", "access": "local production register read", "locator": "AI-078 Company, Initiative, Stage_at_disclosure, Source_IDs, Source_URL, Implementation" }, { "url": "https://totalenergies.com/newsroom/digital-transformation-totalenergies-and-cognite-expand-their-partnership-scale/?lang=eng", "access": "direct issuer release opened", "locator": "lines 31-46" } ] }, { "assignment": "round-10-us.json", "finding_id": "T10-R07-GLOBAL-02", "verdict": "correct", "patch": { "canonical_overlap": "AI-078 (TotalEnergies industrial data and AI foundation across operated upstream). Same Cognite agreement announced 26 Sep 2025; duplicate program record.", "claim": "Three-year planned scale-up across operated upstream assets; release states data unification/AI readiness and intended visualization, equipment monitoring and AI acceleration. This is an agreement/objective, not proof rollout completed or a realized result." }, "reason": "Direct release reopened. Merge into AI-078, which already has operator-source detail on data platform layers and later deployment targets; count program once.", "recommended_disposition": "enrich_existing", "sources_checked": [ { "url": "https://totalenergies.com/newsroom/digital-transformation-totalenergies-and-cognite-expand-their-partnership-scale/?lang=eng", "access_status": "Directly reopened primary issuer release in R10; agreement/objectives inspected", "locator": "Lines 31-46", "date": "2025-09-26" }, { "url": "site/dist/assets/research-data.json", "access_status": "Local production register directly searched for canonical IDs; exact IDs/titles inspected", "locator": "AI-078 (TotalEnergies industrial data and AI foundation across operated upstream). Same Cognite agreement announced 26 Sep 2025; duplicate program record.", "date": "accessed 2026-10-07" } ] } ] }, "department": "Data, people & purchasing", "group_id": "T10-R07-GLOBAL-02", "core_company": true, "ai_ids": [ "AI-078" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "Announced 2025-09-26; implementation period three years." }, { "id": "T20-R12-GLOBAL-01", "company": "Woodside Energy / AWS", "title": "Woodside launches AI-assisted maintenance planning at North West Shelf", "category": "maintenance planning / reliability analytics / AI-enabled operations", "kind": "new_initiative", "ai_role": "Woodside says AI analyzed maintenance history and equipment failure modes, then advanced statistical models recommended maintenance intervals against maintenance plans and reliability targets. Human maintenance teams remain the decision users; source does not say the tool autonomously changes work orders.", "asset": "Woodside's North West Shelf Project; first tested and proven on the offshore Angel platform, Western Australia.", "stage": "Woodside reported launch at NWS and prior successful Angel test on 2026-01-05; global rollout to other assets was scheduled for later in 2026, not yet reported as completed in this source.", "operating_period": "North West Shelf launch reported 5 January 2026, following an Angel platform test.", "claim": "Woodside says Maint Intel recommends equipment-maintenance intervals using maintenance records, prior plans and reliability targets. Its Digital team and AWS collaborators reduced model-processing time from five days to under two hours. The issuer says this reduced unnecessary activities but supplies no count, work-hours, deferred maintenance, failures, availability or cost result.", "economics": "No program cost, avoided maintenance spend, incremental downtime, cost per asset, failure rate or realized financial value disclosed. Processing-time reduction is a workflow productivity metric, not equipment reliability ROI.", "baseline": "Five-day prior model-processing cycle compared with under two hours after workflow development; the source does not define the comparison sample, data volume, model count or whether other workflow changes contributed.", "limits": "Company feature story and reported statements, not independently audited. NWS launch and Angel test are distinct deployment phases. Do not infer increased uptime, fewer failures, or maintenance savings from faster model turnaround alone. No performance metric denominator or matched equipment cohort.", "relationship": "This is an update to the existing Woodside Maint Intel profile AI-042. AI-198 is unrelated and identifies Woodside's Trion integrated well-delivery contract with AI-enabled drilling. Preserve the NWS launch/Angel test phases and the absence of quantified reliability or cost savings.", "decision_question": "How many assets and rotating/static equipment units use Maint Intel, what maintenance actions were changed, and what matched-cohort changes occurred in cost, unplanned downtime, failures, or availability after launch?", "company_key": "Woodside", "run": "Rounds 11–20", "disposition": "enrich_existing", "sources": [ { "title": "Right fix at right time – AI delivers for Woodside", "publisher": "Woodside Energy", "date": "2026-01-05", "url": "https://www.woodside.com/media-centre/news-stories/story/right-fix-at-right-time---ai-delivers-for-woodside", "locator": "Dated story lines 13-45: NWS launch, Angel test, workflow, rollout plan, and processing time statement.", "access": "Issuer HTML opened directly", "supports": "Asset and launch/test stage; workflow mechanism and human decision support; reported five-days-to-under-two-hours processing reduction and qualitative claim of fewer unnecessary activities." } ], "references": [ { "id": "AI-042", "relationship": "This is an update to the existing Woodside Maint Intel profile AI-042. AI-198 is unrelated and identifies Woodside's Trion integrated well-delivery contract with AI-enabled drilling. Preserve the NWS launch/Angel test phases and the absence of quantified reliability or cost savings." } ], "review": { "verdict": "correct", "reason": "The Woodside page directly supports its Jan. 5, 2026 NWS launch, prior Angel test, maintenance recommendation workflow and model-processing time falling from five days to under two hours. But the originating record's existing_ids value AI-198 is wrong: the baseline index maps the same URL to AI-042. AI-198 is a different Woodside Trion drilling record. The claim appropriately treats processing-time as workflow productivity and not proof of uptime, failures avoided or maintenance-dollar savings.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R12-GLOBAL-01", "verdict": "correct", "patch": { "existing_ids": [ "AI-042" ], "relationship": "This is an update to the existing Woodside Maint Intel profile AI-042. AI-198 is unrelated and identifies Woodside's Trion integrated well-delivery contract with AI-enabled drilling. Preserve the NWS launch/Angel test phases and the absence of quantified reliability or cost savings." }, "reason": "The Woodside page directly supports its Jan. 5, 2026 NWS launch, prior Angel test, maintenance recommendation workflow and model-processing time falling from five days to under two hours. But the originating record's existing_ids value AI-198 is wrong: the baseline index maps the same URL to AI-042. AI-198 is a different Woodside Trion drilling record. The claim appropriately treats processing-time as workflow productivity and not proof of uptime, failures avoided or maintenance-dollar savings.", "sources_inspected": [ { "url": "https://www.woodside.com/media-centre/news-stories/story/right-fix-at-right-time---ai-delivers-for-woodside", "access": "Directly opened Woodside primary HTML", "locator": "Lines 13–40: date, launch, Angel test, workflow, rollout plan and processing-time claim." }, { "url": "baseline-index.json", "access": "Read local baseline index", "locator": "AI-042 maps the exact Maint Intel URL; AI-198 is a separate Trion drilling profile." } ], "recommended_disposition": "enrich_existing" } ] }, "department": "Maintenance & reliability", "group_id": "T20-R12-GLOBAL-01", "core_company": true, "ai_ids": [ "AI-042" ], "evidence": "Source text reviewed", "context_only": false, "display_period": "North West Shelf launch reported 5 January 2026, following an Angel platform test." }, { "id": "T20-R15-GLOBAL-01", "company": "Woodside Energy", "title": "Pluto LNG flare upgrade pairs composition measurement with continuous combustion imaging", "category": "LNG/process adjacency / flare safety and emissions instrumentation", "kind": "new_initiative", "ai_role": "No AI is disclosed. The deployed method uses a gas chromatograph for flare-stream methane/nitrogen composition and multispectral VISR cameras for live continuous combustion monitoring. Operators can use the measurement to adjust flare performance; autonomous control is not claimed.", "asset": "Pluto LNG facility, Western Australia; flare system supporting safe disposal/depressurization and facility emissions reporting.", "stage": "Woodside reported delivery of new flare-system technology on 2026-03-31 after more than five years of planning/design. The system was entering staged maintenance through 2026 to remain ready for Pluto Train 2 integration.", "operating_period": "Announcement 2026-03-31; no steady-state measurement window or before/after operating data provided.", "claim": "The upgrade includes a new gas chromatograph measuring specific flare-gas components, including methane and nitrogen, and advanced VISR cameras using a multispectral imager for continuous combustion-performance monitoring. Woodside says the cold/dry flare stream contains approximately 50–70% nitrogen, while prior Australian reporting had assumed flare gas was entirely hydrocarbons. The stated aim is better flare tuning, smoke management, safety, and emissions measurement; no measured improvement is quantified.", "economics": "No project cost, methane-slip reduction, combustion destruction efficiency, flare uptime, avoided reporting emissions, or payback disclosed. The system's direct value includes improved composition measurement and visibility; reported aspiration is not an achieved emissions metric.", "baseline": "Prior emissions reporting assumed the stream was entirely hydrocarbon, although Woodside reports 50–70% nitrogen in the cold-dry stream. There is no stated baseline for combustion efficiency, smoke events, methane slip, or downtime.", "limits": "This is an LNG/process-facility adjacent case, not upstream well technology. It is a new measurement/monitoring package paired with flare hardware, and may be relevant to upstream operators with gas handling or flaring; avoid transferring Pluto's value without comparable flare composition, flow and safety constraints. The source does not quantify performance post-installation.", "relationship": "No Pluto flare-upgrade project appears in checked production AI records or earlier consolidated research. Existing Woodside AI-198 (integrated well-delivery) and Maint Intel research are different workflows. This is physical measurement and instrumentation at LNG process facilities; do not count as upstream AI.", "decision_question": "After commissioning, what are observed flare destruction efficiency, methane-slip, smoke events, composition-adjusted reported emissions, safety/reliability and maintenance outcomes against a matched pre-upgrade baseline?", "company_key": "Woodside", "run": "Rounds 11–20", "disposition": "include_as_process_adjacency_with_limits", "sources": [ { "title": "Pluto’s flare upgrade redefines safety and emissions performance", "publisher": "Woodside Energy", "date": "2026-03-31", "url": "https://www.woodside.com/media-centre/news-stories/story/pluto-s-flare-upgrade-redefines-safety-and-emissions-performance", "locator": "Dated story lines 13-40; five-year design/delivery and technologies/mechanism/limits.", "access": "Issuer HTML opened directly", "supports": "Pluto LNG asset, project delivery, gas chromatography and VISR mechanisms, nitrogen reporting context, Train 2 preparation and no disclosed measured result." }, { "title": "Scope 1 and 2 GHG emissions", "publisher": "Woodside Energy", "date": "Current issuer page; cites 2025 operating data", "url": "https://www.woodside.com/sustainability/environment/climate/Scope-1-and-2-ghg-emissions", "locator": "Pluto flare composition optimisation and VISR measurements, lines 98-121.", "access": "Issuer HTML opened directly", "supports": "2025 gas chromatography installation at Pluto and monitoring purpose; separate Karratha result is not combined with Pluto." } ], "references": [], "review": { "verdict": "confirmed", "reason": "Directly reopened Woodside's 2026-03-31 Pluto flare page. It confirms delivery after five years of planning, gas-chromatograph measurement of components including methane/nitrogen, continuous VISR camera monitoring, and staged maintenance to ready the system for Train 2 integration. The page says measurements may help improve management; it does not report realized combustion/emissions gains. The finding correctly limits economics and categorizes it as LNG/process adjacency.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R15-GLOBAL-01", "verdict": "confirmed", "patch": {}, "reason": "Directly reopened Woodside's 2026-03-31 Pluto flare page. It confirms delivery after five years of planning, gas-chromatograph measurement of components including methane/nitrogen, continuous VISR camera monitoring, and staged maintenance to ready the system for Train 2 integration. The page says measurements may help improve management; it does not report realized combustion/emissions gains. The finding correctly limits economics and categorizes it as LNG/process adjacency.", "sources_inspected": [ { "url": "https://www.woodside.com/media-centre/news-stories/story/pluto-s-flare-upgrade-redefines-safety-and-emissions-performance", "access": "Directly opened Woodside primary HTML", "locator": "Lines 13–40: publication date, technology mechanism, nitrogen estimate, conditional value language and staged-maintenance status." } ], "recommended_disposition": "include_as_process_adjacency_with_limits" } ] }, "department": "Water, emissions & energy", "group_id": "T20-R15-GLOBAL-01", "core_company": true, "ai_ids": [], "evidence": "Source text reviewed", "context_only": false, "display_period": "Announcement 2026-03-31; no steady-state measurement window or before/after operating data provided." }, { "id": "O14C-TOTAL", "group_id": "O14C-TOTAL", "company": "TotalEnergies", "company_key": "TotalEnergies", "department": "Drilling & completions", "title": "A 15-year agreement for a shared well-planning environment", "kind": "context", "stage": "New digital-planning agreement; no AI deployment established", "operating_period": "Agreement announced 8 October 2026; implementation and completion dates are not given.", "claim": "SLB announced a 15-year DrillPlan agreement for TotalEnergies’s global upstream portfolio. The work connects subsurface information with well design and engineering. Offset-well data, trajectories, casing, completion inputs and planning assumptions are brought into a common environment while retaining customer workflows and internal digital expertise.", "economics": "No rollout population, achieved operating benefit, contract value or return is disclosed.", "baseline": "No achieved before/after comparison supplied.", "ai_role": "AI component not identified in this announcement.", "limits": "The release does not identify an AI component. It belongs in operating-technology context, not the AI-adoption count. A 15-year term does not prove the whole portfolio is already live.", "decision_question": "Does a common planning environment make it easier to compare alternatives and preserve the assumptions behind a well decision?", "sources": [ { "title": "SLB awarded digital drilling contract by TotalEnergies", "url": "https://investorcenter.slb.com/news-releases/news-release-details/slb-awarded-digital-drilling-contract-totalenergies", "date": "2026-10-08", "publisher": "SLB", "locator": "8 October 2026 release; agreement description and Key Points", "access": "Agreement announced 8 October 2026; implementation and completion dates are not given. Original-source review is not independent validation." } ], "disposition": "background", "category": "Digital well planning", "relationship": "Separate operating-technology announcement; no new AI profile.", "run": "Third October 14 targeted pass", "ai_ids": [], "core_company": true, "context_only": false, "display_period": "2026-10-08", "evidence": "Original publisher disclosure; results remain source-reported" }, { "id": "W14PM-ENI", "group_id": "W14PM-ENI", "company": "Eni", "company_key": "Eni", "department": "Drilling & completions", "title": "Closed-loop drilling and pressure management on one Indonesian well", "kind": "context", "stage": "Operating automation; AI component not specified", "operating_period": "9 July 2026 announcement; one exploration well supports the reported result, not a fleet-wide rollout.", "claim": "Halliburton describes LOGIX coordinating drilling, tripping and managed-pressure drilling on an Eni deepwater exploration well offshore Indonesia. Rig equipment, automated well placement, downhole hydraulics and pressure controls operate in a connected closed loop. Human approval, handoff and safety-interlock arrangements are not detailed.", "economics": "Supplier reports over 15% better efficiency, without defining the efficiency measure, baseline or absolute time/cost effect.", "baseline": "Efficiency baseline and denominator not defined.", "ai_role": "AI/ML component not specified in the deployment release.", "limits": "The release does not identify the AI/ML elements. Retained as operating technology, outside the AI-adoption and result counts.", "decision_question": "Which decisions are automated, and how much useful well-delivery time changes under comparable pressure conditions?", "sources": [ { "title": "Eni and Halliburton achieve industry first with closed-loop rig automation in deepwater Indonesia", "url": "https://www.halliburton.com/en/about-us/press-release/eni-halliburton-achieve-industry-first-closed-loop-rig-automation-indonesia", "date": "2026-07-09", "publisher": "Halliburton", "locator": "9 July 2026 release: deployment, integrated controls and reported efficiency", "access": "Original release read 14 October 2026" } ], "disposition": "background", "category": "Closed-loop drilling automation", "relationship": "One well; distinct from an AI model deployment.", "run": "14 October evening research watch", "ai_ids": [], "core_company": true, "context_only": false, "display_period": "2026-07-09", "evidence": "Original publisher disclosure; results remain source-reported" }, { "id": "W15AM-SUNCOR", "group_id": "W15AM-SUNCOR", "company": "Suncor", "company_key": "Suncor", "department": "Production & field operations", "title": "A single model helps decide where the molecules should go", "kind": "context", "stage": "Operating linear-programming model; management calls it AI", "operating_period": "Present-tense operating description on the 5 August 2026 call, discussing Q2 adjustments. This passage was already in our earnings-call ledger; it is now easier to find in the operating-technology view.", "claim": "Suncor describes one linear-programming model connecting its oil-sands operations, Edmonton refinery, domestic markets and global export sales. During an upset, teams can change the crude slate, move diluent and route intermediate streams. The model supports regional choices across connected assets and markets. Dave Oldreive calls it a big AI tool; the disclosed method is linear programming. No machine learning or LLM is established. Management describes integrated teams maximizing value, but does not specify who approves individual model recommendations.", "economics": "The stated 10,000–15,000 barrels/day is intermediate-stream routing capability. It is not incremental AI production, savings or measured uplift. Record throughput and sales are not assigned to the optimizer.", "baseline": "No model-specific benefit baseline supplied.", "ai_role": "Management calls linear programming AI; no ML or LLM established.", "limits": "No architecture beyond linear programming, counterfactual, model-specific benefit, implementation cost or detailed control boundary. Keep it outside new AI-adoption and result counts. Suncor haulage and truck dispatch remain separate existing records.", "decision_question": "Can a team optimize the whole asset network rather than improving one unit at the expense of another?", "sources": [ { "title": "Second Quarter 2026 Financial Results Call", "url": "https://www.suncor.com/-/media/project/suncor/files/investor-centre/transcripts/2026-q2-suncor-energy-financial-results-call-transcript-en.pdf?created=20260818150055&modified=20260828195420", "date": "2026-08-05", "publisher": "Suncor Energy", "locator": "PDF page 10 (page index 9), Q&A lines 331–358, Dave Oldreive and Rich Kruger; call dated 5 August 2026", "access": "Parent read the relevant original issuer transcript passage on 15 October 2026; results remain source-reported." } ], "disposition": "background", "category": "Integrated optimization", "relationship": "Outside new AI-adoption and numerical-result counts.", "run": "15 October morning research watch", "ai_ids": [ "AI-154", "AI-099" ], "core_company": true, "context_only": false, "display_period": "2026-08-05", "evidence": "Original publisher disclosure; results remain source-reported" }, { "id": "W15AM-PETROBRAS", "group_id": "W15AM-PETROBRAS", "company": "Petrobras", "company_key": "Petrobras", "department": "Supply chain & procurement", "title": "Purchasing automation has its own value case", "kind": "context", "stage": "Reported purchasing automation; AI component not established", "operating_period": "Business plan published 27 November 2025. The slide gives annual figures without a measurement period, start date or rollout denominator.", "claim": "Petrobras reports automating purchase requests to speed up purchasing and avoid costs. The same slide also describes AI projects, but this purchasing box does not identify AI. The slide names request automation without explaining the software, process steps, business-unit coverage, approval rules or exception handling. We retain it as purchasing automation, separate from the neighboring well, forecasting, flare and control-room AI examples.", "economics": "Petrobras reports 190,000 items automated per year and average avoided costs of R$111 million per year. Avoided cost is not the same as cash collected or net savings after implementation and support costs.", "baseline": "No model-specific benefit baseline supplied.", "ai_role": "No AI identified for this purchasing box.", "limits": "Company-reported values without a disclosed baseline, cost method, implementation cost or independent validation. The slide does not establish whether the estimate is realized or forecast. Do not count this as AI adoption or add it to the separate AI benefits.", "decision_question": "Which purchasing steps disappear, which approvals still need people, and how is avoided cost calculated?", "sources": [ { "title": "2026–2030 Business Plan", "url": "https://petrobras.com.br/documents/2677942/12513210/PN%2B2026-30_27nov_final_ing.pdf/3d500254-cbf1-c5ce-56b6-008b4a28a733?download=true&t=1765223843000&version=1.0", "date": "2025-11-27", "publisher": "Petrobras", "locator": "Printed slide 158 / PDF page 158, purchase-request automation box; separate from the AI and digital-twin boxes", "access": "Parent retrieved original PDF and checked the relevant page on 15 October 2026; results remain source-reported." } ], "disposition": "background", "category": "Purchasing automation", "relationship": "Outside new AI-adoption and numerical-result counts.", "run": "15 October morning research watch", "ai_ids": [ "AI-146", "AI-219", "AI-220", "AI-221" ], "core_company": true, "context_only": false, "display_period": "2025-11-27", "evidence": "Original publisher disclosure; results remain source-reported" }, { "id": "W15X-GEORGE", "group_id": "W15X-GEORGE", "company": "Chevron", "company_key": "Chevron", "department": "Production & field operations", "title": "GEORGE helps production engineers work across thousands of wells", "kind": "context", "stage": "Reported company use; issuer or technical corroboration still needed", "operating_period": "Remarks at the 25 August 2026 plenary; SPE report published 4 September. Launch date and active-well denominator unknown.", "display_period": "2026-09-04", "claim": "SPE reports that Chevron’s Peter Nesom described GEORGE, a production-engineering assistant used for analysis, optimization and automation tasks on more than 5,000 wells. The report describes an assistant working with production engineers across several problems. It does not specify its models, tools, data connections, approval steps or control-system permissions.", "economics": "More than 5,000 wells is reported use scope. No production uplift, time saving, cost or net return is supplied.", "baseline": "No matched operating comparison or full-cost baseline supplied.", "ai_role": "Reported assistant; architecture and authority not specified.", "limits": "Original conference reporting of named operator remarks, not an operator-authored deployment paper. The event program corroborates speaker and session only. Keep as reported use awaiting technical corroboration, outside additional adoption/result counts. Do not infer an LLM architecture, autonomous field control or a company-wide knowledge system.", "decision_question": "Which engineering tasks does GEORGE complete, what must engineers approve, and what changes in field performance?", "sources": [ { "title": "Maximizing Every Barrel: Artificial Lift Embraces Automation", "url": "https://jpt.spe.org/maximizing-every-barrel-artificial-lift-embraces-automation", "date": "2026-09-04", "publisher": "SPE / Journal of Petroleum Technology", "locator": "Chevron section: Peter Nesom remarks following the image caption; 25 August 2026 plenary, reported 4 September", "access": "Original SPE/JPT report read by editor 15 October 2026; named operator remarks reported by the publisher, not issuer technical validation." }, { "title": "SPE Artificial Lift 2026 opening plenary program", "url": "https://www.spe-events.org/artificiallift/attend/special-sessions/opening-plenary-session", "date": "2026-08-25 (event date; page publication date unknown)", "publisher": "Society of Petroleum Engineers", "locator": "Opening plenary: Peter Nesom, Chevron Global Upstream Production Engineering CoE", "access": "Official event page read; corroborates speaker identity and session, not GEORGE scope or performance." } ], "disposition": "background", "category": "Engineering assistants and technology foundations", "relationship": "Related company research is not evidence that projects share architecture, control rights or benefits.", "run": "15 October follow-up Luna watch", "ai_ids": [], "core_company": true, "context_only": false, "evidence": "Original SPE/JPT report read by editor 15 October 2026; named operator remarks reported by the publisher, not issuer technical validation." }, { "id": "W15X-PETROBRAS", "group_id": "W15X-PETROBRAS", "company": "Petrobras", "company_key": "Petrobras", "department": "Reservoir engineering & field development", "title": "A reservoir assistant is tested as an interface to technical systems", "kind": "context", "stage": "Research prototype and test scenarios; operating rollout not established", "operating_period": "Published 21 October 2025, OTC Brasil. Test dates and subsequent rollout unknown.", "display_period": "2025-10-21", "claim": "A Petrobras-coauthored paper proposes a GPT-based assistant for reservoir-management systems, intended to let engineers use natural-language requests instead of navigating technical interfaces. The abstract describes model training and tests of domain-specific requests, including attempts to avoid sensitive or irrelevant responses. It does not identify the model provider, connected applications, tool permissions or production deployment.", "economics": "The authors report favorable test behavior and training loss approaching zero. No held-out task-success denominator, active users, field result or economics is disclosed. Training loss is not proof of reliable operating decisions.", "baseline": "No matched operating comparison or full-cost baseline supplied.", "ai_role": "Research prototype; no operating rollout established.", "limits": "Publisher-indexed original abstract reviewed; full paper not retrieved. Retained as research, outside operating adoption and outcome counts. No evidence of permission to change reservoir plans or execute downstream actions.", "decision_question": "Does it perform useful tasks reliably on unseen requests, preserve access rights and leave an auditable record?", "sources": [ { "title": "Virtual Assistant Using Generative Pre-Trained Transformers on Reservoir Management Context", "url": "https://onepetro.org/OTCBRASIL/proceedings-abstract/25OTCB/25OTCB/D011S005R007/792383", "date": "2025-10-21", "publisher": "Petrobras and Tecgraf / PUC-Rio authors; Offshore Technology Conference", "locator": "OTC-36185-MS; publisher-indexed author list and abstract, test-scenario paragraphs", "access": "Original publisher-indexed abstract read by editor 15 October 2026; direct page retrieval failed and the full paper was not retrieved." } ], "disposition": "background", "category": "Engineering assistants and technology foundations", "relationship": "Related company research is not evidence that projects share architecture, control rights or benefits.", "run": "15 October follow-up Luna watch", "ai_ids": [], "core_company": true, "context_only": false, "evidence": "Original publisher-indexed abstract read by editor 15 October 2026; direct page retrieval failed and the full paper was not retrieved." }, { "id": "W15X-EXXON-ESP", "group_id": "W15X-EXXON-ESP", "company": "ExxonMobil", "company_key": "ExxonMobil", "department": "Production & field operations", "title": "ESP recommendations pass safety checks before reaching the controller", "kind": "context", "stage": "26-well pilot in 2025; broader 2026 rollout reported separately", "operating_period": "Paper published 18 August 2025; pilot dates unspecified. A September 2026 conference report describes wider Permian rollout underway, without a completed-fleet count.", "display_period": "2025-08-18", "claim": "ExxonMobil authors describe a closed-loop ESP pilot on 26 Midland wells. Commercial physics-based software recommends changes; internal checks test facility constraints and pump limits before execution. Recommendations that pass the checks can be written automatically to field devices from different controller makers, without a person approving every change. The abstract does not identify machine learning; an AI keyword does not establish the deployed method.", "economics": "The authors describe less surveillance and execution work, without numerical time, production or financial results. No complete cost or net return is supplied.", "baseline": "No matched operating comparison or full-cost baseline supplied.", "ai_role": "No machine-learning mechanism identified; physics-based control.", "limits": "Original publisher-indexed abstract reviewed; full paper not retrieved. It establishes physics-based control and a validation gate, not an LLM controlling pumps. This is separate from AI-235’s gas-lift ML and its oil-uplift figures.", "decision_question": "What happens when data is stale, a recommendation fails a check, or operating conditions move outside the validated range?", "sources": [ { "title": "Closed-Loop ESP Optimization to Maximize Asset Value", "url": "https://onepetro.org/SPEESP/proceedings-abstract/25ESP/25ESP/D031S006R001/788064", "date": "2025-08-18", "publisher": "ExxonMobil authors / Society of Petroleum Engineers", "locator": "SPE-225261-MS; abstract, system checks and 26-well pilot paragraphs", "access": "Original publisher-indexed abstract read by editor 15 October 2026; direct page retrieval failed and the full paper was not retrieved." }, { "title": "Maximizing Every Barrel: Artificial Lift Embraces Automation", "url": "https://jpt.spe.org/maximizing-every-barrel-artificial-lift-embraces-automation", "date": "2026-09-04", "publisher": "SPE / Journal of Petroleum Technology", "locator": "ExxonMobil / Mark Agnew remarks, closed-loop ESP rollout and facility constraints paragraphs", "access": "Original SPE/JPT conference report read. Later rollout is reported underway; no completed-fleet count or quantified ESP benefit. Separate from the 2025 pilot abstract." } ], "disposition": "background", "category": "Engineering assistants and technology foundations", "relationship": "Related company research is not evidence that projects share architecture, control rights or benefits.", "run": "15 October follow-up Luna watch", "ai_ids": [ "AI-235" ], "core_company": true, "context_only": false, "evidence": "Original publisher-indexed abstract read by editor 15 October 2026; direct page retrieval failed and the full paper was not retrieved." }, { "id": "W15X-AETHON", "group_id": "W15X-AETHON", "company": "Aethon Energy", "company_key": "Aethon Energy", "department": "IT, data & enterprise transformation", "title": "Aethon’s CIO describes the foundations for better data use", "kind": "context", "stage": "Executive-reported modernization; no AI deployment disclosed", "operating_period": "20–26 February 2026 issue. Individual project dates and completion of the data initiatives are unknown.", "display_period": "2026-02-20 to 2026-02-26", "claim": "Aethon CIO Kang Chen reports a full cloud migration and technology overhaul, along with new data-quality, analytics and workforce-training initiatives. The profile also describes cybersecurity benchmarking. It names no cloud provider, data domains, field applications or AI model.", "economics": "No quantitative operating or financial result is supplied.", "baseline": "No matched operating comparison or full-cost baseline supplied.", "ai_role": "No AI deployment disclosed.", "limits": "Named executive self-report in an advertising supplement, not independent technical validation. Cloud migration and upskilling do not prove AI readiness or deployment. Keep as company transformation context, outside AI adoption and outcome counts.", "decision_question": "Which field and business data can teams actually reuse, and what applications have they put into daily work?", "sources": [ { "title": "Dallas CIO ORBIE special advertising supplement", "url": "https://media.bizj.us/view/img/13143357/low-res-dallasorbiesciospecial-section2026-8951090d-b07f-4f22-bfba-90c5a075a999.pdf", "date": "2026-02-20 to 2026-02-26", "publisher": "Dallas Business Journal / DallasCIO advertising supplement", "locator": "PDF page 10 / printed page 10, Kang Chen profile; supplement dated 20–26 February 2026", "access": "Original advertising-supplement PDF text read by editor 15 October 2026; named executive self-report, not independent validation." } ], "disposition": "background", "category": "Engineering assistants and technology foundations", "relationship": "Related company research is not evidence that projects share architecture, control rights or benefits.", "run": "15 October follow-up Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Original advertising-supplement PDF text read by editor 15 October 2026; named executive self-report, not independent validation." }, { "id": "W15PM-REPSOL", "group_id": "W15PM-REPSOL", "company": "Repsol", "company_key": "Repsol", "department": "Production & field operations", "title": "Repsol completes an initial phase of an autonomous glycol-plant optimizer", "kind": "context", "stage": "Initial phase completed; operating use not established", "operating_period": "2025 annual report, released 19 February 2026. Project and commissioning dates are not supplied.", "display_period": "2026-02-19", "claim": "Repsol says it completed the initial phase of its first Autonomous Optimizer with Control, developed internally for one section of a glycol plant. The report calls the optimizer AI-based. It does not identify the plant, model, controlled variables, operating limits, approval steps or fallback.", "economics": "No measured plant result, cost or net return is disclosed.", "baseline": "No measured operating comparison or full-cost baseline supplied.", "ai_role": "AI-based autonomous optimizer described; model and control authority unspecified.", "limits": "Completing an initial phase does not establish routine autonomous operation or a plant-wide rollout. Keep separate from Repsol’s multiagent, workforce and legal programs.", "decision_question": "What did the initial phase demonstrate, and what must operators approve before it can control the process?", "sources": [ { "title": "2025 Group Annual Financial Report", "url": "https://www.repsol.com/content/dam/repsol-corporate/en_gb/accionistas-e-inversores/ref/2026/ref19022026-2025-group-annual-financial-report.pdf", "date": "2026-02-19", "publisher": "Repsol", "locator": "PDF page 195 / printed Management Report page 45, section 5.5: AI-based autonomous optimizers", "access": "Editor retrieved the original PDF, read the relevant text and inspected the rendered page on 15 October 2026." } ], "disposition": "background", "category": "Control and engineering feedback", "relationship": "A new control milestone or vendor capability is not a new operating-adoption count.", "run": "15 October evening Luna watch", "ai_ids": [ "AI-031", "AI-032" ], "core_company": true, "context_only": false, "evidence": "Editor retrieved the original PDF, read the relevant text and inspected the rendered page on 15 October 2026." }, { "id": "W15PM-CORVA-OLIA", "group_id": "W15PM-CORVA-OLIA", "company": "Corva / Oliasoft", "company_key": "Corva / Oliasoft", "department": "Drilling & completions", "title": "Well designs and drilling data are being connected in both directions", "kind": "context", "stage": "Integration developed; customer pilots being prepared", "operating_period": "Announced 12 October 2026; pilot start dates are unspecified. Newly found evidence, not a disclosure after the previous update.", "display_period": "2026-10-12", "claim": "The vendors have developed an integration between Oliasoft WellDesign and Corva Real-Time AI and say they are preparing customer pilots. Design trajectories, casing and pressure assumptions can inform drilling workflows. As-drilled trajectories, operational data and nonproductive-time events return to planning and model calibration.", "economics": "No pilot customer, well or rig count, measured benefit, implementation cost or ROI is disclosed.", "baseline": "No measured operating comparison or full-cost baseline supplied.", "ai_role": "Planning and operational data integration; customer pilots being prepared, rig control not established.", "limits": "Model feedback is not evidence of automatic rig control. Two vendor versions of the same release do not provide independent validation; action permissions are unspecified.", "decision_question": "Can the pilot show fewer repeat design errors or faster decisions, with engineers able to review the changes?", "sources": [ { "title": "Corva and Oliasoft Create a Continuous Learning Loop Between Well Design and Drilling", "url": "https://www.corva.ai/blog/corva-and-oliasoft-create-a-continuous-learning-loop-between-well-design-and-drilling", "date": "2026-10-12", "publisher": "Corva and Oliasoft", "locator": "Joint release: engineering-to-operations, operations-to-engineering, and customer-pilot paragraphs", "access": "Editor read both vendors’ original releases on 15 October 2026; neither supplies customer-pilot outcomes." }, { "title": "Corva and Oliasoft Create a Continuous Learning Loop Between Well Design and Drilling", "url": "https://oliasoft.com/articles/corva-and-oliasoft-create-a-continuous-learning-loop-between-well-design-and-drilling", "date": "2026-10-12", "publisher": "Oliasoft", "locator": "Joint release: engineering-to-operations, operations-to-engineering, and customer-pilot paragraphs", "access": "Original partner release read; same joint announcement, not independent validation." } ], "disposition": "background", "category": "Control and engineering feedback", "relationship": "A new control milestone or vendor capability is not a new operating-adoption count.", "run": "15 October evening Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read both vendors’ original releases on 15 October 2026; neither supplies customer-pilot outcomes." }, { "id": "W16AM-TOTAL-DRUM", "group_id": "W16AM-TOTAL-DRUM", "company": "TotalEnergies", "company_key": "TotalEnergies", "department": "Refining, LNG & process operations", "title": "TotalEnergies reportedly dropped one drum-cycling use case", "kind": "negative_evidence", "stage": "One use case reportedly dropped; company confirmation still needed", "operating_period": "Drum work started July 2025; remarks reported June 2026. Exact decision date unknown.", "display_period": "2026-06-11", "claim": "Control Global quotes TotalEnergies engineer Thomas Klein saying a Port Arthur drum-level model achieved 75% prediction accuracy, but the drum-cycling use case was not retained. Drum switching depended on conditions outside the model’s scope. The work provided advice, not autonomous control.", "economics": "The report does not define the accuracy denominator or test set, or quantify cost or loss. Other pilot work continued; the entire program was not reported abandoned.", "baseline": "No comparable full-cost operating baseline disclosed.", "ai_role": "Reported advisory prediction; not autonomous process control.", "limits": "Original conference reporting, labeled Sponsored. We could not retrieve the presentation or a later company statement. The earlier company release confirms the broader pilot, not the decision to drop this use case. Keep these figures separate from its five-event result.", "decision_question": "Did the model help operators choose when to switch drums, rather than merely predict drum level?", "sources": [ { "title": "Honeywell AI pilot aids coker unit operations at TotalEnergies refinery", "url": "https://www.controlglobal.com/show-coverage/honeywell-users-group/article/55383668/honeywell-ai-pilot-aids-coker-unit-operations-at-totalenergies-refinery", "date": "2026-06-11", "publisher": "Control Global / Honeywell Users Group coverage", "locator": "Drum cycling prediction section; Thomas Klein remarks at Honeywell Users Group Americas 2026", "access": "Editor read the original conference report and both partners’ earlier releases. The decision to drop this use case rests on reported named remarks, not a company-authored outcome report." }, { "title": "TotalEnergies and Honeywell pilot AI-assisted control room", "url": "https://corporate.totalenergies.us/news/totalenergies-and-honeywell-pilot-ai-assisted-control-room-accelerated-shift-industrial", "date": "2025-11-11", "publisher": "TotalEnergies", "locator": "Initial DCU pilot and preliminary five-event result paragraphs", "access": "Original issuer release read. Establishes the existing pilot and operator corrective action; it predates and does not corroborate reported drum-use-case non-retention." } ], "disposition": "background", "category": "Reported decision to drop one use case", "relationship": "Related program or product evidence does not establish shared results, AI deployment or control authority.", "run": "16 October morning Luna watch", "ai_ids": [ "AI-207" ], "core_company": true, "context_only": false, "evidence": "Editor read the original conference report and both partners’ earlier releases. The decision to drop this use case rests on reported named remarks, not a company-authored outcome report." }, { "id": "W16AM-HP", "group_id": "W16AM-HP", "company": "Helmerich & Payne", "company_key": "Helmerich & Payne", "department": "Drilling & completions", "title": "ExxonMobil has two FlexRobotics systems deployed; seven more are planned", "kind": "context", "stage": "Two systems deployed; seven additional systems planned", "operating_period": "Published 7 October 2026. Initial deployment dates, basin and rig identities are not supplied.", "display_period": "2026-10-07", "claim": "H&P reports two FlexRobotics systems deployed on its rigs for ExxonMobil. It expects seven more over the following twelve months, for nine in total. The robots automate repetitive rig-floor activities. The announcement does not identify an AI/ML mechanism, task-level approval, supervision or stop authority.", "economics": "Two is the deployed count; nine is the intended total. No quantified safety, time, cost or net return is disclosed.", "baseline": "No comparable full-cost operating baseline disclosed.", "ai_role": "No AI/ML mechanism established in this deployment update.", "limits": "An ExxonMobil executive supports expansion intent; the joint account is not independent outcome validation. It does not establish installation of the separate AI camera add-on in AI-116. Keep as robotics context, outside AI-adoption counts.", "decision_question": "What changes in crew exposure and connection performance after deployment, under comparable rig conditions?", "sources": [ { "title": "H&P & ExxonMobil Expand Deployment of FlexRobotics Technology", "url": "https://ir.hpinc.com/news/press-releases/news-details/2026/HP--ExxonMobil-Expand-Deployment-of-FlexRobotics-Technology/default.aspx", "date": "2026-10-07", "publisher": "Helmerich & Payne", "locator": "Opening release paragraphs: first two systems, seven additional units over next 12 months; ExxonMobil quotation", "access": "Original H&P release read by editor; customer quotation corroborates intent, not quantified results." } ], "disposition": "background", "category": "Robotics and instrumentation", "relationship": "Related program or product evidence does not establish shared results, AI deployment or control authority.", "run": "16 October morning Luna watch", "ai_ids": [ "AI-116" ], "core_company": true, "context_only": true, "evidence": "Original H&P release read by editor; customer quotation corroborates intent, not quantified results." }, { "id": "W16AM-RETINA", "group_id": "W16AM-RETINA", "company": "SLB", "company_key": "SLB", "department": "Drilling & completions", "title": "Earlier formation images are now reported from more than 50 wells", "kind": "context", "stage": "Commercial deployment milestone; vendor-reported", "operating_period": "Published 15 October 2026; individual deployment dates and customer identities unknown. Publication time cannot be placed after the previous update.", "display_period": "2026-10-15", "claim": "SLB says Retina has imaged more than 50 wells across 18 locations during its first year of commercial deployment. The instrument acquires formation images at the bit while drilling, at roughly 2 mm resolution, to inform well placement and development decisions.", "economics": "Deployment and imaging specifications are not measured recovery, drilling-time savings or ROI. No comparative economics is disclosed.", "baseline": "No comparable full-cost operating baseline disclosed.", "ai_role": "No AI/ML mechanism established in this deployment update.", "limits": "No AI/ML mechanism or automatic control is identified. Keep as instrumentation context; do not transfer OQ Oman’s separate drilling-tool results to Retina.", "decision_question": "Does earlier imaging change a placement decision or avoid a cost, compared with the previous workflow?", "sources": [ { "title": "Retina At-Bit Imaging System Surpasses 50-Well Milestone in First Year of Deployment", "url": "https://www.slb.com/newsroom/features/2026/2026-1015-retina", "date": "2026-10-15", "publisher": "SLB", "locator": "Published date; Global adoption and Global deployment sections", "access": "Editor read the original SLB feature; performance and scope remain vendor-reported." } ], "disposition": "background", "category": "Robotics and instrumentation", "relationship": "Related program or product evidence does not establish shared results, AI deployment or control authority.", "run": "16 October morning Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Editor read the original SLB feature; performance and scope remain vendor-reported." }, { "id": "W16PM-PTTEP", "group_id": "W16PM-PTTEP", "company": "PTTEP", "company_key": "PTTEP", "department": "Production & field operations", "title": "PTTEP’s CEO describes AI in drilling, alongside planning and production systems", "kind": "context", "stage": "Company reports operating use; individual assets and scale unspecified", "operating_period": "Meeting held 30 March 2026; minutes posted 10 April, confirmed by the cover letter. Individual deployment dates are unknown.", "display_period": "2026-04-10", "claim": "At its March AGM, PTTEP described deployed AI and automation across subsurface, drilling and production work, including AI that monitors drilling data for early risk detection. The other examples are automated planning of well locations and wellhead platforms, and systems optimizing production across many wells. Their specific AI methods are not identified.", "economics": "Management says benefits are reaching financial performance, but gives no isolated AI result, baseline, cost or ROI.", "baseline": "No matched AI-specific operating or financial comparison disclosed.", "ai_role": "Drilling-data risk monitoring is explicitly AI. Planning is automation and production is optimization; their AI methods are unspecified.", "limits": "No fields, vendors, well count, model performance or approval/control boundaries are disclosed. The separate USD 328m new-business budget is not AI-only. This broad account does not establish the scope or success of the later offshore advisory pilot in AI-067.", "decision_question": "Which fields use these systems, what do people approve, and what operating result survives a matched comparison?", "sources": [ { "title": "Minutes of the 2026 Annual General Shareholders’ Meeting", "url": "https://www.pttep.com/storage/document/shareholder-meetings/agm2026/pttep-agm2026-minutes-en.pdf", "date": "2026-04-10", "publisher": "PTTEP", "locator": "PDF page 13 / printed page 12 of 25, response to question 1.7; cover letter on PDF page 1 confirms publication date", "access": "Editor read the official translated minutes and inspected the rendered passage. Company self-report, not independent outcome validation." } ], "disposition": "background", "category": "Company operating context", "relationship": "A broad company statement does not establish the scope, results or technology of the separately covered offshore pilot or internal audit project.", "run": "16 October evening Luna watch", "ai_ids": [ "AI-067", "AI-245" ], "core_company": true, "context_only": true, "evidence": "Editor read the official translated minutes and inspected the rendered passage. Company self-report, not independent outcome validation." }, { "id": "W17AM-KANTORI", "group_id": "W17AM-KANTORI", "company": "Baker Hughes", "company_key": "Baker Hughes", "department": "Drilling & completions", "title": "An “autonomous” drilling product was used in advisory mode", "kind": "context", "stage": "Single-well advisory case; deployment date unknown", "operating_period": "PDF revised April 2026, with a 2023 copyright. Original publication and field-work dates are unknown; this may be older operating context. The September 2026 webpage date was not independently verified.", "display_period": "2026-04", "claim": "Baker Hughes describes an advisory-mode UAE carbonate-drilling case supported from its remote operations centre. AI assisted torque-and-drag work. Despite the product name, the case explicitly says advisory mode; who approved parameter changes is not stated.", "economics": "The vendor reports 22 alerts, 22 hours saved against a previous well, 5% higher penetration rate and no stuck pipe or fluid losses.", "baseline": "Prior well; matching conditions not disclosed.", "ai_role": "AI assisted torque-and-drag work. Despite the product name, the case explicitly says advisory mode; who approved parameter changes is not stated.", "limits": "The customer and well are unnamed. A prior-well comparison does not isolate AI from the wider automation service, crew or geology. Costs, accepted recommendations and repeatability are undisclosed; no ROI is established. The deployment date is unknown; the PDF revision does not establish a 2026 deployment.", "decision_question": "Which recommendations changed drilling practice, and did the time saving repeat on comparable wells?", "sources": [ { "title": "Kantori drilling advisory case · UAE", "url": "https://dam.bakerhughes.com/m/6c9e1d4e04184778/original/i-Trak-service-maximized-ROP-saved-22hrs-UAE-cs.pdf#page=1", "date": "2026-04", "publisher": "Baker Hughes", "locator": "Single-page case sheet; Solution, Results and footer revision 04/2026", "access": "Original PDF read and rendered. HTML case page returned 403 to editor. Revision date is not a field-deployment date." } ], "disposition": "background", "category": "Drilling advisory case", "relationship": "Supplementary source note; not a new named operator adoption or outcome count.", "run": "17 October morning Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original PDF read and rendered. HTML case page returned 403 to editor. Revision date is not a field-deployment date." }, { "id": "W17AM-PDO", "group_id": "W17AM-PDO", "company": "Petroleum Development Oman", "company_key": "Petroleum Development Oman", "department": "IT, data & enterprise transformation", "title": "PDO contracted for a shared industrial data and workflow system", "kind": "context", "stage": "Agreement announced; operating rollout unverified", "operating_period": "Announced 8 September 2025, with an ambition to start deploying the twins that year. No later completion evidence was verified in this pass.", "display_period": "2025-09-08", "claim": "PDO selected Kongsberg Digital’s Kognitwin to connect operational and enterprise data across operations and maintenance. The release calls it AI-integrated, but does not identify an AI task, model or authority to act.", "economics": "Safety, production and cost improvements are goals. No measured benefit, contract value or ROI is disclosed.", "baseline": "No measured result.", "ai_role": "The release calls it AI-integrated, but does not identify an AI task, model or authority to act.", "limits": "No fields, facilities, users or workflow counts are identified. The company-description paragraph about gas operations does not define deployment scope. A passed target date alone does not establish delay or failure.", "decision_question": "Which facilities are live, which tasks use AI, and what do people still approve?", "sources": [ { "title": "Kongsberg Digital and PDO digital-twin agreement", "url": "https://kommunikasjon.ntb.no/pressemelding/18645626/kongsberg-digital-and-petroleum-development-oman-sign-agreement-for-deployment-of-ai-powered-digital-twin?lang=en&publisherId=17849150", "date": "2025-09-08", "publisher": "KONGSBERG / NTB", "locator": "Release timestamp 8 September 2025; scope and deployment-ambition paragraphs", "access": "Editor read original source; company/vendor claims are not independently validated." } ], "disposition": "background", "category": "Industrial data and workflow foundation", "relationship": "Supplementary source note; not a new named operator adoption or outcome count.", "run": "17 October morning Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original source; company/vendor claims are not independently validated." }, { "id": "W17PM-INPEX", "group_id": "W17PM-INPEX", "company": "INPEX", "company_key": "INPEX", "department": "IT, data & enterprise transformation", "title": "INPEX changed its core system and the processes around it", "kind": "context", "stage": "ERP operating in Japan since January 2026; no AI use case established", "operating_period": "Joint release published 24 June 2026; Japan go-live January 2026. Other countries’ rollout dates are not supplied.", "display_period": "2026-06-24", "claim": "INPEX reports that SAP Cloud ERP Private began full operation in Japan in January 2026. With ABeam’s support, it aligned business processes to SAP standards instead of filling gaps with custom add-ons.", "economics": "The release says development was shortened, without giving elapsed time or a comparison. Reporting and workload improvements are objectives; no measured savings or ROI are disclosed.", "baseline": "Previous IBOS/SAP ERP introduced in 2008; no quantified implementation-time comparison supplied.", "ai_role": "No deployed AI task established. AI compatibility/objectives are not proof of an implemented feature.", "limits": "AI appears as compatibility and a future efficiency objective, not a deployed function. Users, departments, costs and approval rules are unspecified. No connection to the separate Copilot/management-meeting agents in AI-294 is established.", "decision_question": "Which processes changed, and can the separate AI tools access those records with appropriate permissions?", "sources": [ { "title": "INPEX commences operations of SAP Cloud ERP", "url": "https://www.inpex.com/english/news/upload/20260624.pdf#page=2", "date": "2026-06-24", "publisher": "INPEX / SAP Japan / ABeam Consulting", "locator": "PDF pages 1–2; Japan go-live and Fit-to-Standard approach on page 2", "access": "Editor read the official three-page PDF and inspected page 2. ERP use is established; AI operation and Copilot integration are not." } ], "disposition": "background", "category": "Enterprise applications and process reform", "relationship": "Separate company foundation from AI-294. No ERP-to-Copilot integration or shared authority established.", "run": "17 October evening Luna watch", "ai_ids": [ "AI-294" ], "core_company": true, "context_only": true, "evidence": "Editor read the official three-page PDF and inspected page 2. ERP use is established; AI operation and Copilot integration are not.", "asset": "Japan enterprise management systems; no named producing asset.", "partner": "SAP Japan; ABeam Consulting" }, { "id": "W18AM-SPGLOBAL", "group_id": "W18AM-SPGLOBAL", "company": "S&P Global Energy", "company_key": "S&P Global Energy", "department": "IT, data & enterprise transformation", "title": "Energy data is becoming something customers’ agents can query", "kind": "context", "stage": "Built architecture described; launch date and user population undisclosed", "operating_period": "Published 25 September 2026. Implementation and external-customer launch dates are not disclosed.", "display_period": "2026-09-25", "claim": "S&P Global Energy describes giving internal and customer agents conversational access to structured energy datasets. Domain experts curate narrow dataset agents. A reusable MCP interface combines them across commodities. The account says table permissions and audit controls carry through, and experts can test answers against benchmarks.", "economics": "A customer executive reports setup shrinking from development cycles measured in months to days. No sample, measured accuracy, active-user count, cost or ROI is supplied.", "baseline": "No measured matched baseline disclosed.", "ai_role": "Domain experts curate narrow dataset agents. A reusable MCP interface combines them across commodities. The account says table permissions and audit controls carry through, and experts can test answers against benchmarks.", "limits": "This is a vendor-published customer account, not an independent quality or security assessment. Benchmarks are described without scores. Access to research data does not establish authority to trade, approve investment or control field equipment.", "decision_question": "Who owns the data definitions, and which benchmark and permission checks must pass before a new agent can use them?", "sources": [ { "id": "WATCH18AM-SPGLOBAL", "title": "From Data to Dialogue: S&P Global Energy’s Genie and MCP architecture", "url": "https://www.databricks.com/blog/data-dialogue-how-sp-global-energy-made-its-structured-data-estate-conversational-databricks", "date": "2026-09-25", "publisher": "Databricks / S&P Global Energy", "locator": "Date; per-dataset curation; Unity Catalog permissions; FastMCP composition; customer quote and benchmark loop", "access": "Editor read the original vendor customer account. Architecture and benefits remain vendor/customer-reported.", "excerpt": "now takes days" } ], "disposition": "background", "category": "Energy data products", "relationship": "Supplementary context; no new operator adoption or numerical AI-result count.", "run": "18 October morning Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read the original vendor customer account. Architecture and benefits remain vendor/customer-reported." }, { "id": "W18AM-PETROREC", "group_id": "W18AM-PETROREC", "company": "PetroReconcavo", "company_key": "PetroReconcavo", "department": "IT, data & enterprise transformation", "title": "PetroReconcavo connects its field network and back-office systems", "kind": "context", "stage": "ERP implemented and six LTE towers activated in 2024 reporting; GenAI scope unresolved", "operating_period": "Portuguese report published 14 July 2025, confirmed by issuer notice. It covers 2024; exact go-live dates are unknown, so an in-window deployment is not established.", "display_period": "2025-07-14", "claim": "PetroReconcavo reports implementing SAP and activating six LTE towers in Bahia and Rio Grande do Norte. The ERP work connected production data and material tracking. The field network supports monitoring and prepares for IoT and automation. A separate data-lake passage describes GenAI analytics, reports and assistants without naming a tool or defining live use.", "economics": "The report lists more than 2,200 training hours for SAP. Faster response and stronger controls are qualitative claims; no measured savings, cost or ROI is disclosed.", "baseline": "No measured matched baseline disclosed.", "ai_role": "The ERP work connected production data and material tracking. The field network supports monitoring and prepares for IoT and automation. A separate data-lake passage describes GenAI analytics, reports and assistants without naming a tool or defining live use.", "limits": "No partner, user population, AI approval rules or autonomous control is specified. Tower and training counts are implementation scope, not economic outcomes. Company-wide emissions and social results are unrelated and are not attributed to this technology.", "decision_question": "Which field and finance tasks improved after the systems went live, and what did people still have to do manually?", "sources": [ { "id": "WATCH18AM-PETROREC", "title": "Relatório de Sustentabilidade 2024", "url": "https://www.petroreconcavo.com.br/Download.aspx?Arquivo=OXSl%2FB7SEmrx%2BHoNzBeFlQ%3D%3D#page=78", "date": "2025-07-14", "publisher": "PetroReconcavo", "locator": "PDF / printed page 78: SAP, Projeto Waves and data lake", "access": "Editor retrieved the original 100-page Portuguese PDF after encoding the plus sign in its download parameter; page 78 read and rendered.", "excerpt": "A nova rede possibilita monitoramento em tempo real" }, { "id": "WATCH18AM-PETROREC-DATE", "title": "2024 Sustainability Report · Notice to the Market", "url": "https://ri.petroreconcavo.com.br/Download.aspx?Arquivo=6hzxLJkhGOrPzcEDtUKx3A%3D%3D&IdCanal=ckeQVNzVtM%2FZZ4T5tqRLLw%3D%3D", "date": "2025-07-14", "publisher": "PetroReconcavo", "locator": "PDF pages 1–2; publication announcement and English-edition timing", "access": "Original issuer notice read; Portuguese publication 14 July, English edition separately planned for 25 July 2025.", "excerpt": "published, on this date, its 2024 Sustainability Report" } ], "disposition": "background", "category": "Enterprise systems and field connectivity", "relationship": "Supplementary context; no new operator adoption or numerical AI-result count.", "run": "18 October morning Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor retrieved the original 100-page Portuguese PDF after encoding the plus sign in its download parameter; page 78 read and rendered." }, { "id": "W18PM-NOV", "group_id": "W18PM-NOV", "company": "NOV", "company_key": "NOV", "department": "Maintenance & reliability", "title": "NOV connects two agents to recommend maintenance", "kind": "context", "stage": "Supplier reports implementation; customer unnamed", "operating_period": "Release: 28 July 2026. Implementation start and duration unknown.", "display_period": "2026-07-28", "claim": "NOV describes its agent interfacing with a Norwegian operator’s agent at a sulphate-removal unit. Real-time equipment diagnostics on the Max Platform support maintenance recommendations. The release does not establish automatic execution or identify an LLM.", "economics": "No measured accuracy, downtime reduction, savings, cost or ROI disclosed.", "baseline": "No measured comparator disclosed.", "ai_role": "Real-time equipment diagnostics on the Max Platform support maintenance recommendations. The release does not establish automatic execution or identify an LLM.", "limits": "Supplier-only account; operator, unit and user population unnamed. Approval, override and safety rules undisclosed. Separate service-rig monitoring in the same release is not evidence of AI.", "decision_question": "Who checks the recommendation, and which system can authorize maintenance work?", "sources": [ { "id": "WATCH18PM-NOV", "title": "NOV Reports Second Quarter 2026 Earnings", "url": "https://investors.nov.com/news-releases/news-release-details/nov-reports-second-quarter-2026-earnings", "date": "2026-07-28", "publisher": "NOV", "locator": "Significant Achievements: Norwegian sulphate-removal unit; separate remote service-rig monitoring paragraph", "excerpt": "recommend maintenance actions using the Max Platform", "access": "Original publisher text read by editor 18 October 2026; claims remain source-reported." } ], "disposition": "background", "category": "Supplier-reported maintenance workflow", "relationship": "Unnamed customer; no new named-operator adoption or outcome count.", "run": "18 October evening Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original publisher text read by editor 18 October 2026; claims remain source-reported." }, { "id": "W19AM-TOTAL-AWS", "group_id": "W19AM-TOTAL-AWS", "company": "TotalEnergies", "company_key": "TotalEnergies", "department": "Trading & marketing", "title": "TotalEnergies uses generative AI to check trading data", "kind": "context", "stage": "Vendor reports implementation; date and rollout scope unknown", "operating_period": "AWS page undated. Implementation date, trading-desk scope, user count and transaction volume unknown; an in-window launch is not established.", "display_period": "Undated", "claim": "AWS describes a TotalEnergies Trading & Shipping system that matches structured and unstructured transaction data. The workflow supports transaction traceability and input-error detection. AWS lists Bedrock and ECS; the model, connectors and exception-handling process are unspecified.", "economics": "A named customer manager reports more reliable controls and fewer financial losses, without amounts, error rates, a baseline or an observation period.", "baseline": "No measured comparator or transaction denominator disclosed.", "ai_role": "The workflow supports transaction traceability and input-error detection. AWS lists Bedrock and ECS; the model, connectors and exception-handling process are unspecified.", "limits": "Vendor-published customer testimony, not independent validation. No costs or net ROI. Matching records does not establish authority to place trades, release payments or change books. No specific model provider can be inferred from the Bedrock service description.", "decision_question": "Which mismatches need a person’s approval, and how much error-review work does the system remove?", "sources": [ { "id": "WATCH19AM-TOTAL-AWS", "title": "TotalEnergies puts Gen AI to work on its trading operations", "url": "https://aws.amazon.com/solutions/case-studies/totalenergies/", "date": "Undated", "publisher": "AWS / TotalEnergies Trading & Shipping", "locator": "Overview; Olivier Collon customer quotation; AWS Services Used", "excerpt": "matching structured and unstructured data within transaction flows", "access": "Original AWS customer account read by editor 19 October 2026. No visible publication date; a secondary 2024-10-28 clue could not be confirmed from an original dated source." } ], "disposition": "background", "category": "Trading transaction controls", "relationship": "Undated supplementary vendor/customer account; no new adoption or numerical-result count.", "run": "19 October morning Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original AWS customer account read by editor 19 October 2026. No visible publication date; a secondary 2024-10-28 clue could not be confirmed from an original dated source.", "asset": "Trading & Shipping; desk/market scope undisclosed", "partner": "AWS" }, { "id": "W19EX-MURPHY", "group_id": "W19EX-MURPHY", "company": "Murphy Oil", "company_key": "Murphy Oil", "department": "Maintenance & reliability", "title": "A good pilot did not make maintenance AI easy to deploy", "kind": "negative_evidence", "stage": "Retrospective operating project; current status unknown", "operating_period": "Article: 20 January 2025. Alert records begin January/March 2023, before this report’s rolling window; exact project start/end dates unknown.", "display_period": "2025-01-20", "claim": "Murphy’s two-platform, 24-month project deployed 46 rotating-equipment models. Missing data delayed the first model until six months after kickoff. Incomplete maintenance records and generic anomaly alerts created investigation work. Engineers and operations staff reviewed alerts; retraining reportedly reduced false positives. Verified alerts fed maintenance notifications, later through an API.", "economics": "No quantified downtime savings, project cost or net ROI. A known-failure pilot’s 100–121-day warning was a replay, not demonstrated live lead time.", "baseline": "No controlled operational or financial comparator disclosed.", "ai_role": "AI/ML anomaly detection with human alert review; no autonomous maintenance established.", "limits": "The reviewed 2023 alerts are older context; current operating status is unknown. The authors cite insufficient supplier equipment expertise and reported mitigation—not abandonment. Platform names, supplier and precision/recall are undisclosed; no autonomous maintenance established.", "decision_question": "How many alerts lead to useful work, and what does reviewing the rest cost?", "sources": [ { "id": "WATCH19EX-MURPHY", "title": "Framework for AI- and ML-Based Predictive Maintenance for Offshore Rotating Equipment", "url": "https://jpt.spe.org/framework-for-ai-and-ml-based-predictive-maintenance-for-offshore-rotating-equipment", "date": "2025-01-20", "publisher": "Society of Petroleum Engineers / Journal of Petroleum Technology", "locator": "Methodology; Observations; Discussion: Project Planning and Management, Data Prerequisites, Domain Knowledge, Model Development, Performance, and User Experience; Figs. 4–6", "excerpt": "the first predictive model was deployed 6 months after the project kickoff", "access": "Original technical account read by editor 19 October 2026. Text and qualitative figure discussion reviewed; numeric chart values not transcribed. Not an independent outcome audit." } ], "disposition": "background", "category": "Maintenance implementation lessons", "relationship": "Supplementary context; no new adoption or numerical-result count.", "run": "19 October additional Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original technical account read by editor 19 October 2026. Text and qualitative figure discussion reviewed; numeric chart values not transcribed. Not an independent outcome audit.", "asset": "Two unnamed deepwater U.S. Gulf platforms; 2023 alert records.", "partner": "Undisclosed" }, { "id": "W19EX-NOV-AURA", "group_id": "W19EX-NOV-AURA", "company": "NOV", "company_key": "NOV", "department": "Operations & production", "title": "Remote crane control still has a person at the controls", "kind": "context", "stage": "Supplier test and one delivery; customer shore operation unestablished", "operating_period": "Article: 20 August 2026. Supplier test: Kristiansand to Søgne, Norway; exact test and first-delivery dates unknown.", "display_period": "2026-08-20", "claim": "NOV reports controlling a full-size crane from about 20 km away and delivering one Aura-equipped remote-operated crane to an unnamed customer. Aura brings camera feeds, load information, equipment diagnostics and environmental data into the human operator’s screen. Customers are expected to start onboard before moving control ashore.", "economics": "No measured cost, safety or crew reduction. Two further cranes were being built for delivery by early 2027; these are planned deliveries.", "baseline": "No controlled operational or financial comparator disclosed.", "ai_role": "Remote human crane control; no AI/ML identified.", "limits": "No AI/ML identified. Delivery does not establish shore-controlled customer operations or autonomous lifting. Customer, vessel, operational hours, interlocks and fallback arrangements are undisclosed.", "decision_question": "What must be proven onboard before a customer can safely move the operator ashore?", "sources": [ { "id": "WATCH19EX-NOV-AURA", "title": "Aura moves remote crane operations from concept to reality", "url": "https://www.nov.com/news/aura-moves-remote-crane-operations-from-concept-to-reality", "date": "2026-08-20", "publisher": "NOV", "locator": "Remote-access paragraph; Kristiansand/Søgne test; first delivery; two planned deliveries; phased customer adoption", "excerpt": "One fully remote-operated crane has already been delivered", "access": "Original supplier account read by editor 19 October 2026. Supplier demonstration and delivery are distinguished from customer operating use." } ], "disposition": "background", "category": "Remote and autonomous offshore operations", "relationship": "Supplementary context; no new adoption or numerical-result count.", "run": "19 October additional Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original supplier account read by editor 19 October 2026. Supplier demonstration and delivery are distinguished from customer operating use.", "asset": "Supplier Norway test; customer and vessel undisclosed.", "partner": "Undisclosed" }, { "id": "W19EX-OCEANEERING", "group_id": "W19EX-OCEANEERING", "company": "Oceaneering", "company_key": "Oceaneering", "department": "Geoscience & subsurface", "title": "One survey vessel brings several offshore jobs together", "kind": "context", "stage": "Supplier reports campaign started; completion unverified", "operating_period": "Announcement: 30 June 2026. About six months of work expected, including roughly four in Trinidad and two in the U.S. Gulf; not verified completed durations.", "display_period": "2026-06-30", "claim": "Oceaneering says an Ocean Intervention II survey campaign began in April 2026 for an unnamed international operator offshore Trinidad and the U.S. Gulf. The scope combines geophysical and geotechnical work with surface-vessel-supported autonomous underwater surveys. U.S. Gulf pipeline inspections include non-contact cathodic-protection measurement.", "economics": "The supplier says combining work on one vessel and crew can reduce mobilizations, exposure and emissions. No measured savings, baseline or net ROI disclosed.", "baseline": "No controlled operational or financial comparator disclosed.", "ai_role": "Autonomous survey operations; ML/LLM use not established.", "limits": "Autonomous survey is not proof of ML or LLM use. The vessel still has a crew. Operator identity, human supervision, intervention rules, achieved campaign length and comparative performance are undisclosed.", "decision_question": "Does combining survey tasks cut total vessel days once weather, rework and supervision are included?", "sources": [ { "id": "WATCH19EX-OCEANEERING", "title": "Oceaneering Secures Multi-Discipline Cross-Regional Offshore Survey Contracts for Ocean Intervention II", "url": "https://www.oceaneering.com/oceaneering-secures-multi-discipline-cross-regional-offshore-survey-contracts-for-ocean-intervention-ii/", "date": "2026-06-30", "publisher": "Oceaneering", "locator": "June 30 release: opening contract/program paragraphs; Trinidad/U.S. Gulf scope; simultaneous operations; supplier quotation; 2025 vessel upgrades", "excerpt": "The program commenced in April 2026", "access": "Original supplier release read by editor 19 October 2026. Begun campaign is distinguished from planned scopes, durations and unverified completion." } ], "disposition": "background", "category": "Remote and autonomous offshore operations", "relationship": "Supplementary context; no new adoption or numerical-result count.", "run": "19 October additional Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Original supplier release read by editor 19 October 2026. Begun campaign is distinguished from planned scopes, durations and unverified completion.", "asset": "Ocean Intervention II; offshore Trinidad and U.S. Gulf.", "partner": "Undisclosed" }, { "id": "W20AM-OILINDIA", "group_id": "W20AM-OILINDIA", "company": "Oil India", "company_key": "Oil India", "department": "IT, data & enterprise transformation", "title": "Oil India’s plan connects field operations with corporate systems", "kind": "context", "stage": "Programme being undertaken; project completion unverified", "operating_period": "Publication and DRIVE 2.0 start dates unknown. Header: “11/09/2026 09:35 AM”; footer: “20/10/2026 11:28 AM”. These update strings do not date deployment. The 2019 start belongs to earlier DRIVE.", "display_period": "Undated plan; checked 20 October 2026", "claim": "Oil India describes ten DRIVE 2.0 workstreams, including a control centre, a digital oilfield covering 380 producing wells, subsurface agents, maintenance and corporate workflows. The proposed systems would connect operating data with engineering and business records. Rig-planning approvals and safety notifications to designated people are described; AI decision authority and safeguards are not.", "economics": "The 380 wells are planned scope, not a verified connected population. No measured uplift, savings, implementation cost or net ROI.", "baseline": "No measured operational, financial or commissioning comparator disclosed.", "ai_role": "Proposed mix of AI/ML, GenAI/agents, sensors, software and workflow integration. No live deployment or autonomous authority established.", "limits": "One undated issuer plan, now accessible after an earlier blocked route. No completion dates, live user population or model providers established. Ten workstreams are not ten operating AI deployments. Publication and DRIVE 2.0 start dates unknown. Header: “11/09/2026 09:35 AM”; footer: “20/10/2026 11:28 AM”. These update strings do not date deployment. The 2019 start belongs to earlier DRIVE.", "decision_question": "Which parts have been commissioned, and who can approve or override their recommendations?", "sources": [ { "id": "WATCH20AM-OILINDIA", "title": "Digitalization in OIL — DRIVE 2.0 programme", "url": "https://www.oil-india.com/digitalfootprint", "date": "Undated", "publisher": "Oil India Limited", "locator": "Digitalization in OIL; DRIVE 2.0 §§1–10; §2 380-well scope; §4 approvals; §7 notifications; header and footer update strings", "excerpt": "10 digital initiatives are being taken up under Project DRIVE 2.0", "access": "Original issuer page read by editor 20 October 2026. Public /digitalfootprint path accessible; earlier /index.php/digitalfootprint attempt was blocked. Header and footer update strings are not verified publication or launch dates." } ], "disposition": "background", "category": "Enterprise and field transformation plan", "relationship": "One programme-context note; ten proposed components are not ten operating deployments.", "run": "20 October morning Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Original issuer page read by editor 20 October 2026. Public /digitalfootprint path accessible; earlier /index.php/digitalfootprint attempt was blocked. Header and footer update strings are not verified publication or launch dates.", "asset": "Pan-India upstream plan; 380-well proposed scope; OCS Makum, FGGS Madhuban and GCS Hebeda facility-twin scope.", "partner": "Technology/model partners unspecified; SAP S/4HANA and GeM are named integration systems.", "components": [ { "title": "Operations data", "department": "IT, data & enterprise transformation", "scope": "A shared control centre and OT data lake; corporate, field, pipeline and Rajasthan locations.", "locator": "DRIVE 2.0 §1", "stage": "Proposed scope; completion unverified" }, { "title": "Connected wells", "department": "Production & field operations", "scope": "Proposed sensors on 380 producing wells, remote monitoring/control, lift optimization, integrity models and virtual flow measurement.", "locator": "DRIVE 2.0 §2", "stage": "Proposed scope; completion unverified" }, { "title": "Subsurface assistants", "department": "Exploration & geoscience", "scope": "Proposed GenAI/agent tools linking subsurface and operating datasets for forecasts and drilling/workover recommendations.", "locator": "DRIVE 2.0 §3", "stage": "Proposed scope; completion unverified" }, { "title": "Drilling and rig logistics", "department": "Drilling & completions", "scope": "Rig scheduling, readiness/approval workflows and bit-selection support using operating and ERP data.", "locator": "DRIVE 2.0 §4(a)–(b)", "stage": "Proposed scope; completion unverified" }, { "title": "Surface-facility twins", "department": "Refining, LNG & process operations", "scope": "Planned models at OCS Makum, FGGS Madhuban and GCS Hebeda, with engineering records and historian/SAP links.", "locator": "DRIVE 2.0 §5", "stage": "Proposed scope; completion unverified" }, { "title": "Equipment maintenance", "department": "Maintenance & reliability", "scope": "An asset registry and lifecycle/maintenance workflows using SAP S/4HANA; proposed sensor-based failure warnings.", "locator": "DRIVE 2.0 §6", "stage": "Proposed scope; completion unverified" }, { "title": "Camera safety alerts", "department": "HSE & emissions", "scope": "Existing camera feeds and edge processing would flag PPE, access and other hazards for designated people.", "locator": "DRIVE 2.0 §7", "stage": "Proposed scope; completion unverified" }, { "title": "Project control", "department": "Finance, investment & strategy", "scope": "Forecasts of project dates, cost overruns and bottlenecks, with scenario views and audit trails.", "locator": "DRIVE 2.0 §8", "stage": "Proposed scope; completion unverified" }, { "title": "Purchasing", "department": "Supply chain & logistics", "scope": "Requisition-to-order automation, bid support and procurement analysis linked to SAP S/4HANA and GeM.", "locator": "DRIVE 2.0 §9", "stage": "Proposed scope; completion unverified" }, { "title": "Workforce tools", "department": "Workforce & learning", "scope": "A proposed HR system joining onboarding, workforce analytics/chatbot, access, time, benefits, training and contractors.", "locator": "DRIVE 2.0 §10", "stage": "Proposed scope; completion unverified" } ] }, { "id": "W20UP-KODIAK", "group_id": "W20UP-KODIAK", "company": "Atlas Energy Solutions", "company_key": "Atlas Energy Solutions", "department": "Supply chain & logistics", "title": "A driverless truck stayed available for 64 days", "kind": "context", "stage": "Operating industrial deployment; supplier-reported availability", "operating_period": "Announced October 20, 2026. The 64-day streak ran June 30–September 1. The fleet and paid-hours figures are as of June 30; 100 trucks by mid-2027 and a year-end highway launch remain plans.", "display_period": "2026-10-20", "claim": "Kodiak reports a 64-day uptime streak for one driverless truck in Atlas’s Permian Basin fleet, plus five trucks with streaks above 45 days. The truck and autonomy software stayed powered on and available for service. This is physical driving automation, not a language-model assistant. No one was in the cab; remote support and intervention boundaries are not quantified.", "economics": "As of June 30: 35 Atlas-owned and operated driverless trucks and over 40,000 cumulative paid driverless hours. These are supplier-reported fleet figures, not the uptime of every truck. No fleet availability rate, savings or net ROI.", "baseline": "No controlled financial or reliability comparator disclosed.", "ai_role": "Physical driving AI; no LLM identified. Unsupervised in-cab operation, remote support boundaries not quantified.", "limits": "Available does not mean continuously driving or hauling. No mileage, dispatch utilization, collision/exposure comparison or cost denominator disclosed. Kodiak AI is separate from Kodiak Gas Services (AI-193). Announced October 20, 2026. The 64-day streak ran June 30–September 1. The fleet and paid-hours figures are as of June 30; 100 trucks by mid-2027 and a year-end highway launch remain plans.", "decision_question": "How much paid hauling did those available hours produce, and what did remote support, maintenance and autonomy cost per load?", "sources": [ { "id": "WATCH20UP-KODIAK", "title": "Kodiak Driver Sets New Uptime Record By Running 64 Consecutive Days on an Unsupervised Driverless Truck", "url": "https://kodiak.ai/news/kodiak-driver-uptime-record", "date": "2026-10-20", "publisher": "Kodiak AI", "locator": "Opening uptime definition and dates; Atlas fleet as-of paragraph; future fleet and highway plans", "excerpt": "running and available for service", "access": "Full original supplier release retrieved (HTTP 200) and read. Supplier-reported availability and fleet figures; no independent reliability, safety or financial audit." } ], "disposition": "background", "category": "Industrial autonomous transport", "relationship": "Supplementary evidence; not a new main-register deployment or counted-result profile.", "run": "20 October requested research update", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Full original supplier release retrieved (HTTP 200) and read. Supplier-reported availability and fleet figures; no independent reliability, safety or financial audit.", "asset": "Atlas industrial trucking fleet, Permian Basin; 64-day single-truck streak; 35-truck fleet as of June30.", "partner": "Kodiak AI; Atlas owns and operates the trucks." }, { "id": "W20UP-SPE", "group_id": "W20UP-SPE", "company": "SPE / OnePetro", "company_key": "SPE / OnePetro", "department": "IT, data & enterprise transformation", "title": "Engineers may want the knowledge more than another AI product", "kind": "context", "stage": "Classification agreement announced; separate licensing lesson", "operating_period": "Classification release: October 20, 2026. JPT article: September 10 publication header, with an undated following-conference licensing update. Neither dates completed classification rollout.", "display_period": "2026-10-20", "claim": "SPE and i2k announced extended automated classification of OnePetro content. Separately, SPE says customers often wanted its technical content inside tools they already used. i2k describes metadata tagging using more than 20 domain knowledge bases. SPE’s original JPT account says EnRG-LLM remains licensable and identifies Halliburton Landmark as its first content-license customer in an undated follow-up paragraph.", "economics": "No measured retrieval accuracy, time saving, token saving, license revenue, usage population or net ROI. General claims about i2k’s geotechnical agents do not establish that SPE uses every advertised workflow.", "baseline": "No controlled financial or reliability comparator disclosed.", "ai_role": "Automated domain metadata classification and separately licensed technical content; not an operating oilfield agent.", "limits": "The complete issuer release was verified on syndication pages; the Business Wire original timed out. This is not an abandoned EnRG-LLM product. The two announcements do not prove that classification replaced the model. Classification release: October 20, 2026. JPT article: September 10 publication header, with an undated following-conference licensing update. Neither dates completed classification rollout.", "decision_question": "Our reading: make trusted content useful inside existing tools before assuming customers want another assistant. Ask about content rights, retrieval quality and cost per completed task.", "sources": [ { "id": "WATCH20UP-SPE", "title": "SPE extends i2k Connect information-classification collaboration", "url": "https://wrex.marketminute.com/article/bizwire-2026-10-20-society-of-petroleum-engineers-spe-partners-with-i2k-connect-for-information-classification", "date": "2026-10-20", "publisher": "i2k Connect / Business Wire; syndicated by MarketMinute", "locator": "Opening announcement; classification paragraph; SPE CEO statement", "excerpt": "The classification is fully automated", "access": "Complete issuer-authored Business Wire release read on an accessible syndication page. Distributor original timed out; identical release also retrieved from AOL. No independent outcome validation. Distributor URL: https://www.businesswire.com/news/home/20261020770911/en/", "original_url": "https://www.businesswire.com/news/home/20261020770911/en/" }, { "id": "WATCH20UP-SPE-JPT", "title": "Industry Executives Offer Practical Advice on How To Use Modern AI Models Wisely", "url": "https://jpt.spe.org/industry-executives-offer-practical-advice-on-how-to-use-modern-ai-models-wisely", "date": "2026-09-10", "publisher": "Society of Petroleum Engineers / JPT", "locator": "SPE’s AI Journey; licensing-demand discussion; following-conference Landmark paragraph; cost and metadata discussion", "excerpt": "EnRG-LLM remains available for licensing", "access": "Full original publisher article retrieved and read 20 October. September 10 publication header; later following-conference paragraph is undated. Direct current text takes precedence over stale search extracts." } ], "disposition": "background", "category": "Technical knowledge and licensing", "relationship": "Supplementary evidence; not a new main-register deployment or counted-result profile.", "run": "20 October requested research update", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Complete issuer-authored Business Wire release read on an accessible syndication page. Distributor original timed out; identical release also retrieved from AOL. No independent outcome validation. Distributor URL: https://www.businesswire.com/news/home/20261020770911/en/", "asset": "OnePetro technical library; classification population and completed rollout unknown.", "partner": "i2k Connect; SPE; Halliburton Landmark named in a separate undated licensing follow-up." }, { "id": "W20UP-BP", "group_id": "W20UP-BP", "company": "bp", "company_key": "bp", "department": "Drilling & completions", "title": "Bumerangue’s appraisal contract includes drilling automation", "kind": "context", "stage": "Contract awarded; LOGIX deployment planned", "operating_period": "Original announcement August 25, 2026; checked October 20. This is older evidence newly added to this review, not a launch announced today.", "display_period": "2026-08-25", "claim": "Halliburton’s August contract for bp’s Bumerangue appraisal campaign includes LOGIX automation and remote operations offshore Brazil. The integrated drilling and evaluation scope connects planning, execution and evaluation. The release says LOGIX will be deployed; it does not identify an LLM, individual control permissions or human override arrangements.", "economics": "No number of wells, completed automated wells, operating comparator, quantified benefit, contract value or net ROI disclosed.", "baseline": "No controlled financial or reliability comparator disclosed.", "ai_role": "Planned LOGIX automation and remote operations; specific ML/LLM method and control boundaries undisclosed.", "limits": "A contract is not proof of completed field use. Do not transfer LOGIX results from Eni’s Indonesia well or another customer to Bumerangue. Recorded as a named-operator extension of existing LOGIX coverage, not a second platform. Original announcement August 25, 2026; checked October 20. This is older evidence newly added to this review, not a launch announced today.", "decision_question": "Which drilling tasks will run automatically, who can intervene, and how will bp compare outcomes with a credible baseline?", "sources": [ { "id": "WATCH20UP-BP", "title": "bp awards Halliburton integrated contract for Bumerangue field appraisal in Brazil", "url": "https://www.halliburton.com/en/about-us/press-release/bp-awards-halliburton-integrated-contract-for-bumerangue-field-appraisal-in-brazil", "date": "2026-08-25", "publisher": "Halliburton", "locator": "Opening and contract-scope paragraphs; LOGIX sentence", "excerpt": "LOGIX™ automation and remote operations will be deployed", "access": "Full original supplier release retrieved (HTTP 200) and read. Future-tense scope; no completion or measured result established." } ], "disposition": "background", "category": "Planned drilling automation", "relationship": "Supplementary evidence; not a new main-register deployment or counted-result profile.", "run": "20 October requested research update", "ai_ids": [ "AI-016" ], "core_company": true, "context_only": true, "evidence": "Full original supplier release retrieved (HTTP 200) and read. Future-tense scope; no completion or measured result established.", "asset": "Bumerangue appraisal campaign, offshore deepwater Brazil; well count undisclosed.", "partner": "Halliburton; bp." }, { "id": "W20PM-USEDC", "group_id": "W20PM-USEDC", "company": "U.S. Energy Development Corporation", "company_key": "U.S. Energy Development Corporation", "department": "Production & field operations", "title": "Twelve wells moved from recommendations to automatic adjustments", "kind": "context", "stage": "Operating field deployment; operator/vendor-reported results", "operating_period": "Started December 2025. July 2026 article; exact publication day unknown. Six-month results, not a year or the operator’s full fleet. This older case was missed in earlier research.", "display_period": "2026-07", "claim": "U.S. Energy and ROAM-AI describe automatic ESP adjustments on 12 Permian wells. Engineers define the operating limits and handle exceptions. Physics-aware models use live data to adjust setpoints within approved frequency, pressure, temperature and pump-curve limits. The authors say thousands of adjustments were executed automatically. No LLM is identified; exact override and shutdown procedures are undisclosed.", "economics": "The authors report 12.2% higher production against a 90-day pre-activation baseline, and a return exceeding four times initial cost within six months. Full costs and return definitions are absent; this is not verified net ROI. Six months was too early for a definitive pump-failure interval conclusion.", "baseline": "90-day pre-activation baseline; no matched controls disclosed.", "ai_role": "Physics-aware models with bounded automatic ESP setpoint changes; engineers handle exceptions. No LLM identified.", "limits": "Operator/vendor coauthored. No controlled comparator or disclosed adjustment for decline, workovers or other changes. Do not import the article’s separate unnamed 250-plus-well operator results into this 12-well case.", "decision_question": "Ask for the all-in cost and benefit bridge, the baseline calculation and the log of exceptions, overrides and rejected adjustments.", "sources": [ { "id": "WATCH20PM-USEDC", "title": "The Bottleneck Isn’t the Model. It’s the Execution.", "url": "https://www.aogr.com/magazine/cover-story/the-bottleneck-isnt-the-model-its-the-execution", "date": "2026-07", "publisher": "The American Oil & Gas Reporter; ROAM-AI and U.S. Energy Development Corp. coauthors", "locator": "July 2026 cover story; A New Optimization Philosophy; Eric’s Inside View; author biographies", "excerpt": "We activated the system across 12 Permian wells beginning in December 2025.", "access": "Full original publisher article retrieved (HTTP200) and read by editor. Operator/vendor coauthored, not independently validated. Month precision only; vendor’s July20 promotion is not the article’s exact publication date." } ], "disposition": "background", "category": "Named operating ESP cohort", "relationship": "Same case as AI-296; not another deployment.", "run": "20 October evening Luna watch", "ai_ids": [ "AI-296" ], "core_company": true, "context_only": true, "evidence": "Full original publisher article retrieved (HTTP200) and read by editor. Operator/vendor coauthored, not independently validated. Month precision only; vendor’s July20 promotion is not the article’s exact publication date.", "asset": "12 Permian Basin wells.", "partner": "ROAM-AI" }, { "id": "W20PM-CADE", "group_id": "W20PM-CADE", "company": "Ecopetrol", "company_key": "Ecopetrol", "department": "IT, data & enterprise transformation", "title": "Rubiales adds a dated operating footprint to CADE", "kind": "context", "stage": "CADE operating coverage; specific AI-model commissioning unverified", "operating_period": "Issuer announcement May 4, 2026; Rubiales coverage reported from March 2026. Older evidence newly checked, not a new October launch.", "display_period": "2026-05-04", "claim": "Ecopetrol says its ISA-built energy decision platform managed 173 MW at Rubiales from March 2026, across five generation centres and the national grid. CADE supports choices of electricity source, timing and volume. Sixty workers were trained; that is not a user-adoption count. The earlier report describes a Rubiales dispatch-model MVP being built in 2025; the newer platform coverage does not independently confirm that model’s commissioning or AI control authority.", "economics": "The company describes the covered supply as 20% of group demand. Another 931 MW and 80% coverage are plans, not achieved scope. MW is operating power coverage, not energy saved, emissions avoided or ROI.", "baseline": "Power-management footprint, not a measured AI benefit baseline.", "ai_role": "Platform with analytics; specific dispatch-model commissioning and autonomous AI control remain unverified.", "limits": "No measured saving, implementation cost, LLM/model detail or human approval/override rule. The name “autonomous” and platform capacity do not establish autonomous AI dispatch. Group-wide generating capacity is a different population.", "decision_question": "Which decisions are actually automated, and what changes in delivered electricity cost after all platform and operating costs?", "sources": [ { "id": "WATCH20PM-CADE", "title": "Grupo Ecopetrol inaugura centro para optimizar su gestión energética", "url": "https://www.ecopetrol.com.co/wps/portal/Home/es/noticias/detalle/grupo-ecopetrol-inaugura-centro-para-optimizar-su-gestion-energetica", "date": "2026-05-04", "publisher": "Ecopetrol", "locator": "May 4 heading and Bogotá dateline; Rubiales operating coverage, ISA partnership, projected expansion and training paragraphs", "excerpt": "En el campo Rubiales, desde marzo de 2026, se gestionan 173 MW de energía", "access": "Full original operator page retrieved (HTTP200) and read by editor. Coverage and plans remain company-reported; no independent cost or performance validation." } ], "disposition": "background", "category": "Energy-management platform coverage", "relationship": "Existing AI-148; capacity coverage is not an AI outcome.", "run": "20 October evening Luna watch", "ai_ids": [ "AI-148" ], "core_company": true, "context_only": true, "evidence": "Full original operator page retrieved (HTTP200) and read by editor. Coverage and plans remain company-reported; no independent cost or performance validation.", "asset": "Rubiales field; five generation centres and national grid.", "partner": "ISA" }, { "id": "W21AM-PTTEP", "group_id": "W21AM-PTTEP", "company": "PTTEP", "company_key": "PTTEP", "department": "IT, data & enterprise transformation", "title": "PTTEP describes an in-house engine for specialist agents", "kind": "context", "stage": "Engine launch described; eight-agent rollout unverified", "operating_period": "Published 3 November 2025. Launch date, operating population and subsequent rollout status unknown. Missed historical evidence, not a new October 2026 announcement.", "display_period": "2025-11-03", "claim": "PTTEP says it launched X.brain, an internal AI engine grounded in its own operating knowledge and data. The November 2025 feature describes support for analysis and recommendations. Eight specialist agents across subsurface, drilling, production, supply chain and corporate work were planned; the article does not establish that all eight went live.", "economics": "No X.brain user count, adoption rate or measured return is disclosed. The same article separately reports LogSight interpretation falling from two days to one hour and DORA drilling savings described only as “millions of US dollars annually”. Those are product-specific claims, not demonstrated X.brain results.", "baseline": "Separate product claims; no engine-level benefit baseline.", "ai_role": "In-house AI engine and planned specialist agents; runtime and model provider unknown.", "limits": "No proof of comprehensive communications capture, decision-outcome memory or autonomous executive authority. DORA combines machine learning and physics-based simulation; it is not shown to run on X.brain. No asset scope, test population or full costs support the DORA/LogSight comparisons.", "decision_question": "Ask which agents people actually use, what data they can reach and which decisions still need a named human approver.", "sources": [ { "id": "WATCH21AM-PTTEP", "title": "PTTEP’s AI Vision for a Smarter, Sustainable Future of Energy", "url": "https://www.pttep.com/th/newsroom/special-features/1107/pttep-s-ai-vision-for-a-smarter-sustainable-future-of-energy", "date": "2025-11-03", "publisher": "PTTEP", "locator": "Page date; X.brain introduction; eight-agent plan; DORA and LogSight examples", "excerpt": "PTTEP has launched its in-house Enterprise AI Engine, “X.brain,”", "access": "Full original operator page read by editor; Thai date 3 November 2568 converts to 2025-11-03. Company claims, not independent validation." } ], "disposition": "background", "category": "Enterprise engine launch", "relationship": "Same case as AI-297; no additional deployment count.", "run": "21 October morning Luna watch", "ai_ids": [ "AI-297", "AI-067", "AI-245" ], "core_company": true, "context_only": true, "evidence": "Full original operator page read by editor; Thai date 3 November 2568 converts to 2025-11-03. Company claims, not independent validation.", "asset": "Company-wide intended domains; asset/user population unknown.", "partner": "Not disclosed", "components": [ { "title": "DORA: anticipate stuck pipe", "department": "Drilling & completions", "scope": "Drilling Operation Real-Time Analyses combines machine learning with physics-based simulations to predict stuck-pipe risk and support parameter adjustments. The issuer claims annual savings of millions of US dollars, without an exact figure, well population, comparator or full costs. Automatic control and human approval rules are not disclosed.", "locator": "PTTEP feature: DORA example", "stage": "Operating use implied by issuer; rollout and evaluation population unknown" }, { "title": "LogSight: interpret well logs", "department": "Reservoir engineering & field development", "scope": "AI supports petrophysical log interpretation. PTTEP reports a reduction from two days to one hour, without sample size, quality comparison, calendar period, human sign-off rule or full costs.", "locator": "PTTEP feature: LogSight example", "stage": "Reported issuer comparison; deployment population unknown" } ], "components_label": "Read the two operating examples separately", "components_note": "The same feature describes these tools. It does not establish that either runs on X.brain, or that their reported benefits came from the engine." }, { "id": "W21AM-MNVR", "group_id": "W21AM-MNVR", "company": "Energy Solutions / MNVR AI", "company_key": "Energy Solutions / MNVR AI", "department": "Maintenance & reliability", "title": "Five diagnosed equipment faults, with people confirming the fixes", "kind": "context", "stage": "Vendor/partner-reported operating case; adjacent gas-to-power site", "operating_period": "Publication date unknown; checked 21 October 2026. Six-week calendar window unknown. PDF filename is not a verified date. Adjacent gas-to-power operations, not an upstream adoption count.", "display_period": "Unknown", "claim": "An undated MNVR and Energy Solutions case describes ODIE supporting seven gas generators at the Muskrat microgrid in North Dakota’s Bakken Basin. Across six weeks, three cases came from agent alerts and two from operator questions. The authors say all five diagnoses were confirmed on inspection. Confirmed diagnoses and operator corrections are retained for future use. The product page keeps decisions with operators; automatic equipment control is not established.", "economics": "The authors jointly estimate $37,015 in avoided costs across the five selected faults. These are counterfactual estimates, not measured cash savings or net ROI. A $25,500 relay case includes the hypothesized cost of replacing the wrong controller; do not add that controller’s price again.", "baseline": "Five selected faults over six weeks; hypothetical avoided costs, not a controlled outcome.", "ai_role": "Agent fault detection and diagnostic questions, with operator confirmation and retained corrections.", "limits": "Selected equipment faults are not failed AI deployments. No total alert population, missed-fault count, false-positive rate, control group or full system cost. Some repairs were scheduled or could be planned; not all five were completed. Roughly 5,200 signals means data signals, not assets.", "decision_question": "Can the team show every alert, inspection and resulting work order—including alerts that turned out to be wrong?", "sources": [ { "id": "WATCH21AM-MNVR-CASE", "title": "Five Failures Across Five Systems", "url": "https://www.mnvrai.ai/s/MNVR-Customer-Story-Energy-Solutions-5-Examples-09222026.pdf", "date": "Unknown", "publisher": "MNVR AI / Energy Solutions", "locator": "PDF pp. 1–3: seven generators; five fault cases; estimated costs; six-week period and retained diagnoses", "excerpt": "Over six weeks, ODIE identified five separate developing failures", "access": "Original three-page vendor/partner PDF retrieved HTTP200, full text read and pages 1–2 visually inspected. No publication date; filename is not date evidence." }, { "id": "WATCH21AM-MNVR-PRODUCT", "title": "ODIE — Operations Diagnostic Intelligence Engine", "url": "https://www.mnvrai.ai/odie", "date": "Unknown", "publisher": "MNVR AI", "locator": "Human in the loop / operators make decisions section", "excerpt": "ODIE informs decisions. Operators make them.", "access": "Original product page retrieved HTTP200 and read by editor. Undated product description; not a field performance validation." } ], "disposition": "background", "category": "Adjacent gas-to-power diagnosis", "relationship": "Adjacent operating context only; excluded from upstream adoption and ROI counts.", "run": "21 October morning Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Original three-page vendor/partner PDF retrieved HTTP200, full text read and pages 1–2 visually inspected. No publication date; filename is not date evidence.", "asset": "Muskrat microgrid, Bakken Basin, North Dakota; seven CAT XGC1900 generators.", "partner": "MNVR AI; Energy Solutions maintenance partner", "components": [ { "title": "Control relay", "department": "Maintenance & reliability", "scope": "A gas-pressure trip left a generator motoring and drawing grid power for over nine hours. The authors say ODIE identified a relay rather than the initially suspected $18,000 controller. One hour of labor and a $100 relay are described; $25,500 estimated avoidance already includes the hypothesized wrong-controller path.", "locator": "Customer PDF p. 1, case 1", "stage": "Relay correction described" }, { "title": "Ignition transformer", "department": "Maintenance & reliability", "scope": "An agent flagged degradation; operators confirmed it and replaced the transformer during scheduled maintenance. Estimated cost avoided: $4,641, without a measured counterfactual.", "locator": "Customer PDF p. 1, case 2", "stage": "Replacement described" }, { "title": "Valve recession / detonation", "department": "Maintenance & reliability", "scope": "An alert prompted operator inspection. A head replacement could then be planned. Estimated avoidance: $4,000; the account does not confirm the planned replacement was completed.", "locator": "Customer PDF p. 2, case 3", "stage": "Inspection confirmed; replacement could be planned" }, { "title": "Silent NOx sensor", "department": "HSE & emissions", "scope": "A sensor fault reportedly absent from traditional monitoring was identified. Replacement was proposed for the next convenient opportunity. Estimated avoidance: $1,000; completion is unverified.", "locator": "Customer PDF p. 2, case 4", "stage": "Diagnosis described; replacement pending/unverified" }, { "title": "Fouling gas filter", "department": "Maintenance & reliability", "scope": "The team checked and confirmed a restriction and changed the filter during scheduled maintenance. Estimated avoidance: $1,874, based on the authors’ hypothetical failure progression.", "locator": "Customer PDF p. 2, case 5", "stage": "Scheduled replacement described" } ], "components_label": "Read the five equipment faults", "components_note": "These selected equipment faults illustrate diagnosis and maintenance follow-through. They are not failures of the AI system, and the estimated avoided costs are not measured cash savings." }, { "id": "W21AM-QUANTUM", "group_id": "W21AM-QUANTUM", "company": "Quantum Capital Group", "company_key": "Quantum Capital Group", "department": "Reservoir engineering & field development", "title": "Quantum’s planning gain includes a separate algorithm improvement", "kind": "context", "stage": "Existing operating planning workflow; reported updated-version comparison", "operating_period": "Microsoft story dated 30 April 2026; later operator identification remains QB Energy from Quantum’s 2026 report. This is an enrichment of AI-054, not a new deployment.", "display_period": "2026-04-30", "claim": "Microsoft says algorithm changes in an updated version of Quantum’s field-planning tool reduced solve time by 50–65%. The integer-linear-programming optimizer selects feasible pads and wells. A Copilot Studio agent explains outputs. The numerical improvement belongs to the optimization algorithm; the source does not attribute it to the language model.", "economics": "50–65% shorter solve times in an updated version, said to compound over hundreds of runs. The source does not specify absolute times, comparable hardware or the evaluation period. Do not multiply this with the separate three-weeks-to-20-minutes comparison.", "baseline": "Updated solver version; no absolute time or hardware baseline.", "ai_role": "ILP optimizer plus a separate explanatory language-model interface.", "limits": "Vendor/customer reporting with no full-cost return or independent performance validation. The version comparison is a different baseline from the manual-workflow comparison. Engineers retain plan review; no capital approval is delegated. The reported solver improvement is not attributed to the language model.", "decision_question": "Separate the solver, data preparation and assistant when testing which change actually improves the planning decision.", "sources": [ { "id": "OCT5-S032", "title": "Field development planning at Quantum Capital Group", "url": "https://www.microsoft.com/en/customers/story/26476-quantum-capital-group-azure-app-service", "date": "2026-04-30", "publisher": "Microsoft", "locator": "Field development planning solution; Improved speed, scale, and precision; updated algorithm paragraph", "excerpt": "algorithmic improvements have reduced solve times by 50 to 65%", "access": "Full original Microsoft customer story read again on 21 October. Updated-version comparison is vendor-reported; no independent validation." } ], "disposition": "background", "category": "Updated optimization algorithm", "relationship": "Same case as AI-054; no additional deployment count.", "run": "21 October morning Luna watch", "ai_ids": [ "AI-054" ], "core_company": true, "context_only": true, "evidence": "Full original Microsoft customer story read again on 21 October. Updated-version comparison is vendor-reported; no independent validation.", "asset": "Piceance Basin planning; existing QB Energy case.", "partner": "Microsoft; QB Energy operator identified by Quantum" }, { "id": "W21EX-DEVON", "group_id": "W21EX-DEVON", "company": "Devon Energy", "company_key": "Devon Energy", "department": "IT, data & enterprise transformation", "title": "Devon confirms ChatDVN is part of daily work", "kind": "context", "stage": "Operating internal workflow; issuer-described daily use", "operating_period": "Call dated 6 May 2026; CEO describes three years of operation, an approximate history rather than an exact start day. This is newly linked original evidence, not a new launch.", "display_period": "2026-05-06", "claim": "Devon’s CEO says its firewalled ChatDVN tool was a standard part of daily work by May 2026, after years spent organizing internal data. The call distinguishes access to company data, AI-assisted coding and interpretation of operating data, and a next phase of process redesign. It does not establish that every example runs inside ChatDVN. Separate autonomous lift controls remain in AI-006.", "economics": "No active-user count, task-quality comparison, ChatDVN-specific cash benefit or full cost is disclosed. The call does not corroborate the older interview’s 15–30% productivity claim or AI-101 training count. Devon’s $1bn business-optimization target is not ChatDVN savings.", "baseline": "No matched tool-level quality, operating or financial comparator disclosed.", "ai_role": "Internal AI assistant and company-data access; coding and operations-data examples described separately. No external model provider disclosed.", "limits": "Daily use supports an operating workflow, not verified enterprise-wide active adoption. No comprehensive communications capture, decision-outcome memory, execution permissions or AI executive authority is established. Training and productivity claims from the earlier trade interview retain their separate, unverified status.", "decision_question": "Which jobs do employees finish through ChatDVN, and does the full review process improve time, accuracy and follow-through?", "sources": [ { "id": "FU001", "title": "Devon Q1 2026 earnings call — internal ChatDVN workflow", "url": "https://s2.q4cdn.com/462548525/files/doc_financials/quarterly/2026/q1/Q1-2026-DVN-Q-A-Webcast-Commentary-Transcript.pdf", "date": "2026-05-06", "publisher": "Devon Energy / FactSet CallStreet", "locator": "PDF and printed p. 4; Clay Gaspar prepared remarks, three waves of AI", "excerpt": "a fully-firewalled internal tool called ChatDVN", "access": "Issuer-hosted corrected 20-page transcript retrieved HTTP200. Editor read relevant p.4 and visually inspected it; management claims, not independent performance validation." } ], "disposition": "background", "category": "Internal AI workflow", "relationship": "Same AI-086 operating workflow; no new profile or result credit.", "run": "21 October additional Luna watch", "ai_ids": [ "AI-086" ], "core_company": true, "context_only": true, "evidence": "Issuer-hosted corrected 20-page transcript retrieved HTTP200. Editor read relevant p.4 and visually inspected it; management claims, not independent performance validation.", "asset": "Internal company-data workflow; user and asset populations undisclosed.", "partner": "Not disclosed" }, { "id": "W21EX-SLB", "group_id": "W21EX-SLB", "company": "SLB", "company_key": "SLB", "department": "Drilling & completions", "title": "Automated cementing has moved beyond its first job", "kind": "context", "stage": "Supplier reports commercial operating deployments", "operating_period": "Issuer release 24 July 2026; first-quarter 2026 commercialization described. Individual job dates and the remote/automated split are undisclosed.", "display_period": "2026-07-24", "claim": "SLB says its cementing technology had passed 100 remote and automated jobs by July 2026, following first-quarter commercialization. The release also names an automated dual-slurry operation on Shell’s Velox-1 in Egypt. The 100-plus figure combines remote and automated jobs; it is not 100 fully autonomous wells or a Shell-only fleet count.", "economics": "Job count shows reported operating reach. The release gives no controlled cycle-time, cement-quality, safety or cash-return comparison for this cohort.", "baseline": "No matched tool-level quality, operating or financial comparator disclosed.", "ai_role": "Cementing automation and remote operation; AI/ML/LLM attribution unestablished.", "limits": "Automation and remote operation do not establish machine learning or LLM use. Human supervision, control envelopes, fallback and override rules are not specified. The same release’s AI Production Studio is a pre-field demonstration environment, not proof that those capabilities ran on Shell’s well.", "decision_question": "Which steps execute automatically, what still needs the crew, and how does job quality compare under similar well conditions?", "sources": [ { "id": "WATCH21EX-SLB", "title": "SLB Announces Second-Quarter 2026 Results", "url": "https://investorcenter.slb.com/news-releases/news-release-details/slb-announces-second-quarter-2026-results", "date": "2026-07-24", "publisher": "SLB", "locator": "Core / Technology Highlights; automated cementing paragraph and Shell Velox-1 follow-up", "excerpt": "surpassed 100 remote and automated cementing jobs", "access": "Original issuer release opened and relevant technology-highlight paragraphs read by editor. Remote and automated categories are not broken out; no AI method specified." } ], "disposition": "background", "category": "Operating automation and modeling", "relationship": "Supplemental operating context; not an AI adoption or numerical-result addition.", "run": "21 October additional Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original issuer release opened and relevant technology-highlight paragraphs read by editor. Remote and automated categories are not broken out; no AI method specified.", "asset": "Reported global 100-plus combined-job cohort; named dual-slurry case at Shell Velox-1, Egypt.", "partner": "Shell named for Velox-1, not the entire cohort" }, { "id": "W21EX-IAM", "group_id": "W21EX-IAM", "company": "PETRONAS", "company_key": "PETRONAS", "department": "Production & field operations", "title": "Eight fields use physics-based asset modeling", "kind": "context", "stage": "Issuer reports deployed workflow during 2025", "operating_period": "Operating period 2025. Source register dates the 2025 integrated report 27 February 2026; exact posting day was not re-audited. Printed p.55 / PDF p.29 newly inspected.", "display_period": "2026-02-27", "claim": "PETRONAS reports Integrated Asset Management across eight fields, combining physics-based models with near-real-time data for surveillance and production optimization. The report says the workflow helps teams identify production opportunities faster. Its own passage does not attribute AI to IAM. Nearby PROTEAN and ERMAI AI descriptions concern different systems.", "economics": "The issuer says IAM improved production efficiency and value realization in 2025, without giving an amount, baseline, comparison group, attribution method or full costs. Eight is a field count, not eight models or platforms.", "baseline": "No matched tool-level quality, operating or financial comparator disclosed.", "ai_role": "Physics-based models and near-real-time data; this passage does not establish AI use.", "limits": "No field names, user population, human approval or automatic control permissions are disclosed. The chapter’s broad AI heading cannot establish IAM’s method. Do not transfer PROTEAN’s equipment footprint or ERMAI’s time comparison to IAM.", "decision_question": "What production decisions changed, and what incremental result can be separated from other field improvements?", "sources": [ { "id": "RS017", "title": "PETRONAS Integrated Report 2025 — IAM", "url": "https://www.petronas.com/sites/default/files/uploads/PIR%202025/PETRONAS%20Integrated%20Report%202025.pdf", "date": "2026-02-27", "publisher": "PETRONAS", "locator": "PDF p.29 / printed p.55; Turning Data into Production Upside", "excerpt": "IAM has been deployed across eight fields", "access": "Original 10,849,024-byte PDF retrieved HTTP200; editor extracted and visually inspected spread54–55 (PDF29). Publication day retained from existing source register; exact posting day not re-audited in this pass." } ], "disposition": "background", "category": "Operating automation and modeling", "relationship": "Supplemental operating context; not an AI adoption or numerical-result addition.", "run": "21 October additional Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original 10,849,024-byte PDF retrieved HTTP200; editor extracted and visually inspected spread54–55 (PDF29). Publication day retained from existing source register; exact posting day not re-audited in this pass.", "asset": "Eight unnamed fields; country/basin, well and equipment populations undisclosed.", "partner": "Not disclosed" }, { "id": "W21PM-SHELL", "group_id": "W21PM-SHELL", "company": "Shell", "company_key": "Shell", "department": "Maintenance & reliability", "title": "Shell’s pump analysis stalled until an operator joined the team", "kind": "negative_evidence", "stage": "Retrospective precursor analysis; operational deployment unknown", "operating_period": "Undated webpage and video; operating and evaluation dates unknown. Already mentioned in the coverage log, now structured as a readable case. It is not a new 2026 deployment.", "display_period": "Unknown", "claim": "Shell describes an initially unsuccessful search for pump-disruption precursors at Perdido. A field operator helped the data team refine its code and find a chemical signature. The team first drew a blank, later plateaued and considered stopping. The operator supplied equipment knowledge. Shell then reports a signature before 70% of disruptions, with one example about two days beforehand.", "economics": "The 70% is a reported precursor association in the analyzed events, not demonstrated live prediction accuracy. Event count, false alarms, held-out validation, intervention results, uptime benefit and full costs are undisclosed.", "baseline": "Stored-event precursor analysis; no prospective accuracy or false-alert denominator.", "ai_role": "AI-assisted analysis of stored pump data, refined with operator expertise; no LLM or live control established.", "limits": "The transcript does not establish a live alert or control workflow, prevented disruptions or realized savings. The two-day example is not an average warning time. Initial stalled analysis is not proof of an abandoned or failed field deployment.", "decision_question": "Could the team reproduce the result on later events, with all false alerts recorded, and show what operators changed because of it?", "sources": [ { "id": "WATCH21PM-SHELL", "title": "The Data Detectives — Solving the 10-year-old problem at Perdido", "url": "https://www.shell.com/what-we-do/digitalisation/artificial-intelligence.html", "date": "Unknown", "publisher": "Shell", "locator": "Artificial intelligence examples / Perdido video transcript; initial blank, plateau, operator input and refined precursor signature", "excerpt": "the refined algorithm identifies the chemical fingerprint ahead of 70 percent of pump disruptions", "access": "Original operator webpage and relevant video transcript read by editor. Page/video publication and operating dates are not established; historical or undated context only." } ], "disposition": "background", "category": "Model-development limits", "relationship": "Undated supplementary case; no new live deployment or reported-result count.", "run": "21 October evening Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original operator webpage and relevant video transcript read by editor. Page/video publication and operating dates are not established; historical or undated context only.", "asset": "Perdido subsea pumps, Gulf of Mexico; pump/event population undisclosed.", "partner": "Not disclosed" }, { "id": "W21PM-DBX", "group_id": "W21PM-DBX", "company": "Quantum Capital Group", "company_key": "Quantum Capital Group", "department": "Finance, investment & strategy", "title": "Quantum adds a relational layer to its deal-evaluation data", "kind": "context", "stage": "Vendor describes an adopted sponsor-level data layer", "operating_period": "Undated source; adoption and evaluation periods unknown. Extends existing sponsor platform AI-052, separately from QB Energy’s field-planning workflow AI-054.", "display_period": "Unknown", "claim": "Databricks describes Quantum using Lakebase, Unity Catalog and Lakeflow to give deal teams a shared, governed view of geological, production and financial data. A Postgres interface and PostGIS geospatial support connect familiar tools, including Tableau and Spotfire. Schemas, stored procedures, triggers and access controls help teams use consistent datasets. This is data infrastructure; the story does not establish an AI decision-maker.", "economics": "Vendor/customer-reported scale: 1.5 billion records across six vendor feeds and proprietary data, over 100 redundant tables removed, and over 11,000 monthly queries across a 150-person firm. Queries are not active users, completed deals or investment returns.", "baseline": "No time, quality, financial or investment-return comparator disclosed.", "ai_role": "Relational and governed data foundation; no AI model or autonomous investment authority established by this source.", "limits": "No named asset, portfolio-operator rollout, task-time or accuracy baseline, investment-approval rule, full cost or measured return. The story’s investment-performance language is not evidence of investment alpha or AI attribution.", "decision_question": "Can the team trace a deal assumption to its source and show whether shared data reduces reconciliation and review work?", "sources": [ { "id": "WATCH21PM-DBX", "title": "Transforming energy deal evaluation with Lakebase", "url": "https://www.databricks.com/customers/quantum-capital-group", "date": "Unknown", "publisher": "Databricks", "locator": "Building a consistent foundation; Lakebase relational capabilities; adoption and FAQ paragraphs", "excerpt": "The firm now runs over 11,000 unique data queries per month", "access": "Full original vendor customer story read by editor. No publication date shown; search age and footer year are not rollout dates. Vendor/customer claims, not independent validation." } ], "disposition": "background", "category": "Sponsor data infrastructure", "relationship": "Existing AI-052 foundation; not a separate portfolio-operator AI deployment.", "run": "21 October evening Luna watch", "ai_ids": [ "AI-052" ], "core_company": true, "context_only": true, "evidence": "Full original vendor customer story read by editor. No publication date shown; search age and footer year are not rollout dates. Vendor/customer claims, not independent validation.", "asset": "Quantum sponsor-level energy deal evaluation; asset and portfolio-company populations undisclosed.", "partner": "Databricks" }, { "id": "W22AM-FAST", "group_id": "W22AM-FAST", "company": "TC Energy", "company_key": "TC Energy", "department": "Maintenance & reliability", "title": "TC Energy puts people between equipment alerts and field action", "kind": "context", "stage": "Existing advisory process; FAST release completion unverified", "operating_period": "Undated AVEVA World 2026 presentation, internally dated 29 May. Page 16 schedules Canada for Q3 2026 and US/Mexico for Q4; page 23 describes a first release in under seven months. The 16 October opinion does not resolve completion.", "display_period": "Unknown", "claim": "TC Energy describes an equipment-surveillance process built around specialists and field teams. FAST is its consolidation plan with Accenture and AVEVA, separate from Pipeline IQ and compressor-dispatch optimization. Alerts pass through triage, specialist investigation, corrective action and documentation. The proposed platform joins existing tools, AVEVA and AWS. SageMaker model development is marked development-only; language assistants and deeper SAP coordination sit under future work.", "economics": "The presentation credits existing surveillance with over $100m/year in avoided failure costs. FAST’s additional $250m over ten years is a forecast. Neither is measured LLM value or all-in net ROI.", "baseline": "Avoided-cost methodology, currency and comparison period undisclosed; forecast is separate.", "ai_role": "Future AI triage, language assistance and workflow coordination are proposals; operating model-by-model AI scope is undisclosed.", "limits": "The deck’s release wording is inconsistent; scheduled quarters do not prove go-live. Benefits lack a disclosed counterfactual, cost schedule, currency designation and measurement period. Do not add the forecast to the annual claim or assign either to FAST’s future AI features.", "decision_question": "What reached production, who acts on an alert, and what remains after false alarms, specialist time and deployment costs?", "sources": [ { "id": "WATCH22AM-FAST", "title": "Practical AI in Action: TC Energy’s Path to a Unified, Scalable Asset Reliability Platform", "url": "https://cdn.mediavalet.com/eunl/content/W8TklEW5w0msg_eHg0KrTA/gz5XgM6QhE6XBVDXhH9-pA/Original/Practical%20AI%20in%20Action%3A%20TC%20Energy%27s%20Path%20to%20a%20Unified%2C%20Scalable%20Asset%20Reliability%20Platform.pdf", "date": "Unknown", "publisher": "TC Energy and Accenture / AVEVA World 2026", "locator": "PDF pp.14–16: advisory workflow, upcoming FAST and release roadmap; p.17: architecture; p.20: forecast; p.22: future AI work; p.23: release wording", "excerpt": "FAST is TC Energy’s upcoming Facility Asset Surveillance Technology", "access": "Original 27-page presentation downloaded and read by editor; pp.14,16,22 visually inspected. Deck internally dated 29 May 2026; exact publication date unknown." }, { "id": "WATCH22AM-AVEVA", "title": "How the oil and gas industry is putting data first", "url": "https://www.aveva.com/en/our-industrial-life/type/opinion/how-the-oil-and-gas-industry-is-putting-data-first/", "date": "2026-10-16", "publisher": "AVEVA / Cindy Crow", "locator": "Posted date; Improved reliability through AI monitoring section", "excerpt": "the company saved $100 million of value in failure avoidance per year", "access": "Original vendor opinion read by editor. Named-customer program claims are not independent outcome validation or release confirmation." } ], "disposition": "background", "category": "Advisory operations and platform consolidation", "relationship": "Supplementary surveillance/FAST context, distinct from AI-170, AI-171 and compression-dispatch optimization. No new adoption or counted result.", "run": "22 October morning Luna watch", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Original 27-page presentation downloaded and read by editor; pp.14,16,22 visually inspected. Deck internally dated 29 May 2026; exact publication date unknown.", "asset": "North American gas-pipeline facilities; exact FAST rollout population undisclosed.", "partner": "Accenture; AVEVA; AWS" }, { "id": "W22EX-FANG", "group_id": "W22EX-FANG", "company": "Diamondback Energy", "company_key": "Diamondback Energy", "department": "Finance, investment & strategy", "title": "Diamondback wants someone to challenge the economics of its AI projects", "kind": "context", "stage": "Hiring signal; role and framework implementation unverified", "operating_period": "The posting was available when checked on 22 October 2026. Its publication date and whether the role has been filled are unverified.", "display_period": "Unknown", "claim": "An official AI Lead – Value and Economics posting calls for someone to test AI business cases and distinguish actual impact from correlation. The role would set baselines and comparison methods, challenge benefit assumptions, compare forecasts with realized value, and recommend whether projects continue, scale, change course or stop. It works with Finance, product owners and the AI portfolio lead.", "economics": "No project results, filled-role evidence, implemented measurement framework, cost or return is disclosed.", "baseline": "Intended measurement standards, not evidence of a measured intervention.", "ai_role": "Intended economics and attribution governance; no new model or operating workflow established.", "limits": "A job description establishes intended responsibilities. It does not show that these controls exist today or that any project was stopped. Existing Diamondback operating initiatives retain their own evidence.", "decision_question": "Who can challenge an AI business case, and what evidence would make the company stop funding it?", "sources": [ { "id": "WATCH22EX-FANG", "title": "AI Lead – Value and Economics · R100885", "url": "https://diamondbackenergy.wd12.myworkdayjobs.com/DBE/job/Midland-TX/AI-Lead---Value-and-Economics_R100885", "date": "Unknown", "publisher": "Diamondback Energy / official Workday careers", "locator": "Job Responsibilities: valuation framework, baselines/comparison groups, benefits attribution, continue/scale/pivot/stop recommendations. Official public jobPostingInfo payload retrieved.", "excerpt": "recommend whether investments should continue, scale, pivot, or stop", "access": "Editor retrieved and read the full official public Workday job payload. Human-facing page returns no extracted text; search copy corroborates responsibilities. Publication date not verified; metadata startDate is not a verified hire or operating date.", "retrieval_url": "https://diamondbackenergy.wd12.myworkdayjobs.com/wday/cxs/diamondbackenergy/DBE/job/Midland-TX/AI-Lead---Value-and-Economics_R100885", "metadata_start_date": "2026-08-25", "metadata_date_limit": "Workday startDate field; meaning not documented, not treated as publication, employment or deployment date." } ], "disposition": "background", "category": "AI investment governance", "relationship": "Context for Diamondback readiness; separate from AI-045 and AI-251. No new adoption or counted result.", "run": "22 October additional Luna watch", "ai_ids": [], "core_company": true, "logo_available": false, "context_only": true, "evidence": "Editor retrieved and read the full official public Workday job payload. Human-facing page returns no extracted text; search copy corroborates responsibilities. Publication date not verified; metadata startDate is not a verified hire or operating date.", "asset": "Enterprise AI portfolio; Midland and Dallas role locations, no named operating asset.", "partner": "No outside partner named" }, { "id": "W22EX-ITALGAS", "group_id": "W22EX-ITALGAS", "company": "Italgas", "company_key": "Italgas", "department": "Commercial, power & infrastructure", "title": "Italgas’s voice agent can help with appointments; the reported gains need more checking", "kind": "context", "stage": "Adjacent gas-distribution case; limited production beta described", "operating_period": "Undated talk. Full call coverage was planned for September, with no verified year or completion. It is not confirmed as a fresh announcement.", "display_period": "Unknown", "claim": "A vendor-hosted talk describes Italgas testing a voice agent on a subset of customer calls, with people handling complex requests. A real-time language model uses governed knowledge and authenticated CRM tools for appointment work. Databricks supports retrieval and tracing; Azure hosts the voice model. Broader channels are planned.", "economics": "Speakers claim 50% fewer dropped calls and 40% more automated resolutions in beta. Test size, period, metric definitions, quality, costs and net return are absent.", "baseline": "Conflicting transcript baseline; no absolute result reconstruction.", "ai_role": "Customer-service language agent with CRM tools; no physical gas-network control described.", "limits": "The transcript’s earlier baseline figures do not reconcile. The summary omits the beta boundary. Do not reconstruct absolute outcomes, infer full rollout or treat these claims as measured upstream results.", "decision_question": "Does the bot complete the right task, escalate safely, and reduce total effort after corrections?", "sources": [ { "id": "WATCH22EX-ITALGAS", "title": "Building Production Voice Agents with Databricks and AI Gateway", "url": "https://answers.databricks.com/building-production-voice-agents-databricks-ai-gateway-w8XJClcgjx4", "date": "Unknown", "publisher": "Databricks / named Italgas and Reply speakers", "locator": "Full transcript: 02:04 and09:38 baseline conflict;10:10–16:57 architecture and CRM;19:28–20:15 limited beta, planned September rollout and claimed changes;21:05 human operators.", "excerpt": "we are in a kind of beta testing moment", "access": "Editor read vendor-hosted named-speaker transcript, not just its summary/FAQs. Original video link fetch failed. Transcript baseline numbers conflict; exact talk/publication date and full rollout remain unverified." } ], "disposition": "background", "category": "Adjacent gas-distribution customer service", "relationship": "Adjacent gas-distribution analog, not an upstream E&P initiative or addition to core adoption/results.", "run": "22 October additional Luna watch", "ai_ids": [], "core_company": false, "logo_available": true, "context_only": true, "evidence": "Editor read vendor-hosted named-speaker transcript, not just its summary/FAQs. Original video link fetch failed. Transcript baseline numbers conflict; exact talk/publication date and full rollout remain unverified.", "asset": "Gas-distribution contact centre; beta call population undisclosed.", "partner": "Databricks; Reply; Microsoft Azure" }, { "id": "W22FAIL-SPE", "group_id": "W22FAIL-SPE", "company": "SPE pressure-prediction study", "company_key": "SPE pressure-prediction study", "department": "Reservoir engineering & field development", "title": "A neural network struggled to predict pressure in this test", "kind": "negative_evidence", "stage": "Model-test weakness; no operating deployment established", "operating_period": "Published 10 August 2026. The ProBHP data are attributed to sources from 1975 and 1986; collection dates, well count, geography and test chronology are unspecified.", "display_period": "2026-08-10", "claim": "An SPE study compared a random forest and a neural network on 206 historical pressure samples. The neural network performed poorly on the reported test split. The authors used 10 inputs and an 80/20 training/test split. They describe a small, noisy dataset; the abstract does not establish testing on entirely unseen wells.", "economics": "Neural-network mean absolute error: 209.55 psig; random forest: 93.73 psig. Test R² was 0.05 versus 0.81. R² is not a percent-correct accuracy score. No operating loss or deployment cost is reported.", "baseline": "Reported test split of a 206-sample dataset; exact test count and independence by well unverified.", "ai_role": "Random forest versus artificial neural network for pressure prediction; no LLM or field control.", "limits": "Only the publisher-indexed abstract was reviewed; direct access failed. No raw data, full validation protocol, deployed system, stop decision or later outcome verified. This does not establish a failure rate for industry AI projects.", "decision_question": "Would performance hold on entirely new wells, with the full error distribution and an operating decision attached?", "sources": [ { "id": "WATCH22FAIL-SPE", "title": "Evaluation of Influential Parameters for Prediction of Flowing Bottom Hole Pressure in Dry Gas Wells Using Machine Learning", "url": "https://onepetro.org/SPENAIC/proceedings-abstract/26NAIC/26NAIC/SPE-234889-MS/802231", "date": "2026-08-10", "publisher": "Society of Petroleum Engineers / OnePetro", "locator": "SPE-234889-MS; publisher-indexed abstract: dataset/split and Random Forest/ANN comparison paragraphs. Published 10 August 2026; conference 3–5 August 2026.", "excerpt": "ANN model performed poorly", "access": "Editor independently read the search-indexed original publisher abstract and metadata. Direct OnePetro/DOI opens failed; local page fetch returned 403. Full paper, raw data and complete methods not reviewed. No claim of field deployment or independent replication." } ], "disposition": "background", "category": "Technical model-validation limits", "relationship": "Technical benchmark only, separate from Santos AI-139 and all operating pressure-model claims. No core adoption or counted result.", "run": "22 October failure-focused Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor independently read the search-indexed original publisher abstract and metadata. Direct OnePetro/DOI opens failed; local page fetch returned 403. Full paper, raw data and complete methods not reviewed. No claim of field deployment or independent replication.", "asset": "Historical dry-gas pressure dataset; 206 samples, not 206 identified wells.", "partner": "Authors: Fred Akpososo, Victor Aimikhe, David Kalu and Precious Okolaa" }, { "id": "W22PM-VISTA", "group_id": "W22PM-VISTA", "company": "Vista Energy", "company_key": "Vista Energy", "department": "Drilling & completions", "title": "Vista uses AI monitoring to adjust completion designs", "kind": "context", "stage": "Operating since March 2025, per issuer", "operating_period": "Investor day: 12 November 2025. Implementation since March 2025. Results labeled 2025; exact evaluation dates, well count and later continuation not disclosed.", "display_period": "2025-11-12", "claim": "Vista says its own AI monitoring tool helps engineers make completion-design decisions in real time in Vaca Muerta. The tool identifies frac hits and helps adjust stimulation to protect parent wells. The investor-day slide says it has been used since March 2025.", "economics": "Vista reports less than 1% of completion stages lost in 2025 and one runaway stage avoided per well on average. These are issuer-reported technical outcomes. The same slide prints a cost-saving unit as ~150 $M per well; that dollar amount is unresolved and excluded from comparisons. No net ROI is established.", "baseline": "2025 technical measures; matched baseline and denominator undisclosed.", "ai_role": "Proprietary AI monitoring for real-time completion-design decisions; no LLM or autonomous pumping authority established.", "limits": "No matched baseline, well or pad population, effect-isolation method, tool costs or independent validation. Approval and execution rights are not disclosed. The schematic stage numbers are not a project population. The cost-saving unit is ambiguous even in the original image; no dollar benefit is normalized or counted.", "decision_question": "What changed in completion decisions, and do the avoided stages still pay after tool costs and engineering review?", "sources": [ { "id": "WATCH22PM-VISTA", "title": "Vista Investor Day 2025", "url": "https://www.vistaenergy.com/docs/vista-investor-day2025-presentation-1wbmozw.pdf", "date": "2025-11-12", "publisher": "Vista Energy", "locator": "Slide 19 / PDF p. 19; title, implementation date and results column. Date corroborated by SEC exhibit heading.", "excerpt": "Implemented since March 2025", "access": "Editor downloaded and read the original issuer PDF, inspected slide 19 visually and cross-checked the SEC exhibit. Company-reported, not independently validated." }, { "id": "WATCH22PM-VISTA-SEC", "title": "Vista Investor Day 2025 — SEC exhibit", "url": "https://www.sec.gov/Archives/edgar/data/1762506/000119312525276082/d948063dex1.htm", "date": "2025-11-12", "publisher": "Vista Energy / SEC EDGAR", "locator": "Exhibit heading: November 12, 2025; same slide 19 presentation.", "excerpt": "Vista Investor Day", "access": "Original SEC exhibit read. A second access path to the same issuer presentation, not independent corroboration of outcomes." } ], "disposition": "background", "category": "Operating completion decisions", "relationship": "One new named operating profile. The PDF and SEC exhibit are the same publication, not two deployments.", "run": "22 October evening Luna watch", "ai_ids": [ "AI-298" ], "core_company": true, "context_only": true, "evidence": "Editor downloaded and read the original issuer PDF, inspected slide 19 visually and cross-checked the SEC exhibit. Company-reported, not independently validated.", "asset": "Vaca Muerta, Argentina; specific block, pad and well count undisclosed.", "partner": "No implementation partner named on the reviewed slide." }, { "id": "W22PM-SAIPEM", "group_id": "W22PM-SAIPEM", "company": "Saipem", "company_key": "Saipem", "department": "Maintenance & reliability", "title": "Saipem installs a predictive-maintenance pilot on one drillship", "kind": "context", "stage": "Installed pilot on Saipem 12000; fleet extension planned", "operating_period": "Announced 23 February 2026. Pilot installation described; operating evaluation period and later fleet rollout unknown. Saipem 7000 testing was prospective.", "display_period": "2026-02-23", "claim": "Saipem says it installed an AI predictive-maintenance system on the Saipem 12000, the first drillship in its fleet to receive it. With ADC Energy, the pilot reads equipment data to flag anomalies and anticipate failures. A separate BIP project for diesel generators on Saipem 7000 was still being implemented and awaiting tests.", "economics": "No measured downtime reduction, failure forecast quality, intervention count, cost saving or ROI disclosed. One installed pilot is not a fleet deployment.", "baseline": "No pre-pilot reliability comparator or evaluation period disclosed.", "ai_role": "Equipment-data anomaly detection and failure prediction; no LLM or autonomous maintenance execution established.", "limits": "The issuer explicitly calls the 12000 project a pilot. Fleet extension and the separate 7000 project remain plans. Human maintenance approval, automatic execution, fallback rules and measured outcomes are undisclosed.", "decision_question": "Did the alerts lead to useful maintenance interventions, with fewer false alarms and enough avoided downtime to cover full costs?", "sources": [ { "id": "WATCH22PM-SAIPEM", "title": "Saipem introduces an AI-based predictive maintenance system onboard the Saipem 12000", "url": "https://www.saipem.com/en/media/news/Saipem-introduces-an-AI-based-predictive-maintenance-system-onboard-the-Saipem-12000", "date": "2026-02-23", "publisher": "Saipem", "locator": "Page date; Saipem 12000 implementation, ADC Energy, pilot and separate Saipem 7000/BIP paragraphs.", "excerpt": "This pilot project", "access": "Editor read the full original issuer announcement. Installation is described; no measured reliability result or fleet rollout independently verified." } ], "disposition": "background", "category": "Installed predictive-maintenance pilot", "relationship": "Distinct from Saipem scheduling, video safety and drone initiatives. The separate 7000 plan is not another operating profile.", "run": "22 October evening Luna watch", "ai_ids": [ "AI-299" ], "core_company": true, "context_only": true, "evidence": "Editor read the full original issuer announcement. Installation is described; no measured reliability result or fleet rollout independently verified.", "asset": "Saipem 12000 ultra-deepwater drillship. Saipem 7000 is separate future context.", "partner": "ADC Energy for Saipem 12000; BIP for the separate Saipem 7000 project." }, { "id": "W22PM-WORLEY", "group_id": "W22PM-WORLEY", "company": "Worley", "company_key": "Worley", "department": "IT, data & enterprise transformation", "title": "Worley puts four internal tools into engineering and bid work", "kind": "context", "stage": "Four recently deployed internal solutions, per issuer", "operating_period": "FY2025 results presentation dated 27 August 2025. Individual go-live dates, usage duration and later adoption unknown.", "display_period": "2025-08-27", "claim": "Worley lists four deployed tools for vendor comparison, engineering-document checks, internal knowledge search and customer-response drafting. AI.VendorSelect supports technical-bid evaluation; AI.HoldsFinder extracts design holds; AI.Assist searches proprietary engineering knowledge; Smart Response Generator helps draft responses to queries and expressions of interest.", "economics": "Four tool names are a program scope, not four independently measured deployments. No active-user count, measured time saving, accuracy comparison, full cost or return is disclosed.", "baseline": "No tool-level before/after or quality-controlled comparator disclosed.", "ai_role": "Internal AI-assisted document review, search, comparison and drafting. Exact model architecture and execution permissions undisclosed.", "limits": "These are Worley’s internal tools across energy, chemicals and resources. No upstream-only user cohort or client field deployment is established. NVIDIA, Microsoft and Dell appear as general partner logos, not confirmed partners for each tool. No autonomous vendor selection, design approval or customer communication is established.", "decision_question": "Which work do employees complete with each tool, and how much review remains before a bid, design or response is approved?", "sources": [ { "id": "WATCH22PM-WORLEY", "title": "FY2025 full-year results presentation", "url": "https://www.worley.com/-/media/files/worley/investors/results-and-presentations/2025/wor-presentation-full-year-results-fy2025.pdf", "date": "2025-08-27", "publisher": "Worley", "locator": "Slide 31 / PDF p. 31: recently deployed Advanced Development Lab solutions. Date on cover.", "excerpt": "Recently deployed solutions through our Advanced Development Lab", "access": "Editor downloaded and read the original issuer presentation and visually inspected slide 31. Named internal tools, not measured client or field outcomes." } ], "disposition": "background", "category": "Internal engineering and commercial tools", "relationship": "One internal program profile covering four named tools, not four field deployments.", "run": "22 October evening Luna watch", "ai_ids": [ "AI-300" ], "core_company": true, "context_only": true, "evidence": "Editor downloaded and read the original issuer presentation and visually inspected slide 31. Named internal tools, not measured client or field outcomes.", "asset": "Internal engineering and commercial work; no client asset, basin or user population disclosed.", "partner": "No tool-specific implementation partner established by the reviewed slide." }, { "id": "W22PM-WHITECAP", "group_id": "W22PM-WHITECAP", "company": "Whitecap Resources", "company_key": "Whitecap Resources", "department": "IT, data & enterprise transformation", "title": "Whitecap describes the data foundation it is building around AI", "kind": "context", "stage": "Operating data platform; predictive and agentic uses remain prospective", "operating_period": "Vendor index dated 23 April 2026; story itself undated. Platform use described, but project start and evaluation dates are unknown.", "display_period": "2026-04-23", "claim": "A Shakudo customer story describes Whitecap’s governed data platform and business-led AI prototypes, with IT bringing selected work into production. The account describes relational data and operating telemetry, on-premise language models and selective frontier-model access. Human review remains part of the approach.", "economics": "The page’s less-than-one-hour analytics headline conflicts with narrative describing an endpoint still being built toward. It is not counted as achieved savings or ROI. Company production and team size are not an AI user population.", "baseline": "The analytics-cycle headline is not a verified before/after measurement.", "ai_role": "Governed data and internal AI experimentation; no deployed predictive field model or autonomous control established.", "limits": "Vendor account with a named customer executive, without independent operator corroboration. Predictive analytics and agentic work are prospective. The conflicting time claim, model quality, active use and full costs remain unresolved.", "decision_question": "Which prototypes have become routine work, and what does the production team measure before approving wider use?", "sources": [ { "id": "WATCH22PM-WHITECAP", "title": "Whitecap Resources customer story", "url": "https://www.shakudo.io/customers/whitecap-resources", "date": "2026-04-23", "publisher": "Shakudo", "locator": "Key Results; govern-first platform, AI operating model, human review and endpoint being built toward. Page is undated; date comes from vendor customer index.", "excerpt": "The endpoint being built toward", "access": "Editor read the original vendor customer story. Named customer executive is quoted; operator-side corroboration and outcome methods not verified." }, { "id": "WATCH22PM-WHITECAP-DATE", "title": "Shakudo customer stories — Whitecap entry", "url": "https://www.shakudo.io/customers", "date": "2026-04-23", "publisher": "Shakudo", "locator": "Whitecap customer-story listing dated April 23, 2026.", "excerpt": "Whitecap Resources", "access": "Original vendor customer index read; verifies listed publication date, not a deployment or benefit." } ], "disposition": "background", "category": "Data foundations and production governance", "relationship": "Context-only technology note. Does not add a core AI adoption, counted outcome or net ROI.", "run": "22 October evening Luna watch", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read the original vendor customer story. Named customer executive is quoted; operator-side corroboration and outcome methods not verified.", "asset": "Whitecap/Veren operating data; no asset-specific AI evaluation population disclosed.", "partner": "Shakudo" }, { "id": "W22PM-TEN", "group_id": "W22PM-TEN", "company": "Technip Energies", "company_key": "Technip Energies", "department": "IT, data & enterprise transformation", "title": "Technip Energies reports progress, without proving 55 AI deployments", "kind": "context", "stage": "Mixed digital and AI program; end-2025 output counts", "operating_period": "2025 annual report published in 2026; exact publication day unverified. Progress is explicitly at end-2025. The URL timestamp is not treated as a publication date.", "display_period": "2026 (exact publication day unverified)", "claim": "Technip Energies says its transformation plan had launched more than 55 digital and AI initiatives and delivered more than 20 minimum viable products by the end of 2025. The plan began in 2024. An AI-for-all campaign launched in 2025 aims to upskill staff; neither completed training nor routine use by all employees is established.", "economics": "The counts mix digital and AI work. Launched initiatives and delivered MVPs are not equivalent to production deployments, active users, measured savings or net ROI.", "baseline": "End-2025 program output counts, not a benefit baseline.", "ai_role": "Mixed digital and AI initiatives and staff upskilling; no inference of 55 AI production deployments.", "limits": "Only the indexed original p. 41 excerpt was reviewed; direct PDF access returned 403. Full-report definitions and later rollout remain unreviewed. No per-initiative deployment status, active-user denominator, measured benefit or full-cost return verified. The earlier DAP source dates that program to 2025; the annual report dates a broader transformation plan to 2024. Their exact relationship is unresolved.", "decision_question": "Which MVPs survived evaluation, reached routine use and produced a measured result after implementation and review costs?", "sources": [ { "id": "WATCH22PM-TEN", "title": "Technip Energies 2025 Annual Report", "url": "https://investors.technipenergies.com/system/files-encrypted/nasdaq_kms/assets/2026/03/10/14-52-00/TEN_2025%20Annual%20Report.pdf", "date": "2026 (exact publication day unverified)", "publisher": "Technip Energies", "locator": "Printed p. 41, Value creation / We strive for excellence: digital transformation plan and end-2025 output counts.", "excerpt": "more than 55 digital and AI initiatives", "access": "Editor read the search-indexed original annual-report excerpt. Direct PDF returned 403; full report unreviewed. URL timestamp is not used as an exact publication date." } ], "disposition": "background", "category": "Program output and scaling limits", "relationship": "Enriches existing AI-199. No second program, additional deployment count or numerical-result credit.", "run": "22 October evening Luna watch", "ai_ids": [ "AI-199" ], "core_company": true, "context_only": true, "evidence": "Editor read the search-indexed original annual-report excerpt. Direct PDF returned 403; full report unreviewed. URL timestamp is not used as an exact publication date.", "asset": "Company transformation program; project and asset populations undisclosed.", "partner": "No partner verified in the reviewed excerpt." }, { "id": "W23AM-AZULE", "group_id": "W23AM-AZULE", "company": "Azule Energy", "company_key": "Azule Energy", "department": "Drilling & completions", "title": "Azule connects the well plan to drilling automation", "kind": "context", "stage": "Operating single-well example; wider rollout unverified", "operating_period": "Q3 release published 23 October 2026. The related case study is undated. One well and a 2,000-meter section are described; exact operating dates unknown.", "display_period": "2026-10-23", "claim": "SLB describes Azule using one digital workflow from well design through rig execution offshore Angola. DrillPlan passes the plan into DrillOps automation. The supplier case identifies AI-driven operations; it does not isolate AI from engineering automation.", "economics": "Supplier reports 95% of engineering tasks automated, planning time of 192 versus 31 hours and 75% fewer manual handoffs. A 2,000-meter section had zero reported nonproductive time and 16% higher net rate of penetration than the field benchmark. These are different measures, not a common financial return.", "baseline": "Planning before/after and an unspecified field ROP benchmark; no matched controlled comparison.", "ai_role": "AI-enabled DrillOps execution alongside digital well planning; underlying algorithms and model type undisclosed.", "limits": "No well identifier, wider well population, benchmark construction, review-effort adjustment, quality comparison or full cost. Execution is described as autonomous, but approval, override and fallback rules are undisclosed. No LLM or AI-only contribution is established; zero NPT for this section is not a long-term reliability rate.", "decision_question": "Does passing an approved plan into rig execution reduce total work once checking, exceptions and overrides are counted?", "sources": [ { "id": "WATCH23AM-SLB-Q3", "title": "SLB third-quarter 2026 results — selected operating and digital highlights", "url": "https://investorcenter.slb.com/static-files/7045f96e-ee28-4096-934c-49eb4b37e66f", "date": "2026-10-23", "publisher": "SLB", "locator": "PDF p. 16: Digital / Azule Energy paragraph; same case and key measures.", "excerpt": "cut planning time from 192 to 31 hours", "access": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "format": "pdf" }, { "id": "WATCH23AM-AZULE", "title": "Azule Energy pioneers digital well planning and rig automation in Africa", "url": "https://www.slb.com/resource-library/case-study-with-navigation/di/2026/azule-energy-pioneers-digital-well-planning-and-rig-automation-in-africa", "date": "Unknown", "publisher": "SLB", "locator": "Location; Results: Achieving operational excellence; Products Used: DrillOps AI-driven workflows.", "excerpt": "digitally ingested the well plan", "access": "Editor read the original supplier case study. No exact publication date displayed; the 2026 URL path and search crawl dates are not publication dates. Same supplier as the Q3 release; not independent corroboration." } ], "disposition": "background", "category": "Plan-to-execution operating workflow", "relationship": "One named operator profile. Case study and quarterly release are both SLB publications; no independent result validation.", "run": "23 October morning source review", "ai_ids": [ "AI-301" ], "core_company": true, "context_only": true, "evidence": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "asset": "One offshore Angola well; no named field or basin disclosed.", "partner": "SLB" }, { "id": "W23AM-CHEMISTRY", "group_id": "W23AM-CHEMISTRY", "company": "SLB / unnamed Permian operator", "company_key": "SLB / unnamed Permian operator", "department": "Production & field operations", "title": "Better chemical dosing reduced waste across an existing well fleet", "kind": "context", "stage": "Supplier-reported deployment; operator identity withheld", "operating_period": "Performance comparison: 20 months. Savings: first nine months. Exact operating start/end dates and case-study publication date unknown; repeated in Q3 results on 23 October 2026.", "display_period": "2026-10-23", "claim": "SLB reports overtreatment falling from 17% to 3% across nearly 1,400 Permian wells over a 20-month program. Sensors feed ML detection; weekly team reviews support remote adjustments. Detailed approval and fallback permissions are not disclosed.", "economics": "SLB-reported net savings: $4.4 million in the first nine months, attributed to lower chemical spend. The meaning of net and complete deployment costs are not disclosed.", "baseline": "Share of overtreated wells: 17% before, 3% after. The case study also says on- or above-target dosing; Q3 uses on-target. These labels are not silently merged.", "ai_role": "AI injection control plus ML anomaly detection; human review cadence disclosed, execution permissions and fallback unspecified.", "limits": "An anonymous supplier account, without a controlled comparison or complete net ROI. The percentage change concerns the share of overtreated wells, not chemical volume or total cost. The case study and Q3 release are the same publisher, not independent corroboration.", "decision_question": "What costs were included, and did lower overtreatment persist without compromising corrosion or scale protection?", "sources": [ { "id": "RESULTS-SLB-CHEM", "title": "Permian field chemical automation case study", "url": "https://www.slb.com/resource-library/case-study-with-navigation/production-chemicals/permian-basin-field-automations-cs", "date": "Unknown", "publisher": "SLB", "locator": "Results and solution sections; 20-month dosing comparison and first-nine-month savings are different periods.", "excerpt": "USD 4.4 million in net savings in the first 9 months", "access": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "format": "html" }, { "id": "WATCH23AM-SLB-Q3", "title": "SLB third-quarter 2026 results — selected operating and digital highlights", "url": "https://investorcenter.slb.com/static-files/7045f96e-ee28-4096-934c-49eb4b37e66f", "date": "2026-10-23", "publisher": "SLB", "locator": "PDF p. 14: Technology Highlights / United States production chemistry paragraph.", "excerpt": "AI-driven injection control", "access": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "format": "pdf", "existing": true } ], "disposition": "background", "category": "Chemical dosing", "relationship": "Context only; anonymous supplier account excluded from named operator adoption and outcome totals.", "run": "25 October operating-results review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "asset": "Nearly 1,400 producing Permian wells; operator and individual assets unnamed.", "partner": "SLB" }, { "id": "W23AM-ENI", "group_id": "W23AM-ENI", "company": "Eni", "company_key": "Eni", "department": "IT, data & enterprise transformation", "title": "Eni adds a concrete on-premise subsurface workflow", "kind": "context", "stage": "Supplier reports expanded operating workflows", "operating_period": "Published 23 October 2026; exact deployment and expansion dates undisclosed.", "display_period": "2026-10-23", "claim": "SLB says Eni expanded petrophysics and geomechanics AI workflows using an on-premise Lumi platform. Analyst takeaway: the location of the data platform matters when deciding what information a new assistant or model can access.", "economics": "No task-level benefit, asset population or full cost quantified in this update. Eni’s existing portfolio metrics and targets remain separately sourced; none is allocated to Lumi.", "baseline": "No matched quality, time or operating comparison disclosed.", "ai_role": "AI-enabled petrophysics and geomechanics on on-premise Lumi; specific model architecture undisclosed.", "limits": "Supplier statement, without independent operator corroboration of this specific expansion. Model type, user count, data permissions and decision authority are undisclosed. No inference that this uses an LLM or captures all company communications.", "decision_question": "Which petrophysics or geomechanics decisions changed, and what data and review boundaries apply?", "sources": [ { "id": "WATCH23AM-SLB-Q3", "title": "SLB third-quarter 2026 results — selected operating and digital highlights", "url": "https://investorcenter.slb.com/static-files/7045f96e-ee28-4096-934c-49eb4b37e66f", "date": "2026-10-23", "publisher": "SLB", "locator": "PDF p. 16: Digital / SLB and Eni paragraph.", "excerpt": "AI-driven workflows", "access": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "format": "pdf" } ], "disposition": "background", "category": "Existing program: named operating detail", "relationship": "Adds source-bounded detail to AI-027; no new core profile or counted result.", "run": "23 October morning source review", "ai_ids": [ "AI-027" ], "core_company": true, "context_only": true, "evidence": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "asset": "Eni subsurface work; no field, basin or user population identified.", "partner": "SLB" }, { "id": "W23AM-BSP", "group_id": "W23AM-BSP", "company": "Brunei Shell Petroleum", "company_key": "Brunei Shell Petroleum", "department": "IT, data & enterprise transformation", "title": "BSP awards an on-premise software contract", "kind": "context", "stage": "Contract awarded; go-live and usage unverified", "operating_period": "Published 23 October 2026. Award date, implementation timetable and active-use dates unknown.", "display_period": "2026-10-23", "claim": "BSP awarded SLB an on-premise contract for Petrel and Techlog, with digital and AI capabilities across subsurface and production work. Analyst takeaway: a broad contract establishes buying intent and implementation scope; it does not show which AI tasks employees complete.", "economics": "No measured operating or financial result disclosed. Contract scope is not a user population or proof of completed deployment.", "baseline": "No live-use or outcome baseline established.", "ai_role": "Contract includes AI capabilities; no particular live model or LLM workflow established.", "limits": "Supplier reports an award. Live AI workflows, algorithms, asset coverage, approvals and full cost remain unverified. BSP is separately identified; this award does not establish a Shell-wide rollout.", "decision_question": "Which workflows will go live first, and what acceptance test separates installed software from useful work?", "sources": [ { "id": "WATCH23AM-SLB-Q3", "title": "SLB third-quarter 2026 results — selected operating and digital highlights", "url": "https://investorcenter.slb.com/static-files/7045f96e-ee28-4096-934c-49eb4b37e66f", "date": "2026-10-23", "publisher": "SLB", "locator": "PDF p. 16: Digital / Brunei BSP software contract paragraph.", "excerpt": "on-premises software contract", "access": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "format": "pdf" } ], "disposition": "background", "category": "Named software award", "relationship": "One announced customer profile. Distinct from Shell’s global AI-infrastructure collaboration and from BSP’s separate Retina equipment use.", "run": "23 October morning source review", "ai_ids": [ "AI-302" ], "core_company": true, "context_only": true, "evidence": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "asset": "BSP, Brunei; subsurface and production scope, no specific asset or user count.", "partner": "SLB" }, { "id": "W23AM-ADNOC", "group_id": "W23AM-ADNOC", "company": "ADNOC", "company_key": "ADNOC", "department": "Drilling & completions", "title": "SLB repeats ADNOC’s rig-center scope, without a new rollout count", "kind": "context", "stage": "Supplier repeats existing 120-plus-rig scope", "operating_period": "Published 23 October 2026; earlier operator disclosure was 4 August 2026. No new commissioning date.", "display_period": "2026-10-23", "claim": "SLB’s Q3 release repeats that ADNOC’s AI-enabled operations center covers more than 120 onshore and offshore rigs. Analyst takeaway: this is another source for an existing footprint, not evidence that a new set of rigs was added.", "economics": "No additional rollout count or newly measured benefit. Earlier ADNOC claims retain their own source, period and limitations.", "baseline": "No new comparable outcome or rollout baseline.", "ai_role": "AI-enabled drilling oversight; per-rig autonomous execution is not established by this paragraph.", "limits": "Same supplier relationship and already covered footprint; not independent validation. Rig oversight and coordination do not establish autonomous drilling control on every rig. Do not transfer an individual well’s performance to the rig-center fleet.", "decision_question": "What is monitored centrally, what action can the platform take and who approves a change on a rig?", "sources": [ { "id": "WATCH23AM-SLB-Q3", "title": "SLB third-quarter 2026 results — selected operating and digital highlights", "url": "https://investorcenter.slb.com/static-files/7045f96e-ee28-4096-934c-49eb4b37e66f", "date": "2026-10-23", "publisher": "SLB", "locator": "PDF p. 16: Digital / ADNOC Real-Time Operations Center paragraph.", "excerpt": "Real-Time Operations Center", "access": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "format": "pdf" } ], "disposition": "background", "category": "Existing deployment: source corroboration", "relationship": "Existing AI-226 only. No new deployment, result or ROI credit.", "run": "23 October morning source review", "ai_ids": [ "AI-226" ], "core_company": true, "context_only": true, "evidence": "Editor read the original issuer earnings-release HTML and relevant original PDF text. PDF p. 14 and p. 16 are physical page numbers (zero-based viewer P13/P15). Direct local PDF download failed; no call transcript reviewed. Supplier-reported customer claims, not independent validation.", "asset": "Existing ADNOC rig-center fleet; no new asset-specific population.", "partner": "SLB" }, { "id": "W23PM-PETROBRAS", "group_id": "W23PM-PETROBRAS", "company": "Petrobras", "company_key": "Petrobras", "department": "Supply chain & logistics", "title": "AI checks supplier documents. Petrobras staff make the decision.", "kind": "context", "stage": "Wave 2 pilot; rollout unconfirmed", "operating_period": "Undated notice checked 23 October 2026. Forms are scheduled to open from September 2026, with documents due 30 days after each questionnaire opens; actual opening and evaluation dates are not confirmed.", "display_period": "Unknown", "claim": "Petrobras describes AVAL IA Wave 2 reviewing supplier-registration documents before a technical evaluator checks them. The evaluation team records its decision and feeds it back to the AI. Petronect handles registration; the notice does not identify the AI model or developer.", "economics": "No accuracy, workload, completed-case count, cost, saving or ROI reported.", "baseline": "No before/after comparison or measurement period disclosed.", "ai_role": "Preliminary document analysis; model type and developer undisclosed.", "limits": "Technical evaluators keep the final check and decision. The notice says the pilot may pause for adjustments; it does not say it failed or was suspended. No LLM, autonomous approval or full rollout established.", "decision_question": "Does the first AI pass reduce total review work while preserving the quality of supplier decisions?", "sources": [ { "id": "WATCH23PM-PETROBRAS", "title": "Cadastro de Fornecedores — AVAL IA Onda 2 pilot notice", "url": "https://canalfornecedor.petrobras.com.br/pt/cadastro-de-fornecedores/sobre-o-cadastro-de-fornecedores", "date": "Unknown", "publisher": "Petrobras", "locator": "Nova Fase do Projeto Piloto AVAL IA: O que muda / Prazos dessa fase. Portuguese original; September 2026 form schedule is not the publication date.", "excerpt": "A supervisão e a decisão final permanecem sempre com nossos avaliadores técnicos.", "access": "Editor read the original Petrobras Supplier Channel notice in Portuguese. Exact publication date unknown; the notice describes Wave 2 and a form-opening schedule from September 2026. Current completed-case volume and pilot results are not supplied." } ], "disposition": "background", "category": "Supplier qualification", "relationship": "One named pilot. Possible suspension is a future contingency, not a recorded setback.", "run": "23 October evening source review", "ai_ids": [ "AI-303" ], "core_company": true, "context_only": false, "evidence": "Editor read the original Petrobras Supplier Channel notice in Portuguese. Exact publication date unknown; the notice describes Wave 2 and a form-opening schedule from September 2026. Current completed-case volume and pilot results are not supplied.", "asset": "Petrobras corporate supplier registration; no producing asset or basin applies. Participating supplier volume is undisclosed.", "partner": "Petronect registration portal; AI technology partner unknown" }, { "id": "W24AM-HAL-RELIABILITY", "group_id": "W24AM-HAL-RELIABILITY", "company": "Halliburton", "company_key": "Halliburton", "department": "Maintenance & reliability", "title": "A maintenance alert only helps if a crew can act on it.", "kind": "context", "stage": "Supplier reports four deployments; customers unidentified", "operating_period": "Article published 22 October 2026; product page undated. Deployment dates, customers, assets, basins and equipment population are undisclosed.", "display_period": "2026-10-22", "claim": "Halliburton describes LOGIX Unit Vitality detecting early problems in cementing equipment so maintenance teams can investigate and plan repairs. Sensors feed more than 400 equipment parameters into cloud models. Staff check warnings, arrange parts and schedule corrective work. The product page separately describes transferring approved job designs from VIDA and iCem into controllers; this is not proof of autonomous maintenance.", "economics": "The supplier reports estimated downtime costs avoided of $125,000–$150,000 and 91% better maintenance productivity in four deployments. It does not define the productivity measure or say whether the dollar range is per deployment or combined.", "baseline": "No comparator, productivity definition or cost model disclosed.", "ai_role": "Statistical models and machine learning for equipment condition; no LLM identified.", "limits": "No baseline, evaluation period, false-alarm rate, cash reconciliation, full cost or independent validation. Estimated avoided downtime is not booked savings or net ROI. No named customer adoption or new counted result. Separate from LOGIX drilling results in AI-016.", "decision_question": "Did the warning lead to the right intervention, and did avoided downtime exceed inspection, repair and system costs?", "sources": [ { "id": "WATCH24AM-HAL-RELIABILITY", "title": "How predictive intelligence reduces downtime and improves equipment reliability", "url": "https://www.halliburton.com/en/energy-pulse/how-predictive-intelligence-reduces-downtime-improves-equipment-reliability", "date": "2026-10-22", "publisher": "Halliburton", "locator": "A simple question led to a new approach; How predictive reliability works; What early risk identification delivers.", "excerpt": "helped teams avoid an estimated $125,000 to $150,000 in downtime costs", "access": "Editor read the complete original Halliburton article and displayed publication date. Supplier-selected examples; operator names, operating dates and measurement methods are not provided." }, { "id": "WATCH24AM-HAL-PRODUCT", "title": "LOGIX Unit Vitality — cement equipment health monitoring", "url": "https://www.halliburton.com/en/products/logix-unit-vitality", "date": "Unknown", "publisher": "Halliburton", "locator": "Automated cement equipment health assessment; AI-driven models; Real-time monitoring closes the loop.", "excerpt": "more than 400 real-time parameters", "access": "Editor read the original product page. Exact publication date unknown. Same supplier as the article, not independent validation; product capabilities are not proof each feature was used in the four reported deployments." } ], "disposition": "background", "category": "Equipment reliability and planned maintenance", "relationship": "Supplier product with four unidentified deployment examples; not a new named operator deployment.", "run": "24 October morning source review", "ai_ids": [ "AI-304" ], "core_company": true, "context_only": false, "evidence": "Editor read the complete original Halliburton article and displayed publication date. Supplier-selected examples; operator names, operating dates and measurement methods are not provided.", "asset": "Cementing equipment; four deployments reported, with no identified basin, asset or customer.", "partner": "Halliburton" }, { "id": "W24AM-ONGC-ICE", "group_id": "W24AM-ONGC-ICE", "company": "ONGC", "company_key": "ONGC", "department": "IT, data & enterprise transformation", "title": "ONGC’s shared enterprise system predates the current AI wave.", "kind": "context", "stage": "Historical operating foundation; current roadmap undated", "operating_period": "Undated page checked 24 October 2026. The program began with SAP R/3 in 2004. S/4HANA transition date and the roadmap’s starting date are unknown.", "display_period": "Unknown", "claim": "ONGC says Project ICE connects finance, materials, HR, production revenue and other functions on SAP S/4HANA. The operator reports more than 500 locations, 24,000 users and 23 modules. It describes a three-site disaster recovery setup and a SAP RISE journey over the next two to three years; that roadmap has no section-specific date.", "economics": "These are reported platform-scale figures, not active AI users, measured uptime, productivity, cost savings or ROI.", "baseline": "No independently measured platform quality, availability or economic comparison.", "ai_role": "Enterprise software and data foundation; deployed AI not established by this section.", "limits": "Historical non-AI context only. AI-enabled innovation is a roadmap aim; no specific live AI workflow or decision authority established. A shared platform does not by itself prove clean data, adoption quality or AI readiness.", "decision_question": "Can teams retrieve the same trusted records across functions, and which transactions still require manual reconciliation?", "sources": [ { "id": "WATCH24AM-ONGC-ICE", "title": "ONGC Technology — Project ICE", "url": "https://www.ongcindia.com/web/eng/about-ongc/technology", "date": "Unknown", "publisher": "ONGC", "locator": "Project ICE, five paragraphs. Site-wide last-updated stamp does not establish when this section or its roadmap was published.", "excerpt": "24,000 users, and 23 SAP modules", "access": "Editor read the original ONGC Project ICE section. Legacy SAP R/3 rollout is dated 2004; section publication date and S/4HANA transition date are unknown. Website-wide last-updated label is not a section publication date." } ], "disposition": "background", "category": "Historical enterprise software foundation", "relationship": "Adds company context, not an AI adoption, result or new project profile.", "run": "24 October morning source review", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Editor read the original ONGC Project ICE section. Legacy SAP R/3 rollout is dated 2004; section publication date and S/4HANA transition date are unknown. Website-wide last-updated label is not a section publication date.", "asset": "Corporate enterprise systems across more than 500 locations; no basin or asset mapping.", "partner": "SAP platform; implementation partner undisclosed" }, { "id": "SLB-DATA-AI-THESIS", "group_id": "SLB-DATA-AI-THESIS", "company": "SLB", "company_key": "SLB", "department": "IT, data & enterprise transformation", "title": "What holds up in SLB’s data and AI investment thesis?", "kind": "context", "stage": "Existing commercial platform; investor valuation argument remains unproven", "operating_period": "Original investor-day scripts: 17 June 2026. FY2025 baseline released 23 January 2026; Q3 results released 23 October 2026. Terms dates unknown. Investor interview framing published 20 October 2026.", "display_period": "2026-10-23", "claim": "SLB has a credible route to earning more from AI: it can put specialized models into software and operating workflows that customers already use. The public evidence supports a platform, engineering and governed-access advantage. It does not support treating every customer’s downhole data as an unrestricted SLB-owned training pool. Menon describes a seismic model trained on public and SLB multiclient datasets, with customers able to fine-tune for their own assets. Lumi connects governed data; domain models handle technical formats; Tela provides interaction and workflow orchestration. SLB describes subscription upgrades, metered usage, tailored workflows and marketplace revenue sharing. These are commercial mechanisms, not disclosed AI-only earnings.", "economics": "FY2025 Digital revenue was $2.660bn and adjusted EBITDA $928m (34.9% margin). Q3 2026 Digital revenue was $693m, adjusted EBITDA $228m and ARR $1.04bn. These are division-wide figures, not AI revenue or customer ROI. The CFO’s 2030 $1.8–2.0bn adjusted EBITDA and approximately $2bn ARR are ambitions, not results.", "baseline": "Segment accounts are not AI-only economics. No pooled value or return estimate is admitted.", "ai_role": "Technical domain models plus general LLMs and agents; not a single text model trained without restriction on all downhole data.", "limits": "SLB disclaims ownership of Customer Data in its published online-service terms, while allowing specified service/product-improvement uses. Embedded Gen AI prompts and outputs require customer consent for training. Those clauses do not settle rights to every historical field dataset, derivative or negotiated contract. Digital includes software, operations, data licensing and professional services, with no AI-only profit bridge. Digital Operations overlaps Core segment reporting and is eliminated in consolidation. No demonstrated undervaluation or complete customer net cash ROI follows from these disclosures.", "decision_question": "Ask for AI-specific paid usage and retention, incremental profit after compute and support, training rights by data category, held-out-basin model performance, customer-specific control boundaries, and a valuation using post-elimination earnings. For the full evidence map and interactive revenue chart, read the SLB briefing linked from the homepage.", "sources": [ { "id": "SLBTH-Q3", "title": "SLB third-quarter 2026 results — Digital economics and category definitions", "url": "https://investorcenter.slb.com/news-releases/news-release-details/slb-announces-third-quarter-2026-results", "date": "2026-10-23", "publisher": "SLB", "locator": "Digital results; Supplementary Information questions 10–13; Digital customer highlights.", "excerpt": "$693 million decreased 1% sequentially", "type": "Supplier earnings release", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation." }, { "id": "SLBTH-FY25", "title": "SLB full-year 2025 results — Digital financial baseline", "url": "https://investorcenter.slb.com/news-releases/news-release-details/slb-announces-fourth-quarter-and-full-year-2025-results", "date": "2026-01-23", "publisher": "SLB", "locator": "Supplementary Information question 12, Digital FY2025 table.", "excerpt": "Digital revenue increased 9% on a full-year basis", "type": "Supplier earnings release", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation." }, { "id": "SLBTH-MENON", "title": "Shashi Menon: The Race to Scale Digital Operations and AI", "url": "https://investorcenter.slb.com/static-files/cf773c3d-348f-479f-aeb0-81f5418844ca", "date": "2026-06-17", "publisher": "SLB", "locator": "PDF pp. 3–5: data access and control; p. 11: seismic training; pp. 14–15: monetization.", "excerpt": "we trained it with public and SLB multiclient seismic data sets", "type": "Investor presentation and prepared script", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation." }, { "id": "SLBTH-BIGUET", "title": "Stephane Biguet: Proven Growth. Accretive Returns.", "url": "https://investorcenter.slb.com/static-files/0835f6dc-d2fb-4bc0-b85e-afecadcf36fe", "date": "2026-06-17", "publisher": "SLB", "locator": "PDF p. 4: customer base; pp. 7–10: commercial models; p. 11: 2030 ambitions.", "excerpt": "more than 1,500 customers, including 90 of the world’s top 100 oil and gas producers", "type": "Investor presentation and prepared script", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation." }, { "id": "SLBTH-TERMS", "title": "SLB Online Services Terms and Conditions", "url": "https://www.software.slb.com/slb-online-services-terms-and-conditions", "date": "Unknown", "publisher": "SLB", "locator": "Definitions: Customer Data and Interaction Data; sections 8(a)–(b), 9(a), 10(a).", "excerpt": "SLB claims no ownership rights in Customer Data.", "type": "Published online-service terms", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation. Effective/publication date unknown. Public standard terms do not establish the terms of every negotiated customer agreement." }, { "id": "SLBTH-GENAI", "title": "SLB Online Services Service Specific Terms", "url": "https://www.software.slb.com/slb-online-services-service-specific-terms", "date": "Unknown", "publisher": "SLB", "locator": "Generative AI Services: definitions; Connected Gen AI A(i), A(iv); Embedded Gen AI B(iii).", "excerpt": "SLB shall not use Customer Prompts or Output to train models or further develop the Online Services without Customer’s consent.", "type": "Published online-service terms", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation. Effective/publication date unknown. Public standard terms do not establish the terms of every negotiated customer agreement." }, { "id": "SLBTH-MULLIN", "title": "Robert Mullin interview: 3.5% of the S&P, 20% of the Cash", "url": "https://georgenoble.substack.com/p/35-of-the-s-and-p-20-of-the-cash", "date": "2026-10-20", "publisher": "The Noble Update", "locator": "Host introduction and linked interview; exact SLB interview timestamp not established.", "excerpt": "The oil service giant hiding a real AI business that could be worth more than the whole company", "type": "Investor opinion / interview", "access": "Original host introduction reviewed; confirms the investment framing and interview identity. Full interview passage and exact timestamp not independently checked. An Eisman episode containing the same argument remains unconfirmed." }, { "id": "SLBTH-RANNEN", "title": "Trygve Randen: Our Digital Advantage", "url": "https://investorcenter.slb.com/static-files/7aa731c6-2f38-47e4-9aa2-473a8d04ec6e", "date": "2026-06-17", "publisher": "SLB", "locator": "PDF pp. 2–3: governed platforms; pp. 5–6: hosting and trust; p. 7: operational footprint.", "excerpt": "more than ninety percent of global production is simulated or modelled using at least one of our digital solutions", "type": "Investor presentation and prepared script", "access": "Editor read the accessible original publisher text on 24 October 2026. Statements remain publisher-reported; no independent performance validation." } ], "disposition": "background", "category": "Data rights and commercial AI strategy", "relationship": "Expanded existing Lumi dossier and analytical context; no new initiative, operator adoption or reported-result count.", "run": "24 October SLB thesis review", "ai_ids": [ "AI-009", "AI-008", "AI-047", "AI-105" ], "core_company": true, "context_only": true, "evidence": "Original issuer materials and public standard terms reviewed", "asset": "Global Digital business; named operating cases retain their own asset and evidence boundaries.", "partner": "SLB, customer operators and technology partners; no new partner adoption count." }, { "id": "W24PM-PDO", "group_id": "W24PM-PDO", "company": "Petroleum Development Oman", "company_key": "Petroleum Development Oman", "department": "Production & field operations", "title": "PDO has moved ESP prediction from pilot to operating use", "kind": "context", "stage": "Operating deployment, supplier-reported; scale unknown", "operating_period": "Disclosed 21 April 2026, found in this 24 October review. The release says operating use had begun; its exact start date and duration are unknown. This is missed evidence from April, not a newly announced October deployment.", "display_period": "2026-04-21", "claim": "In its 21 April 2026 results, Weatherford reported that Petroleum Development Oman had moved ESP Predictive Analytics from pilot to operational use. The system runs within ForeSite Well Management System and combines it with PetroVisor’s machine-learning framework. The on-premise installation provides failure forecasts, run-life estimates and real-time pump-performance insight while meeting the customer’s cybersecurity requirements. The release does not say whether forecasts trigger automatic changes or how people review alerts and approve maintenance.", "economics": "No pump or well count, predictive accuracy, warning lead time, run-life improvement, avoided downtime, cost or ROI is disclosed.", "baseline": "No counterfactual, baseline or result denominator disclosed.", "ai_role": "PetroVisor machine-learning framework supports pump failure/run-life prediction. No LLM or autonomous pump control established.", "limits": "A named operating deployment is supported by Weatherford’s own statement. There is no independent PDO confirmation in this review, asset/basin or pump-population denominator, stated maintenance approval boundary or measured economic result. Regional expansion is a supplier aspiration, not established regional scale. Do not attribute Weatherford’s consolidated results to this use case.", "decision_question": "Ask which pumps and assets are live, how forecasts are validated, who acts on alerts, and whether failures or maintenance costs improved after full implementation costs.", "sources": [ { "id": "WATCH24PM-WFRD-Q1", "title": "Weatherford Announces First Quarter 2026 Results — PDO ESP analytics", "url": "https://www.weatherford.com/investor-relations/investor-news-and-events/news/news-article/?ItemID=18491", "date": "2026-04-21", "publisher": "Weatherford", "locator": "Technology Highlights → Production and Intervention; Oman / Petroleum Development Oman paragraph.", "excerpt": "moving the technology from pilot to operational use", "access": "Editor read original issuer HTML and its displayed 21 April 2026 publication date on 24 October. Supplier statement; no independent operator confirmation. Exact operating start date unknown." } ], "disposition": "background", "category": "Predictive maintenance", "relationship": "Distinct named customer deployment; related Weatherford AI-113 is a supplier product portfolio, not another PDO deployment.", "run": "24 October evening source review", "ai_ids": [ "AI-305" ], "core_company": true, "context_only": false, "evidence": "Editor read original issuer HTML and its displayed 21 April 2026 publication date on 24 October. Supplier statement; no independent operator confirmation. Exact operating start date unknown.", "asset": "Oman; exact field, basin, pump population and operating period undisclosed.", "partner": "Weatherford; ForeSite Well Management System; PetroVisor machine-learning framework." }, { "id": "W24PM-WFRD-ENERGY", "group_id": "W24PM-WFRD-ENERGY", "company": "Weatherford", "company_key": "Weatherford", "department": "Production & field operations", "title": "A rod-lift retrofit recovers energy on one U.S. well", "kind": "context", "stage": "First commercial installation, supplier-reported", "operating_period": "Disclosed 20 October 2026 in Q3 results. Exact installation/measurement dates unknown. One unnamed well, not a fleet result.", "display_period": "2026-10-20", "claim": "Weatherford reports the first commercial installation of its ForeSite Power Regenerative System retrofit on an existing U.S. rod-lift well. It captures and reuses energy generated during each pumping cycle. The supplier says the retrofit avoids replacement of the installed drive. This is energy recovery equipment; the release does not identify AI or a learning model in this installation.", "economics": "Weatherford reports over 50% energy savings on this installation. Metering method, comparison baseline, test duration and operating conditions are unspecified. No capex, total operating cost or payback is reported.", "baseline": "Comparison baseline, observation period and duty conditions unknown.", "ai_role": "No AI identified; practical non-AI energy recovery.", "limits": "Anonymous single-installation supplier claim. Do not treat the percentage as company-wide energy savings, production uplift, net cash ROI or an AI result. The word ForeSite links a brand family, not proof this equipment used the PDO predictive model.", "decision_question": "Ask for metered before/after energy under comparable duty, uptime and load; retrofit cost and maintenance burden; and the well conditions under which the result transfers.", "sources": [ { "id": "WATCH24PM-WFRD-Q3", "title": "Weatherford Announces Third Quarter 2026 Results — rod-lift energy recovery", "url": "https://www.weatherford.com/investor-relations/investor-news-and-events/news/news-article/?ItemID=18871", "date": "2026-10-20", "publisher": "Weatherford", "locator": "Technology Highlights → Production and Intervention; first U.S. ForeSite Power Regenerative System retrofit paragraph.", "excerpt": "delivering over 50% in energy savings", "access": "Editor read original issuer HTML and displayed 20 October 2026 publication date on 24 October. One unidentified U.S. well; supplier result, not independent validation." } ], "disposition": "background", "category": "Energy efficiency", "relationship": "Supplementary non-AI technology context, outside AI adoption and result counts.", "run": "24 October evening source review", "ai_ids": [], "core_company": true, "context_only": true, "evidence": "Editor read original issuer HTML and displayed 20 October 2026 publication date on 24 October. One unidentified U.S. well; supplier result, not independent validation.", "asset": "One unidentified U.S. rod-lift well; basin and operator unknown.", "partner": "Weatherford" }, { "id": "D24-MARS", "group_id": "D24-MARS", "company": "UNEP IMEO / MARS", "company_key": "UNEP IMEO / MARS", "department": "HSE & emissions", "title": "False alarms changed what the team could put into use", "kind": "negative_evidence", "stage": "Operational system after redesign; model-test limitations", "operating_period": "Preprint v2: 24 March 2026; first submitted 11 November 2025. Test uses 105 granules with known plumes and 95 without, containing 311 labeled events. Operational start dates differ by sensor.", "display_period": "2026-03-24", "claim": "MARS researchers found that testing on small image chips hid the false-alarm burden in full satellite scenes. On the same 200-granule EMIT test, a single-model variant averaged 3,565 false alarms, 213 detected events and 98 misses across five runs. Its five-model ensemble produced 1,501 false alarms, 207 detections and 104 misses. This is a trade-off, not error-free detection.", "economics": "These are test counts, not a live alert rate or measured labor savings. The paper reports 11 months of operational use; analysts verify candidate plumes before notifications. No full-cost ROI is disclosed.", "baseline": "Single-model mean across five runs versus ensemble on the same 200-granule, 311-event EMIT test. Counted objects; not percentages or rates.", "ai_role": "Computer vision ensembles for candidate plume detection; human verification retained.", "limits": "A successful redesign, not a cancelled operator project. Results span emissions sectors; no new named oil-and-gas operator adoption is established. Raw data and code were not rerun. A separate 17 October conference abstract reports a similar benchmark-to-operation gap; its full chapter was unavailable.", "decision_question": "Before scaling, how many false alarms and missed events will a team handle on the full live workload?", "sources": [ { "id": "DEEP24-MARS", "title": "Operational machine learning for remote spectroscopic detection of CH4 point sources", "url": "https://arxiv.org/html/2511.07719v2", "date": "2026-03-24", "publisher": "Růžička and coauthors / arXiv", "locator": "Version 2, 24 March 2026; sections 3.1, 5.1, 6.2 and Table 2; section 6.4 and Table 5.", "excerpt": "the models remain useful in guiding the reviewers", "access": "Editor read original full-text methods, Table 2 and operational workflow. Author preprint, listed as in review on arXiv; raw data/code not replicated. First version 11 November 2025." }, { "id": "DEEP24-SPRINGER", "title": "Reducing False Positives in Operational Remote Sensing: Lessons from Methane Plume Detection", "url": "https://doi.org/10.1007/978-3-032-41086-3_46", "date": "2026-10-17", "publisher": "Springer Nature / Discovery Science 2026", "locator": "Publisher abstract and First Online metadata; chapter pp. 721–736. Full subscription chapter not reviewed.", "excerpt": "generate substantially more operational false positives", "access": "Editor read original publisher abstract and publication metadata. Subscription full chapter, experimental tables and code not obtained; no purchase or bypass." } ], "disposition": "background", "category": "Model validation and operational workload", "relationship": "Supplementary cross-sector methane-monitoring evidence; no core adoption, result or ROI count.", "run": "24 October deeper deployment-limits review", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original full-text methods, Table 2 and operational workflow. Author preprint, listed as in review on arXiv; raw data/code not replicated. First version 11 November 2025.", "asset": "Global satellite methane screening; EMIT test granules, not a well population.", "partner": "UNEP International Methane Emissions Observatory and research coauthors" }, { "id": "D24-HAVTIL", "group_id": "D24-HAVTIL", "company": "Havtil / Norwegian petroleum operators", "company_key": "Havtil / Norwegian petroleum operators", "department": "IT, data & enterprise transformation", "title": "Some operators cannot yet account for all the AI they use", "kind": "negative_evidence", "stage": "Regulator survey finding; no named failure or incident", "operating_period": "Published 23 October 2026. Survey fieldwork dates and responding companies are not identified on the page; May 2025 guidance is earlier context.", "display_period": "2026-10-23", "claim": "Norway’s petroleum regulator says operators vary widely in how they oversee AI. Many lack a complete inventory, including AI inside supplier products. Some companies reported no AI with safety implications while describing AI in well planning, maintenance or operational advice. Havtil questions whether indirect effects on decisions are being recognized.", "economics": "No respondent count, project denominator, incident rate, cost or return is disclosed on the reviewed page.", "baseline": "Survey population and response count unknown; no adoption or failure rate calculated.", "ai_role": "Inventory and oversight of AI in planning, maintenance and operational decision support.", "limits": "This is a regulator’s interpretation of company responses, not proof of a failed deployment, an enforcement finding against every operator or measured poor ROI. It does not rank companies.", "decision_question": "Can the operating team name every AI system it relies on, including supplier features, and who owns its review?", "sources": [ { "id": "DEEP24-HAVTIL", "title": "Artificial intelligence (AI) in the petroleum industry is in need of better oversight and management", "url": "https://www.havtil.no/en/explore-technical-subjects2/technical-competence/reports-from-projects/2026/artificial-intelligence-ai-in-the-petroleum-industry-is-in-need-of-better-oversight-and-management/", "date": "2026-10-23", "publisher": "Norwegian Ocean Industry Authority (Havtil)", "locator": "Varying levels of maturity; An overview is essential for effective risk management; Prudent development and use.", "excerpt": "Many companies lack a comprehensive overview", "access": "Editor read original regulator publication and date. Underlying responses, named companies, response count and questionnaire not published on the reviewed page." } ], "disposition": "background", "category": "AI inventory and operational oversight", "relationship": "Sector governance evidence; no named operator adoption, failure count or ROI credit.", "run": "24 October deeper deployment-limits review", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original regulator publication and date. Underlying responses, named companies, response count and questionnaire not published on the reviewed page.", "asset": "Norwegian petroleum sector; operator and asset identities not disclosed.", "partner": "Norwegian Ocean Industry Authority" }, { "id": "SOL5-BRAE", "group_id": "SOL5-BRAE", "company": "Marathon Oil / West Brae (historical trial)", "company_key": "Marathon Oil / West Brae (historical trial)", "department": "Production & field operations", "title": "West Brae’s model worked, but the value case was weak", "kind": "negative_evidence", "stage": "Undated historical live-asset trial; site-specific limited value", "operating_period": "Undated historical account. Exact trial, publication and end dates unknown; not a new deployment in the rolling 24-month window.", "display_period": "Unknown", "claim": "NZTC says Intelligent Plant’s ML tool recommended valve settings at Marathon’s West Brae, but appeared to add little value on that already optimized field. The eight-well field yielded five usable verification points in four weeks and 12 in a two-year retrospective. Stable operation and larger unrelated production changes made small gains hard to establish.", "economics": "The listed 1% potential and £26.2 million industry-value scenario at 10% uptake are not realized trial benefits or net ROI. Trial costs are undisclosed.", "baseline": "One field; five live usable test points and 12 historical points, not 17 independent projects. No confirmed realized uplift.", "ai_role": "Machine learning uses historical production data to recommend valve movements.", "limits": "No cancellation, negative net cash return or later scale is established. Intelligent Plant has an undated anonymous account with similar trial details that claims benefits; we cannot confirm identical case identity or reconcile it with NZTC’s named assessment.", "decision_question": "Is there enough improvement left in the chosen asset to measure and pay for this tool?", "sources": [ { "id": "SOL5-WESTBRAE", "title": "Well Intelligence – Optimised Production", "url": "https://www.netzerotc.com/case-studies/well-intelligence-optimised-production/", "date": "Unknown", "publisher": "Net Zero Technology Centre", "locator": "Project overview; Industry value; Lessons learned. Undated historical account naming Marathon and West Brae.", "excerpt": "the application does not appear to add significant value to Marathon", "access": "Editor read original project summary and lessons. Exact trial/publication dates unknown; website copyright is not a date. Project assessment, not independently audited cash returns." }, { "id": "SOL5-WELLINT-SUPPLIER", "title": "Case Study: Enhancing Production with Well Intelligence AI Model", "url": "https://www.intelligentplant.com/case-study-well-intelligence", "date": "Unknown", "publisher": "Intelligent Plant", "locator": "Challenge and Testing; Historical Data Review; Results and Impact. Anonymous client, no publication date.", "excerpt": "This finding alone justified the deployment of Well Intelligence.", "access": "Editor read original supplier case. Anonymous account shares four-week/~8,000-bbl/day descriptors with NZTC account; same-trial identity not confirmed. No measured financial result or operator corroboration." } ], "disposition": "background", "category": "Asset fit and value verification", "relationship": "Supplementary undated historical context; Marathon Oil is not Marathon Petroleum. No core adoption/result/ROI count.", "run": "24 October five SOL research rounds", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original project summary and lessons. Exact trial/publication dates unknown; website copyright is not a date. Project assessment, not independently audited cash returns.", "asset": "West Brae; NZTC describes eight production wells and roughly 8,000 bbl/day. These are historical scope figures.", "partner": "Intelligent Plant; NZTC; Marathon as named in historical source" }, { "id": "SOL5-RECORDS", "group_id": "SOL5-RECORDS", "company": "Los Alamos / NETL well-record study", "company_key": "Los Alamos / NETL well-record study", "department": "IT, data & enterprise transformation", "title": "A well-record model picked the wrong depth field", "kind": "negative_evidence", "stage": "Research extraction test; no operating deployment established", "operating_period": "Published 30 December 2024. Historical documents and 2024-era models; no prospective deployment date.", "display_period": "2024-12-30", "claim": "A 2024 study shows why plausible extraction needs field-level checks. With a simple prompt, Llama 2 70B returned depths within 10 ft for 72 of 150 clean Colorado reports. Revised prompts reached 150/150 on the same corpus. On 10 Pennsylvania scanned records, its best prompt located 7/10 wells within 10 m and extracted 9/10 depths within 10 ft. Errors involved source/OCR signs, coordinate conversion and measured depth versus true vertical depth.", "economics": "The paper also tested Llama 3.1 405B on those 10 scans: 9/10 locations and 10/10 depths. These are threshold-based test results, not a current-model ceiling, exact transcription score or live error rate.", "baseline": "Accuracy accepts location within 10 m and depth within 10 ft. Same-corpus prompt comparison, not independently validated production reliability.", "ai_role": "OCR/text conversion plus Llama-family extraction of location and true vertical depth; prompt variations compared.", "limits": "Unequal 150- and 10-document cohorts; no independent untouched prompt-selection holdout established. Do not attribute all errors to the LLM, or infer failed operator rollout, measured savings or net ROI.", "decision_question": "Does the test check the right depth, coordinates, units and source quality before values enter an operating record?", "sources": [ { "id": "SOL5-WELLRECORDS", "title": "Information extraction from historical well records using a large language model", "url": "https://www.nature.com/articles/s41598-024-81846-5", "date": "2024-12-30", "publisher": "Ma, Santos, Lackey, Viswanathan and O’Malley / Scientific Reports", "locator": "Methods: LLMs performance evaluation; Results: Prompt engineering, Tables 2–3, chain-of-thought and comparison with other LLMs. DOI 10.1038/s41598-024-81846-5.", "excerpt": "none of the prompts resulted in completely correct extraction for the 10 Pennsylvania well records", "access": "Editor read original open-access publisher full text, metric definitions and results. Paper independently cross-checked by two SOL tracks; data/code not rerun. Peer-reviewed publication date 30 December 2024; tests use 2024-era models, not current capability." } ], "disposition": "background", "category": "Document extraction and field validation", "relationship": "Research test only. No named corporate adoption, field failure or ROI count; richer prompts and newer models improved results.", "run": "24 October five SOL research rounds", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original open-access publisher full text, metric definitions and results. Paper independently cross-checked by two SOL tracks; data/code not rerun. Peer-reviewed publication date 30 December 2024; tests use 2024-era models, not current capability.", "asset": "150 Colorado completion reports and 10 Pennsylvania records; research corpus, not 160 operating wells.", "partner": "Authors affiliated with Los Alamos National Laboratory and National Energy Technology Laboratory" }, { "id": "SOL5-PID", "group_id": "SOL5-PID", "company": "Nigeria LNG-affiliated document-retrieval study", "company_key": "Nigeria LNG-affiliated document-retrieval study", "department": "IT, data & enterprise transformation", "title": "Text search missed information in engineering diagrams", "kind": "negative_evidence", "stage": "Controlled retrieval experiment; no failed assistant deployment established", "operating_period": "Author manuscript posted 25 March 2026; proceedings marked 2026, exact issue day unknown.", "display_period": "2026-03-25", "claim": "Authors affiliated with Nigeria LNG tested four text-retrieval methods on 60 proprietary oil-and-gas documents: 20 narrative, 20 tabular and 20 piping and instrumentation diagrams. All four struggled with the diagrams. The 60 LLM-assisted queries were human-reviewed; people judged pooled search results. On diagrams, the best mean reciprocal rank was 0.106. That ranks the first relevant passage; it is not 10.6% answer accuracy.", "economics": "Across the full corpus, preserving structure led on MRR/NDCG, while recursive splitting led some MAP/F1 measures. No method won every measure. No cash return or final-answer correctness was measured.", "baseline": "Four separately indexed methods, pooled top 10 results, human relevance grades 0/1/2. Corpus and judgments not independently replicated.", "ai_role": "Azure document extraction; OpenAI text-embedding-3-large; Azure CosmosDB vector retrieval. Answer generation was not evaluated.", "limits": "Small proprietary corpus; diagram-query count and annotator agreement undisclosed. No live-user, hallucination or adoption rate. Employer affiliation does not establish that these tested configurations were deployed at Nigeria LNG.", "decision_question": "Can the system retrieve the right information from drawings and tables, as well as prose, before anyone relies on its answers?", "sources": [ { "id": "SOL5-RAG", "title": "Evaluating Chunking Strategies For Retrieval-Augmented Generation in Oil and Gas Enterprise Documents", "url": "https://arxiv.org/pdf/2603.24556", "date": "2026-03-25", "publisher": "Taiwo and Yusoff / CS&IT proceedings author manuscript", "locator": "Original 11-page PDF: methods PDF pp. 4–7; Tables 1–3 PDF pp. 8–9, printed pp. 64–65. arXiv first submitted 25 March 2026; exact proceedings publication day unknown.", "excerpt": "all four methods demonstrated limited effectiveness on P&IDs", "access": "Editor read original author PDF and visually inspected Tables 1–3. arXiv says manuscript matches CCSEIT 2026 proceedings; raw proprietary corpus and relevance labels unavailable. Author affiliation does not establish deployment or corpus ownership." } ], "disposition": "background", "category": "Retrieval quality and visual documents", "relationship": "Supplementary retrieval-component limitation, not evidence a live Nigeria LNG assistant failed. No core adoption/result/ROI count.", "run": "24 October five SOL research rounds", "ai_ids": [], "core_company": false, "context_only": true, "evidence": "Editor read original author PDF and visually inspected Tables 1–3. arXiv says manuscript matches CCSEIT 2026 proceedings; raw proprietary corpus and relevance labels unavailable. Author affiliation does not establish deployment or corpus ownership.", "asset": "60 documents and 60 queries;20 P&ID files, not an operator or asset population.", "partner": "Samuel Taiwo and Mohd Amaluddin Yusoff; Nigeria LNG Digital and Innovation Department affiliations" }, { "id": "W25AM-PTTEP-XBOT", "group_id": "W25AM-PTTEP-XBOT", "company": "PTTEP", "company_key": "PTTEP", "department": "Supply chain & logistics", "title": "PTTEP reports faster purchase-order processing with X.Bot", "kind": "context", "stage": "Operating procurement workflow; scale undisclosed", "operating_period": "Report covers 2025; exact publication day, go-live and six-month comparison dates unknown. A 9 July 2025 release independently describes procurement AI use without naming X.Bot.", "display_period": "Unknown", "claim": "PTTEP says Procurement X.Bot combines AI and automation in purchase-order processing. The annual report describes improved processing, decision support and compliance. It does not identify model, vendor, user population or approval permissions.", "economics": "Operator reports five fewer processing hours per purchase order and 50% less pending-order backlog within six months. These are system-level process measures, not AI-only cash savings.", "baseline": "Average per-PO time and six-month backlog change; baseline values and cohort unknown.", "ai_role": "AI plus automation; no LLM, autonomous purchasing or X.brain integration established.", "limits": "No PO count, baseline hours, starting backlog, comparison design, implementation costs or cash return. AI and conventional automation are not isolated. Adjacent 172-supplier event, green-spend and vessel-fuel figures do not measure X.Bot.", "decision_question": "Which steps changed, who approves orders, and do the time gains persist after all operating costs?", "sources": [ { "id": "WATCH25AM-PTTEP-XBOT", "title": "PTTEP 56-1 One Report 2025 — Procurement X.Bot", "url": "https://www.pttep.com/en/document/viewer/stream/187064/56-1-one-report-2025", "date": "Unknown", "publisher": "PTTEP", "locator": "Section 9.4.2, printed p.284 / physical PDF p.273 of 557. Procurement X.Bot paragraph; adjacent vessel and green-procurement figures are separate.", "excerpt": "average processing time by five hours per purchase order", "access": "Editor downloaded original 557-page operator PDF, read and visually inspected the complete relevant page on 25 October 2026. Report covers 2025; exact publication date and six-month evaluation dates unknown. Operator claims, not independent outcomes.", "format": "pdf" }, { "id": "WATCH25AM-PTTEP-OPEX", "title": "PTTEP organizes OpEx Day 2025, advancing operational excellence", "url": "https://www.pttep.com/en/newsroom/press-releases/1065/pttep-organizes-opex-day-2025-advancing-operational-excellence", "date": "2025-07-09", "publisher": "PTTEP", "locator": "Press release, procurement AI sentence in operational-excellence examples.", "excerpt": "application of AI to streamline procurement processes", "access": "Editor read original issuer release and displayed 9 July 2025 date. It supports procurement AI use, not X.Bot identity or its measured results.", "type": "Operator press release" } ], "disposition": "background", "category": "Procurement AI and automation", "relationship": "Distinct from AI-245 internal audit and AI-297 enterprise engine. No evidence that X.Bot is one of its eight planned agents.", "run": "25 October morning source review", "ai_ids": [ "AI-306" ], "core_company": true, "logo_available": true, "context_only": false, "evidence": "Editor downloaded original 557-page operator PDF, read and visually inspected the complete relevant page on 25 October 2026. Report covers 2025; exact publication date and six-month evaluation dates unknown. Operator claims, not independent outcomes.", "asset": "Procurement process; geography, business-unit and supplier coverage unknown.", "partner": "Procurement X.Bot; supplier/model not named." }, { "id": "W25AM-BKV-RUNWAY", "group_id": "W25AM-BKV-RUNWAY", "company": "BKV Corporation", "company_key": "BKV Corporation", "department": "IT, data & enterprise transformation", "title": "BKV rebuilt its field-data system around how operators work", "kind": "context", "stage": "Operating SCADA foundation; not AI", "operating_period": "Go-live 19 November 2025. Report letter is dated September 2026; exact report publication day unknown.", "display_period": "Unknown", "claim": "BKV consolidated four inherited SCADA/CygNet environments. Its Barnett platform went live 19 November 2025. Field staff reviewed terminology and screens. Peer-led training and field ride-alongs supported the change.", "economics": "BKV reports 2.5 million data points standardized, over 250,000 obsolete points removed, polling 60 to 15 minutes, and no production downtime. Acquisition integration reportedly fell from 6–8 months to 6–8 weeks.", "baseline": "Four legacy environments; timings are reported process comparisons.", "ai_role": "Conventional operating-data infrastructure; not AI adoption.", "limits": "Issuer-reported measures; no costs, controlled evaluation, cash benefit or AI use established. About 1,100 Bedrock wells were positioned for onboarding, not confirmed live at the go-live date.", "decision_question": "Does the common data model survive the next acquisition, and how much ongoing support does it need?", "sources": [ { "id": "WATCH25AM-BKV-RUNWAY", "title": "BKV 2025 Sustainability Report — Project Runway", "url": "https://www.bkv.com/2025-sustainability-report-governance", "date": "Unknown", "publisher": "BKV Corporation", "locator": "Governance: Project Runway; Informed by field operations; Collaboration beyond implementation.", "excerpt": "the consolidated Barnett platform went live on November 19, 2025", "access": "Editor read original operator page on 25 October 2026. Publication day not displayed; report landing page CEO letter dated September 2026. Metrics are issuer-reported." }, { "id": "WATCH25AM-BKV-REPORT", "title": "BKV 2025 Sustainability Report — letter date", "url": "https://www.bkv.com/2025-sustainability-report", "date": "Unknown", "publisher": "BKV Corporation", "locator": "Letter from CEO footer: September 2026.", "excerpt": "Letter from the CEO | September 2026", "access": "Editor read original report landing page; letter month is not exact report publication date.", "type": "Operator report landing page" } ], "disposition": "background", "category": "Operating-system transformation", "relationship": "Supplementary non-AI operating foundation; not a new AI register profile.", "run": "25 October morning source review", "ai_ids": [], "core_company": false, "logo_available": true, "context_only": true, "evidence": "Editor read original operator page on 25 October 2026. Publication day not displayed; report landing page CEO letter dated September 2026. Metrics are issuer-reported.", "asset": "Barnett Shale; broader portfolio and acquisition populations differ.", "partner": "SCADA/CygNet; external implementation partner unnamed." }, { "id": "W25AM-HARBOUR-COUPA", "group_id": "W25AM-HARBOUR-COUPA", "company": "Harbour Energy", "company_key": "Harbour Energy", "department": "Supply chain & logistics", "title": "Harbour documents the exceptions in its supplier invoice workflow", "kind": "context", "stage": "Documented supplier transaction channel; not AI", "operating_period": "Guide version 4, June 2025; exact day, system start and entity rollout unknown.", "display_period": "2025-06", "claim": "Harbour’s June 2025 Coupa guide covers purchase orders, confirmations, invoices and status tracking. It documents access roles, drafts, receipt matching, disputes and credit/reissue paths. The guide points to ex-Wintershall Dea materials; a separate channel uses SAP Business Network.", "economics": "No measured time, error, cash saving or ROI result. Free supplier access does not establish the operator’s total cost.", "baseline": "Published process instructions, not before/after evaluation.", "ai_role": "Supplier process digitization; no AI established.", "limits": "Do not extend the guide’s all-new-PO wording to every Harbour entity or infer that Coupa replaced SAP. Exception instructions do not prove high failure rates.", "decision_question": "Where do invoices stall, which exceptions require people, and which supplier channel applies?", "sources": [ { "id": "WATCH25AM-HARBOUR-COUPA", "title": "Harbour Energy Coupa Supplier Portal FAQ, version 4", "url": "https://www.harbourenergy.com/media/jbznhqcy/10-coupa-faq-english-harbour.pdf", "date": "2025-06", "publisher": "Harbour Energy", "locator": "PDF p.1 version 4, June 2025 and PO process; pp.2–4 permissions, invoices, receipts and disputes; p.5 refers to ex-Wintershall Dea vendor guides.", "excerpt": "All new purchase orders of Harbour Energy are generated through the Coupa platform.", "access": "Editor read original 5-page operator PDF. Exact revision day, go-live and legal-entity scope unknown. The linked vendor page separately retains SAP Business Network.", "format": "pdf" }, { "id": "WATCH25AM-HARBOUR-VENDORS", "title": "Harbour vendor relations — distinct supplier channels", "url": "https://www.harbourenergy.com/vendor-relations/", "date": "Unknown", "publisher": "Harbour Energy", "locator": "Separate sections: vendors using SAP Business Network; ex-Wintershall Dea vendors.", "excerpt": "Applicable to ex-Wintershall Dea vendors", "access": "Editor read original operator page on 25 October 2026. Undated current channel guidance; SAP start November 2022 is older context, not new AI.", "type": "Operator supplier webpage" } ], "disposition": "background", "category": "Procure-to-pay foundation", "relationship": "Supplementary administrative workflow, not AI adoption or failed deployment.", "run": "25 October morning source review", "ai_ids": [], "core_company": false, "logo_available": true, "context_only": true, "evidence": "Editor read original 5-page operator PDF. Exact revision day, go-live and legal-entity scope unknown. The linked vendor page separately retains SAP Business Network.", "asset": "Affected supplier-channel scope; no asset, user or invoice denominator.", "partner": "Coupa; separate SAP Business Network channel." }, { "id": "W25AM-COP-GEP", "group_id": "W25AM-COP-GEP", "company": "ConocoPhillips", "company_key": "ConocoPhillips", "department": "Supply chain & logistics", "title": "ConocoPhillips shows how suppliers enter orders and invoices", "kind": "context", "stage": "Supplier workflow documented; transition completion unverified", "operating_period": "Updated December 2024; January 2025 transition target. Undated live guidance still uses that future-tense wording; completion by business unit unknown.", "display_period": "2024-12", "claim": "ConocoPhillips’ December 2024 guide chose GEP SMART for supplier registration, PO acknowledgement and invoicing. Suppliers register, accept PO terms, create invoices or service confirmations and inspect remittance. Current guidance offers portal, integration and Enverus submission routes.", "economics": "Faster approvals and better order accuracy are intended benefits; no measured result or ROI.", "baseline": "Process diagram and target, not measured operating comparison.", "ai_role": "Digital procurement and invoice handling; no AI disclosed.", "limits": "No transaction population, costs or actual rollout completion. Supplier fee waivers do not establish operator cost. An available Enverus route is not exclusive-platform adoption.", "decision_question": "Which units and invoice routes are live, and who owns the exceptions?", "sources": [ { "id": "WATCH25AM-COP-GEP", "title": "ConocoPhillips GEP SMART Introduction", "url": "https://static.conocophillips.com/files/resources/gep-smart-introduction_rusa-bu-website.pdf", "date": "2024-12", "publisher": "ConocoPhillips", "locator": "PDF p.1 updated December 2024; p.3 transition target; p.5 intended benefits; p.6 supplier invoice flow.", "excerpt": "all business units should have transitioned to GEP SMART", "access": "Editor read original 7-page issuer PDF. January 2025 is a target, not verified unit-by-unit completion. Exact revision day unknown.", "format": "pdf" }, { "id": "WATCH25AM-COP-VENDORS", "title": "ConocoPhillips technical upgrades to supplier systems", "url": "https://vendors.conocophillips.com/supplier-guide/technical-upgrades-to-supplier-systems/", "date": "Unknown", "publisher": "ConocoPhillips", "locator": "GEP portal/EDI and Enverus routes; supplier training and implemented SSIS support.", "excerpt": "Exceptions to the invoicing process are identified", "access": "Editor read original live supplier page on 25 October 2026. Page retains future-tense January 2025 language, so it cannot verify completion date. No publication date displayed.", "type": "Operator supplier webpage" } ], "disposition": "background", "category": "Procure-to-pay foundation", "relationship": "Supplementary platform/process context, separate from existing AI records.", "run": "25 October morning source review", "ai_ids": [], "core_company": false, "logo_available": true, "context_only": true, "evidence": "Editor read original 7-page issuer PDF. January 2025 is a target, not verified unit-by-unit completion. Exact revision day unknown.", "asset": "Supplier process; geography and business-unit rollout populations unknown.", "partner": "GEP SMART; Enverus alternative channel; Atlassian supplier-support portal." }, { "id": "W25PM-ECO-AIOPS", "group_id": "W25PM-ECO-AIOPS", "company": "Ecopetrol", "company_key": "Ecopetrol", "department": "IT, data & enterprise transformation", "title": "Ecopetrol reports IT gains while its wider AI program still faces data limits", "kind": "context", "stage": "AI in IT operations adopted; wider AI maturity gaps and a 2027 roadmap reported", "operating_period": "The report covers 2025; exact publication day and AIOps start/evaluation dates are unknown. The 2027 target is prospective.", "display_period": "2026 (exact publication day unknown)", "claim": "Ecopetrol says using AI in IT operations raised critical-service availability to 99.52% and generated more than US$1.5 million in savings. The same page says the AI ecosystem maturity review found limits in data access and autonomy. A broader operating model with integrated AI remains a 2027 goal.", "economics": "Company-reported availability level and savings; starting availability, service population, cost perimeter and savings period are not specified. An adjacent 40% digital self-service resolution rate is separate and is not explicitly attributed to AIOps.", "baseline": "99.52% is an availability level, not a 99.52% improvement. Baseline and measurement window unknown.", "ai_role": "AIOps is explicitly AI for IT operations; the report does not identify models, vendors or an LLM. Self-service and infrastructure upgrades are separate.", "limits": "No all-in cost, cash reconciliation, comparison design or complete net ROI. The US$1.5 million-plus may overlap the existing AI-147 portfolio benefits; do not add them. Neither 160 digital initiatives nor more than 100 operating solutions is a count of AI deployments.", "decision_question": "Which services improved, what changed against the prior baseline, and how much of the saving remains after running costs?", "sources": [ { "id": "SW6-004", "title": "Ecopetrol 2025 Integrated Management Report — digital transformation and AIOps", "url": "https://files.ecopetrol.com.co/web/esp/aga2026/informe-integrado-gestion-informe-anual-gc.pdf", "date": "2026 (exact publication day unknown)", "publisher": "Ecopetrol", "locator": "Printed p.314 / physical PDF p.315 of 482, Transformación Digital. AIOps, self-service and AI maturity are separate passages.", "excerpt": "la disponibilidad de los servicios críticos de TI al 99.52%", "access": "Editor downloaded the original report, read the complete relevant page and visually inspected it on 25 October 2026. Reuses existing source SW6-004; earlier claim-level reviews remain separate.", "format": "pdf", "existing": true } ], "disposition": "background", "category": "IT reliability and AI rollout limits", "relationship": "Further context for AI-147, not another counted core profile. AIOps results must not be added to portfolio benefits or assigned to the upstream planner.", "run": "25 October evening source review", "ai_ids": [ "AI-147" ], "core_company": true, "logo_available": true, "context_only": true, "evidence": "Editor downloaded the original report, read the complete relevant page and visually inspected it on 25 October 2026. Reuses existing source SW6-004; earlier claim-level reviews remain separate.", "asset": "Critical IT services; business-unit, service, user and asset populations unspecified.", "partner": "No AIOps supplier or model named." }, { "id": "W25PM-YPF-EKONS", "group_id": "W25PM-YPF-EKONS", "company": "YPF", "company_key": "YPF", "department": "Refining, LNG & process operations", "title": "YPF’s fuel-blending tool supplies estimates to refinery operators", "kind": "context", "stage": "Supplier-reported use at one refinery; still being adjusted", "operating_period": "The interview describes application starting March–April 2026, about six months of implementation and continuing adjustments. A syndicated copy is dated 11 September 2026; the retrieved original does not display its exact date.", "display_period": "Unknown", "claim": "A Boston Consulting Group (BCG) project lead describes Ekons Matrix AI in use at YPF’s La Plata refinery in Argentina. AI and process-simulation rules estimate the properties of streams being mixed into fuel. The estimates support control-room staff; autonomous control is not established.", "economics": "The supplier says blending execution time could fall by up to 50%. This is a potential maximum, without a measured achieved average, comparison cohort or observation period.", "baseline": "No measured before/after cohort; up to 50% is not an observed average.", "ai_role": "AI plus process simulation; no LLM disclosed.", "limits": "Original interview with the supplier project lead, not an operator filing or independent result. No realized saving, quality/error measure, cost or net ROI. No stream, tank, blend, user or throughput denominator. Further rollout is an ambition. Separate from the earlier YPF cataloging and inspection profile.", "decision_question": "Can YPF show achieved blend-time and quality results over enough batches to separate the tool from other operating changes?", "sources": [ { "id": "WATCH25PM-YPF-EKONS", "title": "YPF refinery blending — interview with BCG project lead Roberto Rodrigo", "url": "https://mase.lmneuquen.com/empresas/ia-ypf-la-tecnologia-que-gano-el-premio-digital-del-ano-y-ya-se-aplica-la-refineria-la-plata-n1253008", "date": "Unknown", "publisher": "Más Energía / LM Neuquén; Martina Mongelluzzo", "locator": "Sections Del laboratorio a la operación en tiempo real and Argentina, el primer caso de implementación.", "excerpt": "la solución puede reducir hasta un 50% el tiempo de ejecución de los blending", "access": "Editor read the original interview. The exact date is not displayed in its retrieved body; a syndicated copy is dated 11 September 2026. Original named supplier interview, not operator confirmation or independent performance validation." } ], "disposition": "background", "category": "Refinery decision support", "relationship": "Distinct from AI-149 contract cataloging, customer information and refinery inspection. Linked as company context only; it does not change that profile’s outcomes or stage.", "run": "25 October evening source review", "ai_ids": [], "core_company": true, "logo_available": true, "context_only": true, "evidence": "Editor read the original interview. The exact date is not displayed in its retrieved body; a syndicated copy is dated 11 September 2026. Original named supplier interview, not operator confirmation or independent performance validation.", "asset": "La Plata refinery, Argentina; one implementation described.", "partner": "BCG / Ekons Matrix AI and YPF, as described in the interview." }, { "id": "W25PM-DIXSTONE-IFS", "group_id": "W25PM-DIXSTONE-IFS", "company": "Dixstone", "company_key": "Dixstone", "department": "IT, data & enterprise transformation", "title": "Dixstone selects shared project and fleet software; go-live remains unverified", "kind": "context", "stage": "Software selected; implementation completion and AI use unverified", "operating_period": "Selection announcement dated 9 December 2025. Go-live and implementation milestones are not disclosed.", "display_period": "2025-12-09", "claim": "IFS says Dixstone selected IFS Cloud to manage project finances and fleet maintenance. The intended system brings budgets, schedules, resources and asset data together. The release proposes predictive maintenance for rigs, vessels and platforms.", "economics": "No measured operating result, cost or return. Ten countries and more than 2,200 professionals describe the stated company footprint, not active users, sites live or AI adoption.", "baseline": "Selection and intended scope, without a measured operating comparison.", "ai_role": "Industrial AI is supplier positioning; no specific deployed AI function is established.", "limits": "Vendor announcement, not proof of operating AI or delivered savings. No model, asset rollout, approval boundary or net ROI. Dixstone is a Perenco affiliate consolidating offshore services; this is not a Perenco E&P field deployment.", "decision_question": "Which assets and workflows are live, what still needs implementation, and where does AI actually change the work?", "sources": [ { "id": "WATCH25PM-DIXSTONE-IFS", "title": "Dixstone selects IFS Cloud for offshore services", "url": "https://www.ifs.com/pl/insights/news/dixstone-selects-ifs-cloud-to-power-global-offshore-operations", "date": "2025-12-09", "publisher": "IFS", "locator": "Dated release: selection, project controls and fleet maintenance paragraphs; About Dixstone separates affiliate status from Perenco E&P.", "excerpt": "Dixstone has selected IFS Cloud", "access": "Editor read the original IFS release dated 9 December 2025. A vendor selection announcement with a customer quote; future capabilities and company footprint are not completed rollout or outcomes." } ], "disposition": "background", "category": "Offshore-services software foundation", "relationship": "Supplementary services-company transformation context, not new core AI adoption or Perenco field performance.", "run": "25 October evening source review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the original IFS release dated 9 December 2025. A vendor selection announcement with a customer quote; future capabilities and company footprint are not completed rollout or outcomes.", "asset": "Offshore-services rigs, vessels and platforms; individual rollout assets unspecified.", "partner": "IFS Cloud; Dixstone is described as a Perenco affiliate and Perrodo family company." }, { "id": "RESULTS-PERENCO", "group_id": "RESULTS-PERENCO", "company": "Perenco", "company_key": "Perenco", "department": "Drilling & completions", "title": "Perenco reports faster drilling across three wells", "kind": "context", "stage": "Supplier-reported operating deployment", "operating_period": "2025 three-well campaign. Exact publication day and campaign dates unknown.", "display_period": "Unknown", "claim": "SLB reports a 19% increase in rate of penetration in Perenco’s 2025 offshore Congo campaign. DrillOps and Neuro automated drilling and directional work; SLB describes an automatic safe-state response to a pack-off event. General override and approval rules are not supplied.", "economics": "Three wells; 97% of on-bottom operations automated. These are speed and control measures, not cash return.", "baseline": "Manual operations are discussed; raw ROP baseline and comparison matching unknown.", "ai_role": "AI-driven drilling automation; no LLM identified.", "limits": "Raw drilling-speed baseline, matched offset population, complete costs and AI-only contribution unknown.", "decision_question": "Did the gain hold on more wells after accounting for geology, equipment and full deployment costs?", "sources": [ { "id": "RESULTS-PERENCO", "title": "Perenco enhances drilling efficiency with advanced automation solutions", "url": "https://www.slb.com/resource-library/case-study-with-navigation/di/perenco-enhances-drilling-efficiency-with-advanced-automation-solutions", "date": "Unknown", "publisher": "SLB", "locator": "Summary and Results; three-well 2025 campaign.", "excerpt": "achieved a 19% increase in rate of penetration", "access": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "format": "html" } ], "disposition": "background", "category": "Operating result", "relationship": "Supplementary evidence; not a new core-profile, adoption or numerical-result count. Calendar timing and evidence quality remain explicit.", "run": "25 October operating-results review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "asset": "Offshore Republic of the Congo; individual assets unnamed.", "partner": "SLB / DrillOps / Neuro" }, { "id": "RESULTS-WAFI", "group_id": "RESULTS-WAFI", "company": "Wafi Energy Pakistan", "company_key": "Wafi Energy Pakistan", "department": "Finance & accounting", "title": "Invoice handling fell from about five minutes to under one", "kind": "context", "stage": "Supplier-reported operating deployment", "operating_period": "Publication and operating calendar dates unknown; results observed within weeks of go-live. Twelve weeks describes implementation, not the evaluation period.", "display_period": "Unknown", "claim": "SpendConsole reports invoice processing falling from about five minutes to under one in automated scenarios at Wafi Energy Pakistan. AI document capture, rules and SAP workflows handle routine invoices; finance staff handle exceptions. Autonomous payment approval is not established.", "economics": "The vendor separately reports 50–70% productivity improvement and full go-live in about 12 weeks.", "baseline": "Approximately five minutes of manual handling versus under one in automated scenarios; not every invoice.", "ai_role": "AI document processing plus rules and process changes; effects not isolated.", "limits": "Invoice volume, automated-scenario share, precise measurement window and full costs unknown. This is the Pakistan Shell-brand licensee, not Shell-wide adoption.", "decision_question": "What share of invoices qualifies, and how much staff time is actually released after exception handling?", "sources": [ { "id": "RESULTS-WAFI", "title": "From manual accounts payable to AI-powered finance in 12 weeks", "url": "https://spendconsole.ai/success-stories/from-manual-accounts-payable-to-ai-powered-finance-in-12-weeks/", "date": "Unknown", "publisher": "SpendConsole", "locator": "Client profile; solution; results; automated-scenario qualification.", "excerpt": "under a minute in automated scenarios", "access": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "format": "html" } ], "disposition": "background", "category": "Operating result", "relationship": "Supplementary evidence; not a new core-profile, adoption or numerical-result count. Calendar timing and evidence quality remain explicit.", "run": "25 October operating-results review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "asset": "Wafi Energy Pakistan finance function.", "partner": "SpendConsole / SAP" }, { "id": "RESULTS-APOLLO", "group_id": "RESULTS-APOLLO", "company": "Apollo Resources / unnamed SENM operator", "company_key": "Apollo Resources / unnamed SENM operator", "department": "Production & field operations", "title": "A chemical-treatment redesign cut consumption without identified AI", "kind": "context", "stage": "Supplier-reported operating deployment", "operating_period": "Thirty-day observation; publication and operating calendar dates unknown.", "display_period": "Unknown", "claim": "Apollo reports 65% lower chemical consumption and $210,000 lower monthly H2S treatment cost at an unnamed southeastern New Mexico facility. A flow-meter-linked controller, new chemistry and a relocated injection point changed treatment. Key operator personnel received online write access.", "economics": "Zero out-of-spec H2S events during a 30-day observation. The monthly cost claim is not annualized here.", "baseline": "Prior treatment versus redesigned treatment; comparable throughput and pre-period observation length unknown.", "ai_role": "No AI identified; useful comparison for the same operating problem.", "limits": "Population, throughput, cost calculation, installation costs and longer-term durability unknown. New chemistry and equipment prevent attributing the result to software alone.", "decision_question": "How much could treatment redesign achieve before adding AI, and what does it cost to sustain?", "sources": [ { "id": "RESULTS-APOLLO", "title": "HSV-01 chemical treatment case study", "url": "https://apolloresourcesllc.net/apollo-resources-hsv-01-oil-treating-chemistry-effectively-eliminates-30000-ppm-of-h2s-in-senm/", "date": "Unknown", "publisher": "Apollo Resources", "locator": "Solution and Results; 30-day observation.", "excerpt": "Chemical consumption decreased by 65%", "access": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "format": "html" } ], "disposition": "background", "category": "Non-AI comparison", "relationship": "Supplementary evidence; not a new core-profile, adoption or numerical-result count. Calendar timing and evidence quality remain explicit.", "run": "25 October operating-results review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "asset": "Unnamed facility, southeastern New Mexico.", "partner": "Apollo Resources" }, { "id": "RESULTS-WEATHERFORD", "group_id": "RESULTS-WEATHERFORD", "company": "Weatherford / unnamed trial operators", "company_key": "Weatherford / unnamed trial operators", "department": "Production & field operations", "title": "Targeted chemical placement is another route to less waste", "kind": "context", "stage": "Supplier-reported operating deployment", "operating_period": "Paper dated 16 September 2025. Trial dates and evaluation duration unknown.", "display_period": "2025-09-16", "claim": "A Weatherford-hosted technical-paper abstract reports 65% less chemical use per well and 52% lower operating expense in capillary-injection field trials. Simulation-guided placement, a capillary string and an injection valve deliver chemicals to the treatment point. No AI is identified.", "economics": "Results are from the public abstract of SPE-227643-MS; the full paper was not reviewed.", "baseline": "Traditional cyclic treatment; raw volumes and cost baseline not supplied.", "ai_role": "No AI identified; precision placement and engineering comparison.", "limits": "Operator, geography, well population, raw baseline, cost perimeter and installation costs unknown. This does not establish all-in ROI or scaled deployment.", "decision_question": "Does targeted placement outperform surface optimization after installation and maintenance costs?", "sources": [ { "id": "RESULTS-WEATHERFORD", "title": "Maximizing chemical efficiency with rigless precision-based capillary injection", "url": "https://www.weatherford.com/documents/papers/2025/maximizing-chemical-efficiency-and-reducing-environmental-footprint-with-rigless,-precision-based-ca/", "date": "2025-09-16", "publisher": "Weatherford / SPE", "locator": "Public abstract, SPE-227643-MS; field-trial results.", "excerpt": "a 65% reduction in chemical usage per well", "access": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "format": "html" } ], "disposition": "background", "category": "Non-AI comparison", "relationship": "Supplementary evidence; not a new core-profile, adoption or numerical-result count. Calendar timing and evidence quality remain explicit.", "run": "25 October operating-results review", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the relevant original publisher page on 25 October 2026. Results remain source-reported; no independent outcome validation.", "asset": "Unnamed field trials; geography unspecified.", "partner": "Weatherford" }, { "id": "D26-TOPTAL", "group_id": "D26-TOPTAL", "company": "Toptal / unnamed oil-and-gas technology company", "company_key": "Toptal / unnamed oil-and-gas technology company", "department": "Land & legal", "title": "A title model needed attorney-grounded regression tests", "kind": "context", "stage": "Provider-reported technical evaluation; live test population unverified", "operating_period": "Publication, operating and evaluation dates unknown.", "display_period": "Unknown", "claim": "Toptal reports false positives falling from about 27% to 2%, with recall about 93%; conveyance-party capture rose from about 85% to 96%. A reference database of more than 2,000 attorney-validated answers supports regression tests before releases across a platform handling more than 200,000 land documents.", "economics": "The source does not give evaluated decision counts, class balance or an untouched test design. Document-universe size is not the denominator of these rates.", "baseline": "Approximately 27% versus 2% false-positive rates; same-cohort comparison and denominator unspecified.", "ai_role": "LLM title determination plus legal rules, SQL and knowledge-graph concepts.", "limits": "Anonymous client, undated provider case. No independently confirmed live error rate, realized labor saving, full cost or ROI. Reduced false positives does not eliminate human title review.", "decision_question": "How does the error rate hold on unseen deeds, and who signs off on ownership conclusions?", "sources": [ { "id": "D26-TOPTAL", "title": "Mineral-title evaluation and regression testing", "url": "https://www.toptal.com/case-study/oil-gas-tech-firm-improves-ai-mineral-title-accuracy", "date": "Unknown", "publisher": "Toptal", "locator": "Challenge; Ground-truth AI Evaluation; Outcome. No publication/evaluation date displayed.", "excerpt": "approximately 27% to 2% while maintaining roughly 93% recall", "existing": false, "format": "html", "access": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated." } ], "disposition": "background", "category": "Technical test", "relationship": "Supplementary source review; no new core deployment, adoption, outcome or ROI count.", "run": "26 October results and setbacks", "ai_ids": [], "core_company": false, "logo_available": false, "context_only": true, "evidence": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated.", "asset": "US land records; anonymous technology provider, no named operator.", "partner": "Toptal" }, { "id": "D26-SLB-DDR", "group_id": "D26-SLB-DDR", "company": "SLB", "company_key": "SLB", "department": "Drilling & completions", "title": "High overall accuracy hid weaker rare-event detection", "kind": "context", "stage": "Published patent-application technical examples; no verified commercial rollout", "operating_period": "Application published 5 March 2026; exact underlying evaluation dates unknown.", "display_period": "2026-03-05", "claim": "An SLB patent application reports 89% overall accuracy but 44% equal-class recall for its oil-and-gas GPT-2 comparator. The filing describes minority-class problems in drilling-risk classification. Customized models perform better in its examples, but the results are not a current-model ceiling.", "economics": "Table 15 reports the two different measures; 44% is not overall recall on all remarks. Exact test population and independent validation for that row are not established.", "baseline": "Different metrics for one comparator, not a before/after improvement.", "ai_role": "Classifies risks in daily drilling remarks using language models; engineering review and operating permissions not established.", "limits": "Applicant-authored technical examples, not an independently validated field outcome. Other examples use differing cohorts and later model configurations. No measured reduction in drilling incidents or complete ROI.", "decision_question": "Does the evaluation give rare, costly events enough weight?", "sources": [ { "id": "D26-SLB-DDR", "title": "AI approach for drilling operation insights — US 20260063025 A 1", "url": "https://patents.google.com/patent/US20260063025A1/en", "date": "2026-03-05", "publisher": "Schlumberger Technology Corporation / published US patent application", "locator": "Table 15 and section 5, Model Performance Comparative Analysis; published application, not a granted-patent or commercial-deployment claim.", "excerpt": "especially for minority class when the training data is insufficient", "existing": false, "format": "html", "access": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated." } ], "disposition": "background", "category": "Technical test", "relationship": "Supplementary source review; no new core deployment, adoption, outcome or ROI count.", "run": "26 October results and setbacks", "ai_ids": [], "core_company": true, "logo_available": true, "context_only": true, "evidence": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated.", "asset": "Drilling-report examples; no named customer or live asset tied to the 89%/44% row.", "partner": "Schlumberger Technology Corporation / published US patent application" }, { "id": "D26-SNAM", "group_id": "D26-SNAM", "company": "Snam / Engineering Group", "company_key": "Snam / Engineering Group", "department": "IT, data & enterprise transformation", "title": "Complex plant drawings were harder than simple ones", "kind": "context", "stage": "Operator/provider research evaluation; broad production scale not established", "operating_period": "Preprint 5 November 2025; evaluation and operating calendar dates unknown.", "display_period": "2025-11-05", "claim": "The Snam/Engineering paper reports 42.4% relationship recall at the top 100 predictions; a separate final-task table reports 95% component identification and 90% section assignment. The authors say complex systems remain difficult, although simpler systems work better. This constrains claims about automatic plant digitization.", "economics": "Relationship recall and final component/section measures use different tasks and denominators. The roughly 1,500-ReMi document collection is not a disclosed count of live automated plants.", "baseline": "Table 2 relationship recall@100=.424; Table 3 final-task measures are different quantities.", "ai_role": "OCR, vision/language models, scene-graph reasoning and constrained optimization support MGM users.", "limits": "Authors provide technical tests, not realized time savings or full-cost ROI. Do not merge abstract summary accuracy with task-specific tables or label this a cancelled rollout.", "decision_question": "Which drawings still need manual reconstruction, and how long does correction take?", "sources": [ { "id": "M29-006", "title": "Case Study: Transformer-based Solution for the Automatic Digitization of Gas Plants", "url": "https://arxiv.org/html/2511.08609v1", "date": "2025-11-05", "publisher": "Snam / Engineering Group", "locator": "Sections 3.1,4(Tables 1–3) and 5; top 100 relationship recall and complex-system limitation.", "excerpt": "", "existing": true, "format": "html", "access": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated." } ], "disposition": "background", "category": "Technical test", "relationship": "Supplementary source review; no new core deployment, adoption, outcome or ROI count.", "run": "26 October results and setbacks", "ai_ids": [ "AI-208" ], "core_company": true, "logo_available": true, "context_only": true, "evidence": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated.", "asset": "Snam gas-plant documentation; Italy; approximately 1,500 ReMi in the provided collection.", "partner": "Snam / Engineering Group" }, { "id": "D26-TOTAL", "group_id": "D26-TOTAL", "company": "TotalEnergies", "company_key": "TotalEnergies", "department": "Refining, LNG & process operations", "title": "One useful warning model did not make every coker use case useful", "kind": "context", "stage": "Advisory pilot; one use case reportedly not retained, other work continued", "operating_period": "Joint pilot began October 2024; drum/spalling work July 2025; report 11 June 2026. Steam work began May 2025 and closed a year later; reason for closure not stated.", "display_period": "2026-06-11", "claim": "A named TotalEnergies engineer said a 75%-accuracy drum-level model was not retained because switching also depended on conditions outside its scope. The same sponsored conference report describes 10–18 minutes of steam-warning lead time and at least two acted-on alerts. These concern another use case.", "economics": "No test denominator or definition for 75% accuracy. At least two acted-on alerts is not a total-alert count, avoided-trip count or reliability rate.", "baseline": "Different use cases have different populations; expected benefits are not measured achieved results.", "ai_role": "Advisory alerts and operator decisions; no autonomous process write authority established.", "limits": "Named remarks in sponsored conference coverage; original slides and later company confirmation not located. Other uses continued. No quantified loss, avoided flaring, downtime benefit or full costs; do not call the whole pilot a failure.", "decision_question": "Did the prediction answer the actual operating decision?", "sources": [ { "id": "WATCH16AM-TOTAL-DRUM", "title": "Honeywell AI pilot aids coker unit operations at TotalEnergies refinery", "url": "https://www.controlglobal.com/show-coverage/honeywell-users-group/article/55383668/honeywell-ai-pilot-aids-coker-unit-operations-at-totalenergies-refinery", "date": "2026-06-11", "publisher": "Control Global / Honeywell Users Group coverage", "locator": "Steam perturbance, drum cycling, heater spalling and alarm-decision-support sections; Thomas Klein remarks.", "excerpt": "", "existing": true, "format": "html", "access": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated." } ], "disposition": "background", "category": "Use case not retained", "relationship": "Supplementary source review; no new core deployment, adoption, outcome or ROI count.", "run": "26 October results and setbacks", "ai_ids": [ "AI-207" ], "core_company": true, "logo_available": true, "context_only": true, "evidence": "Editor read the original specified passage on 26 October 2026. Publisher/author-reported evidence; outcomes not independently validated.", "asset": "Port Arthur refinery delayed coker, Texas; alarm guidance separately covered more than 300 tags.", "partner": "Control Global / Honeywell Users Group coverage" } ], "excluded": [ { "id": "R1-GL-06", "company": "PETRONAS / Malaysia Petroleum Management (MPM)", "title": "Estuary Cluster shallow-water subsea development concept for marginal fields", "category": "field development / subsea architecture and infrastructure reuse", "kind": "new_initiative", "ai_role": "None disclosed.", "asset": "Lerek, Korbu and Diwangsa fields in the Malay Basin offshore Peninsular Malaysia.", "stage": "PSC award and technology-led development concept only; no operating deployment or defined technical configuration disclosed.", "operating_period": "PETRONAS page labelled 2026 Media Release - 11 Sep; body dateline says 2026-09-09. Preserve this page/body date discrepancy.", "claim": "Capex/footprint reduction, accelerated production and infrastructure reuse are expected benefits, not measured outcomes. Do not import Mutiara cluster's separate schedule or seismic handover.", "economics": "No capital estimate or savings target disclosed.", "baseline": "Conventional development concepts are the qualitative comparator; no named baseline, cost estimate, cycle-time or environmental delta disclosed.", "limits": "This is a lease award and development concept, not a technology deployment or proven development design. The source withholds the technical configuration and measurable economics. Do not claim field commercialization or first oil/date without newer evidence.", "relationship": "Concept-stage cluster lacks sufficiently firm, project-specific performance or economics; revisit at sanction or named deployment.", "decision_question": "What are reserves, well/facility design, capex, reuse share, schedule and cost-per-barrel versus a named conventional concept?", "company_key": "PETRONAS", "run": "Three-round scope review", "disposition": "hold", "sources": [ { "title": "PETRONAS Progresses Malaysia's Upstream Development with Estuary Cluster PSC Award and Mutiara Cluster Seismic Data Handover", "publisher": "PETRONAS Global / Malaysia Petroleum Management", "date": "2026-09-11 page label; 2026-09-09 body dateline", "url": "https://www.petronas.com/media/media-releases/petronas-progresses-malaysias-upstream-development-estuary-cluster-psc-award", "locator": "Estuary PSC, asset list, shallow-water concept and expected advantages, lines 129-140", "access": "Issuer page opened; full text accessible", "supports": "Award, three fields, geography, technology-led shallow-water concept and claims framed as expectations." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2026-09-09 body dateline; page label 2026-09-11", "url": "https://www.petronas.com/media/media-releases/petronas-progresses-malaysias-upstream-development-estuary-cluster-psc-award", "locator": "Estuary PSC award, three fields, shallow-water development concept and expected benefits; separate Mutiara paragraph", "access": "PETRONAS issuer page opened; text accessible", "supports": "The announcement is strategically interesting but too early and underspecified to evidence an operating technology or economics. Preserve the page/body date discrepancy and monitor for a defined project design." } ], "references": [ { "id": "AI-080", "relationship": "company_context" } ] }, { "id": "R1-LIM-05", "company": "STEP Energy Services / ARC Energy Fund 8", "title": "STEP ended U.S. fracturing operations and sold/redeployed equipment; ARC Energy Fund 8 completed the take-private", "category": "Hydraulic fracturing service technology capacity / supplier economics / private equity ownership", "kind": "new_initiative", "ai_role": "No AI role. It is included as an adjacent supplier-economics boundary case: operational technology and a service footprint can be real, yet segment economics and capital ownership determine where suppliers operate.", "asset": "STEP U.S. fracturing cash-generating unit, equipment and market footprint; surviving STEP business includes Canadian fracturing and coiled tubing.", "stage": "Management committed to terminate the U.S. fracturing operation in Q1 2025. Equipment was marshalled for sale or transfer to Canada. ARC Energy Fund 8 completed take-private on 2025-12-16 after ARC already controlled 55.22% before the offer.", "operating_period": "Q3 2025 operating report published 2025-11; non-binding take-private offer dated 2025-09-25; take-private closed 2025-12-16.", "claim": "Operating footprint exit was driven by changes in business conditions that materially affected the U.S. fracturing CGU's expected economic performance and a depressed U.S. market. Exact market-price/utilization thresholds were not disclosed in cited lines. Equipment was routed to yards for sale or transfer, showing redeployment/asset recovery rather than technology abandonment. ARC funds acquired remaining public shares for $5.50 each and owned/controlled majority pre-offer.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "This is not evidence that a particular frac technology failed or that electric/dual-fuel fleets caused STEP’s exit. Do not infer from U.S. business exit that the overall frac market or Canadian fleet was uneconomic. Company did not in this source quantify technology-specific returns, individual fleet type disposition, or detailed exit valuation.", "relationship": "A service-line exit and asset disposition demonstrate supplier economics, not technology performance or an operator workflow alternative.", "decision_question": "What utilization, day rates, asset-sale proceeds and redeployment values drove U.S. frac exit and impairment, separately from equipment technical condition?", "company_key": "STEP Energy Services", "run": "Three-round scope review", "disposition": "exclude", "sources": [ { "title": "STEP Energy Services Ltd. Reports Third Quarter 2025 Results", "publisher": "STEP Energy Services", "date": "2025-11-06", "url": "https://www.stepenergyservices.com/news-releases/step-energy-services-ltd-reports-third-quarter-2025-results", "locator": "Lines 57–67 and 76–89: termination-related expenses, impairment, PE offer, continued technology investment and exit/redeployment status.", "access": "Opened; issuer results release", "supports": "U.S. fracturing exit, financial charges, cited business-condition rationale, equipment disposition, continuing natural-gas technology investment, and ARC offer status." }, { "title": "ARC Energy Fund 8 Completes Take-Private Acquisition of STEP Energy Services Ltd.", "publisher": "STEP Energy Services / ARC Energy Fund 8", "date": "2025-12-16", "url": "https://www.stepenergyservices.com/news-releases/arc-energy-fund-8-completes-take-private-acquisition-of-step-energy-services-ltd", "locator": "Completion announcement and fund entities involved.", "access": "Search result reviewed; issuer page found", "supports": "Completion of PE take-private, not investment rationale or post-close strategy." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-11-06", "url": "https://www.stepenergyservices.com/news-releases/step-energy-services-ltd-reports-third-quarter-2025-results", "locator": "Results: lines 55–65, 135–138 and 170; U.S. fracturing terminated operations, costs and business-conditions impairment.", "access": "issuer HTML opened", "supports": "Primary source supports market/segment exit and associated charges, not equipment technical failure. Take-private is ownership context, not technical evidence." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-12-16", "url": "https://www.stepenergyservices.com/news-releases/arc-energy-fund-8-completes-take-private-acquisition-of-step-energy-services-ltd", "locator": "Take-private completion.", "access": "issuer HTML opened in prior audit", "supports": "Primary source supports market/segment exit and associated charges, not equipment technical failure. Take-private is ownership context, not technical evidence." } ], "references": [] }, { "id": "R1-LIM-06", "company": "Shell", "title": "Rotterdam biofuels facility construction not restarted after commercial and technical reassessment", "category": "Biofuels process plant / energy transition capex; adjacent comparator outside upstream production", "kind": "new_initiative", "ai_role": "No AI role. Included only as a cross-energy capital discipline example; exclude from upstream technology adoption totals and upstream project pipeline analysis.", "asset": "Shell Energy and Chemicals Park Rotterdam; downstream refinery/chemicals facility, not an upstream producing asset.", "stage": "Construction began in 2022; Shell decided in September 2025 not to restart. This is a cancellation after project evaluation, not a failed operating plant.", "operating_period": "Source published 2025-09-03; Shell says construction began in 2022.", "claim": "Expected product economics and cost to complete did not meet the company's competitiveness bar. Shell reallocated capital toward projects it expected to deliver customer need and shareholder value. No project IRR, remaining completion cost, or written-off investment is specified in this source.", "economics": "Not disclosed", "baseline": "Not disclosed", "limits": "Shell's explanation is issuer-reported and high-level. Do not infer feedstock, technology, contractor, policy or cost-overrun causes beyond the stated market dynamics and completion costs. Shell continues trading/supplying low-carbon fuels; cancellation is not a verdict on biofuels generally. This is deliberately tagged outside upstream.", "relationship": "Out of upstream scope; cancellation is not a failed operating-technology result.", "decision_question": "What remaining completion cost, expected margin/offtake, and sensitivity to market assumptions made the Rotterdam project uncompetitive?", "company_key": "Shell", "run": "Three-round scope review", "disposition": "exclude", "sources": [ { "title": "Shell will not restart construction of Rotterdam biofuels plant", "publisher": "Shell", "date": "2025-09-03", "url": "https://www.shell.com/news-and-insights/newsroom/news-and-media-releases/2025/shell-not-restart-construction-rotterdam-biofuels-plant.html", "locator": "Lines 24–33: stop decision, stated evaluation basis, broader Shell activity.", "access": "Opened; issuer source", "supports": "Decision not to restart and management's competitiveness rationale." }, { "title": "Source reopening in Round 2", "publisher": "See original source", "date": "2025-09-03", "url": "https://www.shell.com/news-and-insights/newsroom/news-and-media-releases/2025/shell-not-restart-construction-rotterdam-biofuels-plant.html", "locator": "Announcement lines 24–32: construction begun 2022; no restart; commercial/technical evaluation; competitiveness and cost to completion.", "access": "issuer HTML opened", "supports": "Strong primary evidence of cancellation and stated economic rationale, but out of scope for upstream operating technology. No performance conclusion should be inferred from the cancellation." } ], "references": [ { "id": "TR-05", "relationship": "company_context" } ] }, { "id": "T10-R01-GLOBAL-03", "company": "PTTEP / FutureTech Energy Ventures", "title": "Lan Sang Arun solar power for S1 upstream production", "category": "field power / upstream electrification", "kind": "update", "ai_role": "No AI contribution to the solar-generation project is disclosed in the cited sources. This is a power-supply technology and operating model; absence of disclosure is not proof of no AI in the wider S1 operations.", "asset": "Lan Sang Arun solar project supplying electricity to PTTEP's S1 Project / Sirikit oil field in Kamphaeng Phet Province, Thailand.", "stage": "Operating use at named upstream asset is confirmed by a 2025 issuer site-visit release. Project generation began in July 2023 (outside the source window); this record is a dated in-window update, not a new launch.", "operating_period": "The PTTEP 2025 annual-report text states power supply during calendar 2025. The 2025-12-12 issuer release confirms current use at S1.", "claim": "Preserve the issuer phrase “14.1 million units” for 2025 renewable electricity supplied to S1; do not convert to kWh/MWh until the annual report’s unit is verified. Solar project scale/forecast reductions are historical targets, not 2025 measured results.", "economics": "No 2025 solar capex, generation cost, gas displacement volume, utilization factor, grid/fuel baseline, realized emissions reduction or savings disclosed in the in-window source reviewed.", "baseline": "No 2025 counterfactual generation mix or measured gas-generated kWh displaced; 14.1 million 'units' is not interpreted as kWh without an opened source definition.", "limits": "Annual-report metric came from official indexed text because the direct report viewer returned an internal error; unit definition and exact denominator remain unverified here. The initial launch and 13,000 tCO2e/year estimate are from 2023 and should remain dated background/target, not in-window result.", "relationship": "Independent physical power technology, useful as a non-AI comparator to electric completion and grid/fuel substitution cases; no same-project canonical match found.", "decision_question": "What fraction of S1 load did the reported solar supply, what gas-fired energy was displaced, and what are generation, storage, balancing and lifecycle costs versus gas power?", "company_key": "PTTEP", "run": "Rounds 1–10", "disposition": "hold", "sources": [ { "title": "56-1 One Report / Annual Report 2025", "publisher": "PTTEP", "date": "2026 (2025 reporting year; exact publication date not surfaced)", "url": "https://sustainability.pttep.com/en/document/viewer/stream/187064/56-1-one-report-2025", "locator": "Search-indexed text under upstream/new-energy section: Lan Sang Arun supplied 14.1 million units of renewable electricity for S1 Project in 2025.", "access": "Official report indexed text inspected; direct document viewer returned internal error. Metric unit definition not available in the extracted text.", "supports": "2025 use/output metric only, as issuer stated; not cost or emissions attribution." }, { "title": "PTTEP shareholders visit Sirikit Oil Field and Lan Sang Arun solar power project", "publisher": "PTTEP", "date": "2025-12-12", "url": "https://www.pttep.com/en/newsroom/press-releases/1121/pttep-shareholders-visit-sirikit-oil-field-and-lan-sang-arun-solar-power-project", "locator": "Lines 8-17; named site, S1 production use and gas-electricity displacement rationale.", "access": "Official page opened; relevant text directly reviewed.", "supports": "Operating use at the named S1/Sirikit upstream asset and mechanism." } ], "references": [ { "id": "AI-067", "relationship": "company_context", "basis": "PTTEP/SLB offshore production-data and AI advisory pilot; distinct asset/workflow from S1 field power." } ], "review": { "verdict": "hold", "reason": "Official annual-report viewer did not expose the unit in accessible extraction; shareholder visit release supports solar use at S1 but not the number or economics.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R01-GLOBAL-03", "verdict": "hold", "patch": { "claim": "Preserve the issuer phrase “14.1 million units” for 2025 renewable electricity supplied to S1; do not convert to kWh/MWh until the annual report’s unit is verified. Solar project scale/forecast reductions are historical targets, not 2025 measured results.", "unit_status": "Unresolved. Do not render “units” as energy unit." }, "reason": "Official annual-report viewer did not expose the unit in accessible extraction; shareholder visit release supports solar use at S1 but not the number or economics.", "recommended_disposition": "hold", "sources_checked": [ { "url": "https://sustainability.pttep.com/en/document/viewer/stream/187064/56-1-one-report-2025", "access_status": "Official PDF viewer returned content-too-large/internal error; indexed excerpt only; exact unit unverified", "locator": "Search-indexed text under upstream/new-energy section: Lan Sang Arun supplied 14.1 million units of renewable electricity for S1 Project in 2025.", "date": "2026 (2025 reporting year; exact publication date not surfaced)" }, { "url": "https://www.pttep.com/en/newsroom/press-releases/1121/pttep-shareholders-visit-sirikit-oil-field-and-lan-sang-arun-solar-power-project", "access_status": "Prior-round source inspection only; R10 re-audit used saved source record/root checks, not a fresh direct reopen", "locator": "Lines 8-17; named site, S1 production use and gas-electricity displacement rationale.", "date": "2025-12-12" } ] } ] } }, { "id": "T10-R04-GLOBAL-03", "company": "Petrobras", "title": "Hydraulic turbine energy recovery in offshore cooling-water discharge", "category": "Process energy efficiency / power recovery", "kind": "context", "ai_role": "No AI role identified; energy recovery equipment is conventional process engineering.", "asset": "New offshore platform projects using seawater cooling flow discharged through control valves; no named platform specified.", "stage": "Company lists under implementation; applicable only to new projects. Specific deployed asset not identified.", "operating_period": "2025 status report; implementation timing and operating period not given.", "claim": "A 2025-reporting-period climate-report passage describes evaluating/recovering hydraulic energy from seawater discharge on a case-by-case basis. No named producing platform, installed unit count, generated MWh, fuel reduction or economics surfaced in this audit.", "economics": "No generation output, fuel savings, CAPEX, OPEX, or payback disclosed; impact potential marked none in the report table.", "baseline": "No specific platform baseline; baseline mechanism is otherwise wasted hydraulic energy across throttling valves.", "limits": "Generic measure rather than an asset-verified deployment. Status is under implementation, and company marks impact potential none; do not count as realized savings or add to platform adoption totals.", "relationship": "AI records are company context; no same-project match. The device is distinct from Petrobras offshore electrification/PRM cases in prior research.", "decision_question": "Which sanctioned new platform has installed this turbine and what metered fuel-gas displacement justified its design?", "company_key": "Petrobras", "run": "Rounds 1–10", "disposition": "hold", "sources": [ { "title": "Climate Change and Energy Transition Supplement 2025", "publisher": "Petrobras", "date": "2026 publication; reports 2025 status", "url": "https://petrobras.com.br/documents/2677942/9192383/Caderno%2Bdo%2BClima%2B2025%2Bingl%C3%AAs%2Bfinal_rev1.pdf/3809f8ca-4def-7df7-7e6e-0ee811d49a90?download=true&t=1779219386000&version=1.0", "locator": "PDF p.67-68, lines 1911-1925", "access": "Issuer PDF opened in R03; this passage surfaced in targeted search excerpt", "supports": "Mechanism, applicable scope, under-implementation status and lack of impact estimate." } ], "references": [ { "id": "AI-219", "relationship": "AI records are company context; no same-project match. The device is distinct from Petrobras offshore electrification/PRM cases in prior research." }, { "id": "AI-220", "relationship": "AI records are company context; no same-project match. The device is distinct from Petrobras offshore electrification/PRM cases in prior research." }, { "id": "AI-221", "relationship": "AI records are company context; no same-project match. The device is distinct from Petrobras offshore electrification/PRM cases in prior research." } ], "review": { "verdict": "hold", "reason": "Technical concept is plausible, but the cited passage was search-excerpted rather than directly located in the opened PDF during this audit. Hold as a deployment case pending exact full-text and installation scope.", "cross_audits": [ { "assignment": "round-10-us.json", "finding_id": "T10-R04-GLOBAL-03", "verdict": "hold", "patch": { "claim": "A 2025-reporting-period climate-report passage describes evaluating/recovering hydraulic energy from seawater discharge on a case-by-case basis. No named producing platform, installed unit count, generated MWh, fuel reduction or economics surfaced in this audit." }, "reason": "Technical concept is plausible, but the cited passage was search-excerpted rather than directly located in the opened PDF during this audit. Hold as a deployment case pending exact full-text and installation scope.", "recommended_disposition": "hold", "sources_checked": [ { "url": "https://petrobras.com.br/documents/2677942/9192383/Caderno%2Bdo%2BClima%2B2025%2Bingl%C3%AAs%2Bfinal_rev1.pdf/3809f8ca-4def-7df7-7e6e-0ee811d49a90?download=true&t=1779219386000&version=1.0", "access_status": "Issuer PDF opened in prior round, but cited passage was located via search excerpt; exact installation passage not directly located in R10", "locator": "PDF p.67-68, lines 1911-1925", "date": "2026 publication; reports 2025 status" } ] } ] } }, { "id": "T20-R12-GLOBAL-02", "company": "PTTEP / AI and Robotics Ventures (ARV) / ADNOC", "title": "Nautilus subsea pipeline repair and Xplorer inspection move into commercial operator deployments", "category": "subsea inspection and repair robotics / remote operations", "kind": "new_initiative", "ai_role": "The named mechanisms are an autonomous underwater inspection vehicle and a remotely operated subsea repair robot with circumferential ultrasonic thickness scanning, satellite-enabled remote operations, and carbon-fiber wrap reinforcement. PTTEP reports ARV as its AI/Robotics subsidiary, but does not attribute the ADNOC repair or Xplorer inspection performance to a specific AI model; do not count these as AI-only deployments.", "asset": "Nautilus: severely corroded underwater pipeline for ADNOC in UAE. Xplorer AUV: more than 700 km of inspection contracts for operators in Thailand and Malaysia.", "stage": "PTTEP's FY2025 report describes commercial-scale implementation: Xplorer commissioned after proof/paid trial in late 2024; Nautilus deployed for an ADNOC repair mission. Source says repair operations completed without shutting production and without divers.", "operating_period": "FY2025 annual-report account; Xplorer proof/paid trial was in late 2024. Exact mission dates, water depth, pipeline dimensions and production rates are not stated in the indexed excerpt.", "claim": "PTTEP reports that Xplorer AUV won Thailand and Malaysia inspection contracts totaling >700 km after successful technical proof and paid trial. Separately, it says Nautilus used full-circumference ultrasonic thickness scanning, satellite-enabled remote operations and carbon-fiber wrapping to repair a severely corroded ADNOC subsea pipeline; work completed without production shutdown or divers.", "economics": "No contract value, intervention time/cost, avoided shutdown value, repair life, inspection accuracy, diver-vessel cost baseline, or comparator provided. >700 km is contracted inspection distance, not completed inspection distance unless report elsewhere confirms completion.", "baseline": "For the ADNOC repair, conventional diver/ROV repair and shutdown are implicit alternatives, but the source provides no before/after cycle time or cost. Xplorer baseline is proof/paid trial, no quantified inspection performance comparator.", "limits": "The originating pass reports the PTTEP 2025 One Report only as an indexed issuer excerpt because direct retrieval exceeded the access limit. This audit retried the exact report URL and received an internal retrieval error. Retain the distinction between Xplorer contracts/commissioning and the completed Nautilus ADNOC repair mission, but treat project-specific performance, >700 km contract distance and repair details as indexed-primary claims pending a directly readable official report passage or operator source. No AI model is attributed to the robot tasks.", "relationship": "No same-project record found in baseline AI register among PTTEP entries; existing PTTEP AI-245 is internal audit. The robot's prior commercial existence is acknowledged; this evidence is a new in-window ADNOC application and scale-up disclosure, not invention or first deployment.", "decision_question": "For the ADNOC repair, what were pipeline size/depth, wall-loss percentage, intervention duration, verification scans, repair lifetime, and total cost against a shutdown/diver alternative; for Xplorer, how much of the 700-km contracted distance is complete and at what inspection accuracy?", "company_key": "PTTEP", "run": "Rounds 11–20", "disposition": "hold_for_direct_primary_excerpt", "sources": [ { "title": "56-1 One Report / Annual Report 2025", "publisher": "PTT Exploration and Production Public Company Limited (PTTEP)", "date": "2026 (FY2025 report; exact release date not confirmed from excerpt)", "url": "https://www.pttep.com/en/document/viewer/stream/187064/56-1-one-report-2025", "locator": "Search-indexed passage on ARV commercial-scale implementation, Xplorer >700 km contracts, and Nautilus ADNOC repair; direct open failed due file-size limit.", "access": "Issuer-hosted source surfaced as indexed excerpt; direct open failed (document exceeds retrieval limit)", "supports": "Xplorer development/deployment stages and contract distance; Nautilus mechanism, ADNOC deployment, completed repair without production shutdown or divers." } ], "references": [], "review": { "verdict": "hold", "reason": "The exact issuer-hosted 2025 One Report URL could not be read directly in this audit (browser returned an internal error; the originating pass had logged document-size failure and an indexed excerpt). The existing record is appropriately careful about contract distance versus completed inspection distance and does not call these AI-only deployments. Direct source verification remains below the standard applied to the other records, so keep as a qualified lead until a readable report excerpt is attached.", "cross_audits": [ { "assignment": "round-20-us.json", "finding_id": "T20-R12-GLOBAL-02", "verdict": "hold", "patch": { "limits": "The originating pass reports the PTTEP 2025 One Report only as an indexed issuer excerpt because direct retrieval exceeded the access limit. This audit retried the exact report URL and received an internal retrieval error. Retain the distinction between Xplorer contracts/commissioning and the completed Nautilus ADNOC repair mission, but treat project-specific performance, >700 km contract distance and repair details as indexed-primary claims pending a directly readable official report passage or operator source. No AI model is attributed to the robot tasks." }, "reason": "The exact issuer-hosted 2025 One Report URL could not be read directly in this audit (browser returned an internal error; the originating pass had logged document-size failure and an indexed excerpt). The existing record is appropriately careful about contract distance versus completed inspection distance and does not call these AI-only deployments. Direct source verification remains below the standard applied to the other records, so keep as a qualified lead until a readable report excerpt is attached.", "sources_inspected": [ { "url": "https://www.pttep.com/en/document/viewer/stream/187064/56-1-one-report-2025", "access": "Direct open failed with internal retrieval error; indexed primary excerpt only in originating record", "locator": "No readable page/paragraph returned by audit tool; originating round indexed passage on ARV commercial implementation, Xplorer and Nautilus." } ], "recommended_disposition": "hold_for_direct_primary_excerpt" } ] } } ], "runs": [ { "label": "Rounds 1–10", "stats": { "assignments_completed": 30, "assignments_expected": 30, "missing_assignments": [], "findings": 51, "findings_by_kind": { "new_initiative": 8, "update": 28, "gap": 2, "context": 12, "negative_evidence": 1 }, "cross_audit_reviews": 68, "unique_finding_source_urls": 64, "search_log_entries": 123, "round10_reviewed_findings": 51, "round10_missing_reviews": [], "validation_errors": [], "complete": true } }, { "label": "Rounds 11–20", "stats": { "assignments_completed": 30, "assignments_expected": 30, "missing_assignments": [], "findings": 31, "findings_by_kind": { "update": 9, "negative_evidence": 3, "context": 11, "new_initiative": 8 }, "cross_audit_reviews": 31, "unique_finding_source_urls": 40, "search_log_entries": 95, "round20_reviewed_findings": 31, "round20_missing_reviews": [], "validation_errors": [], "complete": true } } ], "counts": { "notes": 179, "groups": 169, "company_filter_entries": 86, "held_or_excluded": 6, "ai_register_profiles": 306 }, "latest_targeted_review_on": "2026-10-26" }