PotoP Enterprise Suite for Android

The dashboard is a page of the PotoP Enterprise Suite served by your company's own server, shown in the app at phone width. Hours, open requests and appointments are read from the PostgreSQL database when the page loads and are limited to what the signed-in user's role may see. The interface language and the company's colours come from company settings on the server. The app itself only shows the page and adds notifications and biometric sign-in on top.

Planned, worked and available hours are calculated by the server from the planning board, the recorded hours and the contract of the employee. The calendar shows only the signed-in person's own assignments, because permissions are checked on the server for every page. When the planner moves a job, the change appears here on the next load and can also trigger a notification. Nothing is planned on the phone, so office and field always see one version of the schedule.

Leave balances are computed by the server from the employee's contract, earlier requests and the company's rules. A request submitted here becomes a record in the company database with the status requested, and managers who may approve it are notified. Approval, rejection or withdrawal changes the balance immediately for everyone. The phone stores no leave data itself and only shows the page.

The assistant answers questions from the company's own data, such as projects, planning, storage and colleagues, using a language model that runs on the company's own hardware. The answer is built from database queries made with the permissions of the asking user, so it cannot reveal what the user could not open. Long questions are handled in the background and the reply is shown when it is ready. The suggested questions are starting points and can be replaced by free text.

The list is the technician's own work orders for today, taken from the planning board on the PES server. Address links open the phone's navigation app, and the number opens the dialler. Location is shared only after the user agrees in the app and in Android, and the browser engine reports it to the server. Reporting a fault creates a record in the company database, and files or photos can be attached with the phone camera.

Positions are sent by the phones of colleagues who have chosen to share, through the standard browser location function that Android permits per app. The server keeps the latest position and shows it on an OpenStreetMap-based map, only to users whose role allows it and only while the company setting for sharing is on. The checklist on the screen tests each condition, such as consent, HTTPS and a recent fix. Sharing can be switched off by the person at any time.

Faults are records in the PES database, entered by a person, a form or a linked PotoP VMS system that reports a device failure. The server calculates each fault's SLA deadline from its priority and marks it overdue when the time passes, and the counters at the top come from those results. Filters for priority, technician and source are applied on the server. Assigning a fault notifies the technician on the phone.

The dispatch view combines the planning board with open work orders on the server: who has jobs today, which jobs have no technician and which are late. The planning agent proposes assignments using rules based on availability, skills, location and the existing schedule, and a dispatcher confirms. It runs on the server, and no data is sent to a cloud service. The live map opens from here and uses the same shared positions.

Booked hours come from time entries in the PES database, scheduled hours from the planning board, and billable hours from the project each entry belongs to. Submitting the week locks the entries and sends them to the approver, and the status is visible to both sides. The rules for rounding, overtime and approval are the company's settings on the server. The phone shows the page and stores no timesheet data of its own.

Messages are encrypted in the browser engine of the phone before they are sent and are decrypted only on the devices of the participants, using a Rust-based implementation of the Olm and Megolm ratchets. The server stores and forwards ciphertext and cannot read it. Keys stay on the device, and the backup option stores them encrypted with a passphrase so a new phone can read earlier messages. Attachments are encrypted too and saved to Downloads only after decryption on the phone.

Every module writes its alerts to one notification table on the PES server, filtered by the person's permissions, and this page lists them. The same items reach the phone as Android notifications through a long poll that the app keeps open to your own server, so there is no Google or Firebase in between. Reading an item on one device removes it on the others. The categories, such as bookkeeping or chat, are the module names, and each user can choose which ones alert them.