Shutting a well in from a distance is easy - failing safe closed is the natural safe direction. Bringing it back is the hard part, because reopening a well means restoring pressure and flow, and doing that carelessly can be dangerous. Remote well startup is the capability to reopen a shut-in well from SCADA without sending a truck and a person, done in a way that is verified and controlled. This guide covers the permissive checks the RTU confirms before it will start, the sequence it follows to bring the well back, and why remote start is fundamentally harder to make safe than remote shut-in.
Remote Well Startup in one line: Remote well startup is the ability to bring a shut-in well back online from a SCADA host without a site visit. Before it acts, the RTU verifies a set of permissives - pressures in expected ranges, valves in known states, no active ESD or lockout - then executes a controlled reopen sequence rather than snapping the well fully open. It is harder to make safe than remote shut-in because opening restores hazardous pressure, whereas closing removes it.
A remote start does not simply reverse the shut-in - it is gated behind permissives, conditions that must all be true before the RTU will begin. The RTU checks that pressures are where they should be for a safe start: a flow-line pressure that makes sense, no evidence of a downstream blockage, casing and tubing pressures within expected bounds. It confirms valve states are known and consistent - that the valves it expects to be closed are closed and there is no conflicting position feedback. Above all it confirms there is no active emergency shutdown, no latched trip, and no operator lockout standing in the way. If any permissive is not satisfied, the start does not proceed and the operator is told why.
These permissives exist because a remote operator cannot see, hear, or smell the site. A person standing at the wellhead would notice a leaking connection, a valve someone left in the wrong position, or a hazard that no sensor reports. Remote start has to substitute verified instrument readings for that human presence, which means it can only be trusted where the instrumentation genuinely covers the conditions that matter. The permissive set is the codified version of what a competent operator would check before opening the well by hand, enforced by the RTU so the start cannot go ahead into a state the sensors say is wrong.
Even with every permissive satisfied, a well is not snapped fully open in one motion. The startup follows a controlled sequence so pressure and flow are re-established in a managed way. Depending on the installation this can involve equalizing pressure across the valve before it opens fully, opening in stages, or bringing the well back through a defined path so the system is not shocked. The RTU steps through the sequence, watching the pressures and valve positions at each step and only advancing when the readings confirm the previous step completed as expected. If the response is wrong at any step - a pressure that does not build as it should, a valve that does not confirm open - the sequence halts rather than pressing on blindly.
This step-and-verify approach is what makes the reopen safe to automate. Each action produces an expected sensor response, and the RTU treats a missing or wrong response as a reason to stop and alarm, not something to power through. The sequence also honors any downstream readiness the site depends on, so the well is not brought back into a system that cannot receive its flow. The result is a bring-back that behaves like a careful operator working through a checklist - deliberate, observed at every stage, and abortable the instant reality diverges from the plan - rather than a single command that flings the well wide open and hopes.
The asymmetry between shut-in and start is fundamental. Shutting in removes energy from the surface system - it makes the well safer by closing it - so failing in the safe direction is easy and a fault that causes a shut-in is tolerable. Starting up adds energy back: it restores pressure and flow, the very things that can leak, over-pressure, or harm someone if the system is not sound. There is no equivalent to fail-safe for opening, because opening on a fault is exactly what you must never do. That is why remote start is hedged with permissives and staged sequences while remote shut-in can be a single trusted command.
With a cloud SCADA platform such as Merobix, remote startup is delivered as a supervised action, not a blind one. The operator initiates the start from a browser, but the RTU is what enforces the permissives and drives the controlled sequence locally, reporting each check and each step back to the host so the operator watches the bring-back unfold and sees exactly why it stops if a permissive fails. Because the intelligence that decides whether it is safe to open lives at the RTU, the cloud link is the way a human authorizes and observes the start rather than the thing responsible for its safety. That division - human intent and visibility from the cloud, verified permissives and staged control at the edge - is what lets an operator responsibly bring a remote well back without rolling a truck.
Because shutting in removes energy from the system - it closes the well and makes it safer - so failing in the safe direction is straightforward. Starting up adds pressure and flow back, which are the very things that can leak, over-pressure, or cause harm if the system is not sound. There is no fail-safe equivalent for opening, since opening on a fault is exactly what must never happen, so start requires permissive checks and a controlled sequence rather than a single trusted command.
It verifies that pressures are in expected ranges with no sign of a downstream blockage, that valve positions are known and consistent, and that there is no active emergency shutdown, latched trip, or operator lockout in the way. These conditions substitute verified instrument readings for the human presence a remote start lacks. If any permissive is not satisfied, the RTU refuses to start and reports which condition blocked it.
Only where the instrumentation genuinely covers the conditions a person would otherwise check by hand. Remote start substitutes sensor readings for a human at the wellhead, so it is safe to automate only when pressures, valve states, and trip status are all reliably measured and the reopen can be staged and verified. A site without that coverage cannot be trusted to a remote start, because the RTU would have no way to confirm the conditions the permissives depend on.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.