Call for tenders' details

Tenderers are requested to note that the closing date for submission of tenders has been extended to 26/05/2020 at 12:00 and the opening of tenders will now take place on 27/05/2020 at 14:00.
The Provision of IT Software Development, Configuration, Implementation and Main...
Contracting authority:
European Medicines Agency (EMA)
TED publication date:
Time limit for receipt of tenders:
English (en)
Question details
Lot 1 - Award Criteria - Criterion 5 - MDM new API
Based on your requirements and supposing that the on-prem MDM system will stay the master of data, different types of solutions can be built using an API Gateway. But we need more clarifications: 1. Should the API Gateway redirect API calls to the on-prem APIs and just use caching for offloading most of the cached Read API calls? But then what do you mean by "storing and searching "XML/JSON" payloads"? Create Update Delete calls will be redirected to the onprem MDM server. 2. Should the XML/JSON payloads be considered as "read-only" copies of (some of) MDM entities data that have to be "synced" to the cloud from the MDM for faster read/search operations? 3. Should the XML/JSON payloads be considered as decoupled data and handled by the frontside persistence layer to be synced back to the MDM system at certain intervals? Read,Create, Update, Delete would be handled by the front persistence layer, but synced back to MDM master. 4. Do you want to rebuild existing APIs (for true "decoupling") or extend the existing ones by building new ones in the cloud? 5. To decouple the APIs from the MDM system, can these APIs be asynchronous (using queues,…) to be able to cope with MDM unavailability?
1. The MDM is the data layer, whatever strategy that meets the requirements of the criterion is valid provided that you document any assumptions; 2. See point 1; 3. See point 1; 4. The interface needs to be retained to ensure seamless transition for consuming systems. Other than that, see point 1; 5. See point 1;