| MultiBlock_O80 R001 |
#A1 : User expects that Functionalities are available x s after switch on |
|
MultiBlock_O80 |
R001 |
[G01:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
User Need |
| MultiBlock_O80 R003 |
#A1 : User expects that The system can be switched off at any time, in any state. |
|
MultiBlock_O80 |
R003 |
[G01:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] |
|
|
|
|
User Need |
| MultiBlock_O80 R009 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R009 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R010 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R010 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R011 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R011 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R012 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R012 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R013 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R013 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R014 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R014 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R015 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R015 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R016 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R016 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O80 R017 |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
|
MultiBlock_O80 |
R017 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] |
|
|
|
|
System Requirement |
| MultiBlock_O70 R001 |
#A1 : User expects to the user can deactivate the function by a switch on inner pannel |
|
MultiBlock_O70 |
R001 |
[G01:MultiBlock_O70 R001
| Text: |
the user can deactivate the function by a switch on inner pannel |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R003 |
#A1 : User expects to switch actuation effort is below 10N |
|
MultiBlock_O70 |
R003 |
[G01:MultiBlock_O70 R003
| Text: |
switch actuation effort is below 10N |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R004 |
#A1 : User expects to activation status is displayed |
|
MultiBlock_O70 |
R004 |
[G01:MultiBlock_O70 R004
| Text: |
activation status is displayed |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R005 |
#A1 : User expects to Activation is notified by a sound within 500ms |
|
MultiBlock_O70 |
R005 |
[G01:MultiBlock_O70 R005
| Text: |
Activation is notified by a sound within 500ms |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R006 |
#A1 : User expects to a failure is notified by a warning lamp |
|
MultiBlock_O70 |
R006 |
[G01:MultiBlock_O70 R006
| Text: |
a failure is notified by a warning lamp |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R007 |
#A1 : User expects to driver is notified when activity is in progress |
|
MultiBlock_O70 |
R007 |
[G01:MultiBlock_O70 R007] |
|
|
|
|
HMI Needs |
| MultiBlock_O70 R008 |
#A1 : User expects to switch actuation effort is lower than 5N |
|
MultiBlock_O70 |
R008 |
[G01:MultiBlock_O70 R008
| Text: |
switch actuation effort is lower than 5N |
] |
|
|
|
|
HMI Needs |
| MultiBlock_O60 R001 |
Fluids are contained during storing period before dismantling. |
|
MultiBlock_O60 |
R001 |
[G05:MultiBlock_O60 R001
| Text: |
The environmental impact of the product is neutral |
] [G01:MultiBlock_C60 R001] |
|
|
|
|
Recycling |
| MultiBlock_O60 R002 |
Components are free of forbidden materials (lead, hexavalent chrome, mercury). |
|
MultiBlock_O60 |
R002 |
[G05:MultiBlock_O60 R002
| Text: |
environmental regulations are respected |
] [G01:MultiBlock_C60 R002] |
|
|
|
|
Recycling |
| MultiBlock_O60 R003 |
Components can be reused after the product is dismanteled. |
|
MultiBlock_O60 |
R003 |
[G05:MultiBlock_O60 R006] [G01:MultiBlock_C60 R003] |
|
|
|
|
Recycling |
| MultiBlock_O60 R004 |
Materials marking is applied on components for material sorting. |
|
MultiBlock_O60 |
R004 |
[G05:MultiBlock_O60 R004] [G01:MultiBlock_C60 R004] |
|
|
|
|
Recycling |
| MultiBlock_O60 R005 |
Plastic parts and metallic parts can be separated for recycling. |
|
MultiBlock_O60 |
R005 |
[G05:MultiBlock_O60 R005
| Text: |
The product has a recycling rate of xx % |
] [G01:MultiBlock_C60 R005] |
|
|
|
|
Recycling |
| MultiBlock_O60 R006 |
Individual system parts are reusable after system dismantling. |
|
MultiBlock_O60 |
R006 |
[G05:MultiBlock_O60 R006] [G01:MultiBlock_C60 R006] |
|
|
|
|
Recycling |
| MultiBlock_O60 R007 |
Reusable parts can be disassembled without braking. |
|
MultiBlock_O60 |
R007 |
[G05:MultiBlock_F60 R006] |
|
|
|
|
Recycling |
| MultiBlock_O50 R001 |
#SOI : System of Interest shall ensure #A1 : User is protected against shock, cutting, pinching, pearcing, burning, crushing |
|
MultiBlock_O50 |
R001 |
[G01:MultiBlock_O50 R001
| Text: |
#A1 : User shall be protected against shock, cutting, pinching, pearcing, burning, crushing |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R002 |
#SOI : System of Interest shall ensure #A1 : User is protected against deafening, drawning, emprisoning, suffocating, strangulation |
|
MultiBlock_O50 |
R002 |
[G01:MultiBlock_O50 R002
| Text: |
#A1 : User shall be protected against deafening, drawning, emprisoning, suffocating, strangulation |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R003 |
#SOI : System of Interest shall ensure #A1 : User is protected against poisoning, virus transmission, NBC contamination |
|
MultiBlock_O50 |
R003 |
[G01:MultiBlock_O50 R003
| Text: |
#A1 : User shall be protected against poisoning, virus transmission, NBC contamination |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R004 |
#SOI : System of Interest shall ensure #A13 : Passenger is protected against shock, cutting, pinching, pearcing, burning, crushing |
|
MultiBlock_O50 |
R004 |
[G01:MultiBlock_O50 R004
| Text: |
#A13 : Passenger shall be protected against shock, cutting, pinching, pearcing, burning, crushing |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R005 |
#SOI : System of Interest shall ensure #A13 : Passenger is protected against deafening, drawning, emprisoning, suffocating, strangulation |
|
MultiBlock_O50 |
R005 |
[G01:MultiBlock_O50 R005
| Text: |
#A13 : Passenger shall be protected against deafening, drawning, emprisoning, suffocating, strangulation |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R006 |
#SOI : System of Interest shall ensure #A13 : Passenger is protected against poisoning, virus transmission, NBC contamination |
|
MultiBlock_O50 |
R006 |
[G01:MultiBlock_O50 R006
| Text: |
#A13 : Passenger shall be protected against poisoning, virus transmission, NBC contamination |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R007 |
#SOI : System of Interest shall ensure #A14 : Pedestrian is protected against shock, cutting, pinching, pearcing, burning, crushing, deafening, psychological shock, |
|
MultiBlock_O50 |
R007 |
[G01:MultiBlock_O50 R007
| Text: |
#A14 : Pedestrian shall be protected against shock, cutting, pinching, pearcing, burning, crushing, deafening, psychological shock, |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R008 |
#SOI : System of Interest shall ensure #A15 : Ego vehicle is protected against shock, friction, fire |
|
MultiBlock_O50 |
R008 |
[G01:MultiBlock_O50 R008
| Text: |
#A15 : Ego vehicle shall be protected against shock, friction, fire |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R009 |
#SOI : System of Interest shall ensure #A16 : External vehicle is protected against shock, blinding, fire propagation |
|
MultiBlock_O50 |
R009 |
[G01:MultiBlock_O50 R009
| Text: |
#A16 : External vehicle shall be protected against shock, blinding, fire propagation |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R010 |
#SOI : System of Interest shall ensure #A17 : Weather is protected against air pollution, CO2 emission, oil spoiling, noise, odors |
|
MultiBlock_O50 |
R010 |
[G01:MultiBlock_O50 R010
| Text: |
#A17 : Weather shall be protected against air pollution, CO2 emission, oil spoiling, noise, odors |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R011 |
#SOI : System of Interest shall ensure #A18 : Road is protected against jamming, obstruction, digging potholes, burning, liquid spread (oil, water) |
|
MultiBlock_O50 |
R011 |
[G01:MultiBlock_O50 R011
| Text: |
#A18 : Road shall be protected against jamming, obstruction, digging potholes, burning, liquid spread (oil, water) |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O50 R012 |
#SOI : System of Interest shall ensure #A19 : Signalisation is protected against shock, tearing, reducing road lines visibility |
|
MultiBlock_O50 |
R012 |
[G01:MultiBlock_O50 R012
| Text: |
#A19 : Signalisation shall be protected against shock, tearing, reducing road lines visibility |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O33 R06 |
The system SOI shall ensure that Other activities than driving through on-board displays are suspended when driver attention is required. |
|
MultiBlock_O33 |
R06 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
ALKS requirement. |
"Other activities than driving" through on-board displays available upon activation of the ALKS shall be automatically suspended (i) as soon as the system issues a Transition Demand or (ii) as soon as the system is deactivated, whichever comes first. |
Stakeholder Need |
| MultiBlock_O33 R71 |
The system SOI shall ensure that if a driver presence warning lasts for 15s, a transition demand is emitted. |
|
MultiBlock_O33 |
R71 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Transition requirement. |
As soon as the driver is deemed to be unavailable, or fewer than two availability criteria can be monitored, the system shall immediately provide a distinctive warning until appropriate actions of the driver are detected or until a transition demand is in |
Stakeholder Need |
| MultiBlock_O33 R69 |
The system SOI shall ensure that MRM is engaged if the driver isn't available. |
|
MultiBlock_O33 |
R69 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
MRM requirement. |
The manufacturer shall demonstrate to the satisfaction of the technical service the vehicles capability to detect that the driver is available to take over the driving task. The driver shall be deemed to be unavailable unless at least two availability cri |
Stakeholder Need |
| MultiBlock_O33 R68 |
The system SOI shall ensure that if driver is not present, or safety belt is unfastened, or drowsiness is detected, a MRM is engaged. |
|
MultiBlock_O33 |
R68 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Transition requirement. |
The system shall comprise a driver availability recognition system.The driver availability recognition system shall detect if the driver is present in a driving position, if the safety belt of the driver is fastened and if the driver is available to take |
Stakeholder Need |
| MultiBlock_O33 R85 |
The system SOI shall ensure that the driver can override longitudinal control by braking. |
|
MultiBlock_O33 |
R85 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Control requirement. |
A driver input to the braking control resulting in a higher deceleration than that induced by the system or maintaining the vehicle in standstill by any braking system, shall override the longitudinal control function of the system. |
Stakeholder Need |
| MultiBlock_O33 R82 |
The system SOI shall ensure that the driver can override lateral control by steering wheel operation. |
|
MultiBlock_O33 |
R82 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
ALKS requirement. |
A driver input to the steering control shall override the lateral control function of the system when the input exceeds a reasonable threshold designed to prevent unintentional override. This threshold shall include a specified force and duration and shal |
Stakeholder Need |
| MultiBlock_O33 R86 |
The system SOI shall ensure that the driver can override longitudinal control by acceleration. |
|
MultiBlock_O33 |
R86 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
A driver input to the accelerator control may override the longitudinal control function of the system. However, such an input shall not cause the system to no longer meet the requirements of this Regulation. |
Stakeholder Need |
| MultiBlock_O33 R80 |
The system SOI shall ensure that ALKS deactivation is independent from other ADAS. |
|
MultiBlock_O33 |
R80 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
Any other safety system delivering longitudinal or lateral support in imminent collision situations (e.g. Advanced Emergency Braking System (AEBS), Electronic Stability Control (ESC), Brake Assist System (BAS) or Emergency Steering Function (ESF)) shall n |
Stakeholder Need |
| MultiBlock_O33 R77 |
The system SOI shall ensure that ALKS remains active until the driver takes control or the vehicle is at standstill. |
|
MultiBlock_O33 |
R77 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Transition/MRM requirement. |
In case a transition demand or a minimum risk manoeuvre is on-going, the system shall only be deactivated: (a) As defined. (b) Upon detection that the driver has taken hold of the steering control as a respon |
Stakeholder Need |
| MultiBlock_O33 R73 |
The system SOI shall ensure that ALKS deactivation interface is available during operation. |
|
MultiBlock_O33 |
R73 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
The vehicle shall be equipped with dedicated means for the driver to activate (active mode) and deactivate (off mode) the system. When the ALKS is activated, the means to deactivate ALKS shall be permanently visible to the driver. On deactivation of the s |
Stakeholder Need |
| MultiBlock_O33 R81 |
The system SOI shall ensure that ALKS deactivation is notified. |
|
MultiBlock_O33 |
R81 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
Any deactivation shall be indicated to the driver. |
Stakeholder Need |
| MultiBlock_O33 R75 |
The system SOI shall ensure that activation is made by the driver. |
|
MultiBlock_O33 |
R75 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
The system shall become active only upon a deliberate action by the driver. |
Stakeholder Need |
| MultiBlock_O33 R76 |
The system SOI shall ensure that the driver is protected against manual deactivation. |
|
MultiBlock_O33 |
R76 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
The means of deactivating shall provide protection against unintentional manual deactivation for example by requiring a single input exceeding a certain threshold of time or a double press, or two separate but simultaneous inputs. It shall be ensured the |
Stakeholder Need |
| MultiBlock_O33 R98 |
The system SOI shall ensure that acoustic/optical warning are prioritized. |
|
MultiBlock_O33 |
R98 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
The prioritization of different acoustic and optical warnings during the ALKS operation shall be declared by the manufacturer to the Technical Service during Type Approval. |
Stakeholder Need |
| MultiBlock_O33 R89 |
The system SOI shall ensure that activation is indicated by a dedicated optical signal. |
|
MultiBlock_O33 |
R89 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
Upon activation the system status (active mode) shall be displayed by a dedicated optical signal to the driver. The optical signal shall contain an unambiguous indication. The optical signal shall indicate the active system state until the system is deact |
Stakeholder Need |
| MultiBlock_O33 R92 |
The system SOI shall ensure that constant signal is provided during operation until the initiation of a transition demand. |
|
MultiBlock_O33 |
R92 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
The optical signal shall be constant while the system is in regular operation and with the initiation of a transition demand at least the indication according to (b : An easily perceptible indication in the peripheral field of vision and located near the |
Stakeholder Need |
| MultiBlock_O33 R95 |
The system SOI shall ensure that acoustic signal is emitted during transition demand. |
|
MultiBlock_O33 |
R95 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
An acoustic warning signal shall be provided unless the system is deactivated following a transition demand which contained an acoustic signal. |
Stakeholder Need |
| MultiBlock_O33 R97 |
The system SOI shall ensure that signal characteristics are changed with the start of the MRM. |
|
MultiBlock_O33 |
R97 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
With the start of the minimum risk manoeuvre, the given signal shall change its characteristics to emphasize the urgency of an action by the driver. e.g. by red flashing of the steering control and moving hands of the pictorial information. |
Stakeholder Need |
| MultiBlock_O33 R96 |
The system SOI shall ensure that driver is informed explicitly when a transition request is required. |
|
MultiBlock_O33 |
R96 |
[SOI:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
HMI requirement. |
During the transition phase and the Minimum Risk Manoeuvre, the system shall instruct the driver in an intuitive and unambiguous way to take over manual control of the vehicle. The instruction shall include a pictorial information showing hands and the st |
Stakeholder Need |
| MultiBlock_O32 R47 |
The system SOI shall ensure that emergency manœuvre is adapted in case of system failures. |
|
MultiBlock_O32 |
R47 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
If failures are affecting the braking or steering performance of the system, the emergency manoeuvre shall be carried out with consideration for the remaining performance. |
Stakeholder Requirement |
| MultiBlock_O32 R52 |
The system SOI shall ensure that warning lamps are deactivated after EM. |
|
MultiBlock_O32 |
R52 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
If the emergency manoeuvre results in the vehicle being at standstill, the signal to activate the hazard warning lights shall be generated. If the vehicle automatically drives off again, the signal to deactivate the hazard warning lights shall be generate |
Stakeholder Requirement |
| MultiBlock_O32 R53 |
The system SOI shall ensure that warning lamps are activated during EM and at standstill. |
|
MultiBlock_O32 |
R53 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
The vehicle shall implement a logic signal indicating emergency braking. |
Stakeholder Requirement |
| MultiBlock_O32 R44 |
The system SOI shall ensure that Emergency Manœuvre is required in case of imminent collision risk with maximum braking or evasive manœuvre. |
|
MultiBlock_O32 |
R44 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
An Emergency Manoeuvre shall be carried out in case of an imminent collision risk. The Emergency Manoeuvre shall decelerate the vehicle up to its full braking performance if necessary and/or may perform an automatic evasive manoeuvre, when appropriate. An |
Stakeholder Requirement |
| MultiBlock_O32 R48 |
The system SOI shall ensure that lane is kept during evasive manœuvre. |
|
MultiBlock_O32 |
R48 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
During the evasive manoeuvre the ALKS vehicle shall not cross the lane marking (outer edge of the front tyre to outer edge of the lane marking). |
Stakeholder Requirement |
| MultiBlock_O32 R49 |
The system SOI shall ensure that the position is resumed after evasive manœuvre. |
|
MultiBlock_O32 |
R49 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
After the evasive manoeuvre the vehicle shall aim at resuming a stable position. After an emergency manoeuvre is terminated the system shall continue to operate. |
Stakeholder Requirement |
| MultiBlock_O32 R12 |
The system SOI shall ensure that warning lamps are activated during MRM and after. |
|
MultiBlock_O32 |
R12 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
MRM requirement. |
The signal to activate the hazard warning lights shall be generated with the start of the minimum risk manoeuvre. Once in standstill the vehicle may remain in this condition and shall generate the signal to activate the hazard warning lights within 5 s. |
Stakeholder Requirement |
| MultiBlock_O32 R64 |
The system SOI shall ensure that if driver is not responding to transition demand, MRM is started. |
|
MultiBlock_O32 |
R64 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
In case the driver is not responding to a transition demand by deactivating the system, a minimum risk manoeuvre shall be started, earliest 10 s after the start of the transition demand. |
Stakeholder Requirement |
| MultiBlock_O32 R60 |
The system SOI shall ensure that ADV operates during control transfer to driver. |
|
MultiBlock_O32 |
R60 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
During the transition phase the system shall continue to operate. The system may reduce the speed of the vehicle to ensure its safe operation but shall not bring it to standstill unless required by the situation (e.g. due to vehicles or obstacles obstruct |
Stakeholder Requirement |
| MultiBlock_O32 R59 |
The system SOI shall ensure that transition demand is emitted in case of ALKS failure. |
|
MultiBlock_O32 |
R59 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
In case of a planned event, the transition demand is early enough to allow MRM to stop the vehicle before the planned event if driver is not responding. In case of any failure affecting the operation of the system, the system shall immediately initiate a |
Stakeholder Requirement |
| MultiBlock_O32 R56 |
The system SOI shall ensure that transition demand is initiated to leave enough time for a safe transition to driver. |
|
MultiBlock_O32 |
R56 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
The initiation of the transition demand shall be such that sufficient time is provided for a safe transition to manual driving. |
Stakeholder Requirement |
| MultiBlock_O32 R62 |
The system SOI shall ensure that transition demand is escalated after 4 s. |
|
MultiBlock_O32 |
R62 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
During the transition phase, the transition demand shall be escalated latest after 4 s after the start of the transition demand. |
Stakeholder Requirement |
| MultiBlock_O32 R63 |
The system SOI shall ensure that transition demand is ended by deactivation or MRM. |
|
MultiBlock_O32 |
R63 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
A transition demand shall only be terminated once the system is deactivated or a minimum risk manoeuvre has started. |
Stakeholder Requirement |
| MultiBlock_O32 R57 |
The system SOI shall ensure that if the driver is not responding, early request transition is given to ensure MRM. |
|
MultiBlock_O32 |
R57 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
In case of a planned event that would prevent the ALKS from continuing the operation, a transition demand shall be given early enough to ensure the minimal risk manoeuver, in case the driver would not resume control, would bring the vehicle to standstill |
Stakeholder Requirement |
| MultiBlock_O32 R58 |
The system SOI shall ensure that transition demand is emitted upon unplanned event detection. |
|
MultiBlock_O32 |
R58 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Transition requirement. |
In case of an unplanned event, a transition demand shall be given upon detection. |
Stakeholder Requirement |
| MultiBlock_O32 R11 |
The system SOI shall ensure that speed is decelerated when making MRM in the current lane. |
|
MultiBlock_O32 |
R11 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
MRM requirement. |
During the minimum risk manoeuvre the vehicle shall be slowed down inside the lane or, in case the lane markings are not visible, remain on an appropriate trajectory taking into account surrounding traffic and road infrastructure, with an aim of achieving |
Stakeholder Requirement |
| MultiBlock_O32 R15 |
The system SOI shall ensure that ALKS is deactivated at the end of any MRM. |
|
MultiBlock_O32 |
R15 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
The system shall be deactivated at the end of any minimum risk manoeuvre. |
Stakeholder Requirement |
| MultiBlock_O32 R13 |
The system SOI shall ensure that MRM is ended by vehicle standstill or driver intervention. |
|
MultiBlock_O32 |
R13 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
MRM requirement. |
The minimum risk manoeuvre shall bring the vehicle to standstill unless the system is deactivated by the driver during the manoeuvre. A minimum risk manoeuvre shall only be terminated once the system is deactivated or the system has brought the vehicle to |
Stakeholder Requirement |
| MultiBlock_O32 R17 |
The system SOI shall ensure that reactivation after MRM is possible after each new run cycle. |
|
MultiBlock_O32 |
R17 |
[SOI:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
Reactivation of the system after the end of any minimum risk manoeuvre shall only be possible after each new engine start/run cycle. |
Stakeholder Requirement |
| MultiBlock_O30 R1 |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
|
MultiBlock_O30 |
R1 |
[G01:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O30 R2 |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
|
MultiBlock_O30 |
R2 |
[G01:MultiBlock_O30 R2
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O30 R3 |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
|
MultiBlock_O30 |
R3 |
[G01:MultiBlock_O30 R3
| Text: |
Compliance shall be esured to Human Machine Interface/operator information clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O30 R4 |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
|
MultiBlock_O30 |
R4 |
[G01:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O30 R5 |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
|
MultiBlock_O30 |
R5 |
[G01:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O30 R6 |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
|
MultiBlock_O30 |
R6 |
[G01:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O20 R001 |
Movable components shall be delivered in an initial position for assembling. |
|
MultiBlock_O20 |
R001 |
[G02:MultiBlock_O20 R001] [G01:MultiBlock_O20 R001
| Text: |
The #G01 : Product Overall shall ensure that movable components are in an initial position for assembling. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R002 |
Physical design shall ensure intuitive parts guiding and positioning for assembly. |
|
MultiBlock_O20 |
R002 |
[G02:MultiBlock_O20 R002] [G01:MultiBlock_O20 R002
| Text: |
The #G01 : Product Overall shall ensure that software can be uploaded via diagnostic interface. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R003 |
The product shall tolerate positioning precision of 1mm. |
|
MultiBlock_O20 |
R003 |
[G02:MultiBlock_O20 R003] [G01:MultiBlock_O20 R003
| Text: |
The #G01 : Product Overall shall ensure that failure memory can be cleaned through diagnostic interface. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R004 |
The product shall tolerante a manufacturing capabilitiy of 1mm (6 sigma). |
|
MultiBlock_O20 |
R004 |
[G02:MultiBlock_O20 R004] [G01:MultiBlock_O20 R004
| Text: |
The #G01 : Product Overall shall ensure that automatic functions can be inhibited through diagnostic interface. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R005 |
Workers shall be able to manipulate parts safely. |
|
MultiBlock_O20 |
R005 |
[G02:MultiBlock_O20 R006] [G01:MultiBlock_O20 R006
| Text: |
The #G01 : Product Overall shall ensure that Parts can be manipulated without pinching or cutting by sharp edge. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R006 |
Parts shall resist to dropping before assembling by the operator. |
|
MultiBlock_O20 |
R006 |
[G02:MultiBlock_O20 R006] [G01:MultiBlock_O20 R006
| Text: |
The #G01 : Product Overall shall ensure that Parts can be manipulated without pinching or cutting by sharp edge. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R007 |
If a part is damaged by a shock, then visual inspection shall be sufficient to detect the damage. |
|
MultiBlock_O20 |
R007 |
[G02:MultiBlock_O20 R007] [G01:MultiBlock_O20 R007
| Text: |
The #G01 : Product Overall shall ensure that parts resist to dropping before mounting. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R008 |
Components shall resist to electrostatic shock during assembling without damage. |
|
MultiBlock_O20 |
R008 |
[G02:MultiBlock_O20 R008] [G01:MultiBlock_O20 R008
| Text: |
The #G01 : Product Overall shall ensure that parts resist to electrostatic shock during assembling. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O20 R009 |
Screwed fixations shall resit without damage to efforts up to the twice nominal fastening effort. |
|
MultiBlock_O20 |
R009 |
[G02:MultiBlock_O20 R009] [G01:MultiBlock_O20 R009
| Text: |
The #G01 : Product Overall shall ensure that parts resist to tightening effort. |
] |
|
|
|
|
Assembly Needs |
| MultiBlock_O10 R001 |
User expects to drive without major failures during 15 years or 150000km |
|
MultiBlock_O10 |
R001 |
[G01:MultiBlock_O10 R001
| Text: |
User expects to drive without major failures during 15 years or 150000km |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O10 R002 |
User expects to drive without intermediate failures during 8 years or 75000km |
|
MultiBlock_O10 |
R002 |
[G01:MultiBlock_O10 R002
| Text: |
User expects to drive without intermediate failures during 8 years or 75000km |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O10 R003 |
User expects to drive without minor failures during 3 years or 40000km |
|
MultiBlock_O10 |
R003 |
[G01:MultiBlock_O10 R003
| Text: |
User expects to drive without minor failures during 3 years or 40000km |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O10 R004 |
Product shall be produced with a failure rate lower than 100ppm at factory exit. |
|
MultiBlock_O10 |
R004 |
[G01:MultiBlock_O10 R004
| Text: |
Product shall be produced with a failure rate lower than 100ppm at factory exit. |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O10 R005 |
Geometrical quality of parts positioning shall be better than 1mm. |
|
MultiBlock_O10 |
R005 |
[G01:MultiBlock_O10 R005
| Text: |
Geometrical quality of parts positioning shall be better than 1mm. |
] |
|
|
|
|
Stakeholder Need |
| MultiBlock_O34 UNR106 |
The system SOI shall ensure that a single perception malfunction does not introduce hazardous events. |
|
MultiBlock_O34 |
UNR106 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Failure detection requirement. |
A single perception malfunction without failure should not induce hazardous event. The design strategies put in place shall be described by the vehicle manufacturer and their safety shall be demonstrated to the satisfaction of the technical service. |
|
| MultiBlock_O34 UNR103 |
The system SOI shall ensure that surrounding vehicles are detected. |
|
MultiBlock_O34 |
UNR103 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Control requirement. |
The Technical Service shall verify that the vehicle sensing system detects vehicles during the relevant test. This range shall be equal or greater than the declared range. |
|
| MultiBlock_O34 UNR100 |
The system SOI shall ensure that forward detection range is at least 46m. |
|
MultiBlock_O34 |
UNR100 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Control requirement. |
The manufacturer shall declare the forward detection range measured from the forward most point of the vehicle. This declared value shall be at least 46 metres. |
|
| MultiBlock_O34 UNR102 |
The system SOI shall ensure that lateral detection range covers the full width of the lane immediately to the left and of the lane immediately to the right of the vehicle. |
|
MultiBlock_O34 |
UNR102 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Control requirement. |
The manufacturer shall declare the lateral detection range. The declared range shall be sufficient to cover the full width of the lane immediately to the left and of the lane immediately to the right of the vehicle. |
|
| MultiBlock_O34 UNR104 |
The system SOI shall ensure that the system adapts to environmental conditions affecting sensors. |
|
MultiBlock_O34 |
UNR104 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Control requirement. |
The ALKS shall implement strategies to detect and compensate for environmental conditions that reduce the detection range, e.g. prevent enabling the system, disabling the system and transferring the control back to the driver, reducing the speed when visibility is too low. These strategies shall be described by the manufacturer and assessed. |
|
| MultiBlock_O34 UNR105 |
The system SOI shall ensure that performance of the sensing system is provided for the vehicle time life. |
|
MultiBlock_O34 |
UNR105 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
Control requirement. |
The vehicle manufacturer shall provide evidence that the effects of wear and ageing do not reduce the performance of the sensing system below the minimum required value over the lifetime of the system/vehicle. |
|
| MultiBlock_O34 UNR99 |
The system SOI shall ensure that driving environment is determined by sensing and traffic dynamics. |
|
MultiBlock_O34 |
UNR99 |
[SOI:MultiBlock_O30 R4
| Text: |
Compliance shall be esured to Object and Event Detection and Response (OEDR) clauses of UN Standard |
] |
|
|
ALKS requirement. |
The ALKS vehicle shall be equipped with a sensing system such that, it can at least determine the driving environment (e.g. road geometry ahead, lane markings) and the traffic dynamics: (a) Across the full width of its own traffic lane, the full width of the traffic lanes immediately to its left and to its right, up to the limit of the forward detection range; (b) Along the full length of the vehicle and up to the limit of the lateral detection range. |
|
| MultiBlock_O34 UNR108 |
The system SOI shall ensure that DSSAD records data about ALKS. |
|
MultiBlock_O34 |
UNR108 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Data recording requirement. |
Each vehicle equipped with a DSSAD shall at least record an entry for each of the following occurrences upon activation of the system: Activation or deactivation of the system, due to: (a) Activation of the system (b) Deactivation of the system, due to: (i) Use of dedicated means for the driver to deactivate the system; (ii) Override on steering control; (iii) Override by accelerator control while holding steering control; (iv) Override by braking control while holding steering control. (c) Transition Demand by the system, due to: (i) Planned event; (ii) Unplanned event; (iii) Driver unavailability (as per para. 6.1.3); (iv) Driver not present or unbuckled (as per para. 6.1.2.); (v) System failure; (vi) System override by braking input; (vii) System override by accelerator input. (d) Reduction or suppression of driver input; (e) Start of Emergency Manoeuvre; (f) End of Emergency Manoeuvre; (g) Event Data Recorder (EDR) trigger input; (h) Involved in a detected collision; (i) Minimum Risk Manoeuvre engagement by the system; (j) Severe ALKS failure; (k) Severe vehicle failure. |
|
| MultiBlock_O34 UNR110 |
The system SOI shall ensure that many elements are recorded on a single timestamp. |
|
MultiBlock_O34 |
UNR110 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Data recording requirement. |
A single timestamp may be allowed for multiple elements recorded simultaneously within the timing resolution of the specific data elements. If more than one element is recorded with the same timestamp, the information from the individual elements shall indicate the chronological order. |
|
| MultiBlock_O34 UNR109 |
The system SOI shall ensure that software versions associated to a recorded event are identified. |
|
MultiBlock_O34 |
UNR109 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Software constraints requirement. |
For each event, the R15XSWIN for ALKS, or the software versions relevant to ALKS, indicating the software that was present at the time when the event occurred, shall be clearly identifiable. |
|
| MultiBlock_O34 UNR116 |
The system SOI shall ensure that DSSAD data access is provided through OBD. |
|
MultiBlock_O34 |
UNR116 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Data recording requirement. |
Instructions from the manufacturer shall be provided on how to access the data. Data stored in the DSSAD shall be easily readable in a standardized way via the use of an electronic communication interface, at least through the standard interface (OBD port). |
|
| MultiBlock_O34 UNR112 |
The system SOI shall ensure that recorded data are overwritten using a FIFO procedure when storage limit is reached. |
|
MultiBlock_O34 |
UNR112 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Data recording requirement. |
Once the storage limits of the DSSAD are achieved, existing data shall only be overwritten following a first in first out procedure with the principle of respecting the relevant requirements for data availability. |
|
| MultiBlock_O34 UNR114 |
The system SOI shall ensure that data retrievability is provided in case of impact or power loss. |
|
MultiBlock_O34 |
UNR114 |
[SOI:MultiBlock_O30 R5
| Text: |
Compliance shall be esured to Data Storage System for Automated Systems clauses of UN Standard |
] |
|
|
Data recording requirement. |
The data shall be retrievable even after an impact of a severity level set by UN Regulations. If the main on-board vehicle power supply is not available, it shall still be possible to retrieve all data recorded on the DSSAD, as required by national and regional law. |
|
| MultiBlock_O34 UNR117 |
The system SOI shall ensure that DSSAD is protected against data manipulation. |
|
MultiBlock_O34 |
UNR117 |
[SOI:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
Software constraints requirement. |
It shall be ensured that there is adequate protection against manipulation (e.g. data erasure) of stored data such as antitampering design. |
|
| MultiBlock_O34 UNR119 |
The system SOI shall ensure that protection is provided against cyberattacks. |
|
MultiBlock_O34 |
UNR119 |
[SOI:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
Software constraints requirement. |
The effectiveness of the system shall not be adversely affected by cyberattacks, cyber threats and vulnerabilities. The effectiveness of the security measures shall be demonstrated by compliance with UN Regulation. |
|
| MultiBlock_O34 UNR120 |
The system SOI shall ensure that software updates are provided. |
|
MultiBlock_O34 |
UNR120 |
[SOI:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
Software constraints requirement. |
If the system permits software updates, the effectiveness of the software update procedures and processes shall be demonstrated by compliance with UN Regulation. |
|
| MultiBlock_O34 UNR123 |
The system SOI shall ensure that R15XWIN information are provided. |
|
MultiBlock_O34 |
UNR123 |
[SOI:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
Software constraints requirement. |
If the manufacturer implements an R15XWIN (software that was present at the time when the event occurred), the vehicle manufacturer shall provide the following information in the communication form of this Regulation: (a) The R15XSWIN (b) How to read the R15XSWIN or software version(s) in case the R15XSWIN is not held on the vehicle. |
|
| MultiBlock_O34 UNR121 |
The system SOI shall ensure that the software can be identified by R15XSWIN. |
|
MultiBlock_O34 |
UNR121 |
[SOI:MultiBlock_O30 R6
| Text: |
Compliance shall be esured to Cybersecurity and Software Updates clauses of UN Standard |
] |
|
|
Software constraints requirement. |
For the purpose of ensuring the software of the System can be identified, an R15XSWIN may be implemented by the vehicle manufacturer. If R15XSWIN is not implemented, an alternative software identification system (i.e. software version) shall be implemented. |
|
| State_Modes R01 |
FL013 = ON shall trigger the transition from #M0 : Sleep mode to #M2 : Stand by mode. |
|
State_Modes |
R01 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] [G01:State_Modes R02] |
|
|
|
|
LLR |
| State_Modes R08 |
Activation shall trigger the transition from #M2 : Stand by mode to #M4 : Active mode. |
|
State_Modes |
R08 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R08
| Text: |
FL016== True shall trigger the transition from #M2 : Stand by mode to #M4 : Active mode. |
] |
|
|
|
|
LLR |
| State_Modes R14 |
FL006 = Failure shall trigger the transition from #M4 : Active mode to #M6 : Reduced Functioning mode. |
|
State_Modes |
R14 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R14
| Text: |
FL006 == Failure shall trigger the transition from #M4 : Active mode to #M6 : Reduced Functioning mode. |
] |
|
|
|
|
LLR |
| State_Modes R03 |
FL013 = OFF shall trigger the transition from #M2 : Stand by mode to #M0 : Sleep mode. |
|
State_Modes |
R03 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R03] |
|
|
|
|
LLR |
| State_Modes R10 |
Deactivation shall trigger the transition from #M4 : Active mode to #M2 : Stand by mode. |
|
State_Modes |
R10 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R10
| Text: |
FL017== True shall trigger the transition from #M4 : Active mode to #M2 : Stand by mode. |
] |
|
|
|
|
LLR |
| State_Modes R15 |
FL006 = No Failure shall trigger the transition from #M6 : Reduced Functioning mode to #M4 : Active mode. |
|
State_Modes |
R15 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R15
| Text: |
FL006 == No Failure shall trigger the transition from #M6 : Reduced Functioning mode to #M4 : Active mode. |
] |
|
|
|
|
LLR |
| State_Modes R05 |
FL013 = OFF shall trigger the transition from #M4 : Active mode to #M0 : Sleep mode. |
|
State_Modes |
R05 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R05] |
|
|
|
|
LLR |
| State_Modes R07 |
FL013 = OFF shall trigger the transition from #M6 : Reduced Functioning mode to #M0 : Sleep mode. |
|
State_Modes |
R07 |
[SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] [G01:State_Modes R07] |
|
|
|
|
LLR |
| MultiBlock_O31 R01 |
The system SOI shall ensure that road with pedestrians and cyclists prohibition is a condition to activate the system. |
|
MultiBlock_O31 |
R01 |
Required to satisfy [SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
ALKS can be activated on roads where pedestrians and cyclists are prohibited. |
Stakeholder Need |
| MultiBlock_O31 R02 |
The system SOI shall ensure that lane separation is a condition to activate the system. |
|
MultiBlock_O31 |
R02 |
Required to satisfy [SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
Roads are equipped with a physical separation that divides the traffic moving in opposite directions and prevent traffic from cutting across the path of the vehicle. |
Stakeholder Need |
| MultiBlock_O31 R21 |
The system SOI shall ensure that control is exercised over driver supporting systems, including demist, windscreen wipers and lights. |
|
MultiBlock_O31 |
R21 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
The activated system shall exercise control over systems required to support the driver in resuming manual control at any time (e.g. demist, windscreen wipers and lights). |
Stakeholder Need |
| MultiBlock_O31 R26 |
The system SOI shall ensure that the driver is protected against misuses. |
|
MultiBlock_O31 |
R26 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Failure detection requirement. |
The manufacturer shall take measures to guard against reasonably foreseeable misuse by the driver and tampering of the system. |
Stakeholder Need |
| MultiBlock_O31 R27 |
The system SOI shall ensure that activation is prohibited if operational conditions are not fullfilled. |
|
MultiBlock_O31 |
R27 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Deactivation/Activation requirement. |
When the system can no longer meet the requirements of this Regulation, it shall not be possible to activate the system. |
Stakeholder Need |
| MultiBlock_O31 R25 |
The system SOI shall ensure that magnetic/electrical fields do not affect ALKS. |
|
MultiBlock_O31 |
R25 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Failure detection requirement. |
The effectiveness of the system shall not be adversely affected by magnetic or electrical fields. This shall be demonstrated by the series of amendments to UN Regulation. |
Stakeholder Need |
| MultiBlock_O31 R24 |
The system SOI shall ensure that ADV performs self-checks. |
|
MultiBlock_O31 |
R24 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Failure detection requirement. |
The system shall perform self-checks to detect the occurrence of failures and to confirm system performance at all times (e.g. after vehicle start the system has at least once detected an object at the same or a higher distance than that declared as detec |
Stakeholder Need |
| MultiBlock_O31 R40 |
The system SOI shall ensure that collision with a breaking leading vehicle is avoided through braking or evasive manoeuve. |
|
MultiBlock_O31 |
R40 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
ALKS requirement. |
The activated system shall avoid a collision with a leading vehicle which decelerates up to its full braking performance provided that there was no undercut of the minimum following distance the ALKS vehicle would adjust to a leading vehicle at the presen |
Stakeholder Need |
| MultiBlock_O31 R38 |
The system SOI shall ensure that standstill is required if driving lane is obstructed. |
|
MultiBlock_O31 |
R38 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
ALKS requirement. |
The activated system shall be able to bring the vehicle to a complete stop behind a stationary vehicle, a stationary road user or a blocked lane of travel to avoid a collision. This shall be ensured up to the maximum operational speed of the system. |
Stakeholder Need |
| MultiBlock_O31 R39 |
The system SOI shall ensure that collision risk is detected and avoided by manœuvres. |
|
MultiBlock_O31 |
R39 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
EM requirement. |
The activated system shall detect the risk of collision in particular with another road user ahead or beside the vehicle, due to a decelerating lead vehicle, a cutting in vehicle or a suddenly appearing obstacle and shall automatically perform appropriate |
Stakeholder Need |
| MultiBlock_O31 R41 |
The system SOI shall ensure that collision with a pedestrian is avoided. |
|
MultiBlock_O31 |
R41 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
ALKS requirement. |
The activated system shall avoid a collision with an unobstructed crossing pedestrian in front of the vehicle. In a scenario with an unobstructed pedestrian crossing with a lateral speed component of not more than 5 km/h where the anticipated impact point |
Stakeholder Need |
| MultiBlock_O31 R32 |
The system SOI shall ensure that speed is controlled and limited to 60kph. |
|
MultiBlock_O31 |
R32 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
The activated system shall control the speed of the vehicle. This regulation limits the operational speed to 60 km/h maximum. |
Stakeholder Need |
| MultiBlock_O31 R33 |
The system SOI shall ensure that speed is adapted to environmental conditions. |
|
MultiBlock_O31 |
R33 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
The activated system shall adapt the vehicle speed to infrastructural and environmental conditions (e.g. narrow curve radii, inclement weather). |
Stakeholder Need |
| MultiBlock_O31 R30 |
The system SOI shall ensure that the vehicle position on the lane is stable. |
|
MultiBlock_O31 |
R30 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
ALKS requirement. |
The activated system shall keep the vehicle inside its lane of travel and ensure that the vehicle does not cross any lane marking (outer edge of the front tyre to outer edge of the lane marking). The system shall aim to keep the vehicle in a stable latera |
Stakeholder Need |
| MultiBlock_O31 R31 |
The system SOI shall ensure that speed and position are adapted in the lane according to vehicle nearby. |
|
MultiBlock_O31 |
R31 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
The activated system shall detect a vehicle driving beside and, if necessary, adjust the speed and/or the lateral position of the vehicle within its lane as appropriate. |
Stakeholder Need |
| MultiBlock_O31 R35 |
The system SOI shall ensure that speed is adapted according to the distance with the vehicle ahead. |
|
MultiBlock_O31 |
R35 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
The activated system shall detect the distance to the next vehicle in front and shall adapt the vehicle speed in order to avoid collision. While the ALKS vehicle is not at standstill, the system shall adapt the speed to adjust the distance to a vehicle in |
Stakeholder Need |
| MultiBlock_O31 R36 |
The system SOI shall ensure that time gap is readjusted with vehicle ahead. |
|
MultiBlock_O31 |
R36 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
In case the minimum time gap cannot be respected temporarily because of other road users (e.g. vehicle is cutting in, decelerating lead vehicle, etc.), the vehicle shall readjust the minimum following distance at the next available opportunity without any |
Stakeholder Need |
| MultiBlock_O31 R37 |
The system SOI shall ensure that minimum distance of 2 m is keeped with the vehicle ahead. |
|
MultiBlock_O31 |
R37 |
[SOI:MultiBlock_O30 R1
| Text: |
Compliance shall be esured to System Safety and Fail-safe Response clauses of UN Standard |
] |
|
|
Control requirement. |
the minimum following distance shall never be less than 2 m. |
Stakeholder Need |
| Sequence_O01 T001 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O01 |
T001 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O01 T002 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O01 |
T002 |
[SOI:MultiBlock_O80 R010
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O01 T003 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O01 |
T003 |
[SOI:MultiBlock_O80 R011
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O02 T001 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O02 |
T001 |
[SOI:MultiBlock_O80 R012
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O02 T002 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O02 |
T002 |
[SOI:MultiBlock_O80 R013
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O02 T003 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O02 |
T003 |
[SOI:MultiBlock_O80 R014
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O03 T001 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O03 |
T001 |
[SOI:MultiBlock_O80 R015
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O03 T002 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O03 |
T002 |
[SOI:MultiBlock_O80 R016
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| Sequence_O03 T003 |
#SOI : System of Interest shall satisfy condition xxx |
#UC01 : Case 1 |
Sequence_O03 |
T003 |
[SOI:MultiBlock_O80 R017
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] |
|
#SOI : System of Interest |
|
|
Test |
| SingleBlock_F01 R001 |
Output I013 encodes in electronical data the I001 physical signal with a precision of x% |
|
SingleBlock_F01 |
R001 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] [SOI:MultiBlock_OS1 R010] [SOI:MultiBlock_OS1 R011] |
|
|
|
|
LLR |
| SingleBlock_F01 R002 |
Output I013 stays below MaxValue |
|
SingleBlock_F01 |
R002 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] [SOI:MultiBlock_OS1 R010] [SOI:MultiBlock_OS1 R011] |
|
|
|
|
LLR |
| SingleBlock_F01 R003 |
Output I013 stays above MinValue |
|
SingleBlock_F01 |
R003 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] [SOI:MultiBlock_OS1 R010] [SOI:MultiBlock_OS1 R011] |
|
|
|
|
LLR |
| SingleBlock_F01 R004 |
Output I013 is updated every x ms |
|
SingleBlock_F01 |
R004 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] [SOI:MultiBlock_OS1 R010] [SOI:MultiBlock_OS1 R011] |
|
|
|
|
LLR |
| SingleBlock_F01 R005 |
Output I013 has a lag time lower than xms |
|
SingleBlock_F01 |
R005 |
[SOI:MultiBlock_O80 R009
| Text: |
#A1 : User expects that the service xx is realized with the following performance level: TBD in condition TBD |
] [SOI:MultiBlock_OS1 R010] [SOI:MultiBlock_OS1 R011] |
|
|
|
|
LLR |
| SingleBlock_F03 R1 |
Output I014 encodes in electronical data the I001 physical signal with a precision of x%. |
|
SingleBlock_F03 |
R1 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F04 R001 |
The #[SingleBlock_F04] : Supervise Functioning function shall set the functioning mode.. |
|
SingleBlock_F04 |
R001 |
[SOI:MultiBlock_O80 R001
| Text: |
#A1 : User expects that Functionalities are available x s after switch on |
] [SOI:MultiBlock_O80 R003
| Text: |
#A1 : User expects that The system can be switched off at any time, in any state. |
] |
|
|
|
|
LLR |
| SingleBlock_F06 R001 |
I006 shall be set to 1 if I003 is out of range. |
|
SingleBlock_F06 |
R001 |
|
|
|
|
|
|
| SingleBlock_F06 R002 |
I006 shall be set to 1 if I005 is out of range. |
|
SingleBlock_F06 |
R002 |
|
|
|
|
|
|
| SingleBlock_F06 R003 |
I006 shall be set to 1 if I003 and I005 are inconsistent with model. |
|
SingleBlock_F06 |
R003 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F07 R1 |
The control shall consist in a PID with P = xxx, I =yyy, D=zzz. |
|
SingleBlock_F07 |
R1 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F08 R001 |
I009 shall be transformed into physical action I011 in less than x seconds. |
|
SingleBlock_F08 |
R001 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F08 R002 |
I009 shall be transformed into physical action I011 with a precision better than c %.. |
|
SingleBlock_F08 |
R002 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F09 R001 |
The #[SingleBlock_F09] : Realize Actuation 2 function shall I010 shall be transformed into physical action I012 in less than x seconds. |
|
SingleBlock_F09 |
R001 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F09 R002 |
The #[SingleBlock_F09] : Realize Actuation 2 function shall I010 shall be transformed into physical action I012 with a precision better than c %.. |
|
SingleBlock_F09 |
R002 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F10 R001 |
Signal 1 shall be invalid during initialisation |
|
SingleBlock_F10 |
R001 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F11 R001 |
The #UNKNOWN: ??? function shall Time without relevant signal 2 at switch on shall be less than xms. |
|
SingleBlock_F11 |
R001 |
[SOI:SingleBlock_OS1 R001] [SOI:SingleBlock_OS1 R002] [SOI:SingleBlock_OS1 R003] |
|
|
|
|
LLR |
| SingleBlock_F12 R001 |
The #UNKNOWN: ??? function shall provide SW identification for current SW and SW version for recorded events. |
|
SingleBlock_F12 |
R001 |
[SOI:MultiBlock_O34 UNR123
| Text: |
The system SOI shall ensure that R15XWIN information are provided. |
] [SOI:MultiBlock_O34 UNR121
| Text: |
The system SOI shall ensure that the software can be identified by R15XSWIN. |
] |
|
|
|
|
LLR |
| SingleBlock_F14 R001 |
The #UNKNOWN: ??? function shall Detect and reject unauthorised access. |
|
SingleBlock_F14 |
R001 |
[SOI:MultiBlock_O34 UNR119
| Text: |
The system SOI shall ensure that protection is provided against cyberattacks. |
] |
|
|
|
|
LLR |
| SingleBlock_S01 R001 |
The system SOI shall ensure major failures occurrence is lower than 100ppm over mission profile of 15 years or 150000km |
|
SingleBlock_S01 |
R001 |
[SOI:MultiBlock_O10 R001
| Text: |
User expects to drive without major failures during 15 years or 150000km |
] |
|
|
|
|
System Requirement |
| SingleBlock_S01 R002 |
The system SOI shall ensure intermediate failures occurrence is lower than 100ppm over mission profile of 8 years or 75000km |
|
SingleBlock_S01 |
R002 |
[SOI:MultiBlock_O10 R002
| Text: |
User expects to drive without intermediate failures during 8 years or 75000km |
] |
|
|
|
|
System Requirement |
| SingleBlock_S01 R003 |
The system SOI shall ensure minor failures occurrence is lower than 100ppm over mission profile of 3 years or 40000km |
|
SingleBlock_S01 |
R003 |
[SOI:MultiBlock_O10 R003
| Text: |
User expects to drive without minor failures during 3 years or 40000km |
] |
|
|
|
|
System Requirement |
| MultiBlock_O40 R001 |
Defective parts are identified automatically or by visual inspection. |
|
MultiBlock_O40 |
R001 |
[G01:MultiBlock_O40 R001
| Text: |
#G01 : Product Overall shall ensure that failure are detected and failure codes are recorded. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R011 |
Defective parts can be replaced in a company workshop. |
|
MultiBlock_O40 |
R011 |
[G01:MultiBlock_O40 R011
| Text: |
#G01 : Product Overall shall ensure that failure codes can be accessed through diagnostic tool. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R002 |
Software can be updated without part replacement. |
|
MultiBlock_O40 |
R002 |
[G01:MultiBlock_O40 R002
| Text: |
#G01 : Product Overall shall ensure that software can be uploaded via diagnostic interface. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R003 |
Failure memory can be cleaned after repair operation. |
|
MultiBlock_O40 |
R003 |
[G01:MultiBlock_O40 R003
| Text: |
#G01 : Product Overall shall ensure that failure memory can be cleaned on diagnostic request. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R004 |
Parts can be accessed for disassembling with space and ergonomic conditons |
|
MultiBlock_O40 |
R004 |
[G01:MultiBlock_O40 R004
| Text: |
#G01 : Product Overall shall ensure that movable components can be positioned for disassembling. |
] [G01:MultiBlock_O40 R010
| Text: |
#G01 : Product Overall shall ensure that parts can be accessed for disassembling and reassembling. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R005 |
System automatic functions can be deactiveted for maintenance intervention. |
|
MultiBlock_O40 |
R005 |
[G01:MultiBlock_O40 R005
| Text: |
#G01 : Product Overall shall ensure that function can be activated or inhibited through diagnostic interface. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R006 |
Dynamic parameters can be read to support the diagnstic. |
|
MultiBlock_O40 |
R006 |
[G01:MultiBlock_O40 R006
| Text: |
#G01 : Product Overall shall ensure that dynamic parameters can be viewed. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R008 |
Parts can be manipulated by humans without pinching, cutting or any other damage. |
|
MultiBlock_O40 |
R008 |
[G01:MultiBlock_O40 R008
| Text: |
#G01 : Product Overall shall ensure that parts can be manipulated without pinching, cutting. |
] |
|
|
|
|
Maintenance Needs |
| MultiBlock_O40 R009 |
Failure codes recorded in control units can be read with a specific tool. |
|
MultiBlock_O40 |
R009 |
[G01:MultiBlock_O40 R009
| Text: |
#G01 : Product Overall shall ensure that operators can read failure codes via diagnostic tool. |
] |
|
|
|
|
Maintenance Needs |
