Servicii de implementare a soluției informatice de gestionare a resurselor corporative (licențe, servicii de implementare și servicii de garanție)

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.

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.

1. The Human Resources management module is out of scope of this project. For Lot II (ERP) and CBS it is expected that the proposed solution has interfaces to import from the HR system only the necessary employee/user-related metadata required to support system functionality and integrations. A full HR module (including functionalities such as leave management, time tracking, or comprehensive employee lifecycle management) is not required. 2. It is intended that the ERP system will fully replace the current Budget application. 3. A dedicated software solution (out of scope) is planned for canteen management, with simplified integration into the ERP system. The management of rest house and transport services is expected to be handled within the ERP system, to the extent supported by its native functionalities in a simplify manner (described in the RFP). NBM has a limit number of transport units (up to 15). 4. The procurement process will continue to be conducted through the M-Tender platform in accordance with public procurement regulations. Within the ERP system, it is planned to support the preparation and monitoring of the procurement plan, ensuring its alignment with the approved budget and tracking its execution. 5. Public procurement is carried out based on the approved budget, and therefore the system should support appropriate budget control and commitment mechanisms. The administrative operating expenditure budget is prepared and executed on an accrual basis, and the ERP should support commitment accounting for this category. At the same time, the administrative investment budget for long-term assets is executed on a cash basis, and the ERP should be able to accommodate this approach accordingly. 6. All budget categories should ideally be: - Managed within a unified ERP structure, - Differentiated using analytical dimensions, - With distinct workflows and access controls applied as needed. This approach ensures flexibility and scalability while avoiding system fragmentation. 7. Yes, NBM applies IFRS 16 Leases, and the solution should support full lease accounting in respect of the provisions of IFRS 16, including the right-of-use asset recognition, lease liability and interest amortization, as well as subsequent modifications to lease contracts. However, the NBM has few number of ongoing lease contracts. 8. Yes, shared overhead costs are intended to be allocated across organizational units. There is currently no finalized cost accounting process in place. The approach will depend on the capabilities of the selected system, provided that it supports managerial cost reporting and allocation of shared costs. Allocation keys and related rules will be defined during the design and configuration phase. The solution should allow NBM administrators to configure and adjust allocation rules without vendor intervention, using the standard functionalities of the selected module. 9. The approximate number of cost centers and profit centers is currently under determination. This information will be defined and confirmed during the analysis and design phase of the project. At present, NBM consists of 26 subdivisions, structured across multiple organizational units, with over 30 operational processes.