Physical View: The Intelligence Transportation System

The information exchanges and transportation systems that back up the Intelligence Transportation System (ITS) are collectively known as the Physical view. The architecture of this outlook is shown as an integrated set of physical objects, consisting of terminators and subsystems that interrelate and exchange data to support the ITS service packages (“Physical,” 2021). Subsystems form a part of the general ITS and offer the ITS “inside-the-boundary” functionality. At the same time, terminators lie at the ITS boundary and receive information or provide data required by ITS functions. These physical components help delineate the data exchanges and transportation frameworks linked to the ITS.

The Physical view is correlated with other architecture views, including the functional view and the enterprise view. The former is linked to the functional objects that precisely describe the details and functions of data exchanged by the object. Moreover, physical and functional objects are also used as the enterprise view resources that explain the organizations and roles of objects in certifying, maintaining, operating, and installing all Architecture components. Physical objects in the physical view are arranged in six classes that include one or more subsystems and delineate the highest level of abstraction of ITS (“Physical,” 2021). The general class contains all ITS, while the personal, support, field, center, and vehicle classes specifically group physical objects according to their location, fundamental behavior, and interaction with other physical objects. The architecture view elucidates the functions and components of the exchanged information.

The ITS object plays a significant role in the ARC-IT Physical view since it defines the interfaces and functionality that may apply to all ITS systems or objects, irrespective of class. The ARC-IT physical objects can be put in a hierarchy, with the ITS object at the highest level to define the generally feasible interfaces and functions applicable to the entire ITS (“Physical viewpoint,” 2021). Subsequently, class-level physical objects can follow in the hierarchy, then share interfaces and functions with ITS centers. The specific physical objects, such as the commercial vehicle administration center and the authorizing center that have interfaces and functions unique to the specific center, occupy the last part of the pyramid.

The Physical viewpoint includes physical elements that function in the back office and the field, as well as the roles and functionalities of these constituents in providing user services and their related connections. From an engineering perspective, the physical view is closer to the design viewpoint and directly leads to the view of the communication (“Physical viewpoint,” 2021). The physical viewpoint is informative because it gives the foundation of service packages that are concise and comparatively easy to follow diagrams that communicate concepts of functionality, information exchange, service delivery, and concerns associated with these notions (“Physical viewpoint,” 2021). The physical viewpoint contains the physical entities and interfaces required in the delivery of service, the functionalities allocated to the physical entities, and the security considerations for devices and information traded between elements.

Descriptions incorporated in the two articles include the physical object, functional object, information flow, triple, subsystem, terminator, and service package diagram. An item, person, or place that takes part in ITS is known as the physical object, and it is divided into five classes: vehicle, personal, field, support, and center. The functional object is the building block of all physical objects because it groups related processes of a specific physical object in a package that can be deployed or implemented. Information flow represents the data that is transferred in the Physical view between the Physical Objects. According to the article, a triple is the basis of an interface, and it involves the combination of physical object source, destination, and information flow. Finally, the service package or physical diagram illustrates all the possible physical objects, information flows, and functional objects required to support the package. These elucidations enhance one’s understanding of the ITS’ physical view.

References

Physical. (2021) National ITS Reference Architecture.

Physical viewpoint. (2021). National ITS Reference Architecture.