Show: Field nameElement/attribute nameRequirementOccurrencesData typeDefinitioneDoc ID

# ILCD Format 1.1 Documentation - Life cycle model data set

Field name | Element/attribute name | Requ. | Occ. | Data type | Definition | eDoc ID
--- | --- | --- | --- | --- | --- | ---
Life cycle model data set | lifeCycleModelDataSet | m | [1,1] |  | System of interconnected processes that jointly represent the full or partial life cycle of a product system, with the final process step ('Reference process instance') being referenced from this life cycle model data set, which connects and stepwise scales all other process instances via the connecting product and waste exchanges. | 7-d1e4
Schema version | @version | m |  | SchemaVersion | Version of the ILCD data format schema. | 7-d1e420
Locations list | @locations | m |  | String | Contains reference to used "location" table for this data set. | 7-d1e421
Life cycle model information | lifeCycleModelInformation | m | [1,1] |  | This section comprises the following sub-sections: 1) "Key data set information", 2) "Quantitative reference", 3) "Technology". | 7-d1e20
Key data set information | dataSetInformation | m | [1,1] |  | General data set information, to identify the life cycle model, document a general comment about it, and to reference resulting aggregated process data sets that are based on this ife cycle model and to reference a potential background report. | 7-d1e21
UUID of Life Cycle Model 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. | 7
Name | name | r | [0,1] |  | General descriptive, specifying, structured name of the Life cycle model data set. Note: Ensure proper name structuring and observe restriction to 100 characters for each of the four name fields. | 7-d1e75
Base name | baseName | r | [0,1] | StringMultiLang | General descriptive name of the life cycle model and/or its main good(s), service(s) and/or functions delivered. | 7-d1e245
Treatment, standards, routes | treatmentStandardsRoutes | r | [0,1] | StringMultiLang | Specifying information on the good, service, or function delivered by the life cycle model in technical term(s): treatment received, standard fulfilled, product quality, use information, production route name, educt name, primary / secondary etc. Separated by commata. | 7-d1e246
Mix and location types | mixAndLocationTypes | r | [0,1] | StringMultiLang | Specifying information on the good, service, or function, whether being a production mix or consumption mix, location type of availability (such as e.g. "to consumer" or "at plant"). Separated by commata. May include information of excluded life cycle stages, if any. | 7-d1e247
Quantitative product or process properties | functionalUnitFlowProperties | r | [0,1] | StringMultiLang | Further, quantitative specifying information on the good, service or function 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 to be documented exclusively in the "Flow data set" of the reference flow of this life cycle model.) | 7-d1e248
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
| name | o | [0,1] | StringMultiLang |  |
Classification information | classificationInformation | r | [0,1] |  | Hierarchical or flat classification of the good, service or function that is provided by this life cycle model; typically used to structure database contents in LCA software, among other purposes. (Note: This entry is NOT required for the identification of a Life cycle model, but it should nevertheless be avoided to use identical names for Life cycle model data sets in the same class. The ILCD classifications are defined in the ILCDClassifications.xml file, for common use.) | 7-d1e31
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
Resulting (partly) aggregated process data set | referenceToResultingProcess | o | [0,n] | GlobalReferenceType | Reference to the LCI result or partly terminated system process data set(s) that is/are generated from this model. | 7-d1e27
General comment | generalComment | o | [0,1] | FTMultiLang | General information about the data set. | 7
Data set report, background info | referenceToExternalDocumentation | o | [0,n] | GlobalReferenceType | "Source data set(s)" of detailed LCI or LCA study or other 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. on the level of the life cycle model. (Note: can indirectly reference to electronic and online files.) | 7-d1e23
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Quantitative reference | quantitativeReference | r | [0,1] |  | This section names the quantitative reference of this data set, i.e. the reference to which the inputs and outputs of all process instances of the life cycle model quantitatively relate. | 7-d1e32
Reference process instance | referenceToReferenceProcess | r | [0,1] | integer | Process instance that scales the life cycle model and thereby all directly and indirectly connected process instances of the model; it is often a process instance at the "end" of the life cycle model chain, or the process that provides the delivered good, service or function of the model. | 7-d1e33
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Technological representativeness | technology | r | [0,1] |  | Provides information about the technological representativeness of the data set. | 7-d1e35
Groups for declarations | groupDeclarations | r | [0,1] |  | Section to define groups to which process instances can declare to belong to, in the context of this Life cycle model data set. Groups are user-defined and could be e.g. life cycle stages, foreground/background, ... | 7-d1e36
Groups | group | r | [0,n] |  | Definition for each group. | 7-d1e37
Group id | @id | m |  | integer | Data set internal id of the group. | 7-d1e466
Group name | groupName | r | [0,1] | StringMultiLang | Name of the group. | 7-d1e41
Included process data sets | processes | r | [0,1] |  | "Process data set(s)" included in this life cycle model as separate data set(s). | 7-d1e42
Process instances of this process data set | processInstance | r | [0,n] |  | Instances (occurrences) of the same process data set in this life cycle model. Each process data set may occur in different places within the model, with different parameter settings and connected to different other process instances. | 7-d1e43
ID of the process instance | @dataSetInternalID | m |  | integer | Data set internal id of the process instance. Used to refer to individual instances in the other sections of the life cyce model data set. | 7-d1e480
Multiplication factor | @multiplicationFactor | m |  | double | The multiplication factor corresponds to the amount of output product from the process instance that is needed over the full life cycle. In practice, the Life Cycle Inventory of a specific process instance shall be multiplied by the multiplication factor to calculate the exact amount needed over the full life cycle. | 7-d1e481
Reference to process data set | referenceToProcess | r | [0,1] | GlobalReferenceType | Reference to the process data set and (optional) identifying its version, that is included in the eILCD archive of the Life cycle model and/or accessible at a remote location, i.e. an URI or URL. | 7-d1e44
Scaling factor of process instance | scalingFactor | o | [0,1] | Real | A multiplicative scaling factor for the entire inventory of this process instance, used e.g. to scale the "Reference process" to the aimed-at amount of product (and thereby indirectly the entire inventory of the life cycle model). Note: Care is to be taken that models are not over- or under-specified - note that each process instance scaling is reducing the model's degree of freedom by one. | 7-d1e48
Groups of process instance | groups | r | [0,1] |  | Group(s) to which this process instance belongs. | 7-d1e49
Belongs to group | memberOf | r | [0,n] |  | Refers to one user-definable group, to which this process instance belongs. | 7-d1e50
ID of group | @groupId | m |  | integer | Data set internal ID of the group. | 7-d1e487
Parameter settings of process instance | parameters | o | [0,1] |  | Set of parameters of this process instance with parameter values (changed or unchanged from those in the underlying process data set). | 7-d1e51
Parameter name and value | parameter | o | [0,n] | Real | Value of the parameter. | 7-d1e53
Parameter name | @name | m |  | MatV | Name of free parameter | 7-d1e496
Process instance connections | connections | r | [0,1] |  | Connection information among process instances, via connecting product or waste flow exchanges. | 7-d1e54
Connecting output exchange | outputExchange | r | [0,n] |  | Reference to process data set UUID of one of the connecting output product or waste flow exchanges of this process instance. I.e. which (flow) exchange on output side of this process instance is to be connected to another process instance's input product or waste (flow) exchange? | 7-d1e55
Dominant exchange | @dominant | o |  | boolean | If the connected exchanges are based on different flow data sets, one of these can be marked as dominant. Dominant means that in cases where the connection itself carries properties (e.g. a flow name that may be used in graphical model display), the properties of the dominant flow object are used. | 7-d1e413
UUID of exchange | @flowUUID | m |  |  | UUID of the connected flow exchange in the input of the downstream process instance. | 7-d1e506
Connected downstream process instance | downstreamProcess | r | [0,n] |  | Process instance that is connected downstream with this process instance, with its connected input product or waste (flow) exchange internal ID, the flow UUID and optionally the exchange's "location" (if any). Finally, the dominant flow exchange may be identified, where two different flow data sets are connected, in support e.g. of graphical model display. | 7-d1e56
ID of connected process instance | @id | m |  | integer | Internal ID of the process instance in this model which is to be connected to this output exchange. | 7-d1e511
UUID of exchange | @flowUUID | m |  |  | UUID of the connecting flow exchange in the output of the upstream process instance. | 7-d1e510
Exchange location | @location | o |  | string | Location, e.g. country code, of the connected flow exchange in downstream process, if any. | 7-d1e512
Dominant exchange | @dominant | o |  | boolean | If the connected exchanges are based on different flow data sets, one of these can be marked as dominant. Dominant means that in cases where the connection itself carries properties (e.g. a flow name that may be used in graphical model display), the properties of the dominant flow object are used. | 7-d1e413
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Life cycle model diagramm(s) or screenshot(s) | referenceToDiagram | o | [0,n] | GlobalReferenceType | "Source data set" of the flow diagramm(s), and/or screenshot(s) of the life cycle model represented by this data set. For clearer illustration and documentation of the model. Note: The source data set references the actual picture as jpd or png file or as e.g. pdf file with several pictures. | 7-d1e57
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Modelling and validation | modellingAndValidation | r | [1,1] |  | This section covers the following sub-sections: 1) "Data sources, treatment and representativeness", 2) "Validation", and 3) "Compliance". | 7-d1e22
Data sources, treatment, and representativeness | dataSourcesTreatmentEtc | r | [0,1] |  | Data selection, completeness, and treatment principles and procedures, data sources and market coverage information. | 7-d1e61
Use advice for data set | useAdviceForDataSet | r | [0,1] | FTMultiLang | Specific methodological advice for data set users that requires attention. E.g. on inclusion/exclusion of whole life cycle stages, specific use phase behavior to be modelled, and other methodological advices. | 7-d1e62
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Validation | validation | r | [0,1] |  | Review / validation information on data set. | 7-d1e63
Review(s) | review | r | [0,n] |  | Review information on this life cycle model data set | 7-d1e64
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 declaration(s) | complianceDeclarations | r | [0,n] |  | One or more declarations of compliance to selected standards, schemes and other references, e.g. ISO 14040, ISO 14044, ILCD, EF, EN 15804, ... | 7-d1e65
Compliance system name | compliance | r | [0,1] |  | "Source data set" of the "Compliance system" that is declared to be met by the data set. | 7-d1e66
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 | [1,1] |  | Information on data set management, ownership, use rights, and administration | 7-d1e68
Commissioner and goal | commissionerAndGoal | r | [0,1] |  | Basic information about goal and scope of the data set. |
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 set generator / modeller | dataGenerator | r | [0,1] |  | "Contact data set" of the person(s), working group(s), organisation(s) or database network, that generated the data set, i.e. being technically responsible for its correctness regarding methods, inventory, and documentative information. | 7-d1e69
Data set generator / modeller | referenceToPersonOrEntityGeneratingTheDataSet | r | [0,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 documentative information. | 1-5-26-99
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Data entry by: | dataEntryBy | o | [0,1] |  | "Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information. | 7-d1e70
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
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
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0
Publication and ownership | publicationAndOwnership | r | [0,1] |  | Information related to publication and version management of the data set including copyright and access restrictions. | 7-d1e71
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
Owner of data set | referenceToOwnershipOfDataSet | r | [0,1] | GlobalReferenceType | Quality compliance of this data set with the respective requirements set by the "compliance system" refered to. | 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
Entities or persons with exclusive access to this data set | referenceToEntitiesWithExclusiveAccess | o | [0,n] | GlobalReferenceType | "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".] | 1-5-30-117
License type | licenseType | r | [0,1] | LicenseTypeValues Free of charge for all users and usesThis data set can be freely accessed and used by all user types and for all uses, including for commercial purposes Free of charge for some user types or use typesThis data set can be accessed free of charge for certain user types, such as academic institutions, students, public administration/government, etc., or for certain types of uses, e.g. not-for-profit. Details and license conditions are to be obtained from the "Data set owner" or electronically via the "Permanent URI", if implemented by data owner. Also see "Access and use restrictions". Free of charge for members onlyData set is accessible free of charge only for members. Membership itself must be for free, while not all user types may be able to become member. Membership conditions are to be obtained from the "Data set owner" or electronically via the "Permanent URI", if implemented by data owner. Also see "Access and use restrictions". License feeData set is accessible for a license fee. This can be a fee per data set, for a group of data sets, a whole database, or for obtaining a membership to get access to the data. Details and license conditions are to be obtained from the "Data set owner" or electronically via the "Permanent URI", if implemented by data owner. Also see "Access and use restrictions". OtherAnother LCI method approach is used. This is named in "Deviations from LCI method approaches / explanations" where also additional information is given. | Type of license that applies to the access and use of this data set. | 1-5-30-119
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
Other content | other | o | [0,1] |  | May contain arbitrary content. | 0