we are adding our operating data to Teamcenter (11.2.3).
Temp: 200 - 300 °C
Currently we solved this with two double properties and a string for the unit.
Temp min: 200
Temp unit: °C
This works in general but for the querry we need 6 fields:
Temp min =
Temp min <=
Temp min >
Temp max =
Temp max <=
Temp max >
Temp Unit =
The problem is that we have about 30 values, which leads to 90 fields in the querry, which is quite inconvinient.
Is there a better way to handle range of values in Teamcenter and allow it to search values smaller/bigger than the current value?
Really convinient would be also when we would be able to search indepently of the Unit. If someone has a idea for that I would also appreaciate it.
If the variable name 'Temp min' or 'Temp max' is about operating temperature or something related to temperature, then to me I would approximate it as classification information.
Teamcenter classification should be a good place to store store default value, minimum value, maximum value along with the units (degree C in the case you mentioned).
Did you already try out the Teamcenter classification module for your needs?
Thank you for the answer.
Yes, classification maybe fulfills our requirements.
We have not investigated it more detailed yet, because of the (quite high) additional costs.
The classification module needs a license for each user or?
Currently we do not intend to classify all of our ITEMS, just the product itself.
We do this currently with an additional form, which we add to the ITEM.
Is it possible to map the values of the classification to CAD (Solid Edge)?
AWC3.3 is now also able to handle classification search.
Maybe we should give it a try.
To my knowledge,separate license is not required for classification module.
It should be possible to map values of classification to CAD (my guess through reference attributes)
if we will use classification_user license - it's a floating license.
Otherwise if classification_user license not supported today then only classification_author named user license available
Some update from our side.
ActiveWorkspace 3.4 solved our issue.
The index search provides the capability to search by a range of value or by "bigger or smaller than".