SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "LAR1:hh srt2:(2005-2009);pers:(Danilovic Mike 1955)"

Sökning: LAR1:hh > (2005-2009) > Danilovic Mike 1955

  • Resultat 1-10 av 13
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Danilovic, Mike, 1955-, et al. (författare)
  • Analyzing core competence and core products for developing agile and adaptable corporation
  • 2007
  • Ingår i: Proceedings of the 9th International DSM Conference. - Aachen : Shaker Verlag. - 9783832266417 ; , s. 49-59
  • Konferensbidrag (refereegranskat)abstract
    • IntroductionThe core competence concept was introduced by Prahalad and Hamel in 1990, and the concept received much attention particularly in the management field. They were arguing that in short run, a company’s competitiveness derives from the price/performance attributes of current products. On the other hand, in the long run the competitiveness derives from an ability to build the core competencies that spawn unanticipated products. The real source of corporate advantage is the abilities to consolidate corporate technologies and products in order to adapt quickly to changing business opportunities (Prahalad & Hamel, 1990).Core competencies are seen as collective learning in the organization, not individually based learning or skill (Gallon, Stillman & Coates, 1995). Core competence is the way of work is performed, the ability to coordinate diverse production skills, to integrate and harmonize multitude of skills and technologies into products that deliver value to customers. Core competencies are the glue that binds existing business and also the engine for new business development (Prahalad & Hamel, 1990). Core competence is a combination of complementary skills and knowledge bases embedded in a group or team providing a superior product (Coyne, Hall & Clifford, 1997). Core competence has to be linked with end products. In between core competencies and end products we can identify a set of core products that can be used in a number of different combinations and finally different end products.  Therefore there are numerous relations between core competencies, core products and end products.Global competition and the dynamic changes of markets and customers puts pressure on corporations to identify their core competencies in order to develop capabilities to adopt to changing environment and technological development. The crucial issue for management is to perform analysis of what the core competence is in their corporation and how those core competencies can be related to core products and end products. If management does not find those answers they can not put focus in developing long run competencies and technologies that can be combined in a set of core products and strategic end products.
  •  
2.
  • Danilovic, Mike, 1955-, et al. (författare)
  • Corporate Manufacturing Network – From Hierarchy To Self-Organizing System
  • 2006
  • Ingår i: The International Journal of Integrated Supply Management. - 1477-5360 .- 1741-8097. ; 2:1/2, s. 106-131
  • Tidskriftsartikel (refereegranskat)abstract
    • It is important for small and medium-sized corporations to collaborate in networks in order to develop capacity, capability, and competence to perform product development and become suppliers of complete systems. The purpose of this case study is to identify barriers and to develop an analytical framework of inter-organizational collaboration in network settings. In this paper we present a tentative four-dimensional framework in terms of surface of integration, scope of integration, time horizon of integration, and intensity of integration. This framework can be used to analyze how network settings are developed, in terms of structural design of the network, the design of the workflow in collaborative settings, and the aspects of handling the psychological and social boundaries between people.
  •  
3.
  • Danilovic, Mike, 1955-, et al. (författare)
  • Managing Complex Product Development Projects with Design Structure Matrices and Domain Mapping Matrices
  • 2007
  • Ingår i: International Journal of Project Management. - Oxford : Elsevier BV. - 0263-7863 .- 1873-4634. ; 25:3, s. 300-314
  • Tidskriftsartikel (refereegranskat)abstract
    • Complexity in product development (PD) projects can emanate from the product design, the development process, the development organization, the tools and technologies applied, the requirements to be met, and other domains.  In each of these domains, complexity arises from the numerous elements and their multitude of relationships, such as between the components of the product being developed, between the activities to develop them, and among the people doing the activities. One approach to handing this complexity is to represent and analyze these domains’ design structures or architectures.  The Design Structure Matrix (DSM) has proved to be a very helpful tool for representing and analyzing the architecture of an individual system such as a product, process, or organization. Like many tools, the DSM has been applied in a variety of areas outside its original domain, as researchers and practitioners have sought to leverage its advantages.  Along the way, however, its fundamental rules (such as being a square matrix) have been challenged.  In this paper we formalize an approach to using a Domain Mapping Matrix (DMM) to compare two DSMs of different project domains.  A DMM is a rectangular (m x n) matrix relating two DSMs, where m is the size of DSM1 and n is the size of DSM2.  DMM analysis augments traditional DSM analyses. Our comparison of DSM and DMM approaches shows that DMM analysis offers several benefits.  For example, it can help (1) capture the dynamics of PD, (2) show traceability of constraints across domains, (3) provide transparency between domains, (4) synchronize decisions across domains, (5) cross-verify domain models, (6) integrate a domain with the rest of a project or program, and (7) improve decision making among engineers and managers by providing a basis for communication and learning across domains.
  •  
