Predmet tendera: | Nadgradnja SCADA sistema | |||||||||||||
Partije (lotovi): | Nadgradnja SCADA sistema | |||||||||||||
Mesto: | Crna Gora, Budva | |||||||||||||
Datum objave: | 12.04.2023 | |||||||||||||
Rok: | 19.04.2023 - (rok je istekao) - Pogledajte slične aktuelne nabavke | |||||||||||||
Oblast: | Telemetrija. daljinsko vodjenje i upravljanje. SCADA sistemi. MTK i MTU prijemnici. Brojila el. energije. Software. Informacioni sistemi. Web dizajn. Informaticke usluge. | |||||||||||||
Naručilac: | OTPADNE VODE BUDVA DOO | |||||||||||||
Tekst javne nabavke - tendera: | PODACI O NARUČIOCU Naziv: OTPADNE VODE BUDVA DOO PIB: 03304388 E-mail: office@otpadnevode.me Telefon: 033/473-414 Fax: 033/473-414 Internet adresa: https://www.otpadnevode.me Adresa: Omldinskih brigada bb Grad: Budva Poštanski broj: 85310 ------------------------------------------------------------- OSNOVNI PODACI Opis predmeta javne nabavke Nadgradnja SCADA sistema TEHNIČKA SPECIFIKACIJA PREDMETA NABAVKE 1. Maintenance via remote access | Regular maintenance of local SCADA system made by GrosseWentrup: Maintenance via remote access | 1 hour 2. Maintenance : Helpline | Regular maintenance of local SCADA system made by GrosseWentrup: Helpline | 1 hour 3. Intervention via remote access to equipment | Interventions on local SCADA system made by GrosseWentrup: Intervention via remote access to equipment | 1 hour 4. Intervention Helpline support | Intervention on local SCADA system made by GrosseWentrup: Helpline support | 1 hour 5. On-site intervention | Intervention on local SCADA system made by GrosseWentrup: On-site intervention | 1 hour 6. Travel cost | Travel cost - day arrival | 1 day 7. Travel cost | Travel cost - day departure | 1 day Vrsta predmeta: Usluge Vrsta postupka: Jednostavna nabavka Službenik za javne nabavke: Bojan Šašović Kontakt: 033/475-657 Datum objave: 2023-04-12 13:00:00 Napomena 1.Maintenance of local SCADA systems made by Grosse Wentrup The Contractor must provide categorized levels of support for maintenance of equipment, depending on the type of Users request (reconfiguration or modification of equipment settings, consultations by phone or troubleshooting in production). Levels of support should include all measures required to solve systemic problems in work, or consultations by phone, and their execution from the onset of the problem (corrective maintenance). Problems are categorized into three levels, as specified in the segment on categorization. Preventive activities (proactive maintenance) include active monitoring of hardware, network and operation of SCADA system in order to avoid network and system problems: hardware control due to possible errors, checking the general functioning of SCADA applications, checking the server environment, analysis of system performance, etc. Preventive activities are performed on quarterly basis. The Contractor shall have an all-in-one place to receive, forward and archive calls/report failures (should be adapted to the reporting of problems with the equipment that is subject to maintenance) by the Ordering Party (web portal or similar), and to provide detailed instructions about how to report failures and escalate problems. The Contractor shall submit proof in the bid of being an authorized service provider for the requested brand. The Contractor should provide an expert (certified by the manufacturer of equipment and services to provide installation and service the equipment in question) for any on-site or remote intervention, e.g. replacement of damaged hardware with new spare parts, physical installation of boxes/modules, configuration of spare parts, service intervention, etc. The Contractor shall enable the following types of intervention, depending on the type of failure: •On-site inspection at the plant or pumping station and troubleshooting •Remote access to the equipment, in this case competent unit of the Ordering Party shall make an on-site visit to the plant or pumping station •Consultations by phone, repair is performed by the staff of the Ordering Party, and assistance by phone by the Contractor 1.1.Technical Support Technical support implies the following activities: •consultations by phone and optimization of system resources (equipment and services that are the subject of the Maintenance Agreement), •design verification and consultations for network and system redesign or upgrade, •stand-by readiness at the time of system upgrade, •system software update, •review of network and system status/validity of the system operation once a month for 2 hours. After the performed activities, and no later than the 5th day of the current month for the previous month, the Contractor shall send an e-mail to competent persons of the Ordering Party with a report on the status of performed controls with an indication that it is a regular monthly report, •detailed quarterly reports on system status. After the performed activities, and no later than the 5th day of the month for the previous quarter, the Contractor shall send an e-mail to competent persons of the Ordering Party with a report on the status of performed controls with an indication that it is a regular quarterly report, •consultations during the network and system work cycle of the system. 1.2.CORRECTIVE MAINTENANCE Corrective maintenance in terms of the Maintenance Agreement implies corrective actions in the event of a problem being reported by the User. Corrective maintenance is directly related to the agreed response times and involves the replacement of a non-functional part with a spare new part, incidental intervention to eliminate the consequences of system software bugs or intervention related to other environmental problems closely related to equipment and services that are subject to the Maintenance Agreement. With corrective maintenance, the system should be returned to its original state of functionality as soon as possible. 1.3.PROACTIVE MAINTENANCE Proactive maintenance involves an agreed annual inspection and monitoring of the system, and indicating weak spots and possible problems. The agreement must provide for the review of logs, analysis and indication of updates and installation of updates at the hardware level (update of BIOS, firmware, OS, etc.), preparation of annual reports. 1.4.RESPONSE TIME AND CATEGORIZATION The following is a categorization of possible problems ranked in three levels, with a description of typical failures/outages and the expected maximum response time and removal of failures/outages, according to the 24/7 availability model. CATEGORYDESCRIPTIONRESPONSE TIME LEVEL 1Failure/outages that lead to a system shutdown or cause critical consequences for the Users operations. Failure/outage requires continuous operation (24/7) and reporting until the system recovers. Description of possible problems: •failure of the local SCADA system, monitoring and management of the plant are not possible •operating system failure •telemeter failure •failure of communication between devices, defective process network •failure of measurement transducers24h LEVEL 2 Failure/outage of a part of the system that causes reduced system functionality. Description of possible problems: •A part of the plant has no communication with the local SCADA system, •archive server failure •failure in chart of measurements •AT32 failure •printer failure48h LEVEL 3Consulting services aimed at planned activities and where the regular operation of the system (equipment that is the subject of the Maintenance Agreement) is not compromised or slowed down. The following requirements are possible: •request for system reconfiguration, •request for additional analysis of performance, •request to test the system •request to document all changes to the system, •request to plan the development and improvement of the system, •request for additional training for system maintenance, •request for log analysis.120h Response time is a time interval that begins when the User submits a request (escalation and problem reporting are defined by the MaintenanceAgreement) and ends when the Contractors representative qualified to provide the requested service contacts the User. Troubleshooting time is the time interval in which the full functionality of the service is established, after the failure/problem has been reported. Recovery time includes response time interval. ------------------------------------------------------------- Procijenjena vrijednost nabavke: 19000 EUR ------------------------------------------------------------- ROKOVI Početak podnošenja: 12.04.2023 14:00 Kraj podnošenja: 19.04.2023 14:00 Datum otvaranja: 19.04.2023 14:30 Rok za donošenje odluke: 29.04.2023 14:00 | |||||||||||||
DOKUMENTACIJA: |
|