Real-Time Location Systems for Secure Operations: What Actually Works (and What Fails)

Introduction

Secure operations environments are unforgiving.

Whether in defence facilities, aerospace MRO, or regulated production environments, the tolerance for error is effectively zero. Equipment cannot go missing. Processes cannot be skipped. Assets cannot be in the wrong place at the wrong time.

And yet, many tracking systems deployed into these environments quietly fail.

Not in a dramatic, visible way. They simply become unreliable. Data becomes inconsistent. Teams stop trusting the system. Over time, the platform is either ignored or reduced to a narrow, low-impact use case.

The issue is rarely a lack of awareness. Most organisations already understand the value of real-time visibility. The problem is more fundamental:

The technology deployed is often not aligned to the reality of the environment.

Systems that perform well in controlled demos or simplified pilot zones frequently struggle when exposed to the complexity of secure, operational environments. The result is a gap between expectation and reality — and in secure operations, that gap matters.

What We Mean by Secure Operations

“Secure operations” is often used loosely, but in practice it refers to environments with a specific set of characteristics.

These include:

• Defence and military facilities

• Aerospace manufacturing and MRO environments

• Secure logistics and storage operations

• Regulated production environments such as pharmaceuticals

Across these environments, there are consistent requirements:

• Controlled access to assets and areas

• Strict audit and compliance obligations

• High-value or sensitive equipment

• Complex coordination between people, assets, and processes

For example, in aerospace and defence operations, real-time visibility is used to track tools, vehicles, and personnel while maintaining compliance and operational readiness.

Similarly, in secure asset environments such as armouries or classified equipment storage, systems must maintain continuous chain-of-custody records and enforce access control policies.

These are not optional capabilities. They are baseline requirements.

What defines secure operations is not just the presence of valuable assets — it is the need for continuous, reliable control over those assets within complex, constrained environments.

Why Secure Environments Break Most Tracking Systems

Many tracking technologies are designed and validated in relatively clean, predictable conditions. Secure environments are the opposite.

They introduce a set of constraints that expose weaknesses very quickly.

Infrastructure constraints

In secure environments, you cannot simply install hardware wherever it is convenient.

• Physical modifications may require approval

• Certain areas may be inaccessible

• Cabling and power availability may be restricted

This limits how systems can be deployed and often forces compromises that reduce performance.

Signal complexity

Secure operations environments are rarely signal-friendly.

• Metal-dense structures

• Multi-level facilities

• Obstructed line-of-sight

• Electromagnetic interference

These factors introduce noise, reflection, and inconsistency into tracking systems.

Solutions that rely on ideal signal conditions tend to degrade rapidly in these environments.

Operational reality

Most systems are designed around how processes should work.

In reality:

• Assets are moved unpredictably

• Workflows change under pressure

• People take shortcuts

• Exceptions are common

If a system cannot tolerate this variability, it becomes fragile.

Security and IT constraints

Secure environments also impose restrictions on data and infrastructure:

• Air-gapped or segmented networks

• Strict cybersecurity requirements

• Limited cloud connectivity

Systems must operate reliably within these constraints, not around them.

Ubisense deployments in defence environments, for example, are designed to integrate with existing infrastructure and meet strict cybersecurity and operational requirements.

This is often where otherwise capable technologies fail — not because they cannot track assets, but because they cannot operate within the constraints of the environment.

The Common Technologies — and Where They Fall Down

There is no shortage of tracking technologies available. The issue is not availability — it is suitability.

Each technology has strengths, but also clear limitations when applied to secure operations.

RFID

RFID is widely used for identification and compliance-driven processes.

It works well for:

• Check-in / check-out workflows

• Inventory counts

• Low-cost tagging at scale

However, RFID is not a real-time visibility solution.

• It typically requires manual interaction

• It provides point-in-time data, not continuous tracking

• It does not support live operational awareness

In secure environments, this creates blind spots between scan events.

Bluetooth Low Energy (BLE)

BLE is attractive due to its low cost and scalability.

It can be useful for:

• Broad proximity detection

• Low-resolution location awareness

But in practice:

• Accuracy is inconsistent

• Signal strength fluctuates

• Positioning can drift significantly

In environments where precise location matters — for example, tracking high-value assets or enforcing process steps — this inconsistency becomes a problem.

GPS

GPS is effective in open, outdoor environments.

It is commonly used for:

• Fleet tracking

• Wide-area visibility

However:

• It does not work indoors

• Accuracy degrades near structures

• It cannot support detailed process tracking

Most secure operations involve a mix of indoor and controlled environments, making GPS insufficient on its own.

Ultra-Wideband (UWB)

UWB is one of the few technologies capable of delivering high-accuracy, real-time location data.

It enables:

• Precise indoor positioning

• Continuous tracking of assets and personnel

• Real-time event detection

This level of precision is what allows systems like SmartSpace® platform to build a live operational view of complex environments and support automation, alerts, and process control.

However, UWB is not a shortcut.

• It requires careful infrastructure design

• Deployment quality directly affects performance

• Integration with workflows is critical

When deployed correctly, it is highly effective. When deployed poorly, it fails like any other system.

Why Most RTLS Deployments Fail

The failure of RTLS in secure environments is rarely due to a single issue. It is usually the result of a set of predictable mistakes.

Technology-first thinking

Organisations often start by selecting a technology, rather than defining the operational problem.

This leads to:

• misaligned deployments

• unnecessary complexity

• poor adoption

Pilot success does not scale

Many systems perform well in controlled pilot zones.

But scaling introduces:

• environmental variability

• infrastructure constraints

• operational complexity

What worked in a small test area often does not translate to full deployment.

Ignoring real workflows

