1 / 9

Analysis for the Strike Package Coordination (TAR11) Candidate

Analysis for the Strike Package Coordination (TAR11) Candidate. POC: G. Shea. TAR11 Overview. Summary Descriptionp Strike Package Coordination

winter
Download Presentation

Analysis for the Strike Package Coordination (TAR11) Candidate

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. Analysis for theStrike Package Coordination(TAR11) Candidate POC: G. Shea

  2. TAR11 Overview • Summary Descriptionp • Strike Package Coordination • Provide the capability to have all tasked timing be based off of the Strike Reference Time (SRT) in the Strike Package (SP). This would be received electronically in a SP or performed as an edit to an existing SP. • Provide Composite Allowable Launch Area (LCALA), Composite Launch Basket (CLB), and Conflict Identification Analysis (CIA) across multiple SPs. • Fix several problems with the Allowable Launch Area (ALA) calculations and display. • Fleet Benefit • Provides a means to move the entire launch time of all tasks within a SP without having to send a complete revision to the SP or have the operator manually computing and editing each tasked time in the SP. Provide Strike Coordination across multiple SPs. Fix ALA calculations and display problems. • Fleet Importance: Medium • CR Summary • Adaptive: 1 (External) • Perfective: 4 • Corrective: 1 • TOTAL: 6

  3. TAR11 Analysis • Technical Description • Strike Package Coordination • Provide the capability to have all tasked timing be based off of the Strike Reference Time (SRT) in the Strike Package (SP). This would be received electronically in a SP or performed as an edit to an existing SP. • Provide Composite Allowable Launch Area (LCALA), Composite Launch Basket (CLB), and Conflict Identification Analysis (CIA) across multiple SPs. • Fix several problems with the Allowable Launch Area (ALA) calculations and display. • Effort: Medium • Size: High (rate Low (<100 SLOC), Medium (<500 SLOC) or High (>500 SLOC)) • Complexity: Medium (rate Low (easy changes to implement), Medium (average changes to implement), High (difficult changes to implement)) • External Dependencies: Item #1 requires an ICN to 3900/146 (existing external CR 11253), and requires an IFIR) • Risk: High (due to ICN required to PEO(W) 3900/146 • Addresses 6 CR Eliminates 0 TTBs/TIP entries

  4. TAR11 Recommendation • Recommendation Implement in v6 Defer for future consideration • Rationale • Candidate #1 has been suggested by the Captain and by PMA-281 as a viable way to move the entire launch time of a SP without putting a load on the operator. • Candidate #2 is neede fot the operator to be able to perform Strike Coordination operations across multiple SPs. • Candidate #3 is needed to fix ALA calculation and display problems. • Issues • Believe Item # 1 (SRT) should be a candidate by itself. If the ICN is not approved, TTWCS can still do the edit to a SP.

  5. Backup Slides(TAR11)

  6. CR # Class TIP Description Disposition 11312 P Suggestion for SP edit: The system should provide a global change launch time and timing type capability. This might be invoked via either the Task Manager or the edit SP window. If the Captain's scenario of changing launch time from 1800Z to 1730Z occurs with the current edit capability, this would take the operator about 15 minutes with a 32-missile SP and is very error prone. Addressed in Candidate 11400 P Reference V5 SDR Action 62 The operator should have the capability to view several ESPs engagements in the composite launch basket, ALA and CIA windows. Existing v4 capability and existing v5 prototypes would limit these functions to use on a single SP. Addressed in Candidate 10622 P To find the composite launch basket for 60 missions the operator has to developed 5 ESP's with 12 missions each so we could evaluate what our PLP would be. Which by the way I think this is the only way the boat can evaluate this many missions which I feel is too hard. Once all 5 ESP's were sent into TTWCS we could only use the Composite Launch Basket Analysis tool for one ESP at a time which I also feel is to hard. If the operator wanted to find the composite launch basket the TTWCS operator would need to evaluate the first 2 ESP's and create a PLP overlay and then look at the other ESP's to determine the best PLP. TTWCS should allow the operator to use the Composite Launch Basket Analysis tool for more than one ESP. Addressed in Candidate 10927 P 28012300Z AUG 03 Transmitted ESP with 1 BLK LPMP and 1 BLK IV CFF. 28012700Z AUG 03 Created CFF and build LPMP. Attempted to perform CALA using the ESP twice and failed twice. The chart inset would open but the ALA would never be displayed. The error message "Unable to calculate ALA" was displayed. Mission Criticality: Yes Mission Critical Level: Level 2 Critical Operational Items (COIs) Affected: Strike Coordination Affected DE: 124 Addressed in Candidate TAR11CR Summary

  7. CR # Class TIP Description Disposition 11157 C The following things were observed about the composite ALA window which will lead to operator confusion: 1. The operator can sort the aimpoints based on launch position type, aimpoint, or launch position. When the operator hits update chart, the window resorts based on aimpoint sequence number. 2. When this resort is done, the window does not remember what was selected. Whatever is in the spaces that were selected before the sort is highlighted. 3. The window puts asterisks next to the selected items when the update chart is hit. Item 2 applies to where the asterisks are put in the window. 4. When a change is applied, the asterisks are ignored and whatever is highlighted is set to the new launch type and position. Addressed in Candidate 11253 EXT This is a PR in the DRB 119 and MDS 1735-SA. This would effect TTWCS is fixed. MDS does not change Time at Timing Point for missile assignments in a strike package in Execute state, based solely on a strike package that only contains a Strike Package Definition Table (SPDT)specifying a new Strike Reference Time (SRT). The concept behind SRT is to enable the TSC to move all assignments in the strike in time, without needing to modify each assignment and retransmit the strike package. 3900/146 specifies the capability to send an SPDT-only strike package to all TTWCS FRUs in order to change TSN COMSEC, TSN TRANSEC, and/or the Strike Reference Time without having to send a new strike package revision. This was intended to save time and effort at each node participating in the strike when the inevitable time changes arose. MDS did not implement it this way. Within the strike package, MDS provides the capability to shift all missile assignment times by changing a single time value, effectively slewing the strike in time. However, this is performed during strike planning and coordination prior to strike execution. Once assignment times have been established and the strike package has been saved, distributed and placed in Execute state, MDS does not change Time at Timing Point for the assignments in that strike package based on a change to SRT. Any change to missile assignments governed by a strike package in execute state will require MDS to issue a rev. This results in a loss of comms plans at TTWCS for LPMP assignments. External CR that would effect item #1 in its design and implementation TAR11CR Summary (Con)

  8. TAR11 – Design Concept • CR 11312 & External CR 11253 – Provide the capability to have all tasked timing be based off of the Strike Reference Time (SRT) in the Strike Package (SP). This would be received electronically in a SP or performed as an edit to an existing SP. • Tasked times in the SP would be Delta times based off of the SRT in the SP. This could only occur if the SP was at a Use State of Launch Plan or Hold Fire. • TTWCS would compute the actual tasked times for each engagement. • When an Revision to the SP is received with the SRT changed, TTWCS shall update all the tasked times for each engagement and replan the engagement based on the updated time. LPMP missions may have to be recreated or verified as still valid. • A manual edit to the SRT in an existing SP, shall achieve the same results. • Addressed in the White Paper • CR 11400 & 10622 – Provide Composite Allowable Launch Area (LCALA), Composite Launch Basket (CLB), and Conflict Identification Analysis (CIA) across multiple SPs. • See CRs as to the fix required. • CR 10927 & 11157 – Fix several problems with the Allowable Launch Area (ALA) calculations and display. • See CRs as to the fix required.

  9. Risk and Effort Assessment Guidance • Low • Candidate is very well defined/understood • No issues are identified • Effort is Low (Size = Low AND Complexity = Low OR Size = Low AND Complexity = Medium OR Size = Medium AND Complexity = Low) • Medium • Candidate is defined/understood • Minor issues are identified • Effort is Medium (Size = Low AND Complexity = High OR Size = Medium AND Complexity = Medium OR Size = High and Complexity = Low) • High • Candidate is not fully defined/understood • Major issues are identified • Effort is High (Size = Medium AND Complexity = High OR Size = High AND Complexity = Medium OR Size = High AND Complexity = High)

More Related