DRAFT: Add TAK Wiki synced from Outline

docs/dev/contributing/07-user-groups-and-their-needs.md

@@ -10,8 +10,8 @@ The basic **missions** of all C2 are the below three:
 
 | Name | What | Examples |
 |----|----|----|
-| Fires | **From the forward observer viewpoint:**Plan fires, Order fire, direct fire; <br><br>**From the firing unit viewpoint:** Receive fires plans, Receive fires orders, Calculate fire mission settings for the weapons, Receive directions. | A fires plugin in TAK that enables fires planning and sending & receiving fires orders |
-| Leadership support | **From the leaders'****viewpoint**: Write and send Orders, Send Execution orders (Execute pre-prepared actions via 'Execute Red'). <br><br>**From the subordinates' viewpoint:** Receive Orders & Execution Orders, Report Receiving, Ask for Guidance | An instant messaging service, a PTT (Tactical radio-like push to talk) service, a Google Drive-like staff toolset |
-| Situational Awareness | See where allies are (Blue force tracking) and how they are, <br><br>See reports where the enemies & others are and what they do,<br><br>Prepare & send georeferenced images & layers regarding Orders<br><br>Report data both intentionally and automatically  Analyze data both by hand, by automation and by AI | A situational awareness app / battle management system, a map software  A task management software  A ticketing system |
+| Fires | **From the forward observer viewpoint:**Plan fires, Order fire, direct fire; <br /><br />**From the firing unit viewpoint:** Receive fires plans, Receive fires orders, Calculate fire mission settings for the weapons, Receive directions. | A fires plugin in TAK that enables fires planning and sending & receiving fires orders |
+| Leadership support | **From the leaders'****viewpoint**: Write and send Orders, Send Execution orders (Execute pre-prepared actions via 'Execute Red'). <br /><br />**From the subordinates' viewpoint:** Receive Orders & Execution Orders, Report Receiving, Ask for Guidance | An instant messaging service, a PTT (Tactical radio-like push to talk) service, a Google Drive-like staff toolset |
+| Situational Awareness | See where allies are (Blue force tracking) and how they are, <br /><br />See reports where the enemies & others are and what they do,<br /><br />Prepare & send georeferenced images & layers regarding Orders<br /><br />Report data both intentionally and automatically  Analyze data both by hand, by automation and by AI | A situational awareness app / battle management system, a map software  A task management software  A ticketing system |
 
 **What is needed the most varies by the User Group, their perceived Enemy and their Area of Operations.** A frontline infantry unit will need most Fires, while a Support Area infantry / military police unit will need Situational Awareness and Leadership Support the most.

docs/dev/specs/01-deploy-app/deploy-app-release-process/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Deploy App Release Process",
+  "collapsed": true
+}

docs/dev/contributing/04-deploy-app-release-process/index.md → docs/dev/specs/01-deploy-app/deploy-app-release-process/index.md

@@ -1,5 +1,5 @@
 ---
-title: "04-Deploy App Release Process"
+title: "Deploy App Release Process"
 ---
 
 # Version Release Guide

docs/wiki/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Wiki",
+  "collapsed": true
+}

docs/wiki/index.md

