pre-bid query responsesdoitc.rajasthan.gov.in/administrator/relateddocument/prebid... · s.no. rfp...

F4.3(177)/RISL/Tech/16/IV/8403; Dated: 22.12.2017 2017_RISL_88266_1

RIS1718SLOB00118 NIB Code RIS1718A0129

Time 03:00 PM

S.No. RFP Page

No.

RFP Rule No. Rule Details Query\Suggestion\Clarification RISL Answer

1 14 3. PRE-

QUALIFICATIO

N/ ELIGIBILITY

CRITERIA

6. Bidder should have experience in

providing SMS and USSD services to at

least 3 state government

department/central government

department /PSU/Telecom Operator in

India in last 3 years from the publish

date of RFP.

At-least one project in each SMS and

USSD.

Request you to please clarify the below as the statements are

conflicting with each other:

1. Providing SMS and USSD services to at least 3 state

government

2. At-least one project in each SMS and USSD

Does this mean that that bidder should have alteast 3

references of either SMS or USSD and atleast one for each?

We request you to modify the clause as below (highlighted the

changes in red color)

"6. Bidder should have experience in providing SMS or USSD

services to at least 3 state government department/central

government department /PSU/Telecom Operator in India or

abroad in last 3 years from the publish date of RFP.

At-least one project in each SMS and USSD.

Please refer the updated

RFP

Pre-Bid Query Responses

Title Procurement of USSD and SMS Services for Unified Communication Gateway (e-Sanchar 2.0)

NIB Reference No. e-Proc Tender Id

Unique Bid No.

Pre-bid Meeting Date 02.01.2018

2 14 3. PRE-

QUALIFICATIO

N/ ELIGIBILITY

CRITERIA

Value of one of the project should be

at-least Rs.10 crore OR 2 projects each

of at-least Rs. 5 crore.

As telecom operator references are usually on revenue share

basis, the value of the project can't be proven directly. Hence,

we request you to modify the clause to reflect the capability

instead of value.

Request you to modify the clause as below to reflect capability

of the system:

"Vendor should have experience of implementation of SMS &

USSD Platforms with delivers a combined volume of more than

60 crore messages per month for a customer either within India

or outside".


RFP

3 15 Details of work

(SoW)

An USSD Interface and USSD Menu

Manager systems are to be

provided/build and maintained by the

SI and deploy at RSDC

Here selected vendor is considered to be SI, right? Yes. The selected vendor

shall be termed as System

Integrator (SI)

4 90 Annexure 11 SMS system should also work on

SIGTRAN if provisioned by the backend

SMSC

Request you to remove the mentioned requirement, as the

solution is not being deployed in operator data center. SIGTRAN

connectivity is not provided by operators outside the telco data

center.


RFP

5 91 Annexure 11 13. System should support standard

connectivity protocols: SIGTRAN or

USSD over SMPP or any other custom

operator specific protocol over TCP,

UDP or HTTP




center.


RFP

6 92 Annexure 11 26.

System should also work on SIGTRAN if

provisioned by the backend TSP




center.


RFP

7 91 Annexure 11 10. System should provide a

functionality to convert an existing

hierarchical XML structure to

corresponding USSD menu

Can you please provide the documentation related to existing

XML, so that we can adapt our platform to this requirement?

The structure shall be

shared with the selected

SI

8 100 Annexure 17 Please specify your choice of system

software from the list of system

software available at the RSDC

Please confirm that RISL will provide licenses for any of these

softwares listed in this page, along with applicable support/AMC

and vendor need not consider the cost for these softwares in

their commercials


RFP

9 75 Financial Bid

Format

13. Incoming USSD Transactions & 14.

Outgoing USSD Transactions

Following are the concerns with USSD Connectivity:

1. Connectivity from all operators is needed for USSD.

2. Each operator may propose different charges for USSD

3. Some operators may not provide connectivity unless a letter

is issued from RISL.

Considering the above, we request you to ammend the below

clauses in the RFP:

1. Remove USSD transaction related cost from the RFP and

modify the scope as "vendor needs to integrate with all the

