Value engineering

About: Value engineering is a research topic. Over the lifetime, 1231 publications have been published within this topic receiving 10882 citations. The topic is also known as: VE.

Modeling user acceptance and technology adoption: is there a case for value added services?

Abstract: This paper reports on the findings of on ongoing research project aimed at understanding the behavior of travelers when confronted with novel, technology based, services. The main question addressed is the need for understanding how and when users adopt new technology and when they perceive the services offered with the new technology as added value. The research focuses on the domain of traveler assistance applications offered over cellular wireless networks. The research is carried out by the business development and strategy-consulting department of CMG Unwired Concepts, in conjunction with scientific R&D projects of TNO Cognitive Psychology Institute and the University of Amsterdam. It is a firm belief among cellular network operators that data-driven services will become a large source of income in the near future. With the introduction of new medium (GPRS) and high bandwidth (UMTS) networks, multimedia streaming to handheld devices and PDA's will become reality. The ITS market is a well-suited candidate to introduce these data services as the users are by nature mobile. It is already apparent from the past years that telecom initiated services are entering the automotive market. And vice versa, the automotive market is embracing the telecom opportunities by introducing telematic platforms in their cars. Yet, it is also apparent that creating a sound business case is a different thing altogether. Travel assistance service, route guidance, traffic information, etc. are technically available, but who is willing to pay for it.

4.6.1 Affordability Considerations: Cost Effective Capability

Abstract: This paper examines how best to determine the contextual and dynamic attributes of an affordable system. The complexity of the problem cannot be overstated. The affordability trade space is composed of a relational set of attributes that are contextually sensitive; once this set is bounded, the need arises for an implicit comparison to other systems, sub-systems and components. The problem may be embedded in how systems are designed, how they are governed, and how they are evolved. Considerations are provided to help resolve the complexities involved in identifying and evaluating what an affordable system is. Most of the existing literature is focused on cost comparison or performance comparison of systems separately; the literature which addresses a perspective of how cost and capability of systems can be integrated is found under the disciplines of Cost as an Independent Variable (CAIV) and Value Engineering (VE), but appears insufficient in providing an encompassing framework in which to develop a design for affordability trade space. Both of these disciplines may not adequately address the life cycle or temporal dimensions of systems. To address this deficiency, INCOSE and National Defense Industrial Association (NDIA) have worked to define affordability, and identify related concerns, through ongoing working groups since late 2009. Both organizations have developed definitions for use in this context. Even though affordability has been defined by NDIA, INCOSE and Military Operations Research Society (MORS), in discussions at the recent MORS Special Meeting on Affordability Analysis – How do we do it? (Oct.2012), the Development Planning Working Group discovered that affordability analysis was contextually-sensitive, often leading to misunderstanding and fragmented perspectives. Various industry working groups have recommended developing and formalizing affordability analysis processes, including recognizing the difference between cost and affordability analyses… Key insights include the need to consistently define an affordability context, and establish a framework for the appropriate analytic process. They also have determined that accountability for affordability needs to be assigned across the life cycle. System Engineers must understand that the affordability trade space is fluid, an ever changing set of boundaries that evolve as mission needs evolve, and recognize that any affordable solution is essentially a “snapshot” within that trade space at any point in the life of the system.