Project Brief · Factory Floor Verification System

GES Manufacturing
× Prisma Technology

GES Manufacturing Service (M) Sdn Bhd (Venture Corporation) · Senai, Johor

⬤ Scoping Phase Site Visit: 6 Aug 2026 14 Mini PC Stations 2 Modules · 1 System
System objective: One web-based, on-premises factory floor system — running on a single industrial server, accessed via browser on 12 mini PCs — that verifies part placement at every production station and converts Heller oven recipe data into traceable reports, with full audit trail for customer review.

What We Are Building

Introduced via MLR Machinery (Eric Chew), Prisma Technology is delivering the software layer for GES's factory floor traceability and oven data management initiative.

14
Mini PCs / Stations
2
Software Modules
4+
Items Scanned per Cycle
3
User Roles
1
Industrial Server

"After verified with Master Data then send PASS/FAIL to conveyor controller (at least 1 output, for IO module) to allowed/blocked the parts — with tower light alert."

— Meeting notes, 6 Aug 2026 (MLR Machinery / Prisma alignment)
Module A

Test Process Verification

Scan 5 items per cycle against a master list. Send PASS/FAIL signal to conveyor controller via DI/DO module. Full audit trail for every cycle.

Module B

Oven Recipe Extraction

Read Heller oven JSON recipe files from a Windows shared folder on the Heller PC, convert to Excel/CSV, detect changes against a master reference, and alert management (email alert proposed by Prisma — channel to confirm with GES).

Test Process Verification

At each of 12 production lines, an operator logs in and scans 5 items. The system checks all 5 against the master list and releases the conveyor stopper only on PASS.

Scan Workflow — Per Station Cycle

1
Operator Login UserID
Each operator logs in with their UserID before starting a scan session. Role: Operator / Technician / Admin.
Model Auto — from Planning Document
Model is pre-loaded from the production planning document (work order / schedule) for that line — operator does not enter this manually. The system reads which product/model is scheduled on this line and displays it automatically.
2
Enter Raw Material / PCB Number Manual
PCB has no barcode — operator types the part number manually.
3
Solder Paste Type (2D) Scan
Solder paste used in the SMT process. Barcode or 2D code scan.
4
Stencil Scan
Metal stencil barcode. Confirmed: barcode/QR scan. RFID excluded.
5
Squeegee To Verify
Mentioned in meeting notes — to be confirmed with GES whether Squeegee is a tracked scan item for this system.
System Verification + Stopper Signal
All scanned items checked against Master Data (linked to Model → Product → Customer).
PASS → DI/DO signal to conveyor controller → stopper releases + audit log written.
FAIL → Tower light alarm + stopper locked + operator must state reason.

Audit Log — Fields Captured Every Cycle

DateTime (timestamp)
Line Number
Operator ID
Customer (from Master Data)
Raw Mat / PCB Code
Model
Solder Paste Type
Stencil Code
Squeegee Code
Result: PASS / FAIL
Fail Reason (if FAIL)
Override: Admin + Reason

Master Data — Hierarchy

Customer
└─ Product (Model)
└─ PCB · Solder Paste · Stencil
  • Each product belongs to exactly 1 customer
  • 1 customer can have many products
  • Each product defines the expected parts set
  • Admin manages via web UI (replaces Excel)
  • CSV bulk import for initial migration

Reports & Export

  • Statistics of failure / accuracy rate
  • Filterable by date, line, result, operator
  • CSV export from admin portal
  • Real-time monitoring screen per line

Oven Recipe Extraction & Change Management

The Heller reflow oven exports recipe files in JSON format. This module reads those files, displays them in-system, exports to Excel, and gates any significant changes through an approval workflow.

Core Functions

  • Read JSON recipe files from Heller oven PC — Windows-based PC; GES to configure shared folder (READ access only required)
  • Display recipe data in-system
  • Export to Excel / CSV format
  • Detect changes vs. master reference file
  • Tolerance comparison: working recipe vs. master
  • Email alert to management when recipe changes
  • Authentication required to modify master reference
  • Full history log of all changes

Oven Machine Master Maintenance

  • Configure tolerance thresholds
  • Set shared file location (oven PC path)
  • Manage master reference recipes
  • Review full change history
  • Admin authentication required for changes
⚠ Pending
Heller .json sample file needed before full scoping. Request via Eric Chew (MLR Machinery).
Module B — Workflow
1
System reads Oven PC shared folder
Heller oven exports JSON recipe file to shared location. Prisma system polls / monitors for new files.
2
Compare against Master Reference
System compares new recipe against the approved master reference. Tolerance thresholds applied.
3
Change detected → Email alert to management
Any deviation is logged and flagged. Prisma proposes email alert to management — alert channel to be confirmed with GES.
4
Admin reviews & approves / rejects
Admin authenticates to approve the new recipe as the new master reference. Reject → old reference remains active.
5
Export to Excel / CSV
Any recipe (current or historical) can be exported for external reporting.

System Design

Fully on-premises. Factory floor network is completely isolated from the office network. One industrial server hosts both modules; 12 mini PCs run a browser and connect via factory LAN.

