the rule of thumb I follow is: if its a separate part, have a separate item. Frames are their own item, and cards are their own items. This seems to be the best fit for translating across specifying, diagrams, order processing (internally/and with vendors), serial tracking, etc...IMHO.
this still supports pre-configured packages in a much more "database friendly" fashion. Use the conventional package setup OR (what we do) have the pre-configured item as an item w/model # then accessorize with "packaged" versions of its components.
we don't use the schematic drawings (for a variety of reasons other than this), but one "schematic" solution that you may consider is to make the IO of your frame and cards contain the slot connection. so the frame might have a "card slot connector" and your card would have the same. you could then tie them together in your schematics.
You might also simply omit the connection, drag the frame on, and place the cards on a layer on top of it to have a visual representation of the connection.
__________________
Systems Technician/Crestron Certified Programmer
www.ccisolutions.com
[SIGPIC][/SIGPIC]
|