§1. Course logistics and Slocum's desalinization proposal [00:00]
We will start presentations a week from Monday. This Monday is a holiday, and next Monday is a holiday for Columbus Day. This is the schedule that Jerry put together as of yesterday afternoon — this should be what's on Stellar. She made copies; you can pass them around. If you don't want them, leave them in the back as scrap paper.
Anybody have any questions on the presentations? You only have ten minutes, but any topic you want. Some people have done cooking because they like to cook — there's a lot of material science of cooking. In fact Dr. Taylor, who works with me, is thinking about doing an IAP course on the material science of bread. We'll have to get ourselves some little ovens and some mixers, so it'll be a lab component, and you can eat what you cook, which may or may not be good.
On Tuesday I will lecture and finish up my part, and on Wednesday Professor Slocum will come in. He apologized — he thought classes were at ten o'clock, but there was a miscommunication. He's going to talk about his combined pumped water and desalinization idea. In certain parts of the world where you have an ocean next to a mountain, you could do pumped water storage on the side of the mountain, and then the high pressure of the water could go through a reverse osmosis process. You get both desalinization — low-salt water for a population, easily for a couple of million people — and energy conversion combined. He's looked at the different areas of the world where this can occur and done some of the engineering analysis. It's a new proposal, he just came up with it this summer, so it's a complex problem. It's a way to combine energy conversion and water desalinization for tremendous savings. I wanted him to come in because I consider him one of the three brightest people I've ever met, all of whom I met at MIT.
§2. Three sources of wealth [02:49]
There's another person I would have included in my top four. He was chief technology officer at United Technologies. We got into a debate once as part of a committee. What I said is, there are only three things that increase the wealth in the world: mining, agriculture, and manufacturing. Everything else is just redistribution of the wealth. If you go to the dentist, they're not producing anything new in terms of material goods — they might be improving your health, but you're redistributing money. Financial people on Wall Street — what did they ever produce? Well, except depressions. They're just shifting paper around.
This research fellow at Intel argued with me that I should add knowledge as a fourth area. But mining — oil business, coal, getting something out of the ground that can be made into something. Agriculture — you're growing food. Manufacturing — you're taking things and putting them together, adding a lot of value. All those things increase wealth. Whereas religious clergy, doctors, lawyers, teachers — most of these people are just redistributing the wealth. And it's not always redistributed very fairly either.
To him wealth was money. He couldn't see a broader vision of wealth. So I took him off my list of smartest people. But he was someone very thoughtful — one of the only people I've ever talked to where I had a hard time, just in casual conversation, keeping up. It wasn't that he was incoherent; he was about three steps ahead of wherever we were. He's a brilliant guy. He was on the board of directors of Draper Labs. But I just couldn't figure out why he could only define wealth as money. A lot of people define success as how much money you make. That's not true. It might be for some people, but if I wanted to make a lot of money I'd become a financial analyst on Wall Street and then steal it from everybody. That's what they do.
Bernanke, the former head of the Federal Reserve, just came out a week ago — he actually said yes, there should have been some criminal complaints against these people. His point was the Fed doesn't have the authority to charge people criminally, which is true. But he was head of the Federal Reserve. The question is, did he go to the Justice Department or the FBI to suggest these people be investigated? That's another question. These are ethics questions.
§3. Codes, standards, and Petroski on learning from failure [06:22]
We've been talking about engineering and how it involves complexity, ambiguity, uncertainty, and safety. Today I want to talk about safety and safety factors. Henry Petroski wrote a book called To Engineer is Human: The Role of Failure in Successful Design. Petroski is a civil engineer at Duke University, retired now, living in Maine. He wrote a number of books — a whole book on the pencil, another with a chapter on the paperclip. He's kind of a historian of things. I don't know that he's the first person to come up with this, but he wrote a good book, particularly for civil engineers because that's where the examples come from: we progress by failures.
To give you an example, the very first research contract ever given by the federal government was given around 1836 to the Franklin Institute, to figure out why the cast-iron boilers in the river boats on the Ohio River were blowing up and killing people. We hadn't gone past the Mississippi in 1836 — we were still on this side of the Mississippi. No one understood why. We didn't have fracture mechanics, we didn't know about toughness, we barely knew about strength of materials in 1836.
The thing that helped precipitate the boiler and pressure vessel code — the American Society of Mechanical Engineers sells a code telling you what the rules are if you're going to design and build a pressure vessel. In 1836 we had boilers, but the boiler and pressure vessel code didn't come along until about 1905, when they call it the beginnings of it. The first edition didn't come out until 1916, but in 2005 they wanted to celebrate the 100th anniversary. The boiler and pressure vessel code is about this thick. It comes out and gets renewed every three years, with supplements every six months. For only seventeen thousand dollars you can have a hard copy print, and for sixteen thousand dollars you can have a digital version. It gives you all the updates for three years. And there are people who spend their life on it.
Student: [inaudible question]
Yes, there are some people who spend their entire life on that code. If you're designing nuclear reactors, there's a pressure vessel there and you better know how to do it.
[Tom produces a copy of the structural welding code.] For welding, the boiler and pressure vessel code is one of the primary codes, but it only applies to boilers and pressure vessels. For bridges and buildings you have the structural welding code, for steel. There's actually one for aluminum and other things. The first couple of hundred pages are the code itself, which tells you what you shall do and what you may do. These do not have force of law until they've been adopted by some government agency, and then they do have force of law. This one has force of law virtually around the country for any bridge or building, because every state, every city — New York City has its own set of codes — they'll write this into their codes and say, if you're going to do welding you must follow AWS D1.1.
It turns out the federal government doesn't mandate safety for boilers and pressure vessels, but every one of the 50 states has adopted some part of the ASME code. I have a good friend, probably in his 80s now, who for 30 years was on the boiler and pressure vessel code main committee. There are probably close to a thousand engineers who attend these meetings and help update the codes, and most of it's volunteer work. I used to be able to buy this in the 1990s for two hundred dollars; now it's five or six hundred. Many of the societies have learned there's gold in them thar hills, because if you're going to be in business the law requires you to follow the code, and you have to follow the current edition. This one comes out every three years, like the boiler and pressure vessel code. They tried a few years ago to bring a new one out every year — extra profit — but people yelled and screamed enough that they went back to every three years.
There's no one who knows the whole tax code in the United States — it's a hundred thousand pages. But these codes, there are plenty of designers who can pick out exactly what's there. If you want to get a certified welding engineer certificate, you have to pick a code. You can pick any code you want among a group of five or six, and they will examine you on that code. Part of the test is to show that you are familiar in some detail with the code. It takes hours and hours to study these codes — they're not written to be conversational like reading a novel.
Student: [inaudible question, about how often the code is updated]
It's updated through these committee meetings — someone had some failure somewhere, or some fight. I can look in this code, and this is common with a number of codes: any new edition will be in underlines, so that paragraph didn't exist in the previous edition. Even if it's only one word they'll underline it. So someone who uses the code every day gets a new version and sees the new stuff.
To finish answering your question — there's also commentary. There's 200 pages of code, then about another 200 pages of commentary. The commentary is written by the people who wrote the code, and it interprets more than the code says directly. [Tom flips to commentary section.] You can see they changed 4.5 — the numbering changed, and it is a change, they added something. If you go back to the old code you see it changed. The boiler and pressure vessel code, there are people who write books and sell them, because they know the code in detail better than most people do, and it will help explain things. The codes are pretty dry reading, but they have force of law.
I mentioned once that I was teaching this to someone down at what used to be the National Bureau of Standards [NIST]. She started at MIT as an undergraduate in physics. MIT won't admit undergraduates to graduate school, so she went to Harvard for a doctoral degree. She was heading up like a hundred fifty people at NIST. I mentioned to her I was teaching a course on codes and standards. She said, "You are?" She had never heard of anyone in academia teaching a course on codes and standards. We have one or two civil engineers in the course, but I never heard anything about codes and standards as a student. As an engineer, when I go out and do my consulting, I deal with codes and standards all the time.
§4. Calgary transmission towers and inspection responsibilities [15:43]
The last two days I was out in Calgary dealing with a problem of big steel transmission towers — 500 kVa bringing electricity to the country. One company in India sold a hundred thousand tons to build a bunch of these towers that are going to be in Alberta. If you figure it out, there are 111 towers and a hundred thousand tons, so each really big tower weighs a thousand tons of steel, which is about one and a half million dollars just for the steel. Erecting one of these towers is probably two or three million dollars per tower. So next time you're driving along the highway and you see these big towers, that's two or three million dollars per tower for the really big ones.
I had to go back through my knowledge of the code and help advise people on what the contract said we had to do and what it didn't say we had to do. The buyer and seller were in a big fight — a fifty-million-dollar fight, the value of their claims — about whether they carried out their contract properly. One of the things I know well, because I've run across it many times, is section 6.5. I was quoting it yesterday.
There are sections in the code that talk about the responsibilities of an engineer. Here's contractor responsibilities, obligations of the contractors — build it. Section six is inspection. You've got to inspect it, and then it points out there's some engineering judgment if there's faulty welding. They're arguing over the inspection. People in India would do the inspection, and there'd be people from Canada placed in the plant in India. If you've got a hundred million dollars worth of product, you often put your own owner's inspector right in the facility. If it's around the world and you have to send the inspector to live there for three years, so be it. There are whole organizations that do that all the time.
You've heard of some of them — Lloyd's Register, which you used to know as Lloyd's of London. Lloyd's of London now is a bunch of insurance companies, but Lloyd's Register would put someone in a shipyard — this goes back hundreds of years — the owner would hire someone to look over the shoulder of the people building the ship. We now have American Bureau of Shipping, Lloyd's Register, DNV (Det Norske Veritas), and the French have Bureau Veritas. These are quality control, quality assurance people looking over the shoulders of the people doing it to make sure they do a good quality job. When you're buying a hundred million dollars worth of steel, you might as well have someone inspect it.
It says, if you ask for inspection that wasn't in the original contract agreement, you can have it — the contractor must give it to you — but you as the owner have to pay for it. You didn't put it in the purchase order, it's extra, you're going to have to pay for it. Unless they can prove attempt to defraud or gross non-conformance — you're doing a terrible job, you were careless and didn't even care about being careful, or you're actually committing fraud. Those things happen. There's a whole law that's built up around contracts. Government contracts, this contract's over budget by three hundred percent. The Big Dig was over by, what, seven hundred percent from the original estimate. This leads to lots of disputes.
§5. The Big Dig galvanized bolts case [20:16]
The Big Dig — they brought me in. They had some hangers in the tunnels holding the roof up. This was before the one that collapsed and killed the woman; this was while they were still under construction. Some of the big steel bolts that were going to hold up the roof were supposed to be galvanized — coated with zinc in a particular way. The contractor had done it out of sequence, and the question is whether the threads on the bolts — big bolts, an inch and a half in diameter — were going to rust in service.
These are all supposed to be hot-dip galvanized. Hot-dip galvanized, you dunk it in a bath of molten zinc and get a pretty thick layer, like two or three thousandths of an inch. That's the guardrails along the highways. Or the galvanized buckets on a farm that carry water, or the trough the cows and pigs drink out of. There's also electro-galvanized — if you saw any steel tubing it's zinc-plated. That's one-tenth as thick.
This was going to bankrupt the little company that had made these bolts for the Big Dig. The engineers were saying, "We're going to make you uninstall all this stuff and redo it." This was a mom-and-pop company; they were going to go bankrupt. I was hired to go in and talk about whether this was going to really affect the corrosion up in the ceiling. We were meeting with the chief engineer of the Big Dig, and the underling engineers were telling me, "You did it out of sequence, you need to do this."
So we go in the meeting and I said, I've seen some of the construction, you've got some electro-galvanized up there for the electrical stuff. I talked about the throwing power of zinc and how you have ten times as much on hot-dip galvanized. The fact that they had a little area, a quarter of an inch wide, that didn't have some zinc on it — it would all be protected, because compared to the electro-galvanized you had ten times as much. I said, if anything's going to start rusting up there it would be the electro-galvanized, because it has less zinc. You're going to start seeing rust from the electro-galvanized a lot sooner than from these. And then I said, "Oh, you guys already have rust!" They had to admit — the electro-galvanized was already rusty, and they hadn't even finished building it.
We ended up coming up with a fix that wouldn't bankrupt the company. They didn't have to take everything down. We came up with a fix that would make the underling engineers happy. The chief engineer was the arbiter between me and the guys trying to play hardball — "This is what the contract says." There are always things that go wrong, and as it says in the code, the engineer has to exert some judgment on whether it's important or not. You can have non-conformances, and then you can have waivers, or new ways to fix it. That's what this fifty-million-dollar dispute in Canada is all about. There were certain managers in Quebec who said, "We want exactly what we paid for," whether it was important or not. Some things are cosmetic and hidden — there ain't nobody above the ceiling, which is basically what happened in the Big Dig.
This is where engineering is a lot different than just being a research scientist at MIT. They teach you how to be a research scientist as if that's what people do. Ninety or ninety-five percent of engineers are not what I call the wannabe scientists — they're people who actually go out trying to make something work and solve the problem, and trying to decide when something goes wrong what to do about it. I used to work for a division of Johnson & Johnson that made medical instruments. They'd have a manufacturing hiccup and they'd come to me and say, "Do we have to throw out all this half-million dollars worth of parts we made, or can we do a fix?" I'd have to help decide whether there was a fix or whether they had to throw it out. Sometimes I said, "Sorry, you've got a half million dollars worth of scrap." Sometimes I said, "No, they can do this, but you have to get into the details." You can't always write down equations for this, but you've got to be able to justify it.
§6. The Mach 2.5 aircraft crash investigation [25:48]
A number of times I've been asked to go to Washington and talk to the regulatory agencies, in part because I'm at a university — I'm sort of a neutral party. Sometimes there's a lot of money involved. One day I didn't have to go to Washington because right up here by Burlington Mall the Federal Aviation Administration has offices — they have offices around the country, but these offices have to approve parts manufacturing if it's not the original.
If you want to sell an aircraft in the United States, unless you're going to limit it to flying yourself or your family — if you're flying it for yourself or your family the regulations say you can build anything you want, because it's okay for you to kill you or your family. But if you're going to sell it for other people to fly in it, you've got to follow our rules. I'm not kidding. There was once a group of people who wanted to be able to fly at Mach 2.5, same as an F-14. First of all the government wouldn't sell them an F-14, but also it would probably cost 70 million dollars. Some of these movie stars own their own helicopters. When I went through helicopter flight ground school, Harrison Ford had been there at Bell the week before learning how to fly his helicopter.
Some of these people would like to fly at Mach 2.5. You can design your own private aircraft, but the rules say you have to build half of it yourself. So they set up this factory in Reno, Nevada, and you could buy one of these for like 10 million dollars, and you had to come in and turn the screws and be able to say that you built half of it — even if you could afford someone else to do it, the rules say you have to. They're trying to qualify this aircraft — it was basically an aerospace engineer from Pratt and Whitney and one from General Electric — they built an aluminum frame and put a seat in front and wings.
They had lost their first test pilot over the Nevada desert. I got a call at six o'clock one morning — I was at work — and this NTSB accident investigator said, "Tom, I want you to look at some parts." I said, "Sure, you want to come by?" He said, "I'm down here at 77 Mass Ave, I can be there in five minutes." I said, "Okay, I'll meet you in 8-140." He shows me these parts. The owner of the company had died — he became the test pilot when the first test pilot died, and now he was dead. His widow wanted to understand why her husband had died.
They had a hundred million dollars — you had to put a two-million-dollar down payment, even though this thing hadn't even been proved out, to buy this super-duper plane that you could kill yourself in. He brings by these parts, and I look at them in about 50 minutes and said, "There's nothing here, this is all overload failure. Tell me more about this accident." He said, "They think they had wing flutter. He's at 40,000 feet, going Mach 2, and they think wing flutter starts getting into an unstable mode. Maybe one of the lead weights on the end of the wing flaps had come off." The wing flaps allow you to tilt; one of the lead weights was there to dampen vibration. If it had come off it would be unsteady — asymmetric weight, not balanced. They think that's what caused the wing to rip off.
The wreckage was spread out over 50 miles of the Nevada desert. At 40,000 feet going Mach 2, the first parts that fall off land here, the later parts somewhere else, so it's hard to get everything. I said, "Why don't you try to get me the end of the wings?" They brought in the two tips of the wings about three months later, and sure enough, there was an adhesively bonded one-pound lead weight. I could look at it. We didn't have the lead bit because it was gone, but I could look at the adhesive joints. They didn't get enough adhesive. Why they didn't put a screw in there to join the lead to the aluminum is beyond me. But to me that was the probable cause — that was helped out by an aerodynamics guy. The whole company folded; all the people who put in their two-million-dollar down payment lost it.
These things go on all the time. There was a guy I know who actually bought into another one — an all friction-stir-welded titanium skin plane, like a little Cessna, very light. You had to pay a million dollars down before the thing had even been designed. There are lots of these. I call them scams, but they wouldn't call them scams. When you're doing these things there are lots of uncertainties.
§7. Safety factors and proof testing [31:43]
As Petroski goes through and talks about the factor of safety in chapter nine — "Safety in numbers. While engineers can learn from structural mistakes what not to do, they do not necessarily learn from successes how to do anything but repeat what they already did." This is his thesis, that we learn from failures. He uses the Tacoma Narrows Bridge and other things. We have something called a factor of safety: if we think the required load is going to be a hundred pounds, we make it so it will support 150 pounds. That gives us a 1.5 factor of safety, fifty percent extra, because there are uncertainties in what we design.
Petroski talks about proof testing. If we want to have a rope to lift something and we might need to lift 1400 pounds, we might design a rope and test it at three thousand pounds. If it doesn't fail, we've just proved that one rope will hold 3,000 pounds. The chances of it failing if you load it again at 1400 are pretty small. Proof load testing is done all the time. In fact I ran into that the last two days out in Calgary. You do careful inspections, but you need to know how to define failure. It might seem obvious — it broke — but sometimes if you have a fatigue crack that gets to a certain size, then it has failed because you don't want to put it out there any longer. That's what we do all the time on an aircraft: we inspect them, we know what size cracks are acceptable. We do it in bridges and buildings.
[Tom holds up the structural welding code again.] That's actually why I brought this thing in. In these 200 pages, chapter 6 tells you, if you're going to do ultrasonic testing, what size flaw you can accept. If you find porosity — one pore is easy. What happens if you find a cluster, and how close can they be in a cluster before you say that's too much? The code has historically developed parameters that tell you, this is acceptable, this is not. If it's not, it's classified as a defect. But just because you find an imperfection doesn't mean it's a defect.
In 1849, the Royals [Royal] Commission in Britain asked a bunch of bridge designers how big safety factors should be. They were designing bridges. They'd designed a girder; they hadn't really worked out all the formulas like we have now. They might just put the girder across two pieces and load it up with 10,000 pounds of something and see if it breaks. They asked some of the big names in the industry at the time — Charles Fox the engineer, Crystal Palace, others. One came up and said, "Well, I think three." Another said seven. The Commission came up and said, "We're going to use a safety factor of six." So in 1850 we were using structural safety factors of six.
You have to remember they were using all kinds of material — steel that didn't have much toughness, cast iron that was very brittle, just inherently brittle. Petroski talks about the Washington Monument in crushing having a safety factor of 9. The Washington Monument was designed in the 1870s.
If you go look at the codes today: bridges in the UK in 1850 had a safety factor of six. The ASME boiler and pressure vessel code, one of the most sophisticated codes in the country, includes nuclear reactors as division three. For ductile iron — not gray iron which is very brittle, but ductile iron which is almost as good as steel — you have to have a safety factor of five even today, because it's a casting and castings can have big imperfections. Whereas wrought materials, you've squeezed out the imperfections, so for steel it might be a safety factor of two. The boiler and pressure vessel code is this thick because when you design something, it will tell you what factor of safety you need above your anticipated load.
§8. SN curves, OSHA, and helicopters [36:49]
The structural welding code basically used to have two safety factors. Dynamic loading — a bridge where trucks and buses go over it and it vibrates — that's 2.0. Anybody know why the structural welding code would use 2.0 for dynamic or cyclical fatigue loading? It's because of the way we used to look at stress concentration and fatigue life — fifty, sixty years ago we used what we called an SN curve. [Tom draws on board.] S is stress and N is the number of cycles — actually log N, so ten thousand, a million, you're going on a log scale.
You'll have a stress that's your uniaxial tensile stress, and at about fifty percent — actually 57 would be down here — you get to infinite life. Steel under constant amplitude loading will have infinite life. If you have variable amplitude that will have variable life. That's one of the reasons they use the factor of two. Whereas on a static design like a building, nothing going over it is going to cause it to vibrate like a bridge. Static design is 1.67, five thirds.
If I go through the old structural welding code from 15 years ago, they would require welds to have twice 1.67, or 3.3, as a safety factor. Why? Because just like castings in cast iron, welds can have porosity and imperfections that are larger than you expect in the base metal. So the weld metal has to have twice the safety factor of the base metal. That's the way we used to do it, and we still do sometimes.
OSHA, if someone's going to be up more than six feet in the air, by law requires 4.0 safety. A ladder I go to the hardware store and buy will have a 4.0 safety factor. If it's rated for 225 pounds of person and tools, you can put 900 pounds on it. The odds of that failing are pretty slim — 4.0 safety factor is really big.
Tree stands — hunters who want to go out and kill themselves, actually they want to kill something else, but sometimes they kill themselves — tree stands are only a factor of two. OSHA cares about scaffolding for construction, but OSHA doesn't regulate tree stands. It's like build-your-own-plane, kill yourself, knock yourself out. But if you're going to have workmen building a building, you've got to have them with safety harnesses.
I was watching the construction of the nano lab, I come up an elevator there from the parking garage, and they had a guy just seven feet off the ground, but he had a harness with a D-ring and a cable so if he fell he wouldn't fall more than six feet. Why? Because they've learned that if you weigh 200 pounds and fall six feet, that's 1,200 foot-pounds. I did that calculation in my head. Historically when people fall, they can get fairly serious injuries when you have 1,200 foot-pounds of energy.
The X-33 spaceplane started out with a 2.0 safety factor. They had manufacturing problems — this was a fifty-million-dollar structure — and they knew they had some big defects in it. NASA sharpened their pencils and said, "Oh, we still got 5% safety factor above." They tested it, and it actually passed until they started to warm it up, and the thermal stresses from going from liquid hydrogen temperatures to room temperature — it failed because it didn't have enough safety factor. If it had been manufactured properly it may not have failed.
The New Orleans levees — around 1880 my great-grandfather was a civil engineer working on the levees — I read somewhere after Katrina that the safety factor on the levees was 1.3. That 1.3 is one of the lowest safety factors I know of. Typically safety factors are around 1.67 to 2. When you're hoisting equipment above someone's head, or someone's more than six feet off the ground, they'll go to 4. Some cases when you're working with castings and pressure vessels where the consequences of failure are pretty severe — blowing up a building or a city block — safety factor of five.
Anybody have an idea of what the safety factors might be on a helicopter? It's actually very high. I was surprised. It's a trick question — I said safety factors, there's not one safety factor. You're weight-critical, so they're going to look at how critical the failure would be. Most things I've seen are around 10.
Some things are critical, like the mast. There's no redundancy on the mast. If the mast cracks, you're going down. I don't even know what the safety factor is, I suspect maybe three. The problem is the mast is big steel, it is heavy, so they can't use a factor of ten. But most of the structural stuff, the spars — when I've done safety factor calculations on these things when I've had a failure, it's up around ten. These are vibration machines, they're fatigue machines, and the consequences of failure — it's very easy to kill yourself, particularly if you lose your rotor. There's not much safety after that. If you actually still have the mast and rotor you can do an autorotation. Anybody know what autorotation is?
Student: [explanation of autorotation]
If your engine's working, you're spinning the blades and that gives you lift. If your engine quits — if you have some forward momentum, you can put those rotor blades into the wind, your forward momentum, and the air coming through will cause them to freewheel and give you some lift. If you're just hovering you're dead. I did an autorotation once, and it's not much different than a regular landing if you have enough forward momentum.
There's a little part of the envelope of height versus forward velocity where you can autorotate, and an area called the dead man's zone, for obvious reason, where you can't. Helicopters are not as unsafe as you might think. I was surprised when I started doing calculations — they have so many parts and they're vibrating, but they actually have quite an amazing safety factor given the situation.
§9. ASD vs. LRFD — the modern design transition [45:00]
That's why I brought these two books. The old way was called allowable stress design. We did that from the 1920s probably up through around 2000. The first nine editions of the American Institute of Steel Construction Manual of Steel Construction — it's a really exciting manual, you need to own a couple of these books, one for home, one for work — has tables of sectional properties of an I-beam or a channel. It also has sections on design requirements.
What we did in the old days under ASD, allowable stress design, was basically use 1.67 or 2.0. The structural welding code used to say, before 2000, use ASD — they didn't even call it ASD. You didn't know what the stresses were going to be, so you'd give sixty-seven percent or a hundred percent extra capability in your design, depending on whether you were statically loaded. It doesn't matter if the stresses are coming from north, south, east, or west, top or bottom — you use the same safety factor. Historically we found 1.67 statically loaded, 2.0 fatigue loaded, was good enough. We moved all the way down from six in 1850 to one hundred fifty years later we were down to two or less.
But in the 1950s, an engineer in the Soviet Union said, "This doesn't make any sense, we're using too much material." As an engineer he wanted to do it better. He said, "If we know whether it's tension, compression, shear, bending — there are different types of loads, you can write down the stress tensor and find each one. Rather than just assuming the loading can come from any direction, we often know what direction it's going to come from, and we can do a better design job." He came up with what is load and resistance factor design.
The AISC manual is now the Manual of Steel Construction; I think it's in its 5th edition. The 9th edition was the last ASD design. If I go to the 2010 welding code, it says I can use either allowable stress design — across the top — or load and resistance factor design. This has a safety factor of 1.67; this has a resistance factor. You have to know a lot more about the loading on your structure. But if you know more about the loading, you can save about one third of the weight. So there's a lot of money here.
On those transmission towers in Alberta — a hundred thousand tons — you could be saving 30,000 tons, tens of millions of dollars worth of material. There have been some interesting failures because of this stuff, and I'll talk about that on Tuesday. There are books written on this — Steel Structure Design ASD/LRFD compares the two, and shows that if you know more, you can save weight. But the problem is, it's a more complex system.
Most companies have proprietary computer programs to do the LRFD. ASD we could all do on a sheet of paper with pencil. That's actually why we did it then — the computers were doing it in the 1990s. But now LRFD, just the American Society of Civil Engineers document 360, is a little too complex. You have to ask, do you have to have some expert who really knows the whole thing? With LRFD, yes you do. Or you have a computer program that's a surrogate expert, because most engineers can't do it. I can't do LRFD on my own. Some people coming out of school can, but most of them, unless they're doctoral-level civil engineers, are going to be using some canned program. There are some interesting failures that come about because of canned programs. So I'll talk about some of that. I'll see you next week, have a good weekend.