Revisa cada trabajo en la planta y encuentra la verdadera limitación.

El reto

El seguimiento en papel y código de barras se vuelve obsoleto en cuanto se registra. El personal camina a buscar; los directivos adivinan la restricción; Reequilibrar es lento.

Nuestro enfoque

• Etiqueta a los operadores en proceso, herramientas y activos móviles clave.
• UWB donde la precisión en zonas submétricas importa; BLE para zonificación sensible a costes.
• Análisis de zonas en vivo para exponer el verdadero cuello de botella.
• Progreso automatizado de órdenes de trabajo a partir de eventos de localización.
• Enlazar con MES para la programación en bucle cerrado.

Tecnología e integración

Pila desplegada: UWB (10–30 cm, <100 ms) for precision zones, BLE for broad coverage, Passive RFID for read-points.

Integración: MES , ERP , SCADA / historian, quality systems.

Relacionado: RTLS para fabricación · UWB vs BLE · Fabricación de RTLS

WIP locating for discrete manufacturing ties carriers or units to stations for flow, ageing and OEE loss trees. UHF RFID and UWB both appear depending on metal and accuracy needs.

MES integration decides whether OEE moves or only dashboards multiply.

Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.

We challenge any vendor who asks you to accept demo-day averages as production truth.

Agree the flow unit with supervisors. Tag it. Join MES. Change the daily meeting agenda to live queues. RF survey for metal. Reject accuracy theatre without meeting behaviour change.

KPIs: search minutes, ageing WIP, OEE loss credibility.

For WIP/OEE, change the production meeting ritual in the pilot scope or do not expand.

Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.

Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.

How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.

Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.

Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.

Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early — surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.