Software Requirements Specification

The bidder MUST carefully read the software requirements and illustrate in detail each function
available in the proposed technical offer and reflected in the compliance matrix.
General Functional Requirements:
 It shall be have User Management component for defining user roles to control the access of
tools and database.
 It shall have provision to generate custom reports. The total of number reports and types shall
be finalized during the implementation progress.
 It shall have dashboard with custom charts for to monitor and analyze the use of data and
performance of the applications.
 It shall have multi-language (including English & Arabic) interface. Shall be compatible for
accessibility from any device (i.e. Mobile, Tablet and Laptop), Standard Operating Systems
and Internet Browsers.
 System should be designed and developed in such a way that it will be foundational for future
enhancements.
 System should be flexible to accommodate new/additional pages/integrations.

System Architecture:
 The solution shall be Web based (Mandatory), in addition Desktop (Option).
 System interface/GUI must be easy to use, look & feel.
 The solution must support micro-services and containerized deployment.
 The architecture of the solution should allow flexible modular scaling and integration with
new components.
 The solution architecture must be highly available, when a server is abnormal, all systems
will automatically switch to another server. (Should be under another section “usability”).
 Easy procedure for backup and restore.
 The solution shall support up to 1000 concurrent users (discuss how much user).
 The solution shall be capable to store all subsidiaries assets.

Security and User Management:

 The solution must provide flexible authority management mechanisms, support limiting
users’ rights in menu, ability to configure user groups, create privilege for users based on
subsidiaries and C-level.
 The solution must provide complete log records function, record user’s actions and system
status in detailed, in order for further review and audit.
 The solution should address and enforce network level security, and should encrypt the traffic
between the Mobile app and backend using secured connectivity.
 The solution must provide a multi-org solution (different subsidiaries) to make sure that each
subsidiary’s data is isolated and remains invisible to other organizations. The Proposed
Solution shall manage a single platform for multiple separate groups of users where each
 group has visibility of their services, share and personalize customization of their system
instances and assure the application and data isolation.
 The solution must provide privilege to some users to be able to view a certain amount of
network elements that relate to another subsidiary.
 Data/information can be viewed and changed based on user group permissions.
 The Proposer shall install, configure and deploy the security aspects of the Proposed Solution
to ensure the created users are created as tenants in their own partition, without compromising
their identity or the security of their data.
 Should allow multiple editors to alter the same data in an enterprise or workgroup database
without applying locks or duplicating data. This will help different departments or users to
edit the data without disturbing the default version. Users will be able to view the changes
after reconciling and posting them to an ancestor version.
 Shall allow group-based security policies.
 The Successful Bidder/SI shall suggest firewalls that natively support all protocols required
between the various servers (database, application and web) in the package. No special
configuration should be required to configure the firewall.
 Application users shall not have direct access to the database.
 Any changes to data shall be recorded in a separate table and shall be stamped with the
identity of the user/program and the date / time of the creation/change.
 Shall provide reports on user activity based on the role and the application that was used.
 Capability of self-service reset of passwords in case of forgotten passwords or locked
accounts.
 Shall support security system with a full-fledged Role Based Access Control (RBAC) model.

Integration Capability:
 The proposed solution must support mainstream vendor's equipment and multi-data sources
for multi-vendor and multi-technology.
 The bidder must provide a detailed plan and the available integration methods based on the
current OSS/BSS of the mentioned subsidiaries, and provide the recommended scenarios to
achieve the project objectives and scope as mentioned previously in SOW and Objective
sections..
 The proposed solution must support for a wide range of extraction methods like (API, Web-
services).

Functional Requirements:
1) Searching Tools:
 Shall allow user to run spatial query on multiple layers.
 Shell lets user to select features based on their location relative to features in another layer.
 Shall have a tool allowing users to search and zoom to a location based on GPS coordinates.
 Shall have facility to run combination of attribute & spatial query.
 Shall have facility to auto-complete text boxes based on either feature attributes or linked
records.
2) Navigation Tool Bar:
 Pan View.
 Refresh Map.
 Zoom to full extents.
 Zoom In/Out.
 Zoom to Previous extents (Back),Zoom to Next extents (Forward).(These two buttons, “Go
Back to Previous Extent” and “Go Forward to Next Extent” act like a undo and redo).
 Zoom to Selected Features.
 Move up/down/left/right.
 Show/hide mouse coordinates.
 Activity indicator - display notification while map/data is being processed.
