Attachments

Which sensor measures where. Multiviz knows the sensors that publish and the measuring points declared from them; the sites and machines above the measuring points are this app's, as your plant hierarchy is your system's. Resetting the app's state keeps all of it.

Sensors not mounted yet

These sensors publish, and their measurements are stored but never analysed until a measuring point is declared from them. Drag a sensor into a slot of a measuring point (or select it and click the slot), name the point, and declare it. The chip on each sensor is the axis it reports in its own frame (X, Y, Z); which of those is horizontal, vertical or axial depends on how it was bolted on, so only whoever mounted it can say. The choice is stored with each stream; record it in your own system too.

Measuring points

Place each measuring point on its machine, with an optional component (Motor, Pump, …) and name; without a name it keeps the label it was declared with. A point on no machine is listed as unplaced on the overview, and still alerts.

Sites and machines

{
  "sites": [
    {
      "name": "Mill 2",
      "machines": [
        {
          "name": "Feed pump P-12",
          "measuring_points": [
            {"id": "PUMP-12-DE", "name": "Pump drive end", "component": "Pump"},
            {"id": "PUMP-12-NDE", "component": "Pump"},
            "MOTOR-12-DE"
          ]
        }
      ]
    }
  ]
}

After a sensor replacement

A replacement sensor publishes as a new sensor, so it appears above among the sensors not mounted yet. Attach it to the stream the old one fed rather than declaring a new measuring point: the stream keeps its whole history across the swap, and its priority, clears and trends carry on.