[Feature] Automated Valet Parking Readiness

[apds-change-control]

The EAVP initiative (European Automated Valet Parking) has chosen APDS to the standard for communication between the stakeholders in this type of systems. The current version of APDS does not cover everything that would be required to fulfill this. Some examples would be addressed by changes outlined earlier in this document, others would be new. Examples: online reservation (Quotes domain enhancements), value added services (see „Services“ above), vehicle characteristics to match car parks vs. vehicles

[plexxdigital]

I am in the process of finalising a draft model enhancement for this purpose. There are two sub-tasks in this:

• core AVP readiness and
• readiness for value-added services, in particular automated charging of EVs

core AVP

AVP service availability in a parking location depends on a perfect match between vehicle characteristics and parking location infrastructure characteristics.
The set of about three dozens of properties specifies requirements/constraints of a particular vehicle. Car OEMs will have to define derived vehicle classifications and assign them unique, standardised identifiers. APDS model-wise, this will be implemented as a user-defined code list. We will then need to be able to specify the range of AVP vehicle classifications that are supported. I am thinking to add this as another eligibility qualification usable in right specifications.

The API will then have to be enhanced to

• expose those new properties and list
• offer a query/filter mechanism that considers them

automated charging

Automated charging requires a way to specify requirements/constraints that depend on the robotic charging system used. One - standardised - (ISO 12768-1:2021E, IEC DTS 618851-27) important element here is the so-called mating space, the space required to connect the EVSE (electrical vehicle supply equipment) to the vehicle. It is specified in the format

• x1, x2 (minimum/maximum distance in x-direction cm)
• y1, y2 (minimum/maximum distance in y-direction cm)
• z1, z2 (minimum/maximum distance in z-direction cm)
• rx1, rx2 (minimum/maximum rotation about x axis °)
• ry1, ry2 (minimum/maximum rotation about y axis °)
• rz1, rz2 (minimum/maximum rotation about z axis ° )

I will be meeting with the OEM experts next week to discuss this. I will come back to the team after this.

[plexxdigital]

The initial modelling work is currently done outside the APDS CCG, by the EAVP technical working group who will take it to the CCG once their work is done. Hence, for now putting "on hold" in here.