Applications of the discrete element method in mechanical engineering

Compared to other fields of engineering, in mechanical engineering, the Discrete Element Method (DEM) is not yet a well known method. Nevertheless, there is a variety of simulation problems where the method has obvious advantages due to its meshless nature. For problems where several free bodies can collide and break after having been largely deformed, the DEM is the method of choice. Neighborhood search and collision detection between bodies as well as the separation of large solids into smaller particles are naturally incorporated in the method. The main DEM algorithm consists of a relatively simple loop that basically contains the three substeps contact detection, force computation and integration. However, there exists a large variety of different algorithms to choose the substeps to compose the optimal method for a given problem. In this contribution, we describe the dynamics of particle systems together with appropriate numerical integration schemes and give an overview over different types of particle interactions that can be composed to adapt the method to fit to a given simulation problem. Surface triangulations are used to model complicated, non-convex bodies in contact with particle systems. The capabilities of the method are finally demonstrated by means of application examples. Commemorative Contribution.     

Beyond Boundary Objects: Collaborative Reuse in Aircraft Technical Support

Boundary objects are a critical, but understudied, theoretical construct in CSCW. Through a field study of aircraft technical support, we examined the role of boundary objects in the practical achievement of safety by service engineers. Their resolution of repair requests was preserved in the organization’s memory via three compound boundary objects. These crystallizations did not manifest a static interpretation, but instead were continually reinterpreted in light of meta-negotiations. This suggests design implications for organizational memory systems which can more fluidly represent the meta-negotiations surrounding boundary objects.     

The incompatibility of knowledge regimes: consequences of the material world for cross-domain work

In this paper, we argue that successful integration of knowledge across work domains in the short-term can mask the generation of long-term consequences. We explore a setting, the introduction of environmental considerations into semiconductor manufacturing, where the eventual adoption of common measurement artifacts and associated practices enabled knowledge integration, but failed to address significant underlying consequences. Drawing from observational, interview, and archival data we develop an understanding of the work practices of the Tech and EnviroTech groups as structured by the material world and broader collective conventions. We introduce the concept of knowledge regime to outline the differences in knowledge across these work domains. More specifically, we find that differences in the causal specificity and developmental time horizon of knowledge and the measurement artifacts that result contribute to the relative power of one knowledge regime over another. Understanding these sources of incompatibility provides insight into the design requirements of information systems as boundary objects for knowledge integration, but also specifies the potential limits to any design effort.     

Design of software systems based on axiomatic design

The ability to utilize fully automated flexible manufacturing systems (FMS) or develop reliable computer-integrated manufacturing (CIM) systems will depend on our ability to develop reliable and reusable software for large complex systems on a timely basis. To date, software design has not gone very far beyond the ad hoc trial-and-error stage. Consequently, the development of software is slow, expensive, unreliable, and unmanageable. The purpose of this paper is to provide a scientific basis for designing software. The approach used here is that of axiomatic design, which is based on two design axioms: the Independence Axiom and the Information Axiom. The axiomatic approach is based on the recognition of the following common elements in design: the existence of independent domains (i.e. the consumer domain, the functional domain, the physical domain, and the process domain); the need to map between various domains during the design process; the decomposition of the characteristic vectors (i.e. functional requirements, design parameters, and process variables) in their respective domains; the zig-zagging required between the domains for decomposition; and the need to satisfy the design axioms during the design process. The axiomatic approach discussed in this paper provides decision making tools for software design in addition to systematic means of knowledge and data representation, synthesis and analysis of software, and the construction of the module-junction structure diagram.