What about the asset system? The identification technology route matches the software function.
RFID Knowledge

What about the asset system? The identification technology route matches the software function.

PublishedShanghai Zejie Smart Technology Co., Ltd.

The core of the asset system selection is two matching: identification techniques and asset scenario matching, software modules and management processes. Two things are aligned to the system before it hits the ground; any one is wrong, hardware is expensive and software is all on hold. Reassembly projects delivered over the past few years, pits tend to start with the first step in asset classification.

Asset classification is not detailed. The identification route is blindly selected.

Many companies come up and talk about "no RFID," but the first step is to make sure that assets are clearly divided. At least four dimensions of classification: single value, low space mobility, frequency requirements, real-time positioning.

The example of a factory that does this is made in three stages: their assets are very valuable -- they have a high value on the machine bed and a load, which is almost static, one per month; the plant's fluids, with medium-value molds but frequent moves, are quickly located to the working slot; low-value consumables, tools are available, and labels are too large. The first two sets of barcoded and regularly sweep the plate points, the third only use the registration desk account, and there is no access to the scanned process at all.

The classification is fine, the identification technology is targeted. High value, low flow, long inventory cycle, bar code and handheld terminals are enough; high mobility, fast-tracking, RFID or a two-dimensional positioning program is only calculated; the material-scraper type is directly registered in the system without all hardware input. From past retrospect, when the classification is broad, with one set of technologies covering the full amount of assets, the waste of later hardware input is more apparent.

The choice of the technology, the environment, not the parameter table.

The indicators are often not decisive when they are on the ground.

The other thing is easy to ignore: Once the identification is set, the hardware (hand-held terminals, swipe guns, industrial tablets) must be planned together. The RFID tags are completely useless and must be accompanied by a support RFID terminal or fixed Zreader. Many of these projects have gone through the pit - clients bought RFID labels, field operators were equipped with regular mobile phones, and then they were forced to change all their barcodes back to the bar code, which was largely wasted in the last few months.

The software is not too expensive. Run the main process first.

Asset software feature lists keep getting longer, often running to dozens or hundreds of modules. Once a system goes live, fewer than 30% are typically useful. The reason is simple: features are designed for common scenarios, but every company manages assets differently.

The main process is actually five things: build, take an inventory, allocate, depreciate, and end up. These things run, the system is set. Real-time positioning, smart warning, mobile approval, maintenance plan, inspection route functions are added in order of business development, not spread over time.

For example, a logistics warehouse can get scan-based receiving and dispatch and periodic stocktaking working first, then add location recommendations and excessive dwell alerts six months later. Asking for the entire feature set from day one can stretch development beyond a year. Operational teams can't wait that long, and the project can stall before completion. In our experience, delivering core workflows within three to four months is reasonable. Bring the remaining features online in phases two and three.

Integration and data flow are hidden cost black holes.

Asset systems rarely run on a stand-alone basis, either by reconciling them with ERP, or by synchronizing depreciation with financial systems, or by going to OA. One common error is that the asset system is selected first, then the docking is considered, and it turns out that data specifications, field mapping, and the frequency of delivery are not matched.

The project is set with several points of contact:

When Shanghai-based Sieger Technologies Ltd. undertakes such projects, it usually does a round of data governance consultations before development to clarify fields, calibres, source systems and then enter functional development. This is also a key step in controlling the project’s duration.

The acceptance depends on the scene. Don't run with a functional demonstration.

The manufacturer shows the most smooth way to run, and the client sees everything right in the conference room.

  1. At least three real business scenarios are running in complete fashion, with unusual branches such as inventory discrepancies, transfer across sectors and end-of-life clearances being returned for resubmission;
  2. The pressure test was combined with a count of hundreds of people who could not be coded at the time of the peak;
  3. Data consistency reconciliations are performed, and deviation rates for the three sets of data, namely, system, physical and financial, are within acceptable range.

The three are not contained and the cost of returning to work on-line often exceeds the original budget significantly.

The nature of the selection is the alignment of the condition.

And back to the opening sentence: Identification technology and scene alignment, software modules and processes aligned, systems aligned with external systems. Three layers of alignment, the asset system selection is basically stable. And one more thing that goes down is: a list of constraints -- size of assets, number of count times, budget range, docking system lists, go-live time -- it's much more effective than scoring a functional list.