{'fraction_non_alphanumeric': 0.027777777777777776, 'fraction_numerical': 0.0, 'mean_word_length': 5.755681818181818, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Air Traffic Management system configuration with Kolona™ Mobile Object Technology

Federal Aviation Administration (FAA) facilities, often controlled by different FAA divisions, are sited in varied locations; nonetheless, all Air Traffic Management (ATM) facilities must work smoothly together. This requires resolving complicated network configuration management tasks. New software must be deployed, applications started and stopped to accommodate maintenance and other needs, and legacy applications upgraded or relocated to different machines. Existing network configuration management solutions, even the relatively new Java Management extensions (JMX), are limited in their ability to address the full scope of the need. They function in a conventional client-server architecture based on a manager and agent model. In this type of implementation, the server configuration defines - and restricts - the actions available to the manager. So, if a user needs new features that are not supported by the current management server configuration, the server, at a minimum, must be reconfigured. This limitation-adaptability through reconfiguration-makes these systems rigid and expensive.