FlowSync · Flow Simulator · Hydraulics

Steady-state and transient hydraulics, on today’s data.

Flow Simulator runs liquids and gas across gathering, transmission and distribution: steady-state for the questions that come up daily, transient for line pack, blowdown, surge and emergency response.

For Pipeline and Hydraulics Engineers · Engineering Managers · Gas Control and Operations

12 in12 inCity gateRS-1RS-2RS-3NorthMill RoadSouthIndustrialEast58 psig47 psig41 psig27 psig
Illustrative schematic, synthetic values, no geography

Part of FlowSyncYou buy FlowSync from WorkSync. Flow Simulator is the hydraulic simulation capability of FlowSync, and it ships with the platform.

What Flow Simulator is

Hydraulics that describe the system you are running today.

Liquids and gas, across gathering, transmission and distribution. Steady-state for the questions that come up daily, transient for the events that decide how the system is designed and operated.

It runs on the model Model Builder maintains and the conditions DataHub is reading now, so the answer describes the system as it is rather than as it was when someone last exported it.

What it does

6 capabilities that turn your existing stack into action.

How a study runs

Four steps, and none of them is a rebuild.

The model is already there and already current, so the engineer's time goes into the case and the interpretation.
  1. Case

    Start from the live model

    The network comes from Model Builder and is already current, so a study starts at the question rather than at a rebuild. You set the case: the volumes, the boundary conditions, the equipment in or out.

  2. Run

    On the conditions DataHub is reading now

    Steady-state or transient, on current pressures, flows and temperatures rather than a quarterly snapshot. The same case can be re-run against a different day without rebuilding anything.

  3. Reconcile

    Compare the model against measurement

    Modeled results sit beside your own meters. Where they part company, the difference is shown per element, which is how a model earns trust and how a bad input gets found.

  4. Publish

    The study is a versioned record

    Inputs, assumptions, the model version and the result are kept together. The next engineer can see what was run, on what, and why, instead of finding a file named final-v3 and guessing.

On calibration

A model you have not checked against measurement is an opinion.

Because the same operating history that feeds the run is stored beside it, a case can be replayed against a day you already have meter data for, and the modeled profile put beside the measured one.

Where they disagree, the difference is attributed per element rather than absorbed into a global efficiency factor, so a wrong roughness, a throttled valve or a mis-stated diameter shows up as a place on the map.

Calibration becomes part of running the system rather than a project someone schedules.

A gathering meter skid in a grass field in evening light: a horizontal filter vessel, yellow-painted pipe with flanged valves and a meter run, a grey control cabinet and a telemetry mast, with wooded pasture behind
A gathering meter skid on a gas system, with its telemetry mast

What it replaces

Retires the workarounds your team has been stacking for years.

Works with your existing stack

Reads the systems you already run.

The model

  • FlowSync Model Builder
  • GIS topology and elevation
  • As-builts and MOC history

Pricing · FlowSync

Scoped to your operation.

Impact Guarantee · license fees only when the metrics move

You buy FlowSync from WorkSync; the tracks beside this are rollout scopes of that one purchase.

Scoped to your well count and systems with our implementation team when you plan your pilot. The pilot runs four weeks on one field, and DataHub is included.

See How Pricing Works

GOOD
Model Builder + DataHub on one system
BETTER
adds Flow Simulator for steady-state and transient work
BEST
adds Process Simulator and Taylor across the engineering library

Proof

Hydraulic model builds went from weeks of manual effort to minutes of verification, across 2,000+ miles of pipeline modeled.Deployment account, anonymized. WorkSync Research, Volume V
  • 2,000+
    Miles of pipeline modeled
    Deployment account
  • Weeks → minutes
    The model build ahead of a study
    Deployment account
  • Live
    Runs on current DataHub conditions, not a quarterly snapshot
  • 4 wk
    Pilot on one network
    Standard rollout cadence

Before you ask

Common questions

What is FlowSync Flow Simulator?
Flow Simulator is the FlowSync module that runs hydraulic simulation for liquids and gas across gathering, transmission and distribution systems: steady-state for daily planning and capacity work, transient for line pack, blowdowns, surge and emergency response. It runs against the model Model Builder maintains and the operating conditions DataHub reads, so a study does not start with a model rebuild.
Does it replace Synergi, OLGA or PipeSim?
Only if you want it to. The common arrangement keeps Synergi Pipeline Simulator, Synergi Gas, OLGA or PipeSim for the deep, once-a-project work those tools are built for, with FlowSync building and maintaining the model in front of them and handling the questions that come up every week. Your tools and your licences stay where they are; what changes is that nobody rebuilds a network by hand before a study.
Steady-state or transient: which do we actually need?
Both, for different questions. Steady-state answers whether the system can carry a volume and where the pressure is going. Transient answers what the system does in the first minutes and hours after something changes: a trip, a valve closure, a blowdown, a supply interruption. Operators who only run steady-state tend to discover the transient questions during an event.
How current is the data a run uses?
As current as your historian and SCADA are, because DataHub reads them read-only and the run takes its boundary conditions from there. You can also replay a case against a specific day in the operating history, which is how a model gets checked against measurement you already trust.
How do we know the model is calibrated?
Modeled results are compared against your own meters and the difference is attributed per element rather than absorbed into one global factor. That is what turns calibration from a scheduled project into part of running the system, and it is what makes a disagreement actionable: it points at a place, not at the model in general.
What does it cost?
License fees only when the metrics move. Pick the operating metric that matters, most often study turnaround or model freshness. We agree the baseline in week zero and measure at week four. Scope is set with our implementation team when you plan your pilot, and DataHub is included.

Run a real case on your own network.

Bring one system and a study you already ran by hand. We build the model from your documents, run the same case on current conditions, and put the two results beside each other with the differences explained.