Oracle APEX, QR identification, Zebra label printing and live Power BI reporting for manufacturing tools.
Co-designed and developed a production platform used to track more than 2,100 manufacturing jigs and tools. The system connected operational users, a normalised Oracle data model, QR workflows, label printing and live reporting into one maintainable platform.
The project started with inefficient manual tracking and limited visibility over manufacturing assets. The solution needed to be quick enough for production use while improving traceability and giving teams a consistent source of information.
That meant designing for real users on the factory floor rather than treating the database or interface as separate technical exercises.
Worked directly with users and stakeholders to understand the operational problem, gather requirements and translate workflows into a database-backed application design.
The data model and application flows were structured for maintainability rather than simply reproducing the old manual process on screen.
Developed frontend and backend functionality in Oracle APEX, connected QR identification, and built a Zebra printing pipeline using RESTful print services, ZPL encoding and automated queue handling.
Power BI consumed platform data to provide operational readiness and management reporting.
Released functionality to live users, iterated from feedback, supported production use and produced documentation, training and handover material so the platform could be maintained after the placement.
The project covered the full lifecycle rather than ending at a prototype.
Physical jigs and tools are identified through QR-based workflows, allowing users to interact with the correct asset quickly while keeping status and condition information tied to a shared system of record.
A custom print pipeline integrated Zebra label printers using RESTful services, encoded ZPL commands and automated queue handling so labels could be generated from within the application workflow.
Application data feeds live dashboards used for operational readiness and shift-start decisions, giving teams and management a clearer view of asset status than the previous manual process.
The most important result was that the system became part of a real operational workflow rather than remaining a proof of concept.
The project reinforced that enterprise software is as much about users, process and maintainability as it is about code. Requirements changed as people used the system; deployment exposed edge cases that did not exist in development; and documentation mattered because ownership had to continue after the original developers left.
It is the clearest example in my portfolio of end-to-end delivery under genuine operational constraints.
This is a public case study, so it intentionally omits internal source code, exact database structures, authentication details, proprietary workflows and non-public manufacturing information.
The figures and technologies shown here are limited to the level used in my recruitment materials and are intended to demonstrate scale, engineering decisions and delivery responsibility without exposing internal implementation detail.