Asset Geolocation (Geolocalização de Ativos): A Guide for Portugal

Asset geolocation means knowing where equipment, tools, vehicles and spare parts are, ideally in real time, and tying that position to what the asset is doing in your maintenance process. The right technology depends on three things: how precise the position must be, whether the assets are indoors or outdoors, and how the data will reach your maintenance system. In Portugal there is a fourth: whether the tracking touches workers, because then the Labour Code and the data protection authority (CNPD) apply.

This guide is for maintenance managers, facilities firms and operations leads who are deciding whether to track assets and how to do it without wasting money or breaking the rules.

Fullyops
fullyops.com
Connect Asset Locations to Maintenance
Fullyops brings asset records, work orders, intervention tracking and operational analysis together to support more integrated maintenance management.

Request a demo

TL;DR

  • Start from the operational question (finding tools, proving a pump was serviced, locating a vehicle), then choose the technology. Starting from the hardware is the most common mistake.
  • GPS suits outdoor and moving assets; BLE suits zone-level tracking indoors at lower cost; UWB gives decimetre-level precision at higher cost; LoRaWAN covers wide outdoor sites.
  • Tag batteries, network infrastructure and installation labour often outweigh the hardware price in total cost of ownership.
  • In Portugal, geolocation that serves to monitor employee performance is prohibited, and worker consent does not fix that. Track assets, not people.
  • Location data is only useful when it lands in your work order and asset records, so plan the integration first.

Table of Contents

What asset geolocation covers in a maintenance context

The term is used loosely. In practice it covers three different jobs:

  1. Locating mobile equipment and tools inside a plant, hospital or warehouse (carts, pallets, portable instruments, critical spares).
  2. Tracking vehicles and mobile units across roads and between customer sites.
  3. Confirming where fixed assets are, for example that a chiller, generator or panel is at the site and address your register says it is.

Each job needs a different level of precision and a different technology. A real-time locating system (RTLS) combines hardware, software and a communication network to identify and monitor assets in real time, as the total cost of ownership study on RTLS in factories describes it. A GPS tracker on a van is not RTLS in that sense, but it answers a similar question outdoors.

For a maintenance team the value is concrete: less time searching for equipment, faster dispatch, fewer assets lost between sites, and cleaner records for audits. Our guide to asset tracking methods for field operations compares the broader methods, including barcodes and QR codes, which remain the cheapest option when you only need to know where an asset was last scanned.

Choosing the technology: GPS, BLE, UWB, LoRaWAN

The CIPAM overview of real-time geolocation frames the choice well: there is no one-size-fits-all answer. UWB is preferred where industrial settings need decimetric to centimetric precision, for example for automated guided vehicles or critical tooling. BLE is generally more cost-effective for area-based tracking and offers better battery life. LoRaWAN fits extended outdoor sites where range matters more than precision.

Technology Typical precision Best for Main trade-off
GPS/GNSS Metres, outdoors only Vehicles, trailers, outdoor plant Poor or no signal indoors; needs a power source or frequent recharging
BLE Zone to a few metres Tools, carts, containers, zone presence Less precise; needs enough gateways to cover the area
UWB Decimetres to centimetres AGVs, critical tooling, tight workflows Denser infrastructure, often wired PoE, higher cost
LoRaWAN Wide area, less precise indoors Large outdoor sites, utilities, yards Not suited to fine indoor positioning
Barcode/QR Last scan point only Fixed assets, audits, low budgets Not real time; relies on people scanning

Precision indications for UWB, BLE and LoRaWAN come from the CIPAM page above. GPS and barcode rows are general characteristics of those methods.

Metal, walls and radio conditions

Industrial buildings are hard on radio signals. The CIPAM guidance points out that you should define the required precision, the radio constraints of the environment (metal is the classic one) and the degree of integration with your existing EAM or CMMS before you pick a protocol. A pilot in the worst corner of your site, rather than the best, tells you more than any datasheet.

Metal walls interrupt radio paths to tracked equipment

