The right item, the right code, the right price.
Search the library. Build the set. Check what already exists.
Catalog codes decide whether a specification survives review.
Catalog codes are mandatory where public money is spent
Many funded projects require every specification position to carry a code from the applicable catalog — not a supplier price-list line invented for the moment.
Manual matching is slow and brittle
Hundreds of thousands of positions make exact keyword search a poor fit. Wrong or outdated codes return as review comments and force a rewrite of the specification.
Search and check belong together
Teams either assemble a new catalog-backed set from the library or verify a finished file against the same canonical registry.
Two workflows. One registry.
Semantic library search
Enter a plain-language description or a partial code and receive the canonical item, unit, applicable standard, and price.
Assemble a new specification
Add matched positions into a working catalog and export it in the electronic or printed format the workflow requires.
Line-by-line compliance check
Upload an existing specification and compare each line against the registry for code, nomenclature, unit, and current price.
Highlighted findings
Mismatches, outdated codes, and divergent names are returned as an itemized review instead of a silent pass.
Canonical codes for every position
Each finding and each search hit resolves to the intended catalog identity, ready for correction or reuse.
Structured export
Send the checked or assembled result back out as a spreadsheet or the submission format required by the project.
From a plain description to an exportable result.
Resolve positions
Map every line to a canonical catalog identity.
Build or correct
Add validated positions, or fix the ones that failed.
Export
Issue the set in the format the next party expects.
One product, adapted to the market where it runs.
Jurisdiction-specific catalogs
Load the rate library and item registry that govern the market where the project is delivered.
Organization libraries
Keep approved internal items and supplier lists available alongside the official catalog.
Current editions
Resolve against the intended catalog edition so outdated codes surface before issue.
Human confirmation
Every match and every finding remains subject to specialist review before the specification is issued.
Connected to estimating
Validated catalog positions feed Armeta Smeta and the broader preconstruction workflow.
Structured handoff
Export checked or assembled results for estimating, procurement, and formal review.
Who uses it
Explore the Armeta product line.
See Armeta Materials on your own workflow.
Bring the documents, standards, and project context your team works with today.