How do we build a corporate asset management system? Multilevel control and data sorting.
And the conclusion is, "GASS" isn't a "premature software."
There are only two things at the core of a group asset management system that wants to get really running:Multilevel controlandData Fusion. The former ensures people at each level manage only their own assets. The latter shows how many assets the group owns, where they are, and what condition they're in. Without both, even an expensive system is just a paper ledger on a screen. This suits groups with at least three subsidiaries, assets across multiple regions, and a need for cross-entity transfers or counts. Excel is enough for a small company.
Lesson One: Reconcile the Three Levels of Records First or You'll Be Patching Them Later
Many groups get stuck at the first step after launching an asset system: the records do not match. Headquarters, subsidiaries, and plants use different IDs, classifications, and units of measure. For example, headquarters files an injection molding machine under “Production equipment – Injection molding,” the subsidiary under “Machinery – Class 01,” while the plant operator calls it “the big machine.” One machine, three names, three records in the system.
80% of the reconciliation work we've done comes from this kind of stuff.Main data is not uniform(Source: Public Repossession Report of the Advisory Body for the Implementation of the ERP, 2022-2024). The solution is to run a round of primary data governance before the system goes online: the asset code follows a three-part structure of "group code+sub-company code+flow" such asGT-021-000387, with a fixed length of 16 characters. The first six specify organizational ownership and the last ten are generated automatically in registration order. For the top-level classification, use GB/T 14885-2010, Classification and Codes for Fixed Assets, as a reference and leave room for subsidiaries to customize their categories at the second level.
Lesson 2: Multilevel Control Takes Three Safeguards Working Together, Not More Features
Many suppliers understand "multi-level control" as having different roles with different menus, which is far from sufficient. Real multi-level control needs to be done.Authority, process, levelThree locks are in force at the same time:
- Permission LockThe controls are who can see and who can change. For example, the financials of a subsidiary can look at all of its assets but only modify the asset-use department; the audit function of the group headquarters can look at the entire group data, but only read permissions and no changes can be made.
- Process LockThe transfer of assets requires a "redeployment manager" who transfers the money to the party responsible for the transfer, and a "group asset manager" level four approvals, with each level of clearance and time-consuming lead marks that cannot be passed on or signed.
- Level Lock: Control value and quantity. For example, asset disposals up to 50,000 yuan per transaction are approved by the subsidiary's general manager. Disposals of 50,000–500,000 yuan require the group's chief financial officer, and those above 500,000 yuan must be filed with the board.
It's not hard to put these three locks on one side.ConnectWhen the transfer process reaches level three, for example, the system automatically verifies whether the total assets of the withdrawing and transferring parties exceed the annual budget ceiling, and the verification does not pass through direct interception or manual approval. We have a customer in one of the manufacturing groups that works in Shanghai to select the technology, and when this set of enablers goes online, the average time for approving transfers across sub-companys has been reduced from 11 days to 3.5 days (data source: In-Project Operations Report 2023 Q4).
Lesson three: The hard part of data integration is not collecting, it's in governance.
The data aggregation sounds simple -- it brings the data from the subsidiaries to the group headquarters. But actually, it comes down.90% of the time spent on data cleansing and standardization, only 10% of the time is actually aggregated(Intra-industry implementation experience values, most of them in the SAP, Oracle asset module implementation rewinding).
The common dirty data are of four types:
- It's a lot of stuff.The same equipment is coded differently for each of the three components of acquisition, accounting and depreciation, with three records in the system.
- Unit of measurement disorder: Some assets are "stands", others are "sets", some are directly written in numbers plus units, and cannot be added to the total when group statements are consolidated.
- Status field is missing or expiredThe asset is in "usage" but has been suspended for three years, and there are serious discrepancies between book value and physical.
- Location FuzzyOnly the city, not the specific workshop, could not find the physical items at the time of transfer.
The rhythm of governance is:First count, then go online.Before the system switch, a full inventory is made for 2-3 months, matching bar code or RFID labels (a single tag cost of $0.3-0.8 depending on the material and distance from which it is read). The count rate is recommended to be over 98%, with the remaining 2% being created as separate items for processing, then gradually digested after going online.
Lesson four: Step up is much more than step in.
The most scary thing about a group asset management system is "one-off switch." A group of 20 subsidiaries, if all the subsidiaries are asked to switch to the new system on the same day, it's almost certain that there will be problems -- training is too late, problems are concentrated, transport teams cannot handle them.
The safest thing to do is...Three steps.:
- Step 1: Pilot (3–6 Months). Roll out first to one or two subsidiaries with midsize asset portfolios and representative operations. Validate the three core areas: master data, workflows, and reporting.
- Step Two: Expand (6–12 months). Copy the pilot validated programme to other subsidiaries, fine-tune classification and processes according to industry differences. This phase focuses on interface issues - access to asset systems and existing ERPs, financial systems, and automatic accounting vouchers for changes in assets.
- Step 3: Groupwide Visibility (3–6 Months). All subsidiaries, once they have stabilized data, support multidimensional analysis by industry, region, asset class, and the data board and reporting system at the upper-line group level.
The total cycle usually lasts between 12 and 24 months, with group recommendations of more than 100,000 assets being raised to 24-30 months. Projects that are in a hurry to be completed are typically 2-3 times the cost of late-stage transport.
Proposals for action
If you're going to build an asset management system for the group, three questions will be asked: first, is there a uniform corporate-level standard for the master data standards? Secondly, is there a real need for cross-organizational transfers between subsidiaries, how often? Thirdly, what quality of data is the asset module in existing ERP or financial systems, and can it be used directly?
The answer to these three questions is whether you should start with primary data management, or process combing, or system-based. The order is the opposite, and the cost of returning to work is very high.It's a match.The system is a tool, and what really determines is the governance structure and data standards. Before these two things are clear, do not rush to select software.

Ms. Lei
Mr. Pang