Service and Maintenance Enquiry

Service and Maintenance Enquiry

OWNED DECISION: Collect symptoms, asset identity, operating context and service scope to route a technically useful enquiry without pretending to diagnose a fault remotely. MANDATORY ASSET: Working Service Enquiry Form and Fault Brief.

01 — Direct answer

A useful compressor service enquiry identifies the machine and site, distinguishes a safety-critical condition from a routine service need, records observed symptoms and operating context, and requests the correct technical review. Submission is a request for assessment, not an automatic diagnosis, dispatch commitment, repair authorisation or service-level guarantee.

02 — User journeys

Support breakdown assessment, preventive maintenance, AMC enquiry, inspection, overhaul assessment, spare-parts support, commissioning support, air-quality fault, electrical/control issue and unresolved/other. A single customer may select multiple categories; keep a primary request plus secondary observations. Offer a concise first screen and optional engineering details.

03 — Scope boundary

Do not copy these technical pages or imply their conclusions from a customer-submitted form.

04 — Safety-first entry

At the start ask whether there is injury, fire, smoke, electrical arcing, pressure-vessel concern, uncontrolled discharge, suspected hazardous contamination or other immediate danger. Display a site-specific safety warning: isolate and follow approved emergency procedures; contact local emergency services where necessary. The form must not instruct unqualified users to open pressurised systems, defeat protection or work on live electrical equipment.

05 — Asset identity

Collect manufacturer, model, serial number (optional where unavailable), asset tag, compressor technology, motor or engine drive, nameplate capacity and pressure if known, commissioning year and service location. Photograph of nameplate may substitute for typed details. A guessed model must be marked unverified.

06 — Symptom capture

Use structured choices: fails to start; trips after start; low pressure; slow pressure build; pressure fluctuation; high discharge temperature; oil carryover; water contamination; abnormal vibration/noise; air leak; high differential pressure; high power use; control fault; dryer/filtration issue; planned maintenance; unknown. Provide free-text description and “other”.

07 — Onset and progression

Record first observed date/time, intermittent versus continuous behaviour, recent maintenance or modifications, whether symptoms appear at startup, unload, load, peak demand or shutdown, and whether alarms recur. Preserve customer wording verbatim as well as structured tags; do not rewrite a reported symptom into an asserted root cause.

08 — Operating context

Ask for normal and observed discharge pressure with units and reading location, operating hours, duty cycle, load/unload/VSD state, ambient temperature if available, number of connected compressors, major air users, changes in demand and any downstream restriction. “Pressure low” is incomplete without where and when it was observed.

09 — Fault-code integrity

Capture displayed alarm text/code exactly, controller make/model, timestamp and a screenshot when available. Do not interpret an unfamiliar code using a different OEM manual. Route to qualified reviewer with applicable manual revision and machine identity.

10 — Safety of uploaded media

Allow nameplate images, alarm screenshots, equipment photos and operating logs. Do not request unsafe photographs taken inside live cabinets, behind guards or near moving machinery. Strip unnecessary metadata where policy requires and prevent attachments from becoming public URLs.

11 — Service history

Collect date and nature of last maintenance, service hours, lubricant and filter changes if known, recent parts replacement, recurring failures, outstanding recommendations, previous work order references and current maintenance contract status. Avoid assuming a manufacturer interval from incomplete data.

12 — Air quality and treatment

If moisture, oil or particles are reported, ask for sampling location, downstream impact, dryer status, drain operation, filter differential pressure, target air quality and available test results. Distinguish visible contamination from laboratory-verified quality classification.

13 — Mechanical and thermal symptoms

For noise, vibration and temperature, request trend, operating state, measurement location and instrument if available. Never publish universal safe limits or infer bearing failure from sound alone. Escalate potential mechanical hazards for qualified inspection.

14 — Electrical and controls

Collect supply type, observed power interruptions, starter/VSD/controller information, alarm state and whether a qualified electrician has inspected the system. Do not solicit exposed conductor photographs or instruct users to reset trips repeatedly.

15 — Portable and diesel equipment

