Describe the new feature you would like to see
On top of showing that a localisation mission has been run on the robot, we should also show which deck this was done on last.
Describe the solution you'd like
We should have a nullable value on the robot model which stores localisation deck. It may be hard to guarantee that this is coordinated between Isar and Flotilla, but I still think it's good to have some indication in the frontend of whether or not a robot is ready to receive missions. Whether this is displayed on the robot page or in the robot card is up for debate.
Information about which deck the robot has been localised can be sent to the frontend via signalR, where it can then be stored in a context.
How will this feature affect the current Threat Model?
I don't think this should affect the threat model since we already store which installation the robot is on.
Describe the new feature you would like to see On top of showing that a localisation mission has been run on the robot, we should also show which deck this was done on last.
Describe the solution you'd like We should have a nullable value on the robot model which stores localisation deck. It may be hard to guarantee that this is coordinated between Isar and Flotilla, but I still think it's good to have some indication in the frontend of whether or not a robot is ready to receive missions. Whether this is displayed on the robot page or in the robot card is up for debate.
Information about which deck the robot has been localised can be sent to the frontend via signalR, where it can then be stored in a context.
How will this feature affect the current Threat Model? I don't think this should affect the threat model since we already store which installation the robot is on.