Document:

<PAGE>   1
                                                                   EXHIBIT 10.11

                         SOFTWARE DEVELOPMENT AGREEMENT

        Effective February 20, 2000, Trigon Technology Group ("Developer") and
ANDA Networks (the "Company") agree to the following terms and conditions for
the development by Developer for ANDA of the UAP 2000 China [***]* and the UAP
2000 China [***]* (collectively the "Services"). The parties intend for ANDA to
be able to embed the [***]* into and bundle the [***]* with the Company's UAP
2000 family of products to provide a network management interface for the UAP
2000 family of products in China.

        1. Development.

               a. China [***]*. Developer agrees to use diligent efforts to
develop the UAP 2000 China [***]* (as defined in Exhibit A) (the "[***]*") based
on Developer's [***]* code-named "OM2000" (the "[***]*) in accordance with the
specifications and pursuant to the schedule specified in the Statement of Work
(the "SOW").

               b. [***]*. Developer agrees to use diligent efforts to develop
the UAP 2000 China [***]* (as defined in Exhibit A) (the "[***]*") in accordance
with the specifications and pursuant to the schedule specified in the Statement
of Work (the "SOW").

               c. Statement of Work. Developer agrees to use diligent efforts to
develop the SOW that shall describe in detail the development, specifications
and implementation of the [***]* and the [***]*. The SOW shall also contain a
description of all items to be delivered to Company by Developer (each a
"Deliverable") and a time schedule for such Deliverables. The SOW shall be
considered the first Deliverable, and upon acceptance of the SOW by ANDA, it
shall be attached hereto as Exhibit B. Developer shall proceed with the
development of the [***]* and the [***]* upon ANDA's acceptance of the SOW.

               d. Company's Development Obligation. The Company shall endeavor
to timely provide Developer with the items and assistance specified in
applicable SOW.

        2. Changes. Developer agrees to accept any reasonable change to the
applicable SOW proposed by the Company. In the event that Company proposes a
change, Developer shall provide Company an estimate of the cost to Developer of
making such change.

        3. Milestones, Acceptance. When Developer believes it has completed a
Deliverable (as defined in the SOW), Developer will deliver it to the Company.
The Company will accept or reject the Deliverable within ten (10) days after
delivery.

If the Company rejects the Deliverable, Developer will promptly correct the
failures in any rejected Deliverable. When it has made the necessary
corrections, Developer will again deliver the Deliverable to the Company and the
acceptance/rejection/correction provisions above shall

------------------------

        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       1

<PAGE>   2
be reapplied until the Deliverable is accepted; provided, however, that upon the
third or any subsequent rejection or if the corrections are not made within
twenty (20) days of the initial rejection, Company may terminate this Agreement
by fifteen (15) days written notice unless the Deliverable is accepted during
the notice period.

        4. Payment. Developer shall bill Company on a time and materials basis
for the Services. Developer estimates that the total cost to Company for the
Services will not exceed $[***]*. The Company shall make payments to Developer
within thirty (30) days of invoice by Developer. Each payment will be made in
U.S. dollars, except at Company's option, up to fifty percent (50%) of each
invoice may be paid in Chinese RMB at the then effective exchange rate.

        5. Ownership.

               a. [***]*. [***]* shall retain [***]* its [***]*, [***]* and
[***]* in its [***]* in the [***]* developed by Developer under this Agreement.
"[***]*" shall mean all [***]*, [***]*, [***]*, [***]* and all other [***]*
throughout the [***]*.

               b. [***]*. Company shall own all right, title and interest in the
[***]* including all Intellectual Property Rights in the [***]*, and Developer
hereby makes all assignments necessary to accomplish the foregoing ownership.
Developer shall further assist Company, at Company's expense, to further
evidence, record and perfect such assignments, and to perfect, obtain, maintain,
enforce, and defend any rights assigned. Developer hereby irrevocably designates
and appoints Company as its agents and attorneys-in-fact to act for and in
Developer's behalf to execute and file any document and to do all other lawfully
permitted acts to further the foregoing with the same legal force and effect as
if executed by Consultant. If any part of the [***]* is based on, incorporates,
or is an improvement or derivative of, or cannot be reasonably and fully made,
used, reproduced, and otherwise exploited without using or violating technology
or Intellectual Property Rights owned or licensed by Developer and not assigned
hereunder, Developer hereby grants Company a perpetual, irrevocable, worldwide
royalty-free, non-exclusive, sublicensable right and license to exploit and
exercise all such technology and Intellectual Property Rights in support of
Company's exploitation of the [***]*.

        6. License. Developer hereby grants to Company, subject to the royalty
payments set forth in the SOW, the following license rights:

               a. a perpetual, irrevocable, nonexclusive, nonsublicenseable
worldwide license to use, copy, modify, and prepare derivative works of the
[***]* source codes, solely for Company's internal business purposes and to
support the UAP 2000 family of products;

               b. a perpetual, irrevocable, nonexclusive, worldwide license to
copy, use, modify, prepare derivative works of, sublicense, and distribute, as
bundled with the UAP 2000 family of products, the [***]* object code and
derivative works thereof.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       2

<PAGE>   3
Any license of copyright hereunder includes all rights of paternity, integrity,
disclosure and withdrawal and any other rights that may be known as or referred
to as "moral rights" (collectively "Moral Rights"). To the extent such Moral
Rights cannot be licensed under applicable law and to the extent the following
is allowed by the laws in the various countries where Moral Rights exist, the
party granting the license hereby ratifies and consents to any action consistent
with the terms of this Agreement that would violate such Moral Rights in the
absence of such ratification/consent. The party granting the license will
confirm any such ratifications and consents from time to time as requested by
the other party.

In the event Developer licenses the [***]* to any third party, and the terms of
such license are more favorable than those between Developer and Company,
Developer agrees to amend such license terms with Company, to ensure that
Company receives terms that are at least as favorable as those provided to any
third party licensee.

        7. Confidentiality. Each party agrees that all code, inventions,
algorithms, know-how and ideas and all other business, technical and financial
information they obtain from the other are the confidential property of the
disclosing party ("Proprietary Information" of the disclosing party). Except as
expressly and unambiguously allowed herein, the receiving party will hold in
confidence and not use or disclose any Proprietary Information of the disclosing
party and shall similarly bind its employees in writing. The receiving party
shall not be obligated under this Section 6 with respect to information the
receiving party can document:

               a. is or has become readily publicly available without
restriction through no fault of the receiving party or its employees or agents;
or

                      (1) is received without restriction from a third party
lawfully in possession of such information and lawfully empowered to disclose
such information; or

                      (2) was rightfully in the possession of the receiving
party without restriction prior to its disclosure by the other party; or

                      (3) was independently developed by employees or
consultants of the receiving party without access to such Proprietary
Information.

        8. Limited Liability.

               a. NOTWITHSTANDING ANYTHING ELSE IN THIS AGREEMENT OR OTHERWISE
AND EXCEPT UNDER THE INDEMNITY AND CONFIDENTIALITY PROVISIONS HEREIN, NEITHER
PARTY SHALL BE LIABLE OR OBLIGATED UNDER ANY SECTION OF THIS AGREEMENT OR UNDER
ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY
(I) FOR ANY AMOUNTS IN EXCESS IN THE AGGREGATE OF THE FEES PAID BY COMPANY TO
DEVELOPER HEREUNDER OR (II) FOR ANY COST OF PROCUREMENT OF

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       3

<PAGE>   4
SUBSTITUTE GOODS, TECHNOLOGY, SERVICES OR RIGHTS OR (III) FOR LOSS OR CORRUPTION
OF DATA OR INTERRUPTED USE.

               b. EXCEPT UNDER SECTION 7, NEITHER PARTY SHALL BE LIABLE WITH
RESPECT TO ANY SUBJECT MATTER OF THIS AGREEMENT UNDER ANY CONTRACT, NEGLIGENCE,
STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY FOR ANY INCIDENTAL OR
CONSEQUENTIAL DAMAGES.

               c. Sections 8.a and 8.b will not limit liability for bodily
injury of a person.

        9. Export Control. Each party shall comply with all applicable export
laws, restrictions, and regulations of any United States or foreign agency or
authority and will not export or re-export, or authorize the export or re-export
of any product, technology or information it obtains or learns pursuant to this
Agreement (or any direct product thereof) in violation of any such laws,
restrictions or regulations.

        10. Warranties and Disclaimer.

               a. Developer represents and warrants to the Company that: (i)
Developer has not assigned, transferred, licensed, pledged or otherwise
encumbered the [***]* or [***]* or underlying technology or intellectual
property rights with respect thereto in a manner inconsistent with the terms of
this Agreement or agreed to do so, (ii) Developer has full power and authority
to enter into and perform this Agreement, (iii) Developer is not aware of any
actual or potential violation, infringement or misappropriation of any third
party's rights (or any claim or potential claim thereof) by the [***]* or [***]*
(or inherent in the development, use or production thereof), (iv) neither
Developer's entering nor performing this Agreement will violate any right of or
breach any obligation to any third party under any agreement or arrangement
between Developer and such third party, (v) to the best of the Developer's
knowledge, no licenses, permissions or releases of third party rights are
necessary for Developer's development of or Company's production or distribution
of the [***]* or [***]* in accordance with the terms of this Agreement, (vi) all
copyrightable matter licensed or assigned hereunder has been or will be created
after the effective date of this Agreement by persons who were employees of the
Developer at the time of creation and no third party has or will have "moral
rights" or rights to terminate any assignment or license with respect thereto,
(vii) the work under this Agreement will be performed in a professional and
workman-like manner and shall conform to the specifications set forth in the
applicable SOW; (viii) Developer has and will obtain agreements with its
employees and contractors sufficient to allow it to provide Company with the
assignments and licenses provided for herein.

               b. Company represents and warrants that (i) it has the right,
power and authority to enter into this Agreement and to fully perform its
obligations under this Agreement and (ii) the making of this Agreement by it
does not violate any agreement existing between it and any other party.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       4

<PAGE>   5
               c. EXCEPT FOR THE WARRANTY MADE HEREIN, DEVELOPER AND COMPANY
