Sites & machines

Multiviz stores nothing above the measuring point: the sites and machines are this app's, as your plant hierarchy is your system's. Place each measuring point on its machine here, or import the whole hierarchy from a file. Resetting the alert state keeps all of it.

Unplaced measuring points (7)

Add a site and a machine below first, then place these on it.

Measuring point	Priority	Place on
DE 13db870f-7126-4440-8a66-6d7d93abaaac	Low	no machines yet
NDE 38751221-a56d-4693-84e1-8d8a8d69f159	Low	no machines yet
NDE 928eca2f-22fe-4967-8371-a88704a68bc0	Low	no machines yet
DE 8f62df87-e90a-4e9a-babb-42aeae439be9	Low	no machines yet
-DE -DE	Not analysed	no machines yet
-NDE -NDE	Not analysed	no machines yet
A-NDE A-NDE	Not analysed	no machines yet

Sites

Import or export a file

Export the current hierarchy — the same format; export, edit and import again to change many points at once.

The format

{
  "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"
          ]
        }
      ]
    }
  ]
}

id is the measuring point id the deployment lists. name and component are optional; without a name the point keeps the label it was declared with. A bare string is just the id. Sites match by name, machines by name within their site. Points may be listed before they are declared. By script: curl -F file=@hierarchy.json https://example.<namespace>.multiviz.local/hierarchy/import