Commission Implementing Regulation (EU) 2016/799 of 18 March 2016 implementing Regulation (EU) No 165/2014 of the European Parliament and of the Council laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance) (c. 799)

ANNEX I C Requirements for construction, testing, installation, and inspection

4. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS

4.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,

• positions (latitudes and longitudes) are recorded in degrees and minutes with a resolution of 1/10 of minute.

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

If not otherwise specified, data storage on tachograph cards shall be organized in such a way, that new data replaces stored oldest data in case the foreseen memory size for the particular records is exhausted.

(245) This paragraph specifies minimum storage capacity for the various application data files. Tachograph cards shall be able to indicate to the recording equipment the actual storage capacity of these data files.

(246) Any additional data that may be stored on tachograph cards, related to other applications possibly borne by the card, shall be stored in accordance with Directive 95/46/EC and with Directive 2002/58/EC and in compliance with Article 7 of Regulation (EU) No. 165/2014.

(247) Each Master File (MF) of any tachograph card shall contain up to five Elementary Files (EF) for card management, application and chip identifications, and two Dedicated Files (DF):

• DF Tachograph, which contains the application accessible to first generation vehicle units, which is also present in first generation tachograph cards,

• DF Tachograph_G2, which contains the application only accessible to second generation vehicle units, which is only present in second generation tachograph cards.

The full details of the tachograph cards structure are specified in Appendix 2.

4.5.1 Elementary files for identification and card management

4.5.2 IC card identification

(248) Tachograph cards shall be able to store the following smart card identification data:

• clock stop,

• card serial number (including manufacturing references),

• card type approval number,

• card personaliser identification (ID),

• embedder ID,

• IC identifier.

4.5.2.1 Chip identification

(249) Tachograph cards shall be able to store the following Integrated Circuit (IC) identification data:

• IC serial number,

• IC manufacturing references.

4.5.2.2 DIR (only present in second generation tachograph cards)

(250) Tachograph cards shall be able to store the application identification data objects specified in Appendix 2.

4.5.2.3 ATR information (conditional, only present in second generation tachograph cards)

(251) Tachograph cards shall be able to store the following extended length information data object:

• in the case the tachograph card supports extended length fields, the extended length information data object specified in Appendix 2.

4.5.2.4 Extended length information (conditional, only present in second generation tachograph cards)

(252) Tachograph cards shall be able to store the following extended length information data objects:

• in the case the tachograph card supports extended length fields, the extended length information data objects specified in Appendix 2.

4.5.3 Driver card

4.5.3.1 Tachograph application (accessible to first and second generation vehicle units)

4.5.3.1.1 Application identification

(253) The driver card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.3.1.2 Key and certificates

(254) The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

4.5.3.1.3 Card identification

(255) The 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.

4.5.3.1.4 Card holder identification

(256) The 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.

4.5.3.1.5 Card download

(257) The driver card shall be able to store the following data related to card download:

• date and time of last card download (for other purposes than control).

(258) The driver card shall be able to hold one such record.

4.5.3.1.6 Driving licence information

(259) The 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).

4.5.3.1.7 Events data

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

(260) The 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.

(261) The 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.

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

4.5.3.1.8 Faults data

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

(263) The 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.

(264) The 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.

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

4.5.3.1.9 Driver activity data

(266) The 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.

(267) The 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).

(268) The data listed under requirements 261, 264 and 266 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.

4.5.3.1.10 Vehicles used data

(269) The 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 00h00 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 23h59 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.

(270) The driver card shall be able to store at least 84 such records.

4.5.3.1.11 Places where daily work periods start and/or end

(271) The 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.

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

4.5.3.1.12 Card session data

(273) The 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.

4.5.3.1.13 Control activity data

(274) The 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: card downloading will only be recorded if performed through a recording equipment.

(275) The driver card shall be able to hold one such record.

4.5.3.1.14 Specific conditions data

(276) The 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.

(277) The driver card shall be able to store at least 56 such records.

4.5.3.2 Tachograph generation 2 application (not accessible to first generation vehicle unit)

4.5.3.2.1 Application identification

(278) The driver card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.3.2.2 Keys and certificates

(279) The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

4.5.3.2.3 Card identification

(280) The 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.

