Oil Well Completions Concepts and Calculations Part 1
Oil Well Completions Concepts and Calculations Part 1
- Lifetime access
- Certificate of completion
- Interactive Video Lessons
- Completion Certificate
Why enroll
What enrolled engineers say
The way the abstractions get unpacked made it easier to map equations to what shows up in oilgas field data, and it’s easier to reason about than I expected. The worked example in Section 2.4 backing RPS out from perforation diameter and skin stuck with me, especially the psi/ft conversion step that people usually hand-wave. I’ve already mirrored that calc in a scratch repo and sanity-checked it against a small PR at work; it fits our completions arch, and I don’t feel lost jumping between notes and prod. wished there was more on nodal edge cases during frac hits, but it’s sharpened my sense of where abstractions tend to leak.
Found this while auditing obs gaps tied to our oilgas work, and the first gripe: module 3’s pacing felt uneven, with the spreadsheet setup assumed and not shown. Past that, it clicked fast. The section on perforation friction calculations stuck, especially the worked example where RPS is varied and you see skin swing in the table. That translated cleanly when I sanity-checked numbers in our repo for a completions study. I liked how the arch tradeoffs between tubing ID and frac stages were framed without fluff. It doesn’t try to be infra-heavy, but the math maps to prod decisions I see in PRs. I’ve already reused the casing burst check logic during review time, so this felt like a good use of PD hours.
The framing around testability went deeper than expected, especially when it tied completion choices back to how you actually verify behavior later. The section on pressure test envelopes, where the instructor walks through a tubing/casing pressure calc and then sanity-checks it against field limits, stuck with me; it felt like reading an arch decision memo rather than a slide deck. As someone bouncing between legacy oilgas work and modern infra, I kept mapping it to prod guardrails, CI checks, and the stuff that keeps RPS spikes from surprising you. There's a practical throughline about keeping assumptions consistent across steps, not just getting the math right—helpful if you’ve ever debugged a mismatch between a spreadsheet and what obs says. I wasn't sold on the pace of the cementing overview; wished there was a bit more on failure modes before moving on. Still, the way it weighs consistency tradeoffs across completion options is the part I’ll probably reuse.
Your instructor
Team OG
Oil & Gas Domain
Upstream Oil & Gas Technical Professional
Is this course for you?
You should take this if
- You work in Oil & Gas Upstream
- You're a Petroleum Technology professional
- You have some foundational knowledge in the subject
- You prefer self-paced learning you can revisit
You should skip if
- You're looking for an introductory overview course
- You need a different specialisation outside Petroleum Technology
- You need live interaction with an instructor
Course details
Course suitable for
Key topics covered
Course content
The course is readily available, allowing learners to start and complete it at their own pace.
- Oil Well Completions26 min
Opportunities that await you!
Career opportunities
Why people choose EveryEng
Industry-aligned courses, expert training, hands-on learning, recognized certifications, and job opportunities-all in a flexible and supportive environment.
What learners say about this course
This course nudged how I think about legacy choices, kind of like refactoring old arch without breaking prod. It frames sand control as tradeoffs instead of rules, which clicked for me coming from software and infra, especially when you’re juggling constraints that look a lot like CI gates and RPS limits. The micro-detail that stuck was the screen sizing example in the “Gravel Pack vs Frac Pack” section, where they walk through median grain size and then show how one assumption cascades into cost and ops risk—felt like reading a PR where one default sneaks into prod. I wasn’t sold on every analogy to modern completions; the k8s-style modularity pitch was mostly helpful but a bit hand-wavy in spots. Still, the beginner pacing worked, and the oilgas context mapped cleanly to how we think about legacy systems in energyutilities. I’ve already got a note to tweak some of our internal logic after this, mostly around how we document assumptions before they fossilize in the repo.
For a beginner course, the Chapter 3 pipeline sizing walk-through using the Weymouth equation stuck, the step where they sanity-check RPS vs linepack. As a TL in energyutilities, it's useful for onboarding—I've pointed juniors at it, but I wasn't sold on the coverage of ops/infra handoffs and wished there was more on safety before prod.
The section headers pulled me in, and the content mostly delivered. Chapter 3’s pipeline hydraulics example, walking a pressure drop calc end to end, stuck; it clicked like budgeting RPS before a prod push, and the compressor station tradeoffs read like arch notes you’d leave on a PR. it's beginner-friendly without talking down, though I wasn't sold on how light the infra/obs tie-in was for energyutilities oilgas ops. I’ve already avoided a couple late CI-style scrambles that would've felt like debugging at 2am.
Scheduling-friendly modular chunks made it easy to fit between meetings without losing context. The beginner framing didn't dumb things down; it mapped the gas arch from wellhead to pipeline ops with enough math to reason about prod issues. Chapter 3's worked example on pressure drop comparing Panhandle A vs Weymouth stuck, especially the aside on when assumptions break at low Reynolds numbers. The metering section on standard vs actual cubic feet and temperature correction felt like reviewing a PR where unit consistency can quietly bite prod and infra. Mostly good pacing, though I wasn't sold on the quick skim of compressor controls; wished there was more on failure modes and obs in real stations. The careful handling of consistency tradeoffs across equations and field conventions is the part I keep referencing back to.
Oct 2, 2026 
