OPCUA real-time data

[PetterBMarkussen]

Hi,

I have been using the AASX Package explorer to generate a serialized OPCUA nodeset2.xml file. I have some question regarding the serialization

It does not seam that the OPC UA companion specification for AAS utilizes the native OPC UA variable concept. How should real-time data in an OPC UA server be used in the context of AAS? I see that the serialization from AAS -> nodeset2.xml only uses OPC UA properties. Real time data on an OPC UA server should be implemented by using OPC UA native "variable" concept. Could someone please clearify why this concept has not been used in the serlization? For analogue measurment values, the variables concept is used in OPC UA. AnalogueItemType is the usuall variable type to use in OPC UA for exposing a analogue signal on the server. This variable also includes several standard properties s.a. EURange and EUInformation. I dont see any mention of utilizing these key standard OPC UA concepts in this searilization.

[GoetzGoerisch]

For realtime information the applicable OPC UA companion specification should be used.

[StenGruener]

Regarding use cases with OPC UA CS:
OPC UA Machinery CS provides a description how "Nameplate information" of an asset is findable inside an OPC UA Server (and which Properties are provided). In my view when I want to "onboard or register" an real device to a cloud (and an AAS) I want to look up, if the real asset fits to the digital twin (AAS)... so I typically compare the "AAS SM Nameplate data" with "OPC UA Machinery Identification data" I find in the OPC UA server.

@BFrKUKA In our domain, PA-DIM, we typically assume that ProductInstanceUri from part -100 in the OPC UA device is exactly the "AssetID" in the AAS-Domain and also what is printed on the device (identification link). I guess also that this is a common understanding wrt. your use-case.

[BFrKUKA]

@StenGruener the VDMA Machinery CS also bases for this on the IVendorNameplateType of part 100, which provides the ProductInstanceUri. In the same way PA-DIM does.
And currently I just have this question, "where in the AAS" is the correllated "ProductInstanceUri" defined?
I currently "try to model with AASX Explorer" and as understood I define on the Asset the "Identifiable id as an IRI" and the AAS points via the Asset Reference to the Asset. - Am I right?

[StenGruener]

@BFrKUKA correct. You can also resolve a known AssetID to multiple AAS using AAS registries. Maybe we can combine it with LDS-ME aswell? Maybe you can just give me a ping on firstname.lastname@de.abb.com?

[GEORGEANDREW5962]

Hi,
@PetterBMarkussen @GoetzGoerisch @StenGruener

I am a beginer from Indonesia.
I already collect real time data from some machine PLC'S in DXP Takebishi OPC-UA Server and want to transfer its to the next layer.

Could you give any references how to transfer the real time data to AAS?
For example if I want to move the "actual current value" on DXP Server to the Operational data Submodels, "actual current value" element in AAS?

It will be helpfull for me.

Thank you BR

[BFrKUKA]

Hi, at the IDTA currently we are working on a submodel template which might be usefull for your idea.
It is (currently) called asset interface description and currently has to parts:

1. to describe the communication technology of the "asset" (= the PLC with OPC UA Server) incl. connection information, but it should be able for other communication technologies as MQTT, ModbusTCP, ... as well)
2. to describe in detail the "real time data" (e.g. for OPC UA the NamespaceUri and the NodeId) and in which AAS-Submodel-Element it should be mapped.
   So this is just regarding how we want to standardize such AAS Submodels at the IDTA. But there we have just discussions because of overlaps to the SubmodelTemplate "OPC UA Server DataSheet", which would have all "connection information" for an OPC UA Server...

But for a practical approach I think the way Basys project did it (as I know with OPC UA and MQTT) maybe @StenGruener can help you.

Regards, Bernd