Few abbreviations related to future air traffic management systems have caused many problems and misunderstandings, such as EA [Enterprise Architecture] and SOA [Service Oriented Architecture]. In the United States, since administrative orders are provided by the federal government, these two concepts are an important part of the development of the air traffic management system. However, in Europe, EA and SOA were first introduced into the ATM environment during the SESAR development phase, and the reception was initially mixed.
Today, EA and SOA may have nowhere to go, but the fact remains: for many people in the air traffic management series, the exact meaning of both is still a problem.
Let's try to show these works and see what happens.
EA and non-aerospace famous SOA
Initially, the concept of enterprise architecture and service orientation was not related to air traffic management. They are defined and gradually refinanced to meet the needs of complex information technology [IT] systems, especially to increase the business agility of these systems. EA and SOA aim to break the shackles of information technology in business, enabling business needs to drive IT rather than vice versa.
EA and SOA are also available in the air traffic management environment. This is the default. ATM is not the only requirement, and under the skin ATM system, all the opposite statements have much in common with other critical systems, such as controlling the grid or A person who implements remote control surgery. All of these systems need to process large amounts of real-time data, must provide common situational awareness and be driven by decision making.
If EA and SOA can improve these systems, they can help improve the ATM system even if some adjustments to the original idea may be needed.
What is Enterprise Architecture [EA]?
The EA definition given by the Institute for Enterprise Architecture Development [IFEAD] is as follows:
"Enterprise architecture is the complete embodiment of the enterprise; it is the master plan of "competing forces" between enterprise planning [such as goals, visions, strategies, and governance principles]; various aspects of business operations, such as business terms, organizational structure, processes, and data. Automation aspects such as information systems and databases; and supporting technology infrastructure for services such as computers, operating systems and networks."
Ok, you can say... How does this help air traffic management? Critics often say that no matter where they are described, the structure of the enterprise exists. That's right, but we've seen what happens when many ATM companies grow and try to collaborate without following the overall strategic direction. Prior to SESAR, it was called European ATM...
In this view, the EA definition of the MIT Information Systems Research Center is particularly relevant:
"Enterprise architecture is the organizational logic of business processes and IT infrastructure, reflecting the integration and standardization requirements of the company's operating model."
We are getting closer...
And EA in air traffic management?
The SESAR program is the European Air Traffic Management Modernization Program, which combines the technical, economic and regulatory aspects of ATM and will use Single European Sky [SES] legislation to synchronize plans and actions of different partners and federal resources to facilitate development and adoption. Europe implements the required improvements in airborne and ground systems.
While SES does provide a legislative basis for the implementation of future ATM systems, there is still a need to develop and agree on a general framework in which the loose components of European ATMs can be properly bundled and aligned with the SEASAR strategic objectives. These goals are particularly related to network-centric, service-oriented air traffic management methods.
To achieve these goals, European ATMs must be viewed as a single enterprise with components that work together in a networked, service-based operation that drives IT infrastructure.
Once we realize that Europe's air traffic management needs to be seen as a single enterprise [even if it consists of several constituent entities], the goals and objectives of the enterprise architecture concept suddenly become not only relevant, but also a very ideal solution.
European ATM enterprise architecture?
To instantiate a single enterprise concept, we can define the European ATM Enterprise Architecture [EAEA], based on the more general enterprise architecture [EA] concept, although it applies to the air traffic management environment both in scope and content.
So what is the purpose of EAEA?
EAEA can guide and focus on strategic decisions, especially those related to the implementation of ATM concepts and support for information technology investments. This enables partners to proactively plan the introduction of services, avoid duplication of development, reduce costs and better align IT investments with business processes at all levels.
EAEA can also provide strategic guidance for defining and implementing service-oriented architecture [SOA] adaptation to European ATM environment requirements at the business and IT levels.
But what is an ATM company?
A convenient definition for a European ATM company may be "a partner in the SESAR Performance Partnership." Other definitions are possible, and the important message is that each partner who needs to use ATM or contributes must be considered an element of a single, integrated enterprise.
Using the above definitions, we can conclude that the European ATM enterprise architecture is a description of the structure and behavior of the partners. Process, information systems, people and organizational sub-units are aligned with the corporate performance goals and strategic direction defined in the SESAR program.
So what about SOA?
As described now, EAEA provides a business-driven framework that allows the various parts of European ATM and their interactions to be described from different perspectives, including operational and technical aspects. EAEA provides a meaningful way to divide and manage the complexity of the ATM environment to coordinate different partners. A business vision across a single ATM system in Europe and a bridge between business and IT needs.
SOA is a way to use "service" notifications that can be used to populate the EAEA framework.
The word "service" can mean something different, depending on the context in which it is used. Typically, the context is based on consumer/supplier relationships. In addition, a hierarchy of services can exist, for example, an advanced service consists of multiple lower-level service sub-categories. Therefore, it is important to ensure that the nature, scope and detailed characteristics associated with each service are clear and clear at each use, including determining who is providing what.
Services can be defined from a business or IT perspective.
Service from a business perspective
From a business perspective, services are actually consumers' perceptions of provider capabilities. These services must meet the specified characteristics to ensure their efficiency and cost effectiveness. Among them, they must be modular and autonomous, delivered where they are needed, shareable and reusable, and most importantly, they must drive IT support rather than vice versa.
Services can be defined at multiple levels of the enterprise, but in an air traffic management environment, operational services are the highest level of service. A service can be associated with one or more contracts, which are understood as a protocol between two or more parties [often expressed as a service level agreement].
Increasing competition, globalization and technological advancement are driving airlines, airports and other ATM users to change their products, business processes and prices more frequently than ever before. The service structure provides the flexibility to adapt to fast changing conditions more quickly.
SESAR promotes the vision of a partnership partnership structure that connects airspace users, airport operators and ANSPs as a way to define, create, implement, deliver and manage future ATM systems. The concept of providing and consuming operational services through a range of service level agreements will be a way for partners to be constrained from a business perspective, but retains the flexibility that service-oriented provides to effectively respond to changing environments and claims.
While the term "business" and air traffic management have not been used in the past, it is important to recognize that the ever-evolving business world of airspace users must be served by an air traffic management system that can evolve with it. It is also safe and cost effective. This basic business agility can best be achieved through service orientation.
Service from an IT perspective
From an information technology [IT] perspective, the use of services defines IT services that correspond to real business activities or identifiable business functions, and can be accessed based on established service policies...
Orignal From: Enterprise Architecture and Service Orientation - What is it?
No comments:
Post a Comment