What modules are included in the fixed assets information system? Data standards and desktop design
RFID Knowledge

What modules are included in the fixed assets information system? Data standards and desktop design

PublishedShanghai Zejie Smart Technology Co., Ltd.

A lot of people think the fixed asset system is a "up-end billboard."

When people first contact the fixed asset information system, they think it's just a few buttons and a few buttons. This is barely working in small-scale settings, but once assets are larger, more cross-sectional, more over the years, problems follow: financial depreciation tables cannot match with physical accounts, no responsible person can be found on the count, and the scrapping process hasn't been shut down for six months.

Fixed assets information systems are essentially a set of assets coveredFull life cycleThe three dimensions of the data and process system (from procurement to end-of-life disposal) are linked to module composition, data standards, and desktop design. These three layers are discussed below.

Five core modules of the system

A complete fixed-asset information system usually has five dimensions. Each module corresponds to a category of business actions, with the modules being linked by an asset code (the only serial number for each asset, which corresponds to its ID number).

1. Asset cards and master data module

This is the system's "ground-based" for storing static information on each asset, including asset code, name, classification, specification model, original value (with total tax price at purchase), date of acquisition, department of use, place of storage, custodian, etc. The asset card in principle "one item at a time", one card against a physical object, cannot be combined into a record -- that is a prerequisite for all business going on behind.

2. Business process module

Covers the entire process of entering and exiting assets: purchasing into a warehouse, receiving and inspection, inter-office transfers, maintenance of protection, cash and loss, disposal. Every step must have a flow record, who requested it, who approved it, when completed, what the attachment is. The value of the process module is to block "oral handover" and "private handling" so that every device can be traced back.

3. Depreciation and financial accounting module

The system needs to support the following parameters: expected useful life, residual value (the amount that is expected to be sold at the end of the asset's useful life), date of commencement of depreciation, need for work-time depreciation, etc. The most immediate consequence of this module's error is a discrepancy between the accounts and the actual assets, i.e., the amount on hand and the actual assets.

4. Inventory and inspection module

Use barcodes, QR codes, or RFID tags on equipment to count assets on mobile devices. Staff scan with a PDA (a handheld data terminal like an advanced scanner) or phone. Actual asset status is sent to the system in real time, which automatically categorizes results as surpluses, shortages, or pending verification. This cuts the annual count from two or three weeks to two or three days.

5. Reporting and analysis module

The output of the report by sector, category, life expectancy, idleness and other multidimensional dimensions provides a basis for decisions on acquisition and disposal of assets. For example, the system should provide automatic early warning and avoid duplication of procurement when equipment of certain types is idle at more than 30 per cent.

Data standard: Code rules to be determined before functional development

The data standard is the "linguistic norm" of a fixed asset system, and coding rules are unclear and the best-used functionality is out of line. This is usually three layers.

First tier: asset classification code.In the country, general reference is made to the GB/T 14885 Fixed Asset Classification and Code (STC) national standard, which classifies assets into large categories such as land houses, machinery and equipment, transport vehicles, electronics, etc., then subdivided them into medium classes, small groups. For example, a digital control bed can be coded "06-01-05" (metallic processing equipment - metal cutting machine - number control machine). The classification is harmonized, across sectors, across the industry areas only with the same statistical calibration.

Second tier: unique code for assets.Based on the classification code, and with information such as year, stream number, the only number of each asset is created. The common format is "06-01-05-2024-0127" meaning: 127 number control machine beds entered in 2024. The flow recommendation leaves more than 5 places, avoiding an insufficient number after the size of the asset has been expanded.

Third level: Key field definition.Which fields are filled, which are filled out, and what is the range of field take-up values, need to form a table from the beginning. Like "original value" must be greater than 0, "getting date" format is unified to YYYY-MM-DD, "use status" can only be used in service, idle, maintenance, end-of-life, disposal of one -- this hard constraint is more reliable than people remembering.

Table design: Three principles determine whether the system is land-bound

The billboard (a detailed account of changes in assets by some rule) is the core data carrier for the fixed asset system. How well designed, directly impactes on the efficiency of subsequent queries, statistics, reconciliations. When we do projects, we usually have three principles.

Principle 1: Keep the main register separate from subsidiary registers.The main account records the current state of the asset (what it is called, where it is used, how much it is), the history of the supporting account record changes (when it was transferred, fixed, depreciated). This design is in the database the structure of the "Main Table + Water Flow Table" and only looks at the master table when searching for the current status, fast; then flips the flow table after history, without compromising daily performance.

Principle II: Consistency with financial accounts.The calibers (the preparation of losses to be charged when the asset is expected to recover less than the book value) must be aligned with the financial system, otherwise the end-of-month reconciliation would be a disaster. The method is: Depreciation certificates generated by fixed asset systems are sent monthly to the financial system (ERP or user friend, gold butterflies, etc.), automatic recording of accounts after receipt of the financial system, amounts on both sides, and consistent lines.

Principle III: Change marks, which cannot be physically deleted.When changes occur in asset information, old data cannot be directly covered and the record of changes — who changed it, what changed it before, what changed it after, when changed. This “striking” mechanism is often key evidence when auditing or asset disputes are being conducted.

From design to landing, there are a few pits that can easily be stepped on.

First, do not pursue "large and complete" . The modules are unopened first, go to the main source data plus depreciation two core modules, then gradually expand to process, inventory, analysis, and then a more secure set of one-times.

Second, allow enough time to clean up historical data. A midsize manufacturer may have thousands of asset records in old Excel registers, finance systems, and purchasing contracts. Duplicate codes, missing fields, and inconsistent units are common. Set aside one to two months before go-live for data cleanup.

Third, moving the end-end count is not going to save. The PC system works so well that it needs to be coded when you take a count. It's much better to land the inventory module as a mobile application and support off-line operations (which can also be used in a warehouse without a network, and then automatically upload back to the signal area).

The modules of the fixed asset information system seem simple, but data standards are not well-established, the billing design is irregular, and many functions cannot be sustained. When Shanghai-based Chettech serves its clients, it usually starts with the data team to codify the classification, define the fields, clear the three things about the account structure, then start the system configuration -- this step is solid, and business processes and reports analysis in the back is really controllable.