Your SlideShare is downloading. ×
0
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Gemkomsis 2012
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Gemkomsis 2012

314

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
314
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 12 years ago, we have realized that Expectations from Combat Management Systems (CMS) Software were changing; Real-time, near real time and Network Centric features had to be considered This was; Controlling subsystems for mission execution in Real Time , compiling the Tactical Picture and provide decision support capabilities. And also integrating Logistic, Intelligence, Technical and Personnel information systems. Interoperability was important, Task Forces needed the Capability of operating in integrated networked environment and sharing information through other units. Standards based interface requirements are needed for Seamless integration of more sensors and weapons Common architectures had to be used for Better maintainability, modernization and adaptability More demanding quality attributes needed for better performance, scalability and reliability. We had to decrease life cycle costs
  • To develop such a CMS, utilization of open and international standards is a vital factor in design of military systems. Selection of which standards to be applied is another challenge in the design of the military systems. MilSOFT has evaluated the OACE standard set as the basis in the design of her systems and taken OMG, as a non-profit international organization, as another major standardization body to be followed in the design of complex CMS systems. As architecture driven technologies are applied, first the architectural drivers are identified Open and internationally accepted standards are one of the most important driving factors It has Commonalities across platforms It allows Rapid technology insertions and changes and Rapid warfighting capability introduction It’s Scalable On maintainability point of view , you fix once and deploy everywhere MilSOFT Combat Management System (CMS) Software is based on open standards and products of the 21st Century. Built-in Link-16/22 data structures in the system is one of the superior functionality provided by MilSOFT CMS. We know that; Navies around the world ask for Open Architecture systems which; AEGIS-equipped cruisers and destroyers Ship Self Defense System (SSDS)-equipped carriers and large deck amphibious assault ships (ex. LPD ve LHD) Submarines (ex. VA class SSN 688, Ohio class SSGN) DD(X) land attack destroyers Littoral Combat Ship (LCS) E-2C (Early Warning Aircraft) Turkish Coast Guard Search & Rescue Ships
  • To meet the requirements of new generation CMS, MilSOFT has developed MilSOFT CMS as a solution providing a common CMS infrastructure for different type of platforms which is an Indigenous Development and has Scalable and Modular CMS Infrastructure. With the previous slide drivers, together with our experience, we come up with the solution of OACE/OAFA of US Navy. They were addressing most of our drivers OMG was a good starting point with STANAGs, Mil-STDs Full OACE compliance Compliant to OAFA at Level-0 and Level-1 (to the detail available publicly) As OACE and OAFA are std.s established by US navy as a roadmap to network centric operations, OACE/OAFA provides a readiness for net-centric usability of the GEMKOMSIS system MilSOFT is one of the few implementors of DDS middleware. It is not a in-house implementation, it is fully compliant to OMG std. as it will be explained DDS is already being used by other C2 applications in MilSOFT Link-16/22 data structures in the system is one of the superior functionality provided by GEMKOMSIS which allows the integration of MilSOFT Multi-Link Processor(DLP) and utilize the full functionality of Data Link Capabilities by CMS.
  • GEMKOMSIS has a layered architecture where standards based computing environment includes COTS computing technology, OMG’s DDS middleware and OMG’s AMSM Resource Management. Common Services, that do not change across naval platforms, and OMG’s ALMAS and OMG’s TACSIT implementation. Common Functions layer includes tactical application components satisfying the requirements of naval platforms. Examples of Common Functions are track management, warfare, simulation, and training. All of the common function components are based on modern Link-16/22 data model for future compatibility. Only platform unique functions are specific to any other platform. With SIU concept, we isolate CMS software from sensor specific interfaces and processings. ------------------------------------------------------------------------- Computing Technology defines a common computing environment for applications to run Middleware provides distribution and adaptation middleware and frameworks Resource Manager monitors and manages distributed real time CMS system Ship Common Services supports mission capabilities across ship classes Ship Common Functions defines functions that shows little variations (or no variations) across ship classes Platform Unique Functions and Interfaces Functions, services and interfaces unique to platforms -------------------------------------------------------------
  • Mil SOFT Multi-Purpose Data Link Processor is part of a chain of MilSOFT Combat Management System (CMS) capabilities which enable the operators to fully benefit the Link Neutral Data Structure of the CMS and operate on any communication protocol/standard/medium to execute their tasks.
  • MilSOFT CMS is scalable which can go down to even one single Workstation that allows solutions with one Console/Computer having GEMKOMSİS infrastructure and integrated to Gun and G/M for small boats. All functions can run on one single workstation.
  • MilSOFT CMS has the following Main Functions; Full Integration of Sensors and Systems Track Management and Data Fusion (Identification/Classification/Correlation) Recognized / Common Operational Picture Compilation (All Sensors incl.WAIS, IFF, MHS, Link16/22) CMS Tactical Picture Infrastructure with ECDIS features Effective and Secure Defense / Attack Capability (TEWASA) General and Tactical Navigation Hard Kill / Soft Kill Coordination Naval Gunfire Support / ASW Attack/Search Methods Support Functions Search and Rescue (SAR) Platform Library Support World Management(Real / Simulation) Resource Management Record and Replay On Board Operator Training Capability (Training and Simulation) OACE (Distributed Architecture, COTS Utilization, Layered Structure, Alarm Management, Easy Functioanlity Insertion and chanage of the existing Functions) Distributed Data Structures, Real Time Data distribution (DDS) Convinient for different Size and Type of Platforms(Scalability) Interoperability among platforms
  • MilSOFT CMS has the following Main Capabilities; Integration with all the systems Situational Awareness Recognized Maritime Picture Integration with other Operational Centers and Sea, Air, Land Assets Infrastructure for Network Centric Capability
  • This slides summarizes the reference projects using MilSOFT CMS Infrastructure. GEMKOMSİS Infrastucture is also used in different Projects that were developed by MilSOFT. All these systems can easily be integrated because of the common infrastructure provided by GEMKOMSİS. Video Transfer over DDS has been realized for TIHA Project. The same functionality can be utilized for CMS Systems. Developing Systems as standalone is not sufficient since systems that are designed to work together in coordination should also be compatible with eachother. The integration of C2 Infrastructure with MilSOFT Multi-link Processor in GVLS Project has been realized in a very short time because of the compatibility of the systems.
  • The answer to “Why MilSOFT CMS?” is the following; HIGH QUALITY 1 4 years of experience in CMS Qualified team / Expert engineers CMMI-5 level Quality Assurance and Procedures Compliant to International and Modern Standards Proven technology LOW LEAD TIME OACE Architecture and CMS Product Line Ability to integrate new functions rapidly Prior success stories CUSTOMER SUPPORT Current CMS Architecture (Re-use) Experienced personnel Interoperability between platforms
  • Transcript

    • 1. MilSOFT COMBAT MANAGEMENT SYSTEM
    • 2. New Requirements & Expectations from CMS Control of subsystems for mission execution => Real-time features Tactical picture information and decision support capabilities => Near real time features Integration with Logistic, Intelligence, Technical and Personnel information systems => Network Centric features Capability of operating in integrated networked environment and sharing information through other units => Interoperability Requirements Seamless integration of more sensors and weapons => Standards based interface requirements Better maintainability, modernization and adaptability => Common architectures Better performance, scalability, reliability => More demanding quality attributes Decrease of life cycle costs
    • 3. Solution : Open Architecture To satisfy the new requirements, OACE standards were adopted by US Navy and is being implemented in modern Naval systems. These standards shall provide;  Utilization of open standards in system design  Commonalities across platforms  Rapid technology insertions and changes  Rapid warfighting capability introduction  Scalability  For maintainability; fix once and deploy everywhere Navies all around the world look for open architectures instead of “proprietary”, “integrated” systems and leader companies are switching to this technology;  AEGIS-equipped ships  New Amphibious assault ships (ex. LPD ve LHD)  Submarines (ex. VA class SSN 688, Ohio class SSGN)  Littoral Combat Ship (LCS)  E-2C  Turkish Coast Guard Search & Rescue Ships (x4)
    • 4. MilSOFT Solution : MilSOFT CMS MilSOFT New Generation CMS is a solution providing a common CMS infrastructure for different type of platforms.  Surface, Subsurface, and Air Platforms  Scalable and Modular CMS Infrastructure  Indigenous Development MilSOFT New Generation CMS is based on open Architecture Standards and latest technologies.  OACE System Architecture and OAFA System Features  DDS Middleware (OMG)  GIS Software (PiriMap®) compliant with SOA WEB Services  Compliant to OMG C4I Standards (AMSM, AWIM, TACSIT, etc)  Fully Integrated Functionality (MHS, Navigation, WAIS, ICS)  Link-16/Link-22 data structures integrated with Mil-DLP. Technology Award
    • 5. MilSOFT CMS Software Compliant to Open Architecture Computing Environment (OACE) Software Architecture:  Computing Environment - Middleware - Resource Management  Common Services - Tactical Picture Infrastructure (TPI) - Alarm, Warning and Information Management (AWIM) - Record and Replay - Platform and Environment Data Management - Platform Database - User Role Management  Common Functions - Track Management (TM) - Navigation - Training & Simulation - World Management - Warfare (AAW, AsuW, ASW, EW) - (Warship) Automatic Identification System ((W)AIS) - Link 16 Processing - Message Handling System (MHS)  Platform Unique Functions - Search and Rescue - Helicopter and Aircraft Control - System Monitoring and Maintenance - Sensor Resource Management - SIUs No dependancy to any specific hardware
    • 6. CMS – Multi Link Application Normalized Interface Link Oper. Rules Link Protocol (Independent from Link (5000+ Link Interface Protocol) Oper.Rules) Link 11 Link 16 CMS Link 11 B Infrastructure CMS Infrastructure VMF JREAP Multi Link System Link 22Sensors C2 Legend: Link 16/22 Based Applied Under Development Future
    • 7. MilSOFT CMS – Scability Feature .... Weapon-GM System Navigation Radar Tactical Data Link MHS Platform Unique Functions Console and Required Processor(s)Platform Data (DDU)(Gyro,GPS etc.) All functions on single workstation
    • 8. Additional Functions with MilSOFT CMS  Full Integration of Sensors and Systems  Track Management and Data Fusion (Identification/Classification/Correlation)  Recognized / Common Operational Picture Compilation (All Sensors incl.WAIS, IFF, MHS, Link16/22)  CMS Tactical Picture Infrastructure with ECDIS features  Effective and Secure Defense / Attack Capability (TEWASA)  General and Tactical Navigation  Hard Kill / Soft Kill Coordination  Naval Gunfire Support / ASW Attack/Search Methods Support Functions  Search and Rescue (SAR)  Platform Library Support  World Management(Real / Simulation)  Resource Management  Record and Replay  On Board Operator Training Capability (Training and Simulation)  OACE (Distributed Architecture, COTS Utilization, Layered Structure, Alarm Management, Easy Functioanlity Insertion and chanage of the existing Functions)  Distributed Data Structures, Real Time Data distribution (DDS)  Convinient for different Size and Type of Platforms(Scalability)  Interoperability among platforms
    • 9. Additional Capabilities with MilSOFT CMS  Integration with all the systems  Situational Awareness  Recognized Maritime Picture  Integration with other Operational Centers and Sea, Air, Land Assets  Infrastructure for Network Centric Capability
    • 10. MilSOFT CMS InfrastructureInherited from GEMKOMSİS and bringing togetherdifferent experiences from Multiple Projects Turkish Coast Guard Search And Rescue Ship CMS UAV Video Exploitation System - Stream data/video over DDS middleware GDLS - Frigate Multi-Link (Link-11/16) Modernization Programme - Mil-DLP New Type Submarine Project Multi-Link (Link-11/22) Programme Middleware for CMS, UAV and DLP product lines Scalable CMS
    • 11. Why MilSOFT CMS ?  HIGH QUALITY  14 years of experience in CMS  Qualified team / Expert engineers  CMMI-5 level Quality Assurance and Procedures  Compliant to International and Modern Standards  Proven technology  LOW LEAD TIME  OACE Architecture and CMS Product Line  Ability to integrate new functions rapidly  Prior success stories  CUSTOMER SUPPORT  Current CMS Architecture (Re-use)  Experienced personnel  Interoperability between platforms

    ×