Quicklime by calcination of limestone in a natural-gas-fired parallel flow regenerative kiln

Sourced conceptual inventory per tonne of high-calcium quicklime: limestone and process CO2 from stoichiometry, fuel heat, electricity and kiln emissions from EU CLM BREF ranges for the PFRK. No flowsheet; not reviewed.

Calculation maturity: not assessedDesign maturity: Concept (research)Not independently reviewedCement limeReport a problem with this process
Research outputNot engineering advice and not an approved design: do not use it for construction, operation or safety decisions. What this means

Overview

Sourced conceptual inventory per tonne of high-calcium quicklime: limestone and process CO2 from stoichiometry, fuel heat, electricity and kiln emissions from EU CLM BREF ranges for the PFRK. No flowsheet; not reviewed.

Capacity
per tonne of quicklime (the dataset's basis); no plant size (PFRKs are built for 100 to 600 t/d)

What goes in and out

In

  • LimestoneFeedstockcounted as its CaCO3 (impurities not modelled)
  • MethaneFeedstocknatural gas, taken as pure methane (ASSUMED)
  • AirFeedstockcombustion air, free; its O2 is feed:O2

Out

  • Calcium oxideMain product
  • Calcium oxideCo-productproduct:byproduct-lime: off-specification lime and filter dust, sold for other uses; allocated by mass with the quicklime (the dataset's allocation). No inventory_key, so that it is never taken as an Atlas producer of calcium-oxide
  • Carbon dioxideEmissionprocess CO2 of the carbonate
  • Carbon dioxideEmissionfuel CO2
  • WaterEmissioncombustion water vapour

Utilities: Electricity (kiln only)

Show in the process graph

Life cycle assessment

No footprint assessed yet; the process is part of the life-cycle inventory below.

In the open LCI database (cheme-as-code-atlas-preview-a3c52e4) as Calcium oxide, Quicklime, high-calcium, lump (counted as CaO) Preliminary; By-product lime (off-specification lime and filter dust), sold for other uses Preliminary.

Download it for Brightway, openLCA and other tools.

In the LCI database: system model, datasets and KPIs against the benchmarks

In the LCI database

Status
Preliminary 1 unmapped exchange. Some exchanges have no background mapping yet: they are exported unlinked and count no burden, so the inventory is incomplete.
System model
attributional, cut-off (methodology 1.1.0)
Allocation
mass (deviation, from dataset) · product:byproduct-lime 3 %, product:quicklime 97 %
Allocation findings
none
Change report
Not available: this build has no change report against an earlier release.
Dataset pages
By-product lime (off-specification lime and filter dust), sold for other uses Preliminary · Calcium oxide, Quicklime, high-calcium, lump (counted as CaO) Preliminary

KPI benchmark positions

Maturity and review

Design maturity Concept (claimed): An idea or first flowsheet; numbers are rough. No independent engineering review yet. Automated checks passing is not a review.

Calculation maturity, from the checked evidenceNot assessed

The process has no maturity report (cheme maturity, checks/maturity.json), so no calculation maturity is established.

No level shownThe design maturity (Concept) is the manifest's claim, not evidence. A level appears here once the process's repository holds a current report from cheme maturity --write.

Artifact completeness

Which deliverables exist. They never raise a calculation maturity level: a drawing from unchecked numbers is still unchecked.

Not reported without a maturity report.

Independent review

Not independently reviewed

No independent engineering review yet. Automated checks passing is not a review.

Set by people only. Reaching a calculation maturity level or passing automated checks is not an independent review or an approval.

Where the evidence comes from
Report
processes/lime-1/checks/maturity.json (not in the library)
Method
How ChemE-as-Code checks the levels (requirement by requirement)

Open items

Sources

Library version
a3c52e4 (process last changed in a3c52e4)
Data
Catalog record (JSON) · CC-BY-4.0
Files
View the files on GitHub · change history and authors

References

How to cite

For the data, cite the Process Atlas paper; for the platform that builds and checks it, the ChemE-as-Code paper.

Schweidtmann, A. M. & Weber, J. M. (2026, in preparation). Process Atlas: an open, git-native, reproducible library and life cycle inventory of chemical processes (working title).

For this process: "Quicklime by calcination of limestone in a natural-gas-fired parallel flow regenerative kiln", ChemE-as-Code process library, version a3c52e4.

BibTeX
@unpublished{schweidtmann_process_atlas,
  author = {Schweidtmann, Artur M. and Weber, Jana M.},
  title = {{Process Atlas: an open, git-native, reproducible library and life cycle inventory of chemical processes (working title)}},
  year = {2026},
  url = {https://atlas.cheme-as-code.org},
  note = {in preparation}
}

Schweidtmann, A. M. (2026). ChemE-as-Code: An Open-Source Platform for Agentic AI in Chemical Engineering. arXiv:2611.07947. https://doi.org/10.48550/arXiv.2611.07947

BibTeX
@misc{schweidtmann_cheme_as_code,
  author = {Schweidtmann, Artur M.},
  title = {{ChemE-as-Code: An Open-Source Platform for Agentic AI in Chemical Engineering}},
  year = {2026},
  eprint = {2611.07947},
  archivePrefix = {arXiv},
  doi = {10.48550/arXiv.2611.07947},
  url = {https://arxiv.org/abs/2611.07947}
}