3) Distance and Area Measurements:
 Shall have distance measurements tool to allow user to measure the length of irregular shaped
lines.
 Shall have area measurements tool to allow user to measure irregular shaped polygons.
 Measurements shall be shown using the metric and the imperial system. The ability to snap to
the edge or nodes of the feature being measured is desirable.
4) Descriptive Map Information Tool:
 When the mouse cursor hovers over each map feature, information shall be shown based on
the feature's attributes. Functionality should be available for all GIS Layers; shall be able to
display a combination of attributes and shall not limit the number of features that can be
included with the map tool.
 It shall allow user to turned on and off as needed.
5) Printing:
 Shall have ability to print maps to a printer/plotter with the selection of paper size (A2, A1,
A0, Letter, Tabloid etc.) at suitable scale and page orientation (landscape or portrait).
 Shall have print preview option.
 Shall be able to handle and process any redlining / markups of the map.
 Shall have ability to export the map to a standard image format (BMP, TIF, JPEG and PDF
file).
 Shall have a variety of templates must be available which allow the user to add a custom map
title and to decide which map elements (north arrow, scale bar, overview map, legend, etc.)
will be visible.
 Print date and time shall be automatically added to output at application runtime.
 Legend Shall be automatically adjusted based layers displayed in print area.

6) Redlining Capabilities:
 To provide supplemental information on the map, the system shall allow users to draw simple
shapes (point, line, rectangle, polygon and circle) and add text to make annotations and
markups to the map that must be printable.
7) Drawing:
 The solution must support the ability of drawing a polygon on the GIS map in order to select
all objects inside.
 A polygon should have a polygon type, such as “geo boundary”, “private area”, “military
zone”. Those types should be configurable by users.
 The System should be able to register (plan and modify) physical connections by drawing a
line connection between any two entities.
 The solution must provide various icons for different network elements.
 The solution must support for batch editing of selected objects in polygon.
 The solution must support batch naming & attribute editing.
 The system should support optical / cable facility laying management based on GIS map.
 The solution must support the ability of adding/editing/deleting any new or existing network
element.
8) Modify Features:
 This module will provide user to reshape and modify features and associated attributes. For
Ex: Modifying the shape as well as altering the attributes of a building polygon feature.
9) Select Feature to Edit:
 This will provide user to select features for editing as well as for viewing. It could be done by
the following steps:
a) Feature Locate by Manual Browsing
b) Feature Locate by Entering Lat. and Long.
c) Feature Location by search criteria.
10) Identify Feature to Edit:
 This will provide user with a tool to view data of a feature to be edited on clicking or
selecting it.
11) Add Features:
 This module will provide user to add point, line, and polygon along with its attributes. New
features added will by default take Unique ID besides certain other attributes like State, City,..
For Ex: Adding a new building polygon feature along with attributes whenever a new
building or construction takes place at selected location.
12) Delete Features:
 This module will provide user to delete features. For Ex: Deleting the feature along with its
attributes for a building polygon feature.
13) Move Features:
 This module will allow user to move features. For Ex: Moving a building polygon feature
along with its attributes to a new location.
14) Save Feature Data:
 This will provide user to save geographic feature data and attribute editing done.
15) Hyperlinks:
 Shall have ability to hyperlink to document, images, and PDF files with the feature’s attribute.
16) Emailing:
 Shall allow user to Email map as an attachment.
17) Select Feature:
 Shall be able to select features by clicking on or by drawing a polygon around the feature.
 Shall allow user to generate URL for current view extents, visible layers, and active selection.
 Shall allow user to email the generated URL.
 Shall allow user to export data into KML/KMZ and Shapefile.
18) Thematic Mapping:
 Shall allow user to generate various thematic maps based on the attribute information
available in databases.
19) Bookmarks:
 Shall be able save a map view and be able to return to that exact view at a later date.
 Shall have ability to email the current view extents, visible layers, and active selection in the
form of image.
20) Application Error Reporting:
 Shall allow user to report errors, with a screen capture to complain the support.
21) Data Download:
  User shall have access to the source data in a manner that allows them to interrogate, style,
edit (create, update, and delete), and download individual instance in the Shape File format.
22) Big data:
 GIS application should have ability to filter and organize big data so it can be analyzed and