Where relevant collect engine model, run hours, fuel type, cooling/airflow observations, engine alarm text, site altitude and ambient conditions. Treat engine emissions, exhaust and fuel safety as site-specific review items, not a generic remote troubleshooting checklist.

16 — Maintenance request versus fault request

For routine PM, capture requested service type, hours-to-next-service, consumables needed, site access and preferred date. For breakdowns, capture impact, symptoms and immediate safety state. For overhaul, collect history, failure evidence and whether a condition assessment is requested before scope approval.

17 — Priority classification

Customer may state “production stopped”, “critical process affected”, “degraded but running” or “planned work”. Internal triage priority should be assigned by an authorised coordinator, not automatically represented as guaranteed dispatch or a promised response time.

18 — Continuity options

If production is at risk, ask about parallel compressors, available storage, essential air users and whether a separate temporary-air enquiry is needed.

19 — Site logistics

Capture site area/city, access hours, contact role, entry permits, shutdown windows, lifting/access restrictions and equipment location. Collect a precise address only where needed to process the request, with privacy notice and controlled access.

20 — Initial contact

Require one reliable contact channel and a contact name or role. Validate email/telephone format without requiring both if one is sufficient. Record preferred contact time as a preference, not an appointment.

21 — Progressive disclosure

First screen: request type, machine identification or “unknown”, symptom, urgency, location and contact. Second: operating data, service history and attachments. Third: review, privacy notice and submission. Users should be able to save progress if the chosen platform securely supports it.

22 — Input validation

Validate numerical units and plausible syntax without rejecting legitimate unusual engineering duty. Distinguish 7 bar(g) from 7 bar absolute, kW from hp, operating hours from calendar age, and pressure reading from setpoint. Preserve original units alongside converted values.

23 — Optional unknown values

Permit “unknown/not measured” for serial number, capacity, pressure, hours, model, alarm code and service history. Mark these as clarification needs rather than inventing defaults or blocking a genuine breakdown enquiry.

24 — Attachment controls

Whitelist approved file types, apply server-side MIME verification, malware scanning, file-size limits, randomised storage identifiers, access control and expiry/retention rules. Display accepted types and size limits from deployed configuration, not invented limits.

25 — Privacy and consent

State why contact and machine data are collected, who receives the enquiry, retention basis, privacy contact and any optional marketing choice. Service request consent must not be bundled with marketing consent. Record consent notice version and timestamp where appropriate.

26 — Security

Protect against automated spam, cross-site request forgery, injection, unrestricted uploads, duplicate submissions and unauthorised access to attachments. Do not include confidential fault logs in analytics, URLs or publicly cacheable pages.

27 — Submission workflow

Client-side validation improves usability; server-side validation is authoritative. Persist an enquiry record with unique reference and attachment manifest, then queue routing. The acknowledgement should be generated from confirmed persistence, not merely a button click.

28 — Routing logic

Routine PM → service coordination; suspected mechanical failure → qualified compressor technical reviewer; electrical/control issue → authorised electrical/control reviewer; air quality → treatment specialist; parts → compatibility verification; overhaul → condition-assessment owner; immediate safety concern → safety message and designated internal escalation. Confirm actual staff routing during implementation.

29 — Acknowledgement

Display a neutral message: “Your service enquiry has been received for review. Reference: [generated ID]. A technical coordinator will assess the information. Submission does not confirm diagnosis, availability, visit time or quotation.” Send email/SMS only through approved channels and avoid sensitive fault details in notifications.

30 — Delivery failure

If persistence fails, show a clear accessible error and safe retry. If routing fails after persistence, keep the record, flag a queue exception and avoid duplicate records. If attachment upload fails, allow removal/retry without losing entered fields.

31 — Customer correction

Provide a controlled way to append new symptoms, corrected model details or further attachments to an existing enquiry, with an audit trail. Do not overwrite original reported observations; label revisions and time of receipt.

32 — Internal review and disposition

Technical owner marks accepted for assessment, clarification requested, outside scope, referred, closed by customer or duplicate. Track reason, evidence, next action and responsible person. “Received” is not the same as “accepted for service”.

