On site, every role uses only the screen for its own job. Entries are made on the phone, kept with their evidence and checked by the server's rules; managers see only the projects they are authorised for in the web panel.
Field staff use the mobile app; managers use the web panel, which also works on a phone. Permissions are granted per company, module, action and project; access to a module does not mean access to every action or every project in it.
The company administrator manages users, roles and projects. The project manager draws the site boundaries of their projects and approves or rejects project change requests on behalf of their project; for a side with no approver, the company administrator decides instead.
Manages fuel entries, the review queue, corrections, tanks and the stock ledger. Entries waiting for intervention and count differences land on their work list.
The fleet manager runs the records and assignments, the maintenance planner the templates and the plan, the inspection officer the due dates and results. The reporting role only reads.
Dispenses or receives fuel. Searches the machine by code, enters the reading and the litres, takes the photos with the camera; sees their last three entries and the ones waiting for intervention.
Enter lubrication records for the machines of their project; mount, remove and measure tyres from the chassis diagram. Machines due for measurement wait on a separate list.
The foreman describes the fault to the AI assistant and adds photos. The master takes the draft work order, carries out the repair and closes it with a closing record.
On the Fledium side, opens companies and manages the shared library: equipment types, chassis templates, tyre and oil catalogues. Never sees the companies' field records.
The tanker operator's screen is kept simple: big buttons, little text, no project selection. Nothing is saved before the summary screen has been seen.
Search with at least two characters of the fleet number or registration; results show code, type and project. If the choice is a tanker, the app asks whether the fuel is for its own engine or its distribution tank.
Depending on the machine's meter type, engine hours, kilometres or both are entered. Each meter's photo goes into its own slot and is taken with the camera only.
The litres dispensed and a photo of the tanker's flow meter. If the limit set for the tank is exceeded, the app does not continue.
No entry is complete without a GPS location, its accuracy and the time. With a connection the server's pre-check runs; without one, the entry waits encrypted on the phone.
The operator picks no project. The entry goes to the tanker's project, the site is found from the GPS location, and the machine's assignment is updated with this entry.
A machine with no project is assigned to the tanker's project in the same step; the assignment is written to the audit trail as "automatic assignment".
A request goes to both projects for approval. Once both sides approve, the machine moves to the new project and the site found from the location; the side that rejects picks the right machine, and the entry moves to it.
If the location is inside no boundary, the site stays empty and the entry is not blocked. Several candidates, an accuracy circle crossing a boundary or a faked location go to review.
Field staff sign in with the company code, a username and a password, and set their own password at first sign-in. The session is tied to the device; if a manager revokes the device, the Fledium data on the phone is deleted at the next connection.
A tanker can have several operators for the day and night shifts, with no vehicle handover in the app. Every transaction is recorded under the operator's own ID, and the litres come off the tanker's stock ledger.
| Time | Operator | Machine | Litres | Stock |
|---|---|---|---|---|
| 06:55 | M. Yılmaz | EK-07 | 231 | 6,282 |
| 08:05 | M. Yılmaz | DZ-02 | 512 | 5,770 |
| 21:30 | A. Kaya | EK-07 | 248 | 5,522 |
In a tunnel, at a mine or on a remote site, the app doesn't wait for the internet. Fuel, lubrication, tyre and fault entries are kept encrypted on the device with their photos; when the connection returns they sync without any entry being written twice. An entry the server refuses is not deleted; it shows as "needs intervention".
