What needs attention to be paid to the development of asset management systems for customization?
RFID Knowledge

What needs attention to be paid to the development of asset management systems for customization?

PublishedShanghai Zejie Smart Technology Co., Ltd.

The most vulnerable places for the development of asset management systems are often not technology, but demand boundaries are not clearly defined and acceptance standards are not quantified. We have drawn up a test in many projects: "do what" and "do nothing" first into the document, then start to develop, and then there will be less than half of the conflicts that follow.

I. THE BORDER OF REQUIRED: FROM "WHAT YOU WANT TO "WON'T DO WHAT YOU DON'T DO."

Many clients start with a long list of functions, covering procurement, access to the library, depreciation, inventory, statements, mobile-end approvals, etc. But before you develop, one thing must be done: clearly distinguish between "first phase has to be delivered" and "subsequently extended."

The way to distinguish is simple. Two questions are asked:

Include a feature in phase one only if both answers are yes. If either answer is no, move it to a later release. When Shanghai Zejie helps customers define requirements, we mark each feature P0, P1, or P2. P0 is essential for go-live, P1 is needed within a month after launch, and P2 depends on what actual use shows.

The immediate benefits of this are that the first development cycle is manageable, and the scope of acceptances is clear, so as to avoid half finding a functional logic too complex to slow overall progress.

II. Cost and functional coverage: the more functionality not the better

The cost of custom development usually consists of three components: the number of functions, the complexity of data interfaces, and the precision of personalized interactions. Of these, the number of functions is the variable that can be most easily raised.

For example, a medium-sized manufacturing enterprise wants to have an asset management system that only covers the inventory of assets, access, end-of-life, inventory, depreciation automatically calculates these five core elements, with a development cycle of approximately 2-3 months; if it is to be made in two-way with the financial system during the same period, mobile end-cleaning disk points, approval flow self-defined, BI board, development cycle will be drawn up to 5-6 months, and the budget usually doubles.

The test is this: if the point of pain is "not true" or "no assets", you give priority to the core; if the point of pain is "slow report" or "check card at a certain point," then it's going to solve process problems, not systemic ones, and blind stacking will only make the system harder and harder.

III. THE RECEIVING AND ACCOUNTS: Quite the "good" and "good" and "no difference in the reconciliation."

The most common dispute in the acceptance chain is the difference between "I feel done" and "I feel finished." To avoid this, it must be written as a quantifiable entry before development starts.

A qualified acceptance document contains at least three pieces:

When Shanghai-based Scratch Technologies delivers the project, they ask the client's business manager and the development officer to sign the acceptance document, and then they cross the article after the development is completed, and then they will be officially delivered. If there are "unclearly stated" cases, then both parties have a case for it.

IV. Common pits: the three most recurring problems

After several projects, we found that the highest probability of a demand boundary and receiving-and-receiving pits were concentrated in three categories:

1. Spreading demand.Adding features throughout development can turn a three-month project into a six-month one. Set a requirements freeze. For example, from the second week of development, send all new requests to the next release review instead of inserting them into the current work.

2. Acceptance and inspection are conducted only for presentation and not for data.The developers show the process, and the client signs it "looks good," and then they go online and they find certain scenes that are wrong. The way to circumvent is to check and accept real business data, not demonstrate data.

3. Depreciation logic is inconsistent with finance's accounting rules.The depreciation method of an asset is average age, workload, double-degregate, etc., the financial system's calibre is often linked to tax requirements, and if a developer achieves it by common logic, then it can go online and reconcile. The circumvention is by involving the financial sector at the demand stage, clearly depreciating the calibration, changing the processing, and ending time points.

To sum up, the success of customization development depends on two things: whether the demand boundary is clearly written and whether acceptance criteria are quantified. Both things are solid, and the rest of them will be done in a sequenced fashion.