MAKE NO WARRANTIES TO ANY PERSON OR ENTITY WITH RESPECT TO THE [***]* OR [***]*,
ANY DELIVERABLE OR ANY SERVICES OR LICENSES AND DISCLAIM ALL IMPLIED WARRANTIES,
INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. DEVELOPER AND COMPANY MAKE NO WARRANTY REGARDING FREEDOM
FROM BUGS OR UNINTERRUPTED USE.

        11. Indemnity. Developer agrees to, and shall, indemnify, defend and
hold harmless the Company, its affiliates and their respective directors,
shareholders, officers, agents, employees, successors and assigns from and
against any and all claims, suits, damages, costs, expenses (including
reasonable attorneys' fees and expenses) and other liabilities arising from, in
connection with or related in any way to, directly or indirectly, (a) any breach
of any of the representations or warranties made by it under this Agreement; (b)
any negligent act or omission of it, its directors, officers, agents, employees
or subcontractors; or (c) any claim that anything Developer provides to Company
pursuant to this Agreement infringes any third party Intellectual Property
Right. Company shall promptly notify Developer of any such claim.

        12. Termination.

               a. If either party should materially breach a material provision
of this Agreement, the other party may terminate this Agreement upon thirty (30)
days' notice unless the breach is cured within the notice period or, if the
breach cannot reasonably be so cured, diligent efforts to effect such cure are
commenced during that period and are continued until the cure is completed,
which shall be within a reasonable time.

               b. Sections 5 through 15 of this Agreement, any accrued rights to
payment and any remedies for breach of this Agreement shall survive termination.

               c. This Agreement will remain in effect until the [***]* and or
the [***]* are completed by Developer and accepted by Company, or until this
Agreement is terminated in accordance with the express terms of this Agreement.

        13. Publicity and Press Releases. Except to the extent necessary under
applicable laws, the parties agree that no press releases or other publicity
relating to the substance of the matters contained herein will be made without
joint approval.

        14. Relationship of the Parties. Notwithstanding any provision hereof,
for all purposes of this Agreement each party shall be and act as an independent
contractor and not as partner, joint venturer, or agent of the other and shall
not bind nor attempt to bind the other to any contract.

        15. Assignment. Neither party shall have any right or ability to assign,
transfer, or sublicense any obligations or benefit under this Agreement without
the written consent of the

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       5

<PAGE>   6
other (and any purported assignment will be void), except that a party may
assign and transfer this Agreement and its rights and obligations hereunder to
any third party who succeeds to substantially all its business or assets.

        16. Notice. All notices under this Agreement shall be in writing, and
shall be deemed given when personally delivered or three days after being sent
by prepaid certified or registered U.S. mail to the address of the party to be
noticed as set forth herein or such other address as such party last provided to
the other by written notice.

        17. Miscellaneous.

               a. The failure of either party to enforce its rights under this
Agreement at any time for any period shall not be construed as a waiver of such
rights.

               b. No changes or modifications or waivers are to be made to this
Agreement unless evidenced in writing and signed for and on behalf of both
parties.

               c. In the event that any provision of this Agreement shall be
determined to be illegal or unenforceable, that provision will be limited or
eliminated to the minimum extent necessary so that this Agreement shall
otherwise remain in full force and effect and enforceable.

               d. This Agreement shall be governed by and construed in
accordance with the laws of the State of California and the United States
without regard to the conflicts of laws provisions thereof. The sole
jurisdiction and venue for actions related to the subject matter hereof shall be
the state and U.S. federal courts located in Santa Clara County, California.
Both parties consent to the jurisdiction of such courts and agree that process
may be served in the manner provided herein for giving of notices or otherwise
as allowed by California state or U.S. federal law. Headings herein are for
convenience of reference only and shall in no way affect interpretation of the
Agreement.

               e. The rights and remedies of a party set forth herein with
respect to failure of the other to comply with the terms of this Agreement
(including, without limitation, rights of full termination of this Agreement)
are not exclusive, the exercise thereof shall not constitute an election of
remedies and the aggrieved party shall in all events be entitled to seek
whatever additional remedies may be available in law or in equity.

               f. No liability or loss of rights hereunder shall result to
either party from delay or failure in performance (other than payment) caused by
force majeure including, without limitation, acts of God, fire, flood, war,
government action, compliance with laws or regulations, strikes, lockouts or
other serious labor disputes, or shortage of or inability to obtain material or
equipment.

               g. This Agreement supersedes all proposals or prior agreements,
oral or written, and all other communications between the parties relating to
the subject matter hereof. If any of the terms of this Agreement conflict with
terms of the SOW, the terms of this Agreement shall govern.

                                       6

<PAGE>   7
               h. Each party recognizes and agrees that the warranty disclaimers
and liability and remedy limitations in this Agreement are material bargained
for bases of this Agreement and that they have been taken into account and
reflected in determining the consideration to be given by each party under this
Agreement and in the decision by each party to enter into this Agreement.

               i. The parties recognize and agree that "TIME IS OF THE ESSENCE"
with respect to completion, delivery and correction of development hereunder.

TRIGON TECHNOLOGY GROUP         ANDA NETWORKS

By                              By
                                   ----------------------------------------

Title:                          Title:
                                       ------------------------------------

Address:                        Address:
                                         ----------------------------------

                                         ----------------------------------

                                       7

<PAGE>   8
                                    EXHIBIT A

1)      UAP 2000 CHINA [***]* - This software implements the network management
        agent, which is embedded in the UAP 2000 device for providing an
        external [***]* interface. The [***]* is more fully described in the
        SOW.

2)      UAP 2000 CHINA [***]* - This software implements the [***]* for the ANDA
        UAP 2000 product. It will be a stand-alone [***]* based system operating
        external to the UAP 2000 device. The [***]* is more fully described in
        the SOW.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       8

<PAGE>   9
                                    EXHIBIT B

                            STATEMENT OF WORK ("SOW")

                                       9

<PAGE>   10
                              ANDA NETWORKS UAP V5

                                [***]* & [***]*

                                STATEMENT OF WORK

                                   VERSION 1.2

                                   FEB 3, 2000

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

<PAGE>   11
RELATED PUBLICATIONS

<PAGE>   12
                                TABLE OF CONTENTS

<TABLE>
<S>                                                                                         <C>
0.  Preface..................................................................................1
        a.  Document Structure...............................................................1
        a.  Preface..........................................................................1
        b.  Document Version History.........................................................1
        c.  Acronyms.........................................................................1

PART I - INTRODUCTION........................................................................2

1.  Introduction.............................................................................3

2.  Pricing..................................................................................4

PART II - [***]*.............................................................................5

0.  Preface..................................................................................6
        a.  Document Structure...............................................................6
        b.  Document Version History.........................................................6
        c.  Acronyms.........................................................................6

1.  Introduction.............................................................................7
        a  General System Description........................................................7
           i.  General Operation.............................................................7

2.  Proposed Architecture...................................................................10
        a.  Design Philosophy...............................................................10
        b.  Overview........................................................................10
           i.  System Requirements..........................................................10
           ii.  Functional Modules..........................................................11
           iii.  Advantages.................................................................12
           iv.  System Reliability..........................................................12
           v.  Extensibility and Growth.....................................................12

3.  Functional Requirements.................................................................13
        a  Development Environment..........................................................13
           i.  Hardware.....................................................................13
           ii.  Software....................................................................13
        b.  Anda's Interface................................................................13
        c. [***]*  Interface Module.........................................................13
        d.  Configuration Module............................................................14
</TABLE>

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       i

<PAGE>   13
<TABLE>
<S>                                                                                         <C>
        e.  Performance Module..............................................................15
        f.  Fault Module....................................................................15
        g.  Audit Trail Module..............................................................15
        h.  Database Interface..............................................................15
        i.  Logger Module...................................................................16

4.  Project Activities......................................................................17
        a.  Requirements Analysis...........................................................17
        b   Requirements Review.............................................................17
        c.  Design..........................................................................17
        d.  Design Review...................................................................18
        e   Implementation and Unit Testing.................................................18
        f.  Integration with UAP............................................................18
        g.  Test Plan.......................................................................18
        h.  System Test.....................................................................18

5.  Project Schedule........................................................................19

6.  Assumptions.............................................................................20

PART III - UAP 1000 [***]*..................................................................21

0.  Preface.................................................................................22
        a.  Document Structure..............................................................22
        b.  Document Version History........................................................22
        c.  Acronyms........................................................................22

1.  Introduction............................................................................23
        a.  General System Description......................................................23
           i.  General Operation............................................................23

2.  Proposed Architecture...................................................................27
        a.  Design Philosophy...............................................................27
        b.  Overview........................................................................27
           i.   System Requirements.........................................................28
           ii.  Functional Modules..........................................................28
           iii. Advantages..................................................................29
           iv.  System Reliability..........................................................29
           v.   Extensibility and Growth....................................................29

3.  Functional Requirements.................................................................30
        a.  Development Environment.........................................................30
           i.  Hardware.....................................................................30
</TABLE>

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       ii

<PAGE>   14
<TABLE>
<S>                                                                                         <C>
           ii.  Software....................................................................30
        b.  Anda's Interface................................................................30
        c. [***]*...........................................................................30
           i.  High Level View of [***]*....................................................31
        c. [***]* specification.............................................................32
        d. [***]* Gateway...................................................................32
           i.  [***]*  Access Interface.....................................................32
           ii.  Security Administration.....................................................32
           iii.  Performance Monitoring.....................................................33
           iv.  Logger......................................................................33
           v.  Database Module..............................................................33
           vi.  Report Generation...........................................................33

4.  Project Activities......................................................................34
        a.  Requirements Analysis...........................................................34
        b.  Requirements Review.............................................................34
        c.  Design..........................................................................34
        d.  Design Review...................................................................35
        e.  Implementation and Unit Testing.................................................35
        f.  Test Plan.......................................................................35
        g.  System Test.....................................................................35
        h.  Onsite Integration..............................................................35

5.  Project Schedule........................................................................36

6.  Assumptions.............................................................................37
</TABLE>

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       iii

<PAGE>   15
LIST OF FIGURES

