How is the enterprise integrated equipment asset management system selected?
Many people think that equipment management and asset management are the same thing, and only one module is used to buy software. But actually in factories, parks, equipment-intensive enterprises, these two things are often not matched: this machine is on the fixed assets account of the finance side, and the equipment sector's spot-checking records are in another system, and running is a set of two words. Equipment and assets, which are both sides of the entire life cycle of the equipment, and unbundling is not just data duplication, but also high maintenance costs.
The selection of a system that can manage equipment and assets in tandem is not essentially a choice of functionality, but whether or not to make "physical" and "accounts" available over time. Here's the rationale for this.
Equipment and assets. Why are they always treated as two things?
The type of equipment that a layman is most easily confused with. The device is the real machine in the workshop, from purchasing to buying and selling, which has physical state -- running, decommissioning, waiting for, repairing. Assets are the same machine in the accounting perspective, emphasizing book value, depreciation, department, whether impairments have been charged. The same device, the equipment guy, is concerned about "can it be turned on today, several failures yesterday," and the financial concern is "how much net remains, how much depreciation this year."
The problem is that many companies use two systems to record each. The equipment department uses a single point-checking maintenance software, an ERP or a fixed asset module, and each field is not always the same as the numbering rule for one device. When it comes to annual inventory counts, it has to be matched by human flesh, a couple of weeks.
Even more troublesome, if the physical state of equipment is not reflected in the asset book in time, financial data will be incorrect. For example, a device that adds value after major repairs or that is disabled but depreciated on account would derail the asset report and actual situation. So the first principle of co-management: to make the change in the condition of the equipment reverses the update of the asset account.
The core of co-management is to move data from two sources to one line.
And we've seen a lot of companies that do this at first: there are ERP assets, and then there is a separate set of devices to manage the APP. The two systems maintain relationships by timing or manual import of linkage tables. This approach works in the short term, and three typical problems occur over time.
The first is "orphan data." The system has a new machine, but no one goes to the asset-end recorder, and there is no such device on the financial desk. The second is "time delay." The second is "time delay." The second is "depreciation of the equipment is due for months until Zinventory counting. The third is "unsync" -- the same equipment, the equipment department is classified by "place of installation", the finance is classified by "use department," and fighting with a single calibre when making a consolidated statement.
The real solution to the system of co-management is that, in a data model, equipment and assets are two views of the same object. That is, one device has only one primary record in the database, which carries both "physical properties" (location, state, point-checking cycle, maintenance records) and "assets properties" (original value, net value, depreciation method, subject matter). Any change in field on one side, and a real-time connection on the other.
The following contrast can be consulted with specific reference to synergies in several key fields:
| Business scene | Device Side Actions | Asset side movement |
|---|---|---|
| New equipment arrived. | Enter equipment number, specification, location of installation | Auto-generated asset card, original value recorded |
| Major repairs/technics occurred | Record maintenance work orders and costs | Updates of original value or capitalization of assets |
| Inactive/disable equipment | Change of equipment status | Trigger depreciation policy adjustment or impairment assessment |
| End-of-service disposal of equipment | Submission of a request for scrap | Assets card terminated, residual value and gains and losses recorded |
If the actions in this table are completed in one system, rather than retouching between two systems, the first threshold of co-management has already been reached.
The real dimensions to see when choosing a type
The difference between the equipment asset management system in the market, which ranges from tens of thousands to millions, is not that it looks good on the page but whether the following things can hold.
I. Harmonization of data models
This is the core of a "real synergy" test for a synergetic management system. And the manufacturer asked me if I would take a device from "defunct" to "end-of-life" at the end of the device, and whether the depreciation, residual value, or gain or loss would be automatically processed in the same transaction? If the answer was "Yes, but we need to do one more step-in-time," that's where the two systems were put together, not a symmetry.
How to verify: let the manufacturer demonstrate on site the entire process from the time of purchase to the end of life of a device, whether the physical and asset desk accounts are the same object, number and historical record.
II. Depreciation and configurability of tax rules
The depreciation rules vary widely from one business to another. The common straight-line method of manufacturing, the double-balance reduction, the sum of years; some equipment also differentiates between mandatory end-of-life and accounting depreciation years. A system that adjusts its depreciation strategy by asset class, depending on the intensity of use, is more financially acceptable.
A hyphenation of depreciation and point-checking. For example, a pressure container where the number of one-year check exceeds the specified value, the asset end can set an automatic extension of the minimum useful life, with financial logic and equipment logic automatically linked in the system.
III. Facilitation of data collection in the field
The system is perfect, and the field operator does not want to use it. The co-ordinated on-site end of the system has at least three items: a scan allows for asset information and spot-checking; mobile end operations are offline, back in automatic synchronization in the network environment; failure reporting and maintenance sheets can be done with a cell phone. This sweep is an unobserved step, but any firm that has been audited by ISO 9001 or ISO 55001 knows that the uniformity of asset identification is the first thing the reviewers look at.
IV. Interface with existing ERP, finance software
Many enterprises already have SAP, with ERP systems like friends and butterflies, not an asset module that is intended to replace, but a synergistic one. Let the co-management system do "master data + field data" as source for "sumbooks and vouchers", and the ERP export of "summary certificates" through standard interfaces, which are more mature combinations. Selecting models must make it clear to the manufacturer: what interface protocols are used, what configurations are shown in the fields, whether the rules for document generation can be defined in the system.
V. COMPLETE REPORTING AND DECISION SUPPORT CAPACITY
The ultimate reader of equipment asset management is not just the engineer and accountant, but also the management: OEE, the asset utilization factor, the percentage of the cost of protection to the original value of the asset, the annual capital plan match the budget. The system can get these indicators directly out, deciding whether it can upgrade from "the billing tool" to "the management tool."
And by the way, can a report drill down? For example, see if there's a line of OEE falling, can you point in and see which equipment is actually going on, which shifts are going on, which failures. A report that can drill down is more valuable than a bunch of static numbers.
A few pits that are easy to step on during the landing.
The system is just a start, and the landing process is more of an implementation test than the selection. We have seen many business-selection stages that are very professional, but then go on line, usually focusing on the following points.
Pipe One: Primary data is not cleared first. The device's naming rules, numbering rules, position code is not uniform and the system runs, and the old and new account cannot match. It is recommended that the primary data setup take at least two to four weeks before the system goes online, and that the existing device's numbering, name, specification, location be combed and then re-engineered.
Pipe II: Treating co-management as an IT project rather than a management project. It is not enough for the equipment department and the finance department to have one person to meet with the manufacturer, but it requires a cross-section of project leaders, preferably a deputy or chief worker, who can board when there is a conflict of views between them. The approach of Shanghai-based Skill in multi-purpose projects involving equipment assets is that at the beginning of the project, the equipment department, maintenance classes, treasury, fixed weekly progress meetings, avoid getting online before a key process is found to be missing.
Pipe Three: Pilot selection is too complex or too simple. It's a better way to start running, with the most critical production lines, because of the amount of data, the complexity of the process that causes them to delay, and to break up the team's confidence.
Pipe Four: Ignore the migration of historical data. Whether or not to move old desk data into the new system depends on the purpose. If it is necessary to maintain historical continuity, it must be migrated and field-mapping; if it is only for searching old records, it is possible to keep the old system in a single file. It is much less important to separate these two things than to move them all.
The top line ends. The EAS system is not a one-time project, the number and type of equipment will be adjusted as business changes, the depreciation policy, and tax rules will be adjusted. In the first year after the system goes online, it is recommended that a process review be done on a quarterly basis to see which fields are not set properly, which statements are not read by anyone, which privileges configurations can receive.
Selecting and landing is essentially a choice.
Now back to the question at hand: How do you choose an integrated management system for enterprise equipment? The core is not about how many functions are, but whether the system can make "physical" and "accounts" work under a data set. Think this through, look at the vendor's demonstration, look at the technical architecture, look at the service team, and then get down to the ground, which is less than half as difficult.
For most equipment-intensive enterprises, a qualified synergistic management system is not to worry about at least three things: the only data source that can be configured, depreciation rules are set, field operations are light enough. And so, all that's left is time and patience.
If the current equipment and asset billing of the enterprise has been divided for many years, with the cost of re-opening it at a high cost, it could be implemented first by master data governance + a single pilot, moving forward in stages without having to be put in place one step at a time.

Ms. Lei
Mr. Pang