EN 15804+A2 chapter 7.3.3.2 RSL

RobertSpang commented 9 months ago

Implementation status:

[x] schema
[x] examples
[ ] reviewed & approved internally
[ ] documentation
[ ] validation rules

I raise this change request because...

-- [ ] the ILCD+EPD format lacks compliance with regualtions. -- [X] the ILCD+EPD format lacks conformaty with standards. -- [ ] the ILCD+EPD format needs to be improved regarding existing format or master data elements. -- [ ] there is another problem or use case I´m trying to address.

Problem description

EN 15804+A2 chapter 7 3 3 2_RSL

Solution description

New master datasets need to be created and possibly the format extended

Relevance or added value

High relevance

RobertSpang commented 7 months ago

We find that new fields are needed to cover RSL information, but most likely no master data. We believe only the first line could be translated 1 to 1 into a new field. All other elements should be free text.

okworx commented 6 months ago

General: The declaration of an RSL is mandatory, if all B-modules are declared. Because without all B-modules, the use conditions are not properly defined.

Name

Service Life (Reference Service Life (RSL) or Estimated Service Life (ESL)) mandatory if use stage is declared, only one needs to be selected

Enumeration

Declaration of the source; only 3 valid options:

European product standards or, if not available, a c-PCR, and shall take into account ISO 15686-1, -2, -7 and -8
Public source (e.g. study or country specific list)
Manufacturer declaration mandatory if declared, only one needs to be selected

Description (incl. reference to standard, section/subsection)

Declaration of the products service life acc. EN 15804+A2 chapter 7.3.3.2 RSL. The RSL shall be established in accordance with any specific rules given in European product standards or, if not available, a c-PCR, and shall take into account ISO 15686-1, -2, -7 and -8. Where European product standards or a c-PCR provide guidance on deriving the RSL, such guidance shall have priority. The sources have to be indicated.

Data type (free text, enumeration, number (integer/decimal), date, etc.)

integer number

Cardinality (optional or mandatory, single occurrence or multiple occurrences)

contextually mandatory, single occurrence

Unit; fixed or variable

years; fixed

1aun commented 6 months ago

Use for

EN 15804+A2 chapter 7.3.3.2 'Reference Service Life (RSL)'
ISO 22057 'Estimated Service Life (ESL)'

Suggested Name

Service life in years

Description of Context

Service life describes the lifespan of the product.

The value may be estimated by a manufacturer or calculated according to a standard, which then needs to be referenced.

Occurrence

Optional

Cardinality

1

Content / Data

A value representing the service life in years

Type: Integer
Occurrence: Mandatory
Cardinality: 1

A reference to the standard used

Type: Reference to source data set
Occurrence: Optional
Cardinality: 1

Means to distinguish ESL and RSL

No field needed: This can be done via existence and/or compliance of the reference to some standard. It's RSL if

a standard is referenced and
the standard is acceptable for RSL according to spec. (This, however, is not a format constraint?)

Constraints

Mandatory if use stage is declared (completely)
If declared, all B-modules should be declared

okworx commented 5 months ago

example markup:

<serviceLife>
   <years>50</years>
   <useConditions factor="A - inherent quality" degree="1"/>
   <useConditions factor="B - design level" degree="2"/>
   <useConditions factor="C - work execution" degree="1"/>
   <useConditions factor="D - indoor environment" degree="1"/>
   <useConditions factor="E - outdoor environment" degree="4"/>
   <useConditions factor="F - usage conditions" degree="3"/>
   <useConditions factor="G - maintenance level" degree="5"/>   
<referenceToStandard type="source data set" refObjectId="c0016b33-8cf7-415c-ac6e-deba0d21440d" version="00.01.000">
       <common:shortDescription xml:lang="en">EN15804+A2</common:shortDescription>
       <common:shortDescription xml:lang="de">EN15804+A2</common:shortDescription>
   </referenceToStandard>
   <referenceToUseConditionsDocumentation type="source data set" refObjectId="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" version="00.01.000">
       <common:shortDescription xml:lang="en">wood panel use conditions and service life</common:shortDescription>
       <common:shortDescription xml:lang="de">Einbaubedingungen und Lebensdauer von Holzplatten</common:shortDescription>
   </referenceToUseConditionsDocumentation>
   <comment xml:lang="en">The indicated service life requires installation and maintenance according to manufacturer instructions.</comment>
   <comment xml:lang="de">Die angegebene Lebensdauer setzt eine Installation und Wartung gemäß den Anweisungen des Herstellers voraus.</comment>
</serviceLife>

okworx commented 1 month ago

