You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
At the SPS 2024, we have implemented the use case “Transfer Of Owner Ship”\“Cross Enterprise AAS Transfer”.
An AAS shell including the submodels is transferred from the manufacturer's AAS environment to the customer's AAS environment.
The customer has the option of enriching this AAS with new information and making it available to its customers. However, this means that the customer is obliged to change the AAS ID and submodel ID.
If the AAS ID and submodel ID are changed, the reference to the manufacturer's AAS is lost. This means that it is no longer possible to access the manufacturer's AAS or to access the delivery status.
Describe the solution you'd like
A property such as “CopyFrom”, “OriginalID” or similar would be required at shell and submodel level to enter the manufacturer's AAS ID and submodel ID here.
Describe alternatives you've considered
The attribute "derivedFrom" in the metamodel is used to explicitly state a relationship between assets that are being derived from one another.
Other relationships are not explicitly supported by the metamodel of the Asset Administration Shell, but they can be modelled via the "RelationshipElement" submodel element type.
The text was updated successfully, but these errors were encountered:
HeinrichChristian
changed the title
"CopyFrom" attribute to preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer
Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer
Dec 10, 2024
HeinrichChristian
changed the title
Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer
Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer with modification of Ids
Dec 10, 2024
Hello Sebastian,
I think using the administrative information as a parent element is a good idea. However, an additional field for “CopiedFrom” should actually be added here. The previous fields all already have a precisely specified meaning. TemplateId as you mentioned has the special meaning that it indicates which template led the creation of the submodel/AAS.
If a new field is introduced, the meaning could be specified precisely. Using the TemplateId would cause the information that is actually in this field to be lost.
Is your feature request related to a problem? Please describe.
At the SPS 2024, we have implemented the use case “Transfer Of Owner Ship”\“Cross Enterprise AAS Transfer”.
An AAS shell including the submodels is transferred from the manufacturer's AAS environment to the customer's AAS environment.
The customer has the option of enriching this AAS with new information and making it available to its customers. However, this means that the customer is obliged to change the AAS ID and submodel ID.
If the AAS ID and submodel ID are changed, the reference to the manufacturer's AAS is lost. This means that it is no longer possible to access the manufacturer's AAS or to access the delivery status.
Describe the solution you'd like
A property such as “CopyFrom”, “OriginalID” or similar would be required at shell and submodel level to enter the manufacturer's AAS ID and submodel ID here.
Describe alternatives you've considered
The attribute "derivedFrom" in the metamodel is used to explicitly state a relationship between assets that are being derived from one another.
Other relationships are not explicitly supported by the metamodel of the Asset Administration Shell, but they can be modelled via the "RelationshipElement" submodel element type.
The text was updated successfully, but these errors were encountered: