Real-time locating system
tracking system

Real-time locating systems (RTLS), also known as real-time tracking systems, are used to automatically identify and track the location of objects or people in real time, usually within a building or other contained area. Wireless RTLS tags are attached to objects or worn by people, and in most RTLS, fixed reference points receive wireless signals from tags to determine their location. Examples of real-time locating systems include tracking automobiles with a vehicle tracking system through an assembly line, locating pallets of merchandise in a warehouse, or finding medical equipment in a hospital.
The physical layer of RTLS technology is often radio frequency (RF) communication. Some systems use optical (usually infrared) or acoustic (usually ultrasound) technology with, or in place of RF, RTLS tags. And fixed reference points can be transmitters, receivers, or both resulting in numerous possible technology combinations.
RTLS are a form of local positioning system and do not usually refer to GPS or to mobile phone tracking. Location information usually does not include speed, direction, or spatial orientation.
Origin
The term RTLS was created (circa 1998) at the ID EXPO trade show by Tim Harrington (WhereNet), Jay Werb (PinPoint), and Bert Moore (Automatic Identification Manufacturers, Inc., AIM). It was created to describe and differentiate an emerging technology that not only provided the automatic identification capabilities of active RFID tags, but also added the ability to view the location on a computer screen.
The public source identifies “Real-time locating system” as tracking system. This brief keeps that definition visible, then builds a research path around Real-time, locating and system.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Real-time locating system”, the useful work is to connect “tracking system” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 18, 2026. The linked authority identifier is Q1141977. The first chronological checks are 1998.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Real-time locating system”, its source revision and the description used here.
- Expand the search: follow Real-time locating system primary sources, Real-time locating system archive and Real-time research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Real-time locating system”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Real-time locating system” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.