EUR-Lex Access to European Union law

Back to EUR-Lex homepage

This document is an excerpt from the EUR-Lex website

Document 01985R3821-20141101

Consolidated text: Council Regulation (EEC) No 3821/85 of 20 December 1985 on recording equipment in road transport

ELI: http://data.europa.eu/eli/reg/1985/3821/2014-11-01

1985R3821 — EN — 01.11.2014 — 018.001


This document is meant purely as a documentation tool and the institutions do not assume any liability for its contents

►B

COUNCIL REGULATION (EEC) No 3821/85

of 20 December 1985

on recording equipment in road transport

(OJ L 370 31.12.1985, p. 8)

Amended by:

 

 

Official Journal

  No

page

date

►M1

COMMISSION REGULATION (EEC) No 3314/90 of 16 November 1990

  L 318

20

17.11.1990

►M2

COUNCIL REGULATION (EEC) No 3572/90 of 4 December 1990

  L 353

12

17.12.1990

►M3

COMMISSION REGULATION (EEC) No 3688/92 of 21 December 1992

  L 374

12

22.12.1992

►M4

COMMISSION REGULATION (EC) No 2479/95 of 25 October 1995

  L 256

8

26.10.1995

►M5

COMMISSION REGULATION (EC) No 1056/97 of 11 June 1997

  L 154

21

12.6.1997

►M6

COUNCIL REGULATION (EC) No 2135/98 of 24 September 1998

  L 274

1

9.10.1998

►M8

COMMISSION REGULATION (EC) No 1360/2002 of 13 June 2002

  L 207

1

5.8.2002

 M9

REGULATION (EC) No 1882/2003 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 29 September 2003

  L 284

1

31.10.2003

►M10

COMMISSION REGULATION (EC) No 432/2004 of 5 March 2004

  L 71

3

10.3.2004

►M11

REGULATION (EC) No 561/2006 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 15 March 2006

  L 102

1

11.4.2006

►M12

COUNCIL REGULATION (EC) No 1791/2006 of 20 November 2006

  L 363

1

20.12.2006

►M13

COMMISSION REGULATION (EC) No 68/2009 of 23 January 2009

  L 21

3

24.1.2009

►M14

REGULATION (EC) No 219/2009 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 11 March 2009

  L 87

109

31.3.2009

►M15

COMMISSION REGULATION (EU) No 1266/2009 of 16 December 2009

  L 339

3

22.12.2009

►M16

COUNCIL REGULATION (EU) No 517/2013 of 13 May 2013

  L 158

1

10.6.2013

►M17

COMMISSION REGULATION (EU) No 1161/2014 of 30 October 2014

  L 311

19

31.10.2014


Amended by:

 A1

ACT concerning the conditions of accession of the Kingdom of Norway, the Republic of Austria, the Republic of Finland and the Kingdom of Sweden and the adjustments to the Treaties on which the European Union is founded 94/C 241/08

  C 241

21

29.8.1994

 

  L 001

1

..

►A2

ACT concerning the conditions of accession of the Czech Republic, the Republic of Estonia, the Republic of Cyprus, the Republic of Latvia, the Republic of Lithuania, the Republic of Hungary, the Republic of Malta, the Republic of Poland, the Republic of Slovenia and the Slovak Republic and the adjustments to the Treaties on which the European Union is founded

  L 236

33

23.9.2003


Corrected by:

 C1

Corrigendum, OJ L 049, 25.2.1999, p.  46  (2135/1998)

►C2

Corrigendum, OJ L 077, 13.3.2004, p.  71 (1360/2002)




▼B

COUNCIL REGULATION (EEC) No 3821/85

of 20 December 1985

on recording equipment in road transport



THE COUNCIL OF THE EUROPEAN COMMUNITIES,

Having regard to the Treaty establishing the European Economic Community, and in particular Article 75 thereof,

Having regard to the proposal from the Commission ( 1 ),

Having regard to the opinion of the European Parliament ( 2 ),

Having regard to the opinion of the Economic and Social Committee ( 3 ),

Whereas Regulation (EEC) No 1463/70 ( 4 ) as last amended by Regulation (EEC) No 2828/77 ( 5 ) introduced recording equipment in road transport;

Whereas, taking into account the amendments set out hereinafter, in order to clarify matters, all the relevant provisions should be brought together in a single text, and in consequence thereof, Regulation (EEC) No 1463/70 of the Council should be repealed; whereas, however, the exemptions set out in Article 3 (1) for certain passenger services should be maintained in force for a certain time;

Whereas the use of recording equipment that may indicate the periods of time referred to in Regulation (EEC) No 3820/85 on the harmonization of certain social legislation relating to road transport ( 6 ) is intended to ensure effective checking on that social legislation;

Whereas the obligation to use such recording equipment can be imposed only for vehicles registered in Member States; whereas furthermore certain of such vehicles may, without giving rise to difficulty, be excluded from the scope of this Regulation;

Whereas the Member States should be entitled, with the Commission's authorization, to grant certain vehicles exemptions from the provisions of the Regulation in exceptional circumstances; whereas, in urgent cases, it should be possible to grant these exemptions for a limited time without prior authorization from the Commission;

Whereas, in order to ensure effective checking, the equipment must be reliable in operation, easy to use and designed in such a way as to minimize any possibility of fraudulent use; whereas to this end recording equipment should in particular be capable of providing, on separate sheets for each driver and in a sufficiently precise and easily readable form, recorded details of the various periods of time;

Whereas automatic recording of other details of a vehicle's journey, such as speed and distance covered, will contribute significantly to road safety and will encourage sensible driving of the vehicle; whereas, consequently, it appears appropriate to provide for the equipment also to record those details;

Whereas it is necessary to set Community construction and installation standards for recording equipment and to provide for an EEC approval procedure, in order to avoid throughout the territory of the Member States any impediment to the registration of vehicles fitted with such recording equipment, to their entry into service or use, or to such equipment being used;

Whereas, in the event of differences of opinion between Member States concerning cases of EEC type approval, the Commission should be empowered to take a decision on a dispute within six months if the States concerned have been unable to reach a settlement;

Whereas it would be helpful in implementing this Regulation and preventing abuses to issue drivers who so request with a copy of their record sheets;

Whereas, in order to achieve the aims hereinbefore mentioned of keeping a check on work and rest periods, it is necessary that employers and drivers be responsible for seeing that the equipment functions correctly and that they perform with due care the operations prescribed;

Whereas the provisions governing the number of record sheets that a driver must keep with him must be amended following the replacement of the flexible week by a fixed week;

Whereas technical progress necessitates rapid adaptation of the technical specifications set out in the Annexes to this Regulation; whereas, in order to facilitate the implementation of the measures necessary for this purpose, provision should be made for a procedure establishing close cooperation between the Member States and the Commission within an Advisory Committee;

Whereas Member States should exchange the available information on breaches established;

Whereas, in order to ensure that recording equipment functions reliably and correctly, it is advisable to lay down uniform requirements for the periodic checks and inspections to which the equipment is to be subject after installation,

HAS ADOPTED THIS REGULATION:



CHAPTER I

Principles and scope

Article 1

Recording equipment within the meaning of this Regulation shall, as regards construction, installation, use and testing, comply with the requirements of this Regulation ►M6  and of Annexes I or IB and II thereto ◄ , which shall form an integral part of this Regulation.

▼M11

Article 2

For the purpose of this Regulation the definitions set out in Article 4 of Regulation (EC) No 561/2006 of the European Parliament and of the Council of 15 March 2006 on the harmonisation of certain social legislation relating to road transport and amending Council Regulations (EEC) No 3821/85 and (EC) No 2135/98 ( 7 ) shall apply.

▼B

Article 3

▼M11

1.  Recording equipment shall be installed and used in vehicles registered in a Member State which are used for the carriage of passengers or goods by road, except the vehicles referred to in Article 3 of Regulation (EC) No 561/2006. Vehicles referred to in Article 16(1) of Regulation (EC) No 561/2006 and vehicles, which were exempt from the scope of application of Regulation (EEC) No 3820/85, but which are no longer exempt under Regulation (EC) No 561/2006 shall have until 31 December 2007 to comply with this requirement.

2.  Member States may exempt vehicles mentioned in Articles 13(1) and (3) of Regulation (EC) No 561/2006 from application of this Regulation.

3.  Member States may, after authorisation by the Commission, exempt from application of this Regulation vehicles used for the transport operations referred to in Article 14 of Regulation (EC) No 561/2006.

▼B

4.  In the case of national transport operations, Member States may require the installation and use of recording equipment in accordance with this Regulation in any of the vehicles for which its installation and use are not required by paragraph 1.



CHAPTER II

Type approval

Article 4

▼M6

For the purposes of this Chapter, the words ‘recording equipment’ shall mean ‘recording equipment or its components’.

▼B

Applications for EEC approval of a type of recording equipment or of a model record sheet ►M6  or memory card ◄ shall be submitted, accompanied by the appropriate specifications, by the manufacturer or his agent to a Member State. No application in respect of any one type of recording equipment or of any one model record ►M6  or memory card ◄ sheet may be submitted to more than one Member State.

Article 5

▼M6

A Member State shall grant EC component type-approval to any type of recording equipment, to any model record sheet or memory card which conforms to the requirements laid down in Annex I or IB to this Regulation, provided the Member State is in a position to check that production models conform to the approved type.

▼M14

The system's security must comply with the technical requirements laid down in Annex IB. The Commission shall ensure that the said Annex stipulates that recording equipment may not be granted EC component type-approval until the whole system (the recording equipment itself, driver card and electrical gearbox connections) has demonstrated its capacity to resist attempts to tamper with or alter the data on driving times. Those measures, designed to amend non-essential elements of this Regulation, shall be adopted in accordance with the regulatory procedure with scrutiny referred to in Article 18(2). The tests necessary to establish this shall be carried out by experts familiar with up-to-date tampering techniques.

▼B

Any modifications or additions to an approved model must receive additional EEC type approval from the Member State which granted the original EEC type approval.

Article 6

Member States shall issue to the applicant an EEC approval mark, which shall conform to the model shown in Annex II, for each type of recording equipment or model record sheet ►M6  or memory card ◄ which they approve pursuant to Article 5.

Article 7

The competent authorities of the Member State to which the application for type approval has been submitted shall, in respect of each type of recording equipment or model record sheet ►M6  or memory card ◄ which they approve or refuse to approve, either send within one month to the authorities of the other Member States a copy of the approval certificate accompanied by copies of the relevant specifications, or, if such is the case, notify those authorities that approval has been refused; in cases of refusal they shall communicate the reasons for their decision.

Article 8

1.  If a Member State which has granted EEC type approval as provided for in Article 5 finds that certain recording equipment or record sheets ►M6  or memory cards ◄ bearing the EEC type approval mark which it has issued do not conform to the prototype which it has approved, it shall take the necessary measures to ensure that production models conform to the approved prototype. The measures taken may, if necessary, extend to withdrawal of EEC type approval.

2.  A Member State which has granted EEC type approval shall withdraw such approval if the recording equipment or record sheet ►M6  or memory card ◄ which has been approved is not in conformity with this Regulation or its Annexes or displays in use any general defect which makes it unsuitable for the purpose for which it is intended.

3.  If a Member State which has granted EEC type approval is notified by another Member State of one of the cases referred to in paragraphs 1 and 2, it shall also, after consulting the latter Member State, take the steps laid down in those paragraphs, subject to paragraph 5.

4.  A Member State which ascertains that one of the cases referred to in paragraph 2 has arisen may forbid until further notice the placing on the market and putting into service of the recording equipment or record sheets ►M6  or memory cards ◄ . The same applies in the cases mentioned in paragraph 1 with respect to recording equipment or record sheets ►M6  or memory cards ◄ which have been exempted from EEC initial verification, if the manufacturer, after due warning, does not bring the equipment into line with the approved model or with the requirements of this Regulation.

In any event, the competent authorities of the Member States shall notify one another and the Commission, within one month, of any withdrawal of EEC type approval or of any other measures taken pursuant to paragraphs 1, 2 and 3 and shall specify the reasons for such action.

5.  If a Member State which has granted an EEC type approval disputes the existence of any of the cases specified in paragraphs 1 or 2 notified to it, the Member States concerned shall endeavour to settle the dispute and the Commission shall be kept informed.

If talks between the Member States have not resulted in agreement within four months of the date of the notification referred to in paragraph 3 above, the Commission, after consulting experts from all Member States and having considered all the relevant factors, e.g. economic and technical factors, shall within six months adopt a decision which shall be communicated to the Member States concerned and at the same time to the other Member States. The Commission shall lay down in each instance the time limit for implementation of its decision.

Article 9

1.  An applicant for EEC type approval of a model record sheet shall state on his application the type or types of recording equipment on which the sheet in question is designed to be used and shall provide suitable equipment of such type or types for the purpose of testing the sheet.

2.  The competent authorities of each Member State shall indicate on the approval certificate for the model record sheet the type or types of recording equipment on which that model sheet may be used.

Article 10

No Member State may refuse to register any vehicle fitted with recording equipment, or prohibit the entry into service or use of such vehicle for any reason connected with the fact that the vehicle is fitted with such equipment, if the equipment bears the EEC approval mark referred to in Article 6 and the installation plaque referred to in Article 12.

Article 11

All decisions pursuant to this Regulation refusing or withdrawing approval of a type of recording equipment or model record sheet ►M6  or memory card ◄ shall specify in detail the reasons on which they are based. A decision shall be communicated to the party concerned, who shall at the same time be informed of the remedies available to him under the laws of the Member States and of the time-limits for the exercise of such remedies.



CHAPTER III

Installation and inspection

Article 12

1.  Recording equipment may be installed or repaired only by fitters or workshops approved by the competent authorities of Member States for that purpose after the latter, should they so desire, have heard the views of the manufacturers concerned.

▼M6

The period of administrative validity of approved workshop and fitter cards shall not exceed one year.

If a card issued to an approved workshop or fitter is to be extended, is damaged, malfunctions, is lost or is stolen, the authority shall supply a replacement card within five working days of receiving a detailed request to that effect.

Where a new card is issued to replace an old one, the new card shall bear the same ‘workshop’ information number, but the index shall be increased by one. The authority issuing the card shall maintain a register of lost, stolen or defective cards.

Member States shall take any measure necessary to prevent the cards distributed to approved fitters and workshops from being falsified.

▼M6

2.  The approved fitter or workshop shall place a special mark on the seals which it affixes and, in addition, shall enter for recording equipment in conformity with Annex IB, the electronic security data for carrying out, in particular, the authentication checks. The competent authorities of each Member State shall maintain a register of the marks and electronic security data used and of approved workshop and fitter cards issued.

3.  The competent authorities of the Member States shall forward to the Commission the lists of approved fitters and workshops and the cards issued to them and shall forward to it copies of the marks and of the necessary information relating to the electronic security data used.

▼B

4.  For the purpose of certifying that installation of recording equipment took place in accordance with the requirements of this Regulation an installation plaque affixed as provided in ►M6  Annexes I and IB ◄ shall be used.

▼M3

5.  Any seal may be removed by the fitters or workshops approved by competent authorities under paragraph 1 of this Article, or in the circumstances described in Annex I, Chapter V, paragraph 4 ►M6  or in Annex IB section VI(c) ◄ to this Regulation.

▼B



CHAPTER IV

Use of equipment

▼M6

Article 13

The employer and drivers shall ensure the correct functioning and proper use of, on the one hand, the recording equipment and, on the other, the driver card where a driver is required to drive a vehicle fitted with recording equipment in conformity with Annex IB.

▼B

Article 14

▼M6

1.  The employer shall issue a sufficient number of record sheets to drivers of vehicles fitted with recording equipment in conformity with Annex I, bearing in mind the fact that these sheets are personal in character, the length of the period of service and the possible obligation to replace sheets which are damaged, or have been taken by an authorised inspecting officer. The employer shall issue to drivers only sheets of an approved model suitable for use in the equipment installed in the vehicle.

Where the vehicle is fitted with recording equipment in conformity with Annex IB, the employer and the driver shall ensure that, taking into account the length of the period of service, the printing on request referred to in Annex IB can be carried out correctly in the event of an inspection.

▼M11

2.  The undertaking shall keep record sheets and printouts, whenever printouts have been made to comply with Article 15(1), in chronological order and in a legible form for at least a year after their use and shall give copies to the drivers concerned who request them. The undertaking shall also give copies of downloaded data from the driver cards to the drivers concerned who request them and the printed papers of these copies. The record sheets, printouts and downloaded data shall be produced or handed over at the request of any authorised inspecting officer.

▼M6

3.  The driver card as defined in Annex IB shall be issued, at the request of the driver, by the competent authority of the Member State where the driver has his normal residence.

A Member State may require any driver subject to the provisions of Regulation (EEC) No 3820/85 and normally resident on its territory to hold a driver card.

(a) For the purposes of this Regulation ‘normal residence’ means the place where a person usually lives, that is for at least 185 days in each calendar year, because of personal and occupational ties, or, in the case of a person with no occupational ties, because of personal ties which show close links between that person and the place where he is living.

However, the normal residence of a person whose occupational ties are in a different place from his personal ties and who consequently lives in turn in differnt places situated in two or more Member States shall be regarded as being the place of his personal ties, provided that such person returns there regularly. This last condition need not be met where the person is living in a Member State in order to carry out a fixed-term assignment.

(b) Drivers shall give proof of their place of normal residence by any appropriate means, such as their identity card or any other valid document.

(c) Where the competent authorities of the Member State issuing the driver card have doubts as to the validity of a statement as to normal residence made in accordance with point (b), or for the purpose of ceratin specific controls, they may request any additional information or evidence.

(d) The competent authorities of the issuing Member State shall, as far as this can be done, ensure that the applicant does not already hold a valid driver card.

4.  

(a) The competent authority of the Member State shall personalise the driver card in accordance with the provisions of Annex IB.

For administarative purposes, the driver card may not be valid for more than five years.

The driver may hold one valid driver card only. The driver is authorised to use only his own personalised driver card. The driver shall not use a driver card which is defective or which has expired.

When a new driver card is issued replacing the old, the new card shall bear the same driver card issue number but the index shall be increased by one. The issuing authority shall keep records of issued, stolen, lost or defective driver cards for a period at least equivalent to their period of administrative validity.

If the driver card is damaged, malfunctions or is lost or stolen, the authority shall supply a replacement card within five working days of receiving a detailed request to that effect.

In the event of a request for the renewal of a card whose expiry date is approaching, the authority shall supply a new card before the expiry date provided that the request was sent to it within the time limits laid down in the second subparagraph of Article 15(1).

(b) Driver cards shall be issued only to applicants who are subject to the provisions of Regulation (EEC) No 3820/85.

(c) The driver card shall be personal. It may not, during its official period of validity, be withdrawn or suspended for whatever reason unless the competent authority of a Member State finds that the card has been falsified, or the driver is using a card of which he is not the holder, or that the card held has been obtained on the basis of false declarations and/or forged documents. If such suspension or withdrawal measures are taken by a Member State other than the Member State of issue, the former shall return the card to the authorities of the Member State which issued it and shall indicate the reasons for returning it.

(d) Driver cards issued by Member States shall be mutually recognised.

Where the holder of a valid driver card issued by a Member State has established his normal place of residence in another Member State, he may ask for his card to be exchanged for an equivalent driver card; it shall be the responsibility of the Member State which carries out the exchange to verify if necessary whether the card produced is actually still valid.

Member States carrying out an exchange shall return the old card to the authorities of the Member State of issue and inidcate the reasons for so doing.

(e) Where a Member State replaces or exchanges a driver card, the replacement or exchange, and any subsequent replacement or renewal, shall be registered in that Member State.

(f) Member States shall take all the necessary measures to prevent any possibility of driver cards being falsified.

5.  Member States shall ensure that data needed to monitor compliance with Regulation (EEC) No 3820/85 and Council Directive 92/6/EEC of 10 February 1992 on the installation and use of speed limitation devices for certain categories of motor vehicles in the Community ( 8 ) which are recorded and stored by recording equipment in conformity with Annex IB to this Regulation can be made available for at least 365 days after the date of their recording and that they can be made available under conditions that guarantee the security and accuracy of the data.

Member States shall take any measures necessary to ensure that the resale or decommissioning of recording equipment cannot detract, in particular, from the satisfactory application of this paragraph.

▼B

Article 15

1.  Drivers shall not use dirty or damaged record sheets ►M6  or driver cards ◄ . The sheets ►M6  or driver cards ◄ shall be adequately protected on this account.

▼M6

Where a driver wishes to renew his driver card, he shall apply to the competent authorities of the Member State in which he has his normal residence not later than 15 working days before the expiry date of the card.

▼B

In case of damage to a sheet bearing recordings ►M6  or driver card ◄ , drivers shall attach the damaged sheet ►M6  or driver card ◄ to the spare sheet used to replace it.

▼M6

If the driver card is damaged, malfunctions or is lost or stolen, the driver shall apply within seven calendar days for its replacement to the competent authorities of the Member State in which he has his normal residence.

▼M11

Where a driver card is damaged, malfunctions, or is not in the possession of the driver, the driver shall:

(a) at the start of his journey, print out the details of the vehicle the driver is driving, and shall enter onto that printout:

(i) details that enable the driver to be identified (name, driver card or driver's licence number), including his signature;

(ii) the periods referred to in paragraph 3, second indent (b), (c) and (d);

(b) at the end of his journey, print out the information relating to periods of time recorded by the recording equipment, record any periods of other work, availability and rest undertaken since the printout that was made at the start of the journey, where not recorded by the tachograph, and mark on that document details that enable the driver to be identified (name, driver card or driver's licence number), including the driver's signature.

▼B

2.  Drivers shall use the record sheets ►M6  or driver cards ◄ every day on which they are driving, starting from the moment they take over the vehicle. The record sheet ►M6  or driver card ◄ shall not be withdrawn before the end of the daily working period unless its withdrawal is otherwise authorized. No record sheet ►M6  or driver card ◄ may be used to cover a period longer than that for which it is intended.

▼M11

When as a result of being away from the vehicle, a driver is unable to use the equipment fitted to the vehicle, the periods of time referred to in paragraph 3, second indent (b), (c) and (d) shall:

(a) if the vehicle is fitted with recording equipment in conformity with Annex I, be entered on the record sheet, either manually, by automatic recording or other means, legibly and without dirtying the sheet; or

(b) if the vehicle is fitted with recording equipment in conformity with Annex IB, be entered onto the driver card using the manual entry facility provided in the recording equipment.

Where there is more than one driver on board the vehicle fitted with recording equipment in conformity with Annex IB, each driver shall ensure that his driver card is inserted into the correct slot in the tachograph.

▼B

Drivers shall amend the record sheets as necessary should there be more than one driver on board the vehicle, so that the information referred to in Chapter II (1) to (3) of Annex I is recorded on the record sheet of the driver who is actually driving.

3.  Drivers shall:

 ensure that the time recorded on the sheet agrees with the official time in the country of registration of the vehicle,

 operate the switch mechanisms enabling the following periods of time to be recorded separately and distinctly:

 

(a) under the sign image: driving time;

▼M11

(b) ‘other work’ means any activity other than driving, as defined in Article 3(a) of Directive 2002/15/EC of the European Parliament and of the Council of 11 March 2002 on the organisation of the working time of persons performing mobile road transport activities ( 9 ), and also any work for the same or another employer within or outside of the transport sector, and must be recorded under this sign

image;

(c) ‘availability’ defined in Article 3(b) of Directive 2002/15/EC must be recorded under this sign image;

▼B

(d) under the sign image: breaks in work and daily rest periods.

▼M11 —————

▼B

5.  Each crew member shall enter the following information on his record sheet:

(a) on beginning to use the sheet — his surname and first name;

(b) the date and place where use of the sheet begins and the date and place where such use ends;

(c) the registration number of each vehicle to which he is assigned, both at the start of the first journey recorded on the sheet and then, in the event of a change of vehicle, during use of the sheet;

(d) the odometer reading:

 at the start of the first journey recorded on the sheet,

 at the end of the last journey recorded on the sheet,

 in the event of a change of vehicle during a working day (reading on the vehicle to which he was assigned and reading on the vehicle to which he is to be assigned);

(e) the time of any change of vehicle.

▼M6

5a.  The driver shall enter in the recording equipment in conformity with Annex IB the symbols of the countries in which he begins and ends his daily work period. However, a Member State may require drivers of vehicles engaged in transport operations inside its territory to add more detailed geographic specifications to the country symbol provided that the Member State has notified them to the Commission before 1 April 1998 and that they do not number more than 20.

The above data entries shall be activated by the driver, and may be entirely manual or automatic if the recording equipment is linked to a satellite tracking system.

▼B

6.  The ►M6  recording equipment defined in Annex I ◄ shall be so designed that it is possible for an authorized inspecting officer, if necessary after opening the equipment, to read the recordings relating to the nine hours preceding the time of the check without permanently deforming, damaging or soiling the sheet.

The equipment shall, furthermore, be so designed that it is possible, without opening the case, to verify that recordings are being made.

▼M11

7.  

(a) Where the driver drives a vehicle fitted with recording equipment in conformity with Annex I, the driver must be able to produce, whenever an inspecting officer so requests:

(i) the record sheets for the current week and those used by the driver in the previous 15 days;

(ii) the driver card if he holds one, and

(iii) any manual record and printout made during the current week and the previous 15 days as required under this Regulation and Regulation (EC) No 561/2006.

However, after 1 January 2008, the time periods referred to under (i) and (iii) shall cover the current day and the previous 28 days.

(b) Where the driver drives a vehicle fitted with recording equipment in conformity with Annex IB, the driver must be able to produce, whenever an inspecting officer so requests:

(i) the driver card of which he is holder;

(ii) any manual record and printout made during the current week and the previous 15 days as required under this Regulation and Regulation (EC) No 561/2006, and

(iii) the record sheets corresponding to the same period as the one referred to in the previous subparagraph during which he drove a vehicle fitted with recording equipment in conformity with Annex I.

However, after 1 January 2008, the time periods referred to under (ii) shall cover the current day and the previous 28 days.

(c) An authorised inspecting officer may check compliance with Regulation (EC) No 561/2006 by analysis of the record sheets, of the displayed or printed data which have been recorded by the recording equipment or by the driver card or, failing this, by analysis of any other supporting document that justifies non-compliance with a provision, such as those laid down in Article 16(2) and (3).

▼M6

8.  It shall be forbidden to falsify, suppress or destroy data recorded on the record sheet, stored in the recording equipment or on the driver card, or print-outs from the recording equipment as defined in Annex IB. The same applies to any manipulation of the recording equipment, record sheet or driver card which may result in data and/or printed information being falsified, suppressed or destroyed. No device which could be used to this effect shall be present on the vehicle.

▼B

Article 16

1.  In the event of breakdown or faulty operation of the equipment, the employer shall have it repaired by an approved fitter or workshop, as soon as circumstances permit.

If the vehicle is unable to return to the premises within a period of one week calculated from the day of the breakdown or of the discovery of defective operation, the repair shall be carried out en route.

Measures taken by Member States pursuant to Article 19 may give the competent authorities power to prohibit the use of the vehicle in cases where breakown or faulty operation has not been put right as provided in the foregoing subparagraphs.

▼M6

2.  While the recording equipment is unserviceable or malfunctioning, drivers shall mark on the record sheet or sheets, or on a temporary sheet to be attached to the record sheet or to the driver card, on which he shall enter data enabling him to be identified (driver's card number and/or name and/or driving licence number), including his signature, all information for the various periods of time which are no longer recorded or printed out correctly by the recording equipment.

If a driver card is damaged, malfunctions or is lost or stolen, the driver shall, at the end of his journey, print out the information relating to the periods of time recorded by the recording equipment and mark on that document the details that enable him to be identified (the driver card number and/or name and/or driving licence number), including his signature.

▼M6

3.  If a driver card is damaged or if it malfunctions, the driver shall return it to the competent authority of the Member State in which he has his normal residence. Theft of the driver card shall be the subject of a formal declaration to the competent authorities of the State where the theft occurred.

Loss of the driver card must be reported in a formal declaration to the competent authorities of the State that issued it and to the competent authorities of the Member State of normal residence where they are different.

The diver may continue to drive without a driver card for a maximum period of 15 calendar days or for a longer period if this is necessary for the vehicle to return to its premises, provided he can prove the impossibility of producing or using the card during this period.

Where the authorities of the Member State in which the driver has his normal residence are different from those which issued his card and where the latter are requested to renew, replace or exchange the driver card, they shall inform the authorities which issued the old card of the precise reasons for its renewal, replacement or exchange.

▼B



CHAPTER V

Final provisions

▼M6

Article 17

▼M14

1.  The amendments required to adjust the annexes to technical progress, designed to amend non-essential elements of this Regulation, shall be adopted in accordance with the regulatory procedure with scrutiny referred to in Article 18(2).

▼M6

2.  The technical specifications relating to the following sections of Annex IB shall be adopted as soon as possible and if possible before 1 July 1998 by the same procedure:

(a) Chapter II

 (d) 17:

 

displaying and printing of faults in the recording equipment,

 (d) 18:

 

displaying and printing of faults in the driver card,

 (d) 21:

 

displaying and printing of summary reports;

(b) Chapter III

 (a) 6.3:

 

standards for the protection of vehicle electronics against electrical interference and magnetic fields,

 (a) 6.5:

 

protection (security) of the total system,

 (c) 1:

 

warning signals indicating the internal malfunctioning of the recording equipment,

 (c) 5:

 

format of the warnings,

 (f):

 

maximum tolerances;

(c) Chapter IV, A:

 4:

 

standards,

 5:

 

security, including data protection,

 6:

 

temperature range,

 8:

 

electrical characteristics,

 9:

 

logical structure of the driver card,

 10:

 

functions and commands,

 11:

 

elementary files;

and Chapter IV, B;

(d) Chapter V:

printer and standard print-outs.

▼M14

Article 18

1.  The Commission shall be assisted by a Committee.

2.  Where reference is made to this paragraph, Article 5a(1) to (4) and Article 7 of Decision 1999/468/EC shall apply, having regard to the provisions of Article 8 thereof.

▼B

Article 19

1.  Member States shall, in good time and after consulting the Commission, adopt such laws, regulations or administrative provisions as may be necessary for the implementation of this Regulation.

Such measures shall cover, inter alia, the reorganization of, procedure for, and means of carrying out, checks on compliance and the penalties to be imposed in case of breach.

2.  Member States shall assist each other in applying this Regulation and in checking compliance therewith.

3.  Within the framework of this mutual assistance the competent authorities of the Member States shall regularly send one another all available information concerning:

 breaches of this Regulation committed by non-residents and any penalties imposed for such breaches,

 penalties imposed by a Member State on its residents for such breaches committed in other Member States.

Article 20

Regulation (EEC) No 1463/70 shall be repealed.

However, Article 3 (1) of the said Regulation shall, until 31 December 1989, continue to apply to vehicles and drivers employed in regular international passenger services in so far as the vehicles used for such services are not fitted with recording equipment used as prescribed in this Regulation.

▼M2

Article 20a

This Regulation shall not apply until 1 January 1991 to vehicles registered in the territory of the former German Democratic Republic before that date.

This Regulation shall not apply until 1 January 1993 to such vehicles where they are engaged only in national transport operations in the territory of the Federal Republic of Germany. However, this Regulation shall apply as from its entry into force to vehicles engaged in the carriage of dangerous goods.

▼B

Article 21

This Regulation shall enter into force on 29 September 1986.

This Regulation shall be binding in its entirety and directly applicable in all Member States.




ANNEX I

REQUIREMENTS FOR CONSTRUCTION, TESTING, INSTALLATION AND INSPECTION

I.   DEFINITIONS

In this Annex:

(a)  Recording equipment means:

equipment intended for installation in road vehicles to show and record automatically or semi-automatically details of the movement of those vehicles and of certain working periods of their drivers;

(b)  Record sheet means:

a sheet designed to accept and retain recorded data, to be placed in the recording equipment and on which the marking devices of the latter inscribe a continuous record of the information to be recorded;

(c)  The constant of the recording equipment means:

the numerical characteristic giving the value of the input signal required to show and record a distance travelled of one kilometre; this constant must be expressed either in revolutions per kilometre (k = … rev/km), or in impulses per kilometre (k = … imp/km);

(d)  Characteristic coefficient of the means:

the numerical characteristic giving the value of the output signal emitted by the part of the vehicle linking it with the recording equipment (gearbox output shaft or axle) while the vehicle travels a distance of one measured kilometre under normal test conditions (see Chapter VI, point 4 of this Annex). The characteristic coefficient is expressed either in revolutions per kilometre (w = … rev/km) or in impulses per kilometre (w = … imp/km);

(e)  Effective circumference of wheel tyres means:

the average of the distances travelled by the several wheels moving the vehicle (driving wheels) in the course of one complete rotation. The measurement of these distances must be made under normal test conditions (see Chapter VI, point 4 of this Annex) and is expressed in the form: 1 = … mm.

II.   GENERAL CHARACTERISTICS AND FUNCTIONS OF RECORDING EQUIPMENT

The equipment must be able to record the following:

1. distance travelled by the vehicle;

2. speed of the vehicle;

3. driving time;

4. other periods of work or of availability;

5. breaks from work and daily rest periods;

6. opening of the case containing the record sheet ;

▼M1

7. for electronic recording equipment which is equipment operating by signals transmitted electrically from the distance and speed sensor, any interruption exceeding 100 milliseconds in the power supply of the recording equipment (except lighting), in the power supply of the distance and speed sensor and any interruption in the signal lead to the distance and speed sensor.

▼B

For vehicles used by two drivers the equipment must be capable of recording simultaneously but distinctly and on two separate sheets details of the periods listed under 3, 4 and 5.

III.   CONSTRUCTION REQUIREMENTS FOR RECORDING EQUIPMENT

(a)   General points

1.

Recording equipment shall include the following:

1.1.

Visual instruments showing:

 distance travelled (distance recorder),

 speed (speedometer),

 time (clock).

1.2.

Recording instruments comprising:

 a recorder of the distance travelled,

 a speed recorder,

 one or more time recorders satisfying the requirements laid down in Chapter III (c) 4.

▼M1

1.3.

A means of marking showing on the record sheet individually:

 each opening of the case containing that sheet,

 for electronic recording equipment, as defined in point 7 of Chapter II, any interruption exceeding 100 milliseconds in the power supply of the recording equipment (except lighting), not later than at switching-on the power supply again,

 for electronic recording equipment, as defined in point 7 of Chapter II, any interruption exceeding 100 milliseconds in the power supply of the distance and speed sensor and any interruption in the signal lead to the distance and speed sensor.

▼B

2.

Any inclusion in the equipment of devices additional to those listed above must not interfere with the proper operation of the mandatory devices or with the reading of them.

The equipment must be submitted for approval complete with any such additional devices.

3.

Materials

3.1. All the constituent parts of the recording equipment must be made of materials with sufficient stability and mechanical strength and stable electrical and magnetic characteristics.

3.2. Any modification in a constituent part of the equipment or in the nature of the materials used for its manufacture must, before being applied in manufacture, be submitted for approval to the authority which granted type-approval for the equipment.

4.

Measurement of distance travelled

The distances travelled may be measured and recorded either:

 so as to include both forward and reverse movement, or

 so as to include only forward movement.

Any recording of reversing movements must on no account affect the clarity and accuracy of the other recordings.

5.

Measurement of speed

5.1. The range of speed measurement shall be as stated in the type approval certificate.

5.2. The natural frequency and the damping of the measuring device must be such that the instruments showing and recording the speed can, within the range of measurement, follow acceleration changes of up to 2 m/s2, within the limits of accepted tolerances.

6.

Measurement of time (clock)

6.1. The control of the mechanism for resetting the clock must be located inside a case containing the record sheet; each opening of that case must be automatically recorded on the record sheet.

6.2. If the forward movement mechanism of the record sheet is controlled by the clock, the period during which the latter will run correctly after being fully wound must be greater by at least 10 % than the recording period corresponding to the maximum sheet-load of the equipment.

7.

Lighting and Protection

7.1 The visual instruments of the equipment must be provided with adequate non-dazzling lighting.

7.2. For normal conditions of use, all the internal parts of the equipment must be protected against damp and dust. In addition they must be made proof against tampering by means of casings capable of being sealed.

(b)   Visual instruments

1.   Distance travelled indicator (distance recorder)

1.1. The value of the smallest grading on the instrument showing distance travelled must be 0,1 kilometres. Figures showing hectometres must be clearly distinguishable from those showing whole kilometres.

1.2. The figures on the distance recorder must be clearly legible and must have an apparent height of at least 4 mm.

1.3. The distance recorder must be capable of reading up to at least 99 999,9 kilometres.

2.   Speed indicators (speedometer)

2.1. Within the range of measurement, the speed scale must be uniformly graduated by 1, 2, 5 or 10 kilometres per hour. The value of a speed graduation (space between two successive marks) must not exceed 10 % of the maximum speed shown on the scale.

2.2. The range indicated beyond that measured need not be marked by figures.

2.3. The length of each space on the scale representing a speed difference of 10 kilometres per hour must not be less than 10 millimetres.

2.4. On an indicator with a needle, the distance between the needle and the instrument face must not exceed three millimetres.

3.   Time indicator (clock)

The time indicator must be visible from outside the equipment and give a clear, plain and unambiguous reading.

(c)   Recording instruments

1.   General points

1.1.

All equipment, whatever the form of the record sheet (strip or disc) must be provided with a mark enabling the record sheet to be inserted correctly, in such a way as to ensure that the time shown by the clock and the time-marking on the sheet correspond.

1.2.

The mechanism moving the record sheet must be such as to ensure that the latter moves without play and can be freely inserted and removed.

1.3.

For record sheets in disc form, the forward movement device must be controlled by the clock mechanism. In this case, the rotating movement of the sheet must be continuous and uniform, with a minimum speed of seven millimetres per hour measured at the inner border of the ring marking the edge of the speed recording area.

In equipment of the strip type, where the forward movement device of the sheets is controlled by the clock mechanism the speed of rectilinear forward movement must be at least 10 millimetres per hour.

1.4.

Recording of the distance travelled, of the speed of the vehicle and of any opening of the case containing the record sheet or sheets must be automatic.

2.   Recording distance travelled

2.1. Every kilometre of distance travelled must be represented on the record by a variation of at least one millimetre on the corresponding coordinate.

2.2. Even at speeds reaching the upper limit of the range of measurement, the record of distances must still be clearly legible.

3.   Recording speed

3.1.

Whatever the form of the record sheet, the speed recording stylus must normally move in a straight line and at right angles to the direction of travel of the record sheet.

However, the movement of the stylus may be curvilinear, provided the following conditions are satisfied:

 the trace drawn by the stylus must be perpendicular to the average circumference (in the case of sheets in disc form) or to the axis (in the case of sheets in strip form) of the area reserved for speed recording,

 the ratio between the radius of curvature of the trace drawn by the stylus and the width of the area reserved for speed recording must be not less than 2,4 to 1 whatever the form of the record sheet,

 the markings on the time-scale must cross the recording area in a curve of the same radius as the trace drawn by the stylus. The spaces between the markings on the time-scale must represent a period not exceeding one hour.

3.2.

Each variation in speed of 10 kilometres per hour must be represented on the record by a variation of at least 1,5 millimetres on the corresponding coordinate.

4.   Recording time

▼M1

4.1.

Recording equipment must be so constructed that the period of driving time is always recorded automatically and that it is possible, through the operation where necessary of a switch device to record separately the other periods of time as indicated in Article 15 (3), second indent (b), (c) and (d) of the Regulation.

▼B

4.2.

It must be possible, from the characteristics of the traces, their relative positions and if necessary the signs laid down in Article 15 of the Regulation to distinguish clearly between the various periods of time.

The various periods of time should be differentiated from one another on the record by differences in the thickness of the relevant traces, or by any other system of at least equal effectiveness from the point of view of legibility and ease of interpretation of the record.

4.3.

In the case of vehicles with a crew consisting of more than one driver, the recordings provided for in point 4.1 must be made on two separate sheets, each sheet being allocated to one driver. In this case, the forward movement of the separate sheets must be effected either by a single mechanism or by separate synchronized mechanisms.

(d)   Closing device

1. The case containing the record sheet or sheets and the control of the mechanism for resetting the clock must be provided with a lock.

2. Each opening of the case containing the record sheet or sheets and the control of the mechanism for resetting the clock must be automatically recorded on the sheet or sheets.

(e)   Markings

1.

The following markings must appear on the instrument face of the equipment:

 close to the figure shown by the distance recorder, the unit of measurement of distance, indicated by the abbreviation ‘km’,

 near the speed scale, the marking ‘km/h’,

 the measurement range of the speedometer in the form ‘Vmin … km/h, Vmax … km/h’, This marking is not necessary if it is shown on the descriptive plaque of the equipment.

However, these requirements shall not apply to recording equipment approved before 10 August 1970.

2.

The descriptive plaque must be built into the equipment and must show the following markings, which must be visible on the equipment when installed:

 name and address of the manufacturer of the equipment,

 manufacturer's number and year of construction,

 approval mark for the equipment type,

 the constant of the equipment in the form ‘k = … rev/km’or ‘k = … imp/km’,

 optionally, the range of speed measurement, in the form indicated in point 1,

 should the sensitivity of the instrument to the angle of inclination be capable of affecting the readings given by the equipment beyond the permitted tolerances, the permissible angle expressed as:

  image

 where α is the angle measured from the horizontal position of the front face (fitted the right way up) of the equipment for which the instrument is calibrated, while β and γ represent respectively the maximum permissible upward and downward deviations from the angle of calibration α .

(f)   Maximum tolerances (visual and recording instruments)

1.

On the test bench before installation:

(a) distance travelled:

1 % more or less than the real distance, where that distance is at least one kilometre;

(b) speed:

3 km/h more or less than the real speed;

(c) time:

± two minutes per day with a maximum of 10 minutes per seven days in cases where the running period of the clock after rewinding is not less than that period.

2.

On installation:

(a) distance travalled:

2 % more or less than the real distance, where that distance is at least one kilometre;

(b) speed:

4 km/h more or less than the real speed;

(c) time:

± two minutes per day, or

± 10 minutes per seven days.

3.

In use:

(a) distance travelled:

4 % more or less than the real distance, where that distance is at least one kilometre;

(b) speed:

6 km/h more or less than the real speed;

(c) time:

± two minutes per day, or

± 10 minutes per seven days.

4.

The maximum tolerances set out in points 1, 2 and 3 are valid for temperatures between 0o and 40 oC, temperatures being taken in close proximity to the equipment.

5.

Measurement of the maximum tolerances set out in points 2 and 3 shall take place under the conditions laid down in Chapter VI.

IV.   RECORD SHEETS

(a)   General points

1.

The record sheets must be such that they do not impede the normal functioning of the instrument and that the records which they contain are indelible and easily legible and identifiable.

The record sheets must retain their dimensions and any records made on them under normal conditions of humidity and temperature.

In addition it must be possible to write on the sheets, without damaging them and without affecting the legibility of the recordings, the information referred to in Article 15 (5) of the Regulation.

Under normal conditions of storage, the recordings must remain clearly legible for at least one year.

2.

The minimum recording capacity of the sheets, whatever their form, must be 24 hours.

If several discs are linked together to increase the continuous recording capacity which can be achieved without intervention by staff, the links between the various discs must be made in such a way that there are no breaks in or overlapping of recordings at the point of transfer from one disc to another.

(b)   Recording areas and their graduation

1.

The record sheets shall include the following recording areas:

 an area exclusively reserved for data relating to speed,

 an area exclusively reserved for data relating to distance travelled,

 one or more areas for data relating to driving time, to other periods of work and availability to breaks from work and to rest periods for drivers.

2.

The area for recording speed must be scaled off in divisions of 20 kilometres per hour or less. The speed corresponding to each marking on the scale must be shown in figures against that marking. The symbol ‘km/h’ must be shown at least once within the area. The last marking on the scale must coincide with the upper limit of the range of measurement.

3.

The area for recording distance travelled must be set out in such a way that the number of kilometres travelled may be read without difficulty.

4.

The area or areas reserved for recording the periods referred to in point 1 must be so marked that it is possible to distinguish clearly between the various periods of time.

(c)   Information to be printed on the record sheets

Each sheet must bear, in printed form, the following information:

 name and address or trade name of the manufacturer,

 approval mark for the model of the sheet,

 approval mark for the type or types of equipment in which the sheet may be used,

 upper limit of the speed measurement range, printed in kilometres per hour.

By way of minimal additional requirements, each sheet must bear, in printed form a time-scale graduated in such a way that the time may be read directly at intervals of fifteen minutes while each five minute interval may be determined without difficulty.

(d)   Free space for hand written insertions

A free space must be provided on the sheets such that drivers may as a minimum write in the following details:

 surname and first name of the driver,

 date and place where use of the sheet begins and date and place where such use ends,

 the registration number or numbers of the vehicle or vehicles to which the driver is assigned during the use of the sheet,

 odometer readings from the vehicle or vehicles to which the driver is assigned during the use of the sheet,

 the time at which any change of vehicle takes place.

V.   INSTALLATION OF RECORDING EQUIPMENT

1.

Recording equipment must be positioned in the vehicle in such a way that the driver has a clear view from his seat of speedometer, distance recorder and clock while at the same time all parts of those instruments, including driving parts, are protected against accidental damage.

2.

It must be possible to adapt the constant of the recording equipment to the characteristic coefficient of the vehicle by means of a suitable device, to be known as an adaptor.

Vehicles with two or more rear axle ratios must be fitted with a switch device whereby these various ratios may be automatically brought into line with the ratio for which the equipment has been adapted to the vehicle.

3.

After the equipment has been checked on installation, an installation plaque shall be affixed to the vehicle beside the equipment or in the equipment itself and in such a way as to be clearly visible. After every inspection by an approved fitter or workshop requiring a change in the setting of the installation iteself, a new plaque must be affixed in place of the previous one.

The plaque must show at least the following details:

 name, address or trade name of the approved fitter or workshop,

 characteristic coefficient of the vehicle, in the form ‘w = … rev/km’ or ‘w = … imp/km’,

 effective circumference of the wheel tyres in the form ‘1 = … mm’,

 the dates on which the characteristic coefficient of the vehicle was determined and the effective measured circumference of the wheel tyres.

4.

Sealing

The following parts must be sealed:

(a) the installation plaque, unless it is attached in such a way that it cannot be removed without the markings thereon being destroyed;

(b) the two ends of the link between the recording equipment proper and the vehicle;

(c) the adaptor itself and the point of its insertion into the circuit;

(d) the switch mechanism for vehicles with two or more axle ratios;

(e) the links joining the adaptor and the switch mechanism to the rest of the equipment;

(f) the casings required under Chapter III (a) 7.2;

▼M3

(g) any cover giving access to the means of adapting the constant of the recording equipment to the characteristic coefficient of the vehicle.

▼B

In particular cases, further seals may be required on approval of the equipment type and a note of the positioning of these seals must be made on the approval certificate.

►M3  The seals mentioned in (b), (c) and (e) are authorized to be removed:

 in case of emergency,

 to install, to adjust or to repair a speed limitation device or any other device contributing to road safety,

provided that the recording equipment continues to function reliably and correctly and is resealed by an approved fitter or workshop immediately after fitting the speed limitation device or any other device contributing to road safety or within seven days in other cases ◄ ; for each occasion that these seals are broken a written statement giving the reasons for such action must be prepared and made available to the competent authority.

▼M4

5.

The cables connecting the recording equipment to the transmitter must be protected by a continuous plastic-coated rust-protected steel sheath with crimped ends except where an equivalent protection against manipulation is guaranteed by other means (for example by electronic monitoring such as signal encryption) capable of detecting the presence of any device, which is unnecessary for the correct operation of the recording equipment and whose purpose is to prevent the accurate operation of the recording equipment by short circuiting or interruption or by modification of the electronic data from the speed and distance sensor. A joint, comprised of sealed connections, is deemed to be continuous within the meaning of this Regulation.

The aforementioned electronic monitoring may be replaced by an electronic control which ensures that the recording equipment is able to record any movement of the vehicle, independent from the signal of the speed and distance sensor.

▼M5

For the purpose of the application of the present point, M 1 and N 1 vehicles are those defined in Part A of Annex II to Council Directive 70/156/EEC ( 10 ). For those vehicles that are equipped with tachographs in compliance with the Regulation and are not designed to install an armoured cable between the distance and speed sensors and the recording equipment, then an adaptor shall be fitted as close as possible to the distance and speed sensors.

The armoured cable shall be fitted from the adaptor to the recording equipment.

▼B

VI.   CHECKS AND INSPECTIONS

The Member States shall nominate the bodies which shall carry out the checks and inspections.

1.   Certification of new or repaired instruments

Every individual device, whether new or repaired, shall be certified in respect of its correct operation and the accuracy of its readings and recordings, within the limits laid down in Chapter III (f) 1, by means of sealing in accordance with Chapter V (4) (f).

For this purpose the Member States may stipulate an initial verification, consisting of a check on and confirmation of the conformity of a new or repaired device with the type-approved model and/or with the requirements of the Regulation and its Annexes, or may delegate the power to certify to the manufacturers or to their authorized agents.

2.   Installation

When being fitted to a vehicle, the equipment and the whole installation must comply with the provisions relating to maximum tolerances laid down in Chapter III (f) 2.

The inspection tests shall be carried out by the approved fitter or workshop on his or its responsibility.

3.   Periodic inspections

(a) Periodic inspections of the equipment fitted to vehicles shall take place at least every two years and may be carried out in conjunction with roadworthiness tests of vehicles.

These inspections shall include the following checks:

 that the equipment is working correctly,

 that the equipment carries the type approval mark,

 that the installation plaque is affixed,

 that the seals on the equipment and on the other parts of the installation are intact,

 the actual circumference of the tyres.

(b) An inspection to ensure compliance with the provision of Chapter III (f) 3 on the maximum tolerances in use shall be carried out at least once every six years, although each Member State may stipulate a shorter interval or such inspection in respect of vehicles registered in its territory. Such inspections must include replacement of the installation plaque.

4.   Measurement of errors

The measurement of errors on installation and during use shall be carried out under the following conditions, which are to be regarded as constituting standard test conditions:

 vehicle unladen, in normal running, order

 tyre pressures in accordance with the manufacturer's instructions,

 tyre wear within the limits allowed by law,

 movement of the vehicle: the vehicle must proceed, driven by its own engine, in a straight line and on a level surface, at a speed of 50 ± 5 km/h; provided that it is of comparable accuracy, the test may also be carried out on an appropriate test bench.

▼M8




ANNEX I B

REQUIREMENTS FOR CONSTRUCTION, TESTING, INSTALLATION AND INSPECTION

CONTENTS

I.

DEFINITIONS …

II.

GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT …

1.

General characteristics …

2.

Functions …

3.

Modes of operation …

4.

Security …

III.

CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT …

1.

Monitoring cards insertion and withdrawal …

2.

Speed and distance measurement …

2.1.

Measurement of distance travelled …

2.2.

Measurement of speed …

3.

Time measurement …

4.

Monitoring driver activities …

5.

Monitoring driving status …

6.

Drivers manual entries …

6.1.

Entry of places where daily work periods begin and/or end …

6.2.

Manual entry of driver activities …

6.3.

Entry of specific conditions …

7.

Company locks management …

8.

Monitoring control activities …

9.

Detection of events and/or faults …

9.1.

‘Insertion of a non valid card’ event …

9.2.

‘Card conflict’ event …

9.3.

‘Time overlap’ event …

9.4.

‘Driving without an appropriate card’ event …

9.5.

‘Card insertion while driving’ event …

9.6.

‘Last card session not correctly closed’ event …

9.7.

‘Over speeding’event …

9.8.

‘Power supply interruption’ event …

9.9.

‘Motion data error’ event …

9.10.

‘Security breach attempt’ event …

9.11.

‘Card’ fault …

9.12.

‘Recording equipment’ fault …

10.

Built-in and self tests …

11.

Reading from data memory …

12.

Recording and storing in the data memory …

12.1.

Equipment identification data …

12.1.1.

Vehicle Unit identification data …

12.1.2.

Motion sensor identification data …

12.2.

Security elements …

12.3.

Driver card insertion and withdrawal data …

12.4.

Driver activity data …

12.5.

Places where daily work periods start and/or end …

12.6.

Odometer data …

12.7.

Detailed speed data …

12.8.

Events data …

12.9.

Faults data …

12.10.

Calibration data …

12.11.

Time adjustment data …

12.12.

Control activity data …

12.13.

Company locks data …

12.14.

Download activity data …

12.15.

Specific conditions data …

13.

Reading from tachograph cards …

14.

Recording and storing on tachograph cards …

15.

Displaying …

15.1

Default display …

15.2.

Warning display …

15.3.

Menu access …

15.4.

Other displays …

16.

Printing …

17.

Warnings …

18.

Data downloading to external media …

19.

Output data to additional external devices …

20.

Calibration …

21.

Time adjustment …

22.

Performance characteristics …

23.

Materials …

24.

Markings …

IV.

CONSTRUCTIONS AND FUNCTIONAL REQUIREMTNS FOR TACHOGRAPH CARDS …

1.

Visible data …

2.

Security …

3.

Standards …

4.

Environmental and electrical specifications …

5.

Data storage …

5.1.

Card identification and security data …

5.1.1.

Application identification …

5.1.2.

Chip identification …

5.1.3.

IC card identification …

5.1.4.

Security elements …

5.2.

Driver card …

5.2.1.

Card identification …

5.2.2.

Card holder identification …

5.2.3.

Driving licence information …

5.2.4.

Vehicles used data …

5.2.5.

Driver activity data …

5.2.6.

Places where daily periods start and/or end …

5.2.7.

Events data …

5.2.8.

Faults data …

5.2.9.

Control activity data …

5.2.10.

Card session data …

5.2.11.

Secific conditions data …

5.3.

Workshop card …

5.3.1.

Security elements …

5.3.2.

Card identification …

5.3.3.

Card holder identification …

5.3.4.

Vehicles' used data …

5.3.5.

Driver activity data …

5.3.6.

Daily work periods start and/or end data …

5.3.7.

Events and faults data …

5.3.8.

Control activity data …

5.3.9.

Calibration and time adjustment data …

5.3.10.

Specific conditions data …

5.4.

Control card …

5.4.1.

Card identification …

5.4.2.

Card holder identification …

5.4.3.

Control activity data …

5.5.

Company card …

5.5.1.

Card identification …

5.5.2.

Card holder identification …

5.5.3.

Company activity data …

V.

INSTALATION OF RECORDING EQUIPMENT …

1.

Installation …

2.

Installation plaque …

3.

Sealing …

VI.

CHECKS; INSPECTIONS AND REPAIRS …

1.

Approval of fitters or workshops …

2.

Check of new or repaired instruments …

3.

Installation inspection …

4.

Periodic inspections …

5.

Measurement of errors …

6.

Repairs …

VII.

CARD ISSUING …

VIII.

TYPE APPROVAL OF RECORDING EQUIPMENT AND TACHOGRAPH CARDS …

1.

General points …

2.

Security certificate …

3.

Funtctional certificate …

4.

Interoperability certificate …

5.

Type approval certificate …

6.

Exceptional procedure: first interoperability tests …

Appendix 1.

Data dictionary …

Appendix 2.

Tachograph cards specification …

Appendix 3.

Pictograms …

Appendix 4.

Printouts …

Appendix 5.

Display …

Appendix 6.

External interfaces …

Appendix 7.

Data downloading protocol …

Appendix 8.

Calibration protocol …

Appendix 9.

TYPE APPROVAL — LIST OF MINIMUM REQUIRED TESTS …

Appendix 10.

GENERIC SECURITY TARGETS …

Appendix 11.

COMMON SECURITY MEACHANISMS …

Appendix 12.

ADAPTOR FOR M 1 AND N1 CATEGORY VEHICLES

I.   DEFINITIONS

In this Annex:

(a)

‘activation’ means : phase where the recording equipment becomes fully operational and implements all functions, including security functions; Activating a recording equipment requires the use of a workshop card and the entry of its PIN code;

(b)

‘authentication’ means : a function intended to establish and verify a claimed identity;

(c)

‘authenticity’ means : the property that an information is coming from a party whose identity can be verified;

(d)

‘built-in-test (BIT)’ means : tests run at request, triggered by the operator or by an external equipment;

(e)

‘calendar day’ means : a day ranging from 00.00 hours to 24.00 hours. All calendar days relate to UTC time (universal time coordinated);

▼M15

(f)

‘calibration’ means :

updating or confirming vehicle parameters to be held in the data memory. Vehicle parameters include vehicle identification (VIN, VRN and registering Member State) and vehicle characteristics (w, k, l, tyre size, speed limiting device setting (if applicable), current UTC time, current odometer value);

Any update or confirmation of UTC time only, shall be considered as a time adjustment and not as a calibration, provided it does not contradict Requirement 256.

Calibrating a recording equipment requires the use of a workshop card;

▼M8

(g)

‘card number’ means : a 16 alpha-numerical characters number that uniquely identifies a tachograph card within a Member State. The card number includes a consecutive index (if applicable), a replacement index and a renewal index; a card is therefore uniquely identified by the code of the issuing Member State and the card number;

(h)

‘card consecutive index’ means : the 14th alpha-numerical character of a card number that is used to differentiate the different cards issued to a company or a body entitled to be issued several tachograph cards. The company or the body is uniquely identified by the 13 first characters of the card number;

(i)

‘card renewal index’ means : the 16th alpha-numerical character of a card number which is incremented each time a tachograph card is renewed;

(j)

‘card replacement index’ means : the 15th alpha-numerical character of a card number which is incremented each time a tachograph card is replaced;

(k)

‘characteristic coefficient of the vehicle’ means : the numerical characteristic giving the value of the output signal emitted by the part of the vehicle linking it with the recording equipment (gearbox output shaft or axle) while the vehicle travels a distance of one kilometre under standard test conditions (see Chapter VI(5)). The characteristic coefficient is expressed in impulses per kilometre (w = … imp/km);

▼M15

(l)

‘company card’ means :

A tachograph card issued by the authorities of a Member State to the owner or holder of vehicles fitted with recording equipment;

The company card identifies the company and allows for displaying, downloading and printing of the data stored in the recording equipment which has been locked by this company or which has not been locked by any company;

▼M8

(m)

‘constant of the recording equipment’ means : the numerical characteristic giving the value of the input signal required to show and record a distance travelled of one kilometre; this constant shall be expressed in impulses per kilometre (k = … imp/km);

(n)

‘continuous driving time’ is computed within the recording equipment as ( 11 ) : the continuous driving time is computed as the current accumulated driving times of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN ( 12 ) period of 45 minutes or more (this period may have been split in several periods of 15 minutes or more). The computations involved take into account, as needed, past activities stored on the driver card. When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

(o)

‘control card’ means : a tachograph card issued by the authorities of a Member State to a national competent control authority; the control card identifies the control body and possibly the control officer and allows for getting access to the data stored in the data memory or in the driver cards for reading, printing and/or downloading;

(p)

‘cumulative break time’ is computed within the recording equipment as (12)  : the cumulative break from driving time is computed as the current accumulated AVAILABILITY or BREAK/REST or UNKNOWN (12)  times of 15 minutes or more of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN (12)  period of 45 minutes or more (this period may have been split in several periods of 15 minutes or more). The computations involved take into account, as needed, past activities stored on the driver card. Unknown periods of negative duration (start of unknown period > end of unknown period) due to time overlaps between two different recording equipments, are not taken into account for the computation. When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

(q)

‘data memory’ means : an electronic data storage device built into the recording equipment;

(r)

‘digital signature’ means : data appended to, or a cryptographic transformation of, a block of data that allows the recipient of the block of data to prove the authenticity and integrity of the block of data;

▼M15

(s)

‘downloading’ means :

Copying, together with the digital signature, of a part, or of a complete set of data files stored in the data memory of the vehicle or in the memory of the tachograph card, for which these data are necessary to establish compliance with the provisions set out in Regulation (EC) No. 561/2006.

Manufacturers of digital tachograph vehicle units and manufacturers of equipment designed and intended to download data files shall take all reasonable steps to ensure that the downloading of such data can be performed with the minimum delay to transport undertakings or drivers.

Downloading may not alter or delete stored data. The downloading of the detailed speed file may not be necessary to establish compliance with Regulation (EC) No. 561/2006, but may be used for other purposes, such as accident investigation;

▼M8

(t)

‘driver card’ means : a tachograph card issued by the authorities of a Member State to a particular driver; the driver card identifies the driver and allows for storage of driver activity data;

(u)

‘effective circumference of the wheel tyres’ means : the average of the distances travelled by each of the wheels moving the vehicle (driving wheels) in the course of one complete rotation. The measurement of these distances shall be made under standard test conditions (Chapter VI(5)) and is expressed in the form ‘l = … mm’. Vehicle manufacturers may replace the measurement of these distances by a theoretical calculation which takes into account the distribution of the weight on the axles, vehicle unladen in normal running order ( 13 ). The methods for such theoretical calculation will be approved by a competent Member State authority;

(v)

‘event’ means : abnormal operation detected by the recording equipment which may come from a fraud attempt;

(w)

‘fault’ means : abnormal operation detected by the recording equipment which may come from an equipment malfunction or failure;

(x)

‘installation’ means : mounting of the recording equipment in a vehicle;

(y)

‘motion sensor’ means : part of the recording equipment, providing a signal representative of vehicle speed and/or distance travelled;

(z)

‘non valid card’ means : a card detected as faulty, or which initial authentication failed, or which start of validity date is not yet reached, or which expiry date has passed;

(aa)

‘out of scope’ means : when the use of the recording equipment is not required, according to the provisions of Council Regulation (EEC) No 3820/85;

(bb)

‘over speeding’ means : exceeding the authorised speed of the vehicle, defined as any period of more than 60 seconds during which the vehicle's measured speed exceeds the limit for setting the speed limitation device laid down in Council Directive 92/6/EEC of 10 February 1992 on the installation and use of speed limitation devices for certain categories of motor vehicles in the Community ( 14 );

(cc)

‘periodic inspection’ means : set of operations performed to control that the recording equipment works properly and that its settings correspond to the vehicle parameters;

(dd)

‘printer’ means : component of the recording equipment which provides printouts of stored data;

(ee)

‘recording equipment’ means : the total equipment intended for installation in road vehicles to show, record and store automatically or semi-automatically details of the movement of such vehicles and of certain work periods of their drivers;

(ff)

‘renewal’ means : issue of a new tachograph card when an existing card reaches its expiry date, or is malfunctioning and has been returned to the issuing authority. Renewal always implies the certainty that two valid cards do not co-exist;

(gg)

‘repair’ means : any repair of a motion sensor or of a vehicle unit that requires disconnection of its power supply, or disconnection from other recording equipment components, or opening of it;

(hh)

‘replacement’ means : issue of a tachograph card in replacement of an existing card, which has been declared lost, stolen or malfunctioning and has not been returned to the issuing authority. Replacement always implies a risk that two valid cards may co-exist;

(ii)

‘security certification’ means : process to certify, by an ITSEC ( 15 ) certification body, that the recording equipment (or component) or the tachograph card under investigation fulfils the security requirements defined in Appendix 10 Generic security targets;

(jj)

‘self test’ means : tests run cyclically and automatically by the recording equipment to detect faults;

(kk)

‘tachograph card’ means

:

smart card intended for use with the recording equipment. Tachograph cards allow for identification by the recording equipment of the identity (or identity group) of the cardholder and allow for data transfer and storage. A tachograph card may be of the following types:

 driver card,

 control card,

 workshop card,

 company card;

(ll)

‘type approval’ means : process to certify, by a Member State, that the recording equipment (or component) or the tachograph card under investigation fulfils the requirements of this regulation;

(mm)

‘tyre size’ means : the designation of the dimensions of the tyres (external driving wheels) in accordance with Directive 92/23/EEC of 31 march 1992 ( 16 );

(nn)

‘vehicle identification’ means : numbers identifying the vehicle: vehicle registration number (VRN) with indication of the registering Member State and vehicle identification number (VIN) ( 17 );

(oo)

‘vehicle unit (VU)’ means : the recording equipment excluding the motion sensor and the cables connecting the motion sensor. The vehicle unit may either be a single unit or be several units distributed in the vehicle, as long as it complies with the security requirements of this regulation;

(pp)

for computing sake in the recording equipment ‘week’ means : the period between 00.00 hours UTC on Monday and 24.00 UTC on Sunday;

(qq)

‘workshop card’ means : a tachograph card issued by the authorities of a Member State to a recording equipment manufacturer, a fitter, a vehicle manufacturer or workshop, approved by that Member State. The workshop card identifies the cardholder and allows for testing, calibration and/or downloading of the recording equipment;

▼M13

(rr)

‘adaptor’ means

:

a part of the recording equipment, providing a signal permanently representative of vehicle speed and/or distance travelled, and which is:

 installed and used only in M1 and N1 type vehicles (as defined in Annex II to Council Directive 70/156/EEC) put into service for the first time between 1 May 2006 and ►M17  31 December 2015 ◄ ,

 installed where it is not mechanically possible to install any other type of existing motion sensor which is otherwise compliant with the provisions of this Annex and its Appendixes 1 to 11,

 installed between the vehicle unit and where the speed/distance impulses are generated by integrated sensors or alternative interfaces;

Seen from a vehicle unit, the adaptor behaviour is the same as if a motion sensor, compliant the provisions of this Annex and its Appendixes 1 to 11, was connected to the vehicle unit.

Use of such an adaptor in those vehicles described above shall allow for the installation and correct use of a vehicle unit compliant with all the requirements of this Annex.

For those vehicles, the recording equipment includes cables, an adaptor, and a vehicle unit.

▼M8

II.   GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT

000Any vehicle fitted with the recording equipment complying with the provisions of this Annex, must include a speed display and an odometer. These functions may be included within the recording equipment.

1.   General characteristics

The purpose of the recording equipment is to record, store, display, print, and output data related to driver activities.

001The recording equipment includes cables, a motion sensor, and a vehicle unit.

▼M15

001aThe interface between motion sensors and vehicle units shall be compliant with ISO 16844-3:2004, Cor 1:2006.

▼M8

002The vehicle unit includes a processing unit, a data memory, a real time clock, two smart card interface devices (driver and co-driver), a printer, a display, a visual warning, a calibration/downloading connector, and facilities for entry of user's inputs.

The recording equipment may be connected to other devices through additional connectors.

003Any inclusion in or connection to the recording equipment of any function, device, or devices, approved or otherwise, shall not interfere with, or be capable of interfering with, the proper and secure operation of the recording equipment and the provisions of the Regulation.

Recording equipment users identify themselves to the equipment via tachograph cards.

004The recording equipment provides selective access rights to data and functions according to user's type and/or identity.

The recording equipment records and stores data in its data memory and in tachograph cards.

This is done in accordance with Directive 95/46/EC of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data ( 18 ).

2.   Functions

005The recording equipment shall ensure the following functions:

 monitoring cards insertions and withdrawals,

 speed and distance measurement,

 time measurement,

 monitoring driver activities,

 monitoring driving status,

 drivers manual entries:

 

 entry of places where daily work periods begin and/or end,

 manual entry of driver activities,

 entry of specific conditions,

 company locks management,

 monitoring control activities,

 detection of events and/or faults,

 built-in and self tests,

 reading from data memory,

 recording and storing in data memory,

 reading from tachograph cards,

 recording and storing in tachograph cards,

 displaying,

 printing,

 warning,

 data downloading to external media,

 output data to additional external devices,

 calibration,

 time adjustment.

3.   Modes of operation

006The recording equipment shall possess four modes of operation:

 operational mode,

 control mode,

 calibration mode,

 company mode.

007The recording equipment shall switch to the following mode of operation according to the valid tachograph cards inserted into the card interface devices:



Mode of operation

Driver slot

No card

Driver card

Control card

Workshop card

Company card

Co-driver slot

No card

Operational

Operational

Control

Calibration

Company

Driver card

Operational

Operational

Control

Calibration

Company

Control card

Control

Control

Control (1)

Operational

Operational

Workshop card

Calibration

Calibration

Operational

Calibration (1)

Operational

Company card

Company

Company

Operational

Operational

Company (1)

(1)   008In these situations the recording equipment shall use only the tachograph card inserted in the driver slot.

009The recording equipment shall ignore non-valid cards inserted, except displaying, printing or downloading data held on an expired card which shall be possible.

010All functions listed in II.2. shall work in any mode of operation with the following exceptions:

 the calibration function is accessible in the calibration mode only,

 the time adjustment function is limited when not in the calibration mode,

▼M15 —————

▼M8

 the company locks management function is accessible in the company mode only,

 the monitoring of control activities function is operational in the control mode only,

▼M15

 the downloading function is not accessible in the operational mode (except as provided for in Requirement 150), and except downloading a driver card when no other card is inserted into the VU.

▼M8

011The recording equipment can output any data to display, printer or external interfaces with the following exceptions:

 in the operational mode, any personal identification (surname and first name(s)) not corresponding to a tachograph card inserted shall be blanked and any card number not corresponding to a tachograph card inserted shall be partially blanked (every odd character — from left to right — shall be blanked),

▼M15

 in the company mode, driver related data (requirements 081, 084 and 087) can be output only for periods where no lock exists or no other company holds a lock (as identified by the first 13 digits of the company card number),

▼M8

 when no card is inserted in the recording equipment, driver related data can be output only for the current and eight previous calendar days.

4.   Security

The system security aims at protecting the data memory in such a way as to prevent unauthorised access to and manipulation of the data and detecting any such attempts, protecting the integrity and authenticity of data exchanged between the motion sensor and the vehicle unit, protecting the integrity and authenticity of data exchanged between the recording equipment and the tachograph cards, and verifying the integrity and authenticity of data downloaded.

012In order to achieve the system security, the recording equipment shall meet the security requirements specified in the motion sensor and vehicle unit generic security targets (Appendix 10).

III.   CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT

1.   Monitoring cards insertion and withdrawal

013The recording equipment shall monitor the card interface devices to detect card insertions and withdrawals.

014Upon card insertion the recording equipment shall detect whether the card inserted is a valid tachograph card and in such a case identify the card type.

015The recording equipment shall be so designed that the tachograph cards are locked in position on their proper insertion into the card interface devices.

016The release of tachograph cards may function only when the vehicle is stopped and after the relevant data have been stored on the cards. The release of the card shall require positive action by the user.

2.   Speed and distance measurement

017This function shall continuously measure and be able to provide the odometer value corresponding to the total distance travelled by the vehicle.

018This function shall continuously measure and be able to provide the speed of the vehicle.

019The speed measurement function shall also provide the information whether the vehicle is moving or stopped. The vehicle shall be considered as moving as soon as the function detects more than 1 imp/sec for at least five seconds from the motion sensor, otherwise the vehicle shall be considered as stopped.

Devices displaying speed (speedometer) and total distance travelled (odometer) installed in any vehicle fitted with a recording equipment complying with the provisions of this Regulation, shall comply with the requirements relating to maximum tolerances laid down in this Annex (Chapters III(2)(1) and III(2)(2)).

▼M15

019aTo detect manipulation of motion data, information from the motion sensor shall be corroborated by vehicle motion information derived from one or more source(s) independent from the motion sensor.

▼M8

2.1.   Measurement of distance travelled

020The distance travelled may be measured either:

 so as to cumulate both forward and reverse movements, or

 so as to include only forward movement.

021The recording equipment shall measure distance from 0 to 9 999 999,9 km.

022Distance measured shall be within the following tolerances (distances of at least 1 000 m):

 ± 1 % before installation,

 ± 2 % on installation and periodic inspection,

 ± 4 % in use.

023Distance measured shall have a resolution better than or equal to 0,1 km.

2.2.   Measurement of speed

024The recording equipment shall measure speed from 0 to 220 km/h.

025To ensure a maximum tolerance on speed displayed of ± 6 km/h in use, and taking into account:

 a ± 2 km/h tolerance for input variations (tyre variations, …),

 a ± 1 km/h tolerance in measurements made during installation or periodic inspections,

the recording equipment shall, for speeds between 20 and 180 km/h, and for characteristic coefficients of the vehicle between 4 000 and 25 000 imp/km, measure the speed with a tolerance of ± 1 km/h (at constant speed).

Note: The resolution of data storage brings an additional tolerance of ± 0,5 km/h to speed stored by the recording equipment.

025aThe speed shall be measured correctly within the normal tolerances within 2 seconds of the end of a speed change when the speed has changed at a rate up to 2 m/s2.

026Speed measurement shall have a resolution better than or equal to 1 km/h.

3.   Time measurement

027The time measurement function shall measure permanently and digitally provide UTC date and time.

▼M15

028UTC date and time shall be used for dating data inside the recording equipment (recordings, data exchange) and for all printouts specified in Appendix 4 ‘Printouts’.

029In order to visualise the local time, it shall be possible to change the offset of the time displayed, in half hour steps. No other offsets than negative or positive multiples of half hours shall be allowed.

▼M8

030Time drift shall be within ± 2 seconds per day in type approval conditions.

031Time measured shall have a resolution better than or equal to 1 second.

032Time measurement shall not be affected by an external power supply cut-off of less than 12 months in type approval conditions.

4.   Monitoring driver activities

033This function shall permanently and separately monitor the activities of one driver and one co-driver.

034Driver activity shall be DRIVING, WORK, AVAILABILITY, or BREAK/REST.

035It shall be possible for the driver and/or the co-driver to manually select WORK, AVAILABILITY, or BREAK/REST.

036When the vehicle is moving, DRIVING shall be selected automatically for the driver and AVAILABILITY shall be selected automatically for the co-driver.

037When the vehicle stops, WORK shall be selected automatically for the driver.

▼M15

038The first change of activity to REST or AVAILABILITY arising within 120 seconds of the automatic change to WORK due to the vehicle stop shall be assumed to have happened at the time of vehicle stop (therefore possibly cancelling the change to WORK).

▼M8

039This function shall output activity changes to the recording functions at a resolution of one minute.

▼M15 —————

▼M15

041Given a calendar minute, if DRIVING is registered as the activity of both the immediately preceding and immediately succeeding minute, the whole minute shall be regarded as DRIVING.

042Given a calendar minute that is not regarded as DRIVING according to the previous requirement 041, the whole minute shall be regarded to be of the same type of activity as the longest continuous activity within the minute (or the latest of equally long activities).

▼M8

043This function shall also permanently monitor the continuous driving time and the cumulative break time of the driver.

5.   Monitoring driving status

044This function shall permanently and automatically monitor the driving status.

045The driving status CREW shall be selected when two valid driver cards are inserted in the equipment, the driving status SINGLE shall be selected in any other case.

6.   Drivers manual entries

6.1.   Entry of places where daily work periods begin and/or end

046This function shall allow for the entry of places where the daily work periods begin and/or end for a driver and/or a co-driver.

047Places are defined as the country and, in addition where applicable, the region.

048At the time of a driver (or workshop) card withdrawal, the recording equipment shall prompt the (co-)driver to enter a ‘place where the daily work period ends’.

049The recording equipment shall allow this request to be disregarded.

▼M15

050It shall be possible to input places where daily work periods begin and/or end through commands in the menus. If more than one such input is done within one calendar minute, only the last begin place input and the last end place input done within that time shall be kept recorded.

▼M8

6.2.   Manual entry of driver activities

▼M15

050aUpon driver (or workshop) card insertion, and only at this time, the recording equipment shall allow manual entries of activities. It shall be possible to make manual entries, if required, at the first insertion of a previously unused driver (or workshop) card.

Manual entries of activities shall be performed using local time and date values of the time zone (UTC offset) currently set for the vehicle unit.

At driver or workshop card insertion the cardholder shall be reminded of:

 The date and time of his last card withdrawal.

 Optionally: the local time offset currently set for the vehicle unit

It shall be possible to input activities with the following restrictions:

 Activity type shall be WORK, AVAILABILITY or BREAK/REST.

 Start and end times for each activity shall be within the period of the last card withdrawal — current insertion only.

Activities shall not be allowed to overlap mutually in time.

The procedure for manual entries of activities shall include as many consecutive steps as necessary to set a type, a start time and an end time for each activity. For any part of the time period between last card withdrawal and current card insertion, the cardholder shall have the option not to declare any activity.

During the manual entries associated with card insertion and if applicable, the card holder shall have the opportunity to input:

 a place where a previous daily work period ended, associated to the relevant time (if not already entered at the last card withdrawal),

 a place where the current daily work period begins, associated to the relevant time,

If a location is entered, it shall be recorded in the relevant tachograph card.

Manual entries shall be interrupted if:

 the card is withdrawn or,

 the vehicle is moving and the card is in the driver slot.

Additional interruptions are allowed, e.g. a timeout after a certain period of user inactivity. If manual entries are interrupted, the recording equipment shall validate any complete place and activity entries (having either unambiguous place and time, or activity type, begin time and end time) already made.

If a second driver or workshop card is inserted while manual entries of activities are in progress for a previously inserted card, the manual entries for this previous card shall be allowed to be completed before manual entries start for the second card.

The cardholder shall have the option to insert manual entries according to the following minimum procedure:

Enter activities manually, in chronological order, for the period last card withdrawal – current insertion.

Begin time of the first activity shall be set to card withdrawal time. For each subsequent entry, the start time shall be preset to immediately follow the end time of the previous entry. Activity type and end time shall be selected for each activity.

The procedure shall end when the end time of a manually entered activity equals the card insertion time. The recording equipment may then optionally allow the card holder to modify any activity manually entered, until validation by selection of a specific command. Thereafter, any such modification shall be forbidden.

▼M8

6.3.   Entry of specific conditions

▼M15

050bThe recording equipment shall allow the driver to enter, in real time, the following two specific conditions:

‘OUT OF SCOPE’ (begin, end)

‘FERRY / TRAIN CROSSING’

A ‘FERRY / TRAIN CROSSING’ may not occur if an ‘OUT OF SCOPE’ condition is opened.

An opened ‘OUT OF SCOPE’ condition shall be automatically closed, by the recording equipment, if a driver card is inserted or withdrawn.

An opened ‘OUT OF SCOPE’ condition shall inhibit the following events and warnings:

 Driving without an appropriate card,

 Warnings associated with continuous driving time.

▼M8

7.   Company locks management

051This function shall allow the management of the locks placed by a company to restrict data access in company mode to itself.

052Company locks consist in a start date/time (lock-in) and an end date/time (lock-out) associated with the identification of the company as denoted by the company card number (at lock-in).

053Locks may be turned ‘in’ or ‘out’ in real time only.

054Locking-out shall only be possible for the company whose lock is ‘in’ (as identified by the first 13 digits of the company card number), or,

055locking-out shall be automatic if another company locks in.

055aIn the case where a company locks in and where the previous lock was for the same company, then it will be assumed that the previous lock has not been turned ‘out’ and is still ‘in’.

8.   Monitoring control activities

056This function shall monitor DISPLAYING, PRINTING, VU and card DOWNLOADING activities carried while in control mode.

057This function shall also monitor OVER SPEEDING CONTROL activities while in control mode. An over speeding control is deemed to have happened when, in control mode, the ‘over speeding’ printout has been sent to the printer or to the display, or when ‘events and faults’ data have been downloaded from the VU data memory.

9.   Detection of events and/or faults

058This function shall detect the following events and/or faults:

9.1.   Insertion of a non-valid card‘’ event

059This event shall be triggered at the insertion of any non-valid card and/or when an inserted valid card expires.

9.2.   ‘Card conflict’ event

060This event shall be triggered when any of the valid cards combination noted X in the following table arise:



Card conflict

Driver slot

No card

Driver card

Control card

Workshop card

Company card

Co-driver slot

No card

 

 

 

 

 

Driver card

 

 

 

X

 

Control card

 

 

X

X

X

Workshop card

 

X

X

X

X

Company card

 

 

X

X

X

9.3.   ‘Time overlap’ event

061This event shall be triggered when the date/time of last withdrawal of a driver card, as read from the card, is later than the current date/time of the recording equipment in which the card is inserted.

9.4.   ‘Driving without an appropriate card’ event

062This event shall be triggered for any tachograph cards combination noted X in the following table, when driver activity changes to DRIVING, or when there is a change of the mode of operation while driver activity is DRIVING:



Driving without an appropriate card

Driver slot

No (or non-valid) card

Driver card

Control card

Workshop card

Company card

Co-driver slot

No (or non-valid) card

X

 

X

 

X

Driver card

X

 

X

X

X

Control card

X

X

X

X

X

Workshop card

X

X

X

 

X

Company card

X

X

X

X

X

9.5.   ‘Card insertion while driving’ event

063This event shall be triggered when a tachograph card is inserted in any slot, while driver activity is DRIVING.

9.6.   ‘Last card session not correctly closed’ event

064This event shall be triggered when at card insertion the recording equipment detects that, despite the provisions laid down in paragraph III(1), the previous card session has not been correctly closed (the card has been withdrawn before all relevant data have been stored on the card). This event shall be triggered by driver and workshop cards only.

9.7.   ‘Over speeding’ event

▼M15

065This event shall be triggered for each over-speeding. This requirement shall apply only to vehicles falling within category M2, M3, N2 or N3, as defined in Annex II of Directive 2007/46/EC, establishing a framework for the approval of motor vehicles and their trailers.

▼M8

9.8.   ‘Power supply interruption’ event

066This event shall be triggered, while not in calibration mode, in case of any interruption exceeding 200 milliseconds of the power supply of the motion sensor and/or of the vehicle unit. The interruption threshold shall be defined by the manufacturer. The drop in power supply due to the starting of the engine of the vehicle shall not trigger this event.

9.9.   ‘Motion data error’ event

067This event shall be triggered in case of interruption of the normal data flow between the motion sensor and the vehicle unit and/or in case of data integrity or data authentication error during data exchange between the motion sensor and the vehicle unit.

▼M15

9.9 bis.    ‘Vehicle Motion Conflict’ event

067aThis event shall also be triggered when a zero speed measurement is contradicted by motion information from at least one independent source for more than one uninterrupted minute.

067bIn cases where the vehicle unit can receive or elaborate speed values from external independent source of motion information, this event may also be triggered if such speed values significantly contradict those elaborated from the motion sensor speed signal for more than one minute.

▼M8

9.10.   ‘Security breach attempt’ event

068This event shall be triggered for any other event affecting the security of the motion sensor and/or of the vehicle unit as specified within the generic security targets of these components, while not in calibration mode.

9.11.   ‘Card’ fault

069This fault shall be triggered when a tachograph card failure occurs during operation.

9.12.   ‘Recording equipment’ fault

070This fault shall be triggered for any of these failures, while not in calibration mode:

 VU internal fault,

 printer fault,

 display fault,

 downloading fault,

 sensor fault.

10.   Built-in and self tests

071The recording equipment shall self-detect faults through self tests and built-in-tests, according to the following table:



Sub-assembly to test

Self test

Built-in-test

Software

 

Integrity

Data memory

Access

Access, data integrity

Card interface devices

Access

Access

Keyboard

 

Manual check

Printer

(up to manufacturer)

Printout

Display

 

Visual check

Downloading (performed only during downloading)

Proper operation

 

Sensor

Proper operation

Proper operation

11.   Reading from data memory

072The recording equipment shall be able to read any data stored in its data memory.

12.   Recording and storing in the data memory

For the purpose of this paragraph,

 ‘365 days’ is defined as 365 calendar days of average drivers activity in a vehicle. The average activity per day in a vehicle is defined as at least six drivers or co-drivers, six card insertion withdrawal cycles, and 256 activity changes. ‘365 days’ therefore include at least 2 190 (co-)drivers, 2 190 card insertion withdrawal cycles, and 93 440 activity changes,

 times are recorded with a resolution of one minute, unless otherwise specified,

 odometer values are recorded with a resolution of one kilometre,

 speeds are recorded with a resolution of 1 km/h.

073Data stored into the data memory shall not be affected by an external power supply cut-off of less than twelve months in type approval conditions.

074The recording equipment shall be able to record and store implicitly or explicitly in its data memory the following:

12.1.   Equipment identification data

12.1.1.   Vehicle unit identification data

075The recording equipment shall be able to store in its data memory the following vehicle unit identification data:

 name of the manufacturer,

 address of the manufacturer,

 part number,

 serial number,

 software version number,

 software version installation date,

 year of equipment manufacture,

 approval number.

076Vehicle unit identification data are recorded and stored once and for all by the vehicle unit manufacturer, except the software-related data and the approval number which may be changed in case of software upgrade.

12.1.2.   Motion sensor identification data

077The motion sensor shall be able to store in its memory the following identification data:

 name of the manufacturer,

 part number,

 serial number,

 approval number,

 embedded security component identifier (e.g. internal chip/processor part number),

 operating system identifier (e.g. software version number).

078Motion sensor identification data are recorded and stored once and for all in the motion sensor, by the motion sensor manufacturer.

079The vehicle unit shall be able to record and store in its data memory the following currently paired motion sensor identification data:

 serial number,

 approval number,

 first pairing date.

12.2.   Security elements

080The recording equipment shall be able to store the following security elements:

 European public key,

 Member State certificate,

 equipment certificate,

 equipment private key.

Recording equipment security elements are inserted in the equipment by the vehicle unit manufacturer.

12.3.   Driver card insertion and withdrawal data

081For each insertion and withdrawal cycle of a driver or workshop card in the equipment, the recording equipment shall record and store in its data memory:

 the card holder's surname and first name(s) as stored in the card,

 the card's number, issuing Member State and expiry date as stored in the card,

 the insertion date and time,

 the vehicle odometer value at card insertion,

 the slot in which the card is inserted,

 the withdrawal date and time,

 the vehicle odometer value at card withdrawal,

 the following information about the previous vehicle used by the driver, as stored in the card:

 

 VRN and registering Member State,

 card withdrawal date and time,

 a flag indicating whether, at card insertion, the card holder has manually entered activities or not.

082The data memory shall be able to hold these data for at least 365 days.

083When storage capacity is exhausted, new data shall replace oldest data.

12.4.   Driver activity data

084The recording equipment shall record and store in its data memory whenever there is a change of activity for the driver and/or the co-driver, and/or whenever there is a change of driving status, and/or whenever there is an insertion or withdrawal of a driver or workshop card:

 the driving status (CREW, SINGLE),

 the slot (DRIVER, CO-DRIVER),

 the card status in the relevant slot (INSERTED, NOT INSERTED) (see Note),

 the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST),

 the date and time of the change.

Note: INSERTED means that a valid driver or workshop card is inserted in the slot. NOT INSERTED means the opposite, i.e. no valid driver or workshop card is inserted in the slot (e.g. a company card is inserted or no card is inserted).

Note: Activity data manually entered by a driver are not recorded in the data memory.

085The data memory shall be able to hold driver activity data for at least 365 days.

086When storage capacity is exhausted, new data shall replace oldest data.

12.5.   Places where daily work periods start and/or end

087The recording equipment shall record and store in its data memory whenever a (co-)driver enters the place where a daily work period begins and/or ends:

 if applicable, the (co-)driver card number and card issuing Member State,

 the date and time of the entry (or the date/time related to the entry when the entry is made during the manual entry procedure),

 the type of entry (begin or end, condition of entry),

 the country and region entered,

 the vehicle odometer value.

088The data memory shall be able to hold daily work periods start and/or end data for at least 365 days (with the assumption that one driver enters two records per day).

089When storage capacity is exhausted, new data shall replace oldest data.

12.6.   Odometer data

090The recording equipment shall record in its data memory the vehicle odometer value and the corresponding date at midnight every calendar day.

091The data memory shall be able to store midnight odometer values for at least 365 calendar days.

092When storage capacity is exhausted, new data shall replace oldest data.

12.7.   Detailed speed data

093The recording equipment shall record and store in its data memory the instantaneous speed of the vehicle and the corresponding date and time at every second of at least the last 24 hours that the vehicle has been moving.

12.8.   Events data

For the purpose of this subparagraph, time shall be recorded with a resolution of one second.

094The recording equipment shall record and store in its data memory the following data for each event detected according to the following storage rules:



Event

Storage rules

Data to be recorded per event

Card conflict

— the 10 most recent events.

— date and time of beginning of event,

— date and time of end of event,

— cards' type, number and issuing Member State of the two cards creating the conflict.

Driving without an appropriate card

— the longest event for each of the 10 last days of occurrence,

— the five longest events over the last 365 days.

— date and time of beginning of event,

— date and time of end of event,

— cards' type, number and issuing Member State of any card inserted at beginning and/or end of the event,

— number of similar events that day.

Card insertion while driving

— the last event for each of the 10 last days of occurrence.

— date and time of the event,

— card's type, number and issuing Member State,

— number of similar events that day.

Last card session not correctly closed

— the 10 most recent events.

— date and time of card insertion,

— card's type, number and issuing Member State,

— last session data as read from the card:

— 

— date and time of card insertion,

— VRN and Member State of registration.

Over speeding (1)

— the most serious event for each of the 10 last days of occurrence (i.e. the one with the highest average speed),

— the five most serious events over the last 365 days.

— the first event having occurred after the last calibration.

— date and time of beginning of event,

— date and time of end of event,

— maximum speed measured during the event,

— arithmetic average speed measured during the event,

— card's type, number and issuing Member State of the driver (if applicable),

— number of similar events that day.

Power supply interruption (2)

— the longest event for each of the 10 last days of occurrence,

— the five longest events over the last 365 days.

— date and time of beginning of event,

— date and time of end of event,

— cards' type, number and issuing Member State of any card inserted at beginning and/or end of the event,

— number of similar events that day.

Motion data error

— the longest event for each of the 10 last days of occurrence,

— the five longest events over the last 365 days.

— date and time of beginning of event,

— date and time of end of event,

— cards' type, number and issuing Member State of any card inserted at beginning and/or end of the event,

— number of similar events that day.

▼M15

Vehicle Motion Conflict

— the longest event for each of the 10 last days of occurrence,

— the 5 longest events over the last 365 days.

— date and time of beginning of event,

— date and time of end of event,

— cards’ type, number and issuing Member State of any card inserted at beginning and/or end of the event,

— number of similar events that day.

▼M8

Security breach attempt

— the 10 most recent events per type of event.

— date and time of beginning of event,

— date and time of end of event (if relevant),

— cards' type, number and issuing Member State of any card inserted at beginning and/or end of the event,

— type of event.

(1)   095The recording equipment shall also record and store in its data memory: — the date and time of the last OVER SPEEDING CONTROL, — the date and time of the first over speeding following this OVER SPEEDING CONTROL, — the number of over speeding events since the last OVER SPEEDING CONTROL.

(2)   These data may be recorded at power supply reconnection only, times may be known with an accuracy to the minute.

12.9.   Faults data

For the purpose of this subparagraph, time shall be recorded with a resolution of one second.

096The recording equipment shall attempt to record and store in its data memory the following data for each fault detected according to the following storage rules:



Fault

Storage rules

Data to be recorded per fault

Card fault

— the 10 most recent driver card faults.

— date and time of beginning of fault,

— date and time of end of fault,

— card's type number and issuing Member State.

Recording equipment faults

— the 10 most recent faults for each type of fault,

— the first fault after the last calibration.

— date and time of beginning of fault,

— date and time of end of fault,

— type of fault,

— cards' type, number and issuing Member State of any card inserted at beginning and/or end of the fault.

12.10.   Calibration data

097The recording equipment shall record and store in its data memory data relevant to:

 known calibration parameters at the moment of activation,

 its very first calibration following its activation,

 its first calibration in the current vehicle (as identified by its VIN),

 the five most recent calibrations (If several calibrations happen within one calendar day, only the last one of the day shall be stored).

098The following data shall be recorded for each of these calibrations:

 purpose of calibration (activation, first installation, installation, periodic inspection),

 workshop name and address,

 workshop card number, card issuing Member State and card expiry date,

 vehicle identification,

 parameters updated or confirmed: w, k, l, tyre size, speed limiting device setting, odometer (old and new values), date and time (old and new values).

099The motion sensor shall record and store in its memory the following motion sensor installation data:

 first pairing with a VU (date, time, VU approval number, VU serial number),

 last pairing with a VU (date, time, VU approval number, VU serial number).

12.11.   Time adjustment data

100The recording equipment shall record and store in its data memory data relevant to:

 the most recent time adjustment,

 the five largest time adjustments, since last calibration,

performed in calibration mode outside the frame of a regular calibration (definition (f)).

101The following data shall be recorded for each of these time adjustments:

 date and time, old value,

 date and time, new value,

 workshop name and address,

 workshop card number, card issuing Member State and card expiry date.

12.12.   Control activity data

102The recording equipment shall record and store in its data memory the following data relevant to the 20 most recent control activities:

 date and time of the control,

 control card number and card issuing Member State,

 type of the control (displaying and/or printing and/or VU downloading and/or card downloading).

103In case of downloading, the dates of the oldest and of the most recent days downloaded shall also be recorded.

12.13.   Company locks data

▼M15

104The recording equipment shall record and store in its data memory the following data relevant to the 255 most recent company locks:

 lock-in date and time,

 lock-out date and time,

 Company Card number and card issuing Member States,

 Company name and address.

Data previously locked by a lock removed from memory due to the limit above, shall be treated as not locked.

▼M8

12.14.   Download activity data

105The recording equipment shall record and store in its data memory the following data relevant to the last data memory downloading to external media while in company or in calibration mode:

 date and time of downloading,

 company or workshop card number and card issuing Member State,

 company or workshop name.

12.15.   Specific conditions data

105aThe recording equipment shall record in its data memory the following data relevant to specific conditions:

 date and time of the entry,

 type of specific condition.

105bThe data memory shall be able to hold specific conditions data for at least 365 days (with the assumption that on average, one condition is opened and closed per day). When storage capacity is exhausted, new data shall replace oldest data.

13.   Reading from tachograph cards

106The recording equipment shall be able to read from tachograph cards, where applicable, the necessary data:

 to identify the card type, the card holder, the previously used vehicle, the date and time of the last card withdrawal and the activity selected at that time,

 to check that last card session was correctly closed,

 to compute the driver's continuous driving time, cumulative break time and cumulated driving times for the previous and the current week,

 to print requested printouts related to data recorded on a driver card,

 to download a driver card to external media.

107In case of a reading error, the recording equipment shall try again, three times maximum, the same read command, and then if still unsuccessful, declare the card faulty and non-valid.

14.   Recording and storing on tachograph cards

108The recording equipment shall set the ‘card session data’ in the driver or workshop card right after the card insertion.

109The recording equipment shall update data stored on valid driver, workshop and/or control cards with all necessary data relevant to the period while the card is inserted and relevant to the card holder. Data stored on these cards are specified in Chapter IV.

109aThe recording equipment shall update driver activity and location data (as specified in Chapter IV, paragraphs 5.2.5 and 5.2.6), stored on valid driver and/or workshop cards, with activity and location data manually entered by the cardholder.

▼M15

109bThe ‘Vehicle Motion Conflict’ event shall not be stored on the driver and workshop cards.

▼M8

110Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data.

111In the case of a writing error, the recording equipment shall try again, three times maximum, the same write command, and then if still unsuccessful, declare the card faulty and non valid.

112Before releasing a driver card, and after all relevant data have been stored on the card, the recording equipment shall reset the card session data.

15.   Displaying

113The display shall include at least 20 characters.

114The minimum character size shall be 5 mm high and 3,5 mm wide.

▼M15

114aThe display shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’. The display may use simplified glyphs (e.g. accented characters may be displayed without accent, or lower case letters may be shown as upper case letters).

▼M8

115The display shall be provided with adequate non-dazzling lighting.

116Indications shall be visible from outside the recording equipment.

117The recording equipment shall be able to display:

 default data,

 data related to warnings,

 data related to menu access,

 other data requested by a user.

Additional information may be displayed by the recording equipment, provided that it is clearly distinguishable from information required above.

118The display of the recording equipment shall use the pictograms or pictogram combinations listed in Appendix 3. Additional pictograms or pictogram combinations may also be provided by the display, if clearly distinguishable from the aforementioned pictogram or pictogram combinations.

119The display shall always be ON when the vehicle is moving.

120The recording equipment may include a manual or automatic feature to turn the display OFF when the vehicle is not moving.

Displaying format is specified in Appendix 5.

15.1.   Default display

▼M15

121When no other information needs to be displayed, the recording equipment shall display, by default, the following:

 the local time (as a result of UTC time + offset as set by the driver),

 the mode of operation,

 the current activity of the driver and the current activity of the co-driver.

Information related to the driver:

 if his current activity is DRIVING, his current continuous driving time and his current cumulative break time,

 if his current activity is not DRIVING, the current duration of this activity (since it was selected) and his current cumulative break time.

▼M8

122Display of data related to each driver shall be clear, plain and unambiguous. In the case where the information related to the driver and the co-driver cannot be displayed at the same time, the recording equipment shall display by default the information related to the driver and shall allow the user to display the information related to the co-driver.

123In the case where the display width does not allow to display by default the mode of operation, the recording equipment shall briefly display the new mode of operation when it changes.

124The recording equipment shall briefly display the card holder name at card insertion.

124aWhen an ‘OUT OF SCOPE’ condition is opened, then the default display must show using the relevant pictogram that the condition is opened (It is acceptable that the driver's current activity may not be shown at the same time).

15.2.   Warning display

125The recording equipment shall display warning information using primarily the pictograms of Appendix 3, completed where needed by an additional numerically coded information. A literal description of the warning may also be added in the driver's preferred language.

15.3.   Menu access

126The recording equipment shall provide necessary commands through an appropriate menu structure.

15.4.   Other displays

▼M15

127It shall be possible to display selectively on request:

 the UTC date and time, and local time offset,

 the content of any of the six printouts under the same formats as the printouts themselves,

 the continuous driving time and cumulative break time of the driver,

 the continuous driving time and cumulative break time of the co-driver,

 the cumulated driving time of the driver for the previous and the current week,

 the cumulated driving time of the co-driver for the previous and the current week.

Optional:

 the current duration of co-driver activity (since it was selected),

 the cumulated driving time of the driver for the current week,

 the cumulated driving time of the driver for the current daily work period,

 the cumulated driving time of the co-driver for the current daily work period.

▼M8

128Printout content display shall be sequential, line by line. If the display width is less than 24 characters the user shall be provided with the complete information through an appropriate mean (several lines, scrolling, …). Printout lines devoted to hand-written information may be omitted for display.

16.   Printing

129The recording equipment shall be able to print information from its data memory and/or from tachograph cards in accordance with the six following printouts:

 driver activities from card daily printout,

 driver activities from Vehicle Unit daily printout,

 events and faults from card printout,

 events and faults from Vehicle Unit printout,

 technical data printout,

 over speeding printout.

The detailed format and content of these printouts are specified in Appendix 4.

Additional data may be provided at the end of the printouts

Additional printouts may also be provided by the recording equipment, if clearly distinguishable from the six aforementioned printouts.

130The ‘driver activities from card daily printout’ and ‘events and faults from card printout’ shall be available only when a driver card or a workshop card is inserted in the recording equipment. The recording equipment shall update data stored on the relevant card before starting printing.

131In order to produce the ‘driver activities from card daily printout’ or the ‘events and faults from card printout’, the recording equipment shall:

 either automatically select the driver card or the workshop card if one only of these cards is inserted,

 or provide a command to select the source card or select the card in the driver slot if two of these cards are inserted in the recording equipment.

132The printer shall be able to print 24 characters per line.

133The minimum character size shall be 2,1 mm high and 1,5 mm wide.

▼M15

133aThe printer shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’.

▼M8

134Printers shall be so designed as to produce these printouts with a degree of definition likely to avoid any ambiguity when they are read.

135Printouts shall retain their dimensions and recordings under normal conditions of humidity (10 to 90 %) and temperature.

▼M15

136The printout paper used by the recording equipment shall bear the relevant type approval mark and an indication of the type(s) of recording equipment with which it may be used.

▼M15

136aPrintouts shall remain clearly legible and identifiable under normal conditions of storage, in terms of light intensity, humidity and temperature, for at least two years.

136bThe printout paper shall conform at least to the test specifications defined on the website of the laboratory appointed to carry out interoperability testing, as set out in Requirement 278.

136cAny amendment or updating of the specifications described in the above paragraph shall only be made after the appointed laboratory has consulted the type approved digital tachograph vehicle unit manufacturer in conjunction with the type approval authorities.

▼M8

137It shall also be possible to add handwritten notes, such as the driver's signature, to these documents.

138The recording equipment shall manage ‘paper out’ events while printing by, once paper has been re-loaded, restarting printing from printout beginning or by continuing printing and providing an unambiguous reference to previously printed part.

17.   Warnings

139The recording equipment shall warn the driver when detecting any event and/or fault.

140Warning of a power supply interruption event may be delayed until the power supply is reconnected.

▼M15

141The recording equipment shall warn the driver 15 minutes before and at the time of exceeding the maximum allowed continuous driving time.

▼M8

142Warnings shall be visual. Audible warnings may also be provided in addition to visual warnings.

143Visual warnings shall be clearly recognisable by the user, shall be situated in the driver's field of vision and shall be clearly legible both by day and by night.

144Visual warnings may be built into the recording equipment and/or remote from the recording equipment.

▼M15

145In the latter case it shall bear a ‘T’ symbol.

▼M8

146Warnings shall have a duration of at least 30 seconds, unless acknowledged by the user by hitting any key of the recording equipment. This first acknowledgement shall not erase warning cause display referred to in next paragraph.

147Warning cause shall be displayed on the recording equipment and remain visible until acknowledged by the user using a specific key or command of the recording equipment.

148Additional warnings may be provided, as long as they do not confuse drivers in relation to previously defined ones.

18.   Data downloading to external media

149The recording equipment shall be able to download on request data from its data memory or from a driver card to external storage media via the calibration/downloading connector. The recording equipment shall update data stored on the relevant card before starting downloading.

150In addition and as an optional feature, the recording equipment may, in any mode of operation, download data through another connector to a company authenticated through this channel. In such a case, company mode data access rights shall apply to this download.

151Downloading shall not alter or delete any stored data.

The calibration/downloading connector electrical interface is specified in Appendix 6.

Downloading protocols are specified in Appendix 7.

19.   Output data to additional external devices

152When the recording equipment does not include speed and/or odometer display functions, the recording equipment shall provide output signal(s) to allow for displaying the speed of the vehicle (speedometer) and/or the total distance travelled by the vehicle (odometer).

153The vehicle unit shall also be able to output the following data using an appropriate dedicated serial link independent from an optional CAN bus connection (ISO 11898 Road vehicles — Interchange of digital information — Controller Area Network (CAN) for high speed communication), to allow their processing by other electronic units installed in the vehicle:

 current UTC date and time,

 speed of the vehicle,

 total distance travelled by the vehicle (odometer),

 currently selected driver and co-driver activity,

 information if any tachograph card is currently inserted in the driver slot and in the co-driver slot and (if applicable) information about the corresponding cards identification (card number and issuing Member State).

Other data may also be output in addition to this minimum list.

When the ignition of the vehicle is ON, these data shall be permanently broadcast. When the ignition of the vehicle is OFF, at least any change of driver or co-driver activity and/or any insertion or withdrawal of a tachograph card shall generate a corresponding data output. In the event that data output has been withheld whilst the ignition of the vehicle is OFF, that data shall be made available once the ignition of the vehicle is ON again.

20.   Calibration

154The calibration function shall allow:

 to automatically pair the motion sensor with the VU,

 to digitally adapt the constant of the recording equipment (k) to the characteristic coefficient of the vehicle (w) (vehicles with two or more axle ratios shall be fitted with a switch device whereby these various ratios will automatically be brought into line with the ratio for which the equipment has been adapted to the vehicle),

 to adjust (without limitation) the current time,

 to adjust the current odometer value,

 to update motion sensor identification data stored in the data memory,

 to update or confirm other parameters known to the recording equipment: vehicle identification, w, l, tyre size and speed limiting device setting if applicable.

155Pairing the motion sensor to the VU shall consist, at least, in:

 updating motion sensor installation data held by the motion sensor (as needed),

 copying from the motion sensor to the VU data memory necessary motion sensor identification data.

156The calibration function shall be able to input necessary data through the calibration/downloading connector in accordance with the calibration protocol defined in Appendix 8. The calibration function may also input necessary data through other connectors.

21.   Time adjustment

157The time adjustment function shall allow for adjusting the current time in amounts of one minute maximum at intervals of not less than seven days.

158The time adjustment function shall allow for adjusting the current time without limitation, in calibration mode.

22.   Performance characteristics

159The Vehicle Unit shall be fully operational in the temperature range - 20 oC to 70 oC, and the motion sensor in the temperature range - 40 oC to 135 oC. Data memory content shall be preserved at temperatures down to - 40 oC.

160The recording equipment shall be fully operational in the humidity range 10 % to 90 %.

161The recording equipment shall be protected against over-voltage, inversion of its power supply polarity, and short circuits.

▼M15

161aMotion sensors shall either:

 react to a magnetic field which disturbs vehicle motion detection. In such circumstances, the vehicle unit will record and store a sensor fault (Requirement 070) or,

have a sensing element that is protected from, or immune to, magnetic fields.

▼M8

162The recording equipment shall conform to Commission Directive 95/54/EC of 31 October 1995 ( 19 ) adapting to technical progress Council Directive 72/245/EEC ( 20 ), related to electromagnetic compatibility, and shall be protected against electrostatic discharges and transients.

23.   Materials

163All the constituent parts of the recording equipment shall be made of materials of sufficient stability and mechanical strength and with stable electrical and magnetic characteristics.

164For normal conditions of use, all the internal parts of the equipment shall be protected against damp and dust.

165The Vehicle Unit shall meet the protection grade IP 40 and the motion sensor shall meet the protection grade IP 64, as per standard IEC 529.

166The recording equipment shall conform to applicable technical specifications related to ergonomic design.

167The recording equipment shall be protected against accidental damage.

24.   Markings

168If the recording equipment displays the vehicle odometer value and speed, the following details shall appear on its display:

 near the figure indicating the distance, the unit of measurement of distance, indicated by the abbreviation ‘km’,

 near the figure showing the speed, the entry ‘km/h’.

The recording equipment may also be switched to display the speed in miles per hour, in which case the unit of measurement of speed shall be shown by the abbreviation ‘mph’.

169A descriptive plaque shall be affixed to each separate component of the recording equipment and shall show the following details:

 name and address of the manufacturer of the equipment,

 manufacturer's part number and year of manufacture of the equipment,

 equipment serial number,

 approval mark for the equipment type.

170When physical space is not sufficient to show all abovementioned details, the descriptive plaque shall show at least: the manufacturer's name or logo, and the equipment's part number.

IV.   CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS

1.   Visible data

The front page will contain:

171the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’ or ‘Company card’ printed in large type in the official language or languages of the Member State issuing the card, according to the type of the card;

▼M12

172 ►M16  the same words in the other official languages of the Community, printed to form the background of the card:



BG

КАРТА НА ВОДАЧА

КОНТРОЛНА КАРТА

КАРТАЗА МОНТАЖ И НАСТРОЙКИ

КАРТА НА ПРЕВОЗВАЧА

ES

TARJETA DEL CONDUCTOR

TARJETA DE CONTROL

TARJETA DEL CENTRO DE ENSAYO

TARJETA DE LA EMPRESA

CS

KARTA ŘIDIČE

KONTROLNÍ KARTA

KARTA DÍLNY

KARTA PODNIKU

DA

FØRERKORT

KONTROLKORT

VÆRKSTEDSKORT

VIRKSOMHEDSKORT

DE

FAHRERKARTE

KONTROLLKARTE

WERKSTATTKARTE

UNTERNEHMENSKARTE

ET

AUTOJUHI KAART

KONTROLLIJA KAART

TÖÖKOJA KAART

TÖÖANDJA KAART

EL

ΚΑΡΤΑ ΟΔΗΓΟΥ

ΚΑΡΤΑ ΕΛΕΓΧΟΥ

ΚΑΡΤΑ ΚΕΝΤΡΟΥ ΔΟΚΙΜΩΝ

ΚΑΡΤΑ ΕΠΙΧΕΙΡΗΣΗΣ

EN

DRIVER CARD

CONTROL CARD

WORKSHOP CARD

COMPANY CARD

FR

CARTE DE CONDUCTEUR

CARTE DE CONTROLEUR

CARTE D’ATELIER

CARTE D’ENTREPRISE

HR

KARTICA VOZAČA

NADZORNA KARTICA

KARTICA RADIONICE

KARTICA PRIJEVOZNIKA

GA

CÁRTA TIOMÁNAÍ

CÁRTA STIÚRTHA

CÁRTA CEARDLAINNE

CÁRTA COMHLACHTA

IT

CARTA DEL CONDUCENTE

CARTA DI CONTROLLO

CARTA DELL’OFFICINA

CARTA DELL’ AZIENDA

LV

VADĪTĀJA KARTE

KONTROLKARTE

DARBNĪCAS KARTE

UZŅĒMUMA KARTE

LT

VAIRUOTOJO KORTELĖ

KONTROLĖS KORTELĖ

DIRBTUVĖS KORTELĖ

ĮMONĖS KORTELĖ

HU

GÉPJÁRMŰVEZETŐI KÁRTYA

ELLENŐRI KÁRTYA

MŰHELYKÁRTYA

ÜZEMBENTARTÓI KÁRTYA

MT

KARTA TAS-SEWWIEQ

KARTA TAL-KONTROLL

KARTA TAL-ISTAZZJON TAT-TESTIJIET

KARTA TAL-KUMPANNIJA

NL

BESTUURDERS KAART

CONTROLEKAART

WERKPLAATSKAART

BEDRIJFSKAART

PL

KARTA KIEROWCY

KARTA KONTROLNA

KARTA WARSZTATOWA

KARTA PRZEDSIĘBIORSTWA

PT

CARTÃO DE CONDUTOR

CARTÃO DE CONTROLO

CARTÃO DO CENTRO DE ENSAIO

CARTÃO DE EMPRESA

RO

CARTELA CONDUCĂTORULUI AUTO

CARTELA DE CONTROL

CARTELA AGENTULUI ECONOMIC AUTORIZAT

CARTELA OPERATORULUI DE TRANSPORT

SK

KARTA VODIČA

KONTROLNÁ KARTA

DIELENSKÁ KARTA

PODNIKOVÁ KARTA

SL

VOZNIKOVA KARTICA

KONTROLNA KARTICA

KARTICA PREIZKUŠEVALIŠČA

KARTICA PODJETJA

FI

KULJETTAJAKORTTI

VALVONTAKORTTI

KORJAAMOKORTTI

YRITYSKORTTI

SV

FÖRARKORT

KONTROLLKORT

VERKSTADSKORT

FÖRETAGSKORT ◄

▼M8

173the name of the Member State issuing the card (optional);

▼M12

174 ►M16  the distinguishing sign of the Member State issuing the card, printed in negative in a blue rectangle and encircled by 12 yellow stars; the distinguishing signs shall be as follows:

B

:

Belgium

BG

:

Bulgaria

CZ

:

The Czech Republic

DK

:

Denmark

D

:

Germany

EST

:

Estonia

GR

:

Greece

E

:

Spain

F

:

France

HR

:

Croatia

IRL

:

Ireland

I

:

Italy

CY

:

Cyprus

LV

:

Latvia

LT

:

Lithuania

L

:

Luxembourg

H

:

Hungary

M

:

Malta

NL

:

The Netherlands

A

:

Austria

PL

:

Poland

P

:

Portugal

RO

:

Romania

SLO

:

Slovenia

SK

:

Slovakia

FIN

:

Finland

S

:

Sweden

UK

:

The United Kingdom. ◄

▼M8

175information specific to the card issued, numbered as follows:



 

Driver card

Control card

Company or workshop card

1.

Surname of the driver

Control body name

►C2  Company or workshop name ◄

2.

First name(s) of the driver

Surname of the controller (if applicable)

Surname of card holder (if applicable)

3.

Birth date of the driver

First name(s) of the controller (if applicable)

First name(s) of card holder (if applicable)

4.(a)

Card start of validity date

(b)

Card expiry date (if any)

(c)

The name of the issuing authority (may be printed on page 2)

(d)

A different number from the one under heading 5, for administrative purposes (optional)

5.(a)

Driving licence number (at the date of issue of the driver card)

 

 

5.(b)

Card number

6.

Photograph of the driver

Photograph of the controller (optional)

7.

Signature of the driver

Signature of the holder (optional)

8.

Normal place of residence, or postal address of the holder (optional)

Postal address of control body

Postal address of company or workshop

176dates shall be written using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format (day, month, year);

the reverse page will contain:

177an explanation of the numbered items which appear on the front page of the card;

178with the specific written agreement of the holder, information which is not related to the administration of the card may also be added, such addition will not alter in any way the use of the model as a tachograph card.

image ►(7) C2   ►(7) C2   ►(7) C2   ►(7) C2   ►(7) C2   ►(7) C2   ►(7) C2  

179Tachograph cards shall be printed with the following background predominant colours:

 driver card: white,

 control card: blue,

 workshop card: red,

 company card: yellow.

180Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering:

 a security design background with fine guilloche patterns and rainbow printing,

 in the area of the photograph, the security design background and the photograph shall overlap,

 at least one two-coloured microprint line.

181After consulting the Commission, Member States may add colours or markings, such as national symbols and security features, without prejudice to the other provisions of this Annex.

2.   Security

The system security aims at protecting integrity and authenticity of data exchanged between the cards and the recording equipment, protecting the integrity and authenticity of data downloaded from the cards, allowing certain write operations onto the cards to recording equipment only, ruling out any possibility of falsification of data stored in the cards, preventing tampering and detecting any attempt of that kind.

182In order to achieve the system security, the tachograph cards shall meet the security requirements defined in the tachograph cards generic security target (Appendix 10).

183Tachograph cards shall be readable by other equipment such as personal computers.

3.   Standards

184The tachograph cards shall comply with the following standards:

 ISO/IEC 7810 Identification cards — Physical characteristics,

 ISO/IEC 7816 Identification cards — Integrated circuits with contacts:

 

 Part 1: Physical characteristics,

 Part 2: Dimensions and location of the contacts,

 Part 3: Electronic signals and transmission protocols,

 Part 4: Inter-industry commands for interchange,

 Part 8: Security related inter-industry commands,

 ISO/IEC 10373 Identification cards — Test methods.

4.   Environmental and electrical specifications

185The tachograph cards shall be capable of operating correctly in all the climatic conditions normally encountered in Community territory and at least in the temperature range - 25 oC to + 70 oC with occasional peaks of up to + 85 oC, ‘occasional’ meaning not more than 4 hours each time and not over 100 times during the lifetime of the card.

186The tachograph cards shall be capable of operating correctly in the humidity range 10 % to 90 %.

187The tachograph cards shall be capable of operating correctly for a five-year period if used within the environmental and electrical specifications.

188During operation, the tachograph cards shall conform to Commission Directive 95/54/EC of 31 October 1995 ( 21 ), related to electromagnetic compatibility, and shall be protected against electrostatic discharges.

5.   Data storage

For the purpose of this paragraph,

 times are recorded with a resolution of one minute, unless otherwise specified,

 odometer values are recorded with a resolution of one kilometre,

 speeds are recorded with a resolution of 1 km/h.

The tachograph cards functions, commands and logical structures, fulfilling data storage requirements are specified in Appendix 2.

189This paragraph specifies minimum storage capacity for the various application data files. The tachograph cards shall be able to indicate to the recording equipment the actual storage capacity of these data files.

Any additional data that may be stored on tachograph cards, related to other applications eventually borne by the card, shall be stored in accordance with Directive 95/46/EC of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data ( 22 ).

5.1.   Card identification and security data

5.1.1.   Application identification

190The tachograph cards shall be able to store the following application identification data:

 tachograph application identification,

 type of tachograph card identification.

5.1.2.   Chip identification

191The tachograph cards shall be able to store the following integrated circuit (IC) identification data:

 IC serial number,

 IC manufacturing references.

5.1.3.   IC card identification

192The tachograph cards shall be able to store the following smart card identification data:

 card serial number (including manufacturing references),

 card type approval number,

 card personaliser identification (ID),

 embedder ID,

 IC identifier.

5.1.4.   Security elements

193The tachograph cards shall be able to store the following security elements data:

 European public key,

 Member State certificate,

 card certificate,

 card private key.

5.2.   Driver card

5.2.1.   Card identification

194The driver card shall be able to store the following card identification data:

 card number,

 issuing Member State, issuing authority name, issue date,

 card beginning of validity date, card expiry date.

5.2.2.   Card holder identification

195The driver card shall be able to store the following card holder identification data:

 surname of the holder,

 first name(s) of the holder,

 date of birth,

 preferred language.

5.2.3.   Driving licence information

196The driver card shall be able to store the following driving licence data:

 issuing Member State, issuing authority name,

 driving licence number (at the date of the issue of the card).

5.2.4.   Vehicles used data

197The driver card shall be able to store, for each calendar day where the card has been used, and for each period of use of a given vehicle that day (a period of use includes all consecutive insertion/withdrawal cycle of the card in the vehicle, as seen from the card point of view), the following data:

 date and time of first use of the vehicle (i.e. first card insertion for this period of use of the vehicle, or 00.00 if the period of use is on-going at that time),

 vehicle odometer value at that time,

 date and time of last use of the vehicle, (i.e. last card withdrawal for this period of use of the vehicle, or 23.59 if the period of use is on-going at that time),

 vehicle odometer value at that time,

 VRN and registering Member State of the vehicle.

198The driver card shall be able to store at least 84 such records.

5.2.5.   Driver activity data

199The driver card shall be able to store, for each calendar day where the card has been used or for which the driver has entered activities manually, the following data:

 the date,

 a daily presence counter (increased by one for each of these calendar days),

 the total distance travelled by the driver during this day,

 a driver status at 00.00,

 whenever the driver has changed of activity, and/or has changed of driving status, and/or has inserted or withdrawn his card:

 

 the driving status (CREW, SINGLE),

 the slot (DRIVER, CO-DRIVER),

 the card status (INSERTED, NOT INSERTED),

 the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST),

 the time of the change.

200The driver card memory shall be able to hold driver activity data for at least 28 days (the average activity of a driver is defined as 93 activity changes per day).

201The data listed under requirements 197 and 199 shall be stored in a way allowing the retrieval of activities in the order of their occurrence, even in case of a time overlap situation.

5.2.6.   Places where daily work periods start and/or end

202The driver card shall be able to store the following data related to places where daily work periods begin and/or end, entered by the driver:

 the date and time of the entry (or the date/time related to the entry if the entry is made during the manual entry procedure),

 the type of entry (begin or end, condition of entry),

 the country and region entered,

 the vehicle odometer value.

203The driver card memory shall be able to hold at least 42 pairs of such records.

5.2.7.   Events data

For the purpose of this subparagraph, time shall be stored with a resolution of one second.

204The driver card shall be able to store data related to the following events detected by the recording equipment while the card was inserted:

 time overlap (where this card is the cause of the event),

 card insertion while driving (where this card is the subject of the event),

 last card session not correctly closed (where this card is the subject of the event),

 power supply interruption,

 motion data error,

 security breach attempts.

205The driver card shall be able to store the following data for these events:

 event code,

 date and time of beginning of the event (or of card insertion if the event was on-going at that time),

 date and time of end of the event (or of card withdrawal if the event was on-going at that time),

 VRN and registering Member State of vehicle in which the event happened.

Note: For the ‘time overlap’ event:

 date and time of beginning of the event shall correspond to the date and time of the card withdrawal from the previous vehicle,

 date and time of end of the event shall correspond to the date and time of card insertion in current vehicle,

 vehicle data shall correspond to the current vehicle raising the event.

Note: For the ‘last card session not correctly closed’ event:

 date and time of beginning of event shall correspond to the card insertion date and time of the session not correctly closed,

 date and time of end of event shall correspond to the card insertion date and time of the session during which the event was detected (current session),

 vehicle data shall correspond to the vehicle in which the session was not correctly closed.

206The driver card shall be able to store data for the six most recent events of each type (i.e. 36 events).

5.2.8.   Faults data

For the purpose of this subparagraph, time shall be recorded with a resolution of one second.

207The driver card shall be able to store data related to the following faults detected by the recording equipment while the card was inserted:

 card fault (where this card is the subject of the event),

 recording equipment fault.

208The driver card shall be able to store the following data for these faults:

 fault code,

 date and time of beginning of the fault (or of card insertion if the fault was on-going at that time),

 date and time of end of the fault (or of card withdrawal if the fault was on-going at that time),

 VRN and registering Member State of vehicle in which the fault happened.

209The driver card shall be able to store data for the twelve most recent faults of each type (i.e. 24 faults).

5.2.9.   Control activity data

210The driver card shall be able to store the following data related to control activities:

 date and time of the control,

 control card number and card issuing Member State,

 type of the control (displaying and/or printing and/or VU downloading and/or card downloading (see note)),

 period downloaded, in case of downloading,

 VRN and registering Member State of the vehicle in which the control happened.

Note: security requirements imply that card downloading will only be recorded if performed through a recording equipment.

211The driver card shall be able to hold one such record.

5.2.10.   Card session data

212The driver card shall be able to store data related to the vehicle which opened its current session:

 date and time the session was opened (i.e. card insertion) with a resolution of one second,

 VRN and registering Member State.

5.2.11.   Specific conditions data

212aThe driver card shall be able to store the following data related to specific conditions entered while the card was inserted (whatever the slot):

 date and time of the entry,

 type of specific condition.

212bThe driver card shall be able to hold 56 such records.

5.3.   Workshop card

5.3.1.   Security elements

213The workshop card shall be able to store a personal identification number (PIN code).

214The workshop card shall be able to store the cryptographic keys needed for pairing motion sensors to vehicle units.

5.3.2.   Card identification

215The workshop card shall be able to store the following card identification data:

 card number,

 issuing Member State, issuing authority name, issue date,

 card beginning of validity date, card expiry date.

5.3.3.   Card holder identification

216The workshop card shall be able to store the following card holder identification data:

 workshop name,

 workshop address,

 surname of the holder,

 first name(s) of the holder,

 preferred language.

5.3.4.   Vehicles used data

217The workshop card shall be able to store vehicles used data records in the same manner as a driver card.

218The workshop card shall be able to store at least 4 such records.

5.3.5.   Driver activity data

219The workshop card shall be able to store driver activity data in the same manner as a driver card.

220The workshop card shall be able to hold driver activity data for at least one day of average driver activity.

5.3.6.   Daily work periods start and/or end data

221The workshop card shall be able to store daily works period start and/or end data records in the same manner as a driver card.

222The workshop card shall be able to hold at least three pairs of such records.

5.3.7.   Events and faults data

223The workshop card shall be able to store events and faults data records in the same manner as a driver card.

224The workshop card shall be able to store data for the three most recent events of each type (i.e. 18 events) and the six most recent faults of each type (i.e. 12 faults).

5.3.8.   Control activity data

225The workshop card shall be able to store a control activity data record in the same manner as a driver card.

5.3.9.   Calibration and time adjustment data

226The workshop card shall be able to hold records of calibrations and/or time adjustments performed while the card is inserted in a recording equipment.

227Each calibration record shall be able to hold the following data:

  ►M10  purpose of calibration (activation, first installation, installation, periodic inspection) ◄ ,

 vehicle identification,

 parameters updated or confirmed (w, k, l, tyre size, speed limiting device setting, odometer (new and old values), date and time (new and old values),

 recording equipment identification (VU part number, VU serial number, motion sensor serial number).

228The workshop card shall be able to store at least 88 such records.

229The workshop card shall hold a counter indicating the total number of calibrations performed with the card.

230The workshop card shall hold a counter indicating the number of calibrations performed since its last download.

5.3.10.   Specific conditions data

230aThe workshop card shall be able to store data relevant to specific conditions in the same manner as the driver card. The workshop card shall be able to store two such records.

5.4.   Control card

5.4.1.   Card identification

231The control card shall be able to store the following card identification data:

 card number,

 issuing Member State, issuing authority name, issue date,

 card beginning of validity date, card expiry date (if any).

5.4.2.   Card holder identification

232The control card shall be able to store the following card holder identification data:

 control body name,

 control body address,

 surname of the holder,

 first name(s) of the holder,

 preferred language.

5.4.3.   Control activity data

233The control card shall be able to store the following control activity data:

 date and time of the control,

 type of the control (displaying and/or printing and/or VU downloading and/or card downloading),

 period downloaded (if any),

 VRN and Member State registering authority of the controlled vehicle,

 card number and card issuing Member State of the driver card controlled.

234The control card shall be able to hold at least 230 such records.

5.5.   Company card

5.5.1.   Card identification

235The company card shall be able to store the following card identification data:

 card number,

 issuing Member State, issuing authority name, issue date,

 card beginning of validity date, card expiry date (if any).

5.5.2.   Card holder identification

236The company card shall be able to store the following card holder identification data:

 company name,

 company address.

5.5.3.   Company activity data

237The company card shall be able to store the following company activity data:

 date and time of the activity,

 type of the activity (VU locking in and/or out, and/or VU downloading and/or card downloading),

 period downloaded (if any),

 VRN and Member State registering authority of vehicle,

 card number and card issuing Member State (in case of card downloading).

238The company card shall be able to hold at least 230 such records.

V.   INSTALLATION OF RECORDING EQUIPMENT

1.   Installation

239New recording equipment shall be delivered non-activated to fitters or vehicle manufacturers, with all calibration parameters, as listed in Chapter III(20), set to appropriate and valid default values. Where no particular value is appropriate, literal parameters shall be set to strings of ‘?’ and numeric parameters shall be set to ‘0’. ►M15  Delivery of security relevant parts of the recording equipment can be restricted if required during security certification. ◄

240Before its activation, the recording equipment shall give access to the calibration function even if not in calibration mode.

241Before its activation, the recording equipment shall neither record nor store data referred by points III.12.3. to III.12.9. and III.12.12 to III.12.14. inclusive.

242During installation, vehicle manufacturers shall pre-set all known parameters.

▼M15

243Vehicle manufacturers or fitters shall activate the installed recording equipment at the latest before the vehicle is used in scope of Regulation (EC) No. 561/2006.

▼M8

244The activation of the recording equipment shall be triggered automatically by the first insertion of a workshop card in either of its card interface devices.

245Specific pairing operations required between the motion sensor and the vehicle unit, if any, shall take place automatically before or during activation.

246After its activation, the recording equipment shall fully enforce functions and data access rights.

247The recording and storing functions of the recording equipment shall be fully operational after its activation.

▼M15

248Installation shall be followed by a calibration. The first calibration may not necessarily include entry of the vehicle registration number (VRN), when it is not known by the approved workshop having to undertake this calibration. In these circumstances, it shall be possible, for the vehicle owner, and at this time only, to enter the VRN using his Company Card prior to using the vehicle in scope of Regulation (EC) No. 561/2006 (e.g by using commands through an appropriate menu structure of the vehicle unit's man-machine interface.) ( 23 ). Any update or confirmation of this entry shall only be possible using a Workshop Card.

▼M8

248aThe recording equipment must be positioned in the vehicle in such a way as to allow the driver to access the necessary functions from his seat.

2.   Installation plaque

▼M15

249After the recording equipment has been checked on installation, an installation plaque which is clearly visible and easily accessible shall be affixed onto the recording equipment. In cases where this is not possible, the plaque shall be affixed to the vehicle's ‘B’ pillar so that it is clearly visible. For vehicles that do not have a ‘B’ pillar, the installation plaque should be affixed to the doorframe on the driver's side of the vehicle and be clearly visible in all cases. After every inspection by an approved fitter or workshop, a new plaque shall be affixed in place of the previous one.

▼M13

250The plaque shall bear at least the following details:

 name, address or trade name of the approved fitter or workshop,

 characteristic coefficient of the vehicle, in the form ‘w = … imp/km’,

 constant of the recording equipment, in the form ‘k = … imp/km’,

 effective circumference of the wheel tyres in the form ‘l = … mm’,

 tyre size,

▼M15

 the date on which the characteristic coefficient of the vehicle and the effective circumference of the wheel tyres were measured,

▼M13

 the vehicle identification number,

 the part of the vehicle where the adaptor, if any, is installed,

 the part of the vehicle where the motion sensor is installed, if not connected to the gear-box or an adaptor is not being used,

 a description of the colour of the cable between the adaptor and that part of the vehicle providing its incoming impulses,

 the serial number of the embedded motion sensor of the adaptor.

▼M15

250aFor M1 and N1 vehicles only, and which are fitted with an adaptor in conformity with Regulation (EC) No. 68/2009 ( 24 ), and where it is not possible to include all the information necessary, as described in Requirement 250, a second, additional, plaque may be used. In such cases, this additional plaque shall contain at least the last four indents described in Requirement 250. This second, additional plaque, if used, shall be affixed next to or beside the first primary plaque described in Requirement 250, and shall have the same protection level. Furthermore the secondary plaque shall also bear the name, address or trade name of the approved fitter or workshop that carried out the installation, and the date of installation.

▼M8

3.   Sealing

251The following part shall be sealed:

 any connection which, if disconnected, would cause undetectable alterations to be made or undetectable data loss,

 the installation plaque, unless it is attached in such a way that it cannot be removed without the markings thereon being destroyed.

252The seals mentioned above may be removed:

 in case of emergency,

 to install, to adjust or to repair a speed limitation device or any other device contributing to road safety, provided that the recording equipment continues to function reliably and correctly and is resealed by an approved fitter or workshop (in accordance with Chapter VI) immediately after fitting the speed limitation device or any other device contributing to road safety or within seven days in other cases.

253On each occasion that these seals are broken a written statement giving the reasons for such action shall be prepared and made available to the competent authority.

VI.   CHECKS, INSPECTIONS AND REPAIRS

Requirements on the circumstances in which seals may be removed, as referred to in Article 12.5 of Regulation (EEC) No 3821/85 as last amended by Regulation (EC) No 2135/98, are defined in Chapter V(3) of this annex.

1.   Approval of fitters or workshops

The Member States will approve, regularly control and certify the bodies to carry out:

 installations,

 checks,

 inspections,

 repairs.

In the framework of Article 12(1) of this Regulation, workshop cards will be issued only to fitters and/or workshops approved for the activation and/or the calibration of recording equipment in conformity with this annex and, unless duly justified:

 who are not eligible for a company card,

 and whose other professional activities do not present a potential compromise of the overall security of the system as defined in Appendix 10.

2.   Check of new or repaired instruments

254Every individual device, whether new or repaired, shall be checked in respect of its proper operation and the accuracy of its reading and recordings, within the limits laid down in Chapter III.2.1. and III.2.2 by means of sealing in accordance with Chapter V.3. and calibration.

3.   Installation inspection

255When being fitted to a vehicle, the whole installation (including the recording equipment) shall comply with the provisions relating to maximum tolerances laid down in Chapter III.2.1 and III.2.2.

4.   Periodic inspections

256Periodic inspections of the equipment fitted to the vehicles shall take place after any repair of the equipment, or after any alteration of the characteristic coefficient of the vehicle or of the effective circumference of the tyres, or after equipment UTC time is wrong by more than 20 minutes, or when the VRN has changed, and at least once within two years (24 months) of the last inspection.

257These inspections shall include the following checks:

 that the recording equipment is working properly, including the data storage in tachograph cards function,

 that compliance with the provisions of Chapter III.2.1 and III.2.2 on the maximum tolerances on installation is ensured,

 that the recording equipment carries the type approval mark,

▼M15

 that the installation plaque, as defined by Requirement 250, and the descriptive plaque, as defined by Requirement 169, are affixed,

▼M8

 that the seals on the equipment and on the other parts of the installation are intact,

 the tyre size and the actual circumference of the wheel tyres,

▼M15

 that there are no manipulation devices attached to the equipment.

257aIf one of the events listed in Chapter III Section 9 (Detection of Events and/or Faults) is found to have occurred since the last inspection and is considered by tachograph manufacturers and/or national authorities as potentially putting the security of the equipment at risk, the workshop shall:

(a) make a comparison between the motion sensor identification data of the motion sensor plugged into the gearbox with that of the paired motion sensor registered in the vehicle unit;

(b) check if the information recorded on the installation plaque matches with the information contained within the vehicle unit record;

(c) by checking if the motion sensor serial number and approval number, if printed on the body of the motion sensor, matches the information contained within the vehicle unit record.

257bWorkshops shall keep traces in their inspection reports of any findings concerning broken seals or manipulations devices. These reports shall be kept by workshops for at least two years and made available to the Competent Authority whenever requested to do so.

▼M8

258These inspections shall include a calibration.

5.   Measurement of errors

259The measurement of errors on installation and during use shall be carried out under the following conditions, which are to be regarded as constituting standard test conditions:

 vehicle unladen, in normal running order,

 tyre pressures in accordance with the manufacturer's instructions,

 tyre wear, within the limits allowed by national law,

 vehicle movement:

 

 the vehicle shall advance under its own engine power in a straight line on level ground and at a speed of 50 ± 5 km/h. The measuring distance shall be at least 1 000 m,

 provided that it is of comparable accuracy, alternative methods, such as a suitable test bench, may also be used for the test.

6.   Repairs

260Workshops shall be able to download data from the recording equipment to give the data back to the appropriate transport company.

261Approved workshops shall issue to transport companies a certificate of data un-downloadability where the malfunction of the recording equipment prevents previously recorded data to be downloaded, even after repair by this workshop. The workshops will keep a copy of each issued certificate for at least one year.

VII.   CARD ISSUING

The card issuing processes set-up by the Member States shall conform to the following:

262The card number of the first issue of a tachograph card to an applicant shall have a consecutive index (if applicable) and a replacement index and a renewal index set to ‘0’.

263The card numbers of all non-personal tachograph cards issued to a single control body or a single workshop or a single transport company shall have the same first 13 digits, and shall all have a different consecutive index.

264A tachograph card issued in replacement of an existing tachograph card shall have the same card number as the replaced one except the replacement index which shall be raised by ‘1’ (in the order 0, …, 9, A, …, Z).

265A tachograph card issued in replacement of an existing tachograph card shall have the same card expiry date as the replaced one.

266A tachograph card issued in renewal of an existing tachograph card shall have the same card number as the renewed one except the replacement index which shall be reset to ‘0’ and the renewal index which shall be raised by ‘1’ (in the order 0, …, 9, A, …, Z).

267The exchange of an existing tachograph card, in order to modify administrative data, shall follow the rules of the renewal if within the same Member State, or the rules of a first issue if performed by another Member State.

268The ‘card holder surname’ for non-personal workshop or control cards shall be filled with workshop or control body name.

▼M15

268aMember States shall exchange data electronically in order to ensure the uniqueness of the tachograph Driver Card that they issue. The competent authorities of Member States may also exchange data electronically when carrying out checks of driver cards at the roadside or at company premises in order to verify the uniqueness and status of the cards.

▼M8

VIII.   TYPE APPROVAL OF RECORDING EQUIPMENT AND TACHOGRAPH CARDS

1.   General points

For the purpose of this chapter, the words ‘recording equipment’ mean ‘recording equipment or its components’. No type approval is required for the cable(s) linking the motion sensor to the VU. The paper, for use by the recording equipment, shall be considered as a component of the recording equipment. ►M15  Any vehicle unit manufacturer may ask for type approval of its component with any type of motion sensor, and vice versa, provided each component complies with Requirement 001a. ◄

269Recording equipment shall be submitted for approval complete with any integrated additional devices.

270Type approval of recording equipment and of tachograph cards shall include security related tests, functional tests and interoperability tests. Positive results to each of these tests are stated by an appropriate certificate.

271Member States type approval authorities will not grant a type approval certificate in accordance with Article 5 of this Regulation, as long as they do not hold:

 a security certificate,

 a functional certificate,

 and an interoperability certificate,

for the recording equipment or the tachograph card, subject of the request for type approval.

272Any modification in software or hardware of the equipment or in the nature of materials used for its manufacture shall, before being used, be notified to the authority which granted type-approval for the equipment. This authority shall confirm to the manufacturer the extension of the type approval, or may require an update or a confirmation of the relevant functional, security and/or interoperability certificates.

273Procedures to upgrade in situ recording equipment software shall be approved by the authority which granted type approval for the recording equipment. Software upgrade must not alter nor delete any driver activity data stored in the recording equipment. Software may be upgraded only under the responsibility of the equipment manufacturer.

2.   Security certificate

274The security certificate is delivered in accordance with the provisions of Appendix 10 to this Annex.

▼M15

274aIn the exceptional circumstance that the security certification authorities refuse to certify new equipment on the grounds of obsolescence of the security mechanisms, type approval shall continue to be granted only in this specific and exceptional circumstance, and when no alternative solution, compliant with the Regulation, exists.

274bIn this circumstance the Member State concerned shall, without delay, inform the European Commission, which shall, within twelve calendar months of the grant of type approval, launch a procedure to ensure that the level of security is restored to its original levels.

▼M8

3.   Functional certificate

275Each candidate for type approval shall provide the Member State's type approval authority with all the material and documentation that the authority deems necessary.

▼M15

275aManufacturers shall provide the relevant samples of type approved products and associated documentation required by laboratories appointed to perform functional tests, and within one month of the request being made. Any costs resulting from this request shall be borne by the requesting entity. Laboratories shall treat all commercially sensitive information in confidence.

▼M8

276A functional certificate shall be delivered to the manufacturer only after all functional tests specified in Appendix 9, at least, have been successfully passed.

277The type approval authority delivers the functional certificate. This certificate shall indicate, in addition to the name of its beneficiary and the identification of the model, a detailed list of the tests performed and the results obtained.

▼M15

277aThe functional certificate of any recording equipment component shall also indicate the type approval numbers of all other type approved compatible recording equipment components.

▼M8

4.   Interoperability certificate

278Interoperability tests are carried out by a single laboratory under the authority and responsibility of the European Commission.

279The laboratory shall register interoperability test requests introduced by manufacturers in the chronological order of their arrival.

280Requests will be officially registered only when the laboratory is in possession of:

 the entire set of material and documents necessary for such interoperability tests,

 the corresponding security certificate,

 the corresponding functional certificate,

The date of the registration of the request shall be notified to the manufacturer.

▼M15

281No interoperability tests shall be carried out by the laboratory for recording equipment or tachograph cards that have not been granted a security certificate and a functionality certificate, except in the exceptional circumstances described in Requirement 274a.

▼M8

282Any manufacturer requesting interoperability tests shall commit to leave to the laboratory in charge of these tests the entire set of material and documents which he provided to carry out the tests.

283The interoperability tests shall be carried out, in accordance with the provisions of paragraph 5 of Appendix 9 of this Annex, with respectively all the types of recording equipment or tachograph cards:

 for which type approval is still valid, or

 for which type approval is pending and that have a valid interoperability certificate.

284The interoperability certificate shall be delivered by the laboratory to the manufacturer only after all required interoperability tests have been successfully passed.

285If the interoperability tests are not successful with one or more of the recording equipment or tachograph card(s), as requested by requirement 283, the interoperability certificate shall not be delivered, until the requesting manufacturer has realised the necessary modifications and has succeeded with the interoperability tests. The laboratory shall identify the cause of the problem with the help of the manufacturers concerned by this interoperability fault and shall attempt to help the requesting manufacturer in finding a technical solution. In the case where the manufacturer has modified its product, it is the manufacturer's responsibility to ascertain from the relevant authorities that the security certificate and the functional certificates are still valid.

286The interoperability certificate is valid for six months. It is revoked at the end of this period if the manufacturer has not received a corresponding type approval certificate. It is forwarded by the manufacturer to the type approval authority of the Member State who has delivered the functional certificate.

287Any element that could be at the origin of an interoperability fault shall not be used for profit or to lead to a dominant position.

5.   Type approval certificate

288The type approval authority of the Member State may deliver the type approval certificate as soon as it holds the three required certificates.

289The type approval certificate shall be copied by the type approval authority to the laboratory in charge of the interoperability tests at the time of deliverance to the manufacturer.

290The laboratory competent for interoperability tests shall run a public web site on which will be updated the list of recording equipment or tachograph cards models:

 for which a request for interoperability tests have been registered,

 having received an interoperability certificate (even provisional),

 having received a type approval certificate.

6.   Exceptional procedure: first interoperability certificates

291Until four months after a first couple of recording equipment and tachograph cards (driver, workshop, control and company cards) have been certified to be interoperable, any interoperability certificate delivered (including this very first one), regarding requests registered during this period, shall be considered provisional.

292If at the end of this period, all products concerned are mutually interoperable, all corresponding interoperability certificates shall become definitive.

293If during this period, interoperability faults are found, the laboratory in charge of interoperability tests shall identify the causes of the problems with the help of all manufacturers involved and shall invite them to realise the necessary modifications.

294If at the end of this period, interoperability problems still remain, the laboratory in charge of interoperability tests, with the collaboration of the manufacturers concerned and with the type approval authorities who delivered the corresponding functional certificates shall find out the causes of the interoperability faults and establish which modifications should be made by each of the manufacturers concerned. The search for technical solutions shall last for a maximum of two months, after which, if no common solution is found, the Commission, after having consulted the laboratory in charge of interoperability tests, shall decide which equipment(s) and cards get a definitive interoperability certificate and state the reasons why.

295Any request for interoperability tests, registered by the laboratory between the end of the four-month period after the first provisional interoperability certificate has been delivered and the date of the decision by the Commission referred to in requirement 294, shall be postponed until the initial interoperability problems have been solved. Those requests are then processed in the chronological order of their registration.




Appendix 1

DATA DICTIONARY

CONTENTS

1.

Introduction …

1.1.

Approach for definitions of data types …

1.2.

References …

2.

Data Type Definitions …

2.1.

ActivityChangeInfo …

2.2.

Address …

2.3.

BCDString …

2.4.

CalibrationPurpose …

2.5.

CardActivityDailyRecord …

2.6.

CardActivityLengthRange …

2.7.

CardApprovalNumber …

2.8.

CardCertificate …

2.9.

CardChipIdentification …

2.10.

CardConsecutiveIndex …

2.11.

CardControlActivityDataRecord …

2.12.

CardCurrentUse …

2.13.

CardDriverActivity …

2.14.

CardDrivingLicenceInformation …

2.15.

CardEventData …

2.16.

CardEventRecord …

2.17.

CardFaultData …

2.18.

CardFaultRecord …

2.19.

CardIccIdentification …

2.20.

CardIdentification …

2.21.

CardNumber …

2.22.

CardPlaceDailyWorkPeriod …

2.23.

CardPrivateKey …

2.24.

CardPublicKey …

2.25.

CardRenewalIndex …

2.26.

CardReplacementIndex …

2.27.

CardSlotNumber …

2.28.

CardSlotsStatus …

2.29.

CardStructureVersion …

2.30.

CardVehicleRecord …

2.31.

CardVehiclesUsed …

2.32.

Certificate …

2.33.

CertificateContent …

2.34.

CertificateHolderAuthorisation …

2.35.

CertificateRequestID …

2.36.

CertificationAuthorityKID …

2.37.

CompanyActivityData …

2.38.

CompanyActivityType …

2.39.

CompanyCardApplicationIdentification …

2.40.

CompanyCardHolderIdentification …

2.41.

ControlCardApplicationIdentification …

2.42.

ControlCardControlActivityData …

2.43.

ControlCardHolderIdentification …

2.44.

ControlType …

2.45.

CurrentDateTime …

2.46.

DailyPresenceCounter …

2.47.

Datef …

2.48.

Distance …

2.49.

DriverCardApplicationIdentification …

2.50.

DriverCardHolderIdentification …

2.51.

EntryTypeDailyWorkPeriod …

2.52.

EquipmentType …

2.53.

EuropeanPublicKey …

2.54.

EventFaultType …

2.55.

EventFaultRecordPurpose …

2.56.

ExtendedSerialNumber …

2.57.

FullCardNumber …

2.58.

HighResOdometer …

2.59.

HighResTripDistance …

2.60.

HolderName …

2.61.

K-ConstantOfRecordingEquipment …

2.62.

KeyIdentifier …

2.63.

L-TyreCircumference …

2.64.

Language …

2.65.

LastCardDownload …

2.66.

ManualInputFlag …

2.67.

ManufacturerCode …

2.68.

MemberStateCertificate …

2.69.

MemberStatePublicKey …

2.70.

Name …

2.71.

NationAlpha …

2.72.

NationNumeric …

2.73.

NoOfCalibrationRecords …

2.74.

NoOfCalibrationSinceDonwload …

2.75.

NoOfCardPlaceRecords …

2.76.

NoOfCardVehicleRecords …

2.77.

NoOfCompanyActivityRecords …

2.78.

NoOfControlActivityRecords …

2.79.

NoOfEventsPerType …

2.80.

NoOfFaultsPerType …

2.81.

OdometerValueMidnight …

2.82.

OdometerShort …

2.83.

OverspeedNumber …

2.84.

PlaceRecord …

2.85.

PreviousVehicleInfo …

2.86.

PublicKey …

2.87.

RegionAlpha …

2.88.

RegionNumeric …

2.89.

RSAKeyModulus …

2.90.

RSAKeyPrivateExponent …

2.91.

RSAKeyPublicExponent …

2.92.

SensorApprovalNumber …

2.93.

SensorIdentification …

2.94.

SensorInstallation …

2.95.

SensorInstallationSecData …

2.96.

SensorOSIdentifier …

2.97.

SensorPaired …

2.98.

SensorPairingDate …

2.99.

SensorSerialNumber …

2.100.

SensorSCIdentifier …

2.101.

Signature …

2.102.

SimilarEventsNumber …

2.103.

SpecificConditionType …

2.104.

SpecificConditionRecord …

2.105.

Speed …

2.106.

SpeedAuthorised …

2.107.

SpeedAverage …

2.108.

SpeedMax …

2.109.

TDesSessionKey …

2.110.

TimeReal …

2.111.

TyreSize …

2.112.

VehicleIdentificationNumber …

2.113.

VehicleRegistrationIdentification …

2.114.

VehicleRegistrationNumber …

2.115.

VuActivityDailyData …

2.116.

VuApprovalNumber …

2.117.

VuCalibrationData …

2.118.

VuCalibrationRecord …

2.119.

VuCardIWData …

2.120.

VuCardIWRecord …

2.121.

VuCertificate …

2.122.

VuCompanyLocksData …

2.123.

VuCompanyLocksRecord …

2.124.

VuControlActivityData …

2.125.

VuControlActivityRecord …

2.126.

VuDataBlockCounter …

2.127.

VuDetailedSpeedBlock …

2.128.

VuDetailedSpeedData …

2.129.

VuDownloadablePeriod …

2.130.

VuDownloadActivityData …

2.131.

VuEventData …

2.132.

VuEventRecord …

2.133.

VuFaultData …

2.134.

VuFaultRecord …

2.135.

VuIdentification …

2.136.

VuManufacturerAddress …

2.137.

VuManufacturerName …

2.138.

VuManufacturingDate …

2.139.

VuOverSpeedingControlData …

2.140.

VuOverSpeedingEventData …

2.141.

VuOverSpeedingEventRecord …

2.142.

VuPartNumber …

2.143.

VuPlaceDailyWorkPeriodData …

2.144.

VuPlaceDailyWorkPeriodRecord …

2.145.

VuPrivateKey …

2.146.

VuPublicKey …

2.147.

VuSerialNumber …

2.148.

VuSoftInstallationDate …

2.149.

VuSoftwareIdentification …

2.150.

VuSoftwareVersion …

2.151.

VuSpecificConditionData …

2.152.

VuTimeAdjustmentData …

2.153.

VuTimeAdjustmentRecord …

2.154.

W-VehicleCharacteristicConstant …

2.155.

WorkshopCardApplicationIdentification …

2.156.

WorkshopCardCalibrationData …

2.157.

WorkshopCardCalibrationRecord …

2.158.

WorkshopCardHolderIdentification …

2.159.

WorkshopCardPIN …

3.

Value and size range definitions …

3.1.

Definitions for the Driver Card …

3.2.

Definitions für the Workshop Card …

3.3.

Definitions for the Control Card …

3.4.

Definitions for the Company Card …

4.

Character sets …

5.

Encoding …

1.   INTRODUCTION

This appendix specifies data formats, data elements, and data structures for use within the recording equipment and tachograph cards.

1.1.   Approach for definitions of data types

This appendix uses Abstract Syntax Notation One (ASN.1) to define data types. This enables simple and structured data to be defined without implying any specific transfer syntax (encoding rules) which will be application and environment dependent.

ASN.1 type naming conventions are done in accordance with ISO/IEC 8824-1. This implies that:

 where possible, the meaning of the data type is implied through the names being selected,

 where a data type is a composition of other data types, the data type name is still a single sequence of alphabetical characters commencing with a capital letter, however capitals are used within the name to impart the corresponding meaning,

 in general, the data types names are related to the name of the data types from which they are constructed, the equipment in which data is stored and the function related to the data.

If an ASN.1 type is already defined as part of another standard and if it is relevant for usage in the recording equipment, then this ASN.1 type will be defined in this appendix.

To enable several types of encoding rules, some ASN.1 types in this appendix are constrained by value range identifiers. The value range identifiers are defined in paragraph 3.

1.2.   References

The following references are used in this Appendix:

ISO 639

Code for the representation of names of languages. First Edition: 1988

EN 726-3

Identification cards systems — Telecommunications integrated circuit(s) cards and terminals — Part 3: Application independent card requirements. December 1994

ISO 3779

Road vehicles — Vehicle identification number (VIN) — Content and structure. Edition 3: 1983

ISO/IEC 7816-5

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 5: Numbering system and registration procedure for application identifiers. First edition: 1994 + Amendment 1: 1996

ISO/IEC 8824-1

Information technology — Abstract Syntax Notation 1 (ASN.1): Specification of basic notation. Edition 2: 1998

ISO/IEC 8825-2

Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). Edition 2: 1998

ISO/IEC 8859-1

Information technology — 8 bit single-byte coded graphic character sets — Part 1: Latin alphabet No 1. First edition: 1998

ISO/IEC 8859-7

Information technology — 8 bit single-byte coded graphic character sets — Part 7: Latin/Greek alphabet. First edition: 1987

ISO 16844-3

Road vehicles — Tachograph systems — Motion Sensor Interface. WD 3-20/05/99.

2.   DATA TYPE DEFINITIONS

For any of the following data types, the default value for an ‘unknown’ or a ‘not applicable’ content will consist in filling the data element with ′FF′-Bytes.

2.1.   ActivityChangeInfo

This data type enables to code, within a two bytes word, a slot status at 00.00 and/or a driver status at 00.00 and/or changes of activity and/or changes of driving status and/or changes of card status for a driver or a co-driver. This data type is related to requirements 084, 109a, 199 and 219.

ActivityChangeInfo ::= OCTET STRING (SIZE(2))

Value assignment — Octet Aligned: ′scpaattttttttttt′B (16 bits)

For Data Memory recordings (or slot status):

′s′B

Slot:

′0′B: DRIVER,

′1′B: CO-DRIVER,

′c′B

Driving status:

′0′B: SINGLE,

′1′B: CREW,

′p′B

Driver (or workshop) card status in the relevant slot:

′0′B: INSERTED, a card is inserted,

1′B: NOT INSERTED, no card is inserted (or a card is withdrawn),

′aa′B

Activity:

′00′B: BREAK/REST,

′01′B: AVAILABILITY,

′10′B: WORK,

′11′B: DRIVING,

′ttttttttttt′B

Time of the change: Number of minutes since 00h00 on the given day.

For Driver (or Workshop) card recordings (and driver status):

′s′B

Slot (not relevant when ′p′ = 1 except note below):

′0′B: DRIVER,

′1′B: 2. CO-DRIVER,

′c′B



Driving status (case ′p′ = 0) or

Following activity status (case ′p′ = 1):

′0′B: SINGLE,

′0′B: UNKNOWN

′1′B: CREW,

′1′B: KNOWN (= manually entered)

′p′B

Card status:

′0′B: INSERTED, the card is inserted in a recording equipment,

′1′B: NOT INSERTED, the card is not inserted (or the card is withdrawn),

′aa′B

Activity (not relevant when ′p′ = 1 and ′c′ = 0 except note below):

′00′B: BREAK/REST,

′01′B: AVAILABILITY,

′10′B: WORK,

′11′B: DRIVING,

′ttttttttttt′B

Time of the change: Number of minutes since 00h00 on the given day.

Note for the case ‘card withdrawal’:

When the card is withdrawn:

 ′s′ is relevant and indicates the slot from which the card is withdrawn,

 ′c′ must be set to 0,

 ′p′ must be set to 1,

 ′aa′ must code the current activity selected at that time,

As a result of a manual entry, the bits ′c′ and ′aa′ of the word (stored in a card) may be overwritten later to reflect the entry.

▼M15

2.2.   Address

An address.

Address: = SEQUENCE {

codePage INTEGER (0..255),

address OCTET STRING (SIZE(35))

}

codePage specifies a character set defined in Chapter 4,

address is an address encoded using the specified character set.

▼M8

2.3.   BCDString

BCDString is applied for Binary Code Decimal (BCD) representation. This data type is used to represent one decimal digit in one semi octet (4 bits). BCDString is based on the ISO/IEC 8824-1 ′CharacterStringType′.

BCDString ::= CHARACTER STRING (WITH COMPONENTS {

identification ( WITH COMPONENTS {

fixed PRESENT }) })

BCDString uses an ‘hstring’ notation. The leftmost hexadecimal digit shall be the most significant semi octet of the first octet. To produce a multiple of octets, zero trailing semi octets shall be inserted, as needed, from the leftmost semi octet position in the first octet.

Permitted digits are: 0, 1, … 9.

2.4.   CalibrationPurpose

Code explaining why a set of calibration parameters was recorded. This data type is related to requirements 097 and 098.

CalibrationPurpose ::= OCTET STRING (SIZE(1)).

Value assignment:

′00′H

reserved value,

′01′H

activation: recording of calibration parameters known, at the moment of the VU activation,

′02′H

first installation: first calibration of the VU after its activation,

′03′H

installation: first calibration of the VU in the current vehicle,

′04′H

periodic inspection.

2.5.   CardActivityDailyRecord

Information, stored in a card, related to the driver activities for a particular calendar day. This data type is related to requirements 199 and 219.

CardActivityDailyRecord ::= SEQUENCE {

activityPreviousRecordLength INTEGER(0..CardActivityLengthRange),

image

activityRecordDate TimeReal,

activityDailyPresenceCounter DailyPresenceCounter,

activityDayDistance Distance,

activityChangeInfo SET SIZE(1..1 440 ) OF ActivityChangeInfo

}

activityPreviousRecordLength is the total length in bytes of the previous daily record. The maximum value is given by the length of the OCTET STRING containing these records (see CardActivityLengthRange paragraph 3). When this record is the oldest daily record, the value of activityPreviousRecordLength must be set to 0.

activityRecordLength is the total length in bytes of this record. The maximum value is given by the length of the OCTET STRING containing these records.

activityRecordDate is the date of the record.

activityDailyPresenceCounter is the daily presence counter for the card this day.

activityDayDistance is the total distance travelled this day.

activityChangeInfo is the set of ActivityChangeInfo data for the driver this day. It may contain at maximum 1 440 values (one activity change per minute). This set always includes the activityChangeInfo coding the driver status at 00.00.

2.6.   CardActivityLengthRange

Number of bytes in a driver or a workshop card, available to store driver activity records.

CardActivityLengthRange ::= INTEGER(0..216-1)

Value assignment: see paragraph 3.

2.7.   CardApprovalNumber

Type approval number of the card.

CardApprovalNumber ::= IA5String(SIZE(8))

Value assignment: Unspecified.

2.8.   CardCertificate

Certificate of the public key of a card.

CardCertificate ::= Certificate.

2.9.   CardChipIdentification

Information, stored in a card, related to the identification of the card's Integrated Circuit (IC) (requirement 191).

CardChipIdentification ::= SEQUENCE {

icSerialNumber OCTET STRING (SIZE(4)),

icManufacturingReferences OCTET STRING (SIZE(4))

}

icSerialNumber is the IC serial number as defined in EN 726-3.

icManufacturingReferences is the IC manufacturer identifier and fabrication elements as defined in EN 726-3.

2.10.   CardConsecutiveIndex

A card consecutive index (definition h)).

CardConsecutiveIndex ::= IA5String(SIZE(1))

Value assignment: (see this Annex Chapter VII)

Order for increase : ′0, …, 9, A, … , Z, a, … , z′.

2.11.   CardControlActivityDataRecord

Information, stored in a driver or workshop card, related to the last control the driver has been subject to (requirements 210 and 225).

CardControlActivityDataRecord ::= SEQUENCE {

controlType controlType,

controlTime TimeReal,

controlCardNumber FullCardNumber,

controlVehicleRegistration VehicleRegistrationIdentification,

controlDownloadPeriodBegin TimeReal,

controlDownloadPeriodEnd TimeReal,

}

controlType is the type of the control.

controlTime is the date and time of the control.

controlCardNumber is the FullCardNumber of the control officer having performed the control.

controlVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period downloaded, in case of downloading.

2.12.   CardCurrentUse

Information about the actual usage of the card (requirement 212).

CardCurrentUse ::= SEQUENCE {

sessionOpenTime TimeReal,

sessionOpenVehicle VehicleRegistrationIdentification

}

sessionOpenTime is the time when the card is inserted for the current usage. This element is set to zero at card removal.

sessionOpenVehicle is the identification of the currently used vehicle, set at card insertion. This element is set to zero at card removal.

2.13.   CardDriverActivity

Information, stored in a driver or a workshop card, related to the activities of the driver (requirements 199 and 219).

CardDriverActivity ::= SEQUENCE {

activityPointerOldestDayRecord INTEGER(0..CardActivityLengthRange-1),

activityPointerNewestRecord INTEGER(0..CardActivityLengthRange-1),

activityDailyRecords OCTET STRING (SIZE(CardActivityLengthRange))

}

activityPointerOldestDayRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the oldest complete day record in the activityDailyRecords string. The maximum value is given by the length of the string.

activityPointerNewestRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the most recent day record in the activityDailyRecords string. The maximum value is given by the length of the string.

activityDailyRecords is the space available to store the driver activity data (data structure: CardActivityDailyRecord) for each calendar day where the card has been used.

Value assignment: this octet string is cyclically filled with records of CardActivityDailyRecord. At the first use storing is started at the first byte of the string. All new records are appended at the end of the previous one. When the string is full, storing continues at the first byte of the string independently of a break being inside a data element. Before placing new activity data in the string (enlarging current activityDailyRecord, or placing a new activityDailyRecord) that replaces older activity data, activityPointerOldestDayRecord must be updated to reflect the new location of the oldest complete day record, and activityPreviousRecordLength of this (new) oldest complete day record must be reset to 0.

2.14.   CardDrivingLicenceInformation

Information, stored in a driver card, related to the card holder driver licence data (requirement 196).

CardDrivingLicenceInformation ::= SEQUENCE {

drivingLicenceIssuingAuthority Name,

drivingLicenceIssuingNation NationNumeric,

drivingLicenceNumber IA5String(SIZE(16))

}

drivingLicenceIssuingAuthority is the authority responsible for issuing the driving licence.

drivingLicenceIssuingNation is the nationality of the authority that issued the driving licence.

drivingLicenceNumber is the number of the driving licence.

2.15.   CardEventData

Information, stored in a driver or workshop card, related to the events associated with the card holder (requirements 204 and 223).

CardEventData ::= SEQUENCE SIZE(6) OF {

cardEventRecords SET SIZE(NoOfEventsPerType) OF CardEventRecord

}

CardEventData is a sequence, ordered by ascending value of EventFaultType, of cardEventRecords (except security breach attempts related records which are gathered in the last set of the sequence).

cardEventRecords is a set of event records of a given event type (or category for security breach attempts events).

2.16.   CardEventRecord

Information, stored in a driver or a workshop card, related to an event associated to the card holder (requirements 205 and 223).

CardEventRecord ::= SEQUENCE {

eventType EventFaultType,

eventBeginTime TimeReal,

eventEndTime TimeReal,

eventVehicleRegistration VehicleRegistrationIdentification

}

eventType is the type of the event.

eventBeginTime is the date and time of beginning of event.

eventEndTime is the date and time of end of event.

eventVehicleRegistration is the VRN and registering Member State of vehicle in which the event happened.

2.17.   CardFaultData

Information, stored in a driver or a workshop card, related to the faults associated to the card holder (requirements 207 and 223).

CardFaultData ::= SEQUENCE SIZE(2) OF {

cardFaultRecords SET SIZE(NoOfFaultsPerType) OF CardFaultRecord

}

CardFaultData is a sequence of Recording Equipment faults set of records followed by card faults set of records.

cardFaultRecords is a set of fault records of a given fault category (Recording Equipment or card).

2.18.   CardFaultRecord

Information, stored in a driver or a workshop card, related to a fault associated to the card holder (requirement 208 and 223).

CardFaultRecord ::= SEQUENCE {

faultType EventFaultType,

faultBeginTime TimeReal,

faultEndTime TimeReal,

faultVehicleRegistration VehicleRegistrationIdentification

}

faultType is the type of the fault.

faultBeginTime is the date and time of beginning of fault.

faultEndTime is the date and time of end of fault.

faultVehicleRegistration is the VRN and registering Member State of vehicle in which the fault happened.

2.19.   CardIccIdentification

Information, stored in a card, related to the identification of the integrated circuit (IC) card (requirement 192).

CardIccIdentification ::= SEQUENCE {

clockStop OCTET STRING (SIZE(1)),

cardExtendedSerialNumber ExtendedSerialNumber,

cardApprovalNumber CardApprovalNumber

cardPersonaliserID OCTET STRING (SIZE(1)),

embedderIcAssemblerId OCTET STRING (SIZE(5)),

icIdentifier OCTET STRING (SIZE(2))

}

clockStop is the Clockstop mode as defined in EN 726-3.

cardExtendedSerialNumber is the IC card serial number and IC card manufacturing reference as defined in EN 726-3 and as further specified by the ExtendedSerialNumber data type.

cardApprovalNumber is the type approval number of the card.

cardPersonaliserID is the card personaliser ID as defined in EN 726-3.

embedderIcAssemblerId is the embedder/IC assembler identifier as defined in EN 726-3.

icIdentifier is the Identifier of the IC on the card and its IC manufacturer as defined in EN 726-3.

2.20.   CardIdentification

Information, stored in a card, related to the identification of the card (requirements 194, 215, 231, 235).

CardIdentification ::= SEQUENCE

cardIssuingMemberState NationNumeric,

cardNumber CardNumber,

cardIssuingAuthorityName Name,

cardIssueDate TimeReal,

cardValidityBegin TimeReal,

cardExpiryDate TimeReal

}

cardIssuingMemberState is the code of the Member State issuing the card.

cardNumber is the card number of the card.

cardIssuingAuthorityName is the name of the authority having issued the Card.

cardIssueDate is the issue date of the Card to the current holder.

cardValidityBegin is the first date of validity of the card.

cardExpiryDate is the date when the validity of the card ends.

2.21.   CardNumber

A card number as defined by definition g).

