CE Formula One
Live numbers from the machines and the shift's duties and quests, on the same screen above the line.
- Client
- CE Produkter AB
- Status
- Active
- We built
- Dashboards, duty roster, quests, feed, and admin panel
Overview
CE Produkter's factory runs on CE Formula One, the system we built for them. This is version 1.0, and it's in use on every shift: on 4K panels above the lines, on tablets, and in people's pockets.
The challenge
Production numbers, the week's duties, and the day's tasks had to be in front of everyone on the floor, on every shift. The duties were typed by hand into text boxes every week, and nothing was saved.
What we built
A factory system on Nexus: numbers live from the machines next to the shift's schedules, quests, and bookings, plus a feed, messages, and files.
How it's used today
Version 1.0 runs the factory today, on 4K panels above the lines, tablets, and phones.
The screens show production as it happens. Signals from the machines, and orders from the ERP fetched through Nexus, become widgets for rate per hour, kilos produced, waste, stop time, oven temperature, and the countdown to the next changeover. CE builds its own screens from those widgets, so the panel above a line shows what that line needs.
Next to the numbers sit the people. The duties used to be text boxes on the dashboard that were rewritten by hand every week, nothing was saved, and the system had no idea who did what. Now the roles are set up once, the week fills itself in, and the screen that shows how fast the line is running also shows who has which duty this week and what is left to do today.
Formula One has grown one request at a time while the factory kept running: the duty roster, quests, a feed and messages, shared files, and push notifications all came after the first dashboards. We still run it and look after it.
What came next is called Formula. Everything in 1.0 was made for CE, every screen, table, and rule, which is why it fits and why no other company could use it. So we took what the floor taught us and started a separate product. In Formula, dashboards, schedules, quests, booking, and chat are modules a company switches on, every customer gets its own instance and database, and all factory data comes through Nexus. Formula is not released yet, but it starts from something that proved itself in a working factory first.
How we built it
All of it was built for a factory in full production. This is how it works for the people at the lines and the people running the shift.
Screens CE builds themselves
Every screen is put together from widgets for rate, kilos produced, waste, stop time, oven temperature, the current order, and the countdown to the changeover. A widget that turned out well is saved as a template and reused on the next line.
The rate comes from the saw
The system times the gaps between the machine's cut signals and turns them into kilos an hour with the unit weight from the order in the ERP. It uses the median, so a short stop doesn't drag the number down for several cycles afterwards.
Readable across the hall
Big numbers and high contrast, in CE's racing style. The rate widget is a speedometer, and when a line runs flat out it goes up in flames and the needle starts to shake.
Quests that hand themselves out
Cleaning, safety, and maintenance go each day to someone working the shift, taking turns so it stays fair. With continuity switched on, the same person keeps a quest all week. Whatever isn't done by the end of the shift counts as missed.
The quest board on the floor
The supervisor drags a quest onto a person, or adds a one-off task for today only. The person gets a notification, ticks it off on their phone, earns XP, and can share it with a colleague who helps out.
A duty roster that rotates
Roles like machine operator and pallet picker are set up once and copied every Monday. The system suggests who takes which duty so the load is shared fairly, and keeps the history, so you can see who had what in week 14.
When someone doesn't turn up
If the person holding a duty hasn't clocked in, the system first warns, then tries to hand the duty to someone else on the roster. The quests that belong to the duty follow it to whoever takes over.
One app for the whole floor
A feed, messages, and shared files, with push notifications on computers and phones, iPhones included.
An admin panel for what changes
Lines, shifts, roles, quests, and the skill matrix are set up by CE's own admins, without waiting for us.
- .NET
- SvelteKit
- TypeScript
- PostgreSQL
- WebSockets
- NIT Nexus
- Docker
Gallery
Key metrics
- Runs CE's factory today
- 1.0
- What CE works in on every shift, and the ground that Formula, what came next, is built on.
- Panels above the lines, plus tablets and phones
- 4K
- A panel on the floor always shows the shift that is running, the night shift too after midnight, without anyone touching it.
- Before an absent duty holder is replaced
- 84 min
- On an eight-hour shift. If whoever holds a duty hasn't clocked in, a warning comes after 24 minutes, and after 84 the system tries to hand the duty to someone else.
Got a system everyone's waiting on?
Tell us what you want to build and we'll take it from there.
Next project
Product configuration · 3D & visualization
