01 / At the machine
Collector
Reads the PLC. Holds a buffer if the link is slow. Always starts the connection — the historian never dials into the plant network.
TwinEdge Historian
Ask the record. Trust the answer.
AI-native industrial historian.
TwinEdge Historian is AI-native. It stores each reading with its equipment, time, and unit — on the floor, in your rooms, or in the cloud. You can ask the record in plain language. Agents cite it. A person still approves the next job.
- Ask in plain language. Find the outlet temperature of the second boiler without knowing the tag name.
- AI cites the log of record. The assistant answers from this historian’s own history, not a generic guess.
- People still decide. Agents draft. A person applies the rule, the dashboard, or the work.
AI-NATIVE HISTORIAN
TwinEdge OS keeps a copy at the site. If the WAN drops — or there is no WAN — the plant still has history.
02 / At the site
TwinEdge OS
The edge server next to the equipment. Protocols, local screens, alerts, and a local copy of history — including when the site is air-gapped.
03 / The memory
Historian
AI-native memory for the plant. Stores every reading with its equipment, time, and unit. Agents can ask it. A person still applies the change. Same product in the plant, your rooms, or the cloud.
START WITHTime-stamped equipment signals
TWINEDGE CONNECTSTwinEdge Historian keeps the operating record
MOVE FORWARD WITHHistory for analysis + decisions
THE WORKFLOW
From the PLC to a decision you can explain.
Read the equipment
Collectors sit with TwinEdge OS and read the PLC.
Keep a copy at the site
TwinEdge OS stores, screens, and alerts locally.
Remember, then decide
The historian keeps the long record.
Lower operating cost
See extra energy and wear on the real record, then fix the machine that is actually wasting money.
Smarter capital decisions
Repair versus replace is based on this machine’s history, not a spreadsheet guess.
AI you can audit
The assistant runs in the air gap if you need it.
BUILT FOR THE OPERATION
What this AI-native historian covers.
Collectors that only dial out
Each collector reads signals and opens the connection itself.
TwinEdge OS at the edge
Protocols, local dashboards, alerts, and a site historian run beside the machine , including with no internet.
History with a name on it
Every reading keeps its equipment, timestamp, and unit, so a trend is something you can explain.
Air-gapped, on-prem, or cloud
Same product in the plant, in your rooms, or in the cloud.
Time-window queries
Ask for a period, an asset, or a comparison.
Useful after the shift
Investigations, AI, maintenance, and capital planning all start from the same operating memory.
Explore more capabilities
AI-native assistant. Ask in plain language. Draft a rule, a dashboard, or a calculation from a sentence. Nothing is applied until a person says so.
Analytics that cite the record. Trends, investigations, and agent answers keep the equipment, time, unit, and evidence. The AI does not invent a number.
CONNECTED BY DESIGN
Fits the systems around it.
Keep source context available as the workflow moves between teams and applications.
One connected record.
TwinEdge Historian
- Collectors read PLCs and other sources, then dial out to the historian.
- TwinEdge OS is the edge server: local screens, local history, and optional approved sync.
- TwinEdge Historian stores the long record on-prem or in the cloud.
- TwinEdge DataOps, AI-native Agentic Analytics, AssetOps CMMS / EAM, and Capital Planning use that same history.
BEFORE YOU START
A few useful answers.
Is TwinEdge Historian AI-native?
Yes. TwinEdge Historian is an AI-native industrial historian. You can search in plain language, ask an assistant on the chart, and let agents draft a rule or investigation from the log of record. Models can run on site, including air-gapped. Agents propose. A person applies.
What does the collector do?
It reads the PLC or other source and sends batches to the historian. It always starts the connection. The historian never dials into the plant, which is why air-gapped and DMZ layouts use the same path.
How does TwinEdge OS fit with the historian?
TwinEdge OS is the edge server next to the equipment. It connects protocols, serves local screens, and can keep a local historian. TwinEdge Historian is the long memory — on that same server, in your rooms, or in the cloud.
Can this run with no internet?
Yes. Air-gapped is a supported layout. Collectors, TwinEdge OS, and a local historian stay on the plant network. Nothing needs a route out.
What if we want the cloud?
Keep TwinEdge OS and collectors at the site. They dial out to TwinEdge Historian in the cloud or in your rooms. The site still has a local copy, and each cloud tenant has its own database.
Can we keep an existing historian?
Yes. TwinEdge can read the historian you already run. You can also run TwinEdge Historian beside it, or move later. Migration is free if you choose to switch.
THE NEXT CONNECTION
Explore the product familyBuild the rest of your loop.
START WITH YOUR OPERATION
Put the next decision in motion.
Discuss your sources, assets, and the outcomes your team wants to improve.