Skip to content
PRODUCT OVERVIEW

See the whole factory. Move it faster.

One living model of the factory. IT, OT, and AEC each work it through their own filter, and every change lands everywhere at once.

VERSION 0.9DOMAINS IT · OT · AECPILOTS RUNNINGLOI→FAI −40% TARGET [TK]
01THE PROBLEM

Where factories come from.

Where factories come from

Every factory starts as an agreement — a letter of intent — and ends as mass production. In between: layouts, machine lists, utility loads, construction, commissioning, first article. Years of decisions.

Why it's hard

Three groups own it — IT, OT, AEC — and their tools don't talk. Intent degrades at every handoff. The seams are the problem, and switching between tools is where the schedule goes to die.

What FLM™ changes

One model, three views. Every domain works in its own vocabulary against the same factory. Nothing exported, re-drawn, or lost in translation — and the clock gets its time back.

PH-01LOIthe agreement
−Δ intent
PH-02DESIGNlayouts · systems · building
−Δ intent
PH-03BUILDconstruction · install
−Δ intent
PH-04FAIfirst article
−Δ intent
PH-05OPERATEchange · expand

“These solutions are ancient.” The seams are the problem — and everyone lives with them.

CAD is slow.OT engineer
PPT is dumb.OT engineer
We want to understand OT's intent better and faster.IT lead
How do we communicate exactly about infrastructure locations to OT?AEC planner

Voice of customer, verbatim. Nobody realizes there’s a better way — our job is to show it. ↓

02THE PLATFORM

Same factory. Your filter.

The OT viewMachinery and process, laid out and simulated.

Drag equipment onto the engineering grid, zone the floor, wire connections, and check takt before anything is bolted down. CAD stays your CAD — XENOPS carries the intent.

  • Equipment catalogs with real dimensions and loads
  • Zones, connections, apertures on a 24px snap grid
  • Throughput and bottleneck simulation before commit
VIEW 01 — OT · MACHINERY & PROCESS
feature screenshot — TK
03HOW IT WORKS

The Thread.

Three domains in. One model. Everything downstream falls out of it.

ITsystems & dataERP · MDM · SSO · SECURITYOTmachinery & processCAD · PLM · MES · SCADAAECthe physical plantBIM · CIVIL · GC SCHEDULESXENOPS MODELone factory · three filtersobjects · coordinates · intentchanges propagate everywhereLOIDESIGNBUILDFAILOI→FAI −40% · fig. TKoutputs: layout package · IO map · utility loads · FAI checklistthen: operate · change · expand — same model
FIG. 01 — THE THREAD · high-level product schematicinputs: LOI · equipment list · site drawings
04INTERFACES + TRUST

Fluid with what you run today.

CAD, BIM, ERP, MES — they stay. XENOPS moves intent between them. Nothing here asks you to throw anything away.

FLUID WITH WHAT YOU RUN TODAY — NO RIP & REPLACE
SOLIDWORKS
AUTOCAD
REVIT
SAP
NETSUITE
IGNITION
OPC UA
PROCORE
SYSTEMDOMAINMETHODSTATUS
SOLIDWORKSOTpluginPILOT
AUTOCADOTfile syncPILOT
REVITAECmodel syncPILOT
PROCOREAECAPIPLANNED
SAPITAPIPILOT
NETSUITEITAPIPLANNED
IGNITIONOTOPC UAPILOT
OPC UAOTnativePILOT
● in pilot today · ○ on the roadmap
OUTPUTFORMATTO
Layout packageDWG / PDFAEC · GC
IO mapCSV / JSONIT · controls
Utility loadsXLSXAEC · MEP
FAI checklistPDFquality
Change logJSON feedall domains
everything downstream falls out of the one model
SOC 2 TYPE IIAudit in progress. Report to design partners under NDA. [TK]
SSO / SAMLYour IdP, your rules. Domain-scoped onboarding, same tool.
DATA BOUNDARIESTLS 1.3 in transit, AES-256 at rest. OT data stays in your tenancy.
THE WAITLIST

The next factory shouldn't take quarters.

Pilot partners get the model first. The waitlist is the queue.

no spam · one Line Pulse briefing a month · unsubscribe anytime
Subscribe to Line Pulse — the XENOPS monthly newsletterOne briefing a month. Conveyed directly to your inbox.