How to select a fixed asset management system for SMEs? Lightweight programmes and deployment proposals
The last year, helping a factory that was working on parts, three digitally controlled machine beds were physically located and billed in the same computer, two rounds of depreciation, and the boss laughed about spending one or two weeks around the end of the year "to find assets, to re-check, to make a watch." The core criterion for SMEs to choose fixed asset management systems is actually just one: can you put "where assets are, who's using them, what's worth" within two weeks, and tell them every day instead of being taken away by a list of functions?
From a troupe to the pit: where is the problem?
The plant has more than 800 fixed assets, and it's a list of Excel forms that they can twrite, as they did before: a summary table recording the name of the device, code, date of purchase, original value, depreciation years, plus several separate support tables by workshop and status.
Excel wasn't inoperable, but there were two pits that couldn't be used: the first was a multiplicity of people who were editing the version at the same time, and nobody knew which number was correct; the second was depreciation, change, end-of-life had to sign off, paper process had been changed from Excel, and the billing and physical "two-track" went further and further.
After a double-check, there are three things that really need to be rolled through: the physical location of assets and the accurate records of those responsible; the entire process of acquiring the transfer leaving marks; the monthly depreciation rate; and the direct financial connection. Grab these three main lines, the later selection will not be taken astray from the functional list.
Don't go after Big and Whole: Four hard criteria for light-weight solutions.
The asset management system on the market is broadly divided into two categories. One is the ERP (enterprise resource plan, a large-scale management software that buys, sells, stores, finances all over the board), its own asset module, multiple functions, and financial depth binding, which usually lasts between 3 and 6 months, with the consultant fee plus implementation costs of hundreds of thousands of dollars; the other is an independent system dedicated to fixed asset management, low volume and small focus.
For SMEs with annual revenue from tens of millions to CNY 200-300 million and a workforce of a few dozen to around 200, the second option is more practical. Use four firm criteria to determine whether a system is lightweight enough:
- Time of hand: the administrator has read the document or video and is able to perform new, altered, depreciated operations independently within half a day;
- Functional boundaries: all four items are covered, including card management, depreciation calculation, inventory and reporting, the CRM (customer relationship management), and spare modules of the supply chain;
- (a) Mobile counts: the time when the time was passed when the office had a big screen mouse point, when the inventory must be completed by a mobile phone scan;
- Price range: An annual fee of a few thousand yuan to just over RMB 20,000 is reasonable. For anything more expensive, ask specifically what the extra money buys.
One logistics warehouse company with over 500 fixed assets picked a SaaS plan costing just over CNY 10,000 a year. It rented cloud software without installing its own server, began entering asset records on launch day, and migrated historical data within two weeks. A heavyweight ERP cannot match that pace.
There are only two ways to deploy: clouds or locals.
The deployment of fixed asset management in SMEs is basically two paths: SaaS cloud and localized.
First, there is no IT. One or two companies without an IT job, Cloud Saas is a economy choice, server, backup, version upgrades are in the hands of the supplier; the team has 2 to 3 IT personnel and has no local area network (LAN) requirements, so it can consider localized versions.
Second, the size and amount of assets combined (the number of people operating online at the same time). 500 assets, 20 people in use, are fully adequate for clouds; more than 3000 assets, trans-subsidiary companies, frequent transfers across borders, localization is more stable in response speed and subsequent expansion.
Third, data compliance. Sensitive industries have a specific definition of local storage of data, which is more secure locally. When we do this to a client who does sophisticated instruments, it's because they want all the business data to be on the Intranet, and eventually they get a local version on a medium-configuration server, and there's no problem running for two years.
In either case, three things are identified prior to deployment: backup mechanisms (recommended to provide a full back-up every day, 30 days) and the level of authority (assets administrator, use department, finance, audit authority must be clearly defined), and docking capacity (is it possible to export standard formats for receiving existing financial software).
Pilot Run-through and replicating: How do we get the uplink rhythm?
The most problematic thing is when the system is selected -- a "shoha" -- all data, all sectors, one-off. We generally suggest three steps.
First, pick a unit that is focused on the process. For example, you can start with the administration's office equipment and IT assets, run through cards, sweep the inventory, and depreciate the report as a link, which usually can be seen in 2-4 weeks.
Step two: whether the original book value corresponds to the original system value; and whether the accumulated depreciation and net value are right. Differences are contained within 1%, so they can be fully replicated.
Step three, line up other sectors. In the order of "physical clarity first, and then physical fragmentation," for example, to place workshop equipment and warehouse materials in a position where they can be expanded to local offices and stores. Each batch is given between 2 and 3 weeks of adaptation, during which time the window that runs in parallel with old and new tables will be kept to avoid single-point switching problems.
Shanghai-based Cheeks and Technology, Inc., usually spends one week in the field with an implementing consultant, hand-held clients from pilot to full-scale, with average project life between 6 and 10 weeks depending on the size of the asset and the number of branches.
A list of things that can be compared immediately.
Finally, a list of evaluations that can be scoring in print will follow:
- Core functionality integrity (cards, depreciation, inventory, full set of statements in statement IV, 10 full score is over 8);
- Mobile count support (with an App or micro-inforc, 10 minutes);
- (a) Difficulties in handing out (administrators can operate on their own for half a day, 10 minutes);
- (a) Price transparency (precision of fees, no hidden implementation fee, training fee, 10 cents);
- Implementation support (suppliers provide data migration and online coaching, 10 points);
- Data security (backup mechanism, rights rating, whether publicly searchable equivalent or ISO certification, 10 points).
The total score is over 50, and can enter into business negotiation; below 40, it's recommended that one or two more matches be made. The fixed asset management thing, which is to make sure that the owner doesn't go "where" with the device is depreciated, is repeatedly worrying about the problem. The system is just a tool, the key is to answer the three things that are "where the asset is, who uses it, what is now." When you choose, do not get confused by the number of functions, think about the six above, then decide.

Ms. Lei
Mr. Pang