No, Batch connects to existing COMMANDbatch hardware and ideally running COMMANDbatch v2026.1.0 or higher with internet access at both the plant and user locations. Internet connectivity is required on all devices and compatible browsers are Chrome, Edge, and Safari. Internet Explorer is not supported.

Batch remote access requires internet connectivity. If connectivity is lost, remote users cannot operate through the cloud interface until service is restored. The underlying plant control remains on-premise (i.e., COMMANDbatch), so local operations can continue through on-site batching capabilities.

No, there are no user limits. You are in control of user access. Be sure to check out the packages available and find what works best for you.

Yes, Batch includes an embedded Order module that allows you to create, view, and update orders—and create tickets—directly in Batch. Tickets can be accepted, batched, adjusted, and completed without needing separate access to a Dispatch system. Tickets can also be sent from external dispatch systems into the existing on-prem environment and then executed through Batch.

You will not lose the visibility you rely on today. For reports that have not yet been developed in Batch, your on-prem system remains in place, so that information is still accessible during the transition. In practice, this means nothing is lost, though some reporting may continue to live across both the cloud and on-prem environments until everything is fully built out in Batch.

Batch in Command Cloud continues to expand its dashboard’s widgets and reporting capabilities. Many of the insights that are used today are available directly in the cloud experience.

Batch has a modern, unified interface to operate multiple plants—regardless of whether the underlying on-prem system is COMMANDbatch or Marcotte Batch—without relying on remote desktop tools. It improves operator mobility, standardizes workflows, strengthens security/auditability, centralizes configuration, and tightens integration with Command Cloud services without disrupting your plant operations.

Plant operation access is governed in the cloud through user roles/permissions and auditability. However, for safety reasons if a location batcher needs to take control of a plant, they can log in locally, and it removes the cloud operator automatically.

We highly recommend workflow integrated streaming camera systems and/or driver discharge authorization boxes. It is not recommended to remotely operate a plant without one of those systems in place.

Batch supports integration with several Camera VMS platforms. If the VMS is hosted inside your network, it must be securely exposed for cloud access. While Command Alkon does not sell, setup, or support your camera systems, we can provide referrals to camera providers.

Recommended views include the truck under the batch boot, the mixer/discharge area, key scale areas where visibility is useful, and general yard/traffic flow plus any areas where remote oversight is needed to safely remote batch.

Batch in Command Cloud ROI is most often realized through labor efficiencies and coverage. Producers can better leverage a smaller group of experienced operators and technical experts across multiple plants, reduce reliance on a single local “power user,” and improve coverage for breaks, vacations, and off-hours without adding headcount.

These labor gains typically stack with fewer disruptions: faster issue resolution, fewer unplanned site visits, and more consistent processes that reduce errors, rework, rejected loads, and material waste. The result is a more flexible operating model where efficiency and consistency drive the business case.

1. Tablet-ready batching – batch securely from a tablet anywhere (yard, loader cab, maintenance shop, office), not just the batch room.
2. Multi-Plant Remote Batching (MPRB) – manage and batch production at any number of plants from a single, intuitive interface, no matter where you are.
3. Increase operator confidence using integrated workflow cameras inside the batching experience for remote decision-making.
4. Centralized control of standards – manage materials, mix designs, and plant configuration from one place and push consistency across locations.
5. Role consolidation with tablet batching – keep production moving with fewer dedicated “chair time” operators (ex: FEL operator can batch).
6. Maintenance and manual operations go mobile – handle needed manual interactions from tablet workflows without being tied to the batch PC.