4.
  • Danilovic, Mike, 1955-, et al. (författare)
  • Multi-Domain Matrices : Another Perspective
  • 2008
  • Ingår i: Proceedings of the 10th International DSM Conference. - Munich : Carl Hanser Verlag GmbH. - 9783446418257 ; , s. 55-67
  • Konferensbidrag (refereegranskat)abstract
    • With ever increasing competition, companies are collaborating in networks with projects increasingly spanning across different teams in companies with divisions in different geographical locations and with partner companies with different specializations. This creates the situation in which different companies must interact effectively to achieve a common goal in a multi-domain network environment. In this paper, a new approach for Multi-Domain Matrix (MDM) analysis based on empirical research on 4 companies in a network is presented. The approach builds on the perspective that the MDM consists of several matrices whose interrelationships can be explored. The perspective leads to the formulation of an aggregation of novel concepts for Multi-Domain Analysis which in turn leads us to a novel MDM phenomenon of managerial importance which has been named supercircuit in this paper.
  •  
5.
  • Danilovic, Mike, 1955-, et al. (författare)
  • Rethinking the platform approach in automotive industry
  • 2009
  • Ingår i: POM 2009. - Orlando, FL : Production and Operations Management Society. ; , s. 1-17
  • Konferensbidrag (refereegranskat)abstract
    • In many industrial areas, such as in automotive industry, the development of joint technology platforms is seen as an enabler for improving efficiency, facilitating frequent and rapid new product and technology introductions, as well as transfer of production between units.During the present financial recession especially in the automotive industry, it has become obvious that there might be extensive drawbacks from using integrated platforms for several brands if different companies within large industrial groups are extremely integrated in terms of organization, technology, and know-how. In integrated product structures, major product changes, however, become more difficult and more expensive to carry out. If companies have products based on very different technologies, integration is also not easily achieved and it may be almost impossible to merge several brands into one group and one platform.In this paper we identify implications of widely implemented integrated technology platform thinking in automotive industry.
  •  
6.
  • Danilovic, Mike, 1955- (författare)
  • Supplier Integration in Product Development – A Matter of Designing the Project Structure.
  • 2006
  • Ingår i: South African Journal of Transportation and Supply Chain Management. - Johannesburg. ; 1:1, s. 18-37
  • Tidskriftsartikel (refereegranskat)abstract
    • In product development close collaboration between systems integrators and suppliers is important. The purpose of this article is to investigate the impact of the work breakdown structure (WBS) and work packages (WP) in product development on the possibilities to carry through the strategy of supplier involvement into collaborative practice and to investigate how supplier involvement can be improved by altering the design of collaborative WBS and WP structures. Dependence Structure Matrix (DSM) is introduced in order to analyze, visualize and manage interdependencies, in terms of information exchange between systems integrator and supplier. This article shows how DSM can support alternative design of integrated and collaborative WBS and integrated WP following the logic of dependencies and the flow of information in order to support a strategy focusing on integration of suppliers on the project and team level.
  •  
7.
  • Danilovic, Mike, 1955-, et al. (författare)
  • The Use Of Dependence Structure Matrix and Domain Mapping Matrix in Managing Uncertainty in Multiple Project Situations
  • 2005
  • Ingår i: International Journal of Project Management. ; 23, s. 193-203
  • Tidskriftsartikel (refereegranskat)abstract
    • Development of complex products is performed in multi-project environment in which it is crucial to explore interdependencies and manage the uncertainty with the information exchange and the understanding of the context. The purpose of this paper is to introduce a dependence structure matrix and domain mapping matrix approach that enables the systematic identification of inter- dependencies and relations in a Multi-project environment. These approaches enables clarifications of assumptions, the tractability of dependencies, explores the information needed within and between different departments, projects and people. This creates a transparency and enables the synchronization of actions through transformation of information and exploration of assumptions within and between domains. The outcomes of this process are situational visibility creating direction and accountability and the learning that takes place through communicating, reflecting, understanding, and acting.
  •  
