<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Databricks Assistant Data Science Agent: Autonomous Analytics for Petroleum Engineers in Technical Blog</title>
    <link>https://community.databricks.com/t5/technical-blog/databricks-assistant-data-science-agent-autonomous-analytics-for/ba-p/135246</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Petroleum engineers spend hours wrangling and analyzing data to estimate well production targets. We demonstrate how the Data Science Agent can significantly accelerate this type of analysis and many other problems that petroleum engineers continually strive to solve. Building on the momentum from my previous article on leveraging &lt;/SPAN&gt;&lt;A href="https://community.databricks.com/t5/technical-blog/5-ways-to-leverage-databricks-assistant-to-go-from-petroleum/ba-p/116567" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Databricks Assistant&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; for petroleum workflows, the industry is now witnessing a step-change in analytics tools. With the introduction of the Databricks Data Science Agent, engineers can move beyond simple AI support to benefit from an autonomous analytical partner that streamlines data work and accelerates the path from question to actionable results.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The transition from copilot to autonomous agent addresses a critical gap in petroleum engineering analytics. While the Assistant proved valuable for generating SQL queries and Python code snippets, complex multi-step analyses still required extensive manual orchestration. The global AI market in oil and gas is projected to &lt;/SPAN&gt;&lt;A href="https://www.coherentmarketinsights.com/industry-reports/artificial-intelligence-ai-in-oil-and-gas-market" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;grow&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; from $3.01 billion in 2025 to $6.92 billion by 2032. The &lt;/SPAN&gt;&lt;A href="https://www.databricks.com/blog/introducing-databricks-assistant-data-science-agent" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Databricks Data Science Agent&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; positions petroleum engineering teams at the forefront of this transformation, providing immediate access to autonomous capabilities that enable comprehensive analytical workflows from initial data exploration through final executive reporting, all with a single prompt.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_0-1760706642695.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20811iE7E47587693705A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_0-1760706642695.png" alt="brettaulbaugh_0-1760706642695.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;The Databricks Data Science Agent: Technical Overview&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;The Data Science Agent represents a fundamental advancement in autonomous analytics, extending beyond code generation to comprehensive workflow orchestration. This capability proves particularly valuable for engineering applications that require integration of multiple analytical techniques, complex data relationships, and domain-specific modeling approaches.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Autonomous multi-step execution distinguishes the Agent from traditional AI assistants. Rather than responding to individual queries, the Agent can plan and execute complete analytical workflows. For petroleum applications, this means seamless integration of data validation, statistical modeling, forecasting, and visualization within a single prompt.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unity Catalog Integration provides critical context awareness for petroleum datasets. The Agent leverages Unity Catalog's metadata to understand table relationships, data lineage, and business semantics. This integration enables the Agent to navigate complex petroleum data architectures autonomously, understanding that production tables relate to completion data, geological formations, and operational parameters.&lt;/SPAN&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_1-1760706642695.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20809iD2CA159022054FA7/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_1-1760706642695.png" alt="brettaulbaugh_1-1760706642695.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;SPAN&gt;Governance and Review Capabilities address enterprise requirements for data security and analytical transparency. The Agent operates within existing Unity Catalog permissions, requests human approval for data modifications, and maintains comprehensive audit trails to ensure transparency and accountability. These safeguards ensure that autonomous analytics align with industry standards for data governance and operational integrity in the petroleum sector.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For petroleum engineering teams, these capabilities enable sophisticated analyses previously requiring specialized data science expertise. The Agent democratizes advanced analytics while maintaining professional standards for accuracy, transparency, and governance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;Enabling Agent Mode&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;Currently, Agent Mode is in Beta and requires workspace administrator intervention through the Databricks preview portal for activation. Administrators must enable the "Assistant Agent Mode Beta" feature within the &lt;/SPAN&gt;&lt;A href="https://docs.databricks.com/aws/en/admin/workspace-settings/manage-previews" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;preview management&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; interface to give the team access to autonomous analytics capabilities. This feature will soon be available without this step. In addition to needing administrators to enable this feature, some components of the interface could still be changing while this product is in beta and might differ slightly from what is outlined in the blog below..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Following administrator enablement, users will observe a toggle control in the Assistant interface located in the notebook's bottom-right panel. This toggle allows switching between traditional Assistant mode and the new Agent mode, providing immediate access to autonomous analytical capabilities.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_2-1760706642695.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20810iEFA46A893192E965/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_2-1760706642695.png" alt="brettaulbaugh_2-1760706642695.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN&gt;Configuring Agent Instructions&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;The Data Science Agent and Databricks Assistant support &lt;/SPAN&gt;&lt;A href="https://docs.databricks.com/aws/en/notebooks/assistant-tips#customize-assistant-responses-by-adding-instructions" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;customizable instructions&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; that allow petroleum engineering teams to establish domain-specific preferences, coding standards, and business context that the Agent will consistently apply across all interactions. These instructions prove particularly valuable for standardizing analytical approaches across petroleum engineering workflows.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;User-level instructions&lt;/STRONG&gt; provide individual customization capabilities, enabling petroleum engineers to specify their preferred analytical libraries, coding conventions, and personal preferences. To configure user instructions:&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Open the Assistant panel and click the settings icon&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Select "Add instructions file" to create a &lt;/SPAN&gt;&lt;SPAN&gt;.assistant_instructions.md&lt;/SPAN&gt;&lt;SPAN&gt; file&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Define custom instructions using a natural language format&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN&gt;Example petroleum engineering user instructions:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_3-1760706642696.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20814i72E5923D8F3D911F/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_3-1760706642696.png" alt="brettaulbaugh_3-1760706642696.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;Workspace-Level Instructions&lt;/STRONG&gt; enable standardization across entire petroleum engineering teams, ensuring consistent analytical approaches regardless of individual user preferences.&amp;nbsp; To enable workspace instruction, in the Workspace/ directory of the workspace, create a new file named .assistant_workspace_instructions.md.&amp;nbsp; Workspace administrators can establish organization-wide standards for:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Preferred Python Libraries: Standardize on specific packages for reservoir engineering, geophysics, or production analysis&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Business Terminology: Define company-specific terms, field names, and operational definitions&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Coding Standards: Establish formatting conventions, documentation requirements, and quality standards&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;