CardNumber ::= CHOICE {

SEQUENCE {

driverIdentification IA5String(SIZE(14)),

cardReplacementIndex CardReplacementIndex,

cardRenewalIndex CardRenewalIndex

}

SEQUENCE {

ownerIdentification IA5String(SIZE(13)),

cardConsecutiveIndex CardConsecutiveIndex,

cardReplacementIndex CardReplacementIndex,

cardRenewalIndex CardRenewalIndex

}

}

driverIdentification is the unique identification of a driver in a Member State.

ownerIdentification is the unique identification of a company or a workshop or a control body within a Member State.

cardConsecutiveIndex is the card consecutive index.

cardReplacementIndex is the card replacement index.

cardRenewalIndex is the card renewal index.

The first sequence of the choice is suitable to code a driver card number, the second sequence of the choice is suitable to code workshop, control, and company card numbers.

2.22.   CardPlaceDailyWorkPeriod

Information, stored in a driver or a workshop card, related to the places where daily work periods begin and/or end (requirements 202 and 221).

image

}

placePointerNewestRecord is the index of the last updated place record.

Value assignment: Number corresponding to the numerator of the place record, beginning with ‘0’ for the first occurrence of the place records in the structure.

placeRecords is the set of records containing the information related to the places entered.

2.23.   CardPrivateKey

