What are the functional modules of the RFID fixed-asset platform?
Industry News

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

PublishedShanghai Zejie Smart Technology Co., Ltd.

At the time of inventory, one device in the warehouse is labelled and its licensee cannot be found in the system; another equipment in the office has a record but no physical object. The RFID fixed asset platform addresses problems that are not matched by the account, the item, the location and the responsible person. The common structure consists of the asset desk account, labels and collections, business processes, privileges and data, the report interface, etc., which is critical to leave a mark on each change.

The inventory site found discrepancies: first, the asset desk account and identification.

A platform is based on an asset desk account. Each asset requires a stable asset code and records the name, type, specification, acquisition information, use department, responsible person and current status. The RFID label usually includes or relates to the asset code, from which the asset is identified; the label itself does not allow for changing licensees, location, etc., to be carried in order to avoid any disconnect between the information updates and the table account.

When actually built, the old desk accounts are prepared, duplicated records are consolidated, and it is clear which assets need to be marked and which information must be maintained. For items that are not suitable for labelling, you can keep bar code or manual check and mark identification in the system. Shanghai-based Quiztung Ltd. will use asset coding rules, field calibres and label links as a pre-discussion issue, avoiding leaving underlying data issues at the inventory stage.

Unstable reading at count: layering of labels, equipment and collection services

The live collection usually includes RFID tags, hand-held readers or fixed reading and writing devices, and the collection service that receives and organizes readings. Once the reader has a label number, the collection service also handles duplicate reading, time stamp, device numbering and regional information, and then transmits valid records to the platform. So, the platform sees more than "reading a label" but it can also judge whether the asset is in the expected area by place and time.

Read distance and recognize effects are influenced by label type, metal surfaces, placement direction, environmental cover and reading/writing device settings. The field effects cannot be presumed by the only equipment-named parameters. A small range test is available for different materials and placement positions, which is recorded before the line, and where read and error are repeated, and the label installation and collection range is adjusted. The fixed device is suitable for border identification such as exit and exit, and the handheld device is suitable for manual inspection by room or area.

Information lag after asset flow: recording changes in business processes

The new, received, redeployed, borrowed, repaired, returned and scrap items should be corrected by business process update rather than relying on an inventory only. Each type of process can set up the applicant, the Approving Officer, the operator, status and time record; the responsible department and place of storage are updated simultaneously after redeployment is completed, and the state is marked as being maintained during maintenance. When discrepancies are detected, the system should support the generation of records to be verified, then revise the billings and retain the content before and after the change.

The report is not up to date: check data boundaries and system interfaces

The platform application layer is responsible for pages, queries, processes and reports; service level rules and interfaces; data layer saves assets, labels, process and capture records. Between layers you need to identify the source of data: which system maintains the asset master data, how people synchronize with departmental information, who confirms the inventory results. When the interface is abnormal, you can see the time of transmission, the state of processing and the reason for failure, and avoid that data is not synchronized but the business is mistakenly considered completed.

Selecting or building, you can first verify the complete link with one department or type of asset: build a file, postmark, collect, take an inventory, confirm differences, assign updates and output. The focus is not just " read-to-labels " , but also whether the asset code is matched, whether the process is completed in the back desk, and whether the anomaly is traceable. The architecture module can be expanded gradually by management scope, but the asset code, change rules and permission boundaries should be determined at an early stage.