Frequently asked questions

HiVAM is a connected transport operations platform for full-truck-load (FTL), part-load (PTL) and hybrid businesses. It brings booking, dispatch, fleet, warehouses, people, finance, tracking and the driver app into one workspace. The feature pages distinguish platform tools, API capabilities and planned work.

HiVAM connects transport bookings and package custody with owned or hired departures, delivery evidence, billing and partner settlement. Fleet readiness, warehouses, payroll, analytics, tracking and Ask AI support the same operation. Availability depends on the plan, role and deployment; API-only workflows are labeled on the feature pages.

HiVAM stands for High Volume Asset Management. The name reflects the platform's core mission: enabling businesses to manage large fleets and high-volume logistics operations with intelligence, visibility, and control — regardless of scale.

HiVAM is pronounced "High-VAM" (/haɪ.væm/). The "Hi" is spoken like the English word "high" or "hi" (/haɪ/), and "VAM" rhymes with "jam" or "slam" (/væm/). It is not pronounced "Hivam," "Shivam," "Hee-vam," "Hai-vaam," or "Hiv-um." Common misspellings include Hivam, Hivaam, Hivum, Hyvam, Hiwam, and HiiVAM — all of which refer to HiVAM.

HiVAM is designed for Indian road transport businesses running FTL, PTL or both, including fleets that combine owned vehicles with hired trucks and partner carriers. A small operator can start with one tracked truck; larger businesses can use broader warehouse, finance, workforce and integration capabilities according to their plan.

HiVAM builds transport software with an AI assistance layer. Ask AI helps users investigate permitted operational information and review proposed actions. Rule-based planning and operational recommendations are distinct from validated predictive models and broader autonomous execution, which remain planned.

GPS tracking is one component of HiVAM, but the platform goes far beyond simple location pins on a map. HiVAM is a full logistics operating system that combines tracking with dispatch, analytics, fleet health monitoring, driver management, and operational intelligence. Think of it as GPS tracking plus everything else a fleet manager needs in one place.

Traditional fleet management tools often solve one problem — tracking, or dispatch, or analytics — in isolation. HiVAM unifies all of these into a single platform with a modern interface, real-time data pipelines, and intelligence built in from the ground up. Instead of juggling five different tools and exporting data between them, fleet teams get one dashboard with everything connected.

Most logistics teams drown in data but starve for insights. They have GPS pings, trip logs, fuel records, and driver reports scattered across systems — but no way to connect the dots. HiVAM was built to solve this: a platform where data flows in automatically, gets processed intelligently, and surfaces the insights that actually matter for daily operations.

HiVAM serves logistics and transportation, third-party logistics (3PL), e-commerce delivery, courier and last-mile services, cold chain logistics, construction fleet management, waste management, field services, and any industry that operates vehicle fleets. The modular design means different industries can activate the modules most relevant to their operations.

HiVAM is headquartered in India and currently optimised for the Indian logistics market. The platform architecture is designed for global deployment, and international expansion is on the roadmap. Businesses outside India can reach out to discuss availability and timelines.

HiVAM's vision is to build the world's most intelligent and autonomous operating system for High Volume Asset Management — beginning with logistics and seamlessly unifying hardware, software, and AI to empower every business, regardless of size or geography.

HiVAM's mission is to empower every business — from the smallest fleet operator to the largest global enterprise — with an intelligent and autonomous operating system that transforms how high-volume assets are managed, enabling greater efficiency, visibility, and decision-making at every scale.

HiVAM Technologies Private Limited was incorporated in 2026 under the laws of India (CIN: U62099KA2026PTC222227). The company is headquartered in Karnataka, India.

HiVAM is a young, early-stage company. Team size and structure aren't published figures at this stage — the product and its capabilities are what this site describes, not headcount. Contact admin@hivam.in for anything specific.

Funding details are not publicly disclosed at this stage. HiVAM Technologies Private Limited is an incorporated Indian company (CIN on the About page); commercial and investment specifics beyond that are not shared here.

HiVAM Technologies Private Limited is registered in Karnataka, India, and operates for fleets across India with the architecture built for global deployment. See the About page for the registered entity details.

HiVAM works with GPS hardware vendors as part of its device options and is open to reseller and integration conversations. There is no published partner directory at this stage — reach out to admin@hivam.in to discuss.

Building fleet software in-house means owning the GPS integration, the data pipeline, the dispatch and finance workflows, and the ongoing maintenance of all of it indefinitely — a multi-year effort even for a well-resourced team. HiVAM is that system already built, priced per vehicle rather than as an engineering project.

Calculate commercial charges by customer, lane, goods, packing and vehicle. Preserve the accepted quote and its calculation basis when rate masters change. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Keep who pays and when separate from physical delivery. Invoice eligible delivered quantities, hand over collections and prevent the same quantity from being billed twice. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Tie hire, crossing, commission, receipts and settlement to their source documents. Reconcile the operational statement with the subledger and general ledger. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Choose effective-dated tax treatment and retain the policy, place of supply and charge-level rate on the document. Historical documents keep their original calculation evidence. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Evaluate customer credit exposure and required POD before billing or accepting work. A blocked operation explains the obligation and the authorized next action. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Combine HiVAM and customer trackers. Dated usage periods capture activation, replacement and category changes; payments, refunds and disputes retain their own reconciliation history. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Receive and unload the actual package quantity, retain shortages and damage, and track the branch responsible for every outstanding package. Transit custody is separate from owned SKU stock. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Reserve available stock, group picking tasks, receive transfers partially and reconcile an approved count. Movements explain each change to stock instead of overwriting the balance. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Connect capacity, operational arrivals and storage age to reviewable charge drafts. A geofence visit alone is not proof of receipt or permission to post a charge. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

HiVAM covers eight connected areas: operations, fleet, people, warehouses, finance, analytics, tracking and the driver app. Newer workflows include branch and party masters, PTL quantity custody, hired vehicles, POD review, transport billing, partner settlement and guided setup. Plan rights, role permissions and configured modules all affect access; hiding a module does not change the subscription bill.

The HiVAM dashboard is a modern, web-based interface accessible from any browser. It features a real-time fleet map, vehicle status panels, trip timelines, analytics charts, and dispatch boards — all in one view. The interface supports both light and dark modes and is designed for all-day use by fleet operations teams.

HiVAM has a driver Progressive Web App (PWA) for assigned trips, inspections, delivery evidence, documents and help. It can be installed from a supported browser; it is not a promise of a native app-store application. Supported check-ins and checklist operations can queue offline, while evidence files require a working upload connection. The main dashboard is intended for office work on desktop or tablet.

The office dashboard needs a connection for current operational data. The driver PWA can queue supported check-ins and checklist operations and replay them after reconnection. Photo and signature uploads require connectivity. GPS device buffering depends on the specific hardware and configuration; a network outage is not a guarantee that every reading can be recovered.

HiVAM can display incoming telemetry and operational updates while the connection is active. Freshness depends on the device reporting interval, provider integration and network. Check the last-reported timestamp: an old location is not evidence of a current vehicle position. A published latency guarantee is not provided here.

HiVAM is modular by design. Within the modules your plan tier includes, you can choose which ones to switch on, configure alerts and thresholds, set up custom geofences, and tailor the analytics views to your KPIs. Enterprise customers can discuss deeper customisation with the HiVAM team.

The public website and office dashboard provide English, Hindi, Gujarati, Marathi, Punjabi, Tamil, Telugu and Kannada language options. Coverage varies by screen and the driver PWA has its own language surface. The detailed FAQ corpus is currently English. Confirm the exact driver-language requirements during onboarding rather than assuming every surface has identical translation coverage.

The office dashboard is designed primarily for desktop and tablet browsers. Some information can be checked on a phone, but dense dispatch and administration work should use a larger screen. The driver PWA is the phone-focused experience. Confirm required browser versions and device permissions during your rollout.

Features and fixes are released as the product develops. Review your deployed version and release information with the team; repository code or a roadmap description alone does not mean a feature has already been enabled in your account.

Yes — that is one of HiVAM's primary goals. Many logistics teams still manage fleets through Excel sheets, WhatsApp groups, and paper logs. HiVAM replaces all of that with structured, real-time digital records: live tracking, automated trip logs, driver assignments, and analytics that update themselves.

HiVAM aims to eliminate the need for WhatsApp-based fleet coordination by providing structured dispatch workflows, real-time status updates, and a central command view. Instead of chasing drivers for location updates via WhatsApp, fleet managers can see everything live on the dashboard.

