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

Instancing more than one AAS #913

Closed
AnVentura opened this issue Oct 3, 2024 · 2 comments
Closed

Instancing more than one AAS #913

AnVentura opened this issue Oct 3, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@AnVentura
Copy link

I am currently implementing a project using the FAAAST service and I am looking for assistance. My goal is to ensure that, upon starting the program, more than one Asset Administration Shell (AAS) is instantiated. I have AASs stored both locally and online, and I would like to configure the service so that all of these AASs are available in FAAAST upon startup, rather than just a single instance.

Is there a way to achieve this multiple instantiation of AASs?

Thank you in advance for your support.
Best regards,
André Ventura

@AnVentura AnVentura added the bug Something isn't working label Oct 3, 2024
@mjacoby
Copy link
Member

mjacoby commented Oct 7, 2024

FA³ST Service is started with an AAS Environment file which can contain any number of Asset Administration Shells, Submodels, and Concept Descriptions. However, currently only a single such file can be passed.
I assume that you have multiple files containing each a single AAS and the respective submodels. In this case, the only way to start all of them at once using FA³ST Service is to manually merge these AAS files to a single one before passing them to FA³ST Service.

However, the feature to start FA³ST Service with multiple AAS files as input is in our backlog but not with the highest priority. Also, it is also not trivial because e.g. one needs to implement such a merging algorithm that detects inconsistencies while merging and it is unclear how file-based persistence should work with multiple files in some cases.

As a consequence, it probably will require to rethink the whole process how FA³ST Service is loading models and how file-based persistence works.

This also seems to be the same feature request as in #172

@mjacoby mjacoby added enhancement New feature or request and removed bug Something isn't working labels Oct 16, 2024
@mjacoby
Copy link
Member

mjacoby commented Oct 16, 2024

Closed because duplicate of #172

@mjacoby mjacoby closed this as completed Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants