⭐ 🚀Search for Assets Using External Subject ID Wildcard with digitalTwinType

[mkanal]

Overview

The objective of this feature is to enhance the asset search functionality within dDTR by enabling the use of digitalTwinType as a filtering criterion. This implementation aims to boost search efficiency by leveraging the digitalTwinType attribute, avoiding the need for twins to be loaded for type identification. The outcome will streamline asset identification and improve system performance.

Explain the topic in 2 sentences

The feature allows asset searches to utilize the digitalTwinType attribute , optimizing digital twin retrieval based on type-level filtering. This approach minimizes resource consumption, enhancing response times for asset search queries.

What's the benefit?

This improvement increases search efficiency by reducing computational load, allowing more targeted queries based on the asset’s digitalTwinType. As a result, system performance and scalability are enhanced, particularly for large datasets.

What are the Risks/Dependencies ?

• There may be a risk of incomplete integration if digitalTwinType is not accurately configured in data provisioning, particularly in the supplier ecosystem.
• Collaboration with industry partners is necessary to ensure correct configuration and usage of digitalTwinType.

Detailed explanation

This feature intends to improve the asset search function within Trace-X by adding support for the digitalTwinType attribute. Currently, digital twins must be loaded to detect their type, resulting in performance inefficiencies. With the new approach, asset searches can apply the digitalTwinType filter directly, leading to faster and more precise retrievals.

Current implementation

Asset searches in Trace-X currently do not support direct filtering by digitalTwinType, requiring the system to load and identify twins before processing.

Proposed improvements

Enable direct filtering by digitalTwinType in asset searches.
Ensure compatibility with industry-specific identifiers (e.g., PartInstance for serialized parts and PartType for catalog parts).

Feature Team

Contributor

• Cofinity-X @rogocof
• Cofinity-X @mkanal

Committer

• @ds-jhartmann
• @ds-mwesener
• @ds-lcapellino

User Stories

As a PO
I want to optimize dtr search using digitalTwinType
so that twins must not be loaded to detect digitalTwinType what boost performance

Acceptance Criteria

• IRS EDC CLient allow the use of digitalTwinType for asset searches.
• DTR registry lookup uses digitalTwinType to detect correct BOM Lifecycle
• Assets for INT have to be provided with this digitalTwinType
• The search functionality should support both TypeLevel and InstanceLevel for querying digitalTwinType.
• Comprehensive and reasonable error handling and message in case digitalTwinType is not set correctly.
• ARC42 documentation and Admin manual is updated accordingly
• Integration tests with performance measurements and metrics.
• Execute and document a benchmark test after

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Backlog -> Since for Backlog some requirements are missing ... please update them
• Please add missing sections from the feature template, or fill them out
• Please add contributor and committer
• Please add assignee (overall responsible person who drives the feature)