Automated evaluation passed. Tested through an authenticated local organization server and reconciled with the application’s reporting functions. This is not an independently witnessed hospital pilot or a production certification.
Follow the complete case
Hospital A · Central region · Generic imaging system · Main unit + accessory backup kit. All records are fictional. Open each stage to see what was checked.
01 Customer requestVerified
A signed-in Hospital A customer submits a Down-unit request. The server derives the account and coverage from its asset register. Replaying the same request creates no duplicate. Other accounts and internal costs remain inaccessible.
02 Automatic assignment and delegationVerified
The account engineer is at capacity because an office-work order counts toward workload. The available Central engineer receives the ticket. A customer cannot delegate; the team leader can record a reason and assignment history.
03 Complete compatible kitVerified
The configured requirement is one main unit and one accessory. Both are reserved together. Existing regression checks also cover unavailable items, partial kits and double booking.
04 Coverage and offerVerified
Active warranty: SAR 0 customer loan/delivery charge. Chargeable: 7 × (100 + 10) + 20 + 15 = SAR 805. The planned seven-day offer stays separate from the actual 48-hour loan and from recorded service revenue. It is not an invoice.
05 Acceptance and releaseVerified
The chargeable kit cannot be released before customer acceptance is recorded. Operations releases the complete kit using a document reference. The warranty branch uses explicit Operations approval/release.
06 Repair and service findingsVerified
Staff enter the response, delivery, repair and restoration milestones, the technical findings and all five activity categories. Seven hours of engineering effort × SAR 100 plus SAR 300 parts + SAR 80 travel expense + SAR 20 other costs = SAR 1,100.
07 Return and readinessVerified
The kit is returned with a reference. Both assets become Under service pending inspection/cleaning. Returning or cancelling a request no longer silently creates a replacement request on the same ticket. Further needs require a deliberately created ticket.
08 Independent approval and reportVerified
The engineer submits the completed record and a different reviewer approves it. A subsequent edit is rejected. The record survives encrypted storage reload. The application generates technical reports and reconciles its analytics against the fixed case calculations.
Time measures that mean different things
Response
1 h
Backup delivery
4 h
Repair turnaround
44 h
Original outage
48 h
Ticket resolution
50 h
All durations are calendar hours. Backup delivery is requested-to-receipt; repair is depot-received-to-returned; outage is original-equipment down-to-restored; resolution is reported-to-completed. Backup delivery does not stop the original unit’s outage clock.
Observation: 96 confirmed hours; downtime: 48 h; uptime: 48 h; calendar availability: 50%. On-site arrival: 3 h; delivery transit: 2 h. Clinical capacity restoration is not inferred from delivery alone.
Commercial reconciliation
| Measure | Chargeable | Warranty |
|---|---|---|
| Customer loan offer · SAR | 805 | 0 |
| Recorded service revenue · SAR | 2,000 | 0 |
| Direct service cost · SAR | 1,100 | 1,100 |
| Direct service contribution · SAR | 900 | -1,100 |
| Planned loan days | 7 | 7 |
| Actual loan hours | 48 | 48 |
| Original-unit downtime · h | 48 | 48 |
| Calendar availability · % | 50 | 50 |
Service revenue is explicitly entered synthetic financial data. The loan quote is not added to it automatically. Direct contribution excludes overhead and tax. Loan operational costs are not automatically included in the service-cost total. Early return does not automatically revise an agreed quote or generate an invoice.
What this check changed
- Returned/cancelled backup requests stay closed instead of being silently generated again on a later save.
- The local release workflow rechecks reserved equipment condition and acceptance, matching the server’s existing checks.
- Shared-server writes reject invalid service timelines, invalid timestamps, negative financial inputs and positive customer labor/parts charges marked covered.
No existing modules were removed or disabled. The 1,000-case trial remains separate from these two controlled acceptance cases.
Independent pilot — still to complete
These checkboxes are a printable handoff, not saved approvals. A service team must witness the real deployment on its intended computers and phones.
Remaining limits: mobile/browser visual QA and independent user acceptance were not available here. Email forwarding remains pending configuration; SAP is staging only; native Apple source remains uncompiled. No external pilot users were contacted.