|
2.1
|
Change
to the Price of the TASS Services for the Fourth Quarter of
2004.
The
Parties hereby agree to modify the price of the TASS Services for the
fourth quarter of 2004 set forth in the FWA TASS, which currently is for
the total amount of [*] to the new price of [*] Dollars ([*] United Sates
Dollars). |
|
2.2 |
Service
Credit of US$[*].
Airspan,
for
good and valuable consideration, the receipt and sufficiency of which are
hereby acknowledged,
hereby agrees to reimburse Axtel the amount US$[*] United States Dollars)
of payments made by Axtel in the first three quarters of 2004 for
technical assistance and support services provided by Airspan to Axtel
under the FWA TASS in such period of time. |
|
2.3 |
Amendment
of the Scope of Services under the FWA TASS.
The
Parties hereby agree to amend the scope of services under the FWA TASS, by
replacing in its entirety Annex
“B”
(“Description of the Technical Assistance Support Services”) of the FWA
TASS, with a new annex. The terms and conditions of the new Annex
“B”
are set forth in the document attached as Exhibit
“A” of
this Amendment Agreement No. 3. |
|
2.4 |
New
Prices and Payment Terms for Services under the FWA
TASS.
The
Parties hereby amend the FWA TASS, by modifying the price and payment
terms of the Services set forth in the FWA TASS for the years 2005 and
2006, as follows: |
| (i) |
For
Year 2005.
US$[*], for the Services to be provided by Airspan in year 2005, which
shall be paid by Axtel as follows: |
| · |
US$[*]
for the first calendar quarter, on the last business day of such quarter;
|
| · |
US$[*]
for the second calendar quarter, on the last business day of such
quarter; |
| · |
US$[*]
for the third calendar quarter, on the last business day of such
quarter; |
| · |
US$[*]
for the fourth calendar quarter, on the last business day of such
quarter. |
| · |
Axtel
will issue an Irrevocable Purchase order for the 2005 TASS prior to
15th
January 2005 with the payment terms detailed
above. |
| · |
Airspan
shall deliver to Axtel the respective invoice of such quarter payment, at
least thirty (30) days prior to such payment date (the last business day
of such quarter). |
| (ii) |
For
Year 2006.
US$[*] for the Services to be provided by Airspan in year 2006, which
shall be paid by Axtel as follows: |
| · |
US$[*]
for the first calendar quarter, on the last business day of such quarter;
|
| · |
US$[*]
for the second calendar quarter, on the last business day of such
quarter; |
| · |
US$[*]
for the third calendar quarter, on the last business day of such
quarter; |
| · |
US$[*]
for the fourth calendar quarter, on the last business day of such
quarter. |
| · |
Axtel
will issue an Irrevocable Purchase order for the 2006 TASS prior to
15th
January 2006 with the payment terms detailed
above. |
| · |
Airspan
shall deliver to Axtel the respective invoice of such quarter payment, at
least thirty (30) days prior to such payment date (the last business day
of such quarter). |
|
3. |
CONTINUED
EFFECT.
|
|
3.1 |
The
Parties hereby agree that the present Amendment Agreement No. 3
constitutes an amendment of some of the provisions of the FWA TASS, and
except as amended and modified herein, all of the other terms and
conditions of the FWA TASS shall remain in full force and
effect. |
|
AXTEL, S.A. DE
C.V. |
AIRSPAN COMMUNICATIONS
LIMITED | |
| By:__________________________ | By:__________________________ | |
| Name: Alberto de Villasante Herbert | Name: Peter Aronstam | |
|
Title:
Legal Representative |
Title:
Senior Vice President |
| · |
Provide
remote
troubleshooting
on Airspan
supplied software
and/or hardware |
| · |
Assist
in resolving network fault issues that may be linked to AXTEL’s network
operational procedures and methodologies |
| · |
Assist
AXTEL’s staff in determining fault-locating interface problems between
Airspan hardware or software and other vendors’
equipment |
| · |
Perform
REM software upgrades |
| · |
Remote
Technical Assistance |
| · |
Emergency
Recovery |
| - |
Notwithstanding
Airspan’ determination that on-site support is not necessary, Axtel will
nevertheless have the right to require on site support from Airspan,
provided
that such on site support required by Axtel shall be at Axtel’s cost
unless it is agreed that it was necessary for such support to be provided
on site. |
| · |
Remote
Troubleshooting problems using diagnostic
utilities |
| · |
Providing
advice on how to detect and resolve hardware and network-related
problems |
| · |
Advising
on issues requiring hardware replacement |
| · |
Diagnosing
issues related to Airspan products interfacing with non-Airspan
products |
| · |
Analyzing
trace/log/dump/Operational Measurement (OM)
information |
| · |
Remote
telephone and/or email support to Airspan Second Level support (NTS) in
troubleshooting, diagnosing and correcting failures by Airspan hardware
and/or software to function as per the relevant Airspan product
specifications in Axtel’s network. |
| · |
Providing
regular, on-going updates on case progress using an agreed-upon
medium |
| · |
Service
Restoration and Resolution of the reported cases in accordance with
Section 2.2.3 below of this Exhibit . |
| · |
Confirm
that the products are installed, commissioned, used and maintained by
knowledgeable and skilled people acting in
accordance with
the applicable product documentation from
Airspan |
| · |
Replace
hardware components during diagnosis or as remedial
actions. |
| · |
Generate
performance/availability reports and associated trend
analysis. |
| · |
Gather
data in a timely manner in support of Airspan’ diagnostic process when
reasonably within the technical competency of
AXtel. |
| · |
Identify
issues requiring hardware replacement |
| · |
If
applicable, use all reasonable efforts to maintain hardware and software
at the release or update level for supported hardware and software. This
maintenance will need to be in accordance with policies and procedures
published by Airspan. If Axtel is using a software version released prior
to the then-current minimum supported version(s) and is therefore
unsupported, then Axtel will need to upgrade to one of the then-current
minimum supported versions in order to acquire rights to any known
fix. |
| · |
Perform
software upgrades and/or patch applications, except for REM software
upgrades unless otherwise agreed with
Airspan. |
| · |
Except
for those activities described in Exhibit D of this Agreement, acknowledge
that any hardware / software upgrades / improvements or changes required
to install or use a software fix, update, release, or any part thereof are
charged separately from, and are in addition to, the charges of the
current contract |
| · |
Provide
connectivity in a timely manner to the product(s) for Airspan to establish
a data link for use by Airspan technical support group in order to conduct
remote diagnosis and maintenance |
| · |
Excuse
Airspan from fault resolution for a period equal to such failure or delay,
should Axtel fail or cause delay in providing
connectivity |
| · |
Designate
and make available competent personnel to aid in problem diagnosis and
provide electronic access to the affected product(s) to aid in problem
investigation and resolution for all incidents. For E1/E2 Axtel personnel
should be available to work together with Airspan technical expert
throughout the process. |
| · |
Axtel
should provide their internal escalation process in order to inform all
the contacts to Airspan. |
| · |
Maintain
a support agreement(s) with the third-party supplier(s) for such
product(s), as Axtel sees fit. |
| · |
Axtel’s
in-house structure that performs first-line support will need to exhaust
internal troubleshooting processes. First-level Operations,
Administration, and Maintenance (OA&M) functions may include, but are
not limited to: |
| - |
Performing
day-to-day maintenance and network
operations |
| - |
Monitoring
network and system alarms |
| - |
Performing
diagnosis in accordance with instructions provided by Airspan and carrying
out initial remedial actions, including remote
diagnosis |
| - |
Operating
and controlling Axtel’s internal help desk for logging and tracking fault
inquiries, prioritizing events, and escalating, as required, to the
Airspan technical support group |
| - |
Providing
local time templates and historical actions performed on each event as
reference information to the Airspan technical support group
. |
| · |
The
Technical Support Services program covers all FWA Hardware and Software
(except for Hardware under warranty) installed in Axtel’s network.
|
| · |
Airspan
shall provide an annual product software release designed to enhance the
functionality of the product and when appropriate it will include
solutions to issues raised through the CNR process. The First Market
Application of the annual product software release (including REM software
upgrades) is further described in Exhibit D of this Agreement. The content
of the 2003 annual release is described in Exhibit C to this Agreement.
The content of subsequent years’ releases shall be agreed via the
bi-monthly Product Enhancement Conferences and by the end of September of
the previous year. |
| · |
In
the event that Axtel fails to comply with the requirements described in
section 1.1.3 (Axtel Responsibilities for Technical Support), Airspan will
advise Axtel of its non-compliance. Airspan and Axtel may then agree upon
service to be provided at the then-current time-and-materials basis
published by Airspan plus any travel and living expenses
incurred. |
| · |
Airspan,
or a skilled, qualified third-party authorized by Airspan, will furnish
this service. |
| · |
Airspan
is not responsible for products that have not been installed, commissioned
or upgraded as per the applicable processes and
procedures. |
| · |
Airspan
is not responsible for supporting non-Airspan supplied third-party
product(s). Axtel
will be responsible for maintaining support agreements with the
OEM/third-party supplier for such
product(s). |
| · |
Technical
Support Services do not cover Airspan products not purchased from Airspan
or from a Airspan authorized agent |
| · |
Airspan
will not be obliged to incorporate software corrections into software
releases prior to the then-currently supported software release(s).
Airspan reserves the right to incorporate software corrections into future
software releases |
| · |
Airspan
support obligations are expressly conditional upon the products not being
(i) subject to unusual mechanical stress or unusual electrical or
environmental conditions; (ii) subject to misuse, accident or disaster
including without limitation, fire, flood, water, wind, lightning or other
acts of God; or (iii) altered or modified unless performed or authorized
by Airspan |
| · |
Airspan
Products under Warranty are excluded from this Technical Support Services
Pack. |
| · |
Products
which have not been installed and commissioned by appropriately skilled
and trained personnel using Airspan Procedures are excluded from this
Technical Support Services Pack. |
| · |
Technical
Support Services will not be provided during installation and/or
commissioning process. |
| · |
Airspan
will measure the severity level of hardware or software incidents
according to the following TL9000 Customer Severity classifications for
Critical, Major, and Minor Hardware/Software problem reports. Only if it
is not clear which severity level applies, then the severity level
assigned by Axtel will be used. |
| · |
Airspan
uses case priorities that correspond with the Customer Severity (TL9000)
classifications. Notwithstanding the TL9000 Major Customer Severity
definition, to provide increased focus on certain types of Major problems,
Airspan uses additional case priority definitions: E2, Business Critical,
and Major. |
| · |
Airspan
uses case priorities that correspond to the TL9000 Customer Severities as
shown in the following table: |
|
TL9000
Customer
Severity |
Airspan
Case
Priority |
|
Critical |
E1 |
|
Major |
E2 |
|
Business
Critical | |
|
Major | |
|
Minor |
Minor |
| · |
Airspan
may, where applicable, also provide a customer with the ability to open,
view, and modify cases directly within the Airspan case-tracking system
via .
The customer will bear telecommunication facility charges and/or long
distance toll charges with
access to |
| · |
Where
toll-free +access is not available, the customer will bear
telecommunication facility charges and/or long distance toll charges for
access to the Call Center |
| · |
All
cases are logged into a Airspan case-tracking system. The case is
time-stamped and a case reference number allocated. Furthermore, Airspan
will request that the customer agree to a case priority level
|
| · |
E1
and E2 priority cases are to be reported by telephone
only |
| · |
The
Customer escalation of a case to higher levels of management within
Airspan, shall be in accordance with the following escalation table:
|
|
Axtel’s
NOC |
|||||
|
Call
Center Airspan |
|||||
|
Airspan
Technical Support Engineer |
|||||
|
Airspan
Technical Support Manager. |
|||||
|
Airspan
Technical Support Sr. Mgr. |
|||||
|
Airspan
Technical Support Director |
Airspan
Customer Operation Leader | ||||
| 1. |
Company
name |
| 2. |
Caller
name and phone number |
| 3. |
Personal
Identification Number (PIN) or a unique Customer Purchase Order number or
credit card number, if a PIN has not been
issued. |
| 4. |
Site
Location/Site ID |
| 5. |
Product
on which the problem is being reported |
| 6. |
Problem
description and severity |
| 2.2.2 |
Call
Center Phone Numbers |
|
TL9000
Severity Classification |
Actions |
Response
Times |
Target
Service restoration time |
Resolution
Targets
Based
on RQMS* | |
|
Business
Hours |
Non
- Business Hours | ||||
|
E1
(*1) |
Worked
continuously (7 x 24) until resolution or workaround is
provided |
15
min |
30
min |
7
Hr |
24
hr |
|
E2
(*1) |
Worked
continuously (7 x 24) until resolution or workaround is
provided |
15
min |
30
min |
8
Hr |
10
Days |
|
Business
Critical and Major (*2) |
Worked
during normal business days and business hours. |
2
hrs |
Next
Business
Day |
24
Hr |
30
Days |
|
Minor
(*2) |
Worked
during normal business days and business hours. |
Next
Business Day |
Next
Business Day |
30
Days |
180
days |
|
TL9000
Severity
Classification |
Airspan
Case Priority & Definition |
Examples | ||
|
Critical |
E1 |
» Total
or partial network element outage | ||
|
Problems
that severely affect service, and require or |
» A
reduction in capacity or traffic handling capability such that expected
loads cannot be handled | |||
| day of the week capacity/traffic, billing and |
»
Failure resulting in dynamic routing, switching capability or transport
loss | |||
| maintenance capabilities immediate corrective |
»
Any loss of safety or emergency capability (e.g., emergency calls such as
911 in North America) | |||
| action, regardless of time of day |
»
Loss of the system’s ability to perform automatic system
reconfiguration | |||
|
»
Inability to restart the system | ||||
|
»
Loss of billing/accounting capability | ||||
|
»
Corruption of billing or system databases that requires service affecting
corrective actions |
|
TL9000
Severity Classification |
Airspan
Case Priority & Definition |
Examples | ||
|
Major |
E2 |
»
Loss of redundancy of critical functions | ||
| Problems that result in potential service |
»
Loss of protection switching capability | |||
| degradation and/or total outage. Serious situation not involving service degradation in |
»
Short outages equivalent to system or subsystem outages not seriously
impacting service with accumulated duration of greater than two minutes in any 24-hour period, or that continue to repeat during longer periods | |||
| a live environment, but leading to a total or |
» A
reduction in provisioned capacity of 5% and for a cumulative duration of
more than 10 minutes per 24 hours | |||
| partial loss of redundancy. |
»
Repeated degradation of DS1/E1 or higher rate spans or
connections | |||
|
»
Loss of system’s ability to perform automatic system
reconfiguration | ||||
|
»
Loss of system’s ability to perform automatic system
reconfiguration | ||||
|
»
Loss of access to maintenance or recovery
operations | ||||
|
»
Any loss of functional visibility and/or diagnostic
capability | ||||
|
»
Loss of system’s ability to provide any required system critical/major
alarms | ||||
| » Total loss of access to provisioning |
|
TL9000
Severity Classification |
Airspan
Case Priority & Definition |
Examples | ||
|
Major |
Business
Critical |
»
The customer has been given a work-around but the situation still requires
constant attention due to the temporary nature of the work-around | ||
|
Problems
that result in a major degradation of system or service |
»
Software application/migration issues that gate the introduction of new
services or functionality | |||
| performance that impacts service quality or significantly impairs |
»
Billing error rates that exceed specifications | |||
| network operator control or operational effectiveness. Overall network | » Corruption of system or billing databases | |||
| is degraded resulting in severe limitations to operations or network management software product has major feature that is not working properly with only difficult workaround. |
|
TL9000
Severity Classification |
Airspan
Case Priority & Definition |
Examples | ||
|
Major |
Major |
»
Degradation of any capacity/traffic measurement function; degradation of
functional visibility and/or diagnostic capability | ||
|
Problems
that result in conditions that seriously |
»
Degradation of access for maintenance or recovery
operations | |||
| affect system operation, maintenance and |
»
Degradation of the system’s ability to provide any required system
critical/major alarms | |||
| administration, etc. and require immediate |
»
Loss of access for routine administrative
activity | |||
| attention. The urgency is less than in a |
»
Any system failure without direct immediate
impact | |||
| Business Critical situation because of a lesser |
»
Intermittent degradation of services; partial loss of access to
provisioning | |||
| immediate or impending effect on system |
»
Software application/migration issues that do not impact
service | |||
| performance, customers, and the customer’s |
»
Reduction in any capacity/traffic measurement
function | |||
| operation and revenue. |
»
Any loss of functional visibility and/or diagnostic
capability | |||
|
»
Any significant increase in product-related customer trouble
reports | ||||
|
»
Follow-up to E1 customer problems | ||||
|
»
Other problems that disrupt or prevent routine system activities, or
problems that are jointly viewed as Major events by Airspan and the customer |
|
TL9000
Severity Classification |
Airspan
Case Priority & Definition |
Examples | ||
|
Minor |
Minor |
»
Service analysis, recorded announcements, operational measurements,
maintenance program, or network management problems; or system-related documentation inaccuracies, that do not affect call processing | ||
|
Problems
do not significantly impair the |
»
Test equipment failures for which a backup or manual alternative can be
employed | |||
| functioning of the system and do not | » Circuit pack testing problems | |||
| significantly affect service to customers. These problems are tolerable during system use. |
|
Status |
Description |
Airspan
Clock | ||
Newly
Opened |
This
status is the default. It signifies that no work has been done on the
case. |
Start | ||
WIP
Level 1 |
This
status is used when a NTS Engineer is actively working on the
Case. |
Not
Stopped | ||
WIP
Level 2 |
This
status is used when a Second Level Support Engineer is actively working a
case
*
Second Level Support: Software Support, Product Support. |
Not
Stopped | ||
Escalated
To Design |
This
status is used when a Design Engineer is actively working on the
case |
Not
Stopped | ||
Answer
From Design |
Design
Engineer has concluded its investigation and has replied back to the NTS
Engineer |
Not
Stopped | ||
With
A Customer |
During
the course of conducting their research, the NTS Engineer may need
additional information or activity from the Customer. The "With a
Customer” status is assigned when the NTS Engineer is waiting on a
Customer response in order to continue investigation |
Stopped |
|
Status |
Description |
Airspan
Clock | ||
Interim
Solution |
If
a temporary solution is provided that eliminates the customers pain until
a permanent solution can be delivered, RQMS requirements allow the case to
be set to an “IS” status during this window of time if approved by the
Customer. In calculating case age, this interval will be discounted if the
permanent fix was delivered on the negotiated commitment date. If the
permanent fix does not resolve the reported problem, case status shall be
changed to Work in Progress (Level 1 or 2). If the case is returned to a
Work in Progress (Level 1 or 2) status after using the IS, the IS time
period will be added to the RQMS age of the case. |
Stopped | ||
Future
Deliverable |
Customer
agrees to live with the problem condition and that the fix will be
delivered as part of a future Airspan product release (software release,
maintenance release, documentation release or hardware revision.
Requirements to use this status include Customer consent; fix
identification, and delivery commitment. This status code does not add
time to the RQMS age of the case unless the solution fails and the case is
moved back to Work in Progress (Level 1 or 2) status. If the case is
returned to a Work in Progress (Level 1 or 2) status after using the FD,
the FD time period will be added to the RQMS age of the
case. |
Stopped | ||
Solution
Delivered |
Solution
Delivered or available for testing and verification. If the delivered
solution does not resolve the reported problem, the status will be changed
to Work in Progress (Level 1 or 2). If the case is returned to a Work in
Progress (Level 1 or 2) status after using the SD status, the SD time
period will be added to the RQMS age of the case. |
Stopped | ||
Pending
OEM Vendor |
The
case has been handed over to an OEM Vendor for resolution |
Not
Stopped |
| · |
Cannot
Reproduce:
After 60 days and a reasonable effort, a problem has not been observed in
the Network, is not reproducible or sufficient information has not been
provided to adequately troubleshoot the problem and isolate the root
cause |
| · |
Customer
Process:
Human errors are present or the customer has failed to follow procedures
recommended and documented by Airspan |
| · |
Design
Intent:
The functionality required by customer does not align with the design
specifications of the product set forth in Agreement, in which case
Airspan shall make clear to Axtel which is such design specification
(i.e., the functionality is unsupported), and the issue can only be
resolved through new development efforts subject to a separate product
development agreement and charges. |
| · |
External
Cause:
Issue caused by non-Airspan products |
| · |
Hardware
Deficiency: A
problem is isolated to defective
hardware materials or workmanship or substantial nonconformance to
specifications published by Airspan |
| · |
Hardware
Failure: A
problem is caused by a hardware component failure that falls within Mean
Time Between Failure (MTBF) limitations |
| · |
Airspan
Literature:
Required Airspan technical document does not exist or the contents of an
existing document are in error [for example, an incomplete Airspan
Technical Publication (NTP)] |
| · |
Airspan
Process: A
problem occurs as a result of a Airspan process
deficiency |
| · |
Opened
in Error:
The case should not have been opened |
| · |
Scheduled
Event:
An outage occurs resulting from planned maintenance, installation, or
manual initialization, including such activities as parameter loads,
software/firmware changes, and other OA&M
activities |
| · |
Software
Deficiency: A
problem is isolated to a software design deficiency.
|
| 2.3 |
Airspan
Conditions for Services Provided Outside of the Scope of this Technical
Support Services Pack |
| · |
Support
is needed for efforts not covered under a contract support program (such
as the one proposed herein) |
| · |
On-site
visits to a customer’s system sites, when the visit is at the request of
the customer but is not deemed necessary by Airspan. This includes site
visits requested by the customer for support when resolution could have
otherwise been achieved from a remote location. This is subject to the
terms set forth in Section 1.1 above. |
| · |
Requests
to investigate issues pertaining to software features that are either
outside the functionality as defined in the Airspan Technical Publications
(NTPs) or are outside standards supported by
Airspan |
| · |
Assistance
in set-up and usage of Operational Measurements
(OMs) |
| · |
System
performance assessment |
| · |
Training
on product hardware maintenance |
| · |
Training
on general office operations/maintenance
procedures |
| · |
Training
on test equipment and troubleshooting
procedures |
| 2.3.1 |
Per-Occurrence
Repair Services |
|
Ref |
Part
Number |
Description |
Quantities |
|
1 |
NTEG72AD |
TBM |
16 |
|
2 |
NTEG77EC |
TMU |
16 |
|
3 |
NTED4575 |
TPM |
8 |
|
4 |
NTEG63AA |
TTM |
8 |
|
5 |
NTEG73AA |
NMM |
4 |
|
6 |
NTEG74BA |
OVPM |
12 |
|
7 |
NTEG71HA |
TPM-PD |
12 |
| · |
Pay
the expense of shipping a defective FRU to Airspan’s warehouse or logistic
center defined for this purposes. |
| · |
Use
the specifically-assigned part request number(s) provided by Airspan and
include completed Airspan Fault Report Forms when returning any
FRU |
| · |
Adhere
to Airspan’ packing instructions (including anti-static precautions) when
returning the defective unit. The packing instructions will be included
with the return instructions accompanying the replacement
FRU |
| · |
Put
the replacement FRU into service once it has been returned by Airspan to
Axtel. |
| · |
As
a separate and additional charge, each Base Station item returned for
repair will be charged individually. Invoicing at the beginning of each
month for units delivered to Airspan for repair during the previous
month. |
| · |
The
Individual Base Station element return & repair included
are: |
| - |
TPM
|
| - |
TTM
|
| - |
TBM
|
| - |
NMM
|
| - |
TMU
|
| - |
OVPM |
| · |
As
a separate and additional charge, an RTU Repair & Return service will
be offered through one of two options. Axtel will elect one of these two
options by the Closing Date for the year 2003 and by December
15th of
the prior year for each year thereafter. Both options are detailed in the
Price Summary (Exhibit “A”). |
| · |
Airspan
repair cases resulting in “no fault found” to be charged at 50 % of the
Airspan’ full repair rates. Axtel will pay the handling fee of units
determined by Airspan to be beyond economic repair. Return and repair
turnaround time shall be 60 days. |
| · |
Airspan
will not provide a hardware emergency replacement
service. |
| 2.3.2 |
Axtel
Order Process for FWA Repair
Services |
| 1. |
Customer
or distributor name |
| 2. |
Customer
ID (Project #, Site ID) |
| 3. |
Requestor
name, phone and fax number, and e-mail
address |
| 4. |
Customer
ship to address |
| 5. |
Part
number (PEC or CPC or manufacturer’s part
number) |
| 6. |
Quantity
(quantity of one per serial number) |
| 7. |
Serial
number of the defective part(s) being returned (if
applicable) |
| 8. |
Warranty
status |
| 9. |
Confirmation
of the availability of a fully completed Airspan fault report form for
said product. |
| 10. |
Any
additional information about product (system type or software
release) |
| 11. |
Any
special shipping instructions |
| 1. |
From
(Company name, return address, and telephone
number) |
| 2. |
Ship
Date (Date parts are shipped from the
customer) |
| 3. |
Ship
via (Carrier or Enterprise name) |
| 4. |
Waybill
number (Carrier or Enterprise tracking
number |
| 5. |
Number
of Cartons (Number of cartons being sent on
shipment) |
| 6. |
Customer’s
PO# (Provided, if applicable) |
| 7. |
Repair
order number (RMA# issued by Call Center when order is
placed) |
| 8. |
Site
ID or Project number |
| 9. |
Item
Number |
| 10. |
Quantity
ordered |
| 11. |
Quantity
returned |
| 12. |
Airspan
Part number |
| 13. |
Description
of item |
| 14. |
Serial
number (The serial number for each item in the
shipment) |
| 15. |
Shipment
requested by (Signature of the customer’s
representative) |