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

18-010-MC Add Handover Line Control Measure #507

Open
joebayles opened this issue Aug 20, 2018 · 0 comments
Open

18-010-MC Add Handover Line Control Measure #507

joebayles opened this issue Aug 20, 2018 · 0 comments

Comments

@joebayles
Copy link
Collaborator

STATEMENT OF THE PROBLEM: Handover line is explicitly defined in MCRP 1-10.2 as “1. A control measure, preferably following easily defined terrain features, at which responsibility for the conduct of combat operations is passed from one force to another. 2. A predetermined location, normally a phase line designated as a handover line, where control of the battle is transferred to the main battle force.” The Marine Corps adopted part one of the definition when it was removed from JP 1-02 (now DOD Dictionary) during a revision process eliminating tactical level terminology. Part one of this definition is NATO Agreed per AAP-06, AAP-39, and NATOTerm. Handover line is also referenced in the ADRP 1-02 in the definition of battle handover line. This phase line is additionally described and depicted in multiple graphics in MCWP 3-01, Offensive and Defensive Tactics. A handover line may indicate passing of responsibilities other than ‘battle’ responsibilities, so a distinct symbol needs to differentiate between battle handover lines and handover lines.

PROPOSED SOLUTION: Propose the addition of a line control measure symbol HOL as a T1 text amplifier and include T2 text amplifier within the Maneuver Control Measure Symbols Table of MIL-STD-2525D. Draw rules are the same as those for holding line and release line.

image

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

No branches or pull requests

1 participant