The private key of a card.

CardPrivateKey ::= RSAKeyPrivateExponent.

2.24.   CardPublicKey

The public key of a card.

CardPublicKey ::= PublicKey.

2.25.   CardRenewalIndex

A card renewal index (definition i)).

CardRenewalIndex ::= IA5String(SIZE(1)).

Value assignment: (see this Annex Chapter VII).

′0′

First issue.

Order for increase:

′0, …, 9, A, …, Z′.

2.26.   CardReplacementIndex

A card replacement index (definition j)).

CardReplacementIndex ::= IA5String(SIZE(1))

Value assignment: (see this Annex Chapter VII).

′0′

Original card.

Order for increase:

′0, …, 9, A, …, Z′.

2.27.   CardSlotNumber

Code to distinguish between the two slots of a vehicle unit.

CardSlotNumber ::= INTEGER {

driverSlot (0),

co-driverSlot (1)

}

Value assignment: not further specified.

2.28.   CardSlotsStatus

Code indicating the type of cards inserted in the two slots of the vehicle unit.

CardSlotsStatus ::= OCTET STRING (SIZE(1))

Value assignment — Octet Aligned: ′ccccdddd′B:

′cccc′B

Identification of the type of card inserted in the co-driver slot,

′dddd′B

Identification of the type of card inserted in the driver slot,

