All BlueprintsLogistics
Fleet maintenance log
A servicing log for a small fleet: every van's history in one place, the next service worked out from how fast that van is actually being driven, and what is due soon and what is already overdue on the front page.
What you’ll build.
A service record for a van fleet. You enter an odometer reading and see when the next service falls due at the rate that van is really driven, sign off the work so the next one counts from the day it was done, and get warned while there is still time to book it in. A van past its date is stopped before somebody drives it.
What you’ll learn.
Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.
Authentication
You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.
Roles and permissions
You can give users different roles and have the server refuse what a role may not do — not merely hide the button — and show the refusal working against a request the interface never offered.
Tracking a delivery
You can record location updates against a shipment and show a customer its current state and history without them refreshing.
Proof of delivery
You can capture proof at the point of delivery, store it against the shipment, and produce it later in a dispute.
Background jobs
You can hand work to a worker, tell the user it is in progress, and show the result when it lands — and say what happens to that work if the process dies halfway.
Search and filtering
You can search a list by keyword, combine that with filters, and say what the database does to answer the query — including which part uses an index and which part cannot.
Notifications people do not mute
You can notify a user when an event concerns them, show an unread count that survives a refresh, and honour a preference that says stop.
Going live
Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.
The roadmap. 8 sprints, 45 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Somebody the fleet belongs to
A yard can make an account and come back to it, a workshop account cannot be issued from the sign-up form, and an account that is switched off stops working immediately.
5 tasks
- A yard can register and land signed in
- Coming back on Thursday does not mean signing up again
- Leaving properly on the office machine
- Workshop accounts exist, and cannot be self-issued
- An account switched off stops working in seconds
The vans and what has been done to them
A yard's vans are on the system with the servicing each has already had, and having a role is not the same as being allowed near a particular vehicle.
5 tasks
- A yard puts a van on the system
- The servicing a van has already had
- The right role, the wrong van
- A driver can enter a mileage and nothing else
- The fleet reads at a glance on a phone in a yard
Due is a projection, not a date
From odometer readings taken whenever somebody remembered, the product works out how fast each van is being driven and says when its next service falls due, whichever of miles and months comes first.
7 tasks
- Somebody writes down what the odometer says
- What the van is due, and roughly when
- Three hundred miles a week and thirty
- A reading taken last Thursday, entered on Tuesday
- A mileage typed wrong, and corrected
- The inspection date is a date, and is not projected
- One reading is not enough to guess from
The clock starts at the work
A workshop signs off the work that was done, with evidence, and the next service counts from the day and the mileage of the work rather than from the day it was planned for.
6 tasks
- The yard books a van in to a garage
- The garage records what was actually done
- The next service counts from the work, not the plan
- The date on the job sheet is not simply believed
- The job sheet is attached to the van
- The yard sees what was done without ringing the garage
Late means you may not drive it
Something works out overnight what has gone past its date, a van that may not legally go out is stopped rather than nagged about, and a van parked up stops counting down.
5 tasks
- Something works out overnight what has gone past its date
- A van that may not legally go out is stopped
- A van parked up stops counting down
- Overnight work that stops running says so
- A reading entered at nine changes the answer at nine
The board in the office
One screen shows the whole fleet in the order it needs working through, holds its order while somebody works down it, and does not quietly lie when it is narrowed.
5 tasks
- The board: what is due, worst first
- Working down three screens without losing a van
- Narrowing the list, without it quietly lying
- Finding one van by part of its registration
- A fleet with nothing due
Told while it is still early
The yard hears about work far enough ahead to book it, in one message rather than eleven, and is never sent to something that stopped being true after the message was written.
6 tasks
- A notice that arrives while there is still time to book it
- One message for the fleet, not eleven
- A van that may not be driven does not wait for Monday
- A message that is no longer true when it is opened
- A notice only goes to an address somebody has proved they hold
- Turning the messages off without losing the urgent ones
Put it where the yard is
The log is on the internet at its own address, the overnight work and the messages run there, the job sheets survive a release, and a bad release can be undone before somebody drives on a wrong answer.
6 tasks
- Nothing it needs lives only on your laptop
- A yard can reach it without you
- The overnight work runs where nobody is watching
- The notices actually arrive
- The job sheets survive a release
- A bad release can be undone in minutes
Read before you build. The best engineers do.
Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.
What you are building
The product, who it is for, and why a due date here is an estimate rather than a fact.
How a fleet's servicing actually works
Domain you will not have: whichever comes first, the inspection that is a hard date, off the road, and what late costs.
More logistics Blueprints.
Tool and asset checkout
A tool store for a small builder's yard. Every drill, ladder and transformer is an individual thing with a tag, the store can say who is holding it and since when, and what has not come back is on one screen before somebody needs it.
Returns handling
The returns desk behind a small shop. A customer asks to send something back and says why, the warehouse answers, a parcel turns up that may not match either, and somebody has to decide what happens to the goods and to the money before either can end up in the wrong place.
Warehouse picking list
Picking for one warehouse: an order becomes a route through the shelves, a picker walks it on a handheld, and everything that goes wrong halfway down the list is recorded rather than quietly shipped.
Build fleet maintenance log.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.