China
Africa
Explore chapters and articles related to this topic
st Century Energy Marketplace and Facilities
Published in John J. “Jack” Mc Gowan, Energy and Analytics, 2020
To truly leverage the power of analytics, readers must develop a good working knowledge of a significant number of technology topics that are covered in this book. With the advent of smart grid and the growing predominance of high-speed data communications in most homes, much of this technology is being deployed residentially as well. That is why Part II of this book will provide a thorough treatise on these technologies. Among these technologies are building automation systems, data communications and networking, and “Middleware.” Pervasive standards for data communications, such as BACnet, are the price of entry for buildings to be active participants in new energy markets. Middleware involves a new class of technology products, which allows owners to “integrate” legacy BAS systems with new standard systems, but also opens access to a host of other system integrations.
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.
Supporting Legacy Systems
Published in Steven F. Blanding, Enterprise Operations Management, 2020
Legacy systems continue to be used because they still add value to the business and because they are so expensive to replace. Yet staff members responsible for supporting and maintaining 10-to 20-year-old mission-critical systems may feel they are being denied a chance to acquire new skills. IS managers can protect staff morale in their departments by conveying the business reasons for using legacy systems to the staff assigned the job of maintaining and supporting them. This chapter outlines various ways to minimize apathy among support staff, with tips for helping maintenance employees keep the job fresh.
Crowd tracking and monitoring middleware via Map-Reduce
Published in International Journal of Parallel, Emergent and Distributed Systems, 2022
Alexandros Gazis, Eleftheria Katsiri
The term ‘middleware’ was first used in the early 1980s to describe the software solutions proposed for upgrading legacy systems – mainframes – and migrating them to more advanced technologies and software frameworks. As stated in [16], we characterise middleware as ‘those services found above the transport (i.e. over TCP/IP) layer set of services but below the application environment (i.e. below application-level APIs).’ Middleware typically exists between software applications and the operating system as an intermediary layer. It is responsible for acting as a message broker (e.g. point to point, publish-subscribe) and is largely used in structuring the logic behind back-end development software applications. For example, the simplest middleware developed is when a server sends a request, and the client gets that request and produces a response (action).
The perspective of national ERP vendors in achieving ERP project success in government organisations: a case of Saudi Arabia
Published in Enterprise Information Systems, 2022
Abdullah Ibrahim Alkraiji, Uchitha Jayawickrama, Femi Olan, Md Asaduzzaman, Maduka Subasinghage, Samanthika Gallage
ERP systems are information systems that are essential for organisations to improve business processes (Jayawickrama et al. 2019). The success of ERP implementation is linked to several benefits, such as improvements in the efficiency of business processes, the attainment of integrated real-time information, the achievement of better business performance, the enactment of result-based management, compliance with regulation demands, the sustainment of a competitive advantage, and a response to the desire to deliver new services (Acar et al. 2017; Bharosa et al. 2013; Kautz, Madsen, and Norbjerg 2007; McLeod and Doolin 2012; Nguyen et al. 2017). The technical benefits are related to the limitations of former legacy systems, which include the coexistence of heterogeneous systems, difficulties in affecting evolution, limitations in integration capabilities, and endless (and high) maintenance costs (Bharosa et al. 2013; Jayawickrama et al. 2019; Mayère, Grabot, and Bazet 2008).
Identifying How Nonfunctional Attributes Affect a System’s Lifecycle
Published in Engineering Management Journal, 2021
James R. Enos, John V. Farr, Roshanak R. Nilchiani
Several attributes of systems influence the decision to retire or extend the life of DoD systems to include changeability, interoperability, robustness and versatility. Changeability provides a means to upgrade a system’s capabilities through either extensibility, adding new capability, or flexibility, upgrades to an existing capability. These changes allow for improvements to other critical nonfunctional attributes of DoD systems. Improvements to interoperability allow legacy systems to improve their information flows, shared resources, or physical connections with other legacy systems or newly developed systems. Robustness allows systems to continue to provide value to the DoD despite environmental or threat changes. Finally, the versatility of a system allows the DoD to use systems for an operational activity that it was not designed for and continue to provide value to the DoD. These attributes not only influence the decision to retire or extend the life of a DoD system, but they also provide a basis for calculating the real system age of a system.