Closed 132ndNeck closed 2 years ago
Regarding VIS: 1) I suppose he would also get "tips" from ADMIN in the form of dispatches/reports ("CIA reporting a convoy passed Iraq/Syria border, composition xxxx time yyyy " etc?) 2) I suggest that when we make this public we state up front that this function can potentially be very busy better be done with a team rather than a single person (i.e someone focuses on "small level" analysis/evaluation (what a specific enemy BN or squadron is likely to do next) while other/s handling the high-level (large movements of forces combined with strategic situation etc) 3) I also suppose we should be providing all imagery files and static target information to the VIS and he would provide it to the pilots.
We should of course have a hidden list, with various targets and the effect it may have if they are taken out, and then drop som intel now and then to see if they pick it up (for example, logistical convoys driving into a ammo site during a AR mission or strike mission. So the pilots potientially could pick it up, etc)
Allocation CJTF HQ will set allocation between the following:
So if they set 100% to CAS/AI, then there is no one availeble in case the enemy launches a air attack, and thus the friendly assets can be engaged. Also if they set 100 % to OCA , then no support is given to the ground forces, and they ground forces will suffer.So they will need to find a good balance, and then the AOC translates this into taskings in the ATO.
JPTL - Joint Prioritized Target List CJTF HQ will also select the targets for JPTL for this ATO. This is targets intended to be struck. So it can not be too many targets. JPTL targets are selcted based on the master target list which contains all targets. CJTF HQ will be supported by VIS for this, as VIS can help nominate or suggest targets to JPTL. The JPTL will change daily (follow the ATO cycle)
One suggestion : We change the role of CJTF HQ to Joint Force Air Component Commander (JFACC), The we as mission designers assume the role of the overall CJTF HQ, and thus can give the overall direction (giving us more control, since that will be controlling also sea and ground forces), and the volunteers can affect the air campaign , thus not needed to focus too much on the things they not "care about" in the same way.
We can then submit several air requests from the ground force, and then have them decide who will be supported or not, and also the allocation as mentioned above. Then VIS can submit some targets for the JPTL for winning the war, and JFACC can submit some targets for winning the air campaign, and then we control the JPTL (targets that are to be attacked for the next ATO) better.
What do you think?
Then the JFACC (Joint Force Air Component Commander, commander of the air forces) can give out a Air Operations Directive to the AOC (us). This is all based on : https://www.jcs.mil/Portals/36/Documents/Doctrine/pubs/jp3_30.pdf
The AOD follows the following format: (Can be made into a simple word and/or google docs format to make it easy to fill out. The Situation will be given by us, enemy situation by VIS. What is important is really only part 3, the execution.
SITUATION
a. JFC guidance (verbatim).
(1) JFC’s intent statement.
(2) Execution guidance (if issued).
(3) Supported and supporting command relationships.
b. Enemy situation.
c. Friendly situation (by joint force component).
MISSION The JFACC’s mission statement (verbatim). Covers all phases of the operation, but AOD may state which phase this AOD applies to. This should not change unless the mission itself changes.
EXECUTION–AIR OPERATIONS a. JFACC’s intent. (1) Purpose. (2) End state. b. Execution: What to do, when. c. Focus of effort by objective. d. Weight of effort by objective. e. Acceptable level of risk. f. Collateral damage and civilian casualty guidance g. TST guidance. h. Other issues (e.g., ISR, information, space, mobility, focus of effort, PR).
So many new acronyms for me , I'll need some time learning it :-) So to see if I get this right: 1) We take CJTF-HQ role, and AOC 2) Volunteers are taking VIS, AOD and JAFCC 3) We as CJTF-HQ are "knowing" the overall intelligence picture and can "steer" the whole war effort the way we see fit. 4) We stream the intelligence to the VIS 5) We instruct the JAFCC what efforts are planned during the next day of war ("A. Israel is going to initiate an offensive to retake Mt. Hermon; B. Turkey will be defending on the border against a Syrian division near XXX; C. We've been authorized to conduct a deep strike against Syrian logistics center EAST of DAMASCUS; D. ...." 6) JAFCC takes the objectives we've outlined, consults with his VIS and decide which objectives will be supported by the wing during the event. 7) JAFCC issues an AOD to AOC (Us). 8) AOC (Us) builds the ATO based on the AOD and share it with all pilots so they can start choosing what role they wish to take, and form up flights and packages) 9) VIS is fetching specific intelligence bits from CJTF-HQ and distributes it to the pilots/ JAFCC to enable detailed planning.
Did I get this flow right? Once I've wrapped my head around it I'll try to do a graphical representation of it so it might make it easier on everyone (including timeline of when each step should take place)
Almost right, let me sum up the suggestion, and see if it makes sense for you aswell:
We have the following "agencies"/roles:
Volunteers take VIS and JFACC.
Flow:
Does that make sense? And does it seem reasonable and interesting? And doable?
Makes total sense. Thanks for the clarification. I've never went into those details of how things are conducted (IDF doesn't play the same way as US / NATO I suppose :-P ) And it adds a lot of immersion to the whole campaign I think. Very good addition!
Excellent! Then we can move forward with that organization, and iron out the details needed, and the various products and formats, so everything is ready.
I was also thinking to have different Discord channels:
So a seperate OPAR section with the following channels (all on the 132nd server) (several channels, but just to streamline the information if things go in the right channels)
Yep! As for the "Reports/Orders" I think it should be an announcements-only channel where we only put notes/details/reports but those shall be processed/discussed in any of the other channels.
Yep! As for the "Reports/Orders" I think it should be an announcements-only channel where we only put notes/details/reports but those shall be processed/discussed in any of the other channels.
Yes, I agree.
Ok, so for products that will be used in the campaign:
Anything else you can think of that we need of products during the campaign? (of course not a problem to add more as we see fit).
This thread is for discussing and agreeing on the campaign organization / roles / functions:
All positions should be volunteer, and if no one steps up, then it will be filled by us as the mission designers.
Combined Joint Task Force HQ:
Virtual Intelligence Service (VIS):
Air Operations Centre (AOC):
Admin