06 Part 2A Requirement Specifications

Part 2A REQUIREMENT SPECIFICATIONS
PART 2 – SECTION A
REQUIREMENT SPECIFICATIONS
TENDER REF NO.: PT21-27/7-9/27 RS/1

Table of Contents
1 INTRODUCTION ............................................................................................................................................. 4
1.1 Background ................................................................................................................................... 4
1.2 Scope of Tender ............................................................................................................................ 4
1.3 Domain Expertise .......................................................................................................................... 5
1.4 Eligibility of the Contractor .......................................................................................................... 5
2 OBJECTIVE OF THE SYSTEM .................................................................................................................... 6

2.1 Objectives ...................................................................................................................................... 6
3 DESCRIPTION OF CURRENT SYSTEM .................................................................................................... 8

3.1 Current System ............................................................................................................................. 8
4 SERVICE LEVEL........................................................................................................................................... 18
4.1 Helpdesk ...................................................................................................................................... 18
4.2 Maintenance................................................................................................................................. 20
5 PROBLEM ANALYSIS, RESOLUTION AND MANAGEMENT ............................................................. 23

5.1 Problem Management ................................................................................................................. 23
5.2 Escalation Process ..................................................................................................................... 26
5.3 Problem Management System ................................................................................................... 27
6 PROJECT MANAGEMENT ......................................................................................................................... 28

6.1 Project Organisation ................................................................................................................... 28
6.2 Contractor Team Composition .................................................................................................. 29
6.3 Role of Contractor ....................................................................................................................... 29
6.4 Office in Singapore ..................................................................................................................... 31
6.5 Software Development Facility .................................................................................................. 31
6.6 Access to the Premise of SLA ................................................................................................... 32
6.7 Project Management Plan .......................................................................................................... 32
6.8 Progress Reporting ..................................................................................................................... 32
6.9 Mobilisation / Replacement of Contractor’s Personnel .......................................................... 33
6.10 Data Dictionary ............................................................................................................................ 34
6.11 Documentation Deliverables ...................................................................................................... 34
7 EXIT PLAN ..................................................................................................................................................... 35

ANNEX A : SUMMARY OF APPLICATION SOFTWARE ................................................................................... 36

ANNEX B : SUMMARY OF MOBILE APPLICATION .......................................................................................... 43

ANNEX C : REFERENCE STATIONS INFORMATION ....................................................................................... 46
GLOSSARY OF TERMS ........................................................................................................................................... 54

1 INTRODUCTION
1.1 Background
Since August 2004, the SVY21 Geodetic reference frame has been the authoritative
reference frame in use Singapore for uses in positioning, tracking and monitoring
applications. SiReNT’s main purpose is for the realization of the SVY21 reference
frame. SiReNT is a nation-wide satellite positioning reference network developed to
support real-time high precision positioning applications. An initiative by Singapore
Land Authority (SLA), Singapore Satellite Reference Station Network (SiReNT)
provides precise GNSS (DGNSS) services through techniques including Real Time
Kinematics (RTK), Network-RTK, Differential GNSS (DGNSS) and post processing.
1.2 Scope of Tender
Singapore Land Authority (SLA), invites Contractors to submit a tender proposal for
the provision of maintenance for the Singapore Satellite Reference Station Network,
hereinafter referred to as “SiReNT”.
As SLA is currently supplying GNSS Post-Processing data to SiReNT subscribers,

the services shall not be disrupted. The Contractor shall state clearly in his proposal
how the current SiReNT operations can be carried on without disruption when
implementing the new maintenance plan.
The Contractor, besides providing the infrastructure’s software and hardware,

installation, support, maintenance and professional services, shall also provide
comprehensive training to user and support officers nominated by SLA when
needed.
The Contractor shall have proven experience and skill in maintaining CORS
infrastructure and the system software at the Control Centre, wireless
communication, computer networks as well as developing interface(s) to web
applications. The Contractor shall state this experience and skill clearly in the
proposal.
The Contractor shall quote a flat man-day charge for service requests raised by SLA
to enhance the Infrastructure. The cost of service requests shall be computed based
on the man-day required to make the enhancements. The cost of effort incurred in
preparing the proposal / quotation and estimating the man-days required shall not
be borne by SLA.
The Contractor shall manage to work at height with the certification. The Supplier
needs to have WAH (Work at Heights) assessor and WAH manager to fulfill the
requirements. For workers on the ground, minimum certification is through the work

at height for workers course or building and construction course which allows works
to work at heights
For WAH assessor, supervisor and manager. Manage Work at height or
equivalent certification. https://www.ntuclearninghub.com/course/manage-work-at-
heights-course/
For WAH worker, Work at heights for workers or perform work at height
certification. https://www.ntuclearninghub.com/course/perform-work-at-height/
1.3 Domain Expertise
The Contractor shall provide a team comprising at least one domain expert who
possesses the following skill sets:
(a) 3 years of CORS infrastructure support experience;
(b) 3 years of local field survey experience
(c) Experience in setting up and maintaining a GNSS reference station
network;
(d) At least a degree qualification in land surveying; and
(e) Possesses knowledge in latest CORS & GNSS developments
Services of the domain experts shall be available throughout the Contract period,
i.e. till the end of the system warranty.
1.4 Eligibility of the Contractor
The Contractor is required to have experience in the following technologies and

tools:
S/N Description Details
1 GNSS Knowledge ▪ RTCM
▪ NTRIP
▪ Rinex
▪ GNSS Network Software
▪ TIM (Trimble Integrity Manager)
2 Database ▪ e.g. MSSQL

Management
System (DBMS)
3 Web Based ▪ Web-service development, e.g. IIS

Technologies

4 Core Programming • Software development experience.

and Enterprise
Technologies e.g. Microsoft .NET
5 File Transfer e.g. Secure Copy SSH, Secure FTP SSH

Middleware
6 SMS gateway ▪ SMS Gateway Software Development

and integration
8 Electrical and ▪ Electrical and Electronic Engineering

Electronic background other than IT background
9 GNSS Reference ▪ Track records in providing and

Station maintaining GNSS solution and
Maintenance Reference Stations.
Experience
10 Beginner to ▪ Able to understand the network routing

intermediate AWS (including TLS connectivity) and
Cloud Environment provisioning.
knowledge or
experience in ▪ Working experience with AWS services
previous project such as EC2, KMS, S3, API Gateway and
FSx etc
▪ Able to communicate to cloud infra

support team
2 OBJECTIVE OF THE SYSTEM
2.1 Objectives
The primary objective of the System is to serve as the fundamental infrastructure to

realize Singapore’s Coordinated Cadastre system with the SVY21 reference frame
by setting up a permanent GNSS CORS network that offers high precision
Differential Global Positioning System (DGNSS) services in both real-time and

Post-Processing modes. The system shall also be used to support GNSS users in
surveying, positioning, navigation and scientific research.
The System shall comprise the following:

