Temporary Air Hire Enquiry

Temporary Air Hire Enquiry

OWNED DECISION: Collect duty, quality, utilities and site constraints sufficient for useful rental-duty and continuity triage and a qualified quotation discussion. MANDATORY ASSET: Working Rental Enquiry Form and Attachment Guidance. This document specifies the form and acceptance tests; it is not a deployed or tested live form.

1. Direct answer

A useful compressor temporary air hire enquiry specifies what the air must do, how much is required, where and at what pressure it is required, what air quality is necessary, how demand changes over time, and which electrical, fuel, physical and commercial constraints apply. Missing or estimated inputs must remain explicitly provisional; an enquiry form is not a substitute for site measurement or detailed engineering selection.

2. Scope and ownership

Detailed compressor selection remains with the appropriate technology page and qualified engineering reviewer. Do not duplicate those pages.

3. Visitor decision journey

Start with “New purchase / Replacement / Capacity expansion / Rental / Unsure”. Show a short essential-information step, then optional technical detail. Offer a summary for review before submission. After verified persistence, display a reference identifier and factual acknowledgement without promising quotation timing or equipment availability.

4. Mandatory minimum fields

Require contact name or organisation representative, a usable reply channel, enquiry purpose, broad application, installation location or region, estimated operating pressure with unit, estimated demand or “unknown”, intended duty, and privacy acknowledgement. Where a user genuinely cannot specify a technical value, allow “not yet known” and flag technical review rather than forcing fabricated precision.

5. Pressure entry

Capture pressure at the critical end use and distinguish it from compressor discharge or header pressure. Accept bar(g), kPa(g) or psi(g) with visible conversion and unit preservation. Flag implausible values for review; never silently change gauge to absolute pressure. Record minimum acceptable pressure and any peak requirement separately.

6. Flow entry

Capture demand in a named reference basis, such as m³/min with stated reference conditions or an explicitly declared alternative. Ask whether values are measured, OEM-specified, calculated or estimated. Capture average, maximum, simultaneous tools, duty cycle and demand variation; do not equate receiver volume with sustained airflow.

7. Operating profile

Collect hours/day, days/week, shifts, variable versus steady demand, idle periods, start/stop pattern, peak duration and anticipated expansion. Distinguish planned operating hours from guaranteed availability and separate compressor utilisation from production hours.

8. Air-quality requirement

Ask what contaminants matter: water, particles, oil, process gases or special hygienic requirements. Allow a documented target specification or “to be assessed”. Capture sampling/use point, temperature and downstream treatment constraints. Do not infer that “oil-free compressor” means a verified air-quality class at the point of use.

9. Power and utilities

Capture voltage, phase, frequency, available electrical capacity, starting restrictions, site distribution constraints, diesel preference, fuel access, cooling water where applicable and ventilation. Treat stated values as customer-provided until site verification; do not invent a permitted motor-start current or generator compatibility.

10. Site constraints

Capture indoor/outdoor placement, altitude, ambient conditions, ventilation, acoustic limits if specified, access width/height, lifting restrictions, distance to point of use, piping interfaces, condensate handling, safety controls and available space. Allow sketches/photos with clear privacy and upload controls.

11. Technology branch logic

For rotary screw: load profile, controls and air-treatment interface. For reciprocating: duty and cycling. For portable diesel: mobility, fuel, site access and hose. For high pressure: working pressure, vessel/interface limits and specialist review. For borewell/DTH: hole diameter, hammer/bit size, formation, depth, flushing and altitude; do not promise penetration rate or groundwater yield.

12. Rental branch logic

Capture start window, estimated duration, tie-in point, temporary hose route, site power/fuel, treatment, redundancy, operator responsibilities and demobilisation. Availability and emergency response are subject to confirmation; the form must never display an unconditional commitment.

13. Replacement branch logic

Capture existing make/model, nameplate details, run hours if known, observed performance, reason for replacement, failure history, downstream treatment, electrical installation and intended improvement. Existing motor kW alone is not a valid airflow-sizing method.

14. Procurement and decision constraints

Capture target commissioning window, site survey access, quotation purpose, purchase/rental preference and optional budget range. Do not make budget mandatory for technical triage. Separate customer-requested schedule from any company-approved delivery commitment.

