Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

UMBRELLA SOLUTION FALUT and Performance

MANAGEMENT

Specifications

Document No. Document Title Author

Umbrella Solution Fault and

Umbrella Project V.0 Pankaj Kumar Mishra and Manuel Merindo
Performance Management

Revision History :
Version No Date Prepared / Modified by List of Changes

Pankaj Kumar Mishra and

V.O 10/03/2017 First Version
Manuel Merindo
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

Approvers:
Name Version Approved Position Reviewed Date
Karthikeyan Chandar CTO
1.0
Antonio Zumbuca Francisco Director – O&M
Arlindo Alves Director -Implementation
Ramaswamy Pillai Director -Engineering
Mohamed Nazar Director - IT
Pedro Ginga Quality

Distribution List:
Name/Position / Available at Published Date
NOC, Operation Team , Integration and DT Team , Quality Team , vendor ,Engineering and
IT Team

For Feedback/Suggestions please drop a mailto:

Pankaj@movicel.co.ao

Manuel.merindo@movicel.ao

Antonio.Francisco@movicel.co.ao

Arlindo.Alves@movicel.co.ao

Ramaswamy.Pillai@movicel.co.ao

Mohamed.Nazar@movicel.co.ao

Pedro.Ginga@movicel.co.ao
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

Index
1. INTRODUCTION
2. SCOPE of WORK
3. ORGANIZATION OF THE DOCUMENTATION
3. DOCUMENTS TO DELIVER WITH THE PROPOSAL
4. GENERAL CHARACTERIZATION of the solution to PROVIDE
4.1. TECHNOLOGY
4.2. SPECIFICATION OF THE APPLICATION TO INTEGRATE
5. DESCRIPTION OF THE UMBRELLA SOLUTION FAULT MANAGEMENT
5.1. GENERAL REQUIREMENTS
5.2. HARDWARE
5.2.1. Hardware Requirements Specification
5.3. SOFTWARE REQUIREMENTS
5.3.1. Software licenses
5.4. Installation and configuration
5.5. UPDATES TO FUTURE VERSIONS
6. FUNCTIONAL SPECIFICATION
6.1. GENERAL REQUIREMENTS
6.2. SYSTEM REQUIREMENTS
6.2.1. Architecture
6.2.2. User Interface
6.2.3. Scalability
6.2.4. System Administration
6.2.5. system performance
6.2.6. availability and reliability
6.2.7. Security
7. TECHNICAL DESCRIPTION of the SOLUTION
7.1. FAULT MANAGEMENT
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

8. Receiving and INSPECTION

8.1. METHODOLOGY
8.2. PROVISIONAL RECEPTION
8.3. WARRANTY
8.4. DEFINITIVE RECEPTION
8.5. SUPERVISION
9. TRAINING
10. MAINTENANCE
10.1. GENERAL CONDITIONS
10.2. CONDITIONS of SERVICE PROVISION
11. REPAIR and replacement METHODOLOGY
11.1. SPARE PARTS
12. SYSTEM LIFE CYCLE
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

1. INTRODUCTION

Objective of this document is the specification of the functional and technical requirements
concerning the supply and installation of Fault and Performance management solution. This
solution should facilitate the provision of services, troubleshooting and service quality
assurance.

2. SCOPE OF WORK

It is intended to acquire a solution that aims at the simplification of procedures for operation,
high robustness and scalability, open architecture that allows for easy integration with other
management systems, in-built graphical interface (user-friendly), Web browser-based, and
enabling access via the Internet/Intranet.

3. DOCUMENTATION ORGANIZATION MODEL

3.1 DOCUMENTATION TO BE DELIVERED WITH THE

PROPOSAL

The supporting documentation to the proposals should be organized as follows:

Fill each of the points of this specifications, item to item, with the words "Meets", "Meets –
with need for developments of source code", "does not meet" and "%" compliance, comments
to entries should be reflected in the field "comments".

Commercial paper, with details, by project phase (timeline), and per item, the price and
quantity for the component or service equipment (HW and SW), mentioning explicitly
optional items, if any.
Must contain the following breakdown of costs:

1. HW
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

2. SW-including cost breakdown of module of Trouble-Ticketing and Fault module

Statistics, Performance Module statistics
3. Licenses
4. Training
5. Maintenance (charged to the supplier 3 years after the Go Live of the project)
6. Project team (if applicable)
7. Travel (if applicable)
8. Stays (if applicable)

Proposed schedule of activities (in the Gantt diagram) with indication of time associated with
the supply of equipment to the various phases of the project, as well as each of the various
activities and interdependencies, identifying critical paths.
Must contain the following project phase’s discrimination:
1. The design phase
2. Implementation phase
3. Rollout phase
4. Maintenance Phase

As regards risk management, the supplier shall provide the resumes of project management
and implementation, as well as an array of Movicel responsibilities/Vendor during the
various phases of the project.

Descriptive document and, preferably, manual containing technical and functional

information (descriptive, of operation, drawings and diagrams) relating to each of the various
components of the system to install, your network integration, additional platforms support
the provision of services, as well as the premises that were considered for the design or
planning of the solution to provide.

Description of acceptance/integration testing, (whether of own equipment wants to integrate

with the other, even if supplied by other manufacturers, including the "core" subsystem, radio
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

subsystem, intelligent network and IT system platforms providing services and additional
features, etc.) and their premises;

The supplier can deliver the proposal, description of the system or components, installation
and operation, etc., if it considers that the provision of such elements help the understanding
of the proposal.

All documentation should be delivered in electronic form (DOCX, XLSX file format, PDF,
JPG and MPP, CSV), accompanied by 3 copies in paper. The business proposal containing
quotations should be delivered, separated from the remaining documentation, in sealed
envelope identified as "business proposal".

4. GENERAL CHARACTERIZATION OF THE SOLUTION TO

PROVIDE
The proposed solution must comply with the generic characteristics indicated below:

4.1. TECHNOLOGY

It should support the provision of mobile services of voice and data using the
technology GPRS/GSM//UMTS/HSDPA/LTE and LTE advance
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

4.2. SPECIFICATION OF APPLICATIONS TO INTEGRATE

The chronological order of applications to integrate should respect the applications most
relevant from the point of view of its impact on businesses, suggests the following priority:

#
Owner of the
Name Details Connector/Protocol events/day
platform
(1)

