I have been asked to look at a project that is somewhat easy, but the consequences of my actions if done wrong can have disastrous results. I am faced with these types of projects from time to time. When putting a proposal together on a project I try to figure how long it will take me to complete a task and then multiply that time by my hourly rate to get the fee I charge the client. In instances like this, I don't believe this is the correct approach. I know there are tons of old time sayings about project like this (not interested in hearing those). I am wondering what other do when faced with such circumstances?
I don't want to get into the details about this specific project as I am interested in the question in general.
Red Flag Submitted
Thank you for helping keep Eng-Tips Forums free from inappropriate posts. The Eng-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Eng-Tips forums is a member-only feature.
In the components business price can often be the determining factor as to what product the manufacturer uses. For a great many mass-market products and applications, the low-cost off-the-shelf, one-piece stamped receptacle fits the bill. The price is right, the performance is adequate. Download Now
In today’s cost-sensitive world, designers are often driven to specify the lowest cost solution for every aspect of their designs to ensure that their solution is competitively priced and their company remains profitable. However, specifying a low-cost, low-quality connector solution can result in premature failure, considerable re-work costs and damage to reputations.
Increasingly, product and services companies are seeking more information and control in the
operational lifecycle of their products, including service and use. Better information about the operational lifecycle, and the ability to use that information, requires more than just unstructured data flowing back from products in the field.