STOCKNO and MCCS_CODE parameters

Modified on Fri, 8 Nov at 11:33 AM

Background

In the spec PTD text files, there are parameters that are listed for each line of both pipes and fittings (shown below outlined in red). These two parameters are not essential for use with spec-driven piping, but are two great places to store extra metadata in your pipes and fittings. From there, these parameters can be designated and stored in Windchill.


Downstream Creo Parameters

When this spec PTD file is used, the data from these two parameters (if they are valid) show up in Creo Parametric. For fittings, these display as an assembly component parameter within the pipeline assembly (shown below).


For pipes, the parameters will flow into Creo as part parameters on the solidified pipe segments (shown below).




Setting in the CadActive Piping Database

The STOCKNO and MCCS_CODE parameters can be applied at two different places within Piping: the Master Catalog or the Spec level.


Catalog Level

In the appropriate Pipe or Fitting Family, you can apply these values to the individual instance. Simply go to the Pipe/Fitting Family and select the button to display the two extra columns. For the below picture, I set example STOCKNO and MCCS_CODE values for three Steel pipe instances.

 When these values are set in the Catalog, they will be the default values for ALL specs that use these pipe/fitting instances. Below is a spec that uses these three Steel pipe instances, you can see the default values are showing here and would be what is written in the PTD text file.


Spec Level

In the appropriate Spec at the pipe/fitting instance level, you can change STOCKNO and MCCS_CODE parameters that apply ONLY to that spec. You can either overwrite the default values (shown below) just for that spec or create parameters for instances within that spec.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article