OSS (Ericsson) Management GSM, UMTS and LTE for Luanda Ericsson -
Net Numen Unified Man.
Manage GSM and UMTS, energy and temperature alarms ZTE Java 521
System
CAS Registration and management of incidents, NDRs Movicel http 90
Backbone monitoring (Luanda-Angola; Lda-Cabinda; Bgla-
U2000 Huawei Java 3408
Huila)
PTN Client MetroLAN Movicel's network monitoring ZTE Java 20
Solar Winds Enterprise network monitoring (retail chain), intranet Movicel (Solaris) http 793
Monitoring the output of internet (Telephonic and Cable &
Cacti Movicel http 28
wireless
Citrix Monitoring of the components of the CORE (Ericsson) Ericsson http 3711
Monitoring and management of services GSM, UMST and
Net Numen M32 ZTE Java 398
LTE
E-Guard Temperature alarms, monitoring sites and Central energy ZTE http -
Nagios IVR monitoring IT System http 978
Rabbitmq SMS monitoring of loading plans IT System http -
Graylog2 Application log monitoring IT System Java 100
PNMS Backbone monitoring of Malange NEC Java -
Unitrans ZXONM E300
Fiber-optic and microwave transmission (SDH) ZTE Java -
(SDH)

(1) Estimated number of events per day

 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

5. DESCRIPTION OF THE UMBRELLA FAULT AND

PERFORMANCE MANAGEMENT SOLUTION
5.1. GENERAL REQUIREMENTS

1. The Umbrella system fault and Performance management must present a flexible
application architecture, allowing also to your future expansion and integration
architecture TMN (Telecommunications Management Network), ensuring the
standardization of communications and of the interfaces.
2. This must generate TT for each alarms and Change request for all Changes. There
must be WO (work order) for TT and CR where third party or team is involved.

3. It should be indicated whether the systems to be managed/controlled have the ability

to do direct interface with external control/management systems, and in this case
through what kind of interfaces.

4. Every WO (Work order) must be assign to assign to corresponding technician

and monitored by system.

5. System should be able to check the amount and efficiency of fuel. System should
give warning and alarms for the action like Fuel is going to finish. This
information need to come one day before.

6. CR (Change Request), WO (Work Order and TT (Trouble Tickets) must have gone
to different phases as per ITIL. Like Analysing and Scheduling, Approval,
Execution, testing and close phase.

3. Must be detail information about the items below and considering the conditions indicated
at each point:
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

1. Architecture Functional and logic.

2. Identification and detailed description of functional blocks and components.
Components of the management system.
3. Managed Domain: listing of managed elements and the mechanisms used for your
management in the areas of configuration, fault and performance Management.

4. The management platform must provide a standard SNMP interface, supporting

authentication mechanisms, encryption and delivery guarantee, enabling the reception of
alarms generated resulting from the supervision of the managed elements. This interface
should still allow bidirectional integration and synchronization with external management
systems by simple configuration, i.e., you should be able to receive and process alarms
generated by external management systems and also able to reroute incoming alarms to
external systems, implementing mechanisms of discrimination on the basis of the delivery
contents of the alarm and the managed element type.

5. The platform should be a scalable and flexible solution with open architecture, which
allows for easy integration with other management systems.

6. The platform must be in compliance with the latest relevant recommendations ITU-T and
TMF Forum (eTOM, SIM/SID, NGOSS) ensuring the standardization of communications
and of the interfaces.

7. The solution must support various technologies, such as (GSM/CDMA/UMTS/LTE,

transmission (SDH, PDH, fiber optic, satellite), MPLS IP).
8. This solution must be able to provide the link utilization of telecom core part
Network.

5.2. HARDWARE

5.2.1. Hardware Requirements Specification

 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

1. The sizing of Hardware must be proposed to support the volumes and response times
indicated for centralized and decentralized operations.

2. The hardware must have ISO 9001 certification.

3. The architecture of the platform should be modular and flexible allowing for future
expansion.

4. The solution hardware should have a single point of failure.

5. The Operating System and hardware version of the equipment to be supplied is the last and
must be indicated.

5.3. SOFTWARE REQUIREMENTS

1. Software applications must be scalable, with multi-layered and distributed, component-

based architecture for reuse and scalability with full support for clustering, failover, and load-
balancing architecture. Scalability for the throughput required, should be done through
configuration only.

2. The Software should be easy integration, based on the industry standard, open transport
technologies and middleware products.

3. The Software should offer the ability to import and export information from/to external
files or systems.

4. The Software will support the CORBA, XML and HTML standards for Internet data
exchange.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

5. The Software should be capable of applying updates to software or information, without

disturbing or disrupting the system.

6. Future versions must be backward compatibility to ensure security updates.

7. Parameterization of software required to meet the business needs of Companies, for the
system supplied, must be done by the supplier during the implementation phase of the
project.

8. The software version of the equipment to be supplied is the last and must be indicated.

9. All modules and sub-modules of the software must be described in summary form.

5.3.1. Software licenses

1. All software licenses must be on behalf of Companies.

2. The Competitor has to calculate the total licensing requirement of different software,
including the RDBMS, etc., as the gift given in volumetric notice with invitation to bid and
the same must be specified, along with the basis for licensing.

3. The bidder shall quote a perpetual license.

4. The copies certified and licensed in the name of the application software Companies, the
RDBMS databases and any other required software for each application according to the
case, with backup will be provided.

5.4. INSTALLATION AND CONFIGURATION

1. The supplier shall provide:

 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

 Installation scripts to configure the base system

 Scripts to configure examples of static reference data, UNIX environment variables.
 Scripts to configure examples of transaction boundaries.
 Any additional scripts required for the completion of the process of installation and
configuration.

2. The system should also provide a system configuration application. This should be a user
application that allows Companies to set up and define the various parameters associated with
the installation.

3. The supplier shall develop and maintain a good cooperation with the hardware vendor and
suppliers of network elements (NE) existing Companies.

5.5. UPDATES TO FUTURE VERSIONS

1. The supplier shall provide a roadmap for future versions of the proposed system.

2. The supplier must also provide an update script to migrate the schema and data from the
previous version to the new version. Upgrade scripts can be used in sequence, if necessary.
3. All APIs should be compatible with previous versions.

6. FUNCTIONAL SPECIFICATION

6.1. GENERAL REQUIREMENTS

1. The solution must be developed in accordance with the international standards

recommended by the TMForum (NGOSS/eTOM) and ITIL. The next Architecture should
make it possible to create interfaces with other external systems with flexibility.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

2. Fault management must receive every alarm event sources, to unify them in a common
format of alarm, correlate and provide a common graphical interface for alarm analysis and
acknowledgement of receipt.

6.2. SYSTEM REQUIREMENTS

The requirements specified in this section are common to all systems of service execution and
service area. The bidder is obliged to prepare a separate declaration of conformity to the
requirements of the system, individually for each of the functional modules. The failure to
follow this schema will result in disqualification of the bid.

6.2.1. Architecture

1. The system must support a component-based architecture that conforms to a layered

architecture.

2. The system should be flexible and modular in design, with the ability to add, remove and
adjust modules for a specific configuration, without disrupting existing services, network
communications and data/communication and the functionality of the company.

3. The system should be customizable to allow new features to be added to the existing
network technologies.

4. The system should manage a heterogeneous network, i.e., multi-vendor, multi-domain,

multi-technology.

5. The components of the solution should be under warranty and service execution which will
interface with the network elements managers (EMS), element and network layer Manager
(NMS), in some cases, you may need a direct interface with the network elements.

6. The system should provide a unique and common mediation platform for alarms.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

7. The system should provide APIs based on interfaces with open standards to allow for
integration with the components of the solution or other third party applications.

8. The system must provide open interfaces based on standard languages and protocols but
not limited to, CORBA, SOAP, and XML.

9. The system shall provide a customizable activation framework that supports standard
protocols, including, but not limited to CORBA, TL1, Telnet, FTP, HTTP and SNMP.

10. The system should support integration with EAI (Enterprise application integration)
products commercially available.

11. The system must support the existing technologies of Movicel network and
products/services with the flexibility to expand to support future technologies and products

12. The solution must provide testing environment and Toolkit for testing of additional
functionality, software patches, etc., before joining with the online system.

13. The system will have the ability to employ relational database.

14. The system databases must be based on standard SQL.

15. The hardware platform on the server side must be based on UNIX and/or LINUX
operating systems.

16. All the configuration details of the necessary hardware and specifications for each
supported technology should be provided.

17. The hardware platform of client-side applications should run on Linux operating systems,
Windows 2000/XP/Vista/Windows 7
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

18. Full details of specific client software must be provided.

19. The bidder must provide the ability to draft detailed in terms of maximum number of
elements that can be managed, including any conditions or limitations because of the size of
the network, the alarm event rates. This project should include requirements DCN (Digital
Communications Network).
20. The following table for statement of compliance must be met, without discarding the list
of requirement shared earlier.

Table 1. Statement of Compliance

Statement of Compliancei Complies / Not Complies

1. IT Infrastructure Management:
a) Monitoring of networks, systems, servers,
applications, and services
b) Comprehensive network discovery and
dynamic mapping
c) Built-in fault management and network
performance/traffic analysis tools
d) Integrated GUI Builder and Report Editor
e) Enterprise scalability and role-based access
control
f) Distributed monitoring and failover
clustering
g) Integration with third-party systems via
open-source APIs
h) Extendibility via driver/plugin SDK.

