1 / 24

TC2S XX/TTWCS V5 Requirements Discussion

TC2S XX/TTWCS V5 Requirements Discussion. Roger Newton NSWCDD K704 Dec 20, 02. SSGN ORD Phase 2 Requirements. Task 156 missiles with new SSGN cell configuration Modify MLOSRF-T, PLR, LER, Strike package, etc. to incorporate SSGN cell configuration Update Location codes for SSGNs.

hafwen
Download Presentation

TC2S XX/TTWCS V5 Requirements Discussion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TC2S XX/TTWCS V5Requirements Discussion Roger Newton NSWCDD K704 Dec 20, 02 3900/146 IWG

  2. SSGNORD Phase 2 Requirements • Task 156 missiles with new SSGN cell configuration • Modify MLOSRF-T, PLR, LER, Strike package, etc. to incorporate SSGN cell configuration • Update Location codes for SSGNs 3900/146 IWG

  3. TTPVORD Phase 2 Requirements DELET THIS SLIDE • Task RGM-109H missiles • Modify MLOSRF-T, PLR, LER, Strike package, etc. to incorporate RGM-109H • Create and transmit RGM-109H mission data • Create new PCTs • No LPMP, CFF, aimpoint update, or retargeting tasking • Expecting a common OES (testing impacts) 3900/146 IWG

  4. TTLORD Phase 2 Requirements • Task Block IV TTL missiles 3900/146 IWG

  5. Receipt of LPMP Missions ORD Phase 2 Requirements • If necessary, change both TTWCS and TC2S to be able to receive and process the LPMP and Retarget missions • Also a fleet request • Need to define the CONOPS for operation • Could be after-the-fact 3900/146 IWG

  6. P3I CANDIDATE #1 OtherFRU/Ghost tasking Verification Problem Statement: Current Fleet Doctrine requires that each FRU tasked in an INDIGO/LSP determine what tasking it can do in a backup role for the complete tasking in the INDIGO/LSP and in the TTWCS timeframe they will want to continue the process of verification of other FRU tasking whether it be another TTWCS or ATWCS or TWCS FRU. Also current Fleet Doctrine uses Ghost tasking to see what each FRU can do. New Capability Description: TC2S will have the capability to send ATTWCS, TWCS, and Ghost tasking in an ESP. TWCS will verify other FRU/Ghost tasking (have the mission onboard, can reach the launch basket, and have “a” missile of the type required available) in the ESP and then provide exceptions for items it cannot perform via an Exception (modified) Report. TC2S will have the information available to be displayed to the TSC/LAC which FRU can back up another FRU’s tasking and which FRU can perform the Ghost tasking. Requirements:Requires an ICN to 3900/146 to modify the Exception Report for tasking verification. Requires TTWCS to perform the tasking verification. Requires PC-MDS to be able to task ATWCS & TWCS tasking in an ESP. Requires PC-MDS to be able to display the tasking verification to the TSC/LAC. Issues:None Possibly more exception codes. Operational Impact:If not done, would be very hard for the FRU & TSC/LAC to continue following the current doctrine as it would all have to be accomplished via voice/workarounds that are very tedious and time consuming. 3900/146 IWG

  7. P3I CANDIDATE #2FDU capability for updating Location Codes Problem Statement: Currently the only way to update the Location Codes within TTWCS is to provide a new software build. New Capability Description: TC2S will have the capability to send a FDU to TTWCS with all the Location Codes and Names and corresponding SIDs. TTWCS will receive this FDU and replace the existing Location Code table with the new one. Requirements:Requires an ICN to 3900/146 to add a FDU for Location Codes and SIDs. Requires PC-MDS to be able to formulate and transmit the FDU upon operator selection. Requires TTWCS to receive the FDU and update its Location Code/SID table. Issues:None Operational Impact:If not done, it is very costly & time consuming to make a modification to the Location Code table. 3900/146 IWG

  8. P3I CANDIDATE #3 Common and UniqueESP ASNs and INDIGO TLDs Problem Statement: Current Fleet Doctrine requires that each FRU tasked in an INDIGO/LSP be able to perform backup tasking via voice tasking. This is accomplished by using the TLD in the INDIGO message. In the initial TTWCS timeframe the Fleet wants to continue the process of voice tasking for backups due to the many ATWCS & TWCS platforms (Interoperability issue). New Capability Description: TC2S will have the capability to use common and unique ASNs and TLDs. Requirements:Requires PC-MDS to be able to formulate ESPs and INDIGOs such that they have will have the capability to use common and unique ASNs and TLDs. Issues:None If length of ASN changes then could be an impact to non-V5 TTWCS FRUs Operational Impact:If not done, would be very hard for the FRU & TSC/LAC to continue following the current doctrine of voice tasking backups as the ASNs and TLDs would not be common or unique. 3900/146 IWG

  9. P3I CANDIDATE #4 • Web based data pool • (TTWCS ACK) Add ability to put into message which parts of the FDU are missing (similar to a UER message). Also only send one TACK for an FDU when the FDU has been completed or timed out after an error in the message. (not one for each part) • (TC2S ACK) Modify the same as TACK. Also Word 13 needs clarification • Add the capability to transmit BDII off the platform. DO WE WANT THIS • If comms planning is to be done on the FRU, then what is required in the MIO must be specified. • Pool missiles are to be used as Rolling Ready Spares and tasking must provide for their identification. • Modify range of both DB Extract and Update Version Ids to include zero. • Every time a Strike Package, Revision, or Manual update occurs, a validation of all SPs within TTWCS will occur and an Exception Report will be sent for each SP. • LMO possible additions: • When to auto-generate FPPWP • Tasked time – TOT/TOS/TOA • LMO Tactical Change possible additions: • Include flight altitude for Aimpoint Update • Departure point for Retarget • Time for AU departure (maybe- not before or not later then) • Flag to ignore threats or maybe only ignore threats if retarget route can’t be generated 3900/146 IWG

  10. P3I CANDIDATE #5New DBRI Supplemental Message Problem Statement: Current DBRI message does not contain enough information to resync the PC-MDS & TTWCS databases in the case of major failures. New Capability Description: A new DBRI supplemental message would be added that details all of the files actually contained on the PML. Another option would be to replace the current DBRI with a MAF type message. The PC-MDS operator could either request the transmission of the message or it could be initiated by the TTWCS operator. Requirements:Requires an ICN to 3900/146 to add a new DBRI supplemental type message. Requires TTWCS to formulate this message and send to PC-MDS. Requires PC-MDS to be able to receive the message and be able to re-establish actually what TTWCS is contained in the TTWCS databases. Issues:None Operational Impact:If not done, it would be very hard to resync the PC-MDS & TTWCS databases in the case of major failures. 3900/146 IWG

  11. P3I CANDIDATE #6Clarification of Missile Status Problem Statement: Currently in 3900/146 there is no description of what the FRU is to do with the missile when tasking is modified(for example, canceled) . New Capability Description: 3900/146 will be modified to delineate the state of a missile after every ESP transition. Requirements:Requires an ICN to 3900/146 to delineate what the FRU is to do with the missile after every Use State transition of the ESP. Issues:None Operational Impact:If not done, whatever is currently being done with the missile will continue. THIS IS NOT IN TAR 3900/146 IWG

  12. P3I CANDIDATE #7SP Cancel for individual FRU Problem Statement: Currently in 3900/146 there is no way to cancel only one FRU, out of many, in an ESP. New Capability Description: 3900/146 will be modified to be capable of deleting only one FRU from a multi-FRU ESP. Requirements:Requires an ICN to 3900/146 modify the ESP so that one FRU can be deleted from a Strike Package at a time. Issues:None Operational Impact:If not done, whatever is currently being done to delete a FRU from the ESP will continue. 3900/146 IWG

  13. P3I CANDIDATE #8ESP with Common Name Problem Statement: The ESP currently contains just a location code vice a common name for whoever is sending the strike package. New Capability Description: 3900/146 will be modified to be capable of deleting only one FRU from a multi-FRU ESP. Requirements:Requires an ICN to 3900/146 modify the ESP for common names. Issues:This could be handled in TTWCS from the location code table. Operational Impact:If not done, location code will continue to be shown. DO WE NEED THIS ??? 3900/146 IWG

  14. P3I CANDIDATE #9Post Strike Report Problem Statement: Current Post Strike report does not contain enough information for the Block IV missile after launch (i.e. new target location, comms status, BDII). status at the conclusion of the strike (per Strike Package or Secondary Execution) New Capability Description: TTWCS will send a Post Strike Report at the conclusion of a strike (all tasking completed in an ESP) or by operator action for each ESP or Secondary Execution. The report will contain flex, retargeting, aim-point update information, and BDI data at a minimum for each tasked Block IV missile. PC-MDS will receive this report, process it, and display information to the operator. Requirements:Requires an ICN to 3900/146 modify the ESP for common names. Requires TTWCS to formulate the report and send it. Requires PC-MDS to receive, process, and display the report. Issues:None Operational Impact:If not done, post strike data will not be accurately reported electronically and will have to be reported manually. 3900/146 IWG

  15. P3I CANDIDATE #10LMO Modify Missile Control after Launch Problem Statement: Current tasking process requires a complete update of the ESP to the FRU to modify missile control for a particular missile after launch. This involves a lot of data being sent on the circuit. The current implementation can only be for taking control away from the FRU. New Capability Description: TC2S will send a LMO (Tactical Change) to remove or task missile control after launch Requirements:Requires an ICN to 3900/146 modify the LMO (Tactical Change) to task or remove control. Requires TTWCS to receive and process the message. Requires PC-MDS to send a LMO after launch to change missile control. Issues:Addresses only LPMP tasking and not preplanned mission tasking. Operational Impact:If not done, more data must be transmitted on the comms circuit. 3900/146 IWG

  16. P3I CANDIDATE #11TIR as a formatted message Problem Statement: Currently the Tomahawk Information Report (TIR) is only transmitted as an OPNOTE and when modified TTWCS software must be modified to accommodate the new message structure. New Capability Description: TTWCS will send a 3900/146 formatted message that will contain the same information and will therefore stop software from having to be modified. Requirements:Requires an ICN to 3900/146 to add a new message, TIR. Requires TTWCS to formulate and send the message. Requires PC-MDS to receive, process and display the TIR. Issues:None. Operational Impact:If not done, the TIR will continue to change without being under TWS control. BELIEVE WE SHOULD DELETE THIS ONE 3900/146 IWG

  17. P3I CANDIDATE #12TTWCS/TC2S PING over TSN Problem Statement: Currently the is not a way to verify that TTWCS or PC-MDS has connectivity over the TSN before missile launch . New Capability Description: TTWCS or PC-MDS will send a 3900/146 formatted message over the TSN to the other one and that one will respond with a message back to the sender. This will enable the operators to verify that they have connectivity over the TSN. Requirements:Requires an ICN to 3900/146 to add a new message and reply for TTWCS and PC-MDS. Requires TTWCS to formulate and send the message or receive and process the message. Requires PC-MDS to formulate and send the message or receive, process the message. Issues:None. Operational Impact:If not done, the TWS will not know if TTWCS or PC-MDS has TSN connectivity. 3900/146 IWG

  18. P3I CANDIDATE #12TTWCS/TC2S PING over TSN Problem Statement: Currently the is not a way to verify that TTWCS or PC-MDS has connectivity over the TSN before missile launch . New Capability Description: TTWCS or PC-MDS will send a 3900/146 formatted message over the TSN to the other one and that one will respond with a message back to the sender. This will enable the operators to verify that they have connectivity over the TSN. Requirements:Requires an ICN to 3900/146 to add a new message and reply for TTWCS and PC-MDS. Requires TTWCS to formulate and send the message or receive and process the message. Requires PC-MDS to formulate and send the message or receive, process the message. Issues:None. Operational Impact:If not done, the TWS will not know if TTWCS or PC-MDS has TSN connectivity. DUPLICATE - DELETE 3900/146 IWG

  19. Deferred 3900/146 Item #1Launch Exception Report Problem Statement:The Launch Exception Report was deferred by TTWCS in phase I. Currently the only way to get a Launch Exception Report is by voice. New Capability Description: TTWCS will implement the current design in 3900/146 and transmit a launch exception whenever a missile fails to launch and provide reasons for failure. Requirements:Requires an ICN to 3900/146 to add a new message and reply for TTWCS and PC-MDS. Requires TTWCS to formulate and send the message. Requires PC-MDS to receive and process the message and to act upon the result to transmit Secondary Execution messages or additional ESP. Issues:Possibly more launch exception codes. Operational Impact:If not done, the TWS will continue to use the voice/manual method of launching the backup for missile launch failures. 3900/146 IWG

  20. Deferred 3900/146 Item #2Tasking by Tail number, Cell, and TTL Problem Statement:Tasking by Tail number, Cell/TTL, or XMID was deferred in Phase 1 by TTWCS. New Capability Description: TC2S will be able to task in the ESP by eitherTail number, Cell/TTL, or XMID. TWCS will process the ESP and provide exceptions for any tasking that cannot be meet as tasked. (i.e. if tasked cell is not available, the tasking will be exempted.) Requirements:Requires an ICN to 3900/146 to remove exemption from TTWCS. Requires PC-MDS to be able to allow the operator to task by either Tail number, Cell/TTL, or XMIDin the ESP when desired. Requires TTWCS to accept tasking by Tail number, Cell, and TTL in the ESP and provide exceptions when required. [NOTE: tasking can only specify one.] Issues:Possibly could result in more tasking being exempted due to temporary faults in the system. What happens if the cell tasked fails during launch sequence? Can the operator select another and send a LER or something and continue on unless told not to? This needs further CONOPS Operational Impact:If not done, the TWS will continue to use the current method of tasking which is none missile specific. 3900/146 IWG

  21. Deferred 3900/146 Item #3Launch Area ACMS Problem Statement:Launch Area ACMS message was deferred by TTWCS in phase 1. New Capability Description: TC2S will be able to task a launch area to a FRU by sending it in a Launch Area ACMS message. TTWCS will use the Launch Area name specified in the ESP for engagement planning and if no name is specified, the FRU will continue EP processing as it currently does. Only one launch area will be valid per ESP which means that different ESPs can have different launch areas. Requirements:Requires an ICN to 3900/146 to: 1) Add the desired Launch Area name to the ESP; 2) Add a statement that if no name is specified in the ESP,the FRU will select his own launch area; 3) Add a statement that only one launch area will be valid for an ESP; 4) Launch Area ACMS must be received prior to the ESP otherwise the tasking for the FRU will be exempted. Requires PC-MDS to allow the operator to be able to select a Launch Area and be able to send the Launch Area ACMS to the FRU when desired. Requires TTWCS to accept the Launch Area ACMS message, process it, and use it in the engagement planning process. Issues:None Operational Impact:If not done, the TWS will continue to use the current method of selecting and using the launch area. 3900/146 IWG

  22. Deferred 3900/146 Item #4TTWCS Strike Package Problem Statement:TTWCS Strike Package message was deferred by TC2S in phase 1. New Capability Description: TC2S will be able to receive the TTWCS Strike Package transmitted by the FRU. TTWCS will use the Launch Area name specified in the ESP for engagement planning and if no name is specified, the FRU will continue EP processing as it currently does. Only one launch area will be valid per ESP which means that different ESPs can have different launch areas. Requirements:Requires an ICN to 3900/146 to remove exemption from TC2S. Requires PC-MDS to receive the TTWCS Strike Package and allow the operator to display it when desired. Issues:CONOPS required for the use of the TTWCS generated Strike Package. Fleet wants this implemented by has no requirements for its use except to be displayed to the TSC/LAC?? Operational Impact:If not done, ?? 3900/146 IWG

  23. Deferred 3900/146 Item #4 TC2S Compatibility Indicator Problem Statement:The TC2S Compatibility Indicator serves no purpose in TTWCS and should be removed/reserved. New Capability Description: None Requirements:Requires an ICN to 3900/146 to remove/reserve the TC2S Compatibility Indicator. Issues:None Operational Impact:If not done, ?? 3900/146 IWG

  24. TSN Related Items • Verify Alternate Strike Controller has TSN access (This could be accomplished by the TTWCS/TC2S Ping) • TTPV modified H&S requirements REMOVE 3900/146 IWG

More Related