(a) Data Control Centre (DCC) with redundancy built-in;
(b) Remote Access Terminal (RAT) running remote access software;
(c) A minimum of 7 GNSS Reference Stations with meteorological sensors;
and
(d) Web portal to support data and information dissemination, and
operations.
The Data Control Centre shall be connected to GNSS Reference Stations including
the offshore Stations through two separate communications mediums provided by
separate service providers.
The Supplier shall maintain a Web application to allow public users to access the
GNSS data for both post-processing and real-time usage.

3 DESCRIPTION OF CURRENT SYSTEM
3.1 Current System
The Survey & Geomatics Division (SGD) of Singapore Land Authority (SLA) is
responsible for maintaining records of comprehensive and precise definition of all
land parcels (land lots) in Singapore. As a backbone of Singapore’s coordinated
cadastre (SVY21) reference frame, which was gazette on 2nd August 2004, the
SiReNT infrastructure provides a permanent GNSS Reference Station network that
offers Precise GNSS services in both real-time and Post-Processing mode. The
system supports the GNSS users in various positioning, navigation and monitoring
applications.
The current SiReNT infrastructure was migrated to Cloud in 2021 and started
operations in July that year. The Reference stations were refreshed in 2006.
The infrastructure consists of 8 permanent GNSS reference stations, six of which

are on mainland Singapore and two are on Singapore’s southern islands. Each
reference station consists of equipment that allows it to receive satellite signals
twenty-four hours a day.
The System provides these four major services on a monthly subscription model:
(a) Post Processing (PP) On-Demand
(b) Post Processing (PP) Archive
(c) Real-Time Kinematic (RTK)
(d) Differential Global Navigation Satellite System (DGNSS)
Information on the four major services:
(a) Post Processing (PP) On-Demand

i. PP On-Demand enables users generate RINEX files from SiReNT
website.
ii. Users need to log-in CorpPass or SingPass to access PP On-
Demand.
iii. For high accuracy positioning applications such as geodetic survey,
Post-Processing On-Demand is suitable for establishing survey
control points as well as for monitoring.
(b) Post Processing (PP) Archive
i. For users who need archived RINEX data which are not available for
download from SiReNT website, where the required data can be
requested for.

ii. Archived RINEX data is useful for various applications, one of which
is meteorological application which require trend analysis on data over
a long period of time.
(c) Real-Time Kinematic (RTK)
i. Using SiReNT RTK, field operators can determine real-time positions

up to centimetre-level using RTK-enabled GNSS receivers and a
connection to the internet.
ii. Users need to log-in using the given username and token via the
NTRIP (Network Transfer of RTCM over IP) protocol in GNSS
Receivers to access SiReNT RTK. We provide both Single-Base RTK
and Network RTK. Users are free to select the appropriate correction
data stream.
(d) Differential Global Navigation Satellite System (DGNSS)
i. Similar to SiReNT RTK, SiReNT DGNSS allows field operators to

determine their sub-metre positions in real-time with the incoming
pseudo-range or code-based DGNSS correction messages via
GPRS.
ii. Users need to log-in using the given username and token via the
NTRIP (Network Transfer of RTCM over IP) protocol in GNSS
Receivers to access SiReNT RTK. We provide both Single-Base RTK
and Network RTK. Users are free to select the appropriate correction
data stream.
iii. DGNSS can be used for navigation and other applications that do not
need the precision of RTK.
iv. The SiReNT webpage provides information on how to subscribe to

SiReNT services and the contact number for customized requests.
The services mentioned in Paragraph 3.1.4 are offered as subscription and one
time upfront payment schemes in our business model. There are also free-to-use
services under special schemes, e.g. SiReNT Proof Of Concept Scheme (POCS),
SiReNT Promotion Scheme and SiReNT Trial Scheme.
SLA’s Survey & Geomatics Division (SGD) uses SiReNT RTK and DGNSS services
for our daily field work in a variety of applications. SGD also uses SiReNT post
processing data for processing of Horizontal Control Point Markers (HCP) setup and
submitted by Registered Surveyors (RS). SiReNT services are also used in various
precise GNSS positioning applications including survey and mapping, construction

automation, self-mobility platforms development and operations, fleet and asset

management, and others in both public and private industries.
The System host a public website at URL: “https://app.sla.gov.sg/sirent/”. Internet
users can visit the SiReNT website by typing the website address. The Contractor
shall study the website to understand the services provided.
Figure 3.1 Home page
The SiReNT servers are hosted in Government Commercial Cloud (GCC).
All SiReNT reference stations are configured with “IBSS/NTRIP Server” stream with
SSL enabled. On the server side, a NTRIP Caster module contains 8 mountpoints
that served as the data receiving end for reference stations. Each receivers are
sending real-time observables or RT27 format with an epoch interval of 1 Hz to
corresponding mountpoints.
GNSS modules are configured with a connection type of NTRIP client. These
modules are connected to mountpoints from the NTRIP Caster of reference
stations.
Under the GNSS modules, there are satellite tracking, skyplot, multipath and raw
data analysis processing. The raw data analysis is installed for all receiver
connections and RTO Single base for RTCM generator for each type of single base
service. The singe base services output are socket clients and connect to the NTRIP

Caster for public use. There are two storage modules configured as well to generate
the Rinex files and T02. The Rinex module is configured to log at 1 second epochs
and rolling over every 1hour/3600 seconds for each station. The T02 module which
is being used for PP On-Demand is also generating raw data with the same epoch
interval at every 1 second and generating observation file every hour.
SiReNT also uses a network processor module which is the central calculation unit
of Pivot server. This module is responsible for the creation of tropospheric and
ionospheric models of reference station network which contributes and generates
corrections to RTO Net modules used by rovers in the field. On the Pivot server,
there are 2 network processor modules configured (VRSNet_GNSS and
DGPSNet_GNSS). These modules are fed with data from the reference stations
with the help of synchroniser. This Sync_GNSSProc configuration uses the
satellites collected by reference stations, predicted orbit and differential code bias
which made available by ephemeris manager module.
The ephemeris module is separated from the main Pivot server, this module is
configure in one server and directly writing the data to the shared FSx service which
is being mapped to all SiReNT servers in GCC.
SiReNT website configuration and all services are residing in app servers. All the
modules of Pivot server is connected through the load balancer. The connection of
each modules are using unique port number including accounting, reference data
shop and sensor maps.

Mobile Apps
(a) The SiReNT Companion App allows users to receive notification messages
about planned maintenance, subscription details and to locate the nearest
reference station and select them for accurate Global Navigation Satellite
System (GNSS) usage. Users will no longer need to constantly visit our
website for updates. Please refer to Annex B for the mobile application
details.
Figure 3.2 Sample of the User Interface on mobile

Network Diagram
(a) Tenderers should be familiar in cloud environment as the systems were

deployed in cloud.
(b) The public users can login to the SiReNT Web.
(c) The RTK / DGPS user’s device connection to the System to get the
correction signal.
(d) The Reference Stations connection to the System. The connection through
broadband fibre as primary connection while Singtel Mobile IoT as
secondary connection. For those Reference Stations in island, the primary
connection will be Starhub mobile line.
(e) The System needs to connect to the license server.
(f) The System connects to External proprietary FTP servers from Trimble for
ephemeris data.
(g) The System connects back to SLA via the API Gateway for data exchange
on finance data.
The Software for SiReNT is as follows:

