Custom Cables - D-Tools Forum

eddieasher · 05-12-2008, 03:35 AM

What is the best way to add custom made interconnect cables to the database?

Example
Product sku: Gold 6 ft custom made composite video cable

Parts needed:
6 ft of liberty interflex cable
2 CM-RG59-GRCA connectors
Labor for terminations of connectors
Labor to install cable

The problem I am having is the reports. If I do not add the connectors/cable in accessories, it does not show up on the pick list reports or other reports correctly Or if I add them to the accessories then my proposal reports are not correct.

Thanks

Eddie

**Kevin Mikelonis** · 05-12-2008, 05:48 AM

Lots of ways to handle this, here is one solution:

http://www.imakenews.com/d-tools/e_a...Vn2b7,b4lbvLHD

eddieasher · 05-13-2008, 12:53 AM

Thanks for the help, it somewaht works. I added .050 to the "unit labor Hrs" and it shows $541.00 for install hours. shows up correctly on the proposal, but on some of the reports I have some problems.
attached is a "pick list" report. it shows 12 of the interconnects, but that 12 should be the length of the cable.

Thanks

Eddie

**Kevin Mikelonis** · 05-13-2008, 01:21 AM

Great Job!

You only need to make a few adjustments and understand a few things about the structure of this to put it in place.

First of all, the labor $'s are high because your default wire length is probably 100, so the project is pricing the interconnect as though it were 100 feet long.

If your project is not prompting you with the head end dialogue box, you are not seeing this length, and do not have a chance to adjust it down to say, 3 or so feet.

The head end dialogue can be overidden to/not to display in the project's options in addition to being set for the phase as outlined in our newsletter article you read.

If you are bringing all your rough wire into projects via packages, the wire length for rough wire can be set and controlled in the package. Do this and the default wire length that is in setup (and therefore in the project) can be set to the average length of your typical interconnect.

The pick list you attached is actually right-on! In your example, your technician only needs to know that a certain number of a certain type of interconnect is being made, not what length - afterall the actual length will be based on how much cable is needed between devices, the technician will build the appropriate length, not spool off the designated amount.

Custom interconnects are typically built using wire that is in inventory, pulled off the spool as needed, and accounted for to the back office once all the connections are completed. Therefore, knowing how much cable in feet is needed is not important, estimating the cost per foot is important, and if you are doing that by way of the methods and adjustments mentioned above.

Take the next few steps and see how it works!

11-14-2008, 12:05 AM

Kevin,

The method you use makes alot of sense, but I have done it a little differently, at least for now. I made dummy SKUs for all the custom made cables with the actual wires and connectors as accessories. It means I can't add the custom cable as an accessory to another item, but I think that's OK. I can just add and manage regular interconnects that are easier to manage for purposes of the proposal, then if need be replace them with custom interconnects when doing the actual design schematic before any parts are ordered.

One question for you though - in alot of cases the same connectors are used for prewire trim and for making custom interconnects. If you assign the same connectors to build custom interconnects they will show up in the "trim" phase rather than the "rack build" phase.

**Kevin Mikelonis** · 11-14-2008, 05:27 AM

LIVE FROM DTU 2008!

I am glad you found a method that works for you. If it is consistent, it can be learned and that is most important so others can maintain and support the database along with you.

Your point about phases is a good one and one of those issues that you just settle with.

Phases do three things,

...they allow specific labor rates to apply to products
...they enable you to look at and evaluate the labor effort required for stage of the project
...phases help you control the release of products in to the purchasing queue

These connectors you cite most likely do not add up to a significant amount of labor hours, and if they were ordered during the trim phase rather than the rack build phase (which likely occur at the same time) I cannot see any detrimental impact to that.

Therefors I say plug all your connectors into the Trim Phase for consistency.

Thanks for implementing our ideas and for sharing your experiences for others to learn from.

Best-

11-25-2008, 09:51 AM

OK, my first question for you Kevin is how do you keep D-Tools from asking you to specify a shape for your interconnect every time you drop one on the page?! It seems D-Tools doesn't understand the "Rack Build" phase and or the "Interconnect" Category and will ask you what shape you want to use every time you drag one to a page.

Now for some pros and cons on our different methods:

Pros - My method will report correctly all the items needed for a PO - all the wire types, connectors & quantities. It's idiot proof on the backend.

Cons - Each wire including the shell is assigned a component ID and a headend. Not only does this throw the labeling off it also gets annoying when you get like 4 prompts when adding a component video interconnect to a project. I could possibly assign the shell product to a different phase like design or something, but there would still be like 3 different component IDs and headend prompts for something like a component interconnect.

I may go one further than your method and just make a bunch of interconnect products with fixed lengths with the price of the wire, connectors, etc. all built-in. Something like COMPANY - COMPONENT-INTERCONNECT-2M. This way I can still assign it as an accessory, I won't have to manage connectors separately from wire, and I can assign them to the finish phase so there will be no prompt for a headend, and only one component ID per interconnect. The reports will also show the quantity of interconnects instead of the length of all the interconnects combined, which makes more sense. The only downside to this is that the person doing POs needs to know how to translate the custom interconnect parts into the correct parts required, but at least the cost/sell price will still be accurate.