Vanasadamas hakkasid laevu teenindama automaatsed sildumisseadmed
Vanasadamasse saabuvaid ja lahkuvaid Tallinn-Helsinki liinil sõitvaid laevu asusid teenindama automaatsed sildumisseadmed, mis aitavad hoida kokku sildumisele kuluvat aega ja säästa keskkonda.
“Traditsioonilisel viisil ehk kasutades otsi ja pollareid kulub kaimadrustel täna sildumise korraldamiseks kümme või rohkem minutit, vaakumseadmetega võtab aga sama protsess alla kahe minuti ning laeva vabastamisel mõõdame aega juba sekundites. Kogu süsteem on kaugjuhitav ning vaid laevakapteni poolt opereeritav,“ ütles Tallinna Sadama infrastruktuuri arendusdivisioni juht Peeter Nõgu.
Aja kokkuhoid toob ühtlasi kaasa keskkonnasäästu. „Kuna laev kulutab kai juures manööverdamisele vähem aega, siis isegi 5 minutit kokku hoitud sõiduaeg vähendab laeva kütusekulu ning heitmekoguseid. Pika perioodi jooksul on sellel märkimisväärne keskkonnamõju,“ selgitas Nõgu.
Uued vaakumseadmed paigaldati Tallinn-Helsinki liini teenindavatele kaidele. Kaile 5 ja 12 paigaldati ettevõtte Cavotec-i seadmed, kaile 13 Trelleborgi seadmed. Oma tehnilistelt parameetritelt on seadmed sarnased.
Cavoteci juhatuse esimees Mikael Norin rääkis: “Me oleme äärmiselt uhked, et Cavoteci tehnoloogia toetab Tallinna Sadama visiooni saada Läänemere uuendusmeelseimaks sadamaks ning aitab ellu viia kestlikke eesmärke puhtama õhu tagamisel. Meie automaatsed vaakumsildumisseadmed MoorMaster võimaldavad laevadel hoida kokku aega sildumisel ning seetõttu sõita aeglasemalt ja väiksema kütusekuluga vahemaad Tallinnast Helsingisse vähendades seeläbi laevade poolt õhku paisatavaid kasvuhoonegaaside emissioone kuni 12 000 tonni aastas, mis on võrreldav 10 000 diiselkütusel autoga.“
Automaatsildumise seadmed on töökindlad ja neid on võimalik kasutada praktiliselt kõigis ilmastikutingimustes. Arvestada tuleb vaid tuulepiiranguga 17 m/s ning sedagi oludes kui tuul puhub risti laeva välispardaga kaist eemale. Sellisel juhul kasutatakse ohutuse tagamiseks lisaks ka laeva otsi.
Lähimad sarnased seadmed asuvad Helsinki Läänesadamas, Marienhamni sadamas ja Langnas’i sadamas Ahvenamaal.
Uute sildumisseadmete paigaldamine toimus projekti TWIN-PORT 3 raames ja seda toetas Euroopa Liit infrastruktuuri investeeringute meetme CEF kaudu. Tallinn-Helsingi meretee arendusele suunatud projekt viiakse ellu perioodil 2018-2023, selles osalevad Tallinna Sadam, Helsingi Sadam, Helsingi linn ja kolm laevaoperaatorit (Tallink, Viking Line ja Eckerö Line) ning projekti kogueelarve on 61,2 mln eurot. Tallinna Sadama poolt tehtavate investeeringute maht oli 15,8 mln eurot.
Vaata videost, kuidas automaatsildumine välja näeb!
Vanasadama reisiterminalide juures on võimalik reisijate
pealevõtmiseks ja mahapanekuks lühiajaliselt tasuta parkida –
selleks on nii A- kui D-terminali juures Kiss&Sail parklad.
Kiss&Sail parklad on kasutamiseks nii erasõidukitele, mittelepingulistele
taksodele kui ka sõidujagamis-app’ide sõidukitele (Bolt, Uber, Yandex jne).
Otse terminali uste ette pääsevad vaid lepingulised taksod (Tallink, Tulika).
Terminalide ees on lubatud lühiajaliselt parkida ainult bussidel.
Cookie Consent
Weusecookiestoensureconvenientfunctioning of thewebsite. Necessarycookies are alwaysactive. Weuseanalyticalcookiesonlywithyour consent. See ourcookiepolicy.
Cookie preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
WPForms is a user-friendly WordPress plugin for creating custom forms with drag-and-drop functionality.
Name
Description
Duration
wpfuuid
Used to track user interactions with forms.
11 years
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Facebook Pixel is a web analytics service that tracks and reports website traffic.