Skip to main content

FlowSync · Taylor · Engineer Agent

The senior engineer who never retires.

Taylor is the engineer agent inside FlowSync. She reads your drawings, MOCs, procedures and the codes your team works to, answers against the live model, and cites the document behind every answer. She works in chat, in the simulator, in the document viewer, and inline while an MOC or a procedure is being drafted.
See Your Wells RankedPlan Your Pilot

For Engineering Managers · Process and Pipeline Engineers · Operations and Compliance

Taylor, the FlowSync engineer agent
Taylor, the engineer agent inside FlowSync
Cited
Every answer points at the document it came from
Weeks → minutes
The model build she answers against, deployment account
2,000+
Miles of pipeline modeled, deployment account
4 wk
Pilot on one project folder, standard rollout cadence

Part of FlowSyncYou buy FlowSync from WorkSync. Taylor is the engineer agent of FlowSync, and it ships with the platform.

What Taylor is

An engineer agent that has read everything your team wrote down.

Not a wrapper on a chat box. Taylor works on your own engineering library and on the live model, and every answer arrives with the document it came from.

Engineering knowledge in an operator is mostly written down and mostly unfindable. It is in a decade of MOCs, in procedures, in incident write-ups, in the margin of a drawing, and in the head of the engineer who is retiring next year. The cost of that is not dramatic, it is daily: a half day hunting for the right revision, a decision remade because nobody could find the last one, a study rerun because its assumptions were never written beside it.

Taylor is the part of FlowSync that makes that library answerable. She reads it, she answers against the model Model Builder maintains, and she cites her sources, so an engineer can check her in one click instead of taking an answer on trust.

The question
4 examples
What you ask
Why is this line sized the way it is?The sizing basis, the change that revised it, and a link to both documents at the page that states them.
What happens to the outlet if we take another 12 MMcf/d?A sensitivity run on the live model, with the case, the assumptions and the elements that bind it.
Draft the MOC for replacing this control valve.A drafted package for an engineer to edit and approve. She does not submit it, and she does not approve it.
What did we decide last time this happened?The prior decision, who made it, what it was based on, and the document it is written in.

What it does

6 capabilities that turn your existing stack into action.

  1. 01

    Reads your engineering library

    Drawings, datasheets, as-builts, a decade of MOCs, operating procedures and incident write-ups, plus the codes your team works to. Her knowledge of your asset comes from your documents, not from a general impression of the industry.
  2. 02

    Cites her sources on every answer

    Each answer carries the drawing, datasheet, MOC or code clause behind it, at the page. Checking her takes one click, which is what makes an answer usable by an engineer who has to sign their name to the work.
  3. 03

    Runs sensitivities on the live model

    Questions about behaviour are answered by running the model Model Builder maintains rather than by recalling a figure. The case and the conditions it ran on come back with the result.
  4. 04

    Drafts the paperwork, for a person to approve

    MOC packages, calculation packages, operating procedures and incident summaries arrive as drafts built from your own templates and precedents. The engineer edits and approves; Taylor does not submit and does not sign.
  5. 05

    Explains the decision a previous engineer made

    She can retrieve why a line was sized the way it was, what changed it, and what was decided the last time a similar thing happened, with the documents attached. That is the part of the retiring engineer that was written down.
  6. 06

    Works where the work happens

    In chat, in the simulator beside a run, in the document viewer, and inline in MOC and procedure workflows. Nobody has to leave the task to ask the question.

How an answer is built

Retrieve, ground, cite, hand over.

The order matters. An answer that cannot name its source is a guess with good grammar, and an engineer cannot sign their name to it.
  1. 1 · Retrieve

    From your library, not the open internet

    Taylor searches your own drawings, MOCs, procedures, datasheets and incident records, plus the codes your team works to. Where an answer has no support in those sources, she says so rather than filling the gap.
  2. 2 · Ground

    Against the live model

    Questions about behaviour are answered by running the model, not by recalling a number. The case she ran, and the conditions it ran on, come back with the answer.
  3. 3 · Cite

    Every claim points at a document

    Each answer carries the drawing, datasheet, MOC or code clause behind it, at the page. Checking her is one click, which is the only way an engineer can responsibly use an answer they did not derive.
  4. 4 · Hand over

    A person approves

    Drafted MOCs, calculation packages and procedures arrive as drafts. Taylor assists inside a controlled workflow: she does not submit, approve, or change a system of record on her own authority.
  1. Your library
    Drawings, MOCs, procedures, incidents

    Your own documents, plus the codes your team works to.

  2. FlowSync
    The live model

    Maintained by Model Builder, run by Flow Simulator and Process Simulator.

  3. Taylor
    The answer, with its sources

    Retrieved, grounded in a run where behaviour is in question, and cited at the page.

  4. An engineer
    Reviews and approves

    Drafts stay drafts until a person signs them. Nothing is submitted on her authority.

