How does the online fixed asset management system work?
RFID Knowledge

How does the online fixed asset management system work?

PublishedShanghai Zejie Smart Technology Co., Ltd.

Let's put the conclusions to the front.

The online fixed asset management system, which combines mobile and approval-based work, solves three typical problems: the lack of consistency in the accounts, the long process for asset recovery, and the lag in depreciation and inventory data. The system is not used consistently, and it is critical that there are no more functions, but processes that are not really available to approvers and on-site users.

Why can't traditional billings hold up the current asset management?

Many companies still track fixed assets in Excel or on paper. It works reasonably well with fewer than 50 assets, but once there are more than 200 or 300, problems tend to surface all at once:

Shanghai-based Sieger Technologies, in its contacts with some early projects, found that the easiest point to get caught was not "no system" but "assets numbering rules are unclear" — three people with one asset could write three numbers.

The system has to run. Let's get these four things straight.

The preparation for landing must be done before going online, in order of course:

I. Rules for classification and coding of assets.The four-level code is coded "Big-Middle-Sate-Sate-Serial" such as 01-03-002-0008. Once the code is established, all documents, labels, reports are quoted in the same number and no more temporary numbers can be issued.

II. Main data harmonization.It is recommended that a person or group be designated as the master data administrator, while others have only the right to apply.

III. Process nodes combing.The full range of assets from procurement to end-of-life is listed: new, requisitioned, returned, redeployed, maintained, scrapped, each ring corresponding to who approves, what documents are used, and what annexes are drawn in advance.

IV. Competences and roles.Asset managers, users, heads of department, finance and approval managers, with separate authority.

We were doing these four things for the first two weeks when we helped our clients get on the line. Looks slow, but running back is going well.

The movement side really saves time. It's three actions.

Many people think that the mobile end is "readable on the phone" and that it's important to use the value of the mobile end, depending on whether three actions are in place:

A customer who does storage has a previous inventory count that takes two weeks, then compresses to three days after moving the end-cleaning disk count, and the error rate is down from 8% to less than 1%. The movement-end is almost useless if it just plugs a computer page into a cell phone. It's really good for a mobile side, and the operation steps are done within 3 steps.

The approval of synergies is not a stack, but a reduction in the number of backs and forths.

Approval workflows are often overcomplicated. A CNY 50,000 purchase might need five approvals. If the asset arrives before approval, staff have to make an exception or retroactively complete the workflow, creating more confusion.

Experience shows that the number of approved nodes is differentiated by amount and scene:

Unit price below $10,000 Use department head to approve.
CNY 10,000-100,000 Head of department + Asset management
More than $100,000 Plus a level of supervisor or finance

The approval nodes of the same type are kept within 3 levels as far as possible.

The approval status is to synchronize with the sponsors in real time -- the most annoying thing is "not knowing who's stuck." Our approach is to add a stopover of more than 24 hours to the list.

The last mile of the system's value is the data running.

The ability to continue using the data is dependent on whether the data is automatically flowing:

After this automatic flow, a manufacturing firm increases the annual reconciliation from 92% to 99.5%, and the closing time at the end of the financial month is nearly half. If the system runs for six months, the asset card is still in manual patches, then it's almost certain that the system is not actually working.

Three of the most frequent pits on the line.

1. Use the system as Excel.The symptoms are all filled in in the notes without filling in the standard fields. The solution is mandatory field entries and regular cleansing of unstructured data.

2. Labels are removed or defiled.The symptoms are that half the labels cannot be cleaned at the time of the count. The solution is to select the label material (the external asset is a filmed PT), print it out clearly and arrange for quarterly inspections.

3. The approval nodes are not covered.The solution is to set up an agent mechanism for approving nodes, to transfer them automatically and to keep a record of the transfer.

I'm gonna give the team a suggestion to get ready to go online.

Do not aim for a complete feature set from day one. Spend four weeks getting coding, master data, workflows, and permissions working. Run a mobile scan-based stocktake before adding relatively independent modules for depreciation, reporting, and transfers. The system's value ultimately depends on whether people follow the rules. Technology helps implement those rules, but even advanced tools cannot compensate for unclear procedures.