Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
SOA PowerPoint Presentation

SOA

237 Views Download Presentation
Download Presentation

SOA

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SOA • CONOPS for TWS with a SOA implementation • Receive Missions and TCI data • Receive Strike Tasking • Information Reporting • Training

  2. Receive Missions and TCI • Preparation for Deployment • Receive MIDB Extract and Updates • Receive Updated DTED data • Load Missions and TCI data into TED using ATDCs • Load DTED into TED using ATDCs • Receive from command an updated VPL which is placed into the TED • Receive and load missiles on ship • Execute MIRS on the missiles using ATDCs • VML/VFIL/OES requested from TED • Data loaded on missiles • Missile Data is loaded into the TED • Prepare data in a service for Tomahawk Inventory Report

  3. Receive Missions and TCI • Preparation for INCHOP • Receive ACMSs and Overlays • Data stored in TED • Receive E-Mail about planning constraints • Update planning constraints • Receive Mission and TCI updates and store in TED • If OES/PCT/VMIL/VFIL updates, need to rerun MIRS • If rerunning MIRS update TED with inventory data • Preparation for Strike • Create new timeline event record • Update all parameters, based on Tactical Guidance and LAC Intentions • Check missile inventory, shipboard status, and interfaces for an active status • Load CRYPTO data based on communication guidance.

  4. Receive Strike Tasking • Verbal/Paper Tasking Received • Operator creates a strike folder on MDS from the ATDCs • The strike folder is completed and saved • Strike folder is sent up the change of command • System indicates that strike is ready • System requests the tasking lines from the strike folder • Missions are requests from the TED associated with the tasking • Allocation is done of the tasking line specified • Problems are recorded into the TED against the specified tasking • Exceptions are sent up the chain of command • Based on operator settings either the engagements are created or created after the operator requests they be created. • System requests ACMSs and Overlays from the TED • System requests surface tracks from the NCES in the AOI. • System creates engagements

  5. Receive Strike Tasking • Verbal/Paper Tasking Received (Continued) • Operator reviews the created engagements • Makes any changes necessary to meet tactical guidance. • Operator request a OTW be produced • System creates a CRD file and stores the OTW in the TED. The TED provides updates to the higher command • Operator requests pairing missiles to tasking plans • Operator pairs plans to missiles • Missiles begin powering up. • Operator monitors the missile to be able to respond to faults. • Operator performs a final review of the tasking lines • System requests ACMSs and Overlays from the TED • System requests surface tracks from the NCES in the AOI. • System updates the engagement track with the new data • Operator updates the engagement based on tactical guidance. • Operator requests a new OTW be produced

  6. Receive Strike Tasking • Verbal/Paper Tasking Received (Continued) • System creates a CRD file and stores the OTW in the TED. The TED provides updates to the higher command • Operator requests launching missile • System issues commands to launch missile • Missile is launched • System loads the data into the TED. TED provides updates to the higher command • Inventory is updated in the TED. TED provides updates to the higher command • Operator updates missiles after launch. • Operator enters information of missile failure to transition to cruise. • Operator monitors the missile in flight request data from the TED.

  7. Receive Strike Tasking • Verbal/Paper Tasking Received (Continued) • In response to verbal tasking, the operator request a redirection. • From the Strike Monitor window the operator selects the correct tasking line and does an aimpoint update/retarget/flex base on conditions and tactical guidance. • System processes the request and issues the IMMM to the missile • Missile responds the IMMM and persecutes the new target. • On completion of all tasking the Operator removes the strike folder from the system using the ATDC. • On indication of removal of the strike folder from system the system removes tasking from windows.

  8. Receive Strike Tasking • Electronic Tasking Received • The strike folder is received and stored into the TED • System indicates that strike is ready • System requests the tasking lines from the strike folder • Missions are requests from the TED associated with the tasking • Allocation is done of the tasking line specified • Problems are recorded into the TED against the specified tasking • Exceptions are sent up the chain of command • Based on operator settings either the engagements are created or created after the operator requests they be created. • System requests ACMSs and Overlays from the TED • System requests surface tracks from the NCES in the AOI. • System creates engagements

  9. Receive Strike Tasking • Electronic Tasking Received (continue) • Operator reviews the created engagements • Makes any changes necessary to meet tactical guidance. • Operator request a OTW be produced • System creates a CRD file and stores the OTW in the TED. The TED provides updates to the higher command • Operator requests pairing missiles to tasking plans • Operator pairs plans to missiles • Missiles begin powering up. • Operator monitors the missile to be able to respond to faults. • Operator performs a final review of the tasking lines • System requests ACMSs and Overlays from the TED • System requests surface tracks from the NCES in the AOI. • System updates the engagement track with the new data • Operator updates the engagement based on tactical guidance. • Operator requests a new OTW be produced

  10. Receive Strike Tasking • Electronic Tasking Received (continue) • System creates a CRD file and stores the OTW in the TED. The TED provides updates to the higher command • Operator requests launching missile • System issues commands to launch missile • Missile is launched • System loads the data into the TED. TED provides updates to the higher command • Inventory is updated in the TED. TED provides updates to the higher command • Operator updates missiles after launch. • Operator enters information of missile failure to transition to cruise. • Operator monitors the missile in flight request data from the TED.

  11. Receive Strike Tasking • Electronic Tasking Received (continue) • An updated strike folder is received to redirect a missile. • System processes the request and issues the IMMM to the missile • Missile responds the IMMM and persecutes the new target. • On completion of all tasking the Operator removes the strike folder from the system using the ATDC. • On indication of removal of the strike folder from system the system removes tasking from windows.

  12. Receive Strike Tasking • LPMP • Objective arrives as either electronic tasking or manually tasking, the system request an mission planning task to begin. The task is completed and stored into the TED. • All other actions are the same as electronic or manual tasking.

  13. Information Reporting • TIR • Data from inventory and mission TCI are loaded into the TED • Data is pulled from the little TED to the big TED • MDS prepares the TIR • MLOSRF-T • Missile data is loaded into the TED • Data is pulled from the little TED to the big TED • TAF • Since all TCI data is loaded into the TED no need for an TAF • ACMS-R • Since all ACMS data is loaded into the TED no need for an ACMS-R • Exception Report • MDS validate the strike folder • Allocation and engagement errors are stored into the TED • Data is pulled from the little TED to the big TED

  14. Information Reporting • SCOs • Create OWR in CRD format and store in the TED • Create a service to allow the GCCS-M system to pull data. • LER • Upon launch success or failure state is stored into the TED • Need an HCI for operator input for failure to transition to cruise to be stored into the TED • Data is pulled from the little TED to the big TED • PLR • Since all launch information is being stored into the TED for the LER no need for a post launch report • Data is pulled from the little TED to the big TED • PSR • Since a PSR is a PLR with free text at the end and since we no longer are handling post launch processing this report will come from the TED.

  15. Information Reporting • Free Text • MDS has free text with e-mail • Manual Strike Package • Since the manual strike folder is created and stored on the TED it can be pulled to the big TED.

  16. Training • Single Ship Training • The training lead on the ship setup a training objective on the CTN laptop • The trainer puts together an inventory to meet the training objective. • The trainer decides to either using existing world tracks or constructs a track scenario • The trainer decides to either using TSRT or internal PLE for Post Launch • The trainer logs into the MTC and logs onto the MDS to construct the strike package(s), ACMS(s), and Overlay(s) to meet the training objective • The trainer retrieves the strike information from the MDS. • The trainer places any need faults into the inventory • The crew is called to conduct training • The CTN is plug into the LAN

  17. Training • Single Ship Training (continuing) • The scenario is started • Inventory is established • Ships position is established • ACMS(S) and Overlay(s) are sent in to established the situational constraints • The track scenario is started • From the MTC the MDS is displayed and the first strike package is sent in. • The operators review allocation, create engagements, review engagements, pair missiles, monitor powering missiles, respond to faults, launch missiles, respond to added tasking. • The data is collected from MDS and TTWCS onto the CTN • The trainer assess the training and the crew respond • The crew and command is informed of the results

  18. Training • Multi Ship Training • The trainer setup the objective for the test • Determines who is participating in the test • Creates inventories for all the participating FRUs • Creates the strike package, ACMSs, and overlay(s) needed for the test • The trainer retrieves the strike information from the MDS. • The trainer places any need faults into the inventory • The trainer sends inventories to the participating FRUs CTN • The trainer on the ships plug in their CTN laptops and start the scenario. • The inventories are done, the real world track picture is being broadcasted, the ship position are determine. • The CTNs on the FRUs are receiving updates from TTWCS/MDS • The operators are on the ATDC logged into both TTWCS and MDS

  19. Training • Multi Ship Training (continue) • The lead trainer request the TA operator to send the strike package. • Normal operation continues with validation, allocation, mission creation, engagement creation, powering missiles, launching, and post launch processing • Data is collected at all the nodes and sent to a coordinating node for evaluation and a report