From service events
to a fuller business view.

How this is calculated: Work-order counts include all 1,000 sample cases. Equipment availability uses the 36 assets with complete observation records.

Suggested next steps: Review overdue work, late deliveries and recurring faults when planning service capacity.

What to keep in mind: The figures illustrate the platform using fictional data; they do not represent actual customer results.

Recorded revenueSAR 1,882,330.00

Complete direct costSAR 1,375,141.25

Margin on complete records26.9%

Complete / undated / incomplete records840 / 120 / 40

Enlarge chart ↗

How this is calculated: The financial record date determines the reporting period. Entered itemized charges replace the base charge; installation and warranty fees are added. Direct costs include recorded labor, parts, travel and other service expenses.

Suggested next steps: Review jobs with negative contribution and check coverage, travel and parts usage before adjusting prices.

What to keep in mind: Contribution means recorded revenue less direct cost. It excludes overhead, tax, depreciation and bad debt, and should not be read as net profit, invoiced revenue or cash received.

Regions3

Largest workloadCentral

Enlarge chart ↗

How this is calculated: Financial comparisons use dated records with complete cost and charge information. Equipment availability is calculated separately from each asset observation period.

Suggested next steps: Review travel, local stock and overdue work together when allocating regional resources.

What to keep in mind: Sample regional volumes illustrate a case mix rather than market demand. Staffing capacity and live travel-distance data are not included.

Hospitals10

Orders per hospital100

Enlarge chart ↗

How this is calculated: Work orders, costs and charges are grouped by customer. Annual contract values are reported separately and are not added to job revenue.

Suggested next steps: Identify customers who may benefit from a service-plan, coverage or recurring-fault review.

What to keep in mind: This view does not include customer satisfaction, accepted service outcomes or a verified assessment of contract profitability.

Recorded activity hours4,663.0

Engineers in sample5

Enlarge chart ↗

How this is calculated: Recorded hours are added across the five activity categories. Missing hours are excluded; open sample cases do not contain actual labor hours.

Suggested next steps: Check workload distribution, travel demands and supporting activities before reallocating work.

What to keep in mind: Recorded hours alone do not measure utilization or productivity. Those measures also require available hours, leave, skills and job complexity.

Observation period (asset-hours)245,088.0

Downtime / available time (hours)55,631.0 / 189,457.0

Assets included / excluded36 / 4

Average interval between orders (hours)269.8

Enlarge chart ↗

How this is calculated: Availability equals observed calendar hours minus downtime, divided by observed calendar hours. Overlapping downtime is counted once per asset. The time-between-orders measure uses 960 consecutive intervals across all work-order types.

Suggested next steps: Review high-downtime equipment and confirm that service logs are complete before discussing replacement.

What to keep in mind: Availability assumes equipment is available outside recorded downtime. It is not measured by live monitoring or operating shifts. Time between work orders is not mean time between failures (MTBF). Four incomplete asset logs are excluded from fleet availability.

Average response h2.3

Response records960 / 1,000

Requests meeting SLA target92.0%

Average arrival h4.4

Enlarge chart ↗

How this is calculated: Service-level agreement (SLA) compliance is 920 requests meeting target out of 1,000 eligible requests. The 40 unanswered overdue requests count as missed targets but are excluded from average response time. Arrival averages exclude missing arrival records and remote cases.

Suggested next steps: Review delayed urgent requests and unanswered requests separately, rather than relying only on the average.

What to keep in mind: First response, arrival, repair and completion are different measures. The sample targets are assumptions and do not establish clinical performance.

Open orders120

Past expected closure120

Completed late / completed264 / 880

Mean request-to-close h60.7

Enlarge chart ↗

How this is calculated: Open-work age is measured from the reported time to the report snapshot. A completed job is late when completion occurs after its expected completion time. Elapsed calendar time is separate from labor hours.

Suggested next steps: Assign an owner to each parts, site-readiness or customer-access delay and update expected completion dates with supporting information.

What to keep in mind: Delay reasons are sample assumptions. This report does not pause elapsed time or automatically exclude customer-related delays.

Returned repairs40

Mean turnaround h450.0

Over 14-day threshold28

Enlarge chart ↗

How this is calculated: Turnaround is calculated from receipt to return for 40 completed repairs. The 14-day target is a configurable demonstration assumption, not a regulatory requirement.

Suggested next steps: Review parts availability and repair capacity when investigating repairs beyond target.

What to keep in mind: Total turnaround does not show how much time was spent in the technician queue, on the bench or waiting for suppliers. Those stages need separate timestamps.

Delivered orders80

Mean lead time h114.0

Mean transit h72.0

On-time delivery25.0%

Enlarge chart ↗

