rfp template€¦ · web viewopen request for proposals for contract awarding to provide roaming...

Documentation on Open RFP

July 07, 2011

Purchasing documentation on

Open Request for Proposals for Contract Awarding to Provide Roaming Billing Solution to “K-Telecom” CJSC

for the Period of Y2011

Yerevan2011

1


July 07, 2011

Contents

Company Profile...................................................................................................................3

1.General Provisions.........................................................................................................4

1.1. General information on Request for Proposals..........................................................4

1.2. Legal status of procedures and documents...............................................................4

1.3. Appeal........................................................................................................................6

1.4. Other provisions.........................................................................................................6

2.Subject of RFP.................................................................................................................8

2.1. The subject of RFP is as follows:...............................................................................8

3.Order of execution of Request for Proposals.............................................................10

3.1. Preparation of Proposals.........................................................................................10

3.2. Requirements to Applicants. Approval of compliance with the presented requirements............................................................................................................12

3.3. Submission and acceptance of Proposals...............................................................14

3.4. Amendment and call back of Proposals...................................................................15

3.5. Evaluation of Proposals...........................................................................................16

3.6. Decision-making......................................................................................................19

3.7. Agreement conclusion.............................................................................................19

3.8. Rights of the Applicant that provided the best offer for RFP....................................19

3.9. Notification of Applicants about the results of Request for Proposals......................20

4.Samples of standard forms of documents, included in the Annex..........................21

4.1. Letter about offer submission (Form 1)....................................................................21

4.2. Technical/Commercial Proposal on provision of works, goods or services (Form 2).................................................................................................................................23

Applicant’s Questionnaire (Form 3)................................................................................24

Applicant’s Work History Reference List (Form 4)..........................................................26

Technical Specification (Annex 3)..................................................................................27

Technical Specification of existing hardware (Annex 4).................................................40

2


July 07, 2011

Company Profile“K-Telecom” CJSC (VivaCell-MTS), is Armenia’s leading mobile operator with over 2

million subscribers. Starting its activity on July 1, 2005, VivaCell-MTS spearheaded the

development of the telecommunication sector in Armenia, offered innovative mobile voice

and data products and services, and tailored solutions for different market segments. On

September 14, 2007, the Company became the subsidiary of “Mobile TeleSystems” OJSC

(MTS), one of the world’s largest multinational mobile operators.

VivaCell-MTS has become the choice of remote mountainous villagers, housewives,

youth, middle-class, as well as travelling business people. VivaCell-MTS also paved the

way and leads the partnership with the society through its Corporate Responsibility:

everywhere hand in hand with all Armenians in social, cultural, health, sports, educational

and humanitarian activities.

3


July 07, 2011

1. General Provisions

1.1.General information on Request for Proposals

1.1.1. “K-Telecom” CJSC (legal address: 4/1 Argishti str., Yerevan, Armenia),

(hereinafter referred to as the Organizer), with the public notification posted on its

website at www.mts.am/procurement on conducting Open Request for Proposals,

has invited legal entities (hereinafter referred to as the Applicants) for submission of

Proposals with the right to conclude agreement on providing Roaming Billing

Solution with “K-Telecom” CJSC for the Y2011.

1.1.2. For further information, please apply to the Organizer

Contact person: Rousanna Apoyan

Procurement Leading Specialist

Administration Services Department

Purchasing Unit

“K-Telecom” CJSC (VivaCell-MTS)

4/1 Argishti Street

Yerevan 0015, Armenia

Tel.: +374 93 298507

Fax: +374 93 298541

E-mail: [email protected]

1.1.3. The complete information on participation in open purchasing process is

posted on the Organizer’s website at www.mts.am/procurement.

1.1.4. The procedures as well as instructions on participation and preparation of

Proposals for open purchasing process are provided in the Section 4.

1.1.5. No fee is foreseen for provision of RFP Documentation.

1.2.Legal status of procedures and documents

1.2.1. The Open Request for Proposals (RFP) is not a tender and the given

procedure of Open RFP is also not considered as a public tender. It is a collection

of respective offers available in the market, as a result of which the best offer might

4

http://www.mts.am/procurement

mailto:[email protected]



July 07, 2011

be accepted. The process of the Request for Proposals is not regulated by the

Articles 463-465, 1043-1044 of RA Civil Code and Law “On Public Auctions”.

1.2.2. Publication of RFP in compliance with point 1.1.1. with its indispensable

annexes is the invitation to submit Proposals and must be considered by the

Applicants as such.

1.2.3. Applicant’s Proposal has legal status of offer, which should include all the

essential terms of the given contract and shall be considered by the Organizer in

compliance with this Document. The Organizer reserves the right to determine

Applicants’ Proposals, as firm offers, which are not subject to further changes

except for the cases foreseen by this Document.

1.2.4. The Agreement concluded on the basis of RFP Process results, stipulates all

agreements reached by the Parties.

1.2.5. In the course of determination of Agreement terms with the Applicant that

submitted the best offer the following documents are used with the strict order of the

indicated hierarchy (in case of their controversy):

a) Notification about conducting Open RFP and this Documentation on Open

RFP for all the executed stages including all the addenda and

clarifications;

b) Applicant’s Proposal with all the attachments and clarifications in

compliance with Requirements of the Organizer.

1.2.6. Other documents of the Organizer and the Applicants do not define the

rights and obligations of the parties with regard to the current Open RFP.

1.2.7. In all other cases, which are not regulated by the Notification about

conducting the Open RFP and current Documentation on Open RFP, parties are

governed by the legislation of the Republic of Armenia (RA).

1.2.8. Upon the authority of submitting Proposal and in case of waving the right to

call them back according to the procedure stipulated by the given Document and

RFP, the Applicants shall agree with the procedures and provisions prescribed by

the given Document and RFP.

5


July 07, 2011

1.3.Appeal

1.3.1. All disputes and disagreements, arising as a result of conducting the RFP,

including the one, concerning execution of obligations by Organizer and Applicants,

should be resolved through negotiations. When one of the parties receives a claim,

it shall send the response to the other party within 10 working days from the

moment of its receipt. In case disputes are not regulated after 30 days of their

commencement, they should be regulated according to the rules and procedures of

RA legislation.

1.4.Other provisions

1.4.1. The Applicants independently incur the expenses with regard to the

