The Very Simple Example

The name “very simple” is rather misleading. The problem is very simple, but the example has been expanded to illustrate many of the core features of the Business Object Model

Scenario Overview

The scenario is illustrated below.

../../../_images/VSE_scenario.png

Very Simple Example

The aim is to compute the deflection of a beam.

The key features are:

  • Geometrical shape (planar surface)
    • Hollow beam, defined by Thickness
    • Beam length
    • Billet chosen from catalogue of fixed sizes
    • Machining time derived from differences in volumes of beam and billet
    • Material provides density property for Mass
    • Billet properties provide Youngs Modulus E (impacted by billet roll direction etc)
    • Deflection of cantilever under evenly distributed weight of beam
    • Range derived from inner area (I.e. fuel volume)

The Associative Model Networks [AMN]

The following are illustrations of the networks for the example

Beam Geometry AMN

The first stage is to create the geometry for the example. It is may appear to be overly complex for the simple problem, but this is to enable illustrations of other areas. The first image shows the network and the

../../../_images/vse_shell_solid_amn.png

AMn for the Geometry (ShellSolid)

Representation using Business Object Model classes

This shows a study with a concept that is managing the AMN. The ModelInstances and KeyValueInstance belong to the AMN. The AMN is actually a combination of the Geometry and the Spreadsheet deflection.

../../../_images/vse_ea_beam_geometry_amn.png

Associative Model Network for the Beam Geometry

The instances in the above diagram each have a corresponding type. The types are themselves in a Collaborative Model Template [CMT] which is shown in the second image.

../../../_images/vse_ea_beam_geometry_cmt.png

Collaborative Model Template for the Beam Geometry

Note

There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class.

Deflection AMN

There are then two alternative ways to compute the deflection. The first is using a simple formula in a spreadsheet. This has several assumptions, or limitations, in that it is only applicable for prismatic shapes. The second approach is by using an Finite Element analysis. This can work on any solid shape, and it is probably over-kill for this example so can be used to illustrate a poor “utility” rating.

../../../_images/vse_xls_defln.png

AMN for Deflection computed using a formula in a spreadsheet

Representation using Business Object Model classes

This shows a study with a concept that is managing the AMN. The ModelInstances and KeyValueInstance belong to the AMN. The AMN is actually a combination of the Geometry and the Spreadsheet deflection.

../../../_images/vse_xls_defln_with_MT.png

The schematic illustration of the deflection network but also including the types

../../../_images/vse_ea_beam_geometry_amn.png

Associative Model Network for the Beam Geometry

The instances in the above diagram each has a corresponding type. The types are themselves in a Collaborative Model Template [CMT] which is shown in the second image.

../../../_images/vse_ea_xls_defln_cmt.png

Collaborative Model Template for the Deflection computed using a formula in a spreadsheet

Note

There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class.

../../../_images/vse_fe_defln.png

AMN for Deflection computed using Finite Element Analysis

Representation using Business Object Model classes

The example does not contain a single network that contains all the elements of the Finite Element Deflection analysis, because this is part of the second study which builds on the first study. Therefore only the Collaborative Model Template is shown here.

../../../_images/vse_ea_fe_defln_cmt.png

Collaborative Model Template for the Deflection computed using Finite Element Analysis

Note

There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class.

Manufacturing AMN

Finally there is a stage that brings in some manufacturing issues. Here the scenario is, that depending on the size of the beam, different billet sizes have to be used, and these have different material properties (Youngs modulus) due to the roll characteristics of the forging process

../../../_images/vse_manuf_amn.png

AMN for the manufacturing models

Combined AMN

These stages can be combined into a single picture, which are illustrated below using either the spreadsheet, or the Finite Element method of calculating the deflection.

../../../_images/vse_xls_combined_amn.png

Combined AMN for the Geometry, manufacturing and spreadsheet deflection

../../../_images/vse_fe_combined_amn.png

Combined AMN for the Geometry, manufacturing and FE deflection