Edit Use Case: Suez Canal Blockage: EverGiven

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in one of the groups: Users, Writers.

Note

The following fields are mandatory:

Core data → Brief summary
Questions → Which thematics are closest to the goal of the Use Case?

Leaving these fields without an answer will prevent you from saving the form.

Please do not include any personal or confidential information (e.g., addresses, contact details, etc.) in your contributions!

[edit]

Core data
Extended data
Questions

Category	Exercise Preventive campaign Real-world
Year
Publishing Organisation:
Location City and country.
Hazard e.g., earthquake, flood
Scale Leave at "none" if you don't know the answer.	None/unknown City Country County
What is the overall timeframe of the use case? Leave at "none" if you don't know the answer.	None/unknown Less than 1 day 1 to 3 days More than 3 days
Brief summary Required. This text will also appear in the list of all use cases.	In March 2021, the Suez Canal was blocked for six days by the Ever Given, a container ship that had run aground in the canal.

Theme Which general theme did the Use Case cover?	Crowdsourcing Social Media
Disaster Management Phase	After Before During
Which vulnerable groups were involved?
Which social media and crowdsourcing technologies were used?
Was a technology specifically developed for this use case? Leave at "none" if you don't know the answer.	None/unknown yes no
Which guidelines were used?
Which Social Media Platforms were used?
Which hashtags or keywords were used (if applicable)? e.g., #covid #tornado

Description If you would like to extend the brief summary, you can do so here.	In March 2021, the Suez Canal was blocked for six days by the Ever Given, a container ship that had run aground in the canal. The 400-metre-long (1,300 ft), 224,000-ton, 20,000 TEU vessel was buffeted by strong winds on the morning of 23 March, and ended up wedged across the waterway with its bow and stern stuck in the canal banks, blocking all traffic until it could be freed. Egyptian authorities said that "technical or human errors" may have also been involved. The obstruction occurred south of the two-channel section of the canal, so there was no way around it for other ships. The blockage of one of the world's busiest trade routes significantly slowed down trade between Europe, Asia and the Middle East. On 28 March, at least 369 ships were queuing to pass through the canal, stranding an estimated US$9.6 billion worth of trade. On 29 March, Ever Given finally freed by 14 Egyptian, Dutch, and Italian tug boats at high tide to dislodge it. (Source: Wikipedia)
Involved Organisations:
What was the overall goal of the Use Case?	From the perspective of the Hamburg Fire Department, the consequences for the Port of Hamburg are to be assessed. The aim was to evaluate information in real time from Social Media.
Which thematics are closest to the goal of the Use Case?	Collecting and Analysing Information from SMCS Ensuring Credible Information Making Information Accessible Mobilising Citizens Mobilising Volunteers Targeting Communication
What limitations were identified? e.g., regulatory hurdles	Plausibility must be checked for all searches, and specially trained personnel are required for this purpose.
What worked well and could be recommended to others?	Photos and information about the operation were pulled from social media more quickly than was possible using conventional fire service means and improved the situational picture. The salvage operation provides information for the company's own operational planning in the event of accidents in the port. In particular, the timeline was tracked to estimate when the impact in Hamburg is likely to occur in future events. The use of special maps, estimating which ships will be „delayed“ are useful.
Links for further reading Important tweets, sources, articles, photos, videos, etc.

Summary:

Cancel