preparation and submission of the Proposal, whereas the Organizer is not

responsible for those expenses and has no obligations regardless of the course and

results of the purchasing process.

1.4.2. The Organizer provides reasonable confidentiality regarding all the

information received from the Applicants, including the one described in the

Proposal. This information may be provided to other Applicants or to a Third Party

only in cases directly stipulated by the existing legislation of RA or the given RFP

Documentation.

1.4.3. The Organizer reserves the right to reject the Proposal if he/she ascertains

that the Applicant expressly or by implication gave, agreed to give or offered the

Organizer’s employee reward in any form: job, service, any value as a stimulus that

can influence the decision-making to define the best offer.

1.4.4. The Organizer has the right to reject the Proposals of the Applicants, which

came to an agreement with each other on the determination of best offer or for the

purpose of having impact on that process.

1.4.5. The Organizer reserves the right to cancel the purchasing process on

conducting an Open RFP at least 3 days prior to the closing date of this Open RFP

(as specified in item 3.3.4.), respectively notifying about it the Applicants via posting

of this information on www.mts.am/procurement webpage. The Organizer bears no

6



July 07, 2011

responsibility for the expenses incurred by the Applicants or Third Parties as a

result of such cancellation.

7


July 07, 2011

2. Subject of RFP

2.1.The subject of RFP is as follows:Implement Roaming Billing software and hardware solution to facilitate data,

information support for “K-Telecom” CJSC providing national and international

roaming services and executing the roaming broker, data clearing house (MACH)

functions in compliance with international standards. Interoperates with the existing

Eskadenia billing system; integration with accounting system is also required in order

to reflect monthly roaming revenues and expenses per roaming partner (TADIG

code) in accounting system. The hardware design, architecture, configuration and

training details are integral part of Applicants’ proposal.

For detailed technical specification please refer to Annex 3.

Applicants’ proposal must give the possibility to choose one of the options below: Complete solution (Hardware, Software License, Implementation and Training) Software License, Training and Implementation on existing hardware (application

server, database storage and test environment).

For detailed technical specification of existing hardware please refer to Annex 4

2.1.1. Technical part

Project Management (project plan, project charter, risk assessments, etc)

Proposal of new hardware and design for the solution servers and storage

Providing the best and optimal solution for hardware availability, data

redundancy, and load balancing (based on Oracle RAC, Sun Cluster, others)

Providing data backup, restore and cleanup solution

Providing complete documentation of the delivered system and transfer of

knowledge to the “K-Telecom” DBAs

Migration of the current database to the new system

Highly qualified consultants and engineers with at least 5 years of

experience

8


July 07, 2011

Proposal of system administrator, database administrator and business

user training.

2.1.2. Commercial part

Support and maintenance should be implemented for 2 years

The payment should be quarterly after providing services based on the

invoices and acceptance act

The prices should be presented in AMD, VAT excluded (if the prices are

mentioned in other currency the RA Central Bank’s of data will be used for

further calculation according to the daily exchange rate).

2.2. The Applicants’ Proposals should be elaborated in accordance with Forms in

Section 4.

9


July 07, 2011

3. Order of execution of Request for Proposals

3.1.Preparation of Proposals

3.1.1. General requirements to Proposal

The Applicant who wishes to respond to the RFP must prepare a Proposal,

which shall include:

3.1.1.1. Letter about offer submission in the form and according to

instructions, stipulated in this Documentation (Form № 1 );

3.1.1.2. Technical/Commercial Proposal for provision of goods, works or

services in the form and in accordance with instructions, stipulated

in this RFP (Form № 2);

3.1.1.3. Price proposal in accordance with instructions indicated in this

RFP;

3.1.1.4. The draft Agreement in accordance with instructions stipulated in

this RFP;

3.1.1.5. Documents, which prove the Applicant’s compliance with

requirements of this RFP (subpoint 3.2.).

3.1.2. The Applicant shall submit all documents in hard copies. The Applicant shall

also submit electronic version of the proposal to [email protected] e-mail

address after RFP submission deadline. The electronic version of the file shall be

protected by password of at least 12 characters combined of letters, numbers,

symbols etc. The password of the proposal shall be enclosed in the envelope of the

hard copy of the Proposal submitted to Organizer. The Applicant bears

responsibility for non-compliance to this request.

3.1.3. The Applicant is entitled to submit only one Proposal. In case of violation of

this rule, all Proposals of this Applicant are rejected without consideration of their

merits.

3.1.4. If there are multiple lots, the Participant prepares an individual Proposal for

each lot applied. All Proposals shall be filled in according to this purchasing

Documentation and have to be placed in different envelopes and shall be sealed

with the stamp of the Applicant. The lot numbers have to be specified on the

10

mailto:[email protected]


July 07, 2011

envelopes. Afterwards the envelopes have to be inserted into the envelope of the

Applicant.

3.1.5. Each document, included in the Annex, should be signed by the person who,

pursuant to RA legislation, is entitled to act on behalf of the Applicant without power

of attorney, or the person duly authorized by the Applicant on the basis of notarized

power of attorney. In the second case, the original of the power of attorney shall be

fixed as an Attachment.

3.1.6. Each document, enclosed in Applicant’s Proposal, must be sealed with

Applicant’s seal.

3.1.7. Documents (sheets or informational envelopes), included in Proposal,

should be fixed or packed in a way that would prevent documents or informational

envelopes from accidental loss or replacement.

3.1.8. Applicant shall prepare one original and one copy of Proposal in each

language (if multiple languages are applied), on which the words “original” and

“copy” should respectively be indicated.

3.1.9. Neither of corrections in the Proposal text has legal force, except for the

cases, when these corrections are authorized by handwritten script “corrections are

verified” and personal signature of the authorized person is indicated next to each

correction.

3.1.10.Requirements to the language of Proposal

3.1.10.1.All the documents, included in the Proposal, should be prepared in

Armenian and/or English with the exception of the following:

The documents original copies of which were presented to the

Applicant by Third Parties in another language, may be presented

in the original language, with attached translation of these

documents into Armenian and/or English (in specially envisaged

cases the translation must be apostilled), for authentication of

which the Applicant is responsible. In case of revealing

discrepancies between the translation and the original of the

document, the Organizer makes a decision on the basis of the

translation.

11


July 07, 2011

