What are the elements of a full-life asset management system? Processes and data design
Build path: whole-module self-study or a mature platform
Before building an asset management system, most enterprises would be stuck on the same issue -- whether they build a life-cycle system from the beginning or buy off a ready-made platform, and then localize. The former sounds more relevant to their own business, the latter looks more economical, but the core criteria for choosing are: whether your assets are simple accounts, or need to be maintained, depreciated, and modified to end-of-life disposal. If it is the latter, the scope of the module is more important than the freedom to develop. This paper uses the construction path, links cover, data design, and four dimensions of common problems, to determine how much a system should be built.
The advantage of full-module self-study is that the process and data calibration are fully customized to business, so it can fit industry characteristics in depth, such as grid equipment billings, chemical plant modules, hospital video equipment, each with a very different focus. The cost of self-study is also evident -- a system of cover planning, procurement, registration, transport, adaptation, six-step systems that are scrapped, and usually have a development cycle of 18 to 36 months, where teams need to understand both business and engineering and keep their resources invested.
The benefits of introducing mature platforms are that they are fast-lined, process templates are ready, industry best practices have settled in the configuration. The cost is that data models are often defined by product, and you take time to understand their field logic rather than form a table as you think. Budget estimates, based on medium-sized enterprises of around 200 people, are usually between 3 million and 8 million for initial self-study inputs (including manpower, external development, hardware), and outside maturity platforms typically range from 800,000 to 2.5 million (data is common in industry, only for reference).
Shanghai-based technology is more common in terms of service to manufacturing and park customers: platform bottom + key modules are self-studyed. For example, the procurement to registration section uses platform standard processes, transport peacekeeping end-of-life disposals because they involve a wide range of industry-specific asset codes and depreciation rules, and are developed by teams twice. The test is simple: if a change in process triggers a change in primary data, it is worth self-study; if a pure flow stream is used, the selection of standard modules is more cost-effective.
Core: the chain from registration to disposal is unbreakable
If you have only six keywords for the full life cycle -- planning, setting, purchasing, registering, routing, disposal -- it is easy to understand as six isolated functional modules. But what really determines whether a system can run is its connection: the output of the last one is not the next input.
The planning and projecting outputs are the rules on asset codes, projected shipping times, preliminary technical parameters. This segment is one in which many people skip to buy directly, but it is not until the equipment is on site that the code is unruled or the billboards cannot be built.
The central point of the procurement and registration chain is that equipment is bound to the owner of the asset. The design points here are: Equipment exits, serial numbers, contract numbers, and retroactivity between the warehouse line number. We have seen a customer in the project who does warehousing logistics because the contract number and the device number are not tied, and by the time the depreciation count is made it will be based on Excel manual reconciliations, which take almost two months each year.
The transport segment is the largest data volume, the most complex segment of the business. Point check, maintenance, repair, retrofit, state monitoring, individual distribution, each type of business corresponds to a different table of data, but they are all attached to the same asset code. The design principle is: one master data sheet (who records the device, where it is, how in what condition) + more business events forms (recording what happened with the equipment), rather than creating an independent bill for each operation.
The retrofit and end-of-life disposal chain is easily ignored. The retrofit means that the original value of the asset, the depreciation period, may change in the department to which it belongs; the end-of-life involves residual value assessment, tax processing, physical disposal records. If these two links are not properly interfaced into the system, the historical asset will be found to be unreconciled in three or five years.
Data design: master data harmonization or multiple sets of accounts
The data structure is essentially chosen to answer the question: which set of accounts is going to be calculated by the same device. The common two approaches -- one centred on the master data of assets, all of which are quoted through asset codes; and the other, separate units by department or line of business, which are regularly reconciled. The former is an ideal for data governance, while the latter is a product of real-life compromise.
The key to the main data harmonization is to define the particle size of an asset code. The particle size is too thick, a device with multiple subsystems can only count one asset, and failure points cannot be located while moving; the particle size is too small, and there is confusion that separate parts of the same device are depreciated and disposed of separately. One possible way to judge is whether it is possible to calculate depreciation independently, to dispose of it independently, or to perform different functions -- if these three criteria are met at the same time, then to break down into separate asset codes; otherwise, to merge under the parent asset.
Organisation, people, locations, and three main types of data are harmonized in advance. Assets are located in the department, who is responsible, which building, which workshop, and if they have a separate code system, then when you move across sectors, it will be discovered that the system cannot identify "two changes to the same device."
The first is to clarify the lines of responsibility for each set (e.g., one set of financials, one set of business, one set of equipment management), and the second is to establish a regular reconciliation mechanism and a process of discrepancy processing. When Shanghai is in the drop-out of a higher education laboratory asset project, it uses a parallel programme of financial accounts + laboratory accounts, by using a primary key coded through assets, running a reconciliation script every month, triggering manual review when the difference exceeds the threshold. The cost of this mechanism is about 30% more than the amount of data that was managed in the previous period, but avoiding even greater difficulties with later periods.
Common pits: process break points and data islands
Building up the system is just a start, and what really determines how long it takes -- whether the process is closed and data shared.
The most common breakpoint occurs between purchase and registration. When the receipt and inspection process is not robust, asset registers are delayed, and it is only when the financial depreciation is charged that the equipment has been in operation for six months that it has not been recorded. The way to circumvent is to allow the receipt and inspection to trigger the automatic registration process, rather than relying on artificial memory.
The second pit is the incoherence of transport and financial data. The cost of spare parts for maintenance, capital expenditure on alterations, adjustment of asset values to accounting standards, but in many systems these two lines are broken, resulting in an incorrect reconciliation of the depreciated base of equipment on book and actual inputs.
The third pit is a historical data migration. When the system switches, the asset status of the old desk account, the depreciation period, how the amount is charged to move into the new system, directly determines whether it's on the first day of the line or not. Those who have done similar projects know that this part of the work is usually 1.5 to 2 times the budget, and cannot be saved.
The last point that is easily overlooked is the traceability of the end-of-life and disposal chain. An item of equipment usually spans 10 to 20 years, involving multiple modifications, transfers, repairs, if the disposal chain does not keep its historical trajectory in full, the audit finds that it cannot explain the net change in value of the device.
Return to the question of choice at the beginning — whether self-study or procurement, how many modules are covered, how do you agree on data — there is no standard answer, but there is a common starting point: first think whether your asset is an "account" or a "matter," and then determine the complexity of the system. The lightweight account is enough for the level of accounts; it is worth putting in a full life cycle management system that requires assets that continue to have business events throughout the life cycle.

Ms. Lei
Mr. Pang