Work Order System
Manages the maintenance of industrial equipment, from arrival at the workshop to the report delivered to the customer.
- My role
- Only developer, from the start as an intern through to production: specification, backend, frontend and deployment.
- Technologies
- .NET 10 · React 19 · TypeScript · PostgreSQL · Docker · Azure DevOps · Spec Kit · Claude Code
- Under review
- Awaiting quote
- Awaiting parts
- In progress
- Final checks
- Delivered
The problem
CRC Equipamentos tracked each work order on paper, Trello and spreadsheets, and put together the customer report by hand. To find out where an order stood, someone had to ask around.
What I delivered
- A single work order flow that records who did what, and when, at each stage.
- A technical checklist with per-part scoring that works out whether a repair is worth it.
- Evidence photos annotated straight from a phone, and a PDF report generated by the system.
- Kanban board, operations dashboard, role-based permissions and parts import from Excel.
- 358 automated tests and continuous delivery with Azure DevOps and Docker.
Technical decisions
Checklist frozen on delivery
When a work order is delivered, its completed checklist becomes an immutable copy. Changing the template later does not alter the history.
Trade-off: checklist templates need versioning.
One contract between API and frontend
React types and calls are generated from OpenAPI with Orval. An API change shows up as a compile error, not as a bug on screen.
Trade-off: one extra generation step for each change.
Outcome
In production at CRC Equipamentos, after three versions delivered and validated in acceptance testing.
Built at Rumo Soluções: the code and screens are not public.