Cancel
Showing results for 
Search instead for 
Did you mean: 

It’s not only logical

Siemens Legend Siemens Legend
Siemens Legend

In today’s multi-disciplinary design environment there is a need to link the software develop cycle to the mechanical development cycle. These are however design processes on very different release processes and timelines with the only traditional established comminution interfaces being that of passing simple documents and spreadsheets between departments. The Systems Driven Product Development approach assists in bring these domains closer together. This is achieved via the Systems Engineering Logical Architecture Model which not only defines the desired multidisciplinary solution for a product and links to the different domain models but also tracks key performance indicators (KPIs) of the product though the use of Measureable Attributes. These measurable attributes track the goal and the current measured value of a KPI and provides a linkage to parameters used in different design domains. The goals will be decomposed for the main product requirements while the measured values will be used by and come from many sources, including simulation and tests results, and from different domain design applications. This includes NX, Simcenter 3D and Amesim.

MultiDomain.png

To simplify the extraction of goals from the logical model and returning result values to measurable attribute on the logical blocks from the physical model a workflow process call an Analysis Requests is used to communicate between the design release engineer (or systems engineer) and the mechanical designer in NX.

workflow.png

Using Active Workspace an Analysis Request from a design release engineer is submitted to the NX designer who can view this using Active Workspace inside of NX. The NX designer can then associate measurable attributes to NX files and in doing so creates a requirement in the MCAD file of the physical model from the goal in the logical model. During the design of components, by associating a measurement to the requirement in NX a connection is made between the measured result and the measurable attribute from the analysis request. This process provides the whole design team with visual reporting on the maturity of the product (see What you require). On save of an NX file the values are written back to the measurement attributes on the analysis request. The NX designer can then decide when to release the new measured values back to the design release engineer who can then update the Measureable Attributes values on the logical architecture model.

AssociatetoNX1.png

This method provides an effective means of communicating product requirements to the design engineer while allowing the systems architect or design release engineer to receive accurate and reliable up-to-date values of key performance indicators without the need for complex file transfer, data entry and communication processes.

One innovative advantage of this process is that relationships are automatically built between Logical blocks and Physical components allowing cross probing to take place between Logical and Physical models, providing clear information on which physical objects satisfy which logical solutions.

Crossprob.png

This tight integration of parameters across design domains is a key piece in building up of the product digital twin.

 

Steve V
Contributors