Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reference between different asset administration shells #35

Closed
githublena opened this issue Jun 22, 2020 · 3 comments
Closed

reference between different asset administration shells #35

githublena opened this issue Jun 22, 2020 · 3 comments

Comments

@githublena
Copy link

is there a possibility within existing AASX Explorer to reference between different asset Administration shells in order to implement for example nestability of Shells or to make it possible one asset is able to have different asset Administration Shells across its lifecycle?

@BirgitBoss
Copy link
Collaborator

It is possible to have more than one AAS for an asset: the asset has a unique id and is referenced by the AssetAdministrationShell-object.

Nestability of shells is not supported (by design decision), but what is supported are so-called composite I4.0 components, i.e. composite assets. These are modelled by creating a submodel and then creating Entity submodel elements. Via the RelationshipElement also relations between these entity objects can be modelled, e.g. partOf or connectedTo. An Entity may have its own AAS (self-managed) but this is not required.

Examples can be found in https://github.com/admin-shell/aasx-package-explorer/blob/master/builds/development/DataModelV2/build200518/sample-aasx.zip: see sample-docu-BOM.aasx or MTPsample.aasx

@BirgitBoss
Copy link
Collaborator

I think this issue can be closed.

@BirgitBoss
Copy link
Collaborator

I close the issue, for any new issues please go to admin-shell-io/aasx-package-explorer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants