Shows whether fleet availability is increasing or decreasing over the selected period.
Total downtime hours and breakdown closures — lower is better (improvement).
Recent Searches
| Operation | Work Place | Type | Size | Equipment ID | SECTION | OEM | Actions |
|---|
| Equipment | Task | Interval | Last Done | Due | Days Left | Source | Actions |
|---|
Operation Status
| Status | Count | Percentage |
|---|
Problem Equipment
| Equipment ID | Status | Color | Last Reason/Fault | Total Downtime Hours |
|---|
High Risk Equipment
| Equipment ID | Failures | MTTF (Hours) | Availability % |
|---|
Supports breakdown Excel sheets plus PDF pre-use checklists (Loco / Caboose / Hopper), Non-routine Maintenance Orders, and Action Manager reports. Text PDFs are parsed directly; scanned PDFs use on-device OCR (may take longer).
Clean up duplicate status records
Database cleanup
0
Records with fault text
—
Top failure mode
0
Equipment with 2+ faults
0
Total downtime hours
| # | Equipment ID | Fault entries | Down hrs | Top mode | Last fault |
|---|
| Equipment ID | Mode | Times | Dates | Suggestion |
|---|
Test Classifier
Availability = uptime % over the selected analysis period (—). MTBF (h) = operating hours ÷ failures. MTTR (h) = downtime hours ÷ failures. Rows with fewer than 3 failures in the period are marked Low confidence. Click a row for the full equipment profile.
| Equipment ID | Shaft | Availability (%) | MTBF (hours) | MTTR (hours) | Failures | Confidence |
|---|
Reliability Recommendations
Captures status changes
1. What do you want to delete?
2. Which data?
Tip: untick “Equipment register” to clear only the history and keep the units. The date range applies to status / breakdown history only.
3. Preview & confirm
Invite / register user
Creates user profile
| User name | User ID | Role | Status | Allowed shafts | Actions |
|---|---|---|---|---|---|
| Loading… | |||||
Admin runbook (short)
- Invite — save role + ≥1 shaft in this UI
- Create Auth user — Firebase Console → Authentication → Add user (same email)
- Assign scope — shafts already set on invite; edit anytime
- Disable — set status disabled here; also disable Auth user in Console to revoke sessions
- Production checklist — see MASTER_FIX.md / ADMIN_RUNBOOK
99.5%
Target SLA (uptime)
< 4h
Critical incident response
Bi-weekly
R&D / release cycle
ZA
Primary data residency
Enterprise controls in this build
- Role-based access — admin, reliability, operations, executive, viewer with menu and action gating
- Audit trail — actor, action, timestamp, equipment context on critical writes
- Data residency indicator — South Africa primary; TLS in transit via Firebase
- Reliability layer — Event-based risk scores, gated MTBF/MTTR, data-quality metrics (RUL deferred until calibrated models exist)
- Export & governance — Executive PDF/Excel for board and reliability reviews
Roadmap toward Emerson / ABB / AVEVA class
IoT/sensor connectors, historian API, webhook alerts, SSO (SAML/OIDC)
Calibrated reliability models, multi-site hierarchy, CMMS/ERP bi-directional sync (Phase 3–4)
Digital twins, edge agents, global support org, formal SOC 2 / ISO program
Support channels
For production deployment: designate a platform owner, define RACI for reliability vs operations, and route critical alerts to on-call. This build is ready for site-level use and staged enterprise pilot; full 24/7 global support requires vendor or internal SRE capability beyond the application shell.
Version: RBE Monitor Enterprise 2.2 · Build focus: stability fixes — shaft-scoped writes, invite/RBAC clarity, import safety, dual-SDK removed