2. Network Monitoring: Comprehensive discovery and

dynamic mapping. Advanced event management and
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

alerting, real-time operation dashboards. Reporting,

charting, grouped operations.

3. Router/Switch Monitoring: Monitoring status,

Performance and bandwidth usage of individual

router/switch interfaces. All popular network hardware
vendors, including Cisco, Juniper, Alcatel, Huawei and D-
Link, are supported. Integrated charts, reports, alerts for
both standard and custom metrics (e.g. 3G signal
strength).

4. Performance Monitoring: Tracking network links quality

by measuring and analyzing response times, packet loss
rates and downtime. Host capacity planning assistance by
long-term historical trending for CPU load, disk/memory
usage and service response time. Performance degradation
alerting, "Top 10" dashboard.

5. Wireless Infrastructure Monitoring: Browsing detailed

information on access point's wireless network interfaces,
including MAC addresses, number of connected clients,
bridges and repeaters, SSID data, etc. Viewing information
on wireless clients connected to an access point, including
types/roles, signal strength, IP/MAC addresses, uptime and
traffic stats.

6. Network traffic monitoring: The solution must comply

fully with the ITIL Framework, must be
customized/configured for the environment – this
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

configuration must Companies meet the following ITIL

processes: Incident Management; Change Management;
Problem Management; Request Fulfilment; Service Asset
and Configuration; Release and Deployment Manager;
Knowledge Management Configuration Management.

