China
Africa
Explore chapters and articles related to this topic
IT supported construction project management based on IFC and ISO9001:2000
Published in Manuel Martínez, Raimar Scherer, eWork and eBusiness in Architecture, Engineering and Construction, 2020
K.U. Gökçe, P. Katranuschkov, R.J. Scherer
In this context, based on the experience gained from studying state-of-the art systems and best practice examples, the operational objectives for the development of an efficient IT-supported CPM solution can be defined as follows: – Generalize and formally describe CPM processes to facilitate interoperability over a broad spectrum of applications.– Develop a common formalized information model for CPM to provide integration of product, process, cost and management data.– Develop methods to integrate existing legacy systems.
The (In)Security of Smart Cities: Vulnerabilities, Risks, Mitigation, and Prevention
Published in Tommi Inkinen, Tan Yigitcanlar, Mark Wilson, Smart Cities and Innovative Urban Technologies, 2020
The second area of vulnerability concerns the use of insecure legacy systems and poor ongoing maintenance. Many smart city technologies are layered onto much older infrastructure that relies on software and technology created 20 or 30 years ago, which has not been upgraded for some time, nor can they be migrated to newer, more secure systems (Rainie et al., 2014; Cerrudo, 2015). These technologies can create inherent vulnerabilities to newer systems by providing so-called “forever-day exploits” (holes in legacy software products that vendors no longer support and thus will never be patched) (Townsend, 2013). Even in the case of newer technologies, it can be difficult to test and rollout patches onto critical operational systems that need to always be on (Cerrudo, 2015).
The Lean IT and Business Partnership
Published in Steven C. Bell, Michael A. Orzen, Lean IT, 2010
Steven C. Bell, Michael A. Orzen
A common example of ineffective IT and business coordination is the existence of a significant legacy information system—homegrown or extensively modified software that remains in place long past its useful life cycle. A legacy system may persist for a number of reasons, among them: unique or unusual business processes are dependent upon it, it may rely on obsolete or obscure technology, those who designed and built it have long since left the company, and the system has been patched repeatedly but the changes are poorly documented. As a result, most IT associates are reluctant to tinker with a legacy system unless it’s absolutely necessary.
Service-Oriented Computing for intelligent train maintenance
Published in Enterprise Information Systems, 2019
Boukaye Boubacar Traore, Bernard Kamsu Foguem, Fana Tangara, Xavier Desforges
Servicization of enterprise information systems: in many organizations, legacy information systems constitute a hard core of defining fundamental functions in business services; so for the modernization of these systems towards SOA, there is a need for suitable better methods to identify business value in large code bases. In this context, we are concerned with web service technologies and those of the MDA approach. The servicization can be performed in four methods namely (Almonaies, Cordy, and Dean 2010) (Table 1): Replacement of Legacy Systems by the new service oriented system: is to rewrite the application of existing systems or replace them entirely with a new software product,Wrapping of the existing system functionality to provide the web service functions: provide a new interface to existing components and make them easily accessible as services to other software components,Reengineering or development of the existing system: using approaches of reverse engineering and re-engineering to add SOA functionality to systems,Migration: that moves the current system to the more flexible environment for SOA or cloud while preserving the original data and system functionality.