Implementation Guidance

See https://github.com/cchangelabs/open-xpd-uuid-lib

dataSetInformation/name/baseName

doctype is always "OpenEPD" for this API. Purpose is compatability with future related stuff, like OpenLCI etc.

tuple sort=+id,+version

publicationAndOwnership/dataSetVersion, converted to integer

Unless otherwise specified, only most recent version should be returned. Retention of previous versions is recommended.

"https://epd-online.com/EmbeddedEpdList/Download/6029"

required if `private` == false

this will always contain the UUID and version number, so it should be possible to look up whether a given ILCD+EPD dataset has already been converted to OpenEPD

/org for READ or /org_ref for CREATE

{"web_domain":"c-change-labs.com"}

required if `private` == false

publicationAndOwnership/referenceToOwnerShipOfDataSet (contact) -> name

[{"id":"6PH57VP3+PR.interface.com"},{"id":"84VVJVR7+W6.structurelam.com"}]

Geographical representativeness/Location/@latitudeAndLongitude

/org for READ or /org_ref for CREATE

required if `private` == false

v1.2: publicationAndOwnership/registrationAuthority (contact) -> name

if an ILCD+EPD dataset is compliant with ILCD+EPD v1.2, it will carry a processDataSet/@epd2:epd-version attribute with the valie "1.2"

tuple sort=+program_operator_doc_id,+program_operator_version

publicationAndOwnership/registrationNumber

tuple sort=+program_operator_doc_id,+program_operator_version

/org for READ or /org_ref for CREATE

{"web_domain":"we-verify-epds.com"}

required if `private` == false

validation/review/referenceToNameOfReviewerAndInstitution (contact) -> name

ref: critical review in https://www.iso.org/obp/ui/#iso:std:iso:ts:14071:ed-1:v1:en

validation/review/referenceToNameOfReviewerAndInstitution (contact) -> name

ref: critical review in https://www.iso.org/obp/ui/#iso:std:iso:ts:14071:ed-1:v1:en

"https://we-verify-epds.com/en/letters/123-456.789b.pdf"

validation/review/referenceToNameOfReviewerAndInstitution (contact) -> email

validation/review/referenceToNameOfReviewerAndInstitution (contact) -> name

validation/review/referenceToNameOfReviewerAndInstitution (contact) -> email

/org for READ or /org_ref for CREATE

{"web_domain":"we-do-lca.com"}

required if `private` == false

v1.2: time/publicationDateOfEPD
v1.1: usually in time/timeRepresentativenessDescription , there's a string like "01.01.1980" - "31.12.1984" which indicates the start and end dates

required if `private` == false

time/dataSetValidUntil has the year, combine with value from above

It should include time part to avoid confusion. Really it just designates UTC+0 as the source of timing.

required if `private` == false

the PCR document(s) is/are linked under modellingAndValidation/LCIMethodAndAllocation/referenceToLCAMethodDetails

possibly, these need to be checked against the PCRs in OpenEPD

.issuer.web_domain, .name, .version,

the reference flow dataset is referenced in the exchanges section, it is the exchange whose internal ID is given under quantitativeReference/referenceToReferenceFlow. It has a value (factor a) that we'll need to calculate the value of the declared unit. In the reference flow dataset, the reference flow property is specified (mass, volume, area etc.) with a factor b. The product of factors a and b yields the value of the declared unit.

The Quantity field lets us express EPDS in 1000 square feet as being in '92.903 m2'

required if `private` == false

in the reference flow dataset in the materialProperties section, there are conversion factors (density, mass per unit area etc.) that can be used to calculate this value

"Ready Mixed Concrete, 6000 psi, 0.75 inch line, self-compacting, low heat"

OpenEPD Implementation doesn't guarantee that applicable_in fileld will not be sanitized and compressed.

[{"lcia":"TRACI 2.1","gwp":{"A1A2A3":{"mean":1.23e4,"unit":"kgCO2e","rsd":0.22,"dist":"log-normal"}}},
{"lcia":"EN 15804+A2","gwp":{"A1A2A3":{"mean":1.26e4,"unit":"kgCO2e","rsd":0.23,"dist":"log-normal"}}}]

required if `private` == false

GWP is the indicator with UUID 77e416eb-a363-4258-a04e-171d843a6460

{
"RPRe":{"A1A2A3":{"mean":1.23e4,"unit":"MJ","rsd":0.43,"dist":"log-normal"},"A5":{"mean":3.21e-1,"unit":"MJ","rsd":0.40,"dist":"log-normal"}},
"fw":{"A1A2A3":{"mean":0.123e-4,"unit":"m3","rsd":0.21,"dist":"log-normal"}}
}

{"concrete":{"28d Strength":"2500 psi","exposure_class":["F2","S3","A3"]}}

{{short_name:"ISO14024:2018","link":"https://www.iso.org/standard/72458.html"},}

complianceDeclarations/compliance

may need to filter for applicable ones like ISO 14025, EN 15804, EN15804+A2, ISO 21930 and ignore the rest, as here also compliance to compliance systems are declared which are not officially standardised (such as InData 2018/2020)

