14 “The first 72 hours, everybody was sending me data over email,” Hanna said. “I was spending all night processing that and then posting it onto the dashboard. It was not sustainable.” “We set up a call with the Army Corps, NOAA, and others on how we wanted to share data,” Adams said. “We created a partnered collaboration group, with restricted access. We were all seasoned on data sharing details surrounding natural disasters and what that means in terms of data governance.” With portal-to-portal GIS connections, each agency maintained full control over its authoritative data. Shared GIS data layers included bathymetry, water levels, the temporary channels, and ultimately the cleared main channel. A 3D web scene visualized details of the salvage crews working to free the grounded ship and remove pieces of the bridge (see sidebar). Administrators provided access to anyone who needed to see the data, from divers doing the salvage work to surveyors mapping the channel and White House officials monitoring the progress. took the lead. Its Marine Transportation System Recovery Unit started working to reopen the Port of Baltimore as quickly as possible. “At the start, we pulled together bridge blueprints from the 1970s. By the third day, we built a GIS dashboard to focus on creating new channels,” said Lt. Commander Ian Hanna, lead of the Coast Guard’s Response GIS Support Team. “We knew it was going to be a while for the main channel to reopen.” The Coast Guard set up a Unified Command Center at the Maryland Cruise Terminal. They added all key data to a real-time GIS dashboard, including vessel locations provided by Esri partner Spire. This dashboard became the center’s common operating picture, with a constant flow of new inputs to keep all stakeholders informed. The National Oceanic and Atmospheric Administration (NOAA) incorporated sensor data from buoys, which monitor water currents, and depth data from multibeam sonar surveys to update nautical charts. The US Army Corps of Engineers (USACE) added bathymetric channel surveys to monitor changes as pieces of the bridge were removed. Personnel and data from the Maryland Transportation Authority, the City of Baltimore, and other state agencies joined the effort. Soon, the individual agencies wanted to create their own purpose-built apps to coordinate missions and feed updates into the common operating picture. Amilynn Adams, a marine transportation system specialist with the Coast Guard, built a site with ArcGIS Hubsm to connect vital data and share the purpose-built apps from each agency. The Key Bridge Response Common Operating Picture was in place early on, and it constantly evolved. Users could query a wealth of data layers to see progress and understand the complexity of this critical salvage operation.
RkJQdWJsaXNoZXIy MjA2NTE0Mw==