PALDESK CONCEPT PAPER · 2025
Workshop Stay
A Unified Service Event for the PALDESK Ecosystem
A Unified Service Event for the PALDESK Ecosystem
Workshop touchpoints in PALDESK are handled individually — PDI, Inspection, Claim, Smart Record — with no unifying container. Data stays siloed, follow-ups are manual, and the service partner's visit goes largely unrecorded as a coherent event.
A Workshop Stay is a new first-class entity in PALDESK. It acts as the container for everything that happens during a service visit — capturing what, when, and why, while automatically linking relevant history and triggering follow-up workflows.
Service partners report once. PALDESK routes automatically to Claim Desk, Smart Inspection, Oil Monitoring, CRM and more. Full traceability of the equipment's service life becomes possible for the first time.
"Everything starts with a workshop visit."
EQ-Screen shows service history items individually without a connecting event concept. Service partners interact with PDI forms, Smart Inspection checklists, and Claim forms independently of each other. There is no way to say "these three things all happened during the same workshop visit on March 12th" — every interaction stands in isolation, stripped of its operational context.
Workshop Stay is not a new tool — it is a new organizing principle. It becomes the event that gives meaning and context to everything else that PALDESK already does.
Scheduled workshop visits that are known in advance. These are entered into PALDESK before the equipment arrives, allowing service items to be pre-assigned.
Examples: Contract Service, Annual Legal Inspection (UVV), PDI, Recall Actions, Planned Modifications
Reactive visits triggered by a breakdown, error code, or customer complaint. Created when the equipment arrives unexpectedly at the workshop.
Examples: Hydraulic repair, sensor replacement, error code investigation, customer complaint
Start and end date of the workshop visit, total duration in days
Hours on the equipment at time of visit — critical for maintenance planning and warranty evaluation
Planned vs. Unplanned, category (Repair, Inspection, PDI, Recall, etc.)
Free-text entry in the service partner's own language, with automatic translation to other supported languages
AI-powered translation allows partners to write in their native language; Palfinger teams read in theirs
System suggests service history entries (Paltronic uploads, PALCODE sessions, Smart Records) from the same timeframe for linking
One-click initiation of Claim, Smart Inspection, CRM inquiry, or Oil Check directly from the Workshop Stay
Workshop identity, technician name, and location linked to the PALDESK partner record
Draft, Scheduled, In Progress, Completed, Requires Action — with notification triggers on status change
Workshop Stay is a first-class data object in PALDESK, linked to Equipment (EQ) and Service Partner. It exists in the core data model alongside existing entities.
Algorithm suggests service history items within ±3 days of the stay date, ranked by a confidence score based on equipment ID, location, and event type.
Integration with translation API (e.g., DeepL); original language is preserved alongside the translation. Translations are cached to avoid redundant API calls.
Workshop Stay state changes trigger events consumed by Claim Desk, Smart Processes, and other modules via the existing PALDESK event bus — no direct coupling required.
