Your fleet of terminals, without a spreadsheet
Which device is where, in whose hands, in what condition, and until when is it under warranty? Today this information lives in a spreadsheet, when it exists at all. AMS turns it into a record in the software, next to your products and your warehouses.
Right required
Just 1
States of a unit
4
Starting catalogue
Zebra TC22, 7 variants
1
right to manage everything
4
states: in service, in stock, in repair, retired
100%
history in the audit log
0
data lost by closing the module
What is the AMS module?
AMS = Asset Management System. Here is the idea in one sentence:
"A loan card for every terminal, scanner or printer in the company."
The model describes the device
Brand, specifications, photos — either from the catalogue provided by GSE (Zebra TC22 and its accessories), or added by your organisation.
The unit is the real device
Serial number or asset tag, status, assigned to a person and/or a warehouse, purchase date, warranty end date — exactly what you look for when a device goes missing.
The history writes itself
Every status or assignment change goes straight into the audit log, with the before and the after. Nothing to tick, nothing extra to fill in.
It's like a library loan card…
…except it's GSE-Web that keeps it up to date with every movement, with no re-keying. You never retire a device still on loan, you never lend a retired device. The software refuses both, on its own.
Enable the module in two moves
Closed by default for every organisation: a company with no mobile terminal has nothing to do with it.
The platform opens the module
From "Manage organisations": the organisation → module checkboxes → AMS → save. Nothing is ever deleted: closing it hides it, reopening it restores everything.
The administrator holds the right by default
A single right, "Manage asset fleet", granted automatically to the organisation's administrators. No read/write split to configure: a deliberate choice, to keep a module that should stay simple from getting complicated.
Nothing is ever deleted. Closing the module hides the models, units and their history; reopening it restores all of them, intact.
An archived warehouse, a unit that stays if a warehouse still referenced by units is archived, its name stops appearing but the unit keeps its reference — the assignment is simply corrected from its record.
The four states of a unit
In stock
The default state of a new unit
The device exists in the fleet but is assigned to no one. A new 4-slot charger, for instance, stays "in stock" until it is put into service.
A unit in stock can be linked to a warehouse without being assigned to a person.
In service
The device is in use
Assigned to a person and/or a warehouse. The record shows the holder's name, resolved by the server — never something to cross-check against another list.
Assigning a retired unit is rejected by the server, not just discouraged by the screen.
In repair
Out of action, but not lost
Useful for tracking a device sent for servicing without taking it out of the fleet or losing its history.
The status change is logged with the before and the after, like everything else.
Retired
Out of service, never out of the fleet
A device that's out of order is retired rather than deleted: its history stays available.
Retiring a unit still assigned to someone is rejected: it must be freed up first.
What the software guarantees on its own
Four rules checked by the server, never left to the team's discipline alone.
The GSE catalogue can't be improvised
A model from the catalogue provided by GSE (Zebra TC22 and its accessories) is read-only for your organisation. Only the platform administrator changes it, on the server that manages the fleet.
Retired ↔ assigned: incompatible
You can't retire a unit still assigned to someone, and you can't assign a unit already retired. The server rejects both, not just the screen.
A member holding equipment stays
A user still holding a non-retired unit isn't removed from an organisation — this rule still applies even if the module is closed in the meantime.
Nothing is lost by closing the module
Closing AMS for an organisation hides its models and units; reopening it restores them intact, with all their history.
A ready-to-use catalogue, a quote in one click
KLS Concept provides a first catalogue of terminals (Zebra TC22, its seven variants, its six accessories) set up on every server — every organisation also adds its own models, Honeywell, TSC or Toshiba TEC printers included.
A model's record, at a glance:
Large cut-out photo, essential specifications in tiles (OS, processor, screen, battery, IP rating…)
Variants as chips — the TC22 has seven, each with its own scan engine or NFC support
The model's accessories in a strip, at a glance
A pre-tax price identical for every organisation, shown only if the model is for sale
Quote in one click
On an orderable model, a "Quote" button composes a priced request: quantities, calculation done by the server, a PDF ready to send with "Approved for order" or "Request for pricing" depending on availability.
Published across the whole fleet
An addition or correction to the catalogue, made once by the platform, is published to every server — schools included — so none of them is left on an old version.
Zebra® is a registered trademark of Zebra Technologies Corporation. GSE-Web is neither affiliated with nor endorsed by Zebra Technologies Corporation.
The vocabulary, one sentence each
Four words are enough to understand how the fleet is organised.
Model
A device's generic record: brand, specifications, photos. Provided by GSE or added by your organisation.
Variant
A version of the model with genuinely different specifications — the TC22 has seven, depending on the reader or the built-in module.
Accessory
A model in its own right, linked to the main model — a case, a holster, a spare battery.
Unit
The physical device itself: its serial number or asset tag, its status, its holder, its warranty.
GSE catalogue
The models provided by KLS Concept, identical on every server, read-only for organisations.
Retired
The status of a device taken out of service — never deleted, its history stays available.
Every piece of data lives at one level
The model describes the device in general, the unit describes the actual item — never mixed up.
| Level | What lives there | |
|---|---|---|
| Platform catalogue | ||
| GSE models, variants, accessories | Zebra TC22 and its versions, photos, pre-tax price and sale mode, display order — identical on every server | |
| Organisation | ||
| Organisation's model | A device the GSE catalogue doesn't know about — brand, name, category, imported or generic photo | |
| Own variants and accessories | The same notions as the GSE catalogue, but for an in-house model | |
| Physical fleet | ||
| Unit | Serial number or asset tag, status (in service, in stock, in repair, retired), assignment, purchase date, warranty end date | |
| History | Every creation, status or assignment change, with the before and the after | |
A module
reversible by design
AMS opens organisation by organisation, never turned on by default: a company with no mobile terminal has nothing to do with it, and closing the module for another one costs it no data at all.
A single right to distribute, no read/write matrix to configure
Automatic history: every enforceable action goes into the audit log
GSE catalogue identical on every server, corrected once, published everywhere
Warehouse and person names already resolved by the server — never three lists to cross-check
"serialNumber": "PDA-00123",
"model": "Zebra TC22",
// Assignment resolved in one pass
"status": "in_service",
"assignedTo": "Julie Martin",
// Warranty calculated in the organisation's timezone
"warrantyUntil": "2027-03-12"
Get your asset fleet
out of the spreadsheet
A ready-to-use catalogue, a right to distribute, a history that writes itself.
Frequently asked questions
Does the module handle equipment orders?
Not yet. The quote is the first step towards it: it composes a priced request, but tracking the order through to delivery and automatically creating the units received are still being worked on.
Can equipment from a brand other than Zebra be inventoried?
Yes. The GSE catalogue is a starting point, not a limit: your organisation freely adds its own models — Honeywell, TSC or Toshiba TEC printers, scanners from any other brand — with an imported photo or one of the generic images provided.
What happens if I disable the module?
Nothing is deleted. The models, units and their history are hidden, not erased: reopening it restores everything, intact.
Who can change the catalogue provided by GSE?
Only the platform administrator, never a client organisation. An organisation that tries to write to a catalogue model gets an explicit refusal, not a save that silently has no effect.