Process data set: baseName0; treatmentStandardsRoutes0; mixAndLocationTypes0; functionalUnitFlowProperties0 (en)
Table of Contents: Process information - Modelling and validation - Administrative information - Inputs and Outputs - LCIA results
Process information
Key Data Set Information
LocationLocation, country or region the data set represents. [Note 1: This field does not refer to e.g. the country in which a specific site is located that is represented by this data set but to the actually represented country, region, or site. Note 2: Entry can be of type "two-letter ISO 3166 country code" for countries, "seven-letter regional codes" for regions or continents, or "market areas and market organisations", as predefined for the ILCD. Also a name for e.g. a specific plant etc. can be given here (e.g. "FR, Lyon, XY Company, Z Site"; user defined). Note 3: The fact whether the entry refers to production or to consumption / supply has to be stated in the name-field "Mix and location types" e.g. as "Production mix".]EU-28
Geographical representativeness descriptionFurther explanations about additional aspects of the location: e.g. a company and/or site description and address, whether for certain sub-areas within the "Location" the data set is not valid, whether data is only valid for certain regions within the location indicated, or whether certain elementary flows or intermediate product flows are extrapolated from another geographical area.descriptionOfRestrictions0
Reference yearStart year of the time period for which the data set is valid (until year of "Data set valid until:"). For data sets that combine data from different years, the most representative year is given regarding the overall environmental impact. In that case, the reference year is derived by expert judgement.1234
NameGeneral descriptive and specifying name of the process.
Base nameGeneral descriptive name of the process and/or its main good(s) or service(s) and/or it's level of processing.; Treatment, standards, routesSpecifying information on the good, service, or process in technical term(s): treatment received, standard fulfilled, product quality, use information, production route name, educt name, primary / secondary etc. Separated by commata.; Mix and location typesSpecifying information on the good, service, or process whether being a production mix or consumption mix, location type of availability (such as e.g. "to consumer" or "at plant"). Separated by commata.; Quantitative product or process propertiesFurther, quantitative specifying information on the good, service or process in technical term(s): qualifying constituent(s)-content and / or energy-content per unit etc. as appropriate. Separated by commata. (Note: non-qualifying flow properties, CAS No, Synonyms, Chemical formulas etc. are documented exclusively in the "Flow data set".)
baseName0; treatmentStandardsRoutes0; mixAndLocationTypes0; functionalUnitFlowProperties0
Identifier of sub-data setIdentifier of a sub-set of a complete process data set. This can be the life cycle stage that a data set covers (such as used in EPDs for modular LCI reporting, with the inventory split up into "resource extraction stage", "production stage", "use stage" and "end-of-life stage"). Or it can be e.g. the type of emission source from which the elementary flows of the Inputs and Outputs stems (e.g. "incineration-related", "transport-related", etc.). Together with the field "Complementing processes" this allows to split up a process data set into a number of clearly identified data sets, each carrying only a part of the inventory and that together represent the complete inventory. Care has to be taken when naming the reference flow, to avoid misinterpretation.identifierOfSubDataSet0
Use advice for data setSpecific methodological advice for data set users that requires attention. E.g. on inclusion/exclusion of recycling e.g. in material data sets, specific use phase behavior to be modelled, and other methodological advices. See also field "Technological applicability".useAdviceForDataSet0
Technical purpose of product or processDescription of the intended / possible applications of the good, service, or process. E.g. for which type of products the material, represented by this data set, is used. Examples: "This high purity chemical is used for analytical laboratories only." or "This technical quality bulk chemical is used for large scale synthesis in chemical industry.". Or: "This truck is used only for long-distance transport of liquid bulk chemicals".technologicalApplicability0
SynonymsSynonyms / alternative names / brands of the good, service, or process. Separated by semicolon.synonyms0
Complementing processes"Process data set(s)" that complement this partial / sub-set of a complete process data set, if any and available as separate data set(s). The identifying name of this sub-set should be stated in the field "Identifier of sub-data set".
Complementing process (process data set)reference to one complementing processshortDescription78 (No URI available)
reference to one complementing processshortDescription80 (No URI available)
ClassificationOptional statistical or other classification of the data set. Typically also used for structuring LCA databases. ()
Class nameName of the class. / Hierarchy levelHierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.
Energy carriers and technologies / Electricity
ClassificationOptional statistical or other classification of the data set. Typically also used for structuring LCA databases. ()
Class nameName of the class. / Hierarchy levelHierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.
class2 / class3
General comment on data setGeneral information about the data set, including e.g. general (internal, not reviewed) quality statements as well as information sources used. (Note: Please also check the more specific fields e.g. on "Intended application", "Advice on data set use" and the fields in the "Modelling and validation" section to avoid overlapping entries.)generalComment0
Copyright?Indicates whether or not a copyright on the data set exists. Decided upon by the "Owner of data set". [Note: See also field "Access and use restrictions".]No
Owner of data set (contact data set)"Contact data set" of the person or entity who owns this data set. (Note: this is not necessarily the publisher of the data set.)shortDescription58 (No URI available)
Data set LCA report, background info (source data set)"Source data set(s)" of detailed LCA study on the process or product represented by this data set, as well as documents / files with overarching documentative information on technology, geographical and / or time aspects etc. (e.g. basic engineering studies, process simulation results, patents, plant documentation, model behind the parameterisation of the "Mathematical model" section, etc.) (Note: can indirectly reference to digital file.)shortDescription0 (No URI available) (subReference0, subReference1)
"Source data set(s)" of detailed LCA study on the process or product represented by this data set, as well as documents / files with overarching documentative information on technology, geographical and / or time aspects etc. (e.g. basic engineering studies, process simulation results, patents, plant documentation, model behind the parameterisation of the "Mathematical model" section, etc.) (Note: can indirectly reference to digital file.)shortDescription2 (No URI available) (subReference2, subReference3)
Quantitative reference
Reference flow(s)One or more of the Inputs or Outputs in case "Type of quantitative reference" is of type "Reference flow(s)". (Data set internal reference.) - 0 ()
One or more of the Inputs or Outputs in case "Type of quantitative reference" is of type "Reference flow(s)". (Data set internal reference.) - 0 ()
Functional unit, Production period, or Other parameterQuantity, name, property/quality, and measurement unit of the Functional unit, Production period, or Other parameter, in case "Type of quantitative reference" is of one of these types. [Note: One or more functional units can also be given in addition to a reference flow.]functionalUnitOrOther0
Functional unit, Production period, or Other parameterQuantity, name, property/quality, and measurement unit of the Functional unit, Production period, or Other parameter, in case "Type of quantitative reference" is of one of these types. [Note: One or more functional units can also be given in addition to a reference flow.]functionalUnitOrOther1
Time representativeness
Data set valid until:End year of the time period for which the data set is still valid / sufficiently representative. This date also determines when a data set revision / remodelling is required or recommended due to expected relevant changes in environmentally or technically relevant inventory values, including in the background system.1234
Time representativeness descriptionDescription of the valid time span of the data set including information on limited usability within sub-time spans (e.g. summer/winter).timeRepresentativenessDescription0
Geographical representativeness
Sub-location(s)One or more geographical sub-unit(s) of the stated "Location". Such sub-units can be e.g. the sampling sites of a company-average data set, the countries of a region-average data set, or specific sites in a country-average data set. [Note: For single site data sets this field is empty and the site is named in the "Location" field.]DE
Geographical representativeness descriptionFurther explanations about additional aspects of the location: e.g. a company and/or site description and address, whether for certain sub-areas within the "Location" the data set is not valid, whether data is only valid for certain regions within the location indicated, or whether certain elementary flows or intermediate product flows are extrapolated from another geographical area.descriptionOfRestrictions2
Sub-location(s)One or more geographical sub-unit(s) of the stated "Location". Such sub-units can be e.g. the sampling sites of a company-average data set, the countries of a region-average data set, or specific sites in a country-average data set. [Note: For single site data sets this field is empty and the site is named in the "Location" field.]FR
Geographical representativeness descriptionFurther explanations about additional aspects of the location: e.g. a company and/or site description and address, whether for certain sub-areas within the "Location" the data set is not valid, whether data is only valid for certain regions within the location indicated, or whether certain elementary flows or intermediate product flows are extrapolated from another geographical area.descriptionOfRestrictions4
Technological representativeness
Technology description including background systemDescription of the technological characteristics including operating conditions of the process or product system. For the latter this includes the relevant upstream and downstream processes included in the data set. Professional terminology should be used.technologyDescriptionAndIncludedProcesses0
Included data sets (process data set)"Process data set(s)" included in this data set, if any and available as separate data set(s).shortDescription4 (No URI available)
"Process data set(s)" included in this data set, if any and available as separate data set(s).shortDescription6 (No URI available)
Pictogramme of technology (source data set)"Source data set" of the pictogramme of the good, service, technogy, plant etc. represented by this data set. For use in graphical user interfaces of LCA software.
Flow diagramm(s) or picture(s) (source data set)"Source data set" of the flow diagramm(s) and/or photo(s) of the good, service, technology, plant etc represented by this data set. For clearer illustration and documentation of data set.
Flow diagramm(s) or picture(s) (source data set)"Source data set" of the flow diagramm(s) and/or photo(s) of the good, service, technology, plant etc represented by this data set. For clearer illustration and documentation of data set.
Model descriptionDescription of the model(s) represented in this section of mathematical relations. Can cover information on restrictions, model strenghts and weaknesses, etc. (Note: Also see information provided on the level of the individual formula in field "Comment" and in the general process description in the fields in section "Technology".)modelDescription0
Variable / parameter
Variable / parameterName of variable or parameter used as scaling factors for the "Mean amount" of individual inputs or outputs of the data set.FormulaMathematical expression that determines the value of a variable. [Note: A parameter is defined by entering the value manually into the field "Mean value" and this field can be left empty.]Mean valueParameter value entered by user OR in case a formula is given in the "Formula" field, the result of the formula for the variable is displayed here.Minimum valueMinimum value permissible for this parameter. For variables this field is empty.Maximum valueMaximum value permissible for this parameter. For variables this field is empty.Uncertainty distribution typeDefines the kind of uncertainty distribution that is valid for this particular object or parameter.Relative StdDev in %The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness etc. [Notes: For log-normal distribution the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), Mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals 97.5% value (= Maximum value), Mean value minus 2*SD equals 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.]Comment, units, defaultsComment or description of variable or parameter. Typically including its unit and default values, e.g. in the pattern <[unit] description; defaults; comments>.
variable0formula0000undefinedProbability distribution information not available.12.123 %comment0
variable1formula1000undefinedProbability distribution information not available.12.123 %comment2
Modelling and validation
LCI method and allocation
Type of data setType of the data set regarding systematic inclusion/exclusion of upstream or downstream processes, transparency and internal (hidden) multi-functionality, and the completeness of modelling.Unit process, single operation
LCI method principleLCI method principle followed in the product system modelling, i.e. regarding using average data (= attributional = non-marginal) or modelling effects in a change-oriented way (= consequential = marginal).Attributional
Deviation from LCI method principle / explanationsShort description of any deviations from the general "LCI method principles" and additional explanations. Refers especially to specific processes/cases where the stated "attributional" or "consequential" approach was not applied. Or where deviations were made from any specific rules for applying the "Consequential with attributional components" approach. A reference to the "Intended application" of the data collection can be made here, too. Allocated co-products may be reported here as well. In case of no (quantitatively relevant) deviations from the LCI method principle, "none" should be stated.deviationsFromLCIMethodPrinciple0
LCI method approachesNames briefly the specific approach(es) used in LCI modeling, e.g. allocation, substitution etc. In case of LCI results and Partly terminated system data sets this also covers those applied in the included background system.Allocation - market value
Names briefly the specific approach(es) used in LCI modeling, e.g. allocation, substitution etc. In case of LCI results and Partly terminated system data sets this also covers those applied in the included background system.Allocation - market value
Deviations from LCI method approaches / explanationsDescription of relevant deviations from the applied approaches as well as of the relevant specific approaches that were applied, including in an possibly included background system. Further explanations and details of the allocation, substitution and other consequential approaches applied for relevant processes, e.g. how the marginal substitute was identified, year and region of which market prices were used in market allocation, i.e. method, procedure, data/information details. In case of no (result relevant) deviations from the before stated LCI method approaches, and in case of no need for further explanations, "none" is entered.deviationsFromLCIMethodApproaches0
Modelling constantsShort identification and description of constants applied in LCI modelling other than allocation / substitution, e.g. systematic setting of recycling quota, use of gross or net calorific value, etc.modellingConstants0
Deviation from modelling constants / explanationsShort description of data set specific deviations from the "Modelling constants" if any, including in the possibly included background system.deviationsFromModellingConstants0
LCA methodology report (source data set)"Source data set"(s) where the generally used LCA methods including the LCI method principles and specific approaches, the modelling constants details, as well as any other applied methodological conventions are described.shortDescription14 (No URI available) (subReference14, subReference15)
"Source data set"(s) where the generally used LCA methods including the LCI method principles and specific approaches, the modelling constants details, as well as any other applied methodological conventions are described.shortDescription16 (No URI available) (subReference16, subReference17)
Data sources, treatment, and representativeness
Data cut-off and completeness principlesPrinciples applied in data collection regarding completeness of (also intermediate) product and waste flows and of elementary flows. Examples are: cut-off rules, systematic exclusion of infrastructure, services or auxiliaries, etc. systematic exclusion of air in incineration processes, coling water, etc.dataCutOffAndCompletenessPrinciples0
Deviation from data cut-off and completeness principles / explanationsShort description of any deviations from the "Data completeness principles". In case of no (result relevant) deviations, "none" is entered.deviationsFromCutOffAndCompletenessPrinciples0
Data selection and combination principlesPrinciples applied in data selection and in combination of data from different sources. Includes brief discussion of consistency of data sources regarding data itself, modelling, appropriateness. In case of averaging: Principles and data selection applied in horizontal and / or vertical averaging.dataSelectionAndCombinationPrinciples0
Deviation from data selection and combination principles / explanationsShort description of any deviations from the "Data selection and combination principles". In case of no (result relevant) deviations, "none" is entered.deviationsFromSelectionAndCombinationPrinciples0
Data treatment and extrapolations principlesPrinciples applied regarding methods, sources, and assumptions done in data adjustment including extrapolations of data from another time period, another geographical area, or another technology.dataTreatmentAndExtrapolationsPrinciples0
Deviation from data treatment and extrapolations principles / explanationsShort description of any deviations from the " Data treatment and extrapolations principles". In case of no (result relevant) deviations, "none" is entered. (Note: If data representative for one "Location" is used for another "Location", its original representativity can be indicated here; see field "Percentage supply or production covered".)deviationsFromTreatmentAndExtrapolationPrinciples0
Data handling report (source data set)"Source data set"(s) of the source(s) in which the data completeness, selection, combination, treatment, and extrapolations principles' details are describedshortDescription18 (No URI available) (subReference18, subReference19)
"Source data set"(s) of the source(s) in which the data completeness, selection, combination, treatment, and extrapolations principles' details are describedshortDescription20 (No URI available) (subReference20, subReference21)
Data source(s) used for this data set (source data set)"Source data set"(s) of the source(s) used for deriving/compiling the inventory of this data set e.g. questionnaires, monographies, plant operation protocols, etc. For LCI results and Partly terminated systems the sources for relevant background system data are to be given, too. For parameterised data sets the sources used for the parameterisation / mathematical relations in the section "Mathematical model" are referenced here as well. [Note: If the data set stems from another database or data set publication and is only re-published: identify the origin of a converted data set in "Converted original data set from:" field in section "Data entry by" and its unchanged re-publication in "Unchanged re-publication of:" in the section "Publication and ownership". The data sources used to model a converted or re-published data set are nevertheless to be given here in this field, for transparency reasons.]shortDescription22 (No URI available) (subReference22, subReference23)
"Source data set"(s) of the source(s) used for deriving/compiling the inventory of this data set e.g. questionnaires, monographies, plant operation protocols, etc. For LCI results and Partly terminated systems the sources for relevant background system data are to be given, too. For parameterised data sets the sources used for the parameterisation / mathematical relations in the section "Mathematical model" are referenced here as well. [Note: If the data set stems from another database or data set publication and is only re-published: identify the origin of a converted data set in "Converted original data set from:" field in section "Data entry by" and its unchanged re-publication in "Unchanged re-publication of:" in the section "Publication and ownership". The data sources used to model a converted or re-published data set are nevertheless to be given here in this field, for transparency reasons.]shortDescription24 (No URI available) (subReference24, subReference25)
Percentage supply or production coveredPercentage of the overall supply, consumption, or production of the specific good, service, or technology represented by this data set, in the region/market of the stated "Location". For multi-functional processes the market share of the specific technology is stated. If data that is representative for a process operated in one "Location" is used for another "Location", the entry is '0'. The representativity for the original "Location" is documented in the field "Deviation from data treatment and extrapolation principles, explanations".12.123 %
Annual supply or production volumeSupply / consumption or production volume of the specific good, service, or technology in the region/market of the stated "Location". The market volume is given in absolute numbers per year, in common units, for the stated "Reference year". For multi-fucntional processes the data should be given for all co-functions (good and services).annualSupplyOrProductionVolume0
Sampling procedureSampling procedure used for quantifying the amounts of Inputs and Outputs. Possible problems in combining different sampling procedures should be mentioned.samplingProcedure0
Data collection periodDate(s) or time period(s) when the data was collected. Note that this does NOT refer to e.g. the publication dates of papers or books from which the data may stem, but to the original data collection period.dataCollectionPeriod0
Uncertainty adjustmentsDescription of methods, sources, and assumptions made in uncertainty adjustment. [Note: For data sets where the additional uncertainty due to lacking representativeness has been included in the quantified uncertainty values, this field also reports the original representativeness, the additional uncertainty, and the procedure by which the overall uncertainty was assessed or calculated.]uncertaintyAdjustments0
Completeness
Completeness product modelCompleteness of coverage of relevant product, waste and elementary flows. [Notes: For LCI results and Partly terminated systems this means throughout the underlying product system model. "Relevant" refers to the overall environmental relevance, i.e. for unit processes including the upstream and downstream burdens of product and waste flows.]All relevant flows quantified
Supported impact assessment methods (LCIA method data set)"LCIA methods data sets" that can be applied to the elementary flows in the Inputs and Outputs section, i.e. ALL these flows are referenced by the respective LCIA method data set (if they are of environmental relevance and a characterisation factor is defined for the respective flow). [Note: Applicability is not given if the inventoty contains some elementary flows with the same meaning as referenced in the LCIA method data set but in a different nomenclature (and hence carry no characterisation factor), or if the flows are sum indicators or flow groups that are addressed differently in the LCIA method data set.]shortDescription26 (No URI available)
"LCIA methods data sets" that can be applied to the elementary flows in the Inputs and Outputs section, i.e. ALL these flows are referenced by the respective LCIA method data set (if they are of environmental relevance and a characterisation factor is defined for the respective flow). [Note: Applicability is not given if the inventoty contains some elementary flows with the same meaning as referenced in the LCIA method data set but in a different nomenclature (and hence carry no characterisation factor), or if the flows are sum indicators or flow groups that are addressed differently in the LCIA method data set.]shortDescription28 (No URI available)
Completeness elementary flows, per topicCompleteness of the elementary flows in the Inputs and Outputs section of this data set from impact perspective, regarding addressing the individual mid-point problem field / impact category given. The completeness refers to the state-of-the-art of scientific knowledge whether or not an individual elementary flow contributes to the respective mid-point topic in a relevant way, which is e.g. the basis for the ILCD reference elementary flows. [Note: The "Completeness" statement does not automatically mean that related LCIA methods exist or reference the elementary flows of this data set. Hence for direct applicability of existing LCIA methods, check the field "Supported LCIA method data sets".]Climate changeClimate change / global warming: All relevant flows quantifiedAll relevant flows are recorded. [Note: This does not consider yet the quality or representativeness of the data.]
Completeness of the elementary flows in the Inputs and Outputs section of this data set from impact perspective, regarding addressing the individual mid-point problem field / impact category given. The completeness refers to the state-of-the-art of scientific knowledge whether or not an individual elementary flow contributes to the respective mid-point topic in a relevant way, which is e.g. the basis for the ILCD reference elementary flows. [Note: The "Completeness" statement does not automatically mean that related LCIA methods exist or reference the elementary flows of this data set. Hence for direct applicability of existing LCIA methods, check the field "Supported LCIA method data sets".]Freshwater ecotoxicityFreshwater eco-toxicity (EXcluding ionising radiation): All relevant flows quantifiedAll relevant flows are recorded. [Note: This does not consider yet the quality or representativeness of the data.]
Completeness other problem field(s)Completeness of coverage of elementary flows that contribute to other problem fields that are named here as free text, preferably using the same terminology as for the specified environmental problems.completenessOtherProblemField0
Validation
ReviewReview information on data set.Dependent internal reviewReviewer(s)/verifier(s) have been involved in collecting, modelling, or entering the data set information or inventory, have commissioned or financed the work, or represent the process or product system (or quantiatitively relevant parts of it).
Scope of reviewScope of review regarding which aspects and components of the data set was reviewed or verified. In case of aggregated e.g. LCI results also and on which level of detail (e.g. LCI results only, included unit processes, ...) the review / verification was performed.Method(s) of reviewValidation method(s) used in the respective "Scope of review".
Goal and scope definitionReview/verification is done regarding e.g. goal definition, subsequent scope definition and corresponding product system description, appropriate identification and definition of function and functional unit, system boundary and cut-off criteria setting, choice of appropriate LCI modelling principles and approaches for multi-functional processes.Expert judgementAnalysis by means of expert opinions. The expert(s) have methodological and detailed technical expertise on the item to be verified and the process or product system in question.
Compliance with ISO 14040 to 14044Methodological compliance with ISO 14040 to 14044 was checked by an LCA expert.
Unit process(es), single operationThe review is done on the level of the "Unit operation type unit process(es)" that can not be further subdivided. Covers multi-functional processes of unit operation type.Element balanceThe balance of the relevant chemical elements of the Inputs and Outputs is calculated and validated. The validated elements should be named in the review comments. [Note: For processes that have undergone allocation or consequential modeling the value of this review method is limited.]
Expert judgementAnalysis by means of expert opinions. The expert(s) have methodological and detailed technical expertise on the item to be verified and the process or product system in question.
Data quality indicatorData quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.Technological representativenessDegree to which the data set reflects the true population of interest regarding technology, including for included background data sets, if any.: GoodMeets the criterium to a high degree, having little yet significant need for improvement. This is to be judged in view of the criterium's contribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.CompletenessShare of (elementary) flows that are quantitatively included in the inventory. Note that also the completeness of interim product and waste flows in the product model contributes to the overall completeness of the inventory.: FairMeets the criterium to a still sufficient degree, while having the need for improvement. This is to be judged in view of the criterium's contribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
Review detailsSummary of the review. All the following items should be explicitly addressed: Representativeness, completeness, and precision of Inputs and Outputs for the process in its documented location, technology and time i.e. both completeness of technical model (product, waste, and elementary flows) and completeness of coverage of the relevant problem fields (environmental, human health, resource use) for this specific good, service, or process. Plausibility of data. Correctness and appropriateness of the data set documentation. Appropriateness of system boundaries, cut-off rules, LCI modelling choices such as e.g. allocation, consistency of included processes and of LCI methodology. If the data set comprises pre-calculated LCIA results, the correspondence of the Input and Output elementary flows (including their geographical validity) with the applied LCIA method(s) should be addressed by the reviewer. An overall quality statement on the data set may be included here.reviewDetails0
Reviewer name and institution (contact data set)"Contact data set" of reviewer. The full name of reviewer(s) and institution(s) as well as a contact address and/or email should be provided in that contact data set.shortDescription82 (No URI available)
"Contact data set" of reviewer. The full name of reviewer(s) and institution(s) as well as a contact address and/or email should be provided in that contact data set.shortDescription84 (No URI available)
Subsequent review commentsFurther information from the review process, especially comments received from third parties once the data set has been published or additional reviewer comments from an additional external review.otherReviewDetails0
Complete review report (source data set)"Source data set" of the complete review report.shortDescription86 (No URI available) (subReference80, subReference81)
ReviewReview information on data set.Independent external reviewReviewer(s)/verifier(s) do not belong to the organisations or legally linked organisations that have been involved in collecting, modelling, or entering the data set information or inventory, have not commissioned or financed the work, or represent the process or product system (or quantiatitively relevant parts of it).
Scope of reviewScope of review regarding which aspects and components of the data set was reviewed or verified. In case of aggregated e.g. LCI results also and on which level of detail (e.g. LCI results only, included unit processes, ...) the review / verification was performed.Method(s) of reviewValidation method(s) used in the respective "Scope of review".
Raw dataReview/verification is done on basis of the original "raw data", i.e. the data before it was scaled, converted, or treated in other ways to be used for modelling of a unit process.Expert judgementAnalysis by means of expert opinions. The expert(s) have methodological and detailed technical expertise on the item to be verified and the process or product system in question.
Energy balanceThe energy balance (e.g. gross or net calorific value or exergy) of the Inputs and Outputs is validated. [Note: For processes that have undergone allocation or consequential modeling the value of this review method is limited.]
DocumentationEvidence collection by means of documentation (e.g. data set's meta data, background report)Expert judgementAnalysis by means of expert opinions. The expert(s) have methodological and detailed technical expertise on the item to be verified and the process or product system in question.
Data quality indicatorData quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.Overall qualityThe degree to which the data set’s overall representativeness, completeness, precision as well as methodological appropriateness and consistency reflects the reality the data set is representing.: GoodMeets the criterium to a high degree, having little yet significant need for improvement. This is to be judged in view of the criterium's contribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.Technological representativenessDegree to which the data set reflects the true population of interest regarding technology, including for included background data sets, if any.: FairMeets the criterium to a still sufficient degree, while having the need for improvement. This is to be judged in view of the criterium's contribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
Review detailsSummary of the review. All the following items should be explicitly addressed: Representativeness, completeness, and precision of Inputs and Outputs for the process in its documented location, technology and time i.e. both completeness of technical model (product, waste, and elementary flows) and completeness of coverage of the relevant problem fields (environmental, human health, resource use) for this specific good, service, or process. Plausibility of data. Correctness and appropriateness of the data set documentation. Appropriateness of system boundaries, cut-off rules, LCI modelling choices such as e.g. allocation, consistency of included processes and of LCI methodology. If the data set comprises pre-calculated LCIA results, the correspondence of the Input and Output elementary flows (including their geographical validity) with the applied LCIA method(s) should be addressed by the reviewer. An overall quality statement on the data set may be included here.reviewDetails2
Reviewer name and institution (contact data set)"Contact data set" of reviewer. The full name of reviewer(s) and institution(s) as well as a contact address and/or email should be provided in that contact data set.shortDescription82 (No URI available)
"Contact data set" of reviewer. The full name of reviewer(s) and institution(s) as well as a contact address and/or email should be provided in that contact data set.shortDescription84 (No URI available)
Subsequent review commentsFurther information from the review process, especially comments received from third parties once the data set has been published or additional reviewer comments from an additional external review.otherReviewDetails2
Complete review report (source data set)"Source data set" of the complete review report.shortDescription86 (No URI available) (subReference80, subReference81)
Compliance declarations
Complianceone compliance declaration
Compliance system name (source data set)"Source data set" of the "Compliance system" that is declared to be met by the data set.
shortDescription88 (No URI available)
Approval of overall complianceOfficial approval whether or not and in how far the data set meets all the requirements of the "Compliance system" refered to. This approval should be issued/confirmed by the owner of that compliance system, who is identified via the respective "Contact data set".
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Nomenclature complianceNomenclature compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Methodological complianceMethodological compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Review complianceReview/Verification compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Documentation complianceDocumentation/Reporting compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Quality complianceQuality compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Complianceone compliance declaration
Compliance system name (source data set)"Source data set" of the "Compliance system" that is declared to be met by the data set.
shortDescription90 (No URI available)
Approval of overall complianceOfficial approval whether or not and in how far the data set meets all the requirements of the "Compliance system" refered to. This approval should be issued/confirmed by the owner of that compliance system, who is identified via the respective "Contact data set".
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Nomenclature complianceNomenclature compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Methodological complianceMethodological compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Review complianceReview/Verification compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Documentation complianceDocumentation/Reporting compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Quality complianceQuality compliance of this data set with the respective requirements set by the "compliance system" refered to.
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Administrative information
Commissioner and goal
Commissioner of data set (contact data set)"Contact data set" of the commissioner / financing party of the data collection / compilation and of the data set modelling. For groups of commissioners, each single organisation should be named. For data set updates and for direct use of data from formerly commissioned studies, also the original commissioner should be named.shortDescription30 (No URI available)
"Contact data set" of the commissioner / financing party of the data collection / compilation and of the data set modelling. For groups of commissioners, each single organisation should be named. For data set updates and for direct use of data from formerly commissioned studies, also the original commissioner should be named.shortDescription32 (No URI available)
ProjectProject within which the data set was modelled in its present version. [Note: If the project was published e.g. as a report, this can be referenced in the "Publication of data set in:" field in the "Publication and ownership" sub-section.project0
Intended applicationsDocumentation of the intended application(s) of data collection and data set modelling. This indicates / includes information on the level of detail, the specifidity, and the quality ambition in the effort.intendedApplications0
Data set generator / modeller
Data set generator / modeller (contact data set)"Contact data set" of the person(s), working group(s), organisation(s) or database network, that generated the data set, i.e. being responsible for its correctness regarding methods, inventory, and documentative information.shortDescription34 (No URI available)
"Contact data set" of the person(s), working group(s), organisation(s) or database network, that generated the data set, i.e. being responsible for its correctness regarding methods, inventory, and documentative information.shortDescription36 (No URI available)
Data entry by
Time stamp (last saved)Date and time stamp of data set generation, typically an automated entry ("last saved").2006-05-04 18:13:51.0 UTC
Data set format(s) (source data set)"Source data set" of the used version of the ILCD format. If additional data format fields have been integrated into the data set file, using the "namespace" option, the used format namespace(s) are to be given. This is the case if the data sets carries additional information as specified by other, particular LCA formats, e.g. of other database networks or LCA softwares.ILCD format
"Source data set" of the used version of the ILCD format. If additional data format fields have been integrated into the data set file, using the "namespace" option, the used format namespace(s) are to be given. This is the case if the data sets carries additional information as specified by other, particular LCA formats, e.g. of other database networks or LCA softwares.shortDescription40 (No URI available)
Converted original data set from: (source data set)"Source data set" of the database or data set publication from which this data set has been obtained by conversion. This can cover e.g. conversion to a different format, applying a different nomenclature, mapping of flow names, conversion of units, etc. This may however not have changed or re-modeled the Inputs and Outputs, i.e. obtaining the same LCIA results. This entry is required for converted data sets stemming originally from other LCA databases (e.g. when re-publishing data from IISI, ILCD etc. databases). [Note: Identically re-published data sets are identied in the field "Unchanged re-publication of:" in the section "Publication and Ownership".]shortDescription42 (No URI available)
Data entry by: (contact data set)"Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information.shortDescription44 (No URI available)
Official approval of data set by producer/operator: (contact data set)"Source data set": Names exclusively the producer or operator of the good, service or technology represented by this data set, which officially has approved this data set in all its parts. In case of nationally or internationally averaged data sets, this will be the respective business association. If no official approval has been given, the entry "No official approval by producer or operator" is to be entered and the reference will point to an empty "Contact data set". [Notes: The producer or operator may only be named here, if a written approval of this data set was given. A recognition of this data set by any other organisation then the producer/operator of the good, service, or process is not to be stated here, but as a "review" in the validation section.]shortDescription46 (No URI available)
"Source data set": Names exclusively the producer or operator of the good, service or technology represented by this data set, which officially has approved this data set in all its parts. In case of nationally or internationally averaged data sets, this will be the respective business association. If no official approval has been given, the entry "No official approval by producer or operator" is to be entered and the reference will point to an empty "Contact data set". [Notes: The producer or operator may only be named here, if a written approval of this data set was given. A recognition of this data set by any other organisation then the producer/operator of the good, service, or process is not to be stated here, but as a "review" in the validation section.]shortDescription48 (No URI available)
Publication and ownership
UUID of Process data setAutomatically generated Universally Unique Identifier of this data set. Together with the "Data set version", the UUID uniquely identifies each data set.00000000-0000-0000-0000-000000000000
Date of last revisionDate when the data set was revised for the last time, typically manually set.2006-05-04T18:13:51.0Z
Data set versionVersion number of data set. First two digits refer to major updates, the second two digits to minor revisions and error corrections etc. The third three digits are intended for automatic and internal counting of versions during data set development. Together with the data set's UUID, the "Data set version" uniquely identifies each data set.00.00
Preceding data set version (process data set)Last preceding data set, which was replaced by this version. Either a URI of that data set (i.e. an internet address) or its UUID plus version number is given (or both).shortDescription50 (No URI available)
Last preceding data set, which was replaced by this version. Either a URI of that data set (i.e. an internet address) or its UUID plus version number is given (or both).shortDescription52 (No URI available)
Permanent data set URIURI (i.e. an internet address) of the original of this data set. [Note: This equally globally unique identifier supports users and software tools to identify and retrieve the original version of a data set via the internet or to check for available updates. The URI must not represent an existing WWW address, but it should be unique and point to the data access point, e.g. by combining the data owner's www path with the data set's UUID, e.g. http://www.mycompany.com/lca/processes/50f12420-8855-12db-b606-0900210c9a66.]
Workflow and publication statusWorkflow or publication status of data set. Details e.g. of foreseen publication dates should be provided on request by the "Data set owner".Working draft
Unchanged re-publication of: (source data set)"Source data set" of the publication, in which this data set was published for the first time. [Note: This refers to exactly this data set as it is, without any format conversion, adjustments, flow name mapping, etc. In case this data set was modified/converted, the original source is documented in "Converted original data set from:" in section "Data entry by".]shortDescription54 (No URI available) (subReference54, subReference55)
Registration authority (contact data set)"Contact data set" of the authority that has registered this data set.shortDescription56 (No URI available)
Registration numberA unique identifying number for this data set issued by the registration authority.registrationNumber0
Owner of data set (contact data set)"Contact data set" of the person or entity who owns this data set. (Note: this is not necessarily the publisher of the data set.)shortDescription58 (No URI available)
Entities or persons with exclusive access to this data set (contact data set)"Contact data set" of those entities or persons (or groups of these), to which an exclusive access to this data set is granted. Mainly intended to be used in confidentiality management in projects. [Note: See also field "Access and use restrictions".]shortDescription60 (No URI available)
"Contact data set" of those entities or persons (or groups of these), to which an exclusive access to this data set is granted. Mainly intended to be used in confidentiality management in projects. [Note: See also field "Access and use restrictions".]shortDescription62 (No URI available)
License typeType of license that applies to the access and use of this data set.Free of charge for all users and uses
Access and use restrictionsAccess restrictions / use conditions for this data set as free text or referring to e.g. license conditions. In case of no restrictions "None" is entered.accessRestrictions0
Inputs and Outputs
Inputs
Type Of FlowNames the basic type of the flow.ClassificationVariableData set internal reference to a variable or parameter name as defined in the section "Mathematical model". The value of this variable or parameter acts as linear multiplier to the value given in the field "Mean amount" to yield the "Resulting amount", which is the final value in the inventory.LocationLocation where exchange of elementary flow occurs. Used only for those LCIA methods, that make use of this information. This information refers to the entry within the same field in the "Inputs and Outpts" section of the "Process or LCI result data set".Flow"Flow data set" of this Input or Output.Resulting amountFinal value to be used for calculation of the LCI results and in the product system: It is calculated as the product of the "Mean amount" value times the value of the "Variable". In case that no "Variable" entry is given, the "Resulting amount" is identical to the "Mean amount", i.e. a factor "1" is applied.Mean amountMean amount of the Input or Output. Only significant digits of the amount should be stated.Minimum amountMinimum amount of the Input or Output in case the uncertainty distribution is uniform or triangular. In case of calculated LCI results and for the aggregated flows in Partly terminated system data sets, the lower end of the 95% likelihood range, i.e. the "2.5% value" can be reported in this field.Maximum amountMaximum amount of the Input or Output in case the uncertainty distribution is uniform or triangular. In case of calculated LCI results and for the aggregated flows in Partly terminated system data sets, the upper end of the 95% likelihood range, i.e. the "97.5% value" can be reported in this field.Uncertainty distribution typeDefines the kind of uncertainty distribution that is valid for this particular object or parameter.Relative StdDev in %The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness etc. [Notes: For log-normal distribution the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), Mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals 97.5% value (= Maximum value), Mean value minus 2*SD equals 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.]Allocationscontainer tag for the specification of allocations if process has more than one reference product. Use only for multifunctional processes.Data source typeIdentifies the data source type of each single Input or Output as being "Primary", "Secondary", or "Mixed primary/secondary".Data derivation type / statusIdentifies the way by which the individual Input / Output amount was derived (e.g. measured, estimated etc.), respectively the status and relevancy of missing data.
variable0FRshortDescription64 (No URI available) (subReference66, subReference67, subReference68, subReference69)0 ()000undefinedProbability distribution information not available.12.123 %
no description available (No URI available)42.02 %
no description available (No URI available)57.98 %
General reminder flowReminder flow on the amount of (selected) product and waste flows of included processes. Purely informative flow for additional reporting that has already been fully considered in the inventory of the data set. Serves to document e.g. the total amount of hazardous waste generated over the life cycle of a product system.PrimaryData stems exclusively from primary data source(s), i.e. was collected from owner or operator of the process (independently how the data was derived).MeasuredAll data was measured for the purpose of LCA or is meeting the related requirements (e.g. being quantiatively and qualitatively related to unit process and its quantitative reference/products, etc.). This includes calculated data with models based on measured plant data (but not exclusively theoretical calculations) as used e.g. in parameterised unit processes.
Reference to Data Source"Source data set" of data source(s) used for the value of this specific Input or Output, especially if differing from the general data source used for this data set.shortDescription66 (No URI available) (subReference66, subReference67)
Reference to Data Source"Source data set" of data source(s) used for the value of this specific Input or Output, especially if differing from the general data source used for this data set.shortDescription68 (No URI available) (subReference68, subReference69)
General CommentGeneral comment on this specific Input or Output, e.g. commenting on the data sources used and their specific representatuveness etc., on the status of "finalisation" of an entry as workflow information, etc.generalComment0
variable1DEshortDescription70 (No URI available) (subReference72, subReference73, subReference74, subReference75)0 ()000undefinedProbability distribution information not available.12.123 %
General reminder flowReminder flow on the amount of (selected) product and waste flows of included processes. Purely informative flow for additional reporting that has already been fully considered in the inventory of the data set. Serves to document e.g. the total amount of hazardous waste generated over the life cycle of a product system.PrimaryData stems exclusively from primary data source(s), i.e. was collected from owner or operator of the process (independently how the data was derived).MeasuredAll data was measured for the purpose of LCA or is meeting the related requirements (e.g. being quantiatively and qualitatively related to unit process and its quantitative reference/products, etc.). This includes calculated data with models based on measured plant data (but not exclusively theoretical calculations) as used e.g. in parameterised unit processes.
Reference to Data Source"Source data set" of data source(s) used for the value of this specific Input or Output, especially if differing from the general data source used for this data set.shortDescription70 (No URI available) (subReference72, subReference73)
Reference to Data Source"Source data set" of data source(s) used for the value of this specific Input or Output, especially if differing from the general data source used for this data set.shortDescription72 (No URI available) (subReference74, subReference75)
General CommentGeneral comment on this specific Input or Output, e.g. commenting on the data sources used and their specific representatuveness etc., on the status of "finalisation" of an entry as workflow information, etc.generalComment2
Outputs
Type Of FlowNames the basic type of the flow.ClassificationVariableData set internal reference to a variable or parameter name as defined in the section "Mathematical model". The value of this variable or parameter acts as linear multiplier to the value given in the field "Mean amount" to yield the "Resulting amount", which is the final value in the inventory.LocationLocation where exchange of elementary flow occurs. Used only for those LCIA methods, that make use of this information. This information refers to the entry within the same field in the "Inputs and Outpts" section of the "Process or LCI result data set".Flow"Flow data set" of this Input or Output.Resulting amountFinal value to be used for calculation of the LCI results and in the product system: It is calculated as the product of the "Mean amount" value times the value of the "Variable". In case that no "Variable" entry is given, the "Resulting amount" is identical to the "Mean amount", i.e. a factor "1" is applied.Mean amountMean amount of the Input or Output. Only significant digits of the amount should be stated.Minimum amountMinimum amount of the Input or Output in case the uncertainty distribution is uniform or triangular. In case of calculated LCI results and for the aggregated flows in Partly terminated system data sets, the lower end of the 95% likelihood range, i.e. the "2.5% value" can be reported in this field.Maximum amountMaximum amount of the Input or Output in case the uncertainty distribution is uniform or triangular. In case of calculated LCI results and for the aggregated flows in Partly terminated system data sets, the upper end of the 95% likelihood range, i.e. the "97.5% value" can be reported in this field.Uncertainty distribution typeDefines the kind of uncertainty distribution that is valid for this particular object or parameter.Relative StdDev in %The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness etc. [Notes: For log-normal distribution the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), Mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals 97.5% value (= Maximum value), Mean value minus 2*SD equals 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.]Allocationscontainer tag for the specification of allocations if process has more than one reference product. Use only for multifunctional processes.Data source typeIdentifies the data source type of each single Input or Output as being "Primary", "Secondary", or "Mixed primary/secondary".Data derivation type / statusIdentifies the way by which the individual Input / Output amount was derived (e.g. measured, estimated etc.), respectively the status and relevancy of missing data.
LCIA results
LCIA result
LCIA method (LCIA method data set)"LCIA method data set" applied to calculate the LCIA results.shortDescription74 (No URI available)
Mean amountMean amount of the Input or Output. Only significant digits of the amount should be stated.0
Uncertainty distribution typeDefines the kind of uncertainty distribution that is valid for this particular object or parameter.undefined
Relative StdDev in %The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness etc. [Notes: For log-normal distribution the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), Mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals 97.5% value (= Maximum value), Mean value minus 2*SD equals 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.]12.123 %
CommentGeneral comment on this specific LCIA result, e.g. commenting on the correspondence of the inputs and outputs with the applied LCIA method etc.generalComment4
LCIA result
LCIA method (LCIA method data set)"LCIA method data set" applied to calculate the LCIA results.shortDescription76 (No URI available)
Mean amountMean amount of the Input or Output. Only significant digits of the amount should be stated.0
Uncertainty distribution typeDefines the kind of uncertainty distribution that is valid for this particular object or parameter.undefined
Relative StdDev in %The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness etc. [Notes: For log-normal distribution the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), Mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals 97.5% value (= Maximum value), Mean value minus 2*SD equals 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.]12.123 %
CommentGeneral comment on this specific LCIA result, e.g. commenting on the correspondence of the inputs and outputs with the applied LCIA method etc.generalComment6