MADEKnowledge

MADE Training > Session 1 > Session 1.7: System Modeling (Logical & Physical)

Session 1.7: System Modeling (Logical & Physical)

Note: This training deck is primarily composed of instructional screenshots (numbered dialog boxes, toolbar callouts, field highlights). The text below preserves all extractable slide text — titles, bullet points, discussion/exercise headings, and table content. Where a slide is dominated by an unlabeled screenshot, only the caption and step-list text could be extracted; screenshot visual detail itself is not represented.

Session 1.7: System Modeling (Logical & Physical)

SESSION 1.7 OUTLINE

1.7.1: Advanced Properties 1.7.2: System Model & Boundary 1.7.3: Modeling Subsystems & Components (Logical Blocks) 1.7.4: Modeling Parts (Physical Blocks)


Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.1 ADVANCED PROPERTIES

The Advanced Properties Overview page shows where high-level/detailed information of a system or item can be stored.


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.1 ADVANCED PROPERTIES

To open the Advanced Properties editor:

Right-click `Vehicle System' in the Project Explorer

Select Advanced Properties

Populate the following fields:

   Item Number: VS1
   Physical Description: A land vehicle consisting of a

                                driveline and power generation
                                system.
   Enter a Model Year/Program: 2026

Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.2 SYSTEM MODEL & BOUNDARY

System Model is the canvas for all MADE modeling work Shows the contents (children) of an item and the boundary MUX bars for that item Defines the scope of the system Represented by Input and Output MUX bars MUX Bars define the input and output flows for the item


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.2 SYSTEM MODEL & BOUNDARY

To open the System Model:

Right-click the `Vehicle System' Select System Model Select the IN & OUT MUX bars Shift it away from End Effect Item text

Note: When Functions are defined, double-clicking `Vehicle System' will also open the System Model Note: Select the grid icon in the toolbar to show gridlines


Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS)

What does system modeling involve?

   Representing the structure and functionality of system of interest in MADE

Does system modeling require defined hardware?

   Before beginning modeling the user should decide how detailed the model needs to be based upon

          System complexity
          Required analyses

How does system modeling differ from functional modeling?

   A functional model is a simplistic model outlining the functions a system should achieve
   System modeling in MADE includes a hierarchical structure of items
   Items have functions associated with them and interact with one another via causal relationships between the

     functions

Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS)

A taxonomy of system elements in the System Model is shown in the table below:

Term Icon Definition System A grouping of sub-systems, components, and parts which interact to fulfil a common function. A system Subsystem is the highest level of indenture within a MADE project. Component A grouping of components or parts that work together to fulfil a common function. Pair A model item that performs a function and forms part of a larger system. Part The combination of two parts, created by assigning a physical connection between them. A pair possesses functions and failures, and may be connected up to the failure of a component. The lowest possible level of hierarchy in MADE. A part on its own cannot perform a function.


Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS)

The MADE model creation can be accelerated by:

   Importing from a .STEP file � this will populate the model item names according to the .STEP file.
   Importing from a configured .xlsx spreadsheet � this will populate the model item names and any associated

     parameters. Parameters include maintenance actions, reliability values, LCN, descriptions etc.

          To import from a .xlsx file, please refer to the Model Import Guide.

Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS)

To model Subsystems:

   Right-click on the system canvas on the system model
   Select New  Subsystem
   Select the Subsystem and using the Properties viewer,

     Rename the Item name to Power Generation

Note: You can move a model item by clicking and dragging it


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS) (CONTINUED)

Right-click the `Power Generation' and select System Model Right-click the system canvas and select New Component Select the new component and using the Properties viewer

edit the name to `Fuel Tank'


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS) (CONTINUED)

Right-click the Power Generation' subsystem in the project explorer and select: New Component Using the Properties viewer, edit the name to Control Unit'

Note: You can create a new component by selecting in the icon toolbar


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.3 MODELING SUBSYSTEMS & COMPONENTS (LOGICAL BLOCKS) (CONTINUED)

Create a new subsystem in Vehicle System' Rename the subsystem to Driveline' Open the `Driveline' system model and create the following 7 driveline components:

  Transmission
  Driveshaft
  Differential
  Half Shaft Front
  Half Shaft Rear
  Planetary Gearbox Front
  Planetary Gearbox Rear

Session 1.7: System Modeling (Logical & Physical)

DISCUSSION 1.7.4 MODELING PARTS (PHYSICAL BLOCKS)

Parts represent the most granular, physical level of detail in a MADE System Model Loading characteristics, features and environmental factors are attributed to part-level items Parts do not perform individual functions � instead part-pairs perform a function Parts interact with the logical model via failure diagram � do not connect directly to MUX bars


Session 1.7: System Modeling (Logical & Physical)

EXERCISE 1.7.4 MODELING PARTS (PHYSICAL BLOCKS)

To create parts:

   Open the `Fuel Tank' System Model
   Create two new parts
   Edit the names of the parts to: `Inlet' and `Outlet'
   Use the Palette window and search for `Lining'
   Drag this Palette part onto the canvas

To create a part-pair Connection:

  Select from the toolbar to create a connection
  Left-click from the `Inlet' to the `Lining'
  Repeat for the `Lining' and `Outlet'

Session 1.7: System Modeling (Logical & Physical)

SESSION 1.7 SUMMARY

1.7.1: Advanced Properties 1.7.2: System Model & Boundary 1.7.3: Modeling Subsystems & Components (Logical Blocks) 1.7.4: Modeling Parts (Physical Blocks)

Source: Local MADE 3.9.1 installation: com.phm.made.help.plugin/documents/help/pdf/MADE Training Session 1.pdf · retrieved 2026-07-09