FlowSync · Taylor · Engineer Agent
The senior engineer who never retires.
Taylor is the engineer agent inside FlowSync.
For Engineering Managers · Process and Pipeline Engineers · Operations and Compliance

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.
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.
| What you ask | What she reads | What comes back |
|---|---|---|
| Why is this line sized the way it is? | What she readsThe original design basis, the alignment sheet, and the MOC that changed it in between. | What comes backThe 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? | What she readsThe live model, current operating conditions, and the equipment ratings on the units in the path. | What comes backA 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. | What she readsYour MOC template, the prior MOCs on similar equipment, the datasheets and the procedures they touch. | What comes backA 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? | What she readsA decade of MOCs, incident write-ups and operating procedures in your own library. | What comes backThe prior decision, who made it, what it was based on, and the document it is written in. |
| What is this Synergi run actually telling us? | What she readsThe output of the run, whether it came from Synergi, HYSYS, ProMax or OLGA, beside the model and the case it was run on. | What comes backA plain reading of the result, the elements that bind it, and the drawings and datasheets behind those elements. |
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.
What it does
7 capabilities that turn your existing stack into action.
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.
A study result from Synergi, Aspen HYSYS, ProMax or OLGA can be read beside the model and the case it ran on. Taylor explains what the run is showing, which elements are binding it, and which drawing or datasheet each of those elements came from, so the interpretation is checkable rather than taken on trust.
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.
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.
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.
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.
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.
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.
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.
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.
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.
- Your libraryDrawings, MOCs, procedures, incidents
Your own documents, the codes your team works to, and the study output your simulators produce.
- FlowSyncThe live model
Maintained by Model Builder, run by Flow Simulator and Process Simulator, and by Synergi, HYSYS, ProMax or OLGA where your team runs those.
- TaylorThe answer, with its sources
Retrieved, grounded in a run where behaviour is in question, and cited at the page.
- An engineerReviews and approves
Drafts stay drafts until a person signs them. Nothing is submitted on her authority.
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 secure by design.
What it replaces
Retires the workarounds your team has been stacking for years.
The document exists, it is just unfindable across drives, folders and email. Retrieval against the whole library ends the hunt.
That person is in a meeting, on a plane, or retiring. A question that only one calendar can answer is a bottleneck with a name.
Most 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 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 and the runs
- FlowSync Model Builder
- FlowSync Flow Simulator
- FlowSync Process Simulator
- Study output from Synergi, HYSYS, ProMax and OLGA
Operating data
- WorkSync DataHub
- AVEVA PI System
- Proficy Historian
- Maintenance and CMMS 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.
- 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
- CitedEvery answer points at the document it came from
- Weeks → minutesThe model build she answers againstDeployment account
- 2,000+Miles of pipeline modeledDeployment account
- 4 wkPilot on one project folderStandard rollout cadence
Before you ask
Common questions
Is Taylor a chatbot or something more?
What is she trained on, and does our library go anywhere?
How do we know an answer is right?
Can Taylor change anything on her own?
Does this replace engineers?
What do we need in place before Taylor is useful?
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.
- ModuleFlow SimulatorSteady-state and transient hydraulics for liquids and gas, run against current operating conditions rather than a snapshot.
- ModuleProcess SimulatorDehydration, sweetening, compression and separation, sized for the everyday facility questions your team answers each week.
- 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.
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.