How does the fixed assets management system compare? Functional, performance and cost assessment
At the end of last year, a mechanically processed plant was doing its annual inventory. The warehouse had thousands of equipment and moulds, the asset numbers on the books were not matched to physical items, some had been on the books for years, others had been transferred to other workshops without updating their records. Financial pressure was made, the head of the workshop was pressuring to conclude that the IT department could not produce a credible statement in the middle. It took six weeks before this count, and eventually hundreds of thousands of dollars of assets could still be located.
How fixed asset management systems compare, often starts with this pain. The functionality, the performance, the cost of three things cannot be seen separately: just looking at the list of functions that are easily biased by a sales demonstration, only at being confused by parameters, and at the price that is easily deceived by a surface budget. Putting these three in the same evaluation frame makes it possible to select a system that can actually land.
Phase one: starting with a count, find out what the problem is.
Before comparing systems, list your own pain points. A midsize manufacturer with 300 million yuan in annual revenue will typically have over 20 million yuan in fixed assets, potentially including equipment, molds, vehicles, office furniture, and IT hardware. Count frequency, responsible staff, and depreciation rules vary by asset type.
The pains are common in the actual project:
- The asset numbers were up for three or four years and the guns couldn't be removed.
- Access, transfer, end-of-life without process constraints, relying on Excel and verbal
- Depreciation depends on financial manual work. It takes two or three days a month.
- Management wants to see asset distribution and idle rates, but the system can't get that.
These pain points are sorted in "emergency" and "important" order, so that they can sift out a number of functional fancy systems that do not solve real problems. A plant with a mollusc at its core will require sub-amortization; an enterprise based on vehicle management is more concerned with GPS and annual check-ups. The demand list has no standard answers, but the more specific the better.
Stage 2: Compare functionality. Don't be swayed by the demo.
The most vulnerable aspect of the functional dimension is "looks like it". In each manufacturer's demonstration, the code, inventory, depreciation, report can run, but the difference is actually found at the site. Several functional points are worth asking:
One-dimensional or two-dimensional.In the actual inventory scene, one-dimensional code is less visible in oily and light-poor environments, with a better tolerance for two-dimensional codes, and can carry more information such as equipment specifications, maintenance log links.
Count mode.The inventory mode that supports the handheld PDA terminal and offline cache is almost necessary for the warehouse and workshop environment. Pure phone APP makes frequent errors in weak webs or offline status.
Depreciation policy flexibility.The listed company also needs to see whether the latest requirements of accounting standards are met.
Process is customised.If the process is not changed, it will be difficult to change the code for each business.
Data set.The ability to connect with existing ERPs and finance software is one of the key indicators for the evaluation function. Data isolation makes fixed asset systems another stand-alone account, with a significant discount on their value.
In the functional comparison, it is suggested that a detailed list be taken to go to the manufacturer and separate "demonstration can run" from "real after-line." When we do customer combing, they usually get them to the scene with three typical scenarios of paper documentation, which is a much more reliable way to show the manufacturer than to look at PPT.
Phase III: Performance assessment, depending on performance under real operational pressure
The next step is performance. Fixed asset systems are not as high as electricians, but have their own performance bottlenecks.
Batch processing capacity.When first enabled, there are often tens of thousands of historical asset data to import. Imports are slow, miscalculation is difficult, fields are not visible, are the first-time system's entry point. Optimized import tools can be completed in half an hour; poor processing requires batching, and it can't be done for a week.
Count and send.During an annual stocktake, more than a dozen staff may be scanning and uploading data at the same time. The system's write performance directly affects how fast the count progresses. Ask the vendor for a concurrency test report, or simulate ten people scanning at once yourself.
Query response.For more than three years, a detailed asset search, cross-section asset summary statement, response time should be within three seconds. More than five seconds will make the inventory officer impatient and start using Excel back.
Stability.The deployment structure of the system is one-plane, cluster or cloud-end SaaS. Asset data are critical for the enterprise and single point down risk needs to be considered.
The performance is not a parameter list, but it must be written into the contract with performance indicators and untimely processing, so as to avoid going online and ripping. Shanghai-based Chettech, in its pre-delivery phase of POC, will bring client history data into the real environment, run a full business stream, then use data to speak.
Phase IV: Cost assessment, not just quotations
Prices are often the most sensitive of decisions, but only when price quotations are procured, many hidden costs are missing.
Software licence fees.There is a big difference between the number of users and the number of assets. Larger assets, fewer businesses, costed by the number of assets; more user-intensive, relatively small-assets scenes, more appropriate for the number of users. This needs to be selected in the context of growth estimates over the next three to five years.
Implementation service fees.This is usually a cost of 0.5 to 2 times the cost of software, and it varies significantly. Tens of thousands of dollars are offered but hundreds of millions of dollars are spent on programmes.
Hardware and consumables.The PDA, bar-coded label printer and two-dimensional tag paper are long-term consumables. A company may consume light labels every year at 5 to 10% of the annual cost of the system.
Transport costs.After the system is running steadily, there are costs for routines, secondary development, upgrades, and server renewal. The total cost of the first year is often 2 to 4 times the annual cost of subsequent service.
When assessing costs, it is recommended that a TCO scale of three to five years be made, all items being distributed back into the year.
Phase V: How to make the final choice after a comprehensive assessment
The results of the assessment of functionality, performance and cost are grouped together, with a combined assessment of the next step.
Weight points.For example, for older enterprises with a historical burden, data cleansing is difficult, and the implementation capacity can be reduced to 40%; for large-sized businesses with high volume assets and fast growth of business, performance and expansion weights can be brought up to more than 30%.
Site validation.In the POC phase, it is proposed to select three or five of the most difficult historical business scenarios for running real commercial data. For example, to bring in the category of equipment that has been most frequently scrapped over the past year and see if the system can handle special depreciation rules.
Contract terms.The list of functions, performance indicators, response time and long-term work are all written into the contract, only through oral sales commitments, and follow-up problems are difficult to address.
Long-term perspective.The use cycle of fixed asset systems is usually five to ten years or more. The choice of a manufacturer is not just a product, but also a partner.
In general, the fixed asset management system contrasts not to replicate other people's selection findings, nor to look at the manufacturer's promotion. Each enterprise has different asset structures, business processes, and managerial maturity. Put functionality, performance, cost into a single evaluation framework, and do a realistic picture of its own scene, so that it can choose a system that really fits in, and can be used in a day-to-day way. The rest is to put data quality and process norms in place during the landing phase. Tools cannot solve problems, but good tools can actually get management intent on each device, on every document.

Ms. Lei
Mr. Pang