(a) The System is based on Trimble software. The major features of the
software are:
i. Trimble VRS3Net App - Generates correction data for cm accurate
positioning solutions in a dense network. An overview status
information of all network processors is also available.
ii. Trimble NTRIP Caster App - Manages the administration of multiple
NTRIP Casters. An overview of status information of so-called
connected users to the Pivot platform is also available.

iii. Trimble Integrity Manager App - Provides real time and post
processing engines to monitor GNSS reference stations.
iv. Trimble Data Shop App - Includes the Reference Data Shop module
which can be used to generate and download correction data for either
a CORS or a VRS for a given period.
v. Trimble iScope App - Provides an overview of iScope rovers
presented on the iScope Map to allow the operator to administrate the
connected rovers and to allow users to review survey sessions.
vi. Trimble Atmosphere App - Calculates IPWV and TEC values from
gathered GNSS data including weather information from various data
sources.
vii. Trimble Accounting App - Provides relevant account information such
as the number of registered users, contracts and subscriptions.
viii. Trimble Rover Integrity App - Analyzes the performance of permanent
rovers in a network based on incoming NMEA strings.
Following Trimble Software bundle is deployed into the System:
Item # Trimble - PIVOT VRS3Net Bundled Quantity
1 Trimble VRS3Net App 1
2 Trimble DGPS Output 1
3 Trimble Data Shop App 1
4 Trimble Integrity Manager - Real Time 1
5 Trimble Integrity Manager - Post Process 1
6 Expansion License for Multi-Servers 1
7 Storage Integrity for Trimble CORS only 1
8 Sparse GLONASS Support 1
9 Trimble Rover Integrity App 1
10 Redundant Communication 1
11 Advanced Multipath 1
12 Google Maps Support in PIVOT UI 1
13 Trimble Atmospheric App (TEC) 1
14 Trimble iScope App 1

15 QZSS Processing Engine 1
16 iGate Support 1
Table 3.1 Trimble Software Bundle
The Server OS as follows:
Item # Software Server Name Quantity
1 MS Windows Server 2019 PIVOT1 UAT 1
2 MS Windows Server 2019 PIVOT2 UAT 1
3 MS Windows Server 2019 APP1 UAT 1
4 MS Windows Server 2019 APP2 UAT 1
5 MS Windows Server 2019 IOT UAT 1
6 MS Windows Server 2019 PIVOT1 PRD 1
7 MS Windows Server 2019 PIVOT2 PRD 1
8 MS Windows Server 2019 APP1 PRD 1
9 MS Windows Server 2019 APP2 PRD 1
10 MS Windows Server 2019 IOT PRD 1
Table 3.2 Server OS
Item # Database server Server Type Quantity
1 UAT Database AWS RDS 1

DATABASE UAT
(Microsoft SQL
Server 2019)
2 PRD Database RDS DATABASE 1

PRD
Table 3.3 Database Software
For the Application Software of the System, please refer to Annex A.

The GNSS Reference Station locations and connections are listed below:
S/N GNSS Location Primary Secondary

Reference connection connection
Station ID
1 SNUS 21 Heng Mui SingTel Fibre SingTel 4G
Keng Terrace
Rooftop
National
University
Singapore
2 SLYG 30 Loyang Way SingTel Fibre SingTel 4G
Loyang Industrial
Estate
3 SNPT Nanyang SingTel Fibre SingTel 4G
Polytechnic
180 Ang Mo Kio
Avenue 8 Rooftop
4 SNYU Block N1 SingTel Fibre SingTel 4G
School of Civil
and
Environmental
Engineering
Nanyang
Technological
University
Nanyang Drive
(high data usage

as including Leica
equipment from
3rd party)
5 SRPT 9 Woodlands SingTel Fibre SingTel 4G
Avenue 9 Rooftop
Republic
Polytechnic
6 SSMK Semakau Island StarHub 3G SingTel 4G
(oldest routers IoT
currently) need
update the router
for 4g, also with
dual sim for
secondary
7 SSTS Sultan Shoal StarHub 3G/4G
SingTel 4G
IoT
8 SNSC National Sailing StartHub 3G/4G SingTel 4G
Center IoT
9 SING Dairy Farm Mobile 4G internet Nil
(maintained by Nature Park connection
Earth provided
Observatory
Singapore The Supplier need
(EOS)) to maintain and
monitoring the
connection to the
System
The reference stations hardware and architecture
The schema will be provided only to the awarded Contractor.
For the parts details of the reference stations, please refer to the Annex C
Reference Stations Information.

4 SERVICE LEVEL
4.1 Helpdesk
A hot-line/helpdesk service shall be provided during the System’s Support Hours.

Beyond the Support Hours, an automatic answering system shall be provided to
record messages left by the customers for following up on the next business day;
Helpdesk services shall be provided to handle requests for assistance from users
during the Support Hours. It will be around 40 calls per month on average while it
will be expected to have higher number of calls in the first year launch;
The Helpdesk service shall be manned by competent and trained personnel during
the support hours, who should be able to answer most of the user queries on
telephone or through electronic mail. A problem resolution log shall be maintained;
Helpdesk service shall compile with the following criteria:
Electronic Services (Websites, Emails)
Commonalities Service Standards Target
% of emails that were rated at least 4

Image out of 6 for helpfulness and
Portrayed politeness. 100%
(Emails only)
% of acknowledgements of receipt
sent within 1 working day of receiving
the email/online application. 100%
Reply Lead
Time % of all general enquiries received,
(designated which were resolved with full replies
email accounts within 3 working days.
to receive public
feedback,
95%
enquiries)
Note: For feedback which cannot be
responded with full replies within 3
working days, Interim Replies should
be sent within 3 working days.

% of all case-specific (excluding

investigation-based) enquiries
received, which were resolved with full
replies within 14 working days.
95%
Note: For enquiries which cannot be
responded with full replies within 14
working days, Interim Replies should
be sent within 14 working days.
Service Quality % of emails that were rated at least 4 100%

out of 6 for effectiveness in attending
(Emails only) to customer needs.
Telephone Services (Public Hotlines)
Image % of calls where officers were rated at

Portrayed least 4 out of 6 for their helpfulness, 100%
(Public patience, politeness, and friendly tone.
Hotlines Only)
% of all calls that was able to get
95%
through to the ringing tone.
% of all calls that were attended to

within 30s.
Service Level Note: In the case of hotlines that use

(Public Automated Voice Response Systems,
Hotlines Only) the 30s is from the time the customer 80%
has selected the option to speak to an
officer to the time the call is connected
to the officer. This will include the
recorded music etc that is played while
the customer is waiting.

Telephone Services (Public Hotlines)
Service Quality % of officers who were rated at least 4

(Public out of 6 for their effectiveness in 95%
Hotlines Only) attending to customer needs.
% of officers who were rated at least 4