operators for USSD. RISL will support with the necessary letters.

RISL will pay for the USSD tranaction cost directly to the

operators based on actuals".

As per RFP

10 75 Financial Bid

Format

2. Outgoing SMS The SMS price to be quoted should be for regular transactional

SMS or for G2C government (TRAI exempted) sender id? Please

confirm

All SMSs shall be of G2C

nature

11 14 Pre-

Qualiffication/E

ligibility Criteria

Bidder should have experience in

providing SMS and USSD services to at

least 3 state government




date of RFP.

As infobip has deployed several USSD solution in global and we

do have few international reference. Please kindly consider this

as one of the tender requirement.


RFP

12 15 USSD Scope of

Work

As Infobip is ready with all USSD technology and platform, who

will be providing the USSD connectivity service from local

Mobile Operator in India ?

Vendor shall be

responsible to provide

the USSD services to RISL.

Connectivity with local

mobile operator shall be

provided by vendor

13 90 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 8

System should work independently

from the backend TSPWe are not able

to run USSD service without

connectivity provided from TSP.

All service provider are not able to run USSD service without

connectivity provided from TSP.

Suggest to remove this requirement

The USSD System

developed and/or

deployed by SI should be

capable enough to work

with different TSPs if

required

14 91 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 16

System should support SMPP / HTTP

protocol for integration with SMSC and

HTTP / VXML integration with IVR to

provide USSD Call-back kind of services

Please explain more in the use case of USSD call back function. As per RFP

15 92 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 32

System should support automatic

pagination if required

Please explain in more detail regarding pagination and what is

the related use case ?

If USSD menu is larger

then the requesting

mobile screen, the menu

should be paginated

automatically as per the

client screen size

16 92 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 33

System should support subscriber

activated pause of USSD sessions

Please explain in more detail regarding subscriber activated

pause and what is the related use case ?


RFP

17 92 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 34

System should support resume of

expired sessions

This feature is depend on end-user device. Suggest to remove

this requirement.


RFP

18 92 ANNEXURE-11

b.

Unstructured

Supplementary

Service Data

(USSD) System

(Pull/Push)

Item 35

System should be able to support

content scanning for the

incoming/outgoing data though USSD

Please explain in more detail for the requirement for content

screening.


RFP

19 93 ANNEXURE-11

d. USSD Menu

Manager item

7

Menu Manager would be hosted at

RSDC

we suggest to host our server in Infobip Mumbai DC and

provide managed cloud service model.

This model will benefit RISL for saving hardware and software

O&M cost.

As per RFP

20 93 ANNEXURE-11

d. USSD Menu

Manager item

8

It should manage the user state

machine to keep track of the current

user menu level.

Please explain what is user-state machine System should keep track

of the current state of the

user and should manage

the current menu level

and selection along with

the application data

pertaining to current

session.

21 Is Joint bidding allowed ? It is not specified in the Terms &

Conditions.

As per RFP

22 Functional & Block diagram details of their Unified

Communication Gateway : e-sanchar 2.0 so that we can have

the broader view and also position other possible digital

messaging through Web tracking of their portal, Mobile App &

Browser Push Notification to help their G2C venture.

As per RFP

23 Kindly pitch for Bulk Mailing methodology (Our On-site/Partial

On-site & Cloud based) offering.

As per RFP

24 Kindly check (off-line) possibility of Chat-bot & Analytic

opportunity in e-Sanchar & if yes, ask them to add the same in

the present requirements.

As per RFP

25 5. Ask for a single Panel Dash Board for these alerts to various

departments.

As per RFP

26 6. ISO-9001 & ISO-27001 should be included in their "Eligibility

Criterions".

As per RFP

27 89 SMS Clarification System should be able to support content scanning of the SMSs

being sent/received.

As per RFP

28 89 SMS Clarification What various kind of USSD project & services are running live

with client currently?

Presently, no USSD

services are being used

by RISL

29 89 SMS Clarification System should allow to use a sender id other than the

configured sender ids ?

Sometimes, it may be

required that message be

sent by some other

sender id. So, system

should allow to do so.

