# Clearance Lifecycle

{% hint style="warning" %}
The following flows are closely related to OEM integrations and our internal software, and are subject to change without prior notice.
{% endhint %}

## Activation

The following flowchart explains the high level of activation procedure&#x20;

{% @mermaid/diagram content="graph TD
classDef eventProducerErrorClass fill:red,color:white;
classDef eventProducerSuccessClass fill:green;
ActivationRequest\[Activation Requested] --> CheckThereIsOnGoing{In progress?₁}
CheckThereIsOnGoing --> |yes| CheckThereIsOnGoing
CheckThereIsOnGoing --> |no| AlreadyActive{Already in<br />HM Fleet?₂}
AlreadyActive --> |yes| CheckForPackage{Use<br /> the same package?}
CheckForPackage --> |no| Rejected:::eventProducerErrorClass
AlreadyActive --> |no| CheckEligibility{Check Eligibility }
CheckEligibility --> |eligibel| ActivateVehilce\[Activate Vehicle]
CheckForPackage --> |yes| Approved:::eventProducerSuccessClass
CheckEligibility --> |ineligible| Rejected
ActivateVehilce --> OemConfirmed{Wait until activated<br />on OEM side?}
OemConfirmed --> |yes| VerifyDataDelivery{Wait until data is being delivered?₃}
VerifyDataDelivery --> |10 days past| RemoveVehicleFromOEM --> Rejected
VerifyDataDelivery --> |yes| Approved
RemoveVehicleFromOEM --> WaitForOEMConfirmation{Wait for OEM Confirmation₄}
WaitForOEMConfirmation --> WaitForOEMConfirmation
" %}

1. If this vin is already used by any of our customers and in transition, your activation gets paused. It includes when this vehicle is revoked/canceled by HM status but OEM side hasn't confirmed it yet.&#x20;
2. You may use one VIN from stellantis brand in multiple app as long as they use the package.&#x20;
3. We only change status of the vehicle to `approved` only we have received data for that vehicle. If no data is delivered in 10 days, we change the vehicle status to `rejected` and remove the vehicle from OEM side.
4. Event hough you see the vehicle status as  `rejected` in [Broken link](https://docs.high-mobility.com/oem-guides/stellantis/broken-reference "mention"), you can only activate this vehicle again if we get confirmation from OEM that they have removed it on their side.

## Deactivation

The following flowchart explains the high level of deactivation procedure

{% @mermaid/diagram content="graph TD
classDef eventProducerSuccessClass fill:orange;
DeactivationRequest --> VehicleIsUsedByAnotherCustomer{Is vehicled<br/>used by another app?}
VehicleIsUsedByAnotherCustomer --> |no| RemoveVehicleFromOEM\[Deactivate Vehicle<br />On OEM side]
RemoveVehicleFromOEM --> Revoked:::eventProducerSuccessClass
RemoveVehicleFromOEM --> WaitForOEMConfirmation{Wait for OEM Confirmation₁}
WaitForOEMConfirmation --> WaitForOEMConfirmation
VehicleIsUsedByAnotherCustomer --> |yes| Revoked\[Revoked/Canceled]
" %}

1. If you deactivate a vehicle, event hough you might see its status as  `revoked` in [Broken link](https://docs.high-mobility.com/oem-guides/stellantis/broken-reference "mention"), you can only activate this vehicle again if we get confirmation from OEM that they have removed it on their side.
