MixPilot: Frequently Asked Questions

MixPilot is a non-invasive, self-calibrating sensor that monitors concrete slump and related properties in-transit, from plant to pour, without touching the concrete directly.

Readings improve in accuracy over the first couple of minutes after mixing/water addition; Giatec is working to shorten this window toward about 30 seconds.

Certain mixes only produce reliable readings within a specific drum rotation speed range (roughly 1 to 9 RPM); outside that range, readings may be missing.

MixPilot now supports slump flow calculation for self-consolidating concrete (SCC), in addition to standard slump. Accuracy for high-slump and SCC mixes is still maturing as more data is collected. Dispatch integration (which feeds in mix design and load size) improves results, and performance is validated against field measurements during onboarding.

The system factors in flowability-related behavior, but dedicated viscosity measurement continues to be refined. Confirm current capability for your mix.

Return volume is estimated from drum rotation and load data; accuracy improves with calibration over time.

Yes, remaining volume is calculated and can be displayed to drivers or dispatch depending on configuration.

Yes. Water-addition data can be tracked via a physical water meter/drum counter or manual/dispatch-linked entry.

Approval status can vary by hardware version and jurisdiction. Confirm current status with your rep.

Yes, imperial-unit digital readouts are available in most current hardware; calibration/reset is typically done via the mobile app.

Report specific instances to support; troubleshooting or a hardware check can resolve most issues.

No, this is not currently supported.

Basic flagging capability exists; more advanced automated tolerance/deviation alerting is on the roadmap.

Current support for this is limited in some deployments; expanded alerting is planned.

MixPilot supports integrations with several major batching platforms; specific integration depth varies by partner system.

Support varies. Some integrations are available at a basic/app level only; full data-sync may not be supported for every platform.

In some configurations yes, depending on the integration depth available for your specific telematics platform. We also offer an open API and an MCP.

Some data can flow through existing telematics, but MixPilot’s core sensing hardware is generally still required. Contact your sales rep for more information.

Integration compatibility varies by platform version. Confirm current status with your rep.

Installation requirements vary by truck; your installation team can confirm voltage compatibility for your fleet.

Cable routing follows standard installation guidelines; compatibility is broad across common ready-mix trucks.

Most standard ready-mix trucks are compatible; unusual drum designs should be reviewed with the installation team.

Timing depends on issue type and stock availability; straightforward replacements are typically processed quickly.

Pricing is generally subscription-based, often per truck per month; confirm your plan structure and volume discounts with your rep.

Cost scales with fleet size. Request a fleet-specific quote from your rep.

Giatec is generally positioned around total platform value; ask your rep for a use-case-specific comparison.

It’s a short trial using a limited number of truck units on real batches so you can validate accuracy and value first.

Yes, bundled pricing for MixPilot and SmartMix together is often available.

Timelines vary with fleet size and hardware lead times, but most deployments are phased over several weeks to a few months.

There’s no strict minimum, but starting with a smaller pilot fleet at a single plant is a common recommended approach.

MixPilot is designed to be non-invasive, minimizing warranty concerns. Confirm with your truck manufacturer if you have concerns.

Language support varies and continues to expand. Ask your rep whether your preferred language is currently supported.

MixPilot provides continuous, non-invasive slump monitoring versus single-point manual readings from traditional meters.

Accuracy depends on proper calibration; validate results against your specific mix during onboarding.

MixPilot can help flag anomalies like unexpected water addition, an indirect signal of a batching issue.

Continuous readings are designed to closely track manual spot-checks; periodic validation is good practice.

MixPilot is sold to ready-mix producers who operate the truck fleet.

Adding plants is a configuration and hardware-provisioning step; cost scales with additional trucks/plants.

This can vary. Switching may require reconfiguration rather than a full new fee; confirm with your account manager.

Standard support is included with your MixPilot subscription.

Initial fees may apply, typically to cover implementation work such as dispatch integration setup. Please contact your sales rep to confirm.

Yes, MixPilot is designed to help detect and document unauthorized water additions, supporting QC accountability.

Driver views emphasize real-time status; dispatch/QC views provide broader analytics and historical reporting.

In many cases yes, depending on your specific integrations.

MixPilot doesn’t require calibration to function. The slump algorithm is pre-trained on a large dataset of slump tests across North America and works out of the box once installed. What we do recommend is a validation step: comparing MixPilot’s readings against field slump tests during onboarding (and periodically after, if desired) to confirm accuracy and make configuration adjustments if needed, but that’s validation, not a required calibration step.

Hardware can be moved between trucks with proper reconfiguration in the platform.

Yes, multi-plant fleets can typically be managed and reported under a single unified account.