Fuel Distribution
PDOMS (Pomdes Delivery Order Management System)
PDOMS (Pomdes Delivery Order Management System) is a web-based application designed to manage the entire transaction and distribution workflow for fuel (BBM) in an integrated manner, connecting PT Zoomindo Inti Perkasa (PT ZIP), Pomdes business partners, and suppliers.
PDOMS (Pomdes Delivery Order Management System) is a web-based application designed to manage the entire transaction and distribution workflow for fuel (BBM) in an integrated manner, connecting PT Zoomindo Inti Perkasa (PT ZIP), Pomdes business partners, and suppliers. This application serves as a digitalization solution, replacing manual data and transaction management—which were previously unstructured and prone to administrative errors—with a centralized system. This ensures that transaction management becomes more organized, accurate, transparent, and efficient for all parties involved.
The system supports four user roles, each with specific authorities and functions. The "Admin" role acts as a super-user, managing master data (such as users, locations—provinces and cities—and fuel types) and possessing full access to all application features. The "Head Office" (PT ZIP) role is responsible for reviewing and approving fuel orders submitted by Pomdes, issuing invoices, verifying payments, and addressing reports regarding delivery discrepancies. The "Pomdes" role, representing business partners, can submit fuel purchase requests, upload proof of payment, confirm the receipt of fuel, and report any volume discrepancies. Meanwhile, the "Supplier" role is tasked with receiving and confirming orders, uploading proof of shipment along with estimated arrival times, reporting any transit issues, and periodically updating fuel prices.
The transaction workflow within the system follows a structured process, from initial request to final completion. It begins when a Pomdes unit submits a fuel purchase request via the application, which is then reviewed and approved by the Head Office. Once approved, the Head Office issues an invoice to be paid by the Pomdes unit. After the payment is verified by the Head Office, the order is forwarded to the supplier for delivery to the Pomdes location. Upon arrival, the Pomdes unit verifies that the fuel received matches the order. If everything is in order, the transaction is marked as complete, and a PDF receipt can be generated and printed. However, should a discrepancy in volume arise, the Village-Owned Enterprise (Pomdes) may submit a non-conformity report; the corresponding value will then be accumulated or deducted from the invoice for the subsequent transaction.
From a technical perspective, the SPPPP application is built using a combination of modern front-end and back-end technologies. The user interface is developed using HTML, CSS, JavaScript, Bootstrap, jQuery, and Vue.js to provide an interactive and responsive user experience. On the back-end, the application utilizes the PHP programming language with the Laravel framework to handle business logic and system architecture, supported by PostgreSQL—a relational database management system (RDBMS)—to store and manage transaction data securely and reliably.
The system supports four user roles, each with specific authorities and functions. The "Admin" role acts as a super-user, managing master data (such as users, locations—provinces and cities—and fuel types) and possessing full access to all application features. The "Head Office" (PT ZIP) role is responsible for reviewing and approving fuel orders submitted by Pomdes, issuing invoices, verifying payments, and addressing reports regarding delivery discrepancies. The "Pomdes" role, representing business partners, can submit fuel purchase requests, upload proof of payment, confirm the receipt of fuel, and report any volume discrepancies. Meanwhile, the "Supplier" role is tasked with receiving and confirming orders, uploading proof of shipment along with estimated arrival times, reporting any transit issues, and periodically updating fuel prices.
The transaction workflow within the system follows a structured process, from initial request to final completion. It begins when a Pomdes unit submits a fuel purchase request via the application, which is then reviewed and approved by the Head Office. Once approved, the Head Office issues an invoice to be paid by the Pomdes unit. After the payment is verified by the Head Office, the order is forwarded to the supplier for delivery to the Pomdes location. Upon arrival, the Pomdes unit verifies that the fuel received matches the order. If everything is in order, the transaction is marked as complete, and a PDF receipt can be generated and printed. However, should a discrepancy in volume arise, the Village-Owned Enterprise (Pomdes) may submit a non-conformity report; the corresponding value will then be accumulated or deducted from the invoice for the subsequent transaction.
From a technical perspective, the SPPPP application is built using a combination of modern front-end and back-end technologies. The user interface is developed using HTML, CSS, JavaScript, Bootstrap, jQuery, and Vue.js to provide an interactive and responsive user experience. On the back-end, the application utilizes the PHP programming language with the Laravel framework to handle business logic and system architecture, supported by PostgreSQL—a relational database management system (RDBMS)—to store and manage transaction data securely and reliably.