EN 15804+A2, chapter 7.1, a), the name and address of the manufacturer(s)

[RobertSpang]

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

the name and address of the manufacturer(s) shall be mentioned. Is most probably not covered at the moment, since it could vary from C2.3 data set generator and C3.8 owner of the data set

Solution description

Check if new field is needed and how we would deal with large assiciations

Relevance or added value

Medium relevance

[RobertSpang]

We understand, that the format already contains a field which is "owner of the EPD" and in the field "use advice for the dataset" the sites covered shall be described. So from our perspective no action is required at the moment.

[okworx]

The discussion arrives at a point where both the names and addresses of the manufacturers (legal entity) are to be declared as well as the production sites (geo coordinates).

Proposal: we are allowing a list of manufacturers and nested for each manufacturer the productions sites can be declared using geo coordinates and optionally street address. Site ID and manufacturer ID to be included.

addresses https://github.com/InDataWG/ILCD-EPD-Data-Format/issues/18, #22 and https://github.com/InDataWG/ILCD-EPD-Data-Format/issues/23

[1aun]

Use for (incl. reference to standard, section/subsection)

• EN 15804+A2, chapter 7.1, a), the name and address of the manufacturer(s)

Don't user for

• Dataset generator
• Owner of the dataset

Suggested Name (if e.g. a single new field is requested)

manufacturers

Suggested Locations within ILCD

• DatasetInformation

Description of context

Goods and products have a manufacturer, sometimes even more than one. That is the case, if a product is developed

• simultaneously in more than one plant
• in parts in different places.

Occurrence

Optional

Cardinality

multiple

Content / Data

A reference to a contact data set

• Type: Global reference type
• Occurence: Mandatory
• Cardinality: 1

The contact should include a operator id.

Site data

• Occurence: Mandatory
• Cardinality: Multiple

Should include facility id, geodata and street adress

Constraints

• List the constraints that need to be enforced (validation errors)