@@ -0,0 +1,37 @@
+---
+title: "Wiki"
+---
+
+English version of the TAK Wiki, for Finnish version go to [HERE](https://pvarki.getoutline.com/doc/fi-VbAwTbzvUO).
+
+### @[What is TAK](wiki/what-is-tak)
+
+### @[TAK Products for Users](wiki/tak-products-for-users/)
+
+* @[ATAK - Android TAK](wiki/tak-products-for-users/atak-android-tak/)
+* @[iTAK - Apple TAK](wiki/tak-products-for-users/itak-apple-tak)
+* @[TAK Tracker - Lightweight TAK](wiki/tak-products-for-users/tak-tracker-lightweight-tak) - Android and Apple
+* @[VR-TAK - VirtualReality TAK](wiki/tak-products-for-users/vr-tak-virtualreality-tak)
+* @[WinTAK - Windows TAK](wiki/tak-products-for-users/wintak-windows-tak/)
+
+### @[TAK Tools for Products](wiki/tak-tools-for-products/)
+
+* **Tools**
+  * @[Bloodhound tool](wiki/tak-tools-for-products/bloodhound-tool)
+  * @[Contacts / GeoChat tool](wiki/tak-tools-for-products/contacts-geochat-tool)
+  * @[Point Dropper tool](wiki/tak-tools-for-products/point-dropper-tool)
+* **Plugins**
+  * @[Data Sync -plugin](wiki/tak-tools-for-products/data-sync-plugin)
+  * @[TAK Replay -plugin](wiki/tak-tools-for-products/tak-replay-plugin)
+  * @[UAS Tool -plugin](wiki/tak-tools-for-products/uas-tool-plugin)
+  * @[VNS -plugin](wiki/tak-tools-for-products/vns-plugin)
+
+### @[TAK Admin Tools](wiki/tak-admin-tools/)
+
+* @[Takserver](wiki/tak-admin-tools/takserver/)
+* @[Advanced Features](wiki/tak-admin-tools/advanced-features/)
+
+### @[Usage Models](wiki/usage-models/)
+
+* @[PVARKI Standard](wiki/usage-models/pvarki-standard/)
+* @[Use Cases](wiki/usage-models/use-cases/)

docs/wiki/tak-admin-tools/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "TAK Admin Tools",
+  "collapsed": true
+}

docs/wiki/tak-admin-tools/advanced-features/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Advanced Features",
+  "collapsed": true
+}

docs/wiki/tak-admin-tools/advanced-features/index.md

@@ -0,0 +1,10 @@
+---
+title: "Advanced Features"
+---
+
+Additional features for advanced admins. Not all of the features are final and finished.
+
+## Pages
+
+* @[MTX - Streaming](./mtx-streaming)
+* @[Keycloak - Group Management](./keycloak-group-management)

docs/wiki/tak-admin-tools/advanced-features/keycloak-group-management.md

@@ -0,0 +1,39 @@
+---
+title: "Keycloak - Group Management"
+---
+
+Current Rasenmaeher environment uses Keycloak to manage user groups. These groups are relayed to takserver and connected users get them automatically.
+
+The idea in long term is to get the group management to Rasenmaeher in some capacity.
+
+## Basic instructions:
+
+* Login to keycloak with kc.your-server.fi using the mtls certificate provided with Rasenmaeher.
+* Navigate to Groups on the sidebar
+* Navigate to tak Group to manage TAK Groups.
+* Create a group in the Child groups page of tak Group
+  * Naming has to be tak_groupname
+* Navigate to the new Group
+* Navigate to Members and Add member
+  * Choose users you want to add to the Group
+
+Users in the new Group that are connected to takserver will get the new Group
+
+\n ![](./_media/f48af8be-9172-47f5-a091-1e0f943729d9.png)
+
+ ![](./_media/c26fd666-474b-4c6b-80c8-ff06863fc59e.png)
+
+ ![](./_media/f1157d4a-765b-48a5-9274-ba8a04fc1640.png)
+
+ ![](./_media/94afeba3-357d-41a1-9197-65bdc2ee42b2.png)
+
+ ![](./_media/14d13002-7adc-4391-8981-d03a07900ecf.png)
+
+
+## Advanced instructions: (Write or Read Groups)
+
+Create Groups the same way as Basic instructions, but in the Group naming use _WRITE or _READ to specify how the users in the group are dealt with.
+
+tak_test_WRITE group users are sending information to test group but cannot receive information from it.\n\nThis feature can be used to let Command Post see everyone but only permitted users get the full access or read access to CP group. (tak_CP for Command Post personnel)
+
+ ![](./_media/eb55ed8d-199a-45dc-917b-b1079aff2760.png)

docs/wiki/tak-admin-tools/advanced-features/mtx-streaming.md

@@ -0,0 +1,27 @@
+---
+title: "MTX - Streaming"
+---
+
+MTX = MediaMTX is a videoserver that is used to stream live materials from users forward.
+
+
+### Currents Products supported or in evaluation
+
+* Opentak ICU
+* UAStool
+* ICU (not verified to work with credentials and encryption)
+* Helmcam (not verified to work with credentials and encryption)
+* GoPro
+* Browser
+* VLC
+
+### Current Protocols supported or in evaluation
+
+MTX Ports and Protocols
+
+* 1936 RTMPS
+* 8322 RTSPS
+* 8890 SRT
+* 9888 HSL
+* 9889 WebRTC
+* 9996 Playpack for videos

docs/wiki/tak-admin-tools/index.md

@@ -0,0 +1,17 @@
+---
+title: "TAK Admin Tools"
+---
+
+Instructions for PVARKI admin users about the functions of takserver and other features. For basic use these are not needed.
+
+## @[Takserver](./takserver/)
+
+* @[Basic UI](./takserver/basic-ui)
+* @[Update Server (OTA)](./takserver/update-server-ota)
+* @[Mission Manager (Data Sync)](./takserver/mission-manager-data-sync)
+* @[Device Profiles](./takserver/device-profiles)
+
+## @[Advanced Features](./advanced-features/)
+
+* @[MTX - Streaming](./advanced-features/mtx-streaming)
+* @[Keycloak - Group Management](./advanced-features/keycloak-group-management)

docs/wiki/tak-admin-tools/takserver/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Takserver",
+  "collapsed": true
+}

docs/wiki/tak-admin-tools/takserver/basic-ui.md

@@ -0,0 +1,18 @@
+---
+title: "Basic UI"
+---
+
+Takserver UI is found at tak.server.fi address on Rasenmaeher environment.
+
+
+ ![](./_media/508b5fa7-e7c0-42ce-aadc-6cc8ceb324bb.png)
+
+The dropdown menu on the right side is where the functions can found and the official tak.gov documentatio  is at the end "Documentation".
+
+
+ ![](./_media/f52117e5-e3a9-41c0-ae05-ddbd0c115905.png)
+
+
+\
+
+\

docs/wiki/tak-admin-tools/takserver/device-profiles.md

@@ -0,0 +1,24 @@
+---
+title: "Device Profiles"
+---
+
+Device Profiles are used to manage devices connected to takserver. Mainly ATAK as the device needs to support receiving profiles from the server.
+
+Device Profiles are made in the Device Profile Manager and are implemented on users in specified groups. The profiles can be shared to users with enrollment, connection to server or as a manual tool.
+
+The preferred format of shared settings is .pref files inside a TAK data package, as the packages can trigger import function in ATAK for the files inside the data package.
+
+
+ ![](./_media/7ac14247-68de-456f-9116-87ada5f1cbcb.png) ![](./_media/d41d3ed4-4d48-4799-bd4f-aa16f447efa4.png)
+
+#### Apply on Enrollment
+
+With username/password enrollment for certificate users can get settings for the EUD's. This is mainly used as first/minimum configuration for users in the server like update server, maps and toolbars for users.
+
+#### Apply on Connection
+
+User already enrolled or with connection via certificate can be have their configurations updated when they reconnect to takserver when needed. This can be used to provide needed changes or provide additional setting for additional features. Like Medic toolbar for users in Medic group or update the Mesh encryption key's when they are updated. 
+
+#### Tool
+
+Tool is used as a manual method of updating configurations or sharing files to specified users. Mainly as a forced update for users that haven't gotten the files with other methods.

docs/wiki/tak-admin-tools/takserver/index.md