Clarity in out of 6 for clarity in communication. 95%
Communicatio (clear, and audible)
n (Public % of officers who were rated at least 4
Hotlines Only) out of 6 for their competent work 95%
knowledge.
4.2 Maintenance
All customers support work will be on-going and day-to-day production support will
be on a daily basis and all service requests will be raised on a need basis. The
service requests shall be prioritized by the user departments in order to roll out the
important ones earlier. The completion time for service requests will also be based
on the service level agreement or mutually agreed schedule with the users.
(a) Problem Analysis and Resolution Time
i. The problem resolution time is measured from the time the problem is
received to the time the resolution is accepted. Depending on the
severity of the problem (which is to be jointly agreed by the users and
the vendor).
(b) Service Requests Assessment Report Turnaround Time
i. Service Request (SR) refers to requests for changes or

enhancements to the Application or modules comprising minor
change requests as well as major change requests.
(c) The Contractor’s scope of work shall include:

i. Make an assessment on the SR and submit a proposal to the Authority

for approval.
ii. The proposal shall detail the impact analysis of the changes on the
existing system environment such as security, system performance,
integration, availability and etc.
iii. The Supplier shall bear all costs in the assessment and preparation
of the proposal. The impact analysis and effort assessment shall be
considered as part of the production support; carry out design,
development, testing and implementation to modify the Systems in
order to meet the requirements of the SR;
iv. Prepare/update relevant documentation to reflect changes made to
the Systems, not limited to the following:
• Functional Specification
• Design Specification
• User Guide
• Administration Guide
• Operations Guide
• Online Help
• Hardware and Software list
v. Train the Authority’s users on the changes made to the Systems to

enable them to be competent and self-reliant in the operation of the
Systems; and
vi. Handover the operations to users or Authority’s infrastructure FM
team.
The submission time for Impact Analysis report submission will be based on
the following schedule or mutually agreed schedule with the customer:
Estimated Man-day Submission of Completion

for change Assessment Report Time Within
Less than or equal 1 working day from the 3 working days

to one (1) working date the service request
day / change request is
raised
Greater than one 2 working days from the 1 calendar week

(1) day but less date the service request
than or Equal to / change request is
three (3) working raised
days

Estimated Man-day Submission of Completion

for change Assessment Report Time Within
Greater than three 3 working days from the 2 calendar week

(3) days but less date the service request
than or Equal to ten / change request is
(10) working days raised
Greater than ten 1 calendar week or Subject to

(10) working days unless specified by SLA negotiation
between the
Supplier and
SLA
vii. The Contractor shall ensure that the SRs are successfully
implemented according to agreed schedule based on agreed man-
efforts. In the event that the Contractor cannot meet the pre-agreed
schedule, any additional costs incurred for the completion of the SR
shall be borne by the Contractor.
viii. The Contractor shall ensure sufficient resources to meet the service
levels. For urgent major Service Requests, the Contractor shall be
required to mobilise additional manpower after being notified by the
Authority to undertake urgent requirements.
ix. The SR would only be considered completed after the enhancements
have been successfully migrated to production environment and when
all relevant documentation is prepared/updated and accepted by the
Authority. In cases where the Authority decides to shelve the
approved SR due to some unforeseen reasons, the Authority shall
determine if the SR can be considered as completed.
x. The Contractor shall note that the implementation of a SR may be
carried out on a one-time basis or in phases, to be specified by the
Authority.
xi. The SR shall be subjected to User Acceptance Tests (UAT) in the
UAT environment, unless otherwise agreed by the Authority.
xii. The additional costs for the maintenance and support services for all
completed SRs shall be deemed to be included in the annual cost for
the application maintenance and support services.

5 PROBLEM ANALYSIS, RESOLUTION AND MANAGEMENT
5.1 Problem Management
The Contractor shall follow the Problem Management Procedure endorsed by the
Authority.
The Contractor shall provide remedial support the application systems for correction
of any system failure or system malfunction. The Contractor shall:
Respond to the Authority within the Response Time specified in Table upon receipt
of notification from the Authority or any other parties regarding any system failure
or any system malfunction.
Make such repairs and adjustments to and replace such parts of the Systems as
may be necessary to restore the Systems to its original working order within the
Resolution Time specified in this Table.
Problem Management Timeline based on Severity Level
Severity Status
Response Time Resolution Time
Level Reporting
1 Within 2 hours Every 4 hours Within 24 hours
Within 1 working Within 4 working

2 Daily
day days
End of
Within 3 working Within 7 working
3 Problem
days days
Resolution
The resolution time shall include implementing a bypass solution. The Contractor
shall implement the permanent solution with full functionality within seven (7)
working days from the implementation of any bypass solution(s) unless otherwise
mutually agreed with SLA.
Severity levels are priority levels assigned to the problem based on urgency,
number of users affected, type and extent of service disrupted and availability of a
workaround or fallback. When a problem is communicated to the Contractor, the
Contractor shall assign the severity level of the problem based on Authority’s

severity definition. Authority reserves the right to re-classify the severity levels if the
needs arise.
The definition of the Severity Level is as follows:

(a) Severity 1
(i) Impact on Business Operations:
• Affects SLA to the extent it is unable to perform its business
function;
• Result in negative publicity to the Government and its agencies;
and
• Cause a significant degradation in the mission capability to the
extent that although SLA is able to perform its regulatory
function for the duration, the effectiveness of the function is
significantly reduced
(ii) Effect on Key Decision-Making Users / Stakeholders:

• Affects VIPs (Directors and above)
(iii) Disruption to Public or User Base at Large:

Creates public or user base inconvenience/alarm/chaos and is
time-critical
(iv) Impact on Organisation:

• Result in significant damage to SLA’s assets;
• Result in significant financial loss;
• Result in significant harm to individuals; and
Cause exceptionally grave or serious damage to national
security
(b) Severity 2
(i) Impact on Business Operations
• Affect a particular process or the System for which there are
existing alternatives to by-pass the incident;
• Affect other agencies but can be contained easily with no
negative impact on the rest of Government; and
Cause some degradation in mission capability and
effectiveness of SLA
(ii) Disruption to Public or User Base at Large

• Some public or user base inconvenience but not time-critical
(iii) Impact on Organisation

• Result in some damage to SLA assets;
• Result in some financial loss; and
• Cause some damage to national security

(c) Severity 3
(i) Impact on Business Operations
Disruption of service that has minimal or no impact on SLA’s
ability to perform its function
(ii) Disruption to Public or User Base at Large

• No inconvenience to public; and
• Inconvenience is contained within a specific user in the user
base
(iii) Impact on Organisation

• Result in no damage to SLA assets;
• Result in no financial loss; and
• Cause no damage to national security
The “Response Time” shall begin from the time or date the problem is
communicated to the Contractor’s single point of contact, regardless of whether the
single point of contact acknowledges receipt of the message. The message may be
communicated by the System’s helpdesk, any of the Authority’s Helpdesks, the
Authority’s Representative responsible for the system concerned, or any Authority
user through telephone or electronic mail. The “Response Time” ends when a
response is provided by the Contractor for the problem via telephone or electronic
mail to the person who reports the problem. (Refer to illustration below).
The “Problem Resolution Time” shall begin upon communication of the problem to
the Contractor’s single point of contact, regardless of whether the single point of
contact acknowledges receipt of the message. The “Problem Resolution Time” ends
when the problem is resolved and the defect is restored to a satisfactorily working
condition (Refer to illustration below).
Illustration of Response Time and Problem Resolution Time
Problem reported Problem Call Problem