30 89 USSD Clarification How currently USSD pull request working in client environment

?

Presently, no USSD

services are being used

by RISL

31 89 USSD Clarification What kind of trigger client is referring to ? "System should

allow to trigger an event on receiving of an USSD pull

request"

Menu Manager should

send an event notification

to the backed application

on receiving of a USSD

pull request

32 89 USSD Clarification What kind of data client is referring to ? "System should allow

to send data against an incoming USSD pull request"

If a user send some

request throgh an USSD

menu, system should be

able to send a reply

message/information in

response back

33 14 3.1 Copies of work orders and

completion/phase completion

certificates issued by the client

organization. Work order(s) should

contain the value of order.

We have agreement with Telecom Operators. Agreement does

not have value of order. We can show invoices.

As per RFP

34 17 4.1.2 The SP shall also deploy additional

hardware and software resources

required for successful implementation

USSD and SMS services

Hardware will be provided by SDC or by SP? Who will own the

hosting of infrastructure?


RFP

35 18 4.3 Configuration, System Integration and

commissioning of SMS and USSD

services as per sec 4.1.2 of the Scope

of Work -> Time Frame (in Weeks) T0 +

3

3-5 days will be required for integration with each of the

operator for USSD. This activity will take atleast 6-8 weeks after

Signing Off the FRS. This time will exclude procurement of

Shortcode for USSD. Every operator has different configuration

mechanism and also approvals take time.


RFP

36 64 7.1.ii Service Level Requirements for SMS

and USSD services

RISL to ensure network and power upkeep for the infra hosted

for the services at SDC and shall not be in SLA of SP


RFP

37 64 7.1.iv Penalty for non-achievement of Service

Level Requirements for SMS services

1. Service outage due to Operator or any service outage due to

uncontrolled conditions like natural calamity or communal

disturbances shall be excluded.

2. Service outage due to connectivity/integration between

eSanchar systems and that of SMS shall not be included in this

SLA


RFP

38 65 7.1.iv Penalty for non-achievement of Service

Level Requirements for USSD

transactional services

1. Service outage due to Operator or any service outage due to

uncontrolled conditions like natural calamity or communal

disturbances shall be excluded

2. Service outage due to connectivity/integration between

eSanchar systems and that of USSD shall not be included in this

SLA


RFP

39 17 4.2.a Shall designate a single point of

contact (available remotely and not

necessarily in the location premises)

equipped with all the required tools/

resources, for handling day-to-day

issues/ problems/ monitoring of the

lines and for co-ordinating with the

nodal officer of source and designated

locations.

RISL will own the responsibility of providing remote access for

the SP SPOC to monitor and control the services.

Remote access shall be

subjected to the RSDC

policies

40 91 Annexure

11.1.b.13

System should support standard

connectivity protocols: SIGTRAN or

USSD over SMPP or any other custom

operator specific protocol over TCP,

UDP or HTTP

From the complete RFP it seems we need to deliver a USSD

service creation application. However, from these statements it

seems USSD Gateway is also required if we need to connect

over SIGTRAN. Please clarify if USSD gateway needs to deployed

in operator network over SIGTRAN.


RFP

41 92 Annexure

11.1.b.26

System should also work on SIGTRAN if

provisioned by the backend TSP

From the complete RFP it seems we need to deliver a USSD

service creation application. However, from these statements it

seems USSD Gateway is also required if we need to connect

over SIGTRAN. Please clarify if USSD gateway needs to deployed

in operator network over SIGTRAN.


RFP

42 P17-4.1 It has been specified that Servers will be provided by RSDC,

Please

confirm if

a) The server instances be Physical server or these will be virtual

servers.

b) Any additional H/w apart from server e.g. Switches, Signaling

servers, Racks, Software Licenses, Public IP, HTTPS certificates

etc will

also be provided by RSDC/RSIL or to be procured by bidder?


RFP

43 Do this system will integrate separately with each department

separately or there will be integration from single point

Single point integration

with Unified

Communication Gateway

would be there

44 P17-4.1.a The major inputs Parameters defined under this clause i.e. User

Circle,