7. Network Configuration: Control the process of

automated and error free configuration change compliance
in the operations environment.

6.2.2. User Interface

1. The solution must provide a graphical user interface (GUI) that provides a Windows-style
or Web-based.

2. The solution should provide drop-down lists and similar characteristics, as applicable to
allow quick and accurate data input by the user

3. The solution should provide clear feedback messages to the user (such as the confirmation
of the execution of a user command), error messages and context sensitive help.

6.2.3. Scalability
1. The solution must allow for easy expansion of the network, in addition to new services,
new network elements, and new protocols and distribute the network through a wide
geographical area, without updated code for the system.

2. CPU usage on full charge for any one of the systems may not exceed 60%

6.2.4. System Administration

1. The system shall make the record (log) of administrative activities.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

2. The system should provide a graphical interface that allows administrators to manage users
and monitored devices.

3. The system shall provide the administrator with tools to monitor system performance.

4. The system should support system administration functions. The system shall provide
utilities, procedures and documentation to perform regular administrative functions required
to maintain the system.

5. The system shall provide utilities for file system data.

6. The system shall retain the history of all changes to the operations of the system and the
user.

6.2.5. System performance

1. Response time for login procedures must be less than 5 seconds after the user issuing the
command login.

2. The response time does not include the time that the user provides to the system with
necessary information, such as passwords.

3. During periods of normal load on the system, the system should pass transactions for
multiple systems in less than 2 seconds.

4. During the period of normal load, system operation with database management system
should be completed in less than 10 seconds.

5. During periods of peak load on the system, the system should pass transactions for
multiple systems in less than 10 seconds.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

6. During the period of maximum load on the system, operation with database management
system should be completed in less than 20 seconds.

7. Provide details about the amount of time required to upgrade a graphics screen and display
a new alarm.

8. Provide details about the time required to perform the backup of the data.

9. Provide details about the time required to generate reports of daily, weekly and monthly
performance preset.

6.2.6. Availability and reliability

1. The system must support a highly reliable platform, with a system of failover that
replicates services and protects the system in case of failure.

2. The system should incorporate high availability system project using a cluster
configuration.

3. The network failure must not result in any system failure.

4. A component of application Failures may not cause any interruption in other application
components running on the system.

5. The operational failures and software application should never cause a complete automatic
system restart.

6. Provide a description on the options and recommendations to provide high availability and
disaster recovery for the proposed solution.

7. Describe the solutions for the following:

 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

A. providing backup processors and other physical devices.

B. providing a fault-tolerant solution.
C. provision of redundant data/telecommunications channels.

6.2.7. Security
1. The platform should have a coherent security system to protect yourself from malicious
attacks and accidental damage, both internal as external sources.

2. The system should allow the creation of user profiles/Admin/customer management with
authentication based on login identifier and password.

3. The system must support a custom role based on the user profile as Movicel requirement.

4. Access control system with possibility of use in setting SSO (Single Signed On) IE, the
user only needs to login once to be able to access all the necessary applications relevant to
your/your work function and in line with the user profile. In other words, there should be no
login separately required to access the various free software applications (fault management,
resource management, management of tickets, and others).

5. All actions performed by authorized users shall be recorded with the date and time in the
database and must be easily retrievable.

6. Passwords should have a limited duration, and the duration can be provisioned.

7. All login attempts should be recorded in the log.

