Korea Institute of Green Climate Technology · December 2025 · 1 month
Renewable energy convergence support
The field installer's mobile workflow that the programme's management system did not have.

In short
The existing REMS system held the data the programme required but gave field engineers no way to find a site, connect equipment and record an installation. I reviewed the specification with stakeholders, organised the installer's tasks into one sequence, and turned twelve Figma screens into a working React mobile prototype, including a capacity chart that switches between by-source and total views.
Context
Korea's renewable energy convergence programme funds the installation of several kinds of renewable equipment across a district. Local-government staff administer it and field engineers carry out installations. The programme's management system, REMS, was organised around institutional reporting rather than the people doing the work. This prototype covers the field engineer's mobile workflow. Equipment connection and submission are simulated, and field records are not retained on a server.
- Role
- Project Manager / Service Designer
- Team
- Frontend and backend engineers at KGCT
- Organisation
- Korea Institute of Green Climate Technology
- Timeline
- December 2025 · 1 month
- Tools
- Figma · AI-Figma MCP · React + Vite mobile prototype
What was built
- A mobile installer journey from finding a site through equipment connection, work records and submission
- Separate assigned-work and installation-record views, with site search by region and status
- A capacity-status chart drawn from data, switching monthly growth between by-source and total views
The problem
REMS was built to satisfy what the programme requires, and it did that. What it lacked were the screens field engineers needed for their day: which sites are mine, what needs doing at this one, how do I connect the telemetry unit and record the work. Holding the information a programme requires did not, by itself, give the people in the field a way to act on it.
What I was responsible for
I owned the installer workflow from specification review to a running prototype. I sat with internal stakeholders to settle the specification sentence by sentence, organised the installer's actions into one sequence, generated the screens in Figma through AI-Figma MCP, and assembled them into a React mobile prototype that could be reviewed on a phone. The whole sequence took one month. The scope was deliberately narrow: the installer's journey, not the local-government side.
Decisions that shaped the design
- Two lists for one site. Finding the next task and reviewing an installation record need different status information, so assigned work and installation records are separate views, each carrying only the status relevant to its purpose.
- Filtering has to be easy to undo. Region filters help an installer find nearby sites, and an All option clears the selection in one step so the full list can be browsed again.
- One chart that reads two ways. The programme installs several equipment types together, so the capacity chart toggles between stacked by-source bars and a single total. The bars are drawn from data, so the toggle switches real series, and the cumulative tiles and region grid are computed from the same numbers.


What was built and verified
A working mobile prototype covering the installer's journey from site search to work-record submission, reviewed by stakeholders and engineers on the same screens as the specification. This is the case where the full sequence of specification review, AI-Figma prompt and working prototype was applied end to end: twelve screens delivered in a month. Equipment connection and submission are simulated, so no field adoption figures are claimed.