To retrieve the specification of an instance of physical object, a priority order has been defined.
- If a specification is defined on the instance of the physical object, then the value of the specification is the one of the physical object. When the specification of the physical object is different from the one of the line ID, the value is considered as Out-of-spec.
- If the specification is defined on the instance of the physical object and the value is None-spec, the reference of this object comes from any specification.
- If the physical object has no specification, the value of the specification is the one of the logical object.
- If the logical and the physical objects have no specification, the value of the specification is the one of the line ID.
The following table gives an example of how specifications are retrieved.
Part | Line ID Specification | Logical Part Specification | Physical Part Specification | Result Value is Specification column |
---|
1 | CS150R | - | CS150R | CS150R |
2 | CS150R | - | | CS150R |
3 | CS150R | SS140T | - | SS140T |
4 | CS150R | - | SS140T | SS140T (Out-of-spec) |
5 | CS150R | CS150R | SS140T | SS140T (Out-of-Spec) |
6 | - | CS150R | - | CS150R |
7 | - | CS150R | SS140T | SS140T (Out-of-Spec) |
8 | CS150R | - | NoneSpec | (None) |
9 | - | CS150R | NoneSpec | (None) |
10 | CS150R | CS250R | SS140T | SS140T (Out-of-Spec) |
How Is Retrieved the Physical Object When the Specification Is not Defined
The specification is not defined in the following cases:
- In None-spec mode
- When the line ID is not used (no RFLP session)
- The line ID is used but the value is unset
The physical object is retrieved in the default specification when using Engineering Specification resources, and in the Pipe (or Duct) Specification Definition table with criteria <AnyValue> when using file-based resources.