4.5.3.2.4 Card holder identification

(281) The 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.

4.5.3.2.5 Card download

(282) The driver card shall be able to store the following data related to card download:

• date and time of last card download (for other purposes than control).

(283) The driver card shall be able to hold one such record.

4.5.3.2.6 Driving licence information

(284) The 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).

4.5.3.2.7 Events data

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

(285) The 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,

• Communication error with the remote communication facility,

• Absence of position information from GNSS receiver event,

• Communication error with the external GNSS facility

• Motion data error,

• Vehicle motion conflict,

• Security breach attempts,

• Time conflict.

(286) The 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.

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

4.5.3.2.8 Faults data

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

(288) The 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.

(289) The 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.

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

4.5.3.2.9 Driver activity data

(291) The 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,

(292) The 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).

(293) The data listed under requirements 286, 289 and 291 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.

4.5.3.2.10 Vehicles used data

(294) The 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 00h00 if the period of use is on-going at that time),

• vehicle odometer value at that first use time,

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

• vehicle odometer value at that last use time,

• VRN and registering Member State of the vehicle,

• VIN of the vehicle.

(295) The driver card shall be able to store at least 84 such records.

4.5.3.2.11 Places and positions where daily work periods start and/or end

(296) The 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,

• the vehicle position,

• the GNSS accuracy, date and time when the position was determined.

(297) The driver card memory shall be able to hold at least 84 pairs of such records.

4.5.3.2.12 Card session data

(298) The 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.

4.5.3.2.13 Control activity data

(299) The 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.

(300) The driver card shall be able to hold one such record.

4.5.3.2.14 Specific conditions data

(301) The 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.

(302) The driver card shall be able to store at least 56 such records.

4.5.3.2.15 Vehicle units used data

(303) The driver card shall be able to store the following data related to the different vehicle units in which the card was used:

• the date and time of the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period),

• the manufacturer of the vehicle unit,

• the vehicle unit type,

• the vehicle unit software version number.

(304) The driver card shall be able to store at least 84 such records.

4.5.3.2.16 Three hours' continuous driving places data

(305) The driver card shall be able to store the following data related to the position of the vehicle where the continuous driving time of the driver reaches a multiple of three hours:

• the date and time when the continuous driving time of the card holder reaches a multiple of three hours,

• the position of the vehicle.

• the GNSS accuracy, date and time when the position was determined.

(306) The driver card shall be able to store at least 252 such records.

4.5.4 Workshop card

4.5.4.1 Tachograph application (accessible to first and second generation vehicle units)

4.5.4.1.1 Application identification

(307) The workshop card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.4.1.2 Keys and certificates

(308) The workshop card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

(309) The workshop card shall be able to store a Personal Identification Number (PIN code).

4.5.4.1.3 Card identification

(310) The 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.

4.5.4.1.4 Card holder identification

(311) The 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.

4.5.4.1.5 Card download

(312) The workshop card shall be able to store a card download data record in the same manner as a driver card.

4.5.4.1.6 Calibration and time adjustment data

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

(314) Each calibration record shall be able to hold the following data:

• 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).

(315) The workshop card shall be able to store at least 88 such records.

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

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

4.5.4.1.7 Events and faults data

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

(319) The 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).

4.5.4.1.8 Driver activity data

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

(321) The workshop card shall be able to hold driver activity data for at least 1 day of average driver activity.

4.5.4.1.9 Vehicles used data

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

(323) The workshop card shall be able to store at least 4 such records.

4.5.4.1.10 Daily work periods start and/or end data

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

(325) The workshop card shall be able to hold at least 3 pairs of such records.

4.5.4.1.11 Card session data

(326) The workshop card shall be able to store a card session data record in the same manner as a driver card.

4.5.4.1.12 Control activity data

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

4.5.4.1.13 Specific conditions data

(328) The workshop card shall be able to store data relevant to specific conditions in the same manner as the driver card.

(329) The workshop card shall be able to store at least 2 such records.

4.5.4.2 Tachograph generation 2 application (not accessible to first generation vehicle unit)

4.5.4.2.1 Application identification

(330) The workshop card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.4.2.2 Keys and certificates

(331) The workshop card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

(332) The workshop card shall be able to store a Personal Identification Number (PIN code).

