4 ms·
Last time I had a discussion about this my put was that licensing is an archaic way of doing things. In short the idea is we trust the PE's signature that ever
by Gibbon1 8y ago
Last time I had a discussion about this my put was that licensing is an archaic way of doing things.
In short the idea is we trust the PE's signature that everything is copacetic. In more modern fields like automotive, aerospace and software engineering that idea is laughable. Everything is about process, audit and testing.
- ggcdn 8y agoHow do you propose municipal planning departments process, audit, and test the thousands of building permit drawings they receive every year? Have a staff of hundreds of engineers of their own? The professional reliance model seems to work well enough, but that isn't to say it is the optimal model out there.
- wazanator 8y agoI feel like that's something that could be at least in part be automated by a computer. If everyone is following a standard you should be able to feed the data in and start doing pass/fail tests on requirements. I assume that's what people who sign off on plans kind of already do anyway.
- sgc 8y agoThe engineer's work is largely edge cases that don't fit into prescriptive code. Ie, that is substantially the system in place: We have a set of things that can be done without an engineer because they were already designed and approved by a group of engineers, and for everything else it is bespoke engineering.
- imgabe 8y agoIt all comes down to insurance. If your building collapses, the insurance company will want to know if you did every reasonable thing possible to prevent it before they pay out on your policy. One of those things is making sure that the person who designed the building knew what they were doing, i.e. were they a licensed engineer. I think most product companies are essentially self-insured. If Ford releases the Pinto and they get sued, they're paying the settlements themselves, not filing an insurance claim. So they are free to use whatever method they like to verify the competence of their employees.
- fbonawiede 8y agoYes, for attritional claims they “self-insure” (often through a captive or equivalent.) But for large claims they buy insurance. This is usually done from global reinsurers.
- runeks 8y ago> It all comes down to insurance. If your building collapses, the insurance company will want to know if you did every reasonable thing possible to prevent it before they pay out on your policy. One of those things is making sure that the person who designed the building knew what they were doing, i.e. were they a licensed engineer. That has nothing to do with the law, though. Ie. any insurance company ought to be able to decide for itself what qualifies as "engineer". There's no need for the state to define this and sue people -- the insurance company can simply refuse to sell an insurance unless the work was done by people considered, by the insurance company, as "engineers".
- rtkwe 8y agoA law defining what make the difference between an engineer and a professional engineer though reduces rriction in that context by creating a shared definition so instead of every insurance client having to provide the documentation that their eng was a p. eng (according to that insurance company's definition) both the customer and the insurance company can just refer to the licensing board to check. The biggest issue in this case is that the state was using it punatively against a person who was not providing a p eng sign off or advertising services as a p eng. Having a regulatory shared definition is fine and helps smooth commerce.
- eigenvector 8y agoMany places have an exemption for manufactured goods that are subject to testing. So for instance, a device doesn't have to be designed by a licensed engineer if it meets and is verified by testing to meet CSA standards. But if you want to use something that's not CSA, then it does need to be reviewed and signed off by an engineer. A home's electrical design doesn't have to be signed off by an engineer, but it has to meet code and be inspected. If it doesn't meet code and you want an exemption (for instance because you are doing something that wasn't anticipated by the code), then you need an engineer to sign off confirming that what you're doing is safe and truly requires an exemption.
- tbrownaw 8y agoSo, how do you do that sort of testing on one-off construction? What is the audit checking against? Where does the process come from?
- deleted 8y ago[deleted]
- naasking 8y ago> Everything is about process, audit and testing And how do you know the process, auditing and testing was done? With documentation signed by someone who can verify this and is legally liable if it wasn't done properly.
- vonmoltke 8y agoWhen I worked at Raytheon, there were no PEs n staff signing off on process documents or conducting audits of our design, manufacturing, or testing processes. Processes were developed in accordance with relevant ISO/IEEE/ASME/whatever standards, and these standards were periodically audited by external people certified by the corresponding standards body. While many of the older engineers had PEs, I do not recall any position that required one. As for legal liability, that falls primarily with the company. The chances that an individual is going to be held legally liable for a process failure in a corporation is very low, and whether or not that person has a PE will be irrelevant.
- naasking 8y agoAnd that's great when you have Raytheon's reputstion, clout, budget and bargaining power with insurance companies. If you want to start an engineering firm, I expect that having an accredited professional engineer on staff to ensure these processes are respected or the work meets certain standards will significantly affect your premiums. I wouldn't underestimate these costs, particularly for a new company.
- eigenvector 8y agoI can only speak for the area where I am licensed - British Columbia - but the presence of a professional engineer's seal on something should mean more than "this person thinks it's OK". It is supposed to mean: 1. This person has performed the work that went into this plan/design/report or, if someone else performed it, the signing person carefully verified every important aspect of the work 2. If they used software to perform calculations, they have designed a reasonable method to check and verify the output of that software, either by using selected hand-calculations or comparing to another, independent, software system 3. They have employed a quality assurance process that is suitable for the type of work being done, which may include peer review, non destructive testing, testing to failure of a sample, etc. 4. If field work is being sealed, the PEng has personally verified the field work, or provided detailed specifications for another qualified person to do quality assurance on the field work Now whether most PEngs really follow these "best practices" is an entirely different story. And yes, for fields that often involve very complex systems, the idea of any one single person meeting the quality management guidelines to place a professional seal on, say, an entire 787 aircraft, doesn't make sense. And when those systems also have life safety implications, it makes sense to test rigorously wherever possible. In many fields, professional engineers are effectively delegated the authority of government under a system known as "professional reliance". Rather than the city government hiring hundreds of people to review the plans of every building, they simply require developers to have a professional engineer certify that the plans meet the building code. This strikes a balance between the city having to review everything (and the associated increase in costs), and the developer being able to tick the box saying everything is fine with no real accountability beyond their numbered company that is owned by another numbered company in the Cayman Islands.