Operational framework
Maintenance and error traceability
Connecting machine use, print history, errors, maintenance, and technician actions so defects can be traced before they create further loss.
- My role
- System design, SharePoint implementation, rollout, and production ownership
- Evidence
- Working professional framework
- AI involvement
- None. Entry, filtering, and investigation are manual and human-led.
When a print defect or machine error occurred, technicians could not always determine which machine or build had produced the part, who had started it, or what recent errors and maintenance activity were associated with the equipment. The goal was to preserve enough history to investigate a problem before it created further loss.
I designed and built a connected SharePoint framework covering print history, machine use, error events, maintenance history, and technician actions. QR-linked entry allowed production-floor personnel to record information at the relevant equipment. The system is used across the production floor.
If a part is found to have a print defect, technicians can trace it back to the machine and build associated with it. That history allows the equipment to be checked before the same condition affects more parts. The system supports faster investigation and better use of material and production time.
The framework relies on structured records, manual entry, filtering, and human investigation. It does not use AI or claim predictive maintenance. A future improvement would connect it with the order-tracking system through available APIs so relevant action points can be created automatically.