with the following identification codes:

′0000′B

no card is inserted,

′0001′B

a driver card is inserted,

′0010′B

a workshop card is inserted,

′0011′B

a control card is inserted,

′0100′B

a company card is inserted.

2.29.   CardStructureVersion

Code indicating the version of the implemented structure in a tachograph card.

CardStructureVersion ::= OCTET STRING (SIZE(2))

Value assignment: ′aabb′H:

▼M10

‘aa’H

Index for changes of the structure, ‘00h’ for this version

‘bb’H

Index for changes concerning the use of the data elements defined for the structure given by the high byte, ‘00h’ for this version.

▼M8

2.30.   CardVehicleRecord

Information, stored in a driver or workshop card, related to a period of use of a vehicle during a calendar day (requirements 197 and 217).

CardVehicleRecord ::= SEQUENCE {

vehicleOdometerBegin OdometerShort,

vehicleOdometerEnd OdometerShort,

vehicleFirstUse TimeReal,

vehicleLastUse TimeReal,

vehicleRegistration VehicleRegistrationIdentification,

vuDataBlockCounter VuDataBlockCounter

}

vehicleOdometerBegin is the vehicle odometer value at the beginning of the period of use of the vehicle.

vehicleOdometerEnd is the vehicle odometer value at the end of the period of use of the vehicle.

vehicleFirstUse is the date and time of the beginning of the period of use of the vehicle.

vehicleLastUse is the date and time of the end of the period of use of the vehicle.

vehicleRegistration is the VRN and the registering Member State of the vehicle.

vuDataBlockCounter is the value of the VuDataBlockCounter at last extraction of the period of use of the vehicle.

2.31.   CardVehiclesUsed

Information, stored in a driver or workshop card, related to the vehicles used by the card holder (requirements 197 and 217).

CardVehiclesUsed := SEQUENCE {

vehiclePointerNewestRecord INTEGER(0..NoOfCardVehicleRecords-1),

cardVehicleRecords SET SIZE(NoOfCardVehicleRecords) OF CardVehicleRecord

}

vehiclePointerNewestRecord is the index of the last updated vehicle record.

Value assignment: Number corresponding to the numerator of the vehicle record, beginning with ′0′ for the first occurrence of the vehicle records in the structure.

cardVehicleRecords is the set of records containing information on vehicles used.

2.32.   Certificate

The certificate of a public key issued by a Certification Authority.

Certificate ::= OCTET STRING (SIZE(194))

Value assignment: digital signature with partial recovery of a CertificateContent according to Appendix 11 ‘common security mechanisms’: Signature (128 bytes) Public Key remainder (58 Byte) Certification Authority Reference (8 bytes).

2.33.   CertificateContent

The (clear) content of the certificate of a public key according to Appendix 11 common security mechanisms.

CertificateContent ::= SEQUENCE {

certificateProfileIdentifier INTEGER(0..255),

certificationAuthorityReference KeyIdentifier,

certificateHolderAuthorisation CertificateHolderAuthorisation,

certificateEndOfValidity TimeReal,

certificateHolderReference KeyIdentifier,

publicKey PublicKey

}

certificateProfileIdentifier is the version of the corresponding certificate.

Value assignment:: ′01h′ for this version.

CertificationAuthorityReference identifies the Certification Authority issuing the certificate. It also references the Public Key of this Certification Authority.

certificateHolderAuthorisation identifies the rights of the certificate holder.

certificateEndOfValidity is the date when the certificate expires administratively.

certificateHolderReference identifies the certificate holder. It also references his Public Key.

publicKey is the public key that is certified by this certificate.

2.34.   CertificateHolderAuthorisation

Identification of the rights of a certificate holder.

CertificateHolderAuthorisation ::= SEQUENCE {

tachographApplicationID OCTET STRING(SIZE(6))

equipmentType EquipmentType

}

tachographApplicationID is the application identifier for the tachograph application.

Value assignment: ′FFh′ ′54h′ ′41h′ ′43h′ ′48h′ ′4Fh′. This AID is a proprietary non-registered application identifier in accordance with ISO/IEC 7816-5.

equipmentType is the identification of the type of equipment to which the certificate is intended.

Value assignment: in accordance with EquipmentType data type. 0 if certificate is the one of a Member State.

2.35.   CertificateRequestID

Unique identification of a certificate request. It can also be used as a Vehicle Unit Public Key Identifier if the serial number of the vehicle Unit to which the key is intended is not known at certificate generation time.

CertificateRequestID ::= SEQUENCE {

requestSerialNumber INTEGER(0..232-1)

requestMonthYear BCDString(SIZE(2))

crIdentifier OCTET STRING(SIZE(1))

manufacturerCode ManufacturerCode

}

requestSerialNumber is a serial number for the certificate request, unique for the manufacturer and the month below.

requestMonthYear is the identification of the month and the year of the certificate request.

Value assignment: BCD coding of month (two digits) and year (two last digits).

crIdentifier: is an identifier to distinguish a certificate request from an extended serial number.

Value assignment: ′FFh′.

manufacturerCode: is the numerical code of the manufacturer requesting the certificate.

2.36.   CertificationAuthorityKID

Identifier of the Public Key of a Certification Authority (a Member State or the European Certification Authority).

CertificationAuthorityKID ::= SEQUENCE {

nationNumeric NationNumeric

nationAlpha NationAlpha

keySerialNumber INTEGER(0..255)

additionalInfo OCTET STRING(SIZE(2))

caIdentifier OCTET STRING(SIZE(1))

}

nationNumeric is the numerical nation code of the Certification Authority.

nationAlpha is the alphanumerical nation code of the Certification Authority.

keySerialNumber is a serial number to distinguish the different keys of the Certification Authority in the case keys are changed.

additionalInfo is a two byte field for additional coding (Certification Authority specific).

caIdentifier is an identifier to distinguish a Certification Authority Key Identifier from other Key Identifiers.

Value assignment: ′01h′.

2.37.   CompanyActivityData

Information, stored in a company card, related to activities performed with the card (requirement 237).

