Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

team flags / rescue team callsign handling #729

Open
caver456 opened this issue Feb 23, 2024 · 2 comments
Open

team flags / rescue team callsign handling #729

caver456 opened this issue Feb 23, 2024 · 2 comments

Comments

@caver456
Copy link
Collaborator

Recent callsign conventions for NCSSAR have been changing a bit to mimic other teams.

This should all be clarified and confirmed with the unit leader.

There are two changes in question:

  1. The main change is that the first team to arrive at the subject should assume control of the scene (e.g. establish a 'mini-IC' to manage incoming resources etc.) and should prepend the word 'rescue' to their callsign.

So, if team 104 is the first to reach the subject, they become 'team rescue 104' or just 'rescue 104'.

  1. Also, the lead medical person should use a different callsign, such as '104 medical'.

How can radiolog be enhanced to handle these cases?

An idea for 1) is to 'set a flag' on team 104, which would visually highlight that team's tab, and would prepend 'RESCUE TEAM:' or such to each entry as long as the flag is set.

For 2), it seems like no extra handling is needed - that the first call from '104 medical' should result in a new callsign / new tab '104med' or such. Possibly set a similar flag for that callsign. This is all up to the radio operator to do - either change callsign if the radio has called in before, or, set callsign if it's the first call from that radio.

@johnpictin
Copy link

johnpictin commented Feb 23, 2024 via email

@caver456
Copy link
Collaborator Author

@johnpictin thanks for the feedback, that would be my preference too, but our team decided to go with the name changes. I can't really say which way works better for them in the field, but I do see the logic of the name changes. Unfortunately it kind of turns things into a bowl of spaghetti after the rescue is done.

Either way, from radiolog point of view, the question is what if any enhancements to make, that accommodates either way of doing things. For the 'keep the original callsigns always' method, there aren't any enhancements needed, since that is already working.

Anyway this came up for us again at a MRA mock test recently. I got to be radio operator to see some of these questions first-hand and to take a bunch of notes. Here's what happened:

  • team 101 became the rescue group on arrival at the scene, but there was never any clear message about it such as "team 101 is now rescue 101" or 'rescue team 101' or 'rescue group 101' or 'rescue group 1' or 'rescue group' or any other variation. Seemed like the de-facto callsign after a while was 'rescue group 1'.

  • later callsigns that came over the radio: 'rescue rigging group 1'; 'rescue group 2'; 'medical 101'; 'medic 1'; 'medic 2'. We're sorting this out within the team, but the point is that there may be an interesting set of new callsigns.

  • when rescue group called to say the scenario was complete, we (ops, deputy IC, and comms) decided to ask them to revert to original callsigns for the trek back down the mountain. They decided not to do this. Also working this out within the team, but it also brings up the point that radiolog can't make any assumptions about what callsigns will be after the rescue.

  • changing callsigns - effectively creating a new team - meant that the original team tabs (101 etc) became 'inactive' and would flash red with timeouts for the rest of the day. This is not a big deal as long as the operator is aware of what's going on, but handing off to a different operator who may not be aware of this could cause them to do a welfare check on a team that's effectively inactive. Maybe a way to indicate this in radiolog would be helpful? Probably not a good idea to just disable timeouts for that team, because we want to restart timeouts with their next incoming call. That restart of timeouts could be automatic.... is it safe to wait for their next incoming call? Basically to put a callsign on inactive status, and the next incoming call removes that inactive flag which restarts timeouts? Would probably need some type of visual indication...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants