You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: specs/index.bs
+64-23
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ This specifcation does not cover the following topics or aspects as they are cov
37
37
6. How to perform data audits and verification
38
38
7. Modes of transport cable car and pipelines. Although these are acknowledged in both the GLEC Framework and ISO14083, they are left out of scope of the current project, and will be incorporated in future versions of these technical specifications.
39
39
8. Book and claim methods to track the environmental attributes of low emission transport solutions separately from the physical delivery. This will be incorporated in later versions of these technical specifications.
40
-
9. Variables for detailed GHG emissions modelling, as described in [[!ISO14083]], Section 13.4.3 and Annex M. The current data model is considered a key enabler for primary data collection, where its main focus lays. The basic use of modelled and default data is also supported, but detailed parameters for modelling are not in focus.
40
+
9. Variables for detailed GHG emissions modelling, as described in [[!ISO14083]], Section 13.4.3 and Annex M. The current data model is considered a key enabler for primary data collection, where its main focus lays. The basic use of modelled and default data is also supported, but detailed parameters for modelling are not in focus.
41
41
10. Refrigerant emissions, due to leakage of refrigerants used by vehicles and hubs, as described in [[!ISO14083]], Annex I. This will be incorporated in later versions of these technical specifications.
42
42
43
43
Advisement: The current technical specifications are undergoing continuous refinement as part of the ongoing iLEAP project. Significant modifications may be introduced as the project progresses. Certain subsections, such as Hub Operation Category, intentionally remain blank and will be filled in during subsequent stages of the iLEAP project.
@@ -738,11 +738,34 @@ The Data Type <{TCE}> has the following properties:
738
738
<td>Identification no of a specific vessel conducting a specific route.
739
739
740
740
<tr>
741
-
<td><dfn>Incoterms</dfn>
742
-
<td>Categorical
741
+
<td><dfn>incoterms</dfn>
742
+
<td>String
743
743
<td>O
744
744
<td>
745
-
Incoterms are a set of internationally recognized rules defining the responsbilities of sellers and buyer in relation to the logistics activities between the parties. Unterstanding who pays for the shipment can help identify the SCope3 Category in which each party has to report their emissions. This variable can take the values: EXW, FCA, CPT, CIP, DAP, DPU, DDP, FAS, FOB, CFR, CIF
745
+
Incoterms are a set of internationally recognized rules defining the responsbilities of sellers and buyer in relation to the logistics activities between the parties. Unterstanding who pays for the shipment can help identify the Scope3 Category in which each party has to report their emissions.
746
+
747
+
If defined, the value of this property MUST be one of the following:
748
+
: EXW
749
+
750
+
: FCA
751
+
752
+
: CPT
753
+
754
+
: CIP
755
+
756
+
: DAP
757
+
758
+
: DPU
759
+
760
+
: DDP
761
+
762
+
: FAS
763
+
764
+
: FOB
765
+
766
+
: CFR
767
+
768
+
: CIF
746
769
747
770
<tr>
748
771
<td><dfn>co2eWTW</dfn> : [=Decimal=]
@@ -875,12 +898,12 @@ The Data Type <{TOC}> has the following properties:
875
898
<td>String
876
899
<td>O
877
900
<td>
878
-
Temperature control status of the TOC.
901
+
Temperature control status of the TOC.
879
902
880
903
If defined, the value of this property MUST be set to one of the following values:
881
904
- `ambient`: for non-temperature controlled freight
882
905
- `refrigerated`: for refrigerated freight
883
-
- `mixed`: for TOCs comprising the handling of both ambient and refrigerated freight
906
+
- `mixed`: for TOCs comprising the handling of both ambient and refrigerated freight
884
907
885
908
<tr>
886
909
<td><dfn>energyCarriers</dfn>
@@ -923,35 +946,54 @@ The Data Type <{TOC}> has the following properties:
923
946
Indicates the freight transport activity unit at the denominator of the <{TOC/co2eIntensityWTW}>. At the TOC level, preferred throughputs are tkm, or TEUkm for sea and inland waterways. Alternative units (e.g. number of items, kg, etc.) are possible.
924
947
925
948
<tr>
926
-
<td><dfn>ltlFTL</dfn>
927
-
<td>Categorical
949
+
<td><dfn>truckLoadingSequence</dfn>
950
+
<td>String
928
951
<td>O
929
952
<td>
930
-
Only for road. LTL indicates less than truck load. FTL indicates full truck load, as defined in the [[!GLEC]] Framework. The sequence of pick-up & drop-off for LTL is PU-PU-DO-DO, and for FTL is PU-DO-PU-DO.
931
-
This variable can take the values: LTL, FTL.
953
+
Only for road. If defined, the value MUST be one of the following:
954
+
955
+
: LTL
956
+
:: For less than truck load, as defined in the [[!GLEC]] Framework. The sequence of pick-up & drop-off is PU-PU-DO-DO
957
+
: FTL
958
+
:: For full truck load, as defined in the [[!GLEC]] Framework. The sequence of pick-up & drop-off is PU-DO-PU-DO
932
959
933
960
<tr>
934
961
<td><dfn>shippingOptionAir</dfn>
935
-
<td>Categorical
962
+
<td>String
936
963
<td>O
937
964
<td>
938
-
Only for air transport. Indicates if the movement of freight is combined with passanger transport (belly freight), or a dedicated aircraft for the movement of freight (freighter).
939
-
This variable can take the values: belly freight, freighter.
965
+
Only for air transport. Indicates if the movement of freight is combined with passanger transport (belly freight), or a dedicated aircraft for the movement of freight (freighter).
966
+
967
+
If defined, the value MUST be one of the following:
968
+
: belly freight
969
+
:: For freight combined with passanger transport
970
+
: freighter
971
+
:: For freight moved by a dedicated aircraft
940
972
<tr>
941
973
<td><dfn>flightLength</dfn>
942
-
<td>Categorical
974
+
<td>String
943
975
<td>O
944
976
<td>
945
-
Only for air transport. Indicates if the distance travelled is lower or greater than 1500 km, as defined in the [[!GLEC]] Framework.
946
-
This variable can take the values: short-haul, long-haul.
977
+
Only for air transport. Indicates if the distance travelled is smaller or greater than 1500 km, as defined in the [[!GLEC]] Framework.
978
+
979
+
If defined, the value MUST be one of the following:
980
+
: short-haul
981
+
:: For distances smaller than 1500 km
982
+
: long-haul
983
+
:: For distances greater than 1500 km
984
+
947
985
<tr>
948
986
<td><dfn>electAccountingMethod</dfn>
949
-
<td>Categorical
987
+
<td>String
950
988
<td>O
951
989
<td>
952
-
Only applicable to electricity emissions. Indicates the accounting method chosen for electricity emissions accounting. Location-based is applicable when average grid mix factors are used, and market-based when low carbon electricity or its attributes are purchased and accounted for the defined TOC.
953
-
This variable can take the values: location-based, market-based
954
-
990
+
Only applicable to electricity emissions. Indicates the accounting method chosen for electricity emissions accounting.
991
+
992
+
If defined, the value MUST be one of the following:
993
+
: location-based
994
+
:: For average grid mix factors
995
+
: market-based
996
+
:: For low carbon electricity or its attributes purchased and accounted for the defined TOC
955
997
<tr>
956
998
<td><dfn>glecDataQualityIndex</dfn> : [0..4]
957
999
<td>Number
@@ -1003,12 +1045,12 @@ The Data Type <{HOC}> contains [=HOC=] data. It is referenced in a [=Transport C
1003
1045
<td><dfn>isVerified</dfn>
1004
1046
<td>Boolean
1005
1047
<td>M
1006
-
<td>Indicates that the truthfulness of the GHG emissions value and related variables has been confirmed by a Validation and Verification Body (VVB), as declared in a Verification Statement. The VVB must follow a widely recognized standard for their GHG verification services (example: the ISO or ISAE standards). Verification should use ISO 14083 as audit criteria.
1048
+
<td>Indicates that the truthfulness of the GHG emissions value and related variables has been confirmed by a Validation and Verification Body (VVB), as declared in a Verification Statement. The VVB must follow a widely recognized standard for their GHG verification services (example: the ISO or ISAE standards). Verification should use ISO 14083 as audit criteria.
1007
1049
<tr>
1008
1050
<td><dfn>isAccredited</dfn>
1009
1051
<td>Boolean
1010
1052
<td>M
1011
-
<td>(=certified)Indicates that the calculation methodology has been evaluated as compliant with ISO 14083:2023, as declared in an Accreditation (=Certification) certificate.
1053
+
<td>(=certified)Indicates that the calculation methodology has been evaluated as compliant with ISO 14083:2023, as declared in an Accreditation (=Certification) certificate.
1012
1054
<tr>
1013
1055
<td><dfn>hubType</dfn>
1014
1056
<td>{{HubType}}
@@ -1064,7 +1106,6 @@ The Data Type <{HOC}> contains [=HOC=] data. It is referenced in a [=Transport C
1064
1106
<td>M
1065
1107
<td>
1066
1108
Indicates the freight transport activity unit at the denominator of the <{HOC/co2eIntensityWTW}>. At the HOC level, preferred throughputs are tonnes leaving the hub, or TEU leaving the hub for sea and inland waterways. Alternative units (e.g. number of items, etc.) are possible but not recommended.
0 commit comments