Explore

ATA Acceptance Terms Agreement

Document Change Control

Revision

Date

Author(s)

Description

17/03/2020

Weslei Calazans

Initial Draft

There are no rows in this table

⁠

This document, called as Acceptance Terms Agreement ("ATA") entered into on March 17, 2020 between NETWORK TO NETWORK INTERFACE DIGITAL LTD. ("NNi.Digital") and ("Customer") provides the general terms and conditions applicable to the purchase of communications services ("Service") to NNi's Customer.

This Mutual Confidentiality Agreement ("Agreement") is entered into on the "Effective Date" according to the signature dates, whichever is more recent, between:

NNI.DIGITAL, a company of STUDIOTECH ANALYTICS SOLUTIONS LTDA with its principal place of business at São Paulo Brazil ("Discloser A")

and

[The Company], [the customer] with its principal place of business at [Telecom Company Address] ("Discloser B").

ACCEPTANCE TERMS AGREEMENT (ATA)

This Acceptance Terms Agreement ("ATA") is Exhibit to the Master Services Agreement ("MSA") dated [Date] between [Customer Name] ("Customer") and [Telecom Provider Name] ("Provider"). This ATA defines the acceptance criteria and testing procedures for Services provided under the MSA.

⁠

1.0 DEFINITIONS

1.1 "Acceptance" means Customer's formal acceptance that a Service meets the Acceptance Criteria defined herein. 1.2 "Acceptance Criteria" means the technical and performance specifications against which Services are tested. 1.3 "Acceptance Period" means the time window during which Customer may perform Acceptance Tests. 1.4 "Acceptance Test" means the testing procedures defined in this ATA. 1.5 "Defect" means a failure of the Service to meet Acceptance Criteria. 1.6 "Service Activation Date" means the date Provider notifies Customer that a Service is ready for testing. 1.7 "Test Plan" means the documented testing procedures for each Service type. 1.8 "Trouble Ticket" means a formal notification of a Defect requiring Provider action.

⁠

2.0 GENERAL ACCEPTANCE PRINCIPLES

2.1 Purpose

Acceptance Testing verifies that Services:

Meet technical specifications in the Service Order

Perform to committed service levels

Are properly configured and functional

Are ready for production use

2.2 Acceptance Workflow

2.3 Key Dates & Timelines

Acceptance Timelines

Acceptance Timelines

Service Type

Acceptance Period

Correction Period

Deemed Acceptance

Connectivity Services

5 Business Days

End of Acceptance Period

Data Center Services

3 Business Days

End of Acceptance Period

Cloud Connect Services

3 Business Days

End of Acceptance Period

Complex Deployments

10 Business Days

End of Acceptance Period

There are no rows in this table

⁠

Note: "Complex Deployments" include multiple circuit installations, international IEPL, or multi-site deployments.

⁠

3.0 CONNECTIVITY SERVICES ACCEPTANCE TESTS

3.1 Dedicated Internet Access (DIA)

3.1.1 Test Criteria

Circuit Configuration: Verify circuit ID matches Service Order

Bandwidth Validation: Confirm committed and burstable rates

BGP Peering: Establish and validate BGP sessions

Routing: Confirm default route and prefix advertisements

IP Allocation: Validate assigned IP block(s)

3.1.2 Performance Tests

Performance Tests

Performance Tests

Test

Method

Acceptance Criteria

Tools

Throughput

iPerf3, TCP/UDP

≥95% of committed rate

iPerf, Spirent

Latency

ICMP ping

≤[X]ms to Provider POP

Ping, SmokePing

Packet Loss

Sustained ping

≤0.1% over 1,000 packets

Ping, MTR

Jitter

UDP streams

≤5ms for 95th percentile

iPerf, Wireshark

Availability

Continuous monitoring

100% during test period

Provider portal

There are no rows in this table

⁠

3.1.3 Test Duration & Pattern

Throughput Tests: 24-hour continuous test for production circuits

Stress Tests: 15-minute bursts at 100% committed rate

Protocol Validation: TCP/UDP/ICMP verification

Sample Rate: 5-minute intervals for all metrics

3.2 IP Transit Services

3.2.1 Test Criteria

Peering Validation: Confirm peering with transit providers

Route Table: Verify full Internet routing table (>900k routes)

Traffic Engineering: Validate MED, AS-PATH, Local Pref settings

DDoS Protection: Confirm scrubbing center connectivity (if applicable)

3.2.2 Performance Benchmarks

Performance Benchmarks

Performance Benchmarks

Destination

Latency Target

Packet Loss Target

Test Points

Major IXPs

≤[X]ms

≤0.05%

AMS-IX, DE-CIX, LINX

Cloud Providers

≤[X]ms

≤0.1%

AWS, Azure, Google

CDN Networks

≤[X]ms

≤0.05%

Akamai, Cloudflare, Fastly

Regional POPs

≤[X]ms

≤0.1%

All Provider POPs

There are no rows in this table

⁠

3.3 IEPL (International Ethernet Private Line)

3.3.1 Circuit Validation

Circuit Path: Validate complete Layer 2 path

VLAN Configuration: Confirm VLAN tagging and mapping

Ethernet OAM: Verify 802.1ag/Y.1731 continuity

Carrier Codes: Validate UNI, EVC, and EPL identifiers

3.3.2 International Specific Tests

Regulatory Compliance: Document import/export certifications

Cross-Border Testing: Validate handoff at each country border

Time Zone Testing: Confirm timestamp synchronization

Currency Conversion: Billing validation (if applicable)

3.3.3 Performance Requirements

Performance Requirements

Performance Requirements

Circuit Size

Throughput

BER Requirement

MTU

≤100Mbps

≥99% of CIR

≤10⁻⁹

1522 bytes

1Gbps

≥99.5% of CIR

≤10⁻¹⁰

1522 bytes

10Gbps

≥99.8% of CIR

≤10⁻¹¹

1522 bytes

100Gbps

≥99.9% of CIR

≤10⁻¹²

1522 bytes

There are no rows in this table

⁠

CIR = Committed Information Rate

3.4 VPN Services (MPLS, VPLS, SD-WAN)

3.4.1 Site-to-Site Testing

Full Mesh Testing: All sites to all other sites

Hub-Spoke Validation: Central site connectivity

QoS Validation: DSCP/CoS marking and prioritization

Encryption: IPSec/SSL tunnel establishment

3.4.2 Class of Service Validation

Class of Service

Class of Service

Class

Jitter

Latency

Packet Loss

Bandwidth Allocation

Real-Time

≤5ms

≤50ms

≤0.01%

Guaranteed

Critical Data

≤10ms

≤100ms

≤0.05%

Guaranteed

Standard

≤50ms

≤200ms

≤0.1%

Burstable

Best Effort

N/A

Remaining

There are no rows in this table

⁠

4.0 DATA CENTER SERVICES ACCEPTANCE TESTS

4.1 Physical Infrastructure Validation

4.1.1 Rack & Space Acceptance

Rack & Space Acceptance

Rack & Space Acceptance

Test Item

Method

Acceptance Criteria

Documentation

Rack Dimensions

Physical measurement

Match Service Order specs

Photos, measurements

Weight Capacity

Static load test

1500lb per cabinet

Load test report

Clearance

3D modeling verification

≥36" front/rear clearance

CAD drawings

Security

Access control test

Badge/pin/biometric working

Access logs

There are no rows in this table

⁠

4.1.2 Power Acceptance Tests

Power Acceptance Tests

Power Acceptance Tests

Test

Procedure

Acceptance Criteria

Duration

Circuit Load

Progressive load test

≤80% of rated capacity

4 hours

Phase Balance

Multi-phase verification

≤10% phase imbalance

Continuous

Transfer Test

Manual transfer

≤20ms transfer time

3 attempts

Generator Test

Load bank test

0% voltage sag

2 hours

There are no rows in this table

⁠

4.1.3 Cooling Validation

Temperature Mapping: Thermal imaging of rack

Airflow Verification: Smoke test for containment

Redundancy Test: CRAC unit failover

Humidity Control: Rapid humidity change test

4.2 Cross-Connect Acceptance

4.2.1 Physical Cross-Connects

Cross-Connect Acceptance

Cross-Connect Acceptance

Type

Test Procedure

Acceptance Criteria

Documentation

Fiber

OTDR testing

≤0.5dB loss per connection

OTDR traces

Copper

Fluke certification

Cat6A/Cat8 specifications

Test report

Intra-facility

End-to-end ping

100% packet delivery

Test logs

Inter-facility

Throughput test

≥99% of rated speed

iPerf results

There are no rows in this table

⁠

4.2.2 Virtual Cross-Connects

VLAN Configuration: VLAN isolation testing

Broadcast Domain: Spanning tree validation

MAC Learning: MAC address table verification

Loop Prevention: STP/RSTP/MSTP convergence

⁠

5.0 CLOUD CONNECT SERVICES ACCEPTANCE TESTS

5.1 Direct Connect Acceptance

5.1.1 Physical Port Validation

Physical Port Validation

Physical Port Validation

Test

Procedure

Acceptance Criteria

Cloud Provider

Port State

Interface status

Up/Up, no errors

All

Speed/Duplex

Negotiation test

Match Service Order

All

Optical Power

Light levels

Within spec range

All

LACP

Link aggregation

Active/standby working

AWS, Azure

There are no rows in this table

⁠

5.1.2 Virtual Interface Testing

Virtual Interface Testing

Virtual Interface Testing

Interface Type

Test Focus

Acceptance Criteria

Key Metrics

Private VIF

VPC/VNet connectivity

Full routing table exchange

Routes received

Public VIF

Internet egress

NAT/PAT validation

Public IP access

Transit VIF

Gateway connectivity

Direct routing to cloud

Latency ≤10ms

BGP Session

Peer establishment

Established state

Prefix exchange

There are no rows in this table

⁠

5.1.3 Cloud-Specific Tests

AWS Direct Connect: VPC attachment, Direct Connect Gateway

Azure ExpressRoute: Circuit provisioning, peering configuration

Google Cloud Interconnect: VLAN attachment, BGP session

Oracle Cloud: FastConnect virtual circuit, DRG attachment

5.2 Cloud-to-Cloud Connectivity

5.2.1 Multi-Cloud Validation

Cloud-to-Cloud Connectivity

Cloud-to-Cloud Connectivity

Connection

Test Type

Acceptance Criteria

Test Tool

AWS-Azure

Cross-cloud ping

≤20ms latency

Cloud-native tools

Azure-GCP

Data transfer

≥95% of committed rate

azcopy, gsutil

GCP-AWS

Service endpoint

Successful connection

SDK validation

Multi-region

Geo-redundancy

Failover within 30 seconds

Automated tests

There are no rows in this table

⁠

5.2.2 Performance Benchmarks

Performance Benchmarks Tests

Performance Benchmarks Tests

Metric

Within Region

Cross-Region

Global

Latency

≤5ms

≤50ms

≤150ms

Throughput

≥99% CIR

≥98% CIR

≥95% CIR

Packet Loss

≤0.01%

≤0.05%

≤0.1%

Jitter

≤2ms

≤10ms

≤20ms

There are no rows in this table

⁠

6.0 DEFECT MANAGEMENT & RESOLUTION

6.1 Defect Classification

Defect Classification

Defect Classification

Severity

Impact

Response Time

Resolution Time

Billing Impact

Critical

Service unusable

1 hour

4 hours

No billing until resolved

Major

Significant degradation

4 hours

1 Business Day

50% credit during defect

Minor

Non-critical issue

1 Business Day

3 Business Days

25% credit during defect

Cosmetic

Documentation/visual

2 Business Days

5 Business Days

No billing impact

There are no rows in this table

⁠

6.2 Defect Reporting Process

Notification: Email to [Acceptance Test Team] with subject "[Defect] - [Circuit ID]"

Required Information:

Service Order number

Circuit/Service ID

Detailed description with screenshots

Test logs and evidence

Impact assessment

Acknowledgement: Provider acknowledges within 2 Business Hours

Tracking: Defects tracked in [Provider Ticketing System]

6.3 Re-Testing After Correction

Partial Defect: Test only affected components

Critical Defect: Full re-test suite required

Multiple Defects: Extended Acceptance Period (additional 2 Business Days)

Repeated Defects: Escalation to Provider management required

⁠

7.0 ACCEPTANCE DOCUMENTATION

7.1 Required Deliverables

7.1.1 Provider Deliverables (Prior to Testing)

Complete circuit documentation (LOD/LSR)

Test IP addresses and credentials

Network diagrams (Layer 1-3)

Configuration details (BGP, VLAN, QoS)

Access credentials to monitoring portal

Contact lists for support escalation

Emergency procedures documentation

Change management process

7.1.2 Test Execution Documentation

Signed test plan (by both parties)

Raw test results and logs