User Type ( Pre-post), current Menu level, Unique identifier are

operator dependent. These can be passed to E-Sanchar only if

these

are available from operator end ? Please confirm ( Also, P93-

Anx11,1.c.3 )


RFP

45 P17-4.2.a Please confirm if RSIL/RSDC to provide Remote connectivity for

Remote monitoring and Support of bidder has to arrange

himself and

build the cost.

Remote access shall be

subjected to the RSDC

policies

46 P18-4.3 Considering integration with all the operators which includes

Short

code provisioning, opening of pass through CLI's etc the defined

3

weeks timelines is too short for this process the same should be

atlest

12 months.


RFP

47 P64-7.1.iii.b There will be dependency on the operator network , natural

climates,

Fiber cuts etc hence, there is a possibility that there might be

few

instances where downtime might be beyond the scope of

Service

provider, hence any downtime due to connectivity should be

excluded

from definition of downtime.


RFP

48 P89-

Anx11,1.a.7

Please explain the exact requirement for the Scanning of

content and

weather it will be offline or online ( Also for P91-Anx11,1.b.35)


RFP

49 P89-

Anx11,1.a.1

0

Pass through CLI is operator dependent and supporting letter

from

DOT should be required in this case

RISL will help the SI in

obtaining necessary govt.

approvals for the project

during the

implementation /

maintenance period

50 P90-

Anx11,1.a.1

5

Deployment of Sigtran means requirement is of SMSC/USSD, Do

RSIL

wants an SMSC/USSD gateway to be deployed ? Sigtran

connectivity

has been mentioned at various instances, Please clarify for all (

e.g.

P91,ANC11,1.b.13 ; P92,ANC11,1.b.26


RFP

51 P91-

Anx11,1.b.8

Please clarify what is meant by "Work independently from the

backend

TSP" in this clause

The USSD System

developed and/or

deployed by SI should be

capable enough to work

with different TSPs if

required

52 P92-

Anx11,1.b.3

3

Please clarify what is meant by "Subscriber activated pause of

USSD

session" in this clause


RFP

53 P91-

Anx11,1.b.3

4

Please clarify what is meant by "resume of expired sessions, is it

relevant to above points i.e.P92-Anx11,1.b.33 .


RFP

54 In case of USSD push, how it will be determined the operator of

a

mobile number. Will access to NPDB will be provided.

It shall be idenfied by the

system of SI

55 For understanding of E-Sanchar system for integration, kindly

provide

the document to have better understanding w.r.t integration

API's.

As per RFP

56 P17-4.1.a For Integration of USSD across Operator for USSD and SMS with

required parameters in the RFP document required specific

permission

from all the operators. For all such permissions and shortcode

RISL to

obtain a letter is required from DOT and the same is to be

addressed

to Telecom operators for below points.

1. Opening of SMS & USSD Shortcode across operators for

MO/USSD

PULL

2. Request forwarding of these shortcodes to our server (over

public

IP if required) over SMPP/HTTP

3. Pass through CLI for MT SMS.

4. Allow MT SMS & Push USSD across operators with adequate

capacity

5. The major input parameters that would be passed from the

USSD

gateway to the e-Sanchar 2.0 platform as mentioned in 4.1.a.

RISL would support the SI

for obtaining of necessary

approvals from GoI/DOT

and in integartion with

other networks

57 P90-

Anx11,1.b.3

As per this clause the system capacity is capped to send 2 crore

USSD

Push/day. The capacity capping is very high against the

expected

requirement of 10 Lakh push /month as quoted in Point.4 SOW .

The

costing against the capped capacity will be high , so kindly

reconfirm

on capacity capping or expected requirement.


RFP

58 P90-

Anx11,1.b.4

System should allow 1000 concurrent USSD sessions, The

capacity

capping is very high against the expected requirement of 10

Lakh

push /month as quoted in Point.4 SOW . The costing against the

capped capacity will be high , so kindly reconfirm on capacity

capping

or expected requirement.


RFP

59 15 4.1 USSD Stack would contains following

components

a. USSD Interface

This component of the platform

interfaces with the operator USSD

platform for receiving the user request.

The operator USSD system will first

receive the user request from the

telecom network and then use the API

provided from this component to send

the user request to the platform.

Below are the major input parameters

that would be passed from the USSD

gateway to the e-Sanchar 2.0 platform:

USSD connectivity between various operators and USSD

interface will be provisioned by RISL?

It shall be provided by SI

60 65 7.2 7.2. Telecom Related Terms

a) All the services in scope shall be

