This article expands upon the definition of Partial Deployment with TS4 systems. For a definition of other deployment options, see TS4 Systems - Methods of Deployment.
Partial Deployment is defined as TS4-A-O deployed on some PV modules but not all, with monitoring enabled via the CCA and TAP:
Partial deployment features the application of strategically placed TS4 MLPEs only on PV modules that may be experiencing shade issues. The remaining PV modules are wired directly to each other.
This deployment is only applicable to systems that do not require a full system Rapid Shut Down (RSD) solution (i.e., ground-mounted systems). It includes Tigo TS4-A-O (Optimizers), a TAP (Tigo Access Point), and network connected CCA (Cloud Connect Advanced).
This method of deployment offers:
- Targeted optimization
- Localized data reporting
- Remote system updates
- Full warranty coverage (supported deployment, but not recommended)
Rule: Partial deployment should only be used when a string has its own MPPT and is actively independent of any other string. Partial deployment of optimization on parallel strings is NOT supported.
The following examples reinforce this rule.
When using a single string per MPPT, optimization can be partially deployed on the shaded modules (using TS4-O). For monitoring and safety/rapid shutdown functionality, TS4-S can be deployed on all unshaded modules.
Dual MPPT inverters can offer Partial Deployment of optimization on each MPPT.
Partial Deployment of optimization on parallel strings within a single MPPT is NOT supported.
IMPORTANT: With parallel strings on the same MPPT input, Full Deployment of optimization (TS4-O) is recommended: