Please use this identifier to cite or link to this item: https://dl.eusset.eu/handle/20.500.12015/2816
Full metadata record
DC FieldValueLanguage
dc.contributor.authorLarsson, Andreas
dc.contributor.authorEricson, Åsa
dc.contributor.authorLarsson, Tobias
dc.contributor.authorRandall, Dave
dc.date.accessioned2017-04-15T12:14:14Z-
dc.date.available2017-04-15T12:14:14Z-
dc.date.issued2008
dc.description.abstractIn a traditional business partnership, the partner companies are under contractual obligation to share data, information, and knowledge through one or several information systems that the leading firm decides. In such a case, the issue of sharing “whatever needs to be shared” is settled in contracts before any action is taken, however, also giving the implications that sharing expertise becomes a heavy and time-consuming activity. In turn, it can be argued that the heavy administration affects the lead time of product development negatively since the necessary input flows are delayed. In addition, the adaptation to certain predefined collaborative information systems is both expensive and resource-consuming (e.g., educating staff to use them). Also, the system might not be adaptable to the existing internal technology structure, causing a “translation” procedure, again taking up resources. Another structure for collaboration is a network or alliance of independent partner companies. One motivation for a network structure is that the partners can join or leave it more easily. A reason for joining and staying is an implicit sense of knowledge sharing (Tomkins 2001) and access to a “win–win” environment. Furthermore, the partners can be linked by information technology, i.e., forming a virtual ­structure rather than a physical one. The technologies provide the channels with additional knowledge. In a best-case scenario, a company would get access to a wide range of useful competences, and in a worst-case scenario the company would be drained of its core competences. Accordingly, at least two considerations for joining a partner network can be considered. First, the resources needed to couple the technologies have to be reasonable, due to the underpinning logic of going in and out of more than one network. Second, the company has to identify its knowledge base and evaluate the prospective gains and losses of sharing its expertise.
dc.language.isoen
dc.publisherACM Press
dc.relation.ispartofFrom CSCW to Web 2.0: European Developments in Collaborative Design Selected Papers from COOP08
dc.relation.ispartofseriesCOOP
dc.titleEngineering 2.0: Exploring Lightweight Technologies for the Virtual Enterprise
dc.typeText
mci.conference.date2008-05-20
mci.conference.locationCarry-le-Rouet, France
mci.conference.sessiontitleFull Papers
Appears in Collections:COOP 2008: Proceedings of the 8th International Conference on Designing Cooperative Systems

Files in This Item:
File Description SizeFormat 
00477.pdf154,72 kBAdobe PDFView/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.