<TABLE>
<S>                                                                                         <C>
Figure  1.  [***]* Architecture.............................................................10
Figure  2.  [***]* Architecture.............................................................28
Figure  3.  High Level View of [***]*.......................................................31
</TABLE>

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       iv

<PAGE>   16
0.      Preface

This section describes the organization, version history, acronyms used within
the document.

a.      Document Structure

This document is organized into sections as defined below:

<TABLE>
<S>                 <C>
        Preface     This section describes the document structure, conventions, and

        Part I      Introduction - This section describes the purpose of the document.

        Part II     [***]* - This part describes the statement of work for
                    the UAP 1000 [***]*.

        Part III    [***]* - This part describes the statement of work for
                    the UAP 1000 [***]*.
</TABLE>

b.      Document Version History

c.      Acronyms

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

<PAGE>   17
                              PART I - INTRODUCTION

                                       2

<PAGE>   18
1.      INTRODUCTION

        This document describes the TTG statement of work, for the development
of the following network management systems, for the management of the ANDA
Networks UAP 1000 product line ("UAP 1000" is used in the rest of this document
to refer to the UAP 1000 product line).

1.      UAP 1000 [***]* - This software implements the [***]* , which is
        embedded in the UAP 1000 device for providing an external [***]* based
        management interface. Part II of this document provides a detailed
        description of the [***]* and the associated delivery and pricing
        schedules.

2.      UAP 1000 [***]* - This software implements the [***]* for the ANDA UAP
        1000 product. It will be a stand-alone [***]* based system operating
        external to the UAP 1000 device. Part III of this document provides a
        detailed description of the [***]* and the associated delivery and
        pricing schedules.

        This proposal provides ANDA Networks the flexibility to have independent
development schedule for the two interfaces. The schedule for the [***]* will be
as described in this proposal. The schedule for [***]* will be decided at a
later date. The break down of the [***]* development given in this proposal is
for reference only. The dates of delivery for various items in the [***]* will
be adjusted depending on the start date chosen in the future.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       3

<PAGE>   19
2.      PRICING

        The total price for the development of the [***]* and the [***]* will
include NRE and royalties. The NRE is stated in the contract . The royalty
schedule is stated in this section.

        All pre-approved travel and living expenses incurred for the development
and delivery of above two interfaces will be billed to ANDA Networks at cost.

        ROYALTIES

        In addition to the development of the [***]* and [***]*, Trigon will
license to Anda its OM2000 [***]*. Anda will use the [***]* and commit
engineering resources to adapt the [***]* to work with Anda's [***]*, as
outlined in the Statement of Work for the [***]*.

        For each system shipped by Anda ,or Anda's OEMs, with one or more copies
or licenses of the [***]* or one or more copies of the [***]* ("[***]*") derived
from Trigon's [***]*, Anda will pay a royalty to Trigon, according to the
following declining royalty schedule:

<TABLE>
<CAPTION>
System no.         [***]* per copy fee  [***]* per copy fee
----------         -------------------  -------------------
<S>                <C>                  <C>
1 - 50                 $[***]*               $[***]*
51 - 100               $[***]*               $[***]*
101 - 500              $[***]*               $[***]*
501 - 1000             $[***]*               $[***]*
1001 - 2000            $[***]*               $[***]*
2001 - 5000            $[***]*               $[***]*
5001 - 10000           $[***]*               $[***]*
</TABLE>

The royalty schedule is confidential information between Anda and Trigon.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       4

<PAGE>   20
                                PART II - [***]*

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       5

<PAGE>   21
0.      Preface

This section describes the organization, version history, acronyms used within
the document.

a.      Document Structure

This part of the document is organized into sections as defined below:

<TABLE>
<S>                   <C>
        PREFACE       This section describes the document structure,
                      conventions, and references used to develop this document.

        SECTION 1     Introduction

        SECTION 2     Proposed Architecture - This section describes the
                      architecture being proposed for the project.

        SECTION 3     Functional Requirements - This section briefly outlines work involved
                      in the project.

        SECTION 4     Project Activities - This section describes the
                      different phases in the implementation of the project.

        SECTION 5     Project Schedule - This section lists implementation time of each
                      component.

        SECTION 6     Assumptions - This sections lists the assumptions made in this proposal.

        SECTION 7     Pricing - This section provides the pricing for the
                      implementation of the project.
</TABLE>

b.      Document Version History

c.      Acronyms

                                       6

<PAGE>   22
1.      Introduction

        This document provides a statement of work for the development of [***]*
to be embedded into the ANDA Networks UAP 1000 product. The purpose of this
document is to identify

-   the scope of project

-   the work involved in the implementation of the [***]*

-   Time Estimates and

-   Pricing

        Providing a [***]* Interface to ANDA UAP product is a joint effort
between ANDA and TTG. This document mainly focuses on the responsibilities of
TTG with a few references to the responsibilities of ANDA.

        The remaining part of this section provides a general description of the
[***]* solution that will be developed for Anda by TTG.

a.      General System Description

        [***]* provides a [***]* based network management interface to the UAP
1000. [***]* Systems developed by customers of ANDA Networks can interact with
UAP 1000 product using [***]*. This will provide high degree of flexibility for
developers of network management systems and also provide ANDA the advantage of
having a leading edge network management interface. The purpose of the [***]* is
to manage V5 interface for international market offered by the UAP 1000 product.
The [***]* will be developed using the TTG OM2000 Product ([***]*).

        The remainder of this section outlines various major components and
functions provided by the [***]*. More detailed description is provided in the
following sections of the documents.

i.      General Operation

(1)     System

                [***]* will be embedded into the UAP 1000 product and can be
                accessed using the services offered by any [***]* platform.
                [***]* will come up as part of the general start up sequence of
                the UAP 1000. [***]* supported by the UAP 1000 can be
                distributed to customers of ANDA Networks.

(2)     [***]*

                The [***]* does not have any [***]*.

(3)     Software Updates

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       7

<PAGE>   23
               The software should be designed so that individual objects
               (functions) may be added into the system without the need for a
               complete replacement of the platform software, or re-
               installation. It is desirable to allow software to be added to
               the system without a system-wide outage.

(4)     Security

               The [***]* will provide [***]* authentication.

(5)     System Administration

               [***]* will provide API for integration with ANDA local craft
               interface for the purpose of administration of the [***]*.
               Administration will include configuration of tracing, logging,
               usage of threads, semaphores, database etc.

(6)     Database

               The [***]* will have a build-in database for persistency. API
               will also be provided for different modules in the UAP to access
               information stored in the [***]* database.

(7)     Audit Trail

               The [***]* will store information about all operations performed
               for the purposes of audit. The [***]* shall provide hooks for the
               purpose of routing the audit trail records to a device (printer,
               disk, etc.) of choice.

(8)     Alarm Management

               [***]* includes the ability to generate alarms corresponding to
               faults and troubles detected in the UAP 1000 product. [***]* will
               provide API for integration with UAP alarm subsystem. [***]*
               shall create log records for all alarms raised. [***]* will also
               provide capability to the network management system for applying
               filters for the alarms generated and logged by the UAP product.
               The [***]* will also provide the network management system with
               the capability to set up alarm severity assignments for various
               alarms that can be raised by the [***]*. [***]* shall also
               maintain counters of different types of outstanding alarms.

(9)     Performance Management

               [***]* includes the capability to collect performance management
               information. API will be provided for the integration with UAP
               performance data collection software. Performance data could be
               available to network management systems on a daily, hourly and
               minute basis. Threshold crossing alerts will also be

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       8

<PAGE>   24
               generated by the [***]*. The [***]* will provide API to interface
               with the UAP local craft for the administration of the
               granularity periods, number of intervals and threshold values for
               performance management.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       9

<PAGE>   25
2.      Proposed Architecture

        This section briefly describes the architecture being proposed for the
implementation of [***]*.

a.      Design Philosophy

        The [***]* will be implemented using the TTG OM2000 Product. It will be
designed to allow the external interfaces to be modified easily as the needs of
the customer change, and standardized interfaces are developed. The core
functionality will be shielded from the external interfaces via strictly defined
and maintained APIs, and interaction between functional sections of the system
is also structured so that enhancements to one feature or function will have
predictable and limited impact to all other areas of the system. The NE specific
functions and databases will be isolated from the main system and be easy to
test and configure to minimize maintenance over the product lifetime.

b.      Overview

        The system architecture for this approach is shown in Figure 2.

                                     [***]*

Figure  1. [***]* Architecture

i.      System Requirements

                      The System requirements for this approach are:

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       10

<PAGE>   26
        -       The amount of RAM and flash required for the [***]* software and
                database will be determined at a later stage.

ii.     Functional Modules

               The main functional modules in the system are:

        -       [***]* INTERFACE MODULE: This module provides the [***]*
                Interface to the external management systems. [***]* requests
                will be received by this module and forwarded to other modules
                in the [***]* for execution. Responses, alarms and threshold
                violation alerts will be received from different modules and
                forwarded to external network management systems.

        -       PERFORMANCE MODULE: This module maintains the performance
                management data collected by the [***]*. This module will
                compute the data for different granularity periods periodically.
                New performance data is reported to this module by other modules
                outside of the [***]* in the UAP using the API provided by the
                [***]*. As new data is received this module will perform the
                necessary aggregations and determine threshold violations. Any
                threshold violations determined will be reported to the external
                management systems and also logged within the [***]*.

        -       LOGGER MODULE: This module maintains different kinds of audit
                trails/logs for different operations performed by [***]*. This
                will be useful for report generation.

        -       DATABASE INTERFACE: This module involves updating the database
                with application data, performance data, log data, configuration
                data.

        -       FAULT MODULE : This module receives alarms and notifications
                from other UAP subsystem via the API, stores them in the local
                database and forward them to the external management systems.
                This module supports the capability for external management
                systems to :

                -       setup filters for alarms to be reported

                -       assign severity levels for various alarms that can be
                        raised by the UAP

                -       setup filters for alarms that should be logged to the
                        database for later retrieval.

        -       CONFIGURATION MODULE: This module receives configuration data
                for the various configurable entities in the UAP and stores them
                in the database. The configuration information will be used to
                the other modules in the UAP using the API shown in FIGURE 2.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       11

