Create Digital Twin
For each saved provider connector, list the asset ids to pull from that provider. Add multiple rows to combine assets from different connectors into one twin. Then pull, review the merged passport fields, and publish to dataspace and the Federity provider (BaSyx + EDC).
- Connectors & assets
- Pull data
- Create & publish
Choose a provider connector to load assets your consumer can access.
Published digital twins
Twins you published from this dashboard. Use Publish passport to issue a reference-only passport (QR opens a viewer that loads the twin live from dataspace).
Passports
Each passport stores only a public id and remote twin id locally. Opening the passport URL fetches the digital twin from the dataspace API on the fly.
Provider Connectors
Each row is the supplier side of the link: name, their BPN, and their public data plane (DSP URL or connector origin). The server normalizes the DSP URL and derives a management URL for optional checks. Pulls use your consumer EDC from Settings — not the provider's management key. An optional default provider key in env is only for probing their management API, not for Federity consumption.
No provider connectors yet.
Settings
Register your organization as the dataspace consumer: these values are used for catalog, negotiation, transfer, and twin publish on your EDC (saved per user). Provider connectors still describe each supplier.
Fill every field below for a complete profile (required for pulls and publish from the dashboard).