Note
What a Factory Electrical Maintenance Agreement Must Say
A maintenance agreement signed at handover is a good start. The problem is that general terms leave gaps exactly where both sides need clarity most.
When a factory calls at 7am because the solar system stopped generating overnight, the first question is: is this visit covered? If the agreement says “regular maintenance and inspections,” the contractor and the customer interpret that sentence differently under pressure. The contractor sees a scheduled service agreement. The customer sees around-the-clock support. Neither is wrong given what the agreement actually says.
What resolves this is a maintenance agreement scope written specifically enough that whoever takes the call can check coverage in two minutes. Here is what that scope needs to contain.
What Does a Factory Electrical Maintenance Agreement Cover?
The standard scope divides by system type.
For industrial LED retrofit installations, the scope typically includes:
- Annual lux verification at the measurement points recorded during installation
- Replacement of failed LED drivers and lamps within the manufacturer’s warranty period
- Visual inspection of conduit runs, junction boxes, and distribution panel connections
- A signed inspection report the factory can keep on file for compliance purposes
For commercial and industrial solar systems, the scope usually adds:
- Panel cleaning on a set schedule. In Thailand, twice a year is common: once before the wet season (around April) and once near year-end.
- Inverter inspection: error log review, cooling fan and filter check, DC and AC connection torque verification
- System performance review comparing actual energy yield against the commissioning baseline record
- Annual electrical inspection report for submission to the relevant authority
Both lists are starting points. The site-specific scope adjusts for panel count, inverter model, site access conditions, and any special equipment installed alongside the main system.
What Falls Outside the Scope?
Most disputes in maintenance agreements are not about what is included. They are about what happens when something breaks and the agreement is silent on whether it applies.
Three categories belong explicitly in the exclusions section:
Grid-side events. An inverter protection trip caused by grid over-voltage is the inverter responding correctly to an external condition. The contractor did not cause it and cannot prevent it. Diagnosing and resetting the inverter after a grid event is chargeable unless the agreement specifically includes it.
Physical damage from factory operations. Conduit struck by a forklift, panels damaged during a building expansion, connections disturbed by a third-party electrician are all outside a maintenance scope. Photograph the damage on arrival before any work begins.
Third-party modifications. If the customer’s maintenance team or another contractor has modified the installation since handover, that work is outside the scope. The original design and workmanship obligations apply only to the installation as it left your crew.
Stating these exclusions in plain language is not adversarial. The customer benefits from knowing what falls to them. The contractor benefits from having a document to reference when the conversation becomes difficult.
How Often Should Visits Be Scheduled?
Thai factory electrical installations require at least one inspection per year under statutory requirements. The first inspection falls roughly twelve months after commissioning, which ties naturally to the date already in the site register.
Beyond the statutory minimum:
- Solar systems benefit from two panel cleans per year. April and October work well for most central and eastern Thailand factories: the first clean removes dry-season accumulation before the wet season, the second clears pollen and debris after the wet season ends.
- LED installations typically require one annual visit. Driver failure rates are low in the first few years. The annual visit handles the lux check, connection inspection, and the signed inspection report.
Write the schedule as specific months, not as “biannual” or “Q2 and Q4.” A maintenance agreement that names April and October is easier to staff than one that specifies a vague interval. Both parties know what to expect, and the visits can be added to the schedule twelve months in advance.
Does the Agreement Cover Emergency Calls?
This is the most common source of disagreement between contractors and clients. The customer assumes that a maintenance relationship includes emergency response. The contractor knows that an unplanned visit disrupts the technician schedule and involves short-notice travel.
Three structures work in practice:
Capped inclusion. The agreement covers a set number of emergency call-outs per year (two unplanned visits, for example). Additional calls are chargeable at a separately agreed rate.
Separate billing. Emergency response is available but invoiced outside the agreement. The agreement covers scheduled visits only; emergency calls are billed per visit.
Explicit exclusion. The agreement states clearly: scheduled visits only. Emergency response is available at the agreed rate and is not part of this agreement.
Worked example: a contractor closes a 300 kWp rooftop solar install at a factory in Samut Prakan. The site register shows 840 panels, two 150 kW inverters (manufacturer warranty: 5 years from handover), and combiner boxes (manufacturer warranty: 2 years). The maintenance agreement written at handover includes two panel cleans (April and October), one inverter inspection combined with the October clean, one annual statutory inspection in November, and one included emergency call-out per year. Calls beyond that are chargeable at an agreed rate. That is the entire scope in one paragraph.
Using Handover Data to Write the Scope
At handover, you have everything you need: the equipment list, serial numbers, warranty expiry dates for each component, and the date of the first required inspection. That information is already in the site register from the closed job.
Writing a specific maintenance scope from that data at handover takes thirty minutes. Getting the same information two years later, when a scope addition is needed or a dispute arises, requires a site visit to reconfirm what was installed. The site register that closes the job is the same document that opens the maintenance conversation.
FAQ
What If the Customer Wants to Add Scope Mid-Year?
A scope addition is a written confirmation attached to the original agreement. An email from the customer’s authorized representative confirming the addition is sufficient. Verbal agreements during a site visit are not reliable: the person who was present may not be the one who receives the invoice.
What If Site Conditions Have Changed Since Handover?
If the factory has expanded the system, modified the installation area, or changed access conditions, the visit scope agreed at handover no longer applies cleanly. Flag the change before the visit, not on the day the crew travels. Both sides can confirm what the visit now covers before the truck moves.
When Is the Right Time to Write the Scope?
At handover, using the site register data from the closed job. Equipment lists, serial numbers, warranty expiry dates, and the first inspection date are already recorded. Writing a specific maintenance scope from that data at handover takes thirty minutes and prevents a dispute twelve months later.
To see how TRACE 30 links the site register at job close to maintenance planning and visit scheduling, the overview is at /program/. If your current close process does not produce the data a specific maintenance scope requires, a short call at /schedule-a-call/ is a useful starting point.