Design and Development of an AIoT Architecture for Introducing a Vessel ETA Cognitive Service in a Legacy Port Management Solution

Current Internet of Things (IoT) stacks are frequently focused on handling an increasing volume of data that require a sophisticated interpretation through analytics to improve decision making and thus generate business value. In this paper, a cognitive IoT architecture based on FIWARE IoT principles is presented. The architecture incorporates a new cognitive component that enables the incorporation of intelligent services to the FIWARE framework, allowing to modernize IoT infrastructures with Artificial Intelligence (AI) technologies. This allows to extend the effective life of the legacy system, using existing assets and reducing costs. Using the architecture, a cognitive service capable of predicting with high accuracy the vessel port arrival is developed and integrated in a legacy sea traffic management solution. The cognitive service uses automatic identification system (AIS) and maritime oceanographic data to predict time of arrival of ships. The validation has been carried out using the port of Valencia. The results indicate that the incorporation of AI into the legacy system allows to predict the arrival time with higher accuracy, thus improving the efficiency of port operations. Moreover, the architecture is generic, allowing an easy integration of the cognitive services in other domains.

Generating Program Identifier Dictionary for Maintaining Legacy Systems

Descriptions of program identifiers improve the maintainability of programs. Modern software projects maintain proper descriptions by following coding conventions. However, software projects maintained for a long time have two problems: (i) descriptions at incorrect locations and (ii) no descriptions. We propose the method of generating a identifier dictionary for managing identifiers and their descriptions, which enables developers to refer to identifier descriptions from anywhere within programs. The method involves two steps: (i) extracting identifiers and descriptions from design documents and programs and (ii) generating descriptions using information-retrieval and machine-learning methods. We applied the proposed method to COBOL programs and design documents of a legacy system that has been maintained for over 20 years as a case study. The proposed method obtained the descriptions of 83% of identifiers and reduced the cost of locating files to be modified by enhancing search keywords using the identifier dictionary. This means that the proposed method can improve the maintainability of systems maintained over many years.

Parallel Assessment Tracks for Human-Centered Design (PATH): A Framework for Transitioning to a New Health Information Technology System

This practice-oriented paper presents a human-centered design (HCD) framework that we developed to perform a comprehensive evaluation of a new health information technology (HIT) system under development, intended to replace a legacy system. The Department of Veterans Affairs (VA) Veteran Crisis Line (VCL) program provides a vital service in crisis intervention and suicide prevention. VCL staff rely on a Customer Relationship Management (CRM) legacy system, Medora. VCL intended to replace Medora with Microsoft Dynamics 365 (D365) CRM system. Due to wide-spread criticism of D365, the VA Human Factors Engineering (HFE) team engaged in a multi-study, mixed-method HCD evaluation to investigate the legacy system and intended replacement in terms of ability to support VCL staff needs. The HCD framework we developed to perform this evaluation may be adapted for other large-scale HIT transitions and may provide human factors practitioners with guidance to make evidence-based decisions to support (or abandon) such transitions.

Fit for Purpose: Analyzing the German Archiving and Exchange Interface for Medical Practice Management Systems

The archiving and exchange interface for practice management systems of the Kassenärztliche Bundesvereinigung, defined by FHIR (Fast Healthcare Interoperability Resources) profiles with extensions, describes a new opportunity for medical practitioner to change the system provider. The expectation is to transfer an entire database of a legacy system to another system without data loss. In this paper the potential loss of data is analyzed by comparing parameters. The results show that during an import on average 75% of the parameters per profile are supported and on average only 49% of the reviewed parameters, existing in the exporting system, could be represented based on the interface specification.