Site Survey & Network Infrastructure Assurance · Data Sheet
Site Survey & Network Assurance Results
Commercial and operating results separated by evidence status, so identified exposure is not confused with recovered value.
Evidence discipline
IDENTIFIED means the source pack supports a discrepancy or exposure. DIAGNOSTIC means a measured or analytical result that explains performance. ACKNOWLEDGED means the service provider accepted that reconciliation or credit action was required.
ACHIEVED would require evidence that the corrective action or financial recovery was completed. The supplied pack does not support an achieved monetary saving, so no final recovered amount is stated anywhere in this document.
Quantity variances
Signed against invoiced, line by line
Scroll table sideways →
| Status | Item | Signed / invoiced | Variance |
|---|---|---|---|
| Identified | Large rack quantity | 15 / 16 | +6.7% |
| Identified | Small rack quantity | 34 / 37 | +8.8% |
| Identified | Brush-panel quantity | 246 / 261 | +6.1% |
| Identified | Patch-panel quantity | 246 / 254 | +3.3% |
| Identified | PoE switch quantity | 77 / 83 | +7.8% |
| Identified | Five-line aggregate | 618 / 651 units | 33 excess units, +5.3% |
The aggregate 5.3% is an excess unit count across five isolated invoice lines. It is not a percentage of spend, and the source labels it that way explicitly.
Service and performance
What the diagnostic work measured
Scroll table sideways →
| Status | Measure | Finding |
|---|---|---|
| Acknowledged | Reconciliation and credit principle | Provider correspondence records that a full reconciliation was required and credit would be paid where due. The principle is acknowledged; the final value is not evidenced. |
| Diagnostic | Connectivity performance | Contracted headline profile of 20 Mbps per branch, against cited measurements of 2 to 9 Mbps — observed delivery at 10% to 45% of headline. |
| Diagnostic | Historical service incidents | 3,534 tickets in the fault review, 141,667.8 cumulative incident-hours, average repair duration about 40 hours. |
| SLA exception | Long-duration incidents | 166 tickets exceeded the prolonged-downtime threshold, with the source analysis stating an average above 400 hours for that group — approximately 4.7% of analysed tickets. |
| Diagnostic | Equipment-failure incidents | 689 incidents grouped under equipment failure; 178 resolved by replacement, averaging about 42 hours. |
| Identified | Legacy service billing | Continuing billing for legacy communications equipment reportedly unplugged or no longer required, with migration status uncertain. Exposure identified; recovery not evidenced. |
Reading the connectivity figure
Between a tenth and a half of what was contracted
A contracted headline of 20 Mbps per branch against measurements of 2 to 9 Mbps is not a marginal shortfall. At the lower end the branch received a tenth of the profile it was paying for.
That finding is diagnostic rather than financial here, because converting a performance gap into a recovery requires the contract's own service-level definitions, measurement method and remedy provisions — which is the work the companion contractual claim did.
Why the two problems were kept apart
A technical fault and a billing error argue differently
Mixing them is the common failure in this category. A provider defending a performance complaint will discuss network conditions; a provider defending a quantity variance has to reconcile a signed schedule against an invoice. They are different conversations with different evidence and different remedies.
Isolating the five billing lines at line-item level is what made the commercial half of this engagement actionable, independently of whether the throughput argument was ever resolved.