Archives
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
Subassembly Order Matters
Its come up a couple of times over the course of the last couple of weeks. The manner in which you build you corridor assemblies does matter. First of all, the side that you attach the first subassembly to sets the assembly to see everything that goes on that side first. This can come in handy when you are targeting your subassemblies to alignments or profiles. If I need the right side pavement to target a given alignment I know that the right side was first, so the first pavement in my list is going to the right.
Let me show you an example. Here is a fairly straightforward assembly. It is symmetrical with the crown at the center. I first put in the right hand pavement. Then it doesn’t matter what other parts I put in, or what order. Anything attached to that first pavement is considered to the right, and after the pavement in the list. The entire left side is also after everything that is on the right side.
Here is the corridor page where I target alignments and profiles. When I target an alignment to identify the right edge of travelled way I know the first of the two pavements is to the right.

On a simple design that is really all I need. On a more complicated design I might want to go in and change the names of the subassemblies so there is no doubt as to which is which. But it never hurts to have a standard method for assembly creation, just in case.
Another place where this is of utmost importance is if you are using a Marked Point.
Some subassemblies allow the design to cross over to a specifically identified point to fill in gaps. A perfect example is a median that is filling the gap between two sections of pavement. The subassembly called Marked Point has to exist before the median subassembly is told to look for it. Now, time order isn’t as important as is the list of items. Since I always design to the right first my marked point goes on the right of my design, and the median goes on the left of my design and targets the marked point from there.
By the way, you will notice the median appears to be falling well short of its intended target. This is just a function of the layout, and not how the assembly will work in the field. It takes a little getting used to, but don’t judge a corridor by its layout assembly!
![]()
Leave a Reply
Recent Posts
Recent Comments
- Russ Nicloy - MasterGraphics on The Funny Thing About Profile Grade Markers
- Brian L on The Funny Thing About Profile Grade Markers
- Dan on Using iLogic to Enforce iProperty Completeness
- Alex Petak on Free Body Diagrams in Autodesk Force Effect
- Jim Ritter on Autodesk Inventor 2013 Workstation Recommendations