8.
  • Khudyakova, Tatyana, et al. (författare)
  • System-level based IDM/DSM/DMM dataset for multi-project coordination
  • 2007
  • Ingår i: Proceedings of the 9th International DSM Conference. - Aachen : Shaker Verlag. - 9783832266417 ; , s. 393-402
  • Konferensbidrag (refereegranskat)abstract
    • For many product development companies a multi-project situation is reality driven by competitive environment: offering customers a variety of new, more complex, high performing yet flexible products at a shortest possible time and lowest cost. Customers’ product complexity is however not an equivalent of the product development complexity and, while striving to deliver highly sophisticated products, development companies use various complexity management techniques in order to control and minimize it internally. High level of modularization, well-defined interfaces between the modules and components commonality & standardization are some factors contributing to complexity reduction. The benefits (according to Anderson, 1997) would be a capability to rapidly introduce incremental product improvements which can be called "new" products — that are really planned "variations on a theme," based on common parts and modular product architecture. Independent design of system components allows for clear definition of project boundaries and scopes within a project development portfolio, minimization of uncertainty and results in reduction of development cycle and ultra-fast time-to- market. However, according to Kentaro & Cusumano (1993) “…focusing on design modification is not advantageous strategy either in terms of the new product introduction rate or average platform design age”. According to Whitney, some products, like high power mechanical ones, as opposed to low power signal processor type products, would benefit from more integral design if technical performance is a priority. Technical constraints, such as light weighting, low power consumption etc. drive designers towards more integral architectures (adopted from Hölttä-Otto, 2005). Integral architecture is characterized by multiple dependencies between system entities (where entities could be functions, physical or non-physical elements), when interfaces are difficult to define clearly.  Kentaro & Cusumano (1993) demonstrated that system-level co-ordination is required between different projects when composing and optimizing a project portfolio for complex products with integrated architecture. A practice of early enforcement of restrictions upon the project scope /requirements in order to avoid potential system-level dependency conflicts with other projects makes further development process less flexible and responsive to changing business requirements such as costs, product flexibility etc. Resolving system-based interdependency-related issue has traditionally been seen as system architect’s task: ”...architects’ greatest concerns and leverage are still, …with the systems’ connections and interfaces because (1) they distinguish a system from its components; (2) their addition produce unique system-level functions, a primary interest of the systems architect; (3) subsystem specialists are likely to concentrate most on the core and lest on the periphery of their subsystems (Maeir & Rechtin, 2002). Other players like development project group members and management in general have often limited access to dependency-based system views and use intuitive approach when dealing with dependencies., hence a transfer of knowledge is essential to be able to support flexibility in system-level project co-ordination.
  •  
9.
  • Kreimeyer, Matthias, et al. (författare)
  • Team composition to enhance collaboration between embodiment design and simulation departments
  • 2007
  • Ingår i: DS 42. - Bristol : The Design Society. - 1904670024
  • Konferensbidrag (refereegranskat)abstract
    • Efficient collaboration between design and simulation departments is a key factor to efficient product development. There are numerous efforts to systematically “integrate” product development activities using CAD- and CAE-systems.This paper presents a team-based approach to render collaboration, i.e. communication and coordination, between the engineers involved in designing and simulating the product more efficient. It is part of an overall integration strategy to support collaboration between the departments in question in terms of the product architecture and the engineers involved as well as information objects, tools, and the process.The team structures proposed combine the different ways of organization prevailing in design and simulation. Based on a product architecture regarding both functional and geometry-oriented perspectives onto the product, virtual teams attributed to parts of this component-function-structure serve as a basis to enhance communication. This is intended to offer a means of orientation to coordinate common efforts between engineers involved. The paper lines out a method to compose teams that merge the necessary competences and responsibilities involved to foster communication across different engineers involved in a set of functions and components.
  •  
10.
  • Proceedings of the 10th International DSM Conference : Stockholm, 11 and 12 November 2008
  • 2008
  • Proceedings (redaktörskap) (refereegranskat)abstract
    • The proceedings contain 34 papers. The topics discussed include: introduction of software related DSMs to software engineers; modeling structural change over time - requirements and first methods; an approach to model time dependent process-stakeholder networks; indirect connections in a supply chain: visualisation and analysis; applying Apollo to DSM for schedule adherence visualisation; advanced project management framework for product development; simulation of product change effects on the duration of development processes based on the DSM; a complexity measure for concurrent engineering projects based on the DSM; assessing design strategies from a change propagation perspective; re-engineering legacy knowledge based engineering systems using DSM: extending the affordance structure matrix - mapping design structure and requirements to behavior; and using the design structure matrix (DSM) and architecture options to optimize system adaptability.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 13

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy