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.

Sign up for GitHub

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

Jump to bottom

[User Story] As a admin I want to deploy hierarchical objects with subcomponents so that manage multi-objects in the iff-agent #555

Closed
wagmarcel opened this issue May 24, 2024 · 0 comments
Closed

[User Story] As a admin I want to deploy hierarchical objects with subcomponents so that manage multi-objects in the iff-agent #555

wagmarcel opened this issue May 24, 2024 · 0 comments
Assignees
@wagmarcel
Labels
user story

Comments

@wagmarcel
Copy link
Member

wagmarcel commented May 24, 2024 •
edited
Loading

Details

Today IFF-Agent can only manage one single object. What needs to be added is the capability to onboard hierarchical objects and allow IFF-Agent to update them.
(1) Multi object token
(2) Extention of Agent API to allow to forward data to several objects
(3) Onboarding process which can derive the hierarchy of objects
(4) Document tcp/udp schema for subdeviceid

Acceptance Criteria

  1. [If I do A.]
  2. [B should happen.]

Resources:

  • Mockups: [Here goes a URL to or the name of the mockup(s) in inVision];
  • Testing URL: [Here goes a URL to the testing branch or IP];
  • Staging URL: [Here goes a URL to the feature on staging];

Notes

[Some complementary notes if necessary:]

  • Here goes a quote from an email

  • Here goes whatever useful information can exist…
@wagmarcel wagmarcel self-assigned this May 24, 2024
@wagmarcel wagmarcel mentioned this issue Mar 8, 2024
Closed
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jul 1, 2024
@wagmarcel
Add subcomponent/subdevice processing
db89cf3 
Up to now the IFF-agent can only manage one single device with a certain id. This limits cases where the device
is consisting of several subsystems. For such cases, all the subsystem data was mapped to the main device with
the respective id. With these changes, a device can now consist of several subsystems and these IDs can be added
to the device token. This PR contains everything needed to support subdevice/subcomponent processing:

* IFF-Agent accepts deviceIds in the TCP/UDP messages
* IFF-Agent utils offer additional options to add subcomponent IDs and send data for subcompoentns
* Keycloak allows now the field "subdevice_ids" in the token to add subdevice IDs
* The MQTT-Bridge permits subdevice IDs to stream data

Related Epic: IndustryFusion#514
Related User-stories: IndustryFusion#555

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Jul 2, 2024
@wagmarcel @abhijith-hr
Add subcomponent/subdevice processing
71f4e30 
Up to now the IFF-agent can only manage one single device with a certain id. This limits cases where the device
is consisting of several subsystems. For such cases, all the subsystem data was mapped to the main device with
the respective id. With these changes, a device can now consist of several subsystems and these IDs can be added
to the device token. This PR contains everything needed to support subdevice/subcomponent processing:

* IFF-Agent accepts deviceIds in the TCP/UDP messages
* IFF-Agent utils offer additional options to add subcomponent IDs and send data for subcompoentns
* Keycloak allows now the field "subdevice_ids" in the token to add subdevice IDs
* The MQTT-Bridge permits subdevice IDs to stream data

Related Epic: #514
Related User-stories: #555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jul 7, 2024
@wagmarcel
Add subComponentRelationship type to entity file
0ce3029 
In the datamodel the entity.ttl file describes the "static" knowledge
about attributes. For instance the domain and range of attributes. In this PR, the
Relationships will be typed as subcomponents and peer relationships.

Related Epics: IndustryFusion#514
Related User-stories: IndustryFusion#555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jul 11, 2024
@wagmarcel
Add subComponentRelationship type to entity file
13fa336 
In the datamodel the entity.ttl file describes the "static" knowledge
about attributes. For instance the domain and range of attributes. In this PR, the
Relationships will be typed as subcomponents and peer relationships.

Related Epics: IndustryFusion#514
Related User-stories: IndustryFusion#555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jul 11, 2024
@wagmarcel
Add subComponentRelationship type to entity file
78c9961 
In the datamodel the entity.ttl file describes the "static" knowledge
about attributes. For instance the domain and range of attributes. In this PR, the
Relationships will be typed as subcomponents and peer relationships.

Related Epics: IndustryFusion#514
Related User-stories: IndustryFusion#555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit that referenced this issue Jul 11, 2024
@wagmarcel
Add subComponentRelationship type to entity file
708cf62 
In the datamodel the entity.ttl file describes the "static" knowledge
about attributes. For instance the domain and range of attributes. In this PR, the
Relationships will be typed as subcomponents and peer relationships.