visualized from a geographic perspective. Big data connectors to GIS engine should be able to
handle not only massive volumes of data but also data of disparate types.

GIS Presentation
 The system shall have the ability to hold location details of:
a. Countries.
b. Provinces/States.
c. Cities.
d. Buildings, including specific naming and information:
i. Core sites
ii. Access sites
iii. Customer sites
iv. Co-location and other operator sites
v. BTS building sites
e. Rooms
f. Cabinet sites (indoor / outdoor)
g. Manhole, handhole, cabinet hole sites
h. BTS sites (non-building)
i. Any other site/location

 The system shall have, as a minimum, the ability to hold the following location details,
General information, like:
a) Address details, including specific building information.
b) Room/floor name (in case of room location).
c) City + Country.
d) Status.
e) Phone number.
f) Geo coordinates, Longitude/ Latitude.
g) Access Description.
h) Owner.
 i) Contact person(s).
j) General description.
 Equipment (active and passive) placed in the location:
a) Connections beginning or ending at a location.
b) DDF, ODF, Patch-Panels in the location.
c) Location alias names (different names for same location).
d) Cabinets/Racks in the location.
 Sites should have an option to relate to a parent site, to parent-child relation.
 The parent site should list all sub-sites and all equipment and connections from all subsites
together.
 The sub(child)site would show the related parent site.
 The solution must support resource coordination and presentation on map
 The solution must support layer functionality.
 The solution must support tower presentation on map
 The solution must support wireless site (sector/alarm/performance data/revenue data)
presentation on map.
 The system shall be able to manage parameters belonging to the BTS/NodeB/eNodeB, such
as but not limited to: antenna height, building height, electrical tilt, mechanical tilt, azimuth,
etc.
 The solution must support wireless site transmission (alarm status/performance data/revenue
data) presentation on map.
 The solution must support PON access network (alarm status/performance data/revenue data)
presentation on map.
 The solution must support region/area revenue presentation on map
 The solution must support PSTN public network presentation on map
 When clicking on a line (trench, duct, cable), the whole path should be highlighted in the GIS
map.

GIS Views & Query

 The network view should have the possibility to switch from graphical view to geographical
view.
 The network view should be interactive, meaning it should not be a drawing, but an
interactive map, where objects can be opened and right mouse menus are available. From the
network view, other forms should be opened automatically when navigating to the requested
right mouse menu option.
  The network view should have the option to enable and disable object types, so they become
visible or are hidden on the map.
 The network view should have an option to show multiple connections as 1 line or multiple.
 The network view should have an option to highlight a physical or logical connection on the
map.
 In case of a protection path, the working path should be highlighted in green and the
protection path in red.
 The system must support legend display that can be easily customized.
 In case a list in form or report has many records, it should allow users to filter on any field to
have a more specific search/result.
 All network resources (such as equipment, locations, domains, IP addresses, vendors) must be
searchable via search fields.
 The GIS map should have functions to show more or less information, such as enable/disable
object names, object types, etc.
 A function should be there to measure the distance of lines, but also to measure “free draw”
on the map, for checking distances.
 The new system should be able to show the map of the whole network, but also maps per
project.

GIS Base Map

The bidder shall prepare a final base map incorporating the data collected, processed and digitized
after survey process. Hard copy base maps are to be prepared at 1:2500 scale ward wise. The base
maps will be prepared in various layers for ease of operation in GIS application. The details of the
various layers (indicative not exhaustive) to be part of the final base map are given as below: (modify
it to fit the RFP narrative).

Sr. No Layer Name Vector Vector Representation Data Source

1 Buildings Polygon LPTIC's subsidiaries, Field Survey
2 Lands Polygon LPTIC's subsidiaries, Field Survey
3 Branches Polygon LPTIC's subsidiaries
4 Customer care centers Polygon LPTIC's subsidiaries
5 Agencies Polygon LPTIC's subsidiaries
6 Dealers Polygon LPTIC's subsidiaries
7 Towers Point LPTIC's subsidiaries, Field Survey
8 GSM,WCDMA,LTE sites Point LPTIC's subsidiaries, Field Survey
9 SDWAN sites Point LPTIC's subsidiaries, Field Survey
10 VSAT sites Point LPTIC's subsidiaries
11 Wireless leased lines Line LPTIC's subsidiaries
12 ADSL Line, Polygon LPTIC's subsidiaries
13 Fiber optics (backbone, Line, Polygon LPTIC's subsidiaries, Field Survey
NGBN, leased lines,
 FTTX)