Yes. HiVAM supports team-based access with role-based permissions. Fleet managers, dispatchers, operations heads, and administrators can all access the same account with appropriate access levels. This ensures everyone sees the data relevant to their role.

HiVAM is built for commercial vehicle fleets — trucks, trailers, tempos, vans, and similar goods-carrying vehicles are the primary use case the platform (dispatch, LRs, freight billing) is designed around. Non-commercial or unusual vehicle types can be discussed directly with the team.

Yes. Invoices, lorry receipts and other generated documents are designed to be viewed and printed directly from the dashboard, for situations where a physical or PDF copy is still needed alongside the digital record.

HiVAM's notification system delivers alerts within the dashboard. The specific external channels (email, SMS, push) available to you depend on your plan and configuration — check current options in your account settings or ask the team.

Yes. The HiVAM dashboard supports both light and dark modes, so it's comfortable for a control-room screen running all day as well as a quick daytime check.

Yes, in the areas where it matters most at scale: bulk employee import and bulk SKU/carrier import are both part of the inventory. For vehicle onboarding at volume, contact the team to discuss the best import path for your fleet size.

The audit log records material account actions — who changed what, and when. Specific retention periods scale with your plan; contact the team for the exact retention window that applies to your subscription.

HiVAM generates GST-compliant invoicing documents as part of the finance module. Whether e-invoice/IRN generation specifically applies to your business depends on your turnover threshold under GST rules — confirm your specific compliance requirement with the team.

Create a transport booking with the parties, payer and payment terms, locations, goods, packages, weight and handling details. The LR identifies that consignment; it may be allocated across several departures in PTL work. Check the booking and print pack before sharing it. A single trip is not necessarily the whole consignment.

Select the trip or departure, inspect available vehicles and drivers, and check readiness and conflicting assignments before saving. Hired movements use their own carrier and vehicle details. Review any blocked assignment reason; an availability list is not permission to ignore a critical hold.

Review eligible freight quantities, payer, payment terms, rates, POD requirements and tax treatment before creating an invoice. A completed trip does not make every package billable: partial delivery, holds and already-invoiced quantities matter. Invoicing starts at Growth; tariffs and accepted quote calculations also have API workflows.

Geofences are drawn as a boundary on the live map around a location — a warehouse, a customer site, a restricted zone — and the platform raises an alert the moment a vehicle crosses that boundary, without anyone watching the map for it.

A vehicle is added once to the asset registry with the details compliance and assignment depend on — registration, documents, device — and from that point it's available to dispatch, maintenance and every other module that references it.

New logins are added from the users screen and assigned a role — dispatcher, fleet admin, finance, or a custom role built permission by permission on plans that support custom roles — which sets what they can view, edit or approve from the moment they accept the invite.

On Scale and above, review the workforce period, attendance, leave, advances and approved payroll inputs before calculating and approving a pay run. Trip allowances and duty integration also have API capabilities. A trip completion is not authorization to release wages or transfer money.

Procurement raises a purchase order against a registered vendor and tracks it from pending through to approved inside the same account — no separate spreadsheet to keep in sync with what warehouse and finance are seeing.

The export manager pulls a dataset — trip records, invoices, whichever you need — out as a file for use in a spreadsheet or another system whenever you need it, which is also how your data stays exportable if you ever decide to leave (see the data-deletion-on-cancel FAQ).

Preventive maintenance is set by distance or time against a specific vehicle, so a service is flagged before something actually breaks rather than after — the maintenance calendar shows the coming week's load at a glance so a bottleneck is visible before it happens.

Open the shipment or booking and review its current status, quantity movements and timeline. A split consignment can have several departures and outstanding packages after one trip is delivered. Customer access uses scoped APIs on your own pages; a hosted customer portal is not promised.

Every compliance document — RC, insurance, permit, fitness certificate — carries its own countdown to expiry, and the platform surfaces what's expiring inside 30 days automatically rather than requiring anyone to check a filing cabinet or spreadsheet on a schedule.

Submit the supported request with its source record and reason. Configured rules determine whether it qualifies for automatic approval or needs a reviewer or approval chain. An approval must remain tied to the current request, permissions and limits; it is not a general authorization for unrelated edits.

HiVAM receives live location data from GPS devices installed in your vehicles. This data flows through real-time pipelines into the platform, where it is processed, enriched, and displayed on an interactive map. You can see every vehicle's current location, speed, heading, and status at a glance.

The reporting interval depends on hardware and provider configuration. HiVAM surfaces incoming telemetry, but a currently displayed location can be stale. Check the last-reported time and agreed connection behavior before treating it as live.

Yes. The HiVAM fleet map displays all your vehicles simultaneously with colour-coded status indicators (moving, idle, stopped, offline). You can filter by vehicle group, status, driver, or route — and click any vehicle for detailed information.

Yes. HiVAM stores complete trip history with route playback, stop durations, speed profiles, and distance covered. You can replay any past trip on the map and review detailed timeline data for compliance, analysis, or dispute resolution.

Geofences define locations for entry, exit and dwell context. Supported alerts can draw attention to an arrival or deviation. A geofence event is location evidence; it does not confirm received package quantity, accepted delivery or an approved charge.

Yes. HiVAM supports geofence-based alerts. You can configure notifications for entry, exit, or dwell time within any geofenced area. Alerts help fleet managers monitor deliveries, track warehouse arrivals, and detect unauthorised detours.

Yes. You can set speed thresholds per vehicle or fleet-wide. When a vehicle exceeds the defined limit, the platform logs the event and can trigger an alert. Speed monitoring is critical for driver safety, fuel efficiency, and regulatory compliance.

Absolutely. The HiVAM dashboard provides a real-time status breakdown showing how many vehicles are currently moving, idle, stopped, or offline. This bird's-eye view helps fleet managers identify underutilised assets and potential issues instantly.

Accuracy depends on the device, satellite reception, installation and environment. Check the raw reading and its timestamp. A displayed pin is not a guaranteed physical location or proof of delivery, and map matching should not be assumed unless the configured integration provides it.

HiVAM is designed primarily for vehicle fleet management, but the underlying architecture supports tracking any GPS-enabled asset — trailers, containers, equipment, or high-value cargo. Contact the HiVAM team to discuss non-vehicle asset tracking requirements.

Yes. By combining geofencing, time-based rules, and trip analysis, HiVAM can flag vehicle movements outside permitted hours, routes, or zones. This helps prevent misuse, theft, and policy violations without requiring constant manual monitoring.

The platform is designed for small and larger fleets, and pricing supports a single tracked truck. The fleet register is separate from chargeable connected-tracker usage. Performance and throughput should be assessed for your data volume and deployment rather than assumed to be unaffected at every scale.

HiVAM's asset registry supports tracking vehicles and assets as distinct entries. Whether a trailer needs its own device and its own tracked identity, separate from the tractor pulling it, is a hardware and configuration question best discussed with the team for your specific combination.

Geofences let you draw a boundary around a location such as a warehouse or customer site. Supported shapes depend on the current version of the map tooling in the dashboard — check the geofences screen for the shapes currently available.

Route deviation is one of the exception types HiVAM surfaces automatically when a planned route exists for a trip. Threshold configuration options are set within the platform — check current settings in the dispatch/exceptions configuration.

In general fleet-tracking terms, "idle" typically means the engine is running but the vehicle isn't moving, while "stopped" means the vehicle is stationary with the engine off — the exact distinction HiVAM's dashboard applies depends on what the connected hardware reports (ignition status vs. pure motion).

HiVAM works with a range of GPS hardware options. You can use devices provided by HiVAM, bring your own compatible GPS trackers, or use a combination. The platform is designed to be hardware-flexible rather than locking you into a single vendor.

HiVAM supports standard GPS tracking protocols and can integrate with most commercial fleet GPS devices. For specific compatibility questions, contact the HiVAM team with your device model and protocol information.

Installation depends on the device type. Plug-and-play OBD devices can be self-installed in minutes. Hardwired GPS trackers typically require a technician for professional installation. HiVAM can assist with installation guidance or recommend certified installers.

Yes. HiVAM's architecture supports data ingestion from various IoT sensors — temperature sensors for cold chain monitoring, fuel level sensors, door open/close sensors, and more. The range of supported sensors continues to expand with each platform release.

Most GPS tracking devices require cellular connectivity (via SIM card or embedded eSIM) to transmit location data to the platform. The data usage is minimal — typically a few megabytes per month per device. HiVAM can advise on connectivity options suitable for your fleet.

