Confidential — internal TECHNICAL analysis — separate from the legal file

The Bearing Housing Failure & Retrofit — Technical Timeline

Second analysis: management record, decision timeline, and the stick-slip causation hypothesis · NOT part of the legal position

Months before any module cracking was reported, the Skyline II fleet suffered a distinct, documented failure: plastic bearing housings slipping and "exploding" across the portfolio. Arctech's corrective action — riveting/screwing the bearing housings on ~444 units — was completed in January–February 2026. The first cracked modules were found on 11 May 2026, roughly three months later. This page reconstructs the full chronology from the mailbox and the Dropbox 9. Warranty Issues record, and assesses whether the retrofit itself could be the root cause of the cracking.

9 Oct 2025
Bearing failures formally reported by iEnergia (2 Falcon + 1 Angol)
444
Bearing housings in Arctech's retrofit scope
≈9 Feb 2026
Retrofit reception (Angol + LS1; Dinamo/Falcon done by 3 Feb)
11 May 2026
First cracked modules found — ~3 months after the retrofit

Two damage waves — keep them distinct

WAVE 1 Oct 2025 – Feb 2026 · Direct breakage from exploding bearing housings

Failed housings physically destroyed adjacent modules. iEnergia, 10 Feb 2026: "Las piezas explotadas provocaron la rotura de una cantidad significativa de módulos… Estos no fueron reemplazados por el contratista." Photos in 9. Warranty Issues\Broken Modules (Trina-Arctech) dated 7 Oct 2025.

WAVE 2 From 11 May 2026 · Recurrent edge-cracking pattern

A different signature: "cracked modules at the short-side edges", mainly rear glass, some with electrical failure/smoking — portfolio-wide, on trackers with "wave-like movement" and documented torsional deflection. Photos dated 12 May 2026, in folders named Cracks in modules, Gap between modules, Deflection by torsion.

The distinction matters for any RCA: Wave 1 is mechanical impact damage from a failed component (undisputed, Arctech's contractor left modules unreplaced). Wave 2 is a stress-pattern failure whose cause is the open question — and it appeared only after the fleet-wide retrofit.

Full chronology — decisions, pushes, and management

The hypothesis: did the retrofit cause the cracking?

Stick-slip / constrained-bearing mechanism (working hypothesis — unproven)

The question: the added rivet/screw fixes the plastic bearing to (or through) its housing. If the fastener restricts the motion the bearing was designed to allow, two things follow:

CONSISTENT with the hypothesis

  • Sequence: retrofit completed ≈9 Feb 2026 → first edge-cracks 11 May 2026. No Wave-2 cracking is on record before the retrofit.
  • Failure signature: cracks at the short-side edges — where torsional/bending stress concentrates at the outer clamps — not random impact damage.
  • Field observations post-retrofit: jerky, uneven slew movement; wave-like motion; torsional deflection at tracker 56; module gaps (axial displacement indicator); misalignment vs as-delivered.
  • Wave 2 is portfolio-wide on the retrofitted fleet, same configuration everywhere.
  • Arctech's own precedent cases (Chile/Trina, Colombia/LONGi) were on Skyline II — recurrence on this product line.

AGAINST / UNKNOWN — must be tested

  • ~3-month lag Feb→May needs explaining (candidates: accumulating fatigue cycles; autumn/winter wind loads; larger thermal swings; detection lag — thermography only began May).
  • No cross-map yet of cracked-module positions vs retrofitted-bearing positions. If cracks cluster on non-retrofitted trackers, the hypothesis weakens badly.
  • LS2 retrofit status unclear — the documented scope was Dinamo/Falcon (444 u) + Angol/LS1 reception; LS2 had 3 failed bearings but its retrofit record hasn't been located.
  • Alternative causes uncontrolled: inherent module fragility (dual-glass 2.0 mm on 33 mm frame), purlin/fastener interface (bolt-washer vs rivets — the Owner's own open question), tracker control behaviour, O&M practices.
  • Arctech's 28 Jun position: "no significant structural abnormalities" — an interested party's conclusion, but on record.

How to test it — data requests and field work

#ActionWhat it proves / kills
1Cross-map: overlay (a) Wave-2 cracked-module locations, (b) the 444 retrofitted bearing positions, (c) Wave-1 failed-bearing locations, on the plant layouts (GA DWGs available per plant)If cracks cluster at/near retrofitted bearings → strong support. If uncorrelated → hypothesis substantially dead.
2Physical inspection of a sample of retrofitted housings: does the fastener contact/penetrate the bearing? Can the tube still slide axially? Measure breakaway torque vs an un-retrofitted unitDirect mechanical confirmation of binding
3Request Arctech's retrofit engineering: the method statement, fastener spec, and the engineering approval for the 444-unit campaign — plus TCU/slew-drive motor current logs (their system measures drive load; ours does not)Their own design docs either allowed for motion or didn't; current logs show binding as elevated/spiky draw
4Thermal test: measure module-gap / tube position morning vs midday on retrofitted rowsAxial-constraint confirmation (gaps should breathe; pinned tubes won't)
5Video + accelerometer on a jerky tracker during a full tracking dayCaptures stick-slip events and shock magnitude

Motor current on the layout — feasibility

Short answer: not mappable from our current SCADA — but there are three practical routes.

The Skyline II TCUs communicate via LoRa/RS-485 to Arctech's own controller; motor/slew-drive current is not exposed in the plant monitoring we operate for these sites (no tracker motor-current channel exists in the configured datapoints). Slopes concentrating friction on specific bearings is exactly the kind of pattern a current map would reveal, so:

Management record — what this timeline shows about iEnergia's handling

This page is a technical/management record. Its hypothesis is deliberately excluded from the legal correspondence until tested — an untested causation theory cuts both ways.