Before you can twin a plant, you have to know what's in it.

AssetTwin™ is the foundation layer of the Wistwin® digital twin platform. It digitizes every machine, instrument, valve, motor, panel, sensor, and spare in your plant into a hierarchical, ISO 14224-aligned asset register. Every other Wistwin module · SmarTwin, VolTwin, PredicTwin, TrusTwin and so on · reads from AssetTwin. Indian manufacturers use AssetTwin to replace fragmented asset registers (SAP + spreadsheets + tribal knowledge) with one live source of truth synced sub-3-seconds to the ERP.

Every twin needs to know what it's twinning. SmarTwin can't show OEE on a machine that isn't in the asset register. PredicTwin can't predict failure on an asset it doesn't know about. TrusTwin can't map regulator controls to undefined plant elements. AssetTwin is the substrate · the layer of identity, hierarchy, and ownership that every other module needs to function. Trying to deploy any other Wistwin module without AssetTwin would be like deploying SAP without a chart of accounts.

SAP's asset module is a financial accounting view · built around capitalization, depreciation, and the general ledger. AssetTwin is a plant-floor view · built around hierarchy, sensors, work orders, spares, and lifecycle. The two views are complementary, not competing. AssetTwin syncs bi-directionally with SAP so the financial view and the operational view stay aligned. Most customers run them side by side.

No. ISO 14224 is the default because it's the industry standard for reliability data exchange and works well across sectors. If your plant uses a different taxonomy (KKS for power plants, RDS-PP for energy, custom in-house), AssetTwin can be configured to that hierarchy. Most Indian customers stay with ISO 14224 because it makes auditor and OEM data exchange easier.

Pilot (single plant): 6–10 weeks. Includes ERP integration, template selection, asset import, hierarchy structuring, QR code generation, mobile app rollout to maintenance team. Multi-plant: 4–6 months for hub-and-spoke architecture across 3–5 plants with group-level governance. Most customers see their plant fully digitized within 60 days of kickoff.

AssetTwin reads from OEM systems where available · Siemens TIA Portal, Schneider EcoStruxure, ABB Ability · and stitches that data into the unified register. We don't try to replace OEM-supplied asset data; we federate it into one queryable view alongside ERP and plant-floor data. This is what Indian Plant Heads actually need: one place to look, regardless of where the underlying data lives.

Yes. AssetTwin runs on AWS Mumbai (ap-south-1) by default. On-premises deployment is available for customers with strict data-residency or air-gap requirements. The platform is DPDP Act-compliant. ISO 27001 certification is in progress (Q3 2026 target).

Pricing is not published. AssetTwin is the foundation module of the Wistwin platform. Pricing is sized to your plant footprint · asset count, sector, and integration scope. Most Indian customers see rapid payback on spares overhead reduction and audit-readiness alone · before any other Wistwin module is added. Talk to our team for a tailored quote.

Hub-and-spoke architecture. Each plant runs its own local AssetTwin reading from local ERP/MES/PLC sources. A central corporate AssetTwin pulls master taxonomy across all plants. Group CFOs and Quality Heads see one register across the entire manufacturing footprint, while plant-level engineers work in their local view. Asset transfers between plants are tracked end-to-end.

Yes · that's the default. Our import flow accepts SAP exports, Oracle tables, Tally CSVs, raw Excel sheets, and even hand-keyed paper logs (we'll OCR them). The first thing our deployment team does is import your existing register against a sector-specific template, then guide your team through gap-filling on the 8–15% of assets that typically aren't in any system yet.