{"datasheet":"https://somemanufacturer.com/datasheets/abcd1234"}

list of /database
may POST as list of /resource_reference.

[{"owner":{"web_domain":"ecoinvent.org"},
"name":"ecoinvent",
"version":"3.10",
"link":"https://support.ecoinvent.org/ecoinvent-version-3.10"},
{"owner":{"web_domain":"lcacommons.gov"},
"name":"ULSCI"
"version":"FY24.Q3.01",
"link":"https://www.lcacommons.gov/lca-collaboration/National_Renewable_Energy_Laboratory/USLCI_Database_Public/datasets"}]

List of software tool(s) and version(s) used for LCA and/or EPD generation.

/software
may POST as /resource_reference.

{"owner":{"web_domain":"greendelta.com"},
"primary_function":"LCA Analysis",
"name":"openLCA",
"version":"2.3.1",
"link":"https://share.greendelta.com/index.php/s/D1xa3haTiHJdhqt?path=%2F2.3.1"}

*Italic text is default guidance and should be deleted before publication. This field uses [Markdown formatting](https://en.wikipedia.org/wiki/Markdown)*
# Packaging
*Information on product-specific packaging: type, composition and possible reuse of packaging materials (paper, strapping, pallets, foils, drums, etc.) shall be included in this Section. The EPD shall describe specific packaging scenario assumptions, including disposition pathways for each packaging material by reuse, recycling, or landfill disposal based on packaging type.*

# Product Installation
*A description of the type of processing, machinery, tools, dust extraction equipment, auxiliary materials, etc. to be used during installation shall be included. Information on industrial and environmental protection may be included in this section. Any waste treatment included within the system boundary of installation waste should be specified.*

# Use Conditions
*Use-stage environmental impacts of flooring products during building operations depend on product cleaning assumptions. Information on cleaning frequency and cleaning products shall be provided based on the manufacturer’s recommendations. In the absence of primary data, cleaning assumptions shall be documented.*

# Re-Use
*The possibilities of re-use, recycling and energy recovery shall be described. If an Extended Producer Responsibility initiative such as a product take-back program exists, this may be included.*

# Disposal
*The possible disposal channels shall be indicated in accordance with disposal routes and waste classification.*

# Cut-Off Criteria
*Cut-off criteria applied shall be documented.*

# Allocation
*Co-product allocation methods used, and a description of how allocation is performed across recycled and/or secondary raw materials, as well as allocation of energy, ancillary, and operating matierals used for individual products in a factory.*

# LCA Interpretation
*An interpretation shall be provided in the EPD which discusses the assumptions and limitations associated with the interpretation of results as declared in the EPD, both methodology and data related.*

*This interpretation shall also include a description of the time frame and/or variance of the LCIA results if the EPD is valid for several products. An illustration of the results with figures is recommended in the EPD, e.g. for the dominance analysis, the distribution of impacts across the modules, the CO2-balance, etc. as appropriate for a reader's understanding of the environmental profile of the declared product.*

# Environment and Health during Manufacturing
*Measures relating to environmental and health protection during the product manufacturing process extending beyond national guidelines (of the production country) may be described, e.g. reference to a product safety data sheet (SDS), description of Environmental Management Systems or similar, programs addressing air emissions, wastewater, noise, etc*
# Environment and Health during Installation
*Information should be provided in this section on the relationship between the product, the environment and health, including possible harmful substances or emissions e.g. reference to a product safety data sheet (SDS). Any recommendations concerning cleaning, maintenance, etc. of the declared product should be listed in “Technical information on scenarios”.*
# Extraordinary Effects - Fire, Water, Mechanical Destruction
## FIRE
*Information should be included on the product’s fire performance and possible impacts on the environment e.g. reaction-to-fire, other relevant fire tests as applicable, and emissions to air.*

## WATER
*Information should be included on the product’s performance and possible impacts on the environment following unforeseeable influence of water, e.g. flooding.*

## MECHANICAL DESTRUCTION
*Information should be included on the product’s performance and possible impacts on the environment following unforeseeable mechanical destruction.*

# Delayed Emissions
*If a manufacturer wishes to declare quantitative or qualitative information on delayed emissions used to calculate Global Warming Potential within the EPD, information may be provided here.*

# Environmental Activities and Certifications
*Other environmental activities, such as participation in recycling or recovery programs along with the details of these programs and contact information, may be provided.
For certifications applied to the product and listed in the EPD, a statement shall be included on where an interested party can find details of the certification program.*

Notes

Endpoints return entities with one layer deep. For example /epds/ endpoint will not fetch and return subsidiaries of manufacturer of epd.

A user may provide open-xpd-uuid in any shape (e.g. 1u7zsed8, 1U-7Z-SED8) during EPD/PCR creation. If not provided, an OpenEPD implementation must accept the open-xpd-uuid returned by the registry.

Color Coding

Text that is in draft form, and is under discussion

Recently changed text that may not yet be implemented

Normal text that describes the current openEPD

Deprecated text (which will not be supported in future versions)