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

Lessons learned VIS #3

Open
132ndNeck opened this issue Mar 24, 2024 · 2 comments
Open

Lessons learned VIS #3

132ndNeck opened this issue Mar 24, 2024 · 2 comments

Comments

@132ndNeck
Copy link
Contributor

Please provide all lessons learned and experiences toward the role of VIS in this issue.

@132ndNeck
Copy link
Contributor Author

132ndNeck commented Mar 26, 2024

Campaign Manager
The tool Campaign Manager have been a valuable tool for VIS. Having the option to export to CombatFlite have made the job as VIS a lot easier/better than before we had this tool. This have made it possible to focus on assessing and understanding the situation, and not work typing coordinates and making sure that BDA or intel is plotted on a map.

Suggestion for improvement of Campaign Manager
A suggestion for improving Campaign Manager into a tool to run and organize a campaign for the roles of JFACC, VIS, MCC and LCC can include the following:

  • Possibility to show pictures (for example hosted on Discord in the #BDA channel). That way VIS analysts do not need to go into open the link and make a lot of extra clicks to see the image (if one have been added to the intelligence report)

Intelligence Requirements and target list

  • Add a function to have Intelligence Requirements and the target list hosted on Campaing Manager
  • Make it possible for VIS analysts to connect reports to Intelligence Requirements or the target list (See attached powerpoint, slide 4, VIS Intelligence Requirements)
  • Make it possible for VIS to sort on Intelligence Requirements or the target list, and then get all intelligence or BDA reports connected to the various IR's or targets
  • Make it possible for VIS to tag a intelligence or BDA report by either: air, maritime, IADS, ground, other. This in order to make it possible for the VIS analyst with that responsibility to see "their" relevant reports

Enemy order of battle and BDA

  • Create a section where the enemy order of battle can be created (See attached powerpoint, slide 5, VIS Enemy order of battle) to remove the need for a excel spreadsheet to keep track.
  • Make it possible for VIS to have the available BDA from a specific event and go in and add these to the enemy order of battle to reduce the numbers (both for air, ground and maritime units).
  • Have a way to visualize the status of enemy forces aggrevated to parent unit with % of strength to be able to assess when a unit is not combat operational (less than 50%)

RFI Tracker

  • Create a button that creates a request for information
  • Request for information can be adressed to:
  • VIS (VIS volunteer team)
  • JFACC (JFACC volunteer team)
  • MCC (MCC volunteer team
  • LCC (LCC volunteer team)
  • JFC (Mission designer/organizer)
  • RFIs populate a list that is available on the "front page" of the campaign manager site
  • The entity responsible can answe the RFI
  • If possible, the RFI can be translated into a Intelligence Requirement by VIS
  • It should be possible for everyone to see all RFIs
    VIS campaign functions.pptx

@132ndNeck
Copy link
Contributor Author

VIS TTP
VIS TTP is too large and theoretical. Should be simplified and made easier and for something to be of use.
Additional "theoretical" or background information can be placed in a doctrine document that is available, but not mandatory.
VIS TTP should be tailored better to how the process actually work, and so it supports the VIS volunteers better.

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

No branches or pull requests

1 participant