to Supplier responded resolved
RECTIFICATION
Response Time
Problem Resolution Time

The Contractor shall perform a thorough analysis of the problem, which includes
identification of the cause of problem, the systems affected, data or any loss
suffered and the recommended solution.
For Severity 1 problems, the Contractor shall provide in writing a preliminary report
to explain the incident the following working day. Subsequently the Contractor shall
provide a post incident review report to explain in detail the cause of the incident,
the corrective actions taken and the solutions to prevent the incident from recurring,
within five (5) working days after the incident has been rectified.
The Contractor shall provide a mechanism and substantiate to the Authority that
Service Levels are met. There must be proper acknowledgement and monitoring of
all reported defects and problems by the Contractor. The Contractor shall be
responsible to ensure that the Authority's Representative is kept updated on the
latest status of the reported defects or problems without being prompted.
The Contractor shall work with all parties designated by the Authority and take
whatever actions to resolve all problems.
In the event of any dispute on the cause of the problem, the Contractor shall
demonstrate and prove services rendered within the scope of this Contract is not
the cause of the problem. The Contractor shall continue to work with the relevant
parties to resolve the problem.
The Contractor shall schedule problem reviews to track unresolved problems and
provide rectification effort to prevent problem from recurring. The Authority shall
specify frequency of such reviews.
The Authority reserved the rights to impose liquidated damages of Five hundred
(S$500) per occurrence of failure to meet Resolution Time for Severity Level 1
incidents up to a maximum of 5 incidents for each calendar month.
5.2 Escalation Process
The Contractor shall follow the escalation guidelines specified with the Authority’s
Quality Management System (QMS) escalation procedure via electronic mail or

telephone/ SMS. The escalation procedure shall be given to the Contractor upon
award of the contract.
For problem under Severity 1, the Contractor shall inform the Authority immediately
through escalation process and shall brief the Authority on the causes, area of
impact and lead-time for recovery within the Response Time specified in Table 10.
The Contractor shall note that the severity of a problem may be escalated based on
circumstances such as high impact to user's operations. The Authority reserves the
right to vary the recovery time when the need arises.
The Contractor shall notify the Authority Helpdesks when any application system is
not available due to application problems.
The Contractor shall escalate any Infrastructure problems back to the relevant
Authority’s Helpdesk if the problem is determined to be caused by the Infrastructure.
Currently, Authority monitors the effectiveness of Authority’s Helpdesks based on

the mis-escalated calls to the Contractor. Mis-escalated calls are defined as
answers found in the Frequently Asked Questions (FAQ) prepared by the
Contractor. The Contractor shall assist the Authority by providing the necessary
information on mis-escalated calls.
The Contractor shall attend meetings with the various Authority’s Helpdesk
Managers if there is system instability or whenever there is a need to close up the
escalation gaps between the Contractor’s Helpdesk and the Authority’s Helpdesks.
The Contractor shall attend meetings initiated by Authority together with the
Authority’s Helpdesks to discuss on the major problems or issues encountered by
users.
5.3 Problem Management System
The Contractor shall propose a Problem Management System to enable its staff to
log, update and track the status of the problems and major support activities.
Where problems are communicated to the Contractor through the Helpdesk or via
telephone or electronic mail from the Authority user directly, the Contractor is

expected to log all such problems reported into the Problem Management System
and shall respond to the problem as stipulated in Table 10.
The Contractor’s helpdesk shall provide incident numbers to the users or Authority’s
Helpdesk who have reported the problems.
The Authority may from time to time request the Contractor to locate specific type
of problems or Helpdesk calls logged by specific users. The Contractor shall be able
to extract and print this information from the Problem Management System.
For any problems/defect and resolution, the Authority’s Representative shall be

updated of its status according to the timing specified in Table 10.
All problems/defects shall be tracked. There must be proper acknowledgement of

all reported system errors and encountered problems and monitoring of the status
of the reported errors and problems by the Contractor.
The Problem Management System shall be able to capture the following

information:
(a) Caller information (Name, Department, Telephone number, Location, Email
address);
(b) Date and time of user/Authority Helpdesk call;
(c) Type/Category/Sub-category of problem;
(d) Problem description;
(e) Details of problem resolution;
(f) Date and time of response;
(g) Date and time of problem resolution;
(h) Date and time of problem closed; and
(i) Severity of problem.
The Contractor shall also provide an analysis of the problems encountered and
propose actions to prevent these problems from recurring, and pre-empt similar
problems from occurring.
The Contractor shall be measured on its Service Level for production support via
the Problem Management System.
The Problem Management System shall be made available to the Authority’s

Representative as and when needed.
6 PROJECT MANAGEMENT
6.1 Project Organisation

The Contractor shall submit a detailed project structure clearly defining the duties
and responsibilities of all the personnel assigned to the Contract. The project
structure shall be subjected to the Authority’s endorsement.
The Contractor shall designate a Project Manager who shall have overall
responsibility for managing and co-ordinating the performance and delivery of the
Services in the Contract. The Project Manager shall have at least (7) years of IT
Project management experience. The Project Manager shall be subjected to the
Authority’s approval. The Project Manager(s) shall be the single point of contact for
the Authority’s Representative.
In addition to the Project Manager, the Contractor may designate Project Lead(s) to
manage the team(s) awarded the respective scope of work in the Tender. The
Project Lead(s) shall have at least five (5) years of experience in managing project
teams of similar scale and nature with this tender. The Project Lead(s) shall have
good project management, supervisory and communication skills. The Contractor’s
designated Project Lead(s) shall be subjected to the Authority’s approval.
6.2 Contractor Team Composition

The Contractor shall provide the optimal manpower team required to meet the scope
of works stipulated.
SLA will review and approve the on-site support personnel. SLA will provide the
office space, basic furniture and shared desktop/laptops for connectivity to SLA’s
user acceptance test environment or SLA’s staging environment.
The Contractor shall ensure that it already has trained and experienced key
personnel fully capable of delivering the services to meet the requirements. A list
of the personnel, their qualifications and experiences, roles and responsibilities shall
be included in the tender proposal. The submission is to be done according to the
format as specified in Annex V of Part 3 – Guidelines for Tender.
All personnel assigned during the Contract Period shall be subjected to security
clearance and approval by the Authority.
The Contractor shall note that the proposed team shall be very conversant or self-
motivated to update itself on the latest technology / operating system trends as
systems are constantly upgraded to meet technology changes.
The Authority reserves the right to interview the proposed Contractor team
members.
6.3 Role of Contractor

