ZTE LTE - Asset Update with IVLP and Engine Update to 66k ...€¦ · Commercial in Confidence...

Copyright 2016 AIRCOM - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping or storage in an information retrieval system - without the written permission of the copyright owner.

External

ZTE LTE - Asset Update with IVLP and Engine Update to 66k cells

Author: Fabio Rodrigues Date: 11/09/2016 Version: 1.0 Status: Final Sec. Class: Commercial in Confidence

Commercial in Confidence

Author: Fabio Rodrigues Page 2 of 24 Date: 11/09/2016 Commercial in Confidence

Contents

1 Document Control ............................................................................................................................ 3 1.1 Revision History ...................................................................................................................... 3 1.2 Reviewers ................................................................................................................................ 3 1.3 Document Acceptance Signature Block .................................................................................. 3

2 Solution Introduction and Overview ................................................................................................. 4 2.1 Solution Architecture ............................................................................................................... 4 2.2 Supported Network Elements ................................................................................................. 5 2.3 Supported ZTE LTE Parameters............................................................................................. 5

3 Scope of Work ................................................................................................................................. 5 3.1 Problem Statement ................................................................................................................. 5 3.2 Project Deliverables ................................................................................................................ 7 3.3 Hardware and Equipment ....................................................................................................... 8 3.4 Assumptions ............................................................................................................................ 9 3.5 Exclusions ............................................................................................................................. 10

4 Commercials .................................................................................................................................. 11 4.1 Pricing ................................................................................................................................... 11 4.2 Payment milestones .............................................................................................................. 11 4.3 Payment Schedule and Terms .............................................................................................. 12

5 Project Approach and Governance ................................................................................................ 12 5.1 Project Approach ................................................................................................................... 12 5.2 Project Governance .............................................................................................................. 14

6 Change Control Procedure ............................................................................................................ 18 6.1 Change Control Process ....................................................................................................... 18 6.2 Change Control Forms .......................................................................................................... 18

7 Standard Reservations .................................................................................................................. 19 8 Glossary ......................................................................................................................................... 20 9 Signatures ...................................................................................................................................... 21

9.1 APPENDIX A – Solution Delivery Certificate ........................................................................ 22 9.2 APPENDIX B – Change Control Form .................................................................................. 23 9.3 APPENDIX C – Acceptance Test Procedure (ATP) ............................................................. 24 9.4 APPENDIX D - Service Level Agreement (SLA) ................................................................... 24



1 Document Control

1.1 Revision History

Revision Number

Date Name Revision

0.1 1/11/2016 Fabio Rodrigues First Draft

0.2 8/11/2016 Fabio Rodrigues Ready for internal review

0.3 8/11/2016 Evelyn Costa Commercial Proposal

1 9/112/2016 Evelyn Costa Ready for internal commercial review

1.2 Reviewers

Reviewer Date Feedback

Katty Bibic 1/11/2016

1.3 Document Acceptance Signature Block

This Statement of Work is accepted by ENTEL Bolivia in full without amendments and exclusions

Signatory Organization Role Signature Date



2 Solution Introduction and Overview

ENTEL Bolivia has IVLP deployed in production for updating of the ASSET data with the defined scope and the solution is currently licensed for 26,000 cells. ENTEL would like to expand the license to include 40,000 additional cells to the scope and also include additional vendor interface for the ZTE LTE technology. AIRCOM is pleased to extend the existing scope of the deployed IVLP solution to include additional cells for Entel Bolivia. The proposed solution also includes the ZTE LTE interface in addition to the already deployed interfaces which were part of the initial scope. The license scope now includes up to 66,000 cells in IVLP 3.0 for Entel Bolivia. This will include remaining cells from Entel Bolivia. The parameters of the basic Asset Update package will be updated in Asset with the use of IVLP 3.0. Hardware Impact – The existing system hardware has been evaluated and it is ENTEL’s responsibility to ensure the hardware is upgraded to the adequate specs as mentioned in the Section 3.3 to guarantee the optimal performance and working of the solution. If Entel Bolivia wants to include any other OPCO data or expand the number of cell count further than 66,000, they need to be done in a revised scope in coordination with AIRCOM subject to commercial agreement.