Hardwired GPS devices draw minimal power from the vehicle battery — negligible compared to the vehicle's normal electrical consumption. Battery-powered portable trackers have their own rechargeable batteries and do not affect the vehicle at all.

Dashcam integration is on HiVAM's product roadmap. The planned capability will allow fleet managers to correlate video footage with trip data, location, and driver events for enhanced safety and compliance monitoring.

An OBD (On-Board Diagnostics) device plugs into a vehicle's diagnostic port to read engine data — including speed, RPM, fuel consumption, and fault codes. HiVAM supports OBD device data, providing deeper vehicle health insights alongside location tracking.

Temperature monitoring through IoT sensors is supported by HiVAM's data ingestion architecture. Cold chain logistics operators can track temperature alongside location to ensure cargo integrity throughout the delivery journey.

Fuel monitoring depends on the installed sensor or provider feed. Supported fuel imports and receipts can be used as operational evidence even when a live fuel-level sensor is absent. Confirm the exact hardware fields and update frequency; do not assume every tracker reports fuel.

Hardware pricing and the deposit/trial mechanics are detailed on the Pricing page — devices are loaned during the one-month free trial against a refundable deposit, and can be owned outright at cost with no markup on the Own HiVAM Hardware plan. See /pricing for exact figures.

Hardware warranty terms depend on the specific device and vendor. Ask the team for the warranty documentation relevant to the device you're installing.

A plug-and-play OBD device typically installs in minutes. A hardwired tracker generally needs a technician and can take longer per vehicle. Total rollout time across a fleet depends on vehicle count and whether installation happens in one location or is spread across depots.

Device connectivity is monitored — the fleet dashboard shows which devices are reporting and which have gone offline. Tamper-specific detection depends on the capabilities of the specific hardware installed.

Panic-button support depends on the specific hardware model installed — some commercial GPS trackers include one, others don't. Ask the team which device options include this feature if it's a requirement for your fleet.

AIS-140 is an Indian regulatory standard for vehicle location tracking devices, mandated for certain categories of commercial and public-service vehicles. Whether it applies to your fleet depends on vehicle category and state rules — confirm your specific compliance requirement with a regulatory advisor, and discuss device compatibility with the HiVAM team.

AI fleet management is the use of intelligent assistance to interpret operational information and support decisions. In HiVAM, Ask AI and reviewable proposals are current surfaces; data-trained predictions and unrestricted autonomous interventions must be validated before they are described as released.

The current depot planner provides reviewable load proposals and exclusions. Staff can inspect a proposal before committing it; a saved plan does not silently dispatch freight. Broader multi-stage optimization across shifts, skills and connection windows remains planned.

Operational exceptions and rule-based risk checks can help staff find work needing attention. Ask AI can help investigate permitted records. This is different from a validated model predicting every failure in advance; predictive models remain on the roadmap.

Predictive delay detection is being developed as part of HiVAM's intelligence roadmap. By combining historical trip data, real-time traffic, weather conditions, and current fleet status, the system aims to flag at-risk deliveries before the delay actually occurs — enabling proactive customer communication and rescheduling.

Idle-time records and analytics can help a manager identify vehicles or locations needing attention. The team still needs to decide and verify a scheduling, routing or coaching change. HiVAM does not promise a particular saving or that AI will automatically remove idle time.

Improving fleet utilisation is one of the highest-impact applications of intelligence. By analysing which vehicles are underused, which routes could be consolidated, and when demand peaks occur, HiVAM helps fleet managers get more output from the same number of vehicles — reducing the need to add assets.

AI helps logistics managers by converting overwhelming amounts of operational data into actionable decisions. Instead of manually reviewing trip logs and spreadsheets, managers get automated anomaly alerts, performance summaries, and recommendations — freeing them to focus on strategy rather than data crunching.

AI reduces logistics costs through multiple levers: optimising routes to reduce fuel consumption, minimising idle time, improving fleet utilisation so fewer vehicles do more work, predicting maintenance to avoid expensive breakdowns, and identifying operational inefficiencies. Even small improvements across a large fleet compound into significant cost savings.

Predictive maintenance capabilities are under development. By analysing vehicle telemetry data — engine hours, mileage patterns, sensor readings — HiVAM aims to predict when a vehicle is likely to need maintenance, allowing fleet managers to schedule service proactively rather than reacting to breakdowns on the road.

Ask AI is intended to operate within the user's organization, role, facility and feature permissions. See the Privacy Policy for how information is processed and shared with service providers. Do not infer that operational data is used to train models, anonymised for every use, or covered by an independent compliance certification merely because AI is available.

AI doesn't replace fleet managers — it amplifies them. Manual management works at small scale but becomes impossible when tracking hundreds of data points across dozens of vehicles. AI processes this volume instantly, catches patterns humans miss, and surfaces what matters most. The best results come from experienced fleet managers using intelligent tools.

Ask AI answers can include source references and navigation to permitted records. Proposed actions should be reviewed before execution, with permissions checked again when applied. An answer is decision support: verify important amounts, dates and quantities against the source record. Predictions without a released validation basis are not represented as current features.

Driver scoring is intended as a coaching input, not an automatic penalty mechanism — it surfaces patterns (speeding, harsh braking, idling) for a fleet manager to review and act on with context, not as an automated disciplinary trigger.

Intelligence features are built on the operational data your own fleet generates — trip records, telemetry, exceptions — processed and aggregated per HiVAM's data handling practices described in the Privacy Policy.

Intelligence features are designed to surface insights alongside the underlying operational screens, not to replace manual control. Specific configurability of individual AI features depends on the module — ask the team about your particular use case.

Operations intelligence is the practice of using real-time data and analytics to monitor, understand, and optimise business operations as they happen. In fleet management, it means going beyond basic tracking to understand why deliveries are late, where bottlenecks form, which assets are underperforming, and what operational changes would have the biggest impact.

Operational visibility means having a clear, real-time view of everything happening across your fleet operations — vehicle locations, delivery status, driver behaviour, trip progress, and performance metrics. Without visibility, fleet managers are forced to make decisions based on incomplete information, leading to inefficiencies and missed SLAs.

Raw data alone doesn't drive decisions. A fleet generates thousands of data points daily — GPS pings, speed readings, stop durations, fuel levels. Analytics transforms this raw data into meaningful insights: fleet utilisation rates, cost-per-kilometre trends, driver performance scores, and route efficiency comparisons. Without analytics, this data sits unused.

Telemetry — the automated collection and transmission of data from vehicles — is the foundation of modern fleet management. It replaces manual reporting (phone calls, paper logs) with continuous, objective data streams. This enables real-time tracking, automated record-keeping, anomaly detection, and the data foundation needed for AI-powered optimisation.

Key fleet KPIs include: fleet utilisation rate, average idle time, on-time delivery rate, cost per kilometre, fuel efficiency, vehicle downtime, driver safety scores, and distance covered per vehicle. The specific KPIs that matter most depend on your business model — a delivery company focuses on on-time rates, while a transport company may prioritise cost per tonne-kilometre.

Common causes include: excessive vehicle idle time, unoptimised routes, poor dispatch decisions, underutilised assets, reactive (not preventive) maintenance, lack of driver performance visibility, manual processes prone to errors, and data silos where information doesn't flow between teams. HiVAM addresses these by providing unified visibility and intelligence across operations.

Smart dispatch combines available freight, capacity, vehicle and driver readiness and the exceptions that need review. HiVAM provides assignment and depot-planning workflows; advanced constraints and predictive optimization remain distinct planned capabilities.

Data silos occur when information is trapped in disconnected systems — GPS data in one tool, dispatch records in a spreadsheet, fuel logs in another app. Fleet managers can't see the full picture, leading to duplicated work, missed insights, and slow decision-making. HiVAM solves this by centralising all fleet data into one platform.

Batch reporting compiles data at intervals — end of day, end of week — and delivers static reports. Real-time reporting shows data as it happens. For fleet operations, this distinction matters: a real-time dashboard lets you act on a delayed delivery now, while a batch report only tells you about it tomorrow. HiVAM prioritises real-time operational data.

Exception-based management means a manager only actively reviews what deviates from plan — late trips, off-route vehicles, expiring documents — rather than checking every record individually. HiVAM's Exceptions module (Operations domain) is built specifically for this: it surfaces what needs attention automatically.

It means one authoritative record for each fact — one trip, one status, one invoice number — rather than the same information re-entered separately into a GPS portal, a spreadsheet and an accounting tool, where the three can silently disagree. This is the core structural idea behind HiVAM's unified record.

