Paramus — Cement Admixture Compatibility Screen

Overview

Screen cement–admixture combinations for compatibility: relate superplasticizer/retarder/accelerator chemistry to workability and set. The value is package-level triage, not one lookup.

Guidance vs execution: compatibility and set-behavior estimates come from tested Paramus tools. Treat outputs as screening signals, not certified concrete performance.

When to Use

• Checking an admixture package against a specific cement chemistry
• Diagnosing loss of workability or erratic set early Do not use for: certified concrete mix qualification or field placement decisions.

Workflow

Cement + admixture package
  ↓ 1. Characterize cement chemistry    → C3A / alkali / sulfate
  ↓ 2. Map admixture actions            → dispersion/retard/accel
  ↓ 3. Predict compatibility            → workability retention
  ↓ 4. Flag incompatibilities           → flash set / slump loss
  ↓ 5. Emit compatibility summary       → ranked risks + provenance

Procedure

1. Discover tools via search/get_schema ("cement", "admixture", "compatibility").
2. Characterize the cement chemistry (C3A, alkali, sulfate balance).
3. Map each admixture's intended action.
4. Predict workability retention and set behavior for the package.
5. Flag incompatibilities (flash set, rapid slump loss).
6. Emit a ranked compatibility summary with provenance.

Domain Judgment

• Compatibility is cement-specific — an admixture that works on one can fail on another.
• Sulfate balance drives many superplasticizer incompatibilities; check it.
• Rank by risk to workability window so the user knows what to trial.

Fallbacks

• Compatibility tool unavailable → deliver a manual admixture-interaction checklist.
• Endpoint unreachable → stop and report; do not fabricate set verdicts.