Commission Regulation (EC) No 2216/2004 of 21 December 2004 for a standardised and secured system of registries pursuant to Directive 2003/87/EC of the European Parliament and of the Council and Decision No 280/2004/EC of the European Parliament and of the CouncilText with EEA relevance
Modified by
- Commission Regulation (EC) No 916/2007of 31 July 2007amending Regulation (EC) No 2216/2004 for a standardised and secured system of registries pursuant to Directive 2003/87/EC of the European Parliament and of the Council and Decision No 280/2004/EC of the European Parliament and of the Council(Text with EEA relevance), 32007R0916, August 1, 2007
- Commission Regulation (EC) No 994/2008of 8 October 2008for a standardised and secured system of registries pursuant to Directive 2003/87/EC of the European Parliament and of the Council and Decision No 280/2004/EC of the European Parliament and of the Council(Text with EEA relevance), 32008R0994, October 11, 2008
- Commission Regulation (EU) No 920/2010of 7 October 2010for a standardised and secured system of registries pursuant to Directive 2003/87/EC of the European Parliament and of the Council and Decision No 280/2004/EC of the European Parliament and of the Council(Text with EEA relevance), 32010R0920, October 14, 2010
- Commission Regulation (EU) No 1193/2011of 18 November 2011establishing a Union Registry for the trading period commencing on 1 January 2013, and subsequent trading periods, of the Union emissions trading scheme pursuant to Directive 2003/87/EC of the European Parliament and of the Council and Decision No 280/2004/EC of the European Parliament and of the Council and amending Commission Regulations (EC) No 2216/2004 and (EU) No 920/2010(Text with EEA relevance), 32011R1193, November 29, 2011
(a) "2005-2007 period" means the period from 1 January 2005 to31 December 2007 as referred to in Article 11(1) of Directive 2003/87/EC;(b) "2008-2012 period and subsequent five-year periods" means the period from 1 January 2008 to31 December 2012 plus consecutive five-year periods as referred to in Article 11(2) of Directive 2003/87/EC;(c) "account holder" means a person who holds an account in the registries system; (d) "assigned amount" means the amount of greenhouse gas emissions in tonnes of carbon dioxide equivalent calculated in accordance with the emission levels determined pursuant to Article 7 of Decision No 280/2004/EC; (e) "assigned amount unit" (AAU) means a unit issued pursuant to Article 7(3) of Decision No 280/2004/EC or by a Party to the Kyoto Protocol; (f) "authorised representative" means a natural person authorised to represent the Central Administrator, a registry administrator, an account holder or a verifier pursuant to Article 23; (g) "CDM registry" means the clean development mechanism registry established, operated and maintained by the executive board of the clean development mechanism pursuant to Article 12 of the Kyoto Protocol and the decisions adopted pursuant to the UNFCCC or the Kyoto Protocol; (h) "Central Administrator" means the person designated by the Commission pursuant to Article 20 of Directive 2003/87/EC to operate and maintain the Community independent transaction log; (i) "Community independent transaction log" means the independent transaction log provided for in Article 20(1) of Directive 2003/87/EC for the purpose of recording the issue, transfer and cancellation of allowances, and established, operated and maintained in accordance with Article 5; (j) "competent authority" means the authority or authorities designated by a Member State pursuant to Article 18 of Directive 2003/87/EC; (k) "discrepancy" means an irregularity detected by the Community independent transaction log or UNFCCC independent transaction log whereby the proposed process does not conform to the requirements specified under Directive 2003/87/EC as elaborated in this Regulation and the requirements elaborated pursuant to the UNFCCC or the Kyoto Protocol; (l) "force majeure allowance" means a force majeure allowance issued pursuant to Article 29 of Directive 2003/87/EC; (m) "inconsistency" means an irregularity detected by the Community independent transaction log or UNFCCC independent transaction log whereby the information regarding allowances, accounts or Kyoto units provided by a registry as part of the periodic reconciliation process differs from the information contained in either independent transaction log; (n) "Kyoto unit" means an AAU, RMU, ERU or CER; (o) "process" means any one of the processes referred to in Article 32; (p) "registry" means a registry established, operated and maintained pursuant to Article 6 of Decision No 280/2004/EC, incorporating a registry established pursuant to Article 19 of Directive 2003/87/EC.Special provisions are applicable to registries referred to in Article 63a; (q) "registry administrator" means the competent authority, persons or person, designated by the Member State or the Commission, that operates and maintains a registry in accordance with the requirements of Directive 2003/87/EC, Decision No 280/2004/EC and this Regulation; (r) "removal unit" (RMU) means a unit issued pursuant to Article 3 of the Kyoto Protocol; (s) "temporary CER" (tCER) is a CER issued for an afforestation or reforestation project activity under the CDM which, subject to the decisions adopted pursuant to the UNFCCC or the Kyoto Protocol, expires at the end of the commitment period following the one during which it was issued; (t) "long-term CER" (lCER) is a CER issued for an afforestation or reforestation project activity under the CDM which, subject to the decisions adopted pursuant to the UNFCCC or the Kyoto Protocol, expires at the end of the crediting period of the afforestation or reforestation project activity under the CDM for which it was issued; (u) "third country registry" means a registry established, operated and maintained by a country listed in Annex B to the Kyoto Protocol which has ratified the Kyoto Protocol and is not a Member State; (v) "transaction" means the issue, transfer, acquisition, surrender, cancellation and replacement of allowances and the issue, transfer, acquisition, cancellation and retirement of ERUs, CERs, AAUs and RMUs and carry-over of ERUs, CERs and AAUs; (w) "UNFCCC independent transaction log" means the independent transaction log established, operated and maintained by the Secretariat of the United Nations Framework Convention on Climate Change; (x) "verifier" means a competent, independent, accredited verification body with responsibility for performing and reporting on the verification process, in accordance with the detailed requirements established by the Member State pursuant to Annex V of Directive 2003/87/EC; (y) "year" means a calendar year, defined according to Greenwich Mean Time.
(a) all registries have successfully completed the UNFCCC initialisation procedure; and (b) the Community independent transaction log and the UNFCCC independent transaction log are able to provide the necessary functionality and to link to each other.
(a) the law enforcement and tax authorities of a Member State; (b) the European Anti-fraud Office of the European Commission; (c) the European Court of Auditors; (d) Eurojust; (e) the competent authorities referred to in Article 11 of Directive 2003/6/EC and in Article 37(1) of Directive 2005/60/EC; (f) the competent national supervisory authorities; (g) registry administrators of Member States and the competent authorities referred to in Article 18 of Directive 2003/87/EC.
(a) deleting from the national allocation plan table and replacing with a null any allowances in the national allocation plan table that were not yet allocated to the installation until the proposed national allocation plan table change; (b) adding an equivalent number of allowances to the part of the national allocation plan table representing the quantity of allowances not allocated to existing installations.
(a) the notification was posted within the deadline indicated in the first subparagraph of paragraph 2; (b) the proposed manual intervention only reverses the effects of the transaction considered to have been initiated unintentionally or erroneously and does not involve reversing the effects of later transactions involving the same allowances or Kyoto units.
(a) within its registry as requested by an account holder in accordance with the internal transfer process set out in Annex IX; (b) between registries as requested by an account holder for allowances issued for the 2005-2007 period in accordance with the external transfer (2005-2007) process set out in Annex IX; and (c) between registries as requested by an account holder for allowances issued for the 2008-2012 period and subsequent five-year periods and Kyoto units in accordance with the external transfer (2008-2012 onwards) process set out in Annex IX.
(a) transfer a specified number of allowances for a specified year from the relevant operator holding account into the Party holding account of that registry; (b) enter the number of transferred allowances into the section of the surrendered allowance table designated for that installation for that year.
(a) transfer a specified number of CERs or ERUs for a specified year from the relevant operator holding account into the Party holding account of that registry; (b) enter the number of transferred CERs and ERUs into the section of the surrendered allowance table designated for that installation for that year.
(a) for the years 2005, 2006 and 2007, the compliance status figure for that installation and for each year by calculating the sum of all allowances surrendered pursuant to Articles 52, 53 and 54 for the 2005 to 2007 period minus the sum of all verified emissions in the current five-year period up to and including the current year; (b) for the year 2008 and each year thereafter, the compliance status figure for that installation and for each year by calculating the sum of all allowances surrendered pursuant to Articles 52, 53 and 54 for the current period minus the sum of all verified emissions from the year 2008 up to and including the current year, plus a correction factor.
(a) converting a number of allowances issued for that five-year period and held in the Party holding account, equal to the total number of allowances surrendered pursuant to Article 52 as entered in the surrendered allowance table since 1 January of the first year of the relevant period until 31 May of the subsequent year and since 1 June of the preceding year until 31 May of each of the subsequent years, into AAUs by removing the allowance element from the unique unit identification code of each such AAU comprising the elements set out in Annex VI in accordance with the "conversion of surrendered allowances for retirement (2008 to 2012 onwards)" process set out in Annex IX; and (b) transferring a number of Kyoto units of the type specified by the competent authority, with the exception of Kyoto units resulting from projects referred to in Article 11a(3) of Directive 2003/87/EC, equal to the total number of allowances surrendered pursuant to Articles 52 and 53 as entered in the surrendered allowance table since 1 January of the first year of the relevant period until 31 May of the subsequent year and from 1 June of the preceding year until 31 May of each of the subsequent years, from the Party holding account to the retirement account for the relevant period in accordance with the "retirement of surrendered allowances (2008 to 2012 onwards)" process set out in Annex IX.
(a) transferring a number of allowances, equal to the number of allowances held in the registry issued for the 2005 to 2007 period by any registry minus the number of allowances at the moment of cancellation and replacement surrendered pursuant to Articles 52 and 54 since the moment of retirement on 30 June of the preceding year, from their holding accounts referred to in Article 11(1) and (2) to the cancellation account for the 2005 to 2007 period; (b) if instructed to do so by the competent authority, issuing a number of replacement allowances specified by the competent authority by converting an equal number of AAUs issued for the 2008-2012 period held in the Party holding account into allowances by adding the allowance element to the unique unit identification code of each such AAU comprising the elements set out in Annex VI; (c) transferring any such replacement allowances referred to in (b) from the Party holding account into the operator and person holding accounts specified by the competent authority from which allowances were transferred under point (a).
(a) transferring all allowances allocated to operators for the preceding five-year period from their operator and person holding accounts to the Party holding account; (b) converting a number of allowances, equal to the number of allowances held in the registry allocated by any registry for the preceding five-year period minus the number of allowances surrendered pursuant to Article 52 since 31 May of the preceding year, into AAUs by removing the allowance element from the unique unit identification code of each such AAU comprising the elements set out in Annex VI; (c) issuing an equal number of replacement allowances by converting AAUs issued for the current period held in the Party holding account into allowances by adding the allowance element to the unique unit identification code of each such AAU comprising the elements set out in Annex VI; (d) transferring a number of those allowances issued under point (c) for the current period from the Party holding account into each operator and person holding account from which allowances were transferred under point (a), equal to the number of allowances that were transferred from those accounts under point (a).
(a) transferring the allowance to be converted to the gateway deposit account of the registry; and (b) issuing an equal amount of allowance with an initial unit type of 0 and a supplementary unit type of 4 to the account where the allowances to be converted were transferred from.
(a) transferring the allowances requested to be converted into the cancellation account; and (b) transferring an equal amount of allowances with an initial unit type of 1 to the account where the allowances to be converted were transferred from.
(a) transferring a number of allowances, equal to the number of allowances issued for the 2005 to 2007 period minus the number of allowances surrendered at the moment of cancellation and replacement pursuant to Articles 52 and 54 since 30 June of the preceding year, from their holding accounts referred to in Articles 11(2) and 63i to the cancellation account of the Community registry for the 2005 to 2007 period; (b) if instructed to do so by the competent authority, issuing a number of replacement allowances specified by the competent authority by issuing an equal number of allowances for the 2008 to 2012 period, giving each allowance a unit identification code comprising the elements set out in Annex VI; (c) transferring any such replacement allowances referred to in point (b) from the Party holding account into the operator and person holding accounts specified by the competent authority from which allowances were transferred under point (a).
(a) transferring a number of allowances, equal to the number of allowances issued for the preceding five-year period minus the number of allowances surrendered pursuant to Article 52 since 31 May of the preceding year, from their holding accounts referred to in Articles 11(2) and 63i to the cancellation account of the Community registry for the relevant period; (b) issuing an equal number of replacement allowances with a supplementary unit type of 4 for the current period into the Party holding account and assigning to each of these allowances a unique unit identification code comprising the elements set out in Annex VI; (c) transferring a number of those allowances issued in accordance with point (b) for the current period from the Party holding account into each operator and person holding account from which allowances were transferred in accordance with point (a), equal to the number of allowances that were transferred from those accounts under point (a).
(a) attempted to access accounts or processes which he is not authorised to access; (b) repeatedly attempted to access an account or a process using a non-matching username and password; or (c) attempted, or is attempting, to undermine the security of the registry or the registries system.
(a) the account holder died without a legal successor or ceased to exist as a legal person; (b) the account holder did not pay its fees; or (c) the account holder violated the terms and conditions applicable to the account; or (d) the account holder did not agree to the changes in the terms and conditions; (e) the account holder did not provide evidence concerning the changes to account information; (f) the account holder failed to maintain the required minimum number of authorised representatives for the account; (g) the account holder failed to maintain compliance with the Member State requirement to have an authorised representative with a permanent residence in the Member State of the administrator of the account; (h) the account holder failed to maintain compliance with the Member State requirement that the account holder have a permanent residence or registration in the Member State of the administrator of the account.
(a) the registry is available for access by account holders 24 hours a day, 7 days a week, and that the communication link between the registry and the Community independent transaction log is maintained 24 hours a day, 7 days a week, thereby providing backup hardware and software in the event of a breakdown in operations of the primary hardware and software; (b) the registry and the Community independent transaction log respond promptly to requests made by account holders.
(a) for a maximum period of two weeks if it suspects that the allowances or Kyoto units have been the subject of a transaction constituting fraud, money laundering, terrorist financing or other serious crime; or (b) on the basis of and in accordance with national law provisions that pursue a legitimate objective.
(a) any testing procedures on a new version or release of a registry are completed without reducing the availability to account holders of the version or release of the registry which currently has a communication link with the Community independent transaction log or UNFCCC independent transaction log; and (b) any communication link between a new version or release of a registry and the Community independent transaction log or UNFCCC independent transaction log is established and activated with minimum disruption to its account holders.
(a) web server; (b) application server; (c) database server installed on a separate machine to that or those used for the web server and application server; (d) firewalls.
(a) the record of the time in the Community independent transaction log and each registry shall be synchronised to Greenwich Mean Time; (b) all processes concerning allowances, verified emissions, automatic national allocation plan table changes and accounts shall be completed by the exchange of data written in extensible markup language (XML) using the simple object access protocol (SOAP) version 1.1 over the hypertext transfer protocol (HTTP) version 1.1 (remote procedure call (RPC) encoded style).
(a) the record of the time in the UNFCCC independent transaction log, Community independent transaction log and each registry shall be synchronised; and (b) all processes concerning allowances and Kyoto units shall be completed by the exchange of data;
1. Each Member State registry shall be capable of tabulating the following information which shall comprise the verified emissions table: (a) Years: in individual cells from 2005 onwards in ascending order. (b) Installation identification code: in individual cells comprising the elements set out in Annex VI and in ascending order. (c) Verified emissions: the verified emissions for a specified year for a specified installation shall be entered into the cell connecting that year to that installation’s identification code.
2. Each Member State registry shall be capable of tabulating the following information which shall comprise the surrendered allowances table: (a) Years: in individual cells from 2005 onwards in ascending order. (b) Installation identification code: in individual cells comprising the elements set out in Annex VI and in ascending order. (c) Surrendered allowances: the number of allowances surrendered in accordance with Articles 52, 53 and 54 for a specified year for a specified installation shall be entered into the three cells connecting that year to that installation’s identification code.
3. Each Member State registry shall be capable of tabulating the following information which shall comprise the compliance status table: (a) Years: in individual cells from 2005 onwards in ascending order. (b) Installation identification code: in individual cells comprising the elements set out in Annex VI and in ascending order. (c) Compliance status: the compliance status for a specified year for a specified installation shall be entered into the cell connecting that year to that installation’s identification code. The compliance status shall be calculated in accordance with Article 55.
1. Points 1 to 3.1, 3.4 to 4.5 and point 6 of the information identifying the installation as listed in Section 14.1 of Annex I to Decision 2007/589/EC. The name of the operator should be identical to the name of the natural or legal person that is the holder of the relevant greenhouse gas permit. The name of the installation shall be identical to the name indicated in the relevant greenhouse gas permit. 2. The permit identification code specified by the competent authority, comprising the elements set out in Annex VI. 3. The installation identification code, comprising the elements set out in Annex VI. 4. The alphanumeric identifier specified by the operator for the account, which shall be unique within the registry. 5. Name, address, city, postcode, country, telephone number, facsimile number and e-mail address of the primary authorised representative of the operator holding account specified by the operator for that account. 6. Name, address, city, postcode, country, telephone number, facsimile number and e-mail address of the secondary authorised representative of the operator holding account specified by the operator for that account. 7. Name, address, city, postcode, country, telephone number, facsimile number and e-mail address of any additional authorised representatives of the operator holding account and their account access rights, specified by the operator for that account. 8. Evidence to support the identity of the authorised representatives of the operator holding account.
| 1 | Account ID (given by registry) |
| 2 | Account type |
| 3 | Commitment period |
| 4 | Account holder ID (issued by registry) |
| 5 | Account holder Name |
| 6 | Account Identifier (given by account holder) |
| 7 | Account holder address — country |
| 8 | Account holder address — region or state |
| 9 | Account holder address — city |
| 10 | Account holder address — postcode |
| 11 | Account holder address — street |
| 12 | Account holder address — street No |
| 13 | Account holder address Company registration No or ID No |
| 14 | Account holder address Telephone 1 |
| 15 | Account holder address Telephone 2 |
| 16 | Account holder address email address |
| 17 | Date of Birth (for natural persons) |
| 18 | Place of Birth (for natural persons) |
| 19 | VAT registration number with country code |
(a) an identity card issued by a State that is a member of the European Economic Area or the Organisation for Economic Cooperation and Development; (b) a passport.
(a) the identity document submitted under point 3, if it contains the address of the permanent residence; (b) any other government-issued identity document that contains the address of permanent residence; (c) if the country of permanent residence does not issue identity documents that contain the address of permanent residence, a statement from the local authorities confirming the nominee’s permanent residence; (d) any other document that is customarily accepted in the Member State of the administrator of the account as evidence of the permanent residence of the nominee.
(a) a copy of the instruments establishing the legal entity and a copy of a document proving the registration of the legal entity; (b) bank account details; (c) a confirmation of VAT registration; (d) information on the legal entity’s beneficial owner as defined in Directive 2005/60/EC; (e) list of directors; (f) a copy of the annual report or of the latest audited financial statements, or if no audited financial statements available, a copy of the financial statements stamped by the tax office or the financial director.
| 1 | Person ID |
| 2 | Type of AR |
| 3 | First Name |
| 4 | Last Name |
| 5 | Title |
| 6 | Job title |
| 7 | Address — country |
| 8 | Address — region or state |
| 9 | Address — city |
| 10 | Address — postcode |
| 11 | Address — street |
| 12 | Address — street number |
| 13 | Telephone 1 |
| 14 | Telephone 2 |
| 15 | E-mail address |
| 16 | Date of Birth |
| 17 | Place of Birth |
| 18 | Preferred language |
| 19 | Confidentiality level |
| 20 | AARs rights |
(a) an identity card issued by a State that is a member of the European Economic Area or the Organisation for Economic Cooperation and Development; (b) a passport.
(a) the identity document submitted under point 3, if it contains the address of the permanent residence; (b) any other government-issued identity document that contains the address of permanent residence; (c) if the country of permanent residence does not issue identity documents that contain the address of permanent residence, a statement from the local authorities confirming the nominee’s permanent residence; (d) any other document that is customarily accepted in the Member State of the administrator of the account as evidence of the permanent residence of the nominee.
(a) unit identification code; (b) account identification code; (c) permit identification code; (d) account holder identification code; (e) installation identification code; (f) correlation identification code; (g) transaction identification code; (h) reconciliation identification code; (i) project identification code.
| Element | Display Order | Identifier Required for the Following Unit Types | Data Type | Length | Range or Codes |
|---|---|---|---|---|---|
| Originating Registry | 1 | AAU, RMU, CER, ERU | A | 3 | ISO3166 (2 letter code), "EU" for the Community registry |
| Unit Type | 2 | AAU, RMU, CER, ERU | N | 2 | |
| Supplementary Unit Type | 3 | AAU, RMU, CER, ERU | N | 2 | |
| Unit Serial Block Start | 4 | AAU, RMU, CER, ERU | N | 15 | Unique numeric values assigned by registry from 1 – |
| Unit Serial Block End | 5 | AAU, RMU, CER, ERU | N | 15 | Unique numeric values assigned by registry from 1 – |
| Original Commitment Period | 6 | AAU, RMU, CER, ERU | N | 2 | |
| Applicable Commitment Period | 7 | AAU, CER, ERU | N | 2 | |
| LULUCF Activity | 8 | RMU, CER, ERU | N | 3 | |
| Project Identifier | 9 | CER, ERU | N | 7 | Unique numeric value assigned for project |
| Track | 10 | ERU | N | 2 | 1 or 2 |
| Expiry Date | 11 | lCER, tCER | Date | Expiration date for lCERs or tCERs |
| Initial Unit Type | Supplementary Unit Type | Description |
|---|---|---|
| 1 | [not applicable] | AAU |
| 2 | [not applicable] | RMU |
| 3 | [not applicable] | ERU converted from AAU |
| 4 | [not applicable] | ERU converted from RMU |
| 5 | [not applicable] | CER (not tCER or lCER) |
| 6 | [not applicable] | tCER |
| 7 | [not applicable] | lCER |
| 1 | 1 | Allowance issued for the 2008-2012 period and subsequent 5-year periods and is converted from an AAU |
| 0 | 2 | Allowance issued for the 2005-2007 period and not converted from an AAU or other Kyoto unit |
| 0 | 3 | Force-majeure allowance |
| 0 | 4 | Allowance issued for the 2008 to 2012 and subsequent five-year periods by a Member State that does not have AAUs, and which is not converted from an AAU or other Kyoto unit |
| Element | Display Order | Data Type | Length | Range or Codes |
|---|---|---|---|---|
| Originating Registry | 1 | A | 3 | ISO3166 (2 letter code), "CDM" for the CDM registry, "EU" for the Community registry |
| Account Type | 2 | N | 3 | |
| Account Identifier | 3 | N | 15 | |
| Applicable Commitment Period | 4 | N | 2 |
| Element | Display Order | Data Type | Length | Range or Codes |
|---|---|---|---|---|
| Originating Registry | 1 | A | 3 | ISO3166 (2 letter code), "EU" for the Community registry |
| Permit Identifier | 2 | A | 50 | ([0-9] [A-Z] ["-"]) + |
| Element | Display Order | Data Type | Length | Range or Codes |
|---|---|---|---|---|
| Originating Registry | 1 | A | 3 | ISO3166 (2 letter code), "EU" for the Community registry |
| Account Holder Identifier | 2 | A | 50 | ([0-9] [A-Z]) + |
| Element | Display Order | Data Type | Length | Range or Codes |
|---|---|---|---|---|
| Originating Registry | 1 | A | 3 | ISO3166 (2 letter code), "EU" for the Community registry |
| Installation Identifier | 2 | N | 15 | Unique numeric values assigned by a registry from 1 to |
| Element | Display Order | Data Type | Length | Range or Codes |
|---|---|---|---|---|
| Originating Registry | 1 | A | 3 | ISO3166 (2 letter code), "EU" for the Community registry |
| Correlation Identifier | 2 | N | 15 | Unique numeric values assigned by a registry from 1 to |
| Code | Description |
|---|---|
| 1 | Combustion installations with a rated thermal input exceeding 20 MW |
| 2 | Mineral oil refineries |
| 3 | Coke ovens |
| 4 | Metal ore (including sulphide ore) roasting or sintering installations |
| 5 | Installations for the production of pig iron or steel (primary or secondary fusion) including continuous casting |
| 6 | Installations for the production of cement clinker in rotary kilns or lime in rotary kilns or in other furnaces |
| 7 | Installations for the manufacture of glass including glass fibre |
| 8 | Installations for the manufacture of ceramic products by firing, in particular roofing tiles, bricks, refractory bricks, tiles, stoneware or porcelain |
| 9 | Industrial plants for the production of (a) pulp from timber or other fibrous materials (b) paper and board |
| 99 | Other activity opted-in pursuant to Article 24 of Directive 2003/87/EC |
| Code | Description |
|---|---|
| 1 | Account holder |
| 2 | Primary authorised representative of the account holder |
| 3 | Secondary authorised representative of the account holder |
| 4 | Additional authorised representative of the account holder |
| 5 | Authorised representative of the verifier |
| 6 | Contact person for the installation |
| Code | Description |
|---|---|
| 01-00 | Issue of AAUs and RMUs |
| 02-00 | Conversion of AAUs and RMUs to ERUs |
| 03-00 | External transfer (2008-2012 onwards) |
| 04-00 | Cancellation (2008-2012 onwards) |
| 05-00 | Retirement (2008-2012 onwards) |
| 06-00 | Cancellation and replacement of tCERs and lCERs |
| 07-00 | Carry-over of Kyoto units and allowances issued for the 2008-2012 period and subsequent five-year periods |
| 08-00 | Change of expiry date of tCERs and lCERs |
| 10-00 | Internal transfer |
| 01-51 | Allowance issue (2005-2007) |
| 10-52 | Allowance issue (2008-2012 onwards) |
| 10-53 | Allowance allocation |
| 01-54 | Force-majeure allowance issue |
| 10-55 | Correction to allowances |
| 03-21 | External transfer (2005-2007) |
| 10-01 | Allowance cancellation (2005-2007) |
| 10-02 | Allowance surrender |
| 04-03 | Retirement (2005-2007) |
| 10-41 | Cancellation and replacement |
| 10-61 | conversion of surrendered allowances for retirement(2008 to 2012 onwards) |
| 10-62 | conversion of unallocated allowances for retirement (2008 to 2012 onwards) |
| 05-00 | retirement of Kyoto units (2008 to 2012 onwards) |
| 05-01 | retirement of surrendered allowances (2008 to 2012 onwards) |
| 05-02 | retirement of unallocated allowances (2008 to 2012 onwards) |
| 01-22 | Allowance issue (registries referred to in Article 63a) |
| 03-00 | External transfer (between a registry referred to in Article 63a and other registry) |
| 10-22 | Transfer between two registries referred to in Article 63a |
| 05-22 | retirement (registries referred to in Article 63a) |
| Code | Description |
|---|---|
| 0 | No supplementary unit type |
| 1 | Allowance issued for the 2008-2012 period and subsequent five-year periods and is converted from an AAU |
| 2 | Allowance issued for the 2005-2007 period and not converted from an AAU or other Kyoto unit |
| 3 | Force-majeure allowance |
| 4 | Allowance issued for the 2008 to 2012 and subsequent five-year periods by a Member State that does not have AAUs, and which is not converted from an AAU or other Kyoto unit |
| Code | Description |
|---|---|
| 1 | Add people to the account or installation |
| 2 | Update people |
| 3 | Delete people |
(a) the authorised representative of an account shall submit a request to the registry administrator of that registry; (b) the registry administrator shall assign a unique correlation identification code comprising the elements set out in Annex VI to the request; (c) provided that these processes are completed through the exchange of data via the UNFCCC independent transaction log and thereon to the Community independent transaction log, the registry administrator shall call the appropriate operation on the UNFCCC independent transaction log account management Web service. In all other cases the registry administrator shall call the appropriate operation on the Community independent transaction log account management Web service; (d) the Community independent transaction log shall validate the request by calling the appropriate validation function within the Community independent transaction log; (e) if the request is successfully validated and thereby accepted, the Community independent transaction log shall amend the information it holds in accordance with that request; (f) the Community independent transaction log shall call the "receiveAccountOperationOutcome" operation on the account management Web service of the registry which sent the request, notifying the registry as to whether the request was successfully validated and thereby accepted, or whether the request was found to contain a discrepancy and was thereby rejected; (g) if the request was successfully validated and thereby accepted, the registry administrator which sent the request shall amend the information held in the registry in accordance with that validated request; otherwise, if the request was found to contain a discrepancy and was thereby rejected, the registry administrator which sent the request shall not amend the information held in the registry in accordance with that rejected request.
| Component | Function | Scope |
|---|---|---|
| MgmtOfAccountWS | CreateAccount() | Public |
| UpdateAccount() | Public | |
| CloseAccount() | Public | |
| UpdateVerifiedEmissions() | Public | |
| ReceiveAccountOperationOutcome() | Public | |
| AccountManagement | ValidateAccountCreation() | Private |
| CreateAccount() | Private | |
| ValidateAccountUpdate() | Private | |
| UpdateAccount() | Private | |
| ValidateAccountClosure() | Private | |
| CloseAccount() | Private | |
| ValidateVerifiedEmissionsUpdate() | Private | |
| UpdateVerifiedEmissions() | Private | |
| DataValidation | AuthenticateMessage() | Private |
| CheckVersion() | Private | |
| DataFormatChecks() | Private |
| The purpose of this component is to handle web service requests for the management of accounts and verified emissions. | |
| CreateAccount() | Handles the account creation requests |
| UpdateAccount() | Handles the account update requests |
| CloseAccount() | Handles account closure requests |
| UpdateVerifiedEmissions() | Handles verified emissions update requests |
| ReceiveAccountOperationOutcome() | Receives an account operation (creation, update, …) outcome ("accepted" or "rejected") |
| Not applicable. | |
| Community independent transaction log (for all functions) and registry (for the ReceiveAccountOperationOutcome function only) | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountType | Mandatory |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Mandatory |
| CommitmentPeriod | Optional |
| Optional | |
| InstallationIdentifier | Mandatory |
| PermitIdentifier | Mandatory |
| Name | Mandatory |
| MainActivityType | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Mandatory |
| Mandatory | |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| PhoneNumber1 | Mandatory |
| PhoneNumber2 | Mandatory |
| FaxNumber | Optional |
| Mandatory | |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Optional |
| Optional | |
| PermitIdentifier | Optional |
| Name | Optional |
| MainActivityType | Optional |
| Country | Optional |
| PostalCode | Optional |
| City | Optional |
| Address1 | Optional |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Optional |
| Optional | |
| Action | Mandatory |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Optional |
| Country | Optional |
| PostalCode | Optional |
| City | Optional |
| Address1 | Optional |
| Address2 | Optional |
| PhoneNumber1 | Optional |
| PhoneNumber2 | Optional |
| FaxNumber | Optional |
| Optional | |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountIdentifier | Mandatory |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| Year | Mandatory |
| Mandatory | |
| InstallationIdentifier | Mandatory |
| VerifiedEmission | Mandatory |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Outcome | Mandatory |
| Response List | Optional |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| The purpose of this component is to provide the validating and update functions for the management of accounts and verified emissions. | |
| Not applicable. | |
| ValidateAccountCreation() | Validates an account creation |
| ValidateAccountUpdate() | Validates an account update |
| ValidateAccountClosure() | Validates an account closure |
| ValidateVerifiedEmissionsUpdate() | Validates a verified emissions update |
| CreateAccount() | Creates accounts |
| UpdateAccount() | Updates accounts |
| CloseAccount() | Closes accounts |
| UpdateVerifiedEmissions() | Updates verified emissions for installations |
| Transaction log (all functions), registry (for information only). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountType | Mandatory |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Mandatory |
| CommitmentPeriod | Optional |
| Optional | |
| InstallationIdentifier | Mandatory |
| PermitIdentifier | Mandatory |
| Name | Mandatory |
| MainActivityType | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Mandatory |
| Mandatory | |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| PhoneNumber1 | Mandatory |
| PhoneNumber2 | Optional |
| FaxNumber | Mandatory |
| Optional | |
| Result Identifier | Mandatory |
| Response List | Optional |
| Range | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountType | Mandatory |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Mandatory |
| CommitmentPeriod | Optional |
| Optional | |
| InstallationIdentifier | Mandatory |
| PermitIdentifier | Mandatory |
| PermitDate | Mandatory |
| Name | Mandatory |
| MainActivityType | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Mandatory |
| Mandatory | |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| PhoneNumber1 | Mandatory |
| PhoneNumber2 | Optional |
| FaxNumber | Optional |
| Optional | |
| Result Identifier | Mandatory |
| Not applicable. | |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Optional |
| Optional | |
| PermitIdentifier | Optional |
| PermitDate | Optional |
| Name | Optional |
| MainActivityType | Optional |
| Country | Optional |
| PostalCode | Optional |
| City | Optional |
| Address1 | Optional |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Optional |
| Optional | |
| Action | Mandatory |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Optional |
| Country | Optional |
| PostalCode | Optional |
| City | Optional |
| Address1 | Optional |
| Address2 | Optional |
| PhoneNumber1 | Optional |
| PhoneNumber2 | Optional |
| FaxNumber | Optional |
| Optional | |
| Result Identifier | Mandatory |
| Response List | Optional |
| Range | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountType | Mandatory |
| AccountIdentifier | Mandatory |
| IdentifierInReg | Mandatory |
| Optional | |
| InstallationIdentifier | Mandatory |
| PermitIdentifier | Mandatory |
| PermitDate | Mandatory |
| Name | Mandatory |
| MainActivityType | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| ParentCompany | Optional |
| SubsidiaryCompany | Optional |
| EPERIdentification | Optional |
| Latitude | Optional |
| Longitude | Optional |
| ContactPeople (see People) | Mandatory |
| Mandatory | |
| RelationshipCode | Mandatory |
| PersonIdentifier | Mandatory |
| FirstName | Optional |
| LastName | Mandatory |
| Country | Mandatory |
| PostalCode | Mandatory |
| City | Mandatory |
| Address1 | Mandatory |
| Address2 | Optional |
| PhoneNumber1 | Optional |
| PhoneNumber2 | Optional |
| FaxNumber | Optional |
| Optional | |
| Result Identifier | Mandatory |
| Not applicable. | |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountIdentifier | Mandatory |
| Result Identifier | Mandatory |
| Response List | Optional |
| This function closes an account or accounts by setting the end validity date of the account(s) to be closed to the current date. | |
| Registry | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| AccountIdentifier | Mandatory |
| Result Identifier | Mandatory |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Mandatory | |
| Year | Mandatory |
| Mandatory | |
| InstallationIdentifier | Mandatory |
| VerifiedEmission | Mandatory |
| Result Identifier | Mandatory |
| Response List | Optional |
| Range | |
| Updates the verified emissions for the year and installation specified. | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| Mandatory | |
| Year | Mandatory |
| Mandatory | |
| InstallationIdentifier | Mandatory |
| VerifiedEmission | Mandatory |
| Result Identifier | Mandatory |
| Process description | Community independent transaction log response codes |
|---|---|
| Account creation | |
| Account update | |
| Account closure | |
| Verified emissions update | Range |
(a) registry version and registry authentication checks; (b) message viability checks; (c) data integrity checks; (d) general transaction checks; and (e) message sequence checks.
(a) the Kyoto units or allowances are held in the transferring account (a discrepancy returns response code 7027 );(b) the transferring account exists in the specified registry (a discrepancy returns response code 7021 );(c) the acquiring account exists in the specified registry (a discrepancy returns response code 7020 );(d) both accounts exist in the same registry for an internal transfer (a discrepancy returns response code 7022 );(e) both accounts exist in different registries for an external transfer (a discrepancy returns response code 7023 );(f) the transferring account is not blocked pursuant to Article 27 (a discrepancy returns response code 7025 );(g) force majeure allowances are not being transferred (a discrepancy returns response code 7024 ).
| Process description | Process type | Community independent transaction log response codes |
|---|---|---|
| Issue of AAUs and RMUs | 01-00 | [not applicable] |
| Conversion of AAUs and RMUs to ERUs | 02-00 | |
| External transfer (2008-2012 onwards) | 03-00 | |
| Cancellation (2008-2012 onwards) | 04-00 | [not applicable] |
| Retirement (2008-2012 onwards) | 05-00 | Range |
| Cancellation and replacement of tCERs and lCERs | 06-00 | [not applicable] |
| Carry-over of Kyoto units and allowances issued for the 2008-2012 period and subsequent five-year periods | 07-00 | [not applicable] |
| Change of expiry date of tCERs and lCERs | 08-00 | [not applicable] |
| Internal transfer | 10-00 | |
| Allowance issue (2005-2007) | 01-51 | |
| Allowance issue (2008-2012 onwards) | 10-52 | |
| Allowance allocation | 10-53 | |
| Force-majeure allowance issue | 01-54 | |
| Correction to allowances | 10-55 | Range |
| External transfer (2005-2007) | 03-21 | |
| Allowance cancellation (2005-2007) | 10-01 | |
| Allowance surrender | 10-02 | |
| Retirement (2005-2007) | 04-03 | |
| Cancellation and replacement | 10-41 | |
| Conversion of surrendered allowances for retirement (2008 to 2012 onwards) | 10-61 | |
| Conversion of unallocated allowances for retirement (2008 to 2012 onwards) | 10-62 | |
| Retirement of Kyoto units (2008 to 2012 onwards) | 05-00 | |
| Retirement of surrendered allowances (2008 to 2012 onwards) | 05-01 | |
| Retirement of unallocated allowances (2008 to 2012 onwards) | 05-02 | |
| External transfer (between a registry referred to in Article 63a and other registry) | 03-00 | Range |
| Allowance issue (registries referred to in Article 63a) | 01-22 | |
| Retirement (registries referred to in Article 63a) | 05-22 | |
| Transfer between two registries referred to in Article 63a | 10-22 |
(a) upon the account holder's request to transfer allowances with a supplementary unit type 4 from an account in a registry referred to in Article 63a, the transferring registry: (i) checks if the balance of the Party holding account in the registry referred to in Article 63a which is only capable of holding allowances with a supplementary unit type 1, 2 or 3 is at least equal to the quantity to be transferred; (ii) redirects the allowances to the Party holding account in the registry referred to in Article 63a which is only capable of holding allowances with a supplementary unit type 4; (iii) transfers an equivalent amount of supplementary unit type 1, 2 or 3 allowances from the Party holding account that is only capable of holding allowances with a supplementary unit type of 1, 2 or 3 to the account of the account holder initiating the transaction; (iv) transfers these supplementary unit type 1, 2 or 3 allowances from account of the account holder initiating the transaction to the destination account;
(b) upon the account holder's request to transfer allowances with a supplementary unit type of 1, 2 or 3 to an account in a registry referred to in Article 63a, the acquiring registry: (i) transfers the allowances with a supplementary unit type of 1, 2 or 3 to the destination account; (ii) transfers these allowances from the destination account to the Party holding account in the registry operated in accordance with Article 63a which is only capable of holding allowances with a supplementary unit type 1, 2 or 3; (iii) transfers an equivalent amount of supplementary unit type 4 allowances from the Party holding account that is only capable of holding allowances with an initial unit type of 0 and a supplementary unit type of 4 to the destination account. If the balance on the Party holding account capable of holding supplementary unit type 4 allowances is less than the quantity that needs to be transferred, the missing number of supplementary unit type 4 allowances are created on the Party holding account before the transfer.
(a) the total number of allowances held in each account type in that registry; (b) the unit identification codes of any allowance held in each account type in that registry; (c) the transaction log and audit log history of any allowance held in each account type in that registry; (d) the total number of allowances held in each account in that registry; (e) the unit identification codes of any allowance held in each account in that registry; and (f) the transaction log and audit log history of each allowance held in any account in that registry.
(a) the total number of allowances, AAUs, RMUs, ERUs, CERs (not tCERs or lCERs), lCERs and tCERs, held in each account type in that registry; (b) the unit identification codes of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER, held in each account type in that registry; and (c) the transaction log and audit log history of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in each account type in that registry.
(a) the total number of allowances, AAUs, RMUs, ERUs, CERs (not tCERs or lCERs), lCERs and tCERs held in each account in that registry; (b) the unit identification codes of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in each account in that registry; and (c) the transaction log and audit log history of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in each account in that registry.
| Process description | Community independent transaction log response codes |
|---|---|
| Reconciliation | Range: |
(a) Transaction clean-up all processes under Annex IX which have been initiated but not yet terminated, completed or cancelled within 24 hours shall be cancelled. Transaction clean-up occurs on an hourly basis. (b) Outstanding units all allowances which have not been cancelled pursuant to Articles 60 or 61 on or after 1 May 2008 and on or after 1 May in the first year of each subsequent five-year period shall be identified.(c) Process status a registry administrator may query the status of a process under Annex IX which has been initiated by that registry administrator. (d) Time synchronisation upon request, each registry administrator shall provide the system time of its registry in order that the consistency between the system time of a registry and the system time of the Community independent transaction log can be checked, and that the two times can be synchronised. Upon request, a registry administrator shall change the system time of its registry in order to ensure time synchronisation.
(a) Status of a registry: if the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process, the message shall be rejected and the response code 7005 shall be returned.(b) Registry version and registry authentication, message viability, and data integrity: if the Community independent transaction log detects a discrepancy, the message shall be rejected and the appropriate response codes shall be returned as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC.
(a) Status of a registry: if the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process, the message shall be rejected and the response code 7005 shall be returned.(b) Registry version and registry authentication, message viability, data integrity and time synchronisation: if the Community independent transaction log detects a discrepancy, the message shall be rejected and the appropriate response codes shall be returned as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC.
(a) the registry administrator shall initiate the automatic national allocation plan table change process by assigning a unique correlation identification code comprising the elements set out in Annex VI to its request; (b) the registry administrator shall call the appropriate operation on the Community independent transaction log automatic national allocation plan table change Web service; (c) the Community Independent Transaction Log shall validate the request by calling the appropriate validation function within the Community Independent Transaction Log; (d) if the request is successfully validated and thereby accepted, the Community Independent Transaction Log shall amend the information it holds in accordance with that request; (e) the Community Independent Transaction Log shall call the "receiveNapManagementOutcome" operation on the automatic national allocation plan table change Web service of the registry which sent the request, notifying the registry as to whether the request was successfully validated and thereby accepted, or whether the request was found to contain a discrepancy and was thereby rejected; (f) if the request was successfully validated and thereby accepted, the registry administrator which sent the request shall amend the information held in the registry in accordance with that validated request; otherwise, if the request was found to contain a discrepancy and was thereby rejected, the registry administrator which sent the request shall not amend the information held in the registry in accordance with that rejected request.
| Component | Function | Scope |
|---|---|---|
| NAPTableManagementWS | AddNEInstallationtoNAP() | Public |
| IncreaseNAPallocationtoNEInstallation() | Public | |
| RemoveNAPallocationofclosingInstallation() | Public | |
| IncreaseNAPallocationReserve | Public | |
| RemoveNAPallocationReserve | Public |
| The purpose of this component is to handle web service requests for the management of automatic changes to the national allocation plan table | |
| AddNEInstallationtoNAP() | Handles the requests for adding new entrant new installations to the national allocation plan table |
| IncreaseAllocationtoNEInstallationinNAP() | Handles the requests for increasing the allocation in the national allocation plan table of existing installations that are new entrants |
| RemoveNAPallocationofclosingInstallation() | Handles the requests for removing the allocation from the national allocation plan table of installations that are closing |
| IncreaseNAPallocationReserve() | Handles the requests for increasing the reserve in the national allocation plan table by a quantity of allowances acquired by the registry through "replenishment" |
| RemoveNAPallocationReserve() | Handles the requests for removing from the reserve in the national allocation plan table, a quantity of allowances acquired by the registry through "replenishment" |
| Not applicable. | |
| Community independent transaction log (for all functions) and registry (for the receiveNapManagementOutcome function only) | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| InitiatingRegistry | Mandatory |
| CommitmentPeriod | Mandatory |
| NewValueofReserve | Mandatory |
| Mandatory | |
| PermitIdentifier | Mandatory |
| InstallationIdentifier | Mandatory |
| Mandatory | |
| YearinCommitmentPeriod | Mandatory |
| AmountofAllowances | Mandatory |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| InitiatingRegistry | Mandatory |
| CommitmentPeriod | Mandatory |
| NewValueofReserve | Mandatory |
| Mandatory | |
| InstallationIdentifier | Mandatory |
| Mandatory | |
| Yearincommitmentperiod | Mandatory |
| AmountofAllowances | Mandatory |
| ResultIdentifier | Mandatory |
| ResponseCode | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| InitiatingRegistry | Mandatory |
| CommitmentPeriod | Mandatory |
| NewValueofReserve | Mandatory |
| Mandatory | |
| InstallationIdentifier | Mandatory |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| Outcome | Mandatory |
| Response List | Optional |
| Result Identifier | Mandatory |
| Response Code | Optional |
| |
| Not applicable (called as a web service). | |
| Purpose | |
|---|---|
| Input parameters | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| InitiatingRegistry | Mandatory |
| CommitmentPeriod | Mandatory |
| NewValueofReserve | Mandatory |
| Output parameters | |
| Result Identifier | Mandatory |
| Response Code | Optional |
| Uses | |
| |
| Used By | |
| Not applicable (called as a web service). | |
| Purpose | |
|---|---|
| Input parameters | |
| From | Mandatory |
| To | Mandatory |
| CorrelationId | Mandatory |
| MajorVersion | Mandatory |
| MinorVersion | Mandatory |
| InitiatingRegistry | Mandatory |
| CommitmentPeriod | Mandatory |
| NewValueofReserve | Mandatory |
| Output parameters | |
| Result Identifier | Mandatory |
| Response Code | Optional |
| Uses | |
| |
| Used By | |
| Not applicable (called as a web service). | |
| Process description | Community independent transaction log response codes |
|---|---|
| NAPTableManagementWS.AddNEInstallationtoNAP | 7005, 7122, 7125, 7153, 7154, 7155, 7156, 7159, 7215, 7451, 7452, 7700, 7701, 7702, 7703, 7704 |
| NAPTableManagementWS.IncreaseallocationtoNEInstallationinNAP | 7005, 7153, 7154, 7155, 7156, 7159, 7207, 7451, 7452, 7700, 7701, 7702, 7703, 7705 |
| 7005, 7153, 7154, 7155, 7156, 7159, 7207, 7451, 7700, 7706 | |
| IncreaseNAPallocationReserve | |
| RemoveNAPallocationReserve |
| Response Code | Description | |
|---|---|---|
| Response Code | Description | Equivalent response code under the data exchange standards |
| The current status of the initiating (or transferring) registry does not permit this process to take place. | ||
| The current status of the acquiring registry does not permit this process to take place | ||
| The specified account identification code does not exist in the acquiring registry. | ||
| The specified account identification code does not exist in the transferring registry. | ||
| The transferring account and acquiring account must be in the same registry for all transactions except external transfers. | ||
| The transferring account and acquiring account must be in different registries for external transfers. | ||
| Force majeure allowances cannot be transferred out of the Party holding account unless being cancelled and retired in accordance with Article 58. | ||
| The transferring account is blocked for all transfers of allowances out of that account, with the exception of the surrender and cancellation and replacement processes pursuant to Articles 52, 53, 60 and 61. | ||
| One or more units in the serial block are not recognised as being held by the transferring account. | ||
| The account has already been created. | ||
| An account must have one and only one account holder. | ||
| An account must have one and only one primary authorised representative. | ||
| An account must have one and only one secondary authorised representative. | ||
| An installation must have one and only one contact person. | ||
| The installation associated to this account is already associated to another account. | ||
| The authorised representatives of the account must all be different. | ||
| The alphanumeric identifier specified for the account is already specified for another account. | ||
| The account type being created has not been given the correct commitment period. | ||
| An operator holding account must have one and only one installation associated with that account. | ||
| The specified account does not exist, and therefore it is not possible to update or close the account. | ||
| It is not possible to change the account holder of a person holding account. | ||
| The specified account has already been closed therefore it is not possible to close the account. | ||
| The specified account still holds units and therefore it is not possible to close the account. | ||
| The installation linked to the specified account is not in compliance therefore it is not possible to close the account. | ||
| The specified installation does not exist and therefore it is not possible to update the verified emissions table for that installation. | ||
| The specified year is a future year and therefore it is not possible to update the verified emissions table for that year. | ||
| The people and their relationship with the account do not exist and therefore it is not possible to update that relationship. | ||
| The correlation identifier is not in valid format or is out of range. | ||
| The account alphanumeric identifier is not in valid format or is out of range | ||
| The permit identifier is not in valid format or is out of range. | ||
| The installation name is not in valid format or is out of range. | ||
| The installation main activity is not in valid format or is out of range. | ||
| The installation country is not in valid format or is out of range. | ||
| The installation postal code is not in valid format or is out of range. | ||
| The installation city is not in valid format or is out of range. | ||
| The installation address1 is not in valid format or is out of range. | ||
| The installation address2 is not in valid format or is out of range. | ||
| The installation parent company is not in valid format or is out of range. | ||
| The installation subsidiary company is not in valid format or is out of range. | ||
| The installation EPER identification is not in valid format or is out of range. | ||
| The installation latitude is not in valid format or is out of range. | ||
| The installation longitude is not in valid format or is out of range. | ||
| The people relationship code is not in valid format or is out of range. | ||
| The person identifier is not in valid format or is out of range. | ||
| The people first name is not in valid format or is out of range. | ||
| The people last name is not in valid format or is out of range. | ||
| The people country is not in valid format or is out of range. | ||
| The people postal code is not in valid format or is out of range. | ||
| The people city is not in valid format or is out of range. | ||
| The people address1 is not in valid format or is out of range. | ||
| The people address2 is not in valid format or is out of range. | ||
| The people phonenumber1 is not in valid format or is out of range. | ||
| The people phonenumber2 is not in valid format or is out of range. | ||
| The people fax number is not in valid format or is out of range. | ||
| The people email is not in valid format or is out of range. | ||
| The people action is not in valid format or is out of range. | ||
| The installation verified emission is not in valid format or is out of range. | ||
| The from element is not in valid format or is out of range. | ||
| The to element is not in valid format or is out of range. | ||
| The major version is not in valid format or is out of range. | ||
| The minor version is not in valid format or is out of range. | ||
| The account type is not in valid format or is out of range. | ||
| The account identifier is not in valid format or is out of range. | ||
| The installation identifier is not in valid format or is out of range. | ||
| It is not possible for a person holding account to have a contact person or his details, or an installation or its details (as listed in section 11.1 of Annex I to Commission Decision 2004/156/EC) associated with that account. | ||
| The installation related to the operator holding account is not indicated as "closed" in the national allocation plan table and therefore it is not possible to close the account. | ||
| The installation related to the operator holding account does not have an entry in the national allocation plan table and therefore it is not possible to open the account. | ||
| The amount of allowances for the specified period requested to be issued exceeds the amount approved by the Commission in the national allocation plan. | ||
| The acquiring account is not a Party holding account. | ||
| The national allocation plan table has not been submitted to the Commission and therefore it is not possible for the issuance or allocation of allowances for the specified period to take place. | ||
| The units requested to be converted into allowances must be AAUs that have been issued for a commitment period matching the commitment period for which allowances are being issued. | ||
| The specified acquiring account is not the operator holding account which is associated to the specified installation. | ||
| The installation does not exist in the national allocation plan table. | ||
| The specified year does not exist in the national allocation plan table. | ||
| The acquiring account is not the retirement account for the 2005-2007 period. | ||
| Force-majeure allowances can only be issued prior to | ||
| The amount of force-majeure allowances requested to be issued exceeds the amount approved by the Commission for the commitment period. | ||
| The acquiring account is not the cancellation account for the 2005-2007 period. | ||
| The reduction in the number of allowances exceeds the correction to the NAP as approved by the Commission. | ||
| The number of allowances transferred is not strictly equal to the number foreseen in the NAP for the specified installation and specified year. | ||
| The installation does not exist. | ||
| The number of allowances transferred for the specified installation and specified year as foreseen in the national allocation plan has already been transferred. | ||
| The specified year is not part of the period 2005-2007. | ||
| The specified AAUs are allowances and therefore it is not possible to convert those AAUs into ERUs. | ||
| The units requested to be issued do not have the correct allowance identification code and therefore it is not possible for the issue to take place. | ||
| The units requested to be issued do not have the correct force majeure allowance identification code and therefore it is not possible for the issue to take place. | ||
| The acquiring or transferring account may not be in a registry referred to in Article 63a. | ||
| The allowances to be transferred may not have a supplementary unit type 4. | ||
| The acquiring account must be the cancellation account for the relevant period. | ||
| Allowances to be issued must have a supplementary unit type 4. | ||
| The combined holdings after the transaction of the two Party holding accounts involved in the transaction in the registry referred to in Article 63a must be equal to their combined holdings before the transaction. | ||
| The balance of the Party holding account capable of holding supplementary unit type 1, 2 or 3 allowances must be greater than or equal to the quantity to be transferred from the registry referred to in Article 63a. | ||
| The acquiring account must be the retirement account for the current period. | ||
| Allowances must be those issued for the current period. | ||
| Warning: holdings calculated pursuant to Decision 18/CP.7 of the Conference of the Parties of the UNFCCC are only 1 % above commitment period reserve | ||
| There is no mutual recognition agreement between the transferring registry and the acquiring registry that enables the transfer of allowances. | ||
| After 30 April of the first year of the current period, allowances issued for the preceding period may only be transferred to the cancellation account or retirement account for that period. | ||
| Allowances are not those issued for the 2005-2007 period. | ||
| It is not possible to surrender allowances issued for the period 2005-2007 for the period 2008-2012 and subsequent five-year periods. | ||
| The transferring account is not an operator holding account. | ||
| It is not possible to surrender allowances issued for the current period for the previous period. | ||
| Units are not eligible for surrender pursuant to Article 53. | ||
| The number of allowances and force majeure allowances requested to be transferred to the retirement account is not equal to the number of allowances surrendered pursuant to Articles 52 and 54. | ||
| The number of AAUs requested to be converted from allowances is not equal to the number of allowances surrendered pursuant to Article 52. | ||
| The number of units requested to be transferred to the retirement account is not equal to the number of allowances surrendered pursuant to Article 52 and 53. | ||
| The transferring account(s) are not Party holding account(s). | ||
| Units are not eligible for retirement pursuant to Articles 58 and 59. | ||
| The number of CERs requested to be transferred to the cancellation account is not equal to the number of allowances surrendered pursuant to Article 53. | ||
| the quantity of AAUs to be retired is not equal with the quantity of allowances converted with the "conversion of unallocated allowances for retirement" process. | ||
| The transaction is not initiated after 30 June of the year following the last year of the relevant five-year period. | ||
| The units to be retired are allowances and thus cannot be retired. | ||
| The quantity to be converted cannot exceed the number of allowances issued but not allocated. | ||
| The number of AAUs requested to be converted into allowances is not equal to the number of allowances cancelled. | ||
| Specified unit type requested to be cancelled in advance of replacement is not an allowance issued for the preceding period. | ||
| The number of allowances cancelled is not equal to the number of allowances to be cancelled pursuant to Article 60(a) and 61(b). | ||
| The quantity of allowances cancelled from the transferring account is not equal to the quantity of allowances transferred back to this account. | ||
| The transferring account(s) must be accounts referred to in Article 11(1) and (2). | ||
| The acquiring account(s) must be accounts referred to in Article 11(1) and (2). | ||
| The number of allowances cancelled must be equal to the number of allowances to be cancelled pursuant to Article 63o. | ||
| The total quantity of allowances in the updated NAP and in the current NAP must be equal. | ||
| The quantity allocated to new entrants may not be greater than the quantity by which the reserve is decreased. | ||
| The quantity of allowances added to the reserve must be positive. | ||
| The quantity of allowances removed from the reserve must not exceed the total quantity of allowances acquired through "replenishment". | ||
| There is an inconsistency between the registry and the CITL in the operator holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the person holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the operator holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the person holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the operator holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the person holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the operator holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the person holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the Party holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the retirement account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the cancellation account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the Party holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the retirement account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the cancellation account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the Party holding account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the retirement account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the cancellation account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the Party holding account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the retirement account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the cancellation account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the replacement account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the replacement account unit blocks. | ||
| There is an inconsistency between the registry and the CITL in the totals of the replacement account unit blocks. | ||
| Information: there are no inconsistencies between the registry and the CITL in the totals of the replacement account unit blocks. | ||
| The verified emissions figure for year X cannot be corrected after 30 April of year X+1 unless the competent authority notifies the Central Administrator the new compliance status applicable to the installation whose verified emissions figure is corrected. | ||
| Reminder: the specified unit blocks of allowances issued for the previous period have not yet been cancelled pursuant to Articles 60 and 61. | ||
| The commitment period code is out of range. | ||
| Allocation must be provided for all the years. | ||
| The new reserve must remain positive or zero. | ||
| The amount of allowances to allocate for an installation and a year must be greater than or equal to 0. | ||
| The permit identifier must exist and be connected to the installation identifier. | ||
| The amount of allowances allocated for an installation and a year in the updated NAP must be greater than or equal to this amount in the current NAP. | ||
| The amount of allowances deleted from the NAP table for installations must be equal to the amount by which the reserve is increased. | ||
| Initiating registry must be listed in Registry table. | ||
| Initiating registry status must allow transactions to be proposed. (The CITL will maintain the current status of each registry. In this case, the CITL must recognize that the registry is fully operational.). | ||
| Acquiring registry status must allow transactions to be accepted. (The CITL will maintain the current status of each registry. In this case, the CITL must recognize that the registry is fully operational.). | ||
| Registry status must allow reconciliation actions to be conducted. (The CITL will maintain the current status of each registry. In this case, the CITL must recognize that the registry is available for reconciliation.). | ||
| Transaction ID must be comprised of a valid registry code followed by numeric values. | ||
| Transaction type code must be valid. | ||
| Supplementary Transaction Type code must be valid. | ||
| Transaction status code must be valid. | ||
| Account Type code must be valid. | ||
| Initiating Account Identifier must be greater than zero. | ||
| Acquiring Account Identifier must be greater than zero. | ||
| The Originating Registry of all unit blocks must be valid. | ||
| Unit Type code must be valid. | ||
| Supplementary Unit Type code must be valid. | ||
| Unit Serial Block Start and Unit Serial Block End must be present. | ||
| Unit Serial Block End must be greater than or equal to the Unit Serial Block Start. | ||
| RMUs, ERUs converted from RMUs, tCERs and lCERs must have a valid LULUCF activity code. | ||
| AAUs, ERUs converted from AAUs and CERs must not have a LULUCF activity code. | ||
| ERUs, CERs, tCERs, and lCERs must have a valid Project ID. | ||
| AAUs or RMUs must not have a Project ID. | ||
| ERUs must have a valid "Track Code". | ||
| AAUs, RMUs, CERs, tCERs and lCERs must not have a track code. | ||
| AAUs, RMUs, ERUs and CERs must not have an Expiry Date. | ||
| Transaction ID for proposed transactions must not already exist in the CITL. | ||
| Transaction ID for ongoing transactions must already exist in the CITL. | ||
| Previous completed transactions cannot be completed again. | ||
| Previously rejected transactions cannot be completed. | ||
| Transactions for which a CITL discrepancy has been previously identified cannot be completed. | ||
| Previously terminated transactions cannot be completed. | ||
| Previously cancelled transactions cannot be completed. | ||
| Previously accepted external transactions cannot be terminated. | ||
| Transaction status of Accepted or Rejected is not valid for non-external transactions. | ||
| Transaction status from Initiating registry must indicate status of Proposed, Completed, or Terminated. | ||
| Transaction status from Acquiring registry for an External Transfer must indicate status of Rejected or Accepted. | ||
| Applicable Commitment Period must correspond to the current or next Commitment Period (including their "true-up" periods). | ||
| Units identified in the transaction must already exist in the CITL. | ||
| Units identified in the transaction must be held by Initiating registry. | ||
| All attributes of all unit blocks must be consistent with CITL unit block attributes except where attributes are changed by the current transaction. | ||
| All unit blocks in transaction must be for a single Applicable Commitment Period. | ||
| For all transactions except for external transfers, the Initiating and Acquiring Registries must be the same. | ||
| For external transfers, the Initiating and Acquiring Registries must be different. | ||
| Units identified in the transaction must not have inconsistencies identified through reconciliation with the CITL. | ||
| Units identified in the transaction must not be involved in another transaction. | ||
| Cancelled units must not be subject to further transactions. | ||
| A transaction proposal must contain at least one unit block. | ||
| A transaction must not issue more than one Unit Type. | ||
| The Original Commitment Period must be the same for all units issued by the transaction | ||
| The Applicable Commitment Period must be the same as the Original Commitment Period for all units issued by the transaction. | ||
| Cancellation to Excess Issuance Cancellation Account must not take place in a national registry. | ||
| The Acquiring Account for a cancellation transaction must be a cancellation account. | ||
| Account identifiers must be provided for acquiring accounts in cancellation transactions. | ||
| The unit blocks to be cancelled must have the same Applicable Commitment Period as the cancellation Account. | ||
| The Initiating registry retiring units must be a national registry or the Community Registry. | ||
| The Acquiring Account for a retirement transaction must be a retirement account. | ||
| Account identifiers must be provided for acquiring accounts in retirement transactions. | ||
| The Unit Blocks retired must have the same Applicable Commitment as the Retirement Account. | ||
| The Initiating registry carrying over units must be a national registry. | ||
| The Initiating Account for a carry-over transaction must be a holding account. | ||
| Units may be carried-over only to the next subsequent commitment period. | ||
| Reconciliation Identifier must be greater than zero. | ||
| Reconciliation ID must be comprised of a valid registry code followed by numeric values. | ||
| Reconciliation status must be a value between 1 and 11. | ||
| Reconciliation snapshot must be a date between | ||
| Account Type must be valid. | ||
| Reconciliation ID must exist in the Reconciliation Log table. | ||
| Reconciliation status sent by registry must be valid. | ||
| Incoming reconciliation status must be the same as the reconciliation status recorded by the CITL. | ||
| The registry reconciliation snapshot DateTime must be consistent with the CITL Reconciliation Snapshot DateTime. |
(a) Unit tests: individual components shall be tested against their specifications. (b) Integration tests: groups of components, comprising parts of the complete system, shall be tested against their specifications. (c) System tests: the system as a whole shall be tested against its specifications. (d) Load tests: the system shall be subjected to peaks in activity reflecting the likely demands that will be made on the system by its users. (e) Security testing: any security weaknesses of the system shall be identified.
(a) Authentication tests: the ability of the registry to identify the Community independent transaction log, and vice versa, shall be tested. (b) Time synchronisation tests: the ability of the registry to establish its system time and to change its system time in order to be consistent with the system time of the Community independent transaction log and UNFCCC independent transaction log shall be tested. (c) Data format tests: the ability of the registry to generate messages corresponding to the appropriate process status and stage and to the appropriate format, set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC, shall be tested. (d) Programming code and database operations tests: the ability of the registry to process messages received which correspond to the appropriate format, set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC, shall be tested. (e) Integrated process testing: the ability of the registry to execute all processes, including all relevant statuses and stages set out in Annexes VIII to XI and XIa, and to allow manual interventions to the database pursuant to Annex X, shall be tested. (f) Data logging tests: the ability of the registry to establish and maintain the records required pursuant to Article 73(2) shall be tested.
(a) Name, address, city, postcode, country, telephone number, facsimile number and e-mail address of the registry administrator for its registry. (b) Address, city, postcode and country of the physical location of the registry. (c) The uniform resource locator (URL) and the port(s) of both the secure area and public area of the registry, and the URL and the port(s) of the testing area. (d) Description of the primary and backup hardware and software used by the registry, and of the hardware and software supporting the testing area pursuant to Article 68. (e) Description of the systems and procedures for the safeguarding of all data, including the frequency with which a backup of the database is undertaken, and the systems and procedures for prompt recovery of all data and operations in the event of a disaster pursuant to Article 68. (f) Description of the security plan of the registry established pursuant to the general security requirements under Annex XV. (g) Description of the system and procedures of the registry in respect of change management pursuant to Article 72. (h) Information requested by the Central Administrator to enable the distribution of digital certificates pursuant to Annex XV.
(a) The total number of ERUs and CERs which operators are allowed to use for each period pursuant to Article 11a(1) of Directive 2003/87/EC. (b) The commitment period reserve, calculated in accordance with Decision 18/CP.7 of the Conference of the Parties to the UNFCCC as 90 per cent of the Member State’s assigned amount or 100 % of five times its most recently reviewed inventory, whichever is lowest. Any subsequent changes shall be promptly notified to the Commission.
(a) total number of allowances issued: in a single cell the total number of allowances that will be issued for the period covered by the national allocation plan. (b) total number of allowances not allocated to incumbents (reserve): in a single cell the total number of allowances (issued or purchased) that are set aside for new entrants and auctioning for the period covered by the national allocation plan. (c) years: in individual cells for each of the years covered in the national allocation plan in ascending order. (d) installation identification code: in individual cells in ascending order. The installations listed shall include installations unilaterally included under Article 24 of Directive 2003/87/EC and shall not include any installations temporarily excluded under Article 27 of Directive 2003/87/EC. (e) allocated allowances: the allowances to be allocated for a specified year for a specified installation shall be entered into the cell connecting that year to that installation's identification code.
(a) Secure transmission shall be achieved through the use of secure socket layer (SSL) technology with a minimum of 128 bit encryption. (b) The identity of each registry shall be authenticated using digital certificates for the requests originating from the Community independent transaction log. The identity of the Community independent transaction log shall be authenticated using digital certificates for each request originating from a registry. The identity of each registry shall be authenticated using a user name and password for each request originating from a registry. The identity of the Community independent transaction log shall be authenticated using a user name and password for each request originating from the Community independent transaction log. Digital certificates shall be registered as valid by the certification authority. Secure systems shall be used to store the digital certificates and usernames and passwords, and access shall be limited. Usernames and passwords shall have a minimum length of 10 characters and shall comply with the hypertext transfer protocol (HTTP) basic authentication scheme (http://www.ietf.org/rfc/rfc2617.txt).
(a) Secure transmission shall be achieved through the use of secure socket layer (SSL) technology with a minimum of 128 bit encryption. (b) The identity of each authorised representative shall be authenticated through the use of usernames and passwords, which are registered as valid by the registry.
(a) At any time, each authorised representative shall have a unique username and a unique password. (b) The registry administrator shall maintain a list of all authorised representatives who have been granted access to the registry and their access rights within that registry. (c) The number of authorised representatives of the Central Administrator and registry administrator shall be kept to a minimum and access rights shall be allocated solely on the basis of enabling administrative tasks to be performed. (d) Any default vendor passwords with Central Administrator or registry administrator access rights shall be changed immediately after installation of the software and hardware for the Community independent transaction log or registry. (e) Authorised representatives shall be required to change any temporary passwords they have been given upon accessing the secure area of the Community independent transaction log or registry for the first time, and thereafter shall be required to change their passwords every two months at a minimum. (f) The password management system shall maintain a record of previous passwords for an authorised representative and prevent re-use of the previous ten passwords for that authorised representative. Passwords shall have a minimum length of 8 characters and be a mix of numeric and alphabetical characters. (g) Passwords shall not be displayed on a computer screen when being entered by an authorised representative, and password files shall not be directly visible to an authorised representative of the Central Administrator or registry administrator.
(a) A firewall shall protect the Community independent transaction log and each registry from the Internet, and shall be configured as strictly as is possible to limit traffic to and from the Internet. (b) The Community independent transaction log and each registry shall run regular virus scans on all nodes, workstations and servers within their networks. Anti-virus software shall be updated regularly. (c) The Community independent transaction log and each registry shall ensure that all node, workstation and server software is correctly configured and routinely patched as security and functional updates are released. (d) When necessary, the Community independent transaction log and each registry shall apply additional security requirements to ensure that the registry system is able to respond to new security threats.
(a) name, address, city, postcode, country, telephone number and email address of the account holder. (b) alphanumeric identifier: the identifier specified by the account holder assigned to each account; (c) name, address, city, postcode, country, telephone number, facsimile number and email address of the primary and secondary authorised representatives of the account specified by the account holder for that account, provided that the account holder requested the registry administrator in writing to display all or some of this information.
(a) points 1 to 4.1, 4.4 to 5.5 and point 7 (activity 1) of the information identifying the installation related to the operator holding account as listed in section 11.1 of Annex I to Commission Decision 2004/156/EC; (b) permit identification code: the code assigned to the installation related to the operator holding account comprising the elements set out in Annex VI; (c) installation identification code: the code assigned to the installation related to the operator holding account comprising the elements set out in Annex VI; (d) allowances and any force majeure allowances allocated and issued to the installation related to the operator holding account, which is part of the national allocation plan table or is a new entrant, under Article 11 of Directive 2003/87/EC and any corrections to such allocations;(e) The date of the greenhouse gas permit's entry into force and the date of the opening of the account.
(a) verified emissions figure, along with its corrections for the installation related to the operator holding account for year X shall be displayed from 1 April onwards of year (X+1), or if 1 April falls on a weekend or on a holiday, then the verified emissions figure shall be displayed from the first working day following 1 April.; (b) units surrendered pursuant to Articles 52 and 53, by unit identification code (in the case of ERUs and CERs), for year X shall be displayed from 1 May onwards of year (X+1); (c) a symbol identifying whether the installation related to the operator holding account did or did not surrender the necessary number of allowances for year X by 30 April of year (X+1) in accordance with point (e) of Article 6(2) of Directive 2003/87/EC and any subsequent changes to that status pursuant to corrections to verified emissions in accordance with Article 51 (4) of this Regulation shall be displayed from 15 May onwards of year (X+1). Depending on the installation's compliance status figure and the registry's operational status, the following symbols shall be displayed together with the following statements: Table XVI-1: compliance statements Compliance status figure for year X under Article 55 on 30 April of year (X+1) Symbol Statement to be displayed on CITL and registries Total surrendered allowances in accordance with Articles 52, 53, 54 for period ≥ verified emissions in period until current year A "A number of allowances and Kyoto units greater than or equal to verified emissions were surrendered by 30 April" Total surrendered allowances in accordance with Articles 52, 53 and 54 for period < verified emissions in period until current year B "A number of allowances and Kyoto units lower than verified emissions were surrendered by 30 April" C "Verified emissions were not entered until 30 April" Verified emissions in period until current year were corrected pursuant to Article 51 D "Verified emissions were corrected by competent authority after 30 April of year X. The competent authority of the Member State decided that the installation is not in compliance for year X." Verified emissions in period until current year were corrected pursuant to Article 51 E "Verified emissions were corrected by competent authority after 30 April of year X. The competent authority of the Member State decided that the installation is in compliance for year X." X "Entering verified emissions and/or surrendering was impossible until 30 April due to the allowance surrender process and/or verified emissions update process being suspended for the Member State's registry in accordance with Article 6(3)" (d) a symbol indicating if the installation’s account is blocked in accordance with Article 27(1) shall be displayed from 31 March onwards of year (X+1).
(a) the national allocation plan table of each Member State, indicating the allocations to installations and the quantity of allowances reserved for later allocation or sale shall be displayed and updated whenever there is a correction to the national allocation plan table, clearly indicating where corrections were made; (b) the fees charged for the creating and annual maintenance of holding accounts in each registry. Updates to this information shall be notified to the Central Administrator by the registry administrator within 15 working days of any change in fees; (c) the type of Kyoto units that may be held by operator and person holding accounts in registries.
(a) project name: a unique name for the project; (b) project location: the Member State and town or region in which the project is located; (c) years of ERU issuance: the years in which ERUs have been issued as a result of the project activity implemented pursuant to Article 6 of the Kyoto Protocol; (d) reports: downloadable electronic versions of all publicly available documentation relating to the project, including proposals, monitoring, verification and issuance of ERUs, where relevant, subject to the confidentiality provisions in Decision -/CMP.1 [Article 6] of the Conference of the Parties to the UNFCCC serving as the meeting of the Parties to the Kyoto Protocol; (e) any set-aside table drawn up in accordance with Commission Decision 2006/780/EC OJ L 316, 16.11.2006, p. 12 .
(a) the total quantity of ERUs, CERs, AAUs and RMUs held in each account (person holding, operator holding, Party holding, cancellation, replacement or retirement) on 1 January of year X shall be displayed from 15 January onwards of year (X+5); (b) the total quantity of AAUs issued in year X on the basis of the assigned amount pursuant to Article 7 of Decision No 280/2004/EC shall be displayed from 15 January onwards of year (X+1); (c) the total quantity of ERUs issued in year X on the basis of project activity implemented pursuant to Article 6 of the Kyoto Protocol shall be displayed from 15 January onwards of year (X+1); (d) the total quantity of ERUs, CERs, AAUs and RMUs acquired from other registries in year X and the identity of the transferring accounts and registries shall be displayed from 15 January onwards of year (X+5); (e) the total quantity of RMUs issued in year X on the basis of each activity under Article 3, paragraphs 3 and 4 of the Kyoto Protocol shall be displayed from 15 January onwards of year (X+1); (f) the total quantity of ERUs, CERs, AAUs and RMUs transferred to other registries in year X and the identity of the acquiring accounts and registries shall be displayed from 15 January onwards of year (X+5); (g) the total quantity of ERUs, CERs, AAUs and RMUs cancelled in year X on the basis of activities under Article 3, paragraphs 3 and 4 of the Kyoto Protocol shall be displayed from 15 January onwards of year (X+1); (h) the total quantity of ERUs, CERs, AAUs and RMUs cancelled in year X following determination by the compliance committee under the Kyoto Protocol that the Member State is not in compliance with its commitment under Article 3, paragraph 1 of the Kyoto Protocol shall be displayed from 15 January onwards of year (X+1); (i) the total quantity of other ERUs, CERs, AAUs and RMUs, or allowances, cancelled in year X and the reference to the Article pursuant to which these Kyoto units or allowances were cancelled under this Regulation shall be displayed from 15 January onwards of year (X+1); (j) the total quantity of ERUs, CERs, AAUs, RMUs and allowances retired in year X shall be displayed from 15 January onwards of year (X+1); (k) the total quantity of ERUs, CERs, AAUs carried over in year X from the previous commitment period shall be displayed from 15 January onwards of year (X+1); (l) the total quantity of allowances from the previous commitment period cancelled and replaced in year X shall be displayed from 15 May onwards of year X; (m) current holdings of ERUs, CERs, AAUs and RMUs in each account (person holding, operator holding, Party holding, cancellation or retirement) on 31 December of year X shall be displayed from 15 January onwards of year (X+5).
(a) The Central Administrator shall make available on the public area of the Community independent transaction log's website the following information: (b) account identification code of the acquiring account: the code assigned to the account comprising the elements set out in Annex VI; (c) account holder name of the transferring account: the holder of the account (person, operator, Commission, Member State); (d) account holder name of the acquiring account: the holder of the account (person, operator, Commission, Member State); (e) allowances or Kyoto units involved in the transaction by unit identification code comprising the elements set out in Annex VI; (f) transaction identification code: the code assigned to the transaction comprising the elements set out in Annex VI; (g) date and time at which the transaction was completed (in Greenwich Mean Time); (h) process type: the categorisation of a process comprising the elements set out in Annex VII.
the percentage share of allowances surrendered in each Member State in the preceding calendar year that were surrendered from the account to which they were allocated to, the sum of verified emissions by Member State entered for the preceding calendar year as a percentage of the sum of verified emissions of the year before that year, the percentage share belonging to accounts administered by a particular Member State in the number and volume of all allowance and Kyoto unit transfer transactions in the preceding calendar year, the percentage share belonging to accounts administered by a particular Member State in the number and volume of all allowance and Kyoto unit transfer transactions in the preceding calendar year between accounts administered by different Member States.
(a) current holdings of allowances or Kyoto units; (b) list of proposed transactions initiated by that account holder, detailing for each proposed transaction the elements in paragraph 12(a) to (f), the date and time at which the transaction was proposed (in Greenwich Mean Time), the current status of that proposed transaction and any response codes returned consequent to the checks made pursuant to Annex IX; (c) list of allowances or Kyoto units acquired by that account as a result of completed transactions, detailing for each transaction the elements in paragraph 12(a) to (g); (d) list of allowances or Kyoto units transferred out of that account as a result of completed transactions, detailing for each transaction the elements in paragraph 12(a) to (g).