Proposal SMS Gateway

!"$% &'()% *,.
) /%024
" 5680:+; <0"=!+; ?"=@+; B-D.0+; EDFA
? "4'HI+; B4DHK+; <D@!+ "
SMS Gateway
Questions and Answers

" #$&(* + ,$' -./0134 568 9;(=) >@A -./02 C29D" F29G " H$I9K34 59/L.34 -N /LO34 QSTU934 VTWP -N /"1YZ34 Q"TY(34 5TO.3 "

-./02 -<1'#2 -@\U# C29D" " H$I9K34 59/L.34 -N /LO34 QSTU934 VTWP -N /"1YZ34 Q"TY(34 5TO.3 " SMS Gateway RFP Questions and Answers
Q 1. We need Details of all the systems SMS Gateway /MSDP needs to interact
Answer: External systems will send SMS messages to the SMS gateway via a web-service call to the GSB.
The GSB will send the data to the SMS gateway via WebSphere MQ and Web Service calls. Apart from
administration, as long as the SMS gateway can communicate via Web Service (SOAP/HTTP) and
WebSphere MQ, there is no need to define details of other systems. Administration should be accomplished
via Portal.

Q 2. No. of Sites in which the system needs to be installed
Answer: One site - Yesser. The idea is that Yesser will provide an SMS gateway that external Government
agencies can use. Agencies will be able to administer their own account/sub-account via a portal. There will
be a user case in the future of both and active/active and active/passive DR site. Any solution must not
preclude this.

Q 3. All the interfaces that are being currently used by the various systems which need to be integrated
with SMS Gateway
administration (see later), as long as the SMS gateway can communicate via Web Service (SOAP/HTTP) and
via Portal.

Q 4. Will the gateway be replacing any existing system or it will be a new setup?
Answer: New set-up. A previous version was created, but never went live

Q 5. In case of replacement we will need the details of all the features ,interfaces and functionality
via Portal.

Q 6. Process of charging and details
Answer: The winning bidder required to purchase the SMS on behalf of Yesser according to the following
approximate traffic per year:
1st Year: 50,000,000 messages
2nd Year: 100,000,000 messages
3rd Year: 200,000,000 messages or more
Extend the volume of SMS should be possible any time and on short notice.
The SMS pricing shall be follow the section 5.6.2.1 SMS Package and SMS Telecom Provider

Q 7. Log format and the duration for which the logs need to be stored
Answer: Logs to be held in a form allowing review/reporting of data as per RFP. Duration - three years

Q 8. Reporting requirements
Answer: All logged information should be stored in tables whose format is disclosed to Yesser. Crystal
Reports or similar will be used to create custom reports. But...Data Reporting & Statistics: Bidders are
required to integrate with existing tools.

