How do you design the asset management system visualization presentation? board and space view
RFID Knowledge

How do you design the asset management system visualization presentation? board and space view

PublishedShanghai Zejie Smart Technology Co., Ltd.

The visualization of asset management is not "pretty" but a central goal that allows people at different levels to get their own answers in 30 seconds. The board is "indicator-spectrum," the space view is "position-spectrum", and the two are combined, with a drill-to-tape, which basically covers 90% of daily use. Here's what we're going to do.

Point 1: First, make sure you know who to see and what to solve.

This is the easiest step to jump. Visualization, if you come up and talk about what to use, is basically going to get out of line.

It is suggested that the use of objects be divided into three categories:

Each group cares about different questions, which call for different layouts and chart density. List three to five key questions for each of the three groups and design the pages around them so the result does not become a cluttered mix.

Element 2: Three-tier "total-separation-subsidiary" board

The most vulnerable to problems is "all up" and the result is that users can't get a focus on the page. It's suggested three layers:

First tier: overview page

Include only five to eight core KPIs. Choose one or two from each of the following four areas:

Each KPI will be accompanied by a small arrow of the same scale/ring, and a mini-trend map will suffice.

Second floor: Analysis page

Organize by topic, such as asset distribution, maintenance costs, and alert trends. Use two to four charts on each analysis page to answer one question.

Third floor: detailed pages

Supports filtering, sorting, exporting, and key fields are highlighted, such as "overtime unchecked" and "expiring".

Point 3: Chart selection follows the problem, not the aesthetic.

The same set of asset data, asking different questions and drawings are completely different.

Questions to answer Recommended Charts
Comparison of assets by sector/plant area Column Chart
The trend in the cost of protection for nearly 12 months Line Chart
Type of asset composition (item 6) Ring
Level / Plant asset density Heat to fold the plan
Asset-responsible-location relationship Sanki or relational chart

One test matters: can the viewer draw a conclusion from the chart in five seconds? If not, use a different chart.

Element 4: Space view selects the background map, layered over information

Space view is also known as GIS view, map view and key to the visualization of asset management from other business systems.

After the bottom map is selected, the superseding layer is typically four-layered:

  1. Asset point layer: Icon + Colour for Type and Status
  2. Police level: Scratch or red box markings for equipment in the process of warning
  3. Thermosphere: indicators showing continuous density, energy consumption, temperature, etc.
  4. Path layer: Patrol route, secure trajectory, pipe direction

The screen switch allows the user to control the display and avoid stacking everything on a map.

Element 5: Interacting with the "Screen-Dip-Leak-Contact" package

The static map is not enough. Users must be able to "go down."

Filter

Put global filters at the top: date range, organization, asset type, and status. Fewer is better. Users start giving up once there are more than five.

Drill

The KPI on the overview page clicks into the detail, and the details of the individual asset.

Connect

This is the killer of space view -- a field on the left map, and the right view board and list are updated in tandem. When you do asset visualization, Shanghai-based technology uses this set of contacts as a core interactive design, and users feedback "the time to find a device has dropped from minutes to seconds."

Point 6: Performance is pre-considered, not optimized.

Visualization is not the design, it's Carton. A park with thousands of devices, a bunch of points on the map being rendered at the same time and falling apart without optimizing.

Performance issues are being pressed at the prototype stage, or later it is costly to change.

Point 7: Drop in four steps, and make less of a hole.

  1. Needs research: 3-5 interviews with each of the three categories of users, list of issues
  2. Prototype design: Run through the "total-score-spectrum" three-tiered structure using low-confirming frame and even paper sketches
  3. Organisation: 5-8 real users are on trial, video-screened to observe their click paths
  4. Get on line and run.: Go online and see the usage rate, do a major six-monthly re-engineering

The third step matters most. Fixing problems users uncover in a prototype costs one-tenth as much as fixing them after launch.

In summary, the core of asset visualization programmes is never design-driven, but rather...Demand to dismantle + Structure Organisation + Interactive grindingThink clearly of who to look at, what to solve, and then use the "total-point-line" board, connect with space viewing, and finally take the performance. The whole process runs down, and there's a visual panel that can really be used.