\n\n## What is Fleet-Ops?\n\nFleet-Ops is the core logistics and fleet management extension for the [Fleetbase](https://www.fleetbase.io) platform. It gives operations teams a dispatch console for managing orders, drivers, vehicles, fleets, service areas, live maps, route execution, analytics, maintenance, and connected telematics.\n\nFleet-Ops ships as two packages:\n\n| Package | Purpose |\n| --- | --- |\n| `@fleetbase/fleetops-engine` | Ember Engine/Add-on that powers the Fleet-Ops console UI. |\n| `fleetbase/fleetops-api` | Laravel/PHP package that provides the Fleet-Ops API, models, jobs, events, and integrations. |\n\nFleet-Ops is included with Fleetbase Cloud and self-hosted Fleetbase installations. For product concepts, workflows, and setup guides, start with the [Fleet-Ops documentation](https://www.fleetbase.io/docs/fleet-ops).\n\n## Features\n\n### Operations\n\n- Create, import, schedule, dispatch, start, cancel, and complete delivery orders.\n- Manage multi-waypoint routes, payloads, entities, labels, order metadata, notes, comments, files, and proofs.\n- Track live order progress with ETAs, route overlays, driver pings, activity timelines, and configurable status flows.\n- Configure custom order types, activity flows, entity fields, proof requirements, and service-rate rules.\n- Run orchestration workflows for order allocation, driver assignment, vehicle capacity, and route sequencing.\n- Plan work with the scheduler, fleet schedule, service quotes, routes, manifests, and manifest stops.\n\n### Live Map\n\n- View live drivers, vehicles, active orders, routes, places, service areas, zones, and geofences.\n- Filter and inspect operational layers with Fleet-Ops map controls and drawer panels.\n- Support Leaflet-based and Google-based map experiences through Fleetbase map settings.\n- Capture positions, replay movement, track vehicles and drivers, and surface geofence events.\n\n### Fleet Management\n\n- Manage drivers, vehicles, fleets, places, contacts, customers, vendors, and integrated vendors.\n- Assign drivers and vehicles to fleets, vendors, and orders.\n- Track driver schedules, availability, positions, active shifts, and hours-of-service status.\n- Track vehicle status, devices, positions, equipment, schedules, work orders, and maintenance history.\n- Manage issues, fuel reports, imports, exports, bulk actions, and custom resource fields.\n\n### Maintenance\n\n- Define preventive maintenance schedules and calendar feeds.\n- Manage work orders, maintenance records, line items, equipment, parts, and warranties.\n- Send work orders, trigger schedule runs, pause and resume schedules, and review maintenance history.\n\n### Connectivity\n\n- Connect telematics providers, devices, sensors, events, and tracking data.\n- Discover and link telematics devices, test provider credentials, and receive telematics webhooks.\n- Use Fleet-Ops tracking providers for calculated, OSRM, and Google Routes-backed route intelligence.\n\n### Analytics and Dashboards\n\n- Use Fleet-Ops KPI widgets for earnings, average order value, distance, active orders, online drivers, and open issues.\n- Review analytics for operations pulse, live fleet, revenue trends, order status volume, on-time delivery, top drivers, fuel efficiency, issues, maintenance, and geofence violations.\n- Create and view reports from the Fleet-Ops analytics workspace.\n\n### Settings and Extensions\n\n- Configure Navigator app onboarding, routing, tracking, map providers, notifications, scheduling, payments, orchestrator settings, custom fields, and avatars.\n- Expose Fleet-Ops order tracking on the Fleetbase login surface.\n- Integrate Fleet-Ops entities into other Fleetbase extensions through registered components and virtual detail tabs.\n\n## Architecture\n\nFleet-Ops follows the Fleetbase extension architecture: an Ember Engine for the console interface and a Laravel package for API and backend capabilities.\n\n```text\nfleetops/\n+-- addon/ # Ember Engine source: routes, controllers, components, services, templates\n+-- app/ # Ember app re-exports and integration points\n+-- assets/ # Frontend assets bundled with the engine\n+-- translations/ # Fleet-Ops locale files\n+-- server/\n| +-- config/ # Fleet-Ops API configuration\n| +-- migrations/ # Database migrations\n| +-- resources/ # Backend views and resources\n| +-- seeders/ # Seed data\n| +-- src/ # Controllers, models, jobs, events, support services, providers\n| +-- tests/ # Backend test suite\n+-- tests/ # Ember test suite\n+-- package.json # Frontend package metadata and scripts\n+-- composer.json # Backend package metadata and scripts\n```\n\nCore frontend dependencies include Ember Octane, Ember Engines, Fleetbase Ember Core, Fleetbase UI, Fleet-Ops Data, Leaflet, Leaflet Draw, Turf, JointJS, and Stripe Connect. Core backend capabilities are provided by Laravel, Fleetbase Core API, Fleet-Ops models/controllers, orchestration engines, tracking providers, analytics, notifications, jobs, and telematics integrations.\n\n## Getting Started\n\nFleet-Ops comes pre-installed with Fleetbase Cloud and standard self-hosted Fleetbase installations. If you are setting up the Fleetbase platform itself, use the Fleetbase documentation:\n\n- [Fleet-Ops documentation](https://www.fleetbase.io/docs/fleet-ops)\n- [Fleetbase documentation](https://www.fleetbase.io/docs)\n- [Fleetbase console](https://console.fleetbase.io)\n\nWhen developing Fleet-Ops from source, install both frontend and backend dependencies:\n\n```bash\npnpm install\ncomposer install\n```\n\n### Link Fleet-Ops into Fleetbase\n\nWhen working from the Fleetbase monorepo, use the Fleetbase package linker to connect this local package to the running Console and API applications. From the Fleetbase repository root:\n\n```bash\nflb-package-linker enable fleetops\nflb-package-linker install fleetops\n```\n\nThis links the local Fleet-Ops Ember engine and Laravel package so Console and API use your source checkout instead of the published packages. See the [Fleetbase development setup guide](https://www.fleetbase.io/docs/platform/quickstart/development-setup) for the full package-linking workflow, Docker setup, Octane reload notes, and frontend hot-reload options.\n\n### Link Fleet-Ops Data\n\nFleet-Ops also depends on the shared `@fleetbase/fleetops-data` package. That package contains Fleet-Ops Ember Data models, adapters, and serializers, and can be reused by other Fleetbase modules that need to read or write Fleet-Ops resources without duplicating data-layer definitions.\n\nIf you are changing shared Fleet-Ops data models or consuming them from another extension, link `fleetops-data` through the root Console workspace:\n\n```bash\nflb-package-linker enable-shared fleetops-data\nflb-package-linker install\n```\n\nFor broader Fleet-Ops frontend work, you may also link the common shared Ember packages used by Fleetbase:\n\n```bash\nflb-package-linker enable fleetops --shared ember-core ember-ui fleetops-data\nflb-package-linker install fleetops\n```\n\n## Development\n\nStart the Ember Engine in development mode:\n\n```bash\npnpm start\n```\n\nBuild the production frontend bundle:\n\n```bash\npnpm build\n```\n\nRun frontend linting:\n\n```bash\npnpm lint\n```\n\nRun backend linting:\n\n```bash\ncomposer test:lint\n```\n\n## Testing\n\nRun the Ember/QUnit test suite:\n\n```bash\npnpm test:ember\n```\n\nRun the full frontend check suite:\n\n```bash\npnpm test\n```\n\nRun the backend test suite:\n\n```bash\ncomposer test\n```\n\nRun backend checks individually:\n\n```bash\ncomposer test:lint\ncomposer test:types\ncomposer test:unit\n```\n\n## Documentation\n\n- [Fleet-Ops docs](https://www.fleetbase.io/docs/fleet-ops)\n- [Fleet-Ops quickstart](https://www.fleetbase.io/docs/fleet-ops/getting-started/quickstart)\n- [Fleet-Ops core concepts](https://www.fleetbase.io/docs/fleet-ops/getting-started/core-concepts)\n- [Navigator app setup](https://www.fleetbase.io/docs/fleet-ops/getting-started/navigator-app-setup)\n- [Fleetbase docs](https://www.fleetbase.io/docs)\n\n## Contributing\n\nContributions are welcome. Please read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.\n\nUseful project files:\n\n- [package.json](package.json) for frontend scripts and package metadata.\n- [composer.json](composer.json) for backend scripts and package metadata.\n- [extension.json](extension.json) for Fleetbase extension metadata.\n\n## License\n\nFleet-Ops is open-source software licensed under the [GNU Affero General Public License v3.0 or later](LICENSE.md).\n","readmeFilename":"README.md"}
![\"Fleetbase\"](\"https://flb-assets.s3.ap-southeast-1.amazonaws.com/static/fleetbase-logo-svg.svg\"){kind=logo}
\n![\"Repository\"](\"https://img.shields.io/badge/repo-fleetbase%2Ffleetops-111827?style=flat-square\"){kind=icon}
![\"License:](\"https://img.shields.io/badge/license-AGPL--3.0--or--later-blue?style=flat-square\"){kind=icon}
![\"Coverage\"](\"https://codecov.io/gh/fleetbase/fleetops/branch/main/graph/badge.svg\"){kind=icon}
\n \n \n ![\"NPM](\"https://img.shields.io/badge/npm-%40fleetbase%2Ffleetops--engine-CB3837?style=flat-square\"){kind=icon}
![\"Packagist](\"https://img.shields.io/badge/packagist-fleetbase%2Ffleetops--api-F28D1A?style=flat-square\"){kind=icon}
![\"Fleet-Ops](\"https://img.shields.io/badge/docs-fleet--ops-0EA5E9?style=flat-square\"){kind=icon}
![\"Node](\"https://img.shields.io/badge/node-%3E%3D18-339933?style=flat-square\"){kind=icon}
![\"PHP](\"https://img.shields.io/badge/php-%5E8.0-777BB4?style=flat-square\"){kind=icon}
![\"Fleet-Ops](\"https://www.fleetbase.io/images/screenshots/fleet-ops/fleet-ops-multi-waypoint-order.webp\")
\n