Everything in SmartFleet happens under a contract. A contract is the job pack: it says who is on the job, which vehicles, what work is specified, which tools and parts are on the list, and where each record sits on the vehicle. Every record you make under it inherits those answers, so you never type them.
You meet the contract in one of three ways, and you only need your own slice
On the shop floor: the contract is one drop-down. Pick it, pick the vehicle, and the sign-off opens with its tasks, limits, tools and parts already there.
Running the job: the contract is your register and dashboards: documents, fleet, progress, defects waiting on a decision, the weekly KPI page, the pack for the client.
Setting it up: once per contract, one person fills the register and its lists. The two drawings below show everything that person creates, and nothing more.
A MakeIt contract: Freight International's hopper wagons
Freight International is a fictitious freight operator with forty bogie hopper wagons and a depot that maintains them to its own maintenance instruction. One contract holds all three regimes, so each wagon's whole history is in one place. Read the drawing top down: the hub decides who may enter; the job pack is filled once and frozen; every record in the bottom band is stamped with the contract and reads the pack. An examiner sees only the bottom band and chooses the contract from a list.
A CheckIt contract: Ravensby's corrosion survey and repair
Ravensby Rail Engineering is a fictitious body repair contractor surveying corrosion on a fleet owner's diesel multiple units, a fictitious Class 149, under contract SFCR-149-01. The same frame as the wagons. What differs is the pack: a specification whose repair codes become repair jobs, a survey template with the car's structure drawings as plates, and two MakeIt scopes. The bottom band shows why one hub serves both wraplications: a finding on the survey launches a repair sign-off, and the finding closes only when the repair is frozen.
The shape is always the same
Who gets in is one hub workgroup per contract. It has no members; it trusts the people workgroups of the companies on the job. Nobody outside those groups can open a record stamped with the contract.
The job pack is a register plus its lists: the scope of work or survey template, the fleet, the tools, the materials, the asset map or plates, the documents. Filled once, frozen, and pinned by issue, so a record made in March still reads the March scope.
The work is every record made under it, each stamped with the contract and found again by contract and vehicle. A sign-off, a finding, a repair, a dashboard, a pack: all of them inherit the pack rather than repeat it.
So the end user's whole model is: pick the contract, and the job pack does the rest.
Send us one of your maintenance specifications, procedures or checklists, or the engineering problem you want solved, and we'll show it to you working in SmartFleet: your tasks, your limits, your signatures.