Vehicle yards
Vehicle yard software: separate location from readiness
Evaluate vehicle yard software with a receiving, preparation and release checklist. Understand recorded positions, inspection evidence and Virtual Yard beta.
Knowing where a vehicle is parked does not tell you whether its receiving inspection is complete or its preparation work has been reviewed. A useful vehicle-yard demonstration should connect those questions without pretending they are the same state. Start with the physical handover and work back to the records required to support it.
Map the work before drawing the yard
Choose one incoming batch and describe the work between arrival and release. Your process might include receiving, condition inspection, preparation and a final review. These are examples for discovery, not a mandatory sequence: configure the operations around the work your team actually performs.
- Who confirms the identity of an incoming vehicle?
- Which inspection or checklist must be recorded?
- Who reviews unfinished or disputed work?
- What must the next team receive before the physical handover?
Keep a location record in context
The Stevedoring App's Virtual Yard beta supports layouts, reservations, recorded movements and occupancy. A recorded position reflects the information entered into the system. It is not automatic discovery of the physical vehicle, and it should not be presented as GPS, RFID or telematics tracking.
During a demo, ask who records a move and how the office checks the result. Include a vehicle moved without the expected record so the team can discuss its reconciliation process. Confirm current release availability, permissions and mobile access before depending on a yard workflow.
Make preparation evidence easy to review
Configured operation steps and inspection checklists can support a preparation or pre-delivery inspection process. They do not turn the platform into a complete workshop system for parts, labour, warranties or invoicing. Keep those responsibilities explicit when deciding which records belong here and which remain in an existing system.
Review the vehicle's recorded work and condition evidence separately from the site's decision to release it. A supervisor still applies the business's acceptance rules; a photograph or completed checklist is supporting information, not a universal readiness certification.
Run a bounded yard exercise
- Choose a small area and an anonymised set of vehicle records.
- Represent the relevant places and configure the receiving and preparation work.
- Record an ordinary arrival, a condition exception and a subsequent move.
- Review what the office can see and which records are still missing.
- Generate the relevant inspection report and assess whether it supports the next handover.
Write down the pilot's unanswered questions
Record questions about device access, connection requirements, staff responsibility and existing-system handoffs. If a location update or required task is missing, agree how the team will detect and correct it. This is a more useful pilot output than a promise of a live digital twin across every site from day one.
Questions to clarify
Does Virtual Yard find vehicles automatically?
No. Virtual Yard is a beta capability for recorded layouts, positions and movements, not automatic vehicle tracking. Confirm access and rollout for your intended users.
Can it replace our workshop system?
Do not assume that. Configured work and checklists can support preparation evidence, but parts, labour, warranty and workshop accounting requirements need a separate assessment.