FACTORY FLOOR NETWORK (isolated — no office network access) ┌──────────────────────────────────────────────────────────────────┐ │ │ │ [ Industrial Server ] [ Heller Oven PC ] │ │ Both Module A + B JSON recipe files │ │ Web app (browser-based) ◄── shared folder (READ) ───────┐ │ │ │ │ │ │ 32/48-port network switch │ │ │ │ │ │ │ ┌──────┴──────────────────────────────────────────────┐ │ │ │ │ │ │ │ │ [Stn 01] [Stn 02] [Stn 03] ... [Stn 14] │ │ │ Mini PC Mini PC Mini PC Mini PC │ │ │ │ + Screen + Screen + Screen + Screen │ │ │ │ Browser Browser Browser Browser │ │ │ │ │ │ │ │ │ │ │ │ Stopper Stopper Stopper Stopper ◄─ DI/DO module │ │ (locked) (locked) (locked) (locked) conveyor ctrl │ │ │ │ │ │ │ └─────────────────────────────────────────────────┘ └───┘ │ └──────────────────────────────────────────────────────────────────┘ Access: Factory staff → mini PC browser → Industrial Server (same LAN) Signal: Server → DI/DO module → Conveyor controller → Stopper open/close Alert: Server → Email (management) on oven recipe change

🖥 Industrial Server × 1

  • Hosts Module A + Module B
  • Web application server
  • Database (audit logs, master data)
  • Industrial-grade preferred

💻 Mini PC × 14

  • One per station / production line
  • Browser-only (thin client)
  • Fixed Station ID in server config
  • Specs from GES: due 8 Aug 2026

🔌 Network Switch

  • 32 or 48 ports recommended
  • Connects all 12 lines + oven PCs
  • Factory LAN only
  • No office network bridge

User Roles

Role Parts Scanning Oven Module Admin Functions
Operator Run scans, view own results View recipes, run exports
Technician Operator + (TBC overrides) TBC TBC
Admin Full + master list mgmt + override log Full + approve recipe changes User mgmt, system config, full audit

Phase-Based Rollout

Phase 1 pilots on a single production line for validation and sign-off. Phase 2 rolls out to all 12 lines after pilot acceptance.

Active
Phase 0 · Now
Requirements & Scoping
  • Site visit completed (6 Aug 2026)
  • Core requirements captured
  • PRD drafted
  • Mini PC specs (due 8 Aug)
  • Heller .json sample pending
  • GES PIC contact TBC
Next
Phase 1 · Pilot
1-Line Pilot & Sign-Off
  • Hardware procurement finalized
  • Software development
  • Installation on Line 1
  • ≥ 20 PASS + 20 FAIL test cycles
  • 5 consecutive stable working days
  • Admin CSV export verified
Pending
Phase 2 · Full Rollout
All 12 Lines
  • After Phase 1 sign-off
  • Roll out to Lines 2–12
  • Staff training
  • Module B full deployment
  • Handover & maintenance SLA
Requirements Confidence by Module
Source: PRD v0.4 + meeting notes 6 Aug 2026 · Updated 7 Aug 2026

People

Prisma Technology leads software delivery. MLR Machinery handles all hardware and physical installation.

J
Jay (Lew Wen Jyue)
Project Director
Prisma Technology
K
Jas Teo (Kae Shyong)
Director / Partner
Prisma Technology
C
Mr Chang (SC Chang)
AutoCount / VecTech Specialist
Prisma Technology
D
Dhai Muhammad
Lead Developer / PM
Prisma Technology
E
Eric Chew
Main Contractor
MLR Machinery Sdn Bhd
?
GES PIC
Customer Contact
GES Manufacturing (Venture)

Open Items

The following items require confirmation from GES or the team before development can begin on the respective components.

BLOCKER
→ Eric / GES

Heller oven .json sample file

Without a real sample, Module B cannot be scoped or developed. Please share any recent recipe export from the Heller oven PC.

HIGH
→ GES / Eric

Mini PC specifications

GES to provide full model, brand, and I/O spec by 8 Aug 2026. Required to confirm DI/DO port availability for stopper control.

HIGH
→ GES PIC

GES PIC contact details

Name, phone number, and role of the primary contact at GES for this project. Required before direct requirements alignment meetings.

MED
→ Dhai + Eric

DI/DO module technical spec

Exact wiring, port assignment, and protocol for the DI/DO module connecting the server to the conveyor controller. Dhai to align with Eric after receiving mini PC specs.

MED
→ GES PIC

Customer audit template / required fields

Exact fields GES's customer mandates for traceability reports (IPC-A-610 or customer-specific format). Affects audit log schema design.

MED
→ GES PIC

Planning document format for Model

Prisma proposes to auto-load the Model from the production planning document (work order / schedule). GES to confirm: what format is the planning document? Is it a file, an ERP export, or a printed sheet? This determines how the system reads it.

MED
→ Mr Chang / GES

Squeegee — confirm as scan item

Mentioned in post-meeting notes. To be confirmed with GES: is the Squeegee one of the items to be scanned and tracked in this system?

LOW
→ Dhai

FAIL re-scan limit

How many consecutive FAIL attempts before the station locks and requires Admin/Technician unlock? Dhai to recommend a number for Jay's approval.

LOW
→ GES PIC

Traceability data retention period

How many years / months must audit records be retained on the server? Required for storage capacity planning.

LOW
→ GES PIC

Technician role exact permissions

What specifically can a Technician do that an Operator cannot? E.g., override FAIL, view full logs, modify settings.