33 — Technical fault brief generation

Generate a structured internal fault brief summarising exact customer statements, machine identity, current status, observations, known unknowns, media, safety flags and proposed review route. Avoid auto-generated root-cause certainty or unauthorised repair instructions.

34 — Customer-visible summary

Before submission show all entered data, units, attachments and privacy notice. Offer an editable review step and a copy of the submitted brief with confidential data protected. A PDF download may be added only after safe implementation and user consent.

35 — Service enquiry analytics

Measure form starts, completion, validation errors, attachment failures, route failures and acknowledgement delivery using privacy-preserving event names. Do not send serial numbers, telephone numbers, alarm screenshots or free-text fault descriptions to third-party analytics.

36 — Accessibility

Provide programmatic labels, keyboard-operable controls, clear required/optional status, logical focus, error summaries linked to fields, accessible progress indicators and screen-reader-announced acknowledgement. Never rely on colour alone for urgency or errors.

37 — Mobile performance

Design for field technicians using narrow screens and intermittent connectivity. Avoid wide fixed tables, allow camera capture only with user control, preserve draft fields after validation errors, and ensure attachment progress/error messages remain readable.

38 — Content governance

Name owners for field schema, safety text, privacy policy, routing rules, form plugins, email templates, security updates and technical FAQ answers. Maintain version history and staging test evidence before any field/routing change.

39 — Engineering claim boundary

The enquiry is not a remote diagnostic instrument. It does not establish compressor defect, repair price, availability, warranty eligibility, response time or safe operation. Such conclusions require relevant inspection, OEM information and agreement.

40 — Standards-aware implementation

Assess accessibility against the applicable WCAG version, security against current deployment requirements, privacy against the applicable jurisdiction, and technical decisions against relevant OEM and site procedures. Do not imply compliance certification solely because a checklist exists.

41 — Mandatory asset: Working Service Enquiry Form and Fault Brief

Intake and consent

• Machine identity
• Symptoms
• Operating evidence
• Attachments
• Routing and outcome

42 — Example fault brief A: pressure falls under production demand

ILLUSTRATIVE ONLY. Rotary-screw compressor, reported 7 bar(g) setpoint, header observed at 5.5 bar(g) during peak demand; compressor outlet reading not supplied. Other parallel equipment status unknown. Recent filter change reported. Intake classification: LOW PRESSURE / PROCESS IMPACT. Review asks for simultaneous compressor-outlet and critical-use pressure, loaded state, flow/demand and filter differential pressure. No conclusion about undersizing or repair scope is justified.

43 — Example fault brief B: temperature trip

ILLUSTRATIVE ONLY. Operator reports repeated high-temperature shutdown after 45 minutes, ambient condition unmeasured, cooling path unknown. Classify as technical review with safety warning against repeated resetting. Request exact fault code, temperature reading location, cooler maintenance history and site ventilation context. Do not diagnose failed thermostat, low oil or cooler fouling from the form alone.

44 — Example fault brief C: scheduled maintenance

ILLUSTRATIVE ONLY. Portable compressor at 1,850 displayed run hours requests scheduled maintenance. OEM schedule, engine hours source and previous service record are not attached. Route to service planner for identity verification, applicable service interval and approved consumables. Do not automatically assert service is due at a universal hour threshold.

45 — Example fault brief D: moisture downstream

ILLUSTRATIVE ONLY. User reports liquid water at a CNC machine following weekend shutdown. Dryer type, pressure dew point, drains, sampling location and startup sequence unknown. Route to air-treatment review and capture site-specific process risk; do not promise an air purity class or prescribe a replacement dryer without measurements.

46 — Example fault brief E: motor/VSD alarm

ILLUSTRATIVE ONLY. Controller displays a drive fault after a utility outage. User uploads a photo of the alarm display, not electrical cabinet internals. Route to qualified electrical/control reviewer, request exact OEM model and alarm code, and advise against bypassing protection. No remote reset instructions are issued.

47 — End-to-end functional acceptance matrix