What are the functionalities of the asset management system software?
The functionality of the asset management system software, untraceable, is to work around a "full life-cycle list": assets start with the purchase of the inventory, experience access, transfer, inventory, maintenance, and end-of-life links, each of which requires the corresponding module. The two common intertwinings at the selection are: whether the modules should be fully integrated or slowly, deployed with clouds or local rooms. Our experience is to see not how long the list of functions is, but first what it is most painful now -- slow counting, poorly depreciated, unobserved, repairing, or missing assets. The smallest set of modules that can solve core pain points, is more effective than a system that has full functional but half of them.
Core module dismantling: what is needed and what can be added
The MIS on the market appears to be very different in terms of functional modules, but each module has a very different maturity. Below is the breakdown by frequency of use from high to low.
Basic five packages: inventory, access, maintenance, end-of-life, depreciation
This is the module that most enterprises actually use:
- A stocktaking module: Supports barcodes, QR codes, or bulk RFID reads. RFID uses radio waves so a nearby reader can capture asset details. These options can cut document entry from half an hour of manual work to five minutes.
- Access and restitution: Record who gets what and when they pay back, the liability for assets falls directly to someone, avoiding the risk of being skinned.
- Maintenance worksheetsFrom the reporting to the dispatching to completion, each step is marked and spare parts consumption and maintenance costs are aggregated into specific assets.
- Waste disposalProcessed approval, retention of written-off documents and disposal photographs, and documented financial write-offs and audits.
- Depreciation: Supports the mainstream depreciation methods of average age, workload method and double-declining method, which automatically generate vouchers monthly.
Step-by-step module: positioning, redeployment, reporting, compliance
Enterprises of a small size or high management requirements will be used:
- Asset positioning·: A real-time display of the floor and workshop at which the assets are located, in conjunction with RFID or GPS, suitable for large-scale and dispersed groups of plants and equipment.
- Cross-sectoral redeployments: Asset transferred from one user department to another, approved on a full-way basis and avoided signing off and running back.
- Custom Report: Statement by asset class, user department, procurement time etc., directly from the owner and the finance.
- Compliance and audit trails: All operational logs are retroactive and meet internal control and external audit requirements.
When we help our clients to combe the program, we generally suggest that we run the base five sets and then consider the next-level module. Too many functions at once, high initial training costs, resistance of grass-roots staff, rather than moving forward.
Cost comparison of deployment modalities: SaaS, private cloud, localization
The asset management system was selected and the manner of deployment determined directly how the account would be calculated.
| Contrast | SaaS. | Private clouds | Localized deployment |
|---|---|---|---|
| Initial input | Low. Pay on a yearly basis. Thousands to tens of thousands. | Medium, required to rent cloud servers, 100,000 | High. We need to buy servers. Start with hundreds of thousands of dollars. |
| Transport costs | The manufacturer is responsible. | Vendors are responsible for this part of the case. | Self-supporting teams or outsourcing |
| Data control | Medium, dependent vendor | Higher | Highest |
| Upline Period | One or two weeks. | A month or two. | Two or six months. |
SaaS (software, service, in short, rents the system on a yearly basis, and the manufacturer installs it on a cloud you use) is suitable for a few thousand scenarios of small and medium-sized enterprises and assets. A trading company that works as furniture agents, with less than 500 fixed assets, does not need to localize. A few thousand dollars per year, the manufacturer is responsible for upgrading and backup, saves attention.
The data are on the clouds that you rent, controlable and extended.
Localize for large groups, financial institutions, industries that require very high data compliance. One-time investment is huge, but if the system plans to take 8-10 years, it's not necessarily more expensive than SaaS.
Shanghai's proposal for short-sized, fast-track SaaS is that data-sensitive and large-scale smuggling be clouded or localized. Don't push localization to "look safer" and end up in a much more troublesome position.
Applicable scenario: matching by enterprise size and management complexity
The same asset management system is used in different businesses.
Manufacturing plants: multi-equipment, fast-moving, depreciation
A factory that does sophisticated parts, the equipment moves hundreds of thousands to millions each. How do you account for depreciations every month, how much is used, which machine is always malfunctioning -- these require systems running out in real time. In this scenario, depreciation and maintenance worksheet modules are core, and counting modules are second to inventory.
Chained shop: scattered around, fast-tracked
A 50-door brand, each with a few dozen assets like air conditioners, shelves, cash collections. To get full asset information, headquarters cannot count by people going to each store. In this scenario, mobile endpoints (or codeding in hand data terminals using mobile phones or PDA) and multi-organizational support are key.
Group headquarters: multi-organization, cross-legal, consolidated statement
Large groups often have dozens of subsidiaries, each with its own asset booking. Groups need a unified perspective on all assets and to meet the self-accounting requirements of their subsidiaries. Such needs typically involve multi-organization, multi-account products that generate consolidated statements by organizational dimensions.
Administrative services: compliance, light process
The system is not functionally demanding by the users, but requires that the entire process of asset configuration, use and disposal be followed up with data from the competent authorities.
When you choose to help your client, we ask each other whether it is a discrete or process-making, an organization or a multi-organization, to control the production equipment or to manage office assets.
Select the usual pit: six months is enough to step on one.
The asset management system is chosen as a technical activity, but rather as a pit-screeching exercise. These pits below show the highest frequency.
Pipe One: The function list is as long as possible
Some factory chambers write full lists of functionality, dozens of them. But you find that half the functionality has nothing to do with your scenes, and the remaining half is a simple page. The way to judge is simple: let the manufacturer walk through the demo according to your actual business, not show you their standard functional list.
Pipe II: Ignore data migration costs
Moving from Excel or the old system to the new system, data cleansing and import is far more than you can imagine. Asset names are irregular, coded differently, pictures are missing -- historical data problems are not handled well, the new system is full of garbage. The selection phase allows manufacturers to migrate data, asking whether they can provide a cleaning template.
Pipe Three: Focus on the software itself, ignore hardware
The inventory requires a bar-code printer to tag the asset with a scrutinizer or a PDA terminal. These hardware is not budgeted, the system works better, the count is manual. The selection takes all of the expenses for a "soft and hard" ledger, including labels, printers, scanning equipment, training.
Pocket Four: It's a pretty, real-time response.
The system is only on the line, and the real test for a manufacturer is the speed of response to problems. It's common in contracts to write "7x24-hour responses," but when you get to the database, can you contact an engineer in 10 minutes? Suggesting to check the vendor's client case, ask the old customer after the sale.
Pipe V: Ignore the secondary development costs
Standard products meet 80% of the demand, and 20% of the product is developed individually. If you have a special business process, such as communication with ERP or financial systems, it could cost hundreds of thousands of dollars to customize development. Before signing a contract, you can list where there might be secondary developments, ask for a price.
A short selection list
And finally, I'll help you comb the core of the selection:
- First, you're going to have one or two of the pain points you want to solve, like slow counts, uncalculated depreciation and no one to fix.
- What modules are needed for a push based on pain, and they are not touched without being relevant.
- The total of the deployment modalities, including hardware, implementation, training and secondary development, is clearly calculated.
- Let the manufacturer go over your real business and ask what to do with the specific scene.
- The contract contained specific terms for data migration, secondary development and post-sale response.
- Run small steps on the line, run for three months with a basic module before deciding whether to add an additional step module.
Asset management systems are not a one-time buyout, but a tool to tweak together with processes. It takes two weeks to compare the selection phase carefully and then leaves one or two years less to go through the line, which is all for the best.

Ms. Lei
Mr. Pang