ZIWIGPT Agent Hub
LinkedIn

Workflow Studio

Bring AI into Engineering Workflows

Connect engineering information, ZIWIGPT Agents, people and actions around real oil & gas work.

AI inside the workflow, not beside the workflow.

SETUP · WHEN → USE → REVIEW → THEN

Build in Workflow Studio

Choose the input, Agent, reviewer and next action. Start with the example below or use a template.

01 WHEN

What starts the workflow?

Source labels describe your intended setup. No mailbox, folder, schedule or operational system is connected.

02 USE

Which Agent should work?

Wells & Drilling

Turn fragmented well records into structured, traceable context for faster well review and engineering analysis.

View Agent →
Optional supporting Agent

Add domain context only where relevant, such as Wells Agent in a wells-based handover.

03 REVIEW

Who needs to validate the result?

The Agent prepares the engineering output. The engineer reviews, corrects and confirms where required.

04 THEN

What happens next?

Demo configurations stay on this page only. Reloading or leaving clears them. Do not enter credentials or confidential information.

Workflow Studio Templates

Start from a proven engineering workflow and adapt it to your team.

01

Daily Well Report Review

Powered by:
Wells Agent

Turn incoming daily well reports into structured engineering review before the engineer starts from scratch.

  1. WHENDaily Well Report
  2. USEWells Agent
  3. REVIEWDrilling Engineer
  4. THENEmail Reviewed Summary + Save to Well Context
View Workflow

When to Use

Use this workflow when a new Daily Well Report or similar operational well record becomes available and requires engineering review.

Agents Used

  • Wells Agent

    Prepares structured well context and AI-assisted engineering review.

    View Agent

What ZIWIGPT Does

Wells Agent organizes the report and available well context around:

  • key operational events
  • NPT
  • important operational changes
  • relevant exceptions
  • supporting source records

What You Do

The drilling / wells engineer:

  • reviews the identified events
  • verifies the context
  • corrects anything necessary
  • adds engineering interpretation
  • decides what requires further attention

What You Get

A reviewed, traceable engineering summary.

What Happens Next

After engineer review:

  • send the reviewed summary to the selected drilling / engineering team
  • retain the reviewed result as part of the well context

Share the reviewed engineering summary with the relevant team and retain the result as reusable well context.

  • Email Reviewed Summary

    Send to: Selected Drilling / Engineering Team

    After Engineer Approval
  • Save to Well Context

    Retain in: Well Context

    After Engineer Approval

Descriptive delivery steps only. Email, notifications, sharing and saving are not connected here.

Engineering Value

Less time rebuilding the day. More time understanding what matters.

02

Production Event Review

Powered by:
Production Optimization Agent

Move from production events to clearer diagnosis, engineering recommendations and review.

  1. WHENProduction Event / Input
  2. USEProduction Optimization Agent
  3. REVIEWProduction Engineer
  4. THENShare Decision Note + Notify Responsible Engineer + Save Outcome
View Workflow

When to Use

Use this workflow when production performance changes, an event occurs, or an engineer needs to understand a production issue or opportunity.

Agents Used

  • Production Optimization Agent

    Brings production data and events together for diagnosis and engineering recommendations.

    View Agent

What ZIWIGPT Does

The Agent brings together available:

  • production data
  • operational events
  • relevant production context

to support:

  • understanding what changed
  • diagnosis
  • engineering recommendations
  • review of possible next steps

What You Do

The production engineer:

  • validates the diagnosis
  • reviews the recommendation
  • considers operational constraints
  • decides whether and how to act

What You Get

A clearer engineering decision path with production context, recommendation and review kept together.

What Happens Next

After the production engineer reviews the diagnosis and recommendation:

  • share the decision / recommendation with the relevant operations team
  • notify the responsible engineer where appropriate
  • retain the reviewed result / outcome for future reference

Share the reviewed recommendation with the relevant operations team and retain the decision and outcome for future review.

  • Share Decision Note

    Share with: Relevant Operations Team

    After Engineer Approval
  • Notify Responsible Engineer

    Notify: Responsible Engineer, where appropriate

    After Engineer Approval
  • Save Outcome

    Retain in: Reviewed Decision / Outcome

    After Engineer Approval

Descriptive delivery steps only. Email, notifications, sharing and saving are not connected here.

Engineering Value

From production event to engineering decision — with context preserved.

ZIWIGPT recommends. The engineer decides.

03

Follow-the-Sun Engineering Handover

Powered by
Meeting AgentWithWells Agentfor well context

Keep engineering work moving across time zones without losing critical context between handovers.

  1. WHENHandover Email
  2. USEMeeting Agent + Wells Agent
  3. REVIEWIncoming Engineering Team
  4. THENReviewed Handover Forwarded
View Workflow

When to Use

Use this workflow when engineering teams collaborate across:

  • countries
  • time zones
  • shifts
  • remote support centers