14 Wireless fixed phone Point LPTIC's subsidiaries, Field Survey
(CDMA 1X and EVDO)
sites
15 Fixed phone Line, Polygon LPTIC's subsidiaries, Field Survey
16 Copper lines Line, Polygon LPTIC's subsidiaries, Field Survey
17 ASON network Line, Polygon LPTIC's subsidiaries, Field Survey
18 Main and terminal Polygon LPTIC's subsidiaries
Exchanges

Base map creation:

The Successful Bidder/SI is expected to provide technical and management support during the
planning, design, development and implementation phases of GIS base maps preparation activity as
described below but not limited to, for satisfactory performance of the services within the Project
Duration.
Business Process Re-engineering:

 Creation of conversion standards, map templates, CAD standards, Standardization of layers

and scale.
 bidder/SI shall prepare the thematic data models considering the current and future
requirements of spatial and attribute databases.
Procurement and Processing of Satellite Imagery:

 The Successful Bidder/SI shall procure and supply ortho rectified image of the preprocessed
data with the high resolution for the area of Libya (Area of Goa State) on WGS-1984 with
projection on UTM.
 The Successful Bidder/SI shall procure and supply updated open street map.
Basemap Preparation and Digitization:

 The Bidder/SI shall prepare an up-to-date large-scale base map (Scale 1:2500) of entire Goa
State using satellite imageries. The Bidder/SI shall then prepare a new GIS Database as
unified Geo-spatial Data with infrastructure details.

 The Successful Bidder /SI shall conceptualize, design and develop Standardized State Data
Model based on national and global standards for storing the spatial & non-spatial data.
a) Standardization of Regional Coordinate System and Datum
b) Should support horizontal and vertical projections
c) Designed Data Model should be based on global best practices where all different types
of Spatial & Non-Spatial Feature Datasets & layers, Annotations, Relationships, Rules,
Cartography etc. can to be organized.
d) Data Model should provide expandable schema to integrate available MIS parameters
from various data sources.
e) Designed Data Model should promote Standardization of Cartography and should provide
provision to store Rules, Relationships, and Tables etc.
f) Data Model should support and store different types of data formats like Vectors, Rasters,
Time Series, Static documents and dynamic datasets.
 g) The Successful Bidder/SI shall then prepare a new database using the existing Database,
as unified Geo-spatial Data with infrastructure details.
h) The Successful Bidder/SI shall perform all related tasks to make sure that legacy data is
successfully migrated to standardized data models.
i) The successful bidder must perform the analysis of the data that needs to be converted /
migrated, prepare and submit a plan for the conversion/migration, and deliver utilities and
programs to achieve the conversion/migration.
These tasks shall include:

 Data scrubbing: Flag & notify of any errors detected in legacy data, assist with corrective
actions as required, add any necessary information in the attribute fields not found in legacy
data.
 Data conversion: Convert data to the standard format to be used in the new data model iii.
Data migration: Migrate data to the new data model
 Data operability: Ensure migrated data is bug free and fully operable
 Meta data: The Successful Bidder/SI shall responsible for formulating a comprehensive and
consistent metadata standard which complies with industry standards and follows National
Mapping guidelines. Most features do not have existing metadata. Identify and flag gaps and
inconsistencies within metadata and assist with completing the data.
 Using the heads on digitization technique, the Satellite image shall be digitized to prepare a
base map by digitizing all the features and attributes available as public like Roads, Bridges,
Railway Tracks, Parks, Gardens, Stadiums, Traffic Squares, Water Bodies (River, Lake,
Pond, Drainage, Canal etc.) etc.
 The Successful Bidder/SI shall while doing the digitization, a special care of data correctness
to be taken like no overshoots / undershoots, proper layering, proper symbology etc.
 The Successful Bidder/SI shall also integrate information of utilities features such as,
telecom, buildings as layers with base map based on availability of data.
 The digital map data shall be GIS compatible. Each map object shall be defined uniquely by
its feature code and symbology (point, line, and polygon).
 The Successful Bidder/SI shall prepare a final base map incorporating the data collected,
processed and digitized. Hard copy base maps are to be prepared at 1:2500 as and when
required during the project.