Transport intelligence is the application of data analytics, machine learning, and real-time monitoring to transportation operations. It goes beyond simple tracking to provide insights into route efficiency, carrier performance, transit time accuracy, cost optimisation, and supply chain visibility — helping transport operators make smarter decisions.

Logistics intelligence refers to the use of integrated data and analytics to optimise the end-to-end logistics chain — from warehouse departure to final delivery. It encompasses fleet performance analysis, delivery pattern recognition, demand forecasting, and operational benchmarking. HiVAM provides logistics intelligence through its unified analytics and monitoring capabilities.

Fleet intelligence is the ability to derive actionable insights from the massive amounts of data generated by a vehicle fleet — GPS positions, engine telemetry, driver behaviour, trip records, fuel consumption. HiVAM is built as a fleet intelligence platform because we believe raw data without intelligence is just noise.

Basic GPS tracking answers one question: "Where is my vehicle?" Transport intelligence answers dozens more: "Why was this delivery late?" "Which routes are most efficient?" "Which drivers need coaching?" "Where am I losing money?" It's the difference between seeing a dot on a map and understanding your entire operation.

Supply chain visibility is the ability to track goods, vehicles, and information in real-time as they move through the supply chain — from origin to destination. Full visibility reduces uncertainty, enables proactive exception management, and improves customer communication. HiVAM contributes to supply chain visibility by providing the transportation leg's real-time data.

Fleet monitoring is passive — watching what happens. Fleet management is active — making decisions based on what you see. HiVAM provides both: real-time monitoring shows you the current state, while management tools (dispatch, route planning, analytics) give you the ability to act on it.

Key trends include: real-time fleet visibility platforms, AI-powered route and dispatch optimisation, IoT sensor networks for vehicle health and cargo monitoring, electric vehicle fleet management, autonomous vehicle preparation, data-driven sustainability initiatives, and the consolidation of point solutions into unified operating systems — which is exactly what HiVAM is building.

HiVAM provides fleet utilisation analytics, trip-level analysis, driver performance metrics, speed and idle time reporting, distance and route efficiency comparisons, geofence activity logs, and operational KPI dashboards. Analytics are built into the platform — no external BI tools required.

HiVAM provides pre-built analytics views for the most common fleet KPIs. Custom report capabilities are being expanded with each platform release. Enterprise customers can discuss bespoke reporting requirements with the HiVAM team.

Yes. HiVAM supports data export for trip records, analytics, and operational reports. You retain ownership of all your data and can request full data exports at any time as outlined in HiVAM's terms of service.

HiVAM retains historical fleet data based on your subscription plan. Standard data retention covers operational history needed for meaningful trend analysis. Enterprise plans offer extended retention periods. Contact the team for specific retention details.

HiVAM's analytics allow you to benchmark individual vehicles, drivers, and routes against each other. Identifying your best and worst performers is the first step to raising the average. Fleet-wide benchmarking against industry averages is a capability being explored for future releases.

Yes. By combining distance data from GPS tracking with fuel, maintenance, and operational cost inputs, HiVAM can surface cost-per-kilometre metrics at the vehicle, route, or fleet level. This is one of the most important KPIs for transport operators managing profitability.

Fuel evidence can combine supported imports and manual receipts with sourced distance or odometer readings. Sensor-based reporting requires compatible hardware and a configured data feed. An anomaly is a reason to review evidence, not proof of theft.

Ask about authorized records and source-linked metrics. Review a proposed action before applying it; permissions and record revisions are checked again when the action executes. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Search canonical records, follow their timeline and investigate the detail behind a total. Reports keep date, facility, filters and exported evidence aligned. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Review a sourced margin estimate before dispatch, inspect billable work left unbilled and identify onward connections at risk. Estimates and recommended actions remain clearly labeled. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Compare a labeled simulation against historical demand, or draft recurring bookings under an explicit policy. A simulation is not a production allocation and a schedule does not silently dispatch freight. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Data-trained predictions, calibrated uncertainty and autonomous interventions require validation before release. Rule-based recommendations are not described as predictive models. It is not included as a released feature or promised for a specific delivery date.

Route optimisation is the process of finding the most efficient path for a vehicle to travel — minimising distance, time, fuel consumption, or cost while meeting delivery constraints. It goes beyond simple navigation by considering multiple stops, time windows, vehicle capacity, and real-world road conditions.

Yes. HiVAM includes route planning capabilities with map-based visualisation. The platform provides route creation, distance calculation, and trip routing. Advanced multi-stop optimisation with constraint handling is being enhanced with each release.

Yes. HiVAM lets you overlay the planned route against the actual GPS trace. This comparison reveals route deviations, unauthorised detours, and opportunities to improve future route plans based on real driver behaviour.

HiVAM supports multi-stop trip management. You can define trips with multiple waypoints and monitor progress against each stop. AI-powered multi-stop sequence optimisation is on the development roadmap.

Yes. Route playback lets you visually replay a completed trip on the map, seeing exactly where the vehicle went, where it stopped, how fast it travelled, and how long it spent at each location. This is valuable for post-trip analysis, customer disputes, and driver coaching.

Traffic-aware routing is part of HiVAM's intelligence roadmap. The goal is to incorporate real-time and historical traffic data into route recommendations, helping drivers avoid congestion and reducing delivery time variability.

Yes. Route planning in HiVAM is a working tool for dispatch, not an automated black box — a dispatcher can adjust a route to reflect real-world knowledge a map doesn't have.

Multi-stop trip management supports defining a trip with several waypoints. Whether a specific milk-run pattern fits depends on how the trip and route are configured — the underlying multi-leg journey capability (Operations domain) is what this is built on.

Dispatch management is the process of assigning vehicles and drivers to delivery tasks, routes, or service requests. Effective dispatch considers vehicle availability, driver location, load capacity, delivery priorities, and time windows. HiVAM's dispatch module digitises this process, replacing phone calls and paper with a structured workflow.

Yes. HiVAM includes a dispatch management module where fleet managers can view available vehicles and drivers, create assignments, and track task completion. The dispatch board provides real-time context so dispatchers can make informed assignment decisions.

The depot load planner can propose work from available quantities and capacity for staff review. Committing a proposal and dispatching freight are separate controlled actions. Configurable workflows and rules handle supported operational events; unrestricted unattended dispatch and broader predictive optimization are not promised.

Phone-based dispatch creates no records, requires constant back-and-forth, and falls apart at scale. Digital dispatch through HiVAM creates structured assignment records, provides real-time status updates, reduces communication overhead, and generates data that can be analysed for continuous improvement.

Yes. Tasks and deliveries can be prioritised within the dispatch workflow. This helps dispatchers focus on time-sensitive assignments first and ensures that priority deliveries get the right vehicles and drivers.

The dispatch board groups work by status. Supported moves must follow the allowed workflow and required evidence; dragging a card is not an unrestricted way to mark freight delivered or bypass an approval. Open the job to review its quantities, holds and next action.

Yes. Hired-vehicle and partner workflows allow market vehicles without creating a fictitious owned vehicle. Capture the carrier or broker, vehicle details, hire terms and advances against the actual movement. Partner settlements and finance rights are separate from the permission to dispatch.

Define the places you serve, branch responsibilities and connections. Booking and movement use canonical locations instead of conflicting spellings. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Keep consignor, consignee, customer, carrier and broker roles attached to the right party and address. The payer can differ from the sender. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Record package type, private marks, quantities, weight, dimensions and handling needs so booking, labels and planning describe the same goods. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Assign a pickup, identify packages and confirm what actually entered custody. Loading scans record the packages on the departure, with discrepancies visible. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Split a booking across owned or hired departures. Received, moving, delivered, held and returned quantities remain tied to the original booking; completing one trip never completes the remaining goods. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Use a market vehicle without inventing an owned asset. Connect hire, advances, broker commission, inbound crossing and partner balances to the actual movement. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Record failed delivery reasons, reschedule work and preserve custody of refused or damaged packages. A hold blocks its dependent action until an authorized release. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Capture delivery evidence, review its quality and follow an original POD from handover to customer submission. Physical delivery and billing eligibility remain separate facts. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Propose loads from available depot quantities and vehicle capacity, inspect exclusions and commit selected loads. Quantity and resource checks run again at commit; dispatch remains a separate controlled step. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Broader scheduling across shifts, skills, connection windows and per-segment capacity is an expansion beyond the current depot planner. It remains planned until independently verified. It is not included as a released feature or promised for a specific delivery date.

HiVAM provides driver profiles, assignment tracking, trip history per driver, and the ability to associate drivers with specific vehicles. Driver performance metrics — such as speed compliance and idle time — help fleet managers identify coaching opportunities and reward top performers.

