Escolar Documentos
Profissional Documentos
Cultura Documentos
FOR THE
Procurement of
Convergent Billing System
(CBS)
Purchaser: Afghan Telecom Corporation
RFP
Table of Contents
ITB .................................................................................................... 3
Conditions of Contract ..................................................................... 19
Number of License Required ......................................................... 111
Technical Requirements ................................................................ 112
List Of Acronyms ........................................................................... 226
Bidding Forms ............................................................................... 228
ITB
Table of Contents
SCOPE & DEFINITION OF PROJECT .................................................................................................................................................................4
GENERAL PROCUREMENT INFORMATION .....................................................................................................................................................4
CLARIFICATION OF TERMS ............................................................................................................................................................................5
CORRUPT OF FRAUDULENT PRACTICES .........................................................................................................................................................5
CONFIDENTIALITY .........................................................................................................................................................................................6
Qualification OF BIDDERS .............................................................................................................................................................................7
SUBCONTRACTORS .......................................................................................................................................................................................7
BIDDERS CONSORTIUMS AND JOINT VENTURES ...........................................................................................................................................8
COST OF BIDDING .........................................................................................................................................................................................9
BIDDING DOCUMENTS .................................................................................................................................................................................9
CLARIFICATION OF BIDDING DOCUMENTS ....................................................................................................................................................9
AMENDMENT OF BIDDING DOCUMENTS..................................................................................................................................................... 10
COMPOSITION OF BID ................................................................................................................................................................................ 10
STATEMENT OF COMPLIANCE TO TECHNICAL SPECIFICATIONS .................................................................................................................... 11
BID PRICE AND BID CURRENCY .................................................................................................................................................................... 11
BID SECURITY ............................................................................................................................................................................................. 12
SUBMISSION OF BIDDS ............................................................................................................................................................................... 13
BID OPENING .............................................................................................................................................................................................. 13
MODIFICATION, SUBSTITUTION, AND WITHDRAWAL OF BID ....................................................................................................................... 13
AUTOMATIC BID REJECTION ....................................................................................................................................................................... 14
BID EVALUATION AND AWARD CRETERIA ................................................................................................................................................... 15
PRELIMINARY EXAMINATION ..................................................................................................................................................................... 15
DETAILED TECHNICAL EVALUATION ............................................................................................................................................................ 16
DETAILED FINANCIAL EVALUATION ............................................................................................................................................................. 16
CLARIFICATION OF BIDS .............................................................................................................................................................................. 17
AFGHAN TELECOM S RIGHT TO ACCEPT OR REJECT ANY ALL BIDS ............................................................................................................... 17
AFGHANTELECOMS RIGHT TO VARY QUANTITIES ....................................................................................................................................... 17
SIGNING OF CONTRACT .............................................................................................................................................................................. 17
TRAINING REQUIREMENTS ......................................................................................................................................................................... 18
ITB
General
ITB
2.3 For clarification of issues over email, please keep cbs@afghantelecom.af in cc and
m.hamid@afghantelecom.af, saboor.khawaja@afghantelecom.af in to fields.
2.4 Interested eligible Bidders may obtain Bidding Documents from:
Afghan Telecom Corporation,
Procurement Department,
Post Parcel Building, 4th Floor
Mohammad Jan Khan Watt
Kabul, Afghanistan
Phone Number: +93 (0) 20 210 4440
Email: saboor.khwaja@afghantelecom.af
Website: http://www.afghantelecom.af
2.5 Interested local Bidders should register with Afghan Telecom Corporation by submitting a
nonrefundable fee of USD $20.00 via check or wire transfer. Only registered Bidders will
receive a complete set of bidding documents in English from Afghan Telecom, will receive
answers to the submitted clarification questions on the bidding documents, and will
receive automatic notice of answers and of addenda to the bidding documents. As
an alternative, a hard copy set of the bidding documents may be purchased by
interested Bidders on submission of a written application to the address above and upon
payment of a nonrefundable fee of USD $20.00. and for those bidders which applies from
outside of Afghanistan and online will receive the RFP free of cost .
2.6 A pre-bid conference that potential Bidders may attend will be held on 7-Nov-2012.
3. Clarification of Terms
3.1 The terms Afghan Telecom and Purchaser may be used interchangeably throughout the
bidding documents.
3.2 The terms Supplier and Bidder may be used interchangeably throughout the bidding
documents.
3.3 Throughout the Bidding Documents, the term "in writing" means communicated in written
form (e.g., by mail, email, fax, or scan) with proof of receipt.
3.4 The term "days" means calendar days unless a different meaning is evident from the context.
3.5 The term Contract, unless otherwise defined, refers to the ultimate goal of this tender, which
is for Afghan Telecom to purchase a real-time convergent billing and charging and
interconnect settlement system (CBS) from a Bidder in a binding legal arrangement.
ITB
4.2.1 Corrupt Practice means the offering, giving, receiving or soliciting of anything of value
to influence the action of an official in the procurement process or in Contract
execution; and
4.2.2 Fraudulent Practice means a misrepresentation of facts in order to influence a
procurement process or the execution of a Contract to the detriment of the Afghan
Telecom, and includes collusive practice among Bidders (prior to or after Bid
submission) designed to establish Bid prices at artificial non-competitive levels and to
deprive the Borrower of the benefits of free and open competition;
4.3 Bidders, separately or as part of a Consortium or Joint Venture and to include manufacturers,
shall not be under a declaration of ineligibility for corrupt and fraudulent practices issued
by Government of the Islamic Republic of Afghanistan. Any bidders who are black listed or
are under the process of being black listed shall not be eligible to participate this bidding
process. Afghan Telecom shall reject all bids offered by such Bidders, whether
independently or as part of a Consortium or Joint Venture, and they shall not be considered
for the Bid Evaluation.
4.4. Afghan Telecom will reject a proposal for award if it determines that the Bidder recommended
for award has engaged in corrupt or fraudulent practices in competing for the Contract.
5. Confidentiality
5.1. Except if otherwise specified, the "Receiving Party" (either Afghan Telecom or the
Supplier) shall keep confidential and shall not, without the written consent of the other
party (the Disclosing Party), divulge to any third party any documents, data, or other
information of a confidential nature (Confidential Information) connected with this
tender and furnished directly or indirectly by the Disclosing Party prior to, during, or
upon conclusion of this tender.
5.2. Notwithstanding Clause 5.1:
5.2.1. The Supplier may furnish to its subcontractors and support service suppliers Confidential
Information of Afghan Telecom to the extent reasonably required for them to
determine costs and work related to the bid and to furnish such costs to the Supplier.
5.2.2. In which event the Receiving Party shall ensure that the person to whom it furnishes
Confidential Information of the Disclosing Party is aware of and abides by the
Receiving Partys obligations under this Clause 5 as if that person were party to
the Contract in place of the Receiving Party.
5.3. Afghan Telecom shall not, without the Suppliers prior written consent, use any Confidential
Information received from the Supplier for any purpose other than evaluation of its
bid.
5.4. The Supplier shall not, without Afghan Telecoms prior written consent, use any
Confidential Information received from Afghan Telecom for any purpose other than
those that are required to prepare and submit a bid.
5.5. The obligation of a party under this Clauses 5, however, shall not apply to that information
which:
5.5.1. Now or hereafter enters the public domain through no fault of the Receiving Party;
ITB
5.5.2. Can be proven to have been possessed by the Receiving Party at the time of
disclosure and that was not previously obtained, directly or indirectly, from the
Disclosing Party;
5.5.3. Otherwise lawfully becomes available to the Receiving Party from a third party that has
no obligation of confidentiality.
5.6. The provisions of this Clause 5 shall survive the conclusion of the tender process for three
(3) years.
Instructions to Bidders
6. Qualifications of Bidders
6.1. By submission of documentary evidence in its bid, the Bidder must establish to Afghan
Telecoms satisfaction:
6.1.1. That it has the financial, technical, and production capability necessary to
perform the Contract, meets the qualification criteria specified and has a successful
performance history. If a prequalification process has been undertaken for the
Contract(s) for which these Bidding Documents have been issued, the Bidder shall,
as part of its bid, update any information submitted with its application for
prequalification. (For the purposes of establishing a Bidders qualifications, the
experience and / or resources of any Subcontractor will not contribute to the
Bidders qualifications; only those of a Joint Venture partner will be considered.)
6.1.2. That, in the case of a Bidder offering to supply key goods components of the real-time
CBS that the Bidder does not itself produce, the Bidder is duly authorized by the
producer to supply those components in Afghanistan under the Contract(s) that may
result from this bidding; (This will be accomplished by including Manufacturers
Authorizations letter.
6.2. The Bidder shall not have ownership with competitors of Afghan Telecom in Afghanistan and
must not have a plan to have any ownership until the completion of all the obligations of
the Contract for the CBS.
6.3. Bidder must have implemented same system or major part of offered system in 5 other
companies around the Globe.
7. Subcontractors
7.1. For the purposes of these Bidding Documents, a Subcontractor is any vendor or service
provider with whom the Bidder contracts for the supply or execution of any part of
the CBS to be provided by the Bidder under the Contract (such as the supply of major
hardware, software, or other components of the required CBS specified, or the
performance of related services, e.g., software development, transportation, installation,
customization, integration, commissioning, training, technical support, maintenance,
repair, etc.).
ITB
7.2. If a Bidder intends to subcontract major items of supply or services, it shall include in
its Bid Submission details of the name and nationality of the proposed Subcontractor(s)
for each of those items and shall be responsible for ensuring that any Subcontractor(s)
proposed complies with the requirements of this ITB, and that any goods or services
components of the CBS to be provided by the Subcontractor(s) comply with the
requirements of the ITB Clause 5
7.3. Bidders are free to list more than one Subcontractor against a good or service. Quoted rates
and prices will be deemed to apply to whichever Subcontractor(s) is appointed and no
adjustment of the rates or prices will be permitted.
7.4. Afghan Telecom reserves the right to delete any proposed Subcontractor from the Bidders
list. This shall be done prior to Contract signature, by deleting such unacceptable
Subcontractors from Appendix 3 to the Contract Agreement, which shall list the
approved Subcontractors for each item prior to Contract signature.
7.5. For all Subcontractors, the Bidder must establish to Afghan Telecoms satisfaction:
7.5.1. That, if a Bidder proposes Subcontractors for key components or services, these
Subcontractors will have agreed in writing to serve for the Bidder under the
Contract(s) that may result from this bidding, which proof shall be submitted as part
of the Bid Submission; and
7.5.2.That, in the case of a Bidder not doing business within Afghanistan, the Bidder is or will be
(if awarded the Contract) represented by an Afghan Agent in that country who is
equipped and able to carry out the Bidders maintenance, technical support,
training, and repair obligations prescribed in the General and Special Conditions of
Contract, and/or Technical Requirements.
ITB
requirement is not met, all bids involving the entity as a single Bidder or
Consortium or Joint Venture partner will be disqualified;
8.1.7. All partners of the Consortium or Joint Venture shall be liable jointly and severally for the
execution of the Contract in accordance with the Contract terms, and a statement to
this effect shall be included in the authorization, in the bid as well as in the
Contract (in case of a successful bid).
9. Cost of Bidding
9.1. The Bidder shall bear all cost associated with the preparation and submission of its bid, and
Afghan Telecom will in no case be responsible or liable for those costs, regardless of the
conduct or outcome of the bidding process.
ITB
10
ITB
11
ITB
15.2. Bidder shall quote all bid prices in Afghani or US dollars (USD or $). The prices shall be
inclusive of all duties and taxes such as customs and duties fees, import and export taxes,
etc. that are applicable to the Bidders country and the Islamic Republic of Afghanistan.
15.3. If a Supplier has quoted bid prices in US dollars wishes to receive payment in Afghanis (Afs)
currency, the exchange rate applicable to the conversion shall be as of the Bid Opening
Date.
15.4. An Afghan Bidder furnishing the Bid Security on behalf of the Foreign Bidder
shall state the Foreign Bidders name as (Name of Bidder) bidding on behalf of (Name of
Foreign Bidder). The name and address of principal company must be mentioned in the
bid and the payments shall be made accordingly to the principal company or the foreign
company (not to the Afghan Company).
15.5. Afghan Telecom shall open a L/C in the name of Principle manufacturer and payment shall be
made to the Principle Manufacturer only after deducting Tax deduction at Source
applicable at the time of payment as per Income Tax law of Afghanistan.
15.6. All prices submitted by Bidders shall be final and shall not be subjected to any variation.
15.7. The unit prices of all goods and services, including shipping or transportation, if applicable,
shall be quoted in the Price Schedule. Bidders shall not quote any other text such as
Included Above, Not Applicable, Not Available, Free of Cost, etc.
15.8. Discount and Free of Cost items, if any, offered by the Bidders shall not be
considered.
15.9. Therefore, Bidders desiring to offer discounted or free goods or services shall modify their
offers suitably while quoting and shall quote clearly net price taking all such factors like
discounts and free items into account.
15.10. The quoted unit prices shall remain valid for 5 years from the date of completion of the
Warranty Period and shall be applicable to all subsequent purchases by Afghan Telecom
until such time.
15.11. Unit Prices of the offered goods, services and inland Transportation in all lots, phases and
packages shall be same.
15.12. The terms DDP., shall be governed by the rules prescribed in the current edition of DDP
INCOTERMS published by the International Chamber of Commerce, Paris.
12
ITB
16.6. The Bid Security of all the Bidders will be discharged upon signing of the Contract and after
furnishing of the Performance Security by the successful Bidder.
13
ITB
19.2. The Bidders modification, substitution, or withdrawal notice shall be prepared, sealed,
and marked and dispatched, with the outer and inner envelopes duly marked as
WITHDRAWAL, SUBSTITUTION, or MODIFICATION as appropriate.
19.3. No Bid Submission may be withdrawn, substituted, or modified after the deadline for
submission of bids.
19.4. If a Bidder submits a bid on behalf of a merged company, it shall submit a legally-certified
document indicating such along with its Bid Submission. The eligibility of separate
companies in such cases will be combined for the purpose of verifying the eligibility criteria.
Bids submitted on behalf of amalgamated/acquired companies having independent legal
status shall be treated separately.
19.5 In case of global companies, the Bid Submission must be fully supported by the headquarters
(HQ).
14
ITB
20.2.5. The Power of attorney and signature specimen of the authorized person (including
designation and other information) in a separate sheet shall be submitted along with
the Bid.
21. In order to simplify the process of Bid Opening and also to economize the time consumed during the
Bid Opening, the Bidders are required to submit the above documents mentioned in Clauses in a
separate sealed envelope marked as DOCUMENT FOR BID OPENING". Otherwise, the Bidder shall
be fully responsible for the probable consequences that may result therein after.
15
ITB
16
ITB
17
ITB
29.
Signing of Contract
29.1 After the receipt of the Letter of Acceptance (LOA) from Afghan Telecom, the successful
Bidder shall send its authorized representatives within fifteen (15) days for Contract
negotiation and Contract signing. At the time of signing the Contract, the Supplier shall
submit a Performance Security in the form of bank guarantee for ten percent (10%) of the
amount of the Contract in the same currency as that of the Contract or equivalent in US
dollars ($).
29.2. Non-submission of Performance Security at the time of signing the Contract may lead
to the cancellation of the Contract.
Training Requirement:
Training should be divided into three parts.
1) Training of 10 employees right after signing the Contract and before implementation of
the project. Training materials should be designed in a way that these people can monitor
the implementation phase.
2) Train the trainers: A group of 8 employees from Marketing, technical, IT and Finance will
be trained as Master trainers to further train others on using the software package.
3) Training administrators so that they can make any changes that are possible inside the
software package for the purchaser.
4) Training of employees to carry out their job responsibilities from all related departments.
Bidder shall submit detailed costs, syllabus and duration of the training courses
considering the five working days per week and office hours of 09:00 hours to 16:00
hours of Employer.
The instructors shall be fluent in English and have better communication skills.
The Bidder shall provide documents detailing instructors qualifications and experience
for approval by Employer.
The Bidder shall provide appropriate training material including Notes and diagrams
appropriate to the training program and training Setup not later than two weeks
before the start of the course.
The Contract shall not be considered complete for the purpose of acceptance until
such training requirements as called for have been provided.
More detailed information regarding training is mentioned in Technical part.
18
Conditions Of Contract
Conditions OF Contract
1. Definitions ................................................................................. 23
2. Interpretation............................................................................ 30
3.Notices ........................................................................................ 33
4. Governing Law........................................................................... 34
5. Settlement of Disputes .............................................................. 34
6. Scope of the System .................................................................. 38
7. Time for Commencement and Operational Acceptance .............. 38
8. Suppliers Responsibilities ......................................................... 40
9. Purchasers Responsibilities ....................................................... 40
10. Contract Price ........................................................................... 43
11. Terms of Payment ..................................................................... 43
12. Securities .................................................................................. 44
13. Taxes and Duties ....................................................................... 45
14. Copyright .................................................................................. 45
15. Software License Agreements ................................................... 46
16. Confidential Information ........................................................... 47
17. Representatives ...................................................................... 50
18. Project Plan............................................................................... 53
19. Design and Engineering ............................................................. 53
20. Product Upgrades ..................................................................... 56
21. Inspections and Tests ................................................................ 57
22. Installation of the System .......................................................... 59
23. Commissioning and Operational Acceptance ............................. 59
19
Conditions Of Contract
2.
3.
4.
5.
6.
9.
20
Conditions Of Contract
21
Conditions Of Contract
22
Conditions Of Contract
1. Definitions
1.1 In this Contract, the following terms shall be interpreted as
indicated below.
(A)
Contract elements
(i)
(ii)
23
Conditions Of Contract
Entities
(i)
(ii)
24
Conditions Of Contract
Scope
(i)
(ii)
(iii)
Information
Technologies means
all
information processing and communicationsrelated hardware, Software, supplies, and
consumable items that the Supplier is required
to supply and install under the Contract.
(iv)
(v)
25
Conditions Of Contract
(vii)
26
Conditions Of Contract
do so.
27
Conditions Of Contract
activities
(i)
(ii)
Conditions Of Contract
(E)
(vi) Operational
Acceptance
means
the
acceptance by the Purchaser of the System (or
any Subsystem(s) where the Contract provides
for acceptance of the System in parts), in
accordance with GCC Clause 27.3 (Operational
Acceptance).
Place and time
(i)
(ii)
(iii)
29
Conditions Of Contract
2. Interpretation
Conditions Of Contract
2.7 Amendment
No amendment or other variation of the Contract shall be
effective unless it is in writing, is dated, expressly refers to
the Contract, and is signed by a duly authorized
representative of each party to the Contract.
2.8 Independent Supplier
The Supplier shall be an independent contractor
performing the Contract. The Contract does not create any
agency, partnership, joint venture, or other joint
relationship between the parties to the Contract.
Subject to the provisions of the Contract, the Supplier shall
be solely responsible for the manner in which the Contract
is performed.
All employees, representatives, or
Subcontractors engaged by the Supplier in connection with
the performance of the Contract shall be under the
complete control of the Supplier and shall not be deemed
to be employees of the Purchaser, and nothing contained
in the Contract or in any subcontract awarded by the
Supplier shall be construed to create any contractual
relationship
between
any
such
employees,
representatives, or Subcontractors and the Purchaser.
31
Conditions Of Contract
Conditions Of Contract
3.Notices
3.1.1 Any notice sent by cable, telegraph, telex,
facsimile,
electronic mail, or EDI shall be confirmed within two
(2) days after dispatch by notice sent by airmail post
or special courier, except as otherwise specified in
the Contract.
3.1.2 Any notice sent by airmail post or special courier shall
be deemed (in the absence of evidence of earlier
receipt) to have been delivered ten (10) days after
dispatch. In proving the fact of dispatch, it shall be
sufficient to show that the envelope containing such
notice was properly addressed, stamped, and
conveyed to the postal authorities or courier service
for transmission by airmail or special courier.
3.1.3 Any notice delivered personally or sent by cable,
telegraph, telex, facsimile, electronic mail, or EDI
shall be deemed to have been delivered on the date
of its dispatch.
3.1.4 Either party may change its postal, cable, telex,
facsimile, electronic mail, or EDI addresses for receipt
of such notices by ten (10) days notice to the other
party in writing.
3.2 Notices shall be deemed to include any approvals,
consents, instructions, orders, certificates, information and
other communication to be given under the Contract.
3.3 Pursuant to GCC Clause 17, notices from/to the Purchaser
are normally given by, or addressed to, the Project
Manager, while notices from/to the Supplier are normally
given by, or addressed to, the Supplier's Representative, or
33
Conditions Of Contract
4. Governing Law
4.1
5. Settlement of Disputes
5.1 Adjudication
5.1.1 If any dispute of any kind whatsoever shall arise between
the
Purchaser and
the
Supplier in connection with or arising
out of the Contract, including without prejudice to the generality of the
foregoing, any question regarding its existence, validity, or termination,
or the operation of the System (whetherduring
the
progress of implementation or after its achieving Operational Acceptance
and whether
before or after the termination, abandonment,
or
breach
of the Contract), the parties shall seek to resolve
any such dispute by mutual consultation. If the parties fail to resolve such a
dispute by mutual consultation within fourteen (14) days after one party has
notified the other in writing of the dispute, then, if the Contract Agreement
includes and names an Adjudicator, the dispute
shall,
within another fourteen (14) days, be referred in writing by either party to
the Adjudicator, with a copy to the other party. If there is no Adjudicator
34
Conditions Of Contract
35
Conditions Of Contract
Conditions Of Contract
(b)
37
Conditions Of Contract
Conditions Of Contract
Finalized Project Plan, or within such extended time to which the Supplier shall
be entitled under GCC Clause 34 (Extension of Time for Achieving Operational
Acceptance).
39
Conditions Of Contract
8. Suppliers Responsibilities
8.1 The Supplier shall conduct all activities with due care and diligence, in accordance
with the Contract and with the skill and care expected of a competent provider of
information technologies, information systems, support, maintenance, training, and other
related services, or in accordance with best industry practices.
In particular, the
Supplier shall provide and employ only technical personnel who are skilled and
experienced in their respective callings and supervisory
staff who are
competent
to
adequately supervise the work at hand.
8.2 The Supplier confirms that it has entered into this Contract on the basis of a proper
examination of the data relating to the System provided by the Purchaser and on the
basis of information that the Supplier could have obtained from a visual inspection
of the site (if access to the site was available) and of other data readily available
to the Supplier relating to the System as at the date twenty-eight (28) days prior to
bid submission.
The Supplier acknowledges that any failure to acquaint
itself with all such data and information shall not relieve its responsibility for
properly estimating the difficulty or cost of successfully performing the Contract.
8.3 The Supplier shall be responsible for timely provision of all resources, information,
and decision making under its control that are necessary to reach a mutually
Agreed and Finalized Project Plan (pursuant to GCC Clause 18.2) within the time
schedule specified in the Implementation Schedule in the Technical Requirements
Section. Failure to provide such resources, information, and decision making
may constitute grounds for termination pursuant to GCC Clause 35.2.
8.4 The Supplier shall comply with all laws in force in the Purchasers Country. The
laws will include all national, provincial, municipal, or other laws that affect the
performance of the Contract and are binding upon the Supplier. The Supplier shall
indemnify and hold harmless the Purchaser from and against any and all liabilities,
damages, claims, fines, penalties, and expenses of whatever nature arising or resulting from
the violation of such laws by the Supplier or its personnel, including the Subcontractors and
their personnel, but without prejudice to GCC Clause 9.1. The Supplier shall not
indemnify the Purchaser to the extent that such liability, damage, claims, fines,
penalties, and expenses were caused or contributed to by a fault of the Purchaser.
9. Purchasers Responsibilities
9.1 The Purchaser shall ensure the accuracy of all information and/or data to be supplied
by the Purchaser to the Supplier, except when otherwise expressly stated in the
Contract.
40
Conditions Of Contract
9.2 The Purchaser shall be responsible for timely provision of all resources, information,
and decision making under its control that are necessary to reach an Agreed and
Finalized Project Plan (pursuant to GCC Clause 18.2) within the time schedule
specified in the Implementation Schedule in the Technical Requirements Section.
Failure to provide such resources, information, and decision making may constitute
grounds for Termination pursuant to GCC Clause 41.3.1 (b).
9.3 In such cases where the responsibilities of specifying and acquiring or upgrading
telecommunications and/or electric power services falls to the Supplier, as
specified in the Technical Requirements, SCC, Agreed and Finalized Project Plan, or
other parts of the Contract, the Purchaser shall use its best endeavors to assist the
Supplier in obtaining such services in a timely and expeditious manner.
9.4 The Purchaser shall be responsible for timely provision of all resources, access, and
information necessary for the Installation and Operational Acceptance of the
System (including, but not
limited to, any required telecommunications
or
electric power services), as identified in the Agreed
and Finalized Project Plan, except where provision of such items is explicitly identified
in the Contract as being the responsibility of the Supplier. Delay by the Purchaser
may result in an appropriate extension of the Time for Operational Acceptance, at
the Suppliers discretion.
9.5 Unless otherwise specified in the Contract or agreed upon
by the Purchaser and the Supplier, the Purchaser shall
provide sufficient, properly qualified operating and
technical personnel, as required by the Supplier to properly
carry out Delivery, Pre-commissioning, Installation,
Commissioning, and Operational Acceptance, at or before
the time specified in the Technical Requirements Sections
Implementation Schedule and the Agreed and Finalized
Project Plan.
9.6 The Purchaser will designate appropriate staff for the
training courses to be given by the Supplier
9.7 The Purchaser assumes primary responsibility for the
Operational Acceptance Test(s) for the System, in
accordance with GCC Clause 23.2, and shall be responsible
for the continued operation of the System after Operational
Acceptance. However, this shall not limit in any way the
Suppliers responsibilities after the date of Operational
Acceptance otherwise specified in the Contract.
9.8 The Purchaser is responsible for performing and safely
storing timely and regular backups of its data and Software
in accordance with accepted data management principles,
except where such responsibility is clearly assigned to the
41
Conditions Of Contract
42
Conditions Of Contract
C. PAYMENT
10. Contract Price
(b)
Conditions Of Contract
12. Securities
12.1 Issuance of Securities
The Supplier shall provide the securities specified below in
favor of the Purchaser at the times and in the amount,
manner, and form specified below.
12.2 Performance Security
12.2.1 The Supplier shall, within fifteen (15) days of the
notification of Contract award, provide a security for
the due performance of the Contract in the
amount and currency specified in the SCC.
12.2.2 The security shall be a bank guarantee in the form
provided in the Sample Forms Section of the Bidding
Documents, or it shall be in another form acceptable
to the Purchaser.
12.2.3 The security shall automatically become null and void
once all the obligations of the Supplier under the
Contract have been fulfilled, including, but not limited
to, any obligations during the Warranty Period and
any extensions to the period. The security shall be
returned to the Supplier no later than twenty-eight
(28) days after its expiration.
12.2.4 Upon Operational Acceptance of the entire System,
the security shall be reduced to the amount specified
in the SCC, on the date of such Operational
Acceptance, so that the reduced security would only
44
Conditions Of Contract
D. INTELLECTUAL PROPERTY
14. Copyright
14.1 The Intellectual Property Rights in all Standard Software and
Standard Materials shall remain vested in the owner of such
rights.
14.2 The Purchaser agrees to restrict use, copying, or duplication
of the Standard Software and Standard Materials in
45
Conditions Of Contract
nonexclusive;
(ii)
valid throughout the territory of the Purchasers Country (or such other
territory as specified in the SCC); and
(ii)
Conditions Of Contract
Conditions Of Contract
Purchaser or the Supplier) shall keep confidential and shall not, without the
written consent of the other party to this Contract (the Disclosing Party), divulge
to any third party any documents, data, or other information
of
a
confidential
nature (Confidential Information) connected
with this Contract, and furnished directly or indirectly by the Disclosing Party
prior to or during performance, or following termination, of this Contract.
16.2 For the purposes of GCC Clause 16.1, the Supplier is also deemed to
be
the
Receiving
Party
of
Confidential Information generated by the
Supplier itself in the course of the performance of its obligations under the Contract
and relating to the businesses, finances, suppliers, employees, or other contacts of
the Purchaser or the Purchasers use of the System.
16.3 Notwithstanding GCC Clauses 16.1 and 16.2:
(a)
(b)
the Purchaser may furnish Confidential Information of the Supplier: (i) to its
support service suppliers and their subcontractors to the extent reasonably
required for them to perform their work under their support service
contracts; and (ii) to its affiliates and subsidiaries,
in which event the Receiving Party shall ensure that the person to whom it
furnishes Confidential Information of the Disclosing Party is aware of and abides by
the Receiving Partys obligations under this GCC Clause 16 as if that person were
party to the Contract in place of the Receiving Party.
16.4 The Purchaser shall not, without the Suppliers prior written consent, use any
Confidential Information received from the Supplier for any purpose other than
the operation, maintenance and further development of the System. Similarly,
the Supplier shall not, without the Purchasers
prior written consent, use any Confidential Information
received from the Purchaser for any purpose other than
those that are required for the performance of the Contract.
16.5 The obligation of a party under GCC Clauses 16.1 through
16.4 above, however, shall not apply to that information
which:
(a)
(b)
Conditions Of Contract
16.6 The above provisions of this GCC Clause 16 shall not in any
way modify any undertaking of confidentiality given by
either of the parties to this Contract prior to the date of the
Contract in respect of the System or any part thereof.
16.7 The provisions of this GCC Clause 16 shall survive the
termination, for whatever reason, of the Contract for three
(3) years or such longer period as may be specified in the
SCC.
49
Conditions Of Contract
Representatives
Conditions Of Contract
51
Conditions Of Contract
52
Conditions Of Contract
Supplier
Conditions Of Contract
19.1.2 The
54
Conditions Of Contract
Conditions Of Contract
Conditions Of Contract
Conditions Of Contract
58
Conditions Of Contract
(b)
or
the
59
Conditions Of Contract
(c)
23.1.2 The Purchaser shall supply the operating and technical personnel and all
materials and information reasonably required to enable the Supplier to carry
out its obligations with respect to Commissioning.
Production use of the System or Subsystem(s) shall not
commence
prior
to
the
start
of
formal
Operational
Acceptance
Testing.
23.2 Operational Acceptance Tests
23.2.1 The Operational Acceptance Tests (and repeats of such tests) shall be the
primary responsibility of the Purchaser (in accordance with GCC Clause 9.7), but
shall be conducted with the full cooperation of the Supplier during
Commissioning of the System (or major components or Subsystem[s] if
specified in the SCC and supported by the Technical Requirements), to
ascertain whether the System (or major component or
Subsystem[s])
conforms
to the Technical Requirements and
meets the standard of performance quoted in the Suppliers bid, including,
but not restricted to, the functional and technical
performance requirements.
The Operational
Acceptance Tests during Commissioning will be
conducted as specified in the SCC, the Technical
Requirements and/or the Agreed and Finalized
Project Plan.
At the Purchasers discretion, Operational Acceptance
Tests may also be performed on replacement Goods,
upgrades and new version releases, and Goods that
are added or field-modified after Operational
Acceptance of the System.
23.2.2 If for reasons attributable to the Purchaser, the
Operational Acceptance Test of the System (or
Subsystem[s] or major components, pursuant to the
SCC for GCC Clause 23.2.1) cannot be successfully
completed within the period specified in the SCC,
from the date of Installation or any other period
agreed upon in writing by the Purchaser and the
Supplier, the Supplier shall be deemed to have
fulfilled its obligations with respect to the technical
and functional aspects of the Technical Specifications,
SCC and/or the Agreed and Finalized Project Plan, and
GCC Clause 24.2 and 24.3 shall not apply.
23.3 Operational Acceptance
60
Conditions Of Contract
(b)
(c)
Conditions Of Contract
(b)
62
Conditions Of Contract
24.2 If the Supplier fails to supply, install, commission, and achieve Operational Acceptance
of the System (or Subsystems pursuant to the SCC for GCC Clause 23.2.1) within the
time for achieving
Operational Acceptance specified
in
the
Implementation Schedule in the Technical Requirement or the Agreed and Finalized
Project Plan, or any extension of the time for achieving Operational Acceptance
previously granted under GCC Clause 34 (Extension of Time for Achieving
Operational Acceptance), the Supplier shall pay to the Purchaser liquidated
damages at the rate specified in the SCC as a percentage of the Contract Price, or the
relevant part of the Contract Price if a Subsystem has not achieved Operational
Acceptance.
The aggregate amount of such
liquidated damages shall in no event exceed the amount specified in the SCC (the
Maximum). Once the Maximum is reached, the Purchaser may consider termination of
the Contract, pursuant to GCC Clause 35.2.2.
24.3 Unless otherwise specified in the SCC, liquidated damages
payable under GCC Clause 24.2 shall apply only to the
failure to achieve Operational Acceptance of the System (and
Subsystems) as specified in the Implementation Schedule in
the Technical Requirements and/or Agreed and Finalized Project
Plan.
This Clause 24.3 shall not limit,
however, any other rights or remedies the Purchaser may have
under the Contract for other delays.
24.4 If liquidated damages are claimed by the Purchaser for the
System (or Subsystem), the Supplier shall have no further
liability whatsoever to the Purchaser in respect to the
Operational Acceptance time guarantee for the System (or
Subsystem). However, the payment of liquidated damages
shall not in any way relieve the Supplier from any of its
63
Conditions Of Contract
64
Conditions Of Contract
Conditions Of Contract
Conditions Of Contract
Conditions Of Contract
68
Conditions Of Contract
Conditions Of Contract
(b)
G. RISK DISTRIBUTION
(insofar as they relate to the country where the Project Site is located)
nuclear reaction, nuclear radiation, radioactive contamination, a pressure
wave caused by aircraft or other aerial objects, or any other occurrences that an
experienced contractor could not reasonably foresee, or if reasonably
foreseeable could not reasonably make provision for or insure against,
In so far as such risks are not normally insurable on
the insurance market.
(b)
Conditions Of Contract
(c)
Conditions Of Contract
Conditions Of Contract
73
Conditions Of Contract
(b)
(c)
confiscation,
nationalization,
mobilization,
commandeering or requisition by or under the order
of any government or de jure or de facto authority or
ruler, or any other act or failure to act of any local
state or national government authority;
(d)
Conditions Of Contract
(b)
Conditions Of Contract
Conditions Of Contract
Change Proposal,
following:
which
Conditions Of Contract
Conditions Of Contract
79
Conditions Of Contract
(b)
(c)
(d)
and
as
34.2 Except where otherwise specifically provided in the Contract, the Supplier shall
submit to the Project Manager a notice of a claim for an extension of the time for
achieving Operational Acceptance, together with particulars of the event or
circumstance justifying such extension as soon as reasonably practicable after the
commencement of such event or circumstance. As soon as reasonably practicable
80
Conditions Of Contract
after receipt of such notice and supporting particulars of the claim, the Purchaser and
the Supplier shall agree upon the period of such extension.
In the event that
the Supplier does not accept the Purchasers estimate of a fair and reasonable
time extension, the Supplier shall be entitled to refer the matter to the provisions
for the Settlement of Disputes pursuant to GCC Clause 5.
34.3 The Supplier shall at all times use its reasonable efforts to minimize any delay in the
performance of its obligations under the Contract.
35. Termination
35.1 Termination for Purchasers Convenience
35.1.1 The Purchaser may at any time terminate the
Contract for any reason by giving the Supplier a
notice of termination that refers to this GCC
Clause 35.1.
35.1.2 Upon receipt of the notice of termination under
GCC Clause 35.1.1, the Supplier shall either as soon
as reasonably practical or upon the date specified in
the notice of termination
(a) cease all further work, except for such work as
the Purchaser may specify in the notice of
termination for the sole purpose of protecting
that part of the System already executed, or any
work required to leave the site in a clean and
safe condition;
(b) terminate all subcontracts, except those to be
assigned to the Purchaser pursuant to GCC
Clause 35.1.2 (d) (ii) below;
(c) remove all Suppliers Equipment from the site,
repatriate the Suppliers and its Subcontractors
personnel from the site, remove from the site
any wreckage, rubbish, and debris of any kind;
(d) in addition, the Supplier, subject to the payment
specified in GCC Clause 35.1.3, shall
(i)
(ii)
Conditions Of Contract
Conditions Of Contract
83
Conditions Of Contract
(i)
(ii)
(iii)
(iv)
Another party refers to a public official acting in relation to the procurement process or contract
execution]. In this context, public official includes MCIT staff and employees of other organizations
taking or reviewing procurement decisions.
A party refers to a public official; the terms benefit and obligation relate to the procurement process
or contract execution; and the act or omission is intended to influence the procurement process or
contract execution.
Parties refers to participants in the procurement process (including public officials) attempting to
establish bid prices at artificial, non competitive levels.
A party refers to a participant in the procurement process or contract execution
84
Conditions Of Contract
obstructive practice is
(aa) deliberately destroying, falsifying,
altering or concealing of evidence
material to the investigation or
making
false
statements
to
investigators in order to materially
impede AFTEL investigation into
allegations of a corrupt, fraudulent,
coercive or collusive practice; and/or
threatening,
harassing
or
intimidating any party to prevent it
from disclosing its knowledge of
matters relevant to the investigation
or from pursuing the investigation;
or
(bb) acts intended to materially impede
the exercise of AFTELs inspection
and audit rights .
Conditions Of Contract
Conditions Of Contract
the site.
35.2.5 Subject to GCC Clause 35.2.6, the Supplier shall be
entitled to be paid the Contract Price attributable to
the portion of the System executed as at the date of
termination and the costs, if any, incurred in
protecting the System and in leaving the site in a
clean and safe condition pursuant to GCC
Clause 35.2.3 (a). Any sums due the Purchaser from
the Supplier accruing prior to the date of
termination shall be deducted from the amount to
be paid to the Supplier under this Contract.
35.2.6 If the Purchaser completes the System, the cost of
completing the System by the Purchaser shall be
determined. If the sum that the Supplier is entitled
to be paid, pursuant to GCC Clause 35.2.5, plus the
reasonable costs incurred by the Purchaser in
completing the System, exceeds the Contract Price,
the Supplier shall be liable for such excess. If such
excess is greater than the sums due the Supplier
under GCC Clause 35.2.5, the Supplier shall pay the
balance to the Purchaser.
35.3 Termination by Supplier
35.3.1 If:
(a) the Purchaser has failed to pay the Supplier any
sum due under the Contract within the specified
period, has failed to approve any invoice or
supporting documents without just cause
pursuant to the SCC, or commits a substantial
breach of the Contract, the Supplier may give a
notice to the Purchaser that requires payment
of such sum, with interest on this sum,
requires approval of
such
invoice
or
supporting documents, or specifies the breach
and requires the Purchaser to remedy the
same, as the case may be. If the Purchaser fails
to pay such sum together with such interest,
fails to approve such invoice or supporting
documents or give its reasons for withholding
such approval, fails to remedy the breach or
take steps to remedy the breach within
fourteen (14) days after receipt of the
Suppliers notice; or
(b) the Supplier is unable to carry out any of its
obligations under the Contract for any reason
attributable to the Purchaser, including but not
87
Conditions Of Contract
Conditions Of Contract
36. Assignment
36.l Neither the Purchaser nor the Supplier shall, without the
express prior written consent of the other, assign to any
89
Conditions Of Contract
90
Conditions Of Contract
91
Conditions Of Contract
The following Special Conditions of Contract (SCC) shall supplement or amend the
General Conditions of Contract (GCC). Whenever there is a conflict, the provisions of the
SCC shall prevail over those in the General Conditions of Contract. For the purposes of
clarity, any referenced GCC clause numbers are indicated in the left column of the SCC.
Note: The following are sample clauses. The Purchaser/supplier may complete, modify, add, or
delete the following sample SCC clauses as appropriate at the time of contract negotiation.
1.
The Project Manager is: Jabir Sarfaraz, Chief Information Officer, Afghan
Telecom.
The Contract shall continue in force until the Information System and all
the Services have been provided unless the Contract is terminated
earlier in accordance with the terms set out in the Contract.
92
Conditions Of Contract
93
Conditions Of Contract
2.
GCC2.1.1
3.
4.
5.
The Contract's
governing language is
English with
translation in one of
the local language
Pashto/Dari.
94
Conditions Of Contract
GCC 5.2.3
95
Conditions Of Contract
6.
GCC 6.3
The Suppliers obligations under the Contract will include the following
recurrent cost items, as identified in the Recurrent Cost tables in
the Suppliers Bid:
The Supplier agrees to supply spare parts required for the operation and
maintenance of the System, as stated below, for the 12 months
beginning with Operational Acceptance. Moreover, the price of such
spare parts shall be those specified in the spare parts price schedule
submitted by the Suppler as part of its bid.
These prices shall
include the purchase price for such spare parts and other costs and
expenses (including the Suppliers fees) relating to the supply of spare
parts
7.
8.
GCC 7.1
GCC 7.2
96
Conditions Of Contract
9.
GCC 9
C. PAYMENT
10.
97
Conditions Of Contract
11.
GCC 11.1
98
Conditions Of Contract
GCC 11.2
GCC 11.3
For Goods and Services supplied locally, the Purchaser will pay the
Supplier in the currency stated in the Contract Agreement and
the Price Schedules it refers to.
The Supplier will invoice the Purchaser in the currency used in the
Contract Agreement and the Price Schedules it refers to, for
Goods and Services supplied locally, and the conversion
between this currency and Afghani for payment purposes - in
case the two currencies are different - will be made as of the
actual payment date using the exchange rate found in Herald
Tribune.
GCC 11.4
Payment for Goods supplied from outside the Purchasers Country shall
be in the form of: a confirmed, irrevocable, divisible, and
transferable Letter of Credit.
99
Conditions Of Contract
12.
GCC 12.2.1
GCC 12.2.4
13.
GCC 13
For Goods or Services supplied from outside and inside the Purchasers
country, the Supplier shall be entirely responsible for all taxes, stamp
duties, license fees, and other such levies imposed outside and inside
the Purchasers country.
D. INTELLECTUAL PROPERTY
14.
GCC 14.3
Conditions Of Contract
15.
The Software license shall permit the Software to be used or copied for
use or transferred to a replacement computer provided the
replacement computer falls within approximately the same class
of machine and maintains approximately the same number of users, if a
machine.
GCC 15.1 (b) (vi) multi-user
The Software
license shall permit the Software to be disclosed to and
reproduced for use (including a valid sublicense) by subject to the same
restrictions set forth in this Contract clause GCC 15.4.
GCC 15.1 (b) (vii) In addition to the persons specified in GCC Clause 16.1 (b) (vi), the
Software may be disclosed to, and reproduced for use by,
employees and customers of Ministry of Communications and IT,
Ministry
of Interior
republic
of Afghanistan
subject
to thetosame
GCC 15.2
The Suppliers
right of
to Islamic
audit the
Standard
Software will
be subject
the
following terms: none
16.
GCC 16.1
GCC 16.7
The provisions of this GCC Clause 17 shall survive the termination, for
whatever reason, of the Contract for the period specified in the
GCC.
101
Conditions Of Contract
17.
GCC 17.1
GCC 17.2.2
The Suppliers Representative shall have the following additional
powers and / or limitations to his or her authority to represent
the Supplier in matters relating to the Contract: no additional
powers or limitations.
102
Conditions Of Contract
18.
GCC 18.1
(b)
(c)
Training Plan
(d)
(e)
(f)
(g)
(h)
103
Conditions Of Contract
GCC 18.2
Within 30 days from the Effective Date of the Contract, the Supplier
shall present a Project Plan to the Purchaser. The Purchaser
shall, within 14 days of receipt of the Project Plan, notify the
Supplier of any respects in which it considers that the Project
Plan does not adequately ensure that the proposed program of
work, proposed methods, and/or proposed Information
Technologies will satisfy the Technical Requirements and/or the
SCC (in this Clause 19.2 called non-conformities below). The
Supplier shall, within 6 days of receipt of such notification,
correct the Project Plan and resubmit to the Purchaser. The
Purchaser shall, within 6 days of resubmission of the Project
Plan, notify the Supplier of any remaining non-conformities. This
procedure shall be repeated as necessary until the Project Plan is
free from non-conformities. When the Project Plan is free from
non-conformities, the Purchaser shall provide confirmation in
writing to the Supplier. This approved Project Plan (the Agreed
and Finalized Project Plan) shall be contractually binding on the
Purchaser and the Supplier.
GCC 18.5
104
Conditions Of Contract
(ii)
problems;
19.
GCC 19.3.1
The Supplier shall prepare and furnish to the Project Manager the
following documents for which the Supplier must obtain the
Project Managers approval before proceeding with work on the
System or any Subsystem covered by the documents
(i)
(ii)
105
Conditions Of Contract
20.
GCC 20.4
21.
GCC 21
22.
GCC 22
23.
The Supplier shall provide the Purchaser with all new versions,
releases, and updates to all Standard Software during the
Warranty Period, for free, as specified in the GCC.
GCC 23.2.1
GCC 23.2.2
106
Conditions Of Contract
24.
GCC 24.2
GCC 24.3
25.
GCC 25.1
The Supplier warrants that the following items have been released to the
market for the following specific minimum time periods: No
specific minimum time requirements are established for this
Contract other than that the Information Technologies must have
been previously released to the market.
GCC 25.4
The Warranty Period (N) shall begin from the date of Final Acceptance
of the System or Subsystem and extend for 12 months.
GCC 25.10
During the Warranty Period, the Supplier must commence the work
necessary to remedy defects or damage immediately
107
Conditions Of Contract
26.
GCC 26
27.
GCC 27
Supplier warrants that Supplier will not knowingly infringe on the
copyright or trade secrets of any third party in performing services
under this agreement. To the extent any material used by Supplier contains
matter proprietary to third party, contractor shall obtain a license from the
owner permitting the use of such matter and granting contractor the right to
sub-license its use.
If any third party brings a lawsuit or proceeding against
purchaser based upon a claim that the software
breaches the third partys patent, copyright or
trade secrets rights, and it is determined that
such infringement has occurred, contractor
shall hold customer harmless against any
loss, damage, expense or cost, including
reasonable attorney fees, arising from the claim.
This indemnification obligation shall be effective only if:
The third party intellectual property rights
involved were known to contractor prior to delivery
of the software Supplier has make all payments
required by this agreement
Supplier has given prompt notice of the claim
and permitted contractor to defend, and
The claim does not result from customers
modification of the software.
To reduce or mitigate damages, contractor may at
its own expense replace the software with a
non-infringing product.
108
Conditions Of Contract
G. RISK DISTRIBUTION
29.
GCC 29
30.
GCC 30
31.
Loss of or Damage to Property; Accident or Injury to Workers; Indemnification (GCC Clause 31)
GCC 31
32.
GCC 32
Conditions Of Contract
33.
GCC 33
34.
Extension of Time for Achieving Operational Acceptance (GCC Clause 34)
GCC 34
There are no Special Conditions of Contract applicable to GCC Clause 34
35.
GCC 35
110
Licenses Requirements
Service
PSTN
Wimax
VSAT
GSM and 3G
No of licenses
150000
1000
5000
500000
Service
GSM and 3G
PSTN
Wimax
VSAT
No of licenses
2000000
500000
1000
10000
111
Technical Requirements
Table of Contents
General requirements............................................................................................................................................................................... 113
Platform ................................................................................................................................................................................................... 114
Technical architecture .............................................................................................................................................................................. 123
Interface and integration ......................................................................................................................................................................... 124
Monitoring and fault reporting ................................................................................................................................................................. 129
Data management ................................................................................................................................................................................... 132
Encryption and security ............................................................................................................................................................................ 135
Web environment .................................................................................................................................................................................... 139
Support and maintenance......................................................................................................................................................................... 141
Mediation................................................................................................................................................................................................ 144
Interconnect and whole sale ..................................................................................................................................................................... 153
Products and services ............................................................................................................................................................................... 160
Distribution channels................................................................................................................................................................................ 164
Customer, account and credit MGT ........................................................................................................................................................... 165
Tariff and charges ..................................................................................................................................................................................... 168
Charging and balance control.................................................................................................................................................................... 174
Rates and rating ....................................................................................................................................................................................... 186
Fees & Taxes............................................................................................................................................................................................. 195
Pkgs, Discounts & Promotions .................................................................................................................................................................. 198
Invoices & Billing ...................................................................................................................................................................................... 202
Payments & Credits .................................................................................................................................................................................. 215
Reporting ................................................................................................................................................................................................. 221
Time to Market......................................................................................................................................................................................... 223
112
Technical Requirements
1
1.1
FC/PC/NC+NP/P
OB/MOD
Comments
Minimum Requirements
Vendor asserts that its
solution:
1.1.1
Is an end-to-end convergent
billing and charging system
(CBS)
1.1.2
1.1.3
1.1.4
Supports interconnection
settlement and carrier billing
1.1.5
1.1.6
1.2
Executive Summary
Provide an Executive
Summary of your solution,
including, at a minimum:
1.2.1
1.2.2
1.2.3
1.2.4
A description of components
of your solution and whether
they are mandatory or
optional
1.2.5
1.2.6
1.2.7
1.2.8
Technical Requirements
1.3
Overview of Architectures
Provide a description and
explanation of your
solution's architecture,
including:
1.3.1
Hardware architecture
1.3.2
1.3.3
1.3.4
Tarriff/product/package
architecture
Customer/subscriber/accoun
t architecture
1.4
Partners and Third Parties
Describe all partners and
third parties involved in
the solution, including:
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.5
Product Road Map;
Research and
Development (R&D)
Describe your product
road map for the next:
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
Platform
2.1
FC/PC/NC+NP/P
OB/MOD
Comments
Platform Components
2.1.1
2.1.2
Technical Requirements
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.1.10
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.16
2.1.17
2.1.18
2.2
Platform Hardware &
Software
Vendor asserts the
hardware in its proposed
solution:
115
Technical Requirements
2.2.1
Is from world-renowned
suppliers and carries all
necessary and standard
certificates and warranties
2.2.2
2.2.3
Is CE (European
Conformity) and FCC
(Federal Communications
Commission) compliant
2.2.4
2.2.5
2.2.6
2.3
Platform Architecture and
Design
Vendor asserts its
solution:
2.3.1
2.3.2
2.3.3
2.3.4
Is component-based to
increase flexibility and
reusability of code
2.3.5
2.3.6
Technical Requirements
2.3.7
2.3.8
2.3.9
2.3.10
2.3.11
2.3.12
2.3.13
2.3.14
Is designed to eliminate
single points of failure
(SPOF). Any exceptions to
this requirement must be
documented and agreed
with Afghan Telecom prior to
inclusion in the design
2.3.15
2.3.16
2.3.17
2.3.18
2.3.19
Solution supports
connection of multiple sites
using private lines or the
Internet
2.3.20
Supports geographical
redundancy in two sites that
might be deployed now or at
a later stage
2.3.21
2.4
Platform Functionality
117
Technical Requirements
Vendor asserts its
solution:
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
Supports hierarchical
customer relationship
management with at least
three layers of hierarchy
2.4.6
2.4.7
2.5
Platform Availability
2.5.1
2.5.2
2.5.3
118
Technical Requirements
2.5.4
2.5.5
Architecture supports a
shadow platform (hardware
and software), acting as a
disaster recovery site, that is
capable of supporting key
business functions, though
with a lower throughput
2.6
Configuration
Management
Vendor asserts its
solution suports:
2.6.1
2.6.2
A fully-configurable backup
operation for each element,
which outputs the result of
the backup into a log file.
The backup operation must
allow configuration of both
full and incremental
operation to both hard disk
and tape or other removable
media and to FTP servers.
2.6.3
A recovery mechanism to
allow the restoration of any
element from a stored
backup
2.6.4
Functionality to perform
remote software upgrades
on any applicable element
2.7
Performance Management
Vendor asserts its
solution supports:
119
Technical Requirements
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
Measuring of performance
statistic from all network
elements in real-time or near
real-time manner (5-minute
intervals or less,
configurable per
measurement or task)
2.7.6
2.7.7
2.7.8
120
Technical Requirements
2.7.9
2.7.10
2.8
User Management
Vendor asserts its system
supports:
2.8.1
2.8.2
2.8.3
2.8.4
2.8.5
2.8.6
2.9
Platform Capacity and
Scalability
Vendor asserts that its
solution:
121
Technical Requirements
2.9.1
2.9.2
2.9.3
2.9.4
Provides updates, at no
extra cost, that enable the
software to scale up and
support the requirements for
the target maximum
capacity
2.9.5
Supports load-balancing to
accommodate additional
hardware
2.9.6
Is scalable up to 2 million
customers
2.10
Dimension Requirements
Capability
Remarks
Total subscribers
2.10.2
2.10.3
2.10.4
2.10.5
2.10.7
2.10.8
2.10.9
2.10.10
2.10.11
2.10.12
2.10.13
Mediation
2.10.14
2.10.15
2.10.6
122
Technical Requirements
2.10.16
2.10.17
2.10.18
3
Other
Default system busy hour
per day
Default working days per
month
Technical Architecture
3.1
FC/PC/NC+NP/P
OB/MOD
Comments
Servers
Vendor asserts its
solution supports the
following servers:
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
Server-centric application
architecture
Unix
Windows
Other
3.2
Clients
Vendor asserts its
solution supports the
following clients:
3.2.1
3.2.2
3.2.3
Platform-independent
solution
3.2.4
Thin-client application
architecture
3.2.5
3.2.6
3.2.7
3.2.8
Linux
Microsoft
Other
3.3
Databases
Vendor asserts its
solution supports the
following databases:
3.3.1
3.3.2
3.3.3
3.3.4
Microsoft
MySQL
Oracle
SQL server
123
Technical Requirements
3.3.5
3.3.6
PostgreSQL
Server 914 UC7, 914
Other (please list)
Vendor asserts its
solution supports the
following with respect to
databases:
3.3.7
3.3.8
3.3.9
3.3.10
3.3.11
3.3.12
3.3.13
FC/PC/NC+NP/P
OB/MOD
Comments
4.1
Platform Interfaces
124
Technical Requirements
Vendor asserts its
solution supports
interfaces to (please
describe):
4.1.1
Mediation system
4.1.2
4.1.3
Customer relationship
management (CRM) system
4.1.4
Provisioning system
4.1.5
4.1.6
Financial systems
4.1.7
4.1.8
4.1.9
4.1.10
4.1.11
4.1.12
4.1.13
Workflow management
processes
Order management
processes
Provisioning and activation
processes
Call center system
4.2
Industry and Technical
Interfaces
Vendor asserts its
solution supports:
4.2.1
4.2.2
4.2.3
Industry standard
application programming
interfaces (APIs) and
development environments
4.2.4
Industry standard
programming languages (C,
C++, Java, etc.) and
reporting tools
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
HTTP
IBM MQSeries
MSMQ
BizTalk
File
125
Technical Requirements
4.2.11
4.2.12
4.2.13
4.2.14
4.2.15
4.2.16
4.2.17
4.2.18
4.2.19
COM
CORBA
Java
SQL
OLEDB
SAP IDOC
SAP BAPI
Oracle OI
Ethernet connectivity
4.3
Protocols
Vendor asserts its
solution supports the
following protocols:
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
4.3.10
Signaling Protocols
Signaling System 7 (SS7)
Internet Commerce &
Security Protocols
Secure transaction
technology (SST)
Secure electronic payment
protocol (SEPP)
Secure electronic
transactions (SET)
Secure sockets layer (SSL)
Private communication
technology (PCT)
Transport layer security
(TLS)
Hypertext Transfer Protocol
Secure (HTTPS)
4.3.11
Lightweight Directory
Access Protocol (LDAP)
adapters
4.3.12
4.3.13
4.3.14
4.3.15
E-mail: S/MIME
E-mail: UUEncode
E-mail: MIME
4.3.16
4.3.17
Messaging Protocols
4.3.18
4.3.19
4.3.20
4.3.21
Technical Requirements
Other
4.3.22
4.3.23
SFTP to transfer
performance data between
the CBS system and the
external performance
management systems
4.4
Platform/System
Integration
Vendor asserts its
solution:
4.4.1
4.4.2
Employs an integration
methodology follows widelyaccepted integration models
4.4.3
4.4.4
4.4.5
4.4.6
4.4.7
4.4.8
4.4.9
4.4.10
4.4.11
4.4.12
127
Technical Requirements
4.4.13
4.4.14
4.4.15
4.4.16
4.5
Desktop Tools Integration
Vendor asserts its
solution supports realtime delivery of data to
and integration with:
4.5.1
4.5.2
Spreadsheets
4.5.3
4.5.4
4.5.5
Google Docs
4.5.6
Microsoft Excel
Other
Word Processing
Programs
4.5.7
Microsoft Word
4.5.8
Apache OpenOffice.org
Writer
4.5.9
4.5.10
4.5.11
4.5.12
Google Docs
Other
Databases
Microsoft Access
4.5.13
Apache OpenOffice.org
Base
4.5.14
Google Docs
Other
128
Technical Requirements
4.5.15
Do we need Email
integration here?
4.6
User Interfaces
4.6.1
4.6.2
4.6.3
4.6.4
4.6.5
4.6.6
4.6.7
4.6.8
FC/PC/NC+NP/P
OB/MOD
Comments
Network Topology
Management
Vendor asserts its
solution supports:
5.1.1
5.1.2
5.1.3
Technical Requirements
5.1.4
5.1.5
5.1.6
5.2
System Resource
Management
Vendor asserts its
solution supports
monitoring of:
5.2.1
CPU utilization
5.2.2
Memory utilization
5.2.3
Disk utilization
5.2.4
5.3
Fault Management
Vendor asserts its
solution has event
management system
(EMS) that supports:
5.3.1
5.3.2
5.3.3
5.3.4
Technical Requirements
5.3.5
5.3.6
5.3.7
5.3.8
Real-time updating of
monitor windows as alarms
enter the EMS
5.3.9
5.3.10
5.3.11
5.3.12
5.3.13
5.3.14
5.3.15
5.3.16
5.3.17
131
Technical Requirements
5.3.18
5.3.19
5.3.20
5.3.21
5.3.22
5.3.23
Data Management
6.1
FC/PC/NC+NP/P
OB/MOD
Comments
Data Architecture
Vendor asserts its
solution supports:
6.1.1
6.1.2
6.1.3
6.1.4
6.1.5
Resiliency to transaction
failure or hardware failure
via suitable system
checkpoints, thus ensuring
data integrity at all times
132
Technical Requirements
6.1.6
Automated archiving
procedures that copy active
data to storage media when
the archive age has been
reached
6.1.7
6.1.8
An entity relationship
diagram
6.2
Importing Data
Vendor asserts its
solution supports:
6.2.1
Importing of data in a
comma separated values
(CSV) format
6.2.2
6.2.3
6.2.4
6.2.5
6.3
Exporting Data
Vendor asserts its
solution supports:
6.3.1
Exporting of data in a
comma separated values
(CSV) format
6.3.2
6.3.3
6.3.4
6.3.5
6.4
Data Transfers
133
Technical Requirements
6.4.1
6.4.2
6.4.3
6.4.4
6.5
Data Record Access
Vendor asserts its
solution supports:
6.5.1
6.5.2
6.5.3
6.5.4
Determine by system
administrators which record
layout views are available to
users or user groups
6.5.5
6.5.6
Definiation by system
administrators as to which
specific data fields users
can view or edit
6.5.7
6.6
Data Backups
Vendor asserts its
solution:
134
Technical Requirements
6.6.1
6.6.2
6.6.3
Supports reinstatement of
data into system
components from backups.
Please describe.
6.7
Data Storage
Vendor asserts its
solution supports:
6.7.1
6.7.2
Storage management
software to ensure that data
is not corrupted or lost in the
case of hardware or
software failures
6.8
On-line Data
Vendor asserts its
solution supports:
6.8.1
On-line availability of
customer interaction data for
a period of one year
6.8.2
On-line availability of
customer billing data (bills
and account information) for
a period of two years
6.8.3
6.8.4
6.8.5
6.8.6
7
7.1
FC/PC/NC+NP/P
OB/MOD
Comments
135
Technical Requirements
Encryption
Vendor asserts its
solution supports:
7.1.1
7.1.2
7.1.3
7.1.4
Server authentication
Data integrity assurance
Data encryption standard
(DES) data
Support for third-party
encryption tools or modules
7.1.5
Security zones
7.1.6
7.1.7
Encoding of information
transmitted over the Internet
using HTTPS and SSL
protocols
7.1.8
7.1.9
Digital certifications
Digital signatures
7.2
Access Control
Vendor asserts its
solution supports:
7.2.1
7.2.2
Organization-level access
control
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7.2.8
7.3
System Security
7.3.1
7.3.2
136
Technical Requirements
7.3.3
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8
7.3.9
7.3.10
7.3.11
7.3.12
7.3.13
Expiration of user
passwords after a preset
period
7.3.14
7.3.15
137
Technical Requirements
7.3.16
7.3.17
7.3.18
The ability of an
administrator to restrict an
access to the system based
on IP addresses
7.3.19
7.3.20
7.4
Security Management and
Audit Tools
Vendor asserts its
solution supports:
7.4.1
7.4.2
7.4.3
7.4.4
A mechanism to deactivate
users from all systems
7.4.5
7.4.6
Automatic logging of
changes to the system
setup, and tagging of which
user made each change
138
Technical Requirements
7.4.7
8.1
FC/PC/NC+P/NP
OB/MOD
Comments
Web Browsers
Vendor asserts its
solution supports the
following web browsers:
8.1.1
8.1.2
8.1.3
8.1.4
8.1.5
8.2
8.2.1
8.2.2
8.2.3
8.2.4
8.2.5
8.2.6
Degree of Web
Enablement
Vendor asserts its
solution supports:
A true web-based thin client
accessible via a web
browser
Intranet capabilities
Extranet capabilities
That lookups processed
online occur in real-time
That browses processed
online occur in real-time
That data validations
processed online occur in
real-time
8.2.7
8.2.8
Information on demand
8.3
Web Interface
Vendor asserts its
solution:
8.3.1
8.3.2
8.3.3
Technical Requirements
8.3.4
8.3.5
Supports pre-configured
screens
8.3.6
8.3.7
8.3.8
8.3.9
8.3.10
8.3.11
8.3.12
8.4
Web Functions and
Functionality
Vendor asserts its
solution supports:
8.4.1
8.4.2
8.4.3
8.4.4
8.4.5
8.4.6
8.4.7
8.4.8
8.4.9
8.4.10
A single enterprise-wide
application that houses
product management, sales
and order management, and
customer support
8.4.11
8.4.12
8.4.13
Mobile processing
environment
Multiple languages
Multiple window navigation
and tiling
140
Technical Requirements
8.4.14
8.4.15
Common development
language
Support & Maintenance
8.4.16
9
9.1
FC/PC/NC+NP/p
OB/MOD
Comments
Help Facilities
Vendor asserts its system
supports:
9.1.1
A comprehensive help
facility for each component
that can be initiated online
for each screen and each
data item on that screen
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.8
9.1.9
A clear explanation or
reason code when an
application error causes
abnormal termination
9.1.10
9.1.11
9.2
Technology Transfer and
Training
141
Technical Requirements
Vendor asserts it
supports:
9.2.1
A comprehensive in-person
training program that
ensures that Afghan
Telecom is prepared to
operate and support the
solution and systems
9.2.2
9.2.3
9.2.4
9.2.5
9.2.6
9.2.7
9.2.8
9.2.9
9.2.10
9.2.11
9.2.12
9.2.13
9.2.14
9.2.15
9.2.16
Train-the-trainer
142
Technical Requirements
9.2.17
Certification training
9.2.18
Industry (non-product)
training in CBS
9.2.19
Industry (non-product)
training in fraud
management
9.2.20
Industry (non-product)
training in revenue
assurance
9.2.21
Industry (non-product)
training in business process
management
(eTOM/NGOSS)
9.2.22
The provision of
comprehensive training
manuals
9.3
Documentation
9.3.1
9.3.2
Documentation in an
electronic format, such as
MS Word, PDF, ODF, or
similar
9.3.3
9.3.4
9.3.5
9.3.6
9.3.7
Business requirements
documentation
Systems requirements
documentation
9.3.8
Functional documentation
9.3.9
Technical documentation
9.3.10
Business process
documentation
9.3.11
Operational documentation
9.3.12
Data/object model
documentation
9.3.13
Database documentation
9.4
Support and Maintenance
Vendor asserts it will
provide:
143
Technical Requirements
9.4.1
9.4.2
9.4.3
9.4.4
9.4.5
Application of necessary
quality assurance processes
during the initial
development, as well as
post-production support and
maintenance
9.4.6
24x7 support
9.4.7
9.4.8
9.4.9
9.4.10
9.5
Release Management &
Control
Vendor asserts it will
provide:
9.5.1
9.5.2
10
FC/PC/NC+NP/P
OB/MOD
Comments
10.1
General
Vendor asserts that its
solution:
10.1.1
Incorporates industry
standards into the mediation
platform
10.1.2
Supports interface to
multiple networks
144
Technical Requirements
10.1.3
10.1.4
10.1.5
10.1.6
10.1.7
10.1.8
10.1.9
Supports interface to
automated clearing house
(ACH) systems
10.1.10
Collects, converts,
processes and distributes
event records from all
sources, including switches,
third-party files, servers,
AAA servers and RADIUS
servers
10.1.11
Supports automatic
collection, conversion, and
routing of event records
from arbitrary network
equipment to arbitrary
business and operations
support systems
10.1.12
10.1.13
145
Technical Requirements
10.1.14
10.1.15
10.1.16
10.1.17
10.1.18
10.1.19
10.2
Data Element Collection,
Handling, Processing, and
Distribution
10.2.1
10.2.2
10.2.3
Pulling or receiving of
pushed files from a systemconfigurable directory
10.2.4
10.2.5
10.2.6
10.2.7
Technical Requirements
10.2.8
10.2.9
10.2.10
10.2.11
The decoding/encoding of
event records
10.2.12
10.2.13
10.2.14
10.2.15
10.2.16
10.2.17
Detection of duplicate
records and elimination of
duplicate event records
10.2.18
Detection of duplicate
records based on the
composite key method, full
record or physical record
number gap analysis, or
time gap validation
10.2.19
147
Technical Requirements
10.2.20
10.2.21
Correlation of data
generated from GPRS, IP,
content billing, VoIP, and
specialized Internet
services, wireless calls with
handoffs, long duration calls,
and sessions, etc.
10.2.22
10.2.23
10.2.24
10.2.25
10.2.26
10.2.27
10.2.28
Replication (cloning) of
event records
Filtering and sorting of event
records
Reconciliation of event
records
Configurable and easily
customizable rules for
collection, correlation,
validation, conversion,
routing, filtering, and sorting
Downstream format
mapping
Header and trailer
generation
10.2.29
10.2.30
10.2.31
Application of rules to
change the value of a field
upon certain predefined
conditions in batch mode
10.2.32
148
Technical Requirements
10.2.33
Combination of multiple
event records into one
intermediate record of long
duration
10.2.34
10.2.35
10.2.36
10.2.37
10.3
Error Detection and
Handling
Vendor asserts that its
solution supports:
10.3.1
Performance of syntax
checks according to user
defined rules
10.3.2
Performance of checks on
data retrieved from
database lookups, such as
circuit, route, dialed number,
MSC, customer, etc.
10.3.3
Automatic generation of
alarms when errors are
detected in event records
10.3.4
Automatic generation of
alarms when an error type
repeats beyond a predefined
threshold
10.3.5
Configuration of alarm
conditions by Afghan
Telecom
10.3.6
Storage of erroneous
records for correction later,
and an editor to check
records, change the value of
the field, and provide
authority checks and an
audit trail
149
Technical Requirements
10.3.7
10.3.8
Subsequent re-input or
recycling of suspended
event records
10.3.9
Automatic collection
recovery when there are
abnormalities
10.4
CDR Aggregation and
Processing
Vendor asserts that its
solution:
10.4.1
10.4.2
10.4.3
10.4.4
10.4.5
10.4.6
10.4.7
10.4.8
10.4.9
Supports aggregation of
CDR data based on any
field of the CDRs
10.4.10
Supports aggregation of
CDR data based on any
group of fields or time span
10.4.11
Supports configurable
criteria for CDR data
aggregation and
summarization
150
Technical Requirements
10.4.12
10.4.13
10.4.14
10.4.15
Supports a sophisticated
query tool for searching the
CDR database
10.4.16
10.4.17
10.4.18
10.5
Mediation GUI Tasks
10.5.1
10.5.2
10.5.3
10.5.4
10.5.5
10.5.6
10.5.7
151
Technical Requirements
10.5.8
10.5.9
10.5.10
10.5.11
10.5.12
10.6
Reporting and Audit Trail
Vendor asserts that its
solution:
10.6.1
Generates statistics
regarding the number of
event records, by type
(normal, abnormal, error)
and in total
10.6.2
Generates statistics
regarding the number of files
10.6.3
Generates statistics
regarding the number of
event units
10.6.4
Generates statistics
regarding the number of
bytes
10.6.5
10.6.6
10.6.7
10.6.8
10.6.9
10.6.10
10.6.11
10.6.12
10.6.13
Aggregate number of
records received by record
type
152
Technical Requirements
10.6.14
10.6.15
10.6.16
10.6.17
10.6.18
10.6.19
10.6.20
10.6.21
10.6.22
11
FC/PC/NC+NP/P
OB/MOD
Comments
11.1
Basic Interconnect
System Services and
Functionality
Vendor asserts that its
system supports:
11.1.1
National interconnect
settlement and wholesale
billing and reconciliation
based on parameters in the
interconnect agreements
11.1.2
International interconnect
settlement and wholesale
billing and reconciliation
based on parameters in the
interconnect agreements
11.1.3
11.1.4
11.1.5
11.1.6
11.1.7
Technical Requirements
11.1.8
11.1.9
Status checking of
interconnection settlement
rating files received from
multiple exchanges
11.1.10
11.1.11
11.1.12
11.1.13
11.1.14
11.1.15
11.1.16
11.1.17
11.1.18
Management of suspended
CDRs
Settlement billing workflow
diagram
Interconnect partner
management
Functionality in sections 1222 for interconnect
settlement and wholesale
billing
11.2
Interconnect Agreement
Arrangements
Vendor asserts its system
supports the following
interconnect agreement
arrangements:
11.2.1
11.2.2
11.2.3
11.2.4
11.2.5
Divisions of revenue
agreements (ITU-based)
11.2.6
Interconnect settlement
11.2.7
11.2.8
11.2.9
Technical Requirements
11.2.10
Minutes-based
11.2.11
11.2.12
11.2.13
11.2.14
11.2.15
PSTN-mobile
interconnection (and vice
versa)
11.2.16
Mobile-to-mobile (roaming)
interconnection and
settlement (national and
international)
11.3
Service Types
Vendor asserts its system
supports interconnect
settlement and wholesale
billing:
11.3.1
11.4
Internetworking
Vendor asserts its system
supports the following:
11.4.1
11.4.2
11.4.3
11.4.4
11.4.5
11.4.6
11.4.7
Technical Requirements
11.5
11.5.1
11.5.2
11.5.3
11.5.4
11.5.5
11.5.6
11.5.7
Returned accounts
procedure (RAP) file
receiving (list standards
supported)
11.5.8
11.5.9
11.5.10
11.5.11
11.5.12
11.6
Dial Code Treatment
Please describe how your
solution handles dial codes.
Vendor asserts that its
system supports:
11.6.1
11.6.2
11.6.3
156
Technical Requirements
11.6.4
11.6.5
11.6.6
11.6.7
11.7
Reconciliation and
Settlement
Vendor asserts that its
system supports:
11.7.1
A flexible reporting
subsystem to facilitate CDR
analysis
11.7.2
11.7.3
11.7.4
11.7.5
Importing of incoming
electronic summary usage
figures from interconnect
partners
11.7.6
11.7.7
Processing of incoming
CDRs and usage data as
declared by interconnect
partners, including wire line
operators, mobile operators,
ISPs, and other operators
11.7.8
Validation of received
declarations against Afghan
Telecom data
11.7.9
11.7.10
157
Technical Requirements
11.7.11
11.7.12
11.8
Statement Preparation and
Production; Invoicing and
Accounting
Vendor asserts that its
system supports:
11.8.1
11.8.2
Production of statements
that include detailed
incoming, outgoing, and
transit information
11.8.3
Production of preliminary
(pre-settlement) statements
11.8.4
Adjustments in the
settlement process before
final statements are
produced
11.8.5
11.8.6
Flexible invoicing
arrangements and methods
11.8.7
11.8.8
Interface to financial
systems to send and receive
G/L transactions
11.9
Reporting
11.9.1
11.9.2
11.9.3
Technical Requirements
11.9.4
11.9.5
Reporting by element or
unit, groups of elements or
units, individually, and in the
aggregate
11.9.6
11.9.7
11.9.8
11.9.9
Standard reports
11.9.10
11.9.11
11.9.12
11.9.13
11.9.14
11.9.15
Customizable reports
11.9.16
Scheduling of reports
11.9.17
11.9.18
Exception reports
11.9.19
Location-based statistics
and reports
11.9.20
11.9.21
Technical Requirements
11.9.22
11.9.23
11.9.24
11.9.25
11.9.26
11.9.27
11.9.28
11.9.29
11.9.30
12
FC/PC/NC+NP/P
OB/MOD
Comments
12.1
Product and Service
Catalog
Vendor asserts its
solution supports:
12.1.1
12.2
Voice Services
Vendor asserts its
solution supports billing
for:
12.2.1
12.2.2
12.2.3
12.2.4
12.2.5
12.2.6
Operator services
12.2.7
12.2.8
12.2.9
12.2.10
Emergency calls
160
Technical Requirements
12.2.11
12.2.12
12.3
Data Services
Vendor asserts its
solution supports billing
for:
12.3.1
12.3.2
12.3.3
12.3.4
12.3.5
12.4
Other Services
Vendor asserts its
solution supports billing
for:
12.4.1
12.4.2
12.4.3
12.4.4
12.4.5
12.4.6
12.4.7
12.4.8
12.4.9
Number portability
12.4.10
12.4.11
Satellite-based village
communication network
(VCN) service
12.4.12
12.4.13
12.4.14
161
Technical Requirements
12.5
Features and Value-Added
Services (VAS)
Vendor asserts its
solution supports billing
for:
12.5.1
12.5.2
Call divert
12.5.3
Call forward
12.5.4
Call barring
12.5.5
Call transfer
12.5.6
Call hold
12.5.7
Call waiting
12.5.8
12.5.9
12.5.10
Voicemail service
12.5.11
12.5.12
12.5.13
12.6
Equipment and Related
Services
Vendor asserts its
solution supports billing
for:
12.6.1
Equipment (dongles,
modems, handsets, PBX,
other customer premise
equipment (CPE), etc.) and
accessories sales and
rentals
12.6.2
12.6.3
Insurance
12.6.4
12.7
Mobile Products and
Services and Wireless
Technologies
Vendor asserts its
solution supports billing
for:
12.7.1
Technical Requirements
12.7.2
12.7.3
12.7.4
2G to 4G services, including
3GPP and 4G/LTE - please
list
12.7.5
GPRS/EDGE
12.7.6
HSDPA/HSPA/HSUPA
12.7.7
12.7.8
12.7.9
12.7.10
12.7.11
12.7.12
12.7.13
Unstructured supplementary
service data (USSD) and
USSD callback
12.7.14
Standard GPRS-based
features and upgrades
12.7.15
12.7.16
12.7.17
12.7.18
12.7.19
Top-up cards
12.7.20
Microwave circuits
12.7.21
WiFi
12.7.22
WiMAX
12.7.23
WiMAX fixed
12.7.24
12.8
Optical Fiber Services
Vendor asserts its
solution supports billing
for:
12.8.1
Technical Requirements
12.8.2
12.8.3
12.8.4
Dark fiber
12.8.5
12.8.6
Distribution
Channels
13
FC/PC/NC+NP/P
OB/MOD
Comments
Vendor
asserts its
solution
supports
billing for
the
following
distributio
n
channels:
13.1
Retail
13.2
Resale
13.3
Wholesale
13.4
Agents
13.5
Distributor
s
13.6
Affinity
marketers
13.7
Call shops
13.8
Internet
cafs
164
Technical Requirements
13.9
Points of
sale (POS)
13.10
Other
(please
describe)
Customer, Account and
Credit Management
14
FC/PC/NC+NP/P
OB/MOD
Comments
14.1
General
Vendor asserts its
solution supports:
14.1.1
Default subscription
definition by system and
Afghan Telecom
14.1.2
Overriding of default
subscription definition
14.1.3
Creation of subscriptions
within account and customer
hierarchies
14.1.4
Modification of subscription
expiration date upon
activation
14.2
Authorization and Audit
Vendor asserts its
solution supports:
14.2.1
14.2.2
Recording of authority
reference and date of
approval for changes to
customer, account and
credit data
14.2.3
14.2.4
14.3
Credit Verification, Limits
and Control
Vendor asserts its
solution supports:
165
Technical Requirements
14.3.1
14.3.2
14.3.3
14.3.4
Parameter-driven credit
thresholds and limits
14.3.5
14.3.6
14.3.7
Use/application of a credit
balance for charges and
fees and toward usage
14.3.8
Decrementing of account
balance in full prior to using
credit balance
14.4
Account Establishment
Vendor asserts its
solution supports:
14.4.1
14.4.2
Customizable accounts
14.4.3
End-user establishment of
accounts via multiple media
(online, IVR, etc.)
14.5
Account Hierarchy and
Groups
Vendor asserts its
solution supports:
14.5.1
14.5.2
166
Technical Requirements
14.5.3
14.5.4
Multiple simultaneous
reservations on shared
accounts
14.5.5
Configurable consumption
limits by individual group
member and total group
14.5.6
14.5.7
Consumption limit
14.5.8
Service type
14.5.9
Time schema
14.5.10
Percentage
14.5.11
Unlimited
14.6
Account Adjustments
14.6.1
14.6.2
14.6.3
14.6.4
14.6.5
14.6.6
14.7
Lifecycle States
Vendor asserts its
solution supports:
14.7.1
14.7.2
Technical Requirements
14.7.3
14.7.4
14.7.5
14.7.6
14.7.7
14.7.8
14.7.9
14.7.10
14.7.11
14.7.12
15
15.1
FC/PC/NC+NP/P
OB/MOD
Comments
Tariffs
General
15.1.1
15.1.2
15.1.3
15.1.4
15.1.5
15.1.6
15.1.7
Technical Requirements
15.1.8
15.1.9
15.1.10
15.1.11
15.1.12
Storage, maintenance,
archiving and retrieval of
historical tariffs
15.1.13
15.2
Tariff Modifications
Functionality
Authorization and Audit
Vendor asserts its
solution supports:
15.2.1
15.2.2
Recording of authority
reference and date of
approval for changes to
tariffs and tariff plans
15.2.3
15.2.4
15.3
General
Vendor asserts its
solution supports the
following:
15.3.1
15.3.2
15.3.3
169
Technical Requirements
15.3.4
15.3.5
15.3.6
Accommodation of tariffs
with start and end dates, or
start date and open end
date
15.3.7
Application of pricing
packages, discounts, and
promotions without
modifying original tariff plan
15.3.8
Addition, modification, or
removal of tariff plans prior
to the change effective date
15.3.9
15.3.10
15.3.11
15.3.12
15.3.13
15.3.14
15.3.15
15.3.16
15.3.17
15.3.18
Technical Requirements
15.4
Tariff Plan Search,
Storage and Retrieval
Vendor asserts its
solution supports:
15.4.1
Storage, maintenance,
archiving and retrieval of
historical tariff plans
15.4.2
15.4.3
15.4.4
15.4.5
15.4.6
15.5
Charges
Categories of Charges
Vendor asserts its
solution supports:
15.5.1
Prepaid charges
15.5.2
Postpaid charges
15.5.3
15.5.4
15.5.5
Recurring charges
15.5.6
15.5.7
Flat-rate charges
15.5.8
Usage-based charges
15.5.9
Duration-based charges
15.5.10
Distance-based charges
15.5.11
15.5.12
15.5.13
Roaming charges
15.5.14
Location-based charges
15.5.15
Non-charged events
15.5.16
Non-charging based on
defined business rules (e.g.,
X minutes or KBs free)
171
Technical Requirements
15.5.17
Session charges
15.5.18
Surcharges
15.5.19
15.5.20
15.5.21
15.5.22
15.5.23
15.5.24
Bundling of charges
15.5.25
Differential charging
15.5.26
15.5.27
Commission charges
15.5.28
15.5.29
15.6
Specific Types of Charges
Vendor asserts its
solution supports:
15.6.1
15.6.2
15.6.3
15.6.4
Operator-assisted calls
15.6.5
15.6.6
15.6.7
15.6.8
15.6.9
15.6.10
Technical Requirements
15.6.11
15.6.12
Content-based charges
(Afghan Telecom and thirdparty)
15.6.13
Interactive services
15.6.14
Mobile services
15.6.15
15.6.16
15.6.17
15.6.18
15.6.19
15.6.20
Fixed fee
15.6.21
Rank pricing
15.6.22
15.6.23
Reference pricing
15.6.24
Mixed pricing
15.6.25
15.7
Charge Functionality
Authorization and Audit
Vendor asserts its
solution supports:
15.7.1
15.7.2
Recording of authority
reference and date of
approval for changes to
charges
15.7.3
15.7.4
Technical Requirements
Charging and Balance
Control
16
FC/PC/NC+NP/P
OB/MOD
Comments
16.1
General
Vendor asserts its
solution supports:
16.1.1
16.1.2
16.1.3
16.1.4
Different charging
mechanisms available for
different sales and
distribution channels,
including for POS and hybrid
customers
16.1.5
Generation of charges
based on applicable tariff
plan(s) or other relevant
charge data
16.1.6
Generation of charges
based on third-party costs
and prices
16.1.7
16.1.8
Application of different
charges for the same
destination, unit, or other
charged service or event
depending on variables such
as account, subscriber,
activation date, and type of
customer
16.1.9
16.1.10
16.1.11
174
Technical Requirements
16.1.12
Accommodation of charges
with start and end dates, or
start date and open end
date
16.1.13
16.1.14
Accrual of charges up to
prepaid balance and credit
limit
16.1.15
16.1.16
16.1.17
16.1.18
Charging by a period
different than the bill cycle,
such as on an annual basis,
over multiple bill cycles, and
by remaining days of the
month or year
16.1.19
16.1.20
16.1.21
16.1.22
16.1.23
16.1.24
16.1.25
Storage, maintenance,
archiving and retrieval of
historical charges
16.1.26
16.1.27
Automatic generation of
charges for the printing and
reprinting of invoices and
call detail reports
175
Technical Requirements
16.1.28
16.1.29
16.1.30
16.1.31
16.2
Recurring Charges
Vendor asserts its
solution supports:
16.2.1
Calculation of recurring
charges based on standard
and customer-defined
intervals
16.3
Non-recurring Charges
Vendor asserts its
solution supports:
16.3.1
Calculation of non-recurring
charges, standard and
customer-configurable
16.3.2
Manually-added one-off
charges
16.4
Flat-rate Charges
16.4.1
16.4.2
16.4.3
Technical Requirements
16.5
Usage-based Charges
Vendor asserts its
solution supports:
16.5.1
Calculation of usage-based
charges for both voice and
data services
16.5.2
16.5.3
Charging based on
origination, termination, or
both
16.5.4
16.5.5
16.5.6
16.5.7
16.5.8
Configurable minimum
number of seconds before a
call is charged (minimum
call duration)
16.5.9
16.5.10
Customer-defined rounding
rules for usage charges
16.5.11
16.5.12
16.5.13
177
Technical Requirements
16.5.14
16.5.15
16.5.16
16.6
16.6.1
16.6.2
16.6.3
16.6.4
16.6.5
Non-charging of sessions
(e.g., for mobile-to-mobile
calls, toll-free calls,
emergency services calls,
short codes)
16.6.6
16.6.7
Charging of mobile
subscriber-originated calls to
independent network
services
16.7
Data Service Charges
Vendor asserts its
solution supports:
16.7.1
Technical Requirements
16.7.2
16.7.3
16.7.4
16.7.5
16.8
Differential Charging
Vendor asserts its
solution supports:
16.8.1
16.8.2
16.8.3
16.8.4
16.9
Preferential Charging
Vendor asserts its
solution supports:
16.9.1
16.10
Caclulation and
Application of Charges
Vendor asserts its
solution supports:
16.10.1
16.10.2
16.10.3
16.10.4
16.10.5
Technical Requirements
16.10.6
Inclusion or exclusion of
specific charges in the
calculation of discounts,
fees and taxes
16.10.7
Application of charges to a
subscriber, account or
customer directly
16.10.8
Application of charges to
another subscriber, account
or customer
16.10.9
16.10.10
16.10.11
16.11
Commission and ThirdParty Charges
Vendor asserts its
solution supports:
16.11.1
Calculation of commission
charges on units and usage
(volume and revenue)
16.11.2
Calculation of commission
charges by account,
customer, product/service,
or other criteria
16.11.3
Calculation of commission
charges by sales person
and sales channel,
individually and in the
aggregate
16.11.4
16.12
Online Charging Gateway
Vendor asserts its
solution supports:
16.12.1
Technical Requirements
16.12.2
16.12.3
Pre-charge confirmation
16.12.4
16.12.5
16.12.6
Balance-on-demand
capabilities
Multiple access modes
(please describe)
Virtual distribution
16.13
Balance Functionality
16.13.1
16.13.2
16.13.3
16.13.4
16.13.5
16.13.6
16.13.7
16.13.8
16.13.9
16.13.10
16.13.11
181
Technical Requirements
16.13.12
16.13.13
16.13.14
16.13.15
Administering several
balances in different units
for an account (e.g., a voice
balance in money and a
data balance in MB)
16.13.16
16.13.17
16.13.18
16.13.19
Registering of multiple
balances in the same unit,
e.g., a private balance and a
business balance
16.13.20
Configurable balance
expirations with override
capability
16.13.21
Communication of balance
expiration to change
account state
16.13.22
Automatic resetting of
customer to active state
upon recharge
182
Technical Requirements
16.13.23
16.13.24
Decrementing of account
balance in full prior to using
credit balance
16.13.25
Use/application of a credit
balance for charges and
fees and toward usage
16.13.26
16.13.27
16.13.28
16.13.29
Application of refunds,
discounts, and rebates as a
balance credit
16.14
Reserve Balances
Vendor asserts its
solution supports:
16.14.1
Real-time balance
reservation capabilities,
configurable and executable
by end-users
16.14.2
16.14.3
Multiple simultaneous
balance reservations
16.14.4
Balance reservation
cancellation and refunds in
real time
16.15
Balance Transfers
183
Technical Requirements
Vendor asserts its
solution supports:
16.15.1
Tranferring balances
between and among
accounts of different
subscribers
16.15.2
16.15.3
16.15.4
16.15.5
16.15.6
16.15.7
Limitations on transferer's
balance during transfers
Limitations on transferer
amounts
Charging for balance
transfers
Notifications of balance
transfers
16.15.8
16.15.9
16.15.10
16.16
Hybrid Customers
Vendor asserts its
solution supports:
16.16.1
16.16.2
16.16.3
16.16.4
16.17
Voucher Management
Please describe:
184
Technical Requirements
16.17.1
16.17.2
16.17.4
16.17.5
16.17.6
An import function to
introduce internal and
externally-generated
voucher number ranges via
a batch interface
16.17.7
Voucher activation by
entering voucher serial
number only
16.17.8
No time restrictions on
voucher activations (can be
done at any time of day)
16.17.9
16.17.10
Querying of vouchers by
voucher serial number and
by voucher code
16.17.11
16.17.3
16.18
Recharging
Vendor asserts its
solution supports:
16.18.1
16.18.2
16.18.3
Customer-triggered and
automatic recharging (e.g.,
upon reaching minimum
balance)
185
Technical Requirements
16.18.4
16.18.5
16.18.6
16.18.7
16.18.8
16.19
Messaging and Charge
Information
Vendor asserts its
solution supports:
17
16.19.1
16.19.2
16.19.3
16.19.4
16.19.5
Ability to provide
notifications in multiple
languages and currencies
Rates and Rating
FC/PC/NC+NP/P
17.1
OB/MOD
Comments
Rating by Event
Type/Category
Vendor asserts its
solution supports rating
by/for:
186
Technical Requirements
17.1.1
17.1.2
Tariff plan
17.1.3
Tariff class
17.1.4
Type of subscriber
17.1.5
Type of account
17.1.6
Type of customer
17.1.7
17.1.8
Event
17.1.9
Usage
17.1.10
17.1.11
Distance
17.1.12
Total usage/volume
17.1.13
Time of day
17.1.14
Day of week
17.1.15
17.1.16
17.1.17
17.1.18
Local calls
17.1.19
17.1.20
Regional calls
17.1.21
National calls
17.1.22
International calls
17.1.23
17.1.24
17.1.25
On-net calls
17.1.26
Off-net calls
17.1.27
17.1.28
Shared-cost calls
17.1.29
Premium-rate calls
187
Technical Requirements
17.1.30
17.1.31
17.1.32
17.1.33
17.1.34
Originating zone/band (A
number)
Terminating zone/band (B
number)
Combination of originating
zone/band (A number) and
terminating band/zone (B
number)
Special B numbers and
short codes
Special A and B number
pairs
17.1.35
17.1.36
Destination-specific calls
17.1.37
17.1.38
17.1.39
17.1.40
Time bands
17.1.41
17.1.42
17.1.43
Internet bandwidth/data
service, by usage (e.g,
Mbytes)
17.1.44
Internet bandwidth/data
service, by duration
connected
17.1.45
17.1.46
17.1.47
17.1.48
Location-based services
17.1.49
17.1.50
17.1.51
17.1.52
Volume rating
17.1.53
Flat-rate events
188
Technical Requirements
17.1.54
Fixed-charge events
17.1.55
Interactive events
17.1.56
17.1.57
17.1.58
17.2
Rating Engine
17.2.1
17.2.2
17.2.3
Real-time rating
17.2.4
17.2.5
17.2.6
17.2.7
17.2.8
17.2.9
17.2.10
Configurable dynamic
exchange rates
17.2.11
Multi-dimensional rating
17.2.12
17.2.13
17.2.14
17.3
Functionality
Authorization and Audit
Vendor asserts its
solution supports:
189
Technical Requirements
17.3.1
17.3.2
Recording of authority
reference and date of
approval for changes to
rates
17.3.3
17.3.4
17.4
Multiple Rating Processes
Vendor asserts that its
solution supports:
17.4.1
17.4.2
Rating processes to
calculate and apply,
separately or in
combination, fees,
discounts, taxes and
commissions
17.4.3
17.4.4
17.5
General
Vendor asserts its
solution supports:
17.5.1
17.5.2
17.5.3
17.5.4
Filtering of non-chargeable
records from chargeable
records
Rating by any field in the
CDR/UDR
Rating by a combination of
fields in the CDR/UDR
Rating of raw and rounded
usage/data
17.5.5
17.5.6
Technical Requirements
17.5.7
17.5.8
Rating according to
rounding rules (initial and
incremental)
17.5.9
17.5.10
Processing of pre-rated
CDRs/UDRs
17.5.11
17.5.12
Re-rating of unrated
CDRs/UDRs, automtically
and on demand
17.5.13
17.5.14
17.5.15
17.5.16
17.5.17
17.5.18
17.5.19
17.5.20
17.5.21
17.5.22
191
Technical Requirements
17.5.23
17.5.24
Real-time determination of
the tariff plan under which
the service shall be rated
17.5.25
17.5.26
Application of third-party
rates and tariff plans
17.6
Usage Rating
Vendor asserts its
solution supports:
17.6.1
17.6.2
17.6.3
17.6.4
Configurability as to
whether, for calls/sessions
spanning different time
bands, the whole
call/session is charged at
the initial time band rate or
the call is charged at the
appropriate rate for the time
duration in each time band
17.6.5
Identification of variations in
usage records and
generation of warning
messages
17.6.6
Identification of unrated
usage
17.6.7
17.6.8
Examination of usage
records through on-line
access to these records
17.6.9
192
Technical Requirements
17.6.10
Investigations based on
customer-defined criteria,
such as a search for B
number usage
17.7
Call Charge and Long
Distance Rating
Vendor asserts its
solution supports:
17.7.1
Rating by dial-code, by
origination, termination or
both
17.7.2
Ability to accommodate
multiple dial-code lists,
whether by product, service,
account, customer, etc.
17.7.3
17.7.4
17.7.5
17.7.6
Outcollect processing
17.7.7
Incollect processing
17.7.8
Clearinghouse functionality
17.7.9
Local portability
17.7.10
Service portability
17.8
Mobile and Wireless
Vendor asserts its
solution supports:
17.8.1
17.8.2
193
Technical Requirements
17.8.3
17.8.4
17.9
Other
Vendor asserts its
solution supports:
17.9.1
17.9.2
17.10
Rate Search, Storage and
Retrieval
Vendor asserts its
solution supports:
17.10.1
17.10.2
17.10.3
17.10.4
Storage, maintenance,
archiving and retrieval of
historical rates
Storage, maintenance, and
retrieval of future rates
The ability to correct
historical rate errors
Extensive search criteria to
query rates (past, present
and future)
194
Technical Requirements
17.10.5
17.10.6
18
FC/PC/NC+NP/P
OB/MOD
Comments
18.1
Types of Fees
Vendor asserts its
solution supports:
18.1.1
18.1.2
18.1.3
Regulatory fees
18.1.4
Transaction fees
18.1.5
Activity fees
18.1.6
Commission fees
18.1.7
18.1.8
18.1.9
18.1.10
18.1.11
18.1.12
18.1.13
Miscellaneous fees
18.1.14
18.2
Fee Schedules
Vendor asserts its
solution supports:
18.2.1
Specification of which
portfolios are associated
with which fee schedules
18.2.2
18.2.3
18.2.4
Account-specific fee
schedules and discounts
Application of multiple fee
schedules
195
Technical Requirements
18.2.5
Assignment of fee
schedules based on
activities that require manual
intervention, versus those
that are a straight through
process
18.3
Calculation and
Application of Fees
Vendor asserts its
solution supports:
18.3.1
Specification of the
beginning and end date for a
fee period
18.3.2
Proration of fees
18.3.3
18.3.4
Calculation of fees
automatically by customerdefined variables and
manually
18.3.5
18.3.6
18.3.7
18.3.8
18.3.9
Inclusion or exclusion of
attributes (such as
payments, receivables,
other fees) for fee
calculation
18.3.10
18.3.11
Calculation of commission
fees on units and usage
(volume and revenue)
18.3.12
Calculation of commission
fees by account, customer,
product/service, or other
criteria
18.3.13
Calculation of commission
fees by sales person and
sales channel, individually
and in the aggregate
196
Technical Requirements
18.3.14
18.3.15
Calculation, modification,
and accrual of fees for thirdparty providers and
intermediaries based on fee
schedules, transaction
volumes, assets, or
negotiated terms and rates
and business rules
18.3.16
18.3.17
18.3.18
18.3.19
18.3.20
18.3.21
Recalculation/correction of
erroneous fees
18.3.22
18.4
Taxes
Vendor asserts its
solution supports:
18.4.1
18.4.2
18.4.3
18.4.4
18.4.5
197
Technical Requirements
18.4.6
18.4.7
Inclusion or exclusion of
attributes (such as
payments, receivables,
other fees) for tax
calculation
18.4.8
18.4.9
18.4.10
18.4.11
18.4.12
18.4.13
Editing of taxes
18.4.14
18.4.15
18.4.16
18.4.17
18.4.18
18.4.19
19
FC/PC/NC+NP/P
OB/MOD
Comments
19.1
Packages (Bundling)
Vendor asserts its
solution supports:
19.1.1
19.1.2
Flexibility to specify
pricing/tariff plans and
conditions, such as eligible
customer profiles and
payment terms, for each
package
198
Technical Requirements
19.1.3
19.1.4
19.1.5
19.1.6
19.1.7
Display of packages,
discounts, and promotions
(e.g, savings rendered and
how) on invoices
19.2
Discounts
Types of Discounts
Vendor asserts its
solution supports
discounts based on:
19.2.1
19.2.2
19.2.3
19.2.4
19.2.5
19.2.6
19.2.7
19.2.8
19.2.9
Packages or bundles
19.2.10
Time of day
19.2.11
19.2.12
199
Technical Requirements
19.2.13
19.2.14
Features or groups of
features
19.2.15
19.2.16
19.2.17
19.2.18
Step-wise cumulative
discount (at least five levels)
19.2.19
Volume/usage - specific
destination, product/service
and total
19.2.20
19.2.21
19.2.22
19.2.23
19.2.24
19.2.25
Loyalty plans
19.2.26
"Affinity" or "association"
programs, where identified
customers are part of a
specific group that is given a
reduced rate or discount
19.2.27
Referrals
19.2.28
Customized contracts
19.3
Discount Functionality
Vendor asserts its
solution supports:
19.3.1
Real-time discounting
19.3.2
Periodic discounting
19.3.3
Flexible, customizable
discounting mechanisms
19.3.4
Percentage discounts
200
Technical Requirements
19.3.5
19.3.6
Unit discounts
19.3.7
Cross-product/service
discounts, such as buy one
product/service and get a
discount on another other
product/service
19.3.8
19.3.9
Assignment of multiple
discounts plans to multiple
products/services, accounts,
customers, etc.
19.3.10
19.3.11
19.3.12
19.3.13
19.3.14
"Double-dipping"
discounting
Multi-discount qualification
rules
19.3.15
Multi-customer usage
aggregation for volume
discounting
19.3.16
Rebates
19.3.17
Application of discounts as a
balance credit
19.4
Promotions
19.4.1
19.4.2
Promotions specific to
products/services and
supplementary services
19.4.3
19.4.4
19.4.5
19.4.6
19.4.7
19.4.8
Promotions specific to
market segments
Multi-product and multiservice promotions
Promotions for referrals
Award of free units as
promotional scheme
Promotions that combine
discounts and free units
19.5
Free Units
Vendor asserts its
solution supports:
201
Technical Requirements
19.5.1
19.5.2
19.5.3
19.5.4
19.6
Customer Loyalty
Programs
Vendor asserts its
solution supports:
19.6.1
19.6.2
19.7
External Alliances
Vendor asserts its
solution supports:
19.7.1
19.7.2
20
FC/PC/NC+NP/P
OB/MOD
Comments
20.1
General
Vendor asserts its
solution supports:
20.1.1
20.1.2
Paper invoicing
20.1.3
Technical Requirements
20.1.4
20.1.5
20.1.6
20.1.7
20.2
Authorization and Audit
Vendor asserts its
solution supports:
20.2.1
20.2.2
Recording of authority
reference and date of
approval for all changes
20.2.3
20.2.4
20.2.5
20.3
Data Importing
Vendor asserts its
solution supports:
20.3.1
Import of calculated
customer charges from
other billing systems, such
as IN, ISP and PDN billing
systems through standard
interfaces
20.3.2
Import of calculated
customer charges generated
by other billing
systems/partners, such as
the IN, ISP, and PDN billing
systems, from standard text
formatted files
20.3.3
Technical Requirements
20.4
Billing Functionality
Vendor asserts its
solution supports:
20.4.1
Specification by Afghan
Telecom or customer of the
currency to calculate
invoices in
20.4.2
Specification by Afghan
Telecom or customer of the
currency to present invoices
in
20.4.3
Specification by Afghan
Telecom or customer of the
language to present invoices
in
20.4.4
20.4.5
Presentation of invoices in
multiple languages
20.4.6
Monitoring of back-end
billing processes and status
checks on each node
20.4.7
20.4.8
20.4.9
20.4.10
20.4.11
20.4.12
20.4.13
20.4.14
20.4.15
20.4.16
Invoicing of an account or
customer directly
204
Technical Requirements
20.4.17
20.4.18
20.4.19
Combining accounts or
customers into a single
invoice
20.4.20
20.4.21
20.4.22
20.4.23
Flexible invoicing to
customers with hierarchical
accounts
20.4.24
20.4.25
20.4.26
Custom messages on
invoices and statements,
based on variables such as
customer type,
product/service, payment
status
20.4.27
20.5
Bill Messages
Vendor asserts its
solution supports:
20.5.1
Addition of messages
(marketing and financial) to
invoices
205
Technical Requirements
20.5.2
20.5.3
20.5.4
20.5.5
Addition or suppression of
specific messages based on
selected criteria, such as
type of customer or account,
total bill amount,
products/services, and
location
Prioritization of messages
based on customer profile
Addition of reminders to
invoices
Messages that are in the
same language as the bill
20.5.6
20.5.7
20.5.8
20.6
20.6.1
20.6.2
Customer/subscriber
information, including name
and unique identifier
20.6.3
Account(s) information
20.6.4
Summary charge
information
20.6.5
20.6.6
Previous balance,
payments, and credits
20.6.7
Remittance information
20.6.8
Parameter-driven invoice
and statement formats, in
which fields and sections
may be added, amended,
and deleted without help
from the vendor, and with
flexible, configurable layouts
20.6.9
206
Technical Requirements
20.6.10
20.6.11
20.6.12
20.6.13
20.6.14
20.6.15
20.6.16
Customization of invoice
and statement formats for
specific customers
20.6.17
Display or suppression of
call details based on
specified criteria and
customer preference, such
as usage type, service type,
and bill amount
20.6.18
Double-sided printing of
invoices and statements
20.6.19
20.6.20
20.6.21
20.6.22
20.7
Bill Cycle Processing
Vendor asserts its
solution supports:
20.7.1
20.7.2
20.7.3
20.7.4
207
Technical Requirements
20.7.5
20.7.6
20.7.7
20.7.8
20.7.9
Identification of any
discrepancies found in the
reconciliation process,
investigation of these
discrepancies, and reporting
on any discrepancy found
20.7.10
Reprocessing of a billing
cycle in order to
accommodate new billing
data and to correct errors
20.7.11
20.7.12
20.7.13
20.7.14
Out-of-cycle on demand
billing (hot billing)
20.7.15
20.7.16
20.7.17
20.7.18
Flagging of customers or
accounts whose billing
cycles should not be
changed
208
Technical Requirements
20.7.19
Configurable exclusion of
event records from an
indefinite number of days
before the date of the actual
bill run, and then addition of
them in the next bill run
(configurable cut-off dates)
20.7.20
20.7.21
20.7.22
Generation of exception
reports for all unbilled
charges and unaccounted
for events, in total and by
configurable parameters
20.8
Bill Management Files
Vendor asserts its
solution supports:
20.8.1
20.8.2
20.8.3
20.8.4
20.9
Sample Bills and Bill
Verification
Vendor asserts its
solution supports:
20.9.1
20.9.2
20.9.3
Technical Requirements
20.9.4
20.9.5
20.10
Invoice and Statement
Generation, Printing, and
Presentment
20.10.1
20.10.2
20.10.3
20.10.4
20.10.5
20.10.6
20.10.7
20.10.8
20.10.9
210
Technical Requirements
20.10.10
20.10.11
20.10.12
20.10.13
20.10.14
20.10.15
20.10.16
Generation of multiple
copies of invoices and
statements
20.10.17
Sending of invoices to
multiple addresses within
the customer or account
hierarchy
20.10.18
20.10.19
20.10.20
20.10.21
Availability or export of
invoice and statement
informaton to external
systems, such as IVR
20.10.22
20.11
Bill Inserts
20.11.1
Technical Requirements
20.11.2
General inserts
20.11.3
20.11.4
Customer type
20.11.5
Product/service
20.11.6
20.11.7
Bill cycle
20.11.8
Geographical area
20.11.9
20.11.10
Consumption level
20.11.11
20.12
Types of Bills and Billing
Advice
Normal Bills
Vendor asserts its
solution supports:
20.12.1
20.12.2
20.13
Bills upon Subscription or
Service Termination
Vendor asserts its
solution supports:
20.13.1
Bills, automatically or on
demand, for customers
terminating their
subscription or services
20.13.2
Technical Requirements
20.13.3
20.13.4
20.13.5
20.13.6
20.14
Split Bills
20.14.1
20.14.2
20.14.3
20.14.4
20.14.5
20.14.6
20.15
Bills on Demand
Vendor asserts its
solution supports:
20.15.1
20.15.2
213
Technical Requirements
20.15.3
20.15.4
20.15.5
20.15.6
20.15.7
20.15.8
20.16
Billing Advice
20.16.1
20.16.2
20.16.3
20.16.4
20.16.5
Technical Requirements
20.16.6
20.16.7
20.17
Interface to Financial
Systems
Vendor asserts that its
solution supports:
20.17.1
20.17.2
20.17.3
20.17.4
20.17.5
20.17.6
21
FC/PC/NC+NP/P
OB/MOD
Comments
21.1.2
Recording of authority
reference for all payment
transactions
21.1.3
21.1.4
215
Technical Requirements
21.1.5
21.2
Types and Methods of
Payments
Vendor asserts its
solution supports the
following payment
methods:
21.2.1
Cash
21.2.2
Check
21.2.3
21.2.4
Credit card
21.2.5
Debit card
21.2.6
21.2.7
Lockbox
21.2.8
21.2.9
Vouchers
21.3
EBPP
Vendor asserts its
solution:
21.3.1
21.3.2
21.4
Deposit and Prepayments
Vendor asserts its
solution supports:
21.4.1
21.4.2
21.4.3
Ability to decrement a
deposit or prepayment for
unpaid charges
216
Technical Requirements
21.4.4
21.4.5
21.5
21.5.1
21.5.2
21.5.3
21.5.4
21.5.5
21.5.6
21.5.7
Externally-initiated payment
requests (e.g., from
payment gateways, e-care)
21.5.8
21.5.9
21.5.10
Application of payments, in
full or in part, to customer
accounts
21.5.11
Application of payments, in
full or in part, to other
accounts
21.5.12
217
Technical Requirements
21.5.13
21.5.14
21.5.15
21.5.16
Determination of late
payments according to
defined payment cut-off
dates
21.5.17
21.5.18
21.5.19
21.5.20
21.6
Credits, Refunds, Rebates,
and Adjustments
21.6.1
21.6.2
21.6.3
21.6.4
Technical Requirements
21.6.5
21.6.6
Voiding of payments
21.6.7
Processing of authorized
credits, refunds, rebates,
overrides, and voids
21.6.8
Rejection of unauthorized
credits, refunds, rebates,
overrides, and voids
21.6.9
Application of adjustments
immediately or upon next bill
cycle processing
21.6.10
21.7
Collections, Dunning, and
Bad Debts
Vendor asserts its
solution supports:
21.7.1
Ability to categorize
outstanding receivables
according to standard and
Afghan Telecom-defined
aging rules (e.g., 30 days,
60 days, etc.)
21.7.2
21.7.3
Multi-step, multi-phase
dunning procedures and
actions
21.7.4
Ability to automatically
initiate dunning processes
according to Afghan
Telecom-defined
parameters
21.7.5
Generation of pre-defined
customer communication via
multiple media (e.g.,
reminders via letter, email,
and SMS)
21.7.6
Automatic triggering of
dunning-related actions
(e.g., blocking, suspending,
and barring)
21.7.7
219
Technical Requirements
21.7.8
21.7.9
21.7.10
21.7.11
21.8
Storage and Retrieval of
Payment Information
Vendor asserts its
solution supports:
21.8.1
21.8.2
21.9
Interface to Financial
Systems
Vendor asserts that its
solution supports:
21.9.1
21.9.2
21.9.3
21.9.4
21.9.5
Technical Requirements
21.9.6
22
22.1
FC/PC/NC+NP/P
OB/MOD
Comments
22.1.6
22.1.7
22.1.8
Distribution channels
22.1.9
22.1.10
22.1.11
22.1.12
22.1.13
22.1.14
22.1.15
Recharges
22.1.16
22.1.17
Exceptions
22.1.18
22.1.19
22.1.20
221
Technical Requirements
22.1.21
22.1.22
Reporting by element or
unit, groups of elements or
units, individually, and in the
aggregate
22.1.23
22.1.24
22.1.25
22.1.26
22.1.27
Standard reports
22.1.28
Customizable reports
22.1.29
Exception reports
22.1.30
22.1.31
22.1.32
22.1.33
22.1.34
22.1.35
22.1.36
22.1.37
22.1.38
22.1.39
22.1.40
22.1.41
222
Technical Requirements
22.1.45
22.1.46
22.1.47
22.1.48
22.1.42
22.1.43
22.1.44
Time to
Market
23
Please
indicate
your time
to market
(TTM) for
the
following:
Item
23.1
Modify
existing
tariff plans
and tariff
values
Description/Example
TTM
223
Technical Requirements
Establish a
new tariff
plan for
existing
product or
service
23.2
Establish a
tariff plan
for new
product or
service
23..3
23.4
Modify a
charging
rule
23.5
Add a new
charging
rule
23.6
23.7
Add a new
package or
bundle
Add new
discount
schema
23.8
Add new
accumulat
or
23.9
Add a new
account
type
224
Technical Requirements
23.10
23.11
23.12
23.13
Add a new
customer
attribute
Add a new
diameter
parameter
Modify
web
service
interface
Create a
new report
225
List OF Acronyms
List Of Acronyms
2G to 5G
3GPP
4G/LTE
A/P , A/R
ACH
BTN
CBRT
CDMA
CDRs/UDRs
CLIP
CLIR
CPE
CUG
DBD
DPLC
DSL
EBPP
EDGE
EMS
GPRS
GSM
HSDPA/HSPA/HSUP
IN
IP
IPLC
IPTV
IRU
ISDN
ISP
IVR
MBPS
MMS
NFC
OCG
PBX
PDSN
PNP
POS
List OF Acronyms
PRI
QoS
SIM
SMS
TDMA
UMS
USSD
UVC
VAS
VCN
VoIP
VPN/IP VPN
WAP
SGSN
NE
SDR
TAP
RAP
OLAP
DSL
GL
AP and AR
COS
CRM
CE
FCC
ATCA
SPOF
HA
IMDB
GDR
SS7
SST
SEPP
SET
SSL
PCT
TLS
HTTPS
LDAP
ADSI
RPC
CTI
EAI
APIs
GUI
NMS
EMS
CSV
DES
227
Bidding Forms
Date:
Loan/Credit No.:
RFP:
Contract:
Having examined the Bidding Documents, including Addenda Nos. [ insert numbers ], the
receipt of which is hereby acknowledged, we, the undersigned, offer to supply, install, achieve
Operational Acceptance of, and support the Information System under the above- named Contract
in full conformity with the said Bidding Documents for the sum of:
[ insert: amount of
228
Bidding Forms
plus
plus
plus
229
Bidding Forms
or such other sums as may be determined in accordance with the terms and conditions of the
Contract. The above amounts are in accordance with the Price Schedules attached herewith
and made part of this bid.
We undertake, if our bid is accepted, to commence work on the Information System and to
achieve Installation and Operational Acceptance within the respective times stated in the Bidding
Documents.
[ and delete the following paragraph, or, as appropriate, delete the above and
include the following, or, if no Adjudicator is stated in the Bid Data Sheet,
delete both the above and the following ]
We hereby certify that the Software offered in this bid and to be supplied under the
Contract (i) either is owned by us, or (ii) if not owned by us, is covered by a valid license from
the proprietor of the Software.
We agree to abide by this bid, which, in accordance with ITB, consists of this letter (Bid
Submission Form) and the enclosures listed below, for a period of [ Purchaser insert: number from
ITB ] days from the date fixed for submission of bids as stipulated in the Bidding Documents, and it
shall remain binding upon us and may be accepted by you at any time before the expiration of that
period.
Bidding Forms
Amount and
Currency
Purpose of
Commission or
Gratuity
231
Bidding Forms
Etc.
Until the formal final Contract is prepared and executed between us, this bid,
together with your written acceptance of the bid and your notification of award, shall
constitute a binding contract between us. We understand that you are not bound to accept the
lowest or any bid you may receive.
Dated this [ insert: ordinal ] day of [ insert: month ], [ insert: year ].
Signed:
Date:
Duly authorized to sign this bid for and on behalf of [ insert: name of Bidder ]
ENCLOSURES:
232
Bidding Forms
Position
Personnel
information
Name
Date of birth
Professional qualifications
Present
employment
Name of employer
Address of employer
Telephone
Fax
Job title
Summarize professional experience over the last 20 years, in reverse chronological order. Indicate
particular technical and managerial experience relevant to the project.
From
To
233
Bidding Forms
234
Bidding Forms
235
Bidding Forms
236
Bidding Forms
Bidders and each partner to a JVA should provide information on their current commitments on all contracts
that have been awarded, or for which a letter of intent or acceptance has been received, or for contracts
approaching completion, but for which an unqualified, full completion certificate has yet to be issued.
Name of contract
Employer,
contact
address/tel/fax
Value of
outstanding work
(current US$
equivalent)
Estimated
completion date
Average monthly
invoicing over
last six months
(US$/month)
1.
2.
3.
4.
5.
etc.
237
Bidding Forms
Financial Situation
Historical Financial Performance
Date: _____________________
Financial
information
in US$
equivalent
Year 1
Year 2
Year 3
Year
Year n
Avg.
Avg.
Ratio
Bidding Forms
Profits Before
Taxes (PBT)
Attached are copies of financial statements (balance sheets, including all related notes, and
income statements) for the years required above complying with the following conditions:
(a) Must reflect the financial situation of the Bidder or partner to a JVA, and not sister or
parent companies
(b) Historic financial statements must be audited by a certified accountant
(c) Historic financial statements must be complete, including all notes to the financial
statements
(d) Historic financial statements must correspond to accounting periods already completed
and audited (no statements for partial periods shall be requested or accepted)
239
Bidding Forms
Date: _____________________
Year
*Average
Annual
Construction
Turnover
_________________________________________ ____________________
*Average annual turnover calculated as total certified payments received for work in progress or
completed, divided by the number of years specified in Section III, Evaluation Criteria, Sub-Factor 2.3.2.
240
Bidding Forms
Financial Resources
Specify proposed sources of financing, such as liquid assets, unencumbered real assets, lines of credit, and
other financial means, net of current commitments, available to meet the total construction cash flow
demands of the subject contract or contracts as indicated in Section III, Evaluation and Qualification Criteria
Source of financing
1.
2.
3.
4.
241
Bidding Forms
Date: _____________________
Starting
Month /
Year
Ending
Month /
Year
Contract Identification
Years*
Role of
Bidder
Contract name:
______
______
_________
Name of Employer:
Address:
Contract name:
______
______
_________
Name of Employer:
Address:
Contract name:
______
______
_________
Name of Employer:
Address:
242
Bidding Forms
Starting
Month /
Year
Ending
Month /
Year
Contract Identification
Years*
Role of
Bidder
Contract name:
______
______
_________
Name of Employer:
Address:
Contract name:
______
______
_________
Name of Employer:
Address:
Contract name:
______
______
_________
Name of Employer:
Address:
*List calendar year for years with contracts with at least nine (9) months activity per year starting with
the earliest year
243
Bidding Forms
Specific Experience
Bidders Legal Name: ___________________________
Date: _____________________
Information
Contract Identification
_______________________________________
Award date
Completion date
_______________________________________
_______________________________________
Role in Contract
Contractor
Management
Contractor
Subcontractor
__________________________ US$_______
__
___
US$_______
Employers Name:
_______________________________________
Address:
_______________________________________
_______________________________________
_______________________________________
_______________________________________
Telephone/fax number:
E-mail:
244
Bidding Forms
has withdrawn its Bid during the period of bid validity specified by the
Bidder in the Form of Bid; or
(b)
having been notified of the acceptance of its Bid by the Employer during the
period of bid validity, (i) fails or refuses to execute the Contract Form, if
required, or (ii) fails or refuses to furnish the performance security, in
accordance with the ITB.
This guarantee will expire: (a) if the Bidder is the successful Bidder, upon our receipt of copies
of the contract signed by the Bidder and the performance security issued to you upon the
instruction of the Bidder; and (b) if the Bidder is not the successful Bidder, upon the earlier of (i)
our receipt of a copy your notification to the Bidder of the name of the successful Bidder; or (ii)
twenty-eight days after the expiration of the Bidders bid.
Consequently, any demand for payment under this guarantee must be received by us at the office
on or before that date.
This guarantee is subject to the Uniform Rules for Demand Guarantees, ICC Publication No.
458.
_____________________________
[signature(s)]
245
Bidding Forms
Manufacturers Authorization
[To be given for the Equipment, and its associated Power Supply Equipment, where the Bidder is not
the Manufacturer of these items]
Date: __________________
To: ________________________
WHEREAS
We hereby extend our full guarantee and warranty in accordance with Conditions, with respect to the
goods offered by the above firm.
Signed: _______________________________________
Name: ______________________________________
Title:______________________________________
246
Bidding Forms
247
Annextures
Phases:
Phase 1: Commercially operational system to support GSM& 3G network within 6 month after
the contract effective date (CED).
Phase 2: Commercially operational system to support PSTN, Wimax, VSat within 3 months after
phase 1.
248
Annextures
AFTEL will make the following payment terms to the winner/contractor in stages;
1. 30% of the total contract value upon arrival of goods at AFTEL warehouse.
2. 20% of the total contract value after installation of Hardware.
3. 20% of the total contract value after PAC.
4. 30% of the total contract value after FAC.
249
Annextures
SL.No
1
clause Number
10.2.16
(technical
requirements)
Original Statement
Revised Statement
CDR normalization
17.7
(ITB Section)
8.4.8
2
17.6.8
(technical
requirements)
3
250
Annextures
S.No
1.1
1.1.1
1.1.2
1.2
1.2.1
1.2.2
1.3
1.3.1
1.3.2
1.4
1.4.1
1.4.2
1.5
1.5.1
1.5.2
2
2.1
2.2
3
3.1
4
4.1
5
5.1
6
Country
Of
Origin
Unit
Cost
DDP
6.1
Expert
6.2
Intermediate
6.3
7
Beginner
7.1
QTY
8 persons
for 45 days
11 persons
for 20 days
40 persons
on Job
Project
Total
Price
DDP
Annextures
All Modules(Provisioning, CRM, PRM, Mediation, CBS) in solution. So that we can exclude anyone or
many of these if required
S.No
Country Of
Origin
Unit Cost
DDP
Total Price
DDP
252
Annextures
Clause :No
Statement
12.2.6
operator Services
16.1.26
17.1.49
17.8.2
5
20.6.22
Braille bills
13.2.3(ITB)
9.2.11
9.2.12
9.2.13
9.2.14
10
11
2.1.11
2.1.12
253
Annextures
2.1.13
2.1.14
Annexture 6. the clauses which has been added to RFP Technical Requirement
2.1.19.2
2.1.19.3
254
Annextures
2.1.19.6
2.1.19.7
Business Requirements
have an efficient, state of the art IT infrastructure that can roll
out these services quickly and efficiently to X customers
Technical Requirements
The provisioning system in vendors solution should be able to
support various telecom networks such as GSM, PSTN,
Broadband, IPTV, 3G (, UMTS), WiMAX, VSAT, etc.
2.1.19.8
2.1.19.9 Provisioning Requirements
2.1.19.10 General
2.1.19.11
2.1.19.12
2.1.19.13
System should be able to archive data, present reports and
2.1.19.14 statistics.
Web GUI is supported for performing system and user
administration.
2.1.19.15
The solution must be network vendor independent.
2.1.19.16
2.1.19.17 Interface
2.1.19.18
255
Annextures
2.1.19.28
2.1.19.29
2.1.19.31
256
Annextures
The provisioning flow is not affected when either one of the link
to Network Element is down. Execution of task can be made
independent on each channel to NE in the flow. Hence avoiding
X request in the system when one of the NE is down during the
process of execution.
2.1.19.34
The system can provide a clear view and status of all its
2.1.19.35 connectivity towards the NE.
2.1.19.36
2.1.19.37
2.1.19.38
2.1.19.40
2.1.19.41
2.1.19.42
2.1.19.43
2.1.19.44
Annextures
General Requirements
24
24.1
24.2
Marketing Management
System should cover the end-to-end management of campaigns
from the, planning, design, selection and creation of a campaign
to execution and to reporting.
System should provide and easy to user interface to enable
marketers to control the entire campaign cycle.
System should be able to apply offers directly to customer
accounts and launch the campaigns - all without any need for
manual intervention, with the minimal time and minimal system
interventions.
24.3
24.4
24.5
24.6
24.7
24.8
24.9
24.1
24.11
258
Annextures
24.12
24.13
24.14
24.15
24.16
24.17
24.18
24.19
24.20
24.21
24.22
24.23
24.24
24.26
24.27
24.28
24.29
24.30
24.31
24.32
24.33
259
Annextures
24.29
24.30
Name of Summary
Marketing & Sales KPI
Outcome of monitoring, that should give out the factors causing
service enhancement or degradation.
Evaluation comment (The result is accurate or to-be-improved)
The level of necessity to improve (High, medium, low)
24.31
24.32
24.33
24.34
24.37
25
Sales Management
24.35
24.36
25.1
25.2
25.3
260
Annextures
25.4
25.5
The system should be able to Support the legal user adding and
maintenance business opportunity data. Store business
opportunity for corresponding customer, business opportunity
decision-maker, business opportunity content, potential
competitor, success probability, status and so on.
25.6
The system should be able to Support single and batch or
grouping methods for distributing the business opportunities to
team or sales personnel.
25.7
The system should be able to Support the business opportunity
automatically distributing rule be configured, according to
customer, team work plan, and sales areas. According to the
rule, the business opportunity can be distributed automatically
by the system.
25.8
The system should be able to Support business opportunity
upgrade processing, for example, when the sales personnel find
him cannot satisfy the customer requirements in his privilege,
but the customer is important; he can transfer the business
opportunity to the high level sales personnel.
25.9
The system should be able to Support business opportunity
period of validity process, for the out-of-date and no progress
business opportunity, it can be closed according to the rule.
25.10
25.11
25.12
261
Annextures
25.13
25.14
25.15
25.16
25.17
25.18
26
Inventory management
26.1
26.2
26.3
26.4
26.5
26.6
26.7
262
Annextures
27.1
27.2
27.3
27.4
27.5
27.6
27.7
27.8
27.9
27.10
27.11
27.12
Main Storage
28
263
Annextures
264