Domain intelligence
for the oil & gas lifecycle.
AWP's Oil & Gas Digital Workforce Workspace brings specialist Digital Employees, industrial data, engineering tools, evidence and approvals into one governed environment. The supplied reference architecture identifies six employee domains: Seismic, Well Logging, Drilling, Reservoir, Production and Assets.
Specialist roles.
Connected execution.
Domain role families below are illustrative configurations of the AWP Digital Employee model. Each employee has an identity, role, objectives, responsibilities, knowledge, skills, authorised tools, workflows, policies, human escalation and evaluation.
Seismic
Interpretation and survey analysis
Illustrative role: Seismic InterpreterWell Logging
Log interpretation and formation evaluation
Illustrative role: Well Logging AnalystDrilling
Drilling reports, operations analysis and risk investigation
Illustrative role: Drilling Operations AdvisorReservoir
Reservoir performance, pressure analysis and development scenarios
Illustrative role: Reservoir Engineering AdvisorProduction
Production surveillance, well performance and optimisation
Illustrative role: Production Engineering WorkerAssets
Equipment condition, maintenance intelligence and reliability
Illustrative role: Asset Integrity AdvisorGround every employee
in the operating context.
Well identity, wellbore structure and associated records.
Survey datasets and interpretation context.
LAS, DLIS and related well-log information.
Daily reports, operational documents and engineering references.
Reservoir information, models and supporting studies.
Measurements and operating histories.
Equipment, condition and maintenance records.
From request to
evidence-backed result.
The same AWP execution controls apply: understand the request, resolve context, plan, authorise, execute through approved tools, collect evidence, reason and present findings.
Governance is part
of the workforce.
Industry fit is configured
and validated in context.
The supplied architecture is explicitly an Oil & Gas Digital Workforce Workspace and labels the data foundation OSDU-compatible. OSDU compatibility should be treated as an architectural alignment objective; actual interoperability depends on the selected data services, schemas, APIs and implementation.
The page describes an AWP industry application model. It does not imply that all integrations, domain employees or workflows are preconfigured or production-deployed. Data access, tool behaviour, validation criteria, permissions and approval gates are established for the specific environment.
Start with the work.
Design the right employee.
Identify a priority workflow, define the employee's skills and boundaries, connect approved tools, and validate the evidence and outcomes.