A practical way to decide

Ask these questions in order:

  1. What decision will the location change? If the answer is “nobody knows”, do not buy hardware yet.
  2. Is a zone (“workshop 2”) enough, or do you need a spot (“bay 4, shelf C”)? Zone-level usually means BLE; spot-level may justify UWB.
  3. Indoors, outdoors or both? Mixed sites often need two technologies and a single place where the data meets.
  4. How many assets, and how often does each move? Ten critical instruments and ten thousand tags are different projects.
  5. Where must the data end up? If the answer is your maintenance system, check the integration options before you sign anything.

What it really costs

Hardware quotes are only the start. The RTLS total cost of ownership study reports direct hardware and software costs of roughly €4,500 to €5,500 for simpler ultrasonic systems and €11,000 to €15,000 or more for complex UWB deployments. Those figures exclude network infrastructure such as PoE switches and cabling, installation labour, and tag battery replacement over time. The same paper notes that installation can run from a few thousand euros for small room systems to tens of thousands for large applications, and that battery replacement is the main maintenance cost, with an estimated tag battery life of around two years in the case it models.

For a budget, list these lines separately:

  • Tags and anchors or gateways
  • Network and power (cabling, PoE, mounting)
  • Installation and commissioning
  • Software licences and integration work
  • Battery replacement plan: who changes batteries, how often, and how a dead tag is detected
  • Internal IT time to keep it running

The battery line is the one most often forgotten. With thousands of tags over several years, it becomes a recurring work order of its own. That is one reason to consider BLE before UWB when zone-level accuracy is enough: UWB’s higher precision requires a denser infrastructure of anchors, often wired, which adds installation complexity.

For smaller teams, a research team’s low-cost UWB system with an economic assessment shows that custom builds are possible, but they shift the effort from purchase price to development and upkeep, which most maintenance departments are not set up to absorb.

Portuguese rules: track assets, not people

This is the part many projects underestimate. Under the Código do Trabalho, geolocation devices used in the workplace are treated as remote surveillance (vigilância à distância). According to act legal’s analysis of a Lisbon Court of Appeal ruling on GPS in company vehicles, the employer needs a legitimate, specific purpose such as asset security or fleet management, and may not use the system to monitor productivity, verify visits or control performance. Workers must also be informed beforehand of the system’s existence, purpose and operation.

Two points deserve emphasis:

  • Consent does not solve it. The same analysis explains that the protection is mandatory, so an employee agreeing to be tracked does not make performance monitoring lawful. The employer stays liable.
  • The CNPD has set detailed conditions. Its Deliberação n.º 7680/2014 on geolocation in the employment context notes that geolocation data can be used to build behavioural profiles of the person using a vehicle or device, which is precisely why the limits exist. Read it before you configure anything that follows a vehicle or a phone.

In practice, for a maintenance organisation:

  1. Write down the purpose in terms of the asset (“locate shared test equipment”, “protect high-value vehicles from theft”), not the person.
  2. Prefer tags attached to tools and equipment over trackers that follow a named technician all day.
  3. Where a vehicle is assigned to a technician, check the CNPD conditions for vehicles and what the system may and may not record, including private use outside working hours.
  4. Inform workers in writing before activation, and keep that record.
  5. Do not use location data in performance reviews or to check visit times.
  6. Consult your data protection officer or legal adviser before launch. This article is not legal advice, and the rules for your specific fleet and contracts may differ.

Our own piece on geofencing for technicians and the Portuguese privacy rules goes through the setup checks in more detail.

Making location data useful: integration with maintenance

A dot on a map does not reduce downtime. Value appears when the location is attached to the asset record and the work order. Practitioners in industrial IoT cite interoperability and scalability as the main challenges, and recommend open approaches so location data does not stay locked in a proprietary silo. The IDTA data model for asset location is one example of a standardised way to describe where an asset is, and it is worth reading if you are writing a tender specification.

