Vehicle-list capacity depends on accounts, devices and synchronisation, with size, revocation and recovery tested for local copies.
Capacity needs to be established at account, tenant and device level, including offline copies. A central database limit does not explain how many entries each lane can use or how changes reach it after a failed update.
The useful demonstration is at the proposed deployment size, with additions, revocations and recovery. Inactive entries also need a review policy so a list does not grow simply because nobody removes old associations.
Authorized lists began as registers or small controller tables. Connected deployments can maintain a larger central register while sending subsets to devices. Storage capacity and operational capacity therefore describe different parts of the system.
The cloud account, local cache and synchronisation service can have different ceilings and update behavior. Knowing that a record exists centrally does not establish that the latest version is available at every site.
Capacity assessment matters when many holders, vehicles or sites share a deployment. For a small property, a large permanent list may be unnecessary. Time-limited permits and site-specific subsets can provide a more appropriate way to structure the same entitlements.
Another credential may also suit some users. Former staff or residents should not remain indefinitely associated with vehicles simply to avoid changing a list; expiry and review are part of managing its contents.
Count active holders, vehicles per holder, temporary entries and expected changes separately. A central list of 20,000 records does not demonstrate the same local-device capacity. This is an illustration, not an Aero Ranger capacity statement.
Establish whether archives consume quota and whether every lane receives the full register. Test initial load, a small change, offline revocation and a partially applied update. Version and last successful synchronisation should distinguish configured entitlement from a stale site copy.
Aero Ranger CORE documents permit accounts and configurable cap rules for structuring entitlements and administrative limits. SolarLink separately describes local lists and later synchronisation. These address different parts of the capacity question and need to be assessed together where both are proposed.
Actual account and device ceilings, field limits, update throughput and offline revocation behavior need confirmation. Published unlimited users or permit categories do not establish unlimited vehicle-list capacity.
Aero Ranger: Permits; Aero Ranger: permit cap rules; Aero Ranger: SolarLink edge processing
Sources were reviewed on the publication date. Check the linked material for current details.
