What are the elements of systematizing asset management?
RFID Knowledge

What are the elements of systematizing asset management?

PublishedShanghai Zejie Smart Technology Co., Ltd.

The systematization of asset management includes modules such as asset classification standards, process systems, data acquisition, desk account management, dynamic inventory, value assessment and end-of-life disposal. The core is to align the "system" and "systems" under one calibre rather than one set each. Projects that have been done are seen as only system-neutral or simply not system-optimizing processes are blocked.

The system first or the system first.

As many enterprises advance their asset systematization management, the first step is stuck: to write down the system process and then go to the system landing programme; or to go on to the system and then push it back with the system?

Experience is that it takes a week or two to sort assets, to belong to the department, to set down the "bottom rules" of value calibre, and then to make system selections and more stable functional configurations. The difficulty with systemized asset management has never been in software functionality itself, and whether basic data are consistent and authority is clear. Without uniform asset classification and coding rules, data from different departments will not be available, and it is common to count the difference between the number of systems and the physical quantity.

In turn, the system is bypassed by direct access systems, which are often built, unfilled, approved and bypassed, resulting in an empty record-keeping desk and two skins for actual operations.

The test is simple: three questions in a week — on what classification of assets, who is responsible for managing them and how the value is calculated. Three questions have clear answers, and the system is launched no later than it is.

Modules included in the systematization of assets

Full systematization of assets, which typically covers the following modules:

How system processes are aligned with system functions

The module lists the easy, and the most problematic when you actually land is the alignment of systems and systems.

Data caliber is not uniform

Treasury recognizes asset entries in accordance with accounting standards, physical management creates desk accounts from a user perspective, data on both sides are separate, and two records may appear in the same asset. The solution is to place the finance field and the use field into the same card at the system design stage, specifying which one is maintained by which department, when it is updated.

Fuzzy boundaries of authority and responsibility

The asset is used, the user department or the asset department. What budget does maintenance cost go? These are not clear in the system, and the system is only focused on people. The corresponding design of the system is that each asset card binds the specific duty-bearer and responsibility department, which role the process pushes to at which point it goes, and it's easy to trace back.

Business nodes are not fully connected

Assets go from purchasing to being disposed of at least six or seven nodes. Any node allows "underline processing," the whole link is broken. The system level has to be done by forcing each node to be completed online, otherwise the next section cannot go in. The system level needs to be matched with a review, and avoid people being bypassed.

A couple of easy-to-touch pits.

After much more, the project will find that there are problems which recur:

Hardware Light ManagementSome companies spend money on the system, but the responsibility for day-to-day asset management falls to specific people, and the system doesn't work. We have a similar situation in some projects, and then help our clients set up the asset managers' team, then go online, and we stabilize the usage.

A list flow to formThe system says "monthly count" and a few people are actually asked to sign it. It is suggested that the inventory be assigned to specific duty-holders, requiring a code-checking, comparing differences with incomplete automatic reminders.

The code is too complicated.Some enterprises divide the code into a dozen, with the top five six being classification, the last five being year and current numbers, using which the department cannot remember, and entering it on a checklist. Six to eight of the actual exercise is sufficient, and the key is that the rules remain stable.

System and system updates are not synchronizedThe system is changing, the system is not changing, and two sets of rules are fighting each other. This problem requires a clear maintenance mechanism, who is responsible for the system revision, who is responsible for system configuration and regular synchronization.

A few suggestions on the way forward.

If it is intended to initiate the systematic management of assets, this can be done in the following order:

Phase I (one to two weeks)This step will be done without system involvement and by working paper.

Phase 2 (two to four weeks)– System-based combing, drawing the current asset management process along a "acquisition-use-transfer-take-end" chain, marking the input/output and approval roles for each node. Once the flow chart is out, there are no faults.

Phase III (around a month)This step prioritizes products that can be connected to existing ERP or financial systems and avoid secondary data entry. The functionality does not need to be large-scale, but runs through three core modules: desktop accounts, processes, inventory.

Phase IV (continuing operations)The system is reviewed and the system optimizes. The asset data and process performance are re-examined every quarter, adjusting rules to business changes. Shanghai-based Tech Co. usually moves at this pace -- from basic rules to systems landing, to continuous operations -- to a replicable working method.

The essence of systematizing asset management is to hold each asset accountable in the system, to have a record in the system, and to have clear value on the books. Three things are done simultaneously, so management is really less.