Systems are frequently designed around idealised processes.

In reality, workflows are:

• dynamic

• inconsistent

• influenced by human behaviour

If the system does not align with how work actually happens, it will not be used effectively.

Lack of ownership

RTLS often sits between:

• IT

• operations

• engineering

Without clear ownership, it becomes:

• underutilised

• poorly maintained

• deprioritised

Overpromising accuracy

Accuracy is often presented as a headline metric.

But in practice:

• consistency matters more than peak accuracy

• reliability builds trust

• inconsistency destroys it

Once users stop trusting the data, the system loses value quickly.

What Actually Works in Practice

If most RTLS deployments fail for predictable reasons, then successful ones tend to follow a consistent pattern.

The difference is not just the technology used. It is how the system is designed, deployed, and integrated into the operation.

Start with operational outcomes

The starting point should not be the technology.

It should be the outcome you are trying to achieve.

In secure operations, these are typically:

• Ensuring tools are accounted for at all times

• Maintaining process compliance across complex workflows

• Knowing where critical assets are, in real time

• Reducing delays caused by missing or unavailable equipment

When deployments begin with clearly defined outcomes, decisions around technology, infrastructure, and integration become more straightforward.

Without this, systems tend to become generic visibility layers with limited operational impact.

Design for the environment, not the technology

Secure environments impose constraints that cannot be ignored.

Successful deployments are designed around:

• physical layout

• material conditions

• movement patterns

• restricted zones

Rather than forcing a standard architecture into every site, systems need to be adapted to the environment they operate in.

This is where many deployments fail — they assume that what worked in one facility will translate directly to another.

In practice, each environment requires deliberate design.

Combine technologies where needed

There is no single technology that solves every problem.

In many secure environments, the most effective approach is a combination of methods:

• RFID for compliance and identification

• UWB for real-time location and precision tracking

• Integration with existing systems for context

This layered approach allows each technology to be used where it is most effective, rather than stretching one system beyond its limits.

Focus on reliability over perfection

High accuracy is often used as a selling point, but in practice, consistency is more important.

A system that delivers:

• predictable performance

• stable location data

• consistent behaviour

is more valuable than one that occasionally delivers very high accuracy but is unreliable over time.

Trust in the system is built through consistency.

Once that trust is lost, adoption drops quickly.

Integrate into existing systems and workflows

Tracking data on its own has limited value.

It becomes useful when it is connected to:

• maintenance systems

• production workflows

• compliance and audit processes

For example, platforms like the SmartSpace® platform are designed to integrate location data into operational systems, enabling automation, alerts, and process control rather than just passive visibility.

This is what turns RTLS from a tracking system into an operational tool.

From Visibility to Intelligence: Where AI Actually Adds Value

There is increasing focus on AI within operational environments, often positioned as a solution in its own right.

In practice, AI is only as effective as the data it depends on.

Most environments are not AI-ready.

Data is often:

• incomplete

• inconsistent

• disconnected across systems

Without reliable, real-time location data, AI models produce unreliable outputs. In some cases, they amplify errors rather than reduce them.

This is why many AI initiatives in operational environments struggle to deliver meaningful results.

Once a consistent, high-quality data layer is in place, the picture changes.

Reliable RTLS data enables:

• identification of process deviations

• detection of bottlenecks and inefficiencies

• analysis of asset utilisation

• early identification of risks or delays

At this point, AI becomes useful — not as a replacement for operational systems, but as an extension of them.

The key point is simple:

AI does not fix poor operational visibility. It depends on it.

Where RTLS Delivers Real Value

When deployed correctly, RTLS delivers value in a small number of clearly defined areas.

These tend to be consistent across secure operations environments.

Tool accountability

Ensuring that tools are:

• present

• correctly assigned

• returned after use

This is critical in environments where missing tools can create safety risks or operational delays.

Asset tracking across secure facilities

Maintaining visibility of:

• high-value equipment

• mobile assets

• critical components

This reduces time spent searching for assets and improves overall operational efficiency.

Process compliance and audit trails

RTLS can provide:

• automatic records of asset movement

• verification of process steps

• audit-ready data

This supports compliance in regulated and high-security environments.

For example, in defence and aerospace contexts, compliance tracking is a key requirement for maintaining operational readiness and meeting regulatory standards. (Ubisense compliance tracking)

Personnel coordination and safety

Understanding the location of personnel enables:

• improved coordination across teams

• faster response to incidents

• better overall situational awareness

This is particularly important in complex or hazardous environments.

How to Evaluate an RTLS System

For organisations considering RTLS, the evaluation process should be grounded in practical questions.

Not all systems are equal, and not all are suitable for secure operations.

Key considerations include:

• Does it work in your actual environment, not just in a demo?

• Can it scale beyond a pilot deployment?

• Is the data consistent and reliable over time?

• Does it integrate with your existing systems and workflows?

• Can it operate within your security and IT constraints?

• Is it maintainable over the long term?

These questions are more valuable than headline claims about accuracy or performance.

They focus on what actually determines success in practice.

Conclusion

Real-time location systems are not new.

The technology is well understood, and the potential benefits are widely recognised.

What remains challenging is applying that technology effectively within secure operations environments.

Most failures are not due to a lack of capability. They are the result of:

• misaligned technology choices

• poor deployment design

• unrealistic expectations

Secure operations require a different approach.

One that prioritises:

• reliability over theoretical performance

• operational fit over technical novelty

• integration over isolation

When these factors are addressed, RTLS becomes a practical, valuable part of the operation.

Without them, it remains an underused system that never delivers on its initial promise.

If you are looking to impliment an RTLS or would like more information, please contact Ubisense now.