Centralised governance of assets, users, departments, alerts and site identity for the Optimal® Trend tenant.
Admin access required System configuration is restricted to administrators. Sign in with an admin account to continue.
Hierarchy management
Edit the hierarchy here; every other Trend page reads from this managed structure.
Configuration
Import source data
Drop a CSV, Excel (.xlsx) or P&ID PDF on the area below, or use the file type filters. Excel files of any shape are accepted; the mapping wizard proposes the column to canonical field mapping for review before commit. PDFs are queued for OCR plus vision review (coming soon).
Map each Excel column to a canonical hierarchy field. Pre-filled high-confidence guesses are editable; review the low-confidence rows highlighted below before committing.
| Source column | Maps to | Confidence | Source |
|---|
| Username | Full name | Role | Status | Last login | Actions | |
|---|---|---|---|---|---|---|
| Loading user accounts… | ||||||
| Department code | Name | Parent | Owner | Asset count | Actions |
|---|---|---|---|---|---|
| Loading departments… | |||||
Read-only inventory of upstream and downstream integrations. Edits routed through the SCADA integration page.
| System | Type | Endpoint | Status | Last sync |
|---|---|---|---|---|
| No configured online systems | ||||
Rule-based triggers that drive on-demand acquisition cycles across the collector fleet.
| Rule ID | Asset scope | Trigger type | Threshold | Status | Actions |
|---|---|---|---|---|---|
| No configured trigger rules | |||||
| Rule ID | Measurement | Operator | Threshold | Severity | Active | Actions |
|---|---|---|---|---|---|---|
| No configured alert rules | ||||||
Maintenance windows during which alerts are suppressed and trends are flagged as planned-outage.
| Window ID | Asset scope | Start | End | Reason | Owner |
|---|---|---|---|---|---|
| No configured planned exceptions | |||||
Availability, MTBF and acknowledgement-time targets driving the ARaaS® dashboards.
Internal methodology: the “How this score is derived” column documents how each SLA metric is calculated from live data (per-channel commissioning baselines, exclusions, forensic-stream basis, manual-entry status, etc.). This detail is for administrators configuring the SLA and is intentionally hidden from the client-facing Fleet Overview.
| # | Parameter | Contract | Target | How this score is derived |
|---|---|---|---|---|
| 1 | Data Quality (Vibration & Thermal) | >90% valid transmit, monthly | % | Loading... |
| 2 | Fault Detection Accuracy | Fewer than 5 incorrect / month | max incorrect | Loading... |
| 3 | Early Fault Detection (lead time) | Lead time > 24 h | h (min) | Loading... |
| 4 | Reduction in Unplanned Downtime | ≤ 8% undetected (baseline 10%) | % (max) | Loading... |
| 5 | Online Support Response Time | < 2 incidents > 4 h / month | max slow | Loading... |
| 6 | Onsite Support Respond Time | < 2 incidents (m1-2), < 1 (m3+) | max slow (m1-2) | Loading... |
| 7 | Weekly Reporting | > 90% of weekly reports to RUL | % | Loading... |
| 8 | Alarms reported via Email | All fault alarms emailed on time | % | Loading... |
| 9 | Cost Avoidance | > N$200,000 / month | N$ (min) | Loading... |
Manual items show Pending until a score is entered for the selected evaluation month, or when the saved score is older than 30 days. Blank fields preserve any previously-saved score.
| Bearing code | Manufacturer | BPFI | BPFO | BSF | FTF | Actions |
|---|---|---|---|---|---|---|
| No configured bearings | ||||||
| Timestamp | Actor | Action | Target | Details |
|---|---|---|---|---|
| Loading audit log… | ||||
Logos and accent colour edits are restricted to the Optimal® brand custodian. Contact the tenant lead for changes.
These settings define the benchmark context displayed on Benchmark Metrics. The Benchmark Metrics page remains read-only.