Yes. Using GPS and telemetry data, HiVAM can track driving patterns including speeding, harsh braking, rapid acceleration, and excessive idling. These metrics contribute to driver safety scores and help fleet managers proactively address risky driving habits.

Driver scoring based on behaviour metrics is part of HiVAM's analytics capabilities. Scores consider factors like speed compliance, idling patterns, and route adherence. These scores help fleet managers benchmark drivers, identify training needs, and create incentive programs.

The driver-facing PWA provides assigned trip information, supported check-ins, vehicle inspections, delivery proof, documents and help. Drivers see their permitted work rather than an office administrator view. Device permissions, connectivity and the capabilities in your plan affect what is available.

Recorded trip duty and availability can support planning and review. GPS movement alone cannot establish whether a driver is rested or fit to drive. Formal duty-hour compliance and automated fatigue detection should be assessed against the actual deployed workflow and applicable operating requirements.

Yes. HiVAM supports driver-to-vehicle assignment tracking. You can see which driver is currently assigned to each vehicle and maintain a history of assignments for compliance and accountability purposes.

Driver readiness and operational holds can affect assignment. A record should explain the restriction and who may release it. Suspension of login access and a dispatch eligibility restriction are different controls; verify both when setting up your policy.

Duty and assignment information can be recorded and reviewed; supported workforce inputs can feed allowances and payroll through the relevant APIs. This is not a blanket certification for a particular hours-of-service regulation, and inferred movement time should not be treated as an approved duty record.

Adding a driver record, their licence and document details, and assigning them to a vehicle are the core steps — handled through the People (Drivers) module. Documents can be uploaded to the driver record for the driver app and compliance tracking to draw on.

The driver app is built to run on a driver's own phone, one hand, in poor network — trip status, inspections, delivery proof and documents. An operation without a smartphone per driver can still run dispatch, tracking and compliance from the dashboard side; the driver-facing capture just depends on a phone being present in the cab.

Yes — assignment is per trip, not a fixed pairing of one driver to one vehicle, so a driver logs into whichever vehicle they've been assigned for that trip rather than being locked to a single truck.

The driver app is built for drivers across India, and language coverage is part of that design intent. Confirm which specific languages are live today with the team, since this expands over time.

The driver app captures what's needed to run a trip — position while on duty, inspections, delivery proof, licence and certificate documents. See the Privacy Policy for the full account of what's collected and why; this is not a general-purpose personal tracking tool outside of trip and duty context.

Check-ins, checklist answers and status updates made with no signal are held on the phone and sync automatically the moment signal returns — the driver sees a small pending indicator until the sync completes. Photos and signatures (a delivery photo, a defect photo, a signature) need a live connection at the moment they're captured, since evidence is uploaded as it's taken rather than stored on the phone first; if a connection drops mid-capture, the app tells the driver right away so they can retry once signal returns, rather than the item silently vanishing.

Show the papers for the actual consignment, record accepted or refused quantities and collection details, and safely replay supported queued operations. Files still require a working upload connection. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

A typical fleet manager starts the day by checking the dashboard for overnight alerts, reviewing today's dispatch queue, monitoring live fleet positions, responding to exceptions, and ending with performance summaries. HiVAM is designed to be the single screen that supports this entire workflow — eliminating tab-switching between disconnected tools.

Fleet managers can configure alerts for: geofence entry/exit, speed violations, excessive idle time, vehicle going offline, and trip milestones. Alerts ensure managers are notified about exceptions without needing to constantly watch the screen.

By replacing verbal instructions with digital dispatch records, tracking actual routes versus planned routes, and measuring objective performance metrics, HiVAM creates a transparent system where driver activities are documented and measurable — benefiting both managers and drivers.

Yes. HiVAM supports multi-location fleet management from a single dashboard. You can view vehicles across all depots, filter by location, and manage operations centrally — or delegate specific locations to regional managers with appropriate access permissions.

Measure the results against your own baseline: time spent booking and reconciling, missed billable work, utilization, failed deliveries and collection delays. HiVAM does not publish a verified customer ROI percentage or a guaranteed payback period.

The HiVAM dashboard is fully responsive and works from a mobile browser, so a fleet manager can check status away from a desk. It is optimised for desktop/tablet use for extended dispatch work — see the browser-support FAQ for full detail.

Because trip status, exceptions and the dispatch board are all live, shared records rather than one person's notes, an incoming shift can see exactly where things stand without a verbal handover — the system state is the handover.

Yes — the approval chain capability supports value-based rules, for example routing an advance over a set rupee amount through an extra approver before it clears, rather than every request following the same single-step path.

Check compliance, overlapping work and available resources before assignment. Effective-dated trailer coupling preserves which equipment carried the load. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Connect a critical inspection defect to grounding and a repair task. Repair evidence and authorized release restore readiness; repeated submissions do not create duplicate work. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Reconcile provider fuel records and manual receipts, preserve odometer provenance and flag suspicious consumption. Journey information distinguishes fresh telemetry from stale or inferred data. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

HiVAM gives logistics teams real-time visibility into the transportation leg of their supply chain. You can see where every vehicle is, whether deliveries are on schedule, and get alerted to exceptions — replacing the "call the driver" approach with live data on your screen.

Yes. Third-party logistics providers manage fleets for multiple clients with varying requirements. HiVAM's modular structure and multi-client capabilities make it well-suited for 3PL operations that need to track, dispatch, and report across different client accounts.

Yes. Last-mile delivery operations benefit heavily from real-time tracking, route management, and dispatch tools — all of which HiVAM provides. The platform helps last-mile operators improve delivery density, reduce failed deliveries, and provide customers with accurate ETAs.

E-commerce logistics demands speed, visibility, and scale — all areas where HiVAM excels. The platform provides the tracking, dispatch, and analytics backbone that e-commerce delivery operations need, whether you're running your own fleet or managing a 3PL partnership.

Bookings retain package and quantity references through loading, branch arrival, onward movement and delivery. Recorded shortages, damage and held or returned goods remain part of the custody history. GPS and geofence events add journey context; they do not replace a receiving or delivery transaction.

Delivery proof is available through supported driver and operations workflows, including uploaded evidence, delivered or refused quantities and POD review. Original paper POD custody can be tracked separately. A GPS geofence arrival is location evidence, not proof that the consignee accepted the goods or that an invoice is eligible.

Customer-facing tracking and document access can be built on HiVAM's scoped portal APIs for your own pages. A separate HiVAM-hosted customer portal is not represented as available. ETA quality depends on fresh journey data and the configured integration; check the tracking workflow and deployment with the team.

When paired with temperature sensors, HiVAM's IoT data ingestion can track temperature alongside location (see the temperature-monitoring FAQ), which is the core requirement for cold chain visibility. Formal cold-chain compliance certification is a separate question to confirm against your specific regulatory needs.

HiVAM's document vault and compliance records can hold hazmat-related documentation alongside standard vehicle documents. Specific hazmat regulatory workflows should be confirmed directly with the team against your exact requirements.

The document vault and compliance records module can store permits associated with a vehicle or a trip. Whether ODC-specific permit workflows are fully supported today is worth confirming directly with the team.

Yes. HiVAM provides APIs for data access and integration with external systems. This allows businesses to connect HiVAM with their existing ERP, TMS, WMS, or custom applications. API documentation is available to subscribed customers.

HiVAM's API-first architecture enables integration with ERP systems. The specifics depend on your ERP platform and requirements. Contact the HiVAM team to discuss integration feasibility and approach for your specific setup.

HiVAM provides many capabilities that overlap with traditional TMS platforms — fleet tracking, dispatch, route planning, and analytics — in a more modern, real-time package. Whether it replaces your TMS or complements it depends on your specific workflows and requirements.

Yes. HiVAM is designed to be hardware-flexible. If your vehicles already have GPS trackers installed, HiVAM can often integrate with them — avoiding the need to replace existing hardware. Contact the team with your device details for compatibility confirmation.

Signed event delivery and delivery history are represented in the integration API capability set. Integrations must configure authorized endpoints, scopes, signatures and failure handling. Retries mean consumers should handle repeat deliveries safely; they must not assume exactly-once receipt. Check the supported events for your deployment.

HiVAM's own finance module handles invoicing, payments and accounting registers natively. Integration with external accounting tools like Tally would go through the API — confirm current integration status and approach with the team.

The codebase includes API capability for provider-related transport evidence, but a source module is not proof of an activated live FASTag integration. Confirm the specific provider, credentials, supported import or live feed and reconciliation process before relying on automated toll reporting.