Taylor assists inside a controlled workflow. She reads broadly, she writes drafts, and the approval stays with the engineer whose name goes on the work.

Where she stops

Built to make your best engineers faster. Not to replace them.

Taylor does not approve an MOC, sign a calculation, change a system of record or make an operating decision. She retrieves, she runs cases on the model, she drafts, and she shows her working. Where the library does not support an answer, she says the library does not support it, which is the behaviour that makes the rest of it usable. Access follows your own permissions, and your engineering library stays yours: WorkSync is SOC 2 Type II in progress, with the report targeted for Oct 30, 2026.

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 half day hunting for the right revisionThe document exists, it is just unfindable across drives, folders and email. Retrieval against the whole library ends the hunt.
Waiting on the one engineer who knowsThat person is in a meeting, on a plane, or retiring. A question that only one calendar can answer is a bottleneck with a name.
Knowledge that walks out at retirementMost of it was written down somewhere. What was missing was a way to ask the library a question and get the document back with the answer.
An assistant that cannot show its workAn answer with no source cannot be checked, so an engineer has to redo it. Citations are the difference between a tool and a curiosity.

Works with your existing stack

Reads the systems you already run.

Engineering library
  • Drawing and document stores
  • SharePoint and network file shares
  • MOC packages and procedures
  • Incident and investigation records
Codes and standards
  • API
  • ASME
  • AGA and PHMSA
  • ISA and NFPA
The model
  • FlowSync Model Builder
  • FlowSync Flow Simulator
  • FlowSync Process Simulator
Operating data
  • WorkSync DataHub
  • AVEVA PI System
  • Proficy Historian
  • Maintenance and CMMS history
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 system
BETTER
adds Flow Simulator and Process Simulator on the same model
BEST
adds Taylor across your engineering library and MOC workflow

Proof

Hydraulic model builds went from weeks of manual effort to minutes of verification, across 2,000+ miles of pipeline modeled. Taylor answers against that same model.

Deployment account, anonymized. WorkSync Research, Volume V

Read the white paper on automated hydraulic model builds →

Before you ask

Common questions

Is Taylor a chatbot or something more?
More. Taylor is the engineer agent inside FlowSync. She reads every drawing in your project folder, the MOCs behind them, the procedures they touch and the codes your team works to, and she answers against the live model rather than from memory. She drafts MOC documents, runs sensitivity studies on the model, retrieves cited answers inside the simulator, and explains why a previous engineer made the call they did. She is part of the platform, not a wrapper on top of it.
What is she trained on, and does our library go anywhere?
She works on your own engineering library and your own model, under your own access permissions, plus the public codes and standards your team works to. Access to source systems is read-only, your systems of record stay authoritative, and WorkSync is SOC 2 Type II in progress with the report targeted for Oct 30, 2026. Security architecture and the data-handling detail are on the security page.
How do we know an answer is right?
You check it, and she makes that cheap. Every claim carries the drawing, datasheet, MOC or code clause it came from, at the page. Anything about system behaviour is answered by running the live model, and the case and conditions come back with the result. Where the library does not support an answer, she says so instead of filling the gap, which is the behaviour that makes the rest trustworthy.
Can Taylor change anything on her own?
No. She retrieves, runs cases, and drafts. An MOC package, a calculation package or a procedure arrives as a draft for an engineer to edit and approve. She does not submit, approve or write to a system of record on her own authority. Agents assist inside a controlled workflow here, deliberately.
Does this replace engineers?
It is built to make your best engineers faster, not to replace them. The work it takes off the desk is retrieval, transcription and first drafts. The work it hands back is judgement, which is what an operator is short of and what the retiring generation is taking with them.
What do we need in place before Taylor is useful?
A model and a library. In practice that means Model Builder connected to your drawings and GIS, and DataHub reading your operating data, which is the same four-week pilot the other modules run. Taylor gets sharper as more of the library is connected, because her answers are only as good as the documents she is allowed to read.
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 Taylor on your project folder.

Bring one project folder and the questions your team keeps having to chase down. Four weeks later you can see what she retrieves, what she cites, and where she says the library does not answer it.

See Your Wells RankedTalk to us