The Contractor shall monitor and manage effectively any Sub-contractor that has
been selected in the discharge of their duties to meet the requirements established.
All matters that require interface between the Sub-contractor shall be coordinated
by the Contractor to ensure harmony in the relationship among all parties concerned
and to establish a common understanding of the Authority’s requirements.
The Authority may engage other Contractors to undertake works related to or supply
hardware and software intended to integrate with the IT Infrastructure. The
Contractor shall co-operate fully with all such Contractors to ensure proper
integration and interoperability of the IT Infrastructure with the works, hardware, and
software.
The Contractor shall undertake full responsibility for the quality of work produced by
his team and the Sub-contractors. This includes ensuring that there is consistency
and uniformity in the different works produced by his team and the Sub-contractors.
The Contractor shall report to the Authority periodically on the progress of the
Services. The nature and frequency of the progress reporting shall be determined
by the Authority.
The Contractor shall prepare monthly progress and status reports, supplementary
documentation, and if applicable, performance/fault analysis reports required by the
Authority.
The Contractor shall maintain records of all work activities including proper
accounting and administrative records of all services performed during the
contractual period.
The Contractor shall ensure that staffs observe security and safety regulations in
accordance with the Official Secrets Act and the Authority security policies.
The Contractor shall ensure that only appropriate personnel are assigned to perform
any services under the Contract and they are security cleared to the appropriate
level by the Authority before commencing the performance of such services.
The Authority’s Software comprises software in which the proprietary rights belong
to the Authority. The Authority shall permit or obtain all consents necessary (as the
case may be) and necessary system / operating manuals for the Contractor to
access, maintain and operate all such software.
The Contractor agrees not to use the Authority’s Software directly or indirectly other
than in connection with the provision of services under this Contract.
The Contractor shall not disclose any of the Authority’s Software or supply any copy
to any third person other than in the performance of services under this Contract.

The Contractor shall not permit any copy of the Authority’s Software to be made
except for reasons of security and backup. All such copies shall be returned to the
Authority in the event of expiry or termination of services.
All information and data (including any customised software), which relates to the
Authority, whether contained in the Authority’s data files or otherwise (the
“Authority’s Data”) is the exclusive property of the Authority. Upon termination or
expiration of this Contract, the Contractor shall return to the Authority all of the
Authority’s Data in the Contractor’s then existing machine-readable format and
media, and shall also ensure that no part or copies of the Authority’s Data remains
in its possession, custody or control.
The Contractor shall procure own software licenses for SIT or any other
environments, except for software licenses in both Production and UAT
environments which shall be supplied by the Authority.
The Contractor shall Middleware software FM support for the proposed solution.
6.4 Office in Singapore
The Contractor shall have an office in Singapore and have technical experts
resident in Singapore who can provide consultancy and support on the
development, implementation and maintenance of the System. SLA shall not bear
any expenses involved in bringing in overseas expertise to provide consultancy in
problem resolution at any phase of the Contract.
In the event that the Contractor is not the product distributor of the proposed
solution, the product distributor shall have an office with adequate technical support
staff within Singapore, to support the Contractor on matters relating to the proposed
solution. Product distributor shall have consultants represented in the project team.
6.5 Software Development Facility
Development works, unit testing and System integration testing shall be done off-
site within Singapore.
The Contractor shall provide the development facility, including the necessary
hardware and system software for the development, PGP, SWP and maintenance
phase at their own cost.
The Contractor shall ensure the confidentiality and integrity of the development
facility and the data according to the security requirements specified.
The Contractor shall furnish detailed procedures to assure SLA that the information
of the application issued by SLA are safeguarded against unauthorised access, and
are returned to SLA upon termination/ expiry of the Contract.

SLA shall be given full and direct access to the development facility at any point of
time.
6.6 Access to the Premise of SLA
The Contractor shall specify the number of staff who will be onsite and it will be
subjected to approval by SLA.
Access will only be granted during office hours. The only exception will be during
System cut-over, which will happen over weekends.
6.7 Project Management Plan

The Contractor shall update Project Management Plan to reflect planned and actual
completion dates. All revised Project Management Plan shall be subjected to
Authority’s approval.
The Project Management Plan shall include activities to be carried out by the
Authority as well as all other personnel whose actions are required. The Project
Management Plan shall include a diagram depicting the reporting structure and the
key personnel who shall be involved in the project. It shall define clearly the roles
and responsibilities of all personnel assigned by the Contractor to the project and
how each project team interacts with one another to deliver the desired Services.
6.8 Progress Reporting

The Project Manager shall submit monthly progress report to the Authority.
All formats of the progress reports shall be submitted by the Contractor for approval
by the Authority.
The progress report shall cover the following items:
(a) Performance of service levels;

(b) Major milestones achieved or major capabilities delivered;
(c) Problems encountered and project delays;
(d) Status of problems reported;
(e) Progress on tasks and services requested;
(f) Total system availability and response time;
(g) Job overruns and batch job failures;
(h) Monthly analysis of trends; and
(i) Any other details requested by the Authority.

The Contractor shall provide management reports that include monthly status
reports of all problems reported and queries raised. Information such as the date of
the problem reported, date of the problem resolved, status of problem, cause of the
problem and some details on the problem and corrective action taken shall be
included.
The Contractor shall be responsible for informing the Authority earliest possible, of
any impending slippage in the delivery dates and any matters likely to impede the
progress of the project. Recommendation shall be put forth, by the Contractor, on
the alternatives available.
The Project Manager shall be responsible for proposing the time and agenda for
each progress meeting in accordance with the milestones, which will be approved
by the Authority before implementation. The Project Manager must be prepared for
each progress meeting with the necessary details for discussion.
All minutes of progress meetings shall be produced by the Project Manager and
presented, within three (3) working days, to the Authority’s representative(s) for
endorsement.
6.9 Mobilisation / Replacement of Contractor’s Personnel

In the event of a need for replacement of key Contractor personnel, the Contractor
shall seek approval from the Authority in writing at least one (1) month prior to the
date of replacement, indicating the personnel to be replaced, reasons for the
replacement and particulars of the new personnel who shall be assuming the
responsibilities concerned. The proposed personnel must be of equal or higher
qualification and skill level of the personnel that is leaving. The Contractor shall also
prepare a detailed replacement/handover plan to be submitted to the Authority. The
Authority reserves the right to accept or reject the proposed replacement personnel.
The Contractor shall be responsible for training the successor to be technically

competent to carry out the work. The replacement personnel must be available for
at least three (3) weeks for the existing personnel to handover his responsibilities
and duties. The training shall be conducted concurrently with the ongoing normal
maintenance support required of the Contractor without affecting the maintenance
service level. The cost incurred for the provision of the replacement personnel
during the handing over period shall be borne by the Contractor.
The Contractor’s Project Manager must supply evidence to the Authority’s

Representatives that the project handover is duly completed before releasing the
personnel.
The Authority’s Project Handover Procedure must be adhered. Where alternatives

are proposed by the Contractor, the procedure must be approved by the Authority.
The scope of the handover plan, for any types of handover, shall include the
following:
(a) Processes and procedures;

(b) Roles and responsibilities;
(c) Schedule Plan; and
(d) Outstanding requests/activities.
6.10 Data Dictionary

The Contractor is required to build and maintain the data dictionary in accordance
to SLA Data Administration Policy/ Metadata Standards throughout the project
lifecycle.
6.11 Documentation Deliverables

The Contractor shall ensure system documentation is updated for any defect
rectification and change/ enhancement, at no additional cost to SLA.
The Contractor is required to update the Helpdesk Handover Documentation as and

