مدیریت روابط نرم افزار تامین کننده اجزای رقابتی
|کد مقاله||سال انتشار||مقاله انگلیسی||ترجمه فارسی||تعداد کلمات|
|21164||2014||10 صفحه PDF||سفارش دهید||7127 کلمه|
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : Journal of Purchasing and Supply Management, Volume 11, Issues 2–3, March–May 2005, Pages 97–106
This study addresses purchasing challenges faced by companies buying commercial software components. The purpose is to find out how we can understand the purchasing challenges in software component business. First we develop pre-understanding based on knowledge on competitive supplier relationships and competitive bidding. This is elaborated empirically through a qualitative case study. We contribute to prior literature by concluding that the nature of software component supplier relationships is influenced by the object and costs of exchange. We also argue that, in markets like software component business, it is essential to pay attention to the development of the whole supply market.
For some time now industrial purchasing literature has emphasised the importance of creating close and co-operative relationships with strategic suppliers and developing supply networks composed of close relationships. The world of competitive bidding has, at least in relation to complex products and services, been abandoned and it has suggested that competitive bidding works only for very standardised and basic products. There is, however, an industry which apparently contradicts this point of view. In the software industry, a new segment has rapidly been emerging, one that is based on the idea of standard and competitive market forces: commercial software component business (Ulkuniemi, 2003). The software industry is one of the most influential branches of business in the present growth of the global economy (Autere et al., 1999). Software as part of other products has had a great impact across several industries, and it has enabled and fuelled economic growth in many high-tech industries, such as the telecommunication, automotive and medical industries (Hoch et al., 1999). In the field of software engineering (the development of software products and software-intensive systems), one of the most recent issues has been the increasing interest in software components (Morisio et al., 2000). Estimates put the annual market for commercial software component applications to 200 million dollars worldwide (SIIA, 2003). Component-based software engineering is based on the idea that software systems are developed by pre-producing and selecting appropriate existing components and assembling them according to a well-defined architecture that supports the componentisation (Pour, 1998). There are many benefits of software components including lower development costs, higher productivity and more manageable quality of the software. Componentisation can be seen as one type of modularisation, which has already been used in manufacturing processes of physical products. A final software system includes several software components of which some are possible to purchase from the competitive software component market. Hence, these components form modules within a software system (a product) increasing the degree to which the components of the software can be separated and recombined to customer oriented software product without losing functionality (Schilling, 2000; Pekkarinen and Ulkuniemi, 2005). Manufacturers using software as a part of their products are turning to software components in the hope of reducing the risks associated with software development (Feblowitz and Greenspan, 1998). It is seen that if a specific software component is developed as a core product of a particular supplier, it will be more reliable than the same software developed in-house, beyond the competence of the buying company. Furthermore, as other customers also use the component, possibly even competitors, quality of the component is regarded as higher. One of the underlying factors behind the increasing use of software components has also been the possibility of attaining shorter time-to-market for products, simply because the buying organisations do not need to make everything themselves (Ochs et al., 2000). However, there are also several problems associated with the use of such components. From the perspective of manufacturing companies, component-based software engineering is very different from the more traditional software engineering approach in which software systems are implemented entirely from scratch in-house or by specialised subcontractors (Xia et al., 2000). In reality, component-based software development and especially the use of commercial components has presented significant risks related to software development processes and the nature of software components, component technologies and vendors’ support to customers (Kotonya and Awais, 2001). It has been cited in many sources that the software component markets are far from mature, and they lack industry standards and management guidelines (e.g. Harmon, 1999; Xia et al., 2000; Seppänen et al., 2001). This emerging industry includes many different types of players: sellers may vary from a one-man company to a large software house, and software component brokers sell a variety of different components through their websites. Buyers are typically manufacturing companies buying software components to include in their product's software system. On the other hand, some buyers may in fact also turn into selling companies as they start selling software they originally developed for their own system. All in all, the emerging software component marketplace represents a challenging field for buyers. Despite all the difficulties currently faced in buying and using software components, many companies approach the commercial software component market in the hope of benefiting from the use of components. Apparently, for manufacturing companies, increasing the use of components is a necessary strategic decision, as software and other IT industries increasingly turn towards componentisation. This requires a thorough analysis of the purchasing problems faced by companies. The whole process of acquiring and using software components presents many problems to manufacturers. In the field of software engineering literature, a number of models including step-by-step guidelines for buying software components have been presented. These are strongly concentrating on technical issues, describing the business issues as a simple acquisition of a standard product. In practice acquiring software has included sub-contracting and closer forms of partnering, i.e. exchange mechanisms through which manufacturers have been able to get software solutions tailored to their needs. However, the emerging software component markets represent quite different challenges in managing the supplier interface. The traditional models for competitive supplier relationships represent contexts where the object of exchange is a more or less standard physical item, which can easily be provided by alternative supplier. In the context of software component business, however, the issue of replacing the component with another piece of software is not that clear. This study addresses purchasing challenges faced by software companies buying commercial software components in this emerging market. The overall purpose of the paper is to find out how we can understand the challenges faced by buying companies in software component business. More specifically, the present study examines ‘what are the specific characteristics of the software component supplier relationships?’ and ‘what implications do these have on purchasing in this context?’ This aim is pursued by first developing an understanding based on existing knowledge in industrial purchasing literature. This initial understanding is elaborated empirically through a qualitative case study. The conclusion of the study suggests both theoretical and managerial implications with respect to understanding and managing competitive software component supplier relationships in the emerging market. In more general terms, the study contributes to our knowledge on industrial purchasing in emerging supply markets of technology intensive industries.
نتیجه گیری انگلیسی
This study has addressed purchasing challenges faced by software companies buying commercial software components in an emerging market. The overall purpose of the paper was to find out how we can understand the challenges faced by buying companies in the modern purchasing setting of competitive supplier relationships. More specifically, the present study examined the characteristics of software component supplier relationships and the implications for industrial purchasing in this context. The literature review identified a rather limited number of studies concentrating on the types of supplier interfaces that commercial software component buyers seemed to face. The literature heavily emphasising closer exchange mechanisms between industrial buyers and sellers provides us with very little knowledge that is specifically relevant in the context studied here. Earlier research based on industrial buying behaviour has depicted different types of models for purchasing. This literature emphasised the careful specification of the purchasing process (e.g. Robinson et al., 1967; Webster and Wind, 1972) and purchasing situation (Robinson et al., 1967) for the management of software component supplier relationships. Supplier or product switching costs were assumed to be low or none and the cost of handling the supplier relationship was also assumed to be low, but adapting to the standard products was possibly expensive (Araujo et al., 1999). All in all, a lot of attention was directed at the buying company's internal procedures and the actual exchange situation. In order to elaborate this knowledge, we conducted an empirical study. The following empirical findings were drawn out: • Supplier relationships in the context of software components are long-term. • Supplier relationship management requires a lot of managerial resources. • Buying these components and the management of the component supplier relationships require a lot of technical and purchasing competencies. • Supplier relationship management also requires understanding the whole market, and thus purchasing needs to pay attention to the nature of both supply and demand. 6.1. Nature of the relationship As a starting point of this research, we argued that the types of supplier interfaces that the software component buyers faced are competitive. However, based on the empirical findings, apparently the interfaces between software component sellers and buyers resemble somewhat more close and co-operative relationships. Therefore, it is important to understand more in depth the factors that make software component supplier relationships so difficult to categorise in terms of their competitive or co-operative elements. There exist certain characteristics of the object of exchange and cost structure that can be examined in order to understand the supplier relationships and purchasing in this specific context. The object of exchange, the software component, is regarded as a standard product in software engineering literature. However, it can also be characterised as more complex in terms of nature and life-span of the component. Complexity of the exchange increases when new versions are introduced after the component is integrated into the software system of the final product. In addition to the object, the cost structure of the exchange increases the complexity of the relationship from the industrial purchasing perspective. The underlying assumption of software componentisation is that the costs of buying commercial components are mostly derived from the component itself while relationships costs (costs of handling the exchange and supplier interface) are lower than in sub-contracting, for example. On the basis of our empirical study, this is not the case. Thus, the costs of the exchange are high creating complexities into the relationship as well. The nature of relationship in this specific empirical context thus is a major issue in terms of understanding the challenges faced by buying companies in software component business. The existing literature makes a rather clear distinction between transactional and relational exchanges. However, the present study illustrates an empirical context where both of these exist in the supplier relationship. Thus, it is not a question of transactional or relational exchange, but a relationship where both of these exist simultaneously. Theoretically, this brings forth future research implications, especially in relation to the industrial purchasing literature. The existence of both co-operative and competitive elements in business relationships has been acknowledged in previous research in business-to-business marketing (see e.g. Ford et al., 1998), but in the purchasing perspective the issue deserves more attention on the basis of our study.