7. TECHNICAL DESCRIPTION OF THE SOLUTION

7.1. FAULT MANAGEMENT

 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

The solution will make it possible to implement processes of supervision of networks and
services. Shall carry out the monitoring in real time of infrastructure (networks, equipment,
and platforms) and services. Will be able to:

 Troubleshooting in anticipation of the client.

 Centralized fault signaling in a single management application.
 Intuitive interface (user-friendly), Web Browser-based, with access via the
Internet/Intranet.
 Determination of the impact of service alarms.
 Reduction of average time of troubleshooting (MBTF) and increased service
availability.
 Simplification of operational tasks – reduction of operating costs (OPEX).

Main features

1. Collection and centralized processing of alarms.

2. Enable drilldown , from the highest levels until a detailed view of the network element and
its components.
3. Advanced alarm Correlation based on rules, making it easier to detect the original cause of
the problem.
4. Create new correlation rules without the need of additional software developments.
5. Enable automatic resolution of incidents (possible to solve without human intervention)
based on two-way interactions with the OSS.
6. Enable the display of all information from vendors on the same display for consultation.
7. Allow the cleaning of most of the alarms so that they are only presented the relevant to the
activity of the NOC.
8. Applying filters to reduce the number of priority alarms to the operator.
9. Allow scalability, increased level of network and new systems to OSS.
10. Allow the import of automatic network typology, georeferenced information and map
dynamic dependency.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

11. Allow the enrichment of the alarm with the SP information, contact, contract, SLA.
12. Signaling the alarm severity (Critical, Major, Minor Alarm alarm and warning) on
affected entities, using standard colours mechanism.
13. The Dashboard must present all relevant statistics for the user on the home page for
graphic and tabular methods, including the view bar. Each user can set your own Panel
and can select a Panel to be displayed on the home page. The performance statistics can
be viewed with alarm by the statistics Panel.
14. Automatic creation of a "work order" associated with the trouble ticket, sent by the NOC
for the resolution.
15. Manual and Automatic Generation of trouble tickets.
16. Association of multiple events at the same alarm log.
17. Shares of alarms with Manual closing comments and registration to the event log.
18. Registration and storage of the alarms and events Log of the network.
19. Available workflow configuration rules alarm (End time, Time, Time of Urgency for
action, and Required Recognition threshold).
20. Summary of module alarms by severity in tabular and graphic format.
21. Preview mode for videowall.
22. Allow extraction of reports intuitively and in a short space of time in Excel, pdf and word
format.
23. Allow extraction of reports of number of breakdowns and average time of interruption in
service because of the malfunction.
23.1 By dimension analysis period.
23.2 By dimension type of intervention (energy-infrastructure, energy-Hvac, energy-
Diesel, transmission, Core, Access, etc.).
23.3 By dimension type of malfunction.
23.4 By dimension company providing services.
23.5 By OSS dimension.
23.6 For technology dimension.
23.7 By dimension Movicel feature that accompanies the event.
23.8 By Geographical Area dimension (Province/County).
23.9 By dimension types of equipment.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

23.10 By Mark dimension of equipment.

24. Allow extraction of network availability report.
25. Allow extraction of report with percentages of defects resolved in time_objectives
26. Allow extraction of report with performances of the teams meet the SLA.
27. Allow the creation of Active and archived alarms reports customizable by user.
28. Allow an analysis of 2-year-old history.
29. Rules/actions module for sending SMS and/or email.
30. Sending automatic alerts after a given threshold, Time.
32. Degree of severity (based on the potential affected traffic, website, etc.)
33. Average number of failure/event/incident.
34. Integration in "real time" with all the OSS without the additional developments, including
identification of the OSS that triggered, alarm type, physical location of the alarm, degree
of severity, etc.

8. RECEIPT AND INSPECTION

8.1. METHODOLOGY

Should be described in detail the methodology and acceptance testing of all components
supplied (HW and SW), as well as your integration in the proposed solution. Also should be
described in the scope and content of the documentation to produce and deliver to the same
purpose. Should be clearly specified and accepted the conditions of test and their results
(acceptance/rejection) before performing any test phase.

