30 likes | 217 Vues
SOUTHCOM OPERATIONAL SCENARIO. TIGR 710 Server set up in Miami Local SOUTHCOM TIGR Server Set to Sync to Miami Server SOUTHCOM troops prepare either a TIGR Laptop or TIGR HH for mission Troops deploy on Mission with TIGR (Laptop or HH)
E N D
SOUTHCOM OPERATIONAL SCENARIO • TIGR 710 Server set up in Miami • Local SOUTHCOM TIGR Server Set to Sync to Miami Server • SOUTHCOM troops prepare either a TIGR Laptop or TIGR HH for mission • Troops deploy on Mission with TIGR (Laptop or HH) • (Optional) When events are captured, they are synced over the air with local TIGR Server • When troops return from Mission new or modified TIGR (Laptop or HH) information is sneaker netted to local server • Local Server syncs with Miami Server
Basic Operating Environment (Disconnected) Pre-mission TIGR TOC User Creates Mission data in TIGR TOC application and stores as .tgm. Mission data includes:Sneakernet, MAPS, PatrolView and Personality (Types and Categories 1 TIGR TOC TIGR HH user connects HH device to TIGR TOC VIA USB and downloads mission data to HH device via PC command dataloader install 2 In-Mission TIGR HH user uses high quality maps, and existing TIGR information for SA TIGR HH user creates additional ASCOPE elements to be use for analysis and future missions. 4 5 Post Mission Post Mission TIGR HH user returns to FOB. Connects HH to PC via USB and new TIGR Sneakernet data is uploaded to the TIGR TOC 6
Basic Operating Environment (Connected) Pre-mission Same as Disconnected In-Mission Same as Disconnected 5* New events are synched to TIGR TOC Server when over the air connectivity is available Post Mission 1 6 4 5 2 TIGR HH user returns to FOB. Connects HH to PC via USB and TIGR Sneakernet data is uploaded to the TIGR TOC (If it has not already been synced over the air) TIGR TOC