The navigational structure for objects and design parts on a Tree View within the Business Object Explorer can be determined by navigational models. A navigational model is a template that determines the configuration for both object and design part groupings within Business Object Explorer tree views. For a navigational model to be displayed in the Business Object Explorer a tree view must be configured to use the particular navigational model. Navigational models can display special groups of information, such as all object classes, all pumps in the facility, or all design parts with attached purchase requisitions. Navigational models also determine the navigational path of each grouping. For example, a grouping of all pumps could have navigational levels based on class, object status, and object ID.
Node displays work in conjunction with navigational models to define the display format of the object or design part nodes in the Business Object Explorer tree views. For example, a node display can be configured to display class, keyA01, and description. Each navigational model needs to have a connected node display. If node displays are not defined or connected to a navigational model, the default values of design object or design part ID and the main description are used instead. A single node display model may be applied to one or several navigational models.
Note: When defining navigational models, avoid using the following characters: \, /, : , *, ?, ", <, >, and |. These characters can cause problems for navigator node desktop shortcuts.
A navigational model is comprised of a grouping and one or more levels. The levels in the grouping determine the navigational structure within the Business Object Explorer tree views. For example a navigational model, NavModel1 can be defined for Class, KeyA01 and KeyA02 with a prefix being defined for each level and will be displayed as follows:
NavModel1
Class: MOTOR
Class: PUMP
Department: 10
Type: X
Department: 11
Type: AAA
A navigational model, NavModel2 can be defined for Class and KeyA01 without prefixes and will be displayed as follows:
NavModel2
MOTOR
PUMP
10
11
Node displays determine which items of an object or design part are displayed as node text for the object or design part in the navigational model. Displays are concatenated with an optional separator defined as part of the display model. For example, a node display model Display1 for NavModel1 can be defined for Class, KeyA01, KeyA02 and KeyA03 with a - Separator and will be displayed as:
Class: PUMP
Department: 10
Type: X
PUMP-10-X-1
PUMP-10-X-2
PUMP-10-X-3
PUMP-10-X-4
PUMP-10-X-5
PUMP-10-X-6
Department: 11
Class: SIGNAL, ANALOG INPUT
A node display model, Display2 for NavModel2 can be defined for Class, KeyA01, KeyA02 and KeyA03 with a / Separator and will be displayed as follows:
PUMP
10
10/PU/001
ROOM
SIGNAL, ANALOG INPUT
Main objects are affected by a defined display model. However, their sub objects are not. Sub objects (objects that are related to the main object) get a default display model of KeyA and Denom1. Display3 illustrates this:
Display 3
Pump Design
Facility, CM
Facility, PM
System, 311
PUMP
CENTRIFUGAL
PM-311-PA-001:Feed Water Pump 001:70:Y
Leaving
PM-311-L0001, Feed Water Line
The main object has a display model of KeyA, Denom1, Site, and Process Data Status. The pump object in the Pump Centrifugal folder shows KeyA (PM-311-PA-001), Denom1 (Feed Water Pump 001), Site (70), and Process Data Status (Y=object has process data changes). The sub object contained in the Leaving folder shows the default display model of KeyA (PM-311-L-00001) and Denom1 (Feed Water Line).
Navigational models can be created using variations such as design statuses, purchasing attributes, design part versions, and design part statuses.
You can create navigational models for the display of objects by their design status (e.g. Under Design and Completed among others) and/or by their operational status (e.g. In Operation and Out of Operation, among others).
Navigational models can be created for objects that have attached purchasing attributes, such as a purchase requisition, a request for order quotation, or neither of the two.
Navigational models can also be created to display design parts by their version level (1, 2, 3, and so on).
Navigational models can also be created to display design parts by their status (Available/UnAvailable).
Navigational items are descriptive text names given to generic database column names. These names correspond with the different levels in your plant. For example, KEYA01 is configured to appear as Facility, KEYA02 is configured as System, KEYA03 is configured as Subsystem, and so on. Navigational items are not displayed within tree views on the Business Object Explorer. However, they simplify the creation of node displays.
After a navigational model has been changed, it is rebuilt. During the rebuild the model is automatically locked to navigation. This locking avoids the display of partial information that may result in an incomplete navigational structure