Agents Used

  • Meeting Agent

    Capture and structure meeting / handover decisions, actions, open issues and follow-up.

    View Agent

  • Wells Agent

    Supporting Agent for this wells-based example, where relevant.

    Provide relevant well context and supporting records when the handover involves well operations.

    View Agent

What ZIWIGPT Does

Meeting Agent structures:

  • key decisions
  • open issues
  • action items
  • responsibilities
  • follow-up items

Where relevant, Wells Agent can add:

  • well history
  • operational events
  • supporting records
  • relevant engineering context

What You Do

The incoming engineering team:

  • validates the handover context
  • investigates open issues
  • adds engineering judgment
  • progresses outstanding work

What You Get

A structured handover containing decisions, actions, engineering context and follow-up for the next team.

What Happens Next

After the incoming engineering team completes the review:

  • prepare the updated handover
  • forward it to the originating or next engineering team
  • preserve key decisions, actions and unresolved issues for the next working period

Forward the reviewed handover to the next team so work can continue without rebuilding the context.

  • Reviewed Handover Forwarded

    Forward by email to: Originating or Next Engineering Team

    After Engineer Approval

Example only: Canada / outgoing team → ZIWIGPT → China / remote engineering team → reviewed handover → Canada / next team. Teams and locations vary by engagement.

Descriptive delivery steps only. Email, notifications, sharing and saving are not connected here.

Engineering Value

From time-zone gap to engineering continuity.

04

Geological Section Review

Powered by:
GEOSection Agent

Turn geological section information into structured observations and interpretation support.

  1. WHENGeological Section / Supporting Information
  2. USEGEOSection Agent
  3. REVIEWGeoscientist
  4. THENShare Interpretation Output + Save Result
View Workflow

When to Use

Use this workflow when a geoscientist needs to review a geological section together with relevant supporting information.

Agents Used

  • GEOSection Agent

    Supports geological section understanding, pattern extraction and interpretation.

    View Agent

What ZIWIGPT Does

GEOSection supports:

  • geological section understanding
  • pattern extraction
  • geoscience Q&A
  • structured interpretation output

What You Do

The geoscientist:

  • reviews identified patterns
  • validates geological meaning
  • corrects or expands interpretation
  • applies domain judgment

What You Get

A more structured interpretation process with observations and supporting context prepared for engineering review and reporting.

What Happens Next

After geoscientist validation:

  • share the structured interpretation output with the relevant subsurface team
  • retain the result for reporting or subsequent technical review

Share the reviewed interpretation with the subsurface team and retain the structured output for reporting and future review.

  • Share Interpretation Output

    Share with: Relevant Subsurface Team

    After Engineer Approval
  • Save Result

    Retain in: Reporting / Future Technical Review

    After Engineer Approval

Descriptive delivery steps only. Email, notifications, sharing and saving are not connected here.

Engineering Value

Move from section review to reusable interpretation more efficiently.

05

Logging QA/QC Review

Powered by:
Well Logging Agent

Bring log-data validation and curve review directly into the subsurface QA/QC workflow.

  1. WHENLAS / Log Data
  2. USEWell Logging Agent
  3. REVIEWPetrophysicist / Subsurface Engineer
  4. THENSend QA/QC Findings + Save Validated Result
View Workflow

When to Use

Use this workflow when new well-log data needs quality checking before it is used for subsurface interpretation.

Agents Used

  • Well Logging Agent

    Reviews log data, compares curves and prepares validation findings.

    View Agent

What ZIWIGPT Does

The Agent supports:

  • LAS data review
  • curve comparison
  • validation rules
  • identification of potential quality issues
  • structured QA/QC findings

What You Do

The petrophysicist / subsurface engineer:

  • reviews flagged issues
  • validates whether findings are meaningful
  • determines whether correction is required
  • decides whether the data is suitable for subsequent interpretation

What You Get

A structured QA/QC result that makes potential data issues visible before downstream interpretation.

What Happens Next

After findings are validated:

  • send the reviewed QA/QC findings to the relevant data owner or subsurface reviewer
  • where appropriate, route findings back for correction
  • retain the validated QA/QC result

Send validated QA/QC findings to the relevant data owner or subsurface reviewer before downstream interpretation.

  • Send QA/QC Findings

    Send to: Relevant Data Owner or Subsurface Reviewer

    After Engineer Approval
  • Save Validated Result

    Retain in: Validated QA/QC Result

    After Engineer Approval

Descriptive delivery steps only. Email, notifications, sharing and saving are not connected here.

Engineering Value

Identify data-quality issues earlier and improve confidence in the data used for interpretation.

How a Workflow Runs

RUN · Intended behavior after connections and execution are implemented. Saving a demo configuration does not start this process.

  1. 1. Event happens

    A report arrives.

  2. 2. Agent works

    Wells Agent prepares the engineering review.

  3. 3. Engineer reviews

    The engineer validates and confirms the result.

  4. 4. Work moves forward

    The reviewed summary is emailed and saved.

The Agent provides the engineering intelligence. The Workflow connects that intelligence to the work around it.