SOFTWARE PLATFORM
Choose software by the work it must support.
Compare software access for one return point, a multi-site RVM fleet or a network with existing systems. Scope alerts, collection, service and integration by role.
SOFTWARE SCOPE
Match access to sites, people and decisions.
Start with the actions your team must take, then define users, integrations and support alongside the equipment proposal.
Sites and people
Define where the software is used and who needs access.
Actions and records
Choose the alerts, tasks and reports the operating team will own.
Interfaces and support
Specify customer systems, implementation and service commitments.
SOFTWARE SUBSCRIPTIONS
Three operating scopes to discuss.
Compare the workflow each scope is designed to support. A proposal identifies the included users, sites, interfaces, onboarding and service terms.
Essential
For a focused site team. Review device status and core exceptions, keep a basic activity record and export the agreed data. Define who checks the station and who receives alerts.
Operations
For an operator coordinating several sites. Assign collection and service work, review exceptions by location and give people role-based access to the records they own.
Enterprise
For a network with multiple parties or an existing platform. Define organization boundaries, the event contract, reconciliation, data ownership and an implementation acceptance plan.
A software subscription should match how many sites a team runs, who acts on exceptions, and which existing systems need data. Equipment and software are quoted as separate scopes so each project has a clear operating model.
What to compare in a software proposal
Ask which equipment signals are included, how quickly they reach the operator view, how collection and service work is assigned, which records can be exported and which team maintains the user list. For an integration, add the receiving system, event vocabulary, authentication, retry behavior and acceptance tests. A tier name alone does not answer those questions.
Equipment, software access, implementation, interfaces and ongoing service are separate commercial lines. Send the number of sites, operator roles and systems in scope for a relevant walkthrough and written proposal. A single equipment site can begin without a full network subscription.
Turn your site brief into a configuration
Share the location, container stream, operating team and systems already in place.