How this is calculated: Lead time runs from request to delivery. Transit time runs from dispatch to delivery. On-time performance compares delivery with the recorded promised date.

Suggested next steps: Review the 60 late sample deliveries and distinguish dispatch delays from transit delays.

What to keep in mind: The report supports one delivery record per order. Split shipments, live carrier tracking, proof-of-delivery attachments and invoice-readiness checks are not included.

How this is calculated: Maintenance visits come from work orders; next-due dates come from equipment records. The sample cases include visits completed on time and after the planned date.

Suggested next steps: Confirm each asset’s maintenance plan and update its next-due date after the visit has been accepted.

What to keep in mind: A next-due register alone cannot establish fleet maintenance compliance. A complete planned schedule and valid completion or deferral records are also required.

How this is calculated: The demonstration includes 40 completed installations and 40 cases awaiting site readiness. Installation fees are additional recorded revenue. Activity hours are grouped by work category.

Suggested next steps: Confirm site readiness before dispatch, retain acceptance evidence and review the effort spent on sales support.

What to keep in mind: Signed acceptance, site-checklist approvals, milestone billing and project accounting are not included in this report.

Standard warranty cases40

Extended warranty variants120

Service-contract cases120

Enlarge chart ↗

How this is calculated: Costs are grouped by the recorded coverage type, including standard warranty, extended warranty, service contracts and chargeable work. Covered labor and parts still create internal costs.

Suggested next steps: Check the applicable agreement before billing and review covered costs by service type.

What to keep in mind: Coverage is entered by the user and does not confirm manufacturer or insurer approval. Fee revenue is assumed in the demo; premium allocation, reserves and contract accruals are not calculated.

How this is calculated: Stored contract status and expiry dates are checked separately. Annual contract values describe the register; they are not recognized revenue or job contribution.

Suggested next steps: Resolve contracts marked active after expiry, confirm account owners and maintain a renewal calendar.

What to keep in mind: Asset-level entitlement links, a renewal sales pipeline, signed agreements, tax treatment and premium allocation are not included.

Part references20

Stock locations3

Known stock valueSAR 241,444.06

Active reservations10

Enlarge chart ↗

How this is calculated: On hand equals opening stock plus posted net movements. Available stock equals on hand less active reservations. Incoming costs update the moving-average value at each location. All 40 stock positions have opening valuations.

Suggested next steps: Check expired items and stock at or below the reorder point before planning replenishment. The suggested top-up is the reorder point plus one unit, less available stock.

What to keep in mind: Reorder suggestions are not demand forecasts or purchase orders. Expiry is recorded at item-reference level; batch and serial tracking, quarantine and earliest-expiry picking are not covered by this report.

Posted movements110

Reservations40

Net issues to open jobsSAR 4,794.68

Enlarge chart ↗

How this is calculated: The sample ledger includes 110 movements. Of 40 reservations, 10 remain active, 20 are fulfilled and 10 are released. Twenty open jobs use stock-ledger parts costs and have no financial date. Returns use the original issue cost.

Suggested next steps: Confirm stock-ledger costing before replacing manually entered parts costs. Reconcile returns and document adjustment reasons.

What to keep in mind: Stock movements do not automatically change customer charges. Posted entries require correcting movements rather than edits. Browser-only actor labels do not verify identity; authenticated audit records are provided by the self-hosted server.

How this is calculated: Estimated costs and charges are entered assumptions. Price-list entries have validity dates, but the sample estimates are not automatically linked to individual price-list entries.

Suggested next steps: Review cost overruns by job and retain the pricing basis used for each commercial quote.

What to keep in mind: This report does not provide tax calculations, discount approvals, currency conversion, purchasing or a formal quotation approval process.

How this is calculated: Repeat alerts identify assets with at least two corrective orders in the 30 days before the report snapshot. First-visit resolution uses recorded Yes or No outcomes for completed jobs. Technical narratives and possible causes are fictional.

Suggested next steps: Review the original fault, technical findings and verification results before assigning an investigation or corrective action.

What to keep in mind: A repeat visit does not by itself prove repair failure. Report metadata does not confirm an engineer signature, customer acceptance, safety release or an approved root-cause investigation.

Cases / scenario families1,000 / 25

Incomplete financial records40

Unanswered requests40

Excluded observation logs4 assets

Enlarge chart ↗

How this is calculated: Each measure uses the records available for that calculation. Missing financial details, unanswered requests and incomplete observation logs are shown separately. See Technical readiness for testing and deployment details.

Suggested next steps: Replace sample assumptions with verified records, complete missing information and agree acceptance criteria for your organization.

What to keep in mind: This report uses fictional data to demonstrate the platform’s features and calculations. Validate the configured system with your organization before operational use.