@@ -0,0 +1,16 @@
+---
+title: "Takserver"
+---
+
+Available at:\n[https://tak.gov/products/tak-server](https://tak.gov/products/tak-server)
+
+## **Product Description**
+
+TAK Server is a tactical information management platform that provides data access and encryption across disparate networks. TAK Server secures, brokers, and stores data in standalone and federated configurations. It is required whenever TAK clients are not operating in a peer-to-peer network or there is an operational need to encrypt and store mission data. Client plugins, such as DataSync and Execution Checklist, also require TAK Server.
+
+## Pages:
+
+* @[Basic UI](./basic-ui)
+* @[Update Server (OTA)](./update-server-ota)
+* @[Mission Manager (Data Sync)](./mission-manager-data-sync)
+* @[Device Profiles](./device-profiles)

docs/wiki/tak-admin-tools/takserver/mission-manager-data-sync.md

@@ -0,0 +1,46 @@
+---
+title: "Mission Manager (Data Sync)"
+---
+
+Missions (Data Sync Feeds) are managed withing Mission Manager inside takserver UI.
+
+Mission Manager can be found  at https://tak.server.fi:8443/Marti/MissionManager.html
+
+
+ ![](./_media/55c76275-735d-417e-b9ba-9b2a863d343f.png)
+
+## Managing Missions
+
+Managing the Missions (Data Sync - Feeds) is done withing Takserver or with TAK Products in Data Sync tool. For Managing the Missions the user need either Owner or Write user rights for the feed. If you want to change your user rights check [Change User Rights](https://pvarki.getoutline.com/doc/mission-manager-data-sync-HdRqCuoE2v#h-change-user-rights).
+
+ ![](./_media/41f5fcb2-c3ec-4f44-b0f8-cf42cd76ea55.png)
+
+### Create Mission
+
+Admin users can create missions in the Takserver Mission Manager. Choose + ADD and fill the in what is wanted for the feed. If the defaultRole is set as ReadOnly, you will need to set Owner and/or ReadWrite users. For this check [Change User Rights](https://pvarki.getoutline.com/doc/mission-manager-data-sync-HdRqCuoE2v#h-change-user-rights).
+
+The main things to set for the Mission are the Name, possible Password, defaultRole and Groups. \nThe defaultRole sets the user rights for users that are subscribing to the feed: ReadOnly, ReadWrite, Owner..\nGroups setting defines what takserver groups will see the feed and can subscribe to it.
+
+ ![](./_media/3e917274-4ab9-4735-8280-42dc7e484759.png)
+
+### Delete Mission / Archive
+
+Deleting Missions is done with selecting the feeds and choosing Delete. The deleted feeds are kept in the Archived Missions so the data hasn't been removed from the server.
+
+ ![](./_media/41f5fcb2-c3ec-4f44-b0f8-cf42cd76ea55.png)
+
+### Edit Mission
+
+Editing mission via takserver is done from the Mission Manager, choose the feeds that are desired to change and change the settings. Select Save and Close after the changes are done.
+
+ ![](./_media/57c0df67-af80-4387-8f30-2fcb7e3cbab9.png)
+
+### Change User Rights
+
+If the RECON feed is needed to be ReadOnly for basic users, at least one of the admins needs to be set as Owner for the feed so they can manage it.
+
+To get user to be the Owner from takserver the feed needs to be edited to use the defaultRole of Owner and the wanted user needs to subscribe to the feed to get the rights. After all the needed users have the needed Role the setting can be changed back to what is needed for the other users.
+
+Owners can change other users Roles withing the data sync -plugin and manage the users by inviting them or removing them from the feed. Changing the role is done within the feed settings in the Active Members menu via the key-icon.
+
+ ![](./_media/752b45f5-b4b0-4c0d-a00d-dce19f7e880a.png) ![](./_media/a3662bf8-332d-4822-9e63-71d3e681a658.png)

docs/wiki/tak-admin-tools/takserver/update-server-ota.md

@@ -0,0 +1,41 @@
+---
+title: "Update Server (OTA)"
+---
+
+Takserver has a feature to provide updates to ATAK applications and plugins with takserver connection. When users are connected to takserver with the service enabled, they can update and install applications and plugins from Plugins Tools (TAK Package Mgmt).
+
+
+Currently PVARKI is providing ATAK -app and Data Sync -plugin for installing and updating.
+
+
+There is a plan to have a portal for admin to update/add/remove the .apk files shared to clients but this function is not on the road map yet. List on some of the available plugins is @[Plugin list](../../tak-products-for-users/atak-android-tak/plugin-list).
+
+### Current way of managing plugins inside Rasenmaeher
+
+Admin need ssh root access to server!
+
+
+Add .apk' to /tmp/update and run taktool pp, inside the folder. Move the folder to mapped location and fix permissions.
+
+```javascript
+cd /tmp/  
+taktool pp
+sudo cp -r update /opt/docker-rasenmaeher-integration/takserver/  
+sudo chmod 755 /opt/docker-rasenmaeher-integration/takserver/update -R 
+```
+
+Restart takserver instance inside Rasenmaeher
+
+
+### Preparing the needed files for Update folder
+
+Needed files:
+
+* APK -files
+* product.infz file
+  * zip file including product.inf file and the apk icons.
+
+
+### Later on the roadmap / preliminary plan
+
+Current idea is to have a webpage inside Rasenmaeher where you can manage the .apk files and upload new ones when needed. Taktool should be part of that so when there are changes in the files it would be run automatically or prompted to admin to run.

docs/wiki/tak-products-for-users/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "TAK Products for Users",
+  "collapsed": true
+}

docs/wiki/tak-products-for-users/atak-android-tak/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "ATAK - Android TAK",
+  "collapsed": true
+}

docs/wiki/tak-products-for-users/atak-android-tak/index.md

@@ -0,0 +1,27 @@
+---
+title: "ATAK - Android TAK"
+---
+
+Product available:
+
+[https://tak.gov/products/atak-civ](https://tak.gov/products/atak-civ)
+
+[https://play.google.com/store/apps/details?id=com.atakmap.app.civ](https://play.google.com/store/apps/details?id=com.atakmap.app.civ)
+
+## Product manual
+
+[ATAK 5.5 User Guide.pdf 4198740](/api/attachments.redirect?id=554b4fa7-2aa0-4866-ad7e-7f94304c76d2)
+
+## **Product Description**
+
+The Android Team Awareness Kit (ATAK-CIV) offers matching capabilities to the ATAK-MIL baseline with minor changes from the military lexicon. TAK-CIV is made available to support the principles of civil authority emergency operations: prevention, mitigation, preparation, response, or emergency evacuation and recovery. The primary difference between MIL & CIV is the baseline signing key that restricts military specific capability from being loaded through plugins. Just like ATAK-MIL, ATAK-CIV is network-agnostic and works with many tactical communication systems. ATAK-CIV supports DoD and commercial formatted maps, imagery, and overlays. Where possible, the ATAK application adheres to the user experience design guidelines produced by Google to ensure that end users have a familiar experience.
+
+## **System Requirements**
+
+ATAK System Requirements
+
+* Operating System: ATAK requires Android 5.0 (API 21) or later.
+* Hardware: ATAK does not require specific hardware and should run on any Android device that supports the other System Requirements.
+* Graphics: ATAK requires a graphics processor that supports GLES 3.0.
+* Storage, Memory and Processor: ATAK does not have any specific requirements for storage, memory or processor, however, performance of the application will depend on the configuration.
+* Examples of Devices: Testing of TAK is generally done across a range of Samsung devices since they are primarily what has been fielded. That being said, TAK works on other non-Samsung devices. For a small phone style device the Samsung S5 equivalent hardware or newer is required and for a tablet style device Samsung Tab S equivalent or newer. It is recommended: for optimal experience, at least a Samsung S9 equivalent hardware or newer is used and for a tablet style device Samsung S2 equivalent or newer.