EP1917611A2 - Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur - Google Patents

Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur

Info

Publication number
EP1917611A2
EP1917611A2 EP06778219A EP06778219A EP1917611A2 EP 1917611 A2 EP1917611 A2 EP 1917611A2 EP 06778219 A EP06778219 A EP 06778219A EP 06778219 A EP06778219 A EP 06778219A EP 1917611 A2 EP1917611 A2 EP 1917611A2
Authority
EP
European Patent Office
Prior art keywords
objects
component
parameter
data model
resolution
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP06778219A
Other languages
German (de)
English (en)
Inventor
Martin FRÖHLICH
Frank Neumann
Armin Ortmann
Torsten Thiele
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Pace Aerospace Engineering and Information Technology GmbH
Original Assignee
Pace Aerospace Engineering and Information Technology GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Pace Aerospace Engineering and Information Technology GmbH filed Critical Pace Aerospace Engineering and Information Technology GmbH
Publication of EP1917611A2 publication Critical patent/EP1917611A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/10—Geometric CAD
    • G06F30/17—Mechanical parametric or variational design
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2111/00—Details relating to CAD techniques
    • G06F2111/04—Constraint-based CAD

Definitions

  • the invention relates to a device for the conception or configuration of a machine object represented by an object data model.
  • the design process can roughly be divided into the following phases:
  • the documentation phase which completes the product development process, generates the necessary technical publications, plans the corporate structures required for production, structures for support of product retrofit (Retrofit Support) and lifecycle documentation.
  • the present invention relates to development processes in phases a), conception, or c), configuration.
  • the software platforms contain an interface through which various software tools are integrated. Different interface types are known.
  • the spectrum ranges from an application call with file-based communication for data exchange via network-like communication protocols to tailored coding of special application interfaces (API).
  • API application interfaces
  • KBE Knowledge-Based Engineering
  • CAD Computer Aided Generation
  • Disadvantage of both products is that the embedding of knowledge in the system is not uniform.
  • rule-based definition techniques and check mechanisms for activating the rules are used, or script interfaces such as VisualBasic or C ++ programming interfaces are provided.
  • DesignSheet Another well-known product is Rockwell Scientific's "DesignSheet.” DesignSheet's goal is to analyze conceptual designs, which are defined by variables and constraints.Constraints are algebraic equations that are symbolically defined on a user interface in Designsheet DesignSheet assumes that equations are explicitly present in symbolic form and can be resolved symmetrically after each variable involved, which limits the usability of designsheets because in practice constraints are often based on analysis functions that implement in a programming language Furthermore, functions define non-symmetric, ie directional constraints (directed from input to output) so that solving after the output of a function is simple, but after the input it is difficult and only numeric, but not symbol is possible. DesignSheet continues to be limited to the conceptual design analysis.
  • a KBE application is also the subject of WO 02/0734723 A1, which relates to an apparatus and method for configuring the interior of vehicles, in particular aircraft.
  • a user calls one in this procedure certain type of aircraft and can then modify the configuration by symbolic inputs via a graphical user interface. In doing so, the admissibility of the modifications made with regard to regulations of state authorities is ensured by means of implemented monitoring procedures and indicated in case of infringement.
  • Disadvantage of this device is on the one hand its limitation to the task of the configuration. On the other hand, the device restricts the user to a fixed repertoire of predefined modification possibilities of a particular aircraft type.
  • the technical problem underlying the invention is therefore to provide a device for the conception of a machine object using an object data model in the form of a system of equations, which provides a uniform embedding of engineering knowledge in the device and allows with particularly high flexibility, data models of machine components and - Objects and design rules in the conceptual design of different machine objects to use ..
  • the device according to the invention for the conception or configuration of a machine object using an object data model that can be represented, for example, by an equation system is specified in claim 1.
  • Preferred embodiments of the device according to the invention define the dependent claims.
  • the inventive device for conception, preliminary design and configuration of a machine object represented by an object data model has an object database containing component objects in the form of component data models.
  • a component object or component data model has in a simple form a parameter object or a plurality (in the context of this application in the sense of "multiplicity" to understand) parameter objects that can take a numeric or a non-numerical parameter value from a respective predetermined range of values
  • Numerical parameter values are, for example, numbers of the type double, float or unit-related values.
  • Non-numerical parameter values are, for example, For example, data structures of the type array or string, or discrete variables, such as of the type integer, can also be formed by geometry objects or component objects themselves.
  • a particularly preferred embodiment contains parameter objects in the form of unit-related physical quantities.
  • Component objects thus encapsulate the component-specific engineering knowledge with respect to the parameters, wherein in preferred exemplary embodiments, the relationships between the parameters are additionally detected by formula objects and the geometry of the component objects.
  • the object database of the device according to the invention also contains function objects.
  • a respective functional object is configured to form a predetermined link between two or more parameter objects of different component objects, modify parameter values contained in a component object, add a component object to the object data model and set parameter values of the added component object, or from the object data model Remove component object.
  • functional objects thus represent design strategic engineering know-how which advances the respective stage of a design process and analyzes a product status achieved in each case.
  • the modeling approach implemented by the separation of component objects and functional objects according to the invention makes it possible to distinguish between constraints within a component object (for example the value of a non-changeable parameter object) and boundary conditions that exist between components.
  • the former are captured by the component objects themselves, the latter by the function objects.
  • This encapsulation has the particular advantage that the modeling process can be made much clearer.
  • the encapsulation allows the reuse of the component objects in different machine objects, even in different technical systems such as different types of aircraft. This considerably increases the freedom of design of the user and solves the binding to each specified systems, as known from WO 02/073473 A1 in the form of airplane interior design (AIC), which is firmly related to an aircraft type.
  • AIC airplane interior design
  • the device according to the invention also contains a modeling unit which is connected to the object database and which is designed to generate a component object instance of a component object contained in the object database or a function object instance of a function object contained in the object database and to add it to an object data model , Furthermore, the modeling unit is designed to correspondingly modify the object data model to the input of an instruction for linking different component objects to one another or to component objects with function objects, and to mark a parameter object as input parameter or output parameter of a resolution process upon receipt of a corresponding instruction.
  • a user of the device according to the invention can design an object data model, accessing the component and function objects formed by the object database.
  • the device contains an execution unit which is connected to the model formation unit and to the object database and which is designed to execute a function object instance contained in the object data model with modification, addition or destruction with component objects of the object data model linked to it, based on the input of a corresponding execution instruction.
  • the device according to the invention is capable of analyzing, supplementing or modifying a current design stage of an object data model by executing suitably defined function objects.
  • the already mentioned advantages of the object structures according to the invention in the object database make it possible to reconcile the area spanning a respective design stage. automatically explore native designs by executing function objects to determine a suitable design.
  • the device according to the invention particularly preferably contains a resolution unit which is connected to the model-forming unit and to the object database.
  • the resolution unit is designed
  • This device in terms of its usability, covers a range of design stages that may not be reached in its scope by known devices, including the design, pre-design, and configuration of machine objects. So it becomes possible to use a design tool for many different design stages. Therefore, the problems of compatibility between data formats of different applications in conception, preliminary design and configuration, which have hitherto arisen, are eliminated. This is made possible by the above-described inventive structure of the component objects and functional objects.
  • the resolution unit directly accesses this structure when determining the links between the parameters contained in the object data model. This determination is greatly simplified over known resolution systems. A user does not have to do a symbolic input of equations, as it is known from the product DesignSheet.
  • a parameter object of a component object contained in the object database is formed by a further component object having at least one further parameter object.
  • a component object contained in the object database additionally contains a structure object which contains a list of the further component objects contained in the component object.
  • the hierarchical structure of the component objects corresponds to the situation encountered in actual life in the design of complex systems, that they are composed of separable components.
  • a component object contained in the object database additionally contains at least one formula object which is designed to form a predetermined mathematical link between two or more parameter objects of the component object.
  • This guide implements functional boundary conditions within a component object in the form of formula objects.
  • Formula objects are thus distinguished from the function objects in that they do not create a link between a component object and an external component object, but create links within the same component object alone.
  • This structure creates additional possibilities for mapping boundary conditions and at the same time strengthens the encapsulation of the constraints already created by the separation of component objects and function objects.
  • a component object contained in the object database additionally contains at least one method object which is designed to check the fulfillment of a relation between parameter objects of the component object and, depending on the test result, a value of at least one of the parameter objects included in the component objects according to a predetermined rule or to add a new component object or subcomponent object to an object data model.
  • Subcomponent objects form all objects contained in the component object, in particular parameter objects, formula objects, method objects, geometry objects and structure objects.
  • Method objects thus represent design knowledge with respect to a given component object. They can involve complex decisions or conditional operations. They are called in particular from formula objects in order to assign a value to a parameter object or to generate new component object structures.
  • method objects can be implemented in the form of complex, many-pronged C ++ methods.
  • the object database additionally contains at least one rule object that is designed to check the object data model or a component object or subcomponent object or its parameter values contained therein to fulfill a predefined boundary condition.
  • Rule objects capture design, manufacturing, customer or Product certification requirements to be met by the machine object.
  • rule objects are limited to more complex requirements that go beyond a mere comparison of parameter objects.
  • the modeling unit is connected to a graphical user interface and includes a graphics unit.
  • the graphics unit is designed to generate or modify a graphical representation of the object data model based on instructions received via the graphical user interface.
  • the graphical representation has for each component object, each formula object and each rule object of the object data model and each link between them each a predetermined graphic element.
  • the graphics unit is furthermore preferably designed to output the graphical representation to the graphical user interface.
  • a user may graphically create an object data model as a mathematical model via the graphical user interface, without the need to symbolically input the equations of the system.
  • the mathematical system is represented graphically, for example in the form of blocks connected by lines. As a result, graphical manipulations on these blocks, for example by manipulating a computer mouse, modify the mathematical model.
  • the creation of the mathematical equation system is carried out automatically by the resolution unit.
  • the graphics engine is configured to generate and output graphical representation of a number of component objects and functional objects contained in the object database and to output to the graphical user interface a graphical representation of the object data model containing all component objects contained therein and one contained therein Structure objects reflects a defined component object hierarchy.
  • a user may To recognize particularly clearly the component structure of the machine object in the design and to supplement or modify it by graphical manipulations.
  • the resolution unit includes a resolution diagnostic unit connected to the graphical user interface and configured to
  • This exemplary embodiment has the advantage that solution possibilities are determined for overcoming the under-determination of the mathematical model, to which the user is informed by the diagnosis message. He can then reduce or eliminate the sub-determination by setting the determined parameter object as an input parameter and by determining the parameter value.
  • the diagnostic message preferably contains all objects contained in the sub-determined subsystem. Depending on the diagnosis, both equations and parameters can occur in the diagnostic message.
  • the resolution diagnostic unit is additionally designed to determine at least one overdetermined parameter object in the presence of an overdetermined sub-system and to generate a diagnostic message that identifies the determined parameter object and to the graphical user interface Output user interface.
  • the diagnostic message preferably contains all objects contained in the overdetermined subsystem. Depending on the diagnosis, both equations and parameters can occur in the diagnostic message.
  • An intuitive graphical output of the diagnosis by the resolution diagnostic unit succeeds in an exemplary embodiment in which the resolution diagnostic unit is designed to additionally identify at least one further parameter object linked to the determined parameter object in the diagnostic message and output it to the graphics unit, and in which the graphics unit is designed. to generate a graphical representation of the determined parameter object, the further parameter object and their link and output to the graphical user interface for common representation with the diagnosis message.
  • the resolution diagnostic unit is designed to additionally identify at least one further parameter object linked to the determined parameter object in the diagnostic message and output it to the graphics unit, and in which the graphics unit is designed. to generate a graphical representation of the determined parameter object, the further parameter object and their link and output to the graphical user interface for common representation with the diagnosis message.
  • a component object includes a geometry object in the form of a set of geometry parameters having information about a geometric shape associated with the first parameter object.
  • the graphics unit is designed to use the input parameter values and the determined output parameter values of an object data model to determine values of the geometry parameters of all parameter objects and to generate a model graphic which corresponds to the geometric shape of the machine object with the determined geometry parameters.
  • the graphics unit is additionally designed to create and output an impact graphic that contains a graphical representation of all component objects, formula objects and rule objects that are directly or indirectly linked to a parameter object that can be selected via the user interface. In this way, it is determined and presented to the user, which other objects are influenced by the selected parameter object.
  • the graphics unit is additionally designed to create and output a computation graphic that contains a graphic representation of all component objects, formula objects and rule objects that directly or indirectly influence the calculation of a parameter value of a parameter object that can be determined as an output parameter via the user interface incorporated. This allows the user a visual and thus fast and effective analysis of the influence of other objects on a selected parameter object.
  • the resolution unit has a solver diagnostic unit which is designed
  • an embodiment of the device according to the invention proves to be particularly fast in comparison with known devices, in which the resolution unit is additionally designed, after an output of the determined If there is a change in the input parameter set for the object data model, values of the output parameters for the object data model are to be determined by the input parameter set of the input parameter set, and then a partial resolution plan is to be created which only contains those resolution steps that relate to the comparison systems, the solution of which or the changed one Input parameters depends directly or indirectly. In this embodiment, therefore, not the entire resolution process with the changed input parameter values has to be repeated. Rather, only those steps of the resolution process are determined and executed that are influenced by the changed input parameter values. In this way, input parameters can be quickly tested by the user and the design and pre-design process is therefore made more effective.
  • an optimal solution of the mathematical model is determined under given boundary conditions.
  • the modeling unit is designed to supplement an already solved object data model by a target relation entered via the user interface for the value of an output parameter.
  • the resolution unit is designed to create a partial solution plan that contains only those resolution steps relative to the previously created resolution step, which relate to sub-systems whose solution influences the output parameter limited by the target relation, and determine the parameter set that uses the equation system using an optimization algorithm solves and satisfies the target relation.
  • known optimization algorithms can be used. For example, a target parameter, an optimization type (minimization, maximization), an optimization algorithm, free parameters and constraints can be set via a dialog.
  • the mathematical system is then repeatedly solved by varying the free parameters, the resolution unit being designed to process only the partial resolution plan that is influenced by the free parameters.
  • the result is an assignment of the free parameters, which optimizes the target parameter while maintaining the constraints.
  • a component object drafting unit is provided that is connected to the graphical user interface and the object database and that is configured to generate a new component object or parameter object according to a user input at the graphical user interface and a parameter object or a new component object Add function object.
  • the component object design unit is preferably designed to display on the graphical user interface a mask with mask fields for querying definition elements of a new parameter object or component object, evaluate user entries in the mask fields, to generate the parameter object or component object corresponding to the entries in the mask fields and to store them in the object database ,
  • This variant saves the user the input of complex data structures and allows a simple and clear, individual creation of new component objects that are added to the object database. It is understood that in a larger enterprise context the release of the newly created objects in the object database for other users may be subject to predetermined rules.
  • a further preferred embodiment alternatively or additionally contains a functional object design unit which is connected to the graphical user interface and the object database and which is designed to generate a new functional object and to store the new functional object in the object database in accordance with a user input at the graphical user interface.
  • the functional object design unit is designed to display on the graphical user interface a mask with mask fields for querying definition elements of a new function object, to evaluate entries in the mask fields, to generate the new function object corresponding to the entries in the mask fields and to store it in the object database.
  • Another embodiment includes a rule object drafting unit connected to the graphical user interface and the object database and configured to generate a new rule object according to a user input at the graphical user interface and to store the new rule object in the object database.
  • Another aspect of the invention relates to a computer software product for designing, pre-designing, or configuring a machine object represented by an object data model containing code for implementation
  • a component object comprises a parameter object or a plurality of parameter objects which can assume a numerical or a non-numerical parameter value from a respectively predetermined value range;
  • 1.1.2.2 to modify parameter values contained in a component object
  • 1.1.2.3 add a component object to the object data model and set parameter values of the added component object
  • the computer software product of the present invention is for implementing the previously described device on a computer system. Depending on the application environment, this can be a single-user computer or a network formed by several computers communicating with one another.
  • Embodiments of the computer software product according to the invention contain code for implementing the above-described embodiments of the device according to the invention. The embodiments can be combined with each other.
  • FIG. 1 shows a block diagram of a first exemplary embodiment of a design device
  • FIG. 2 is a block diagram of a second embodiment of a design apparatus
  • FIG. 3 is a block diagram of a network-based design device
  • FIG. 4 shows a block diagram for a more detailed explanation of a system for generating object data for the object database
  • FIG. 5 is a diagram illustrating the structure of a component object
  • FIG. 6 is a diagram for explaining a component object concept
  • Figure 7 is a block diagram for explaining the relationships between component object categories, component object concepts and
  • FIG. 8 is a diagram for explaining various types of functional objects
  • FIG. 9 shows a diagram for explaining the structure of a controlled object
  • FIG. 10 shows a more detailed block diagram of a further embodiment of a design device
  • FIG. 11 is a block diagram showing in more detail the analysis unit of the resolution unit of FIG. 10;
  • FIG. 12 shows a simple example of a dependency graph as determined by the analysis unit.
  • Figure 13 shows as a result of combinatorial analysis and graph decomposition in the analysis unit the system shown in Figure 12 with a decomposed dependence graph from which a resolution plan can be derived.
  • FIG. 1 shows an exemplary embodiment of a device 100 according to the invention for the conceptual design of a machine object.
  • the device contains an object database 102 in which predefined component objects, function objects and rule objects are stored.
  • object database 102 in which predefined component objects, function objects and rule objects are stored.
  • the device further includes a unit 104, hereinafter referred to as a knowledge designer.
  • the knowledge designer is connected to the object database 102.
  • the Knowledge Designer enables the definition and modification of component objects, function objects and rule objects. Newly created or modified objects are stored in the object database 102.
  • the object database 102 generates a new version for each modified object, which is identified by a corresponding version number.
  • Using the knowledge designer and the object database it is possible to create and maintain a library that contains all the component objects, function objects, and rule objects required for the design. Later design processes can directly access the knowledge thus created.
  • the device 100 further includes a resolution unit 106, which is also referred to as Workbench in the context of this application.
  • the workbench 106 forms a working platform for a definition, analysis, solution and optimization of an object data model.
  • the object data model is based on component objects, function objects and rule objects that are stored in the object database 102.
  • Workbench 106 allows its analysis and modification in addition to the definition of the object data model. The detailed structure of the workbench 106 will be explained in more detail below with reference to FIG.
  • FIG. 2 shows an alternative structure of a device according to the invention.
  • the reference numbers already used in FIG. 1 are used in FIG. 2, where identical parts are to be identified.
  • the device of FIG. 2 differs from that of FIG. 1 in that it contains no knowledge designer 104. Therefore, in the device of this embodiment, it is not possible to define new component objects, function objects, or rule objects.
  • the design work on the Workbench 106 therefore uses only the already stored in the object database 102 objects. These can be recorded, for example, in the case of a manufacturer-side initialization of the device or as part of a later update of the object database (update).
  • FIG. 3 shows a further exemplary embodiment of a device according to the invention in a network structure.
  • an object database 304 Via network 302 for data transmission, an object database 304, a knowledge designer 306 and a number of workbenches, symbolized here by the workbenches 308 and 310, are connected to one another.
  • a database server 312 and a license server 314 perform administrative tasks on the network 302.
  • the database server implements a DBMS (Data Base Management System) and may be, for example, an MSDE (Microsoft SQL Server Desktop Engine), an Oracle or a Microsoft SQL Server.
  • the Pacelab license server 314 monitors access to the object database 304 and prevents unlicensed access.
  • the network-based structure shown in FIG. 3 can also be realized with a single workbench.
  • the object database and the workbench are installed together with a database management system (DBMS) on a single workstation.
  • DBMS database management system
  • MSDE is preferably used.
  • the computer can also be equipped with Oracle or a MSSQL server.
  • a single-user computer additionally contains a knowledge designer.
  • FIG. 4 shows a block diagram for a more detailed explanation of a system for generating objects for the object database.
  • the system 400 shown here corresponds to the knowledge designer 306 of FIG. 3 and the knowledge designer 104 of FIG. 1.
  • the knowledge designer 400 has a three-part structure that reflects the three different types of objects that can be generated.
  • a component object designer 402 is for generating component objects 404.
  • a functional object designer 406 is for creating functional objects 408.
  • a rule object designer 410 is for generating rule objects 410.
  • the units 402, 406, and 410 are additionally designed to modify the structures they create.
  • the component object designer 402 can open, edit and store a component object stored in an object database, for example the object database 304, and store it in the object database in the form of a new version.
  • a respective input mask facilitates the redefinition of component objects, function objects or rule objects.
  • required steps such as coding and compilation are not required.
  • geometric and non-geometric product data can be used.
  • a geometry unit (not shown) generates a geometric model used to support the component object design, which is used to create visualizations that can be passed to CAD or DMU (Digital Mock-Up) systems.
  • the knowledge designer is specially trained to support calculations with physical units.
  • a component object is formed by a number of subcomponent objects 502 to 512.
  • the structure of the component object 500 is designed so that all data and relations necessary for the design are included for the description of a corresponding actual machine component.
  • FIG. 5 shows that the subcomponent objects themselves can take the form of component objects.
  • the subcomponent object 506 is formed by further component objects 508, 510 and 512.
  • the component object 508 in turn is formed by two subcomponent objects 510 and 512.
  • This data structure of a component object makes it easy to assemble new component objects from predefined component objects of the database.
  • a first form of subcomponent objects are parameter objects.
  • a parameter object 602 is formed by a parameter that can take a numerical or a non-numerical parameter value from a predetermined value range.
  • Numeric parameters are, for example, numbers of the type Double or Float.
  • non-numeric variables such as arrays and discrete variables, such as integer numbers, can also be used.
  • a parameter object can also be formed by a component object.
  • a component object may include at least one formula object 604.
  • a formula object is configured to form a predetermined mathematical link between two or more parameter objects 602 of the component object. With the help of formula objects, a dependency between specific parameter objects within the same component object can be specified.
  • An example of a formula object is a formula for determining the volume of an armrest of an aircraft seat by multiplying the width, height, and depth of the armrest.
  • the component object, the armrest is defined here among other things by the parameter objects width, height and depth.
  • the armrest component object may form a subcomponent object of another component object that describes a passenger seat of an aircraft.
  • component objects also contain at least one method object 606.
  • Method objects are designed to check the fulfillment of a relation between component objects of an object data mode and, depending on the test result, to set a value of at least one of the parameter objects included in the component objects according to a specific rule or Add a new component object or a new subcomponent object to an object data model.
  • Method objects are implemented in the form of executable program code.
  • a method object can serve, for example, to monitor the height between the steps in the design of a staircase as part of a scaling and to insert an additional step into the staircase when a predetermined threshold height is exceeded.
  • a component object may also include a geometry object 608 in the form of a set of geometry parameters.
  • the geometry parameters contain information about a geometric shape associated with a component object or parameter object. They are used to help with a graphical user interface of the Knowledge Designer or the resolution unit described below.
  • a component object contains a structural object (not shown in FIG. 6) which has a list of the subcomponent objects contained in the component object.
  • the structure object describes the hierarchy of the subcomponent objects contained in the component object.
  • the illustrated hierarchical structure of the component objects corresponds to the situation encountered in actual life in the design of complex systems, that these are composed of separable components.
  • an aircraft cabin consists of various cabin elements such as seats, hatracks and other elements, which are assembled to form an overall arrangement.
  • the modeling approach implemented by the component objects therefore distinguishes between boundary conditions within a component and boundary conditions that exist between components.
  • This encapsulation has the particular advantage that the modeling process can be made much clearer.
  • encapsulation allows the reuse of component objects in different systems.
  • FIG. 7 shows another block diagram for explaining the relationships between component object categories, component object concepts and component objects.
  • a component object category 700 may include a number of component object concepts 702, 704, and 706.
  • a component object concept can for example be formed by a model for jet engine of an aircraft.
  • An alternative component object concept may be formed by a propeller engine.
  • the set of all component object concepts forms the component object category "aircraft engine.”
  • different component object types can be assigned to each component object concept, with the reference symbols 702.1, 702.2 with respect to the component object concept 702, 704.1, 704.2 and 704.3 with respect to the component object concept 704 and 706.1 706. n are characterized with respect to the component object concept 706.
  • the component object types may be, for example, a jet engine of a manufacturer A and a jet engine of a manufacturer B. These differ, for example, with regard to their mass and air resistance, see above that the type of jet engine is to be considered, for example, in the calculation of fuel consumption in a flight over a given distance.
  • FIG. 8 shows a diagram for explaining various types of functional objects.
  • function objects form a predetermined link between two or more parameter objects of different component objects. You can modify parameter values contained in a component object or subcomponent object of the component object. You can add component objects to an object data model and set parameter values of the added component object. Furthermore, function objects can remove a component object from an object data model. Functional objects can also be used for analysis functions in which they acquire parameter values in at least one component object encompassed by an object data model and determine and output at least one analysis parameter value as a function of these and a predefined analysis rule. An example of a functional analysis function is the determination of the number of seats in an aircraft cabin.
  • Such methods may exist either as external methods encoded in the form of a dll (Dynamic Link Libary) file 802, or in the form of an Excel sheet 804 or in the form of an ODBC database 806 or in the form of an external application 808.
  • dll Dynamic Link Libary
  • FIG. 9 shows the structure of a controlled object.
  • a rule object is designed to check an object data model or a component object or subcomponent object or its parameter objects contained therein for the fulfillment of a predefined boundary condition, and to generate a rule violation message indicating this result if the boundary conditions are not met.
  • a rule object therefore contains a check section 902, which defines the condition to be fulfilled, and an instruction section 904, which defines the action to be taken, for example the display of a rule violation message, in the event of non-fulfillment of the condition.
  • FIG. 10 shows a more detailed block diagram of an exemplary embodiment of a device 1000 according to the invention for the conceptual design, the preliminary design and the configuration of a machine object.
  • An object database 1002 stores and manages component objects 1004, function objects 1006, and rule objects 1008.
  • the three-part structure of the graphical representation of the object database 1002 in FIG. 10 is merely illustrative of the three different types of objects contained within it. As such, the object database 1002 need not have a three-part physical structure.
  • the object database is connected to a knowledge designer 1010, which has already been described in more detail above in connection with FIG.
  • the object database is furthermore provided with a modeling unit 1014 and an execution unit 1016 for functional objects, hereinafter referred to as FO implementation. unit, connected.
  • the modeling unit provides as output an object data model that is used for the execution of function objects in the FO execution unit 1016 and for a resolution process in a connected resolution unit 1018.
  • the resolution unit 1018 comprises a unit 1020 for generating a mathematical model in the form of a system of equations from the object data model, an analysis unit 1022 for drawing up a resolution plan and a solver unit 1024 for executing the resolution plan.
  • an optimizer 1026 is connected to the solver unit 1024.
  • a graphics unit 1028 is provided, which is arranged in the data flow between the graphical user interface 1012 and the other functional units mentioned.
  • the graphical user interface 1012 in cooperation with the graphics engine 1028, enables a user of the modeling engine to graphically generate an object data model.
  • a "workbench" is created for the user, in which he assembles the object data model of the machine object from ready-made or self-created components, for which the user accesses component objects, function objects and rule objects that are stored in the object database, as described above
  • the modeling unit 1014 generates instances of the user-selected component objects, function objects and rule objects, whereby, for example, a structure representation similar to the tree graph shown in Figure 5.
  • the object data model can be created by manipulating the tree graph using a computer mouse, for example a likewise depicted graphical representation of the component objects contained in the object database by "drag and drop" a selected component object to the currently created object data model at a specific position of the tree graphene is added. More detailed definition features of a component object in the context of an object data model can be input via a data mask or further graphical representations.
  • the modeling unit 1014 allows The addition of the object data model by using and integrating external method objects via an API.
  • the knowledge designer 1010 which forms a graphical user interface separate from the "workbench"
  • new component objects, function objects and rule objects can be generated and published in the object database 1002.
  • the graphical user interface 1012 enables a user in this context Possibility to make graphic inputs in connection with the creation of new data bank objects via the knowledge designer 1010.
  • the user can initiate the execution of functional objects by the FO execution unit 1016, which are designed according to the functional feature for analysis or manipulation of the object data model (see above).
  • This functionality is especially useful in the configuration of machine objects and enables fast execution of predefined design and analysis functions.
  • parameter objects of the object data model are set as known within the scope of a resolution process and which are to be determined as output parameters in the resolution process.
  • the resolution unit 1018 is instructed to create a mathematical model from the object data model.
  • extensive graphical assistance for the manipulation of the mathematical model are provided.
  • each component object, functional object and control object can be assigned a preferably correspondingly labeled, graphic symbol.
  • a substructure of component objects in parameters, formulas and methods can be defined by a corresponding division of the symbol or arrangement of the different symbols for each of the subcomponents are represented.
  • the links existing between the individual objects continue to be of great importance, which can be indicated by corresponding connecting lines.
  • arrows can represent the relationship between the respective objects (parameter x is input parameter for the determination of the value of parameter y).
  • the user can thus graphically define a mathematical model created by the unit 1020 for creating a mathematical model in the form of a system of equations by adding and linking symbols. An arduous symbolic input of mathematical equations of a system of equations is therefore not required here.
  • the analysis unit 1022 determines whether the equation system is adequately determined. If so, the analysis unit 1022 creates a resolution plan that is communicated to the solver unit 1024. Further details of the structure and operation of the analysis unit 1022 will be presented below with reference to FIGS. 11 to 13.
  • the solver unit 1024 processes the resolution step submitted by the analysis unit 1022 for the resolution step.
  • solver blocks represent irreducible subsystems.
  • the solverblock selects a suitable solution method. Examples of such solution methods are numerical solution methods based on the known Newton method, discrete solution methods, geometric solution methods or algebraic-symbolic solution methods. The totality of these approaches, which the solver is able to select and apply, enables a hybrid resolution process that can bring about a resolution of the object data model with high efficiency and speed.
  • the optimizer 1026 serves to parameter values using well-known optimization strategies change and enter into the resolution process to determine an optimal solution under given constraints.
  • the illustrated comprehensive functionality of the device 1000 in the context of different phases of the design of a machine object is simplified by the underlying uniform data structure.
  • Concept, preliminary design and configuration are based on a uniform data model.
  • FIG. 11 shows the structure of the analysis unit 1008 in more detail.
  • a dependence graph determiner 1102 is connected to the unit 1020 and configured to create a dependency graph from the mathematical system formed by the object data model.
  • the term dependency graph will be explained below with reference to FIG.
  • Figure 12 shows a simple example of a dependency graph.
  • functions are symbolized by rectangular blocks. Circles symbolize variables. Arrows pointing from a variable to a function indicate that the function contains that variable. Arrows pointing from a function to a variable indicate that the variable depends on its function by its input variables.
  • the dependency graph of FIG. 12 was accordingly derived from the following equivalent system of equations:
  • V2 f1 (V2)
  • V2 f2 ()
  • V3 f ⁇ (VO, V2)
  • V3 f3 (V2)
  • V1 f4 (V2, V4, V1).
  • the analysis unit additionally has an input unit connected to the graphic user terminal 1002 via the graphics unit 1004.
  • the input unit saves instructions which parameter objects are to be treated as input parameters and parameter objects as output parameters.
  • Combiner analyzer 1106 is connected to dependency graph maker 1102 and input unit 1104.
  • the combiner analyzer 1106 is configured to determine if the mathematical system defined by the dependency graph and the input and output parameters is well-determined. If there is no well-defined system, the combinatorial analyzer partitions the system into a well-defined proportion, an under-determined proportion, and an over-determined proportion, if any, and analyzes the cause of under-determination or over-tuning of a block of the equation system.
  • the ascertained cause is output to a diagnosis unit 1108, which generates the corresponding detailed message and, via the graphics unit 1004, displays an analysis image of a under- or over-determined subsystem and submits a proposal for a solution.
  • Part of the combinatorial analysis is the calculation of a maximum size matching between variables and constraints.
  • matching algorithms are used for weighted graphs.
  • a graphics decomposition unit 1110 After a successful combinatorial analysis, in a graphics decomposition unit 1110, the dependency graph is decomposed into irreducible subsystems according to a decomposition strategy, which can be solved individually and in sequence. This sequence forms the resolution plan that is drawn up by the 1112 resolution plan unit.
  • FIG. 13 shows the result of a graph decomposition for the system shown in FIG. Two irreducible blocks 1302 and 1304 are indicated by a dashed border. From the decomposed dependency graph of FIG. 13, the following resolution plan can be determined:
  • An optimization strategy used by optimizer 1012 (FIG. 10) iterates the resolution process by varying the free variables to find acceptable solutions that are optimal under the given target relation.
  • the hierarchical, component-based modeling in the system according to the invention causes the encapsulation of existing within a component object relations.
  • Cross-component constraints only have access to free parameters of component objects.
  • Component object-internal parameters that depend on free parameters are invisible to the outside.
  • Machine objects within the meaning of the present invention can also be, for example, vehicles such as rail-bound vehicles and motor vehicles, but also buildings such as airport buildings.
  • the examples mentioned form complex units.
  • machine objects can also form part of these examples.

