AWS IoT TwinMaker for facility management guide

Create TwinMaker workspace: aws iottwinmaker create-workspace --workspace-id my-facility --s3-location s3://my-bucket/twinmaker --role arn:aws:iam::account:role/twinmaker-role. Connect data sources: IoT SiteWise connector (pulls measurements from SiteWise assets), Timestream connector (time-series data), or custom Lambda connector (any API). The custom Lambda connector is the most flexible — write a Python Lambda that queries your historian, CMMS, or BMS and returns entity property values in TwinMaker's format. Our DevOps team handles TwinMaker Terraform deployments.

Define entity types (ComponentType in TwinMaker API) — EquipmentAsset, BuildingFloor, ProductionLine. Each ComponentType declares its properties (temperature, status, efficiency) and their data source bindings. Create entity instances for each real asset: aws iottwinmaker create-entity --workspace-id my-facility --entity-name "Pump-A1" --components "{...}". Create relationships: aws iottwinmaker create-entity --parent-entity-id "Building-1". Import from CSV via the bulk operations API for large facilities (1000+ assets). Validate with TwinMaker Console → Knowledge Graph view.

In TwinMaker Console → Scene Composer: upload your facility 3D model (glTF format) or connect to your CAD export. Place entity tags on the 3D model — each tag binds a 3D location to a TwinMaker entity. Now clicking a pump in the 3D view shows its live data. Create Grafana dashboards using the Amazon Managed Grafana TwinMaker plugin — query entity properties and time-series data directly in Grafana panels. This combination (3D view + operational dashboards) is the standard TwinMaker operations centre interface for facility management teams.