Using thin-client architecture to access the legacy training database within the Federal Aviation Administration Academy

Scope and method of study. This study was designed to identify considerations in the development of an alternative to replacing the Consolidated Personnel Management Information System (CPMIS) by examining the use of new client/server technologies and database migrations. CPMIS is a proprietary database system containing information vital to the performance of training administration but with very limited access available to the users. Increasing costs and lack of sustainability of the CPMIS legacy database mandate that the Federal Aviation Administration (FAA) find a viable alternative. To avoid repeating previous replacement failures any new system must meet the needs of the users both in functionality and usability. The study laid the foundation for initiating the design of an incremental migration project by capturing lessons learned from previous CPMIS replacement attempts and captured initial user interface preferences to determine requirements of the targeted system. Project managers of previous replacement projects were interviewed to gain lessons learned. A focus group was conducted to identify user interests and refine questions for a survey instrument. The instrument was then distributed to 142 training administrators to gather basic requirements of the system users. Responses from the instrument were analyzed to determine which characteristics were considered most desirable and most needed by the users.; Findings and conclusions. The study found that the lessons learned from previous replacement attempts indicated failure was due primarily to the failure to adequately determine the user needs and preferences. This resulted in “requirements creep” during the programming phase that caused time and budget overruns, as well as rejection of the user-unfriendly design. The response of the survey instrument indicated that the users greatest need is for rapid, reliable access to the data. The overwhelming preference for a system interface is a Windows environment, graphical user interface (GUI). In order to leverage the existing hardware and network architectures in use by the FAA the users need a system capable of being run on the widest possible range of computer workstations and network protocols. Comparing these needs to the capabilities of thin-client architecture indicates the FAA should use this technology to solve its legacy system replacement dilemma.