Service Scope
Detailed description of SD-WAN services delivered, site list, circuit dependencies, and any hardware or virtual appliance responsibilities for both provider and customer.
A focused addendum clarifies technical deliverables, assigns operational responsibilities, and isolates SD-WAN-specific billing and SLA terms so parties avoid ambiguity in performance, change orders, and incident response.
Teams from IT, networking, procurement, and vendor account management commonly collaborate to prepare an SD-WAN addendum.
Each party should confirm internal approval pathways so signatory authority and operational contacts are included in the executed addendum.
Typically an enterprise network lead or technical director who validates the SD-WAN configuration, approves acceptance criteria, and receives technical support contacts. This signer confirms the service meets specified throughput, encryption, and failover requirements and coordinates site-level changes with field engineering teams.
A procurement or vendor manager who confirms commercial terms, billing start date, renewal cycles, and any early-termination liabilities. This signer ensures purchase orders align with the addendum and that billing integrations with AP systems are documented.
Detailed description of SD-WAN services delivered, site list, circuit dependencies, and any hardware or virtual appliance responsibilities for both provider and customer.
Measured metrics (latency, jitter, packet loss), target levels, measurement windows, remedies or credits for missed SLAs, and escalation contact paths.
Procedures for pushing configurations, approval workflow for changes, maintenance windows, rollback plans, and notification lead times for planned changes.
Encryption standards, segmentation requirements, logging obligations, incident response roles, and any HIPAA or data residency considerations.
Pricing, billing commencement trigger, contract term, renewal mechanics, early termination charges, and hardware ownership or lease terms.
Acceptance criteria, test cases, measurement tools, timeline for remediation, and final sign-off procedure for site activation.
| Field | Configuration |
|---|---|
| Signer Sequence | Customer IT -> Procurement -> Provider Accounts |
| Authentication Level | Email link plus SMS OTP for external signers |
| Conditional Fields | Enable device serial entry when hardware supplied |
| Notifications | Immediate email on each completed step |
Ensure the signing platform supports the document format, authentication, and integrations you need.
MM/DD/YYYY; provisioning can start
Typically 15–45 days depending on circuits
Commences on service acceptance
30 days notice for material changes
60–90 days as specified
Optica used the addendum to define acceptance and NOC responsibilities
Xerox attached device management rules and NetSuite billing codes in the addendum