Skip to main content

FlowSync · Process Simulator · Facilities

Facility answers in minutes, from the drawing you already have.

Process Simulator covers the everyday facility work: dehydration, sweetening, compression, separation, and the sizing, revamp and debottleneck checks that come up every week. It runs on the same model Model Builder maintains, so the answer reflects the equipment currently installed and the conditions currently measured.
See Your Wells RankedPlan Your Pilot

For Facilities and Process Engineers · Engineering Managers · Plant Operations

A gas facility valve manifold under a heavy sky: a hand-wheel gate valve, three yellow actuators and process vessels behind them
Facility valving and vessels, the everyday subject of a process question
Weeks → minutes
The model build ahead of a study, deployment account
2,000+
Miles of pipeline modeled, deployment account
1
Asset specification, shared with the deeper study you already run
4 wk
Pilot on one facility, standard rollout cadence

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

What Process Simulator is

Sized for the work that fills the week, not the once-a-decade greenfield.

Dehydration, sweetening, compression, separation and small-facility design, answered from the drawing and the live operating data rather than from a model somebody has to build first.

The bulk of operator process engineering is not greenfield design. It is a rate change, a revamp check, a debottleneck, a spec question, a what-if before a turnaround. Those questions are worth a day, not a project, and they are usually answered in a spreadsheet nobody can audit because standing a full study up would take longer than the answer is worth.

Process Simulator is built for exactly that band of work. It reads the facility from the model Model Builder maintains, runs on the conditions DataHub is reading, and keeps the assumptions attached to the result. When the question turns out to need the deep study your team does elsewhere, the same verified asset specification goes with it rather than being rebuilt.

  1. Dehydration

    Glycol and desiccant

    Contactor and regenerator performance, circulation rate, water dew point against the contract spec, and what happens to all of it when inlet rate or inlet temperature moves.
  2. Treating

    Sweetening and stabilization

    Amine and scavenger duty, treated gas specification, stabilizer and separator performance, and the operating window between meeting spec and wasting energy.
  3. Compression

    Stations and units

    Stage pressures and ratios, horsepower and fuel, recycle and cooling duty, and whether the installed unit still fits the rate the field is making now.
  4. Separation

    Vessels and flash

    Two- and three-phase separation, flash and vapor recovery, relief and flare loads, and the liquids the design assumed against the liquids the field is delivering.

What it does

6 capabilities that turn your existing stack into action.

  1. 01

    The unit operations your facilities actually run

    Dehydration, amine and scavenger treating, stabilization, compression, two- and three-phase separation, flash and vapor recovery, plant utilities and small-facility design. The work that fills an operator engineering week.
  2. 02

    Built from the installed equipment, not a template

    Vessel dimensions, exchanger duties, compressor curves and valve ratings come from the model built out of your P&IDs and datasheets, so a result describes your facility rather than a representative one.
  3. 03

    Runs on measured inlet conditions

    Rate, composition, pressure and temperature arrive through DataHub read-only. When the field changes what it is delivering, the case can be re-run against that instead of against the design basis nobody has revisited.
  4. 04

    Cases sit beside each other

    A revamp, a rate increase and a do-nothing case are compared with the assumptions attached to each, which is what makes the recommendation defensible when someone asks a month later why the call was made.
  5. 05

    Assumptions and results stay together

    Every case keeps its inputs, its assumptions and the model version it ran on. The result stops being a number in an email and becomes a record the next engineer can check rather than redo.
  6. 06

    Hands off cleanly to the deeper study

    When a question genuinely needs the full study your team runs elsewhere, the same verified asset specification goes with it. The deep work stays where it belongs, and nobody describes the facility twice.

How a facility question gets answered

Four steps, inside the working week.

The model is already current, so the engineer spends the day on the comparison and the recommendation.
  1. 1 · Ask

    Start from the installed facility

    The unit comes from the model Model Builder maintains, populated from your P&IDs and datasheets, so the case starts from the equipment you actually have rather than a generic template.
  2. 2 · Run

    On current conditions

    Inlet composition, rate, pressure and temperature come from DataHub read-only. The answer describes the facility as it is operating, which is usually what the question was about.
  3. 3 · Compare

    Cases beside each other

    A revamp, a rate change and a do-nothing case sit side by side with the assumptions attached to each, so the decision is made on a comparison rather than on the most recent run.
  4. 4 · Hand off

    The deep study keeps its home

    When a question needs the full study your team does elsewhere, the same verified asset specification goes with it. Nobody rebuilds the facility a second time to ask a harder question about it.
  1. Model Builder
    The installed facility

    Equipment, ratings and connectivity, read from your P&IDs and datasheets.

  2. DataHub
    Inlet conditions as measured

    Rate, composition, pressure and temperature, read-only.

  3. Process Simulator
    The case, and the cases beside it

    Assumptions recorded with each result.

  4. Outputs
    A decision, or a clean hand-off

    The recommendation, or the same asset specification handed to the deeper study your team already runs.

The facility is described once. Everything after that reads the same description, including the tools your engineers already use for their deepest work.

Why it matters operationally

An answer that arrives after the decision is not an answer.

Facility questions have a shelf life. A rate is accepted or declined, a unit is run harder or it is not, a turnaround scope is set. When engineering takes weeks, the field decides without it and the study becomes a record of what should have happened. Making the everyday question answerable inside the week is what puts engineering back in front of the decision instead of behind it.

The rest of FlowSync

Every module reads the same model.

There is one model of your asset, not one per tool. Build it once, and the simulators, the agent and the simulator your team already runs all work from the same verified picture.

What it replaces

Retires the workarounds your team has been stacking for years.

The workaround
4 retired
What it retires
The sizing spreadsheet nobody can auditIt cannot be checked, cannot be rerun on current conditions, and carries assumptions that live only in the head of whoever built it.
Standing up a full study for a two-day questionThe setup outlasts the decision. By the time the model is ready, the rate has been accepted or the turnaround scope is already set.
A facility model that does not match what is installedEquipment gets replaced, re-wheeled and re-rated, and the model usually does not follow. Building from the current drawings and as-builts is what keeps the two in step.
Waiting for the one person who has the facility model openWhen the model is a personal artifact, engineering capacity is one calendar. When it is maintained by the platform, the question can be asked by whoever has it.

Works with your existing stack

Reads the systems you already run.

The model
  • FlowSync Model Builder
  • P&ID and datasheet extraction
  • As-builts and MOC history
Operating data
  • WorkSync DataHub
  • AVEVA PI System
  • Proficy Historian
  • Lab and chromatograph results
Facility records
  • Equipment registers and asset hierarchy
  • Relief and flare studies
  • Maintenance and CMMS history
Engineering tools
  • The simulator your team already runs
  • Shared asset specification export
  • Calculation packages
  • MOC and procedure workflow
See all 39 integrations 

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 Your Wells RankedSee How Pricing Works
GOOD
Model Builder + DataHub on one facility
BETTER
adds Process Simulator for facility and revamp work
BEST
adds Flow 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

Read the white paper on automated hydraulic model builds →

Before you ask

Common questions

What is FlowSync Process Simulator?
Process Simulator is the FlowSync module for facility process work: gas processing, dehydration, sweetening, compression, separation and small-facility design. It runs on the model Model Builder maintains from your P&IDs and datasheets and on the operating conditions DataHub reads, so the everyday sizing, revamp and debottleneck questions can be answered inside the working week.
Is this meant to replace the deep process study we do today?
No. It is sized for the fast, drawing-driven questions that make up the bulk of operator engineering, and it is designed to hand off cleanly when a question needs the full study your team runs elsewhere. The same verified asset specification goes with the hand-off, so the facility is described once and the deep work keeps its home.
Where do the equipment specifications come from?
From your own documents. Model Builder reads the P&IDs, datasheets and vendor cutsheets, populates vessel dimensions, exchanger duties, compressor curves and valve ratings, and keeps every value traceable to the page it came from. Where a document disagrees with an as-built, the conflict is flagged for an engineer rather than silently resolved.
What if the field is no longer delivering the design basis?
That is the common case, and it is the reason to run on measured inlet conditions. Rate, composition, pressure and temperature come through DataHub, so a unit can be evaluated against what it is actually being fed rather than against the basis it was bought on.
Who uses it day to day?
Facilities and process engineers, and the engineering managers who are trying to get more questions answered than the team currently has capacity for. Operations uses the output more than the tool: what the unit will do at the new rate, whether the revamp is worth it, what to change before the turnaround.
What does it cost?
License fees only when the metrics move. Pick the operating metric that matters, most often study turnaround or engineer time per study. 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.

Put a real facility question through it.

Bring one facility, its drawings, and a question your team is already working on. We build the model from your documents and run the case on measured conditions, beside the answer you arrived at by hand.

See Your Wells RankedTalk to us