2.1 Solution Architecture

The software architecture for the proposed solution will be the same as currently installed in ENTEL Bolivia, and will not change. The main and only input data will be the raw files that contain the CM data (live data), plus the customizations done in IVLP using Entel Bolivia MOVILDB database.

Note: The accuracy and maintenance of MOVILDB database is ENTEL’s responsibility.



2.2 Supported Network Elements

As part of the scope of the project AIRCOM will deliver the following Asset parameters update, which will provide support for the vendor interfaces listed below:

Interface Vendor Software

Version

LTE ZTE

2.3 Supported ZTE LTE Parameters

LTE Supported Parameters

ENodeB ID

LTE Cell Name

EARFCN DL

EARFCN UL

TAC

MCC

MNC

# of Tx Elements

# of Rx Elements

Max Tx Power

Scheduler

# of Scheduled Users

Highest Supported Modulation

Physical Cell ID

Group

Code

Bandwidth (MHz)

The support of the above parameters is subject to their availability in the live data feed.

3 Scope of Work This section describes the broad requirements of the solution.

3.1 Problem Statement

ENTEL Bolivia would like to load data from ZTE LTE interface in IVLP 3.0 to update basic parameters in Asset production project. This data will be added to the current already supported interfaces. ENTEL IVLP 3.0 engine currently supports 26,000 cells. With the growth of the ENTEL’s network and addition of the new interface, it is forecasted that the ENTEL network will grow to up to 66,000 cells on the near future. So, update of the engine license is necessary to support ENTEL’s network growth.



3.1.1 Key functional requirements

3.1.1.1 The parameters available on ZTE LTE raw file and applicable to ASSET will be uploaded on the IVLP 3.0 and updated on the ASSET production project.

3.1.1.2 The licenses restriction to load the number of network elements will be changed from 26,000 to 66,000 cells in total; this includes all vendor interfaces supported currently in IVLP at ENTEL including the new deployment of ZTE LTE.

3.1.2 ENTEL Bolivia will provide the following requirements

a. ENTEL Bolivia will provide sample data as required for further development activities for

the interfaces in Section 2.2.

b. ENTEL Bolivia will provide a copy of ASSET database dump. c. ENTEL Bolivia and AIRCOM will review and agree to these requirements before

development commences. d. VPN access for testing and implementation of the solution will be provided by ENTEL

Bolivia. e. Raw file with the live data for the additional ZTE LTE interface.



3.2 Project Deliverables

This section refers to the deliverables required to implement the proposed solution. The deliverables are subject to a number of assumptions and exclusions identified in this SOW. This project will be delivered in 2 phases:

3.2.1 Phase 1 – Development & Integration

3.2.1.1 Enable support for the additional 40,000 cells in the current IVLP.

3.2.1.2 Development & Integration a. Once the requirements document has been signed off by both parties, the development

of the solution shall commence. AIRCOM shall be developing the support ZTE LTE parser off-site within AIRCOM development environment. Upon completion of development and internal testing, the system shall be ready for on-site implementation. The duration of this activity shall be aligned between AIRCOM and ENTEL during the kickoff of this project.

b. It is recommended that the on-site implementation be done in a Staging environment, previously configured in ENTEL premises.

3.2.2 Phase 2 – Implementation

3.2.2.1 At this point the functionality of ZTE LTE interface has been tested in AIRCOM and ENTEL Bolivia staging environments. Acceptance sing-off acquired from ENTEL Bolivia.

Note: At this point all implementation shall take place in the staging environment at ENTEL Bolivia

3.2.2.2 System is ready to Go-live in the production environment.

3.2.3 Go-live

