Why maintenance support is decided too late

Most manufacturers think about ongoing support at the end of the procurement process, if at all. The supplier has been selected, the contract is signed, and someone asks: "What about maintenance?" By that point, the answer is whatever the supplier says it is — and there is no leverage to negotiate harder terms or a better model.

The smarter approach is to treat maintenance and support capability as a procurement criterion from the start, not a post-delivery consideration. A line that runs at 85% OEE for five years is worth far more than one that hits peak output in month one and degrades to 60% by year three.

Decision rule: evaluate the after-sales and support model before you sign the procurement contract, not after the equipment ships.

The five questions that reveal real maintenance capability

1. Where are your engineers, and what is their realistic response time to my site?

Ask for the specific location of the engineers who would respond to your line, not the company's registered office address. A Johannesburg-headquartered supplier with its nearest engineer in Cape Town is a different proposition from one with an engineer 30 minutes from your plant.

Then ask: in a production-down breakdown, what is the realistic time from call to engineer-on-site? Get a number, not a policy. "We target 24 hours" is a target. "Our engineer lives in Germiston and can be on the N1 within the hour" is a capability.

Failure mode: accepting "we have nationwide coverage" as an answer. Ask for postcode-level specifics.

2. What A-list spares do you hold in-country, and where?

A-list parts are the components whose failure stops the line and cannot be improvised. For an imported Chinese line, these are typically: PLC I/O cards, drive units, specific bearings, seal assemblies, and any mechanical component with a 6+ week lead time from the OEM.

Ask the supplier to show you their in-country spares holding — specifically which A-list items for your line category, where they are physically held, and on what replenishment cycle. A maintenance partner whose answer is "we can order from China in 4–6 weeks" is not a maintenance partner for a production-down scenario.

Failure mode: taking "full spares support" at face value without asking what is actually on the shelf.

3. Do your engineers have PLC and controls capability on my specific platform?

Mechanical maintenance and controls maintenance are different disciplines. A supplier with good mechanical engineers but no one who can read your PLC ladder logic will be able to replace a gearbox but not diagnose a control fault. On modern automated lines, the majority of unplanned stoppages have a controls root cause.

Ask specifically: which PLC platform does your line use, and can the supplier show you a certified programmer or engineer for that platform? This matters most for Siemens TIA Portal, Allen-Bradley Studio 5000, Schneider Unity, and Beckhoff TwinCAT — the platforms most common on Chinese industrial equipment destined for Africa.

4. Is remote support possible, and what does it actually look like?

Remote diagnostics and PLC access can resolve 30–50% of controls-related faults without an engineer on site, dramatically reducing downtime for non-mechanical issues. Ask whether:

  • The line has or can be fitted with a remote access gateway (VPN-secured industrial router).
  • The supplier has a structured first-response process — a defined escalation from remote triage to dispatch.
  • Response to a remote support request is measured in hours, not in "someone will call you back."

Failure mode: confusing "we can do remote support" (a capability claim) with "we have a defined remote-first response process" (an operating commitment).

5. Can you give me two or three references from comparable lines, post-warranty?

The reference check for maintenance is different from the reference check for delivery. For delivery, you are asking whether the line was commissioned on time. For maintenance, you are asking what happened in year two and year three, when the commissioning engineer is long gone and the relationship is just an ongoing service contract.

Ask references specifically:

  • What was the worst breakdown you had, and how long was the line down?
  • Were the spares you needed actually available locally?
  • Is the partner still as responsive now as they were in the first year?

A supplier who cannot produce two or three post-warranty references from comparable lines in your geography is telling you something important.

The three support models and what they cost

Model What it covers Typical cost band (SA, 2026) Best for
Ad-hoc / call-outYou call when something breaks. No retainer, no scheduled PM.ZAR 2 500–6 000 per call-out + partsSimple lines, strong internal maintenance team
Scheduled PM contractPlanned preventive maintenance visits (typically quarterly or bi-annual) plus priority response on breakdowns.ZAR 8 000–25 000 per month depending on line complexityLines where downtime risk is moderate and internal skills are partial
Full support contractScheduled PM + spares management + SLA-backed response time + remote monitoring + budget certainty.ZAR 20 000–80 000 per monthLines where downtime cost is high and internal maintenance is limited

These are indicative ranges only. The actual cost depends heavily on line complexity, geographic remoteness, spares holding required, and response-time SLA.

What CISH does in this area

CISH offers commissioning and maintenance support through Commissioning & Maintenance, with field engineers based in South Africa, critical-spares buffer stock in Johannesburg, and remote access capability for lines where controls access is configured. We support both lines we have delivered and lines we have not — the entry point is an equipment inspection and a scope definition meeting before any contract is signed.

We are not the right answer when your line is simple, well-documented, and your internal team has the controls capability to diagnose and repair. We are worth a conversation when any of the following applies: the line is imported and Chinese-documented, the nearest OEM engineer is in Shanghai, your maintenance team is strong mechanically but weak on controls, or your last breakdown took longer than it should have because the right spare was not in the country.

Frequently asked questions

How do I know if my line needs a maintenance contract or ad-hoc support?

If a production stoppage of more than 48 hours would materially affect your business, a scheduled maintenance contract is worth modelling. The break-even is usually the cost of one unplanned major breakdown versus the annual contract fee.

Can a local partner support a Chinese production line they did not install?

Yes, with conditions. The partner needs the documentation package (schematics, PLC code, BOM), familiarity with the controls platform, and a defined spares strategy. Without these, support is reactive and slow. CISH can take on lines we did not install after an inspection and documentation review.

What is a realistic SLA response time for a production-down breakdown?

For lines in Gauteng, same-day or next-morning engineer on site is achievable with a proper support contract. For more remote sites in SADC, 24–72 hours is realistic depending on the location and whether a remote diagnosis can precede the dispatch.

Is remote support a real alternative to on-site maintenance?

For controls-related faults on lines with remote access configured, yes — a significant share of stoppages can be diagnosed and cleared remotely. For mechanical faults, remote support can diagnose and prepare for on-site work, but cannot replace it. The most effective model uses remote triage as a first-response step before dispatch.

How should I structure a maintenance contract for an imported Chinese line?

The contract should specify: response time SLA (hours to on-site, by severity), which A-list spares the partner holds in-country, the PM visit schedule and scope, remote access terms, and what happens when a part is not available locally. A contract that is silent on spares availability is not a serious maintenance commitment.