Show: Field nameElement/attribute nameRequirementOccurrencesData typeDefinitioneDoc ID

ILCD Format 1.1 Documentation - LCIA Method data set

Field name Element/attribute name Requ. Occ. Data type Definition eDoc ID
LCIA Method data set LCIAMethodDataSet m [1,1] 3
@version m SchemaVersion
@locations o String
@LCIAMethodologies o String
LCIA method information LCIAMethodInformation m [1,1] 3-17
Data set information dataSetInformation m [1,1] 3-17-70
UUID of LCIA method data set UUID m [1,1] UUID Automatically generated Universally Unique Identifier of this data set. Together with the "Data set version", the UUID uniquely identifies each data set. 3-17-70-201
Name of LCIA method or methodology name r [0,1] StringMultiLang Name of the data set. Composed as follows "LCIA methodology short name; Impact category/ies; midpoint/endpoint; Impact indicator; Source short name". Not applicable components are left out. Examples: "Impacts2007+; Climate change; midpoint; Global Warming Potential; IPCC 2001"; "ABC 2006; Acidification; endpoint; Species diversity loss; John Doe 2006"; "My-indicator2009; combined; endpoint; Ecopoints; various" 3-17-70-202
Belongs to: Name of LCIA methodology/ies methodology r [0,n] string Name of the LCIA methodology/ies the data set belongs to, if any 3-17-70-208
Classfication information classificationInformation [0,1] 3-17-70-204
Classification classification r [0,n] Optional statistical or other classification of the data set. Typically also used for structuring LCA databases. 1-1-2-7-2
Classification system name @name r string Name of the classification system. 1-1-2-7-2-a
Classes @classes r anyURI URL or file name of a file listing all classes of this classification system. [Notes: the referenced file has to be in form of the "ILCDClassification.xml" format. If a classification file is specified, the "class" entry should correspond to the classes defined in the classification file.] 1-1-2-7-2-b
Class name class r [1,n] Name of the class. 1-1-2-7-2-1
Hierarchy level @level r LevelType If more than one class is specified in a hierachical classification system, the hierarchy level (1,2,...) could be specified with this attribute of class. 1-1-2-7-2-1-a
Unique class identifier @classId r string Unique identifier for the class. [Notes: If such identifiers are also defined in the referenced category file, they should be identical. Identifiers can be UUID's, but also other forms are allowed.] 1-1-2-7-2-1-b
Other content other o [0,1] May contain arbitrary content. 0
Impact category/ies impactCategory r [0,n] LCIAImpactCategoryValues

Climate changeClimate change / global warming
Ozone depletionStratospheric ozone layer depletion
Terrestrial Eutrophication
Aquatic Eutrophication
AcidificationAcidification of land and water bodies
Photochemical ozone creation
Land useLand use (occupation and transformation)
Abiotic resource depletion
Biotic resource depletion
Ionizing radiation
Cancer human health effects
Non-cancer human health effects
Respiratory inorganics
Aquatic eco-toxicity
Terrestrial eco-toxicity
other
Impact category/ies covered by the LCIA method or methodology. 3-17-70-209
Area(s) of Protection areaOfProtection r [0,n] AreaOfProtectionValues
Natural resources
Natural environment
Human health
Man-made environment
OtherAnother LCI method approach is used. This is named in "Deviations from LCI method approaches / explanations" where also additional information is given.
For damage (endpoint) and single-point indicators only: Area(s) of Protection the data set relates to. 3-17-70-210
Impact indicator impactIndicator r [0,1] String Description of the meaning of the impact indicator of this data set (not applicable for LCIA methodologies data sets). 3-17-70-211
General comment generalComment o [0,1] FTMultiLang General 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.) 3-17-70-207
External documentation / files source referenceToExternalDocumentation r [0,n] GlobalReferenceType "Source data set(s)" of external documents / files with further documentative information on the data set including on underlying data sources (e.g. time, geographical coverage, impact models, characterisation factors, substance property databases employed, etc.). (Note: can indirectly reference to digital file.) 3-17-70-213
Other content other o [0,1] May contain arbitrary content. 0
Quantitative reference quantitativeReference o [0,1] This section allows to refer to the LCIA method(ology)'s quantitative reference, which is always the unit, in which the characterisation factors of the impact indicator are measured, e.g. "kg CO2-Equivalents". 3-17-72
Reference quantity referenceQuantity r [1,1] GlobalReferenceType "Flow property data set" of the reference quantity (flow property), in which the impact indicator values are measured. 3-17-72-208
Other content other o [0,1] May contain arbitrary content. 0
Time representativeness time o [0,1] 3-17-74
Reference year referenceYear r [0,1] StringMultiLang Reference year when the emission is assumed to take place, i.e. the start year of the time period for which the impact is modelled. For time-independent models "time independent" should be stated. 3-17-74-1
Duration of modelled impact duration r [0,1] StringMultiLang Time period for which the impact is modelled. 3-17-74-2
Time representativeness description timeRepresentativenessDescription 0 [0,1] FTMultiLang Description of the valid time span of the data set including information on limited usability within sub-time spans, if any. 3-17-74-3
Other content other o [0,1] May contain arbitrary content. 0
Reference year referenceYear r [0,1] Year Start 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. 1-1-6-18
Data set valid until: dataSetValidUntil r [0,1] Year 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. 1-1-6-19
Time representativeness description timeRepresentativenessDescription r [0,1] FTMultiLang Description of the valid time span of the data set including information on limited usability within sub-time spans (e.g. summer/winter). 1-1-6-20
Other content other o [0,1] May contain arbitrary content. 0
Geographical representativeness geography m [1,1] 3-17-76
Intervention location interventionLocation r [0,1] Specific, country, or region of the elementary flows' / exchanges' occurence for which the LCIA method(ology) is valid / modelled. [Note: 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). ] 3-17-76-212
Latitude and Longitude @latitudeAndLongitude o GIS Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field is empty. 1-1-8-23
Intervention sub-location(s) interventionSubLocation o [0,n] Geographical sub-unit(s) of "Intervention location(s)" that further specify the specifically modelled sub-locations. Such sub-locations can be e.g. sites of a company, specific catchments modleled, countries of a continent, or locations in a country. Information on limited representativeness should be provided if applicable. 3-17-76-213
Latitude and Longitude @latitudeAndLongitude o GIS Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field is empty. 1-1-8-23
Impact location impactLocation r [0,1] Location or region where the impact is modelled to take place. [Note: 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 catchment etc. can be given here, user defined).] 3-17-76-214
Latitude and Longitude @latitudeAndLongitude o GIS Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field is empty. 1-1-8-23
Geographical representativeness description geographicalRepresentativenessDescription r [0,1] FTMultiLang Further explanation on additional aspects of the location, both regarding the intervention and the impact: whether certain areas are exempted from the location, whether data is only valid for certain sub-locations within the location indicated, or whether impact indicator values for certain elementary flows are extrapolated from another geographical area than indicated. Information on the use of generic intervention and/or impact locations, and other restrictions. 3-17-76-215
Other content other o [0,1] May contain arbitrary content. 0
Impact model impactModel o [0,1] Provides information about the general representativiness of the data set and about its composition of single LCIA-methods. 3-17-78
LCIA characterisation model(s) name(s) modelName r [0,1] ST Name(s) of the model(s) used for calculating the LCIA impact indicator values (if any) 3-17-78-215
LCIA characterisation model description and included sub-models modelDescription r [0,1] FTMultiLang Description of the model used for calculating the LCIA impact indicator values, including underlying substance property data sources, background concentrations, etc. If an LCIA methodology comprises several LCIA methods, these are explicitly included in the description. Professional nomenclature is used for the description. Note that eventually included Normalisation and Weighting factors are described in the dedicated separate fields. 3-17-78-216
LCIA characterisation model source referenceToModelSource r [0,n] GlobalReferenceType "Source data set(s)" of data sources concerning the characterisation model (guidelines, supporting documentation etc) 3-17-78-217
Included LCIA characterisation methods referenceToIncludedMethods r [0,n] GlobalReferenceType "LCIA method data set(s)" of LCIA characterisation methods included in this data set or used to derive this LCIA methodology 3-17-78-218
Considered environmental or other mechanisms along the impact chain consideredMechanisms r [0,1] STMultiLang Description of the environmental or other mechanisms included in the explicitly considered part of the impact chain. Can relate to (ilustrative): For emissions e.g.: transport, conversion / degradation, exposure, effect(s), damage(s) on humans and the natural environment. For material and energy resources: scarcity or other impact concept. For land use: soil, area, biocoenosis related meachanisms, effect(s), damage(s). 3-17-78-219
LCIA method(ology) flowchart referenceToMethodologyFlowChart r [0,n] GlobalReferenceType "Source data set(s)" of flowchart(s) and/or pictures depicting the LCIA method(ology). 3-17-78-220
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Modelling and validation modellingAndValidation m [1,1] Covers the five sub-sections 1) LCIA method, normalisation, weighting 2) Data sources 3) Completeness, 4) Validation, and 5) Compliance declarations. 3-19
Use advice for data set useAdviceForDataSet r [0,1] STMultiLang Methodological advice for the use and application of this data set, such as limits in applicability or representativeness as well as recommendations to use it together with others from the same LCIA methodology to ensure consistency. 3-19-84-221
LCIA method, normalisation, weighting LCIAMethodNormalisationAndWeighting r [0,1] LCIA methodological modelling aspects 3-19-83
Type of data set typeOfDataSet r [0,1] TypeOfLCIAMethodValues
Inventory indicatorMethod for an inventory indicator, i.e. without impact assessment method.
Mid-point indicatorMethod for a mid-point indicator at a point of the impact chain between the inventory and the damage.
Damage indicatorMethod for a damage indicator, representing the damage to a part of a Area of Protection or by specific mechanisms, only.
Area of Protection damage indicatorMethod for a damage indicator, representing the damage to one complete Area of Protection.
Combined single-point indicatorMethod for a damage indicator, representing the damage to one complete Area of Protection.
LCIA methodology documentationDataset that refers to actual LCIA method datasets, providing common metainformation.
Type of data set regarding the extent of the impact chain that is covered. 3-19-83-10
LCIA method principle(s) LCIAMethodPrinciple r [0,n] LCIAMethodPrincipleValues
Distance-to-target
Critical surface-time
Effective volumes
AoP-Damage model
Carrying capacity
Resource dissipation
other
LCIA method principle(s) followed to derive the impact factors. 3-19-83-11
Deviation from LCIA method principle(s) deviationsFromLCIAMethodPrinciple r [0,1] FTMultiLang Short description of possible data set specific deviations from "LCIA method principle(s)". Refers especially to explanations on the combination of LCIA methods with different principles in a single LCIA methodology. 3-19-83-12
Normalisation included? normalisation r [0,1] boolean Indication whether or not a normalisation step was included in the resulting impact factors. 3-19-83-13
Usable Normalisation data set(s), if not yet included referenceToUsableNormalisationDataSets r [0,n] GlobalReferenceType "Normalisation data sets" that can be used together with the impact factors of this data set. 3-19-83-14
Description of the included normalisation normalisationDescription r [0,1] STMultiLang Short description of the included normalisation, if any. 3-19-83-15
"Normalisation data set(s)" that was/were used to calculate the normalised impact factors of this data set, if any. referenceToIncludedNormalisationDataSets r [0,n] GlobalReferenceType "Normalisation data set(s)" that was/were used to calculate the normalised impact factors of this data set, if any. 3-19-83-16
Weighting included? weighting r [0,1] boolean Indication whether or not a weighting-step was included in the resulting impact factors. 3-19-83-17
Usable Weighting data set(s), if not yet included referenceToUsableWeightingDataSets r [0,n] GlobalReferenceType "Weighting data set(s)", that can be used together with the impact factors of this data set. 3-19-83-18
Description of the included weighting weightingDescription r [0,1] STMultiLang Short description of the included weighting, if any. 3-19-83-19
Included Weighting data set referenceToIncludedWeightingDataSets r [0,n] GlobalReferenceType "Weighting data set" that was used to calculate the weighted impact factors of this data set, if any. 3-19-83-20
Data sources dataSources o [0,1] Data sources used for the model and the underlying substance and other data. 3-19-84
Data sources referenceToDataSource r [0,n] GlobalReferenceType "Source data set(s)" of the data source(s) used for the data set e.g. paper, questionnaire, monography etc. The main data sources e.g. for underlying substance properties are named, too. 3-19-84-219
Other content other o [0,1] May contain arbitrary content. 0
Completeness completeness r [0,1] 3-19-85
Completeness of impact coverage completenessImpactCoverage r [0,1] Perc Estimate of the completeness of coverage of impact(s), as identified in the fields "Impact category/ies" or - only for LCIA methodologies with Damage indicator or Combined single-point indicators - "Area(s) of Protection". Expressed by the quantitative extent of coverage of the scientifically recognized, impact. Note that this information is typically highly uncertain. 3-19-85-10
Number of basic inventory items covered inventoryItems r [0,1] Int6 Number of chemical substances/substance groups, chemical elements, or types covered, without considering variants by environmental emission or source compartment, geographical location, time, or other. 3-19-85-11
Validation validation o [0,1] Review information on LCIA method. 3-19-88
Type of review review m [1,n] Type of review that has been performed regarding independency and type of review process. 3-19-88-1
@type m TypeOfReviewValues
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).
Independent internal reviewReviewer(s)/verifier(s) have NOT been involved in collecting, modelling, or entering the data set information or inventory, have not commissioned or financed the work, and do not represent the process or product system (or quantiatitively relevant parts of it). But the reviewer(s) belong(s) to the organisation(s) or legally linked organisation(s) that have been involved in the above.
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).
Accredited third party 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). The reviewer(s)/verifier(s) are accredited by an accreditation body, that is independent of the reviewer(s)/verifier(s) and the scheme operator or standardisation party.
Independent review panelPanel of at least three independent internal or external reviewers/verfiers. Chairperson is independent external reviewer/verifier. Chairperson may invite interested parties affected by the conclusions drawn from the LCA, such as government agencies, non-governmental groups, competitors and affected industries. [Notes: "Independent": Reviewer(s)/verifier(s) have NOT been involved in collecting, modelling, or entering the data set information or inventory, have not commissioned or financed the work, and do not represent the process or product system (or quantiatitively relevant parts of it). "External": Reviewer(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).
Not reviewedThe data set was not / not yet reviewed.
Scope of review scope r [0,n] Scope 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. 1-3-20-82
Scope name @name r ScopeOfReviewValues
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.
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.
Unit process(es), black boxThe review is done on the level of process-chain(s) or plant level unit process(es). This covers horizontally averaged unit processes across different sites. Covers also those multi-functional unit processes, where the different co-products undergo different processing steps within the black box.
LCI results or Partly terminated systemThe LCI result or Partly terminated system is the level of review/verification.
LCIA resultsThe LCIA results of the LCI result or Partly terminated system data set are reviewed/verified, i.e. on level of Climate Change potential, Primary energy consumption, Ecosystem damage etc. [Note: see also definition for entry "LCIA results calculation".]
DocumentationEvidence collection by means of documentation (e.g. data set's meta data, background report)
Life cycle inventory methodsThe application of the LCI method(s) in accordance to the goal and scope have been reviewed. This covers data collection including dealing with missing data, data calculation/modelling principles (e.g. consequential or attributional or other/combination), and the application of the related modelling approaches such as allocation and system expansion etc. for the process / throughout the product system.
LCIA results calculationThe selection and application of the LCIA method(s) that have been used for calculation of the LCIA results have been reviewed. This especially refers to a correspondance of the elementary flows in the Inputs and Outputs of the product system with the once referenced by the applied LCIA method(s) regarding e.g. correct assignment, coverage/gaps, doublecounting, etc. [Note: See also definition for entry "LCIA results".]
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.
1-3-20-82-1
Method(s) of review method r [0,n] Validation method(s) used in the respective "Scope of review". 1-3-20-83
Method name @name r MethodOfReviewValues
Validation of data sourcesAnalysis of all data sources declared, checking their context-specific correct use as well as their relevance and quality.
Sample tests on calculationsValues in the inventory are re-calculated from the raw data, or other calculations are validated exemplarily, e.g. scaling, averaging, summing up, stochiometric calculations, formulas in the mathematical models, etc.
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.]
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.]
Cross-check with other sourceComparison with other, independent data and/or information sources (can be both database and literature).
Cross-check with other data setComparison with similar process or product system from the same or from other sources (can be both database and literature).
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.
Mass balanceThe mass balance 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.]
Compliance with legal limitsRegulated Inputs and Outputs e.g. emission data are validated for compliance with legal limits, typically after relating and scaling the data to the regulated processes/sites etc.
Compliance with ISO 14040 to 14044Methodological compliance with ISO 14040 to 14044 was checked by an LCA expert.
DocumentationEvidence collection by means of documentation (e.g. data set's meta data, background report)
Evidence collection by means of plant visits and/or interviewsInterviews and/or plant visits are performed to validate data and other informtion, tyically in case of inconsistencies, uncertainties, or doubts. People interviewed have detailed technical expertise on the analysed process(es).
Method name 1-3-20-83-1
Review details reviewDetails r [0,1] FTMultiLang Summary of the review. All the following items should be explicitly addressed: completeness and appropriateness of the model, geographical and temporal coverage and differentiation, correctness and precision of substance data or other underlying data; appropriateness and coherence of application of normalisation and/or weighting schemes, if included; correctness, appropriateness, comprehensibility, and completeness of the data set documentation; stakeholder aceptance of LCIA method. Optional: Comment of the reviewer on characterisation factors for single elementary flows or groups of elementary flows. Relevant restrictions to the review due to lack of transparency or documentation should be named. An overall quality statement may be included here. 3-19-88-10
Reviewer name and institution referenceToNameOfReviewerAndInstitution r [0,n] GlobalReferenceType "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. 1-3-20-87
Subsequent review comments otherReviewDetails o [0,1] FTMultiLang Further 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. 1-3-20-88
Complete review report referenceToCompleteReviewReport r [0,1] GlobalReferenceType "Source data set" of the complete review report. 1-3-20-89
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Compliance complianceDeclarations o [0,1] Statements on compliance of several data set aspects with compliance requirements as defined by the referenced compliance system (e.g. an EPD scheme, handbook of a national or international data network such as the ILCD, etc.). 3-19-90
compliance o [1,n]
Compliance system name referenceToComplianceSystem r [1,1] GlobalReferenceType "Source data set" of the "Compliance system" that is declared to be met by the data set. 1-3-22-90
Approval of overall compliance approvalOfOverallCompliance o [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Official 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". 1-3-22-95
Nomenclature compliance nomenclatureCompliance r [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Nomenclature compliance of this data set with the respective requirements set by the "compliance system" refered to. 1-3-22-92
Methodological compliance methodologicalCompliance r [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Methodological compliance of this data set with the respective requirements set by the "compliance system" refered to. 1-3-22-91
Review compliance reviewCompliance r [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Review/Verification compliance of this data set with the respective requirements set by the "compliance system" refered to. 1-3-22-93
Documentation compliance documentationCompliance r [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Documentation/Reporting compliance of this data set with the respective requirements set by the "compliance system" refered to. 1-3-22-94
Quality compliance qualityCompliance r [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
Quality compliance of this data set with the respective requirements set by the "compliance system" refered to. 1-3-22-96
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Administrative information administrativeInformation r [0,1] Information required for data set management and administration. 3-21
Commissioner and goal commissionerAndGoal o [0,1] Extract of the information items linked to goal and scope of LCIA method modeling. 3-21-92
Commissioner of data set referenceToCommissioner r [0,n] GlobalReferenceType "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. 1-5-24-96
Project project o [0,1] StringMultiLang Project 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. 1-5-24-97
Intended applications intendedApplications r [0,1] FTMultiLang Documentation 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. 1-5-24-98
Other content other o [0,1] May contain arbitrary content. 0
Data generator dataGenerator m [1,1] Expert(s), that compiled and modelled the data set as well as internal administrative information linked to the data generation activity. 3-21-94
Data set generator / modeller referenceToPersonOrEntityGeneratingTheDataSet r [1,n] GlobalReferenceType "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 documentation. 3-21-94-15
Other content other o [0,1] May contain arbitrary content. 0
Data entry by dataEntryBy r [1,1] Staff or entity, that documented the generated data set, entering the information into the database; plus administrative information linked to the data entry activity. 3-21-96
Time stamp (last saved) timeStamp r [0,1] dateTime Date and time stamp of data set generation, typically an automated entry ("last saved"). 1-5-28-104
Data set format(s) referenceToDataSetFormat r [0,n] GlobalReferenceType "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. 1-5-28-105
Reference to origin of data set referenceToConvertedOriginalDataSetFrom r [0,1] GlobalReferenceType "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 characterisation factors. This entry is required for converted data sets stemming originally from other LCA databases (e.g. when re-publishing LCIA characterisation factors from the database of the original impact method developer). [Note: Identically re-published data sets are identied in the field "Unchanged re-publication of:" in the section "Publication and Ownership".] 3-21-96-249
Data entry by: referenceToPersonOrEntityEnteringTheData o [0,1] GlobalReferenceType "Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information. 1-5-28-103
Official recommendation recommendationBy r [0,1] 3-21-96-250
Official recommendation of data set by governmental body: referenceToEntity r [0,n] GlobalReferenceType "Contact data set(s)" of the governmental body/ies that has/ve officially recommended this LCIA method data set and its impact factors for use within the documented scope. Eventually deviating (downgraded) recommendations for individual exchanges are documented in the "Inputs and Outputs" section of the data set. 3-21-96-251
Recommendation level of LCIA method data set level r [0,1] RecommendationLevelValues
Level IHighest recommendation level. See also field "Specific meaning of the recommendation level".
Level IISecond highest recommendation level. See also field "Specific meaning of the recommendation level".
Level IIIThird highest recommendation level. See also field "Specific meaning of the recommendation level".
InterimLevel between the third highest recommendation level and "not recommended". See also field "Specific meaning of the recommendation level".
Not recommendedNot recommended for use.
Level of recommendation given to this data set by the recommending governmental body. Note that the recommendation level of individual elementary flows can be different (lower) from the general level; this is documented as "Deviating recommendation" in the section "Characterisation factors" directly for each affected elementary flow. 3-21-96-252
Specific meaning of the recommendation level meaning r [0,1] FTMultiLang Specific meaning of the declared recommendation level of this LCIA method / methodology and the characterisation factors, as defined in the guidance document referenced in in the field "Compliance system" 3-21-96-253
Other content other o [0,1] May contain arbitrary content. 0
Publication and ownership publicationAndOwnership m [1,1] Information related to publication and version management of the data set including copyright and access restrictions. 3-21-98
Date of last revision dateOfLastRevision r [0,1] dateTime Date when the data set was revised for the last time, typically manually set. 1-5-30-113
Data set version dataSetVersion m [1,1] Version Version 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. 1-5-30-111
Preceding data set version referenceToPrecedingDataSetVersion o [0,n] GlobalReferenceType 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). 1-5-30-112
Permanent data set URI permanentDataSetURI r [0,1] anyURI URI (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.] 1-5-30-300
Workflow and publication status workflowAndPublicationStatus o [0,1] WorkflowAndPublicationStatusValues
Working draftData set is in preliminary status of on-going development.
Final draft for internal reviewData set is finished and ready for internal review.
Final draft for external reviewData set is ready for an external review (after a potential internal review and correction if required).
Data set finalised; unpublishedData set is finalised (with or without an internal and/or external review and correction if required), but it is not or not yet published.
Under revisionData set is under revision and the publication of the revised data set is foreseen.
WithdrawnData set has been withdrawn and must not be used anymore. For details contact the "Data set owner".
Data set finalised; subsystems publishedData set is finalised (with or without an internal and/or external review and correction if required), and sub-system(s) / included processes have been published.
Data set finalised; entirely publishedData set is finalised (with or without an internal and/or external review and correction if required), and was entirely published.
Workflow or publication status of data set. Details e.g. of foreseen publication dates should be provided on request by the "Data set owner". 1-5-30-110
Unchanged re-publication of: referenceToUnchangedRepublication o [0,1] GlobalReferenceType "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".] 1-5-30-114
Owner of data set referenceToOwnershipOfDataSet r [0,1] GlobalReferenceType "Contact data set" of the person or entity who owns this data set. (Note: this is not necessarily the publisher of the data set.) 1-5-30-115
Copyright? copyright r [0,1] boolean 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".] 1-5-30-116
Access and use restrictions accessRestrictions r [0,1] FTMultiLang Access 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. 1-5-30-118
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Characterisation factors characterisationFactors o [0,1] Flow / Exchanges list with corresponding impact factors according to the respective LCIA method. 3-23
Characterisation factor factor m [1,n] 3-23-100
Reference to flow data set referenceToFlowDataSet m [1,1] GlobalReferenceType Reference to "UUID of flow" of "Flow data set" to link the particular impact factor in the "LCIA data set" to the respective "Flow data set". Please be aware, that for location-specific LCIA methods, there may be multiple references to the same Flow data set. 3-23-100-260
Location of exchange location o [0,1] String Location where exchange of elementary flow occurs. Used only for those LCIA methods, that make use of such information. This information refers to the entry within the same field in the "Process data set". 3-23-100-261
Exchange direction exchangeDirection m [1,1] ExchangeDirectionValues
InputFlow in input list of the process, e.g. resources from nature or energy carriers, or commodities and services entering from the technosphere. (In case the flow has an negative "resulting amount" value this is equivalent to belonging to the output list of the process.)
OutputFlow in output list of the process, e.g. emissions to nature, or products and waste going to the technosphere into another process. (In case the flow has a negative "resulting amount" value this is equivalent to belonging to the input list of the process.)
Direction of exchange; this information refers to the entry within the same field in the "Process data set". 3-23-100-262
Mean value ( of LCIA characterisation factor) meanValue m [1,1] Real Mean value of the impact characterisation factor for the exchange identified by the fields "Reference to flow data set", "Exchange direction" and "Location of direction". It is recommended to report only significant digits of the amount. ! If for an elementary flow its relevant contribution to this LCIA theme is known by state-of-the-art scientific knowledge, but no impact factor is provided in the LCIA method, the flow should nevertheless be referrenced and the mean value to be entered is "0"! 3-23-100-263
Minimum value minimumValue o [0,1] Real Minimum value of the characterisation factor for the exchange in case uncertainty distribution is uniform or triangular. 3-23-100-264
Maximum value maximumValue o [0,1] Real Maximum value of the characterisation factor for the exchange in case uncertainty distribution is uniform or triangular. 3-23-100-265
Uncertainty distribution type uncertaintyDistributionType o [0,1] UncertaintyDistributionTypeValues
undefinedProbability distribution information not available.
log-normalProbability distribution of any random parameter whose logarithm is normally distributed.
normalProbability distribution of any random parameter whose value is normally distributed around the mean of zero.
triangularProbability distribution of any random parameter between minimum value and maximum value with the highest probability at the average value of minimum plus maximum value. Linear change of probability between minimum, maximum and average value.
uniformContinuous uniform probability distribution between minimum value and maximum value and "0" probability beyond these.
Defines the kind of uncertainty distribution that is valid for this particular object or parameter. 3-23-100-266
Relative StdDev in % relativeStandardDeviation95In o [0,1] Perc 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.] 3-23-100-267
Data derivation type / status dataDerivationTypeStatus o [0,1] DataDerivationTypeStatusValues
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.
CalculatedStochiometric or other theoretical relations were used to calculate the amount of this flow. [Note: Calculations that include quantiatively relevant expert judgement are of the type "Expert judgement".]
EstimatedExpert judgement was used to derive the quantity of this flow. This includes the unmodified or corrected use of data from similar processes / technologies, times, or locations, as well as calculated values where the formulas/parameters include quantitatively relevant expert judgement.
Unknown derivationData derivation type information fully or at least for quantiatively relevant parts unavailable.
Missing importantIndicates missing amount information for environmentally directly (elementary flow) or indirectly (product or waste flow) important Input or Output. As the "Mean amount" the value "0" is entered.
Missing unimportantIndicates missing amount information for an however environmentally directly (elementary flow) or indirectly (product or waste flow) NOT relevant Input or Output. As the "Mean amount" the value "0" is entered.
Identifies the way by which the individual Input / Output amount was derived (e.g. measured, estimated etc.), respectively the status and relevancy of missing data. 3-23-100-269
Deviating recommendation deviatingRecommendation m [0,1] RecommendationLevelValues
Level IHighest recommendation level. See also field "Specific meaning of the recommendation level".
Level IISecond highest recommendation level. See also field "Specific meaning of the recommendation level".
Level IIIThird highest recommendation level. See also field "Specific meaning of the recommendation level".
InterimLevel between the third highest recommendation level and "not recommended". See also field "Specific meaning of the recommendation level".
Not recommendedNot recommended for use.
Deviating (downgraded) recommendation level for this exchange, in reference to the recommendation level of the LCIA method data set as a whole (see field "Official recommendation of data set by governmental body:"). 3-23-100-268
Reference to data source(s) referencesToDataSource o [0,1] Reference to "UUID of source"(s) in the "Source data set" of data source(s) used for modelling the value of this single LCIA factor e.g. a specific paper, questionnaire, monography etc. If, as typical, more than one data source was used, more than one source can be referenced. 3-23-100-270
Reference to data source(s) referenceToDataSource o [0,1] GlobalReferenceType Reference to "UUID of source"(s) in the "Source data set" of data source(s) used for modelling the value of this single LCIA factor e.g. a specific paper, questionnaire, monography etc. If, as typical, more than one data source was used, more than one source can be referenced. 3-23-100-270
Other content other o [0,1] May contain arbitrary content. 0
General comment generalComment o [0,1] StringMultiLang General 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.) 3-23-100-272
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0