Killer App in Packages - SI5 - D-Tools Forum

**Kevin Mikelonis** · 11-04-2007, 05:53 PM

COOL!

Working on a project this week using packages, we discovered that when adding a package to a project, you can modify the PACKAGE NAME without adding a new package to the database.

This is a great idea that was implemented when package functionality was improved in SI5 with SP3.

We love packages, and believe the winning combination is to avoid having too many of them, and keep them non-manufacturer and non-quantity specific in their naming so they stay organized in the product explorer and retain flexibility.

We have always been able to modify the description of the package for each instance in a project, but not the NAME.

This is GREAT!

Good work, and keep it coming!

Thanks!

11-06-2007, 08:09 PM

Two things I'd love to see added to packages:
1) Ability to pre-tag stages & / zones (for example we put speakers, wire and controllers into some packages just to make it easy - well that's three different stages, as well as two different zones - I'd like to DEFAULT it in a package so that it doesn't all come in as one zone and I have to split it out).
2) Ability to have a package within a package (For example - a simple CAT5e drop... that requires: 2-Cat5E jacks (or a patch panel that the other end), xxx ft. of wire, 1g face plate, 1g trim ring (new build or retro fit). So that's a lot of parts to keep dragging onto a bid - so we create that as a package called Network Drop. Then we might create a few different network drops, say for Component, Telephone etc... lastly we might want to pull those bundles into another item. Example of that - a Mini-Touch Screen requires a Network Drop). In the long run being able to add packages within packages would make life easier in this case. Hope I explained this one well enough.

**Kevin Mikelonis** · 11-07-2007, 12:35 AM

Originally Posted by slemay

Two things I'd love to see added to packages:
1) Ability to pre-tag stages & / zones (for example we put speakers, wire and controllers into some packages just to make it easy - well that's three different stages, as well as two different zones - I'd like to DEFAULT it in a package so that it doesn't all come in as one zone and I have to split it out).
2) Ability to have a package within a package (For example - a simple CAT5e drop... that requires: 2-Cat5E jacks (or a patch panel that the other end), xxx ft. of wire, 1g face plate, 1g trim ring (new build or retro fit). So that's a lot of parts to keep dragging onto a bid - so we create that as a package called Network Drop. Then we might create a few different network drops, say for Component, Telephone etc... lastly we might want to pull those bundles into another item. Example of that - a Mini-Touch Screen requires a Network Drop). In the long run being able to add packages within packages would make life easier in this case. Hope I explained this one well enough.

We have conquered #2 thorugh having a solid CATEGORY SET and a STANDARD ACCESSORY SCHEMA based on CATEGORY AND TYPE so we accessorize just enoguh to benefit from having PRODUCTS with ACCESSORIES in Packages.

Come with us, we makes D-Tools ROCK!