8.2. PROVISIONAL APPROVAL

The tests for the purposes of receipt will have as purpose to establish the full compliance of
facilities, features and quality of service with their respective technical and functional
Specifications, as well as with the requirements arising out of applicable Standards. The
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

acceptance procedures shall be drawn up by the supplier and approved before the gross and
sale of your respective tests.

The tests for the purposes of receipt shall be obligatorily accompanied by representatives of
the Companies, and the respective program and achievement dates be previously agreed for
this purpose.

The supplier shall draw up where documentation showing the various items or parameters
checked in tests and values or conditions to obtain, with express indication of the reference
test conditions and completion of "valid" or "invalid" and, in this case, accompanied by a
description of possible corrective actions which it intends to perform, to resolve the non-
validating.

For any parameters or conditions which do not pass the test suite and are provisional
acceptance system conditions, the supplier shall have a reasonable amount of time (which
may not exceed 15 days) to make the corrections and perform new tests validation sets
associated with the item or parameter in question, with a view to concluding a provisional
system acceptance.

As mentioned in the previous points, the set of tests to be carried out include integration
testing of equipment that constitute the complete system, therefore, required to complete the
statement of proper interworking and interoperability with equipment to install, possibly by
other suppliers.

8.3. WARRANTY

All system components to be supplied will be covered by a warranty period of 2 years,

reckoned from the date of provisional reception, during which the supplier will repair or
replace, without charge to the Companies, the components that manifest malfunctions.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

The warranty will cover the versions "releases" of SW necessary for the correction of
systemic problems or other errors and shortcomings of the system.

The supplier shall submit quote for warranty extension for a further period of one year.

8.4. DEFINITIVE RECEPTION

After the warranty period on the date of Provisional Reception, and since the system does not
present anomalies or deficiencies of operation or integration, will be made Final reception.

This Receipt can be carried out without testing. If the Companies want the tests to be carried
out prior to such acceptance, will give knowledge of such claim to the supplier with an
advance of up to 30 days of the end of this period, indicating the tests that you want to be
performed, so that the agreed timetable.

At the end of the warranty period, either choose the Companies not testing or after the
completion and acceptance of these, will be drawn up a Definitive Reception self.

8.5. SUPERVISION

Without prejudice to the full responsibility of the Supplier by final results obtained, the
Companies will monitor and supervise all installation works on it's own or outside entity
designated and accredited for this purpose.

Surveillance action does not diminish or affect the liability of the supplier for the proper
execution of work and deadlines, unless it is expressly determined by the Supervision against
the opinion of the supplier, this determination that, to that end, can only be invoked when it
has been made in writing, the supplier may require.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

9. TRAINING

The supplier shall propose the set of actions Training which it considers appropriate for the
proper understanding of the functioning of the system. The reference framework of training
should include:

(a) A course youstema, with the maximum duration of one week, directed to aspects of
network composition, functional articulation of the components, interconnection with
other systems, HW and SW, supervision and management, etc.;

(b) A course of management and operation, including training "on the job". In addition to
aspects associated with the operation and management of equipment, this course will
also include the creation of configuration parameters and user management;

(c)) A course of maintenance and repair. This course will cover aspects related to the
identification and location of faults ("Faulty location" and "trouble shooting"),
replacement of modules or components, auxiliary equipment testing procedures,
procedures for emergency interventions and analysis of the descriptive list of alarms
system.

The training will be supported and complemented by a set of documents to be provided,

aiming at all technical and operational aspects of their objects.

With the possible exception of the course system, all training and associated documentation
shall, obligatorily, be in Portuguese language.

Will be the responsibility of the supplier the cost of travel and subsistence of participants, in
case any of these courses take place outside Angola.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

10. MAINTENANCE

10.1. GENERAL CONDITIONS

Should be included with an annual value of maintenance services for all components of the
network to provide disaggregated by subsystem basis during the period of warranty including
its extension, in which the supplier requires the following:

Permanent availability of technical staff (1st line support), 24/365;

