New vehicle
Sales can add it to a queue; the workshop clock starts at 1. Inward IQCWorkshop board
Click a vehicle to move it to the next stage, log a QC result, or flag a blocker.
Vehicle invoice list
One row per vehicle. The monthly report and its click-through are built from this list. Inward date fills in automatically when the registration matches a vehicle in the workshop.
Import invoice list from Excel
Reads the “Invoices” sheet of the OTO templateMonthly totals without vehicle detail
Used only for months with no vehicles in the list above · Total qty = the three columns added upTargets
Editors can change these. Every dashboard uses them.Lists
Weekly build plan
Planned builds and capacity per week (Monday start). Built comes from the vehicles.Sample data
Sample vehicles are there so every dashboard has something to show. Remove them before real logging starts.
Parts stock
Stores sheet, tab “Exponent”: Part name, OEM Qty/Veh, % Usage / vehicle, Current StockThe stores sheet sends its stock here automatically every 15 minutes (or from its OTO → Send stock to OTO app now menu). To load it by hand instead: in Google Sheets, File → Download → Microsoft Excel (.xlsx), then choose that file here. Either way, the whole list is replaced.
Vehicle BOM
“OTO Full Product vs Service BOM”, tab “OTO Full vehicle”: TC PN, Part Name, Parent Part Number, BOM Category, Qty used/Vehicle, ERP AvailabilityTo update: in Google Sheets, File → Download → Microsoft Excel (.xlsx), then choose it here. Saving replaces the whole BOM. Costs are never copied. Stock for these parts will come from ERP.
Import past data from Excel
Use the OTO past-data template: one row per vehicle, start and end time for each stepGive someone a dashboard
What each role can do
| Role | Can |
|---|---|
| OTO Lead | Everything, including Access and private suggestions |
| Supervisor | Log work, enter component IDs, undo, Setup, invoicing, import |
| Technician / team | Log work at their steps; my-work dashboard |
| Head of After Sales | After-sales dashboard, invoicing, logging |
| Sales Ops | Sales queues (add vehicles, finance approval, hand over to IQC, delivered), vehicle details, invoicing |
| Board | Board summary only (no vehicle-level data) |
| Org-wide | Programme summary only (no vehicle-level data) |
People and their dashboards
How the pieces fit
- Console (the backend). Technicians and supervisors log each vehicle event here: arrival, stage complete, QC pass or fail, blockers. Every action is saved with a timestamp and who did it.
- One shared database. Each vehicle is one record holding its full stage history. Setup holds the targets and lists, Roles holds who sees which dashboard, and your private area holds your notes and analyses.
- Dashboards (the frontend). These only read data. Each role gets a different view of the same numbers, so Board, After Sales and the hubs never disagree.
- Access. Sign-in is Google, @exponent.energy only. Roles are enforced by the database: Board and Org-wide users only ever receive summary numbers, and the lead’s private notes can’t be read by anyone else.
How each number is calculated
| Metric | Definition |
|---|---|
| End-to-end TAT | Dispatch done − arrival, in days |
| Stage time p50 / p90 | Median / 90th percentile hours per stage visit |
| First-time-right | Dispatched with zero QC fails ÷ all dispatched |
| Stuck | Time in current stage > 2× its target |
| Hours lost | Σ max(0, stage time − target), rework included |
| On-time | Dispatched within the SLA |