FleetOps

Transport operations involve many moving parts: drivers, vehicles, routes, kilometer records, fuel requests, and supporting documents. When this data is handled manually, it becomes difficult to track what happened, which vehicle was used, how much fuel was requested, and whether the request has been approved. The challenge was to design a system that feels simple for daily admin work, while still supporting operational details such as role-based access, approval status, SK BBM records, route management, odometer documentation, and manager-level visibility.

I started by understanding how the existing transport workflow works in the field: how drivers report kilometer usage, how fuel requests are created, how approvals are handled, and how admins check supporting data. From there, I broke the system into core modules: dashboard overview, vehicle and route data, Bon BBM requests, SK BBM records, approval flow, and odometer photo documentation. The goal was not to make the system complex, but to make each operational step easier to track and review.

FleetOps is built as a responsive web dashboard using Next.js, Tailwind CSS, Supabase, and Vercel. The system includes role-based access, manager dashboard, Bon BBM approval flow, SK BBM table, route management, and odometer photo upload. Admins can manage operational records, while managers can review requests, check data summaries, and approve fuel-related workflows. The system is designed to reduce scattered manual checking and make transport data easier to access from one place.

• Next.js App Router
• Tailwind CSS
• Supabase
• Role-based Access

FleetOps helped me work on a real internal business system with more complex logic than a typical landing page. The project required product thinking, database structure, dashboard UX, approval workflows, and operational detail handling. It shows my ability to design and build tools for real business operations — especially systems where clarity, accuracy, and daily usability matter more than visual decoration.