3.1.11.Clarification of Documentation on Request for Proposals

3.1.11.1.Applicants are entitled to apply to the Organizer for clarification of

this RFP. The requests for clarification of RFP should be submitted

in the written form with the signature of the head of the organization

or another responsible person authorized by the Applicant.

3.1.11.2.Organizer, within reasonable period, should provide an answer to

any question received not later than 2 days prior to the deadline of

Proposal receipt (point 3.3.4.). If, in Organizer’s opinion, the given

question is of interest to all the Applicants, the answer copy

(without indication of the question source) should be announced to

all the Applicants via the same communication means used for

posting this announcement.

3.1.12.Amending Documentation on Request for Proposals

3.1.12.1.The Organizer is entitled to amend this Documentation on Request

for Proposals before the deadline for submission of the Proposals

but not later than 3 days prior to the submission deadline, except

for the cases when these amendments do not change the

significant conditions indicated in RFP.

3.1.12.2.All Applicants shall be immediately notified on the matter of such

amendments via the same communication means used for posting

this announcement.

3.1.13.Prolongation of the deadline of Proposals acceptance

3.1.13.1. If necessary, Organizer has the right to prolong the deadline of

Proposals acceptance, stipulated in subpoint 3.3.4. with notification

to all Applicants in compliance with the procedure, stipulated in

3.1.12.1.

3.2.Requirements to Applicants. Approval of compliance with the presented requirements

3.2.1. Requirements to Applicants

3.2.1.1. Any legal entity has the right to submit Proposals in accordance

with the rules and procedures prescribed in this Documentation. In

12


July 07, 2011

order to qualify for the best offer and for the right to conclude

Agreement, Applicant should comply with the following

requirements at the moment of the Proposal submission in

compliance with this Documentation on Request for Proposals:

a) Work experience in the relevant market not less than 3 years;b)Sustainable financial situation of the company;c) Organization should not be filed for bankruptcy, liquidation or reorganization; its property should not be arrested;

3.2.2. Requirements to documents, which prove the compliance of the Applicant

with the presented ones

3.2.2.1. Applicant should include in the Proposal Documentation the

following documents certifying its compliance with the above

mentioned requirements:

a) copies of constituent documents;b)copies of state and tax registration and certificates;c) reference about payment of the charter capital, signed by the organization head and chief accountant;d) reference certifying absence of court procedures in connection with liquidation or reorganization or arrest of its property signed by the head of organization;

3.2.2.2. Special requirements:

a) Reference about the Applicant's regional network (list of Applicant’s branches and agencies on the regions, with indication of their addresses and authorizations);b)Other documents, which, in Applicant’s opinion, certify his compliance with the set requirements, with the respective comments, elucidating on the purpose of submission of this documentation;c) Applicant’s Work History Reference List - the list of companies and contact persons that can provide information/reference (Form № 4).

13


July 07, 2011

3.2.2.3. All the indicated documents shall be attached to the Proposal by

the Applicant.

3.2.2.4. In case, when for some reasons, Applicant cannot present the

required documents, Applicant should propose a reference

elaborated in a free form, which explains the reason why the

required document are missing, as well as gives warranties to

Organizer about Applicant’s compliance with the given

requirements.

3.3.Submission and acceptance of Proposals

3.3.1. Prior to submission, the original Proposal and its copy should be properly

sealed in the envelopes (packages, boxes, etc.). The Proposal should be enclosed

in a sealed envelope with “Original Proposal” indication. Copy of the Proposal

should be sealed in envelope, indicated with words “Copy of Proposal”. The

following information should be indicated on each envelop:

“K-Telecom” CJSC (legal address: 4/1 Argishti str., Yerevan, Armenia);

Full business name of the Applicant and its mail address;

Full name of the RFP or the lot for which the Proposal is submitted.

It is advised to submit Proposals and other related documents and envelopes made of recycled paper.

3.3.2. Sealed envelopes with the Proposal and its copy are enclosed in one

external envelope, which should be sealed as well. The following information should

be indicated on the external document:

“K-Telecom” CJSC

4/1 Argishti str., Yerevan, Armenia

Original/Copy of the Proposal

Do not open before 17:00 o’clock (Yerevan time) 02/08/2011. It can be opened only at the Purchasing Committee meeting.

__________________________________________________________________________

(Complete name of the RFP, which the Proposal is submitted)

14


July 07, 2011

__________________________________________________________________________

(Number or Complete name of the Lot, which the Proposal is submitted)

______________________________________

______________________________________

(Full business name of the Applicant and its mail address)

3.3.3. Applicants should provide the delivery of their Proposals to the Organizer’s

location: “K-Telecom” CJSC (legal address: 4/1 Argishti str., Yerevan, Armenia). In

case of sending the Proposal by courier mail, it is necessary to notify the courier

service representative or courier about this order of Proposal delivery.

3.3.4. Organizer stops accepting Proposals at 17:00 o’clock (Yerevan time)

02/08/2011. Proposals, received later than the term indicated above, will be rejected

by the Organizer without consideration of their essence.

3.3.5. Organizer submits the reference to the person, who delivers the envelope,

about its receipt with indication of receipt time.

3.4.Amendment and call back of Proposals

3.4.1. The Applicant is entitled to change or call back already submitted Proposal

provided that a respective written application is received by the Organizer three

days prior to the deadline for Proposals submission (item 3.3.4.). The changing of

the Proposal is carried out in accordance with the procedure stipulated by this

Documentation on Proposal submission. The applications for changing of the

Proposals received after the deadline, set forth by the given item, would not be

considered and the Proposals will be considered by Organizer with their initial

content.

3.4.2. In the case of change of the Proposal, the Applicant has to prepare and

submit the following documents:

Application to the Organizer with the request to change the Proposal,

which has to be provided on the letterhead of the Applicant;

15


July 07, 2011

List of changes to be made in the Proposal specifying the documents of

the original Proposal, which are affected by the change;

New versions of the documents that are to be changed.

3.4.3. In the case of call back of the Proposal, the Applicant has to submit a

respective request to the Organizer on the letterhead of the Applicant.

3.4.4. The request on alteration or call back of the Proposal together with all the

documents that are to be attached shall be sealed in the envelopes, executed in

accordance with the items 3.3.1. – 3.3.2. The envelope shall additionally be marked

