Delayed communication
Reporting a problem could require leaving the workstation.
01INDUSTRIAL CAPSTONE
Connecting
the factory floor.
GlassSync is a web-based operational platform developed through an SUTD capstone collaboration with PT Muliaglass.
A shared workflow for defect communication, hourly production reporting and structured shift handovers between factory teams.
MY ROLECore technical contributor
TEAM1 of 3 primary developers in a team of 7
02THE INDUSTRIAL PROBLEM
Critical information shouldn't depend on walking.
The starting point was a physical communication gap between manufacturing operations.
THE CHALLENGE
How can two production teams coordinate defects and shift information without relying on repeated physical handovers?
Cold End and Hot End teams needed faster, clearer communication about production issues.
The project report described a factory environment in which operators sometimes needed to travel between work areas to communicate defects. Information could become fragmented across people, shifts and records.
Limited shared visibility
Teams needed a common view of defects and their current status.
Shift continuity
Outstanding issues and production context needed to remain visible across handovers.
03THE SOLUTION
One shared digital workflow.
A common system connecting production setup, defect tracking, reports and operator handovers.
PRODUCTION TEAMCold End
Inspection, defect review and follow-up
SHARED APPLICATIONGlassSync
One source of operational information
PRODUCTION TEAMHot End
Defect response, production updates and handover
Defect Management
Report, monitor and resolve production defects.
Hourly Reporting
Record speed, efficiency and rejection information.
Shift Handover
Preserve operator notes and relevant shift history.
Inspection Records
Review consolidated production and defect information.
04DEFECT REPORTING
From reporting to shared visibility.
A defect should remain visible through its operational lifecycle.
To Fix
Reported and awaiting action
Fixing
Work currently in progress
Fixed
Resolution recorded
GlassSync provides a common view of defect categories, status changes and operational information for the relevant teams.
Project-level featureThe defect board is presented here as a team deliverable, distinct from the features I personally took ownership of.
05MY CONTRIBUTION / HOTO
Preserving context between shifts.
I developed the Hand-Over / Take-Over workflow as part of my frontend and backend contribution.
PERSONAL IMPLEMENTATIONHOTO workflow
Shift handover interactions, operator notes, backend integration and the retrieval of previous handover information.
01
Capture Hot End and Cold End handover notes.
02
Associate handover records with shift context.
03
Display earlier notes for continuity and review.
06MY CONTRIBUTION / REPORTING
Making production data usable.
I also contributed to GlassSync's hourly reporting functionality.
Production measurements needed a structured workflow instead of disconnected entries.
01Speed and efficiency
Hourly operational measurements
02Rejection categories
Production rejection rates and notes
03Shift and time context
Reports associated with the relevant operating period
Contribution scopeI worked on hourly reporting as part of the technical team. This is distinct from my HOTO implementation ownership.
07TECHNICAL ARCHITECTURE
Connecting operations through software.
The platform uses a web frontend, application API and relational data layer.
USER INTERFACE
React
Operational dashboards, forms and workflows
APPLICATION
Node.js + Express
REST APIs and business logic
DATA
Relational Database
Shifts, defects, reports and production records
Operational UX
Interfaces designed around day-to-day production tasks and reporting.
Data and workflows
APIs linking shift context, submissions and persistent operational records.
Integration
React, Express, REST services and containerized local development.
Simplified system architecture. My personal contribution spanned frontend and backend work; the overall platform was developed as a team.
08INTERNAL EVALUATION
Measured during prototype testing.
A usability benchmark for defect submission, reported during the team's internal evaluation.
WHAT THE NUMBERS REPRESENT
These figures describe the internal defect-reporting task, not the HOTO workflow or hourly reporting.
AVERAGE SUBMISSION TIME18.2 sec
Internal defect submission
INTERACTIONS10
Average interactions per submission
INTERNAL TASK TARGETS
Time target
≤ 25 secondsInteraction target
≤ 15 interactionsScope of evaluation
This was internal prototype testing. It does not establish factory-wide deployment performance or independently measured production efficiency gains.
09ENGINEERING TAKEAWAYS
Useful software starts with understanding the work.
GlassSync taught me to translate real industrial needs into interfaces, APIs and workflows that support communication across teams and shifts.
01Understand the environment
Design around actual operator workflows.
02Connect the layers
Make frontend and backend behavior coherent.
03Preserve operational context
Keep important information available across shifts.