15. Confidence and source tags

For each important input, allow MEASURED, OEM DOCUMENT, CUSTOMER ESTIMATE or UNKNOWN. Record who supplied it, date, units and whether evidence is attached. A reviewer can then request missing tests before making a selection recommendation.

16. Progressive disclosure

Use a small essential first screen, then expandable technical categories. Preserve values when moving between steps. Show a clear completion indicator, field-level errors and a final review screen. Never hide a critical consent statement behind an optional accordion.

17. Units and conversions

Display the original entered unit and normalized internal value with conversion metadata. Avoid premature rounding. Show both values in the technical brief where conversion may affect selection. Validate numeric ranges server-side and test decimal separators and copied text.

18. Unknowns and assumptions

Unknown is an acceptable engineering state. Do not default pressure, flow, quality class or operating hours to apparently authoritative values. Mark incomplete engineering briefs “Needs technical clarification”, route them to a reviewer and request only missing information.

19. Validation policy

Validate email/telephone syntax only as appropriate to selected contact method; do not reject valid international formats arbitrarily. Reject executable attachments, disallowed MIME types and excessive size; scan uploads and isolate them from public serving. Use CSRF protection, rate limiting and server-side validation.

20. Accessible form semantics

Every control needs a visible label, associated programmatic name, units in the label, help text, accessible errors, keyboard operation and predictable focus. Error summary links to invalid fields; submission status uses an accessible live region. Test zoom, contrast and screen reader.

21. Mobile usability

Use one-column form sections, suitable input keyboards, touch-sized controls, concise examples and save-state behaviour appropriate to the privacy policy. Prevent horizontal table overflow and avoid requiring users to upload a document from a desktop computer.

22. Attachments

Allow optional equipment nameplates, piping sketches, demand logs, site photographs and OEM requirement sheets subject to approved formats and limits. Show file name, type, size, upload status and removal option. Redact or restrict personally identifiable, customer-confidential and safety-sensitive information.

23. Privacy and consent

State purpose of collection, responsible business, recipients, handling of attachments, retention policy and contact for data requests. Obtain any legally required consent without prechecked boxes. Avoid collecting passwords, payment card data or unnecessary identity documents. Jurisdiction-specific policy requires review before release.

24. Submission architecture

Submit over HTTPS to a protected endpoint. Create a server-side immutable enquiry ID and persist a sanitized record before acknowledging success. Log delivery to internal routing separately; do not tell a user the enquiry was received if persistence failed. Avoid sensitive details in analytics or email subject lines.

25. Routing and ownership

Route by enquiry type, duty complexity and region to an approved owner or shared queue. Maintain a fallback queue and exception monitoring. If routing fails after successful persistence, retain the record and show a truthful acknowledgement; alert an administrator without exposing internal addresses.

26. Acknowledgement

Provide a reference number, submitted date/time and a factual summary or downloadable copy when privacy controls allow. Explain that suitability, price, stock, dispatch and response timing require review. Do not invent guaranteed callbacks or quotation turnaround.

27. Failure recovery

For offline, timeout, validation failure, upload error, duplicate click and server rejection, preserve safe form state and display a clear next action. Use idempotency to prevent duplicate submissions; distinguish a failed network acknowledgement from an actually persisted enquiry.

28. Security

Enforce least-privilege record access, protected attachment storage, audit logs, input sanitisation, bot mitigation, encryption in transit and a documented retention/deletion policy. Ensure public confirmation pages cannot expose another customer’s enquiry by changing an ID.

29. Engineering triage

Classify submissions: sufficient for preliminary screening; clarification required; site survey recommended; specialist/high-pressure review; outside verified capability; or unsuitable request. A quotation must not be generated solely from an unverified form value.

30. Reviewer workflow

A reviewer sees original customer entries, derived conversions, source confidence, missing items, attached evidence, clarification history and disposition. Every technical recommendation needs an assigned owner and date; revisions must not overwrite original submissions without audit history.

31. Content and SEO

The page should answer “What information is needed to choose an air compressor?” before the form. Explain pressure, airflow, duty, quality and utilities in brief accessible language, with contextual links to deeper engineering articles. Avoid duplicating the FAQ Centre or technology comparison pages.