Which is the good asset management software?
Asset management software does not have a standard answer to which is the best. We've reached dozens of selected firms, and the most common error is to ask who is recommended at first sight. The result is that buying over-functional systems doesn't work, or choosing cheap ones that can hold up. The conclusion is straightforward -- matching them by size and management maturity, more useful than looking at brand comparison functions. Here are some of the lessons we've learned from our client selection and landing processes over the years.
I. Place "Size and mature" on the desktop first
The first is the annual factory, which is a multi-million-dollar plant, and the business is changing rapidly, and the owner buys a flagship management software, which costs hundreds of thousands of dollars for implementation alone, and then the one-wire scans are not running -- systems fields are much more complex than actual operations. The second is groups that have already done so well in terms of "saving" the light-weight SaaS, and they've done it, and they've done it, and they've done it, and they've done it, and they've done it, and they've done it, and they've done it, and they've done it, and they've done it all over the organization, and they've done it back to back and back.
Both problems are rooted in the fact that "software brand" is placed before "matching" when you select it. We then unified a course -- first, we cut our customers in two dimensions:Size of assets(Ten million, Billion, Billion and Over) andManagement maturity(Account conformity phase, process standardization phase, data driver phase).
By the way, explain management maturity. "Accompanying" means that the accounting and financial transactions are matched, mainly by Excel and manual; "proceeding standardization" is a set of actions from procurement, to the library, to depreciation and disposal; "data drive" is about seeing data for the full life cycle of an asset and making decisions on it. The three phases vary greatly, with hard-to-set systems, and then they go off.
II. FOCUS OF FUNCTIONAL CLASSIONS, POSSIBLE TO BE DIVIDED
Take an example of a client who does mechanical processing. They have billions of assets, but they don't even have a uniform code. They wanted to take RFID directly with the system that automatically captures asset information using electronic tags and Iot. Our suggestion is to do coding and inventory processes, run "the books" and talk about automatic collection. The reason is simple: bottom data are not good, more effort is being taken on top, more garbage data is going.
And look at another case. A listed logistics company, with assets in dozens of cities and tens of thousands of vehicles and equipment. Their claim is "minorized," which requires light quantification on every site. This is not a good way to deploy the embedded management module in heavy ERP, which is too long a deployment cycle, and customised at high cost. They eventually choose an independent management system that supports mobile-end offline operations, and one point up line is contained within two weeks.
In summary:Ten million scale + reconciliation phase— Focus on coding and inventory, not pursuing automation;Billion scale + process standardization phaseThe focus is on the process closed loop and automatic accounting for depreciation, with multiple organizational competencies to be solid;+Data-driven phase, focus on data governance, IOT access and decision analysis capabilities.
III. Several experiences worth more than the functional list
Do not look first at demo, but at the method of implementation.The same software, which can be found in two things in different players. We've seen demo pretty, delivering a lot of cases that are not so bad. The standard for the implementers is not the number of cases, but whether they have standard processes for the size and industry of you.
The real workload of data migration is the hidden cost.Many vendors only count software when they offer it, and the data are moved to "workload" instead. When they do it, they find that old account fields are not aligned, historical depreciation is not fully compensated, end-of-life assets are in a state of confusion -- this is where the real budget is being consumed.Shanghai is a good place to go.In such projects, data check-ups are generally conducted to clarify the workload and risks of relocation before deciding whether to use tools or hand-held.
The permission model should not be designed until it is on line.Asset management involves a three-way role in finance, IT, business, and one field can cause compliance problems. Our approach is to draw out the matrix "Who can see, who can change, who can approve" at the blueprint stage, rather than to put it back on the system.
IV. A validated selection process
If only one recommendation is left, the next four-step approach is recommended. We have ourselves managed to use this method to get a dozen customers to choose, and we have a significantly higher success rate.
- Business portraitThis step suggests that business leaders and IT collaborate not to allow vendors to draw the asset classes (equipment, vehicle, house, IT assets), distribution, organizational level, and existing processes.
- Needs List RatingThe split "must" "show" "need" is in the third. The necessary must be written into a contract; the stake should be added; the future needs to be paid without now.
- Squeeze Check: Run a proof of concept (POC), a limited trial before signing, with each of three candidates using a real scenario. Track how long it takes and what problems arise. Choose something moderately difficult: a simple scenario conceals problems, while an overly complex one may prompt the vendor to send in a handpicked team that overstates its normal capabilities.
- Contract and online planningData migration, training, online switching and test-run stages are required to identify deliverables and acceptance standards. The above-line is recommended to cut modules, first to familiarize the system with a non-arrival module and then to go on to the core module.
Five, when you get on the line, these are the things that really make up for us.
Ongoing input in data governance.Assets are dynamic, and new acquisitions, transfers, and scraps occur every day. Without full-time or part-time data responsibilities, the system becomes a new Excel graveyard within six months.
Actual usage of the report.Many companies pay for a BI (business intelligence) module but still pull Excel reports manually at monthly inventory meetings. We helped one customer build the five to eight reports management cared most about into the system and send them automatically, so the data actually got used.
Software reverses the management maturity.Asset management software is not just a tool, but also a lever to push an organization to upgrade. Assuming that the model is chosen with a clear vision of the next 2-3 years of management upgrade, it does not simply meet current needs.
The last sentence concludes: Asset management software is essentially a "management diagnosis" -- not a "procurement mission." It's about the size and maturity of the project, it's about the hidden costs of implementation, it's about how to do business on the line -- it's more important than choosing which brand. Picking the most expensive or cheap, it's often the beginning of a pedal.

Ms. Lei
Mr. Pang