Related Epics: #514
Related User-stories: #555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jul 19, 2024
@wagmarcel
Add subcomponent retrival for hierachical system onboarding
024cc2e 
This PR provides a script to retrieve all subcomponent IDs from an entity id. The
script assumes to have the entity knowledge and access to a NGSI-LD Context
Broker.
In addition it provides:

* Changed default context in datamodel examples
* Plain JSON-properties to integrate legacy JSON objects
* Validation and tests for json properties
* Add NOTICE for licence compliance and Software BOM
* Bats e2e test for subcompoenent tests
* Updated  README with getsubcomponent example
* Extension of validate.js to validate files from stdin

Related Epic: IndustryFusion#514
Related User Story: IndustryFusion#555

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Jul 19, 2024
@wagmarcel @abhijith-hr
Add subcomponent retrival for hierachical system onboarding
e258472 
This PR provides a script to retrieve all subcomponent IDs from an entity id. The
script assumes to have the entity knowledge and access to a NGSI-LD Context
Broker.
In addition it provides:

* Changed default context in datamodel examples
* Plain JSON-properties to integrate legacy JSON objects
* Validation and tests for json properties
* Add NOTICE for licence compliance and Software BOM
* Bats e2e test for subcompoenent tests
* Updated  README with getsubcomponent example
* Extension of validate.js to validate files from stdin

Related Epic: #514
Related User Story: #555

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Aug 19, 2024
@wagmarcel
Transform nodeset2 files to OWL
dbd6684 
This is the first step of OPCUA to Semantic Web transformation.
The tool added can be used to parse the existing opcua companion specifications
and provide a RDF/OWL based representation. This can then later be used of tools
to validate and translate OPCUA machines to a common data language.

Related Epic IndustryFusion#514
Related User Stories IndustryFusion#555, IndustryFusion#571

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Aug 20, 2024
@wagmarcel @abhijith-hr
Transform nodeset2 files to OWL
edc8cb8 
This is the first step of OPCUA to Semantic Web transformation.
The tool added can be used to parse the existing opcua companion specifications
and provide a RDF/OWL based representation. This can then later be used of tools
to validate and translate OPCUA machines to a common data language.

Related Epic #514
Related User Stories #555, #571

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Sep 7, 2024
@wagmarcel
Add tools to transform opcua data to NGSI-LD, SHACl, OWL and Data bin…
7ab4f9e 
…dings

This PR provides a transfomrational tool which takes nodeset2 owl files and creates NGSI-LD, SHACL and OWL based machine
descriptions. Also, bindings are created to map opcua data to the external data model. The PR also contains:

* Updated Dataservice to work with bindings created by this extractType tool.
* Updated Datamodel to pull NGSI-LD subcomponents based on the OPCUA metadata
* Additional E2e tests for extractType tool

related EPIC: IndustryFusion#514
related User Story: IndustryFusion#555, IndustryFusion#571

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Sep 7, 2024
@wagmarcel
Add tools to transform opcua data to NGSI-LD, SHACl, OWL and Data bin…
26caa39 
…dings

This PR provides a transfomrational tool which takes nodeset2 owl files and creates NGSI-LD, SHACL and OWL based machine
descriptions. Also, bindings are created to map opcua data to the external data model. The PR also contains:

* Updated Dataservice to work with bindings created by this extractType tool.
* Updated Datamodel to pull NGSI-LD subcomponents based on the OPCUA metadata
* Additional E2e tests for extractType tool

related EPIC: IndustryFusion#514
related User Story: IndustryFusion#555, IndustryFusion#571

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Sep 7, 2024
@wagmarcel @abhijith-hr
Add tools to transform opcua data to NGSI-LD, SHACl, OWL and Data bin…
387427a 
…dings

This PR provides a transfomrational tool which takes nodeset2 owl files and creates NGSI-LD, SHACL and OWL based machine
descriptions. Also, bindings are created to map opcua data to the external data model. The PR also contains:

* Updated Dataservice to work with bindings created by this extractType tool.
* Updated Datamodel to pull NGSI-LD subcomponents based on the OPCUA metadata
* Additional E2e tests for extractType tool

related EPIC: #514
related User Story: #555, #571

Signed-off-by: marcel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wagmarcel wagmarcel

Labels
user story
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wagmarcel