“Alteration of the Proposal” or “Call back of the Proposal”.

3.5.Evaluation of Proposals

3.5.1. General provisions

3.5.1.1. Evaluation of Proposals is executed by the Committee created by

the Organizer and other authorized persons (Purchasing Unit,

Working Group, experts and specialists), involved by the Organizer.

3.5.1.2. Evaluation of Proposals includes screening stage, negotiations (if

necessary), and evaluation stage.

3.5.2. Screening stage

3.5.2.1. Within the framework of the screening stage the Organizer verifies:

Accuracy of Proposals elaboration and their compliance with

essential requirements of this RFP Documentation and RA

legislation;

Compliance of Applicants with requirements of this

Documentation;

Compliance of Commercial and Technical Proposal with

requirements of this Documentation.

In case of Agreement submission, the compliance of the

Agreement provisions with the RA legislation and requirements of

the Organizer.

3.5.2.2. Within the framework of the screening stage, Organizer may

request Applicants for clarifications or additions to their Proposals,

16


July 07, 2011

including submission of the absent documents that do not affect the

terms of the Proposal.

3.5.2.3. During the review of Proposal execution accuracy, the Organizer

has the right to ignore minor drawbacks and mistakes, which do not

affect the essence of the Proposal, which refer to the due execution

of the Proposal. The Organizer, upon the written consent of the

Applicant, is also entitled to correct the apparent arithmetic or

grammar errors.

3.5.2.4. Based on the results of screening stage the Organizer has the right

to reject Proposals, which:

Significantly do not comply with requirements to the elaboration

of this Documentation;

Are submitted by the Applicants, that do not comply with

requirements of this Documentation;

Contain provisions, which do not essentially comply with

technical, commercial or contractual requirements of this

Documentation;

Contain obvious arithmetic and grammar errors, with corrections

of which Applicant did not agree;

Do not comply with the RFP requirements;

Do not comply with the requirements of RA legislation.

The Organizer is entitled to reject Proposal at any stage, if it becomes

evident that the Applicant had provided false data, and all Proposals, if none

of them meets the requirements set forth in relation to the Applicants or

execution of the Proposal.

3.5.3. Conducting negotiations

3.5.3.1. After the consideration and evaluation of Proposals, the Organizer

is entitled to conduct negotiations with any Applicant on any

provision of this Proposal.

17


July 07, 2011

3.5.3.2. Negotiations are held in one or several stages. The succession

order of negotiations is defined by the Organizer. While conducting

negotiations, the Organizer should avoid disclosing any information

on the content of the received Proposals, as well as the process

and content of the negotiations to other Applicants, except for the

cases when such Proposals have status of public offer.

3.5.3.3. Any negotiation between the Organizer and the Applicant is

deemed to be confidential.

3.5.3.4. None of the Parties, without consent of the other Party, shall

disclose any technical, price or other marketing information, which

relates to those negotiations to any other person.

3.5.3.5. As a result of the negotiations, the Organizer may propose:

- To any Applicant, to act as a general executor and involve as a

co-executor another Applicant, or an external organization;

- To particular Applicants to join in a collective Proposal.

3.5.3.6. Each Applicant has the right to refuse this Proposal without any

consequences and participate in the further procedure of RFP

independently in case of Proposal execution prescribed by the item

3.5.3.5.

3.5.4. Evaluation stage

Within the framework of evaluation stage the Organizer evaluates and

compares Proposals (the evaluation of each lot is conducted separately, if

there are multiple lots), and ranges them according to the degree of

preference for Organizer, on the basis of the Financial-Commercial (80.0%)

and Technical Criteria (20.0%).

3.6.Decision-making

3.6.1. At the closed executive session the Tender Committee established for RFP

processes makes a decision on conducting additional stages, or on determination of

the best offer and Agreement conclusion, or about closing the given procedure of

18


July 07, 2011

RFP without determination of any Winner, if none of the Applicants meets the

requirements of this procedure and/or RA legislation.

3.6.2. In case, the Proposal of any of Applicants appears significantly better than

other Applicants’ Proposals, and this Proposal completely complies with the

Organizer’s requirements, Organizer determines this Applicant as the best offer

provider and signs an Agreement with this Applicant.

3.6.3. If, in the opinion of the Tender Committee, no opportunities for improvement

of Applicants’ Proposals are envisaged and conducting further stages is pointless,

the Tender Committee is entitled to make a decision about closing the RFP

procedure.

3.6.4. Decision of the Tender Committee is documented by the Protocol based on

the minutes of the Tender Committee Session.

3.7.Agreement conclusion

3.7.1. Agreement between Organizer and Applicant that provided best offer is

concluded within 30 days after the end of RFP procedures and the execution of the

Protocol on its results, or within other time limits defined in RFP or within the period

specified by the Organizer.

3.7.2. Terms of Agreement are defined in accordance with RFP and requirements

set forth by legislation.

3.8.Rights of the Applicant that provided the best offer for RFP

3.8.1. The Applicant that provided the best offer of the RFP process is granted with

the right to conclude agreements for provision of works, goods or services specified

in the lots (Section 2). The agreements for provision of works, goods or services are

concluded for the period of 1 (one) year or other timeline agreed by both parties

with extension possibility, within the terms stipulated by the Organizer or the given

Documentation.

3.8.2. The Applicant that provided the best offer before the date of conclusion of

agreement on provision of specified works, goods, or services has to submit to the

Organizer a confirmation letter of contract conclusion.

19


July 07, 2011

3.8.3. In the case the Applicant that provided the best offer due to whatever reason

refuses to conclude the contract, he forfeits his right and is obliged to reimburse the

damages caused to the Organizer as a result of avoiding the Agreement conclusion.

In case all Applicants that provided the best offer refuse to conclude the contracts,

the Organizer may repeat RFP procedure within 45 days or cancel the RFP

procedure.

3.9.Notification of Applicants about the results of Request for Proposals

3.9.1. Organizer within five working days following the determination of the best

offer publishes the information about RFP results on its website which indicates:

a) Title of the Applicant that provided the best offer;

b) Brief description of the subject, place, date and number of protocol of the

Tender Committee.

20


July 07, 2011

4. Samples of standard forms of documents, included in the Annex

4.1.Letter about offer submission (Form 1)

4.1.1. Form of letter about offer submission

B e g i n n i n g o f f o r m

«_____»_______________№________________________

Dear Sirs!

Having studied the Notification on holding the Request for Proposals processes, which has

been published in K-Telecom CJSC website at www.mts.am/procurement on dd/mm/yyyy

and Documentation on the Request for Proposals on (Subject of RFP)___________, and

accepting the requirements of Request for Proposals stipulated by them,

_______________________________________________________________________,(Applicant’s full name with indication of organizational-legal form)

Registered at

_______________________________________________________________________,(Applicant’s legal address)

Wishes to participate in the RFP process with a Proposal to conclude an Agreement on provision the following works, goods or services:

________________________________________________________________________(Brief description)

In accordance with Technical/Commercial Proposal, Schedule on provision the works, goods or services, Cost Estimate, which are the integral parts of this letter and which jointly with this letter constitute the Proposal for the total amount of

For organizations registered in RA:

Bottom-line price of Proposal in AMD, including VAT ________________________________(Bottom-line price of Proposal in AMD, including VAT)

For organizations registered outside RA:

Price for product/service ________________________________Taxes if applied ________________________________Costs for delivery and other costs if available ________________________________Discounts, if applied ________________________________

21



July 07, 2011

Total price in USD ________________________________

This Proposal has legal status of offer and is valid at least 3 months from the date of its submission.

This Proposal is complimented with the following documents, including the integral annexes:

1. Technical/Commercial Proposal for provision of works, goods and services (Form 2)- on ____ sheets;

2. The draft Agreement - on ____ sheets;3. Documents, which prove Applicant’s compliance with the established

requirements - on____ sheets;4. Password of the electronic version of the documents submitted.

____________________________________(Signature, stamp)

____________________________________(Full name and position of the Signatory)

E n d o f f o r m

4.1.2. Instructions for filling in the form:

The letter should be executed on Applicant’s official letterhead form. The date and number

should be indicated by the Applicant in the letter in accordance with the rules of document

flow established in its organization.

Applicant should indicate its full title (with indication of organizational-legal form) and legal

address.

Applicant should indicate the cost on provision of the works, goods or services in figures

and words, in AMD and/or US dollars, VAT inclusive.

The letter should be signed and sealed according to requirements of subpoints 3.1.5.

22


July 07, 2011

4.2.Technical/Commercial Proposal on provision of works, goods or services (Form 2)

4.2.1. Form of Technical/Commercial Proposal on provision of the works, goods or

services (Form 2)


Annex 1 to the letter about offer submissiondated “____”_____________ city, №__________

Technical/Commercial Proposal on provision of the works, goods or services

Applicant’s title and address: _________________________________

(Here Applicant in free form describes its Technical/Commercial Proposal on provision of the works, goods or services in accordance with requirements of Section 2)

____________________________________(Signature, seal)

____________________________________(Full name and position of the Signatory)

E n d o f f o r m


Date and number of Proposal should be indicated by the Applicant in accordance with the

letter about offer submission. Applicant indicates its business name (including

organizational-legal form) and its address.

Technical/Commercial Proposal describes all points of Section 2. Applicant has the right to

indicate, that it agrees with the draft Technical specification, indicated in Section 2.

23


July 07, 2011

Applicant’s Questionnaire (Form 3)

4.2.3. Applicant’s Questionnaire form


Attachment 2 to the letter about offer submissiondated “____”_____________ city, №__________

Questionnaire for Applicants

Applicant’s title and address _________________________________

№ Title Applicant information1. Applicant’s organizational-legal form and

business name 2. Founders and Shareholders (specify the

names and the organizational-legal form or the full name of all the shareholders whose share in charter capital exceeds 10%)

3. Certificate of registration in the Uniform State Register of Legal Entities(date and number, issued by)

4. Applicant’s tax code5. Legal address6. Postal address7. Branches: name all the branches and their

e-mail addresses8. Bank details (name and address of the

bank, number of the Applicant’s bank account, bank telephones, other bank details)

9. Applicant’s phone numbers(with the indication of the city code)

10. Applicant’s fax number(with the indication of the city code)

11. Applicant’s e-mail address

24

http://www.multitran.ru/c/m.exe?t=3880901_1_2

http://www.multitran.ru/c/m.exe?t=3880901_1_2


July 07, 2011

№ Title Applicant information12. Full name of the Applicant’s head who is

entitled to sign pursuant to the Applicant’s constituent document, with the indication of the position and contact telephone

13. Full name of the Applicant’s Chief Accountant

14. Full name of the Applicant’s responsible person with the indication of the position and contact telephone

____________________________________(Signature, stamp)

____________________________________(Full name, position of the signatory)

E n d o f f o r m


Date and number of Proposal are indicated by the Applicant in accordance with the letter

about offer submission.

Applicant indicates its business name (including its organizational-legal form) and address.

Applicants must fill in the above mentioned table in all positions. In case of absence of any

data, indicate the word “none”.

In row 8 “Bank details…” are indicated the details, which will be used during Agreement conclusion.

25


July 07, 2011

Applicant’s Work History Reference List (Form 4)

4.2.5. Applicant’s Work History Reference List


Attachment 3 to the letter about offer submissiondated “____”_____________ city, №__________

Reference List

Applicant’s title and address _________________________________

Work History Reference Table

N Company Name

Project Name/Type

Project Start Date

Project End Date

Contact Person Name

& Phone Number

1 2 3 4 5 6 7 8 9

____________________________________(Signature, stamp)

____________________________________(Full name, position of the signatory)

E n d o f f o r m

26


July 07, 2011

Technical Specification (Annex 3)

Main functions1. Generate and send outgoing and processing incoming TAP files (test and commercial

files) with an option for receiving erroneous files;

2. Generate and send outgoing and processing incoming XML packages with an option for

receiving erroneous packages;

3. Support of RRP;

4. Rolling back calls, TAP files and XML packages;

5. Able to view TAP/RAP files or XML packages;

6. Calculate markups according to IOT regulations;

7. Work with financial documents (generating, issuing and payment monitoring of invoices,

additional invoices and credit notes for roaming partners, registering and payment

monitoring of invoices received from roaming partners, generating a consolidated

roaming partner invoice for roaming services provided to its subordinate operators);

8. Receive, generate and send fraud reports;

9. Generate analytical reports on mutual payments between roaming partners (with an

option for creating and plugging in user reports);

