What modules are included in the RFID fixed assets information system?
The RFID fixed asset information system is usually composed of modules such as asset files, label management, repository and change, inventory count, life cycle management, authority and report. The configuration of the module should be defined around the process from registration to disposal and designed in conjunction with label type, reading and writing equipment and on-site operations.
Point 1: Establish an asset file to harmonize information on each asset
The asset file is the data base of the system and it is recommended that a unique number be set for each asset, with a record of name, type, specification model, date of acquisition, original value, use department, location, responsible person and status. Asset numbers are used for business identification, and RFID labels are coded for equipment reading, which need to be matched.
Fields should not be too many. First, you can identify which information is used for searching, inventorying, approving or financial reconciliation, setting the required fill and options; for location, department, category phrases, a uniform option can be used to reduce statistical deviations from multiple forms of information.
Element 2: Configure label management, access to physical and archival information
The label management module is responsible for tag encoding, writing, binding, re-suffying and disablement. You can use the asset material, select a label using environment and read distance, and test the reading effects after adhesion. The metal surface, near or more covert liquids, may affect reading and writing performance, and you should determine the location of the label and installation through field testing.
When the label is tied, check whether the physical number is matched by the system file and tag code. If the label is damaged or replaced, keep a record of changes to the original label and new labels, avoid duplication of bindings, and the old codes are not disabled. Shanghai-based & Chinatech, when planning such systems, integrates label selection, live reading and writing with archive rules into the process design, avoiding only markings but not supporting subsequent management.
Point 3: Retroactive process of inventory, access and change of location
When an asset is in a warehouse, it can be processed in the order of "Registration file - Generate or import code - bind labels - confirm the repository"; access, transfer, loan, return and maintenance should record the operator, time, location, new location and approval status. This allows for reasons to be found in the change record when the account does not match.
For operations requiring approval, the applicant, the Approving Officer and the effective node should be identified. For example, the transfer order is approved before the asset is updated, the application is not completed and the system position has changed. If there is a procurement, financial or personnel system, you can first identify the fields and synchronized points that need to be exchanged, then evaluate how the interface works.
Element 4: Design inventory tasks, distinguishing between reading and processing results
The inventory module usually contains tasks created, scope set, live read, discrepancy check and result confirmation. Administrators can generate assignments by department, floor, storeroom or asset class; staff members use hand-held reading/writing devices or fixed devices to collect label information, which is compared with the system book listing.
The inventory results should be distinguished between cases where the asset is lost, unread, not located, not located and not read outside the system. Without reading it, it is not appropriate to determine whether the label is damaged, there is a cover on the scene, then the result of the processing is reviewed by the responsible person and the outcome is recorded. The count is recorded, the reviewers are held up and the time for completion is left to facilitate subsequent inquiries.
Element 5: Supporting day-to-day management with life cycle, privileges and statements
Life cycle module maintenance, maintenance, loan, end-of-life and disposal changes in status; reminder rules can be used to use the time-depiry or return tips. Permission modules are viewed by job setup files, business applications, approvals, inventory and data export privileges, and key operations logs are maintained to reduce error and overstep actions.
The report can be derived from the actual management problems of the number and value of assets, departmental distribution, idle status, inventory differences, maintenance records, etc. Before going online, it is recommended that a department or a warehouse be selected for trial, checking archive fields, checking label reading effects, approving paths and report calibres, and adjusting them to feedback. The key is that each business has a clear data source, handling responsibility and record of results.

Ms. Lei
Mr. Pang