← All ten modules

AFCM · Solid-process module

Adaptive Feed Control Module

Protects the compact Adapt line by accepting, screening and validating named dry feed before any material is handed to Utility.

HOLD · dry-only architecture lockedProject 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

  • Protects the intake from foreign bodies and unacceptable oversize.
  • Screens dry material against released acceptance criteria.
  • Separates accepted feed from reject, quarantine and reprocess material.
  • Creates a verified dry handover to Utility.
DOES NOT

Explicit exclusions

  • No wet slurry, tanks, hydrocyclones or wet separation.
  • No direct transfer to Reaction Module.
  • Legacy wet-AFCM descriptions do not apply to Adapt 20X.

How the module works

The AFCM mechanism, step by step.

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

01Identify source

Source identity and sample chain recorded.

02Protect intake

Protection devices and containment ready.

03Screen feed

Screen state and acceptance result recorded.

04Accept or segregate

Destination and status are unambiguous.

05Handover dry feed

Utility ready and dry interface proven.

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
Named dry feedInletSite dry-feed interface → AFCMSource, PSD, moisture, bulk density, hazards and variability accepted.
Accepted dry feedProduct / intermediateAFCM → UtilityReleased intake criteria met; destination ready.
Oversize / foreign bodiesResidualAFCM → named reject receiverSegregated and traceable.
Quarantine / reprocessOff-specAFCM → controlled hold or reprocess routeNo automatic return to process.

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 codeAFCMFixed architecture
Product familySolid-process moduleFixed architecture
Typical process positionDry-feed front end before UtilityFixed architecture
Feed phaseDry feed only for the Adapt 20X controlled architecture.Fixed architecture
Feed acceptanceNamed source with released PSD, moisture, flowability, contamination and hazard criteria.Project-specific
Screening dutySelected from representative size distribution, oversize and foreign-body risk.Project-specific
CapacityMatched to model, Utility demand and confirmed bulk-material behaviour.Project-specific
ContainmentDust and spill controls follow material hazards and site basis.Project-specific
MaterialsDefined from abrasion, corrosion, contamination and cleaning requirements.Project-specific
ControlsAcceptance state, protection status, route selection and destination feedback are interlocked locally.Fixed architecture
Physical arrangementModel and site layout are selected during engineering.Project-specific

Interface schedule

What crosses the module boundary.

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

InterfaceClassHandoverAcceptance evidence
Dry-feed inletProcess inNamed site feed pointReleased lot/source and intake criteria.
Accepted outletProcess outDry accepted feed to UtilityUtility ready and route selected.
Reject outletsResidualSeparate reject, quarantine and reprocess receiversDestination status proven.
AutomationControlsProtection, screening, route and status evidenceLocal cause/effect and feedback released.

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
SystemOnly dry feed may cross the AFCM → Utility boundary.Phase, source, transport and containment.
ModuleProtection and screening limits are locked to the installed intake configuration.PSD, oversize, moisture, bulk density, dust and abrasion.
Kit / processAccepted feed must also be suitable for the released downstream Kit route.Composition, contamination and variability.
ReceiverEvery reject state has an owned destination.Reject, quarantine and reprocess capacity.

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

  • Assess combustible or harmful dust, exposure, pinch points and foreign-body energy.
  • Interlock intake with protection devices and destination availability.
  • Keep reject and quarantine material physically and digitally segregated.
02

Cleaning & changeover

  • Use a dry-cleaning strategy unless a separately engineered wet-cleaning boundary is released.
  • Confirm cleaning waste and contaminated consumables receivers.
03

Engineering & service

  • Representative dry-feed characterisation and intake trials.
  • Screening, protection and dust-control engineering.
  • FAT/SAT of routes, feedback, reject logic and Utility handover.

Project inputs

What is needed to complete the specification.

  1. 01

    Named dry source and representative sample plan

    REQUIRED
  2. 02

    Composition, mineralogy, particle-size distribution, oversize and variability

    REQUIRED
  3. 03

    Moisture, bulk density, flowability, dust and abrasion characteristics

    REQUIRED
  4. 04

    Hazards, contaminants, foreign-body risk and required containment

    REQUIRED
  5. 05

    Required screening and intake-acceptance criteria

    REQUIRED
  6. 06

    Reject, quarantine and reprocess destinations

    REQUIRED
  7. 07

    Utility dry-feed acceptance criteria, throughput basis 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-AFCM-CTRL-001RevBHOLD · dry-only architecture locked2026-07-22Acceptance, protection, screening, validation, segregation and dry handover. Legacy wet-AFCM content excluded.