Connect your workspace
Sign in token from your Nexus account (Business OS access is sufficient). Tokens stay in page memory for this tab only.
No authenticated workspace.
Loss intelligence, calculated from your own data.
Nexus detects loss signals across five operating domains by applying visible, deterministic formulas to the records you ingest. Every number carries its methodology; investigations require humans before any corrective execution; verified outcomes need evidence and a distinct approver.
What this page does not do: it never fabricates data, never estimates what you have not supplied, never auto-executes anything, never records a financial outcome without evidence and a named approver distinct from the actor, and never treats a calculated exposure as a realized loss. Estimated exposure is a calculation over records you supplied — not a bookkeeping claim.
Overview
Confirmed exposure
—by currency
Human-confirmed detections only.
Estimated exposure
—by currency
Calculated candidate exposure, not realized loss.
Recovered
—by currency
Verified outcomes with evidence and an approving human.
Prevented
—by currency
Recorded prevented value with evidence.
Investigations
—open states
Open, under review, executing or verification pending.
Predictions
—open
Forward-looking signals with explicit evidence limitations.
Detections
Predictions
Investigations
Lifecycle: open → assign reviewer → decide → link corrective task (created via the standard Nexus pipeline with your task details) → verify → record verified outcome with evidence and a distinct approver.
Equipment pilot
Registered assets, their live health, and open operational issues derived from your maintenance records. Issues recommend actions with evidence, confidence and estimated exposure — creating a maintenance task goes through the standard approved execution pipeline. Estimated exposure is never a confirmed loss.
Registered assets
—total
—
Overdue schedules
—assets
Maintenance intervals passed without a later maintenance record.
Open issues
—equipment
—
Downtime (30 days)
—hours
Sum of recorded downtime on maintenance events.
Maintenance spend (30 days)
—by currency
Recorded parts costs on maintenance events.
Financial position
—
Estimated exposure · confirmed loss · verified savings (evidence-backed).
Register an asset
Assets
Condition, failures, downtime, spend and schedule state, computed from ingested records.
Open equipment issues
Every finding carries its supporting records, severity, confidence, estimated exposure (never presented as a confirmed loss) and a recommended next action. Issues without an investigation are unresolved.
Ingest a record
Structured data from your systems (ERP, POS, maintenance, route ops, finance, contracts). The engine keeps the byte-identical replay idempotent and rejects divergent payloads for the same record reference.
Recent records
What detection actually consumes. Nothing is written back to your source systems.