Flagship product
PHL TwinCore
A data-connected model of every critical asset: what it is, what it measures, what it is connected to and what has happened to it. Built to be useful on day one from a tag list and an export, with no 3D model required.
- Category
- Industrial digital twin & asset intelligence
- Status
- In development · first release designed Available in MVP
- For
- Reliability, maintenance and industrial-engineering teams
- Starts with
- An asset list and a CSV export
- Boundary
- Read-only. Never writes to controls
01Interface preview
The twin, the signals and the history on one screen.
Real components running on the illustrative demo cell. Select an asset in the hierarchy or open the Digital twin tab.
PMP-001 Coolant pump
Centrifugal pump · Criticality A · Live (demo) · 14:20
| Signal | Component | Source binding | Unit |
|---|---|---|---|
| Vibration velocity RMS | Drive-end bearing | opcua: ns=3;s=Cell3.P301.VibDE | mm/s |
| Bearing temperature | Drive-end bearing | opcua: ns=3;s=Cell3.P301.BrgT | °C |
| Discharge pressure | — | opcua: ns=3;s=Cell3.P301.Pd | bar |
| Coolant flow | — | opcua: ns=3;s=Cell3.P301.Flow | L/min |
| Motor current | — | opcua: ns=3;s=Cell3.P301.Current | A |
| Electrical power | — | opcua: ns=3;s=Cell3.P301.kW | kW |
02Workflow
From registration to a published twin.
Register assets
Create the hierarchy and import the asset list. Criticality is required, because it drives review order later.
Bring in readings
Upload a historian export or connect a gateway. A validation preview shows unit and timestamp problems before anything is stored.
Map signals
Bind each source tag to an asset, a component and a canonical unit. Unmapped tags are listed, not dropped.
Configure and publish
Place assets on the plan view, add relationships and rules, then publish an immutable twin version.
Monitor and report
Watch condition and freshness, investigate alerts, and generate reports that name the twin version and data coverage.
03Technical capabilities
What TwinCore does, and the status of each part.
| Capability | What it does | Status |
|---|---|---|
| Asset registration | Tag, type, cell, criticality, ratings, datasheets. Manual entry, CSV import or the sample pack. | Available in MVP |
| Facility hierarchy | Facility › Area › Cell › Asset › Component, with aggregate state on every node. | Available in MVP |
| Telemetry mapping | Bind a source tag (CSV column, MQTT topic, OPC UA node) to an asset, component and canonical unit. | Available in MVP |
| Digital-twin configuration | Signal map, typed relationships and plan-view layout, published as immutable versions. | Available in MVP |
| Equipment monitoring | Current values, thresholds, freshness and asset state. | Available in MVP |
| Asset relationships | drives · feeds · cools · supplies · monitors, drawn on the plan view. | Available in MVP |
| Historical state | Readings and twin version as of any time in retention. | Available in MVP |
| Engineering reports | Asset condition, event history, telemetry analysis and twin configuration, each with data coverage and limitations. | Available in MVP |
| Live data through a gateway | MQTT and OPC UA, read-only, via a gateway you install and approve. | Requires adapter |
| 3D twin view | glTF models bound to asset IDs; the plan view remains the default. | Planned |
| Public read API | Programmatic access to assets, signals and twin state. | Planned |
04Data requirements
What you need to provide.
Twin fidelity depends on the inputs. TwinCore shows what is missing rather than filling gaps with assumptions.
Required
- Asset list with tags, types and the cell each asset belongs to
- Criticality (A, B or C) per asset
- Signal names, units and expected reporting interval
- At least one data path: a CSV/Parquet export or a gateway
Recommended
- OEM limits or your own thresholds, with their source
- Ratings (power, speed, flow) and datasheets
- Maintenance history as a CSV export from your CMMS
- A rough cell layout for the plan view
Not required
- 3D or CAD models
- Changes to PLC programs
- Inbound firewall rules to your OT network
- Labelled failure history (needed only for future predictive models)
Twin fidelity levels
- Structural — hierarchy and signal map
- Visual — plus plan or 3D layout
- Parametric — plus engineering parameters for a scenario model
- Validated — only when an engineer records validation evidence
05Integrations
How data reaches TwinCore.
The first release imports CSV and Parquet exports and ships with sample data. Live readings arrive through an AWS IoT Greengrass gateway running on a host you approve: an OPC UA read-only client or an MQTT bridge publishes over outbound TLS with a per-gateway certificate.
Protocols such as Modbus or PROFINET need a third-party converter that exposes OPC UA or MQTT. See every integration and its status →
// MQTT envelope (documented format, illustrative values)
{
"gateway_id": "gw-01",
"signal_key": "Cell3.P301.VibDE",
"ts": "2026-10-14T14:20:00Z",
"value": 4.9,
"unit": "mm/s",
"quality": "good",
"seq": 18842
}Output classes in TwinCore
- OBS A reading as received, with quality code and timestamp
- RULE A conclusion from a rule you configured
- STAT A deviation from the asset’s own baseline
- DATA A data-quality condition: stale, gap, unit or clock problem
See TwinCore on a working cell.
The demo runs the TwinCore interface on four fictional assets with sample data. No signup and no connection to equipment.
Illustrative demo · no signup · not connected to equipment