Logistics spaces

The purpose of the logistics spaces hierarchy tree is to be able to publish logistics containment and an optional phase value for each model object.

Logistics spaces which are used to model relationships between model objects and various logistics phases can form a more complex hierarchy.

• There may be several levels (e.g. outfit area || superblock/block) to which model objects can be assigned to.

• One goal is to be able to form this tree as automatically as possible via spatial containment and rules. When containment is computed from spatial location then the order of evaluation is the order of branches in the tree. In this case contained objects get a default phase value. In the logistics hierarchy of our example case, blocks are under super blocks and outfit areas are on the same level with super blocks. If model object is not completely inside any block, but it is completely inside a super block and at the same time completely inside an outfit area, containment of this model object is outfit area, because outfit area branch is before super block branch in the logistics hierarchy.

• Containment may also be specified explicitly via selection, which creates association and containment is not necessarily computed from spatial location. Same explicit selection and association can specify also the non-spatial phase value. Phase value attribute is associated with the logistics hierarchy and there is no need to use any separate attribute to specify this.

  

• Phase values that are used in logistics hierarchies are defined as the value set of a COS attribute that is associated with the logistics hierarchy.