Skip to content
Sectors

The customers that turn cement into concrete.

Ready-mix operators, precast plants and concrete products manufacturers buy cement on consistency as much as on price. TwoSuns connects mill output, quality results, silo stock, loading and the commercial terms behind each account, so the plant can read what it is sending a customer before the tanker leaves.

Request a Technical Conversation Explore the Platform
Who they are

The concrete customers that buy from one cement plant

A tonne of cement leaves the bulk loading bay or the packing plant and enters a process the producer does not run. Each of these customers mixes, cures and tests it differently, and each judges the cement on a different result.

Ready-mix operatorsRegional batching plants running dozens of approved mix designs against site schedules, where workability and setting are judged at the pour and strength days later.
Precast element plantsBeams, slabs, pipes and segments cast to a cycle, where demoulding time depends on early strength and on heat development in the element.
Concrete products plantsBlock, paving, kerb and pipe lines running dry cast mixes, where demould strength, surface finish and colour are the acceptance criteria.
Masonry and dry mix blendersMortar, render, tile adhesive and grout producers blending cement with sand, lime, fillers and additives to a published specification.
What they buy on

Consistency, availability and a technical answer

Price decides who gets quoted. A concrete customer qualifies a cement on consistency, availability and technical support, and holds the account on the same three.

Cement type, class and strength developmentA declared cement type and strength class under the standard, with the early and 28 day strength pattern they can set a mix design against, not only a class printed on a delivery note.
Predictable mix behaviourWater demand, setting time, workability retention and admixture response held inside a band the customer has already tested.
Fineness and sulphate balanceBlaine, residue and the SO3 optimum held close to the values the customer qualified, each of which moves early strength and setting time, inside the limit the standard sets.
Bulk tanker schedulingLoading slots that match the batching schedule, with turnaround short enough to keep the fleet on its rounds.
Silo availabilityEnough of the right cement class in the right silo at the plant, and deliveries timed to keep the customer covered through a run of pours.
Technical and mix-design supportAccess to the laboratory, trial mixes for a new specification, and a named contact when a result falls outside expectation.
Where it goes wrong

The cement is accepted on delivery and questioned after the pour

A dispute with a concrete customer starts with information that did not travel with the cement. The mill run that produced the load, the silo it was drawn from and the laboratory results that describe it stay in the plant systems, while the customer holds a delivery note and a cube that broke low.

What shows up on the account

  • Batch-to-batch variation that the plant reads as within specification and the customer reads as a changed mix
  • A strength result that arrives days after the concrete is placed
  • Tanker queues at loading that push a customer past its batching window
  • A silo stockout that moves an account to a competitor
  • A cement class loaded into the wrong silo, at either end of the delivery
  • A failed cube test with no shared record to separate cement, aggregate, admixture and site practice
  • Collection held up while a quality claim stays open

One low cube result, several systems

A low cube result reaches the quality manager, the mill operator holding the fineness target, the dispatch planner who chose the silo and the sales manager who holds the account. Each of them reconstructs the same load from a different system, so the answer is assembled by hand while the customer waits for it.

What TwoSuns does

The load, its quality record and the account in one context

TwoSuns is configured around the concrete account rather than around the delivery note. Production, quality, dispatch and commercial teams keep their own authority and work from the same record of what was ground, stored, loaded, delivered and committed.

HorizonContracts and Offers, Order Management and Invoicing, Omni Signals and Finance carry the volume and price commitment, the delivery programme, the claim and the collection on each concrete account.
PulseGrinding and Product and Packing and Dispatch, with the shared Product Quality, Inventory and Logistics facilities, carry the mill run, the silo, the loading slot and the laboratory record behind every tonne the customer receives.
CorePlant basis, operating limits, roles, approval chains and decision history, with the cement types and classes, silo configuration and quality bands this work depends on.
RayExplanation and synthesis against the loads, results and terms a user is permitted to see, with the evidence it worked from.
Mix-relevant quality, per load.Each dispatched load carries its mill run, silo, fineness, SO3, declared constituents and the strength results known so far, so a customer question has one answer.
Bands the plant owns.Fineness, SO3, clinker factor and strength targets are set per cement class within the bands the plant's engineers define and own, and a load outside band is flagged before it is committed to a specification-sensitive account.
Silo and stock visibility.Silo levels by cement class are read against the order book and the delivery programme, so a stockout is visible while there is still time to grind or to reschedule.
Loading and turnaround.Weighbridge and loading times are read per customer and per haulier, so queues appear as a service problem on named accounts rather than as a daily average.
Claims with evidence.A quality claim opens against the specific loads in question, gathers their mill runs, silos and laboratory results, and records the finding, its owner and the commercial outcome.
Account economics.Volume, mix, price, freight, claims and days outstanding are read together per concrete account, against the cost of the cement actually shipped to it.
Quality continuity

From the cement mill to the customer cube test

A concrete relationship depends on the chain from mill run to cube result holding. The records along this path have to hold together for a producer to answer a technical question from the record rather than reconstruct it from several systems.

Mill. The run is recorded with its clinker, additions, gypsum, fineness and the operating setpoints in force.
Silo. Cement is fed to a silo, and the running composition of that silo is held with the mill runs that fed it and the periods they cover, because a silo is drawn down and topped up at the same time.
Loading. A load takes the identity of the silo it is drawn from, with the time, tanker, haulier and destination.
Delivery. The load is recorded against the customer silo named on the delivery, so a question about a given pour can be traced back to the loads that fed that silo.
Result. Laboratory results, including later-age strength, attach back to the run and to the loads that carried it, and so does the customer result when it is shared.

What travels with a load

  • Cement type and class
  • Mill run and silo
  • Fineness and residue
  • SO3 and declared constituents
  • Early and 28 day strength, as each becomes known
  • Loading time, tanker and haulier
  • Destination plant and silo

Figures are tagged as measured, derived or assumed, and a result still outstanding is shown as outstanding rather than filled in.

Take one concrete account and follow it

Pick the account that generates the most technical queries, and the team will walk a trailing twelve months of its loads, laboratory results and claims against your own records, under a mutual NDA.

Request a Technical Conversation Explore the Platform