CompanyActivityData ::= SEQUENCE {

companyPointerNewestRecord INTEGER(0..NoOfCompanyActivityRecords-1),

companyActivityRecords SET SIZE(NoOfCompanyActivityRecords) OF

companyActivityRecord SEQUENCE {

companyActivityType CompanyActivityType,

companyActivityTime TimeReal,

cardNumberInformation FullCardNumber,

vehicleRegistrationInformation VehicleRegistrationIdentification,

downloadPeriodBegin TimeReal,

downloadPeriodEnd TimeReal

}

}

companyPointerNewestRecord is the index of the last updated companyActivityRecord.

Value assignment: Number corresponding to the numerator of the company activity record, beginning with ′0′ for the first occurrence of the company activity record in the structure.

companyActivityRecords is the set of all company activity records.

companyActivityRecord is the sequence of information related to one company activity.

companyActivityType is the type of the company activity.

companyActivityTime is the date and time of the company activity.

cardNumberInformation is the card number and the card issuing Member State of the card downloaded, if any.

vehicleRegistrationInformation is the VRN and registering Member State of the vehicle downloaded or locked in or out.

downloadPeriodBegin and downloadPeriodEnd is the period downloaded from the VU, if any.

2.38.   CompanyActivityType

Code indicating an activity carried out by a company using its company card.

CompanyActivityType ::= INTEGER {

card downloading (1),

VU downloading (2),

VU lock-in (3),

VU lock-out (4)

}

2.39.   CompanyCardApplicationIdentification

Information, stored in a company card related to the identification of the application of the card (requirement 190).

CompanyCardApplicationIdentification ::= SEQUENCE {

typeOfTachographCardId EquipmentType,

cardStructureVersion CardStructureVersion,

noOfCompanyActivityRecords NoOfCompanyActivityRecords

}

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the version of the structure that is implemented in the card.

noOfCompanyActivityRecords is the number of company activity records the card can store.

2.40.   CompanyCardHolderIdentification

Information, stored in a company card, related to the cardholder identification (requirement 236).

CompanyCardHolderIdentification ::= SEQUENCE {

companyName Name,

companyAddress Address,

cardHolderPreferredLanguage Language

}

companyName is the name of the holder company.

companyAddress is the address of the holder company.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.41.   ControlCardApplicationIdentification

Information, stored in a control card related to the identification of the application of the card (requirement 190).

ControlCardApplicationIdentification ::= SEQUENCE {

typeOfTachographCardId EquipmentType,

cardStructureVersion CardStructureVersion,

noOfControlActivityRecords NoOfControlActivityRecords

}

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the version of the structure that is implemented in the card.

noOfControlActivityRecords is the number of control activity records the card can store.

2.42.   ControlCardControlActivityData

Information, stored in a control card, related to control activity performed with the card (requirement 233).

ControlCardControlActivityData ::= SEQUENCE {

controlPointerNewestRecord INTEGER(0..NoOfControlActivityRecords-1),

controlActivityRecords SET SIZE(NoOfControlActivityRecords) OF

controlActivityRecord SEQUENCE {

controlType ControlType,

controlTime TimeReal,

controlledCardNumber FullCardNumber,

controlledVehicleRegistration VehicleRegistrationIdentification,

controlDownloadPeriodBegin TimeReal,

controlDownloadPeriodEnd TimeReal

}

}

controlPointerNewestRecord is the index of the last updated control activity record.

Value assignment: Number corresponding to the numerator of the control activity record, beginning with ′0′ for the first occurrence of the control activity record in the structure.

controlActivityRecords is the set of all control activity records.

controlActivityRecord is the sequence of information related to one control.

controlType is the type of the control.

controlTime is the date and time of the control.

controlledCardNumber is the card number and the card issuing Member State of the card controlled.

controlledVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period eventually downloaded.

2.43.   ControlCardHolderIdentification

Information, stored in a control card, related to the identification of the cardholder (requirement 232).

ControlCardHolderIdentification ::= SEQUENCE {

controlBodyName Name,

controlBodyAddress Address,

cardHolderName HolderName,

cardHolderPreferredLanguage Language

}

controlBodyName is the name of the control body of the card holder.

controlBodyAddress is the address of the control body of the card holder.

cardHolderName is the name and first name(s) of the holder of the Control Card.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.44.   ControlType

Code indicating the activities carried out during a control. This data type is related to requirements 102, 210 and 225.

ControlType ::= OCTET STRING (SIZE(1))

Value assignment — Octet aligned:′cvpdxxxx′B (8 bits)

′c′B

card downloading:

′0′B: card not downloaded during this control activity,

′1′B: card downloaded during this control activity

′v′B

VU downloading:

′0′B: VU not downloaded during this control activity,

′1′B: VU downloaded during this control activity

′p′B

printing:

′0′B: no printing done during this control activity,

′1′B: printing done during this control activity

′d′B

display:

′0′B: no display used during this control activity,

′1′B: display used during this control activity

′xxxx′B

Not used.

2.45.   CurrentDateTime

The current date and time of the recording equipment.

CurrentDateTime ::= TimeReal

Value assignment: not further specified.

2.46.   DailyPresenceCounter

Counter, stored in a driver or workshop card, increased by one for each calendar day the card has been inserted in a VU. This data type is related to requirements 199 and 219.

DailyPresenceCounter ::= BCDString(SIZE(2))

Value assignment: Consecutive number with maximum value = 9 999 , starting again with 0. At the time of first issuing of the card the number is set to 0.

2.47.   Datef

Date expressed in a readily printable numeric format.

Datef ::= SEQUENCE {

year BCDString(SIZE(2)),

month BCDString(SIZE(1)),

day BCDString(SIZE(1))

}

Value assignment:

yyyy

Year

mm

Month

dd

Day

′00000000′H denotes explicitly no date.

2.48.   Distance

A distance travelled (result of the calculation of the difference between two vehicle's odometer value in kilometres).

Distance ::= INTEGER(0..216-1)

Value assignment: Unsigned binary. Value in km in the operational range 0 to 9 999 km.

2.49.   DriverCardApplicationIdentification

Information, stored in a driver card related to the identification of the application of the card (requirement 190).

DriverCardApplicationIdentification ::= SEQUENCE {

typeOfTachographCardId EquipmentType,

cardStructureVersion CardStructureVersion,

noOfEventsPerType NoOfEventsPerType,

noOfFaultsPerType NoOfFaultsPerType,

activityStructureLength CardActivityLengthRange,

noOfCardVehicleRecords NoOfCardVehicleRecords,

noOfCardPlaceRecords NoOfCardPlaceRecords

}

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the version of the structure that is implemented in the card.

noOfEventsPerType is the number of events per type of event the card can record.

noOfFaultsPerType is the number of faults per type of fault the card can record.

activityStructureLength indicates the number of bytes available for storing activity records.

noOfCardVehicleRecords is the number of vehicle records the card can contain.

noOfCardPlaceRecords is the number of places the card can record.

2.50.   DriverCardHolderIdentification

Information, stored in a driver card, related to the identification of the cardholder (requirement 195).

DriverCardHolderIdentification ::= SEQUENCE {

cardHolderName HolderName,

cardHolderBirthDate Datef,

cardHolderPreferredLanguage Language

}

cardHolderName is the name and first name(s) of the holder of the Driver Card.

cardHolderBirthDate is the date of birth of the holder of the Driver Card.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.51.   EntryTypeDailyWorkPeriod

Code to distinguish between begin and end for an entry of a daily work period place and condition of the entry.

EntryTypeDailyWorkPeriod ::= INTEGER

Begin, related time = card insertion time or time of entry (0),

End, related time = card withdrawal time or time of entry (1),

Begin, related time manually entered (start time) (2),

End, related time manually entered (end of work period) (3),

Begin, related time assumed by VU (4),

End, related time assumed by VU (5)

}

Value assignment: according to ISO/IEC8824-1.

2.52.   EquipmentType

Code to distinguish different types of equipment for the tachograph application.

EquipmentType ::= INTEGER(0..255)

- - Reserved (0),

- - Driver Card (1),

- - Workshop Card (2),

- - Control Card (3),

- - Company Card (4),

- - Manufacturing Card (5),

- - Vehicle Unit (6),

- - Motion Sensor (7),

- - RFU (8..255)

Value assignment: According to ISO/IEC 8824-1.

Value 0 is reserved for the purpose of designating a Member State or Europe in the CHA field of certificates.

2.53.   EuropeanPublicKey

The European public key.

EuropeanPublicKey ::= PublicKey.

2.54.   EventFaultType

Code qualifying an event or a fault.

EventFaultType ::= OCTET STRING (SIZE(1)).

Value assignment:

′0x′H

General events,

′00′H

No further details,

′01′H

Insertion of a non-valid card,

′02′H

Card conflict,

′03′H

Time overlap,

′04′H

Driving without an appropriate card,

′05′H

Card insertion while driving,

′06′H

Last card session not correctly closed,

′07′H

Over speeding,

′08′H

Power supply interruption,

′09′H

Motion data error,

▼M15

′0A′H

Vehicle Motion Conflict,

′0B′H to ′0F′H

RFU,

▼M8

′1x′H

Vehicle unit related security breach attempt events,

′10′H

No further details,

′11′H

Motion sensor authentication failure,

′12′H

Tachograph card authentication failure,

′13′H

Unauthorised change of motion sensor,

′14′H

Card data input integrity error

′15′H

Stored user data integrity error,

′16′H

Internal data transfer error,

′17′H

Unauthorised case opening,

′18′H

Hardware sabotage,

′19′H to ′1F′H

RFU,

′2x′H

Sensor related security breach attempt events,

′20′H

No further details,

′21′H

Authentication failure,

′22′H

Stored data integrity error,

′23′H

Internal data transfer error,

′24′H

Unauthorised case opening,

′25′H

Hardware sabotage,

′26′H to ′2F′H

RFU,

′3x′H

Recording equipment faults,

′30′H

No further details,

′31′H

VU internal fault,

′32′H

Printer fault,

′33′H

Display fault,

′34′H

Downloading fault,

′35′H

Sensor fault,

′36′H to ′3F′H

RFU

′4x′H

Card faults,

′40′H

No further details,

′41′H to ′4F′H

RFU

′50′H to ′7F′H

RFU,

′80′H to ′FF′H

Manufacturer specific.

2.55.   EventFaultRecordPurpose

Code explaining why an event or a fault has been recorded.

EventFaultRecordPurpose ::= OCTET STRING (SIZE(1)).

Value assignment:

′00′H

one of the 10 most recent (or last) events or faults

′01′H

the longest event for one of the last 10 days of occurrence

′02′H

one of the 5 longest events over the last 365 days

′03′H

the last event for one of the last 10 days of occurrence

′04′H

the most serious event for one of the last 10 days of occurrence

′05′H

one of the 5 most serious events over the last 365 days

′06′H

the first event or fault having occurred after the last calibration

′07′H

an active/on-going event or fault

′08′H to ′7F′H

RFU

′80′H to ′FF′H

manufacturer specific.

2.56.   ExtendedSerialNumber

Unique identification of an equipment. It can also be used as an equipment Public Key Identifier.

ExtendedSerialNumber ::= SEQUENCE {

serialNumber INTEGER(0..232-1)

monthYear BCDString(SIZE(2))

type OCTET STRING(SIZE(1))

manufacturerCode ManufacturerCode

}

serialNumber is a serial number for the equipment, unique for the manufacturer, the equipment's type and the month below.

monthYear is the identification of the month and the year of manufacturing (or of serial number assignment).

Value assignment: BCD coding of Month (two digits) and Year (two last digits).

type is an identifier of the type of equipment.

Value assignment: manufacturer specific, with FFh' reserved value.

manufacturerCode: is the numerical code of the manufacturer of the equipment.

2.57.   FullCardNumber

Code fully identifying a tachograph card.

FullCardNumber ::= SEQUENCE {

cardType EquipmentType,

cardIssuingMemberState NationNumeric,

cardNumber CardNumber

}

cardType is the type of the tachograph card.

cardIssuingMemberState is the code of the Member State having issued the card.

cardNumber is the card number.

2.58.   HighResOdometer

Odometer value of the vehicle: Accumulated distance travelled by the vehicle during its operation.

HighResOdometer ::= INTEGER(0..232-1)

Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.

2.59.   HighResTripDistance

A distance travelled during all or part of a journey.

HighResTripDistance ::= INTEGER(0..232-1)

Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.

2.60.   HolderName

The surname and first name(s) of a card holder.

HolderName ::= SEQUENCE {

holderSurname Name,

holderFirstNames Name

}

holderSurname is the surname (family name) of the holder. This surname does not include titles.

Value assignment: When a card is not personal, holderSurname contains the same information as companyName or workshopName or controlBodyName.

holderFirstNames is the first name(s) and initials of the holder.

2.61.   K-ConstantOfRecordingEquipment

Constant of the recording equipment (definition m)).

K-ConstantOfRecordingEquipment ::= INTEGER(0..216-1)

Value assignment: Pulses per kilometre in the operating range 0 to 64 255 pulses/km.

2.62.   KeyIdentifier

A unique identifier of a Public Key used to reference and select the key. It also identifies the holder of the key.

KeyIdentifier ::= CHOICE {

extendedSerialNumber ExtendedSerialNumber,

certificateRequestID CertificateRequestID,

certificationAuthorityKID CertificationAuthorityKID

}

The first choice is suitable to reference the public key of a Vehicle Unit or of a tachograph card.

The second choice is suitable to reference the public key of a Vehicle Unit (in the case the serial number of the Vehicle Unit cannot be known at certificate generation time).

The third choice is suitable to reference the public key of a Member State.

2.63.   L-TyreCircumference

Effective circumference of the wheel tyres (definition u)).

L-TyreCircumference ::= INTEGER(0..216-1)

Value assignment: Unsigned binary, value in 1/8 mm in the operating range 0 to 8 031 mm.

2.64.   Language

Code identifying a language.

Language ::= IA5String(SIZE(2))

Value assignment: Two-letter lower-case coding according to ISO 639.

2.65.   LastCardDownload

Date and time, stored on a driver card, of last card download (for other purposes than control). This date is updateable by a VU or any card reader.

LastCardDownload ::= TimeReal

Value assignment: not further specified.

2.66.   ManualInputFlag

Code identifying whether a cardholder has manually entered driver activities at card insertion or not (requirement 081).

ManualInputFlag ::= INTEGER {

noEntry (0)

manualEntries (1)

}

Value assignment: not further specified.

▼M15

2.67.   ManufacturerCode

Code identifying a manufacturer of type-approved equipment.

ManufacturerCode: = INTEGER (0..255)

The laboratory competent for interoperability tests maintains and publishes the list of manufacturer codes on its web site (requirement 290).

ManufacturerCodes are provisionally assigned to developers of tachograph equipment on application to the laboratory competent for interoperability tests.

▼M8

2.68.   MemberStateCertificate

The certificate of the public key of a Member State issued by the European certification authority.

MemberStateCertificate ::= Certificate

2.69.   MemberStatePublicKey

The public key of a Member State.

MemberStatePublicKey ::= PublicKey.

▼M15

2.70.   Name

A name.

Name: = SEQUENCE {

codePage INTEGER (0..255),

name OCTET STRING (SIZE(35))

}

codePage specifies a character set defined in Chapter 4,

name is a name encoded using the specified character set.

2.71.   NationAlpha

Alphabetic reference to a country shall be in accordance with the distinguishing signs used on vehicles in international traffic (United Nations Vienna Convention on Road Traffic, 1968).

NationAlpha: = IA5String (SIZE (3))

The Nation Alpha and Numeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing, as set out in Requirement 278.

2.72.   NationNumeric

Numerical reference to a country.

NationNumeric: = INTEGER (0.. 255)

Value assignment: see data type 2.71 (NationAlpha)

Any amendment or updating of the Nation Alpha or Numeric specification described in the above paragraph shall only be made out after the appointed laboratory has obtained the views of type approved digital tachograph vehicle unit manufacturers.

▼M8

2.73.   NoOfCalibrationRecords

Number of calibration records, a workshop card can store.

NoOfCalibrationRecords ::= INTEGER(0..255)

Value assignment: see paragraph 3.

2.74.   NoOfCalibrationsSinceDownload

Counter indicating the number of calibrations performed with a workshop card since its last download (requirement 230).

NoOfCalibrationsSinceDownload ::= INTEGER(0..216-1),

Value assignment: Not specified further.

2.75.   NoOfCardPlaceRecords

Number of place records a driver or workshop card can store.

NoOfCardPlaceRecords ::= INTEGER(0..255)

Value assignment: see paragraph 3.

2.76.   NoOfCardVehicleRecords

Number of vehicles used records a driver or workshop card can store.

NoOfCardVehicleRecords ::= INTEGER(0..216-1)

Value assignment: see paragraph 3.

2.77.   NoOfCompanyActivityRecords

Number of company activity records, a company card can store.

NoOfCompanyActivityRecords ::= INTEGER(0..216-1)

Value assignment: see paragraph 3.

2.78.   NoOfControlActivityRecords

Number of control activity records, a control card can store.

NoOfControlActivityRecords ::= INTEGER(0..216-1)

Value assignment: see paragraph 3.

2.79.   NoOfEventsPerType

Number of events per type of event a card can store.

NoOfEventsPerType ::= INTEGER(0..255)

Value assignment: see paragraph 3.

2.80.   NoOfFaultsPerType

Number of faults per type of fault a card can store.

NoOfFaultsPerType ::= INTEGER(0..255)

Value assignment: see paragraph 3.

2.81.   OdometerValueMidnight

The vehicle's odometer value at midnight on a given day (requirement 090).

OdometerValueMidnight ::= OdometerShort

Value assignment: not further specified.

2.82.   OdometerShort

Odometer value of the vehicle in a short form.

OdometerShort ::= INTEGER(0..224-1)

Value assignment: Unsigned binary. Value in km in the operating range 0 to 9 999 999 km.

2.83.   OverspeedNumber

Number of over speeding events since the last over speeding control.

OverspeedNumber ::= INTEGER(0..255)

Value assignment: 0 means that no over speeding event has occurred since the last over speeding control, 1 means that one over speeding event has occurred since the last over speeding control … 255 means that 255 or more over speeding events have occurred since the last over speeding control.

2.84.   PlaceRecord

Information related to a place where a daily work period begins or ends (requirements 087, 202, 221).

PlaceRecord ::= SEQUENCE {

entryTime TimeReal,

entryTypeDailyWorkPeriod EntryTypeDailyWorkPeriod,

dailyWorkPeriodCountry NationNumeric,

dailyWorkPeriodRegion RegionNumeric,

vehicleOdometerValue OdometerShort

}

entryTime is a date and time related to the entry.

entryTypeDailyWorkPeriod is the type of entry.

dailyWorkPeriodCountry is the country entered.

dailyWorkPeriodRegion is the region entered.

vehicleOdometerValue is the odometer value at the time of place entry.

2.85.   PreviousVehicleInfo

Information related to the vehicle previously used by a driver when inserting his card in a vehicle unit (requirement 081).

PreviousVehicleInfo ::= SEQUENCE {

vehicleRegistrationIdentification VehicleRegistrationIdentification,

cardWithdrawalTime TimeReal

}

vehicleRegistrationIdentification is the VRN and the registering Member State of the vehicle.

cardWithdrawalTime is the card withdrawal date and time.

2.86.   PublicKey

A public RSA key.

PublicKey ::= SEQUENCE {

rsaKeyModulus RSAKeyModulus,

rsaKeyPublicExponent RSAKeyPublicExponent

}

rsaKeyModulus is the Modulus of the key pair.

rsaKeyPublicExponent is the public exponent of the key pair.

2.87.   RegionAlpha

Alphabetic reference to a region within a specified country.

RegionAlpha ::= IA5STRING(SIZE(3))

image

2.88.   RegionNumeric

Numerical reference to a region within a specified country.

RegionNumeric ::= OCTET STRING (SIZE(1))

Value assignment:

′00′HNo information available

Spain:

′01′H

Andalucía

′02′H

Aragón

′03′H

Asturias

′04′H

Cantabria

′05′H

Cataluña

′06′H

Castilla-León

′07′H

Castilla-La-Mancha

′08′H

Valencia

′09′H

Extremadura

′0A′H

Galicia

′0B′H

Baleares

′0C′H

Canarias

′0D′H

La Rioja

′0E′H

Madrid

′0F′H

Murcia

′10′H

Navarra

′11′H

País Vasco.

2.89.   RSAKeyModulus

The modulus of a RSA key pair.

RSAKeyModulus ::= OCTET STRING (SIZE(128))

Value assignment: Unspecified.

2.90.   RSAKeyPrivateExponent

The private exponent of a RSA key pair.

RSAKeyPrivateExponent ::= OCTET STRING (SIZE(128))

Value assignment: Unspecified.

2.91.   RSAKeyPublicExponent

The public exponent of a RSA key pair.

RSAKeyPublicExponent ::= OCTET STRING (SIZE(8))

Value assignment: Unspecified.

2.92.   SensorApprovalNumber

Type approval number of the sensor.

SensorApprovalNumber ::= IA5String(SIZE(8))

Value assignment: Unspecified.

2.93.   SensorIdentification

Information, stored in a motion sensor, related to the identification of the motion sensor (requirement 077).

SensorIdentification ::= SEQUENCE {

sensorSerialNumber SensorSerialNumber,

sensorApprovalNumber SensorApprovalNumber,

sensorSCIdentifier SensorSCIdentifier,

sensorOSIdentifier SensorOSIdentifier

}

sensorSerialNumber is the extended serial number of the motion sensor (includes part number and manufacturer code).

sensorApprovalNumber is the approval number of the motion sensor.

sensorSCIdentifier is the identifier of the security component of the motion sensor.

sensorOSIdentifier is the identifier of the operating system of the motion sensor.

2.94.   SensorInstallation

Information, stored in a motion sensor, related to the installation of the motion sensor (requirement 099).

SensorInstallation ::= SEQUENCE {

sensorPairingDateFirst SensorPairingDate,

firstVuApprovalNumber VuApprovalNumber,

firstVuSerialNumber VuSerialNumber,

sensorPairingDateCurrent SensorPairingDate,

currentVuApprovalNumber VuApprovalNumber,

currentVUSerialNumber VuSerialNumber

}

sensorPairingDateFirst is the date of the first pairing of the motion sensor with a vehicle unit.

firstVuApprovalNumber is the approval number of the first vehicle unit paired with the motion sensor.

firstVuSerialNumber is the serial number of the first vehicle unit paired with the motion sensor.

sensorPairingDateCurrent is the date of the current pairing of the motion sensor with the vehicle unit.

currentVuApprovalNumber is the approval number of the vehicle unit currently paired with the motion sensor.

currentVUSerialNumber is the serial number of the vehicle unit currently paired with the motion sensor.

2.95.   SensorInstallationSecData

Information, stored in a workshop card, related to the security data needed for pairing motion sensors to vehicle units (requirement 214).

SensorInstallationSecData ::= TDesSessionKey

Value assignment: in accordance with ISO 16844-3.

2.96.   SensorOSIdentifier

Identifier of the operating system of the motion sensor.

SensorOSIdentifier ::= IA5String(SIZE(2))

Value assignment: manufacturer specific.

2.97.   SensorPaired

Information, stored in a vehicle unit, related to the identification of the motion sensor paired with the vehicle unit (requirement 079).

SensorPaired ::= SEQUENCE {

sensorSerialNumber SensorSerialNumber,

sensorApprovalNumber SensorApprovalNumber,

sensorPairingDateFirst SensorPairingDate

}

sensorSerialNumber is the serial number of the motion sensor currently paired with the vehicle unit.

sensorApprovalNumber is the approval number of the motion sensor currently paired with the vehicle unit.

sensorPairingDateFirst is the date of the first pairing with a vehicle unit of the motion sensor currently paired with the vehicle unit.

2.98.   SensorPairingDate

Date of a pairing of the motion sensor with a vehicle unit.

SensorPairingDate ::= TimeReal

Value assignment: Unspecified.

2.99.   SensorSerialNumber

Serial number of the motion sensor.

SensorSerialNumber ::= ExtendedSerialNumber:

2.100.   SensorSCIdentifier

Identifier of the security component of the motion sensor.

SensorSCIdentifier ::= IA5String(SIZE(8))

Value assignment: component manufacturer specific.

2.101.   Signature

A digital signature.

Signature ::= OCTET STRING (SIZE(128))

Value assignment: in accordance with Appendix 11, ‘Common security mechanisms’.

2.102.   SimilarEventsNumber

The number of similar events for one given day (requirement 094).

SimilarEventsNumber ::= INTEGER(0..255)

Value assignment: 0 is not used, 1 means that only one event of that type have occurred and have been stored on that day, 2 means that 2 events of that type have occurred on that day (one only has been stored), … 255 means that 255 or more events of that type have occurred on that day.

2.103.   SpecificConditionType

Code identifying a specific condition (requirements 050b, 105a, 212a and 230a).

SpecificConditionType ::= INTEGER(0..255)

Value assignment:

′00′H

RFU

′01′H

Out of scope — Begin

′02′H

Out of scope — End

′03′H

Ferry/Train crossing

′04′H .. ′FF′H

RFU.

2.104.   SpecificConditionRecord

Information, stored in a driver card, a workshop card or a vehicle unit, related to a specific condition (requirements 105a, 212a and 230a).

SpecificConditionRecord ::= SEQUENCE {

entryTime TimeReal,

specificConditionType SpecificConditionType

}

entryTime is the date and time of the entry.

specificConditionType is the code identifying the specific condition.

2.105.   Speed

Speed of the vehicle (km/h).

Speed ::= INTEGER(0..255)

Value assignment: kilometre per hour in the operational range 0 to 220 km/h.

2.106.   SpeedAuthorised

Maximum authorised Speed of the vehicle (definition bb)).

SpeedAuthorised ::= Speed.

2.107.   SpeedAverage

Average speed in a previously defined duration (km/h).

SpeedAverage ::= Speed.

2.108.   SpeedMax

Maximum speed measured in a previously defined duration.

SpeedMax ::= Speed.

2.109.   TDesSessionKey

A triple DES session key.

TDesSessionKey ::= SEQUENCE {

tDesKeyA OCTET STRING (SIZE(8))

tDesKeyB OCTET STRING (SIZE(8))

}

Value assignment: not further specified.

2.110.   TimeReal

Code for a combined date and time field, where the date and time are expressed as seconds past 00h.00m.00s. on 1 January 1970 GMT.

TimeReal{INTEGER:TimeRealRange} ::= INTEGER(0..TimeRealRange)

Value assignment — Octet Aligned: Number of seconds since midnight 1 January 1970 GMT.

The max possible date/time is in the year 2106.

2.111.   TyreSize

Designation of tyre dimensions.

TyreSize ::= IA5String(SIZE(15))

Value assignment: in accordance with Directive 92/23 (EEC) 31.3.1992, OJ L 129, p. 95.

2.112.   VehicleIdentificationNumber

Vehicle Identification Number (VIN) referring to the vehicle as a whole, normally chassis serial number or frame number.

VehicleIdentificationNumber ::= IA5String(SIZE(17))

Value assignment: As defined in ISO 3779.

2.113.   VehicleRegistrationIdentification

Identification of a vehicle, unique for Europe (VRN and Member State).

VehicleRegistrationIdentification ::= SEQUENCE {

vehicleRegistrationNation NationNumeric,

vehicleRegistrationNumber VehicleRegistrationNumber

}

vehicleRegistrationNation is the nation where the vehicle is registered.

vehicleRegistrationNumber is the registration number of the vehicle (VRN).

▼M15

2.114.   VehicleRegistrationNumber

Registration number of the vehicle (VRN). The registration number is assigned by the vehicle licensing authority.

VehicleRegistrationNumber: = SEQUENCE {

codePage INTEGER (0..255),

vehicleRegNumber OCTET STRING (SIZE(13))

}

codePage specifies a character set defined in Chapter 4,

vehicleRegNumber is a VRN encoded using the specified character set.

Value assignment: Country specific.

▼M8

2.115.   VuActivityDailyData

Information, stored in a VU, related to changes of activity and/or changes of driving status and/or changes of card status for a given calendar day (requirement 084) and to slots status at 00.00 that day.

VuActivityDailyData ::= SEQUENCE {

noOfActivityChanges INTEGER SIZE(0..1 440 ),

activityChangeInfos SET SIZE(noOfActivityChanges) OF ActivityChangeInfo

}

noOfActivityChanges is the number of ActivityChangeInfo words in the activityChangeInfos set.

activityChangeInfos is the set of ActivityChangeInfo words stored in the VU for the day. It always includes two ActivityChangeInfo words giving the status of the two slots at 00.00 that day.

2.116.   VuApprovalNumber

Type approval number of the vehicle unit.

