xmlns:atom="http://www.w3.org/2005/Atom" xmlns:atom="http://www.w3.org/2005/Atom"

Please note that the date you requested in the address for this web page is not an actual date upon which a change occurred to this item of legislation. You are being shown the legislation from , which is the first date before then upon which a change was made.

ANNEX I CU.K. Requirements for construction, testing, installation, and inspection

3.CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENTU.K.

3.12 Recording and storing in the data memory U.K.

For the purpose of this paragraph,

(91)Data 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. In addition, data stored in the external remote communication facility, as defined in Appendix 14, shall not be affected by power-supply cut-off of less than 28 days.U.K.
(92)The recording equipment shall be able to record and store implicitly or explicitly in its data memory the following:U.K.
3.12.1 Equipment identification data U.K.
3.12.1.1 Vehicle unit identification data U.K.
(93)The recording equipment shall be able to store in its data memory the following vehicle unit identification data:U.K.
(94)Vehicle 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 and the ability to use first generation tachograph cards.U.K.
3.12.1.2 Motion sensor identification data U.K.
(95)The motion sensor shall be able to store in its memory the following identification data:U.K.
(96)Motion sensor identification data are recorded and stored once and for all in the motion sensor, by the motion sensor manufacturer.U.K.
(97)The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent pairing of motion sensors (if several pairings happen within one calendar day, only the first and the last one of the day shall be stored):U.K.

The following data shall be recorded for each of these pairings:

3.12.1.3 Global Navigation Satellite Systems identification data U.K.
(98)The external GNSS facility shall be able to store in its memory the following identification data:U.K.
(99)The identification data are recorded and stored once and for all in the external GNSS facility, by the external GNSS facility manufacturer.U.K.
(100)The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent couplings of external GNSS facilities (if several couplings happen within one calendar day, only the first and the last one of the day shall be stored).U.K.

The following data shall be recorded for each of these couplings:

3.12.2 Keys and certificates U.K.
(101)The recording equipment shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A and part B.U.K.
3.12.3 Driver or workshop card insertion and withdrawal data U.K.
(102)For 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:U.K.
(103)The data memory shall be able to hold these data for at least 365 days.U.K.
(104)When storage capacity is exhausted, new data shall replace oldest data.U.K.
3.12.4 Driver activity data U.K.
(105)The 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:U.K.

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)

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

(106)The data memory shall be able to hold driver activity data for at least 365 days.U.K.
(107)When storage capacity is exhausted, new data shall replace oldest data.U.K.
[F13.12.5 Places and positions where daily work periods begin, end and/or where 3 hours accumulated driving time is reached U.K.
(108) The recording equipment shall record and store in its data memory: U.K.
(109)When the position of the vehicle is not available from the GNSS receiver at these times, the recording equipment shall use the latest available position, and the related date and time.U.K.
(110)Together with each place or position, the recording equipment shall record and store in its data memory:U.K.
[F1(111) The data memory shall be able to hold places and positions where daily work periods begin, end and/or where 3 hours accumulated driving time is reached for at least 365 days.] U.K.
(112)When storage capacity is exhausted, new data shall replace oldest data.U.K.
3.12.6 Odometer data U.K.
(113)The recording equipment shall record in its data memory the vehicle odometer value and the corresponding date at midnight every calendar day.U.K.
(114)The data memory shall be able to store midnight odometer values for at least 365 calendar days.U.K.
(115)When storage capacity is exhausted, new data shall replace oldest data.U.K.
3.12.7 Detailed speed data U.K.
[F1(116) The 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.] U.K.
3.12.8 Events data U.K.

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

(117)The recording equipment shall record and store in its data memory the following data for each event detected according to the following storage rules:U.K.
EventStorage rulesData to be recorded per event
Insertion of a non-valid card
  • the 10 most recent events.

  • date and time of event,

  • card(s) type, number, issuing Member State and generation of the card creating the event.

  • number of similar events that day

Card conflict
  • the 10 most recent events.

  • date and time of beginning of event,

  • date and time of end of event,

  • card(s) type, number, issuing Member State and generation 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 5 longest events over the last 365 days.

  • date and time of beginning of event,

  • date and time of end of event,

  • card(s) type, number, issuing Member State and generation 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, issuing Member State and generation,

  • 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, issuing Member State and generation,

  • last session data as read from the card:

    • date and time of card insertion,

    • VRN, Member State of registration and VU generation.

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 5 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 type, number, issuing Member State and generation of the driver card (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 5 longest events over the last 365 days.

  • date and time of beginning of event,

  • date and time of end of event,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.

Communication error with the remote communication facility
  • 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,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.

Absence of position information from GNSS receiver
  • 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,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.

[F2Communication error with the external GNSS facility
  • 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,

  • card(s) type, number, issuing Member State and generation 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 5 longest events over the last 365 days.

  • date and time of beginning of event,

  • date and time of end of event,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.

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,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.

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),

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • type of event.

[F1Time conflict
  • the most serious event for each of the 10 last days of occurrence (i.e. the ones with the greatest difference between recording equipment date and time, and GNSS date and time).

  • the 5 most serious events over the last 365 days.

  • recording equipment date and time

  • GNSS date and time,

  • card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

  • number of similar events that day.]

(1)

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

3.12.9 Faults data U.K.

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

(118)The 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:U.K.
FaultStorage rulesData 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, issuing Member State and generation.

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,

  • card(s) type, number and issuing Member State and generation of any card inserted at beginning and/or end of the fault.

3.12.10 Calibration data U.K.
(119)The recording equipment shall record and store in its data memory data relevant to:U.K.
(120)The following data shall be recorded for each of these calibrations:U.K.
(121)In addition, the recording equipment shall record and store in its data memory its ability to use first generation tachograph cards (still activated or not).U.K.
(122)The motion sensor shall record and store in its memory the following motion sensor installation data:U.K.
(123)The external GNSS facility shall record and store in its memory the following external GNSS facility installation data:U.K.
3.12.11 Time adjustment data U.K.
(124)The recording equipment shall record and store in its data memory data relevant to time adjustments performed in calibration mode outside the frame of a regular calibration (def. f)):U.K.
(125)The following data shall be recorded for each of these time adjustments:U.K.
3.12.12 Control activity data U.K.
(126)The recording equipment shall record and store in its data memory the following data relevant to the 20 most recent control activities:U.K.
(127)In case of downloading, the dates of the oldest and of the most recent days downloaded shall also be recorded.U.K.
3.12.13 Company locks data U.K.
(128)The recording equipment shall record and store in its data memory the following data relevant to the 255 most recent company locks:U.K.

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

3.12.14 Download activity data U.K.
(129)The 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:U.K.
3.12.15 Specific conditions data U.K.
(130)The recording equipment shall record in its data memory the following data relevant to specific conditions:U.K.
(131)The data memory shall be able to hold specific conditions data for at least 365 days (with the assumption that on average, 1 condition is opened and closed per day). When storage capacity is exhausted, new data shall replace oldest data.U.K.
3.12.16 Tachograph card data U.K.
(132)The recording equipment shall be able to store the following data related to the different tachograph cards in which had been used in the VU:U.K.
(133)The recording equipment shall be able to store at least 88 such records.U.K.