RTLS for procurement.
Most RTLS RFPs come back unscoreable: vendors compare against different baselines, omit hidden costs, and structure SOWs to make exit expensive. This is the procurement lens — how to run an RFP that produces a defensible shortlist and a contract that protects the spend.
RFP structure that produces comparable responses
An RFP that doesn't define accuracy budget, integration scope, deployment scale and operational handover expectations produces apples-and-oranges responses.
A well-structured RTLS RFP imposes the same evaluation matrix on every bidder: technical fit (40%), commercial fit including 5-year TCO (30%), security and compliance (15%), and deployment capability with references (15%). Our RFP template (coming soon) encodes this.
Vendor scorecard with named criteria
‘Best fit for the environment’ is unscoreable. ‘Demonstrated accuracy of ≤30 cm at 95th percentile across 14 days of pilot operation under 2,000-tag load’ is scoreable.
The evaluation matrix forces every named criterion into a measurable form, with weighted scoring and explicit tie-break rules. This is what makes the shortlist survive an internal audit.
Security questionnaire that doesn't disqualify the right vendors
Standard SIG or CAIQ questionnaires were written for SaaS, not for RTLS hardware vendors. Many credible RTLS suppliers fail them on questions that don't apply.
We help you adapt the questionnaire so it scores the right risks (data residency, identity, supply-chain) and ignores the wrong ones (SaaS-only categories that don't apply to OT hardware) — without weakening security posture.
Contractual controls that protect exit
Three contractual controls turn an RTLS commitment into a manageable risk. A gate-driven SOW that permits clean exit at named milestones. Data-portability clauses guaranteeing your location telemetry is yours, in a documented format.
And IP / configuration ownership so a future SI can pick up the system if the original vendor changes hands. We have template language for all three; see our independence policy for the surrounding stance.
Frequently asked questions
Can you provide an RTLS RFP template?
Yes — we publish a vendor-neutral RTLS RFP template that procurement teams use as a starting point. It covers technical requirements, commercial structure, security and compliance, and the SOW controls discussed here. Request the template.
How do we evaluate vendors who self-rate every criterion as 5/5?
By requiring evidence per criterion: customer-reference call notes, deployment-scale numbers, pilot test data. Self-ratings without evidence get zero. This is the single most powerful evaluation rule procurement can enforce.
What's the typical structure of an RTLS commercial proposal?
Hardware (one-time + refresh), software licensing (annual), deployment services (fixed-fee for design, T&M for build), ongoing operations (annual). Hidden costs are usually under deployment services and operations. We model 5-year TCO with sensitivities at gate 1.
Are you available to act as an independent evaluator on our RFP?
Yes — that's vendor-neutral consulting. We score bids against your criteria, run reference calls on your behalf, and produce a defensible shortlist. We never accept compensation from the vendors we score.
Last updated: