What are the types of asset management system software?
At the end of last year, a factory warehouse that was doing sophisticated parts, and the Treasury and Equipment Section had been looking at Excel for three days, and finally found that three imported detection devices purchased last year were not even on the books -- an emergency procurement process, and assets were missing. This "inconsistent" was almost all the trigger points for introducing asset management systems.Coverage, deployment modalities, bottom-up structureThree floors, three layers. First, we'll get these three.
Distinguishing "whatever": functional boundaries of three systems.
Starting with the business scene. A trading company may only care about IT equipment such as office computers, printers and the like, which require a light-quantitative IT asset management (IT Assembly Management, or ITAM); a manufacturing plant is responsible for machinery on production lines, molds, spare parts, or enterprise asset management systems (Enterprise Asset Management, or EAM); And some of the big groups, even writing buildings, parking lots, mechanical equipment, IT assets are managed and require a broader fixed asset management system (Fixed Assembly Management, short FAM).
The three types of functional depth vary considerably. ITAM focuses on the life cycle of equipment, patch management and software licence tracking; EAM is strong in maintenance of equipment, single-issue and predictive maintenance, many interfacing with SCADA (data acquisition and monitoring system), MES (manufacturing implementation system), and FAM is financially biased, focusing on depreciation of assets, recording records, and ending reconciliations. From a user scale, ITAM usually has about 10 to 200 people, EAM single factories can be used at thousands of account numbers, while FAM is cross-sectional, using across locations.
One lesson: look at the type of asset you have in your day-to-day headache, and then push back the type of system. The equipment section has a large number of EAMs, the financial majority group may be more suitable for FAM, and ITAMs for the IT sector alone are enough. Three types can also be combined, such as core EAMs with a light ITAM module covering office equipment.
Look at "Where to put": actual differences in the three deployment modalities
Once the type is determined, deployment will be the next decision point. There are three main types of mainstream deployment: local deployment; SaaS (software, service, directly used by the manufacturer in cloud-operated accounts); and mixed deployment.
Local deploymentIt's a system that is installed on the company's own server or private cloud. The advantage is that data are in its own hands, it's large enough to customize and connect with various internal systems; the disadvantage is that hardware is high, one deployment tends to start at hundreds of thousands of dollars, and it requires specialized teams of people. It is more appropriate for military workers, financials, and large manufacturing companies who have very high data confidentiality requirements.
SaaS modeThe company provides cloud-end services, which are subscribed to year by user. The initial input is low, the account numbers are open and the version updates are sent by the manufacturer. But data are placed on third-party servers, customization is limited, and complex approval processes or special fields are more demanding. SMEs and firms with many branches are much more useful.
Mixed deploymentTake both: Core asset data, depreciation local, compliance and security; perimeter sweeps, mobile end clearance cloud, easy for field staff. The cost is an increase in the complexity of the architecture, requiring local and cloud-based data synchronization mechanisms. From what we're dealing with, finance and manufacturing clients have the most options to mix.
See how? The difference in structure determines the ability to expand.
Many non-technical decision makers will ignore this step, but the follow-up will have a great impact. There are several dimensions to be clearly divided at the level of architecture:
- Single and multi-tenantOne set of independent examples for each individual tenant, which is flexible and cost-shared; multiple customers share the bottom floors, with high resource utilization and low but limited customization. Local deployment is mostly for single tenants, with SaaS almost all multi-tenant.
- C/S and B/S structuresThe early asset management software, mostly C/S (required for a dedicated client), is now the mainstream B/S (direct access to browsers). C/S has continued its advantages in networked workshops and warehouses, and B/S wins are being maintained and upgraded.
- Single-formula and microservices: All the functions of a single-body structure are packed in one program, and deployment of simple but modified is a full-scale operation; microservices are split into business-based independent services such as depreciation, inventory, equipment maintenance is a module that can be upgraded and expanded on an individual basis. When assets weigh over millions or companies have multiple lines of business, the advantages of microservices are clear.
- Integrated capacity: The ability to communicate with ERP (enterprise resource planning system), MES, and financial systems is the core indicator of the assessment architecture. See if the system provides a standard API interface and supports intermediates such as news queues.
When doing a structural assessment, Shanghai-based Sieggers usually asks three questions: what is the estimated asset volume for the next three years, what are the data compliance requirements, what needs and which existing systems are integrated. The answers to these questions basically lock the architecture in its direction.
Back to the selection: Don't just look at the presentation.
It's better to clear up the three layers, and then face the manufacturer.
- First, the pain is clearly shown — whether it is a lack of conformity, slow maintenance response or time-consuming inventory, so that the manufacturer shows the corresponding module and is not being led by a fancy board.
- The manufacturer is required to provide a true case of the same industry (accuracy also) and to give a presentation on the pits that were stepped on in the project, rather than simply reading the functional list.
- It is the industry ' s normal practice to set aside at least 20 to 30 per cent of the budget allocation for implementation services and customization development, in addition to software licence costs.
- The contract was to include clear data attribution, relocation terms and exit mechanisms, particularly the SaaS model, and failure to return the data was a common risk.
The asset management system is not an end-of-the-life tool, but a tool that will accompany operations for long. The type is right, the deployment is clear, the structure is not mined, and the rest depends on whether the team can really use it — more important than any parameter.

Ms. Lei
Mr. Pang