Container inventory and tracking
Give every container a usable operating record.
Container availability connects sales promises to dispatch decisions. A can may be at a yard, committed to a job, on rent, awaiting pickup or held for inspection. TossDock Pro helps qualified large-scale operators evaluate that workflow in one workspace; the public demo shows how the records fit together.
Define a consistent container identity
Begin with the identifier the yard, driver and office will all use. Reconcile duplicate or missing numbers before importing inventory. Size, type, ownership and any service restrictions should be understandable to the people making an assignment. Agree who corrects a record when a physical can and its recorded details disagree.
- Use an identifier that can be checked in the field.
- Review retired, damaged and temporarily unavailable containers separately.
Connect availability to the current commitment
Review the current rental and the next expected service before promising a container to another customer. A planned pickup can change, and a returned can may need inspection before reuse. During acceptance, test how your team distinguishes an expected return from availability it has actually confirmed.
- Check open jobs and rental dates alongside the container record.
- Agree which events change availability and who can override an exception.
Review the age and source of an observation
A location or fill observation is useful when its source, time and limitations are understood. An old device report should prompt a check before the team relies on it. TossGauge remains a Pilot for camera-assisted observation; TossTrack remains a hardware pilot. Neither label is a promise of continuous coverage or measured accuracy.
Scope hardware around field conditions
Digital Matter Oyster3 for containers and a G70 BLE device for trucks are candidates under evaluation for the hardware pilot; no device has yet been validated against real hardware. Device suitability, installation, carrier coverage and field reliability require validation. Hardware, connectivity, replacements and any installation work belong in the proposal so their responsibilities and costs are clear.
Prepare the conversation
Prepare an inventory review
A useful assessment begins with how your cans are identified and used, including the records that need cleanup.
- Container counts by size and type, plus yard locations.
- Your identifier format and known duplicate or missing records.
- Current rental statuses, return expectations and inspection holds.
- Existing devices, coverage concerns and the decisions their data must support.
Use this in an evaluation
Review exercise: an expected return is delayed
Choose an example container that is due back and a job that could use it next. Delay the pickup, then trace how the office would revise availability and select a different can. Include the yard team in the review so the process covers physical readiness as well as the schedule.
- Identify the current rental and next commitment.
- Check an alternative container for size, readiness and restrictions.
- Record the owner of the correction and confirm the updated plan.
Common questions
Does every container need a tracker?
The operating inventory and hardware scope are assessed separately. Device requirements depend on the accepted workflow and field validation; the public demo does not establish that hardware is installed or reporting.
Does a fill estimate mean a container is ready for pickup?
The operator makes that service decision using the customer agreement, material rules, access conditions and available evidence. Pilot observations support review and should not be treated as a guaranteed measurement.
How should we test container software before launch?
Trace a representative can through delivery, rental, pickup and return. Include a delayed pickup, an inspection hold and a stale observation. Check that the people promising availability can explain the current record.