What are the functional modules of the RFID fixed-asset platform? Structure and integration
RFID Knowledge

What are the functional modules of the RFID fixed-asset platform? Structure and integration

PublishedShanghai Zejie Smart Technology Co., Ltd.

Many people have the first impression of RFID's fixed asset platform as "Classes-Screen-Script," which is just one of its most visible actions. A complete platform that manages assets from a library, to use, to flow, to maintain and to repair the entire life cycle of end-of-life, is only one of them; the bottom is dependent on labels, readers, intermediates and multilayering of applications. Here's how this goes through four levels: "Model-structure-integrated-down."

Functional module: four phases of registration, binding, flow and disposal

Shanghai-based technology is doing projects for people like manufacturing, medical care, logistics, and it's not just a "clip app" platform that really works, but rather a "asset card," a process engine, a report analysis of the report, which forms a line. Based on the life phase of the asset, the modules are broadly divided into four categories.

1. Asset registration and labelling

The first step in all operations is to create a new asset card.

The RFID label is tied after the card has been completed. The common practice is to use a desktop hairer to write the EPC code (Electoric Production Code, unique to each label) to the label, then to put it on the surface of the device or to hang it on an asset. Metal shell equipment selects a metal tag and assets near the liquid environment select special labels.

2. Daily management and location tracking

The day-to-day management counterpart "Who is, where and what status" includes access, restitution, redeployment, maintenance registration, status change processes.

Location tracking is the advantage of RFID's relative bar code. A fixed-type reader is deployed at offices, rooms and key nodes of production lines to match antenna layouts to record asset movements across regions and automatically generate flow logs, save for manual case-by-case scanning.

3. Inventory and discrepancy reconciliation

The inventory is the most used function of RFID.

The result is an automatic comparison with the system account, generating three types of statements: positive and negative.

4. Depreciation and Disposal

The depreciation module is a bridging financial system that supports several common algorithms, such as the average number of years, the workload method and double-declining, which are automatically charged on a monthly basis.

The RFID label is also used to "cancellation" and prevent misreading of end-of-life assets.

Technical architecture: hardware, network, application three tiers of synergy

The platform is divided into three layers from the bottom up, each with its own selectional elements.

Hardware Layer

It consists of three parts:

Network Layer

The fixed reader is deployed by PoE (Power over Ethernet, transmits data and power on the Internet simultaneously), saves for a single pull. Handheld terminals return to the backstage via Wi-Fi or 4G/5G.

When there are multiple readers on the scene, you need middle-sized (Middleware) to do weighting, data filtering, and event consolidation.

Application Layer

The part of the user that really deals with, including Web-end administration backstages, moving amp, telecarding, report center. The technology warehouse is usually Java/SpringBoot or.NET Core, which matches MySQL or SQL Server.

System integration: how do you get through ERP, finance, OA?

The RFID platform is rarely run independently and must exchange data with the existing management system, otherwise asset data becomes an island.

The interface is based on RESTful API and the data format is JSON. If the other system is old and connected only to the database, it needs to be isolated in the middle and not recommended to read and write directly into the other business library.

When you're on the ground, there are a few pits that can be easily stepped on.

Questions about the high frequency in several projects were raised, which said that less deviations could be made.

First, the label is not the right type.The metal environment must be marked with a metal resistant label, which is not readable at all.

Second, the inventory tunnel is not designed to be reasonable.Reader's antenna orientation, power and coverage are subject to site survey and are not subject to the manufacturer's default values. In a warehouse-type project, the antenna is adjusted several times at one angle and the reading effects stabilize.

Third, the initialization of data is moving too slowly.If you go live before sorting out basic data such as asset IDs, names, and locations, the count will show many discrepancies. Spend two to four weeks cleaning up the data and assign codes to existing assets under a common scheme before tagging them.

Fourth, training and institutional alignment are neglected.If the person responsible does not know how to respond to an inventory anomaly when the label is missing, the platform will be bypassed soon.

Back to the question at the beginning.

The core of the RFID fixed asset platform is never just a "sweep" light, but it registers, binds, flows, counts, depreciation, scrapes into a main line behind it, with hardware, networks, using three layers of architecture to support it, and then create data interoperable through interfaces with ERP, finance, OA. It's about whether a platform can work, whether it can run on this main line, or not, if it can match existing systems, rather than write them in a much better frame.

If you're evaluating the program, you might want to focus on a few questions: how much of the total and distribution of assets is going to be managed, what systems are being used, and what extent are you planning to automate an inventory in a few years? These things will be clear, then look at specific manufacturers and structures, and then the selection direction will be more stable.