when there are any changes in the application due to system enhancement,
upgrading of application version or frequently asked questions.

7 EXIT PLAN
The Contractor shall propose and submit an Exit Plan six (6) months upon award of
the Contract. The Exit Plan and the detailed schedule shall be subjected to the
Authority's approval.
The Exit Plan shall include the following activities:
(a) Define an overall schedule for the Exit Plan;

(b) Handover complete and up-to-date documentations on the Authority's
resources and corresponding process workflows developed by the
Contractor during the management of the Services. These documentations
shall include:
i. Details on configuration items;
ii. Third-party Contractor’s contact information and corresponding
Service Level Agreements (SLAs); and
iii. Warranty and maintenance information of all Hardware and Software;
(c) Handover complete and up-to-date documentations on the facilities and

layout of the Authority's ICT resource setup;
i. Define the roles and responsibilities of all parties involved in the
transition;
ii. Report on the status of any work-in-progress and problems that have
not been resolved;
iii. Provide contact details of all key personnel involved in the exit
exercise;
(d) Report on any cost implication in the transfer of resources (e.g. hardware
and software licenses) for the effective management of the Services and
(e) Provide handover briefing sessions for the new vendor.
The exit period shall be managed and supervised by the Authority.
The Contractor shall ensure that all activities in the Exit Plan are completed before
the expiry of the Contract Period.
The Contractor shall provide adequate resources to ensure that the SLAs are
maintained during the handover period.
The Contractor shall co-operate with the new vendor to ensure that the SLAs are
maintained during the handover period.
The Contractor shall ensure that all activities in the Exit Plan are completed before
the expiry of the Contract Period. Any outstanding tasks beyond the Contract Period
shall be completed within two (2) months after the expiry of the Contract Period, at
no cost to the Authority.

ANNEX A : SUMMARY OF APPLICATION SOFTWARE

Application SIRENT WEB
Name
Implementation Sept 2014 Tech Refreshed

Date
June 2020 Web Refreshed
June 2021 Migrated to Cloud
Application The System provides precise GNSS (DGNSS) services

Overview subscription on correction data on Real Time Kinematics (RTK),
Network-RTK, Differential GNSS (DGNSS), post processing data
and archive data purchases.
The Web Portal promotes the Prove of Concept trail, Free Services
trial and Business Development Trail application.
The Web Portal provide subscriber the subscription information.
The Web Portal provide the admin pages for operation and finance
management.
The mobile apps companion (both IOS and Android) provide the
notification, location base nearest reference station suggestion and
link to NEA on weather information to facilitate subscriber’s work on
the field.
Key The web application is an internet web for different business

Functions/Mod operation
ules
1. Home
2. About SiReNT
3. Services
4. Reference Stations
5. SiReNT Companion App
6. FAQ
7. Member Pages
➢ Home (Reference station)
➢ My Subscription

• Subscription & Invoices

• Sessions & Tokens
• Account Details
• POCS Scheme Report
➢ SiReNT Archive Data
➢ Atmospheric Information
• I95 Ionosphere
• IRIM/GRIM
• IPWV Map
• Station Chart
• IPWV Contour Map
• IPWV Surface Map Animation
• TEC Contour Map
• IPWV Surface Map Animation
▪ PP On-Demand
• Purchase Post Process Data (Reference Data Shop)
• Post Process Data History
8. Administration
➢ Inbox
➢ Subscription Management
▪ Subscriptions
▪ Applications Overview
▪ User Sessions
▪ Create Subscription
▪ Manage Subscription
➢ User Management
▪ SP/CP Users
▪ User Account Information
▪ Organisations
➢ Announcement Management

▪ Announcements
▪ Create Announcement
➢ Push Notifications Management
▪ Messages
▪ Devices
➢ SiReNT Reports Management
▪ SiReNT Reports
▪ Transaction & Revenue Reports
▪ Subscription Terminations
➢ DGNSS/RTK
▪ VRS iScope Live
▪ VRS iScope
➢ Finance Management
▪ DataFile
▪ Update
• Upload Return File
• Update Payment
▪ Reports
▪ Transaction Reports
▪ User Statement/Invoices
➢ SAP ID
No. of reports Online 11
Batch 3
Interface Finance data file manually download and upload to the web
descriptions (if
any)

Technologies OS Platform: Windows 2019

Used:
Application Platform: .Net
Database Platform: MS SQL 2017 Enterprise Edition
Refer to Part 2A para 3.1.17.
User base Total Active Subscription = 252
CorpPass User = 168
SingPass = 51
Estimated 20-30
number of
concurrent
users
Types of .Net
Application
Program
Estimated No of 100 web pages

Web/App/DB
Objects/ 30 major functions (estimates)
Functions/Jobs Total No. of Database: 6
Total Size of Database: 100gb (estimates)
Estimated No of Around 30,000

Lines of Code

System The System response and turnaround time shall meet the following
response times criteria in 95% of cases:
S/N Description Turnaround Time Remark

Local Client/Server s
Norm Pea
al k
1 On-the-fly 10 15 20 For
generation of 1- RINEX
hour RINEX file file with
15
seconds
tempora
l
resolutio
n.
2 User account - 2 3 Nil
authentication
3 Daily backup of 2 - - Nil
entire database hours
4 Daily export of 15 - - Nil
RINEX file for minute
archiving s
5 Switching to 10 - - Nil
Failover/Redund secon
ant system ds
Notes: Turnaround time – The elapsed time between the command

issued and job completed.
Normal – 1-20 concurrent users’ network
Peak – 100 concurrent users on the network
Timing – In seconds(s), unless otherwise stated
The System shall maintain the following performance criteria for

users on-site who are using Network RTK and conventional RTK
positioning modes:
(a) To be able to initialize within 180 seconds (also known as

Time-To-Fix (TTF)) for a site with the following conditions:

i. Elevation Mask at 15 degrees
ii. 7 satellites or more are observed
iii. PDOP less than 3
(b) To be able to achieve positioning accuracy as follow:
i. Horizontal position deviate from ISN value not more than

0.50m
ii. Horizontal standard deviation not more than 0.030m
The Supplier shall develop scripts to simulate loads to test the

System performance and demonstrate to the SLA that the System
meet the performance requirements.
Average and
Peak
Production Average Offsite /Onsite No. of Problems Reported for
Support Efforts and Peak Production that month
Support Support/Proble
Efforts m Management (By Severity Level)
for past Effort (man-day) Severit Severit Severity 3
6 for that month y1 y2
months
Offsite: 3
Average 0 0 1
month Onsite: 4
Offsite: 3
Peak 0 0 2
month Onsite: 6

Actual System Actual System Availability:

Availability
System Availability System Availability
for last 6 months
April 2021 100%
May 2021 100%
Jun 2021 100%
Jul 2021 100%
Aug 2021 100%
Sep 2021 100%

ANNEX B : SUMMARY OF MOBILE APPLICATION

Application Name SIRENT MOBILE APPS
Implementation Sept 2014 Tech Refreshed

