You are here:
Usage-Based Entitlements for Connected Vehicles in Automotive Cloud
Vehicle Connected Services in Automotive Cloud includes a set of usage-based entitlements that users can use to perform different actions for connected vehicles. Usage-based entitlements don’t limit what you can do in Salesforce; they are contractually enforced limits that vary based on the consumption of data in an org. The entitlements for connected vehicles can be used as guidance for the optimum number of calls that can be executed for specific actions. If your company’s usage exceeds the allowance, Salesforce contacts you to discuss additions to your contract.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions |
Make sure the Vehicle Connected Services Monthly Per Unit Entitlement add-on license is provisioned and Connected Vehicle Services is enabled in the org. For per-month entitlements, your contract determines the start and end of the month. You can view the start and end dates for your org’s usage-based entitlements on the Company Information page in Setup.
This table describes the allocations that are granted when you purchase the Vehicle Connected Services Monthly Per Unit Entitlement add-on license. These allocations apply to the org and not to individual users who perform the actions.
You must also purchase the required number of Omnistudio calls, Business Rules Engine calls, Flow calls, and Business API calls for the connected services separately that compliment the allowed number of calls for each action.
| Usage-Based Entitlement Name | Usage-Based Entitlement Allowance | What’s Counted? |
|---|---|---|
| Active Connected Vehicle Count Limit | You can mark 1 vehicle as Connected Services Active per add-on license. | Each Vehicle Connected Services Monthly Per Unit Entitlement add-on license gives access to one unit of connected vehicle. To activate more vehicles for connected services, you must purchase additional add-on licenses. For example, if you purchase 10,000 units of the add-on license, you can mark 10,000 Vehicle records in your org as Connected Services Active. If a vehicle is marked as connected after the start date of a month, the vehicle is considered in calculations for the entire month. |
| Actionable Vehicle Event Orchestration Limit | 300 per month (150 expression-set and 150 flow-based orchestrations) | For each vehicle where connected services are active, you can trigger 150 actionable event orchestrations per month per execution procedure type. You can trigger the Orchestration Inbound Events (POST) API triggered for each connected vehicle 300 times per month to trigger orchestrations for critical events that the telematics provider raises. For example, if 10,000 connected vehicles are active in the org, the total number of event orchestrations allowed is 30,00,000 (10,000*300) per month distributed across expression-set based and flow based. |
| Vehicle Get Status API Limit | 300 per month. | For each vehicle where connected services are active, you can trigger 300 Get Status API calls per month. The Get Status API retrieves the values of key vehicle metrics such as fuel level, odometer reading, latitude, longitude, ignition status, or any other attribute of your choice in real time from the telematics provider, and shows the values on a Vehicle record. Each time the panel is refreshed and loads with new values, 1 call is consumed for a vehicle. For example, if 10,000 connected vehicles are active in the org, the total number of API calls allowed is 30,00,000 (10,000*300) per month. |
| Vehicle Remote Notification API Limit | 150 per month. | For each vehicle where connected services are active, you can trigger 150 Vehicle Remote Notification API calls per month. The Vehicle Remote Actions API sends a remote notification to the human machine interface (HMI) of a connected vehicle to update the driver about subscriptions, upcoming appointments, repair estimates, or other key information. For example, if 10,000 connected vehicles are active in the org, the total number of API calls allowed is 15,00,000 (10,000*150) per month. |
| Vehicle Remote Action API Limit | 150 per month. | For each vehicle where connected services are active, you can trigger 150 Vehicle Remote Actions API calls per month. The Vehicle Remote Actions API gets the current status of all doors for a connected vehicle so users can lock or unlock one or multiple doors in real time. For example, if 10,000 connected vehicles are active in the org, the total number of API calls allowed is 15,00,000 (10,000*300) per month. |
| Vehicle Connected Actions and Events Limit | 750 per month. This is a cumulative count that includes actionable event orchestration inbound calls, Get Status calls, Remote Notification calls, and Remote Action calls. | For each vehicle where connected services are active, you can trigger 750 API calls for a connected vehicle per month in total. The individual limits are still adhered to. For example, if 10,000 connected vehicles are active in the org, the total number of API calls allowed is 75,00,000 per month (10,000*750). |
