← All ten modules

UM · Solid-process module

Utility Module

Turns accepted material into a controlled, buffered process feed and provides the services required for a stable handover to reaction.

Architecture basis · detailed review values HOLDProject engineering required

Module function

What it does—and what it does not do.

The functional boundary is explicit so a module is never treated as a universal process claim.

DOES

Defined module functions

  • Receives accepted dry material or an engineered wet-route handover.
  • Prepares and conditions slurry to the reaction inlet basis.
  • Buffers feed variability and process timing.
  • Provides and monitors defined process services before RM transfer.
DOES NOT

Explicit exclusions

  • No metal-recovery claim.
  • No automatic acceptance of wet flotation concentrate without an engineered interface.
  • No release to RM without verified feed state and receiver readiness.

How the module works

The UM mechanism, step by step.

Each step names both the physical function and the evidence required before the next handover.

01Receive

Upstream release and receiver readiness recorded.

02Prepare slurry

Density, solids and rheology evidence accepted.

03Buffer

Level, capacity and destination status valid.

04Provide services

Required services are available within limits.

05Transfer to RM

RM inlet criteria and local permissives satisfied.

Stream schedule

Every inlet, product and residual has an owner.

A stream is not released merely because the equipment can move it. Its state, route and receiving boundary must be accepted.

StreamDirectionPhysical handoverAcceptance / release basis
Accepted materialInletAFCM dry feed or engineered wet route → UtilitySource, phase, rate and upstream status accepted.
Process liquids / servicesUtility inletSite / package utilities → UtilityQuality, pressure, temperature and availability defined.
Controlled reaction feedProduct / intermediateUtility → RMDensity, solids, rheology, flow and route accepted.
Drain / flush / off-specResidualUtility → named hold, recycle or residual receiverReceiver and return conditions explicit.

Published datasheet

What is fixed, selectable and project-specific.

Unsupported values are never guessed. The table states either the current public definition or exactly how the value is established.

Specification fieldCurrent definitionEvidence basis
Product codeUMFixed architecture
Product familySolid-process moduleFixed architecture
Typical process positionBefore reactionFixed architecture
Core dutySlurry preparation, buffering, services and verified transfer to RM.Fixed architecture
Feed rateMatched to selected Adapt model, RM demand and confirmed feed behaviour.Project-specific
Solids / density / rheologyReleased from representative testwork and the RM inlet basis.Project-specific
Buffer dutySet by operating cycle, variability, start/stop philosophy and available footprint.Project-specific
UtilitiesWater, power, air, heat and cooling duties are mass-and-energy-balance outputs.Project-specific
MaterialsSelected from chemistry, solids, abrasion, corrosion and cleaning basis.Project-specific
InstrumentationLevel, flow and required feed-state evidence follow the released control philosophy.Configuration option
PerformanceTransfer stability and preparation performance are verified for the project feed.Not publicly released

Interface schedule

What crosses the module boundary.

Process, utility, residual and control handovers are listed separately so responsibility is visible.

InterfaceClassHandoverAcceptance evidence
Feed inletProcess inAccepted dry feed or separately engineered wet feedUpstream status and material state verified.
RM outletProcess outControlled reaction feedRM inlet basis and route proven.
Site utilitiesUtilityDefined services and qualitiesAvailability and failure behaviour released.
Drain / residualResidualNamed hold, recycle, cleaning and disposal receiversNo unowned liquid route.
AutomationControlsState, level, flow, service and route evidenceCause/effect tested.

Operating envelope

The applicable limits form a hierarchy.

The system envelope, Kit or chemistry limits, installed module configuration, project evidence and receiver criteria all apply. The narrowest valid limit governs.

Envelope layerGoverning ruleChecks before release
SystemPhysical and chemical conditions must remain within the Adapt system envelope.pH, temperature, viscosity, chloride, conductivity and selected pack.
KitThe released Kit defines chemistry and reaction-feed limits.Composition, concentration, sequence and compatibility.
ModuleInstalled mixing, holding and transfer configuration defines local limits.Solids, density, rheology, level and transfer.
ReceiverRM acceptance is the final handover condition.Flow, state, route and readiness.

Safety, cleaning and lifecycle

The module includes more than the process duty.

Safe state, cleaning, maintainability and evidence gates are part of the technical definition, not afterthoughts.

01

Safety & release

  • Confirm chemical addition, stored energy, overflow, mixing and exposure hazards.
  • Contain drains and off-spec slurry with named destinations.
  • Block RM transfer when feed state, route or receiver is not verified.
02

Cleaning & changeover

  • Define flush, drain and CIP interfaces from feed and Kit changeover requirements.
  • Verify cleaning completion before a new released configuration.
03

Engineering & service

  • Feed preparation and rheology characterisation.
  • Mass/energy balance, buffer sizing and utility integration.
  • FAT/SAT of service loss, routes, transfer permissives and cleaning.

Project inputs

What is needed to complete the specification.

  1. 01

    Accepted-feed rate and variability envelope

    REQUIRED
  2. 02

    Solids loading, density, rheology and particle-size basis

    REQUIRED
  3. 03

    Buffering and transfer duty

    REQUIRED
  4. 04

    Water, power, air and other required utility availability

    REQUIRED
  5. 05

    Reaction Module inlet criteria

    REQUIRED
  6. 06

    Materials, cleaning, drainage, containment and site interfaces

    REQUIRED

Evidence register

Controlled source and publication boundary.

The source status is shown so a functional public summary cannot be mistaken for a released procurement or performance specification.

Controlled documentRevisionStatusVerified basisPublic claim scope
EA-20X-MLA-001RevAArchitecture basis · detailed review values HOLD2026-07-22Utility owns slurry preparation, buffering, services and verified transfer to RM. Detailed numeric values remain controlled.