ECN Electrical Forum - Discussion Forums for Electricians, Inspectors and Related Professionals
ECN Shout Chat
ShoutChat
Recent Posts
Increasing demand factors in residential
by tortuga - 03/28/24 05:57 PM
Portable generator question
by Steve Miller - 03/19/24 08:50 PM
Do we need grounding?
by NORCAL - 03/19/24 05:11 PM
240V only in a home and NEC?
by dsk - 03/19/24 06:33 AM
Cordless Tools: The Obvious Question
by renosteinke - 03/14/24 08:05 PM
New in the Gallery:
This is a new one
This is a new one
by timmp, September 24
Few pics I found
Few pics I found
by timmp, August 15
Who's Online Now
0 members (), 248 guests, and 16 robots.
Key: Admin, Global Mod, Mod
Previous Thread
Next Thread
Print Thread
Rate Thread
Page 2 of 2 1 2
Joined: May 2005
Posts: 984
Likes: 1
G
Member
I (personally) always design for voltage drop.
The note about the 5% appears on my drawings only to give me a club for when the VE exercises result in the EC sizing the wire for the load and ignoring the effect on voltage drop.
Before that note was there, smaller wire got installed (to save $$) and the voltage drop was suddenly my problem.
Since the note, the problem comes right back to the EC who installed smaller wire than the design called for. It's headed off a lot of problems since starting to appear on the drawings.
...and yes, there are some lazy engineers out there who don't even bother to run the calculations and just hide behind the 'killer note'.


Ghost307
Joined: May 2005
Posts: 41
L
Member
You go ITO! Also, AIC ratings should be shown, and calculated. A lot just plug in high AIC ratings that you know aren't needed. Loads, wherever listed, should clearly show watts or amps. Details are good, but the plans don't need to teach Electrical 101. Make sure the size of print can be read in realtime. If you pass the drafting off to someone, check their work; you can almost see when someone passes it off. And PLEASE (even though it is usually not your call) don't put plans on a paper size that won't fit standard drafting tables!!

Joined: Dec 2005
Posts: 152
A
Member
I dont do plans but here are some things I find useful when defining scope of a job and returning a completed job.

I note on the completed job the assumptions and specifications made about and for the environment (in this case it's a data environment) as defined by the person comissioning the job. I have those typed up and get that person to sign off on them before we start the job - this does two things: 1)Makes the submitter really think about what (s)he is wanting us to do and 2) Covers my a&^* when the job is completed and input data is changed while in process. Having them on the job report reminds everyone of the ORIGINAL scope of the project as these things suffer tremendously from mission creep. I get to bill for my actual hours and keep my cost center on budget (for the most part)

Page 2 of 2 1 2

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.5