Data Analyst
What I learned here
How a national priority programme actually runs — and why the data layer is where most of its problems surface. A programme of this size is not short of data; it is short of people who can read it. Working here taught me to build for the person who has to make a decision before lunch, not for the analyst who already understands the dataset.
The work, in summary
I build the reporting and monitoring layer for the national school nutrition programme (Makan Bergizi Gratis). In practice that means taking data that arrives as separate spreadsheets from different units, reconciling it against our own records so the totals agree, and turning it into dashboards the directorate opens directly. Six systems are in use today, covering SPPG operations, staffing, beneficiaries, suppliers, hygiene certification, and suspension.
Achievements
- Built a real-time executive dashboard covering approximately 27,000 Satuan Pelayanan Pemenuhan Gizi (SPPG) units and 58 million programme beneficiaries, replacing static Excel reporting with filterable reporting accessible from any device, at no licensing cost.
- Developed a procurement monitoring system across four directorates, consolidating roughly Rp1.1 billion in recorded transactions with payment status, administrative completeness, and delay tracking — establishing a single source of truth where the true volume had never been visible in one place.
- Built a suspension dashboard that integrates data from another directorate through a live import-range with a backup fallback, replacing a single-user spreadsheet with a real-time executive summary.
- Built Sistem Tiket Kendala, the field issue ticketing system now carrying the directorate’s operational problems. Reports previously arrived scattered across WhatsApp, letters, chat, and conversation, so nothing could be tracked to closure; the system registers every report with an auto-generated ticket number, adds an SPPG operational status check to separate operational faults from other causes, matches SPPG payments, recaps tickets and volume per province on a dashboard, and keeps a user activity log — with role-based access so each regional PIC works only their own area. It is now the standard input for the directorate’s decision meetings.
Documentation
Photographs from this period.
Dashboard Data Monitoring Program Makan Bergizi Gratis
7 photosOne entry point for the whole programme: SPPG operations, beneficiary numbers, certification status, and supplier delivery. Twelve modules sit behind it, each with filters and period downloads, open to the directorate’s internal users. Directors and the planning team open it themselves for the current picture instead of filing a request to the data team. SPPG and unit identifiers in these screenshots are masked; the underlying records are internal.
Procurement payment progress — working sheet, digest, and recap
5 photosPayment after procurement used to run on scattered manual records. This working sheet became the single place the payment process is recorded: once a procurement is complete, its payment is entered here, and because the sheet reads the national holiday and joint-leave calendar, every deadline counts working days only. Each working day at 9am the four staff in the directorate’s procurement office receive a digest listing which records still lack administrative documents, which invoices are nearing their deadline, and which are already past it — so chasing and completing documents is something the system raises rather than something someone has to remember. A recap dashboard gives the director the current picture on demand.
Sistem Tiket Kendala — field issue ticketing system
8 photosField problems reached the directorate through WhatsApp, letters, chat, and verbal reports — scattered enough that nothing could be tracked to closure. This system gives every report one place to land: an operational status check for SPPG so an operational fault can be told apart from any other cause, payment matching, a ticket recap dashboard, an activity log, and an escalation contact directory. Access is role-based, so each regional PIC works only their own area.