Upon completion of Phase 2 this solution will be taken live, the duration of this activity shall be aligned between AIRCOM and ENTEL during the kickoff of this project.

3.2.4 Support & Maintenance

3.2.4.1 AIRCOM will provide support for the new interface consistent with the support model in place at the time of the deployment.

3.2.4.2 In case that issue on the ZTE LTE interface is found and parameters are not being updated correctly, ENTEL Bolivia will log a support call as per the standard support agreement.



3.3 Hardware and Equipment

This section summarizes the Hardware required for the proposed architecture. It is based on the current information available to us and is a recommendation for the specification to be adhered to ensure that the system performs with expected performance. The recommended hardware proposed to support IVLP 3.0 for ZTE LTE interface and the license update to support up to 66,000 cells is listed on the annex document below:

Hardware Requirements - Entel_Bolivia_IVLP_Nov2016.pdf

Note: Hardware is excluded from this offer and is the responsibility of ENTEL Bolivia. A staging environment can be installed for the purposes of testing patch releases, to offer a great degree of stability and predictability during software upgrades. Rather than directly applying patches and upgrades to a production environment, a staging environment can be used to ensure system stability.

AIRCOM recommends the use of a staging environment, typically scaled to 10% of the dimension of the production system. In this particular instance, this could be a fully virtualized environment running on a single physical PC of suitable specification. Alternatively the entire staging environment could be configured to run on a single blade – of similar spec to the live mediation server, if required. Should a staging environment be required, AIRCOM will work closely with the customer to both design and engineer the most suitable solution. Typically a staging environment is used to install, verify and ultimately release new code into production that has been thoroughly tested.



3.4 Assumptions

In order for AIRCOM to provide the quality deliverables on time, we are taking the following assumptions:

3.4.1 ENTEL BOLIVIA will ensure that unlimited VPN access, remote desktop, FTP access and internet access is provided to AIRCOM as required.

3.4.2 ENTEL BOLIVIA IT support staff (including DBA if applicable) be available throughout the project duration. Names and contact details of this staff should be provided prior to project start.

3.4.3 All hardware, operating systems and administrator permissions for Staging and Production environments will be installed / configured by ENTEL BOLIVIA and ready before the project start and comply with AIRCOM International specifications. ORACLE will be installed by ENTEL.

3.4.4 All hardware where the system will be deployed, as well as its administration, will be located on a single location. If system administration takes place from a different location, AIRCOM will be provided with remote access to the system location and will conduct all its work on the administration site.

3.4.5 ENTEL BOLIVIA is responsible for the licensing, maintenance and support of third party software, such as Windows, Oracle, Citrix, etc.

3.4.6 Backup and restore software, hardware, processes and procedures are the responsibility of ENTEL BOLIVIA

3.4.7 This project will be conducted by AIRCOM off-site.

3.4.8 Working hours will be between 8am – 6pm. Any out of hour’s access will be arranged by ENTEL BOLIVIA, including weekend access.

3.4.9 Any acceptance or performance measurement will be performed under normal operational condition, e.g. not restoring database from archive

3.4.10 Access to staging environment for testing by the time the project starts

3.4.11 AIRCOM will not be responsible for unavailability of raw data (live data) or MOVILDB data per interface, and this will not affect the sign off of this solution.



3.5 Exclusions

Items listed below are out of scope of Supplier, unless otherwise started in this SOW

3.5.1 Any changes to Oracle™ or Oracle™ Licensing.

3.5.2 Any hardware or any 3rd party software licenses such as Windows or any vendor specific licenses.

3.5.3 Any integration point not mentioned in this scope of work

3.5.4 Consultancy Services.

3.5.5 High availability and failover

3.5.6 Data migration

3.5.7 Interfaces other than Radio related parameter data interfaces mentioned on the item 2.2 of this document.

3.5.8 Any integration point, system, databases or tools not mentioned part of the scope