Screenshots of successful tests

Performance graphs and metrics

Defect reports and resolutions

Configuration backup/archives

7.2 Acceptance Certificate Template

ACCEPTANCE CERTIFICATE

Service Order: [Number] Circuit ID: [Identifier] Service Type: [DIA/IP Transit/IEPL/etc.] Service Activation Date: [Date]

Test Results Summary:

All Acceptance Criteria met

Performance tests completed successfully

Documentation received and reviewed

Training completed (if applicable)

No Critical or Major defects outstanding

Customer Acceptance: By signing below, Customer accepts the Service as complete and meeting all requirements. Billing will commence per the Service Order terms.

NNI.DIGITAL

[CUSTOMER COMPANY NAME]

Signature

Name

Title

Date

There are no rows in this table

⁠

8.0 BILLING COMMENCEMENT & SERVICE TERM

8.1 Billing Triggers

Billing commences on the earliest of:

Customer's signed Acceptance Certificate date

Deemed Acceptance date (end of Acceptance Period)

Customer's productive use of the Service

[Number] days after Service Activation Date

8.2 Service Term Start

Service term begins on the billing commencement date, not the Service Activation Date.

8.3 Trial Period (Optional Negotiation)

For critical circuits, negotiate:

30-day Trial Period: Billing at 50% of MRC

Acceptance at End: Full billing only after successful trial

Early Exit Right: Terminate without penalty if performance unacceptable

⁠

9.0 DISPUTE RESOLUTION

9.1 Technical Disputes

Joint Testing: Both parties participate in re-test

Third-Party Validation: Mutually agreed testing firm

Escalation Path: Technical → Management → Executive

Hold Harmless: No billing during dispute resolution

9.2 Performance Disputes

Reference: SLA metrics as definitive measure

Measurement: Provider monitoring + Customer validation

Resolution: Joint review of 24-hour test results

Remedy: Service credit or remediation plan

⁠

10.0 SPECIAL PROVISIONS

10.1 International Services (IEPL)

Regulatory Acceptance: Subject to local authority approvals

Cross-Border Testing: Required at each border point

Currency Acceptance: Billing currency verification

Local Compliance: Adherence to national regulations

10.2 Cloud Connect Services

Cloud Provider Acceptance: Subject to cloud provider provisioning

API Integration: Validation of automated provisioning

Multi-Cloud Complexity: Extended testing for complex environments

Cloud Marketplace: Acceptance of marketplace terms

10.3 Data Center Co-location

Physical Security Acceptance: Site visit and validation

Environmental Compliance: Verification of certifications (ISO, SOC, etc.)

Carrier Neutrality: Validation of available carriers

Remote Hands: Procedure validation

⁠

11.0 APPENDICES

Appendix A: Test Tools & Methodologies

Recommended testing tools (iPerf, SmokePing, etc.)

Test configuration templates

Script libraries for automated testing

Cloud testing methodologies

Appendix B: Sample Test Plans

DIA acceptance test plan

IEPL acceptance test plan

Data center acceptance checklist

Cloud connect validation guide

Appendix C: Regulatory Compliance

International testing requirements

Data sovereignty validation

Encryption standards verification

Compliance certification requirements

⁠

KEY NEGOTIATION POINTS & MARKET PRACTICES

Critical Negotiation Areas:

Acceptance Period Duration:

Provider Standard: 3-5 Business Days

Negotiation Target: 10-15 Business Days for complex services

Best Practice: Tiered based on service complexity

Billing Commencement:

Provider Standard: Service Activation Date or deemed acceptance

Negotiation Target: Only after signed acceptance

Best Practice: 50% billing during testing, 100% after acceptance

Defect Resolution:

Provider Standard: Reasonable efforts

Negotiation Target: Defined SLAs for defect correction

Best Practice: Financial penalties for repeated defects

Testing Methodology:

Request: Jointly developed test plans

Request: Right to use third-party testing tools

Request: Automated testing integration

Red Flags to Address:

Vague acceptance criteria

Short testing windows for complex services

No defined defect resolution process

Billing starts before service is usable

Limited testing access or tools

No acceptance documentation requirements

Industry Best Practices:

Phased Acceptance: For complex deployments

Penetration Testing: For security-critical circuits

Failover Testing: Before production use

Documentation Review: Formal sign-off on all documentation

Training Completion: Before acceptance for managed services

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.