Achiziție - Platforma de Management a Pieței de energie cu servicii de implementare

Avand in vedere costul de deservire al platformei pe 3 ani, va rugam sa clarificati:

1. Ce activitati sunt incluse in perioada de deservire gratuita de 1 an.
2. Ce nivel de suport este asteptat in aceasta perioada (SLA).
3. Daca activitatile de suport si mentenanta pot influenta receptia finala a platformei.

... afișează tot conținutul

Could the deadline for the proposal be postponed to 13.2.? This will allow more precise proposal based on the specification available from Moldelectrica.

... afișează tot conținutul

Is it required that system is installed on-premise? Or is it also possible to provide Software as a service? Is it possible that the solution is deployed to cloud environment (such as MS Azure) due to security reasons, as cloud might offer more secure environment?

... afișează tot conținutul

If we decide to submit the proposal on behalf of Consortium of 2 companies, is it OK if the registration on the portal is done for one of them, and in the proposal it is clearly stated this is submitted by a consortium?

Is it possible that some of the Mandatory requirements (such as Revenue per 3 years of the bidder, References, etc) is fulfilled by a third party, which capacity does bidder rely on? In such case, is it OK if the bidder states that it relies on the capacity of third party and submits the bid under its own bidder account?

... afișează tot conținutul

One of the evaluation criteria is "open-source SW". How do you define open source software? Does Moldelectrica plan to re-sell the software procured (which would fulfill the general definition of open-source SW?) Or is the goal to receive the source codes for the customisations of standard product prepared for Moldelectrica? In case we can hand over such source codes - does it fulfill your understanding of open source? Can you elaborate this topic?

... afișează tot conținutul

Would you be able to define contract for the delivery and maintenance and support? It may influence the delivery or the pricing. Especially the definition of SLAs, penalties, liabilities etc.

... afișează tot conținutul

The specification refers to different sets of environments to be provided and supported by the Contractor.
- In Section 0.3 Contractor, it is stated that Production, Test, and Disaster Recovery sites are encompassed by this procurement.
- In Section 2.1 System-level requirements, it is stated that, in addition to the Production System, a Development and Testing System replicating the Production System with its own infrastructure shall be provided.

Moreover, The documentation specifies an expectation of two sites for the environments (Production), namely a Main site and a Disaster Recovery (DR) site. As part of our proposed technical solution, we would like to consider an alternative architecture based on an Active–Active deployment across three geographically separated locations, consisting of two primary nodes and an additional arbiter node.
Could you please confirm whether such an architecture would be acceptable within the scope of the tender requirements, provided that it fully satisfies (or exceeds) the stated availability, resilience, and disaster recovery objectives ? Are there any possibility to deploy application into 3 geographically separated locations for higher availability of future MMS system ? ​

Related to this, Could you please also confirm whether it is permissible to host the DEV environment at the contractor’s premises or within the contractor’s infrastructure, rather than at the premises of the contracting authority, provided that all security, confidentiality, access control, and compliance requirements specified in the tender documentation are fully met? ​

Could you please confirm the complete and definitive list of environments to be provided under the contract (e.g. Production, Test, Disaster Recovery, etc.)? This clarification is important for proper sizing and cost estimation of the MMS solution.

... afișează tot conținutul

Could you please clarify whether the MMS solution is expected:
- only to generate billing data and export it to external financial systems, or
- to generate the actual invoices (including invoice documents) within the MMS?

... afișează tot conținutul

From the specification, it appears that the requirements include multiple processes that are not yet applicable to the Moldovan energy market, such as integration with JAO, MARI, and PICASSO platforms, as well as the application of flow-based methodology.
Given that:
a) such mechanisms are still evolving at the European level,
b) Moldova currently does not have access to these platforms, and
c) meaningful testing would not be possible during the 12-month MMS implementation period,
we believe that implementing, configuring, and testing these processes at this stage may not be an efficient use of budget and effort, and would likely require additional changes once Moldova is actually ready to join these platforms.
Would you consider reshaping these requirements so that the MMS solution is architecturally ready to support such integrations in the future, without requiring their full implementation and testing within the current project scope?

... afișează tot conținutul

The specification states that data should be presented in different time zones. However, several core processes - particularly scheduling and settlement - are based on daily or monthly periods.
Could you please clarify which time zone Moldelectrica intends to use to define the boundaries of a “day” and a “month” within the MMS? If different time zones are to be applied for different processes, we would appreciate it if you could specify the relevant processes and the corresponding time zones for each.
This clarification will help ensure consistent implementation and avoid ambiguities in period-based calculations.

... afișează tot conținutul

Could you please clarify whether the market schedules resulting from the Day-Ahead and Intraday markets will be provided to the MMS:
- exclusively by the Market Operator, or
- by both the Market Operator and market participants, with subsequent matching performed within the MMS?

... afișează tot conținutul

Active Directory / LDAP Provisioning Scope
The documentation states that an Active Directory (AD) central server using LDAP shall be hosted by the MMS for user authentication. Could you please clarify whether this requirement implies that the Contractor is expected to deliver and operate a dedicated AD/LDAP service as part of the solution, or whether integration with an existing directory service provided by the contracting authority would be acceptable, provided that all functional and security requirements are fully met ? ​

Authentication Mechanisms, SSO, and Second Factor
The documentation refers to SSO authentication, LDAP / AD secure authentication, and mandatory two-factor authentication (2FA). Given that the target system is web-based, could you please clarify whether the use of modern, web-oriented authentication mechanisms (e.g. federation or token-based SSO solutions backed by AD) is acceptable in place of, or in combination with, direct LDAP-based authentication, while still maintaining AD as the authoritative identity source ? ​

... afișează tot conținutul

The tender documentation specifies the delivery of on-premises hardware infrastructure, including servers, storage, network equipment, and associated warranties. In this context, could you please clarify the following:

Hardware Installation
Is the Contractor expected to perform the physical installation of the hardware (rack mounting, cabling, initial power-up) on the contracting authority’s premises, or will these activities be performed by the contracting authority with the Contractor providing guidance and supervision as required ? ​

Hardware Maintenance During Warranty Period
During the warranty and maintenance period, could you please clarify whether the Contractor is expected to provide on-site hardware maintenance and replacement activities, or whether such activities will be handled by the contracting authority (or a designated third party), with coordination from the Contractor ? ​

Physical Access to On-Premises Infrastructure
Given that the solution is on-premises and subject to physical security controls, could you please clarify the expected level of physical access for Contractor personnel to the hardware infrastructure (e.g. escorted access, pre-approved access lists, security clearance procedures) for installation, maintenance, and warranty-related activities ? ​

Responsibility Matrix for Delivered Infrastructure
Could you please clarify the expected responsibility matrix for the delivered infrastructure, in particular the allocation of responsibilities between the Contractor and the contracting authority for hardware operation, monitoring, incident handling, routine maintenance, and lifecycle management during the warranty and support period ? ​

... afișează tot conținutul

The tender documentation specifies the number of workstations and monitor configurations; however, requirements for the remaining workstation components are not explicitly defined. In order to ensure full compliance, could you please clarify the expected scope and specifications for the workstations beyond the monitors, including but not limited to computing hardware characteristics (e.g. CPU, memory, storage), graphics capabilities to support multi-monitor configurations, operating system requirements, preinstalled software, and any security or hardening standards to be applied ? ​

Additionally, please clarify whether the workstations are expected to be based on standard enterprise-grade hardware and operating systems, and whether approval or alignment with the contracting authority’s existing workstation standards is required.

... afișează tot conținutul