<PAGE>   27
        -       AUDIT TRAIL MODULE: This module receives a copy of all requests
                received by the [***]* and logs them in the database for the
                purpose of auditing.

        -       INTEGRATION API: This module provides the API for integration
                with other modules in the UAP. It also defines the hooks
                described in the previous sections.

        Please refer to Section 0 for the list of assumptions.

iii.    Advantages

        -       Flexible architecture

        -       Scalable

        -       Open [***]* interface allows any application to interface with
                the [***]*

iv.     System Reliability

               It should be noted that the initial versions of the software will
               not comply the reliability expectations stated below.

               Reliability is a very important aspect of this system. The system
               is assumed to be operating 24 hours a day, and 7 days a week. The
               basic architecture and improved CPU should assume that
               maintenance and upgrades could be done without a system outage.
               The [***]* will be offered in redundant configurations. Users
               should not be required to take any action when a system
               switch-over occurs, although it may be acceptable to suspend
               operator activity until the [***]* is stabilized. The operator
               will NOT need to login to regain control of the system.

v.      Extensibility and Growth.

               The [***]* will be designed so that the system can be easily
               extended to support future enhanced services of the UAP 1000
               product.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       12

<PAGE>   28
3.      Functional Requirements

        This section describes the work involved in the implementation of the
[***]* solution.

a.      Development Environment

        The following are the hardware and software requirements for the
development environment:

i.      Hardware

        -      [***]* workstation

        -      UAP 1000

ii.     Software

        -      C++ development environment

        -      [***]* development environment

        -      [***]* software from [***]*

b.      Anda's Interface

        ANDA Networks will perform the integration of the [***]* with the
database and other modules in the UAP.

c.      [***]*  Interface Module

        The [***]* Interface shall have the following functionality:

        -       [***]* Interface shall support the following generic
                functionality.

                -       Login and Logout by network management systems.

                -       Capability for multiple network management systems to
                        login and perform operations at the same time.

        -       [***]* Interface shall provide [***]* for the following
                configuration management functions:

                -       Configuration of resources for the [***]* interface.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       13

<PAGE>   29
        -       [***]* Interface shall provide [***]* for the following
                performance management functions:

                -       Provisioning of the number of intervals for which data
                        is kept

                -       Provisioning of the length of intervals of each
                        granularity supported (daily, hourly and minutes).

                -       Provisioning of threshold values for various performance
                        parameters.

                -       Retrieval of information provisioned for performance
                        management.

                -       Retrieval of current and historical performance data.

                -       Retrieval of threshold violation logs stored in the
                        [***]*.

                -       Registration of Network Management Applications
                        interested in receiving performance reports.

        -       [***]* Interface shall provide [***]* for the following fault
                management functions.

                -       Provisioning of filters for the purpose of reporting
                        selective alarms.

                -       Provisioning of alarm severity assignments for the
                        purpose of determining severity of faults and troubles
                        detected in the system.

                -       Provisioning of filters for the purpose of selective
                        logging of alarms raised in the [***]*.

                -       Retrieval of information provisioned for fault
                        management.

                -       Retrieval of alarm records stored in the [***]*.

                -       Purging of alarm records stored in the [***]*.

                -       Registration of Network Management Applications
                        interested in receiving alarm reports.

d.      Configuration Module

        The configuration module shall provide following functionality:

                -       Configuration of [***]* interface

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       14

<PAGE>   30
                -       Provisioning of [***]* provision data and other [***]*
                        related objects

                -       State Management of equipment and termination points.

e.      Performance Module

        The performance module shall support the following functionality:

                -       Ability to collecting performance information (counters)
                        from boards.

f.      Fault Module

        The fault module shall support the following functionality:

                -       Receive fault information from other UAP modules and
                        forward to network management systems.

                -       Log all alarms raised in the local database.

                -       Use filters setup by network management systems for
                        forwarding alarms and storing in the local database.

                -       Use the alarm severity assigned for various alarms by
                        the network management systems, while raising alarms.

                -       Manage the states of the resources (objects) in the
                        system on the occurrence of alarms.

g.      Audit Trail Module

        The audit trail module shall support the following functionality:

                -       Keep an audit trail of all requests received by the
                        [***]*.

                -       Keep an audit trail of all possible responses by the
                        [***]*.

                -       Keep an audit trail of operations denied by the [***]*.

                -       Keep an audit trail of invalid operations received by
                        the [***]*.

                -       Keep an audit trail of network management systems login
                        and logout activities.

h.      Database Interface

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       15

<PAGE>   31
        The database interface shall support the following functionality:

                -       Convert the data model defined for the [***]* into
                        objects in the database.

                -       Provide interface to access objects both through the
                        [***]* Interface and directly using API.

i.      Logger Module

        The logger module provides the following functionality:

                -       Provide capability to log program errors into files.

                -       Provide capability to log program traces into files.

                -       Provide capability to control the generation of program
                        traces and program logs.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       16

<PAGE>   32
4.      Project Activities

        This section outlines the activities involved in the project
development.

a.      Requirements Analysis

        This involves identifying requirements for the [***]*. This will be
based on specifications supplied by Anda. The following items will be
considered:

                -       Features supported by UAP for [***]* interface.

                -       Description of the features in terms of objects,
                        attributes and operations.

                -       Database storage.

                -       Tracing and logging of [***]* and [***]*

                -       Fault management

                -       [***]*

        A detailed Requirements Document shall be produced by the end of this
phase.

b.      Requirements Review.

        This phase involves:

                -       Review the requirements drafted by TTG.

                -       Establish common understanding between TTG and Anda
                        regarding the functionality of the [***]*.

        If necessary, this will be done in the form of a meeting between TTG and
Anda representatives.

c.      Design

        TTG shall prepare a detailed design for the [***]* that involves the
following:

                -       Identification of software components of the [***]*.

                -       Identify the APIs and hooks to be provided to ANDA
                        engineers working on other modules in UAP.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       17

<PAGE>   33
                -       Identify the APIs to be provided by ANDA for the [***]*
                        to interact with the backend resource managers

                -       Document the data model in the modeling language
                        ([***]*) supported by TTG OM2000 product.

d.      Design Review

        This phase involves:

                -       Review the design document drafted by TTG.

                -       Establish a common understanding between TTG and Anda,
                        of the system design and APIs between the [***]* and
                        other modules.

e.      Implementation and Unit Testing

        This phase involves:

                -       Implementation of the components specified in the design
                        document.

                -       Unit testing of the above implementation.

                -       System Integration

f.      Integration with UAP

        The [***]* software developed by TTG will be integrated with other
modules in the UAP by ANDA. TTG shall provide the necessary documentation.
Technical support over the phone to ANDA engineers to support the integration
shall also be provided as part of this project.

        TTG shall also provide consultation services, if necessary, during this
phase. The cost estimates for such services are not addressed in this proposal.

g.      Test Plan

        ANDA shall prepare the test plan to test the [***]* based on the
requirements and design documents.

h.      System Test

        ANDA shall execute the test plan and report any troubles to TTG. All the
troubles reported in the process shall be fixed by TTG.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       18

<PAGE>   34
5.      Project Schedule

        The following are the project deliverables from TTG:

-   Requirements Analysis

-   Design Specification

-   Software after Unit Testing

        ANDA is responsible for the following items:

-   [***]* Integration with UAP.

-   Test Plan

-   System Test

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       19

<PAGE>   35
6.      Assumptions

        The following assumptions are made in this proposal.

1.  Providing a [***]* Interface to UAP is a joint development effort by ANDA
    and TTG. TTG will implement the API for other module to manipulate/retrieve
    managed information maintained in the [***]*. ANDA will responsible for the
    API to able [***]* communicate backend resource managers (configuration
    manager, alarm managers, [***]* resource manager, etc) to convey the
    configuration/provision messages to those managers in order to achieve
    application-related functionality in the system.

2.  The [***]* is implemented using the TTG OM2000 Product.

3.  TTG shall only develop [***]* Interface to UAP. A separate quote shall be
    provided by TTG if any other interfaces such as SNMP, TL1 are desired.

4.  ANDA will integrate the [***]* software with the database.

5.  ANDA will integrate the [***]* software with the other modules in the UAP.

6.  ANDA will document and execute the system test plan for the [***]*.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       20

<PAGE>   36
                           PART III - UAP 1000 [***]*

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       21

<PAGE>   37
0.      Preface

        This section describes the organization, version history, acronyms used
within the document.

a.      Document Structure

        This part of the document is organized into sections as defined below:

<TABLE>
<S>                   <C>
        PREFACE       This section describes the document structure,
                      conventions, and references used to develop this document.

        SECTION 1     Introduction - This section describes the purpose of the document.

        SECTION 2     Proposed Architecture - This section describes the
                      architecture being proposed for the project.

        SECTION 3     Functional Requirements - This section briefly outlines work involved
                      in the project.

        SECTION 4     Project Activities - This section describes the
                      different phases in the implementation of the project.

        SECTION 5     Project Schedule - This section lists implementation time of each
                      component.

        SECTION 6     Assumptions - This sections lists the assumptions made in this proposal.

        SECTION 7     Pricing - This section provides the pricing for the
                      implementation of the project.
</TABLE>

b.      Document Version History

c.      Acronyms

                                       22

<PAGE>   38
1.      Introduction

        This part of the document is a proposal for Anda's [***]* project. The
purpose of this document is to identify

                -       the scope of project

                -       the work involved in the implementation of the [***]*

                -       Time Estimates and

                -       Pricing

        The remaining part of this section provides a general description of
[***]* solution that will be developed for Anda by TTG.

a.      General System Description

        [***]* is a software product that shall support Anda Access Network
Elements. It provides OAM&P (operations, administration, maintenance &
provisioning) to Anda's [***]* access network elements. It supports a
[***]*-based interface to the upper management systems. The [***]* can be scaled
to support multiple network elements in future The [***]* is designed around a
core set of features and functions that are standardized across multiple TTG
products, giving it a predictable and comprehensive set of features.

        The remainder of this section outlines various major components and