[x] add an optional link to other external documentation describing the detailed use conditions
[x] add details about what use conditions the RSL is based on (ISO 22057 pg. 32 table 11): Typ der Bezugsgröße — funktionale Einheit — deklarierte Einheit Faktoren und Faktorkategorien nach ISO 15686-8 — A – inhärente Qualitätsebene — B – Entwurfsebene — C – Ebene der Bauausführung — D – Umgebung im Inneren — E – Umgebung im Freien — F – Nutzungsbedingungen — G – Ebene der Instandhaltung Grad der Nutzungsbedingungen nach ISO 15686-8 — 0 — 1 — 2 — 3 — 4 — 5 — nicht anwendbar

1aun commented 1 month ago

Our understanding of this is insufficient for implementation.

We've been deep diving into the standards and from what we understand, the dataset needs to declare an RSL and explain what assumptions have lead to the RSL value.

From the data format view point this suggests using text field for each of the factors. E.g.

<useCondition factor="E - outdoor environment">Lots of rain, but no wind.</useCondition>

Now,

Does this make sense to you domain experts? Or is it completely off?
This will most likely be in the referenced documentation, too (referenceToUseConditionsDocumentation). Does it need to be machine readable? As far as we can see is no standard to the text value, like e.g. a numerical value.
What does the degree of the use conditions mean? Shouldn't the data set explain a concept of 1 and then the expert working with the data set can derive deviation factors to rescale/adjust the RSL?

RobertSpang commented 1 month ago

My opinion is, that we implement that as textfield as proposed by you for now. Guess the whole topic will be subject to change and regulations/delegated acts/standrads in the future. Only then machine readable implementation would be possible.

okworx commented 1 month ago

My opinion is, that we implement that as textfield as proposed by you for now. Guess the whole topic will be subject to change and regulations/delegated acts/standrads in the future. Only then machine readable implementation would be possible.

