Defuzzy Tech — USV Fleet Dashboard

[00:00] "I'll record this quick brief for this platform that we're trying to build."

[00:04] "At the moment, what you see is a very crude engineering concept — zero consideration for the design aspect, but mostly focused on functionality, developed by a programmer that just wants to quickly sketch some of the features."

[00:30] "This basically serves as a brief more than anything."

[00:34] "The idea is we want to control multiple boats from our user interface system."

[00:44] "The main interface is a map that shows different assets which you can monitor and control. These assets pick up different targets — radar targets or AIS detections."

[01:08] "I select one of those assets, I can view information on the asset — propulsion, comms system. We would like to keep the idea of being able to undock some of these gauges and dock them back again."

[01:30] "Once we take control, we should be able to see the position of the vessel, the heading, the course over ground."

[01:43] "Say I want the vessel to follow a specific path, I should be able to draw a route or select one of the routes I have drawn in the past."

[02:00] "Click on New Route, make a new route, edit it, save it, confirm."

[02:13] "Once this route is saved, I should be able to dispatch it to the boat. The route is dispatched but the boat is not following it yet."

[02:26] "Then I activate the waypoint — ask the boat to follow this way."

[02:44] "Here you can see a number of targets the boat has acquired. I should be able to see targets that other boats have also acquired."

[02:53] "I should be able to track these targets — ask my USV to track them. Set the distance and offset, then start tracking."

[03:20] "We should see the RPM of the engines — the boat has two engines, port and starboard. View RPM of each and the trim level of the outboard engines."

[03:40] "Position, roll and pitch — maybe through an artificial horizon or OpenBridge-style gauge."

[03:51] "Heading, course over ground, direction of wind, and the set direction — the direction the autopilot is telling the boat to follow."

[04:01] "Speed over ground is very important to show. We'd also like to see fuel level."

[04:10] "Video from the asset — separate window, full screen, exchange positions with the map. Video fullscreen with map small, or the other way around."

[04:35] "This is literally just a sketch. Currently our systems do not use a dashboard like this at all."

[04:48] "We have an existing system that I can brief you on at a later stage."

[05:09] "At the moment our system only does 1-to-1 — one operator controls only one boat. We want one operator to control more than one boat at the same time."

[05:36] "I should be able to see all of the alerts coming from the boat over here."

[05:42] "We would like to follow a very specific alert management scheme."

[06:33] "We would like to follow the IMO concepts — borrow from the IMO resolution for alert management."

[06:42] "Alerts get triggered: active and unacknowledged. Once they clear out, they become rectified. They can be unacknowledged if the operator doesn't acknowledge. Finally rectified and cleared."

[06:59] "Sometimes they can be acknowledged but still active — especially warnings."

[07:06] "Every alert has a level of priority: emergency alarm, alarm, warning, or caution."

[07:14] "Some cautions or warnings you can just acknowledge without having them rectified."

[07:27] "Simulated warnings we're getting — acknowledge or silence them. If silenced, they pop up after some time."

[07:38] "Back to the maps — monitor these boats and control them remotely."

[07:51] "There are specific details we want with certain gauges, conveyed at a later stage to the designer. For now, this is the brief. Thank you."

[00:00-04.5] "I'll record the quick beef for this platform that I'm trying to build."

[04.5-14.0] "At the moment, what you see is a very crude, let's say, engineering concept, so with zero consideration for the design aspect, but most of all, on functionality basically developed."

[14.0-22.2] "The idea is we want to control multiple boats from our user interface system that we're trying to develop."

[22.2-30.0] "The main interface is a map that shows different assets which you can monitor and control."

[30.0-38.0] "These different assets also pick up different targets that can be either radar targets, or radar detections, or AIS detections."

[38.0-46.0] "Say I select one of those assets, I can view the asset, get some information on the asset — propulsion, comms system."

[46.0-54.0] "We would like to keep the idea of being able to undock some of these gauges and maybe dock them back again."

[54.0-62.0] "Once we take control, we should be able to see the position of the vessel, the heading that it's taking, its direction of motion, or the course over ground."

[62.0-70.0] "Say I want the vessel to follow a specific path, I should be able to draw a route or select one of the routes that I have drawn in the past."

[70.0-78.0] "Click on New Route, make a new route, edit this route, save the route, confirm."

[78.0-86.0] "Once this route is saved, I should be able to dispatch it to the boat. The route is dispatched to the boat but the boat is not following the route yet."

[86.0-94.0] "Then I should be able to ask the boat to follow this route — activate this waypoint. It asks the boat to follow this way."

[94.0-102.0] "Here you can see a number of targets that the boat has acquired. I should be able to see the targets that the other boats have also acquired."

[102.0-110.0] "I should be able to do things like track these targets — ask my USV to track these targets."

[110.0-118.0] "Say I ask the USV to track this target, I'll do something like set the distance and offset, and then start tracking that other asset."

[118.0-126.0] "Over here we should see the RPM of the engines on each of these boats. The boat has two engines — an engine on the port or left side and another on the starboard or right side."

[126.0-134.0] "We should be able to view the RPM of each of these engines and the trim level of the outboard engines."

[134.0-142.0] "Position, roll and pitch, maybe through an artificial horizon or through this OpenBridge-style gauge."

[142.0-150.0] "Heading, course over ground, maybe direction of wind, and the set direction — the direction that the autopilot is telling the boat to follow."

[150.0-158.0] "Speed over ground is very important to show. We'd also like to see fuel level displayed here."

[158.0-166.0] "Video coming from the asset itself — I'd like to see it on a separate window. We should be able to go into full screen and exchange the positions with the map."

[166.0-174.0] "Have the video go full screen and the map being small, or the other way around."

[174.0-182.0] "This is literally just a sketch of some of the different ideas. Currently, our systems do not use a dashboard like this at all."

[182.0-190.0] "We have an existing system that I can brief you on maybe at a later stage."

[190.0-198.0] "These were the basic ideas that we were trying to capture in this new dashboard that allows us to control more than one boat at the same time."

[198.0-206.0] "At the moment, our system only does 1-to-1 — one operator controls only one boat. But what we are trying to do is give one operator the capacity to control more than one boat."

[206.0-214.0] "One of the things that I forgot to mention is also alert management — it's very important. You can forget about all the other entries here. For now, the most important ones are Map and Alert Management."

[214.0-222.0] "I should be able to see all of the alerts coming from the boat over here. And we would like to follow a very specific alert management scheme."

[222.0-230.0] "We would like to follow the IMO concepts — borrow some of the concepts from the IMO resolution for alert management."

[230.0-238.0] "Basically alerts get triggered. They are active and unacknowledged. Once they clear out, they become rectified. They can be still unacknowledged if the operator does not acknowledge these alerts."

[238.0-246.0] "Then they can finally be rectified and cleared if they're rectified and acknowledged."

[246.0-254.0] "Sometimes they can be acknowledged but still active — especially in the case of warnings."

[254.0-262.0] "Every alert has a level of priority associated with it — emergency alarm, alarm, warning, or caution."

[262.0-270.0] "Some cautions or warnings you can just acknowledge without having them rectified."

[270.0-278.0] "Here you can see some of the simulated warnings we're getting. We can acknowledge or silence them. If silenced, they'll pop up after some time."

[278.0-286.0] "Back to the maps — monitor these boats and control them remotely."

[286.0-294.0] "There are some specific details that we want with certain gauges, conveyed at a later stage to the designer. For now, this is the big thank you."

… plus intermediate segments covering route drawing, waypoint activation, and engine telemetry detail (90 segments total, full 8-minute coverage).