DOCSEARCHbyAlgolia
Submit Docs

FTM Fleet Management System

website·Indexed 32 days ago

https://ftm-doc.benefitcz.cz

Documentation for the FTM system used for fleet management, including vehicle tracking, driver administration, and cost reporting. It covers vehicle acquisition, car-sharing processes, GPS unit and SIM card management, insurance events, fuel and charging records, and integration with SAP and CAFM systems for reporting and helpdesk tickets.

Tokens
18.7K
Snippets
8
Records
161
Agent score
47%

What's inside FTM

  1. Overview of FTM Application Architecture and Integrations

    FTM is a browser-based application that retrieves data via an API. It uses a corporate authentication service for access control and integrates with both internal systems and external data sources to manage vehicle fleets, fueling, and personnel.

  2. Overview of the Spolujízda (Carpool) service

    Spolujízda is a portal-based tool designed for the efficient use of company vehicles. It allows users to post offers for available vehicle capacity. Interested employees can request to use this capacity, and the offer provider then confirms the request.

  3. Overview of Private Car Performance Tracking in FTM

    The FTM system tracks the performance of private vehicles used for corporate purposes. This data is primarily used for two objectives: optimizing the vehicle fleet to minimize the use of private cars and calculating the carbon footprint of vehicles. Note that the FTM system does not handle the calculation of reimbursements for the use of private vehicles. Data regarding private vehicles is imported into FTM via an interface from the SAP system.

  4. Manage GPS unit SIM cards in FTM

    The FTM system tracks GPS units installed in vehicles and their associated SIM cards used for data transmission. This tracking is primarily used to verify billing from GPS data providers. The system maintains a registry of all deployed SIM cards, including their phone number, current status (Active or Suspended), and whether the card is currently assigned to a specific vehicle.

  5. Understand FTM GPS hardware and data flow

    FTM integrates with vehicle tracking systems via a GPS provider. Data is collected from in-vehicle units via GSM connections, sent to the provider's system, and then retrieved by FTM into its own database via API for processing. The hardware ecosystem typically consists of:

    • GPS Unit: Records the current vehicle position.
    • CAN BUS: A vehicle bus providing telemetry such as odometer readings and fuel levels.
    • GSM Module: Handles data transmission from the vehicle to the provider.
    • RFID Reader: Used for driver identification via RFID chips.
    • Service/Private Switch: A physical switch used to distinguish between business and private trips.

  6. Use the Vehicle data source for reporting

    The Vehicle data source is used for reporting on vehicles, typically categorized or summarized by vehicle attributes. It includes all vehicle attributes, including user-defined properties, as well as data regarding the vehicle's driver, cost center, or organizational unit.

    Important Limitation: This data source does not contain vehicle performance data (such as kilometers driven).

  7. Detect refueling discrepancies using GPS and CAN bus data

    The FTM application identifies potential refueling issues for vehicles equipped with GPS and a CAN bus. It compares the fuel increase detected directly via the CAN bus (the actual change in the vehicle's tank level) against the recorded fuel purchase data entered into the system (sourced from CCS, CNG, UTA, or manual entries).

    If there is a significant difference between the purchased liters and the actual increase in the tank, the system flags the vehicle for refueling analysis. Dispatchers can then review these cases within the Dispatcher Closure (Dispečerská uzávěrka), utilizing detailed vehicle location data and tank levels immediately before and after the event to clarify the discrepancy.

  8. Analyze insurance event data using typical reporting scenarios

    The insurance events data source provides comprehensive information regarding insurance claims, including details about the vehicle, the driver, the party causing the damage, the resolution method, and the associated costs of resolving the event. Common reporting scenarios include:

    • Generating an overview of events for a specific time period.
    • Counting events aggregated by company, organizational unit, or individual employee.

  9. Understand the vehicle closing process

    The vehicle closing process (Uzávěrka vozidla) is performed by a dispatcher to summarize, verify, and lock operational data for a specific period. The primary focus is on distance traveled (km) and fuel consumption. Once a closing is created, the system generates a summary containing:

    • Actual fuel consumption (liters)
    • Normalized fuel consumption (liters)
    • Difference between actual and normalized consumption (liters)
    • Difference between actual and normalized consumption per 100 km
    • Total amount of fuel refilled

    If the driver has a manager's contract, the closing also includes the total kilometers driven for private purposes.

  10. Understand FTM notification delivery channels

    The FTM system uses notifications to alert staff about critical vehicle management events and to communicate with external parties. Notifications are delivered through three primary channels: Email, SMS, and the system Bulletin Board (Nástěnka).

  11. Understand application authentication and authorization requirements

    Access to the application requires two conditions to be met: successful user authentication and the existence of configured permissions for that user.

    Authentication is typically handled via an external service (Azure AD). However, authentication alone is insufficient; the system must also find a set of permissions associated with an application role for the user. If no role or permission is found, the user will be denied access. Role and permission configuration is managed by application administrators.

  12. Identify and manage on-site vehicle refuelling

    On-site refuelling occurs when a vehicle is charged from a specific facility's electrical grid, creating a cost for that facility. The FTM application provides tools to identify these events and assign the corresponding costs using two primary methods:

    1. Address-based identification: Authorized users can create a set of recurring addresses associated with a specific site. When the system encounters these addresses in the future, it automatically assigns the refuelling event to that site.
    2. GPS-based identification: The system can identify on-site refuelling if the site has a registered GPS location. For higher precision, the FTM application includes a tool to define exact site boundaries using GPS coordinates.