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
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.
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.
| Mode | The question | What that covers |
|---|---|---|
| Steady-state | The questionCan this system carry the volume we just signed? | What that coversCapacity checks, looping and compression studies, pressure profiles, hydraulic bottleneck hunting, new connection and load addition, class location and MAOP checks against the profile you have. |
| Steady-state | The questionWhere is the system giving back pressure we are paying for? | What that coversLine-by-line pressure drop against measurement, so a restriction shows up as a place on the map rather than a hunch about the trunk line. |
| Transient | The questionWhat does the system do in the first hour after that changes? | What that coversLine pack and drawdown, compressor or pump trip, valve closure and surge, blowdown and repressurization, emergency shutdown sequencing, supply interruption on a distribution network. |
| Transient | The questionHow long do we have before a customer feels it? | What that coversPack drawdown timing under a defined loss, which is the number that decides whether an event is an operating problem or a notification. |
Most hydraulic studies are late for the same reason: the model has to be rebuilt before the question can be answered, and by the time it is rebuilt the operating condition it was built for has moved.
Flow Simulator removes that step by running on the model Model Builder maintains and the operating data DataHub is already reading. On a deployment account, that build step went from weeks of manual effort to minutes of verification, across 2,000+ miles of pipeline modeled.
It is not a replacement play. Plenty of operators keep Synergi Pipeline Simulator, Synergi Gas, OLGA or PipeSim for the deep, once-a-project work and use FlowSync for the model behind it and the questions that come up every week. Both arrangements are normal, and the model is the same either way.
Where the line sits, plainly. Flow Simulator is built for the steady-state and transient work an operating team runs on its own network week to week: capacity and looping, pressure profiles, line pack and drawdown, trips, valve closure and blowdown.
The deep flow-assurance study stays where it belongs, which for most teams means detailed multiphase and slugging work in OLGA, well and production-system modeling in PipeSim, and the regulated pipeline study in Synergi Pipeline Simulator. Those runs get the same maintained model rather than a second hand-built one.
What it does
6 capabilities that turn your existing stack into action.
Capacity and looping studies, compression and pump checks, pressure profiles, new load and new connection work, bottleneck hunting. The cases that come up weekly, run against the network as it is currently configured.
Line pack and drawdown, compressor and pump trips, valve closure and surge, blowdown and repressurization, emergency shutdown sequencing. The behaviour in the first hour, which is where the operating decision actually sits.
Single-phase gas, single-phase liquid, multi-phase gathering, water systems and distribution networks run through the same model-building and simulation loop rather than through a different tool and a different model for each fluid class.
Boundary conditions, setpoints and current measurement come through DataHub read-only. A case can be run on today, or replayed against a day in the operating history, without anyone exporting anything.
Modeled results are placed beside your meters and the difference is attributed per element, so a wrong roughness or a throttled valve shows up as a location rather than disappearing into a global efficiency factor.
Inputs, assumptions, the model version and the result are kept together as one record. Reruns are honest comparisons rather than a folder of near-identical files, and the reasoning stays attached to the result.
How a study runs
Four steps, and none of them is a rebuild.
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.
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.
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.
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.
- Model BuilderThe maintained model
Topology, equipment and specs, re-read as documents change.
- DataHubCurrent operating conditions
Pressures, flows, temperatures and setpoints, read-only.
- Flow SimulatorSteady-state or transient run
Reconciled against your own measurement.
- OutputsA versioned study
Kept with its inputs and assumptions, readable by Taylor, and exportable to Synergi, OLGA, PipeSim or HYSYS.
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.

What it replaces
Retires the workarounds your team has been stacking for years.
The model is already built and already current. On a deployment account, that build step went from weeks of manual effort to minutes of verification.
A snapshot answers the question the system was asked then. Live conditions answer the one you are asking now, which is usually why the study was requested.
A single-line hand calculation cannot see interaction between branches, and it certainly cannot see what happens in the hour after a compressor trips.
When the inputs and assumptions are not stored with the result, the next person reruns the study rather than trusting it. Versioned studies end that.
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
Operating data
- WorkSync DataHub
- AVEVA PI System
- Proficy Historian
- SCADA and gas control
Measurement
- Custody and check meters
- Pressure and temperature history
- Allocation and production accounting
Engineering tools
- DNV Synergi Gas and Synergi Pipeline Simulator
- SLB OLGA and PipeSim
- Aspen HYSYS and Honeywell UniSim
- Steady-state and transient model export
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.
- 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
- 2,000+Miles of pipeline modeledDeployment account
- Weeks → minutesThe model build ahead of a studyDeployment account
- LiveRuns on current DataHub conditions, not a quarterly snapshot
- 4 wkPilot on one networkStandard rollout cadence
Before you ask
Common questions
What is FlowSync Flow Simulator?
Does it replace Synergi, OLGA or PipeSim?
Steady-state or transient: which do we actually need?
How current is the data a run uses?
How do we know the model is calibrated?
What does it cost?
The rest of FlowSync
Every module reads the same model.
- ModuleModel BuilderBuilds the network and facility model from the P&IDs, datasheets, as-builts and GIS you already maintain, and keeps it current.
- ModuleProcess SimulatorDehydration, sweetening, compression and separation, sized for the everyday facility questions your team answers each week.
- Engineer agentTaylorReads your engineering library and answers against the live model, with the source document cited on every answer.
- OverviewFlowSyncThe whole engineering capability: how the model gets built, how it stays current, and the three ways operators deploy it.
- FoundationWorkSync DataHubThe read-only integration backbone the model runs on, included with FlowSync. Your systems of record stay authoritative.
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.