A
Academic / GEA-Spin Student project
Contact
100% ▾
PAGES
Home Academic / GEA-Spin About
CASE STUDIES
Disputes Workspace 360 Control Design System CPQ Academic · Eco-Cash Academic · GEA-Spin Academic · Studytable
SECTIONS
00 · Cover
01 · Overview
02 · My Role
03 · The Problem
04 · Research
05 · Insights & Personas
06 · The System
07 · The App
08 · Model & Reflection
PROJECT
GEA-Spin
contextIUPUI · Enterprise Systems
roleResearch + Service Design
domainConnected IoT
platformMobile + Cloud
scopeProduct + Service
HIGHLIGHTS
10
stakeholder interviews
3 + 5
direct & indirect competitors mapped
$3,600
modeled weekly revenue / site
UP NEXT
Studytable →
capstone · choosing a major
ACADEMIC WORK · INDIANA UNIVERSITY 01 · Eco-Cash 02 · GEA-Spin 03 · Studytable
◇ 00 · Cover
CASE STUDY · ENTERPRISE SYSTEMS

GEA-Spin: turning dorm laundry into a connected, revenue-sharing service

GEA-Spin reimagines university laundry as a connected service. GE Appliances washers and dryers, an IoT gateway, a cloud platform, and a student app come together as a single Laundry-as-a-Service system: students book and pay from their phone, facilities teams see machine health in real time, and the university earns a share of every cycle.

GEA-Spin connected laundry concept
◇ 01 · Overview

Project overview

The product

GEA-Spin is a connected laundry service for university housing. Smart GE Appliances machines report their status to a cloud platform. Students use a mobile app to find an open machine, run a cycle, and pay without coins or cards. Facilities staff get maintenance alerts and usage reports, and detergent is supplied through a P&G partnership built into the app.

The mandate

This was an enterprise systems project at IUPUI. The brief was bigger than an interface: design a product, a service, and a business model that hold together. I had to think about machines, cloud infrastructure, three different users, and the economics that would make the whole thing worth building.

DESIGN GOAL

Make campus laundry effortless for students and visible for facilities teams, while giving the university a reason to say yes: a connected service that pays for itself.

◇ 02 · My Role

My role

I worked across the whole system on this project: running the research, building the personas, mapping the service and its architecture, designing the student app, and modeling the revenue case that justified it.

The hardest part was not the screens. It was holding three stakeholders, a piece of hardware, and a business model in view at the same time, and making sure a decision that helped one of them did not quietly break another.

User research Competitive analysis Service design Systems architecture App UI Business modeling
◇ 03 · The Problem

The problem

Campus laundry is one of those services everyone tolerates and no one owns. Machines break and stay broken. Payment means coins or a separate card. Students walk over only to find every machine full. Facilities teams have no idea a machine is down until someone complains. Meanwhile, student housing is a large, growing, and nearly full market, which is exactly why a better service could pay for itself.

MARKET 01

23M students

NCES projected the US student population would reach 23 million, a large captive base living in managed housing.

MARKET 02

$11B invested

Annual student-housing investment more than tripled since 2014, reaching $11 billion by the end of 2018.

MARKET 03

95% full

On- and off-campus housing stayed consistently full, with 2018 occupancy around 95%. The demand is reliable and recurring.

Market research on student housing growth
◇ 04 · Research

Research & discovery

I needed three angles to understand this space: how competitors solved it, what the market looked like, and what the people who actually live with campus laundry had to say.

METHOD 01

Competitive analysis

Mapped three direct and five indirect competitors to find the patterns everyone shared and the gaps no one had filled.

METHOD 02

Stakeholder interviews

Ran 10 semi-structured interviews with students, dorm and property managers, and resident advisors across IUPUI and the University of Cincinnati.

METHOD 03

Market research

Studied housing and technology trends to understand where the market was heading and what it was ready to adopt.

Who I talked to

Three stakeholder groups: students, property managers, resident advisors
Three stakeholder groups: students, property managers, and resident advisors, recruited across IUPUI and the University of Cincinnati.

How the process ran

Design process from market study to final design
Study the market, interview, categorize, compare, map empathy, draw mind maps, then design, with each step feeding the next.
◇ 05 · Insights & Personas

What the interviews kept surfacing

Affinity mapping