Any reflections on the role of the "degree" value (0-5, n/a) here (question #3 above)?

@EmilieBrisson @szwerenz ?

RobertSpang commented 3 weeks ago

Think this one is rather simple: as long as we have no legal framewortk around this, we cannot make it machine readable. So: we need one (1) new field, containing the RSL in years, and a free text field describing the boundary conditions. That´s it.

EmilieBrisson commented 3 weeks ago

But if there is a RSL which all this text describes, why not add a field, where the RSL number can be? However, I do agree with the text setup and as no specefic law or rules are stated yet it is difficult to implement.

okworx commented 5 days ago

Summary and consensus from the discussion during this morning's meeting: We want to represent a table with factor category / object-specific grade / reference grade / factor / comment

rename "years" to "RSL"
add separate "ESL" value
useConditions allows additional optional multilang comment
rename @factor -> @factorCategory
rename @degree -> @referenceGrade
add attribute @objectSpecificGrade
make sure @degree allows N/A value (could be null -> absent attribute)
add reference to ISO 15686-8 in the schema doc

<serviceLife>
   <RSL>50</RSL>
   <ESL>40</ESL>
   <useConditions factorCategory="A - inherent quality" objectSpecificGrade="3" referenceGrade="1" factor="0.8">
        <comment xml:lang="en">comment here</comment>
        <comment xml:lang="de">Kommentar hier!</comment>
   </useConditions>
   <useConditions factorCategory="B - design level" objectSpecificGrade="3" referenceGrade="2" factor="0.9"/>
   <useConditions factorCategory="C - work execution" objectSpecificGrade="3" referenceGrade="1" factor="0.8"/>
   <useConditions factorCategory="D - indoor environment" objectSpecificGrade="3" referenceGrade="1" factor="0.8"/>
   <useConditions factorCategory="E - outdoor environment" objectSpecificGrade="3" referenceGrade="4" factor="1.1"/>
   <useConditions factorCategory="F - usage conditions" objectSpecificGrade="3" referenceGrade="3" factor="1.0"/>
   <useConditions factorCategory="G - maintenance level" objectSpecificGrade="3" referenceGrade="5" factor="1.2"/>   
<referenceToStandard type="source data set" refObjectId="c0016b33-8cf7-415c-ac6e-deba0d21440d" version="00.01.000">
       <common:shortDescription xml:lang="en">EN15804+A2</common:shortDescription>
       <common:shortDescription xml:lang="de">EN15804+A2</common:shortDescription>
   </referenceToStandard>
   <referenceToUseConditionsDocumentation type="source data set" refObjectId="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" version="00.01.000">
       <common:shortDescription xml:lang="en">wood panel use conditions and service life</common:shortDescription>
       <common:shortDescription xml:lang="de">Einbaubedingungen und Lebensdauer von Holzplatten</common:shortDescription>
   </referenceToUseConditionsDocumentation>
   <comment xml:lang="en">The indicated service life requires installation and maintenance according to manufacturer instructions.</comment>
   <comment xml:lang="de">Die angegebene Lebensdauer setzt eine Installation und Wartung gemäß den Anweisungen des Herstellers voraus.</comment>
</serviceLife>

1aun commented 5 days ago

Additionally, from my understanding: Both RSL and ESL need to declare use conditions.

So let`s give both values all the means to declare use conditions, standards etc.

<referenceServiceLife epd24:years=100>
    <useConditions factorCategory="A - inherent quality" objectSpecificGrade="3" referenceGrade="1" factor="0.8">
            <comment xml:lang="en">comment here</comment>
            <comment xml:lang="de">Kommentar hier!</comment>
    </useConditions>
    <useConditions factorCategory="B - design level" objectSpecificGrade="3" referenceGrade="2" factor="0.9"/>
    <useConditions factorCategory="C - work execution" objectSpecificGrade="3" referenceGrade="1" factor="0.8"/>
    <useConditions factorCategory="D - indoor environment" objectSpecificGrade="3" referenceGrade="1" factor="0.8"/>
    <useConditions factorCategory="E - outdoor environment" objectSpecificGrade="3" referenceGrade="4" factor="1.1"/>
    <useConditions factorCategory="F - usage conditions" objectSpecificGrade="3" referenceGrade="3" factor="1.0"/>
    <useConditions factorCategory="G - maintenance level" objectSpecificGrade="3" referenceGrade="5" factor="1.2"/>   
    <referenceToStandard type="source data set" refObjectId="c0016b33-8cf7-415c-ac6e-deba0d21440d" version="00.01.000">
        <common:shortDescription xml:lang="en">EN15804+A2</common:shortDescription>
        <common:shortDescription xml:lang="de">EN15804+A2</common:shortDescription>
    </referenceToStandard>
    <referenceToUseConditionsDocumentation type="source data set" refObjectId="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" version="00.01.000">
        <common:shortDescription xml:lang="en">wood panel use conditions and service life</common:shortDescription>
        <common:shortDescription xml:lang="de">Einbaubedingungen und Lebensdauer von Holzplatten</common:shortDescription>
    </referenceToUseConditionsDocumentation>
    <comment xml:lang="en">The indicated service life requires installation and maintenance according to manufacturer instructions.</comment>
    <comment xml:lang="de">Die angegebene Lebensdauer setzt eine Installation und Wartung gemäß den Anweisungen des Herstellers voraus.</comment>
</referenceServiceLife>

<esimatedServiceLife epd24:years=8>
    <useConditions factorCategory="A - inherent quality" objectSpecificGrade="5" referenceGrade="1" factor="0.7">
            <comment xml:lang="en">comment here</comment>
            <comment xml:lang="de">Kommentar hier!</comment>
    </useConditions>
    <useConditions factorCategory="B - design level" objectSpecificGrade="5" referenceGrade="2" factor="0.7"/>
    <useConditions factorCategory="C - work execution" objectSpecificGrade="5" referenceGrade="1" factor="0.7"/>
    <useConditions factorCategory="D - indoor environment" objectSpecificGrade="5" referenceGrade="1" factor="0.7"/>
    <useConditions factorCategory="E - outdoor environment" objectSpecificGrade="5" referenceGrade="4" factor="0.7"/>
    <useConditions factorCategory="F - usage conditions" objectSpecificGrade="5" referenceGrade="3" factor="0.7"/>
    <useConditions factorCategory="G - maintenance level" objectSpecificGrade="1" referenceGrade="5" factor="0.7"/>   
    <referenceToStandard type="source data set" refObjectId="c0016b33-8cf7-415c-ac6e-deba0d21440d" version="00.01.000">
        <common:shortDescription xml:lang="en">ISO22057</common:shortDescription>
        <common:shortDescription xml:lang="de">ISO22057</common:shortDescription>
    </referenceToStandard>
    <referenceToUseConditionsDocumentation type="source data set" refObjectId="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" version="00.01.000">
        <common:shortDescription xml:lang="en">wood panel use conditions and service life</common:shortDescription>
        <common:shortDescription xml:lang="de">Einbaubedingungen und Lebensdauer von Holzplatten</common:shortDescription>
    </referenceToUseConditionsDocumentation>
    <comment xml:lang="en">The indicated service life requires installation and maintenance according to manufacturer instructions.</comment>
    <comment xml:lang="de">Die angegebene Lebensdauer setzt eine Installation und Wartung gemäß den Anweisungen des Herstellers voraus.</comment>
</estimatedServiceLife>

InDataWG / ILCD-EPD-Data-Format