Overview
Platform Manager is a Mango by Radix IoT module for fleet-level monitoring. Rather than building a dashboard for every site, you describe the fleet once — the sites, the device types, and the metrics that matter — and Platform Manager renders a consistent set of views over the points your tagging already identifies.
Platform Manager is the product name and it is also the label in the UI. You will not find "PI Portfolio" or "PI Portfolio Manager" anywhere in Mango 5.
Prerequisites
- The Platform Manager module installed and licensed
- Superadmin access — the entire Configuration section is superadmin-only
- Data points tagged with
site,deviceTypeanddeviceID. These three tag keys are fixed. Platform Manager does not offer a tag-key chooser, so your tagging has to use these names - Consistent point names across devices of the same type — Device details matches on point name
- One point for each KPI, tagged for the KPI lookup:
deviceType=SITEplus the site'ssitetag, ordeviceType=GLOBALfor the General overview (see Step 3)
Architecture: Four Views, Three Configuration Levels
Platform Manager renders four pages:
- General overview — the whole fleet, with global KPIs and an optional map of sites
- Site overview — one site, with its KPIs and its device list
- Device details — one device, arranged by its device type's Layout
- Active alarms — alarms filtered by site, device type and device
You configure all of it from Configuration, which has three levels. Each level is a page of tabs:
| Configuration level | Tabs | What you define |
|---|---|---|
| Global | General overview, Layout, KPIs | Fleet-wide KPIs and how the General overview page is arranged |
| Site | Site, Layout, KPIs, Columns, Devices | Each site record, its KPIs, its device list and its table columns |
| Device type | Device type, Layout | Each device type, and the Layout that arranges Device details |
Note
Configuration is superadmin-only. The four view pages are not — a non-superadmin with the right data point permissions can open them. That split is deliberate: operators read the views, administrators change them.
Step 1: Create the Sites
Sites are records you create. Tagging points alone does not produce a site — the tag value has to have something to match against.
- Go to Configuration → Site and choose New
- Set the XID and Name. The XID is the one that matters: a point's
sitetag is matched against the site's XID, not against its name - Optionally fill in Customer, Contact name, Contact email and Address
- For map placement, set Latitude (−90 to 90) and Longitude (−180 to 180)
- Set Read permissions for the roles that should see this site
- Use the switches to control what the Site overview shows: Show KPIs on top, Active alarms, Device list
Step 2: Add the Devices
On the same page, open the Devices tab and add one record per device:
- XID and Name
- Device ID — the value matched against each point's
deviceIDtag - Device type — chosen from the device types defined under Configuration → Device type, and matched against the point's
deviceTypetag - Read permissions for this device
Step 3: Configure the KPIs
KPIs are defined on the KPIs tab — at Configuration → Global for fleet-wide metrics, and at Configuration → Site for a single site. A KPI is a small form, and each KPI reads a single point:
| Field | Required | What it does |
|---|---|---|
| Name | Yes | The label shown on the card |
| Primary Point | Yes | A point name, typed in as free text. Mango shows the point with exactly this name that also carries the KPI tags described below |
| Rollup type | Yes | How the primary point's values are aggregated for display |
| Secondary Point | No | An optional second point name, with its own rollup |
| Image path | No | An icon for the KPI card |
Warning
A KPI reads one point, not one point per device. Mango finds it by exact point name and by tag: for a Site KPI, deviceType = SITE plus that site’s site tag (the site’s XID); for a Global KPI, deviceType = GLOBAL. SITE and GLOBAL are literal values, not device type XIDs. So a site total or a fleet total needs a point of its own, often a meta point that adds up the devices, tagged this way. A point named correctly but tagged with a real device type never appears in a KPI card.
Step 4: Verify
- Open General overview and confirm every site you created appears, with its global KPIs populated
- Click into a site and confirm its devices are listed
- Compare a KPI value against the point value you know it should be reading
- Add a device, tag its points, add the device record, and confirm it appears
How the Matching Actually Works
Device details builds its query in two halves. It filters points by the three fixed tags — tags.site against the site's XID, tags.deviceType against the device type's XID, and tags.deviceID against the device's Device ID — and then narrows that set to the point names the layout asks for. KPIs filter differently: on tags.deviceType = SITE plus tags.site for a Site KPI, or tags.deviceType = GLOBAL for a Global KPI, and then on the KPI's point name.
Both halves have to match. Correct tags with point names that do not match the configuration produce an empty view, and so do correct point names on points whose tags do not match. Neither case raises an error; the page simply renders with nothing in it. When a view is blank, check both.
Permissions
Three separate things govern what a user sees:
- Data point read permission — a user only ever sees values from points their roles can read, so the same page shows different data to different people
- Site and device read permissions — each site record and each device record carries its own Read permissions field
- Superadmin — required for the Configuration section itself, but not for the four view pages
Troubleshooting
| Issue | Cause | Fix |
|---|---|---|
| A site does not appear | No site record exists, or no points carry a site tag matching its XID | Create the site under Configuration → Site, and check the tag value against the site's XID rather than its name |
| A site appears but its KPIs are empty | No point has the KPI's name together with deviceType = SITE and this site's site tag (GLOBAL for General overview KPIs) | Check the KPI point's exact name and both tags; SITE and GLOBAL are literal values |
| A device is missing from a site | No device record, or its Device ID does not match the points' deviceID tag | Add the device on the Site page's Devices tab and align the Device ID with the tag value |
| Device details is empty | The device type's Layout asks for point names that device does not have | Reconcile the Layout's point names with the device's points |
| A page is blank with no error | Expected — a tag or point-name mismatch fails silently | Check the tags and the point names, in that order |
| One user sees less than another | Data point, site or device read permissions differ | Compare the roles against all three |
Tips from the Field
Naming Beats Configuration
Almost every empty Platform Manager view traces back to point naming rather than to the configuration. Standardise point names per device type first; the configuration is quick once the names are uniform.
What Drag-and-Drop Does and Does Not Do
The Layout editor is a drag-and-resize grid, and the order of points within a metering group can be changed by dragging. The site and device lists are not reordered that way — those tables sort by clicking a column header.
Copying a Site Configuration
Mango's JSON configuration import/export copies most objects in the system, so it is a reasonable route for standing up a second site that resembles an existing one — export, change the site-specific values, reimport. Treat the details as something to test on your own system rather than as a documented Platform Manager feature, and verify the result against the Site overview before relying on it.
Keep the Site Filter in Mind
Some points are meaningful fleet-wide and some only within one site. Because the site filter is applied from the site record's XID, a point tagged with the wrong site value will quietly appear in the wrong place rather than nowhere at all.
Summary
Platform Manager turns a disciplined tagging scheme and consistent point naming into fleet, site and device views. Create the site and device records, define KPIs on site- and fleet-level points with a rollup, and arrange Device details with a device type Layout. The three tag keys — site, deviceType, deviceID — are fixed, KPIs match on exact point name plus a deviceType tag of SITE or GLOBAL, and a mismatch on either side renders an empty page without an error. Get the naming right and the rest is configuration.