3.5.9 The correctness of data in ASSET radio network planning tool relies on the data sources, live network configuration information of OMC and user inputs of BTS geographical information, antenna configuration, etc. The inconsistency which is caused by incorrect input is not the responsibility of AIRCOM and should not affect the acceptance or signoff.

3.5.10 Training is excluded from this offer



4 Commercials

4.1 Pricing

4.2 Payment milestones

4.2.1 Payment milestone breakdown

Milestone Payment Milestone % Amount to be paid

Milestone 1 Due on expansion of the license to include

the additional cell count on the existing

system with the already delivered interfaces

60% USD 152,760.00

Milestone 2 On the deployment completion of the ZTE 4G

interface

40% USD 101,840.00

100% USD 254,600.00

4.2.2 High level Project plan

Item Descripcion #ENTEL Price

(USD)

S,M&U

Enhanced

SLA (%)

Total

(USD)

IVLP Interfaces (read only)

ZTE LTE 1 30,000.00USD USD 30,000.00

USD 178,000.00

Installation (System, Interfaces and configuration) 1 USD 41,000.00 USD 41,000.00

Support and Maintenance (8x5 excluding holidays and

weekends)1 USD 35,600.00 20.00% USD 35,600.00

USD 76,600.00

USD 254,600.00Total

IVLP Base Module (up to 66000 cells) and IVLP ASSET

Update Module read only (up to 66000 cells)1 148,000.00USD USD 148,000.00

Subtotal:

Services

Products

Subtotal:



4.3 Payment Schedule and Terms

4.3.1.1 Payment has to be made in USD (US Dollars).

4.3.1.2 AIRCOM will issue an invoice for Professional Services Deliverables upon receipt of a purchase order from Entel Bolivia.

4.3.1.3 Upon completion of Professional Services Deliverable, AIRCOM will issue an invoice for complete deliverables.

4.3.1.4 All invoices should be paid no later than 30 days from receipt (Net 30).

4.3.1.5 The validity of the proposal is 30 calendar days.

4.3.1.6 The amount presented does not include taxes or WHT, this value being what AIRCOM International must receive in your Brazilian office (by bank transfer).

4.3.1.7 It is the responsibility of the client to cover the cost of the bank transfer when making the payment of the tools and associated services.

5 Project Approach and Governance

5.1 Project Approach

This section shows how AIRCOM intends to approach this project in terms of Phases, Work Packages and Deliverables. It also defines the Project Roles, their interactions and escalation routes. Finally, it provides a responsibility matrix, which is crucial for the success of the project.

5.1.1 Responsibility Matrix for Project Deliverables

The following matrix lists all the Project Deliverables and who is the sole owner of the successful completion of the task.

ACTION RESPONSIBILITY

Generation of SOW AIRCOM

Review and signoff of SOW ENTEL BOLIVIA

Generate End to End Testing Document AIRCOM

Procurement of hardware as per hardware specifications or equivalent or better.

ENTEL BOLIVIA

Installation and commission of hardware ENTEL BOLIVIA

Access and connectivity to all required systems, including MOVILDB ENTEL BOLIVIA

Procure required 3rd party software ENTEL BOLIVIA

Development and implementation of the solution AIRCOM

Acceptance Testing Document sign-off AIRCOM

Sign-off of acceptance document ENTEL BOLIVIA



5.1.2 Project Dependencies

5.1.2.1 Availability of existing staging environments for the current deployed interfaces, ASSET, IVLP including new hardware for the deployment of ZTE LTE interface and the additional 40,000 cells.Remote connectivity (VPN)

5.1.2.2 Availability of ENTEL BOLIVIA resources with regards to requirements gathering and sign-off.

5.1.2.3 Availability of live data in the OSS (or repository) and in MOVILDB database for the network elements of ZTE LTE interface.

The Following are key constraints that AIRCOM has in creation of the Project Plan and planning the work and its resources in order to fulfill its obligations under this document. A change request will outline if that particular work is adversely affected; this will be managed via a change request process. The Customer and AIRCOM shall perform the tasks assigned to each party in the Project Plan and cooperate with each other in performing tasks shared by the Customer and AIRCOM according to the Project Plan.