functions provided by the [***]*. More detailed description is provided in the
following sections of the documents.

i.      General Operation

ii.     System

        [***]* may be operated either from a PC-based [***]*, or a web browser.
The [***]* shall support multiple operators. It operates using NT based
communications server, and utilizes a [***]*.

iii.    [***]*

        The operator [***]* ([***]*) will be developed to provide a clear and
consistent product image and operation to the Anda's end customer.

        The operators of the [***]* will operate with the aid of various
graphical screens that will be designed to minimize operator training
requirements, while at the same time the operator will be allowed to directly
access functionality using system menus and the computer keyboard.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       23

<PAGE>   39
iv.     Uplink

        The uplink supported initially is [***]*.

v.      Software Updates

        The software will be designed so that individual applications may be
added into the system without the need for a complete replacement of the
platform software, or reinstallation. It is desirable to allow software to be
added to the system without a system-wide outage.

vi.     Security

        [***]* will provide all access security functions and operator logging
functions for a distributed management system. The operators will each have
individual passwords. It is assumed that the system will be operating on a
secure intranet LAN. Internet firewall security must be provided with a separate
product.

vii.    System Administration

        [***]* will provide the tools and functions that allow the [***]* system
to be administered. This involves operating security functions, updating
topology information, performing database backups, examining [***]*, etc. Our
goal is to perform all system administration without the need for a system
shutdown.

viii.   Topology

        The basis for all operation and functionality of the [***]* system is
the concept of the topology view. The [***]* is represented on the operator
screen as a series of icons and lines. The topology view will allow navigation
of all the managed objects contained in the [***]*.

ix.     Report Generation

        One of the goals of the [***]* is to provide the operator with specific
information on the network configuration, the network status, and network
capacity. Reports are used to allow the operator to pass information to other
groups or individuals, to confirm actions or network changes, and to archive
specific information on the network or customer. [***]* will be designed with a
reporting subsystem that is used to define, generate, and display reports for
the operator. Standard reports will be pre-defined, but the operator may add
additional customized reports as desired.

        Reports can be displayed on the operator screen, output to a specified
printer, or saved into a file on either the [***]* server, or on the operator
terminal.

x.      Alarm Management and Localization

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       24

<PAGE>   40
        [***]* includes the ability to process and display alarm and event
information that is received from the network elements. The events are captured
and stored in the [***]* database and may be retrieved at any time. The [***]*
can [***]* event messages before they are forwarded to the uplink, thus reducing
the volume of traffic sent to the upper management system. If the operator has
the alarm manager feature enabled, elements of the [***]* will change color to
indicate the severity of the fault. The event information is also mapped onto a
set of counters, which indicate the total number of event messages that have
been received for each category. Reports will be available that list outstanding
events, as well as details for the event record.

xi.     Performance Management

        The [***]* provides a set of functions that can collect [***]*
performance information from the [***]*, and store that information into a
database for later reporting. The performance information can be exported to
external applications as desired to provide analysis and graphing capabilities.
Detailed performance studies can be conducted to allow the operator to analyze
the operation of [***]* over any 15 minute interval.

xii.    [***]* Management

        [***]* will provide complete management of all [***]*, including the
following:

-   Current alarm [***]*,

-   Event history [***]*,

-   System event [***]*,

-   Performance history [***]*,

        Allows the performance information to be stored in the [***]* and later
output as a report or a histogram.

-   Operator [***]*,

-   Message [***]*,

        The capacity of the raw message [***]* will be designed to accommodate
the messages from one full day of [***]* operation.

-   SW download status.

        Each stage of the download and activation process should be logged, so
if any faults occur, the operator can analyze the problem.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       25

<PAGE>   41
DATABASE

        The [***]* will provide comprehensive database functionality. The
database module will be able to store the necessary information in a persistent
storage (database). This module will also provide capability to backup and
restore the database. It also provides a database monitoring function in order
to detect % usage of database and other necessary statistics.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       26

<PAGE>   42
2.      Proposed Architecture

        This section briefly describes the architecture being proposed for the
implementation of [***]*.

a.      Design Philosophy

        The system architecture for the [***]* will be implemented using
distributed object oriented techniques to allow feature and capacity
enhancements to be developed with minimum impact to the core functionality of
the [***]*. It will be designed to allow the external interfaces to be modified
easily as the needs of the customer change, and standardized interfaces are
developed. The core functionality will be shielded from the external interfaces
via strictly defined and maintained APIs, and interaction between functional
sections of the system should also be structured so that enhancements to one
feature or function will have predictable and limited impact to all other areas
of the system. The [***]* specific functions and databases will be isolated from
the main system and be easy to test and configure to minimize maintenance over
the product lifetime.

b.      Overview

        The system architecture for this approach is shown in Figure 2.

                                     [***]*

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       27

<PAGE>   43
                          FIGURE 2. [***]* ARCHITECTURE

        In this approach the [***]* is combination of pure Java based front-end
([***]*) and a [***]* server, which communicates with the [***]* using a [***]*.

i.      System Requirements

        The System requirements for this approach are:

-   A PC with [***]* with [***]* Environment

-   A [***]* workstation

-   Object Design's [***]*  Database

ii.     Functional Modules

        The main functional modules in the system are:

-   [***]*: This module is the [***]* for the [***]*.[***]* is used to send
        [***]* commands to the [***]* gateway which in turn are sent to the
        [***]*. This access interface can be used by any other [***]* client.

-   SECURITY MODULE: This module provides a simple user management functionality
        to the system. This involves maintaining:

        -  user ids and password

        -  permitted privileged operations per given user

-   PERFORMANCE MODULE: This module does the performance monitoring function

-   LOGGER MODULE: This module maintains different kinds of audit trails/logs
        for different operations performed by [***]*. This will be useful for
        report generation.

-   DATABASE INTERFACE: This module involves updating the database with
        application data, performance data, log data, security data.

-   FAULT MODULE : This module receives alarms and notifications from the
        [***]*, stores them in the local database and forward them to the [***]*
        for display.

-   CONFIGURATION MODULE: This module receives configuration requests from the
        [***]*, formats the data and forwards them to the [***]*.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       28

<PAGE>   44
-   REPORTING MODULE: This module receives report generation requests from
        the [***]* and generates reports using the data from the local database.

-   PROTOCOL CONVERSION AND ROUTING: This module performs the necessary
        conversion between the internal data and the [***]* data. The converted
        data is then routed to the [***]*.

        Please refer to Section 0 for the list of assumptions.

iii.    Advantages

-   Flexible architecture

-   Scalable

-   Open [***]* interface allows any application to interface with the
        [***]* via the [***]* Gateway

iv.     System Reliability

        It should be noted that the initial versions of the software will not
comply the reliability expectations stated below.

        Reliability is a very important aspect of this system. The system is
assumed to be operating 24 hours a day, and 7 days a week. The basic
architecture and improved CPU should assume that maintenance and upgrades could
be done without a system outage. The element managers in the system will also be
offered in redundant configurations, so the total system behavior must be
defined. Users should not be required to take any action when a system
switch-over occurs, although it may be acceptable to suspend operator activity
until the [***]* is stabilized. The operator will NOT need to login to regain
control of the system.

v.      Extensibility and Growth.

        The [***]* will be designed so that the system can be easily extended to
support [***]*.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       29

<PAGE>   45
3.      Functional Requirements

        This section describes the work involved in the implementation of [***]*
solution.

a.      Development Environment

        The following are the hardware and software requirements for the
development environment:

i.      Hardware

-   [***]* workstation

ii.     Software

-   C++ development environment

-   [***]* or [***]* development environment

-   [***]*

-   [***]*

b.      Anda's Interface

        [***]* interface provided by the UAP1000 [***]* shall be used for
communication between the [***]* and the [***]*.

c.      [***]*

        The [***]* shall have the following functionality:

-   [***]* shall support User login and logout

-   [***]* shall provide the security management functionality

-   Each [***]* session shall allow operations on ONLY ONE [***]*

-   [***]* has a console that displays the alarms coming in from the [***]*.

-   [***]* shall have functionality to generate reports

-   [***]* shall have functionality to view performance statistics

-   [***]* has a menu which supports the operations shown in the table below

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       30

<PAGE>   46

<TABLE>
<CAPTION>
           OBJECT                              OPERATIONS                   # OPERATIONS
           ------                              ----------                   ------------
<S>                            <C>                                          <C>
[***]*                         exit                                              1
[***]*                         create, modify, delete, view                      4
[***]*                         create, modify, delete, view, change              5
                               password
[***]*                         create, modify, delete, view                      4
[***]*                         create, modify, delete, view                      4
[***]*                         create, modify, delete, view, remove,             6
                               restore
[***]*                         create, modify, delete, view, remove,             6
                               restore
[***]*                         create, modify, delete, view, remove,             6
                               restore,
[***]*                         create, modify, delete, view, remove,             6
                               restore
[***]*                         Create, modify, delete, view                      4s
[***]*                         Create, modify, delete, view                      4s
</TABLE>

i.      High Level View of [***]*

        The following is the view of [***]* provided to the operator:

-       Upon startup the operator shall be prompted for user-id and password

-       Upon successful login a console window appears on the screen

-       The layout of the console window shall be as shown below

                      FIGURE 3. HIGH LEVEL VIEW OF [***]*

-       The main menu (AREA-1) provided in the console supports all the
        operations stated above

-       Operator shall be able to navigate through the [***]* by mouse clicks in
        AREA-3

-       Console will be updated with all the alarms arriving from the [***]*.
        This may be accomplished by changing the component colors in the
        navigation area.

-       At each point the navigation area shall provide a pop-up menu with all
        the permitted operation for that particular component currently being
        viewed

-       All the textual messages shall be displayed in AREA-4.

-       AREA-2 will be used to display various charts and graphs containing
        vital statistics such as performance, throughput, etc.,

-       More sub screens will be displayed as needed to take the necessary input
        from the operator.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       31

<PAGE>   47
c.      [***]* specification

        A [***]* interface shall be used for communication between the [***]*
