Servicii de implementare a soluțiilor informatice de operaţiuni bancare și de gestionare a resurselor corporative (licențe, servicii de implementare și servicii de garanție) - REPETAT
suma planificată 79,998,333.33 MDL
| Lot | Valoare | CPV | Titlu achiziției | Cantitate | Livrare |
|---|---|---|---|---|---|
| Servicii de implementare a soluției informatice de operațiuni bancare (licențe, servicii de implementare și servicii de garanție) | 57,079,166.67 MDL | 72200000-7 | Licenţe aferente soluției informatice de operaţiuni bancare (CBS), cu 1 an de suport de la producător inclus | 1 Bucata |
17.06.2026 - 31.12.2026 bd. Grigore Vieru, 1 |
| 72200000-7 | Licenţe complementare pentru rularea CBS (cu excepţia licenţelor pentru sistemele de operare), cu 1 an de suport standard de la producător inclus | 1 Bucata | |||
| 72200000-7 | Servicii de implementare ale soluției informatice de operațiuni bancare (CBS) | 1 Bucata | |||
| 72200000-7 | Servicii de instruire aferente soluției informatice de operațiuni bancare (CBS) | 1 Bucata | |||
| 72200000-7 | Servicii de integrare** | 1 Bucata | |||
| 72200000-7 | Servicii privind dezvoltări suplimentare și solicitări de schimbare | 2000 Bucata | |||
| 72200000-7 | Servicii de garanţie (mentenanţă şi suport) aferente soluției informatice de operațiuni bancare (CBS) | 12 Bucata | |||
| Servicii de implementare a soluției informatice de gestionare a resurselor corporative (licențe, servicii de implementare și servicii de garanție) | 22,919,166.66 MDL | 72200000-7 | Licenţe aferente soluției informatice de gestionare a resurselor corporative (ERP), cu 1 an de suport de la producător inclus | 1 Bucata |
17.06.2026 - 31.12.2026 bd. Grigore Vieru, 1 |
| 72200000-7 | Licenţe complementare pentru rularea ERP (cu excepţia licenţelor pentru sistemele de operare), cu 1 an de suport standard de la producător inclus | 1 Bucata | |||
| 72200000-7 | Servicii de implementare ale soluției informatice de gestionare a resurselor corporative (ERP) | 1 Bucata | |||
| 72200000-7 | Servicii de instruire aferente soluției informatice de gestionare a resurselor corporative (ERP) | 1 Bucata | |||
| 72200000-7 | Servicii de integrare** | 1 Bucata | |||
| 72200000-7 | Servicii de garanţie (mentenanţă şi suport), aferente soluției informatice de gestionare a resurselor corporative (ERP) | 12 Bucata | |||
| 72200000-7 | Servicii privind dezvoltări suplimentare și solicitări de schimbare | 1000 Bucata |
Could you please clarify the requirement regarding Tender Security for bids covering multiple lots? Specifically, for a vendor submitting bids for both LOT-1 and LOT-2, should the Bid Security be submitted separately for each lot (i.e., 1% of the value of each respective lot, excluding VAT), or is it acceptable to submit a single consolidated Bid Security equivalent to 1% of the combined total value of both lots (excluding VAT)? We would appreciate your guidance to ensure full compliance with the tender requirements.
Dear economic operator, if a tenderer submits bids for both Lot I and Lot II, they may choose the format in which the Tender Security is provided.
Specifically, the Economic Operator has the right to either:
• submit a single consolidated Tender Security covering both lots, in an amount at least to 1% of the total combined bid value (excluding VAT), or
• submit separate Tender Securities for each lot, each amounting at least to 1% of the respective lot’s bid value (excluding VAT).
Both options are acceptable and will be considered compliant with the tender requirements.
At the same time, Economic Operators should consider that, if they submit bids for both lots, they are required to upload in the MTender system the full set of mandatory documents (at least the six required documents of the bid) separately for each lot.
In the RFP documentation, you stated you would only accept offers which include perpetual licensing. Can you please explain in details what do you consider as perpetual licensing? If we can offer license prices fixed for the term of the following 3 years, is it acceptable to the bank?
According to the requirement set out in „The Specifications”, CL.15 “The licenses related to the proposed solution must be perpetual. The Tenderer undertakes to provide all licensing conditions and usage restrictions applicable under various circumstances.”
In the understanding of the Contracting Authority, perpetual licenses are those that grant an indefinite, non-expiring right of use. After their acquisition, the user is not required to renew the license itself, but only to pay annual maintenance fees in accordance with the terms specified in the TCO (Annex 4 to „The Specifications”).
Therefore, an offer based on licenses with a fixed price limited to a period of 3 years would not be considered compliant with the requirement for perpetual licensing.
Also, in the context of licensing aspects, it is to be mentioned that regarding complementary licenses, load balancers are excluded from the scope of these licenses.
Can you please specify in details which local requirements (reports, etc.) need to be fulfilled by the ERP system?
The specific localization requirements will be further identified by the Contracting Authority together with the Bidder (Vendor) during the analysis and design phase, based on national regulatory and operational needs. NBM accounting is IFRS and Law 287/2017 based.
As examples of documents may be: Payment Order format, Accounting Note format, Invoice format (main identifications of supporting data), the format of Accounting registers, Account statement, statistical reports (including coding of operations), tax reports (VAT report – type of operations).
All data (nomenclator and formats) will be provided by NBM during the analysis and design phase.
Could you please clarify the requirement regarding Tender Security for bids covering multiple lots? Specifically, for a vendor submitting bids for both LOT-1 and LOT-2, should the Bid Security be submitted separately for each lot (i.e., 1% of the value of each respective lot, excluding VAT), or is it acceptable to submit a single consolidated Bid Security equivalent to 1% of the combined total value of both lots (excluding VAT)? We would appreciate your guidance to ensure full compliance with the tender requirements.
Dear economic operator, if a tenderer submits bids for both Lot I and Lot II, they may choose the format in which the Tender Security is provided.
Specifically, the Economic Operator has the right to either:
• submit a single consolidated Tender Security covering both lots, in an amount at least to 1% of the total combined bid value (excluding VAT), or
• submit separate Tender Securities for each lot, each amounting at least to 1% of the respective lot’s bid value (excluding VAT).
Both options are acceptable and will be considered compliant with the tender requirements.
At the same time, Economic Operators should consider that, if they submit bids for both lots, they are required to upload in the MTender system the full set of mandatory documents (at least the six required documents of the bid) separately for each lot.
CF.90c.: Please describe the difference between securities accepted as collateral and securities pledged in favour of NBM. Please explain the difference through business cases for better understanding.
Securities accepted as collateral are securities that the NBM has approved as eligible to be used as collateral in its operations.
Securities pledged in favor of NBM are securities that have been formally pledged (legally encumbered) to the NBM as security for a specific credit or liquidity operation (e.g. overnight credit).
CF.123.: We would like to ask for a use case for using the scheme for automatic termination of deposits, what kind of conditions should be included in the scheme?
In the event that deposits placed for the purpose of efficient cash management are repaid prior to maturity, the National Bank shall recalculate the amount of interest accrued and paid for the period during which the deposit was maintained and shall deduct the resulting difference from the deposit amount to be returned. The recalculation of interest for the above-mentioned deposits repaid prior to maturity shall be carried out by applying an interest rate determined based on the weighted average interest rate in the banking system on demand deposits attracted from legal entities bearing interest in Moldovan lei, available for the last three months preceding each month of maintenance.
For deposits placed for the purpose of forming the liquidity reserve and repaid prior to maturity, the initial interest rate on the respective deposit shall not be changed and the interest paid shall not be recalculated.
CF.135.: Is our understanding correct, that regarding financial guarantees:
o dedicated workflows for handling the whole process of the guarantee are required related to securities as collaterals,
o registration of guarantees is sufficient for all other types of guarantees?
Dedicated workflows for handling the whole process of the guarantee are required.
The National Bank may accept as collateral the following categories of eligible assets:
1) state securities issued by the Government of the Republic of Moldova;
2) certificates of the National Bank of Moldova;
3) deposits and other accounts with the National Bank, including required reserves in foreign currency maintained in unchanged volume or deposits and other accounts with a bank accepted by the National Bank, representing any kind of assets that the National Bank may purchase, sell and negotiate;
4) pecuniary claims, with the exception of claims of the related parties of the bank;
5) corporate securities admitted to trading on the regulated market and/or within a multilateral trading facility (MTF);
6) other financial assets laid down by the National Bank by the decision of the Executive Board.
CF.145.: Please provide a more detailed use case for your expectations.
The approved credit may be disbursed in several tranches (for example, a credit approved in the amount of MDL 10 million may be disbursed in two equal tranches of MDL 5 million each).
CF.163e.: Please list the Futures products used in present bank operations.
At the moment, the National Bank of Moldova doesn’t use any futures products in its present operations just because of the limitations of the actual core system. Nonetheless, the CBS should mandatory offer the possibility of using and maintaining such products.
CF.165.: Please give us more information on the trading orders mentioned in the requirement, the CBS should import from Bloomberg. What is meant under this transaction type and which parameters/data should be imported?
A trading order refers to a transaction (trade/deal/ticket). These can be of different types, for example: Forex (SWAP, SPOT, FORWARD), term deposits, or buying/selling securities. The main data from the completed transaction (ticket) is loaded from Bloomberg platform into CBS. As about the specific data imported from Bloomberg we can mention the following fields: ticket number, value date, type of operation, currency code, transaction amount, rate, yield, transaction maturity date, dealer’s name, counterparty name, and any other relevant information. The exact data required to be imported from Bloomberg for each type of operation will be discussed in more detail during the analysis and design stage.
CF.169.: Please elaborate your expectations regarding the maintenance of externally managed portfolios. What kind of portfolios are they? What is the expected process the CBS should cover?
For externally managed portfolios CBS should cover the exact same functionality as for the internally managed portfolios with some additional possibilities like backdating and manual registration of the trades reported to the National Bank of Moldova by its external portfolio manager.
Under Moldovan law, does the association require any official registration, or is an association agreement signed by the members sufficient? If the bid is successful, do all members of the association sign the public procurement contract individually, or only the leader?
1. According to the art.16 (2), from Law on Public Procurement of the Republic of Moldova No. 131/2015, the association is obliged to obtain a certain legal form of organization if this registration is necessary for the proper execution of the contract and only after its award. Thus, at the moment of tender submission it is not mandatory to have an official registration of the association. At the same time, all requirements from tender documents related to the association must be fulfilled.
2. Yes, if the bid is successful, all members of the association will sign the public procurement contract individually, according the provisions form point 19, Annex no.8 to the Participation Notice „Requirements Form”.
Are the members of the association jointly and severally liable to BNM?
Are the bank guarantees required only from the leader of the association for the whole bid value (in case the association is bidding for both LOT I. & LOT II.), or each member of the association should provide their guarantees with respect to the value of the relevant LOT?
1. Yes, the members of the association are jointly and severally liable to NBM as is stated in Participation Notice at the point 19 from Annex no.8 „Requirements Form”.
2. According to the Participation Notice, specifically the provision in the table at point 16 (page 6), “Note: The tender guarantee submitted by the Association must be in the name of the Association submitting the tender.”
At the same time, it should be considered that the Economic Operator has the right to either:
- submit a single consolidated Tender Guarantee covering both lots, in an amount at least to 1% of the total combined bid value (excluding VAT), or
- submit separate Tender Guarantees for each lot, each amounting at least to 1% of the respective lot’s bid value (excluding VAT).
Both options are acceptable and will be considered compliant with the tender requirements.
Also, Economic Operators should consider that, if they submit bids for both lots, they are required to upload in the MTender system the full set of mandatory documents (at least the six required documents of the bid) separately for each lot.
It is to be mentioned, also, that in case of a single consolidated Tender Guarantee, the Economic Operator must consider a possible different timeline for contract award and respectively guarantee return, as this guarantee will cover both lots.
Based on our understanding, Part I. is fixed and its content is driven by the Moldavian law. However, in case of complex procedures, there is a possibility to add customization in Part II.
We would like to add some comments with questions and changes in the current contract model. Shall we submit this version together with the SLA, Maintenance & Support, Licencing and Warranty templates or what is the way of communication in terms of the contract model?
Is there any chance to modify the payment schedule outlined in Part I.?
Regarding this question, it is to be mentioned that both parts of the contract: Part I. - the general and standard one and the Part II. - special part of the contract are mandatory for the Tenderers and are not subject to changes, including the payment schedule outlined in Part I. By submitting the tender, the Tenderer confirms agreement with the model contract annexed to the specifications.
Thus, the contract model is considered a fixed document and its core clauses, which represent minimum requirements derived from procurement law, cannot be modified. However, additional clauses or agreements may be proposed, if they do not contradict the existing provisions.
There is no requirement to submit review comments or proposed changes to the contract model. Instead, bidders may build on top of the contract by adding complementary elements, while respecting the mandatory baseline conditions. Also, the bidder submits, together with the Contract, additional supporting documents such as the Service Level Agreement (SLA), maintenance and support agreement, licensing agreement, and product warranty templates, these documents being considered annexes to the contract.
As we understad, NBM is responsible for provisioning all the infrastructures. Given the conservative budget, inclusion of DBMS (Oracle), Application Server and Load Balancer will be extremely challenging to many vendors. Also, the requirement has "etc." and we are not sure what else are included. Besides, the load balancer is a specific infrastructure requirement and inclusion of this alone here is not in alignment with the industry practices.
The requirement regarding complementary licenses is intended to ensure the proper functioning and operability of the proposed solution as a complete and usable system.
By complementary licenses, we refer to all necessary software components above the operating system level that are required for the solution to function as designed (e.g., DBMS, application server, or other software dependencies specific to the solution architecture). These do not include infrastructure components, for which the National Bank of Moldova (NBM) remains responsible.
The examples provided in the requirement (including DBMS, application server, load balancers, etc.) are indicative and aim to cover scenarios where certain solutions rely on embedded or tightly integrated software components. In particular, the mention of load balancers reflects cases where such functionality is delivered as part of the application stack itself.
However, where such components (e.g., load balancing capabilities) are not part of the proposed solution as licensed software, they may be provisioned at the infrastructure level by NBM and therefore are not mandatory to be included as complementary licenses.
Request NBM to accept global banks references for Lot II
With reference to the request to accept global bank references for Lot II, please note that, in accordance with the applicable legal framework governing public procurement in the Republic of Moldova, at this stage of the procedure — while the procurement process is ongoing — the Contracting Authority is not permitted to intervene in the tender documentation in a manner that would result in the modification of the established qualification requirements.
Therefore, the qualification criteria as set out in the tender documentation remain unchanged and applicable as published.
As per the RFP documents received Annex no. 7 is List of processes with associated objectives and KPIs. Request bank to provide the Qualifications Requirements Form if it has been missed.
Please note that the reference to Annex no. 7 in the RFP documentation should be understood as a reference to Annex no. 8 from the Participation Notice. Kindly consider Annex no. 8 as the Qualification Requirements Form.
Generally, these are part of the typical infrastrastructure requirements which includes network, server, backup, enterprise level monitoring and observability tool etc. We request NBM to exclude this from the RFP scope as the given budget is already very aggressive for the wider functional coverage.
The referenced requirements (CNF.104, CNF.105, CNF.106, CNF.107, CNF.115) target application-level capabilities necessary to ensure proper functioning, maintainability, and supportability of the solution.
As the solution is required to be turn-key, it must include all necessary mechanisms to support monitoring, diagnostics, alerting, and maintenance at the application level.
These requirements refer strictly to capabilities of the solution, not to the provision of enterprise infrastructure tools. NBM acknowledges that enterprise-level monitoring, observability, and infrastructure management tools (e.g., network, server, backup, centralized monitoring platforms) are part of the underlying infrastructure and remain the responsibility of NBM.
Therefore, vendors may fulfill these requirements either through native functionalities of the solution or by integrating with standard infrastructure monitoring and observability tools available within NBM.
Generally, these are part of the typical infrastrastructure requirements which includes network, server, backup, enterprise level monitoring and observability tool etc. We request NBM to exclude this from the RFP scope as the given budget is already very aggressive for the wider functional coverage.
Requirement CNF.190 is intended to address application-level backup and restore capabilities, which are essential for ensuring data integrity, operational continuity, and recoverability of the solution.
Given that the requested solution is a turn-key solution, it is expected to provide all necessary mechanisms to manage backups at the application level.
These requirements do not imply the need to provide or replicate enterprise backup infrastructure, which remains under NBM’s responsibility.
It is at the vendor’s discretion to integrate the application-level backup mechanisms with NBM’s existing backup infrastructure or provide native application-level tools that facilitate backup and restore processes, compatible with standard infrastructure practices.
Request the bank to clarify whether these documents are required to be submitted at a later stage on request by the bank.
Please note that tenderers are required to submit their offers exclusively through the MTender platform.
It is recommended that all the requested documents to be uploaded at the time of submission together with the mandatory documents. At the same time, please be informed that each Tenderer is obliged to include in its offer, submitted before the deadline, the following six mandatory documents, duly signed in accordance with the requirements of the tender documentation:
1. Technical Specification (Annex 1 to The Specifications)
2. Price Specification (Annex 2 to The Specifications)
3. ESPD (in case of a consortium, a separate ESPD shall be submitted for each member)
4. Bid Security (minimum 1% of the total tender value, excluding VAT, provided either as a bank guarantee letter or via SWIFT transfer)
5. Detailed Financial Tender for Implementation Services (Annex 3 to The Specifications)
6. Total Cost of Ownership (Annex 4 to The Specifications)
Please note that, according to the Participation Notice, point 39.3, provision from the second paragraph „Due to the public nature of the procurement procedure, forms (Technical Specifications, Price Specifications, the ESPD form, and the tender guarantee (where applicable)) will necessarily maintain their public character and cannot be classified as trade secrets or confidential information. Any non-compliance with the above provisions will result in the disqualification of the tender.” The other two documents, namely the Detailed Financial Tender for Implementation Services (Annex 3 to the Specifications) and the Total Cost of Ownership (Annex 4 to the Specifications), only if they contain confidential information and/or are considered commercial secrets, shall be uploaded to the MTender platform in password-protected format. The access password will be communicated to the Contracting Authority after the tender submission deadline, via a separate email sent to achizitii.contracte@bnm.md.
All other supporting documents mentioned in RFP will be submitted after the deadline for tender submission, upon request, directly to the Contracting Authority via email (To: achizitii.contracte@bnm.md and in Cc: transform_bnm@bnm.md).