AIRCOM will require the Customer to review and approve technical documents submitted by

AIRCOM in order to perform the installation and customization. The documents will be

submitted to review according to the Project Plan. AIRCOM expects the Customer to review

documents and comment on them within an agreed period to be determined and agreed upon

between the parties.

Phased Implementation: The Project Plan assumes that the project is executed and deployed

in streams. Each phase, when completed, can be tested by users (User Acceptance Tests),

deployed into the Production Environment and may be fit for commercial use. The sequence of

phases is of importance and some phases cannot start before their predecessor completed.

The phases will be detailed in the Project Plan. The Customer and AIRCOM should have the

right to carry out concurrent activities to help manage the delivery of the project within the

timelines.

For the benefit of a successful implementation, AIRCOM’s Project Manager, shall have access

to end users for discussions via the Project Manager.

An OSS is a system that requires knowledge to operate, maintain and extend. The Customer

will ensure that only suitable personnel will have access to the system for any purpose.

Where Customer dependencies exist, the Customer has the following AIRCOM dependencies:

Timely delivery of documentations as outlined in the deliverables list.

To complete all deliverables in accordance with the agreed upon scope Project Plan.

To provide necessary resources to complete deliverables in accordance with the agreed plan.

Assign project staff to ensure timely delivery of the project and to provide project governance and reporting.



5.1.3 AIRCOM’s Project Team

The following AIRCOM expertise will be involved throughout the project, at different stages of project life cycle (please note that several functions can be fulfilled by the same person):

AIRCOM-assigned Project Manager

Telecom Expert

Implementation Expert

Integration Expert

Solution Architect

QA Expert

5.1.4 Required Personnel from the Customer

The following Customer-personnel are required throughout the project, at different stages of project life cycle (please note that several functions can be fulfilled by the same person):

Customer-assigned project manager

Technical experts for different equipment types

Communication experts

System administrator

Testers for Acceptance test period

Users

5.2 Project Governance

AIRCOM’s delivery projects operate under a formalized project governance model. This Statement of Work provides an overview to the governance model. Any proposed changes to the Scope of Work will be processed through formalized change management.

5.2.1 Change Request Management

The principles of the process are that the client will approach AIRCOM International’s Project Manager to request any required changes to the Scope of Work. The Project Manager will complete the Change Request with input from the client regarding requirements. The Change Request is analyzed for technical and commercial impact with options evaluated. The Change Request requires approval by all parties. The approved Change Request documentation (as signed by the parties) is then appended to the existing Statement of Work to form the revised Statement of Work for the project.

5.2.2 Acceptance Process

When delivered and validated by AIRCOM International, each Deliverable will be the subject of a Acceptance Test Procedure (“ATP”). This procedure and its related Test Cases and Acceptance Test Specifications are identified, documented and agreed by all parties during the first definition stage of the project (subject to the scope identified in the Statement of Work). The ATP will also describe (a) the procedure for the retest of any component which is demonstrated to have failed the relevant acceptance



test (b) how and when conditional acceptance occurs thereby enabling AIRCOM to proceed with the project subject to resolution of minor snagging items before final project closure. The structure of the acceptance process is described in Work Packages, Deliverables and Project Phases of this document, which represents the agreed effort required to obtain acceptance – Appendix C – Acceptance Test Procedure (ATP). The following sections provide more detail on the testing approach followed by AIRCOM.

5.2.2.1 Test Protocol

This section defines the structure and the performance of the tests. The test structure/protocol will be reviewed by both ENTEL Bolivia and AIRCOM and will require both parties to approve the structure/protocol as adequate before testing will begin. The tests that will be conducted will verify that the IVLP Interfaces have been installed and are working materially according to the Solution Specifications. The test will be performed respectively on each of the interfaces listed. Data or environment dependencies needed for testing scenarios should be identified well in advance of the testing schedule. Identification and resolution of the dependencies are the responsibility of the joint AIRCOM and ENTEL Bolivia Project leads.