and the uplink systems. A well-defined [***]* interface containing operations to
perform various [***]* functions shall be provided. The [***]* clients shall use
the same [***]* interface.

d.      [***]* Gateway

        The [***]* Gateway shall contain the following sub-components:

-   [***]* Access Interface

-   Security Administration

-   Performance Monitoring

-   Logger

-   Database Module

-   Report Generation

-   Protocol Conversion

i.      [***]* Access Interface

        This module shall provide the [***]* server functionality. It provides a
[***]* interface to any client willing to perform manager role operations on the
[***]*. This interface is used by the [***]* described above.

ii.     Security Administration

        This module shall provide the functionality to:

-   create, modify and delete users who can access [***]*

-   create, modify and delete [***]* which are used to create users

-   [***]* management

-   [***]* management and

-   [***]* evaluation

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       32

<PAGE>   48
iii.    Performance Monitoring

        This module shall maintain various statistical parameters that are used
to [***]* the [***]* of the [***]*.

iv.     Logger

        This module shall maintain detailed audit trails or logs through out the
life of the system. The logs shall be maintained as simple text files. The files
shall stay on the system until they are manually purged.

v.      Database Module

        This module shall be responsible for updating the [***]* database with
all the necessary data. The [***]* database shall maintain data that is needed
to generate detailed reports. This module shall also be responsible to maintain
a persistent store of the application data that is needed for [***]*. Other
important functions of this module shall be [***]*,[***]* and [***]*.[***]*
includes utilities to obtain [***]* usage of the database, etc.

vi.     Report Generation

        This module shall perform the task of report generation. The reports
generated shall be placed in simple text files.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       33

<PAGE>   49
4.      Project Activities

        This section outlines the activities involved in the project
development.

a.      Requirements Analysis

        This involves identifying requirements for the Anda [***]*. This will be
done in the form of a meeting between TTG and Anda. The following items will be
considered:

-   interface between Anda's [***]* and the [***]*

-   the attributes, actions and notification in each managed object class
    implemented by Anda

-   the relevant behavior for each managed object from the [***]* perspective

-   database storage

-   tracing and logging of [***]* and [***]*

-   report generation

-   protection switching

-   performance management

        A detailed Requirements Document shall be produced by the end of this
phase.

b.      Requirements Review

        This phase involves:

-   Review the requirements drafted by TTG.

-   Establish common understanding between TTG and Anda regarding the
    functionality of the [***]*.

        This will be done in the form of a meeting between TTG and Anda
representatives.

c.      Design

        TTG shall prepare a detailed design for the [***]* that involves the
following:

-   Identification of software components of the [***]*.

-   Identify/clarify the APIs provided by the Anda managed resource
    communication interface.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       34

<PAGE>   50
-   Mapping [***]* operations to resource operations.

d.      Design Review

        This phase involves:

-   Review the design document drafted by TTG.

-   Establish a common understanding between TTG and Anda, of the system design.

e.      Implementation and Unit Testing

        This phase involves:

-   Implementation of the components specified in the design document.

-   Unit testing of the above implementation.

-   System Integration

f.      Test Plan

        TTG shall prepare detailed plan to test the [***]* implementation. This
test plan shall be reviewed to establish a common understanding between TTG and
Anda.

g.      System Test

        TTG shall execute the test plan and all the troubles reported in the
process shall be fixed.

h.      Onsite Integration

        [***]* implemented by TTG shall be integrated with Anda's [***]*. The
integration test plan shall be executed in Anda lab to verify the software.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       35

<PAGE>   51
5.      Project Schedule

        The following are the project deliverables.

-   Requirements Specification
-   Design Specification
-   Software after Unit Testing
-   Software after System Integration
-   Test Plan
-   System Test
-   Onsite Integration

                                       36

<PAGE>   52
6.      Assumptions

        The following assumptions are made in this proposal.

1.  The [***]* will be implemented on a [***]* workstation.

2.  Oracle database will be used for the storing of information on the [***]*.

3.  The [***]* local database will store only alarm and performance records.

4.  Fault Management Function will provide only alarm display. Alarm correlation
     and root cause analysis are not implemented.

5.  Reports can be generated on alarm and performance records only. Examples:
     report of all alarms generated since yesterday, behavior of the [***]* etc.

6.  Reports Generated will be stored as simple text files.

7.  No performance graphs will be supported.

------------------------
        * CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                       37<PAGE>   1
                                                                   EXHIBIT 10.12

                      OPS IMPLEMENTATION PROJECT AGREEMENT

        Effective February 20, 2000, TRIGON Networks ("TRIGON") and ANDA
Networks (the "Company") agree as follows:

        1. Development. TRIGON agrees to undertake and complete development of
the Open Provisioning Standard Implementation System (the "OPS System") (as
defined in Exhibit A) in accordance with and on the schedule specified in
Exhibit B. However, the Company understands that the OPS System is intended to
work with the Company's Universal products and that TRIGON's performance is
dependent in part on the Company's actions. Accordingly, the Company will use
diligent efforts to timely provide TRIGON with the items and assistance
specified in Exhibit B and any dates or time periods relevant to performance by
TRIGON hereunder shall be appropriately and equitably extended to account for
any delays due to the Company if such delays affect TRIGON's ability to timely
perform.

        2. Changes. If either party proposes a change to Exhibit A or Exhibit B,