completely adhered to the guidelines

and norms issued by TRAI accordingly.

b) All the messages to be sent using

these services shall be completely of

G2C nature and shall be of

informational type.

c) For SMS services, applicable

exemption for G2C messages shall be

obtained from TRAI accordingly.

Has department already taken exemption benefit approval from

TRAIL/DoT for G2C SMS? In case of yes, we shall consider

passing that benefit while submitting the financial quote else. In

case approval is still not taken, we shall quote full price and

further benefit (as per applicability) will be passed as and when

approval is received.


RFP

61 75 Annexure 7 Financial Bid Format SMS and USSD should have a component with line item for price

of:

Change Request price, Qty Per Man day.

On mutual agreement change request will be evaluated, man

days calculated and paid at this price.

It will impact formula as defined on page 77

It should be the part of

Operation and

Maintenance component

62 75 Annexure 7 Financial Bid Format In case we need to apply for only one component out of SMS

and USSD then we need to quote only for that part of the

Financial Bid format and not for other, please confirm.

As per RFP

63 91 Annexure 11.1.b.3System should be able to send at-least

2 crore USSD push notifications per day

(24 hrs). This would be capped by the

capacity of the underlying

communication channel

In reference to financial bid, requirement is of total 50 Lac USSD

Push. Why we require system of 2 Crore daily capacity. It will

increase

As per

64 15 4 SCOPE OF WORK, DELIVERABLES &

TIMELINES

No where in the RFP it has been mentioned who will pay for the

USSD session. Is it going to be Citizen initiating session or

Government?

In case of Government, how will it settle with Operator?


RFP


TIMELINES

Who will own to get shortcode opened across all operators /

circles? Government or SP?

It is one of the tedious task to get USSD shortcode opened in

every operator coming to single price point and managing the

payments.

How billing to be done where if government will pay to

operators?

SI would be responsible

to obtain the cross

operator connectivity.

RISL will help the SI on

behalf of Govt. of

Rajasthan in such

scenarios.


TIMELINES

How we assume same USSD shortcode will be available with

every operator in every circle?

USSD code shall be

selected after consulting

all operators

67 75 Annexure 7 Financial Bid Format -> Outgoing SMS

quantity 2,00,00,00,000

Is this minimum guarantee that government will pay for in two

years?

How billing is done, consumption basis quaterly or monthly?

What if full quantity is not used in two years?

As per RFP

68 76 Annexure 7 Financial Bid Format -> Incoming USSD

Transaction quantity 2,00,00,000


years?



As per RFP

69 76 Annexure 7 Financial Bid Format -> Outgoing USSD

Transaction quantity 50,00,000


years?



As per RFP

70 90 Annexure 11.1.b.1System should allow to send an USSD

push to any mobile number in India

according to the functionality provided

by the underlying communication

channel

Why do we need to send PUSH to PAN India. Lets restrict to

Rajasthan only. PAN india getting the service opened will be a

project in itself


RFP

71 91 Annexure 11.1.b.2System should allow to receive an

USSD pull request from any mobile

number in India according to the

functionality provided by the

underlying communication channel

Why do we need to send PUSH to PAN India. Lets restrict to

Rajasthan only. PAN india getting the service opened will be a

project in itself


RFP

72 45 Clause No. 11

of General

Terms &

Conditions of

Tender and

Contract

Prices charged by the

Supplier/Selected Bidder for the Goods

delivered and the related services

performed under the Contract shall not

vary from the Prices quoted by the

Supplier/Selected in its Bid.

The Prices shall be subjected to change in case of any change in

the rates of taxes and/or any change in the prices suggested by

TRAI. Request to have this point included.


RFP

73 46 Clause No. 14

