BaSyx / Documentation / Components / DataBridge / Features / AAS Endpoint

AAS

The AAS Server can be integrated with DataBridge. The AAS component can be configured as a Data Sink in the DataBridge.

Configuration

To configure AAS Server in DataBridge you need to provide the unique id, endpoint of the Submodel, idShort path and the api type. The AAS endpoint supports both the Dot AAS V1 (BaSyx) as well as Dot AAS V3 (DotAAS-V3) specifications api.

Sample Configuration Dot AAS V1

[
	{
		"uniqueId": "ConnectedSubmodel/ConnectedPropertyA",
		"submodelEndpoint": "http://localhost:4001/shells/TestUpdatedDeviceAAS/aas/submodels/ConnectedSubmodel/submodel",
		"idShortPath": "ConnectedPropertyA",
                "api": "BaSyx"
	}
]

Sample Configuration Dot AAS V3

[
	{
		"uniqueId": "ConnectedSubmodel/ConnectedPropertyA",
		"submodelEndpoint": "http://localhost:4001/shells/TestUpdatedDeviceAAS/aas/submodels/ConnectedSubmodel/submodel",
		"idShortPath": "ConnectedPropertyA",
                "api": "DotAAS-V3"
	}
]

Note: The default api type is Dot AAS V1 (BaSyx).

Similarly, you can configure multiple AAS sinks inside the configuration file.

Naming Convention

The name of the AAS configuration file should be aasserver.json.

Working Example

The integration example with MQTT as a data source, JSONata as a transformer, and AAS as a data sink is on GitHub DataBridge Example.