10.Monitoring and managing data processing jobs;

11.Accounting for daylight shifts and the time difference between the current local time at

the switches and UTC (Coordinated Universal Time);

12.Setting up processing schedules for incoming and outgoing data;

13.Maintain dictionaries of countries, currencies (multicurrency support) and exchange

rates;

14.Create archive copies of sent and received files and documents with an option for

reloading TAP files or XML call packages into the database;

15.To have a file interface option providing integration with the Eskadenia billing system;

16.Collect statistics on file processing;

17.Administration.

27


July 07, 2011

Supported Technologies Processing TAP files in compliance with Transferred Account Procedure Data

Record Format Specification Version (TD57v.3.xx) Support all TAP versions (TAP1, TAP2, TAP2+, TAP3); Processing erroneous TAP files — Return & Reject procedure; Exchanging fraud reports in compliance with version 2.1 of the document “High

Usage Report Format and Contents” (FF04); UMTS; GPRS; Location Services; Content Transaction; Service Center Usage.

SYSTEM Requirements1. Support of different phases of roaming (testing/commercial, unilateral/bilateral) for

different types of roaming (Voice, CAMEL, GPRS, 3G).

2. Support of CAMEL-roaming including:

Correct presentation of «dialed digits», «called number», «camel destination number» in generated TAP files

Correct rating based on «camel destination number» value3. Support of GPRS-roaming including:

Possibility to generate test TAP files with GPRS records for partners already launched commercial Voice – roaming.

Possibility to choose the rating method for partial GPRS records which belongs to 1 GPRS session (aggregate or rate separately)

Representation of GPRS records according to GSMA PRDs.

4. Processing RAP files;

5. Possibility to load/generate RTDR files on both daily and monthly basis.

6. Possibility to configure additional charges for each RP (for ex. CAMEL Invocation Fee)

7. Possibility to load/generate AA.14 documents in RAEX XML format.

8. Should define roaming rates for each roaming partner, rules for receiving incoming

and generating/sending outgoing documents, rules for additional checks and

modifications of incoming and outgoing data on calls, etc.

9. Make it possible to divide roaming partners into groups by any suitable attribute. As a

28


July 07, 2011

result, data exchange can be managed at the level of partner groups.

10.Make it possible to assign to one company multiple TAP codes and IMSI ranges.

11.The system should be able to handle files received from network nodes in near real-

time.

12.Should provide call transfer management for every roaming flow in accordance with

the type of a call.

13.Should be able to set certain rules of call processing for roaming data flows relevant

for the call origination date, the corresponding call events are processed in

accordance with those rules. If receiving of call events is disabled, they are rejected

and included into the generated RAP file with a user error. A RAP file generation

follows a TAP file rejection with reference to either its sender (if receiving through the

incoming flow is disabled) or its recipient (if receiving through the linked outgoing flow

is disabled).

14.The roaming data exchange must include automated receiving and processing of

incoming and generating and sending of outgoing TAP files (test and commercial

files). The system should be able to handle various TAP format versions.

15.Ability to apply discounts on TAP level.

16.Call data that are received from roaming partners, are to be saved in separate

database and sent to the billing system.

17. Incoming TAP files are to be validated in compliance with the Transferred Account

Procedure Data Record Format Specification Version (TD57).

18.NRTRDE (TD.35) support.

19.The system should automatically generate RAP files in response to the received TAP

files.

20.Outgoing TAP files are to be generated based on the data on visitor calls received

from the billing system. The files should be generated automatically, either for all

roaming partners or for each partner, in accordance with individually specified

schedule. Generated TAP files are to be sent to the recipients in accordance with the

document delivery rules specified for each of them.

21. Invoices for roaming partners are to be generated based on the data on outgoing TAP

files, which are stored in the database. The system also should provide pay-off check

29


July 07, 2011

tools. In case of an overdue payment, it should generate additional invoices.

22.Generate a credit/debit note for roaming services.

23.Generate financial documents that are to be sent to the recipients in accordance with

the rules that are defined for each of them individually.

24.Register Incoming invoices and other financial documents to the database. The

invoice data are to be reconciled with the data of TAP files included to the invoice.

25.Generate automatically outgoing Fraud reports in accordance with the rules defined

for each roaming partner individually, and also be able either e-mail or fax to the

recipients.

26.Register Incoming Fraud reports are registered in the database.

27.Have additional tools for generating various statistics reports;

28.Monitoring data handling processes and their management;

29.Accounting for daylight shifts at the switches,

30.Maintaining dictionaries of exchange rates and other reference data;

31.Generating archive copies of incoming and outgoing files and documents;

32.Collecting statistics on file processing.

33.Transaction history (change type, change date, changed by, …)

34.Roaming partner historical data, for ex.

Implementation Status change(Test -> Commercial, Commercial->Inactive) Service addition (GPRS Roaming, etc)

35.Process full logging, for ex. to keep each process name with start and end timestamps

and result

36.FTP client for uploading/downloading TAP files to/from external FTP servers.

37.TAP file checking in accordance with GSMA PRDs (duplicates, oldness, etc.)

38. Integration with SAS analytical system.

39.Reporting part with templates and ability to create own reports.

40.Process rollback in different phases of processing (Rating, file generation, file loading).

41.Possibility to mass settings addition/change/deletion via APIs, for ex.: RP provisioning/status change Tariff addition/change/deletion Service addition/change/deletion

30


July 07, 2011

Zone addition/change/deletion, etc.

Roaming Partners’ Data Maintenance

Provide facilities for maintaining an electronic database of roaming partners. Each partner’s details are entered into a registration card. The data is stored under the following categories:

general information; contact information; rates; document addressing control; additional information; test SIM card records; Number range records.

Be able to mask errors in incoming TAP files received from a specified group of operators. This ensures correct processing of incoming files with syntax elements.

31


July 07, 2011

1. TAP Files Processing

TAP files processing should include performing the following functions: receiving and processing incoming test TAP files and commercial TAP files; generating and sending outgoing test TAP files and commercial TAP files; Re-loading TAP files and notification files into the database.

1.1 Receiving and Processing Incoming Test TAP Files and Commercial TAP Files

