TDL & CMS Integration Issues. Serdar ÖZTÜRK, Emine Esen TAŞDEMİR & Murat ŞAHİN MilSOFT Software Technologies, METU Technopolis, ANKARA/TURKEY

Transcription

1 TDL & CMS Integration Issues Serdar ÖZTÜRK, Emine Esen TAŞDEMİR & Murat ŞAHİN MilSOFT Software Technologies, METU Technopolis, ANKARA/TURKEY

2 Agenda MilSOFT UNCLASSIFIED 2 Integration of TDL and CMS Systems TDL & CMS Deployment Architectures TDL & CMS Integration Issues Conclusion

3 MilSOFT UNCLASSIFIED 3 Integration of TDL and CMS Systems Level of the integration between TDLs and CMS directly affect the benefit of TDL during military operations Goal is to benefit from tactical data link functional areas, data dictionary and granularities to the maximum extent, and try to prevent data losses. CMS (Combat Management System) is the computer system that connects a platform s sensors, weapons, data links and other equipment to provide real-time situational awareness to the operator. It allows the operator to execute combat operations.

4 MilSOFT UNCLASSIFIED 4 Evaluation Criteria for Integration Strategies Capabilities of CMS : Supported Functional TDL Areas: If some of the Link functional areas are missing in the CMS, the integration will be more difficult. HMI Functionality and Display: Modern TDLs require automated operational functions, HMI should support operator level interoperability Cost and Schedule Effect: It may not be cost and schedule effective to develop a new CMS or modify an existing CMS Data Loss: Data dictionary and granularities of interface data are fully compatible with TDLs or not Sensor Data Processing TDL units should report their real time position with trusted positional accuracy based on track quality values. Minimize geodetic position errors Minimize sensor registration errors Minimize data conversion errors This is essential for removing dual designations and assessing reporting responsibility for a clear and reliable tactical picture.

5 MilSOFT UNCLASSIFIED 5 TDL & CMS Deployment Architectures 1. Multilink Processor embedded into CMS 2. Multilink Processor connected to legacy CMS with an adaptation module with Link Console 3. Multilink Processor connected to legacy CMS with an adaptation module

6 MilSOFT UNCLASSIFIED 6 1. Multilink Processor embedded into CMS Multilink Processor is natively and fully integrated to CMS CMS software has to be developed or upgraded in order to be fully Link compatible and supporting Link operations. Therefore this solution may not be cost and schedule effective. Data Dictionary and granularities of interface data are fully compatible with TDLs. No data or precision loss. This integration doesn t require intermediate link operators. All operators depending on their roles of CMS will access task related data coming from TDLs New CMS developments should target this integration model. MilSOFT s CMS and DLP systems are integrated using this model.

7 2. Multilink Processor connected to legacy CMS with an adaptation module with Link Console Multilink Processor is integrated to CMS via an adaptation unit Adaptation module fills the gap between CMS capabilities and the data link functions Operator interactions related to the link functionalities are performed on the dedicated link consoles Minimal or no modification is needed for CMS Cost and effort effective Data loss or data granularity loss can be observed. Some Link operations may not be supported on CMS Consoles. Synchronization of tactical pictures on CMS and Link Consoles can be difficult. MilSOFT UNCLASSIFIED 7

8 3. Multilink Processor connected to legacy CMS with an adaptation module MilSOFT UNCLASSIFIED 8 Similar to previous integration model, Multilink Processor is integrated to CMS via an adaptation unit A separate Link Console is not used, existing CMS console software may be modernized. Link operations are limited to scale of CMS console capabilities. No effort for the synchronization of CMS and Link Consoles.

9 MilSOFT UNCLASSIFIED 9 TDL & CMS Integration Issues Communication Protocols Time Synchronization Initialization and Synchronization of TDL and CMS Systems Definition of Interfaces between TDL and CMS Systems Coordinate System Conversions Tactical Picture Synchronization

10 Communication Protocols Generally CMS and TDL systems use different communication or middleware architectures In order to integrate CMS to TDL a common communication protocol may be constructed an adapter unit can be developed to work as a gateway TCP/IP protocol can be used as a common communication protocol. Gateway adapter unit can be developed which can communicate through both Middleware A and Middleware B If there are CPU architecture differences between TDL and CMS systems, endianness (byte order) problem may occur. As a solution Common Data Representation (CDR) during data serialization and de-serialization may be used. Integration over the same middleware can be ideal solution. MilSOFT UNCLASSIFIED 10

