24,679 research outputs found

    Feature-based representation for assembly modelling

    Get PDF
    The need for a product model which can support the modelling requirements of a broad range of applications leads to the application of a feature-based model. An important requirement in feature-based design and manufacture is that a single feature representation should be capable of supporting a number of different applications. The capability of representing products composed of assemblies is seen to be necessary to serve the information needs of those applications. To achieve this aim it is an essential prerequisite to develop a formal structure for the representation of assembly information in a feature-based design system. This research addresses two basic questions related to the lack of a unified definition for features and the problem of representing assemblies in a feature-based representation. The intention is to extend the concept of designing with features by incorporating assembly information in addition to the geometrical and topological details of component parts. This allows models to be assembled using the assembly information within the feature definitions. Features in this research are defined as machined volumes which are represented in a hierarchical taxonomy. The taxonomy includes several types and profiles of features which cover a general range of machined parts. A hierarchical assembly structure is also defined in which features form basic entities in the assembly. Each feature includes information needed to establish assembly relationships among features in the form of mating relationships. An analysis of typical assemblies shows that assembly interfaces occur at the face level of the mating features and between features themselves. Three mating relationships between pairs of features have been defined (against, fits and align) and are represented in the form of expressions that can be used for evaluations. Various sub-types of these major mating relationships can be identified (e.g. tight fit, clearance fit, etc.) and represented through the use of qualifying attributes. Component Relation Graphs, Feature Relation Graphs and Face Mating Graphs have been developed to represent each level of interaction in an assembly, and assembly relationships are combined with knowledge on process planning into a Component Connectivity Graph. These graphs are used as the basis for deriving an integrated data structure which is used for defining classes for each level in the assembly hierarchy. The implementation of a prototype system has been facilitated by use of an object-oriented programming technique which provides a natural method of adding functionality to the geometric reasoning process of features and the complex relationships between the parts that make up the assembly. The feature-based model is embedded in an object-oriented solid modeller kernel, ACIS®. The research demonstrates the possibilities for a single feature representation to support multiple activities within a computer integrated manufacturing environment. Such a representation can form the basis of design improvement techniques and manufacturing planning as well as be a model to support the life cycle of the product

    Generating target system specifications from a domain model using CLIPS

    Get PDF
    The quest for reuse in software engineering is still being pursued and researchers are actively investigating the domain modeling approach to software construction. There are several domain modeling efforts reported in the literature and they all agree that the components that are generated from domain modeling are more conducive to reuse. Once a domain model is created, several target systems can be generated by tailoring the domain model or by evolving the domain model and then tailoring it according to the specified requirements. This paper presents the Evolutionary Domain Life Cycle (EDLC) paradigm in which a domain model is created using multiple views, namely, aggregation hierarchy, generalization/specialization hierarchies, object communication diagrams and state transition diagrams. The architecture of the Knowledge Based Requirements Elicitation Tool (KBRET) which is used to generate target system specifications is also presented. The preliminary version of KBRET is implemented in the C Language Integrated Production System (CLIPS)

    Advanced manned space flight simulation and training: An investigation of simulation host computer system concepts

    Get PDF
    The findings of a preliminary investigation by Southwest Research Institute (SwRI) in simulation host computer concepts is presented. It is designed to aid NASA in evaluating simulation technologies for use in spaceflight training. The focus of the investigation is on the next generation of space simulation systems that will be utilized in training personnel for Space Station Freedom operations. SwRI concludes that NASA should pursue a distributed simulation host computer system architecture for the Space Station Training Facility (SSTF) rather than a centralized mainframe based arrangement. A distributed system offers many advantages and is seen by SwRI as the only architecture that will allow NASA to achieve established functional goals and operational objectives over the life of the Space Station Freedom program. Several distributed, parallel computing systems are available today that offer real-time capabilities for time critical, man-in-the-loop simulation. These systems are flexible in terms of connectivity and configurability, and are easily scaled to meet increasing demands for more computing power

    Specifications and Development of Interoperability Solution dedicated to Multiple Expertise Collaboration in a Design Framework

    Get PDF
    This paper describes the specifications of an interoperability platform based on the PPO (Product Process Organization) model developed by the French community IPPOP in the context of collaborative and innovative design. By using PPO model as a reference, this work aims to connect together heterogonous tools used by experts easing data and information exchanges. After underlining the growing needs of collaborative design process, this paper focuses on interoperability concept by describing current solutions and their limits. Then a solution based on the flexibility of the PPO model adapted to the philosophy of interoperability is proposed. To illustrate these concepts, several examples are more particularly described (robustness analysis, CAD and Product Lifecycle Management systems connections)

    Army-NASA aircrew/aircraft integration program (A3I) software detailed design document, phase 3

    Get PDF
    The capabilities and design approach of the MIDAS (Man-machine Integration Design and Analysis System) computer-aided engineering (CAE) workstation under development by the Army-NASA Aircrew/Aircraft Integration Program is detailed. This workstation uses graphic, symbolic, and numeric prototyping tools and human performance models as part of an integrated design/analysis environment for crewstation human engineering. Developed incrementally, the requirements and design for Phase 3 (Dec. 1987 to Jun. 1989) are described. Software tools/models developed or significantly modified during this phase included: an interactive 3-D graphic cockpit design editor; multiple-perspective graphic views to observe simulation scenarios; symbolic methods to model the mission decomposition, equipment functions, pilot tasking and loading, as well as control the simulation; a 3-D dynamic anthropometric model; an intermachine communications package; and a training assessment component. These components were successfully used during Phase 3 to demonstrate the complex interactions and human engineering findings involved with a proposed cockpit communications design change in a simulated AH-64A Apache helicopter/mission that maps to empirical data from a similar study and AH-1 Cobra flight test

    THREAD: A programming environment for interactive planning-level robotics applications

    Get PDF
    THREAD programming language, which was developed to meet the needs of researchers in developing robotics applications that perform such tasks as grasp, trajectory design, sensor data analysis, and interfacing with external subsystems in order to perform servo-level control of manipulators and real time sensing is discussed. The philosophy behind THREAD, the issues which entered into its design, and the features of the language are discussed from the viewpoint of researchers who want to develop algorithms in a simulation environment, and from those who want to implement physical robotics systems. The detailed functions of the many complex robotics algorithms and tools which are part of the language are not explained, but an overall impression of their capability is given

    A distributed agent architecture for real-time knowledge-based systems: Real-time expert systems project, phase 1

    Get PDF
    We propose a distributed agent architecture (DAA) that can support a variety of paradigms based on both traditional real-time computing and artificial intelligence. DAA consists of distributed agents that are classified into two categories: reactive and cognitive. Reactive agents can be implemented directly in Ada to meet hard real-time requirements and be deployed on on-board embedded processors. A traditional real-time computing methodology under consideration is the rate monotonic theory that can guarantee schedulability based on analytical methods. AI techniques under consideration for reactive agents are approximate or anytime reasoning that can be implemented using Bayesian belief networks as in Guardian. Cognitive agents are traditional expert systems that can be implemented in ART-Ada to meet soft real-time requirements. During the initial design of cognitive agents, it is critical to consider the migration path that would allow initial deployment on ground-based workstations with eventual deployment on on-board processors. ART-Ada technology enables this migration while Lisp-based technologies make it difficult if not impossible. In addition to reactive and cognitive agents, a meta-level agent would be needed to coordinate multiple agents and to provide meta-level control
    • …
    corecore