4.5.4.2.3 Card identification

(333) The 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.

4.5.4.2.4 Card holder identification

(334) The 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.

4.5.4.2.5 Card download

(335) The workshop card shall be able to store a card download data record in the same manner as a driver card.

4.5.4.2.6 Calibration and time adjustment data

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

(337) Each calibration record shall be able to hold the following data:

• 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, remote communication facility serial number and external GNSS facility serial number, if applicable),

• seal type and identifier of all seals in place,

• ability of the VU to use first generation tachograph cards (enabled or not).

(338) The workshop card shall be able to store at least 88 such records.

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

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

4.5.4.2.7 Events and faults data

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

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

4.5.4.2.8 Driver activity data

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

(344) The workshop card shall be able to hold driver activity data for at least 1 day of average driver activity.

4.5.4.2.9 Vehicles used data

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

(346) The workshop card shall be able to store at least 4 such records.

4.5.4.2.10 Daily work periods start and/or end data

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

(348) The workshop card shall be able to hold at least 3 pairs of such records.

4.5.4.2.11 Card session data

(349) The workshop card shall be able to store a card session data record in the same manner as a driver card.

4.5.4.2.12 Control activity data

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

4.5.4.2.13 Vehicle units used data

(351) The workshop card shall be able to store the following data related to the different vehicle units in which the card was used:

• the date and time of the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period),

• the manufacturer of the vehicle unit,

• the vehicle unit type,

• the vehicle unit software version number.

(352) The workshop card shall be able to store at least 4 such records.

4.5.4.2.14 Three hours' continuous driving places data

(353) The workshop card shall be able to store the following data related to the position of the vehicle where the continuous driving time of the driver reaches a multiple of three hours:

• the date and time when the continuous driving time of the card holder reaches a multiple of three hours,

• the position of the vehicle,

• the GNSS accuracy, date and time when the position was determined.

(354) The workshop card shall be able to store at least 18 such records.

4.5.4.2.15 Specific conditions data

(355) The workshop card shall be able to store data relevant to specific conditions in the same manner as the driver card.

(356) The workshop card shall be able to store at least 2 such records.

4.5.5 Control card

4.5.5.1 Tachograph application (accessible to first and second generation vehicle units)

4.5.5.1.1 Application identification

(357) The control card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.5.1.2 Keys and certificates

(358) The control card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

4.5.5.1.3 Card identification

(359) The 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).

4.5.5.1.4 Card holder identification

(360) The 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.

4.5.5.1.5 Control activity data

(361) The 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 and/or roadside calibration checking),

• 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.

(362) The control card shall be able to hold at least 230 such records.

4.5.5.2 Tachograph G2 application (not accessible to first generation vehicle unit)

4.5.5.2.1 Application identification

(363) The control card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.5.2.2 Keys and certificates

(364) The control card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

4.5.5.2.3 Card identification

(365) The 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).

4.5.5.2.4 Card holder identification

(366) The 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.

4.5.5.2.5 Control activity data

(367) The 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 and/or roadside calibration checking)

• 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.

(368) The control card shall be able to hold at least 230 such records.

4.5.6 Company card

4.5.6.1 Tachograph application (accessible to first and second generation vehicle units)

4.5.6.1.1 Application identification

(369) The company card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.6.1.2 Keys and Certificates

(370) The company card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

4.5.6.1.3 Card identification

(371) The 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).

4.5.6.1.4 Card holder identification

(372) The company card shall be able to store the following card holder identification data:

• company name,

• company address.

4.5.6.1.5 Company activity data

(373) The 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).

(374) The company card shall be able to hold at least 230 such records.

4.5.6.2 Tachograph G2 application (not accessible to first generation vehicle unit)

4.5.6.2.1 Application identification

(375) The company card shall be able to store the following application identification data:

• tachograph application identification,

• type of tachograph card identification.

4.5.6.2.2 Keys and certificates

(376) The company card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

4.5.6.2.3 Card identification

(377) The 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).

4.5.6.2.4 Card holder identification

(378) The company card shall be able to store the following card holder identification data:

• company name,

• company address.

4.5.6.2.5 Company activity data

(379) The 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).

(380) The company card shall be able to hold at least 230 such records.