Lecture and laboratory No. 10 Modeling product as system Óbuda University John von Neumann Faculty of Informatics Institute of Applied Mathematics Master in Engineering Informatics Course Modeling and design Dr. László Horváth

László Horváth UÓ-JNFI-IAM The screen shots in tis presentation was made in the CATIA V5 and V6 PLM systems the Laboratory of Intelligent Engineering systems, in real modeling process. This presentation is intellectual property. It is available only for students in my courses. The CATIA V5 és V6 PLM systems operate in the above laboratory by the help of Dassult Systémes Inc. and CAD-Terv Ltd.

Contents RFLP Structure László Horváth UÓ-JNFI-IAM Laboratory task Model definition for assignment Lecture System modeling Simulations Dynamic behavior Virtual execution Behavior in a component State logic behavior Architecture of a logical system Pathway sets Implement relations

System modeling László Horváth UÓ-JNFI-IAM System architecture definition Definition and simulation of logical systems System is composed by discipline based sub-systems Define and simulate control systems Integration to modeling and simulation environments Simulation behavior of complex systems How change of a system impacts other systems

System modeling László Horváth UÓ-JNFI-IAM Frédéric CHAUVIN, Gauthier FANMUY System Engineering on 3DEXPERIENCE Platform - UAS Use Case Dassault Systèmes

László Horváth UÓ-JNFI-IAM RFLP Structure Description using core elements from Systems Engineering. MIL-STD 499B “Military Standard – Systems Engineering” (1974, 1994). IEEE/1220 (1994, 1999, 2005) “Standard for Application and Management of the Systems Engineering Process”. Requirements, Functional, Logical and Physical views of product

RFLP Structure László Horváth UÓ-JNFI-IAM RFLP is a structure for model of product including requirements, functional, logical, and physical levels of abstraction. Level Requirements (R) includes all the requirements the product has to fulfill. At definition by engineer, requirement may be mandatory, cited, or own intent. Functions (F) are entities describing functions which the product must provide to fulfill its requirements. Behaviors may be included. Functional decomposition. Logical (L) level includes components having logical ports. How functional requirement will be achieved. The required logical architecture to provide functional services Information associated to a logical port (goes through port) Relations between logical ports (exchange information between components Behavior representations. Methods from systems engineering (SE) and requirements engineering (RE). Physical (P) level includes virtual representation of the real world product objects. Actual components are specified to execute the logical model. Source: Dassault Systémes V6 PLM

Dynamic behavior László Horváth UÓ-JNFI-IAM Dynamic logical behavior : Placed in logical components Logical behavior when dynamic behavior is inserted in a logical component. Inputs are computed continuously (not step-by-step). In V6, the dynamic modeler is Dymola, which applies the Modelica language. Physical product components can be connected to a logical component containing a behavior. Context dynamic behavior: Placed in a logical model. It is applied to all sub-components in order to create a global context (e. g. force of gravity, temperature). It has no connection with the logical components!

László Horváth UÓ-JNFI-IAM State logic modeling State Logic Modeling Creating a State Logic behavior connected to an F or L component. Dataflow Modeling Dataflow diagrams describe the flow of data through a system.

László Horváth UÓ-JNFI-IAM State logic behavior Type: Constraining the type of constants, functions, parameters, block ports and signals. Source: Dassault Systémes V6 PLM Function: Uses a parameter and produces a result. Module: Serves structuring of program. Module is a structured unit to package together related objects. Placed in function (F) or logical (L) component. Modeling discrete behavior of functional and logical components of a RFLP system. In V6 state logic behaviors are defined with the logic control modeler (LCM) language. LCM describes reactive systems by means of parallel and hierarchical compositions of finite state machines (FSM).

László Horváth UÓ-JNFI-IAM Virtual execution Application of dynamic behavior model. Needs behavior definitions. Performs virtual execution on a model. In the course of concept product definition. Model parameter values that are used during a virtual execution. Simulation uses values from the functional / logical model.

László Horváth UÓ-JNFI-IAM Behavior in a component Behavior representation to a function or logical component. Example: Source: Dassault Systémes V6 PLM Node that represents the behavior.

László Horváth UÓ-JNFI-IAM Architecture of a logical system Logical components in the RFLP structure. Logical ports on a component. Logical connection between two components. Shape representation for logical component Source: Dassault Systémes V6 PLM

László Horváth UÓ-JNFI-IAM Pathway sets They are associated with systems and sub-systems and not with logical components. It is in the RFLP structure under the active system. It contains one pathway and one segment. Branch is created between pathways and at any point of a pathway. Pathway network is space reservation for cable, pipe or other physical object. Pathway network carries from/to information between component reservations. Routing logical connections through pathways and route components. Source: Dassault Systémes V6 PLM

László Horváth UÓ-JNFI-IAM Implement relations Link between logical component and function. Link between logical and physical components. Source: Dassault Systémes V6 PLM Implement relations connect components of different RFLP levels.

László Horváth UÓ-JNFI-IAM Implement relations Link between requirement and a system type. Source: Dassault Systémes V6 PLM

Simulations László Horváth UÓ-JNFI-IAM Simulations are associated with various definitions. (E. g. Structural analysis, kinematics analysis, interference checking) Simulation specific parameters are applied. (E. g. static loads, thermal loads, motions) Simulation specific objects are involved. (E. g. part, material, mechanism) A simulation consists of model, scenario, and result. Model includes the representation context in which simulation is applied. (E. g. product, finite element mesh, mechanism) Scenario includes objects using as instructions for simulation. (E. g. loads, restraints, ) Result includes the results of the simulation. Simulations are identified, explored, and handled on PLM level. Simulations are defined, executed, and analyzed separately. Simulated models are not impacted.