11 MilSOFT UNCLASSIFIED 11 Time Synchronization Shared data between CMS and TDL includes time based information. Therefore, synchronization of time between TDL and CMS systems is very important The most common method for synchronizing time between different systems is using Network Time Protocol (NTP). NTP applications are available on most of the operating systems and it is very easy to configure it. CMS and TDL systems may be synchronized using external time sources.

12 MilSOFT UNCLASSIFIED 12 Initialization and Synchronization of TDL and CMS Systems During initialization, before sharing important tactical information, two systems should technically be synchronized (establishing connections, time synchronization and receiving appropriate system state/mode or heartbeat data) Inadaquate technical synchronization can cause tactical data loses or misinterpretation. Since sometimes systems are loaded with high amount of track data, In order not to encounter problems in timely reception of technical messages during overload conditions, two separate channels can be established for technical and tactical messaging.

13 MilSOFT UNCLASSIFIED 13 Definition of Interfaces between TDL and CMS Systems Technical agreement document which defines the interface between TDL and CMS systems is vital for a successful TDL & CMS integration. The document usually contains message and field definitions, communication mechanisms, system state/modes, interaction diagrams, responsibilities of each system etc. The document should clearly define the data interface and interactions between TDL and CMS systems for a succesful integration. Machine-readable formats like XML and IDL can facilitate the integration process.

14 MilSOFT UNCLASSIFIED 14 Coordinate System Conversions Link 16 entities are reported as latitude and longitude using WGS-84 reference datum. The legacy CMS may use Cartesian coordinate system. STANAG 5516 offers a lat/long to Cartesian coordinate conversion algorithm. If CMS uses Cartesian coordinates with slant ranges, this algorithm gives incorrect results when the track has altitude. The algorithm that should be implemented has to be determined depending on the coordinate system used by CMS. The algorithm error must be within «data processing error» limits defined in STANAG.

15 Tactical Picture Synchronization When link consoles are included, synchronization of tactical pictures on CMS consoles and Link consoles arises as a problem during integration. Correlation and decorrelation Correlation tests shall be conducted on one side and results shall be applied on both sides Information to be displayed for correlated tracks shall be same on both sides Relation and information management after correlation and decorrelation Same rules shall be applied on both sides Handling of data type differences between CMS and link Conversion is required on adaptation unit Must fields for Link messages may not exist on CMS data types. Adaptation unit shall take care of it. MilSOFT UNCLASSIFIED 15

16 Tactical Picture Synchronization - continued Handling of local track updates received from Link (CDO, DDR) CMS may not be capable of handling local track updates received from link Adaptation unit shall retain local track data received from link and report the local track to DLP with new data until data is updated by CMS Voice coordination is required between Link operator and CMS operatör Management of track information that CMS is not capable of handling but that can be shared on link Additional track data may be entered by link operator Additional data shall be handled by adaptation unit without affecting local track data from CMS Updating and deleting data received from CMS shall be prohibited by Link consoles MilSOFT UNCLASSIFIED 16

17 MilSOFT UNCLASSIFIED Example Modernization Link-11 based ship CMS system is integrated with Mil-DLP (Link 11/16/22) All link-related Local data is maintained by CMS Adaptation unit DTS Link 11 based Ship CMS Link Console M-Series Messages KG 40 TCP/IP Normalized Messages DDS Mil-DLP CMS Interface Unit TDL Interface Unit J-Series Messages CMS Adaptation Unit Link Console MIDS

18 Conclusion There is no perfect solution for TDL and CMS integration Integration model shall be selected according to the; operational needs, required capability, cost, schedule, maintainability issues. CMS-TDL integration can be a challenging endeavor, we would be happy to discuss details at your convenience. MilSOFT UNCLASSIFIED 18

19 MilSOFT UNCLASSIFIED 19 Questions? Thank you very much Serdar ÖZTÜRK

20 TDL & CMS Integration Issues Serdar ÖZTÜRK, Emine Esen TAŞDEMİR & Murat ŞAHİN MilSOFT Software Technologies, METU Technopolis, ANKARA/TURKEY