AssetInformation: add uniqueFacilityIdentifier and unqiueOperatorIdentifier and LifeCycleState

[BirgitBoss]

Is your feature request related to a problem? Please describe.
For DPP as specified in JTC24 prEn 18223 there is the need to identify the

• operator
• and the facility
  In BatteryPass there is
• batterystatus for states like refurbished, new etc.

For batteries it sometimes is the assetKind in combination with the facilility it is produced at that is used for PCF calculation.

Describe the solution you'd like

Add the two attributes to AssetInformation with type "Reference" or type "Identifier". Type shall be compliant with the requirements for identifiers as defined in JTC24 prEn 18219

In the Nameplate and in the BatteryNameplate these two attributes are named like this:
UniqueFacilityIdentifier and
OperatorIdentifier and
LifeCycleState

The assumption here is: if these attributes are filled: change of these values would lead to the creation of a new AAS.

[Manu3756]

Hi Birgit,
Instead of changing the MetaModel, I would recommend going with a JTC24 prEN 18219 Submodel or enhancing the Digital Nameplate Submodel. The OperatorIdentifier can change over the lifetime of an asset (e.g., a battery), which would require changes at the AAS level if you place the OperatorId there instead of in a Submodel. Since a Submodel, by definition, represents a domain- or use-case-specific aspect of the digital twin, it’s perfectly fine to say that DPP is a domain/use case and that we need a dedicated Submodel for it.

Pros of using a Submodel approach:

We stay compatible with version 3.1.

Development can start immediately without waiting for a new MetaModel release.

Existing tooling does not need to change the MetaModel to adopt DPP use cases.

BR

[seicke]

I agree with @Manu3756: The OperatorIdentifier may change (multiple times) during the asset's lifetime. Furthermore, to my understanding an OperatorIdentifier isn't a real assetInformation.
IMHO a submodel fits better for maintaining the OperatorIdentifier.

---

Remark regarding UniqueFacilityIdentifier:

ESPR (EU) 2024/1781, chapter 1, article 2 (definitions):

(33) 'unique facility identifier' means a unique string of characters for the identification of locations or buildings involved
in a product's value chain or used by actors involved in a product's value chain;

Please note that plural is used in the regulation. Maybe it is not sufficient to add only one attribute to identify the facility 🤔
For me it seems that a "list of facility identifier" is expected.

Regardless of this, I appreciate the extension of the assetInformation by a FacilityIdentifier/"list of facility identifier".

[BirgitBoss]

2025-12-11 Workstream AAS Specs:
decision to not add these attributes. These should be added to SMT Nameplate.