Date
June 2020 Web Refreshed
June 2021 Migrated to Cloud
Application The SiReNT mobile app is a companion app for users of the
Overview Singapore Satellite Positioning Reference Network (SiReNT)
services. SiReNT subscribers can view their subscription
information, usage details, Reference Stations information and other
useful information for mission planning. Non-subscribers are
welcome to use the free information included in this app.
Key The web application is an internet web for different business

Functions/Modules operation
1. Home
➢ Summary
➢ Subscriptions
➢ Bills
➢ Quick Links
2. About
➢ About SiReNT
➢ Subscribing to SiReNT
➢ FAQ
➢ Terms of Use
➢ Privacy Statement
➢ Contact Us
3. SiReNT Stations
➢ Network Information’s
➢ Reference Map
➢ Reference Station (Detail)
➢ SiReNT 360

4. VRS iScope Live

5. PSI
6. Weather Forecast
7. Login
No. of reports Online 0
Batch 0
Interface Nil
descriptions (if
any)
Technologies OS Platform: Android & iOS

Used:
Application Platform: Java & Objective C
User base Total Active Subscription = 252
Estimated number 20-30

of concurrent
users
Types of Java & Objective C

Application
Program
Estimated No of 15 views
Web/App/DB
Objects/ 7 major functions
Functions/Jobs
Estimated No of Android: 9000 (estimate)

Lines of Code iOS: 10000 (estimate)

Average and Peak

Production
Support Efforts Average Offsite /Onsite No. of Problems Reported for
and Peak Production that month
Support Support/Problem
Efforts Management (By Severity Level)
for past Effort (man-day) Severity Severity Severity 3
6 months for that month 1 2
Offsite: 3
Average 0 0 1
month Onsite: 2
Offsite: 6
Peak 0 0 2
month Onsite: 3
Actual System Actual System Availability:

Availability
System Availability System Availability
for last 6 months
April 2021 100%
May 2021 100%
Jun 2021 100%
Jul 2021 100%
Aug 2021 100%
Sep 2021 100%

ANNEX C : REFERENCE STATIONS INFORMATION








GLOSSARY OF TERMS
Systems
SiReNT – Singapore Satellite Positioning Reference Network
Organisation
SLA – Singapore land Authority
SGD - Survey & Geomatics Division
Others
ADSL – Asymmetric Digital Subscriber Line
CMR – Compact measurement Record
COTS – Commercial-Off-The-Shelve
DBMS – Database management System
GDC – Government Data Centre
GNSS – Global Navigation Satellite System
GPRS – General Packet Radio Service
GPS – Global Positioning System
GSM – Global System for Mobile Communications
HTTP – HyperText Transfer Protocol
IP – Internet Protocol
ISN – Integrated Survey Network
LAN – Local Area Network
LOA – Letter of Acceptance
LSVY – Land Survey Division (SLA)
MTBF – Mean Time Between Failure
NMEA – (NMEA 0183) National Marine Electronics Association
NTRIP – Networked Transfer of RTCM via Internet Protocol
PGP – Performance Guarantee Period
QMS – Quality Management System
QZSS – Quasi Zenith Satellite System
RINEX – Receiver Independent Exchange
RTCM – Radio Technical Commission For Maritime
RTK – Real Time Kinematic
SD – System Downtime
SOT – Scheduled Operating Time
SWP – System Warranty Period
TCP – Transmission Control Protocol
UAT – User Acceptance Test
WAN – Wide Area Network

06 Part 2A Requirement Specifications

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

06 Part 2A Requirement Specifications

Uploaded by

Copyright:

Available Formats

Part 2A REQUIREMENT SPECIFICATIONS

TENDER REF NO.: PT21-27/7-9/27 RS/1

1.2 Scope of Tender ............................................................................................................................ 4

1.3 Domain Expertise .......................................................................................................................... 5

1.4 Eligibility of the Contractor .......................................................................................................... 5

2 OBJECTIVE OF THE SYSTEM .................................................................................................................... 6

3 DESCRIPTION OF CURRENT SYSTEM .................................................................................................... 8

5 PROBLEM ANALYSIS, RESOLUTION AND MANAGEMENT ............................................................. 23

5.2 Escalation Process ..................................................................................................................... 26

5.3 Problem Management System ................................................................................................... 27

6 PROJECT MANAGEMENT ......................................................................................................................... 28

6.2 Contractor Team Composition .................................................................................................. 29

6.3 Role of Contractor ....................................................................................................................... 29

6.4 Office in Singapore ..................................................................................................................... 31

6.5 Software Development Facility .................................................................................................. 31

6.6 Access to the Premise of SLA ................................................................................................... 32

6.7 Project Management Plan .......................................................................................................... 32

6.8 Progress Reporting ..................................................................................................................... 32

6.9 Mobilisation / Replacement of Contractor’s Personnel .......................................................... 33

6.10 Data Dictionary ............................................................................................................................ 34

6.11 Documentation Deliverables ...................................................................................................... 34

7 EXIT PLAN ..................................................................................................................................................... 35

TENDER REF NO.: PT21-27/7-9/27 RS/2

ANNEX B : SUMMARY OF MOBILE APPLICATION .......................................................................................... 43

TENDER REF NO.: PT21-27/7-9/27 RS/3

1.2 Scope of Tender

As SLA is currently supplying GNSS Post-Processing data to SiReNT subscribers,

The Contractor, besides providing the infrastructure’s software and hardware,

TENDER REF NO.: PT21-27/7-9/27 RS/4

1.3 Domain Expertise

1.4 Eligibility of the Contractor

The Contractor is required to have experience in the following technologies and

1 GNSS Knowledge ▪ RTCM

▪ GNSS Network Software

▪ TIM (Trimble Integrity Manager)

2 Database ▪ e.g. MSSQL

3 Web Based ▪ Web-service development, e.g. IIS

TENDER REF NO.: PT21-27/7-9/27 RS/5

4 Core Programming • Software development experience.

5 File Transfer e.g. Secure Copy SSH, Secure FTP SSH

6 SMS gateway ▪ SMS Gateway Software Development

8 Electrical and ▪ Electrical and Electronic Engineering

9 GNSS Reference ▪ Track records in providing and

10 Beginner to ▪ Able to understand the network routing

▪ Able to communicate to cloud infra

2 OBJECTIVE OF THE SYSTEM

The primary objective of the System is to serve as the fundamental infrastructure to

TENDER REF NO.: PT21-27/7-9/27 RS/6

The System shall comprise the following:

TENDER REF NO.: PT21-27/7-9/27 RS/7

3 DESCRIPTION OF CURRENT SYSTEM

3.1 Current System

The infrastructure consists of 8 permanent GNSS reference stations, six of which

Information on the four major services:

(a) Post Processing (PP) On-Demand

(b) Post Processing (PP) Archive

TENDER REF NO.: PT21-27/7-9/27 RS/8

(c) Real-Time Kinematic (RTK)

i. Using SiReNT RTK, field operators can determine real-time positions

(d) Differential Global Navigation Satellite System (DGNSS)

i. Similar to SiReNT RTK, SiReNT DGNSS allows field operators to

iv. The SiReNT webpage provides information on how to subscribe to

TENDER REF NO.: PT21-27/7-9/27 RS/9

automation, self-mobility platforms development and operations, fleet and asset