XRVE / FACILITY INTELLIGENCE
Command center
One facility context across evidence, assets, planning and decisions.
Browser-local · no upload
Explore a complete facility or create your own
See the entire Studio working together with a fictional packaging plant, or start with your own facility and approved source data. The example never uploads anything or changes a real maintenance system.
Start with the decision you need to make
Choose a familiar maintenance challenge. We will open the relevant existing Studio workflow using the fictional demonstration plant. No data or account needed.
The demo is illustrative. Its records and conclusions do not describe your facility.
Preloaded assets, work orders, PMs, investigations, improvement decisions, parts and schedule scenarios.
Use your own data in two steps: Create a free facility, then select one approved work-order CSV or multi-sheet XLSX workbook. Recognized asset and PM sheets prefill the same shared facility workspace. An asset register and PM export can be added later. Missing equipment, failure-code, or PM context will be shown as limitations, not invented.
Or begin with your own browser-local facility:
Only sanitized, organization-approved data. Your records are stored on this device—not transmitted to XRVE or synchronized across devices. You can export or erase them whenever you want.
One facility. Shared maintenance context.
Connect CMMS evidence to reliability improvement decisions. Your existing CMMS remains authoritative for work orders, PM execution, inventory, purchasing and actual labor. XRVE observations never change those records.
Not sure where to begin? Choose your maintenance problem
Open the relevant Studio module using your active facility. This guide does not generate findings or change source records.
Have one CMMS export? Start here.
Start with a single approved work-order CSV or XLSX. Map the required work-order ID and asset tag, add created dates where present, then review the mappings and analyze. Add asset hierarchy and PM exports later for stronger connections. Unavailable context stays unknown.
See the evidence. Understand the decision.
Two complete, interactive views: where recorded maintenance work concentrates, and where proposed weekly work meets labor and readiness constraints. The charts share this facility's data; missing evidence stays unknown.
Open improvement commitments
Evidence → Decision → CMMS handoff → Verification
01 / ValidateCMMS & equipment context
02 / FocusRecurring work and exposure
03 / RecommendReview and implement changes through the CMMS
04 / ReviewMeasure what improved
Asset Intelligence
Asset tags connect equipment, PMs and work history. Open the embedded P-F workbench to assess whether detection and planning intervals fit an explicitly supported deterioration window.
| Asset | Location / criticality | Known WOs | PM references | Attention |
|---|
Source-backed CMMS investigation
All work-order lenses share the same current facility and filters. Drill into individual reference rows during an import session; reopen an approved export to see them again.
Intervention outcome review
Compare a recorded XRVE improvement decision against approved CMMS work-order references. The two 90-day review windows exclude the actual implementation date. Declare the source for the implementation record and review whether both extracts are complete. Operating hours are optional; without source-referenced exposure, only coded work-order demand may be compared. This is never independent proof of the intervention's effect.
Load approved source work-order records to assess a prior intervention.
Save deliberately: only the equipment, decision, review dates, coded work-order counts, optional stated runtime and an unverified status are kept locally. Original work-order IDs, historian rows and source file references are never stored.
Cross-source evidence: PM execution, incidents, condition & production
Investigate recorded incident onsets and restoration, source-coded alarms, and operating intervals alongside CMMS work orders. Identifiers must agree exactly and timestamps require explicit timezone offsets. This is analysis of reviewed exports, not a live integration or independent source-system verification.
Required fields and evidence interpretation
Condition: asset_id,observed_at,metric,value,unit,state. State is alarm, normal or unknown. Alarm labels remain unverified source classifications.
Production: asset_id,start_at,end_at,runtime_hours. Each row describes an operating interval; overlapping intervals prevent aggregation.
Incident events: event_id,asset_id,failure_code,wo_id,occurred_at,restored_at. The incident must have a unique ID and an exact CMMS work-order reference. XRVE preserves the reported onset and restoration times, but these remain source assertions unless independently reviewed.
Operating scope / review manifest: asset_id,period,start_at,end_at,scheduled_hours,operating_regime,incident_log_complete,production_log_complete,review_reference. Label each scheduled segment baseline or followup; use reviewer-declared yes/no for whether the relevant incident and production extracts are complete. Provide a traceable approval reference. Source intervals must cover every segment without gaps, overlap, or boundary prorating to permit a screened rate.
PM execution history: pm_execution_id,asset_id,pm_id,due_at,completed_at,status,review_reference. Each execution ID is unique. Status is completed, missed, or deferred. Completed records require an offset-qualified completion timestamp; missed/deferred require a blank completion timestamp. A task is connected to this fault only when the PM master explicitly maps the exact PM ID to the exact failure mode. Missing execution records never prove a PM was missed.
Control asset: treated_asset_id,control_asset_id,failure_code,control_unchanged,comparability_basis,review_reference. Supply one different exact asset/code pair for the investigation, explicit yes/no declaration of whether the control avoided the investigated intervention, an engineering comparability rationale and a review reference. Both assets need complete reviewed incident/production/scope extracts and identical absolute-time schedule segments in both periods. A source-rate contrast is descriptive, never a verified causal intervention effect.
Intervention verification: intervention_id,asset_id,failure_code,change_type,implemented_at,implementation_wo_id,verification_method,verified_at,washout_hours,review_reference. Each investigated change must reference an exact completed CMMS work order and a timezone-qualified implementation timestamp. Method is inspection, functional_test, documentation_only, or not_verified. Only source-attested inspection/test methods include a qualified verified_at. The follow-up schedule must begin after both the change and reviewer-declared washout; intervening events remain visible.
Advanced functional verification and multi-period trend analysis are available in paid Facility Studio plans. Free retains the existing source-backed investigation, control-asset and intervention screening tools.
For example: 2026-10-01T14:30:00Z or 2026-10-01T08:30:00-06:00. Dates without timezone offsets are rejected. Where a matching incident log is available, XRVE compares alarms against the reported incident onset; otherwise work-order dates remain date-grain proxies. A chronological relationship is not confirmation of causation.
No supplemental evidence loaded.
Import approved facility exports
XRVE will suggest the export category from recognized column names. Confirm the proposed field mappings below before analysis. One work-order CSV or XLSX is enough to begin; other files are optional.
No quick-start export selected.
Start with one file: A multi-sheet workbook can stage work orders, assets and PM records together, filling all recognized field mappings for review. A work-order-only export can still produce a bounded review when work-order ID and asset tag are mapped. Date fields support temporal analysis; asset register and PM master exports are optional follow-up context. Claims about failure rates, PM effectiveness, or outcomes require sufficient source coverage and verification.
CSV and XLSX are parsed locally in supported browsers. Choose the worksheet, confirm mappings, and use an approved values-only export. Workbook formulas are not executed; unsupported Excel features require CSV. Only selected reference fields are used; employee data and free-text work descriptions are not imported. The workbook can fill source-backed CMMS, asset, and PM reference fields throughout the Studio; it cannot establish safety approvals, material availability, engineer-reviewed RCM, completed PM due schedules, labor capacity, runtime exposure or verified savings. Those require their own approved evidence.
Mapping selections require confirmation. Up to 25,000 work-order rows per approved export (16 MB source-file limit) are analyzed in page memory. Larger histories require reviewed date-scoped extracts; no silent sampling or source-row persistence. Bounded asset / PM references and derived summaries are saved only on this device. No cloud sync.
Evidence integrity & analysis limitations
Before interpreting failure frequency or reliability trends, review source identifiers, coding and measurement coverage. These counts describe the supplied extract—not the quality of the entire CMMS.
Repeat corrective-work patterns requiring review
Only distinct work-order IDs for the same equipment and nonblank failure code are counted; known reactive/emergency classifications, recognized status and valid source creation dates are required. Lookback: 180 days ending on the latest valid date in the extract. Three or more qualifying WO references trigger review, not a proven repeated failure or root cause.
| Group / equipment | Work orders | Known labor | Known downtime | Actual cost | Next step |
|---|
Source work-order references
Reference-level rows appear only while the current authorized browser import remains open.
| WO reference | Asset | Created (source) | Class | Status | Failure code | Decision |
|---|
PM and planning coverage
Review which recorded equipment has a PM reference and which assets deserve a work-scope review. A missing PM record in an export does not prove there is no site preventive maintenance.
| Equipment | PM records | WO history | Review decision |
|---|
Job readiness linked to an existing action
Use the same 12 planning checks as the XRVE Planner Job Readiness Analyzer. Record the review on the selected facility action; site safety, isolation, engineering and scheduling approvals remain separate.
Ready for schedule review does not mean an approved job, safe isolation, work authorization or guaranteed schedule commitment. This record stays in your local free facility workspace.
Reliability improvement decisions
Record why an improvement deserves attention, who will review it, and the CMMS asset, work-order or PM reference that supports it. These are decision records—not another work-order queue. Carry approved recommendations into your existing CMMS.
Review supporting evidence for an existing decision
Keep CMMS references and decision rationale current without making a duplicate work order or changing the operational source.
A CMMS source reference is a reviewer-entered identifier, not an automatically validated link. Exporting this review does not issue or modify CMMS work orders.
| Improvement decision / evidence | Asset | Review owner | Priority | Decision state | Planning review |
|---|
RCA & Bad Actor Intelligence
Review recurring equipment problems, distinguish observations from confirmed causes, and connect corrective actions to job planning and execution.
Schedule readiness and capacity risk
Compare proposed work, labor availability, job-readiness gaps and materials exposure before your site's CMMS schedule is released. This is a planning scenario, not an authoritative weekly schedule or work-dispatch system.
Turn evidence into a management review
Build a clear operating narrative with measured indicators, asset concentration and tracked actions. Source caveats and unknown values remain visible.