of General

Terms &

Conditions of

Tender and

Contract

Copyrights/intellectual property rights

(IPR)

Does that mean we have to

transfer the ownership of the IPR of the platform that we have

developed for providing the Services?

As per RFP

74 59 Rule No. 34 b)

ii.

Transfer of Assets The Software that we have made is for general use. The

Software is not made solely for RISL.

Does this mean that the sofware that we have developed shall

be transferred to RISL? If yes, then, we would request you to

kindly have this clause deleted, as this would lead to restriction

of Services.

As per RFP

75 60 Rule No. 34 d)

i.

Confidential Information, Security and

Data.

The transfer of IPR related documentation cannot be shared

with the RISL as this relates to confidential information of

Bidder.

As per RFP

76 60 Rule No. 34 e) Transfer of Certain agreements The obligations put forth relating to the transfer of agreements,

Access to premises, staffs and employees of Bidder is too

restrcitive and we request for deletion of the said clause.

The Bidder should not be forced to transfer the agreements,

licenses, sub-licenses,etc. in favour RISL.

As per RFP

77 62 Rule No. 35 Settlement of Disputes In case of anyv dispute

the matter shall be resolved by the Standing Committee for

Settlement of Dispute. The Standing Committee

shall be consisting wholly of the employees of RISL.

In this case, it is higly probable that the decision

shall be taken in favour of RISL.

We strongly recommend that, the standing committee either be

constituted with independent members or

the ratio of members be same between RISL & bidder.

As per RFP

78 49 Clause No. 21 Raj Comm. shall have the right to visit

the premises of Bidder and inspect the

goods used for the Services.

We generally do not allow, any of our Clients to visit our

premises.

As per RFP

79 14 3. PRE-

QUALIFICATIO

N/ ELIGIBILITY

CRITERIA

4. Financial Turnover: For the firms

other than the Telecom Service

Providers registered with TRAI, the

average annual financial turnover

of the last three financial year i.e.

2014-15, 2015-16 & 2016-17 should

not be less than 50 crores

We request to kindly amend this clause as "4. Financial

Turnover: For the firms other than the Telecom Service

Providers registered with TRAI, the average annual financial

turnover of the last three financial year i.e. 2014-15, 2015-16

& 2016-17 should not be less than 40 crores"

As per RFP

80 90 14 System should be able to integrate

with any backend SMSC

Please explain backend SMSC A short message service

center (SMSC) is the

portion of a wireless

network that handles

SMS operations, such as

routing, forwarding and

storing incoming text

messages on their way to

desired endpoints.

Wireless network

operators connect SMSCs

through SMS gateways.

81 90 15 SMS system should also work on

SIGTRAN if provisioned by the backend

SMSC

As discussed in our pre-bid meeting, SIGTRAN is not available,

please remove the same.


RFP

82 14 6 Eligibility Criteria for USSD services to

at least 3 state government




date of RFP.

As discussed in our pre-bid meeting, as USSD is not so common

in market and very less organization (state government

department/central government department /PSU/Telecom

Operator in India) are using this service. So we request you

please remove this eligibility clause.


RFP

83 - - As discussed in pre-bid you will choose

2 L1 for both SMS and USSD services.

Our suggestion for this, as you will allow 2 L1 for both services

so please allow separate Eligibility parameter for these services.

As per RFP

84 - - Please confirm your estimated monthly

or yearly SMS and USSD volume

Please confirm your estimated monthly or yearly SMS and USSD

volume

Total volume for 2 years

are listed in Annexure-1:

BOM

85 - - Your existing Vendors for SMS and

USSD services

Your existing Vendors for SMS and USSD services No regular vendor for

SMS and USSD.

86 - - Your existing Sender ID which would be

used to send SMS and USSD

Your existing Sender ID which would be used to send SMS and

USSD

No existing sender id for

USSD

87 15 4.1. Scope Of

work; Sl.2

An USSD Interface and USSD Menu

Manager systems are to be

provided/build and maintained by the

SI and deploy at RSDC. Server for the

hosting of these components shall be

provisioned by RSDC. Bidder firm need

