Download PDF

System Capacity

Performance Metrics & KPIs
Email
Ask AI

The maximum operational load an RTLS can handle including concurrent tags, updates per second, and data storage. Must account for peak scenarios. Exceeding capacity causes increased latency, missed updates, and potential instability.

System capacity in industrial RTLS defines the maximum operational load the system can handle while maintaining specified performance levels including positioning accuracy, update rates, and latency. Tag capacity is often the primary specification: industrial RTLS systems range from small deployments (50-200 tags) through medium scale (500-2,000 tags) to enterprise scale (5,000+ tags). However, raw tag count oversimplifies capacity - system load depends on tag update rates: 1,000 tags at 1 Hz update rate generates 1,000 position calculations per second, while 100 tags at 10 Hz generates the same computational load. Capacity specifications should therefore state maximum tags at specified update rates (eg., 2,000 tags at 1 Hz or 500 tags at 10 Hz). Proper capacity planning requires: understanding application requirements (how many assets need tracking, required update rates for different applications, expected growth trajectory), analyzing system specifications (maximum capacity at different configuration levels), calculating total system load (sum of all concurrent demands), and including margin for growth and peak loads (typically 20-30% headroom beyond normal operation). Testing system capacity before full deployment is essential: stress testing with expected maximum tag count and update rates, monitoring performance metrics (CPU, memory, network utilization) under load, identifying bottlenecks and scaling limits, and validating that performance remains acceptable at maximum specified capacity. Industrial customers should specify capacity requirements clearly during procurement: expected tag count (current and 3-5 year projection), required update rates by application type, geographical coverage area, number of concurrent users and applications, and historical data retention requirements.

Prompt copied — paste it into the chat