System-wide Information Management, or SWIM, is a framework designed to improve how air traffic management (ATM) information is handled and shared among authorized parties. It includes a set of standards, infrastructure, and governance necessary for effective information exchange through interoperable services. The current flight planning systems face significant challenges such as limited information sharing, inconsistent data, and security issues. To tackle these problems, a secure, net-centric environment is essential. This system should rely on a clear and consistent set of information elements to enable a globally interoperable ATM system that focuses on 4D trajectories.
4D trajectory-based ATM systems have specific data-related needs. These needs range from establishing a secure architecture that allows trustworthy information sharing across the entire system to ensuring early access to intent data. Additionally, these systems must support collaborative decision-making and high levels of automation, which require machine-readable data and clearly defined information items.
Key principles guide both SESAR and NextGen initiatives in managing flight information. Information sharing must be secure and system-wide. Relevant data should be accessible when and where it’s needed, with options for personalization and filtering. Cybersecurity measures are crucial, ensuring confidentiality, integrity, availability, and protection for data and communication networks. Authentication processes must be in place for user access, and the responsibility for initial data quality rests with the originator. Subsequent handling should maintain this quality, while adjustments can be made to address proprietary concerns. Overall, information management should utilize globally harmonized attributes.
There are two primary approaches to implementing SWIM and achieving its goals. One option is to create a centralized flight data processing system that acts as a server. The second option connects various individual flight data systems into a broad network. The latter is generally preferred because it leverages existing systems, enhancing reliability and robustness. In a peer-to-peer network, the failure of one element has less impact than if a central server fails.