The incoming TAP file processing procedure should include the following operations: converting incoming binary TAP files in ASN.1 format to XML view; checking files for errors; generating RAP files upon detecting errors in incoming files (this option could be set

for each partner individually); analyzing received TAP files and saving the essential data on the files and on call-

specific information they contain in the database tables; saving XML views of the original incoming TAP files into the database, the files

having been converted to the current TAP version and added with data required for their further processing;

archiving incoming TAP files

The error check of incoming TAP in accordance with TD.57 requirement,:

1.2 Generating and Sending Outgoing TAP Files

Outgoing TAP files are to be generated in the ASN.1 format. They are to be generated either in accordance with the schedule or by the user command.

An individual schedule for TAP file generation is to be specified for each roaming partner. Depending on the process startup options, outgoing TAP files are to be generated either for all roaming partners simultaneously or individually for each partner.

The files are to be generated for roaming operators; calls are grouped within TAP files by their senders.

Ability to generate multiple TAP files for 1 partner based on records quantity.

To support of single TAP file generation for roaming operators.

Archiving of outgoing TAP files.

1.3 Reloading TAP Files (or XML Packages) and Notification Files into the Database

In order to recover the deleted internal XML representation of a file in the database, it should have an option for reloading TAP files (or XML packages with data on calls) into the database.

When receiving a file, the system is to check whether the call event data it contains is identical to the records stored in the call table (including cancelled calls), and to the call-specific data on the amounts of charges and taxes.

32


July 07, 2011

2. Reject and Return Procedure

To provide full support for RRP in accordance with TD32 specification.

Calls received in TAP files that are rejected based on the additional checks and modifications defined for a roaming partner. If sender operators have the RRP Support option enabled, the calls that meet these conditions are to be rejected forming a part of a generated RAP file. Otherwise, a RAP report in a text format is generated and the TAP file is rejected as a whole.

2.1 Generating Outgoing RAP files

To enable automatic generation of RAP files, this will be sent to the roaming partner. RAP files may contain information.

2.2 Processing Incoming RAP Files

To register incoming RAP files received from the roaming partner in response to erroneous TAP files being sent to this partner. Rejected calls are rolled back.

3. Viewing and Editing TAP and RAP Files

Viewing and editing of TAP, RAP and notification file data.

To enable the user to process files in the ASN, XML and NRTRDE formats and export files (either separately or in packages) from one format into the other.

4. Roaming Markups

Calculating Markups for Roaming Calls

According to the roaming markup calculation rules specified for a roaming partner, to calculate the markups for the received TAP file: roaming leg cost which is added when a home subscriber roaming call is recorded; Roaming markup.

Calculation Procedures

Roaming markup calculation procedure to set in accordance with parameters, for ex.: call cost multiplication factor; PL/SQL function; Other

33


July 07, 2011

5. Working with Financial Documents

Monitor the balance with roaming partners, i.e. the difference between the total amount of incoming and outgoing financial documents based on the data on financial documents.

To post credit and debit notes and also to modify the initial balance amount of Roaming partner balances.

To obtain roaming partner account balances reports.

Invoices are to be generated either based on the currency rates relevant for the date of files/calls or based on the common rate.

6. Generating and Sending Outgoing Invoices

To generate two types of outgoing invoices: For all roaming partners having TAP files which have not been previously included

into any other invoices; For individual roaming partners.

To generate invoices of TAP files for certain periods.

To select files either automatically or manually.

To invoice also those TAP files, for the period prior to the calculation period, which have not been invoiced yet, to be able to discount specified invoices.

Generate roaming invoices with detailed information on services.

6.1 Generating Single-Addressed Consolidated Invoices for Multiple Partners

Generate consolidated TAP file invoices addressed to one partner but containing information about the addressee’s subordinate operator’s files.

6.2 Generating Additional Invoices

Generate additional invoices in case of a roaming invoice clearance delay.

Additional invoices to generate automatically or manually, in which case the total in the additional invoice is to be specified by the user.

6.3 Generating Credit/Debit Notes

Generate credit/debit notes.

To generate the notes for the specified amount.

Generate Credit note based on call data.

Convert of the file currency into the invoice currency (to perform in accordance with the invoice generation rules).

Rate calculation based on calls or file data.

34


July 07, 2011

6.4 Generating Invoices for Discount

Generate invoices for the discount provided to a roaming partner. Generate invoices for any period.

6.5 Invoice Printable Forms

Generate invoice addressed to a roaming partner.

Generate invoice, the form of which includes bank details necessary for settlements with a particular partner. The created printable forms are to be stored in the database. Generate bank details in the invoice.

6.6 Registering Incoming Invoices and Other Financial Documents

Incoming invoices and other financial documents received from roaming partners in electronic format are to be registered in the database.

Make reconciliation of the data of the registered invoice against the data of TAP files received from the partner and included in the invoice.

7. Working with Fraud Reports

Automatically generate and send (via e-mail) fraud reports to the roaming partners – either simultaneously to all of them or to individual partners only. All generated fraud reports are to be stored in the database.

-A fraud report contains information on all types of traffic.

-The option to regenerate a fraud report should be provided.

Incoming fraud reports are also to be registered in the database.

8. Generating Analytical Reports

The reporting tool should include and not be limited with the below mentioned reports: Operator Income Change Report; Outgoing TAP Files Report; Incoming TAP Files Report; Roaming Partners and Countries Report; Skipped Incoming/Outgoing TAP Files Report; Missing Incoming/Outgoing TAP Files Report Roaming Traffic Reports; Roaming Partners Settlement Reports(Account Balance Report, Issued/Accepted

Charges Report); Partners Rating Report; Test SIM Cards Usage Report(in the Home Network and in the Roaming Partners’

Networks); Currency Exchange Rates Dynamics Reports;

35


July 07, 2011

Predefined report parameters should be customized by the user.

Also should enable users to create own reports. The generation of the reports should be performed both automatically and manually, with possibility to schedule and distribute via e-mail. The reporting tool should be capable to export reports in different formats (pdf, csv, xls, etc.).

Operator Income Change Report

Generate a report to present information on revenues the operator has earned by providing roaming services for roamers and visitors and on income changes within the reported period.

Outgoing TAP Files Report

Generate a report to represent a list of TAP files generated within the reported period.

Incoming TAP Files Report

Generate a report to represent a list of TAP files received within the reported period.

Roaming Partners and Countries Report