5.2.2.2 Test Structure

The acceptance test is organized into testing segments and tests: A testing segment consists of a set of tests, which correspond to an area of significant functionality. It is furthermore expected that each test in a testing segment should be conducted in a natural progression such that minimum set-up is required for each test. A test is defined by a single predicate that is to be verified. A number of observations and measurements may need to be taken as part of a test. However, the test always has a single result - pass or fail.

5.2.2.3 Test Process

The responsibility for conducting the acceptance test should be allocated to one or more ENTEL Bolivia staff. A single testing segment should be at the minimum allocated to an individual tester. While other ENTEL Bolivia staff may witness a testing segment, a single member of ENTEL Bolivia staff should be responsible for conducting the test and signing the test matrix. The test matrix should be signed on completion of each test by the AIRCOM and ENTEL Bolivia staff conducting the test.

5.2.2.4 Acceptance Protocol

After completion of each test, the test must be determined as pass or fail by ENTEL Bolivia. If the test is failed then AIRCOM have the option to attempt to remedy the problem. If the test is still failing then an Incident Report Form shall be completed and both AIRCOM and the ENTEL Bolivia resource involved in conducting the test shall sign immediately in the test matrix to witness the rejection. The test must then be rerun when a resolution of the problem has been provided.

If the test is accepted then both AIRCOM and the ENTEL Bolivia resource involved in conducting the test shall sign to witness as such in the test matrix. In the case that both AIRCOM and the ENTEL Bolivia resource agree that the test itself is invalid or incorrect or tests functionality are different to that defined in the specification then the test may be modified at ENTEL Bolivia discretion and the test rerun. Once the End to End testing has completed, both AIRCOM and ENTEL Bolivia will sign the End-to-End testing certificate, and progress with project acceptance. – Appendix C - Acceptance Test Procedure (ATP).



If no critical issues are reported after ATP, the system will be deemed accepted after two weeks

of start of ATP execution.

5.2.2.5 Incidents

Any test failures must be documented as completely as possible and must give as much supporting information as is practical.

For each outstanding incident AIRCOM will propose a resolution and a date by which the problem will be corrected.

5.2.2.6 Incident Category

It is recognized that some incidents relate to functionality that is more important to the operation of the system than others. Each incident will therefore be assigned a severity, based on severity definitions in the Support & Maintenance Agreement, to be agreed by both AIRCOM and ENTEL Bolivia. Incidents shall be responded to by AIRCOM in compliance with existing agreed SLA.

5.2.2.7 Acceptance Criteria

For an interface to be accepted by ENTEL Bolivia all of the following statements must be true:

1. No Incidents with category Fatal or Severe impact must be outstanding. 2. No more than three Degraded Operation Incidents should be outstanding 3. AIRCOM must provide a plan to resolve all outstanding incidents within SLA targets

as defined in Support & Maintenance Agreement. 4. All required documentation must be submitted and accepted 5. If no critical issues are reported after ATP, the system will be deemed accepted after

two weeks of start of ATP execution.

5.2.2.8 Final User Acceptance Test Procs

ENTEL Bolivia and AIRCOM will compile a formal report, which will be used to present the findings of the evaluation to the ENTEL Bolivia project board. This report will be compiled and presented at the end of the completion of the evaluation process.

Assuming that the solution meets the evaluation criteria:

ENTEL Bolivia and AIRCOM will sign/document a handoff or acceptance note documenting that the system has been approved and is ready in production. Such handoff/acceptance note shall be issued by ENTEL Bolivia within 5 days of the evaluation report being presented.

If the Final Evaluation findings are such that ENTEL Bolivia cannot accept the solution, then ENTEL Bolivia shall request AIRCOM to remedy the issues encountered subject to the SLA in the Support & Maintenance Agreement.

5.2.2.9 Incidents and Changes

