Skip to main content
GullySystem
Manufacturing

Service Reminders for Compressor manufacturers

Track due service events and their follow-up messages.

Field Service

Does this function belong in your operation?

Use when repeat services or renewals depend on dates or recorded usage.

A service date, usage threshold or contract obligation approaches.

A reminder is raised when running hours reach an oil or separator change point, or a pressure vessel inspection falls due. The customer receives it as a message. A matching spare kit is quoted with it.

Bring the records the workflow depends on.

  • Due-date rules
  • Customer and asset references
  • Contact permissions

Outputs to check

  • Due-service action list
  • Reminder and response history
  • Booking or deferral outcome

Follow the service reminders workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the due event

    Record the service date, usage trigger or contract obligation.

  2. 2. Check current status

    Exclude completed or retired items and verify contact permissions.

  3. 3. Prepare the follow-up

    Create the approved message or staff action.

  4. 4. Record the response

    Capture booking, deferral or an unresolved request.

  5. 5. Update from evidence

    Reset the due event only after the relevant service or renewal is confirmed.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Service advisor

Works the day’s reminders between vehicles and books what can be booked.

Receptionist

Reviews permitted follow-up messages, records customer responses and creates booking handoffs where requested.

Owner

Compares due services with completed visits and reviews unresolved follow-up outcomes.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Contact permission absent

Leave the communication unsent and route the permitted follow-up method.

Customer postpones

Record the agreed next action without falsely marking the service complete.

Asset no longer in use

Review the trigger with its owner before removing future reminders.

Can this work independently?

Reminders require a reliable due date or usage trigger. Job cards, contracts or customer records can supply it; booking systems record the resulting appointment. Messaging needs an authorised channel. A sent reminder does not reset the service due date or prove the service occurred.

Systems and records it connects with

  • Job cards: Service findings, approved work, parts and completion records.
  • AMC contracts: Contract coverage, dates and planned service obligations.
  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • List recurring jobs. Tell us which bring a customer back and after what gap, and reminder types come back to confirm.
  • You draft or approve wording per type. Message templates arrive for staff to use. Existing job cards or sheets supply the dates. A trial import shows today’s list.
  • The service advisor works the list for a while. Replies are recorded and wording is adjusted.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Reminders use the current due date.
  • Completed events do not keep triggering.
  • Failed messages remain visible.
Compressor manufacturers

How the business operates.

Reciprocating and screw compressors share one habit. They earn their reputation after sale, on the plant floor, over thousands of running hours. A maker that cannot see its installed base loses the service work.

Air delivery quotations

Quote by pressure, delivery and duty from your own model and option lists, with every revision kept.

Airend, motor and receiver records

Link the airend, motor, receiver and control panel to the package serial, with certificate numbers noted.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and duty capture. Log pressure, delivery, shift hours and ambient temperature on each enquiry, with site photographs and sketches.
  • Quotations and options. Price packages from your own model and option tables for dryers, filters, enclosures and receivers, and keep each revision.
  • Base frame and parts list control. Release the frame drawing and parts list with a revision letter, so assembly builds what was ordered.
  • Airend and motor receipt. Receive airends and motors with their serials and link them to the package that uses them.

Operational bottlenecks to check

Airend and motor serials are not tied to the package

The airend carries one serial and the package another. When a unit returns for warranty, the pair is looked up in two places.

Receiver tank certificates are filed separately

A vessel arrives with a test record kept by purchasing. The compressor shipped carries only the nameplate.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and duty

    The enquiry records pressure, delivery, shift hours and ambient conditions. A model and options are shortlisted.

  2. 2. Quotation

    The package, dryer, filters and enclosure are priced from your tables. Revisions are kept.

  3. 3. Order and build release

    A confirmed order opens a package serial. The base frame, parts list and control panel are released.

  4. 4. Assembly

    Airend, motor, cooler, separator and wiring are fitted. The receiver is mounted after its pressure result is saved.

  5. 5. Bench test

    Delivery, power and temperature are recorded. The test summary is stored with the serial.

  6. 6. Dispatch and service

    Delivery, commissioning and the first service date are recorded. Running hours then drive the kit and visit plan.

Industry reports to connect with

  • Packages in build, by stage and model
  • Airends and motors received against used
  • Bench tests done, passed and awaiting
  • Open, won and lost quotations, by pressure class

Questions before implementation.

When should compressor manufacturers consider service reminders?

Use when repeat services or renewals depend on dates or recorded usage. A service date, usage threshold or contract obligation approaches.

What should we bring to the requirements discussion?

Bring anonymised examples of Due-date rules; Customer and asset references; Contact permissions. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Track due service events and their follow-up messages. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Regulated health or safety decisions must be made by qualified people rather than reminder rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Reminders use the current due date. Use this check when reviewing the first working version.

Talk to us

Discuss service reminders for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements