How do we choose the corporate asset management software? Need to comb and function.
RFID Knowledge

How do we choose the corporate asset management software? Need to comb and function.

PublishedShanghai Zejie Smart Technology Co., Ltd.

An electronic components plant invested in asset management software. A year later, the records and physical warehouse stock differed by nearly 20%, and reconciliation still depended on Excel. What went wrong? Only after buying the software did the plant discover that its workflows did not fit the system. Staff found it awkward and the configuration had to be revised repeatedly.

And then I'm gonna ask, "Do you want to get this straight?" So, it's not a lot of things that are going to happen with the asset management software, but rather, it's not like there's a problem with pre-processing, and demand doesn't match the function. First, you ask yourself, and then you find a matching product -- which is at the core of the pit.

Don't look at the product. Ask yourself first.

Many companies are wrong to choose the first step – they organize a team to see the manufacturer's demonstration, and then take a look at the thicker set of data, and come back to the meeting and find that there are different functional points of concern.

The need to comb is three things, each of which has to be in specific detail:

And you can write these three things into a list, and each of them goes, "What's going on now, what's the pain, how is the system working." This list will be the basis for all the products that you've been doing. The partners who have been through this selection know that without it, they're going with the sale; with it, the initiative is in their hands.

Translation of the list into specific functional requirements

The list of requirements cannot be asked if the manufacturer can do anything. It is not a matter of translating demand into a specific functional description, for example, "I want to count simple" but "Cash points to support mobile end-cleansing, which can operate offline, and one-way drives at least 500 assets, with an automatic matching of the inventory results with system accounts and generating a discrepancy report."

This is a crucial step in quantifying the vague demand, and several commonly used dimensions of judgement can be consulted:

The more specific the functional requirements, the less it is possible to communicate with the manufacturer, and the more it is possible to test directly whether the manufacturer is able to do so.

Check the list one by one, not just a demonstration.

The manufacturer's demonstration usually shows only the best -- smooth, data-friendly and amazing. But your business is not a demonstration scene, but you have to check with your own list. There are a few tricks for validation.

Try it with your own data.Take a list of real assets that are unsensitized, and let the manufacturer run the whole process of importing, taking an inventory, generating a report in the test environment. One or two hundred data pieces run down, the system can hold it, it's not easy to do it, it's wrong, it's all obvious.

Let's get front-line staff involved in the test.The main thing that happens at the demonstration is IT and procurement, and it's really a warehouse manager and finance. It takes them half an hour to try, and the staff's response is often more credible than the firm's commitment. Shanghai-based Tech has a habit of having its client's actual users participate in UAT, so that the real user can approve the system instead of go online and find no one willing to light it.

Ask for implementation and servicesThe software itself is just the beginning, follow-up implementation training, data migration, secondary development, and the response to the problem is the cost. How long is it going, there are no local service teams, the response time is hours, the system upgrades are free -- all of this is written into the contract.

A few easy-to-penetrate pits.

I've seen too many company-speculation mistakes, focusing on a few high frequency:

♪ To pursue the big and the bigThe first set of asset management platforms was put in place, and the underlying functionality was not solid and advanced modules were not working. Asset management software is not as expensive as it could be, and it solves 80% of your daily problems at a reasonable price, often the highest value for money.

Ignore Data MigrationWhat about historical asset data in the old system, Excel, or even paper books? The availability of migration tools, the volume of data cleansing and any disruptions during migration are assessed in advance.

No Extensions set asideToday, 1,000 assets are managed, possibly 50,000 in three years; today only one city, and tomorrow there may be multiple branches. The system does not support multi-organizations, multi-banking, smooth expansion, better to confirm in advance.

Ignore MoveendThe ease of mobile phone scanneding is very important in the case of inventory, maintenance, field scenes. A system that does not have a moving or a perfunctory end of movement can collapse during the count season.

There's a few things to do after the decision.

The system is on the line. Experience shows that these things work better:

Back to the factory, they re-combine their needs, change a tool that better fits their own processes, harmonizes asset code rules, run through two warehouses and expands the whole plant, eliminates the difference in accounting after six months, and finance doesn't need to get Excel to fill out. The software itself is not much more advanced, but it's a match.

There is no standard answer to the choice of asset management software, but there is a clear line — first to clarify your needs and then to find a match, to verify that it is in place and to sign a contract. The process is backwards and the expensive system cannot be saved.