MAKING CITIES INTEROPERABLE IN TURKEY
International archives of the photogrammetry, remote sensing and spatial information sciences.,
12/2021
Journal Article
The Internet of Things (IoT) has many important applications in multiple domains that include home automation, smart cities, healthcare, agriculture, and environment. IoT comprises a wide range of ...sensors and actuators that communicate with each other over cloud, fog, and edge level networks. Moreover, these devices use various communication protocols and are made by different manufactures. To deal with these diversities, IoT essentially needs interoperable communication interfaces among devices. Unfortunately, existing interoperability solutions are centralized and use fog or cloud level computing resources, making IoT communications latency-prone and poorly scalable. These issues could be handled effectively, if edge level devices could be made interoperable within the edge level and without needing fog or cloud level access. This article proposes a decentralized interoperability solution that stays fully within the edge level. The solution relies on controller devices that work on the interface boundaries of the edge devices. Unlike existing solutions, the proposed solution adopts a hierarchical interoperability model to handle interoperability at network, syntactical, semantic, and organizational levels. Our solution is nonproprietary, generic over vendors and platforms, and easily extendable to new devices. We compare our proposed solution with existing interoperability solutions for edge devices and show its mobility, efficiency, and flexibility.
•Explore the major factors affecting BIM interoperability.•Propose the BIM Interoperability Adoption Model (BIAM).•Identify interoperability dimensions: technical, organizational, legal, and ...semantic.•Provide guidelines to tackle interoperability issues in AEC organizations.•Explore further research to provide an in-depth understanding of interoperability factors.
Building Information Modelling (BIM) is a paradigm shift from the traditional Architecture, Engineering, and Construction (AEC) industry practices to digital construction delivery processes. BIM provides the capabilities of cost reduction, increase quality, enhanced productivity, and on-time delivery. Despite the numerous advantages of BIM, its adoption in AEC is vulnerable to confrontation. Data interoperability is often cited as a significant barrier to BIM adoption; there is a limited focus on other dimensions of interoperability. In other research areas, such as information systems and electronic government, the evolution of interoperability construct is debated beyond data interoperability. These dimensions of interoperability have yet to be explored in the AEC industry. This research article aims to introduce the BIM Interoperability Adoption Model (BIAM). For this purpose, we investigate the interoperability in multiple dimensions according to the European Interoperability framework and develop BIM Interoperability Model with factors affecting each interoperability dimension. BIAM offers a comprehensive assessment of technical, organizational, semantic, and legal interoperability in intra –organizational AEC units, inter-organizational AEC, and BIM partner organizations and assists as a model in assessing the level of compliance and maturity interoperability. BIAM is proposed to work as a link between the organizational, semantic, legal, and technical factors to determine the interoperability issues in the early stages of BIM adoption. The BIAM model addresses interoperability factors and provides recommendations and specifications to help AEC firms to collaborate more effectively by improving interoperability activities, organizational mapping processes, and improving legal coordination. Furthermore, opportunities for future research related to BIM interoperability are discussed, and addressing these aspects of interoperability will make collaborative project delivery well informed, more structured, and effective.
System languages such as C or C++ are widely used for their high performance, however the allowance of arbitrary pointer arithmetic and type cast introduces a risk of memory corruptions. These memory ...errors cause unexpected termination of programs, or even worse, attackers can exploit them to alter the behavior of programs or leak crucial data. Despite advances in memory safety solutions, high and unpredictable overhead remains a major challenge. Accepting that it is extremely difficult to achieve complete memory safety with the performance level suitable for production deployment, researchers attempt to strike a balance between performance, detection coverage, interoperability, precision, and detection timing. Some properties are much more desirable, e.g. the interoperability with pre-compiled libraries. Comparatively less critical properties are sacrificed for performance, for example, tolerating longer detection delay or narrowing down detection coverage by performing approximate or probabilistic checking or detecting only certain errors. Modern solutions compete for performance. The performance matrix of memory safety solutions have two major assessment criteria - run-time and memory overheads. Researchers trade-off and balance performance metrics depending on its purpose or placement. Many of them tolerate the increase in memory use for better speed, since memory safety enforcement is more desirable for troubleshooting or testing during development, where a memory resource is not the main issue. Run-time overhead, considered more critical, is impacted by cache misses, dynamic instructions, DRAM row activations, branch predictions and other factors. This research proposes, implements, and evaluates MIU: Memory Integrity Utilities containing three solutions - MemPatrol, FRAMER and spaceMiu. MIU suggests new techniques for practical deployment of memory safety by exploiting free resources with the following focuses: (1) achieving memory safety with overhead < 1% by using concurrency and trading off prompt detection and coverage; but yet providing eventual detection by a monitor isolation design of an in-register monitor process and the use of AES instructions (2) complete memory safety with near-zero false negatives focusing on eliminating overhead, that hardware support cannot resolve, by using a new tagged-pointer representation utilising the top unused bits of a pointer.
Blockchain interoperability is emerging as one of the crucial features of blockchain technology, but the knowledge necessary for achieving it is fragmented. This fact makes it challenging for ...academics and the industry to achieve interoperability among blockchains seamlessly. Given this new domain’s novelty and potential, we conduct a literature review on blockchain interoperability by collecting 284 papers and 120 grey literature documents, constituting a corpus of 404 documents. From those 404 documents, we systematically analyzed and discussed 102 documents, including peer-reviewed papers and grey literature. Our review classifies studies in three categories: Public Connectors, Blockchain of Blockchains, and Hybrid Connectors. Each category is further divided into sub-categories based on defined criteria. We classify 67 existing solutions in one sub-category using the Blockchain Interoperability Framework, providing a holistic overview of blockchain interoperability. Our findings show that blockchain interoperability has a much broader spectrum than cryptocurrencies and cross-chain asset transfers. Finally, this article discusses supporting technologies, standards, use cases, open challenges, and future research directions, paving the way for research in the area.
Complex and large software-intensive systems are increasingly present in several application domains, including Industry 4.0, connected health, smart cities, and smart agriculture, to mention a few. ...These systems are commonly composed of diverse other systems often developed by different organizations using various technologies and, as a consequence, interoperability among these systems becomes difficult. Many architectural strategies for interoperability have already been proposed; however, selecting adequate strategies is challenging. Additionally, it lacks an overview of such strategies. This work presents TASIS, a typology of architectural strategies for the interoperability of software-intensive systems. We also validated it with 33 practitioners from different countries with an extensive experience in integration projects. This work also offers 12 industry-based association rules that suggest how to combine those strategies to mitigate issues at different interoperability levels. As a result, our typology can serve as a starting point to further aggregate new strategies and, ultimately, supports software architects in designing interoperability-driven architectural solutions.
•It is a typology with architectural strategies and their levels of interoperability.•The typology was created from evidence in literature and validated and refined it.•We offer strategy combinations proven in integration projects, derived from association rules.•Software architects can use it to select architectural strategies for their projects.
•The paper describes the information system and interoperability related challenges, trends and issues that must be addressed to support a new generation of scientific-based and technological ...solutions for facilitating the collaboration of existing enterprise systems.•This paper presents general research priorities and directions of related to context-aware systems, semantic interoperability, cyber-physical systems, cloud-based systems and interoperability assessment.•The listed properties are used to propose the generic abstract architecture of the Next Generation Enterprise Information Systems.
The rapid changes in today's socio-economic and technological environment in which the enterprises operate necessitate the identification of new requirements that address both theoretical and practical aspects of the Enterprise Information Systems (EIS). Such an evolving environment contributes to both the process and the system complexity which cannot be handled by the traditional architectures. The constant pressure of requirements for more data, more collaboration and more flexibility motivates us to discuss about the concept of Next Generation EIS (NG EIS) which is federated, omnipresent, model-driven, open, reconfigurable and aware. All these properties imply that the future enterprise system is inherently interoperable. This position paper presents the discussion that spans several research challenges of future interoperable enterprise systems, specialized from the existing general research priorities and directions of IFAC Technical Committee 5.3,11IFAC Technical Committee 5.3 « Enterprise Integration and Networking », http://www.ifac-tc53.org namely: context-aware systems, semantic interoperability, cyber-physical systems, cloud-based systems and interoperability assessment.
Objective In early 2010, Harvard Medical School and Boston Children’s Hospital began an interoperability project with the distinctive goal of developing a platform to enable medical applications to ...be written once and run unmodified across different healthcare IT systems. The project was called Substitutable Medical Applications and Reusable Technologies (SMART).
Methods We adopted contemporary web standards for application programming interface transport, authorization, and user interface, and standard medical terminologies for coded data. In our initial design, we created our own openly licensed clinical data models to enforce consistency and simplicity. During the second half of 2013, we updated SMART to take advantage of the clinical data models and the application-programming interface described in a new, openly licensed Health Level Seven draft standard called Fast Health Interoperability Resources (FHIR). Signaling our adoption of the emerging FHIR standard, we called the new platform SMART on FHIR.
Results We introduced the SMART on FHIR platform with a demonstration that included several commercial healthcare IT vendors and app developers showcasing prototypes at the Health Information Management Systems Society conference in February 2014. This established the feasibility of SMART on FHIR, while highlighting the need for commonly accepted pragmatic constraints on the base FHIR specification.
Conclusion In this paper, we describe the creation of SMART on FHIR, relate the experience of the vendors and developers who built SMART on FHIR prototypes, and discuss some challenges in going from early industry prototyping to industry-wide production use.
Interoperability stands as a critical hurdle in developing and overseeing distributed and collaborative systems. Thus, it becomes imperative to gain a deep comprehension of the primary obstacles ...hindering interoperability and the essential criteria that systems must satisfy to achieve it. In light of this objective, in the initial phase of this research, we conducted a survey questionnaire involving stakeholders and practitioners engaged in distributed and collaborative systems. This effort resulted in the identification of eight essential interoperability requirements, along with their corresponding challenges. Then, the second part of our study encompassed a critical review of the literature to assess the effectiveness of prevailing conceptual approaches and associated technologies in addressing the identified requirements. This analysis led to the identification of a set of components that promise to deliver the desired interoperability by addressing the requirements identified earlier. These elements subsequently form the foundation for the third part of our study, a reference architecture for interoperability-fostering frameworks that is proposed in this paper. The results of our research can significantly impact the software engineering of interoperable systems by introducing their fundamental requirements and the best practices to address them, but also by identifying the key elements of a framework facilitating interoperability in Systems of Systems.
PDF
