How does the asset management system programme fit in?
Many people use asset management systems as "a desk-to-book" to set things up, with the result that they are not right on line, that staff are reluctant to use them, and that the system is set. The problem comes first: there is no real alignment of needs and objectives. The starting point for a programme is to make it clear what you want to do and why you want to do it, and then talk about functions and options.
The first pit that makes it easy to step on: "Manipulation of assets" as a "building account."
There are many projects that have been approached for asset management systems, and the demand side has often started with a field list: number, name, specification, location, responsible person ... Looks complete, but ask why this field is here, who will use it in what scenario, and can't answer.
The real value of the asset management system is the result, not the target. The real value of the asset management system is on the chain of "procurement-entry-use-use-maintenance": what money spends on, what it is in, when it should be changed, whether it falls into human hands, and whether it accounts or in kind. If you start by looking at "recording data," there's a typical situation when the system goes online: 100 computers on the face, 87 in physical form, and 13 in unexplored places.
This is the typical expression of an mismatch between demand and target: systems are in, the answer is not. So the first step in programming is not to choose a technical architecture or a software brand, but to answer three questions --
- What business are we trying to solve?
- How much loss or risk is this problem entailing?
- I hope when the system goes online, what's the measure of "do it"?
The three questions were clear, and the following functional design, process combing and data governance were the only ones that had a set of guidelines.
Needs and targets are aligned, three levels of clarity.
First tier: operational objectives and constraints
This floor is written "Why." Like a company that does cold chain storage, it's probably targeting:
- (a) Increase the efficiency of the inventory to 2 days for completion of the full field inventory (past 1 week);
- (a) The loss of the stoppage due to equipment failure, which was reduced by 30 per cent per month;
- Depreciation of fixed assets and end-of-life accounts 100 per cent against financial position.
The same conditions are imposed: budget scope, timing of access, compliance requirements (e.g. mandatory requirements for the asset inventory cycle by enterprises with national entrepreneurship), existing systems that must be compatible (financial system, ERP).
There were projects that targeted "full digitization of assets," which sounded good, but "totality" was borderless and out of control.
Second tier: asset audience and management requirements
This floor is a "whatever." The questions to answer are:
- (a) The assets are divided into broad categories? Whether they need to be managed in a hierarchical manner (e.g., for one-way units of the first category and for two types of asset, by batch);
- What are the key attributes of each asset type? Are there requirements for recording suppliers, protection cycles and depreciation policies in addition to specifications?
- What actions are required to be in the system (procurement warehouse, transfer, inventory, end of life) and what can be handled below line during the asset life cycle?
The target of assets varies widely from one industry to another. A factory with sophisticated manufacturing, which may be a multi-million-dollar imported equipment, requires recording the time of stopover, maintenance cycle, spare parts replacement; and a chain retailing enterprise, where the assets are primarily door-to-door equipment, is managed in a decentralized ZZZQQZ, which is allocated quickly. To clarify these differences, the system does not "one size fits all" for the system.
Third level: verifiable demand entry
Turning the first two layers into a single demand that can be checked for acceptance. This is a critical step, because many of the project failures are "unsatisfactory needs" — the developers think they did it, the demand side thinks they didn't do it, and the ripping goes up to the top.
The standard requirement entry is usually long: the system supports the generation of an inventory list by department + asset class, and the inventory operator's on-site scan completes the inventory, and the document returns to the asset manager with a difference within 2 hours. Each article contains "Who, what function, what result", three elements that can be objectively judged not to have done, whether or not.
Four steps to get the alignments solid.
Step 1: Interview Business Users; Go Beyond the Flowchart
The flowchart is the result of an interview, not the starting point. The real firsthand information comes from a first-line view: how the storekeeper counts, how the maintenance man says it, how the finance reconciles, what data is needed when the audit comes. It's going to take all these jobs over again, and it's much more useful than meeting with the flowchart.
Interview each key role for at least an hour. Ask how they work now, what causes the most trouble, and what they would change. The third question often uncovers the real problems.
Step 2: Map the Asset Value Chain
Draws the life cycle of assets into a cross-axis, and vertically lists the roles involved (procurement, vaults, users, maintenance, finance, audit), and each intersection is clear: what is the delivery, how information flows, whether there are break points. Breakpoints are often the power point of the system.
Take the “equipment repair complete” status in a workflow. If Excel used to be updated at month-end, the system should close the work order at this point and sync the repair results to the asset record the same day. We usually map the value chain first, then decide which functions belong at each step. Plans that start by piling up feature lists will almost always need rework later.
Step Three: Prioritize Requirements
When needs are identified, resources will never be sufficient and must therefore be prioritized.
- MoSCoW:Must have (must have), Should have (should have), Could have (if available), Won't have (not for the time being). Suitable to demand-side decision-making;
- The weighting method:Rating each demand by "business value" and "cost realization" is a priority.
Sorting is not a technical task, it's a trade-off. It's suggested that the "what if you don't do" behind every P0 demand be written out, and decision-making is much faster.
Step Four: Write a Two-Page Proposal Summary
A two-page summary of the right two pages, at least:
- Project context and operational issues to be addressed;
- 3-5 quantifiable operational objectives;
- Targeting and management coverage of assets;
- Core business process nodes (no complete flowchart required);
- P0/P1 List of needs and acceptance criteria;
- (a) Implementation cycle and resource input estimation;
- Main risks and ways to respond.
The summary is the "common language" of both demand and supply sides, and all subsequent discussions have been anchored in it.
Common logarithmic error: these are the most common
Target "others' home system".While it is possible to replicate a system when seeing its peers on it, each enterprise has different asset structures, management pellets and compliance requirements, with few direct reuses.
Focus only on static data, ignoring dynamic events.The account fields are complete, but the transfer, maintenance and inventory of these "action data" are not planned. Half the value of the asset system is in a dynamic event.
Ignore data governance.The two sets of accounts appear on the system as soon as it is available, if they are not resolved.
Underestimating the use of resistance.Why should staff cooperate with the new system? Saves who's trouble and burdens? This level of communication is not working, and the best system will be left out.
After landing: continuous alignment is more important than one-off alignment
Set the plan right. The system is running for six months to one year, business changes, organization changes, compliance requirements are updated, and this is when alignment mechanisms are built: regular visits to core users, quarterly needs resets, data on whether the system really improves its operations.
A simple test of judgement: If after a year of system access, the three things are more smooth, faster and more credible to take stock, end-of-life, transfer, then alignment works; if only one more tool for data entry is added, it means that alignment stops on the surface.
Returning to the original question — how can the asset management system programme be determined? The answer is simply one: without rushing to fix a programme, and before matching business objectives and real needs to the point where acceptance standards are written, the programme will naturally take shape.

Ms. Lei
Mr. Pang