Permanent availability of "help-desk" (2nd line assistance), 24/365;
Replacement of the normal operating conditions, in accordance with the spare time of service
(TRS), proposed by the supplier;
Final resolution repetitive nature, failures in the operation of the system and should be
corrected in acceptable time limit to be agreed by the two parties;
Provision of technical support with online access to databases of the supplier;

Periodic verification of operation and QoS.

10.2. CONDITIONS OF SERVICE PROVISION

The Tenderer shall describe the means and proposed organization for this maintenance
program (size and team composition, level of training and expertise, time, etc.).
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

The competitor should detail that periodic preventive maintenance operations deems
necessary to carry out, and the conditions of the corrective interventions.

The supplier undertakes that all contacts, as well as any supporting documentation, reports,
speeches, etc., are made using the Portuguese language. In the case of "help desk" 2nd line
may be used the English language.

The supplier shall respond to all questions of a technical nature requested by Services
Companies discriminated against in the previous paragraph. In particular all
faults/deficiencies reported should be the subject of a report, identifying the possible causes,
affected services, their spare time, proposed methodology, if possible, avoid future similar
situations.

The supplier shall provide cooperation to the coaching staff of Movicel, or who's designate,
follow the development of the work, whenever needed, or do understand audits to assess the
quality of services provided.

The supplier shall request permission to Companies where, as a result of the contracted
services, there is a need to make amendments to the HW or SW of network components.

11. METHODOLOGY OF REPAIR AND REPLACEMENT

The supplier shall guarantee the repair of malfunctioning equipment during and after the
warranty period. Should indicate dipped and main beam repair times ("turn around time") of
modules and components, referring to whether conditions for the realization of this activity in
Angola or if will be held abroad, indicating, in this case the country. In addition, you should
maintain an up-to-date register of all modules or defective components.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

The supplier shall consider, indicating, in the composition and size of the proposed
replacement, any constraints associated with times of repair of components or modules that,
by your importance, is mandatory to have available to ensure the functionality and
availability of the system.

Should be indicated by the supplier if the methodology of repair support includes, for
modules or important components, the immediate availability of modules or similar
components that ensure operational back-up, and can be used in case of need, during the
repair period. If so, should be given the maximum time of availability, on the premises of the
Companies, as well as being listed these modules or components.

11.1. SPARES

The supplier shall submit unit prices of the components that make up the batch of spare parts.

The supplier should also propose rightly a lot of spares for the extended warranty period.

12. SYSTEM LIFE CYCLE

The supplier shall ensure a lifetime, in operation, all components of the network and/or
adjuvant systems, ensuring all the contracted features for a period of not less than 7 years.
This aspect will be important differentiating factor in the evaluation of tenders.

The supplier shall ensure that ensures the support during this period, both at HW components
repair or the correction of shortcomings of SW to be hired and installed.

If, during the period of 7 years, the lack of vendor support, motivated by their decisions,
associated with simple discontinuance of support components, the supplier assumes
guarantee that will make the replacement of these network elements by others with similar
features, whose support is ensured,
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

If, by virtue of replacing SW due to new features required by Companies, or by technological

change, has to be total or partial replacement of HW, because the HW supplied and installed
does not support, the supplier is obliged to take back the equipment installed by a value that
cannot be less than a given percentage of the value of similar equipment that supports this
evolution *. This percentage shall be according to the following cases:

For the purposes of the count of years of the system's life cycle, it is considered the date of
provisional reception of the system.

The supplier shall submit annually, the "roadmap" of evolution of both the HW and the SW
("minor" and "major releases") subject to the provision, in particular with regard to:

 SW update for evolution of standards;

 SW update for technological development; and
 HW replacement for reasons of obsolescence and/or incompatibility with new
versions of SW.

When available by the supplier a new SW release this consider that adds value to the solution
installed, by adding new features initially planned and contracted, it shall communicate such
fact to the Companies, supporting such understanding. The Companies after review and
possible discussion with the supplier shall decide whether or not, by your opts.

______________________________________
* In this context, by replacement of the HW is also any items re added the SW or licenses
associated with the new hardware.
 Directorate of Operations and Maintenance (DOM)

UMBRELLA SOLUTION FAULT and

March 10, 2017
Performance MANAGEMENT

i
This statement of compliance, include as attachment the requirement list shared earlier.