TrackerProcessUnit

The Tracker process unit concept

The TrackerProcessUnit (TPU) is a virtual location where Tracking materials can reside. TPU’s belong to a Process unit, but may not necessary have any physical meaning. Process units with complex material flow are built up of several TPU’s in order to model the material flow inside the unit. In the tracker the tracker process unit is a ModFrame component that performs transaction related to the tracking of material. The Tracker process unit also performs other transactions that is related to the Process unit.

Roles (Aspects)

Roles are used as a way to uniquely identify the tracker process units inside a process unit. The reason for the use of roles is to hide details of the tracker configuration for the web interface configurator and to make the configuration of the web interface more robust against changes in the tracker application. Roles and Aspects are the same thing, it is called Roles in the tracker and Aspects in the portal. In order to reference a TPU in the portal, the ProcessUnit and Role (Aspect) must be specified. Hence, a TPU without a role cannot be identified from the Portal. The predefined roles are listed in the table below. The projects are free to define new roles, but it is recommended to use the predefined roles as much as possible

RoleIDRole name
1Input
2Output
4Check-in
8Check-out
32Run manager
64Time manager
128Performance manager
512Scrap output
1024Scrap input
65537Default input
65538Default output
65540Default check-in
65544Default check-out
65568Default run manager
65600Default time manager
65664Default performance manager
131073Control input
131074Control output
262145Internal input1
262146Internal output1
66048Default Scrap output
66560Default Scrap input

The RoleID's are bit patterns. The bits of these patterns are defined by the following table:

BitDescription
0Input
1Output
2Check-in
3Check-out
5Run manager
6Time manager
7Performance manager
9Scrap output
10Scrap input
16Default
17Control
18Internal1