The predict table stores the prediction data for all expected work items currently defined on the system.
The predict table has the following structure:
|
|
|
|
|
|
|
•
|
0, if this is a predicted work item in a future sub-case, rather than in a currently outstanding sub-case.
|
|
|
|
|
•
|
0, if this is a predicted work item in a future sub-case, rather than a currently outstanding sub-case, that was itself started from a predicted future sub-case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: The step_durn_usecs column can be combined with this column to provide resolution to a microsecond.
|
|
|
|
Note: The step_start_usecs column can be combined with this column to provide resolution to a microsecond.
|
|
Number of microseconds since the start of the seconds value specified in the step_start column.
|
|
Note: The step_end_usecs column can be combined with this column to provide resolution to a microsecond.
|
|
Number of microseconds since the start of the seconds value specified in the step_end column.
|
|
|
|
Value of the CDQP assigned to the field_name field for this predicted work item.
|
The predict table contains one or more rows for each predicted work item generated by each step of each case of each procedure that currently has prediction data defined for it.
If a predicted work item contains one or more fields that have CDQPs assigned to them, duplicate rows are added for each CDQP. In the first row, the field_name and
field_value columns are blank. Each subsequent row contains the
field_name and
field_value entries for one assigned CDQP. For example, if a predicted work item contains 5 fields that have CDQPs assigned to them, it will have 6 rows in this table.