When you evaluate a tracking vendor, ask:

  • Does it expose an API or standard export, so location can flow into your CMMS or EAM?
  • Can you keep the location history if you change vendor?
  • Can you map tag IDs to asset IDs without retyping data?
  • Can access be limited by role, so only the people who need positions can see them?

It also helps to think about the operational chain beyond the map: who is dispatched, which part is used, what gets reported. Project tools built for crews and materials, such as this contractor app for jobs, crews and material orders, show how reporting and material flows are usually linked to task management, and the same logic applies to maintenance: location is one input to a larger workflow.

A worked example

Imagine a facilities contractor in Porto servicing HVAC units across forty buildings, with a pool of fifteen portable measuring instruments shared between teams. Today, instruments go missing for days and nobody knows who last used them.

A proportionate approach would be:

  1. Attach BLE tags to the fifteen instruments, and place gateways at the depot and in the vans. Zone-level accuracy is enough: “in van 3” or “at depot”.
  2. Record each tag against its asset ID in the asset register.
  3. Require the instrument to be assigned to a work order when taken out, so the record shows the job, not a person’s route.
  4. Define the purpose in writing as locating shared equipment, inform the teams, and do not use the data to assess individuals.
  5. Review after three months: search time, lost items, battery changes.

No UWB, no tracking of technicians, and a small, measurable outcome. If it works, extend to spare-part kits and larger equipment.

Our perspective

We see asset geolocation as a feature of a maintenance process, not a product on its own. Teams that struggle usually bought positioning first and only later asked what they would do with it. The ones that succeed begin with the asset record, the work order and the preventive maintenance schedule, and add location where it shortens a specific step, such as finding a part or confirming a unit’s site.

That is also how FullyOps is built: asset lifecycle management, work order control, operational analytics and real-time field data collection in one platform for industrial, facility and maintenance use. Because it offers integrations, location data from a tracking system can sit alongside the asset history instead of in a separate tool. We would add one firm view on privacy in Portugal: design the system around assets from day one. It is cheaper than retrofitting compliance, and it keeps the trust of your technicians, who are the people that make the data accurate.

— Pedro

Where FullyOps fits

If you already know that fragmented records are costing you time, the platform brings work orders, preventive schedules, inventory and analytics into one place, with Basic, Professional and Advanced plans for different user types. Prices are not published on the site, so the way to see what fits is through the FullyOps plans and demo. For a closer look at how automated records support field teams, see why automating asset tracking matters for field service.

Rollout checklist

  • Define the operational question and the metric (search time, lost items, response time).
  • Choose the lowest-precision technology that answers it.
  • Pilot in the hardest radio environment on site.
  • Budget batteries, network and labour, not only tags.
  • Document purpose, inform workers, and check the CNPD conditions.
  • Link tags to asset IDs and work orders from the start. A work order management process with clear states makes the location data actionable.
  • Measure after three months, then scale.

If your next step is organising assets before tagging them, the guide to inventory tracking for maintenance efficiency is a sensible place to start.

FAQ

Tracking equipment is generally acceptable when the purpose is legitimate, such as asset security or fleet management. The difficulty arises when the system also follows people, because the Labour Code treats that as remote surveillance and forbids using it to monitor performance. Check your case with a legal adviser and read the CNPD’s geolocation deliberation.

Which is better for a factory, BLE or UWB?

It depends on the precision you need. BLE is usually cheaper and has better battery life, and it works well for zone-level tracking of tools and containers. UWB gives decimetre-level or better positioning, which matters for AGVs or critical tooling, but needs denser and often wired infrastructure.

Not in a way that legalises performance monitoring. Legal analysis of Portuguese case law stresses that the protection is mandatory, so consent does not remove the employer’s liability. Workers must still be informed beforehand of the system and its purpose.

How much does an RTLS cost?

One academic study puts direct hardware and software costs between about €4,500 and €15,000 or more depending on the technology and complexity, excluding network, labour and batteries. Real projects vary by facility size, so request quotes that itemise every line.

Sources

Enhance Your Operations and Maximize Efficiency with FullyOps