Q 9. Details on the current policies and rules followed by agencies
Answer: The external agencies shall communicate with the GSB (including sending and receiving SMS M
excluding administrative access) using standard web service calls (SOAP over HTTP/S. (The admin
application should be web-based accessible through the GSN. The agencies shall follow the YEFI standards
(for more info, please visit: www.yesser.gov.sa/en/BuildingBlocks/Pages/interoperability_framework.aspx )

Q 10. Details on the YES Method of project management
Answer: Please visit: http://www.yesser.gov.sa/en/Methodologies/mechanisms/Pages/introduction.aspx

Q 11. Details of the business administration and reporting of individual agencies
Answer: The SMS Gateway solution will build on the top of the GSB, the government agencies will subscribe
to the service, the business administration and reporting that mentioned in RFP will apply in the agency that
want to subscribe

Q 12. Details on SMS credit feature
Answer: SMS credit will be purchased by the Vendor on behalf of Yesser. These SMS messages will be
assigned to accounts within the SMS gateway and the account administrators will be able to apportion those
messages to sub-accounts within the agency account. The SMS credit will be the number of SMS messages at
Yesser, Account and Sub-Account levels

Q 13. Input source for Mobile segmentation data
Answer: Depend on the electronic service that provided by the government agency

Q 14. Details on Interactive SMS services
Answer: The interactive nature of the SMS gateway is limited. Take an example of an interactive session
initiated by an individual from his mobile phone. Essentially, the citizen will send an SMS message to a
telephone number (or short code). Using that number and potentially a textual code at the start of the message,
the SMS gateway will forward the message, via a web service call, to a remote agency. If the remote agency
wishes to reply to that message, it will send a Web Service request to the GSB containing the text of the reply
and telephone number to send the reply to. This will be forwarded to the SMS Gateway for dispatch to the
original citizen.
Please note as per the RFP
SMS messages incoming to the GSB are to be routed simply to a web-service at the appropriate agency. If the
agency is to hold an additional dialogues with the user via SMS, that will be the responsibility of the agency,
not the SMS or channel engine.

Q 15. Details of existing reporting & Statistical tools the SMS gateway has to integrate
Answer: All attributes within the system for messages, events, accounts, etc are to be stored in a database. The
format of this database is to be disclosed to Yesser. A reporting tool such as Crystal reports or Cognos can
then be used to proved reports. The vendor is expected to provide sample reports using this tooling.

Q 16. In item 3.3.2 Software Requirements Req.11 and item 3.3.6.1 Software Architecture Req.1 mentioned
that all software component and architecture must be based on SOA implemented on top of J2EE and
Microsoft .Net framework. While our software is based on PHP, Perl and native C language running
on Linux operating system, is this acceptable?
Answer: Yesser have certain favoured hardware and software platforms. These include...
N Hardware
IBM P-series
IBM X-series
etc.
N Software
WebSphere Application Server
Microsoft SharePoint Portal
etc.
N Operating System
AIX
Windows
etc.
The more that a vendor restricts its platforms to Yesser standards, the more favourably the bid will be
received.

Q 17. In item "3.2.1 Acquired solution overview, SMS Quota: the platform must charge with 500,000,000
SMS for 5 years that can be used for the local GSM operators and international SMS.", is the winning
bidder required to purchase the 500,000,000 SMS on behalf of Yesser and to include the cost in the
final price?
The SMS pricing shall be follow the section 5.6.2.1 SMS Package and SMS Telecom Provider, and to include
the cost in the final price.

Q 18. Project Plan for 6 months should include M efforts of co-ordination with the different Govt. Agencies,
understanding each agencies business needs and the other requirements?
Answer: The plan for the first 6 months will be the installation and setup the SMS Gateway solution with
integrate one government agency which is Yesser) as a pilot

Q 19. Details of Government agencies like YESSER, NCDC regarding functions expected, volumes,
subscriber base would help.
Answer: You can find more about Yesser in: www.yesser.gov.sa
You can find more about NCDC in: www.ncdc.gov.sa

Q 20. Please provide the complete list of the Access Channels to the SMS Gateway Solutions, apart from the
Web access given, if any
Answer: Web Service and WebSphere MQ


Q 21. Data Migration: Data volume, related details, existing SMS services details would help.
Answer: Although the existing outgoing SMS system was built, it was never implemented. There is no
information to migrate.

Q 22. What is meant by Odelivery timeP in OThe system shall provide agencies with the capability to
configure the subaccount parameters (e.g. but not limited to message delivery time, expiry time,
number of retries).P?
Answer: E.g. don't send SMS messages after 10pm or before 8am

Q 23. You said that the bidder company should have quality certificate, which quality certificate you mean,
could you please elaborate more on this.
Answer: The quality certificate is a plus and the bidders are required to present their Quality Assurance
framework. The Bidder must be responsible for the quality of work and the execution of the Project. Yesser
reserves the right to inspect and ensure the presence of such control and supervision as it deems necessary (see
section 5.10.4)

Q 24. What are the evaluation criteria for this tender?
Answer: Meeting the requirements with the reasonable cost

Q 25. Yasser required from Contractor to deliver SMS Gateway Application Source Code; so please specify
this point weight in case we can't deliver the source code?
Answer: The more that a vendor restricts its platforms to Yesser standards, the more favourably the bid will be
received. Yesser will not publish individual weights; the merits of the entire bid will be taken as a whole.

Q 26. Shall Yasser require to link to Mobile Operator Directly or thru CITC licensed SMS Aggregator
(more cost effective)? And if you ask to link thru mobile operator directly at KSA What about
International Traffic?
Answer: The vendor shall manage the agreement or contract with the SMS telecom provider(s) to provide the
SMS delivery service according to the following conditions:
One year agreement or contract and subject to renewal or terminate based on Yesser decision
The integration with the provider(s) is done on standard approaches and not limiting Yesser interest
for reuse and later integration with other providers.
Provider subscription details agreement or contract must be disclosed to Yesser.

Q 27. Which countries are the most important destinations for the international traffic and what percentage
of total message dose Yasser projects to be International?
Answer: Because we will allow this solution to the different government agencies to subscribe on it, we
expect to have users from outside the kingdom (e.g. MOFA, MOHE users), so there are no most important
destinations for the international traffic, we expect to have them from all over the world; the approximate
percentage is 10% from the total SMS messages.

Q 28. Summary of SMS Telecommunication Provider Pricing table Page #75, didnRt mention at pricing
summary table page#72 , so we need to know if the total price of this RFP will be affected by SMS
Price or Not ? , and in case it will not affect the total price how you will Yasser select the SMS
Vendor? And may Yasser select 2 Vendor for this project, one for application and another for SMS?
Answer: The SMS package and SMS telecom provider agreement and integration is part from the total price
and Yesser will select one provider for both (application and SMS), in addition to that we need to have details
pricing as mentioned in the RFP

Q 29. What do you mean about "Professional Services" mention at pricing summary table page #72? We
need to know the difference between this item 2 "S;0KJT; UD4VX+; " Oand item 5 " Z"80K+;% \"^@K+;' mention
at same table?
Answer: Any services that more than the standard services

Q 30. Yasser had required that the SMS Gateway backend Database to be DB2, so will Yasser provide DB2
Licensee or it will be Vendors responsibility? And do you have any agreement with IBM that cover
this license cost??
Answer: Yesser will provide the required licenses

Q 31. Can you give us estimation about required number of short codes; also do you need 2 way for
international "long codeP ?
Answer: We do not have a clear numbers for this because it is depend on the every government agency and
yes we need 2 way for international "long code P

Q 32. We need more details about your request in Req.19, Compliance Matrix Page 64?
Answer: Yesser and agency (account and sub-account) administrators need to log in to the portal to be
authenticated and authorised.

Q 33. OThe Proposed solution must allow agencies to be fully hosted in a centralized single instance P, what
do you mean by single instance?
Answer: Should more properly say "centralised and unified solution" i.e. there is one SMS gateway, hosted at
one site, for all government agencies to use.

Q 34. OThe Proposed solution must allow agencies to be fully hosted in a centralized single instance P, do
you mean that SMS Gateway should be running as single instance only without clustering?
Answer: Should more properly say "centralised and unified solution" i.e. there is one SMS gateway, hosted at
one site, for all government agencies to use.

Q 35. OOffer the e-services implemented by government agencies through SMS gateway to beneficiaries P
Offer the e-services implemented by government agencies through SMS gateway to beneficiaries, Can
we propose mobile application for the end user which simplifies the usage of the SMS
Answer: Extra functionality can always be proposed but in the short-term, Yesser requires a solution that
meets its requirements and will largely resolve the bidding process by seeing which vendors match the
requirements, not the ability of vendors to supply extra functionality that was not requested.

Q 36. OIn total, Government Agencies may have more than 3000 employees and contractors P, Is this number
regarding the four agencies covered in the RFP only?
Answer: This number regarding the four agencies covered in RFP

Q 37. OCharge the system SMS quota with 500,000,000 SMS / 5 years excluding the SMS quota for testing
purposesP, what is the expected number of SMS required for testing purposes?
Answer: The number of SMS required for testing purposes is reasonable number to do the all the testing types

Q 38. OThe acquired solutions comprise of three categories of deliverables P, Prerequisites Hardware &
software; and Operations are not mentioned here, is there any reason?
Answer: The operations are embedded in the project services part
Q 39. OSMS Quota: the platform must charge with 500,000,000 SMS for 5 years that can be used for the
local GSM operators and international SMSP, Is there any expectation for the number of users per
provider
Answer: There is no expectation regarding this

Q 40. OLicensing information system of KSA MOCP, Can you please provide more information about this
integration?
Answer: As the SMS Gateway will be a part from the GSB, and the GSB provides (OhostsP) national shared
applications and services for the benefit of integrated government agencies, the supplied application software
shall be integrated with the internal applications software as per the integration requirements listed in the
current IT Systems and Initiatives section, the integration with the Licensing information system of KSA
MOC is no longer valid.

Q 41. OLicensing information system of KSA MOCP, what are the needed SMS services?

Q 42. OLicensing information system of KSA MOCP, What do you mean by inspected agencies:

Q 43. OData migration from the current systemP Do you have current SMS system, if yes, what is the data
size need to be migrated?
Answer: New set-up. A previous version was created, but never went live.

Q 44. OThe system shall allow the throughput of 300 SMS per second or better and 31 million per year. The
system shall allow for growth of 15% per year on the above figures for five years P, In req. 51, you
mention the following
The approximate traffic per year is:
Which estimate is more accurate?
Answer: The following are the approximate traffic per year:

The system shall allow for growth of 15 - 100% per year on the above figures for five years

Q 45. Shall the system provide SMS inbox for each mobile number?
Answer: Yes - or allow different telephone numbers to share inboxes. This should be configurable.

Q 46. OThe system shall be able to receive SMS messages from multiple telephone numbers that are
multiple SMS inboxes.P This requirement is not clear.
Answer: The SMS gateway should be able to provide multiple mobile telephone numbers for customers to
send incoming SMS messages to. Each telephone number is to have its own "inbox".

Q 47. OThe system shall be able to support to use multiple short-codes for ongoing and outgoing SMS and
the vendor responsible for providing short-codes/telephone # from Telco based on Yesser requests
(current & future). Masking of these agency phone# / short-code should be available, so user can see
some meaningful name as sender rather just a phone # / short code. P How many short-codes are
required?
Answer: We do not have a clear numbers for this because it is depend on the every government agency

some meaningful name as sender rather just a phone # / short code. P How short-codes will be
distributed for agencies? Each agency will have their own short code?
Answer: Each agency (Account) may have zero to many short codes. Each department within an agency (Sub-
Account) may have zero to many short codes. The short code will be one of the criteria (along with keywords
in the message - the first word of the message) used to forward the SMS (as a Web Service) to the appropriate
agency.

some meaningful name as sender rather just a phone # / short code. P, Or one short code will be
available then the distribution will be based on keywords (the first word in the pull message)
Answer: Each agency (Account) may have zero to many short codes. Each department within an agency (Sub-
Account) may have zero to many short codes. The short code will be one of the criteria (along with keywords
in the message - the first word of the message) used to forward the SMS (as a Web Service) to the appropriate
agency.

some meaningful name as sender rather just a phone # / short code. P, Do you required unified short-
code from all telecom providers?
Answer: Yes we required this and it is depend on the government agencies demand


Q 51. OAll traffic, reporting information and configurations should be stored in DBP, do you mean that only
monitoring information should be stored in DB2 or all system information (messages, users,
configuration)
Answer: All information that Yesser could use to generate reports should be held in a database the format of
which is disclosed to Yesser so that they can create their own custom reports.

Q 52. OAll traffic, reporting information and configurations should be stored in DBP, Can we use Oracle or
SQL Server instead of DB2?
Answer: Potentially, yes.

Q 53. ONetworking InfrastructureP, does the site contain Routers and Access Switches/ Core Switches?
Answer: Yes

Q 54. ONetworking InfrastructureP, do we have to provide site preparation, power, cabling, UPS or we can
utilized existing infra.
Answer: No

Q 55. OSANP, does the site have existing SAN setup? Or IS has to recommend?
Answer: Yes

Q 56. OSANP, if desired then Sizing is required?
Answer: The bidder must include in his technical proposal the estimated storage and FC interfaces
requirement

Q 57. OAll Hardware (Storage, Routers, Switches) must be redundant P, if Router/ Switches/ Storage required
then what would be sizing of boxes?
Answer: Not required

Q 58. OAll Hardware ( Storage, Routers, Switches ) must be redundant P, Will it be assumed to have a
Small/Medium/Large scale Routers/ Switches/Storage or do you have any value of
throughput/sessions so based upon that IS can recommend according to sizing of your system?
Answer: Storage, router, and switches are not part of the scope

Q 59. OFirewalls, DMZP, is there any available firewall available or do you want IS to quote the Firewall
unit as well?
Answer: Firewalls are available

Q 60. OFirewalls, DMZP, What Throughput and sessions are required for this setup? Either provide
Throughput and sessions or provide the classification in terms of Small/Medium/Enterprise firewall
solution?

Q 61. The required solution should support WAP Push SMS?
Answer: This mean the required solution should support mobile portal and application push SMS

Q 62. The Required solution should support MMS Bulk as add-on feature to be used in future?
Answer: This is not an immediate requirement, but extra functionality can be suggested.

Q 63. The required solution should support USSD technology as add-on to be used in future?

Q 64. The required solution should have intelligent logic to segment the user MSISDN profile for SMS
Bulk?
Q 65. The required solution should have the ability to detect the mobile handset types (DMC) features?
Q 66. Appendix F - Section 5.6.2.1: The pricing considers prices from one telecom provider while Saudi
Arabia has 3 telecom operators. Should we quote the SMS pricing from only one telecom operator? If
yes, then this means that the proposed gateway will terminate messages to different telecom operators
than the priced one. For that, we suggest that we propose detailed pricing from the 3 telecom
operators.
Answer: The pricing is not considers prices from one telecom provider , the summary of SMS
telecommunication provider pricing table can be multiple row with multiple providers depending on the
vendor strategy with telecommunication providers

Q 67. Regarding international messages (international termination), telecom operators might have different
prices from local messages. Should we detail prices for international and local messages or Yesser
requires only one price for the SMS regardless of the destination?
Answer: Yesser requires only one price for the SMS regardless of the destination

Q 68. What is YesserRs payment model of SMS quota? Is Yesser going to pay for the 500M SMS upfront
(pre-paid), or will they pay per monthly/quarterly traffic consumption?
Answer: Yesser will pay per quarterly traffic consumption

Q 69. Regarding receiving SMS
a-What the purpose of receiving SMS.
b-Is it required by the system to process the SMS automatically based on another system and
automatic reply to them.
c- Is the system required to serve this received SMS to any other system, and based on what criteria.
d-Is the system required to display this received SMS to certain users, and based on what criteria.
Answer: For members of the public to send data to one of the agencies within the Yesser program. This may
initiate a two-way dialogue (driven by the agency) or be the reply to a previous SMS sent from the agency
Automatically forward the message to the targeted agency. As the agency knows the tele # that sent the
message, the agency can send an SMS out in reply
Automatically forward the message to the targeted agency based upon the tele # that the message was sent TO
and parseable content in the message (e.g. first 3 bytes are "MOI")
The SMS gateway should forward the message via a web service call to the appropriate message. Who they
display the message to is entirely their own affair.

Q 70. In page 11, you define government service Bus (GSB), who is responsible to integrate with the GSB
and could you please provide some technical information about this integration.
Answer: The vendor is responsible for integration with the GSB. The GSB is a large ESB. It publishes web
services to participating agencies. The agencies invoke services on the GSB by a web service call. The GSB
will communicate with the SMS gateway either by a web service call or WebSphere MQ.

Q 71. In page 12, you defined the public key infrastructure (PKI), should our security model and
authentication depend on eGov PKI, and what about the system specific rules, Username and access
level, will it be implemented inside eGov PKI.
Answer: It is within the winning Bidder Rs scope to integrate with the e-Government PKI solution where ever
applicable

Q 72. In page 14, third paragraph, you talked about Agency account management, is it integrated with PKI
and how?
Answer: Yesser plan to integrated with the PKI, you can find more about NCDC in: www.ncdc.gov.sa

Q 73. In page 17, you talked about Quota management, will Yesser Admin have the authority to specify the
sub-Account SMS quota, or is it the solo responsibility of agency admin?
Answer: Yesser admin as "super users" will be able to administer all accounts and sub accounts. Account
admin will only be able to administer their account t and associated sub-accounts.

Q 74. In page 17, you talked about interface layer and that it should interface with external systems, internal
systems and web applications in a very secure way, could you please specify these internal/external &
web applications, and whoRs responsibility to build the integration with them.
via Portal. The GSB and portal supply the necessary levels of security.

Q 75. In page 18, you asked that the system should have the ability to easily create interactive SMS services
and auto reply without asking for special customization or development, could you please explain this
requirement in more details, will this feature include fetching data from other systems based in the
received SMS and forwarding this data to the sender?
original citizen.

Q 76. In page 19, in the fourth paragraph, you said OThe Supplied solution shall be implemented for
agenciesP is it part of the scope to integrate the solution with the agencies current system, could you
please explain the implementation in more details.
original citizen.
External systems will send SMS messages to the SMS gateway via a web-service call to the GSB. The GSB
will send the data to the SMS gateway via WebSphere MQ and Web Service calls. Apart from administration
(see later), as long as the SMS gateway can communicate via Web Service (SOAP/HTTP) and WebSphere
MQ, there is no need to define details of other systems. Administration should be accomplished via Portal.

Q 77. In page 19, could you please elaborate more on the integration section with the Licensing information
system and the web applications.

Q 78. In page 19, you talked about data migration from current system, could you please explain the
following:
A. The purpose of this data migration
B. The format of the old data, i.e. MS SQL, DB2, etc
C. The size of the data

Q 79. In page 23, first paragraph, you said OSMS Messages incoming to the GBS are to be routed simply to
a web-service at the appropriate agency. If the agency is to hold an additional dialogue with the user
via SMS that will be the responsibility of the agency, not the SMS or channel engine P this seems to
contradict that you requested in page 18 about SMS auto reply, could you please explain?
original citizen.

The SMS gateway may send an automated reply to individuals should the agency web Service be unavailable
and therefore the SMS gateway would be incapable of forwarding the message to the appropriate agency.

Q 80. In page 24, permission section, point 4, you wrote OApproval SMS messages by portal or by SMSP
could you explain what you mean by approval?
Answer: The facility to categorise outgoing SMS messages into OautomaticP and those that require further
manual approval is required. For those that require manual approval, a portal interface to approve the sending
of those messages is required.

Q 81. In page 25, you talked about agency dedicated numbers DB, what format is this DB and who do you
propose our solution to read from various agencies DBsR.
Answer: Messages are sent by an agency sending a Web Service message to the SMS Gateway via the GSB.
That one SOAP message may specify a single mobile telephone number of receipt of the message, multiple
mobile telephone numbers of the name of a stored set of numbers. The format of this stored set and the
method used by an agency to update the stored set and for the vendor to implement.

Q 82. In page 28, you wrote Obidder are required to leverage the existing network infrastructure, existing
racks and UPS, and other equipment provided by the data center P could you please describe the
existing infrastructure, the current racks empty spaces and the UPS available capacity.
Answer: Yesser will provide the required space, power and cabling for the propose solution. The physical
requirement should not affect the bidder proposal. The bidder must include in his technical proposal the
estimated requirement.

Q 83. When a new SMS message received our system will not do any processing actions on it except
forwarding it to the GSB?
Answer: No - forward it (via the GSB) to a Web Service published by the agency.

Q 84. regarding the migration from the old system what is the data and its size that we are going to migrate

Q 85. It mentioned in the RFP that the Accounts and Sub accounts shall adhere to a hierarchy (in page 16-
17) and you mentioned: Attributes that can be specified at message level will be obtained from the sub
account if missing from the message, what are the Attributes here?
Answer: Any attribute that can affect the message / system or events should be specified at all levels. The
vendor should know what attributes could be specified for the messages.

Q 86. We need more explanation about the integration, shall the integration be applied with GSB and other
systems through web services and APIs interface or there is another model of integration.
Answer: WebSphere MQ for SMS messages. WebSphere portal for admin user interface

Q 87. What is the existing basic architecture of the SMS Gateway?
Answer: Not relevant

Q 88. What is the recommended SMPP specification version during implementation?
Answer: The latest version

Q 89. Will the application involve any third party integration? If yes, kindly give more details.
Answer: Only what is mentioned in the RFP and in these answers.

Q 90. What will be the quota held at Agency account and Agency sub accounts level?
Answer: The number of messages to be sent from each sub account, aggregated to the account level. The
value of the quota is not of concern to the vendor.

Q 91. Will the Agency user use Web based interface / client based interface to SMS Gateway?
Answer: For admin usage only - Portal. SMS messages sent to the GSB via Web Services and MQ.

Q 92. What is the different type/format of reports required?
Answer: To be determined with the vendor.

Q 93. Please specify the Application Server, Database Server and Operating system used for deployment.
Answer: Yesser preferred platforms are WAS DB2 and AIX/Windows but this does not preclude other
platforms.

Q 94. Does your system require scheduled messages?
Answer: Yes

Q 95. Do you require additional services like _Distribution listR, _Block listR and the _list of recipientsR?
Answer: Optionally yes

Q 96. Does your system require MMS?
Answer: No current plans but should not preclude the use of MMS

Q 97. What are the different types of GSB channel interfaces other than (Bidirectional Email, fax, IVR)?
Answer: And SMS

Q 98. Do you require licensing /option to authenticate the sub agency during new registration?

Q 99. Is there only 1 site for main implementation?
Answer: Yes - but with the future possibility of active/active and active/passive DR sites.

Q 100. Are we to include the price for 500 million SMS for 5 years in our proposal?
The SMS pricing shall be follow the section 5.6.2.1 SMS Package and SMS Telecom Provider

Q 101. How many out of 500 mile do you expect for international usage?
Answer: Because we will allow this solution to the different government agencies to subscribe on it, we
expect to have users from outside the kingdom (e.g. MOFA, MOHE users), so there are no most important
destinations for the international traffic, we expect to have them from all over the world; the approximate
percentage is 10% from the total SMS messages.

Q 102. In Req#10, it is mentioned 31 million per year, and in req#51, it mentioned 50,100 and 200 per
million per year, please clarify?
Answer: 50, 100 and 200 million per year.

Q 103. The subscription agreement with providers should be in Yasser name or in contractor Rs name?
Answer: The vendor shall manage the agreement or contract with the SMS telecom provider(s) to provide the
SMS delivery service according to the following conditions:
One year agreement or contract and subject to renewal or terminate based on Yesser decision
The integration with the provider(s) is done on standard approaches and not limiting Yesser interest for reuse
and later integration with other providers.
Provider subscription details agreement or contract must be disclosed to Yesser, so the subscription agreement
with providers should be in contractorRs name

Q 104. What is the retention period of the log archive and backup?
Answer: 3 years

Q 105. Are you also looking to monitor and govern the development life cycle?
Answer: Yes

Q 106. Are there any testing tools being used currently?
Answer: Yes, currently we are using RPT, RFT, and SoapUI as testing tools.

Q 107. How versioning of source code being handled at present?
Answer: We are using Rational Clear Case as a version control

Q 108. For performance testing, what are the expected maximum parallel hits on the application at peak time?
Answer: 100,000 concurrent users

Q 109. How many developers are expected to be working in the development phase?
Answer: We expect the winner bidder to provide the enough resources to complete the project according to
the project scope and time

Q 110. Preferred operating system and hardware for WebSphere portal?
Answer: IBM AIX and IBM P-series

Q 111. Number of registered users for WebSphere portal?
Answer: > 100, 000 registered users

Q 112. Number of unregistered users for WebSphere portal?
Answer: > 1,000,000 unregistered users

Q 113. Number of active users in the peak hour for WebSphere portal?
Answer: 10,000

Q 114. Do you want to have WCM (web content management) services in WebSphere portal?
Answer: Yes

Q 115 . [D`Y bD:c+; e+D:+; /%02:*+ :"!& ) 1 .(% Bf gK# h:#V!L ij h:"!+; "+D:+; k:X*+ U;'@. E) mno+; U;'@. "4;6+p; qr!S
&D(T; : "4;6+p; U;'@. $no+; lD.; s*j EV!#

Q 116 . u*+; &'*`:+; v%0w*+ ef u*+; "&0w+; . Bf W'=!:+; x+\& v0w+; e+D:+; qe@^+;% E) D@@H:# g#V!L v0w+; e@^+; u*+D& q#6"*zAp;
{"J i4 &'w=+; hK:(0L s+; u*+; "&0w+; .
&D(T; : EV!L e+D:+; v0w+;% "&0w+; u*+D& |Dc#; }4 #6"*zAp; u*+D& D~:#V!L iH:# :(0K+; Zw> ;];% "&0w+; u*+D& "@^+;% "+D:+; v%0w+;
"&0w+; u*+D& b'H# b; V&p .

Q 117 . Bf 7'z# g#V!L v0j W;04 %) B#V& k^@+ q802+;
&D(T; : B#V& %; W;04 v0j g#V!L D4DFA 7'z# p

Q 118 . V@j g#V!L v%0w+; Zz# }d% B>; mno+;% !"A eS ) b'L08 .( B~S ['*`4 B=S B"*IK+; e+D:+; ij B"*IK+; e@^+; D:4 e@w# g#V!L
) 2 b'L08 ( q E) k^@& ) b'L0H+; ( iH+ W'('& B>) B"*IK*+ e+D:+; B>)% B"*IK*+ e@^+; }4 W'(% 3 !"A BH+ qB"*IL E; gK". g#V!L
i"*"*IK+; v0w& qVJ;%
&D(T; : hX"A% e@^+;% hX"A% e+D:+; D~"S WVI# 0$&& g"!L% VJ;% b'L08 b; Bc^# .

Q 119 . Bf EV!L 0""+; "L;\+; '#0^+ B:w+; }4 v%0w+; E) eS CDJ q".0K+;
&D(T; : v%0w+; }4 EV!L b; Bc^#

Q 120 . C%;V( UD":H+; - U;1%V+; ")#1VK+; - UD"w(0:+; }#1D2:+;% !&D"+; - +]D:@+; <W'(':+; eS B>; !"$% Z*, v%0w+; - gzJ h802+;
WVj% i"^$':+; @.% k".&K+; ... !+. . Bf Zz# }d% <1'> i4 B8 C%V( }4 B>) v%0w+; }4% 1'=+; 4V!:+; i4 qD@S0,
&D(T; : 4'KX4% gwA

Q 121 . Bf /KS 0#1DF:+; E'# 20 - 7 - 2011 jD"+; 10 qDJD)>
&D(T; : gwA

Q 122 . Bf EV!# v0w+; e+D:+; 2n4D3 :"3 500,000,000 +D.1 wSW <VJ;% Dc#% s+. /'z:+; e*H+; v0w*+ qe+D:+; ) {"J /'(0+D&
C%;Vz+ UD":H+; eS !"$% Z*, v%0w+; gL 08] 0"w"L B-D.0+; i:d UD,S (
&D(T; : e*# D:8 B-D.0+; WVw+ ")#0!K+; UDw3'K+; Z"J EV!# v0w+; :
s+%; @"+; : 50,000,000 +D.1
"ADo+; @"+; : 100,000,000 +D.1
o+Do+; @"+; : 200,000,000 +D.1
C%V( eS D~wd% '#0, ij gK# B-D.0+; 0"w"L 5.6.2.1 B-D.0+; 4VY W%64% <0"=!+; "=@+; B-D.0+; ":8 e*H+; 0w"*+ DcL DfVw&%

Q 123 . Bf gK# 0"w"L bDK@"+; bDK"SDdT; BH2& qB=^@4 E) gK# D:~:d /':z:*+ e-D~@+; q/%02:*+
&D(T; : e-D~@+; /':z:*+ D~:d gK#% UD":H+; C%V( Z"J 0"w"K+; gK# .

Proposal SMS Gateway

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Proposal SMS Gateway

Hochgeladen von

Copyright:

Verfügbare Formate

!"$% &'()% *,.

Das könnte Ihnen auch gefallen