Analytics & Reporting

Choose a report on the Analytics page, then set its date range and filters. The report scopes are Overview, Materials, Material waste, and Utilization. All require the analytics.view permission.

Export downloads the displayed report as CSV or JSON, including its scope, date range, and filter IDs. Overview exports contain a section column for each breakdown; utilization exports contain fleet totals and printer rows. Exports use the loaded results. Use Refresh to fetch changes made since loading.

Overview and materials#

Overview shows jobs over time, breakdowns by user and printer, peak submission hours, and estimated material cost over time. The project/cost-center breakdown appears when Department and cost center job-submission fields are enabled in General settings.

Materials shows planned grams by material variant, type, and color. These amounts are recorded when printing starts; they aren’t measurements of actual consumption. Estimated costs use those amounts and current material prices.

Both reports select jobs by their submission date. Filter by user, printer, material type, or status. User and printer selectors appear only when you have permission to view those lists. Changing scopes preserves your selections; only filters relevant to the current scope apply.

Material waste#

Select Material waste, choose your semester or other date window, and optionally filter by material type, printer, or user. The report estimates waste for each material using:

Estimated waste in grams = planned material grams × recorded progress ÷ 100

For example, a 200 g PLA print recorded at 10% contributes an estimated 20 g. Only jobs with a recorded print start that were subsequently marked failed or cancelled qualify. Jobs that failed during processing or were cancelled before starting are excluded. This scope always includes both failure and cancellation, so it has no status filter.

The window applies to the latest matching failure or cancellation event, not the upload date. Each retained job contributes once, using its last recorded progress and material amounts. The table and export break down failed and cancelled jobs by material type; a multi-material job can appear under more than one type.

This is an estimate, not a measurement. It assumes material use is proportional to progress, including for multi-material jobs. Recorded 0% contributes 0 g; missing progress telemetry can therefore undercount waste. Jobs without usable material amounts are reported separately. Supports and purge from successful prints aren’t included.

Reports use retained job history. A reprint that reuses a job can overwrite the previous run’s progress and material amounts, so earlier runs cannot be reconstructed. Deleted jobs are absent. The report excludes cancellations or dispatch failures after a recorded requeue when no new start was recorded.

Machine utilization & OEE#

The Utilization chart compares utilization and OEE by printer. Fleet totals and quality are included in the export. Only date and printer filters apply.

• Utilization: the share of a printer’s available time that it spent actively printing:

  Utilization % = printing time ÷ available time

  Printing time is measured from each job’s print started event to the point the print finished (completed, failed, or cancelled). Available time is the wall-clock time the printer existed within the selected window. A powered-on but idle printer shows 0% utilization rather than dropping out of the report.

• Quality: the success rate of finished prints:

  Quality % = completed ÷ (completed + failed)

• OEE (Overall Equipment Effectiveness): a single headline score combining the two:

  OEE % = Utilization × Quality

  The classic OEE formula also includes a Performance factor (speed loss versus an ideal cycle time). Pluraprint does not store a per-job ideal cycle-time standard, so Performance is treated as 100% and OEE reflects utilization and quality only. This is stated here so the number is never mistaken for a speed-loss-adjusted figure.

Utilization and OEE are reconstructed from each job’s recorded print lifecycle events, so they populate from your existing print history immediately: no extra configuration is required.