the other party will reasonably and in good faith consider and discuss with the
proposing party the proposed change. TRIGON agrees to accept any change proposed
by the Company where the Company agrees to bear any extra expense and pay (at
TRIGON's standard time and materials rates) for any additional work required by
such change.

        3. Development Project Management.

            a. [***]* from TRIGON and Lipong Chow from Company will be the
initial "Project Coordinators" under this Agreement. The Project Coordinators
will be responsible for day-to-day communications between the parties regarding
the subject matter of this Agreement.

            b. Either party may change its Project Coordinator at any time and
from time to time by giving the other party written notice.

            c. Each Project Coordinator will be responsible for (i) monitoring
the schedules and progress of work pursuant to this Agreement; (ii) receiving
and submitting requests for information and/or assistance; (iii) determining
whether a request he or she receives for information and/or assistance from the
other Project Coordinator is necessary for the other party to complete a
specific Deliverable; (iv) receiving and submitting Deliverables; (v)
cooperating with the other Project Coordinator to implement acceptance testing;
and (vi) supervising and re cording the exchange of confidential information
pursuant to this Agreement.

            d. The Project Coordinators will meet every week to discuss the
progress of the development effort and, if applicable, to exchange information
and Deliverables.

            e. Neither party's Project Coordinator is authorized to amend, alter
or extend this Agreement in any manner.

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.
<PAGE>   2

        4. Acceptance. When TRIGON believes it has appropriately completed a
Deliverable (as defined in Exhibit B), TRIGON will deliver it to the Company.
The Company will accept or reject the Deliverable within 30 days after delivery;
failure to give notice of acceptance or rejection within that period or first
commercial distribution (regardless of notice of rejection) will constitute
acceptance. The Company may reject the Deliverable only if the Deliverable fails
to meet the requirements therefor stated in Exhibit B or if it is otherwise
reasonably unacceptable. A rejection notice will be effective only if it
provides a detailed description of any such failures in a manner sufficient to
allow TRIGON to reproduce them.

If the Company rejects the Deliverable, TRIGON will promptly correct the
failures specified in the rejection notice. When it believes that it has made
the necessary corrections, TRIGON will again deliver the Deliverable to the
Company and the acceptance/rejection/correction provisions above shall be
reapplied until the Deliverable is accepted; provided, however, that upon the
third or any subsequent rejection or if the corrections are not made within ten
(10) days of the initial rejection, Company may terminate this Agreement by ten
(10) days notice unless the Deliverable is accepted during the notice period.

If the Company identifies a failure with a Deliverable and TRIGON shows that the
failure was caused by something other than the Deliverable, the Company will pay
TRIGON for any related work to that time at the TRIGON's standard time and
materials rates.

        5. Support for the OPS System. Provided that Company satisfies it
Support payment obligations, TRIGON shall provide Company with the following
support services for the OPS System: (i) telephone support; and (ii) upgrades of
the OPS System when Company reasonably request such updates (e.g. to conform to
changing software standards or interface standards) (collectively the
"Support"). Bug fixes for the OPS System shall not be considered Support,
rather, TRIGON shall provide bug fixes, as reasonably requested by Company, as
part of its development of the OPS System.

        6. Payment. The Company shall make payments to TRIGON for the
development of the OPS System and the Support in accordance with Exhibit B. Each
payment will be made in U.S. dollars in and from the United States and will be
made no later than 30 days from the date of Developer's invoice. Developer shall
invoice Company in accordance with Exhibit B.

        7. OPS Certification Laboratory.

            a. Subject to Company's rights described herein, Company hereby
grants to TRIGON the right to establish and operate an OPS Certification
Laboratory, as described in Exhibit C. Company shall establish interoperability
standards and a program for certifying OPS customers and contractors (the
"Program"), which the Company shall be free to modify at any time. The Company
shall work with TRIGON to implement the Program and to promote the standards.
Subject Company's approval and supervision, TRIGON administer and operate the
Program as further described in Exhibit C (collectively, the "Certification
Services").

            b. Company shall license to TRIGON the UAP 2000 on terms and
conditions mutually agreed upon by the parties, for the purpose of operating the
Program.

                                       2
<PAGE>   3

            c. Trigon's right to administer and operate the Program shall
initially be exclusive, subject only to Company's approval and supervision. The
Company may, in its sole discretion, terminate TRIGON's right to administer and
operate the Program, or may grant third parties the right to operate the
Program.

        8. Ownership.

            a. The Company shall exclusively own all right, title and interest
(including patent rights, copyrights, trade secret rights, mask work rights, sui
generis database rights and all other intellectual and industrial property
rights throughout the world) in any inventions, works of author ship, mask
works, ideas or information made or conceived or reduced to practice by TRIGON
in the course of developing the OPS System and/or administering and operating
the Program.

            b. The parties hereby make any assignments necessary to accomplish
the foregoing ownership provisions. In interpreting such ownership provisions
anything made or conceived or reduced to practice by an employee or contractor
of a party in the course of performance under this Agreement will be deemed so
made or conceived or reduced to practice by that party; each party has and will
have appropriate agreements with all such employees and contractors necessary to
fully effect the provisions of this Section 5.

            (i) A party being assigned any proprietary right under this
Agreement will have the exclusive right to, and, at such party's expense, the
assigning party agrees to assist such party in every proper way (including,
without limitation, becoming a nominal party) to, evidence, record and perfect
the assignment and to apply for and obtain recordation of and from time to time
enforce, maintain, and defend such proprietary right.

            (ii) Any assignment of copyright hereunder includes all rights of
paternity, integrity, disclosure and withdrawal and any other rights that may be
known as or referred to as "moral rights" (collectively "Moral Rights"). To the
extent such Moral Rights cannot be assigned under applicable law and to the
extent the following is allowed by the laws in the various countries where Moral
Rights exist, the assigning party hereby ratifies and consents to any action
consistent with the terms of this Agreement that would violate such Moral Rights
in the absence of such ratification/consent. The assigning party will confirm
any such ratifications and consents from time to time as requested by the other
party.

            (iii) In the event that a party is unable for any reason whatsoever
to secure the other party's signature to any document it is entitled to under
this Section 5(b), the other party hereby irrevocably designates and appoints
such party and its duly authorized officers and agents, as his agents and
attorneys-in-fact to act for and in his behalf and instead of the other party,
to execute and file any such document and to do all other lawfully permitted
acts to further the purposes of the foregoing with the same legal force and
effect as if executed by the other party.

        9. Confidentiality. Each party agrees that all code, inventions,
algorithms, know-how and ideas and all other business, technical and financial
information they obtain from the other are the confidential property of the
disclosing party ("Proprietary Information" of the

                                       3
<PAGE>   4

disclosing party). Except as expressly and unambiguously allowed herein, the
receiving party will hold in confidence and not use or disclose any Proprietary
Information of the disclosing party and shall similarly bind its employees in
writing. The receiving party shall not be obligated under this Section 6 with
respect to information the receiving party can document:

            (1) is or has become readily publicly available without restriction
through no fault of the receiving party or its employees or agents; or

            (2) is received without restriction from a third party lawfully in
possession of such information and lawfully empowered to disclose such
information; or

            (3) was rightfully in the possession of the receiving party without
restriction prior to its disclosure by the other party; or

            (4) was independently developed by employees or consultants of the
receiving party without access to such Proprietary Information.

        Notwithstanding the foregoing, all Proprietary Information designated as
owned by or assigned to a party in connection with this Agreement shall be
deemed Proprietary Information of such party and exceptions (3) and (4) above
will not be applicable thereto.

        10. Limited Liability.

        a. NOTWITHSTANDING ANYTHING ELSE IN THIS AGREEMENT OR OTHERWISE, NEITHER
PARTY SHALL BE LIABLE OR OBLIGATED UNDER ANY SECTION OF THIS AGREEMENT OR UNDER
ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY
(I) FOR ANY AMOUNTS IN EXCESS IN THE AGGREGATE OF THE FEES PAID TO DEVELOPER BY
COMPANY HEREUNDER OR (II) FOR ANY COST OF PROCUREMENT OF SUBSTITUTE GOODS,
TECHNOLOGY, SERVICES OR RIGHTS OR (III) FOR LOSS OR CORRUPTION OF DATA OR
INTERRUPTED USE.

        b. NEITHER PARTY SHALL BE LIABLE WITH RESPECT TO ANY SUBJECT MATTER OF
THIS AGREEMENT UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER LEGAL
OR EQUITABLE THEORY FOR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES.

        c. Sections 7.a and 7.b will not limit liability for bodily injury of a
person or apply to (i) delay or failure of TRIGON to develop or deliver the OPS
System or any Deliverable if TRIGON has failed to use diligent efforts to
perform or (ii) to breach of Section 5 or 6.

        11. Export Control. Each party shall comply with all applicable export
laws, restrictions, and regulations of any United States or foreign agency or
authority and will not export or re-export, or authorize the export or re-export
of any product, technology or information it obtains or learns pursuant to this
Agreement (or any direct product thereof) in violation of any such laws,
restrictions or regulations.

                                       4
<PAGE>   5

        12. Warranty and Disclaimer. TRIGON represents and warrants to the
Company that: (i) TRIGON has not assigned, transferred, licensed, pledged or
other wise encumbered any OPS System or underlying technology or intellectual
property rights with respect thereto or agreed to do so, (ii) TRIGON has full
power and authority to enter into and perform this Agreement, (iii) TRIGON is
not aware of any actual or potential violation, infringement or misappropriation
of any third party's rights (or any claim or potential claim thereof) by the OPS
System, (iv) TRIGON is not aware of any questions or challenges with respect to
the [patentability or] validity of any claims of any existing patents [or patent
applications] relating to the OPS System, (v) neither TRIGON's entering nor
performing this Agreement will violate any right of or breach any obligation to
any third party under any agreement or arrangement between TRIGON and such third
party, (vi) to the TRIGON's knowledge, no licenses, permissions or releases of
third party rights are necessary for TRIGON's development of or Company's
production or distribution of the OPS System in accordance with the terms of
this Agreement, (vii) all copyrightable matter licensed or assigned hereunder
has been or will be created after January 31, 2000 by persons who were employees
of the TRIGON at the time of creation and no third party has or will have "moral
rights" or rights to terminate any assignment or license with respect thereto,
(viii) the work under this Agreement will be performed in a professional and
workman- like manner and (ix) TRIGON has and will obtain agreements with its
employees and contractors sufficient to allow it to provide Company with the
assignments and licenses to intellectual property rights developed by them for
TRIGON. EXCEPT FOR THE WARRANTY MADE HEREIN, TRIGON MAKES NO WARRANTIES TO ANY
PERSON OR ENTITY WITH RESPECT TO THE OPS SOFTWARE, ANY DELIVERABLE OR ANY
SERVICES OR LICENSES AND DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WITHOUT
LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT. DEVELOPER MAKES NO WARRANTY REGARDING FREEDOM FROM BUGS OR
UNINTERRUPTED USE.

        13. Indemnification. TRIGON will indemnify the Company from all damages,
costs, settlements, attorneys' fees and expenses incurred by the Company in
connection with any claim of a third party that the OPS System infringes any
patent, copyright, or any other intellectual property right or misappropriates
any tradesecret; provided that (i) TRIGON is promptly notified in writing of a
claim from a third party, (ii) TRIGON shall have the sole control of the defense
and/or settlement thereof (except that TRIGON shall not settle any such claim
without the consent of Company, such consent not to be unreasonably withheld),
and (iii) Company furnishes to TRIGON, at TRIGON's request and expense,
information reasonably available to the Company for such defense.

        14. Termination.

        a. If either party should materially breach a material provision of this
Agreement, the other party may terminate this Agreement upon 60 days notice
unless the breach is cured within the notice period or, if the breach cannot
reasonably be so cured, diligent efforts to effect such cure are commenced
during that period and are continued until the cure is completed, which shall be
within a reasonable time.

        b. The Company may terminate this Agreement at any time upon 60 days'
notice, provided that the Company shall upon termination pay TRIGON a
termination payment covering

                                       5
<PAGE>   6

TRIGON's direct and indirect costs incurred in performance of this Agreement
(determined in accordance with Exhibit C) plus (as a return on TRIGON's
investment and not as a penalty) 50% of such costs, less amounts previously paid
to TRIGON under this Agreement; provided, however, that the Company will not be
obligated to pay more in the aggregate than it would have had the development
under this Agreement been completed. This will include reasonably incurred
obligations continuing after the date of termination provided that after notice
of termination TRIGON will act reasonably to mitigate costs and to attempt to
cancel continuing obligations on reasonable terms.

        c. Sections 5 through 15 of this Agreement, any accrued rights to
payment and any remedies for breach of this Agreement shall survive termination.

        d. This Agreement will remain in effect until terminated in accordance
with the express terms of this Agreement.

        15. Publicity and Press Releases. Except to the extent necessary under
applicable laws, the parties agree that no press releases or other publicity
relating to the existence or substance of the matters contained herein will be
made without joint approval.

        16. Relationship of the Parties. Notwithstanding any provision hereof,
for all purposes of this Agreement each party shall be and act as an independent
contractor and not as partner, joint venturer, or agent of the other and shall
not bind nor attempt to bind the other to any contract.

        17. Assignment. Neither party shall have any right or ability to assign,
transfer, or sublicense any obligations or benefit under this Agreement without
the written consent of the other (and any purported assignment will be void),
except that a party (i) may assign and transfer this Agreement and its rights
and obligations hereunder to any third party who succeeds to substantially all
its business or assets.

        18. Notice. All notices under this Agreement shall be in writing, and
shall be deemed given when personally delivered or three days after being sent
by prepaid certified or registered U.S. mail to the address of the party to be
noticed as set forth herein or such other address as such party last provided to
the other by written notice.

        19. Miscellaneous.

        a. The failure of either party to enforce its rights under this
Agreement at any time for any period shall not be construed as a waiver of such
rights.

        b. No changes or modifications or waivers are to be made to this
Agreement unless evidenced in writing and signed for and on behalf of both
parties.

        c. In the event that any provision of this Agreement shall be deter
mined to be illegal or unenforceable, that provision will be limited or
eliminated to the minimum extent necessary so that this Agreement shall
otherwise remain in full force and effect and enforceable.

                                       6
<PAGE>   7

        d. This Agreement shall be governed by and construed in accordance with
the laws of the State of California without regard to the conflicts of laws
provisions thereof. In any action or proceeding to enforce rights under this
Agreement, the prevailing party will be entitled to recover costs and attorneys
fees. Headings herein are for convenience of reference only and shall in no way
affect interpretation of the Agreement.

        e. Except as otherwise expressly stated in this Agreement, the rights
and remedies of a party set forth herein with respect to failure of the other to
comply with the terms of this Agreement (including, without limitation, rights
of full termination of this Agreement) are not exclusive, the exercise thereof
shall not constitute an election of remedies and the aggrieved party shall in
all events be entitled to seek whatever additional remedies may be available in
law or in equity.

        f. No liability or loss of rights hereunder shall result to either party
from delay or failure in performance (other than payment) caused by force
majeure, that is, circumstances beyond the reasonable control of the party
affected thereby, including, without limitation, acts of God, fire, flood, war,
government action, compliance with laws or regulations, strikes, lockouts or
other serious labor disputes, or shortage of or inability to obtain material or
equipment.

        g. Each party recognizes and agrees that the warranty disclaimers and
liability and remedy limitations in this Agreement are material bargained for
bases of this Agreement and that they have been taken into account and reflected
in determining the consideration to be given by each party under this Agreement
and in the decision by each party to enter into this Agreement.

        h. The parties recognize and agree that "TIME IS OF THE ESSENCE" with
respect to completion, delivery and correction of development hereunder.

                                     DEVELOPER

                                     By ________________________________________

                                     Address: __________________________________
                                     Address: __________________________________

                                     COMPANY

                                     By ________________________________________

                                     Address: __________________________________
                                     Address: __________________________________

                                       7
<PAGE>   8

                                    EXHIBIT A

                OPEN PROVISIONING STANDARD IMPLEMENTATION SYSTEM

                                      E-8
<PAGE>   9

                                   EXHIBIT A

                           STATEMENT OF WORK ON OPS.

ARCHITECTURE

The suggested architecture for the OPS software based on the discussions we had
is depicted in the diagram below.

                                     [***]*

The details of this implementation are as follows. The OPS manager acts as the
[***]* for the UAP for the purposes of the [***]*. It would in turn use the
[***]* of the UAP itself for the

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

<PAGE>   10

configuration needs of the UAP itself (eg: configuring line cards) and would
use the external interfaces provided by the UAP to access the management
channel to the [***]* to send [***]* messages to the [***]* to configure them.

In order to support flow through provisioning through the [***]* messages from
[***]* channel, the UAP would pipe through the [***]* messages related to [***]*
from the [***]* to the OPS manager. The OPS manager would then do a mediation
function by translating those calls to the appropriate [***]* messages and
passing them on the UAP's [***]* and/or the management channel to the IADs as
appropriate.

Anda envisages that in future, more management interfaces such as the [***]* or
[***]* could be implemented as mediation functions at the OPS manager. This is
however out of the scope of the current work.

The following are the objectives from the OPS Manager. The OPS solution should
provide

      1.    Connectivity.     The UAP should provide connectivity to the [***]*.

      2.    Uniformity.       The OPS must provide a uniform management
                              interface. In other words, the OPS should provide
                              an interface to management where the UAP and the
                              connected devices appear as an integrated device.

      3.    Transcoding.      The OPS Manager should provide mediation services
                              between different management interfaces.

      4.    Addressing.       The OPS Manager should provide a method for
                              management interfaces to address individual [***]*
                              while still providing an integrated interface.

The OPS Manager can be further decomposed as below.

                                     [***]*

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.
<PAGE>   11

WORK TO BE DONE.

Our current understanding is that Trigon will implement the OPS manager and that
Anda would implement the Management channel as well as the [***]* filtering and
pass through for the EOC. The OPS Manager will need to implement support for the
OPS [***]*, UAP 2000 private [***]* as well as a number of standard line [***]*.
The suggested list of [***]* to implement is outlined in the draft RFC document.

IMPLEMENTATION PLAN

Trigon proposes the following implementation plan for the OPS.

Trigon Implemented OPS Components:

     o    OPS [***]*: The OPS [***]* will interface to an [***]* for
          configuration via [***]*. It will also forward traps to the [***]*

     o    INSTRUMENTATION API: This will interface to the [***]* for
          configuration via [***]*, to the [***]* (for configuration
          originating from the [***]* channel), and to the OPS Configuration and
          Provisioning Engine (for OPS pre-configuration and IAD provisioning).
          It also interfaces to [***]* for configuring the UAP. It is also
          responsible for forwarding [***]* traps received from the UAP and the
          Management channel to the [***]* and/or the [***]* as appropriate.

     o    OPS CONFIGURATION AND [***]* PROVISIONING ENGINE: This represents the
          heart of the solution and maintains the repository of configuration
          information. This component is also responsible for provisioning the
          IADs as well as setup of the Permanent Management channel.

     o    [***]* STACK: The [***]* stack is required for configuration of the
          UAP. It also receives traps from the UAP and the Management channels.

     o    [***]*: A commercial [***]* will be used to implement this component.

TRIGON Implemented: [***]* Manager

     o    [***]* MANAGER: Anda believes that the system can best be demonstrated
          only via use of an EMS. Anda proposes a minimal [***]* solution that
          it will develop that will allow configuration of the OPS manager for
          provisioning related purposes.

SCHEDULES:

Anda proposes the following schedule for implementation. Since the
implementation of the line [***]* required for data services support on the
[***]* is a massive addition (in comparison to the OPS MIB) to the required
[***]* support on the OPS, the support for [***]* would be phased. This
implementation is aimed at demonstration at Supercom in June will only attempt
to provide support for the OPS [***]* and the Interface, DSO/DSO Bundle, T1/E1,
ATM and Ethernet [***]*. This is expected to provide adequate support for flow
through provisioning of voice services through the [***]* interfaces as well as
basic data service provisioning support.

Phase 1: Design Phase

1a: TRIGON-ANDA JOINT RESPONSIBILITY

SCHEDULE: [***]*

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

<PAGE>   12
          This phase will require a joint design phase between Trigon and Anda
          engineering. Specifically, the goal of this phase is to resolve
          interfaces between the OPS and the UAP. These interfaces/protocols
          represent the boundaries between Anda and Trigon's engineering.

OUTPUT:   Interface and protocol specification document developed jointly
          between Trigon and Anda.

1B: TRIGON'S RESPONSIBILITY

SCHEDULE: [***]*:
          During this phase, Trigon will develop an internal design for the
          components it provides

OUTPUT:   Design document for OPS, including all interfaces, developed by
          Trigon.

PHASE 2: IMPLEMENTATION

TRIGON AND ANDA'S RESPONSIBILITY
SCHEDULE: [***]*

          This phase will involve development of the OPS Manager and the EMS
          system by Trigon.

PHASE 3: INTEGRATION AND TESTING

SCHEDULE: [***]*

          This phase will involve integration of Trigon and Anda's development,
          and will involve testing using the [***]*, OPS Manager and the UAP at
          Anda's premises.

UNRESOLVED ISSUES

     1.   The bootstrapping process for the management channel is unresolved at
          this point. The OPS overview document states that a default
          Management channel is pre-configured on the [***]* and would be
          operational when the device detects the link is operational. To
          support this however, the UAP would also need to have the default
          management channel operational. Since different types of devices
          would have different default [***]* channels, the UAP must either
          support all default management channels simultaneously or try to
          establish them on a trial and error basis. (Our understanding is that
          the default Management channel must be established by the UAP by
          itself and the OPS can use that channel to establish the permanent
          management channel. The OPS must be pre-configured for this purpose
          through OPS specific [***]*)

     2.   Availability of an [***]* during integration testing is critical. In
          the absence of a real [***]* a simulation could be used if available.
          Note: Availability of an [***]* implies that, at least one [***]*
          vendor accepts and implements OPS in our timeframe.

     3.   It is assumed that when [***]* are provisioned through the [***]*, the
          [***]* provides sufficient information to provision the [***]* without
          requiring any pre-configuration of the OPS.

     4.   If the UAP is connected through an [***]* to an [***]*, it cannot
          automatically detect the presence of a new [***]*. The [***]* operator
          will need to use an [***]* to setup the VC from the UAP to the [***]*
          and configure the UAP to use it as the management channel. This is
          outside the scope of the OPS project.

     5.   The minimal list of [***]* required for data provisioning is assumed
          to be as described in Additional Points (1) above. This is based on
          today's discussions with Anda.

     6.   The list of [***]* variables where sets to [***]* variables require
          corresponding sets to UAP line card objects is to be decided.

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.
<PAGE>   13

                                    EXHIBIT B

                              DEVELOPMENT SCHEDULE

SCHEDULE OF DELIVERABLES
<TABLE>
<CAPTION>
--------------------------------------------------------------------------------
              TIME                                DELIVERABLE
--------------------------------------------------------------------------------
<S>                         <C>
[***]*                      Fully Operational Beta Version of the OPS System
--------------------------------------------------------------------------------
[***]*                      OPS Certification Lab Operational
--------------------------------------------------------------------------------
[***]*                      Commercially Available OPS System
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
</TABLE>

PAYMENT

1)      DEVELOPMENT OF THE OPS SYSTEM

               a.     External Portion:

                      (i) $[***]*, if all of the OPS System Deliverables are
delivered earlier than the dates provided in the above Schedule of Deliverables.

                      (ii) $[***]*, if all of the OPS System Deliverables are
delivered timely, on the dates provided in the above Schedule of Deliverables.

                      (iii) $[***]*, if any of the OPS System Deliverables are
delivered after the dates provided in the above Schedule of Deliverables.

               b.     Internal Portion: $[***]*/hour

2)      SUPPORT       $[***]* per year for services not to exceed 80 hours. In
        the event Company requests Support in excess of 80 hours in any calendar
        year, TRIGON shall provide additional Support at a price mutually agreed
        upon by the parties.

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                      E-9
<PAGE>   14

                                    EXHIBIT C

                    OPS CERTIFICATION LABORATORY AND SERVICES

1)      Description of Laboratory

The Laboratory is equipped with Anda's UAP2000 and a [***]* simulator to verify
that Integrated Access Devices submitted by vendors are compliant with the OPS
specifications.

2)      Description of Certification Services provided by TRIGON

The Laboratory will run trough a suite of provisioning tests provided by Trigon
to ensure that the vendor's [***]* comply with all the OPS requirements. The
[***]* model will be certified for OPS if it passes all the tests. If the device
fails to pass all the test, detail test results will be provided to the vendor.

* CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTION HAS BEEN FILED
  SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.

                                      E-10

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00013-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00013-of-00352.parquet"}]]