Provider fuel records and manual receipts can be imported and reconciled through the fuel evidence APIs. A specific live fuel-card connection depends on the provider adapter and your account configuration. Imported consumption evidence is different from a connected fuel-level sensor.

HiVAM's export manager supports pulling data out as files for use in a spreadsheet or another system (see the export-data FAQ). Confirm the exact format your accounting workflow needs with the team.

Define allowed transitions, evidence and bounded rules. Material events create durable effects with retry history; changing a definition does not silently migrate active jobs. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Preview linked documents and prepare supported print packs. Validate CSV batches, review row errors and merge duplicate masters with a retained identity history. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Connect customer booking intake and booking widgets to controlled staff review. Scoped API keys and signed events have revocation and delivery history; provider health exposes connection failures. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Expose permitted tracking, documents and requests through the organization’s own customer-facing pages and APIs. HiVAM does not claim a separate hosted customer portal where one is not provided. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Preserve column and filter preferences, enforce role and facility scope and trace material changes. Shared views do not grant access to restricted records or fields. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Additional partner exchange formats and governed extensions are planned. Compatibility, installation rights and support agreements must be established before a deployment is promised. It is not included as a released feature or promised for a specific delivery date.

HiVAM is priced per truck, per billing cycle, on one of four fixed tiers — Starter, Growth, Scale or Enterprise — with the rate also depending on whether you take HiVAM's own hardware, connect your own device, or buy hardware outright. Each tier includes a fixed, cumulative set of modules that you can individually switch on or off, but that toggle does not change your bill; you are not charged per module. See the pricing page for exact per-tier, per-truck rates, or contact HiVAM for a fleet-specific quote.

The published commercial trial is one month, subject to the agreed activation and Terms. HiVAM hardware can require a refundable deposit; BYOD does not require a HiVAM hardware deposit. A temporary feature-access grant has its own expiry and is separate from the period in which billing is suppressed. Your account and agreement should identify both.

You are charged only for trucks that have a tracker connected to them. Adding a truck to your fleet register costs nothing, and there is no limit on how many you can add. The moment a tracker is linked to a truck, that truck becomes billable at your plan's per-truck rate; when the tracker is removed or retired, it stops. So a fleet with 200 trucks in the register and 25 trackers fitted pays for 25.

No. Drivers are unlimited on every plan, always, and they never cost anything. A 25-truck fleet running 40 drivers on rotation pays exactly the same as one running 25. Drivers use the HiVAM Driver app, which is included. Dashboard seats — the office logins for your managers, dispatchers and accountants — are separate and are capped by plan; drivers are never counted against that cap.

You are charged only for the days remaining in that cycle, at your plan's per-truck-per-day rate. Before you link the tracker, the dashboard shows you the exact figure — both the daily rate that will recur and the one-off amount for the rest of the current cycle — and that amount is added to your next invoice. Nothing else changes: your billing date, your plan and your existing invoices all stay as they are.

You can. Adding a tracked truck is never blocked. If you contracted for 25 trucks and fit a 26th tracker, the 26th is simply billed at your plan's per-truck rate along with the rest — you are shown the amount before you confirm. If your fleet grows substantially it is usually worth talking to our team about moving to a plan that suits the new size better; you can raise that from the Subscription screen at any time.

The software price is the same as our Own HiVAM Hardware plan — what you save is the hardware. With Connect your own device there is no device to buy, so there is no upfront hardware cost at all; you pay the software rate only. The platform does the same work either way, which is why the software price does not change. One practical note: how much you see on screen depends on what your existing tracker reports. HiVAM's own hardware sends a considerably richer data set than most third-party AIS-140 units.

Yes. Monthly gives you flexibility; Annual gives you better value — paying for the year up front reduces your per-truck rate by 20%. On Connect your own device and Own HiVAM Hardware plans that saving applies straight away. On All-Inclusive plans, where the tracker is included at no upfront cost, it starts once you have completed your first year with us (18 months on Starter). Monthly billing runs on a 28-day cycle — see the next question.

A billing cycle is 28 days — four weeks. Over a 12-month year that works out to 13 cycles rather than 12. The per-truck rate charged in each cycle is exactly the rate shown on the pricing page, and the per-day figure we quote is that rate divided by the 28 days it covers, so the two always agree. Annual plans are billed once, covering 13 cycles. Section 5 of the Terms of Service sets this out in full.

Recurring payment is supported through UPI AutoPay and equivalent mandates, so your invoice is collected automatically each cycle without anyone having to remember. You approve the mandate once in your UPI app, including the maximum amount you are authorising. If your fleet grows beyond that amount you will be asked to approve a new mandate rather than being charged above what you agreed. You can see your mandate status, invoices and payment history at any time on the Subscription screen.

No. HiVAM is transparent about pricing. Your subscription covers the modules and features specified in your plan. Hardware costs, SIM/data charges, and any optional add-ons are quoted separately and clearly before any commitment.

Yes. Monthly subscriptions can be cancelled at any time. Annual subscriptions are subject to the refund policy terms outlined on the HiVAM website. Your data remains accessible for 30 days after cancellation to allow for export.

Yes. Starter is priced and built for small fleets — it covers real-time tracking and analytics without the modules reserved for Growth and Scale — and there is no minimum fleet size: HiVAM is billed per truck from a single vehicle upward, so a small operator only pays for the trucks they actually track.

Yes. Enterprise customers with large fleets, custom requirements, or multi-location deployments can contact HiVAM for tailored enterprise pricing. Enterprise plans may include dedicated support, custom integrations, and extended data retention.

For HiVAM devices loaned during the one-month trial, the refundable deposit is 25% of hardware cost per device. Connecting your existing tracker does not require a HiVAM hardware deposit; a mixed fleet pays it only for the HiVAM devices. If you do not continue, return the loaned devices: any refund is subject to the return deadline, condition assessment and other Terms. If you continue on the all-inclusive plan, the deposit and installed devices remain subject to that plan's return and retention terms. On Own HiVAM Hardware, the deposit is credited toward the purchase price. See /pricing and /terms for the figures and conditions.

Operational records have no per-record count cap when their capability is included in your tier. That does not unlock every capability: invoicing starts at Growth, for example. Office seats, AI credits, storage and integrations have separate plan limits. Truck records without a chargeable connected tracker are free; connected trackers are billed according to their dated usage, mode and agreed rates. See /pricing for the full breakdown.

A seat is one named user login with access to the dashboard — a dispatcher, a fleet admin, a finance user. It is separate from vehicle count and separate from the operational data (LRs, invoices, trips) the account holds, which is uncapped. Seat caps per tier are listed on the Pricing page.

The two purchase modes are structured around the hardware deposit and ownership mechanics described in the trial-deposit FAQ. Contact the team to discuss switching between them after your trial or initial term.

Pricing is structured per device/vehicle per month (see the tier rates on /pricing), with seat caps set per tier at the account level. This is why the platform is described as affordable at small fleet sizes — you're not paying a large flat account fee before adding a single truck.

Every plan is priced at the tier level, not per feature, so a capability you never open doesn't cost you anything extra to have available — HiVAM's own hosting and running cost for a module does not scale linearly with how much a given customer actually uses it. The more expensive mistake tends to run the other way: needing something six months in and discovering it isn't there. Plans are built to have more than a new account typically uses on day one for that reason, not to upsell you into growing.

HiVAM doesn't sell an à la carte, feature-by-feature plan — tiers are scoped by fleet size and operational complexity instead (see /solutions for which one typically fits an operation like yours). Because unused capability doesn't add to what HiVAM has to run for your account, there's no meaningful cost saving in stripping features out, so the platform is priced by tier rather than by a shopping list.

Adding more operational records within an included capability does not create a per-record charge. Your bill can change when you upgrade, connect more chargeable trackers, change tracker mode, or purchase additional credits or services. A truck record alone is free. Seats, AI credits, storage and integrations still follow their own plan limits. See /pricing and your dashboard billing statement for the applicable usage and agreed rates.

Set your operating profile, add the resources you use, and book a first shipment with the setup guide. Connect existing trackers or arrange HiVAM device installation where needed. The team activates your agreed billing trial and any feature-access grant; your account shows the available capabilities and their expiry. Billing is suppressed during the agreed billing trial. A hardware deposit applies only to HiVAM devices, as described in the trial-deposit FAQ.

Report a hardware fault to support. Refunds and responsibility depend on the device condition, warranty and published trial Terms; damage, tampering or missing components can affect the deposit. A fault should not be assumed to create either an automatic refund or an automatic charge.

