Multiple domain modeling (e.g. PackML, IAS95, AAS, OpenPLC)|OPC UA Companion Standards|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Multiple domain modeling (e.g. PackML, IAS95, AAS, OpenPLC)
Avatar
Rudolf Pribis
Member
Members
Forum Posts: 4
Member Since:
03/04/2019
sp_UserOfflineSmall Offline
1
02/10/2023 - 09:10
sp_Permalink sp_Print

I believe I do not duplicate a question.

Is there an explanation or guide how to in a proper way model an "asset" in several information models?

As I understood, different use cases requires different viewpoint on data for instance

- PackML for some KPI calculations

- ISA95 for connection with Production Planning

- OpenPLC for addressing operational values

- AAS for creation I4.0 Component, or Digital Twin.

 

How the interconnection between all these views should be made? Is there somewhere a best practices which describes references between modeling in several information models? Confused

Avatar
Rudolf Pribis
Member
Members
Forum Posts: 4
Member Since:
03/04/2019
sp_UserOfflineSmall Offline
2
02/11/2023 - 05:01
sp_Permalink sp_Print

Ok, I found something in OPC 10000-100: Devices Annex C (informative). I was thinking about something similar, like to use different views.

"In this case, the device is represented by an Object “MyDevice” where the vendor of the OPC UA
Application can provide its specific knowledge of the device. In addition, the Object has two
components called FDTView and AutoIdView in the figure, containing the information as defined in
the corresponding companion specifications."

I am looking forward also for other suggestions...

Avatar
Wolfgang Mahnke
New Member
Members
Forum Posts: 1
Member Since:
02/21/2018
sp_UserOfflineSmall Offline
3
02/13/2023 - 01:08
sp_Permalink sp_Print

rudolf.pribis@stuba.sk said
Ok, I found something in OPC 10000-100: Devices Annex C (informative). I was thinking about something similar, like to use different views.

"In this case, the device is represented by an Object “MyDevice” where the vendor of the OPC UA

Application can provide its specific knowledge of the device. In addition, the Object has two

components called FDTView and AutoIdView in the figure, containing the information as defined in

the corresponding companion specifications."

I am looking forward also for other suggestions...

  

Hi,

you already found a good place describing a solution for your issue, that is composition.

If composition is not an adequate solution for your case, you can also use a specific ReferenceType defined in Part 23 of the base specification, called "RepresentsSameEntityAs" or one of its subtypes. This is for example used in OPC 30142: OPC UA for PROFINET Remote IO or OPC 10000-81 OPC UA FX.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 13
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1345
Posts: 4562