Landscapes

  • Physics & Mathematics (AREA)
  • Geometry (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Pure & Applied Mathematics (AREA)
  • Mathematical Optimization (AREA)
  • Mathematical Analysis (AREA)
  • Computer Hardware Design (AREA)
  • Evolutionary Computation (AREA)
  • General Engineering & Computer Science (AREA)
  • Computational Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un dispositif et un produit logiciel informatique pour concevoir, ébaucher et configurer un objet de machine qui est représenté par un modèle de données objet. Dans une banque de données objets sont enregistrés des objets composants, un objet composant contenant au moins un objet paramètre. La banque de données contient également des objets fonctions. L'élément de modélisation rapporté implémenté par la séparation entre objets composants et objets fonctions, permet la différenciation entre des conditions limites à l'intérieur d'un objet composant, et des conditions limites qui règnent entre les objets composants. Les premières conditions sont détectées par les objets composants eux-mêmes, les dernières conditions sont détectées par les objets fonctions. L'encapsulation présente en particulier l'avantage que le processus de modélisation est sensiblement clair. De plus, elle permet la réutilisation des objets composants dans différents systèmes.
EP06778219A 2005-08-18 2006-08-10 Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur Withdrawn EP1917611A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE102005039646 2005-08-18
DE102005055133A DE102005055133A1 (de) 2005-08-18 2005-11-16 System für den maschinengestützten Entwurf technischer Vorrichtungen
PCT/EP2006/065222 WO2007020231A2 (fr) 2005-08-18 2006-08-10 Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur

Publications (1)

Publication Number Publication Date
EP1917611A2 true EP1917611A2 (fr) 2008-05-07

Family

ID=37450741

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06778219A Withdrawn EP1917611A2 (fr) 2005-08-18 2006-08-10 Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur

Country Status (4)

Country Link
US (1) US8239173B2 (fr)
EP (1) EP1917611A2 (fr)
DE (1) DE102005055133A1 (fr)
WO (1) WO2007020231A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107300860A (zh) * 2017-06-09 2017-10-27 南京航空航天大学 一种航空发动机控制系统仿真平台控制对象在线更改方法

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090076837A1 (en) * 2007-09-13 2009-03-19 Wayne Collier System and method for product definition
US8078443B2 (en) * 2008-05-12 2011-12-13 Ford Motor Company Method and system for generating configuration constraints for computer models
US8014886B2 (en) * 2008-05-12 2011-09-06 Ford Motor Company Method and system for generating an assembly configuration
DE102009043327B4 (de) 2009-09-28 2017-11-23 Airbus Operations Gmbh System und Verfahren zur Konfiguration einer Flugzeugpassagierkabine
US8825459B2 (en) * 2010-11-29 2014-09-02 Autodesk, Inc. Multi-modal manipulation of a geometric model
EP2749858B1 (fr) * 2011-08-22 2018-04-25 Nikkiso Company Limited Dispositif de détection de pression de trajet d'écoulement de fluide
CN102708224B (zh) * 2012-04-10 2014-10-22 中国人民解放军国防科学技术大学 一种基于功能设计的系统结构自动分析方法
JP5469728B1 (ja) 2012-10-19 2014-04-16 日機装株式会社 液体流路の圧力検出装置
JP5587958B2 (ja) 2012-10-19 2014-09-10 日機装株式会社 しごき型ポンプ
US9116960B2 (en) * 2013-05-17 2015-08-25 Sap Se Calculation engine with optimized multi-part querying
US9116953B2 (en) * 2013-05-17 2015-08-25 Sap Se Calculation engine with dynamic partitioning of intermediate results
JP5863871B2 (ja) 2014-04-15 2016-02-17 日機装株式会社 装着部材及びしごき型ポンプ
FR3021775A1 (fr) * 2014-05-27 2015-12-04 Defacto Dispositif et procede de modelisation numerique en trois dimensions
US10108761B2 (en) * 2014-09-15 2018-10-23 Dassault Systemes Solidworks Corporation Predictive simulation
WO2016208705A1 (fr) 2015-06-24 2016-12-29 日機装株式会社 Dispositif de purification du sang
RU2656584C1 (ru) * 2017-03-14 2018-06-05 Общество с ограниченной ответственностью "Новый мир развлечений" Система проектирования объектов в среде виртуальной реальности в реальном времени
JP6464238B1 (ja) 2017-09-07 2019-02-06 日機装株式会社 血液浄化装置及びその気泡の排出方法
JP6462077B1 (ja) 2017-09-07 2019-01-30 日機装株式会社 血液浄化装置及びその気泡の排出方法
US11270034B1 (en) 2018-01-05 2022-03-08 Shiyuan Shen Method and system for kitchen cabinet layout
CN108280276B (zh) * 2018-01-09 2022-02-08 上海大学 基于Revit软件楼梯模型标准创建和用量统计方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5552995A (en) * 1993-11-24 1996-09-03 The Trustees Of The Stevens Institute Of Technology Concurrent engineering design tool and method
US6606731B1 (en) 1999-08-05 2003-08-12 The Boeing Company Intelligent wiring diagram system
US6625507B1 (en) * 2000-02-23 2003-09-23 United Technologies Corporation Method and system for designing a low pressure turbine shaft
DE10041031A1 (de) 2000-08-22 2002-03-21 Airbus Gmbh Verfahren zur Konfiguration von Komponentenanordnungen und zur Generierung von Herstellungsunterlagen
US20020128998A1 (en) 2001-03-07 2002-09-12 David Kil Automatic data explorer that determines relationships among original and derived fields
EP1368758A1 (fr) * 2001-03-13 2003-12-10 Bombardier Inc. Systeme et procede pour la configuration de l'architecture interieure d'un vehicule
US7176942B2 (en) 2001-03-23 2007-02-13 Dassault Systemes Collaborative design
US20050071135A1 (en) * 2003-09-30 2005-03-31 Vredenburgh David W. Knowledge management system for computer-aided design modeling
KR100754387B1 (ko) * 2004-12-06 2007-08-31 삼성전자주식회사 그래픽 컨텐츠 제작장치와 방법 및 컴퓨터 프로그램을저장하는 컴퓨터로 읽을 수 있는 기록매체
US7847807B2 (en) * 2004-12-22 2010-12-07 Hntb Holdings Ltd Geometry creation tool

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2007020231A2 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107300860A (zh) * 2017-06-09 2017-10-27 南京航空航天大学 一种航空发动机控制系统仿真平台控制对象在线更改方法

Also Published As

Publication number Publication date
US20100106466A1 (en) 2010-04-29
DE102005055133A1 (de) 2007-02-22
WO2007020231A2 (fr) 2007-02-22
WO2007020231A3 (fr) 2007-05-03
US8239173B2 (en) 2012-08-07

Similar Documents

Publication Publication Date Title
WO2007020231A2 (fr) Systeme d'ebauchage de dispositifs techniques, assiste par ordinateur
EP0852759B1 (fr) Procede de conception pour systemes industriels et systemes de construction, et systeme de planification assiste par ordinateur a utiliser dans le cadre dudit procede
DE102015100024A1 (de) Wiederverwendbare Grafikelemente mit schnell bearbeitungsfähigen Merkmalen zur Verwendung in Benutzeranzeigen von Anlagenüberwachungssystemen
DE112005001031T5 (de) Grafisches Bildschirmkonfigurationsgerüst für vereinheitlichte Prozesssteuerungssystemoberfläche
DE102008048478A1 (de) Probenermittlungsstrategie unter Verwendung genetischer Algorithmen bei der Optimierung eines technischen Entwurfs
DE102010038146A1 (de) Verfahren zum Auswählen von Formen in einer Grafikanzeige
EP3446185B1 (fr) Procédé et dispositif pour la conception d'un procédé de production pour la production d'un produit composé de plusieurs composants
EP2799983B1 (fr) Répartition flexible des canaux E/S d'un composant matériel
EP2330469B1 (fr) Procédé et environnement de développement destinés à produire un programme de commande complet exécutable
DE102014210854A1 (de) Computerimplementiertes Verfahren und Signalfolge für ein Programm zur Wiederverwendung von ausführbaren Softwarekonfigurationen für Softwaresysteme sowie Rechneranlage und ein Computerprogramm mit Programmcode zur Durchführung des Verfahrens
WO2021058223A1 (fr) Procédé d'application de fonctions de conduite automatisée de manière efficace et simulée
DE10333087A1 (de) Verfahren zum automatischen Zerlegen von dynamischen Systemmodellen in Teilmodelle
EP3364257B1 (fr) Procédé de fonctionnement d'un système d'ingénierie pour un système d'automatisation de processus industriel et programme de commande
DE10324594A1 (de) Verfahren zum Bereitstellen einer verbesserten Simulationsfähigkeit eines dynamischen Systems außerhalb der ursprünglichen Modellierungsumgebung
DE112008003511T5 (de) Integrierter technischer Analyseprozess
DE10046742A1 (de) Vorrichtung und Verfahren für ein Fahrzeugentwurfssytem
EP1533674B1 (fr) Méthode pour développer et implémenter un modèle décrivant formellement un système collaboratif comportant une pluralité de composants distribués, en particulier un système intelligent et flexible de production et/ou d'automatisation de processus
EP3699704B1 (fr) Système et procédé de vérification des exigences du système des systèmes cyber-physiques
EP4224353A1 (fr) Procédé de création d'un modèle virtuel d'un composant, système informatique, produit programme informatique
DE68905848T2 (de) Speicherprogrammierbare steuerung mit strukturierter programmiersprache.
DE102016109596A1 (de) Computerunterstütztes Design von Mechatronischen Systemen zur Beschreibung von textbasierten Systemspezifikationen
DE19831651C1 (de) Verfahren zum Erzeugen eines regel- und anpassbaren Netzwerkes von Modellen von Verhaltensmustern einschließlich Software-Systemen
DE102019131613A1 (de) Verfahren zum Betreiben einer elektronischen Recheneinrichtung für einen Produktentwicklungsprozess mittels maschinellen Lernens, sowie elektronische Recheneinrichtung
EP1387260A1 (fr) Procédé et dispositif pour la génération des logiciels
DE102004023634B4 (de) Verfahren zur Vollständigkeits- und Konsistenzprüfung einer Informationsbibliothek

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080305

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20100526

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20130917