Generate a report containing the summary information on roaming partners that are provisioned in the system (Country, Partner’s Full Name, Operator name, Short Code, Roaming activation statues and dates) both for inbound and outbound.

Skipped Incoming/Out coming TAP Files Report

Generate a report to represent lists of number omissions in incoming and outgoing TAP files and of number omissions in incoming RAP files detected within the reported period.

Roaming Traffic Reports

Generate a Roaming Traffic Report which contains statistical information about the volume of roaming services provided within the reported period.

Roaming Partners Settlement Reports

Generate Reports on settlements with the roaming partners: Account Balance Report; Issued/Accepted Charges Report.

Account Balance Report should contain a summary of the current balance for all roaming partners. The balance is to be calculated in any currency for a specific period of time.

Issued Charges Report should contain information on the total number of invoices issued to/accepted from the partner within the reported period.

36


July 07, 2011

Partners Rating Report

Generate Partners Rating Report including tables and diagrams to illustrate the statistics of the roaming partners’ rating based on the amount of roamers and visitors. The total charges for visitors (roamers) within the period specified by the user; The total amount of visitors (roamers) who made calls inside the mobile operator’s

network within the reported period.

Test SIM Cards Usage Reports

Generate Test SIM Cards Usage Reports containing information on the usage of test SIM cards within the reported period: Inside the roaming partners networks; Inside the home network by the roaming partners.

Currency Exchange Rates Dynamics Reports

Generate reports on: the dynamics of exchange rates for any currency pairs within the reported period; The dynamics of all exchange rates during the specified period.

Customizable Reports

Generate and create other/own reports which would contain customized data and would be presented in the format chosen by the user.

9. Monitoring and Managing Data Processing Jobs

The system should support the following monitoring functions: logging the system operation data; monitoring the generation of outgoing TAP files; monitoring the incoming TAP file processing; Identifying versions of installed server side applications.

10. Accounting for Daylight Saving Shifts

System should enable conversion to Daylight saving time/Standard time performed at any operator’s home switch. To store the time shifting rules specified for each home switch. The time shifts to Daylight saving time/Standard time performed at the switch is to be either automatically or manually registered in the system.

11. Setting Up Processing Schedules for Incoming and Outgoing Data

Provide each partner with an individual schedule for the processing of incoming TAP files and the generation of outgoing TAP files.

Any outgoing TAP file generation schedule has to be set up for each roaming partner separately.

37


July 07, 2011

12. Maintaining Dictionaries

Dictionary of Currencies and their Exchange Rates

Support the multicurrency operation applications to include both rating/national currency and SDR rate. A currency dictionary and an exchange rate dictionary for each currency are to be updatable and editable.

Country Dictionary

Maintain the dictionary of countries on the territory of which the operator’s roaming partners reside. The country dictionary contains the names of the roaming partners’ countries together with country codes (ISO and ITU).

Dictionary of Payment Details

Maintain the dictionary of details of the bank that serves the telecom operator. These details are to be in printable forms of generated invoices.

13. Data Archiving

Provide tools for creating backup copies of incoming and outgoing files and documents.

The backup copies of outgoing documents are to be stored in the file system and, like other files and documents, to be generated in accordance with individual schedules.

The incoming documents are to be backed up at the time they are received.

14. Collecting Statistics on File Processing

Enable the user to collect and store the information about each billing system data exchange file or package: start time of file processing/generation; end time of file processing/generation; number of CDRs contained in the file; file size in bytes (in XML view); number of files used as raw data when generating the file.

15. System Administering

User Authentication and Access Control User access to business functions performed by client applications are to be

restricted by granting certain groups of users different access rights in order for them to perform different business functions.

Access rights are to be extended or restricted depending on the user’s job description.

The access control procedure for business functions is to be managed with the help of visual interface.

38


July 07, 2011

Logging User Operations

Information about all database modifications made by the user is to be kept in the “history” which include the date and the time when the modifications were made and the names of the users who made them. The history is to be displayed in such a way which allows the user to view the modifications easily. This should be achieved by saving every new version of the modified database and displaying all modified versions alongside the current version.

16. Receiving Rated Data from the Billing System

To use the billing system rated call detail records in order to prepare outgoing TAP files.

All data required for the rating calculations is available from the billing system.

Exchange data with the billing system in accordance with a specified schedule.

After the data is received, the system should record the processing results into a system log.

17. Uploading Data from - into the Billing System

Send data on international roaming services used by the operator’s home subscribers to the billing system.

The process of sending data to the billing system (“uploading”) is to be initialized either in accordance with a specified schedule or upon request from the billing system. adding information on charges; uploading data in a specified file format; Logging data uploading results.

18. Downloading Incoming TAP Files Data

Store records which link stored calls to their source packages.

The user should set up the system parameters to enable or disable the uploading of call data of those subscribers which use prepaid cards.

19. Downloading Visitor Calls Data

The system should download call detail records. The downloading should be performed either automatically, in accordance with the schedule specified in the workstation system registry, or manually.

20.Re-pricing of Roaming CallsThe system should be able to re-price (re-rate) calls based on different parameters.

The system should support user-defined rules, for example possibility to split charge

into 2 parts using the user-defined logic.

During re-pricing the original charge received from roaming partner should be kept for

39


July 07, 2011

inter-operator mutual calculations.

21.Uploading Incorrectly Rated or Rejected Calls for Re-RatingThe system should be able to separate rejected calls by specifying the cause of

rejection. Incorrectly rated or rejected roaming calls could be uploaded for re-rating

(re-processing).

22.Tariffication based on different parametersThe system should be able to rate calls based on different parameters, which are:

Partner

Event type

Destination

Special days

Time band

Duration

Session volume QoS (Packet data speed)

Technical Specification of existing hardware (Annex 4)

ServerCPU

RAMLOCAL STORAGE

OSFreq. Qty Type RAID Type HDD

Database3.0

GHz 4X5450

Quad Core8.00 GB

RAID 1+0, RAID 5 2.3TB

Windows Server 2003 Enterprise x64, SP2

Application3.0

GHz 25160 Dual

Core4.00 GB RAID 1+0 136GB

Windows Server 2003 Standard, SP2

Backups and test

3.0 GHz 2

5160 Dual Core

4.00 GB RAID 0 1TB

Windows Server 2003 Standard x64, SP2

40