Talk to the team before the trial month ends so continuation, cancellation or an extension can be arranged explicitly — the deposit mechanics in the trial-deposit FAQ are keyed to that decision point. Nothing about the arrangement is designed to auto-convert you into a paid plan without you saying so.

The commercial terms are built around a refundable deposit and no lock-in, not a signed multi-year agreement (see the homepage's risk-reversal section). Confirm the exact paperwork for your onboarding with the team, but a long-term contract is not what starts the trial.

Yes — pricing is per vehicle per month (see the price-per-vehicle-or-account FAQ), and fleets are expected to grow or shrink over time rather than needing to be fixed in advance. Talk to the team about how a mid-cycle addition is billed for your specific plan.

The platform includes authentication, permissions and audit controls. Production security also depends on deployment configuration, provider connections and verification of those controls. Request the applicable security evidence for procurement; this FAQ is not an independent security certification.

You do. All data you submit to and generate through HiVAM remains your property. HiVAM uses your data solely to provide and improve the service. Your data is never sold to third parties. Full details are in HiVAM's privacy policy.

See the Privacy Policy for the published data-processing, consent and data-rights terms. Requirements depend on your use and deployment; this page does not claim an independent GDPR or DPDP certification. Raise formal compliance and residency requirements during procurement.

Access combines the organization, contracted plan or active trial grant, role permissions and applicable branch or facility scope. A role cannot grant a feature outside the account's entitlement. Use invitations and the supported permission controls to give each person the work they need; sharing a saved view does not grant extra access.

Production traffic should use TLS and storage protections depend on the deployed infrastructure. Review the security documentation and configuration for your deployment. Encryption does not make data tamper-proof or replace access controls, audit history and backup recovery testing.

Backup schedules, retention and restore procedures must be confirmed for your deployed environment. A backup file alone does not establish that recovery has been tested, and no zero-data-loss guarantee is made in this FAQ.

Your data remains accessible for 30 days after cancellation to allow for export (see the cancel-anytime FAQ and the Refund & Cancellation Policy). After that window, data handling follows HiVAM's published data retention and deletion practices — see the Privacy Policy for specifics.

Account security features, including authentication options, are part of the platform's security posture. Confirm current two-factor authentication availability with the team or check your account's security settings.

IP-based access restriction is an enterprise-grade control some platforms offer. Confirm current availability and configuration with the team if this is a requirement for your organisation.

Specific audit or penetration-testing history is not publicly published at this stage. Enterprise customers with formal security review requirements should raise this directly with the team.

Yes — the audit log records material actions across the account (who changed a rate card, who approved an LR, what the system did automatically) with a timestamp, so a change can be traced after the fact rather than relying on memory.

Basic setup — creating your account, adding vehicles, and connecting GPS devices — can be done within a day for small fleets. Larger deployments with custom configurations, hardware installation, and team training may take one to four weeks depending on complexity.

Use the HiVAM learning centre at /guides/learn/hivam-setup for first-job setup, master data, migration and permission checks. Add the resources your actual FTL, PTL or hybrid job needs rather than every possible warehouse or owned truck. Review available assisted onboarding, integrations, hardware installation and staff training with the team and agree responsibilities and timing.

The free HiVAM Transport Guides learning centre at /guides offers a structured English-language transport business course: 12 modules, 48 chapters, step-by-step operating routines, worked examples, downloadable CSV worksheets and self-check answers. Learning paths cover owners, dispatchers, drivers, warehouse staff, finance, people and administrators. Each chapter links relevant HiVAM workflows with platform, API or planned availability labels. Reading progress stays in your browser and is not certification. Agree any assisted team training or onboarding scope with HiVAM separately.

HiVAM provides customer support via email at admin@hivam.in. Support covers technical issues, platform questions, and operational guidance. Enterprise plans may include priority support with faster response times and dedicated account managers.

Yes. If you're switching from another fleet management platform, HiVAM can assist with data migration and hardware transition planning. The specifics depend on your current setup and data formats. Contact the team to discuss your migration scenario.

The platform is designed for self-service setup in most scenarios. Adding vehicles, configuring geofences, setting up alerts, and inviting team members can all be done through the dashboard interface. For hardware installation and advanced configurations, support is available.

Use the supported CSV or spreadsheet template for the specific master or dataset. Preview mapping and validation errors, resolve duplicates and commit the reviewed batch. Historical bookings and financial balances need their own migration and reconciliation plan; they are not equivalent to importing a contact list.

A parallel-run period — operating both systems briefly while your team gets comfortable — is a common and reasonable way to de-risk a switch. Discuss timeline and approach with the team during onboarding.

Support is available via admin@hivam.in. Specific response-time commitments and support hours, especially for priority/enterprise support, should be confirmed directly with the team.

Enterprise plans may include a dedicated account manager and priority support (see the customer-support FAQ). Confirm what's included at your specific plan level with the team.

Guided setup asks for your operating model and the resources required for a first booking, and saved progress can be resumed. Hardware installation, imports, integration testing and staff training can take additional time. Agree a rollout schedule and billing or feature-trial start dates explicitly.

Agree the installation process and schedule with the team for the tracker model and vehicles involved. Compatible BYOD trackers may instead need provider configuration. Do not assume a physical installation is required for every software setup.

No dedicated IT staff is required — the dashboard is a standard web application and the driver app installs from a link (see the pwa-installation FAQ), with onboarding support from the HiVAM team for setup and configuration.

Supported import workflows validate spreadsheet rows and expose errors for review before commit. Employee and SKU imports have plan-specific rights; newer master-data imports and identity merges have their own supported templates. Confirm the template for vehicles, drivers or historical records rather than assuming every spreadsheet can be imported unchanged.

Onboarding includes getting your team comfortable with the parts of the platform relevant to their role. Confirm the specific training format and materials for your account with the team.

Carry completed duty and approved allowances into payroll inputs with source references. Attendance, advances and payroll remain reviewable before release. This is an API capability; a dedicated dashboard control is not implied. Access follows the relevant plan, permissions and deployment configuration.

Choose FTL, PTL or hybrid and owned, hired or mixed fleets. Add the resources needed for your first real job; progress is derived from saved records and resumes across devices. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Separate the contracted plan from temporary trial grants and role permissions. Expiry is checked when work runs; recovery and exports have explicit rights and preserve historical records. Review the relevant feature page and the capabilities enabled for your account; workflow availability does not waive required permissions or evidence.

Enterprise expands the published plan with capabilities such as multi-site and business-unit scoping, SSO and integration access. Deeper transport integration APIs are labeled separately from dashboard controls; EDI expansion and predictive models remain planned. Confirm support, retention and rollout commitments in your agreement.

Absolutely. SMEs can start on Starter, which covers essential tracking and analytics at an affordable per-truck rate, and move up to Growth or Scale as they need more — automated dispatch, maintenance, freight billing and the rest — without switching platforms or migrating data. HiVAM is built to grow with you.

No — HiVAM has no minimum fleet size. Pricing and the plan configurator support fleets from a single truck upward, and you are billed per truck regardless of how large your fleet is. Small fleets often see the biggest relative improvement because they're typically upgrading from purely manual processes — spreadsheets and phone calls — to a fully digital system.

HiVAM is designed for larger operations, but a deployment at thousands of vehicles needs capacity planning and measured testing of telemetry, maps, reports and concurrency. No unqualified zero-lag performance guarantee is stated here.

Multi-country fleet management is on HiVAM's roadmap. The platform architecture supports multi-region deployment and localisation. Businesses with international operations can contact HiVAM to discuss timelines and requirements.

White-label and partner solutions are being evaluated as part of HiVAM's enterprise strategy. If you're interested in offering fleet intelligence capabilities under your own brand, contact the HiVAM team to discuss partnership options.

Because pricing is structured per vehicle per month with no long-term lock-in (see the trust/risk-reversal section on the homepage), adding or reducing tracked vehicles as demand fluctuates seasonally is a normal part of how the platform is meant to be used.

Multi-site and business-unit scoping (Enterprise tier) is built for exactly this — running more than one operation from a single account while keeping each team scoped to its own data.

Multi-site scoping (Enterprise tier) is built for exactly this — each business unit or site sees its own data by default, while the organisation retains an overview across all of them.

The platform is built with redundancy and monitoring to minimise downtime, and scheduled maintenance windows are communicated in advance and planned for low-traffic periods. A published uptime SLA will follow as usage scales and there is a track record to report against, rather than a number stated in advance.

The delay from a physical vehicle event to the dashboard includes the device interval, provider feed, network and processing path. Use source timestamps and integration health to evaluate freshness. A verified single-digit-seconds SLA is not published here.

HiVAM is built as a modern cloud-native platform with real-time data processing pipelines, a responsive web dashboard, and API-first architecture. The system is designed for horizontal scalability, high availability, and fast iteration — enabling rapid feature development without sacrificing reliability.

HiVAM data is stored on secure cloud infrastructure. The platform follows security best practices for data storage, including encryption and access controls. Data residency details can be discussed with enterprise customers who have specific requirements.

The architecture is designed to support growing workloads. Adding vehicles does not require building your own software stack, but actual infrastructure limits, report sizes, concurrency and telemetry throughput must be measured and configured for the deployment.

Yes. API documentation is provided to subscribed customers for integration purposes. The documentation covers available endpoints, authentication, data formats, and usage examples.

Yes. HiVAM uses real-time data streaming to push live vehicle updates to the dashboard. This means your map and status panels update automatically without manual refreshing — providing a truly live view of your fleet.

The dashboard requires an internet connection — it is a real-time system by design (see the hivam-offline-mode FAQ). The driver app is the part of the platform built for offline capture, syncing once signal returns.

Session and authentication typically rely on cookies in a modern web application. See the Cookie Policy on the website for the specific categories of cookies used and their purposes.

API usage terms, including any rate limits, are covered in the API documentation provided to subscribed customers (see the api-documentation FAQ). Check the docs or ask the team for current limits.

Custom domain / white-label dashboard access is not part of the current published capability set. If this matters for your deployment, raise it with the team.

A specific published SLA figure is not available at this stage. If a formal uptime commitment is a requirement for your organisation — common for enterprise procurement — raise it directly with the team.

Fleet management is the practice of overseeing and coordinating a company's vehicle fleet to ensure efficient, safe, and cost-effective operations. It encompasses vehicle acquisition, maintenance scheduling, driver management, route planning, compliance, fuel management, and performance analytics. Modern fleet management increasingly relies on digital platforms like HiVAM.

Telematics is the combination of telecommunications and informatics — the technology behind sending, receiving, and storing vehicle data over cellular networks. When a GPS device in a vehicle transmits its location, speed, and engine data to a platform like HiVAM, that's telematics in action.

IoT (Internet of Things) in fleet management refers to the network of connected devices — GPS trackers, sensors, OBD readers, temperature monitors — installed in vehicles that collect and transmit operational data. This data feeds into platforms like HiVAM to provide real-time visibility and intelligence.

A TMS is software that helps companies plan, execute, and optimise the physical movement of goods. Traditional TMS platforms focus on freight management, carrier selection, and shipment planning. HiVAM takes a different approach by unifying fleet-level operational intelligence with transport management capabilities.

A WMS manages operations within a warehouse — receiving, storage, picking, packing, and shipping. While HiVAM focuses on the transportation and fleet side, it connects with the warehouse through geofence-based entry/exit tracking and trip management that starts from the warehouse dock.

A 3PL provider is a company that offers outsourced logistics services — transportation, warehousing, and fulfilment — on behalf of other businesses. 3PLs manage fleets for multiple clients simultaneously, making multi-client visibility and modular fleet management tools like HiVAM especially valuable.

An FMS is software designed specifically to help fleet operators manage their vehicles — tracking locations, monitoring maintenance, managing drivers, and analysing performance. HiVAM is a modern FMS that adds intelligence, real-time capabilities, and unified analytics on top of traditional fleet management functions.

ETA stands for Estimated Time of Arrival — the predicted time when a shipment or vehicle will reach its destination. Accurate ETA calculation requires real-time location data, route information, and traffic awareness. HiVAM's live tracking provides the data foundation for increasingly accurate ETA estimates.

Dwell time is the amount of time a vehicle spends at a location — such as a warehouse, depot, or customer site — before departing. Excessive dwell time reduces fleet productivity. HiVAM tracks dwell time automatically through geofencing, helping fleet managers identify and address loading/unloading bottlenecks.

Dead mileage, also called empty running, is the distance a vehicle travels without carrying any cargo or passengers. It represents pure cost with no revenue. Reducing dead mileage through better dispatch and route planning is one of the most effective ways to improve fleet profitability.

Fleet utilisation measures how effectively a fleet's vehicles are being used — typically expressed as the percentage of time (or distance) vehicles spend on productive tasks versus sitting idle. Low utilisation means you're paying for assets that aren't earning. HiVAM's analytics help identify and improve utilisation rates.

Vehicle downtime is the period when a vehicle is unavailable for operation — due to maintenance, repair, inspections, or breakdowns. Unplanned downtime is especially costly. Tracking downtime patterns helps fleet managers schedule preventive maintenance and maintain higher fleet availability.

FTL (Full Truck Load) means a single shipment fills an entire truck. LTL (Less Than Truck Load) means multiple smaller shipments share truck space. The choice affects pricing, transit time, and fleet planning. HiVAM supports both operational models through flexible trip and dispatch management.

Reverse logistics covers the return flow of goods — from the customer back to the origin. This includes product returns, recalls, recycling, and waste management. Managing reverse logistics requires the same fleet visibility and dispatch capabilities as forward logistics, making HiVAM applicable to both.

First-mile is the movement of goods from the origin (e.g., factory or supplier) to a distribution hub. Last-mile is the final delivery from a local hub to the end customer. Last-mile is typically the most expensive and complex leg. HiVAM provides the tracking and dispatch tools needed for both, with particular strength in last-mile visibility.

Cross-docking is a logistics strategy where incoming goods are sorted and directly loaded onto outbound vehicles with minimal or no storage in between. It requires precise timing and coordination between inbound and outbound fleets — making real-time fleet visibility critical for successful cross-docking operations.

EV fleet management adds new dimensions: battery charge monitoring, range anxiety management, charging infrastructure planning, and energy cost optimisation. As EV adoption grows in commercial fleets, HiVAM's platform is being designed to accommodate EV-specific telemetry and operational requirements.

Better fleet management directly reduces emissions through: optimised routes (shorter distances), reduced idle time (less fuel burned standing still), improved fleet utilisation (fewer vehicles needed), and predictive maintenance (engines running efficiently). The data and insights from HiVAM help fleet operators measure and improve their environmental impact.

A VLTD is the general regulatory term for a GPS-based device installed in a vehicle to transmit its location for tracking and, in some jurisdictions, compliance purposes. It's the same category of hardware that feeds live location into a platform like HiVAM.

A Lorry Receipt is the document a transporter issues to a consignor when goods are handed over for road transport in India — it records the consignor, consignee, goods description and terms, and is central to freight billing and legal liability. HiVAM generates LRs directly from the trip record (see the lr-tms capability).

An E-Way Bill is an electronic document required under India's GST rules for the movement of goods above a certain value, generated on the government e-way bill portal. HiVAM can generate E-Way Bills against a trip's actual route and value.

ePOD replaces a paper delivery receipt with a digital capture — typically a signature or photo taken on a driver's phone at the point of delivery — attached directly to the shipment record instead of a physical slip that can be lost.

A DVIR is a checklist a driver completes before or after a trip to confirm the vehicle's condition — brakes, lights, tyres and similar safety items — flagging anything wrong before the vehicle goes back on the road.

Under India's GST rules, a Goods Transport Agency's services can attract GST paid by the recipient of the service rather than the transporter, under specific conditions — the Reverse Charge Mechanism. This affects how freight invoices are structured; confirm exact applicability with a tax advisor for your specific transactions.

A detention charge is a fee billed to a customer when a vehicle is held at a loading or unloading point beyond an agreed free time — compensating the transporter for the vehicle's lost productive time. HiVAM's contracts module can attach detention terms to a customer account.

Backhaul is the return trip a vehicle makes after delivering its outbound load — ideally carrying another paying shipment rather than running empty (dead mileage). Reducing empty backhauls is one of the biggest levers for fleet profitability.

The consignor is the party sending the goods; the consignee is the party receiving them. Both appear on a lorry receipt and are central to who is billed and who confirms delivery.

A freight forwarder arranges the movement of goods on behalf of a shipper, often coordinating multiple carriers and modes rather than owning the fleet itself. HiVAM is built primarily for fleet operators who own or manage their own vehicles; a pure forwarder's needs may only partially overlap with the platform.

A multi-axle truck has more than the standard two axles, allowing it to legally carry a heavier load — common for long-haul freight in India. Vehicle configuration like axle count is recorded as part of the asset registry.