&lt;P&gt;&lt;SPAN&gt;Analytical Methodologies: Specify preferred approaches for common petroleum engineering analyses&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Priority Hierarchy ensures that workspace instructions generally take precedence over user instructions, maintaining organizational consistency while allowing individual customization for non-conflicting preferences.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_4-1760706642696.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20812i3F6CED37CFECBD7E/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_4-1760706642696.png" alt="brettaulbaugh_4-1760706642696.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;Case Study: Production Forecasting Analysis&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;This analysis demonstrates the Agent's capability to address complex petroleum engineering challenges through autonomous analytics. A production engineer responsible for a particular set of wells is required to do a year-end production assessment to determine target achievement probability.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Business Requirements encompassed 47 active wells with varying completion designs, production histories, and operational timelines. The analysis needed to compare actual performance against original type curve forecasts and provide actionable insights for year-end planning decisions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This analysis utilizes two core data tables that upstream operators commonly create as foundational data products: the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;Daily Production &lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt;table, which captures actual production volumes at the well and date level, and the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;Type Well Forecast&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt; table, which provides projected production values based on Days from First Production for specific forecast scenarios. Type Well Forecasts are typically assigned to individual wells to enhance production forecasting accuracy. Within our current infrastructure, both tables are maintained in Delta format under Unity Catalog management, where comprehensive metadata and descriptions are systematically documented to support continuous workflow optimization and governance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The comprehensive prompt provided to our Agent is as follows:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;SPAN&gt;I&lt;/SPAN&gt; &lt;SPAN&gt;am&lt;/SPAN&gt; a &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;engineer&lt;/SPAN&gt; &lt;SPAN&gt;responsible&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;all&lt;/SPAN&gt; &lt;SPAN&gt;currently&lt;/SPAN&gt; &lt;SPAN&gt;producing&lt;/SPAN&gt; &lt;SPAN&gt;wells&lt;/SPAN&gt; &lt;SPAN&gt;in&lt;/SPAN&gt; &lt;SPAN&gt;FORMATION_C,&lt;/SPAN&gt; &lt;SPAN&gt;I&lt;/SPAN&gt; &lt;SPAN&gt;need&lt;/SPAN&gt; &lt;SPAN&gt;a&lt;/SPAN&gt; &lt;SPAN&gt;report&lt;/SPAN&gt; &lt;SPAN&gt;to&lt;/SPAN&gt; &lt;SPAN&gt;assess&lt;/SPAN&gt; &lt;SPAN&gt;whether&lt;/SPAN&gt; &lt;SPAN&gt;our&lt;/SPAN&gt; &lt;SPAN&gt;total&lt;/SPAN&gt; &lt;SPAN&gt;oil&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;FORMATION_C&lt;/SPAN&gt; &lt;SPAN&gt;will&lt;/SPAN&gt; &lt;SPAN&gt;end&lt;/SPAN&gt; &lt;SPAN&gt;2025&lt;/SPAN&gt; &lt;SPAN&gt;above&lt;/SPAN&gt; &lt;SPAN&gt;or&lt;/SPAN&gt; &lt;SPAN&gt;below&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;originally&lt;/SPAN&gt; &lt;SPAN&gt;forecasted&lt;/SPAN&gt; &lt;SPAN&gt;values.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Actual&lt;/SPAN&gt; &lt;SPAN&gt;daily&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;data&lt;/SPAN&gt; &lt;SPAN&gt;is&lt;/SPAN&gt; &lt;SPAN&gt;in&lt;/SPAN&gt; &lt;SPAN&gt;vdm_serverless_frlx2w.ds_agent.daily_production.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Type&lt;/SPAN&gt; &lt;SPAN&gt;curve&lt;/SPAN&gt; &lt;SPAN&gt;forecasts&lt;/SPAN&gt; &lt;SPAN&gt;are&lt;/SPAN&gt; &lt;SPAN&gt;in&lt;/SPAN&gt; &lt;SPAN&gt;vdm_serverless_frlx2w.ds_agent.type_curve_daily_df.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For&lt;/SPAN&gt; &lt;SPAN&gt;each&lt;/SPAN&gt; &lt;SPAN&gt;well:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Fit&lt;/SPAN&gt; &lt;SPAN&gt;an&lt;/SPAN&gt; &lt;SPAN&gt;ARPS&lt;/SPAN&gt; &lt;SPAN&gt;decline&lt;/SPAN&gt; &lt;SPAN&gt;curve&lt;/SPAN&gt; &lt;SPAN&gt;to&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;well&lt;/SPAN&gt;&lt;SPAN&gt;'&lt;/SPAN&gt;&lt;SPAN&gt;s&lt;/SPAN&gt; &lt;SPAN&gt;actual&lt;/SPAN&gt; &lt;SPAN&gt;daily&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;history&lt;/SPAN&gt; &lt;SPAN&gt;to&lt;/SPAN&gt; &lt;SPAN&gt;determine&lt;/SPAN&gt; &lt;SPAN&gt;per-well&lt;/SPAN&gt; &lt;SPAN&gt;ARPS&lt;/SPAN&gt; &lt;SPAN&gt;parameters.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Use&lt;/SPAN&gt; &lt;SPAN&gt;these&lt;/SPAN&gt; &lt;SPAN&gt;fitted&lt;/SPAN&gt; &lt;SPAN&gt;parameters&lt;/SPAN&gt; &lt;SPAN&gt;to&lt;/SPAN&gt; &lt;SPAN&gt;forecast&lt;/SPAN&gt; &lt;SPAN&gt;each&lt;/SPAN&gt; &lt;SPAN&gt;well&lt;/SPAN&gt;&lt;SPAN&gt;'&lt;/SPAN&gt;&lt;SPAN&gt;s&lt;/SPAN&gt; &lt;SPAN&gt;daily&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;through&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;end&lt;/SPAN&gt; &lt;SPAN&gt;of&lt;/SPAN&gt; &lt;SPAN&gt;2025&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Compare&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;summed,&lt;/SPAN&gt; &lt;SPAN&gt;re-forecasted&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;all&lt;/SPAN&gt; &lt;SPAN&gt;FORMATION_C&lt;/SPAN&gt; &lt;SPAN&gt;wells&lt;/SPAN&gt; &lt;SPAN&gt;to&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;original&lt;/SPAN&gt; &lt;SPAN&gt;type&lt;/SPAN&gt; &lt;SPAN&gt;curve&lt;/SPAN&gt; &lt;SPAN&gt;forecast,&lt;/SPAN&gt; &lt;SPAN&gt;anchored&lt;/SPAN&gt; &lt;SPAN&gt;at&lt;/SPAN&gt; &lt;SPAN&gt;each&lt;/SPAN&gt; &lt;SPAN&gt;well&lt;/SPAN&gt;&lt;SPAN&gt;'&lt;/SPAN&gt;&lt;SPAN&gt;s&lt;/SPAN&gt; &lt;SPAN&gt;initial&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;date.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The&lt;/SPAN&gt; &lt;SPAN&gt;final&lt;/SPAN&gt; &lt;SPAN&gt;report&lt;/SPAN&gt; &lt;SPAN&gt;should&lt;/SPAN&gt; &lt;SPAN&gt;include:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The&lt;/SPAN&gt; &lt;SPAN&gt;total&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;delta&lt;/SPAN&gt; &lt;SPAN&gt;(difference)&lt;/SPAN&gt; &lt;SPAN&gt;between&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;original&lt;/SPAN&gt; &lt;SPAN&gt;type&lt;/SPAN&gt; &lt;SPAN&gt;curve&lt;/SPAN&gt; &lt;SPAN&gt;forecast&lt;/SPAN&gt; &lt;SPAN&gt;and&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;re-forecasted&lt;/SPAN&gt; &lt;SPAN&gt;values&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;FORMATION_C&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;2025&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The&lt;/SPAN&gt; &lt;SPAN&gt;set&lt;/SPAN&gt; &lt;SPAN&gt;of&lt;/SPAN&gt; &lt;SPAN&gt;ARPS&lt;/SPAN&gt; &lt;SPAN&gt;parameters&lt;/SPAN&gt; &lt;SPAN&gt;(e.g.,&lt;/SPAN&gt; &lt;SPAN&gt;initial&lt;/SPAN&gt; &lt;SPAN&gt;rate,&lt;/SPAN&gt; &lt;SPAN&gt;decline&lt;/SPAN&gt; &lt;SPAN&gt;rate,&lt;/SPAN&gt; &lt;SPAN&gt;b-factor)&lt;/SPAN&gt; &lt;SPAN&gt;you&lt;/SPAN&gt; &lt;SPAN&gt;found&lt;/SPAN&gt; &lt;SPAN&gt;would&lt;/SPAN&gt; &lt;SPAN&gt;have&lt;/SPAN&gt; &lt;SPAN&gt;best&lt;/SPAN&gt; &lt;SPAN&gt;fit&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;actual&lt;/SPAN&gt; &lt;SPAN&gt;performance&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;FORMATION_C&lt;/SPAN&gt; &lt;SPAN&gt;type&lt;/SPAN&gt; &lt;SPAN&gt;curves.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Please&lt;/SPAN&gt; &lt;SPAN&gt;structure&lt;/SPAN&gt; &lt;SPAN&gt;the&lt;/SPAN&gt; &lt;SPAN&gt;results&lt;/SPAN&gt; &lt;SPAN&gt;so&lt;/SPAN&gt; &lt;SPAN&gt;they&lt;/SPAN&gt; &lt;SPAN&gt;are&lt;/SPAN&gt; &lt;SPAN&gt;actionable&lt;/SPAN&gt; &lt;SPAN&gt;for&lt;/SPAN&gt; &lt;SPAN&gt;year-end&lt;/SPAN&gt; &lt;SPAN&gt;production&lt;/SPAN&gt; &lt;SPAN&gt;planning&lt;/SPAN&gt; &lt;SPAN&gt;and&lt;/SPAN&gt; &lt;SPAN&gt;forecasts.&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Upon submitting the prompt, it immediately begins outlining the proposed plan and asks clarifying questions.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Screen-Recording-2025-09-23-at-1.gif" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20824i73DF8AB6551D7223/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen-Recording-2025-09-23-at-1.gif" alt="Screen-Recording-2025-09-23-at-1.gif" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;These clarifying questions continue to shape the agent’s plan.&amp;nbsp; In this case, the agent asked the following:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;How is FORMATION_C identified in your data? Is it a value in a specific column (e.g., type_curve or another identifier)?&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Should we include all wells with any production in 2025, or only those with first production before a certain cutoff?&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Do you want confidence intervals on the ARPS forecasts per well, or only on the group total?&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Should the report include a downloadable table of per-well ARPS parameters?&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Once the requirements were clarified, the agent began its work by writing code, executing it, and correcting mistakes. Ultimately, it generated an entire notebook of code that addressed my problem statement. This notebook includes methods for data sampling and extraction, curve fitting techniques, statistical interpretations, and advanced visualizations, all generated by the Databricks Data Science Agent.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ezgif.com-video-to-gif-converter.gif" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20822i6E3430F89F359146/image-size/large?v=v2&amp;amp;px=999" role="button" title="ezgif.com-video-to-gif-converter.gif" alt="ezgif.com-video-to-gif-converter.gif" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To conclude the analysis, the agent created a summary markdown cell at the top of my notebook with the key takeaways to accompany a fully reproducible notebook.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="brettaulbaugh_7-1760706642697.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/20815i0FC561F3CB4D5A24/image-size/large?v=v2&amp;amp;px=999" role="button" title="brettaulbaugh_7-1760706642697.png" alt="brettaulbaugh_7-1760706642697.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Traditionally, conducting this level of analysis would have required several days of effort from a multidisciplinary team, including reservoir engineers, data scientists, and analysts. With the Agent, these tasks were completed autonomously within minutes. Not only did the Agent automate outlier detection, statistical confidence intervals, and professional visualizations, but it also uncovered a 265k&amp;nbsp; barrel production variance. This critical insight now enables proactive intervention strategies that have the potential to prevent millions in lost revenue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H2&gt;&amp;nbsp;&lt;/H2&gt;
&lt;H2&gt;&lt;STRONG&gt;Revolutionizing Petroleum Engineering Through Intelligent Automation&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;SPAN&gt;Technical Accessibility empowers petroleum engineers to tackle complex analyses—like advanced statistical modeling, machine learning, and probabilistic analysis—through intuitive conversational interfaces, eliminating the need for specialized programming skills. By making these capabilities broadly available, engineers can continuously adapt to new technologies and data-driven workflows, effectively future-proofing their job roles and responsibilities in an evolving industry.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Governance and Compliance ensure enterprise-level security and transparency. All Agent actions adhere to Unity Catalog permissions, need approval for sensitive tasks, and keep the human in the loop throughout the entire process. This ensures autonomous analytics comply with petroleum industry governance standards.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Analytical Scalability supports expanding workflows from single-well analyses to field-wide evaluations without requiring method changes. The Agent maintains analytical rigor across different scopes, enabling consistent approaches regardless of dataset complexity or size.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Knowledge Transfer happens naturally through Agent interactions. As the Agent explains its analytical decisions, methodological choices, and technical details, petroleum engineers build better data science skills through hands-on experience rather than formal training. The overall impact extends beyond efficiency gains to encompass advanced analytical capabilities, enhanced problem-solving skills, and increased confidence in tackling complex data challenges in the field of petroleum engineering.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 21 Oct 2025 11:58:29 GMT</pubDate>
    <dc:creator>brett-aulbaugh</dc:creator>
    <dc:date>2025-10-21T11:58:29Z</dc:date>
    <item>
      <title>Databricks Assistant Data Science Agent: Autonomous Analytics for Petroleum Engineers</title>
      <link>https://community.databricks.com/t5/technical-blog/databricks-assistant-data-science-agent-autonomous-analytics-for/ba-p/135246</link>
      <description>&lt;P&gt;Unlock new levels of efficiency with the Databricks Assistant Data Science Agent—your autonomous analytics partner. In this article, learn how the Data Science Agent transforms well production forecasting and complex workflows, going beyond code generation to provide fully orchestrated, end-to-end analytical solutions. Discover how seamless Unity Catalog integration, strong governance, and domain-specific intelligence enable engineers to move from data wrangling to actionable insights quickly—all while adhering to the energy sector’s strict standards for security and transparency. Whether you want to speed up daily tasks or enhance team-wide analytics, see how intelligent automation is changing the industry’s approach to data-driven decision-making.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 11:58:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/technical-blog/databricks-assistant-data-science-agent-autonomous-analytics-for/ba-p/135246</guid>
      <dc:creator>brett-aulbaugh</dc:creator>
      <dc:date>2025-10-21T11:58:29Z</dc:date>
    </item>
  </channel>
</rss>

