{"id":19258,"date":"2026-08-05T23:57:43","date_gmt":"2026-08-05T15:57:43","guid":{"rendered":"https:\/\/www.lansitec.com\/?p=19258"},"modified":"2026-07-22T19:28:52","modified_gmt":"2026-07-22T11:28:52","slug":"rtls-location-sla","status":"publish","type":"post","link":"https:\/\/www.lansitec.com\/de\/blogs\/rtls-location-sla\/","title":{"rendered":"RTLS-Standort-SLA: Leitfaden zur Spezifizierung von Genauigkeit, Latenz und Akkulaufzeit"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Most RTLS projects start with a vague request: \u201cWe need real-time tracking.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That sounds clear until the first design meeting. Real time for what? A forklift moving through a warehouse? A worker entering a restricted zone? A pallet that sits still for three days? A container moving between a yard, a truck, and a covered loading bay?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is where many projects drift. Buyers ask for \u201c10 cm accuracy\u201d or \u201clive tracking\u201d before they define what the system must actually prove. The result is familiar: too much infrastructure in low-risk areas, not enough performance in critical zones, and a pilot that looks good on a map but is hard to operate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A better starting point is a location Service Level Agreement (SLA).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A Real-Time Locating System (RTLS) location SLA is a written definition of what \u201cgood enough location\u201d means for a specific site, asset type, safety process, and battery target. It can\u2019t and shouldn\u2019t replace technical design but makes technical design possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We\u2019ve seen this often: the hard part is rarely attaching a tag. Agreeing what the tag must prove is the hard part.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Is an RTLS Location SLA?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A useful location SLA should define accuracy, update rate, latency, confidence level, battery life, map assumptions, and failure modes. These are not marketing details. They are the difference between a system that is accepted by operations and one that becomes a permanent exception list. <sup><a href=\"#references\">(1)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A simple SLA table might look like this:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>SLA item<\/th><th>What it defines<\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td>Accuracy<\/td><td>How close the reported location must be<\/td><td>Within 3 m in open warehouse zones<\/td><\/tr><tr><td>Update rate<\/td><td>How often the system reports<\/td><td>Every 5 seconds, 30 seconds, or 1 minute<\/td><\/tr><tr><td>Latency<\/td><td>How quickly the event appears<\/td><td>Alarm visible within 10 seconds<\/td><\/tr><tr><td>Confidence<\/td><td>How often the system must meet the target<\/td><td>90 percent of valid reports<\/td><\/tr><tr><td>Battery target<\/td><td>Expected operating life under the chosen settings<\/td><td>6 months, 1 year, or 5 years<\/td><\/tr><tr><td>Exceptions<\/td><td>What happens in blind spots or degraded conditions<\/td><td>Cache, last known position, unavailable status, or alarm<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Notice what is missing: one universal accuracy number.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is intentional. A chemical plant, warehouse, hospital, tunnel, port, and construction site do not need the same location behavior everywhere. A good SLA allows different service levels by zone.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Define RTLS Requirements Before Choosing Technology<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before choosing hardware, write the operational sentence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not: \u201cWe need <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a>.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Better: \u201cWe need to know whether a worker entered the machine safety zone, and the alarm must appear in the control room within 10 seconds.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not: \u201cWe need 10 cm accuracy everywhere.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Better: \u201cWe need sub-meter positioning near automated equipment, but room-level visibility is enough in offices, storage rooms, and break areas.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This matters because \u201clocation\u201d can mean several things.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.lansitec.com\/blogs\/ble-presence-detection\/\" data-type=\"post\" data-id=\"18559\">Presence detection<\/a> means the system knows that a tag, badge, or beacon is near a gateway, doorway, room, checkpoint, or zone. It is useful for entry and exit records, room-level monitoring, and simple safety logic.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>BLE <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> positioning estimates location from received signal strength. It can be practical for rough indoor positioning, especially when assets do not move constantly, and the system can collect several readings.<\/li>\n\n\n\n<li>GNSS is a strong fit for outdoor tracking of vehicles, containers, and mobile equipment, but it should not be treated as a reliable indoor positioning method. <sup><a href=\"#references\">(3)<\/a><\/sup><\/li>\n\n\n\n<li>Bluetooth AoA improves location by estimating signal direction. It is useful when a site needs more precision than RSSI-based BLE but still wants to use Bluetooth tags or <a href=\"https:\/\/www.lansitec.com\/fr\/balises-bluetooth\/\">beacons<\/a>.<\/li>\n\n\n\n<li><a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> is the better fit when high-precision indoor positioning justifies more planning around anchors, calibration, geometry, and power. <sup><a href=\"#references\">(4)<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The SLA should separate these needs. Do not force one technology to solve every location problem on site.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Specify RTLS Accuracy Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Accuracy should be written with three parts: distance, probability, and zone. <sup><a href=\"#references\">(2)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A weak requirement says: \u201cAccuracy: 1 m.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A stronger requirement says: \u201cIn Zone A, the system shall report personnel location within 1 m for at least 90 percent of valid reports after calibration, excluding marked blind spots and maintenance periods.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That sentence is more useful because it defines where the promise applies, how it will be judged, and what counts as an exception.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For Lansitec-style deployments, it helps to think in location classes:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Location class<\/th><th>Practical meaning<\/th><th>Typical fit<\/th><\/tr><\/thead><tbody><tr><td><a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/detection-de-presence-ble\/\">Presence detection<\/a><\/td><td>The object is near a known point or zone<\/td><td>Entry, exit, room-level monitoring<\/td><\/tr><tr><td>BLE <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> positioning<\/td><td>Approximate indoor location<\/td><td>Assets, corridors, warehouses<\/td><\/tr><tr><td>GNSS positioning<\/td><td>Outdoor location<\/td><td>Yards, vehicles, containers<\/td><\/tr><tr><td>Bluetooth AoA<\/td><td>Direction-based higher precision<\/td><td>Personnel, tools, process zones<\/td><\/tr><tr><td><a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a><\/td><td>High-precision indoor positioning<\/td><td>Safety zones, automation, critical assets<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The keyword is fit. BLE <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> is not a failed <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> system. GNSS is not an indoor RTLS system. <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> is not automatically the right answer for every tagged object.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our customers often start by asking for the highest possible accuracy. After the site walk, the better question usually becomes: where does high accuracy change a decision?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">RTLS Update Rate vs Latency: What\u2019s the Difference?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Update rate and latency are different. Update rate is how often a device scans, advertises, calculates, or reports. Latency is how long it takes for the result to appear in the dashboard, alarm system, API, or third-party platform.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A tracker may support a short report interval, but that does not mean every event will appear instantly. End-to-end latency depends on the device configuration, scan window, radio backhaul, network server, application logic, and dashboard refresh.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Write both into the SLA.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Weak wording<\/th><th>Better SLA wording<\/th><\/tr><\/thead><tbody><tr><td>\u201cReal-time tracking\u201d<\/td><td>\u201cMoving assets shall update every 30 seconds, with dashboard refresh within 10 seconds of server receipt.\u201d<\/td><\/tr><tr><td>\u201cInstant alarm\u201d<\/td><td>\u201cRestricted-zone entry alarms shall appear in the control room within 10 seconds for 95 percent of valid events.\u201d<\/td><\/tr><tr><td>\u201cLive worker tracking\u201d<\/td><td>\u201cPersonnel updates shall run every 5 to 15 seconds in high-risk zones and every 60 seconds in normal zones.\u201d<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This protects battery life and network capacity. A worker near a confined-space entry may need fast updates. A pallet in storage probably does not.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Define RTLS Battery Life Requirements<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Battery life is not a separate datasheet line. It is part of the location service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A badge advertising every 100 ms behaves differently from one advertising every 800 ms. A tracker using GNSS every 30 seconds will not last like one reporting every 10 minutes or only on movement. A gateway with continuous <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/guide-essentiel-sur-la-lecture-et-la-reception-bluetooth-le-deblocage-du-suivi-bluetooth-et-les-performances-des-balises-iot\/\">Bluetooth receiving<\/a> will consume more power than one with a shorter receive window.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So, write the battery promise under the actual reporting policy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cThe badge shall support one working month between charges when configured for 1-second beacon advertising and 30-second location updates in normal zones.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Or:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cThe asset tracker shall support at least 12 months of operation when reporting every 10 minutes while moving and once per day while stationary.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This avoids a common pilot problem: aggressive settings make the demo look great, then production fails because charging, replacement, or maintenance becomes unrealistic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why RTLS Maps and Calibration Matter<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">RTLS depends on the map.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For BLE, AoA, and <a href=\"https:\/\/www.lansitec.com\/uwb-positioning-technology\/\" data-type=\"page\" data-id=\"12921\">UWB<\/a>, <a href=\"https:\/\/www.lansitec.com\/fr\/passerelles\/\">gateways<\/a>, <a href=\"https:\/\/www.lansitec.com\/fr\/balises-bluetooth\/\">beacons<\/a>, or anchors must be placed at known positions. If these reference points move, the system may still show a dot, but the dot may no longer be trustworthy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a>, anchor calibration is especially important because the positioning engine calculates tracker location from anchor coordinates and distance measurements. For <a href=\"https:\/\/www.lansitec.com\/solutions\/bluetooth-beacon-fixed-tracking-solution\/\" data-type=\"page\" data-id=\"9516\">B-Fixed<\/a> BLE architectures, fixed <a href=\"https:\/\/www.lansitec.com\/fr\/balises-bluetooth\/\">beacons<\/a> also need correct coordinates. The same logic applies to floors, walls, restricted zones, obstructions, and large metal structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add map requirements to the SLA:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Requirement<\/th><th>Example wording<\/th><\/tr><\/thead><tbody><tr><td>Reference point control<\/td><td>\u201cGateway, beacon, and anchor coordinates shall be recorded after installation.\u201d<\/td><\/tr><tr><td>Floor handling<\/td><td>\u201cMulti-floor areas shall use floor-specific reference points or altitude logic where supported.\u201d<\/td><\/tr><tr><td>Obstruction handling<\/td><td>\u201cKnown blind spots, metal barriers, roofed GNSS-blocked areas, and RF-shielded rooms shall be marked before acceptance testing.\u201d<\/td><\/tr><tr><td>Change control<\/td><td>\u201cAny movement of anchors, <a href=\"https:\/\/www.lansitec.com\/fr\/passerelles\/\">gateways<\/a>, <a href=\"https:\/\/www.lansitec.com\/fr\/balises-bluetooth\/\">beacons<\/a>, racks, or large machinery requires a validation check.\u201d<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This may sound procedural, but it matters. We like map discipline because it turns RTLS from a gadget into infrastructure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Plan for RTLS Failure Scenarios<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every location system has failure modes. A good SLA names them before deployment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BLE <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> can hear signals from nearby rooms. Walls may weaken a signal but not fully block it. People, humidity, furniture, and metal structures can affect <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a>. GNSS can degrade under roofs, near buildings, or underground. <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> performs best when anchor geometry and line-of-sight conditions are understood. AoA depends on stable gateway installation and careful placement. <sup><a href=\"#references\">(2)(3)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not hide these conditions. Define what the system should do.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Failure mode<\/th><th>SLA decision<\/th><\/tr><\/thead><tbody><tr><td>GNSS cannot fix under a roof<\/td><td>Switch to BLE if available, report last known position, or mark location unavailable<\/td><\/tr><tr><td>BLE signal appears from adjacent room<\/td><td>Use <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> thresholds, calibration, room-specific placement, or classify as presence only<\/td><\/tr><tr><td><a href=\"https:\/\/www.lansitec.com\/fr\/produits\/ancre-uwb\/\">UWB anchor<\/a> is moved<\/td><td>Mark the affected zone unvalidated until recalibration<\/td><\/tr><tr><td>Network outage<\/td><td>Cache where supported or show last known timestamp clearly<\/td><\/tr><tr><td>Battery low<\/td><td>Alert before the device drops below the operational threshold<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">An SLA that defines degraded operation is more credible than one that promises perfect tracking everywhere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">RTLS Location SLA Template for Industrial Projects<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before sending an RFQ, define these items:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Section<\/strong><\/th><th><strong>What to write<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Business objective<\/td><td>What decision the location data must support<\/td><\/tr><tr><td>Tracked objects<\/td><td>People, vehicles, tools, pallets, containers, keys, visitors<\/td><\/tr><tr><td>Zone classes<\/td><td>High-risk zones, normal zones, storage zones, outdoor zones, blind spots<\/td><\/tr><tr><td>Accuracy target<\/td><td>Error radius and confidence level per zone<\/td><\/tr><tr><td>Update policy<\/td><td>Report interval, scan interval, movement logic, event-triggered reports<\/td><\/tr><tr><td>Latency target<\/td><td>Delay from movement or event to dashboard, API, or alarm<\/td><\/tr><tr><td>Battery target<\/td><td>Required life under the agreed configuration<\/td><\/tr><tr><td>Infrastructure assumptions<\/td><td><a href=\"https:\/\/www.lansitec.com\/fr\/passerelles\/\">Gateways<\/a>, anchors, <a href=\"https:\/\/www.lansitec.com\/fr\/balises-bluetooth\/\">beacons<\/a>, power, backhaul, mounting, calibration<\/td><\/tr><tr><td>Map requirements<\/td><td>CAD files, coordinates, floors, obstructions, change control<\/td><\/tr><tr><td>Exception handling<\/td><td>GNSS loss, weak BLE, network outage, moved anchor, low battery<\/td><\/tr><tr><td>Acceptance test<\/td><td>How the system will be tested before sign-off<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A short example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cIn warehouse aisles, asset tags shall be located within 3 m for 90 percent of valid reports. Reports shall update every 60 seconds while moving and every 10 minutes while stationary. Restricted-zone entry alarms shall appear in the application within 10 seconds. Known blind spots behind metal storage structures shall be marked on the map and excluded from accuracy scoring. Battery life shall be at least 12 months under the approved configuration.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is clear. It is testable. It gives procurement, safety, operations, and engineering the same expectation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How an RTLS Location SLA Helps You Choose the Right Technology<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Once the SLA is written, hardware selection becomes much easier. <sup><a href=\"#references\">(3)(4)<\/a><\/sup><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If the SLA says \u201croom-level presence,\u201d a BLE gateway or beacon-based architecture may be enough. You do not need centimeter-level tracking to know that a tool cart entered the maintenance room.<\/li>\n\n\n\n<li>If the SLA says \u201c3 to 5 m in an open warehouse,\u201d BLE triangulation may be sufficient, especially for assets that stay in place long enough for the system to collect stable readings.<\/li>\n\n\n\n<li>If the SLA says \u201coutdoor container and vehicle tracking,\u201d GNSS with <a href=\"https:\/\/www.lansitec.com\/fr\/lorawan\/\">LoRaWAN<\/a>, NB-IoT, LTE-M, or Cat-1 backhaul becomes more relevant.<\/li>\n\n\n\n<li>If the SLA says \u201csub-meter worker location in a hazardous operating zone,\u201d Bluetooth AoA deserves serious consideration.<\/li>\n\n\n\n<li>If the SLA says \u201c10 to 30 cm positioning around high-value inventory, robotics, or safety-critical equipment,\u201d <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> may justify the added infrastructure.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The portfolio should follow the SLA, not the other way around.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices for Writing an RTLS Location SLA<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">RTLS buyers do not really buy tags, anchors, <a href=\"https:\/\/www.lansitec.com\/fr\/passerelles\/\">gateways<\/a>, or dashboards. They buy a location outcome.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">They want to find assets faster. Reduce search time. Prove that workers entered or left defined zones. Improve emergency response. Protect high-value equipment. Reduce manual counting. Understand utilization. Avoid arguing with a map no one trusts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That outcome needs a written SLA. Start with accuracy, latency, confidence, battery life, map quality, and failure mode. Then choose the technology. It may feel slower at the beginning, but it usually makes the pilot cleaner, the quote more realistic, and the final deployment easier to defend. And frankly, it keeps everyone honest.<\/p>\n\n\n<div\n\tclass=\"betterdocs-faq-wrapper layout-modern icon-after betterdocs-faq-layout-1 betterdocs-faq-qppzaf8 betterdocs-shortcode\">\n\t<h2 class=\"betterdocs-faq-layout-1 betterdocs-faq-qppzaf8 betterdocs-faq-section-title\">Frequently Asked Questions<\/h2>\n\t<div class=\"betterdocs-faq-inner-wrapper\">\n\t\t<div class=\"betterdocs-faq-title\">\n\t<h3 class=\"betterdocs-faq-title-tag\">About RTLS Location SLA<\/h3><\/div>\n<ul class=\"betterdocs-faq-list\"><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tWhat is an RTLS Location SLA?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p style=\"text-align:justify\"><span style=\"background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif\">An <a href=\"https:\/\/www.lansitec.com\/blogs\/rtls-location-sla\/\">RTLS location SLA<\/a> is a written definition of how a real-time location system should perform in a specific environment. It normally defines accuracy, update rate, latency, confidence level, battery life, coverage zones, map requirements, and exception handling.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tIs 10 cm Accuracy Always Necessary?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p style=\"text-align:justify\"><span style=\"background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif\">No. A 10 cm system may be valuable for automation, high-risk safety zones, and high-value asset control. Many use cases only need room-level presence, 3 to 5 m asset location, or outdoor GNSS tracking.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tWhat is The Difference Between Update Rate and Latency?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p style=\"text-align:justify\"><span style=\"background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif\">Update rate is how often the system reports. Latency is how long it takes for that report or alarm to appear in the application, dashboard, or API.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tShould Moving People be Tracked with BLE Triangulation?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p style=\"text-align:justify\"><span style=\"background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif\">It depends on the required accuracy and update speed. BLE <a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/positionnement-interieur-rssi\/\">RSSI<\/a> triangulation can work for many asset scenarios, but fast-moving personnel may require denser infrastructure, different settings, Bluetooth AoA, or <a href=\"https:\/\/www.lansitec.com\/fr\/technologie-de-positionnement-uwb\/\">UWB<\/a> in high-risk zones.<\/span><\/p>\n<\/div>\n<\/div><\/li><\/ul><script type=\"application\/ld+json\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What is an RTLS Location SLA?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p style=\\\"text-align:justify;\\\"><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">An RTLS location SLA is a written definition of how a real-time location system should perform in a specific environment. It normally defines accuracy, update rate, latency, confidence level, battery life, coverage zones, map requirements, and exception handling.<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"Is 10 cm Accuracy Always Necessary?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p style=\\\"text-align:justify;\\\"><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">No. A 10 cm system may be valuable for automation, high-risk safety zones, and high-value asset control. Many use cases only need room-level presence, 3 to 5 m asset location, or outdoor GNSS tracking.<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"What is The Difference Between Update Rate and Latency?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p style=\\\"text-align:justify;\\\"><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">Update rate is how often the system reports. Latency is how long it takes for that report or alarm to appear in the application, dashboard, or API.<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"Should Moving People be Tracked with BLE Triangulation?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p style=\\\"text-align:justify;\\\"><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">It depends on the required accuracy and update speed. BLE RSSI triangulation can work for many asset scenarios, but fast-moving personnel may require denser infrastructure, different settings, Bluetooth AoA, or UWB in high-risk zones.<\\\/span><\\\/p>\\n\"}}]}<\/script>\t<\/div>\n<\/div>\n\n\n\n<div id=\"references\"><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">References and further reading:<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.nist.gov\/ctl\/pscr\/isoiec-18305-2016-introduction\" target=\"_blank\" rel=\"noopener\">NIST introduction to ISO\/IEC 18305<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/es.mathworks.com\/help\/bluetooth\/ug\/bluetooth-direction-finding.html\" target=\"_blank\" rel=\"noopener\">MathWorks Bluetooth Location and Direction Finding<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.gps.gov\/gps-accuracy\" target=\"_blank\" rel=\"noopener\">GPS.gov GPS Accuracy<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.firaconsortium.org\/node\/727\" target=\"_blank\" rel=\"noopener\">FiRa Consortium UWB Regulatory Guide<\/a><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most RTLS projects start with a vague request: \u201cWe need real-time tracking.\u201d That sounds clear until the first design meeting. Real time for what? A forklift moving through a warehouse? A worker entering a restricted zone? A pallet that sits still for three days? A container moving between a yard, a truck, and a covered&hellip;&nbsp;<a href=\"https:\/\/www.lansitec.com\/de\/blogs\/rtls-location-sla\/\" rel=\"bookmark\">Weiterlesen \u00bb<span class=\"screen-reader-text\">RTLS-Standort-SLA: Leitfaden zur Spezifizierung von Genauigkeit, Latenz und Akkulaufzeit<\/span><\/a><\/p>","protected":false},"author":12,"featured_media":19398,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[19],"tags":[221,120],"class_list":["post-19258","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iot-education","tag-uwb-solutions","tag-uwb-technology"],"_links":{"self":[{"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/posts\/19258","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/comments?post=19258"}],"version-history":[{"count":4,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/posts\/19258\/revisions"}],"predecessor-version":[{"id":19271,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/posts\/19258\/revisions\/19271"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/media\/19398"}],"wp:attachment":[{"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/media?parent=19258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/categories?post=19258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lansitec.com\/de\/wp-json\/wp\/v2\/tags?post=19258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}