Fieldwork & Domain Exposure
4-month exposure (April–July 2026) across 6 manufacturing facilities, accompanying a mentor. Role: observation, learning, and hands-on wiring/panel work — not independent leadership or design.
Pattern 1 — Just-in-Time Supply Efficiency (2–3 Shift Cycle)
Observation: Manufacturing sites operate 2–3 shift cycles with minimal buffer inventory. Cost efficiency prioritized over storage.
Applied to FinTrack: Accounting admin also operates in high-frequency, low-inventory cycles (daily invoice batches, immediate reconciliation). The Telegram input model mirrors the JIT principle: immediate data capture, same-day P&L visibility, no backlog.
Pattern 2 — Operator Expertise via Standardization (Not Formal Training)
Observation: At MMKI, an SMK-educated magang operates sophisticated multi-axis nutrunner equipment — not from a 3-year engineering degree, but from standardized operation protocols and clear error-prevention mechanisms.
Applied to FinTrack: The Telegram interface is a standardized operation protocol for accounting. SMK-level admin inputs transaction data (not journals); the system handles the expert logic — reconciliation, allocation, P&L assembly.
When designing systems — automation or software — I start from real operator reality: what can this person actually do, what constraints exist, and what can be standardized. This is the bridge between field knowledge and software design.