Affinity map grouped into maintenance, expectation, limitation, existing system and cost
Grouping the interview notes surfaced five themes: maintenance, expectations, limitations, the existing system, and cost.
1.

Maintenance is invisible until it fails

Nobody knew a machine was broken until a student found it broken. Facilities teams were reacting to complaints instead of seeing problems coming.

2.

Payment is friction

Coins, a separate laundry card, a top-up kiosk. Students wanted laundry to cost what it costs and to pay the way they pay for everything else: from their phone.

3.

Cost and sustainability pull together

Facilities staff cared about energy use and the cost of replacing old appliances. A connected system that runs efficiently and lasts longer answers both at once.

4.

Three users, three jobs

Students want a clean, easy cycle. Facilities want machine health and fewer surprises. The university wants a service that does not cost it money. The design had to serve all three.

Personas

Persona: Sarah Hopkins, undergraduate student
Sarah Hopkins, a sophomore living on campus. Wants reliable machines, easy payment, and a budget that lasts the semester.
Persona: Alex Franklin, facilities coordinator
Alex Franklin, a facilities coordinator. Wants safe housing, lower energy use, and a smart system he can actually maintain.
◇ 06 · The System

The system

GEA-Spin is not an app with some machines attached. It is a service. Connected GE Appliances washers and dryers send their status through an IoT gateway to the GEA cloud, which talks to the student app, the facilities team, and a P&G detergent supply line. Each piece has a job, and the cloud is the hub that keeps them in sync.

Service architecture

GEA-Spin service architecture connecting housing, cloud and the facilities team
University housing, the GEA cloud, and the facilities team, connected by preventive maintenance, scheduling, reporting, and payments.
IoT gateway connecting the customer cloud to the GEA cloud
The IoT gateway bridges the customer cloud and the GEA cloud, with P&G supply and machine telemetry flowing through it.

The facilities side of the service

For someone like Alex, the value is visibility. He checks machine status across the dorm, sees which machines need attention, dispatches his team, and sends a weekly report to property managers that shows usage and the revenue each machine earned.

Storyboard of the facilities manager maintenance flow
A facilities manager's day: check status, triage maintenance, message the team, report up, and track usage and revenue per machine.
◇ 07 · The App

The student app

For students, the whole service collapses into three things: find a machine, run it, and keep detergent stocked. Each flow is built to be done in a few taps, with payment handled automatically so no one has to think about coins again.

FLOW 01

Schedule a pair

See every available washer and dryer in the building, book a pair, and let the app charge you automatically when the cycle starts. No machine roulette, no kiosk.

App screens for scheduling a washer and dryer pair
App screens for setting laundry cycles
FLOW 02

Set the cycle

Pick the wash and dry settings for the order and start it from the phone. The machine confirms, and the app tracks the run so students know exactly when their laundry is done.

FLOW 03

Restock detergent

Buy P&G detergent right inside the app at 25% off, paid the same cashless way. The supply partnership is what turns a hardware service into a recurring one.

App screens for purchasing detergent

The facilities dashboard

Facilities dashboard for machine usage and revenue
The other side of the same data: machine health, usage, and revenue, in one view for property managers.
◇ 08 · Model & Reflection

The number that makes it real

A service only gets built if the economics work. So I modeled a single site to see whether GEA-Spin could pay for itself and still hand the university a cut. It can.

WORKED EXAMPLE · UNIVERSITY OF CINCINNATI
Residents400
Washer / dryer pairs8
Cost per cycle$5
Cycles / week (2 per student)800
Weekly revenue$4,000
THE SPLIT
University share (10%)
$400 / week
GEA-Spin revenue
$3,600 / week

The university earns for doing nothing but saying yes. That is the hook that makes the whole service adoptable.

Revenue calculation breakdown
REFLECTION

GEA-Spin was the first time I designed a whole system instead of a screen flow. Hardware, cloud, three stakeholders, and a business model all had to fit, and the lesson stuck: a good interface does not save a service whose economics or maintenance model are broken. If I ran it again I would prototype the facilities dashboard with a real property manager early, because that side carries the value and I treated it as secondary for too long.

NEXT · ACADEMIC WORK 03
Studytable: helping students choose a major with confidence
© 2026 Abhikant Nirbhavane case study · gea-spin