Petroleum Engineering Practice

The working kit of a reservoir, drilling or production engineer: field and well data in order, surveillance and reporting routines, core analysis skills, well proposals and reviews, and the specialist work of a senior engineer.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Petroleum Engineering Practice, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information, not a safety manual or a substitute for proper training. Follow the law where you live and work, the manufacturer's and label instructions for machinery, chemicals, animal medicines and equipment, and any site safety rules. Use trained, licensed or certified people for regulated work such as electrical, gas, structural, pesticide or veterinary work, and stop if something seems unsafe.

What it installs.

1

Pillar

1

Area

50

Projects

198

Starter tasks

🔧 Engineering Practice

Petroleum Engineering Practice

Working as a petroleum engineer: reservoir, drilling and production roles, well planning and reviews, production optimisation, field data and regulatory reporting.

  1. Petroleum engineering role and deliverables map
  2. Field fact sheet for your assigned asset
  3. Well file and data source inventory
  4. Units, conversions and reference conditions sheet
  5. Engineering software and template set-up
  6. Wellbore diagram check for your active wells
  7. Reservoir fluid and PVT summary
  8. Regulatory obligations register for your asset
  9. Wellsite and field visit readiness
  10. Daily production surveillance routine
  11. Well test validation and allocation checks
  12. Monthly production reporting to the regulator
  13. Quarterly decline curve and forecast refresh
  14. Weekly well review with operations
  15. Artificial lift run life and failure log
  16. Well integrity surveillance and barrier register
  17. Annual reservoir data acquisition plan
  18. Well work opportunity register
  19. Annual reserves and resources update
  20. Production database housekeeping
  21. Material balance analysis practice
  22. Nodal analysis and inflow performance modelling
  23. Pressure transient analysis fundamentals
  24. Log interpretation for petroleum engineers
  25. Drilling engineering basics for non-drillers
  26. Reviewing an inherited reservoir simulation model
  27. Production chemistry and flow assurance awareness
  28. Petroleum economics for well proposals
  29. Artificial lift selection for a candidate well
  30. Workover or recompletion proposal
  31. Waterflood performance review
  32. Infill drilling candidate screening
  33. Sand management strategy review
  34. Deferred production loss analysis
  35. Idle well and abandonment candidate review
  36. New well proposal and basis of well design
  37. Drill the well on paper before spud
  38. Completion or well test programme execution
  39. Post-well review and lessons learned
  40. Annual field development plan and budget submission
  41. Technical paper or conference presentation
  42. First-year rotation plan for a graduate petroleum engineer
  43. Rotational field engineer handover routine
  44. Moving from a service company to an operator role
  45. Independent petroleum engineering consulting practice
  46. Stepping up to subsurface or asset team lead
  47. Enhanced oil recovery screening study
  48. Integrated asset model linking reservoir, wells and network
  49. Probabilistic production forecast with uncertainty ranges
  50. Peer review of another asset's subsurface work

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Petroleum engineering role and deliverables map

Petroleum engineering titles hide very different jobs: a reservoir engineer owns forecasts and reserves, a drilling engineer owns well designs and programmes, and a production engineer owns the wells once they flow. Writing down which deliverables are yours, who signs them and who consumes them stops you doing a neighbour's work twice and missing your own. Do it in your first two weeks, before the calendar fills up.

First tasks

  • List every report, model and programme you have been asked for so far
  • Ask your manager which of them you own and which you only contribute to
  • Collect the most recent issued copy of each owned deliverable
  • Write the deliverables map and send it to your manager for agreement

Field fact sheet for your assigned asset

New engineers often spend months answering basic questions about a field from memory and old slide packs. A two-page fact sheet with reservoirs, drive mechanism, well count by status, fluid type, facilities capacity and the production history curve gives you, and everyone you brief, one agreed starting point. It also shows quickly where the data is thin.

First tasks

  • Pull the latest well status list from the production database
  • Plot field production by year from first production to date
  • Summarise reservoirs, drive mechanism and fluid type in one table
  • Ask a senior engineer on the asset to review the sheet for errors

Well file and data source inventory

Well data is usually scattered across a technical database, a document system, shared drives and the drawer of someone who retired. Mapping where each kind of record lives, from deviation surveys and logs to completion diagrams, test reports and intervention histories, saves hours on every later study and shows which wells have missing files before a regulator or partner asks.

First tasks

  • List the data types you have needed in your first month on the asset
  • Find where each type is stored and who is the custodian
  • Check ten wells for a complete file and record what is missing
  • File any new well reports into the right well folder @recurring(monthly:28)

Make it yours.

Install Petroleum Engineering Practice, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.