GHT: Glass House Technologies
GHT service / Operational systems

Asset tracking

Where the equipment is, and who has it

Scans, RFID, BLE, UWB, GPS, cellular, Wi-Fi, cameras, or custody events, chosen by required accuracy, update rate, environment, battery life, privacy, cost, and integration.

What you should have at closeoutAsset records that answer a defined location, custody, condition, utilization, or maintenance question with measured confidence and a visible exception process.
References3 reviewed
Last updated2026-08-20
Overview

What Asset tracking includes

Asset tracking begins with a managed asset identity and lifecycle: acquire, receive, commission, assign, move, maintain, audit, retire, and dispose. Location technology adds observations to that record; it does not replace the system of record or process ownership.

Zone-level presence, room-level location, doorway transitions, outdoor position, custody scans, and continuous real-time location are different requirements. A pilot should measure missed reads, false locations, latency, battery life, coverage, and reconciliation in the real environment.

Question to answer before designWhat decision changes when the asset is found, and what location precision, update rate, and confidence does that decision require?
Common situations

This service may fit when:

  • Teams spend meaningful time searching for mobile or shared equipment
  • Custody, maintenance, calibration, or utilization records do not match the asset state
  • A proposed real-time system has no required accuracy, latency, or action defined
  • Existing tags or labels are duplicated, damaged, inconsistently applied, or detached from the lifecycle
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Identity

Asset class, unique identifier, owner, custodian, lifecycle, location hierarchy

02

Observation

Scan, tag, beacon, position, gateway, camera, sensor or human event

03

Interpretation

Zone, confidence, timestamp, transition, dwell, condition, alert rule

04

Action and record

System of record, work order, search, audit, exception, maintenance, disposal

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Asset classes, quantities, value, size, material, movement, owner, and lifecycle
  • Decision, required location precision, update frequency, confidence, and alert action
  • Indoor/outdoor environment, RF materials, coverage, gateways, power, network, and mounting
Design decisions

What those findings determine

  • Visibility: Buy only the precision and frequency that changes an operational decision.
  • Tag: Compare cost, size, battery, environment, maintenance, privacy, and infrastructure.
  • Location: State accuracy, confidence, and staleness explicitly; no technology provides perfect location.
Closeout records

What you should receive

  • Asset decision, lifecycle, and location hierarchy
  • Technology trade study and pilot acceptance thresholds
  • Tag, gateway, coverage, network, power, and maintenance plan

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Define asset decisions

    Classify assets, value, movement, custody, location question, precision, latency, condition, maintenance, privacy, and actions triggered by an observation.

    EvidenceAsset-class and decision matrix, lifecycle map, location hierarchy, current search or loss baseline, and privacy questions.
  2. 02

    Select the observation method

    Compare barcode, RFID, BLE, UWB, GPS, cellular, Wi-Fi, camera, and manual events against range, accuracy, latency, battery, environment, infrastructure, and cost.

    EvidenceTechnology trade study, tag and gateway plan, coverage model, system-of-record mapping, and pilot acceptance thresholds.
  3. 03

    Pilot in the real path

    Tag representative assets, install the limited pilot infrastructure, integrate events, train users, and run normal movement plus difficult materials, locations, and exceptions.

    EvidencePilot inventory, observed read and location results, latency, missed and false events, battery assumptions, and operator feedback.
  4. 04

    Prove the full lifecycle

    Test receive, assign, move, search, alert, maintenance, lost tag, offline gateway, duplicate, audit, retirement, and data correction.

    EvidenceAccepted scenario set, matched asset records, exception queue, coverage gaps, support runbook, and scale recommendation.
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
VisibilityTypical approach: Custody or point-of-work scanMore demanding conditions: Automated zone, transition, or real-time observationWhat determines the choice: Buy only the precision and frequency that changes an operational decision.
TagTypical approach: Printed barcode or passive RFIDMore demanding conditions: Battery-powered BLE, UWB, GPS, or cellular deviceWhat determines the choice: Compare cost, size, battery, environment, maintenance, privacy, and infrastructure.
LocationTypical approach: Last known transactionMore demanding conditions: Estimated current position with confidence and timestampWhat determines the choice: State accuracy, confidence, and staleness explicitly; no technology provides perfect location.
IntegrationTypical approach: Standalone asset portalMore demanding conditions: Events update the asset, maintenance, or workflow systemWhat determines the choice: Name the system of record and how conflicts and corrections are resolved.
Before design

What we need to know

  • Asset classes, quantities, value, size, material, movement, owner, and lifecycle
  • Decision, required location precision, update frequency, confidence, and alert action
  • Indoor/outdoor environment, RF materials, coverage, gateways, power, network, and mounting
  • Tag form factor, attachment, battery, replacement, tamper, privacy, and disposal
  • System of record, event fields, integrations, retention, permissions, and exception reconciliation
At closeout

What you should receive

  • Asset decision, lifecycle, and location hierarchy
  • Technology trade study and pilot acceptance thresholds
  • Tag, gateway, coverage, network, power, and maintenance plan
  • Pilot measurement and exception evidence
  • Integration map, matched sample records, support runbook, and scale recommendation
Best fit

When this service makes sense

  • Healthcare equipment, tools, returnable containers, vehicles, field kits, and high-value assets
  • Operations with named zones, custodians, events, and exception owners
  • Teams prepared to maintain identifiers, tags, batteries, gateways, and records
  • Use cases where a measured pilot can prove value before scale
Before we commit

What we verify first

  • Location accuracy, latency, and read rate vary with environment, tag, geometry, obstruction, interference, mounting, and movement
  • Battery-powered tags add inspection, replacement, charging, inventory, and disposal work
  • Tracking people, personal devices, vehicles, or customer-associated assets can trigger privacy, labor, consent, and retention obligations
  • An observation is not a reliable asset record until matching rules and ownership are defined
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Is real-time location always better?

No. Continuous location costs more and creates more infrastructure, battery, data, privacy, and support work. A custody scan or doorway transition may answer the business question more reliably.

How accurate is asset tracking?

Accuracy is technology- and environment-specific. Define zone, room, meter, or outdoor-position requirements with latency and confidence, then measure them using representative assets and movement.

What should be measured in a pilot?

Useful measures include detection rate, false location, missed transition, accuracy distribution, latency, battery assumptions, coverage gaps, operator time, exception rate, and reconciliation to the system of record.

Standards and referencesReview the source materialView details