to provide the required configuration

for this server accordingly.

All the TSP has the platform built-in & hosted on their Cloud/

Datacenter. Please allow USSD Interface & Menu Manager with

priviledge access be provided with log-in credentials to GoR.

Menu manager shall be

hosted in RSDC

88 17 4.1.2. a. a. The SP shall also assist RISL in the

following:

Conducting User Acceptance Testing

Rectification of reported errors

Submission of test results

System integration and go live of the

SMS and USSD components of Unified

Communication Gateway.

b. Post successful provisioning, testing

and rectification of the errors reported,

the SMS and USSD services shall be

declared as Go-Live

Please confirm the assistance is expected for UAT of UCG (e-

sanchar2.0) platform for which system integrator is already

selected. Kindly exclude this and limit the scope to connectivity

piece of service provider only. Any platform/ application testing

for in-house development should be excluded from connectivity

scope of service provider.

As per RFP

89 17 4.2.a. Post

Implementatio

n: Operations

and

Maintenance

The SP’s support person/ team shall

remain readily available to the RISL

support team on phone/ email for that

respective location and shall be

readily available in person to the

premises when required, during

government office hours in all days

except Sunday.

The scope mentioned is applicable only for onsite dedicate

resource at RISL. Please change the scope wrt offline support.

As per RFP

90 Please provide Govt. office hours. As per RFP

91 17 4.2.c. Post

Implementatio

n: Operations

and

Maintenance

In the event of a service outage, the

RISL team will intimate the SP through

phone/email about the service(s)

downtime and the SP shall raise a

ticket with a copy of same through

email to designated officer(s) of

respective office and make best efforts

to perform timely fault management of

respective services(s).

Please confirm who will provide the Fault Management System

to log the ticket? On which system tickets to be raised and who

will provide this system.

If SI has any ticket logging

system, it shall be used.

Otherwise, email

communication shall be

used for issue logging and

tracking

92 18 4.3. Project

Milestones,

Deliverables,

Time and

Payment

Schedule:

100 % of the tendered amount for

Supply, Installation, Testing and

Commissioning of SMS and USSD

services as S. No. 1 of the Financial Bid

Please change the payment term and provide 85% on Supply,

10% on installation and 5% on UAT.

As per RFP

93 27 15).k.

Evaluation &

Tabulation of

Financial Bids

k) However, RISL may select more than

one bidders provided that all the

selected bidders would match the

prices quoted by L1 bidder for each

component: SMS and USSD.

Please clarify how order will be distributed between multiple

providers each for SMS and USSD. What is the ratio/ volume in

which order will be distributed individually for SMS and USSD?

i.e. for 5 crore SMS, how many provider will be selected and in

what ratio it will be divided?

Please refer the updated RFP

94 As Airtel we can only provision shortcode on Airtel N/W only for

other N/W integrations customer have to lead and support us.

RISL would support the SI

during the integration

with other networks

95 64 7.1. iii.

Downtime

calculation for

SMS and

USSD

services

a) SLA Downtime would start from the

15 minutes after the date and time of

reporting of problem to SP’s SPOC/

Helpdesk or as automatically identified

by RISL whichever is earlier.

Please clarify how tickets will be logged? Kindly allow provision

of reporting faults to Service Provider Helpdesk system.

If SI has any ticket loggin

system, it shall be used.

Otherwise, email

communication shall be

used for issue logging and

tracking

96 75 Financial Bid

Format

a. Outgoing SMS: 200 crore

b. Incoming USSD Transaction: 2crore

c. Outgoing USSD transaction: 50lac

Please confirm the BoM of SMS & USSD given is for 2 years.

What is the monthly commitment? Please clarify.

As per RFP

97 15 4.1. Details of

work (SoW)

Estimated number of monthly

transactions for SMS and USSD would

be 5,00,00,000 and 10,00,000

respectively.

Please clarify on Monthly transaction? No. are mismatched wrt

Financial Bid.

As per RFP

pre-bid query responsesdoitc.rajasthan.gov.in/administrator/relateddocument/prebid... · s.no. rfp...

Documents