One thing we recently did to keep track of Engineering Orders against models was add more versions into the statebasedversioning.xml. This allowed us to release models at the same time as an EO.
What was
<seed name="ASME">
<value> - </value>
<value>A </value>
<value>B </value>
...
Became
<seed name="ASME">
<value> - </value>
<value>-1 </value>
<value>-2 </value>
<value>-3 </value>
<value>-4 </value>
<value>-5 </value>
<value>-6 </value>
<value>A </value>
<value>A1 </value>
...
It worked for us to just add in the new itterations. It will only show up when you go to revise a part, but it shows up for all parts that had that "ASME" series. There are other methods of creating rules in Windchill config files with multiple levels but we weren't able to get it to work how we needed it to. It took quite a bit of testing on a development server toverify everything would work how we expected it too.
From the Windchill "Versioning Schemes Administration" link on the site/utilities page it shows:
"
wt.series.HarvardSeries.seriesNames=MyHarvardSeries
wt.series.HarvardSeries.MyHarvardSeries.delimiter=.
wt.series.HarvardSeries.MyHarvardSeries.depth=16
wt.series.HarvardSeries.MyHarvardSeries.level.1=wt.series.MulticharacterSeries
wt.series.HarvardSeries.MyHarvardSeries.level.2=wt.series.IntegerSeries
In this example, the series levels alternate between a multicharacter series and an integer series. This Harvard series would result in version numbers such as A.1.A.1.
"
Based on how it's written I would think it would be A.1.1 where the last 1 is itteration.
Hope this helps,
Steven LaPha
"The comments and opinions expressed are my own and do not represent the view of United Space Alliance"
