Λεπτομέρειες πρόσκλησης υποβολής προσφορών
Sla system (5)
According to the Tender Technical Specifications: “Any environmental/operational/financial/project risks surfacing during the life-cycle of an assignment shall be duly analysed and communicated to EFSA as soon as they are detected for the joint definition of a risk response strategy”. Furthermore, the same Specifications distinguish between disruptive risks (“that may compromise the feasibility or the outcome of an event, generate financial loss and/or reputational damage if they occur”) and non-disruptive risks (“that may result in operational delays without impacting budget, reputation and the feasibility or the outcome of an event”) Could you quantify (in number of days or any other time unit) what you consider as ‘as soon’ in the definition of SLA 05? Could you quantify (in number of days or any other time unit) what you consider as the ‘operational delays’ referred to in the note 37, on page 21 of the Technical Specifications? Could you explain how you are going to assess to what extent the ‘reputation of an event’ has been damaged? As it is now expressed, the concept is open to a great degree of interpretation and this generates tremendous insecurity as to its application.
Risk management is a key principle in project management. The objective of SLA 05 is to ensure that risks are proactively monitored and analysed so that corrective measures are identified and implemented before a risk occurs (risk response strategy) and has a negative impact on the project. It is in the primary interest of any service provider to ensure that these principles are adhered to and that any detected risks are communicated to EFSA to encourage the elaboration of a mutually agreed solution in the interest of the project. By “as soon as” EFSA means on the same day. By “operational delay” EFSA means that the contractor missed a pre-agreed project deadline without impacting budget, reputation and feasibility of the outcome of an event.