What are the factors affecting the price of the asset management system?
Consider asset systems an advanced version of Excel is a common starting point.
People evaluating their first asset management system often assume that a SaaS product costing tens of thousands of yuan is enough for an equipment list. Then they see quotes of CNY 50,000–60,000 and more than CNY 1 million for products with the same name. The gap usually comes from several underlying variables, not the label “system.”
The pricing framework is based on four layers -- size of assets and number of users in parallel, deployment (SaaS, private cloud, local deployment), depth of integration with existing ERP/financial systems, and compliance and security requirements. The first two are benchmarks, the last two are real price differentials. The next one is open.
Size of assets and number of simultaneous users: two figures that all manufacturers will ask first
The total number of assets and the number of users on the line directly determine the database capacity, the speed at which queries are responded to and the ability to process them together. Almost all the vendors ' quotations are asked first.
Several reference scales: within 5,000 assets, with light-weight scenarios for less than 20 users, annual SaaS subscriptions usually range between 30,000 and 100,000; between 50,000 and 200,000 assets, with hundreds of medium sizes, often ranging from 200,000 to 800,000 annually; over 500,000 assets, with thousands of large enterprises, and the total price of localized deployment and customized development is usually in million.
One easy-to-neglect detail is the modular package. An enterprise only uses bar code scan + base Zinventory counting+ depreciation, and another requires full life cycle management (procurement, library, access, redeployment, maintenance, end-of-life, depreciation, auditing the whole process), which is often three to five times more expensive than it is. Shanghai's best way of communicating with customers often finds that their original version is stretched in six months, and then double-paid for one upgrade, so it is more important to clear the process at the selection stage than to save money.
Deployment: Make sure you buy us a "right of use" or a "ownership".
Deployment sounds like a technical choice, but it is the one that affects budget structures most. Price ranges and applicable scenarios vary widely across the three mainstream approaches.
SaaS: Annual payment of user fees
The public cloud SaaS is a model for multi-tenant sharing of a bottom system, with low initial input, annual subscriptions, manufacturers' package servers and transport. A medium-sized manufacturing enterprise, usually costing between 80,000 and 300,000, looks at the number of modules and users. Its limitations are that data are on third-party servers, and it is not very applicable to industries where localization requirements for data (e.g., core process formulations, sensitive customer lists).
Private clouds: data belonging to their own compromise option
Private cloudes are the business tenants of companies that install their own cloud account, such as Ariyun and Hua. Data are owned by themselves, with initial buy-outs plus annual transports generally ranging from 300,000 to 1.5 million, and annual maintenance fees usually range from 15 to 20 per cent of the initial cost, which is a standard practice in the software industry.
Local deployment: highest one-time input, largest number of customized space
Local deployment is the integration of the entire system on the enterprise's own server for the room, and the combined costs of software licences plus hardware plus implementation are seen from 1 million to 5 million. The benefits are that it has the largest customization space, data completely unconnected, a large asset size, process complexity or very high system stability requirements, such as a large group-wide multibase-management system. The difference between three types of deployment comes mainly from: whether a licence needs to be bought, a server purchased or leased, and a responsibility for transportation. The budget structure is completely different in combination with one of these variables.
Integration and customization: the most easily underestimated "invisible" costs
Many clients only look at the software itself when asking for offers, neglecting inputs from both integration and customizations, resulting in budget overruns during the implementation phase.
Integrated refers to the existing ERP (SAP, Oracle, used by friends, butterflies, etc.), financial systems, HR, MES (manufacturing implementation system). Single points are connected to one system, which usually cost between 50,000 and 150,000; if four or five systems are to be reached, and involving a two-way data synchronization and approval stream interface, integration costs may account for 20 to 40 per cent of the entire project budget.
Customization looks at the specific scene. For example, adding an industry-specific asset type field, adapting the approval process, and automatically collecting data for access network devices, which are not in standard products, need to be developed individually. When doing the project, Shanghai has met a cold chain logistics client, and it takes almost two months to develop just the function of automatically writing temperature sensor data into asset cards. Integration and customization have been added to the list of key variables that often push out hundreds of thousands of thousands of prices to millions.
Compliance and security: invisible but certain price implications
If your business is in the highly regulated sectors of finance, medical equipment, dangerous chemicals and military industry, the security level requirements of the system are directly reflected in the price quotations.
Common compliance items include: data encrypted transfer and storage, operation logs fully retired, permissions to be graded to field level, audit replaying back to each operation. These requirements are not standard version functions, but rather the need to superimpose safety modules on primary products or make specific compliance modifications, which typically increases by 10 to 30 per cent.
In addition, the security level protection of information is often missed. If a system needs to be in second or third place, the manufacturer has to set up an early budget for safety assessments and modifications. This is almost impossible in the financial and medical sectors, and early communication with the manufacturer will save much of the trouble behind.
How do you figure out how much budget you're gonna have?
Back to the real-eminence level of selection, three steps can change prices from "question mark" to "clear number".
Step one, take a bottom count.The four figures are sent to any manufacturer, and the other side can generally report an approximate range.
Step two, set the deployment borders.Ask yourself three questions: Can data be placed on a third-party server? How much is IT team maintenance? Will there be M&As or organizational adjustments in the next three to five years? The answer will be directly from SaaS, private clouds or local deployment.
Step three, inventory integration and compliance.How the bank reconciliations are made and how the ERPs are synchronized, whether there are industry regulatory requirements, and if they are written to the factory, the price-priced vantage point is much smaller.
Ultimately, the asset management system is not a standard commodity and each price corresponds to the amount of work performed. It is much more effective to ask for prices with clear asset base and demand lists than to cut prices with budget figures.

Ms. Lei
Mr. Pang