VuApprovalNumber ::= IA5String(SIZE(8))

Value assignment: Unspecified.

2.117.   VuCalibrationData

Information, stored in a vehicle unit, related to the calibrations of the recording equipment (requirement 098).

VuCalibrationData ::= SEQUENCE {

noOfVuCalibrationRecords INTEGER(0..255),

vuCalibrationRecords SET SIZE(noOfVuCalibrationRecords) OF VuCalibrationRecord

}

noOfVuCalibrationRecords is the number of records contained in the vuCalibrationRecords set.

vuCalibrationRecords is the set of calibration records.

2.118.   VuCalibrationRecord

Information, stored in a vehicle unit, related a calibration of the recording equipment (requirement 098).

VuCalibrationRecord ::= SEQUENCE {

calibrationPurpose CalibrationPurpose,

workshopName Name,

workshopAddress Address,

workshopCardNumber FullCardNumber,

workshopCardExpiryDate TimeReal,

vehicleIdentificationNumber VehicleIdentificationNumber,

vehicleRegistrationIdentification VehicleRegistrationIdentification,

wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,

kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,

lTyreCircumference L-TyreCircumference,

tyreSize TyreSize,

authorisedSpeed SpeedAuthorised,

oldOdometerValue OdometerShort,

newOdometerValue OdometerShort,

oldTimeValue TimeReal,

newTimeValue TimeReal,

nextCalibrationDate TimeReal

}

calibrationPurpose is the purpose of the calibration.

workshopName, workshopAddress are the workshop name and address.

workshopCardNumber identifies the workshop card used during the calibration.

workshopCardExpiryDate is the card expiry date.

vehicleIdentificationNumber is the VIN.

vehicleRegistrationIdentification contains the VRN and registering Member State.

wVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.

kConstantOfRecordingEquipment is the constant of the recording equipment.

lTyreCircumference is the effective circumference of the wheel tyres.

tyreSize is the designation of the dimension of the tyres mounted on the vehicle.

authorisedSpeed is the authorised speed of the vehicle.

oldOdometerValue, newOdometerValue are the old and new values of the odometer.

oldTimeValue, newTimeValue are the old and new values of date and time.

nextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.

2.119.   VuCardIWData

Information, stored in a vehicle unit, related to insertion and withdrawal cycles of driver cards or of workshop cards in the vehicle unit (requirement 081).

image

}

noOfIWRecords is the number of records in the set vuCardIWRecords.

vuCardIWRecords is a set of records related to card insertion withdrawal cycles.

2.120.   VuCardIWRecord

Information, stored in a vehicle unit, related to an insertion and withdrawal cycle of a driver card or of a workshop card in the vehicle unit (requirement 081).

VuCardIWRecord ::= SEQUENCE {

cardHolderName HolderName,

fullCardNumber FullCardNumber,

cardExpiryDate TimeReal,

cardInsertionTime TimeReal,

vehicleOdometerValueAtInsertion OdometerShort,

cardSlotNumber CardSlotNumber,

cardWithdrawalTime TimeReal,

vehicleOdometerValueAtWithdrawal OdometerShort,

previousVehicleInfo PreviousVehicleInfo

manualInputFlag ManualInputFlag

}

cardHolderName is the driver or workshop card holder's surname and first names as stored in the card.

fullCardNumber is the type of card, its issuing Member State and its card number as stored in the card.

cardExpiryDate is the card's expiry date as stored in the card.

cardInsertionTime is the insertion date and time.

vehicleOdometerValueAtInsertion is the vehicle odometer value at card insertion.

cardSlotNumber is the slot in which the card is inserted.

cardWithdrawalTime is the withdrawal date and time.

vehicleOdometerValueAtWithdrawal is the vehicle odometer value at card withdrawal.

previousVehicleInfo contains information about the previous vehicle used by the driver, as stored in the card.

manualInputFlag is a flag identifying if the cardholder has manually entered driver activities at card insertion.

2.121.   VuCertificate

Certificate of the public key of a vehicle unit.

VuCertificate ::= Certificate

2.122.   VuCompanyLocksData

Information, stored in a vehicle unit, related to company locks (requirement 104).

VuCompanyLocksData ::= SEQUENCE {

noOfLocks INTEGER(0..20),

vuCompanyLocksRecords SET SIZE(noOfLocks) OF VuCompanyLocksRecord

}

noOfLocks is the number of locks listed in vuCompanyLocksRecords.

vuCompanyLocksRecords is the set of company locks records.

2.123.   VuCompanyLocksRecord

Information, stored in a vehicle unit, related to one company lock (requirement 104).

VuCompanyLocksRecord ::= SEQUENCE {

lockInTime TimeReal,

lockOutTime TimeReal,

companyName Name,

companyAddress Address,

companyCardNumber FullCardNumber

}

lockInTime, lockOutTime are the date and time of lock-in and lock-out.

companyName, companyAddress are the company name and address related with the lock-in.

companyCardNumber identifies the card used at lock-in.

2.124.   VuControlActivityData

Information, stored in a vehicle unit, related to controls performed using this VU (requirement 102).

VuControlActivityData ::= SEQUENCE {

noOfControls INTEGER(0..20),

vuControlActivityRecords SET SIZE(noOfControls) OF VuControlActivityRecord

}

noOfControls is the number of controls listed in vuControlActivityRecords.

vuControlActivityRecords is the set of control activity records.

2.125.   VuControlActivityRecord

Information, stored in a vehicle unit, related to a control performed using this VU (requirement 102).

VuControlActivityRecord ::= SEQUENCE {

controlType ControlType,

controlTime TimeReal,

controlCardNumber FullCardNumber,

downloadPeriodBeginTime TimeReal,

downloadPeriodEndTime TimeReal

}

controlType is the type of the control.

controlTime is the date and time of the control.

ControlCardNumber identifies the control card used for the control.

downloadPeriodBeginTime is the begin time of the downloaded period, in case of downloading.

downloadPeriodEndTime is the end time of the downloaded period, in case of downloading.

2.126.   VuDataBlockCounter

Counter, stored in a card, identifying sequentially the insertion withdrawal cycles of the card in vehicle units.

VuDataBlockCounter ::= BCDString(SIZE(2))

Value assignment: Consecutive Number with max, value 9 999 , starting again with 0.

2.127.   VuDetailedSpeedBlock

Information, stored in a vehicle unit, related to the vehicle's detailed speed for a minute during which the vehicle has been moving (requirement 093).

VuDetailedSpeedBlock ::= SEQUENCE {

speedBlockBeginDate TimeReal,

speedsPerSecond SEQUENCE SIZE(60) OF Speed

}

speedBlockBeginDate is the date and time of the first speed value within the block.

speedsPerSecond is the chronological sequence of measured speeds every seconds for the minute starting at speedBlockBeginDate (included).

2.128.   VuDetailedSpeedData

Information, stored in a vehicle unit, related to the detailed speed of the vehicle.

VuDetailedSpeedData ::= SEQUENCE

noOfSpeedBlocks INTEGER(0.216-1),

vuDetailedSpeedBlocks SET SIZE(noOfSpeedBlocks) OF VuDetailedSpeedBlock

}

noOfSpeedBlocks is the number of speed blocks in the vuDetailedSpeedBlocks set.

vuDetailedSpeedBlocks is the set of detailed speed blocks.

2.129.   VuDownloadablePeriod

Oldest and latest dates for which a vehicle unit holds data related to drivers activities (requirements 081, 084 or 087).

VuDownloadablePeriod ::= SEQUENCE {

minDownloadableTime TimeReal

maxDownloadableTime TimeReal

}

minDownloadableTime is the oldest card insertion or activity change or place entry date and time stored in the VU.

maxDownloadableTime is the latest card withdrawal or activity change or place entry date and time stored in the VU.

2.130.   VuDownloadActivityData

Information, stored in a vehicle unit, related to its last download (requirement 105).

VuDownloadActivityData ::= SEQUENCE {

downloadingTime TimeReal,

fullCardNumber FullCardNumber,

companyOrWorkshopName Name

}

downloadingTime is the date and time of downloading.

fullCardNumber identifies the card used to authorise the download.

companyOrWorkshopName is the company or workshop name.

2.131.   VuEventData

Information, stored in a vehicle unit, related to events (requirement 094 except over speeding event).

VuEventData ::= SEQUENCE {

noOfVuEvents INTEGER(0..255),

vuEventRecords SET SIZE(noOfVuEvents) OF VuEventRecord

}

noOfVuEvents is the number of events listed in the vuEventRecords set.

vuEventRecords is a set of events records.

2.132.   VuEventRecord

Information, stored in a vehicle unit, related to an event (requirement 094 except over speeding event).

VuEventRecord ::= SEQUENCE {

eventType EventFaultType,

eventRecordPurpose EventFaultRecordPurpose,

eventBeginTime TimeReal,

eventEndTime TimeReal,

cardNumberDriverSlotBegin FullCardNumber,

cardNumberCodriverSlotBegin FullCardNumber,

cardNumberDriverSlotEnd FullCardNumber,

cardNumberCodriverSlotEnd FullCardNumber,

similarEventsNumber SimilarEventsNumber

}

eventType is the type of the event.

eventRecordPurpose is the purpose for which this event has been recorded.

eventBeginTime is the date and time of beginning of event.

eventEndTime is the date and time of end of event.

cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.

cardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the event.

cardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the event.

cardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the event.

similarEventsNumber is the number of similar events that day.

This sequence can be used for all events other than over speeding events.

2.133.   VuFaultData

Information, stored in a vehicle unit, related to faults (requirement 096).

VuFaultData ::= SEQUENCE {

noOfVuFaults INTEGER(0..255),

vuFaultRecords SET SIZE(noOfVuFaults) OF VuFaultRecord

}

noOfVuFaults is the number of faults listed in the vuFaultRecords set.

vuFaultRecords is a set of faults records.

2.134.   VuFaultRecord

Information, stored in a vehicle unit, related to a fault (requirement 096).

VuFaultRecord ::= SEQUENCE {

faultType EventFaultType,

faultRecordPurpose EventFaultRecordPurpose,

faultBeginTime TimeReal,

faultEndTime TimeReal,

cardNumberDriverSlotBegin FullCardNumber,

cardNumberCodriverSlotBegin FullCardNumber,

cardNumberDriverSlotEnd FullCardNumber,

cardNumberCodriverSlotEnd FullCardNumber

}

faultType is the type of recording equipment fault.

faultRecordPurpose is the purpose for which this fault has been recorded.

faultBeginTime is the date and time of beginning of fault.

faultEndTime is the date and time of end of fault.

cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the fault.

cardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the fault.

cardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the fault.

cardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the fault.

2.135.   VuIdentification

Information, stored in a vehicle unit, related to the identification of the vehicle unit (requirement 075).

VuIdentification ::= SEQUENCE {

vuManufacturerName VuManufacturerName,

vuManufacturerAddress VuManufacturerAddress,

vuPartNumber VuPartNumber,

vuSerialNumber VuSerialNumber,

vuSoftwareIdentification VuSoftwareIdentification,

vuManufacturingDate VuManufacturingDate,

vuApprovalNumber VuApprovalNumber

}

vuManufacturerName is the name of the manufacturer of the vehicle unit.

vuManufacturerAddress is the address of the manufacturer of the vehicle unit.

vuPartNumber is the part number of the vehicle unit.

vuSerialNumber is the serial number of the vehicle unit.

vuSoftwareIdentification identifies the software implemented in the vehicle unit.

vuManufacturingDate is the manufacturing date of the vehicle unit.

vuApprovalNumber is the type approval number of the vehicle unit.

2.136.   VuManufacturerAddress

Address of the manufacturer of the vehicle unit.

VuManufacturerAddress ::= Address

Value assignment: Unspecified.

2.137.   VuManufacturerName

Name of the manufacturer of the vehicle unit.

VuManufacturerName ::= Name

Value assignment: Unspecified.

2.138.   VuManufacturingDate

Date of manufacture of the vehicle unit.

VuManufacturingDate ::= TimeReal

Value assignment: Unspecified.

2.139.   VuOverSpeedingControlData

Information, stored in a vehicle unit, related to over speeding events since the last over speeding control (requirement 095).

VuOverSpeedingControlData ::= SEQUENCE {

lastOverspeedControlTime TimeReal,

firstOverspeedSince TimeReal,

numberOfOverspeedSince OverspeedNumber

}

lastOverspeedControlTime is the date and time of the last over speeding control.

firstOverspeedSince is the date and time of the first over speeding following this over speeding control.

numberOfOverspeedSince is the number of over speeding events since the last over speeding control.

2.140.   VuOverSpeedingEventData

Information, stored in a vehicle unit, related to over speeding events (requirement 094).

VuOverSpeedingEventData ::= SEQUENCE {

noOfVuOverSpeedingEvents INTEGER(0..255),

vuOverSpeedingEventRecords SET SIZE(noOfVuOverSpeedingEvents) OF VuOverSpeedingEventRecord

}

noOfVuOverSpeedingEvents is the number of events listed in the vuOverSpeedingEventRecords set.

vuOverSpeedingEventRecords is a set of over speeding events records.

2.141.   VuOverSpeedingEventRecord

Information, stored in a vehicle unit, related to over speeding events (requirement 094).

VuOverSpeedingEventRecord ::= SEQUENCE {

eventType EventFaultType,

eventRecordPurpose EventFaultRecordPurpose,

eventBeginTime TimeReal,

eventEndTime TimeReal,

maxSpeedValue SpeedMax,

averageSpeedValue SpeedAverage,

cardNumberDriverSlotBegin FullCardNumber,

similarEventsNumber SimilarEventsNumber

}

eventType is the type of the event.

eventRecordPurpose is the purpose for which this event has been recorded.

eventBeginTime is the date and time of beginning of event.

eventEndTime is the date and time of end of event.

maxSpeedValue is the maximum speed measured during the event.

averageSpeedValue is the arithmetic average speed measured during the event.

cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.

similarEventsNumber is the number of similar events that day.

2.142.   VuPartNumber

Part number of the vehicle unit.

VuPartNumber ::= IA5String(SIZE(16))

Value assignment: VU manufacturer specific.

2.143.   VuPlaceDailyWorkPeriodData

Information, stored in a vehicle unit, related to places where drivers begin or end a daily work periods (requirement 087).

VuPlaceDailyWorkPeriodData ::= SEQUENCE {

noOfPlaceRecords INTEGER(0..255),

vuPlaceDailyWorkPeriodRecords SET SIZE(noOfPlaceRecords) OF VuPlaceDailyWorkPeriodRecord

}

noOfPlaceRecords is the number of records listed in the vuPlaceDailyWorkPeriodRecords set.

vuPlaceDailyWorkPeriodRecords is a set of place related records.

2.144.   VuPlaceDailyWorkPeriodRecord

Information, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (requirement 087).

VuPlaceDailyWorkPeriodRecord ::= SEQUENCE {

fullCardNumber FullCardNumber,

placeRecord PlaceRecord

}

fullCardNumber is the driver's card type, card issuing Member State and card number.

placeRecord contains the information related to the place entered.

2.145.   VuPrivateKey

The private key of a vehicle unit.

VuPrivateKey ::= RSAKeyPrivateExponent

2.146.   VuPublicKey

The public key of a vehicle unit.

VuPublicKey ::= PublicKey

2.147.   VuSerialNumber

Serial number of the vehicle unit (requirement 075).

VuSerialNumber ::= ExtendedSerialNumber

2.148.   VuSoftInstallationDate

Date of installation of the vehicle unit software version.

VuSoftInstallationDate ::= TimeReal

Value assignment: Unspecified.

2.149.   VuSoftwareIdentification

Information, stored in a vehicle unit, related to the software installed.

VuSoftwareIdentification ::= SEQUENCE {

vuSoftwareVersion VuSoftwareVersion,

vuSoftInstallationDate VuSoftInstallationDate

}

vuSoftwareVersion is the software version number of the Vehicle Unit.

vuSoftInstallationDate is the software version installation date.

2.150.   VuSoftwareVersion

Software version number of the vehicle unit.

VuSoftwareVersion ::= IA5String(SIZE(4))

Value assignment: Unspecified.

2.151.   VuSpecificConditionData

Information, stored in a vehicle unit, related to specific conditions.

VuSpecificConditionData ::= SEQUENCE {

noOfSpecificConditionRecords INTEGER(0..216-1)

specificConditionRecords SET SIZE (noOfSpecificConditionRecords) OF SpecificConditionRecord

}

noOfSpecificConditionRecords is the number of records listed in the specificConditionRecords set.

specificConditionRecords is a set of specific conditions related records.

2.152.   VuTimeAdjustmentData

Information, stored in a vehicle unit, related to time adjustments performed outside the frame of a regular calibration (requirement 101).

VuTimeAdjustmentData ::= SEQUENCE {

noOfVuTimeAdjRecords INTEGER(0..6),

vuTimeAdjustmentRecords SET SIZE(noOfVuTimeAdjRecords) OF VuTimeAdjustmentRecord

}

noOfVuTimeAdjRecords is the number of records in vuTimeAdjustmentRecords.

vuTimeAdjustmentRecords is a set of time adjustment records.

2.153.   VuTimeAdjustmentRecord

Information, stored in a vehicle unit, related to a time adjustment performed outside the frame of a regular calibration (requirement 101).

VuTimeAdjustmentRecord ::= SEQUENCE {

▼C2

▼M8

oldTimeValue TimeReal,

newTimeValue TimeReal,

workshopName Name,

workshopAddress Address,

workshopCardNumber FullCardNumber

}

oldTimeValue, newTimeValue are the old and new values of date and time.

workshopName, workshopAddress are the workshop name and address.

workshopCardNumber identifies the workshop card used to perform the time adjustment.

2.154.   W-VehicleCharacteristicConstant

Characteristic coefficient of the vehicle (definition k)).

W-VehicleCharacteristicConstant ::= INTEGER(0..216-1))

Value assignment: Impulses per kilometre in the operating range 0 to 64 255 pulses/km.

2.155.   WorkshopCardApplicationIdentification

Information, stored in a workshop card related to the identification of the application of the card (requirement 190).

WorkshopCardApplicationIdentification ::= SEQUENCE {

typeOfTachographCardId EquipmentType,

cardStructureVersion CardStructureVersion,

noOfEventsPerType NoOfEventsPerType,

noOfFaultsPerType NoOfFaultsPerType,

activityStructureLength CardActivityLengthRange,

noOfCardVehicleRecords NoOfCardVehicleRecords,

noOfCardPlaceRecords NoOfCardPlaceRecords,

noOfCalibrationRecords NoOfCalibrationRecords

}

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the the version of the structure that is implemented in the card.

noOfEventsPerType is the number of events per type of event the card can record.

noOfFaultsPerType is the number of faults per type of fault the card can record.

activityStructureLength indicates the number of bytes available for storing activity records.

noOfCardVehicleRecords is the number of vehicle records the card can contain.

noOfCardPlaceRecords is the number of places the card can record.

noOfCalibrationRecords is the number of calibration records the card can store.

2.156.   WorkshopCardCalibrationData

Information, stored in a workshop card, related to workshop activity performed with the card (requirements 227 and 229).

WorkshopCardCalibrationData ::= SEQUENCE {

calibrationTotalNumber INTEGER(0..216-1),

calibrationPointerNewestRecord INTEGER(0..NoOfCalibrationRecords-1),

calibrationRecords SET SIZE(NoOfCalibrationRecords) OF WorkshopCardCalibrationRecord

}

calibrationTotalNumber is the total number of calibrations performed with the card.

calibrationPointerNewestRecord is the index of the last updated calibration record.

Value assignment: Number corresponding to the numerator of the calibration record, beginning with ‘0’ for the first occurrence of the calibration records in the structure.

calibrationRecords is the set of records containing calibration and/or time adjustment information.

2.157.   WorkshopCardCalibrationRecord

Information, stored in a workshop card, related to a calibration performed with the card (requirement 227).

WorkshopCardCalibrationRecord ::= SEQUENCE {

calibrationPurpose CalibrationPurpose,

vehicleIdentificationNumber VehicleIdentificationNumber,

vehicleRegistration VehicleRegistrationIdentification,

wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,

kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,

lTyreCircumference L-TyreCircumference,

tyreSize TyreSize,

authorisedSpeed SpeedAuthorised,

oldOdometerValue OdometerShort,

newOdometerValue OdometerShort,

oldTimeValue TimeReal,

newTimeValue TimeReal,

nextCalibrationDate TimeReal,

vuPartNumber VuPartNumber,

vuSerialNumber VuSerialNumber,

sensorSerialNumber SensorSerialNumber

}

calibrationPurpose is the purpose of the calibration.

vehicleIdentificationNumber is the VIN.

vehicleRegistration contains the VRN and registering Member State.

wVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.

kConstantOfRecordingEquipment is the constant of the recording equipment.

lTyreCircumference is the effective circumference of the wheel tyres.

tyreSize is the designation of the dimensions of the tyres mounted on the vehicle.

authorisedSpeed is the maximum authorised speed of the vehicle.

oldOdometerValue, newOdometerValue are the old and new values of the odometer.

oldTimeValue, newTimeValue are the old and new values of date and time.

nextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.

vuPartNumber, vuSerialNumber and sensorSerialNumber are the data elements for recording equipment identification.

2.158.   WorkshopCardHolderIdentification

Information, stored in a workshop card, related to the identification of the cardholder (requirement 216).

WorkshopCardHolderIdentification ::= SEQUENCE {

workshopName Name,

workshopAddress Address,

cardHolderName HolderName,

cardHolderPreferredLanguage Language

}

workshopName is name of the workshop of the card holder.

workshopAddress is the address of the workshop of the card holder.

cardHolderName is the name and first name(s) of the holder (e.g. the name of the mechanic).

cardHolderPreferredLanguage is the preferred language of the card holder.

2.159.   WorkshopCardPIN

Personal identification number of the Workshop Card (requirement 213).

WorkshopCardPIN ::= IA5String(SIZE(8))

Value assignment: The PIN known to the cardholder, right padded with ‘FF’ bytes up to 8 bytes.

3.   VALUE AND SIZE RANGE DEFINITIONS

Definition of variable values used for definitions in paragraph 2.

TimeRealRange ::= 232-1

3.1.   Definitions for the Driver Card:



Name of the variable value

Minimum

Maximum

CardActivityLengthRange

5 544 bytes

(28 days 93 activity changes per day)

13 776 bytes

(28 days 240 activity changes per day)

NoOfCardPlaceRecords

84

112

NoOfCardVehicleRecords

84

200

NoOfEventsPerType

6

12

NoOfFaultsPerType

12

24

3.2.   Definitions for the Workshop Card:



Name of the variable value

Minimum

Maximum

CardActivityLengthRange

198 bytes

(1 day 93 activity changes)

492 bytes

(1 day 240 activity changes)

NoOfCardPlaceRecords

6

8

NoOfCardVehicleRecords

4

8

NoOfEventsPerType

3

3

NoOfFaultsPerType

6

6

NoOfCalibrationRecords

88

255

3.3.   Definitions for the Control Card:



Name of the variable value

Minimum

Maximum

NoOfControlActivityRecords

230

520

3.4.   Definitions for the Company Card:



Name of the variable value

Minimum

Maximum

NoOfCompanyActivityRecords

230

520

4.   CHARACTER SETS

IA5Strings use the ASCII characters as defined by ISO/IEC 8824-1. For readability and for easy referencing the value assignment is given below. The ISO/IEC 8824-1 supersedes this informative note in case of discrepancy.

! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ?

@ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _

' a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~

▼M15



Other character strings (Address, Name, VehicleRegistrationNumber) use, in addition, characters from the decimal character code range 161 – 255 of the following 8-bit, standard character sets, specified by the Code Page number:

Standard Character Set

Code Page

(Decimal)

ISO/IEC 8859-1 Latin-1 Western European

1

ISO/IEC 8859-2 Latin-2 Central European

2

ISO/IEC 8859-3 Latin-3 South European

3

ISO/IEC 8859-5 Latin / Cyrillic

5

ISO/IEC 8859-7 Latin / Greek

7

ISO/IEC 8859-9 Latin-5 Turkish

9

ISO/IEC 8859-13 Latin-7 Baltic Rim

13

ISO/IEC 8859-15 Latin-9

15

ISO/IEC 8859-16 Latin-10 South Eastern European

16

KOI8-R Latin / Cyrillic

80

KOI8-U Latin / Cyrillic

85

▼M8

5.   ENCODING

When encoded with ASN.1 encoding rules, all data types defined shall be encoded according to ISO/IEC 8825-2, aligned variant.




Appendix 2

TACHOGRAPH CARDS SPECIFICATION

Contents

1.

Introduction …

1.1.

Abbreviations …

1.2.

References …

2.

Electrical and physical characteristics …

2.1.

Supply voltage and current consumption …

2.2.

Programming voltage Vpp

2.3.

Clock generation and frequency …

2.4.

I/O contact …

2.5.

States of the card …

3.

Hardware and communication …

3.1.

Introduction …

3.2.

Transmission protocol …

3.2.1.

Protocols …

3.2.2.

ATR …

3.2.3.

PTS …

3.3.

Access conditions (AC) …

3.4.

Data encryption …

3.5.

Commands and error codes overview …

3.6.

Commands description …

3.6.1.

Select file …

3.6.1.1.

Selection by name (AID) …

3.6.1.2.

Selection of an elementary file using its file identifier …

3.6.2.

Read Binary …

3.6.2.1.

Command without secure messaging …

3.6.2.2.

Command with secure messaging …

3.6.3.

Update Binary …

3.6.3.1.

Command without secure messaging …

3.6.3.2.

Command with secure messaging …

3.6.4.

Get challenge …

3.6.5.

Verify …

3.6.6.

Get response …

3.6.7.

PSO: verify certificate …

3.6.8.

Internal authenticate …

3.6.9.

External authenticate …

3.6.10.

Manage security environment …

3.6.11.

PSO: hash …

3.6.12.

Perform hash of file …

3.6.13.

PSO: compute digital signature …

3.6.14.

PSO: verify digital signature …

4.

Tachograph cards structure …

4.1.

Driver card structure …

4.2.

Workshop card structure …

4.3.

Control card structure …

4.4.

Company card structure …

1.   INTRODUCTION

1.1.   Abbreviations

For the purpose of this appendix, the following abbreviations apply:

AC

access conditions

AID

application identifier

ALW

always

APDU

application protocol data unit (structure of a command)

ATR

answer to reset

AUT

authenticated

C6, C7

contacts No 6 and 7 of the card as described in ISO/IEC 7816-2

cc

clock cycles

CHV

card holder verification information

CLA

class byte of an APDU command

DF

dedicated file. A DF can contain other files (EF or DF)

EF

elementary file

ENC

encrypted: access is possible only by encoding data

etu

elementary time unit

IC

integrated circuit

ICC

integrated circuit card

ID

identifier

IFD

interface device

IFS

information field size

IFSC

information field size for the card

IFSD

information field size device (for the terminal)

INS

instruction byte of an APDU command

Lc

length of the input data for a APDU command

Le

length of the expected data (output data for a command)

MF

master file (root DF)

P1-P2

parameter bytes

NAD

node address used in T=1 protocol

NEV

never

PIN

personal identification number

PRO SM

protected with secure messaging

PTS

protocol transmission selection

RFU

reserved for future use

RST

reset (of the card)

SM

secure messaging

SW1-SW2

status bytes

TS

initial ATR character

VPP

programming voltage

XXh

value XX in hexadecimal notation

||

concatenation symbol 03||04=0304.

1.2.   References

The following references are used in this Appendix:



EN 726-3

Identification cards systems — Telecommunications integrated circuit(s) cards and terminals — Part 3: Application independent card requirements. December 1994.

ISO/IEC 7816-2

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 2: Dimensions and location of the contacts. First edition: 1999.

ISO/IEC 7816-3

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 3: Electronic signals and transmission protocol. Edition 2: 1997.

ISO/IEC 7816-4

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 4: Interindustry commands for interexchange. First edition: 1995 + Amendment 1: 1997.

ISO/IEC 7816-6

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 6: Interindustry data elements. First Edition: 1996 + Cor 1: 1998.

ISO/IEC 7816-8

Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 8: Security related interindustry commands. First Edition: 1999.

ISO/IEC 9797

Information technology — Security techniques — Data integrity mechanism using a cryptographic check function employing a block cipher algorithm. Edition 2: 1994.

2.   ELECTRICAL AND PHYSICAL CHARACTERISTICS

TCS_200All electronic signals shall be in accordance with ISO/IEC 7816-3 unless specified otherwise.

TCS_201The location and dimensions of the card contacts shall comply with the ISO/IEC 7816-2.

2.1.   Supply voltage and current consumption

TCS_202The card shall work according to specifications within the consumption limits specified in ISO/IEC 7816-3.

▼C2