LGU internet TOR and SLA: specify more than Mbps
By 1Gov advisory team · Published · Updated
An LGU internet Terms of Reference (TOR) should define the service, how it will be measured and who will restore it when it fails. The service-level agreement (SLA) turns those needs into measurable commitments.
Define the service and responsibilities
Identify offices, users, critical applications and the impact of downtime. Specify committed bandwidth, latency, packet loss and the measurement points. Separate provider-link faults from internal Wi-Fi, router or power problems. Assign equipment maintenance, security, monitoring and escalation responsibilities.
Practical example: a municipal office
Hypothetical only: the office needs connectivity for online public-service transactions. Its TOR could require bidders to address these points:
- Service: measure availability at the provider handoff; propose a justified monthly target and a method for recording outage start and end.
- Support: state separate incident-acknowledgement and service-restoration targets, escalation contacts and remedies for missed commitments.
- Evidence: demonstrate acceptance tests and backup-link failover; provide monthly outage logs and explain any maintenance exclusions.
Choose targets that fit the LGU
For illustration, acknowledging a fault within 30 minutes is different from restoring service within four hours. These are example targets, not prescribed standards or proven supplier capabilities. Validate targets against service criticality, local coverage, provider capacity and budget before finalizing the TOR.
Compare lifecycle cost and plan the exit
Include installation, circuit fees, equipment, support, retained staff and renewal costs. Compare ownership with managed-service options against the same requirements. Agree on configuration handover, credentials and continuity at contract end. 1Gov provides independent advice; the LGU retains procurement, approval and award decisions.