Construction RFID
RFID Concrete Embed Tag
Cast-In UHF for Precast
Quick answer
RFID concrete embed tags are cast directly into the structural matrix during placement, surviving the pH 12–13 alkaline pore-water chemistry of fresh concrete and delivering a permanent, machine-readable piece-mark for the full 50-to-100-year service life of the element. Built for the code envelope governing modern concrete construction — ACI 318 Building Code Requirements for Structural Concrete, ACI 301 Specifications for Concrete Construction, ACI 313 Concrete Bins / Silos / Bunkers for Granular Materials, PCI MNL-116 Manual for Quality Control for Plants and Production of Structural Precast Concrete Products, EN 13369 Common Rules for Precast Concrete Products, AASHTO LRFD Bridge Design and ASTM C666 Freeze-Thaw Durability. The tag is the missing persistent digital identifier that links BIM models (ISO 19650 / COBie 2.4) to physical precast beams, post-tensioned girders, tunnel segments, pipe joints, seismic shear walls and cast-in-place foundations.
- Cast-in installation during concrete pour. The tag is placed in the formwork or tied to rebar before placing concrete and is permanently encapsulated — no surface-mount handling damage, no label weathering.
- Survives fresh-concrete chemistry (pH 12–13), curing exotherm (up to 70 °C core), 300+ freeze-thaw cycles per ASTM C666 and the full 50–100-year structural design life.
- UHF read through 5–10 cm of cured concrete. Handheld readers against the element surface retrieve the element EPC and link to the ACI 318 / PCI MNL-116 / AASHTO LRFD / COBie record.
Used in these industries
Deployments where this product is referenced on our industry landing pages.
At a glance
Use these short answers to decide whether this page matches the project before moving into the detail.
Code envelope addressed
ACI 318-19 / 318-25 Building Code Requirements for Structural Concrete. ACI 301 Specifications for Concrete Construction (mix, placement, curing).
BIM + digital twin envelope
ISO 19650 Organization and Digitization of Information — BIM processes. COBie 2.4 Construction-Operations Building information exchange.
Next step
Ready to move forward? Start your inquiry to get specific answers for this project.
Request quote and samples- Concrete element types addressed
-
- Precast beams, columns, wall panels (PCI MNL-116).
- Post-tensioned girders (PTI M50.3 recommendations).
- Tunnel segments (TBM / precast concrete ring).
- Concrete pipe, culvert, box sections (ASTM C76 / C1433).
- Cast-in-place foundations, slabs, shear walls (ACI 318 Ch. 18 seismic).
- AASHTO LRFD bridge deck panels and girders.
- Housing envelope
-
- Alkaline-resistant HDPE or PPS encapsulation (pH 12–13 tolerant).
- Glass-filled nylon housing for temperature spike during curing exotherm.
- Rigid cylindrical or flat tile form factor (30×15×5 mm / Ø25×10 mm).
- Integrated cable-tie slot for rebar attachment and form-face clip.
- Placement options
-
- Formwork face attachment via temporary adhesive.
- Rebar-intersection clip (ACI cover depth 25–75 mm typical).
- Post-install pocket (drill-and-grout into existing element).
- Hydrostatic / hydrodynamic spacer placement during slip-form.
- Chip + data
-
- Impinj Monza R6-P — 96-bit EPC + 32-bit user memory.
- NXP UCODE DNA — on-chip AES-128 authentication option (ISO/IEC 29167-10) for bridge / tunnel assets.
- Data fields: mix design ID, pour date, cure class, strength class, BIM GUID.
- Environmental envelope
-
- Operating temperature −40 °C to +80 °C.
- Freeze-thaw: ASTM C666 Procedure A, 300+ cycles.
- Alkaline tolerance: pH 12–13 pore-water chemistry.
- Moisture: permanent saturation in cured concrete.
- Read performance
-
- UHF read through 5–10 cm concrete cover.
- Read range reduced to 0.3–1.0 m depending on cover depth + rebar density.
- Handheld reader against concrete surface: reliable single-tag capture.
- Drone-mounted reader option for bridge soffit inspection reads.
- Lifecycle linkage
-
- Plant production: tag placed in form, EPC written at pour.
- QC + cure: strength-class + curing regime logged to EPC record.
- Transport + erection: read at shipping, receiving, erection pick.
- Service life: periodic inspection reads under ACI 562 / AASHTO bridge NBI.
- Industry fit
-
- Precast plants (beams, columns, walls, stairs, balconies).
- Bridge construction (AASHTO LRFD deck + girder + pier).
- Tunnel construction (TBM ring-segment lifecycle).
- Water and sewer infrastructure (ASTM C76 pipe).
- Seismic-retrofit cast-in-place elements under ACI 318 Ch. 18.
- Failure modes prevented
-
- Stenciled / painted piece-marks weathering off within 2–5 years.
- Surface-adhered tags destroyed during handling, transport, erection.
- Paper records losing integrity over 50+ year service life.
- BIM → physical-asset disconnect during facility handover (COBie).
- ACI 562 assessment traceability gap for aging repair / retrofit.
- Deployment posture
-
- Pilot: 500–5,000 tags on a single precast product line or bridge project.
- Scaled: 100,000+ tags per year for a top-tier precast manufacturer.
- Integration: plant MES → ERP → BIM CDE (ISO 19650) → owner AMS.
- Typical pricing
-
USD 0.60–2.50 /pc by size (typical FOB Shenzhen range) — firm quote in one business day.
Commercial terms
- MOQ
- Varies by SKU — stock items from 100 pcs; custom production typically 200-1,000 pcs
- Lead time
- Production 2-3 weeks after artwork and encoding sign-off; reorders on a 3-4 week cycle
- Samples
- Free samples and RF test report with every order; courier at customer cost
- Payment
- 50% T/T deposit, 50% before shipment; Net 30/60 for established accounts; LC for large orders
- Shipping
- FOB Shenzhen / Yantian; DHL, FedEx or EMS air freight; sea LCL / FCL for volume
- Response
- Itemized quote within one business day, Mon-Fri (UTC+8)
Why paper piece-marks and surface labels fail ACI 318 / PCI MNL-116 / AASHTO LRFD traceability
After the cure, every element in the yard is the same institutional grey, and the difference between beam B-114 and beam B-141 is a coat of paint that transport is already sanding off. Paint is a coating, not a commitment. Casting the identity into the matrix makes the concrete itself the record — the same trick nail tags pull on the timber side of the plant.
| Identification method | How it fails | What the failure costs |
|---|---|---|
| Painted / stenciled piece-marks (PCI MNL-116) | Thousands of elements — beams, columns, panels, pipes — look identical after curing; stencils wear off during transport, handling, stacking and erection | Visual identification fails exactly where the PCI MNL-116 QC chain expects it to work |
| Surface-mounted barcode labels and RFID tags | Destroyed during element handling by cranes, forklifts, C-hooks and rebar-exposed rough edges | Severs the link to the mix-design, strength-test and cure-date records required under ACI 301 |
| Paper records for cast-in-place elements | Foundations, slabs and shear walls carry no practical machine-readable identifier; project databases drift as projects span multiple years | Paper becomes the only piece-to-record link — and it loses accuracy first |
| Manual BIM-to-field matching | ISO 19650 and COBie 2.4 handover require a persistent digital identifier linking the BIM model GUID to the physical element; manual matching is error-prone | BIM-to-physical disconnect lands at exactly the handover moment the model was bought for |
| Service-life traceability on paper | ACI 318, EN 13369 and AASHTO LRFD require traceability of materials, mix design, compressive-strength tests and curing regime for each element | Paper cannot support the 50-to-100-year service life, especially under ACI 562 condition-assessment rules for aging structures |
How the embed tag locks the BIM–physical link into the concrete matrix
Making the ID part of the pour takes three decisions — where the tag sits, what it is made of, and which silicon answers. The full UHF chip comparison settles the third; the cross-section below settles the other two, because in this product the housing chemistry and the cover depth decide whether the chip is ever heard from again.
Paper piece-marks and stenciled IDs under PCI MNL-116
- Stenciled piece-mark weathers off within 2–5 years outdoor exposure.
- Paper QC records lose indexing across multi-year project handover.
- Piece-to-record match depends on manual document search.
- ACI 562 condition-assessment re-traceability requires destructive sampling.
Cast-in RFID embed tag linked to BIM and ERP
- Permanent EPC survives the element's 50–100-year design life.
- Mix-design, strength-class and pour-date written into user memory at pour.
- BIM GUID → physical element matched in seconds with handheld reader.
- ACI 562 / AASHTO NBI inspection writes condition data back to element record.
- Tags are placed in the formwork before pouring — attached to the form face with temporary adhesive (consumed by concrete bonding) or clipped to a rebar intersection using the tag's integrated cable-tie slot. Placement meets ACI 301 cover-depth requirements (typically 25–75 mm) while leaving the tag accessible to handheld UHF readers.
- Alkaline-resistant HDPE or PPS housing tolerates the pH 12–13 pore-water chemistry of fresh concrete throughout the curing exothermic reaction (core temperatures up to 70 °C in mass placements) and for the element's entire service life.
- UHF RAIN RFID with Impinj Monza R6-P or NXP UCODE 9 delivers readable signal through 5–10 cm of cured concrete cover — depending on aggregate type (limestone is more RF-transparent than granite) and reinforcement density. A handheld reader held against the surface retrieves the element ID at 0.3–1.0 m.
- Each tag carries a unique EPC linked to the element's digital record — mix-design ID (ACI 301), pour date, strength-class (PCI MNL-116), compressive-strength test result (ASTM C39), cure regime, BIM GUID and AASHTO LRFD design group — giving field crews instant access to the complete element history.
RFID concrete embed tag specifications
Every number the submittal package will ask for, in one table. And a scope note: if the read must stay proud of the surface — rebar bundles, pipe in a laydown yard — that is the flag tag's job. The embed tag's job is to disappear into the pour and keep answering for decades.
| Attribute | Value | Notes |
|---|---|---|
| Form factor | Rigid flat tile or cylinder | Flat tile suits form-face placement; cylinder suits rebar-clip mounting |
| Dimensions | 30 × 15 × 5 mm flat tile · Ø25 × 10 mm cylinder | Smaller than typical coarse aggregate — no measurable strength effect in ASTM C192 / C39 testing |
| Housing | Alkaline-resistant HDPE or PPS; glass-filled nylon option | Tolerates pH 12–13 pore water and the curing exotherm — up to 70 °C core in mass placements |
| Frequency | UHF RAIN RFID, 860–960 MHz | Global band per the GS1 EPC Gen2 air-interface protocol; regional sub-bands apply |
| Chip options | Impinj Monza R6-P (standard) · NXP UCODE 9 (EPC-only) · NXP UCODE DNA (secure) | UCODE DNA adds AES-128 authentication (ISO/IEC 29167-10) for bridge and tunnel assets |
| EPC + data model | Unique EPC linked to mix-design ID, pour date, cure class, strength class, BIM GUID | Written at the pour station; carried for the element's full service life |
| Read-through cover | 5–10 cm of cured concrete | Aggregate matters: limestone is more RF-transparent than granite |
| Surface read range | 0.3–1.0 m with a handheld reader | Falls as cover depth and rebar density rise — see the attenuation chart below |
| Recommended placement | 25–50 mm cover optimal; 25–75 mm typical ACI 301 band | The element's specified cover class governs — read range never overrules cover |
| Attachment | Rebar clip (integrated cable-tie slot) · form-face adhesive · post-install drill-and-grout pocket | Adhesive is consumed by concrete bonding; grout pockets retrofit existing elements |
| Operating temperature | −40 °C to +80 °C | Covers the IBC / EN climate maps without performance degradation |
| Freeze-thaw durability | ASTM C666 Procedure A, 300+ cycles | No measurable UHF read-rate loss at test endpoint |
| Moisture | Permanent saturation in cured concrete | Solid one-piece encapsulation — no seam, no vent, nothing to delaminate |
| MOQ | 500–1,000 units (standard SKU) | Pilot programmes typically run 500–5,000 tags on a single product line |
| Lead time | 3–4 weeks standard | 5–7 weeks with UCODE DNA provisioning or a custom pre-encoded data model; physical samples precede the batch |
Pour day: how the tag survives placement, vibration and the curing exotherm
Placement is the tag's entire qualification exam, compressed into minutes: impact loading when the mix arrives, high-frequency vibration during consolidation, then a pH 12–13 chemical bath that cures at up to 70 °C. The anchor bolt tag faces the same discipline where steel meets concrete; here is how the embed tag passes.
Fixing happens at rebar inspection, before any concrete moves. The tag clips to a rebar intersection through its integrated cable-tie slot, or bonds to the form face on a temporary adhesive pad that the concrete consumes as it cures. From that moment its position is a specification, not a hope: inside the 25–75 mm cover band, clear of lifting anchors and post-tensioning ducts, logged against the piece-mark at the pour station.
Then the mix arrives — placement impact first, consolidation second. An internal poker vibrator does not care what is mounted in the cage; it re-liquefies everything nearby to drive out entrapped air. A loose tag would migrate or float. A fixed tag rides it out: the solid HDPE / PPS encapsulation has no internal void to collapse, and the rebar clip holds station through placement and vibration. Crews keep the poker head off the tag the same way they keep it off spacers and cast-in instrumentation — standard practice, not a new rule.
The exotherm follows — up to 70 °C at the core of mass placements — then the long alkaline cure at pH 12–13, then form strip. The first handheld read through fresh cover is the plant's QC moment: the EPC answers, the mix-design ID and pour date reconcile against the batch ticket, and the element rolls to the stockyard already wearing its permanent identity. One rule stays absolute for structural work: the specified cover class governs placement, and the tag adapts to it — never the other way around.
- Fix the tag at rebar inspection — cable-tie clip at a rebar intersection inside the 25–75 mm cover band, never loose in the form.
- Log the tag EPC against the piece-mark and batch ticket at the pour station, before placement.
- Place and vibrate as normal — keep the poker head off the tag, as with any cast-in instrumentation.
- Verify a read at form strip with a handheld reader against the element surface, before the element leaves the QC bay.
- Write cure class and strength class to the element record at QC release — the stockyard pick then scans instead of squinting.
Applications across precast, bridge, tunnel, and cast-in-place concrete programmes
One SKU, several very different owners. The common thread: the element outlives every clipboard, binder and project database that ever described it. For the municipal cousins of this programme — access covers scanned from the street — see the manhole cover tag.
Precast plants
Beams, columns, wall panels, stairs, balconies, hollow-core slabs and pipe segments identified from production through storage, transport and erection — aligned to the PCI MNL-116 and EN 13369 QC envelopes.
Bridge construction
AASHTO LRFD deck segments, girders, piers, abutments and post-tensioned elements carry lifecycle IDs for FHWA NBI periodic inspection scheduling under 23 CFR 650 Subpart C.
Tunnel segments
TBM ring segments tracked from production through installation and long-term structural health monitoring (SHM) instrumentation campaigns.
Cast-in-place structures
Foundations, slabs and shear walls gain a permanent identifier for building-lifecycle management under ISO 19650 / COBie 2.4.
Water and sewer infrastructure
Utility vaults, manholes, ASTM C76 concrete pipe, ASTM C1433 box culverts and precast drainage structures enter municipal asset management with machine-readable IDs.
Seismic retrofit and ACI 562 repair
Retrofit elements under ACI 318 Ch. 18 carry the ACI 562 / ASCE 41 assessment record and the repair WPS in the structural element itself.
Integration with ACI / PCI / AASHTO / ISO 19650 workflows
A cast-in EPC is only as useful as the systems that answer it, so this is the wiring diagram from pour station to owner handover. The data model follows the GS1 EPC encoding guide; the hardware side is covered in the reader and writer selection guide.
- Weeks 0–4 — pilot product + data model
Select a pilot precast product line (e.g. bridge deck panels or hollow-core slabs). Define the element data model (mix-design ID, pour date, strength-class, BIM GUID) and integrate with plant MES / ERP.
- Weeks 4–10 — placement procedure + plant rollout
Train form crews on tag placement (form-face adhesive vs. rebar-clip). Validate read-through on 25–75 mm cover depth sample slabs. Roll out tagging across the pilot product line.
- Weeks 10–16 — BIM CDE + AASHTO NBI integration
Wire EPC ↔ BIM GUID mapping into ISO 19650 common data environment. Validate AASHTO NBI inspection workflow with field-team handheld readers.
- Weeks 16–26 — full-scale + owner handover
Scale from the pilot product line to 100,000+ tags per year, with MES → ERP → BIM CDE → owner AMS handover under COBie 2.4 and FHWA NBI digital-twin flows.
| Lifecycle stage | System of record | What the EPC carries or triggers |
|---|---|---|
| Plant floor — pour station | Plant MES + EPCIS | EPC written at pour; mix-design ID, pour date, strength-class and curing regime logged to user memory and the plant MES |
| Design and handover data | ISO 19650 common data environment | EPC ↔ BIM GUID mapping stored in the CDE, enabling COBie 2.4 handover with persistent element IDs |
| Erection site | Handheld reader + erection-sequence plan | Element identity confirmed at pick and set; linked to the erection sequence and torque-log for connection work |
| Owner AMS handover | Owner asset-management system | At substantial completion the element register (EPC → BIM GUID → PCI MNL-116 QC record → AASHTO LRFD design group) transfers to the owner |
| Service-life inspection | FHWA NBI (23 CFR 650 Subpart C) + ACI 562 assessments | Inspection visits read the tag and write condition-state codes back to the element's digital record |
Useful next pages
Use these linked product, guide and comparison pages to keep the next click specific and practical.
Related construction and infrastructure RFID tags
Other RFID tags for construction site and infrastructure applications.
Chip-level technical reference
Deep-dive specifications and chip-family comparisons relevant to this SKU.
FAQ
Can the tag be read after it is fully encapsulated in ACI 318 concrete cover?
Yes. The UHF tag is readable through 5–10 cm of cured concrete when scanned with a handheld UHF reader held against or near the surface. Read range depends on concrete cover depth, aggregate type (limestone is more RF-transparent than granite) and rebar density. We recommend placing the tag at 25–50 mm cover for optimal readability within ACI 301 cover-class requirements.
Does the tag affect concrete structural integrity or ACI 318 compliance?
No. The tag is smaller than a typical piece of coarse aggregate (standard size 30 × 15 × 5 mm) and has no measurable effect on concrete compressive, tensile or shear strength. Tags have been tested in ASTM C192 specimen-prep protocol and ASTM C39 compressive-strength tests with no detectable strength reduction versus control specimens, supporting ACI 318 design assumption integrity.
How does the tag link to a BIM model and survive to owner handover under COBie 2.4?
Each tag carries a unique EPC that is mapped to the BIM element GUID in the ISO 19650 common data environment. At substantial completion, the element register (EPC → BIM GUID → PCI MNL-116 QC record → ACI / AASHTO design data) is exported as a COBie 2.4 handover spreadsheet or IFC 4.3 file. The owner's asset-management system retains the EPC-to-GUID mapping for the element's full 50–100-year service life.
Will the tag survive concrete placement and internal vibration?
Yes, provided it is fixed rather than loose. The tag is clipped to a rebar intersection through its integrated cable-tie slot or attached to the form face with temporary adhesive, so placement impact and internal poker vibration do not displace it. The solid HDPE / PPS encapsulation has no internal void to collapse, and crews keep the vibrator head off the tag as they would with any cast-in instrumentation. A handheld read at form strip confirms the tag survived placement before the element leaves the plant.
What is the MOQ and lead time for RFID concrete embed tags?
MOQ is 500–1,000 units for the standard flat-tile and cylinder SKUs. Standard lead time is 3–4 weeks; allow 5–7 weeks for UCODE DNA authentication provisioning or a custom pre-encoded data model (mix-design ID, pour date and BIM GUID fields). Physical samples precede the production batch so read-through performance can be verified on your own mix design and cover depth.
Can tags be retrofitted into existing concrete structures?
Yes. A post-install pocket is drilled into the existing element and the tag is grouted in place, giving retrofit and repair projects the same permanent identifier as new casts. This is the standard route for ACI 562 assessment and rehabilitation programmes, where existing structures need durable element-level traceability that survives subsequent inspection cycles.
Which chip should I choose for a concrete embed tag?
Impinj Monza R6-P is the standard choice for plant traceability — a unique EPC piece-mark plus a small user-memory block for cure-class and strength-class flags. NXP UCODE 9 is the lean EPC-only option for pure piece-marking. NXP UCODE DNA adds AES-128 cryptographic authentication per ISO/IEC 29167-10 and a larger user memory, which bridge, tunnel and other public-infrastructure owners specify when element identity must be provable, not just readable.
Sources & references
Primary standards, OEM datasheets and regulatory documents cited by this article. All URLs were verified on the access date shown below.
- ACI 318-19 Building Code Requirements for Structural Concrete and Commentary
Design and construction requirements for structural concrete — source of the mix-design, cover-depth and seismic detailing fields encoded in the tag user memory.
- ACI 301 Specifications for Concrete Construction
Specification requirements for concrete placement, cover, curing and QC that the tag's EPCIS integration supports.
- PCI MNL-116 Manual for Quality Control for Plants and Production of Structural Precast Concrete Products (5th edition)
Precast plant QC envelope — piece-mark, strength-class, curing record that the tag carries persistently.
- EN 13369 — Common Rules for Precast Concrete Products
European precast QC / marking rules that the EPC-encoded element record fulfills.
- AASHTO LRFD Bridge Design Specifications, 9th edition
LRFD bridge design envelope and AASHTO NBI inspection traceability supported by the embedded tag.
- ASTM C666 / C666M Standard Test Method for Resistance of Concrete to Rapid Freezing and Thawing
Freeze-thaw durability test underpinning the 300+ cycle tag-survival claim in the dataHighlight.
- FHWA Specifications for the National Bridge Inventory (23 CFR 650 Subpart C)
Periodic bridge-inspection regime under which the embedded tag supports element-level condition reads.
- ISO 19650-1 Organization and digitization of information about buildings and civil engineering works
BIM common-data-environment basis for EPC ↔ BIM GUID mapping.
- COBie 2.4 — Construction-Operations Building information exchange
Asset-handover schema at substantial completion that carries the embedded-tag EPC to the owner AMS.
- ACI 562-21 Code Requirements for Assessment, Repair, and Rehabilitation of Existing Concrete Structures
Assessment / repair envelope under which the embedded tag's service-life traceability becomes operationally valuable.
- GS1 EPC UHF Gen2 Air Interface Protocol
Defines the passive UHF air interface operating in the 860–960 MHz range — source for the frequency-band row in the specification table.
- NXP UCODE DNA product page (SL3S5002N0FUD) — UHF tag IC for secure authentication
Confirms AES-128 cryptographic authentication per ISO/IEC 29167-10 and GS1 UHF Gen2 v2.0 compliance for the UCODE DNA chip option named in the specification table.
Proud Tek is a Shenzhen-based RFID & NFC manufacturer supplying hotel chains, transit operators, event venues and retail brands worldwide. Every order includes free samples, RF testing and dedicated project support.
Get a Quick Quote
Tell us about your project and we'll respond within one business day. Fields marked (asterisk) are required.