DOCSEARCHbyAlgolia
Submit Docs

ATP30 User Manual

website·Indexed 31 days ago

https://atp30-usermanual.vercel.app

User documentation for the ATP30 transport management system, featuring guides for administrators and drivers. Admin modules cover system settings, user and role management, vehicle and contract management, billing calculations, and operational reports (Y Ratio, Trip, and Contract Invoice reports). Driver modules provide instructions for recording logbooks, trips, energy/fuel usage, standby work, and tracking personal income.

Tokens
32.4K
Snippets
76
Records
289
Agent score
74%

What's inside ATP30

  1. Overview of Trip Record Management

    The Trip Record menu is used by the office for vehicle trip planning. Data is organized hierarchically by Customer -> Contract -> Route -> Round -> Date. Information created here flows into Trip History (for approval), Driver Income (for payroll calculation), and Customer/Partner Invoices (for financial documentation).

  2. Overview of the Driver App functionality and scope

    The Driver App (atp30-tos-driver) is designed for drivers to manage their daily operations via mobile. The system controls access to features using route-level and menu-level permissions.

    Core capabilities include:

    • Retrieving driver profile data from /auth/me.
    • Retrieving assigned trip records from /driver/trip-record.
    • Viewing and editing trip records based on permissions.
    • Recording daily activities such as refueling, vehicle log books, and standby work.
    • Reviewing calculated income summaries provided by the backend.

    The system is used by Drivers (primary mobile users), Operation teams (data verification), and Admin/Backoffice (billing and reporting).

  3. Overview of the Customer Management screen

    The 'Customer' (ลูกค้า) menu is used to manage partner company data for ATP30 transport services. This data is critical for trip planning and billing. The main screen consists of three primary elements: a search field for filtering by customer name or ID, a green '+ Add Customer' (+ เพิ่มลูกค้า) button for new registrations, and a customer list table displaying Customer ID, Name, and Status (Active/Inactive).

  4. Overview of ATP30 Admin System Modules

    The ATP30 Admin system is divided into several core modules that manage the flow of data from operations to billing and reporting. The primary modules include:

    • Dashboard: The landing page (/home) providing summaries of customers, vehicles, users, trips, billing revenue, partner revenue, driver revenue, and X-Ratio.
    • Operations: Handles real-time vehicle operations, including oil prices, trip records, trip history, refueling, vehicle records, standby tasks, and general histories.
    • Billing: Manages financial outputs based on backend calculations, covering customer invoices, contract invoices, and driver income.
    • Reports: Provides administrative summaries and data exports, including income reports, trip reports, contract invoice reports, and Y-Ratio reports.
    • Setting / Master Data: Manages core reference data used across all other modules, such as customers, vehicles, users, areas, contract bus companies, vehicle types, roles, fuel cards, and holidays.
    • Contract Management: Located within customer details; used for step-by-step contract creation and defining logic that affects billing and revenue.

  5. Understand Admin Data Flow

    Data flows through the system in three primary stages:

    1. Master Data $\rightarrow$ Contract: Customer, vehicle, vehicle type, user, area, and partner company data serve as the foundation for creating contracts. Contracts are accessed via routes under /customers/:customerId/....
    2. Operations $\rightarrow$ Billing: Trip records, standby tasks, refueling, and vehicle logs provide the source data for calculations. The Billing UI displays summarized data from the backend rather than calculating from a single form.
    3. Billing $\rightarrow$ Dashboard/Reports: The Dashboard consumes summarized data from the /dashboard/ endpoint, while Reports use dedicated routes (e.g., trip-report, income-report).

  6. Understand the Admin Routing and Layout Architecture

    The Admin system is divided into two primary layers:

    1. Login Layer: Uses LoginRoutes for authentication. It employs GuestGuard to prevent authenticated users from returning to the login page and uses MinimalLayout for authentication and maintenance pages.
    2. Application Layer: Main system routes are defined under MainRoutes, which uses AuthGuard to wrap the MainLayout. Module-specific routes (e.g., customer, vehicle, trip-record, invoice, report) are separated into domain-specific route files. All routes are wrapped in an ErrorBoundary located in src/routes/index.tsx.

  7. Understand the Admin system authentication and routing flow

    The Admin system uses a combination of route guards and contexts to manage access. The login pages are located at / and /login and are protected by GuestGuard. Once authenticated, the main routes are wrapped in AuthGuard, and the default landing page is /home.

  8. Understand the role of Step 2 in Contract Management

    In the contract management workflow, Step 2 defines the 'billing formula' associated with the contract structure established in Step 1. This step is critical because the selected contract group determines which form fields are displayed to the user and the backend calculation logic used for vehicleAmount and pricePerVehicle. Selecting the incorrect group will result in incorrect form inputs and erroneous financial calculations.

  9. Manage fuel and electric vehicle energy consumption

    The 'Refuel/Charging' (การเติมน้ำมัน/ชาร์จไฟ) menu allows administrators to monitor, record, edit, and delete energy usage data for both fuel-powered and electric vehicles. The interface is divided into two primary tabs: 'Fuel Vehicles' (รถเติมน้ำมัน) and 'Electric Vehicles' (รถชาร์จไฟฟ้า), each supporting specific operations for adding, editing, and viewing details based on the vehicle type.

  10. Retrieve partner invoice summary list

    The partner invoice list page provides a monthly overview of invoices, including a summary card and a data table. The summary card displays driverCount, totalAmount, maxAmount, and minAmount based on the API response.
    GET /partner-invoice?month=YYYY-MM&q={search_term}&page={page_number}&pageSize={page_size}

  11. Manage daily diesel prices in the Oil Price menu

    The 'Oil Price' (ราคาน้ำมัน) menu is used to record and verify daily diesel prices. This data serves as the critical reference for calculating contracts that use variable pricing formulas, specifically those using Fixed Date or Average Price formulas. Key capabilities include adding new daily prices, editing historical prices, and searching for prices within specific date ranges.

  12. Manage customer contracts in ATP30

    The Contract Management screen is used to define the master data of a contract, billing formulas, and special income that the system uses for actual vehicle operation calculations. This menu becomes available after a customer has been created. A single customer can have multiple contracts, and there is currently no defined maximum limit on the number of contracts per customer. There are 9 primary contract condition types: A1, A2, A3, B1, B2, C, D, E, and F.