Any incidents that are raised during the acceptance process must be documented as completely as possible and give as much supporting information as is practical. For each outstanding incident AIRCOM will propose a resolution and a date by which the problem will be corrected. Should AIRCOM and ENTEL Bolivia agree that the resolution may be implemented during the acceptance process the resolution will be completed and re-evaluated. Where the incident is not addressed during the acceptance process a formal record of the incident will be recorded and monitored, which will be used as part of the final the acceptance process.



5.2.3 Communication Plan

AIRCOM will ensure that clear and effective communication will be maintained throughout the lifecycle of the engagement. All binding day-to-day or routine communication will be between the Project Managers of ENTEL BOLIVIA and AIRCOM by email or by phone followed by a summary email of agreed actions. Commercial communications will be between AIRCOM’s allocated Account Manager

and ENTEL BOLIVIA with both parties Project Managers included in the communication.

5.2.4 Project Meetings

Regular Project Review Meetings will be conducted as often as appropriate, depending on the current stage of the project. All meetings will have a pre-supplied Agenda with Meeting Minutes collated after the meeting and circulated to all parties with agreed Action Points listed.

HOW FREQUENCY PERSON/S INVOLVED

ROLES REASON

Telephone Conference

Weekly AIRCOM &

ENTEL BOLIVIA

Technical Team Lead, Project

Managers Support

Engineers

Informal update. Routine progress reporting,

relationship building, problem solving and risk mitigation.

5.2.5 Project Reports

The AIRCOM Project Manager will on a weekly basis provide updated action list and track progress to all stakeholders detailing progress to plan, key progress since last report and imminent activities with key risks and issues shared. This action list will keep track of issues and risks and will be maintained throughout the project lifecycle and will be available for review upon request.

Weekly project status report will provide the following:

5.2.5.1 Accomplishments –list of key accomplishments met during the current reporting period

5.2.5.2 Issues - provide brief explanation of new issue(s) identified during the current report reporting period and what action(s) were taken or will be taken during the current reporting period.

5.2.5.3 List issues and risks –list of key project activities planned for the next period

5.2.5.4 Schedule Variance – provide brief explanation stating the reason for the variance and what the mitigation plan is.

5.2.5.5 Review of active change requests



6 Change Control Procedure

6.1 Change Control Process

If either Party identifies the need for any change to the Specifications (“Change Control”) under this Agreement, including any Order, the Parties shall proceed in accordance with the change Control Process set forth herein.

Requests to change the SOW may be made by either Supplier or Customer. Since any proposed change in the SOW may result in a change to the price, schedule or the terms and conditions of this SOW, both Supplier and Customer must authorize it in writing. A project change request, attached – Appendix B, must document the proposed change, reason for the change and effect on the project. The authorization to investigate a change prior to approval must be granted by both Supplier and Customer. A written change authorization and any appropriate amendment to this SOW must be issued prior to the implementation of any SOW change.

6.2 Change Control Forms

Please refer to 02 for Change Control forms



7 Standard Reservations

This proposal is subject to the following reservations:

Confidentiality. The information provided by AIRCOM under this proposal is designated

confidential. Customer shall not use or disclose AIRCOM's confidential information to any other

person or entity and for any purpose whatsoever other than for internal purposes.

Limitation of Liability. AIRCOM’s liability shall be limited to direct damages only and in no

way exceed the amount of the applicable purchase order which is subject to the claim.

Intellectual Property. All intellectual property rights in AIRCOM's products whether registered

or unregistered, evidenced by or embodied in and/or attached/connected/ related to AIRCOM’s

products, services or documentation, or part thereof, and any improvements thereof, are and

shall be owned solely and exclusively by AIRCOM.

Use of Software. The use of AIRCOM's software products shall be subject to full payment and

shall be made in accordance with the restrictions in this proposal and subject to AIRCOM’s

standard license agreement.

Service Level Agreement (SLA). This proposal is subject to the terms of the SLA indicated in

