Knowledge base · Service-King
Municipal assets: records, inspections and RFID inventory
Equipment is scattered among buildings, units and people. What brings the most order is a common method of identification and a record of transfer, rather than the slogan "smart city" itself.

Organise names and responsibilities
Establish a hierarchy of units, buildings and rooms. Each item should have a clear link to the appropriate records. A similar name on several sheets is not sufficient to recognize the item.
| Area | Useful decision |
|---|---|
| Identifiers | Rules for broadcasting and preventing duplicates. |
| Locations | Fixed names of units and rooms. |
| People | Responsibility for confirming movements. |
| Documents | Associate the transfer with the correct item. |
| Access | View scope for local team and coordinator. |
Shared IDs reduce duplicates
The same item can be added to a new unit's sheet even though the previous one still has it in stock. Handover should reassign an existing asset, not create a second item. This requires a consistent identity.
Set rules for assigning identifiers and directory ownership. Keep the numbers used in your existing documents as linked data. When importing, check for similar names and serial numbers rather than automatically linking records based on description alone.
The organisational structure should reflect responsibilities
Building, department, and person can be different assignment levels. Determine who is responsible for confirming the move and who sees the entire scope. A central catalog does not necessarily mean identical access for all users.
Preserve the history of old places when reorganizing. The names may change, but a later report should allow you to understand the earlier handover. Access rules and seating arrangements are part of the design, not just a technical list of fields.
Plan stocktaking around the actual scope
The team should know what places they are checking and how to handle equipment outside the unit. RFID helps detect tagged items, but it does not select the inventory method or settle all differences itself. Formal requirements are agreed with the appropriate persons.
With external assets, there are weather conditions and the risk of damage to markings. Don't assume that an office tag will be appropriate for every piece of infrastructure.
Where Service-King helps
Records, assignments and history allow you to go back to specific equipment and recent operations. Branches can work according to common rules instead of creating independent lists.
Infrastructure map, spatial information system and urban device control are separate scopes. Integrations require confirmation, not resulting from RFID use itself.
Example: equipment moves to another organisational unit
When transferring a computer between buildings, it is not enough to add it to the second sheet. You must maintain your identity, traffic document and proper attribution. Otherwise, a duplicate will appear in the entire organization's listings, and local listings will show the same thing at the same time. In the trial, check that the new team can see the data they need and that the previous location has a clear transfer history. It is also worth agreeing on how to correct an incorrectly indicated unit.
Related topic: computer records.
Different smart city areas require different tools
| Area | Question | Scope |
|---|---|---|
| Equipment | What do we have and who was given to? | Records and workflow. |
| List | What has been confirmed in a specific scope? | Inspection and clarification. |
| Location map | How are zones and assets arranged? | Saved locations and sources. |
| GIS | What spatial data do I need? | Separate system requirements. |
| Controls | How does an infrastructure device work? | Expert design and safety. |
Stocktaking across multiple sites requires a shared standard
Teams should use the same result definition and exceptions. Establish handling of off-unit equipment, extraneous items, and malfunctioning tags. Merging files will not fix different meanings of data.
For RFID, check representative surfaces and zones. In the case of external assets, there are environmental conditions. Agree on the methods and formal requirements of the inventory with the appropriate people. The technology improves physical recognition and does not replace the entire settlement.
The first implementation stage across organisational units
Select a limited group and a few representative locations. Prepare imports, IDs and roles. Complete handover between units and correction of misassignment. Assess whether the history is understandable to both parties.
Service-King ranges show public institutions, inventory and zones and equipment. Integrations with accounting or spatial systems require confirmation.
Scenario: equipment moves to another organisational unit
A computer moves to another building and team. If the recipient adds a new entry while the sender keeps the old assignment, the shared list shows two items. A handover should change the existing asset’s assignment rather than duplicate its identity. Both parties need to recognise the same identifier.
Prepare list, recipient, and confirmation of actual scope. If the device comes with accessories, determine their registration level. After receipt, write down the place and responsibility according to the organization's rules. The history of a previous unit should not disappear because it may be needed to clarify an earlier stocktake or document.
During reorganization, names and roles may change. It is worth keeping a clear connection between old places, instead of overwriting the descriptions so that the previous movement becomes incomprehensible. Agree who manages the structure and who can transfer assets between units. A local user does not need to have full control over the entire organization.
Include selection of the wrong organisational unit and partial returns in the pilot. The correction procedure should retain an explanation without creating fictitious movements. If data will be sent to accounting software, agree the identifiers and handover point. Exporting without the right mapping can carry the same problem into the next system.
The effect can be measured by the number of duplicates, reconciliation time and completeness of location. There is no need to immediately connect records with full GIS or infrastructure control. A shared inventory and history is a stand-alone, useful step that can be developed once needs and data sources have been confirmed. Each further module should have a clearly described scope.
| Area | Practical arrangement |
|---|---|
| Identity | One item throughout the organization. |
| Handover | List and proper confirmation of receipt. |
| Structure | Roles and history of ancient units. |
| Correction | Justified change without fictitious workflow. |
| Export | Mapping to the correct system. |
| Effect | Fewer duplicates and faster reconciliation. |
Deployment checklist
- One asset group and selected sample units.
- Consistent locations and IDs.
- Roles and scope of access.
- Rules for transfers between entities.
- Checking the stocktake result and explaining differences.
See RFID stocktaking in Service-King and example of educational institutions.
Questions worth clarifying before implementation
Will the system recognize duplicates from all sheets?
Do not assume error-free automatic connection. Rules, identifiers, and sample control are needed, especially with similar descriptions.
Is a zone map the same as GIS?
These are different ranges. Required spatial data, sources, and features should be established rather than treating each map as a complete GIS.
Can it be implemented in stages?
This is how you can plan for a rolling scope, provided you have common identifiers and rules that will work even after expansion.
Go to solutions related to this topic
- Public institutions - Order in equipment and responsibility for property.
- Property records - Records of company equipment and fixed assets.
- RFID stocktaking — Physical inventory and comparison of the reading with the records.
- Map of locations and facilities - Structure of zones, shelves and saved places.
Free consultation
Let's create shared records for assets across multiple sites.
Describe units, buildings and transfers. We will establish identifiers, roles and the scope of the first stocktake.
Thank you for your inquiry.
Your message has been sent to the correct department. We will contact you to determine next steps.
Send another inquiry