Tenant Logo

What a Contract Is

Pick the contract, and the job pack does the rest

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.

1 · WHO GETS IN Hub workgroup T-FI-HPR-01 No members: the contract's door. It lists who may enter. FI_Owner Nicola Barnes · T-Client (engineering) approves every arising-work decision FI_Depot_Management Conor Byrne · H-Manager (depot manager) Yvonne Ashworth · team leader FI_Depot_Team Lee Harding, Patrycja Zielinska, Marcus Oduya · C-Mech examiners trusts stamps every record made under the contract 2 · THE JOB PACK (SET UP ONCE) Contract register FI-HPR-01 the terms: the owner approves every arising-work decision; frozen by the depot manager Scope of work FI-HPR, issue 1 three jobs, one per regime: trip inspection weekly, 22 tasks; maintenance 6-monthly, 101; inspection and brake test yearly, 113 Fleet (subjects) forty bogie hopper wagons, FI 81001 to 81040, one vehicle each, from the fleet numbering register Documents FI-VMI-HPR-001, the maintenance instruction, as doc 1: every task cites its clause and page Tools register the depot's gauges with calibration dates and the connected torque tool; an out-of-date gauge is refused Materials register brake blocks, split pins, grease: what a sign-off may book against the job, with the part's serial Asset map the wagon drawn: 18 components, 52 points, where every reading sits on the vehicle pins lists every record below reads the pack: tasks, limits, tools, parts, positions an examiner picks the contract and the wagon; nothing else is typed 3 · THE WORK MADE UNDER IT (ONE WAGON SHOWN) Visit: work order 81006-V1 six-monthly maintenance, launched by the depot manager; one per wagon per visit, with its records and freeze Sign-offs two parts, 101 tasks, readings against limits, split pins renewed and booked as material; the examiner signs Arising work (defects) brake block below the 15 mm limit: raised by the examiner, decided by the manager, approved by the owner, closed Queries and alerts an examiner's question with a sketch, answered by engineering; messages acknowledged by name launches a sign-off cannot freeze with its arising work open Wagon dashboard every job on the wagon ticked, hours booked against planned; frozen by management once the wagon is done Work order freeze the wagon returns to traffic once its sign-offs are frozen and no arising work is open DocPack for the owner every sign-off, defect and dashboard of the visit in one signed PDF; a KPI page every week roll up issues the whole visit, found again from the Navigator by contract and wagon; the flange trend chart reads across visits Fourteen visits under this contract: thirteen frozen with signed packs, one in progress; eight arising-work records, all closed.

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.

1 · WHO GETS IN Hub T-SFCR-149-01 One door for survey and repairs: the same three groups see both. The fleet's owner Eleanor Vance · T-Client structures Engineer: referrals, witness Ravensby: management Mark Holloway · H-Manager Sarah Quinn · C-RWC, C-QA Ravensby: the team Mercer, Nowak, Malik, Finch: survey, weld, NDT, paint trusts stamps every survey, finding and repair 2 · THE JOB PACK (SET UP ONCE) Register SFCR-149-01 the owner authorises each repair; an overrun beyond 20 per cent is a variation; fleet: Class 149, four units Specification, issue 2 SF-CR-PR-001: repair codes R1 to R9, reference lengths, member thicknesses; 46 clauses, each cited by page Survey template, issue 3 a finding records member, thickness, size factor, witness, who may raise; plates: the car's structure drawings Documents and welding the welding procedures and the welding requirements, read from Ravensby's document control Scope SF-CR-149 (visit) the visit's own jobs: strip-out and the camber check, read against each other (after within 4 mm of before) Scope SF-CR-149-REP nine repair jobs, one per code: weld, test and paint tasks with sign roles C-Weld, C-NDT, C-Paint Tools, materials, KPI as on any contract: the gauges, the consumables, the weekly page of findings and repairs pins codes become jobs a finding is classified with the specification's codes; its repair reads the matching job the surveyor picks the contract and the unit; the plates and the codes are already there 3 · THE WORK MADE UNDER IT (ONE UNIT SHOWN) Survey: unit 149904 coverage marked plate by plate: inspected, clear, or not accessible until strip-out Findings on the plates a photo on the drawing, coded R1 to R9, thickness in mm; an unclear one is referred to the owner's Engineer Work order 149904-V1 the repair visit, launched by the planner once the findings are coded; one per unit; holds its records Repair sign-off per finding weld, MT or UT test, paint, each signed by its trade; a defect found is raised back on the survey holds the coded findings launch the visit one sign-off per finding defect found during repair: a new finding Finding accepted once its repair sign-off is frozen; the owner's Engineer witnesses the hold points she asked for Work order freeze hours booked against the estimate; an overrun past 20 per cent is a variation the owner authorises DocPack for the owner survey, every finding with its photos, every repair with its evidence, in one signed PDF repair frozen all accepted issues a second survey of the same unit lists the deferred findings and marks a repeat on the same area Units 149903 to 149906 surveyed under this contract; on 149904 every finding is repaired, tested and accepted. The class and its units are fictitious, as Ravensby is.

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.

Your specification, running live.

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.

Send us your specification