UniformQuicky at 19:32, 31 August 2016

2016-08-31T19:32:59Z

Spirit: Created page with "[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides Previous]

TOC

2016-08-31T19:09:46Z

Created page with "[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides Previous] <div id="mainRoleContainer"> <div class="tableOfContents">TOC</div> <h1 class="m..."

New page
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides Previous]

<div id="mainRoleContainer">

<div class="tableOfContents">TOC</div>
<h1 class="mainRoleHeaders">Communications manual</h1>

<p class="jobDescription">
As squad leader you are responsible for communications with other squad leaders and HQ.
</p>
<p class="jobDescription">
To prevent degradation and disturbance to operations, you can follow this guideline to improve your experience as a squad leader.
</p>

<p class="jobDescription">
Keep communication short, clear and respectful.
[Request] –> [Contact] -> [Message] -> [Ending]
</p>

<div id="Communications procedure">
<h1 class="mainRoleHeaders">Communications procedure</h1>

<p class="Communications procedure">
'''Use of OVER and OUT.'''<br>
OVER is used to end the message and you request a reply from the receiver.<br>
''Requesting transport for 8 soldiers main AO, over.''<br>
OUT is used to end the conversation, opening the channel for other elements. Only the starter of the communication can close the conversation.<br>
''Copy, Ghosthawk pad one, (bravo) out.''<br>
Use of over and out is not mandatory, it’s advised.

</p>

<p class="Communications procedure">
'''First address the person you want to speak to, followed by your own call-sign.'''<br>
''HQ this is Alpha, over''<br>
''Foxtrot this is Alpha, how copy''<br>
''(Formal) Alpha this is HQ on command channel, over''<br>
''(Short) HQ - Alpha, over''<br>

</p>

<p class="Communications procedure">
'''The important part is to wait on the response of the receiver. Otherwise, your transmission might be garbled with other channels.''' (and disrespectful)<br>
''(Alpha) this is HQ, over''<br>
''(Alpha) this is HQ, hold one''

</p>

<p class="Communications procedure">
'''Sending your message short and clear after the channel is open.'''<br>
''Requesting 5 artillery round SE of AO on marker 1 till 5, over''<br>
''LZ is secure, land south of church marked with blue smoke, out''<br>
''Requesting use of two unarmed prowlers, over''

</p>

<p class="Communications procedure">
'''Finish your conversation clearly.'''<br>
''Good effect on target, end of fire mission, Alpha out.''<br>
''Copy, Alpha out.''

</p>

<p class="Communications procedure">
'''An emergency transmission can break in on a conversation of other elements.''' This is highly disruptive and misuse will result in penalties. The call BREAK, BREAK means that all communication on the command channel should stop and opens the channel for the emergency. <br>
''Break, Break''<br>
''Rhino(armour) this is Alpha, over''<br>
''This is Rhino, send it''<br>
''Priority target, T-100 NE of town, grid 090-075, taking heavy casualties, over''<br>
''Target located, engaging, over''<br>
''Good effect on target, thank you, Alpha out.''

</p>

<p class="Communications procedure">
'''Sending a statement on command channel (use sparingly) is possible.''' You can send a statement to all elements if the message has a high priority and multiple elements are concerned. Make sure you don’t interrupt other communication on the command channel. <br>
''All actuals, priority message, armoured column consisting of 3 APC’s and 1 T-100 moving in from the north, Alpha out.''<br>
The preferred option is to send the info to HQ so he can address the issue and task an element. <br>
''HQ this is Alpha, priority message, over''<br>
''This is HQ, over''<br>
''Armoured column consisting of 3 APC’s and 1 T-100 moving in from the north, Alpha out.''<br>
</p>

<p class="Communications procedure">

</p>

77th JSOC / Public Servers/ Communication - Revision history

UniformQuicky at 19:32, 31 August 2016