Typical Use Cases
AosEdge supports the operation of connected Units across their lifecycle.
The use cases below describe common scenarios for OEMs, Service Providers, Fleet Owners, and Admins. They use current public-facing terminology: Unit, Deployable Item, Deployment Bundle, Verification, Campaign, Fleet, and Unit Set.
Managing connected Units after production
OEMs often need to operate connected products long after they leave production.
AosEdge helps the OEM keep visibility and control over Units in the field. The OEM can organize Units into fleets, monitor their state, manage deployment scope, and support controlled lifecycle changes without physical access to each Unit.
Typical roles involved:
- OEM
- Fleet Owner
- Admin
Related documentation:
Delivering software-defined functionality to Units
Connected products increasingly depend on functionality that evolves over time.
AosEdge provides a controlled way to deliver Deployable Items to Units. A Deployable Item represents managed delivery content that can be installed, operated, monitored, and governed by the platform.
This helps OEMs and Service Providers collaborate while keeping ownership and access boundaries clear.
Typical roles involved:
- OEM
- Service Provider
- Admin
Related documentation:
Grouping related delivery content into Deployment Bundles
Some functionality requires several related pieces of delivery content to be managed together.
AosEdge uses Deployment Bundles to group related Deployable Items into one controlled delivery scope. This helps users plan, verify, and operate related content as a coherent deployment unit.
Typical roles involved:
- OEM
- Service Provider
- Fleet Owner
Related documentation:
Verifying deployment before broad rollout
Large-scale deployment should not start blindly.
AosEdge supports Verification on limited scopes such as selected Units or Unit Sets. This allows users to check behavior before broader rollout.
Verification helps reduce deployment risk, especially when Units differ by hardware, configuration, region, fleet assignment, or operating conditions.
Typical roles involved:
- OEM
- Fleet Owner
- Service Provider
Related documentation:
Running controlled rollout across fleets and Unit Sets
OEMs may need to roll out changes gradually.
AosEdge supports controlled deployment planning through Campaigns. Campaigns help manage rollout scope, order, progress, and operational control across fleets and Unit Sets.
This is useful when changes must be introduced carefully across a large number of Units.
Typical roles involved:
- OEM
- Fleet Owner
- Admin
Related documentation:
Monitoring Unit health and operational state
Units in the field must remain observable.
AosEdge helps users monitor health, connectivity, deployment state, logs, alerts, and resource usage. This allows teams to understand what is happening across the fleet and respond when attention is required.
Typical roles involved:
- OEM
- Fleet Owner
- Service Provider, where access is permitted
- Admin
Related documentation:
Supporting Service Provider delivery into OEM-managed environments
Service Providers may need to deliver functionality into Units they do not own.
AosEdge gives Service Providers a structured path to prepare and manage Deployable Items within OEM-defined governance. This supports collaboration while keeping access, ownership, and operational responsibility separated.
Typical roles involved:
- Service Provider
- OEM
- Admin
Related documentation:
Operating heterogeneous or multi-Node Units
Some Units contain several computing elements.
AosEdge supports Units that may contain one or more Nodes. This allows the platform to work with more complex edge architectures where computing resources are distributed inside the Unit.
Typical roles involved:
- OEM
- Fleet Owner
- Integration engineer
- Admin
Related documentation:
Troubleshooting through reported state, logs, alerts, and monitoring data
When something goes wrong, users need evidence.
AosEdge helps users investigate problems through reported state, logs, alerts, health information, and monitoring data. This reduces the need for physical access and helps teams identify whether the issue is related to deployment, connectivity, resource limits, configuration, or Unit health.
Typical roles involved:
- OEM
- Fleet Owner
- Service Provider, where access is permitted
- Admin
Related documentation:
Supporting long-term product lifecycle management
Connected products may operate for years.
AosEdge supports long-term lifecycle management by providing a consistent model for deployment, verification, monitoring, access control, and operational feedback.
This helps OEMs keep connected Units maintainable after production and throughout field operation.
Typical roles involved:
- OEM
- Fleet Owner
- Service Provider
- Admin
Related documentation: