Equipment and business capabilities · Metrology examples
Plan the collection, follow the route and preserve the handover.
Connect customer pickup requests, delivery stops, driving order, destination details and recorded outcomes to the equipment and service behind the trip.
Pilot / Early Access Asset by MetraSlate, AssetLight by MetraSlate and Standard by MetraSlate: Metrology Edition. How Evaluation Works
01Request collection
02Confirm the stop
03Plan the route
04Follow the sequence
05Record the handover
06Continue the service
Logistics dispatch schedule
Review scheduled runs, pickup and delivery stops and the details of the selected route.Interface preview · sample data · 24 October 2026.
Logistics starts with a customer and a real destination. Pickup and delivery records retain the site, address, requested or scheduled date, collection window, notes and the work they support. A customer portal request becomes the lab's stop record, giving dispatch a direct starting point.
The control tower, dispatch queue, route record and company-routes view read the same logistics records. Staff can inspect waiting work, open a planned run and follow its stops without maintaining a second list for the driver.
The collection request already belongs to the customer's account.
A customer requests collection at a site their portal account is authorized to use. The preferred day, optional collection window and note enter the lab's actual logistics record. An address is required so the request describes a place the driver can reach.
The lab can then confirm operational details, connect equipment and related work where appropriate, and move the stop through its permitted states. The readiness check includes the required map pin and payment-readiness state before dispatch.
The work order
Each instrument retains its progress within the same customer order.Standard by MetraSlate: Metrology Edition demonstration data · Captured 21 October 2026. Confirm the screens and workflows in your pilot configuration.
The route is a plan the whole team can inspect.
A planned route identifies the origin lab, date, driver and stop order. Changing the day also changes the linked stops' scheduled day. Reordering checks that the request includes the route's complete current stop set, and a concurrent mismatch refuses the change instead of leaving a partly rewritten sequence.
A dispatcher can split part of an oversized planned run into another run or change its driver before departure. Once the run has left, the plan is protected from those desk edits so the route the driver is following does not change silently.
The driver follows the sequence and the next unfinished stop.
The company-routes view lets staff select a day, route and stop. A permitted driver can narrow the view to assigned routes. The selected stop shows the customer, address, collection or delivery window, contact details and the next actions available for its current state.
Navigate opens the destination in Google Maps on the device. The route also offers a map view where the map connection is configured, while the ordered stop list remains a direct way to inspect the driving sequence. Route estimates combine returned driving legs with the stated service allowance for each stop.
The outcome keeps the physical handover accountable.
Confirming pickup or delivery records who signed for the handover and can retain its supporting note. A failure or cancellation records its reason. Legal transition checks keep a stop from being moved through a state the workflow does not permit.
The movement becomes part of the operating history and can supply a workflow event for the next step. Staff can distinguish a planned collection, a recorded pickup, laboratory receipt, finished calibration and equipment return as different parts of the same service.
Equipment history
Follow the individual instrument through its service history and supporting records.Standard by MetraSlate: Metrology Edition demonstration data · Captured 21 October 2026. Confirm the screens and workflows in your pilot configuration.
In everyday use
What your team can do.
Follow the record, the decision and the person responsible for the next step.
Pickup requests become operational stops.
The portal validates the customer's site and address, then creates the same pickup record used by the lab's logistics workflow.
A route records its driver, day and sequence.
The dispatcher plans from an origin and places existing stops in driving order, with the server retaining the resulting route.
A plan can be revised before it leaves.
The planned run supports a different day or driver, reordered stops, added or removed stops and a split into another run.
The next stop retains the customer's context.
The route and company-routes views show destination, window, contact and recorded progress. Navigate hands the destination to Google Maps.
Handover outcomes retain evidence.
Pickup and delivery confirmations require the signer's name. A failed or cancelled stop carries the required reason.
Recorded movement can inform the next workflow step.
Permitted status changes retain movement history and a workflow-dispatch intent with the operational change.
Related capabilities
Keep Following the Work.
A conversation about your work
See it with your own workflow in mind.
Start with your items, your business, and the processes you need to manage. We’ll help you identify the right product.
