Reference

Software & Operations Glossary

Clear definitions for the systems, integrations and operating ideas discussed across our work.

Explore the terms

A practical reference for business teams

Each definition starts with the meaning, then links to a relevant service or solution.

Business software: Business software helps an organisation record information, coordinate work and make decisions. It may support one task, such as invoicing, or connect several workflows across a team. The right choice depends on who uses it, what data it handles and how it must fit existing operations. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Custom software: Custom software is planned and built for a particular organisation or workflow. It can fit roles, rules and integrations that general products do not cover, while requiring the organisation to fund ongoing hosting, support and improvements. A discovery process should compare those costs with configuration or off-the-shelf options. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Telematics: Telematics combines communications and vehicle or device data to provide operational visibility. Fleet teams may use it to see location, movement, utilisation or equipment health, depending on the hardware and permissions involved. The data needs clear ownership, retention and access rules to be useful and responsible. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Fleet management software: Fleet management software helps teams coordinate vehicles, drivers, trips and maintenance information. A system can bring location events, schedules and operational reports into one view. Useful capabilities depend on the operator’s fleet, installed devices and dispatch process. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Geofence: A geofence is a virtual boundary around a physical place. When a configured device enters or leaves that boundary, software can record an event or notify permitted users. Teams should tune boundaries to real operating conditions and avoid treating a location signal as proof of a person’s actions. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Device compliance: Device compliance is the work of tracking whether equipment meets applicable registration, inspection, licence or renewal requirements. A central register with owners, evidence and reminders can reduce missed follow-ups. The requirements differ by device and regulator, so organisations must confirm the rules that apply to them. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Inventory management: Inventory management records what stock or equipment an organisation holds, where it is, and how it moves. Good processes make updates traceable and reports timely. Software can support counts, transfers, reorder signals and audit history when data entry responsibilities are clear. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Operational dashboard: An operational dashboard presents a focused view of current work and the measures a team needs to act. It should surface meaningful exceptions and trends, identify where data came from and let users move from a summary to its underlying records. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
System integration: System integration connects applications or devices so that selected data and events can move between them. Integrations may use APIs, files or messaging. Before building one, teams should define ownership, error handling, security boundaries and how changes on either side will be managed. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
API: An application programming interface (API) defines how software can request or exchange information with another system. A dependable API has clear authentication, validation, error responses, limits and versioning. Integrations should expose only the data and actions required for the task. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Cloud hosting: Cloud hosting runs an application on computing infrastructure provided over a network. It can simplify capacity changes and managed backups, but still requires careful configuration, access control, monitoring, cost management and recovery planning. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Software as a service: Software as a service (SaaS) is software accessed over the internet, usually under a subscription. The provider operates the application, while the customer should review data export, access, uptime, support and exit arrangements before depending on it for critical work. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Progressive web app: A progressive web app is a web application that can offer app-like features through a supported browser, such as installation, cached content or notifications. Available capabilities vary by device and browser, so the experience should be tested on the phones and networks a team actually uses. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Customer relationship management: Customer relationship management (CRM) software organises customer profiles, interactions, opportunities and follow-up work. A CRM is most effective when teams agree who maintains records, which stages mean what and how customer data is protected. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Business process automation: Business process automation uses software rules to handle repeatable steps such as routing a request, sending a reminder or recording a status change. Teams should retain human review for exceptions and make failures visible rather than silently dropping work. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
E-commerce platform: An e-commerce platform supports online product discovery, ordering and payment. Business operations also depend on inventory accuracy, fulfilment, customer communication, refunds and reporting. Integration and ownership across those steps matter as much as storefront design. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
M-Pesa integration: M-Pesa integration connects a business application to a supported Safaricom payment workflow. The implementation needs merchant credentials, secure callback handling, reconciliation and clear treatment of delayed or reversed transactions. Confirm the required Daraja products and commercial account setup before planning delivery. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Data migration: Data migration moves records from one system or format into another. A safe migration maps fields, checks duplicates and invalid values, protects sensitive files and rehearses rollback. Owners should approve the source of truth and reconcile totals before cutover. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Software maintenance: Software maintenance keeps an application dependable after launch through updates, fixes, monitoring and compatibility work. A support plan should define response expectations, responsibilities, backups, security updates and how enhancement requests are prioritised. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.
Last-mile delivery: Last-mile delivery is the final movement of goods from a local hub or distribution point to the receiving customer. Visibility across dispatch, routes, delivery evidence and exceptions helps teams coordinate changes and communicate realistic status. AxoraOrbit helps teams assess the workflow and choose a proportionate system approach. Before selecting an approach, identify who owns the information, who acts on it, what can go wrong when it is late or missing, and what the team will do if a device, service or connection is unavailable. A short workflow review can surface these dependencies early.

Need help?

Software & Operations Glossary

A practical reference for business teams