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 12 Production Lines 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.

12
Production Lines
2
Software Modules
5
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 via email when recipe changes.

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 Scan
Confirmed in meeting notes ("Squeeee"). The squeegee blade used for solder paste printing. Scan method TBC.
✓
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
✓ Sample Received
Heller .json sample received 7 Aug 2026 from Eric Chew. Full structure analysis complete — see Oven Data section below.
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. Email alert sent to management (confirmed requirement from meeting notes).
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.

Oven Data: Sample Received & Analysed

Eric Chew sent the Heller reflow oven JSON recipe file and the Excel controlled form on 7 Aug 2026. The analysis below is drawn directly from those files.

1. JSON Recipe File — Structure

Machine & Recipe Identity

  • Oven firmware: hellerOvenRevision SW v3.12.1
  • HeaterPIDVersion: 1
  • Recipe name: J8-A16382H9C2-RSS
  • temperatureOffsetsPath: "*** Use Setup Defaults ***"

Zone Count

topZones: 13
bottomZones: 13
coolZones: 1
belts: 1
irZones: 0
vefoZones: 0

Belt label: Main · setpoint: 85.0 cm/min

Zone Field List — 16 Fields per Zone

id
setpoint
hiProcAlarm
loProcAlarm
hiAlarm
loAlarm
hiWarn
loWarn
alarm
kp
ki
kd
deadband
offset
label
nitrogenControl

Warn / Alarm Values in the JSON (Actual Sample Values)

Field Value (all 13 zones identical) Meaning
hiWarn / loWarn ±15 °C Zone temp deviates >15 °C from setpoint → oven issues warning
hiAlarm / loAlarm ±40 °C Hard alarm — oven triggers directly
hiProcAlarm 400 °C Absolute upper limit — prevents overtemperature
loProcAlarm 0 °C Absolute lower limit — detects broken thermocouple
deadband 2 PID dead zone (°C) — prevents hunting
offset −1.0 Thermocouple calibration correction

2. Controlled Form Module B Must Replace

GES currently records oven recipes manually on form QR-AS-100 B/AS-02-062 — an auditable controlled document. Module B must produce an equivalent digital output.

Excel Form Structure

  • CUSTOMER — e.g. ABCD
  • LINE — e.g. SMT 5
  • MODEL — e.g. C02-0327-1601-01F
  • CS / SS — Component Side / Solder Side profile
  • SPEED (CM/MIN) — belt speed
  • TOP 1–13 — setpoint per top zone (°C)
  • BOTTOM 1–13 — setpoint per bottom zone (°C)

2 sheets · ~12 recipe blocks per file · same model appears twice (CS row + SS row)

JSON → Excel Field Mapping

Excel Field JSON Source
TOP 1–13 topZones[].setpoint
BOTTOM 1–13 bottomZones[].setpoint
SPEED (CM/MIN) belts[0].setpoint
MODEL NOT in JSON — must come from master data or filename convention
CUSTOMER NOT in JSON — must come from master data
LINE NOT in JSON — inferred from file path / source PC
CS / SS NOT in JSON — may be in recipe filename (e.g. RSS suffix) — pending GES confirmation
⚠ Critical Finding — Two Different Tolerances

The JSON file and GES's verbal requirement each describe a different kind of tolerance. They are not interchangeable. Conflating them would produce the wrong system.

Tolerance A — Inside the JSON (Oven PLC)
  • What: Runtime safety band — monitors measured zone temperature vs setpoint during production
  • When: Continuously, during active production run
  • Who acts: Oven PLC — triggers alarm or stoppage automatically
  • Values: ±15 warn / ±40 alarm — identical across all 13 zones
  • Significance: Generic factory config — not product-specific process engineering
Tolerance B — What GES Asked For (Not in JSON)
  • What: Engineering gate — compares working recipe setpoints against a versioned, authenticated master reference file
  • When: At recipe import / changeover time, before production starts
  • Who acts: Prisma system — flags deviation, triggers management approval workflow
  • Values: Defined by GES process engineers — not yet provided
  • Significance: The JSON provides nothing for this — a Prisma-managed Tolerance Master must be built

The JSON warn/alarm fields protect the oven from overtemperature during a run. The tolerance GES requires protects the process from unauthorised recipe changes before a run. Different timing, different purpose, different data source. The Prisma system must build and manage the Tolerance Master independently — it cannot read it from the oven JSON.

4. Open Questions for GES — Module B

The following items are unconfirmed and must be resolved before Module B development can be fully specified. Items are marked as INFERENCE (reasonable assumption, not confirmed) or EVIDENCE (from received files or meeting notes).

OQ-1
→ GES Process Eng.

Is tolerance per-zone per-model, or a global fixed value?

INFERENCE awaiting GES confirmation. If per-zone per-model, the Tolerance Master table is significantly more complex. Impact: database schema and maintenance UI design.

OQ-2
→ GES Process Eng.

Tolerance unit: absolute °C or percentage deviation?

INFERENCE awaiting GES confirmation. Determines the comparison engine formula. A ±5 °C tolerance at 150 °C is very different from ±5%.

OQ-3
→ GES Management

When tolerance is exceeded: hard-block import, or approval-gated workflow?

INFERENCE awaiting GES confirmation. Hard-block = recipe cannot be used until approved. Approval-gated = recipe can proceed but requires management sign-off within a time window. These have different development complexity and operational risk profiles.

OQ-4
→ GES / Eric

CS / SS meaning — confirmed as Component Side / Solder Side?

INFERENCE awaiting GES confirmation. The Excel form shows the same MODEL appearing twice (CS row, then SS row) with different temperature profiles. Industry convention = Component Side / Solder Side (two oven passes). If confirmed, the master reference must store two profiles per model — more complex than a single profile per model.

OQ-5
→ GES / Eric

Recipe filename convention — what do J8, A16382H9C2, RSS mean?

INFERENCE awaiting GES confirmation. The sample recipe is named J8-A16382H9C2-RSS. J8 may be the line number; RSS may encode the profile type (matching CS/SS). MODEL and LINE are not inside the JSON — if they can be reliably parsed from the filename, that resolves the mapping gap without needing a separate lookup table.

OQ-6
→ GES Process Eng.

Which JSON fields count as a "recipe change" triggering an alert?

Context from sample. Each zone contains 16 fields; across 28 zones the total is ~460 comparable values. If all fields are monitored, minor PID tuning (kp/ki/kd) will generate frequent alerts. GES must define which parameters are process-critical (likely: setpoint, offset, belt speed, alarm bands) vs which are routine machine maintenance (PID gains, deadband).

OQ-7
→ GES PIC

Audit retention period for recipe history

INFERENCE awaiting GES confirmation. Customer audit requirements may specify a minimum retention period (e.g. 3 years, 5 years). Determines storage capacity planning for the oven history log.

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 │ │ │ │ │ │ │ ┌──────┴──────────────────────────────────────────────┐ │ │ │ │ │ │ │ │ [Line 01] [Line 02] [Line 03] ... [Line 12] │ │ │ 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 × 12

  • One per production line
  • Browser-only (thin client)
  • Fixed Line 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 received (7 Aug 2026)
  • 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.5 + meeting notes 6 Aug 2026 + oven JSON sample analysis · Updated 13 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.