80 likes | 261 Views
Analysis for the Strike Coordination Support (LMC04) Candidate. POC: G. Shea. LMC04 Overview. Summary Description Description: Provide the ability for LPMP to use a route altitude and route type received from TC2S in a Tactical Change LMO. Fleet Benefit
E N D
Analysis for the Strike Coordination Support (LMC04) Candidate POC: G. Shea
LMC04 Overview • Summary Description • Description: Provide the ability for LPMP to use a route altitude and route type received from TC2S in a Tactical Change LMO. • Fleet Benefit • Provides the TSC with the option to provide guidance as to the route altitude and route type when tasking Retargets. • Fleet Importance: Medium • CR Summary • Adaptive: 1 • Perfective: 0 • Corrective: 0 • TOTAL: 1
LMC04 Analysis • Technical Description Provide the ability for LPMP to use a route altitude and route type received from TC2S in a Tactical Change LMO. • 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: Requires an ICN to PEO(W) 3900/146 (IFIR has been approved by PMA-281) • Risk: Med (due to ICN required for PEO(W) 3900/146) • Addresses 1 CR Eliminates 0 TTBs/TIP entries
LMC04 Recommendation • Recommendation Implement in v6 Defer for future consideration • Rationale • There currently is no way for the TSC to provide electronic guidance on an individual Retarget. • Issues • None.
CR # Class TIP Description Disposition 8707 A To perform a retarget, we need to supply route altitude. We can do it manually, as the Retarget window has a field for it. However, we cannot do it electronically, because the 3900/146 spec does not provide a route altitude field in the LMO-T object. We looked in the original spec, plus ICNs 1, 10, 12 and 17. Nothing in any of these ICNs. This is not a serious TTWCS issue, however, because we verified before writing this PR that when an electronic retargeting command is received, TTWCS will use the default LPMP altitude contained in the Operator Controls window. The thing that is lost here is the ability for the tasking authority to specify the route altitude. Because TTWCS is able to manage without this field, I recommend pri 4. Addressed in White Paper LMC04 CR Summary
LMC04 – Design Concept • CR 8707 – Provide the ability for LPMP to use a route altitude and route type received from TC2S in a Tactical Change LMO. • Provide the capability to receive Route altitude and route type in a Tactical Change LMO from TC2S. • LPMP would use the specified altitude and type when creating a retarget. • TC2-PLE would use the specified altitude and type when creating an Aimpoint Update. • If they are not specified in the message, the current default would be used. • Addressed in the White Paper.
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)