Appendix D.

No Other Terms. Unless otherwise is indicated, any other pre-printed terms and conditions

including standard terms in a PO shall not apply.

Screenshots: The delivered products may vary in appearance from the screenshots illustrated

in this proposal according to AIRCOM's decisions.



8 Glossary

Presented in alphabetical order:

TERM DEFINITION

ATP Acceptance Test Procedure

BSC Base Station Controller

DBA Database Administrator

Deliverable A group of actions which result on a tangible and verifiable result.

Deliverables are made of one or more Work Packages.

Environment Refers to the installation environment, e.g. the combination of Software,

Hardware, peripherals and location.

FTP File Transfer Protocol

HW Hardware

IT Information Technology. Refers to the staff that supports Computing and

Network equipment within the ENTEL BOLIVIA.

Oracle A third party Software vendor. AIRCOM uses Oracle database software.

OS Operating System

Phase A major grouping of deliverables with a major milestone attached to it.

Phases are made of one or more Deliverables.

RNC Radio Network Controller

SOW Statement of Work

SLA Service Level Agreement

UAT User Acceptance Testing

Vendor Interface It’s an interface to extract, transform and load data from a Network Vendor, such as NSN. For AIRCOM, a full Vendor Interface also includes a set of

KPI’s, Modules (queries) and Reports.

VPN Virtual Private Network

Work Package A discrete component of a Deliverable.



9 Signatures

Customer hereby orders the services as described in this Statement of Work executed by Customer and Supplier. Customer and Supplier hereby agree that upon execution, this Statement of Work shall constitute a binding order by Customer for foregoing services, subject to the terms and conditions set forth in the Agreement and without requirement for additional order documentation. Any purchase order issued by Customer in relation to the foregoing services will be for Customer’s administrative purposes only. Accepted for and on behalf of: Accepted for and on behalf of: AIRCOM ENTEL Bolivia ……………………………………………. ……………………………………………. Signature Signature ……………………………………………. ……………………………………………. Print Name Print Name ……………………………………………. ……………………………………………. Date: Date:



9.1 APPENDIX A – Solution Delivery Certificate

Project: ZTE LTE Deployment and Addition of 40,000 cells

Description of Milestone Deliverable(s)

Deliverable(s):

1. Phase 1 – Development & Integration to support in IVLP the update of Asset

parameters for ZTE LTE cells and the addition of 40,000 cells in IVLP. 2. Phase 2 – Implementation of the solution in staging environment. 3. Phase 3 – Go-live, implementation of the solution in production environment.

Delivery Certification

We hereby accept that the supplied services and /or software as stated above are in accordance with the conditions, requirements and specifications stipulated in the Contract documentation entered into with AIRCOM. Handed Over By: AIRCOM Name: Designation: Project Manager Date: ____/____/______ Signature: ___________________ Accepted By: ENTEL Bolivia Name: Designation: Project Manager Date: ____/____/______ Signature: ___________________



9.2 APPENDIX B – Change Control Form

Reference

o Original SOW # - o Execution date of original SOW – o CR# -

Reason for this Change Request

Changes in Scope

Changes in Commercials, Delivery Schedule & Billing Customer: ENTEL BOLIVIA USA: Name:____________________________ Title:_____________________________ Signature:_________________________ Date:_____________________________

Supplier: AIRCOM Name:____________________________ Title:_____________________________ Signature:_________________________ Date:_____________________________



9.3 APPENDIX C – Acceptance Test Procedure (ATP)

9.3.1

IVLP_ATP_ZTE-LTE.xlsx

9.4 APPENDIX D - Service Level Agreement (SLA)

9.4.1

Unified SLA -

TEOCO Support and Maintenance Agreement.docx

Date post:	12-Apr-2018
Category:	Documents
Upload:	dangkien
View:	219 times
Download:	3 times

ZTE LTE - Asset Update with IVLP and Engine Update to 66k ...€¦ · Commercial in Confidence...

Documents