The Evil Eyebrow Header Image

Archive for the 'opinion' Category

Aug 06 2010

The Road Goes Ever On

Published by Bill Ruhsam under opinion, blog admin

Forest Road

The Road goes ever on and on
Down from the door where it began.
Now far ahead the Road has gone,
And I must follow, if I can,
Pursuing it with eager feet,
Until it joins some larger way
Where many paths and errands meet.
And whither then? I cannot say.

–J.R.R. Tolkien

I read The Lord of the Rings at an impressionable age. This particular poem is one of the ones that stuck with me. It’s generally applicable to almost any situation that involves inconstancy or motion or change.

Today marks the third anniversary of the first podcast published on Talking Traffic. I thought about doing a retrospective of some sort via the podcast but decided it wasn’t worth your time. So, here is me marking the moment. I hope you’ve been enjoying reading and listening here.

2 responses so far

Apr 10 2009

Professional Ethics Statements

Published by Bill Ruhsam under opinion, ethics

Stack of Documents
Image by unk’s dump truck on flickr

Ethics Statements
There was a question posted on one of the Traffic Engineering listservs I’m a part of that sent me out to read (again) the various Canons of Ethics in the professional societies I’m associated with.

I have two opinions about these various statements of professional ethics: One, they’re absolutely necessary to maintain our profession as a profession and two, they’re amazingly over detailed.

There is a lot of good stuff in those documents1,2,3,4, but it brings to mind a saying which, paraphrased, says “If you have to write down your ethical standards, you’re already lost.”

For the record, I don’t agree with that statement. At least, not for broad overarching ethics guidelines. For example, all the engineering ethics statements that I’m associated with begin with:

Engineers shall hold paramount the safety, health and welfare of the public in the performance of their professional duties

That is an excellent statement that sums up the entire raison d’etre of the Professional Engineer. Every young engineer, whether they intend to become a Professional Engineer or not should know and be able to quote that statement.

Other Canons, as they’re generally called, which are consistent between the various documents are briefly summarized as:

  • Act in a faithful manner to your clients
  • Act in a professional manner to your competitors
  • Don’t break laws
  • Be a good engineer5

Getting back to my earlier statement about how I think the various documents were too detailed, it depends on your perspective. There are two basic times in an engineer’s life when these docs should be reviewed and the ethical standards serve different purposes depending on which phase you’re in:

Just starting out
You, as a beginning engineer, might not realize that certain activities are considered unethical by your professional community. The one I always bring up as an example is moonlighting6. It is unethical to practice moonlighting because the engineer in question is able to underbid a non-moonlighting engineer, thereby depriving him or her of work. This falls under “Engineers shall build their professional reputation on the merit of their services and shall not compete unfairly with others.” 2

Another basic example of unethical practice which may not be obvious to the beginning engineer is allowing “authority” to dictate your professional judgment. “Engineers shall advise their employers or clients when, as a result of their studies, they believe a project will not be successful.”1 Seems obvious, right? However it’s easy for a person to be persuaded to shade their conclusions or recommendations because that’s what the client wants.

The difficulties of beginning engineers is broadened the cut back of ethics classes in colleges nationwide. Ethics is most often an elective class, not a requirement. This leads to engineers being required to learn their professional responsibilities on the job, which might dump them into court. This is why professional societies need detailed ethics statements.

Experienced Engineer
The experienced engineer does not need specific examples of unethical behavior. She will have already gone through the learning process mentioned above and will need only refreshers of what needs to be watched for. To that end, I heartily congratulate the State of Texas’ Board of Professional Engineers for requiring that 1 hour of the required yearly continuing education be in ethics7. Knowing the broader aspects of what is a required activity or what she is required to avoid is paramount to every engineer, but the experienced engineer does not want to spend time reading a document that appears to have been drafted by lawyers.1 That is why professional societies need a short ethics statements. Preferably with bullet points. Everybody likes bullet points.

A Better Document
You’ll notice that I have now called for both a brief and detailed ethics statement. Which brings me to the call to arms for committees who are slated to update their various ethics documents: Leverage the two-tier approach and use the web. I think that of the documents listed in footnotes 1 through 4, ASCE gets it best by listing their seven canons right up at the top of the document, then following up with “Guidelines to Practice Under the Fundamental Canons of Ethics”2.

Future ethics documents should be web-based, with internal links (perhaps even wikis). Five to 10 bold statements, starting with the most important one concerning public welfare, and then deeper discussion behind the links of what is an acceptable/unacceptable action under particular scenarios. I’ll draw a parallel to the United States Golf Association which lists their Rules of Golf, plus has a separate section for Decisions8 and follows up with an online quiz to test your knowledge of the nitty gritty details.

This is what I’ll push for if I’m ever on one of those committees. This will allow experienced engineers to review the guidelines quickly and for new engineers to deeply learn what is meant by “unfair competition” and other important details.


1: Institute of Transportation Engineers Canon of Ethics for Members
2: American Society of Civil Engineers Code of Ethics
3: American Society of Mechanical Engineers, Society Policy: Ethics
4: IEEE Code of Ethics
5: The various documents I’m referencing go into more detail about what all that entails, on a “year to year” basis. I was going to say “day to day” but it’s not so detailed as to list specific no-nos.
6: Moonlighting is the practice of cost-competing for extra work while employed in a full-time job elsewhere. The moonlighting engineer can underbid a competitor due to having their overhead expenses taken care of by their employer. Moonlighting is not unethical always, it depends on the circumstances. I’m primarily aware of this ethical standard due to my time as a mechanical engineer where work was less likely to be awarded on Qualifications standards.
7: Although I will chastise them for allowing “(d) A minimum of 1 PDH per renewal period must be in the area of professional ethics, roles and responsibilities of professional engineering, or review of the Texas Engineering Practice Act and Board Rules [ed. emphasis].” Reviewing board rules isn’t a strong indicator of ethical practices, in my opinion.
8: A Decision is the official determination of a questionable rules situation by the USGA.

3 responses so far

Feb 26 2009

Georgia DOT has its Work Cut Out

As mentioned previously, I’ve been doing some research into the portion of the Transportation Stimulus that will end up in Georgia. I’ve come up with some numbers that leads me to believe that the Georgia Department of Transportation contract office is going to be a madhouse in a few months.

ENORMOUS CAVEAT! All numbers here are WAGs1 at best and downright assumptions at worst.

Here’s what I’ve got. According to GDOT, here’s the preliminary list of projects that might be included in the stimulus. That list and some assumptions about what might be ready lead to these conclusions:

  1. $1 billion in stimulus funds for Georgia Transportation
  2. $500 million to be spent by July 8, 2009 (120 day shovel-ready provision)
  3. 75 projects on the books that would probably be ready and that meet the $500 million dollar goal which leads to…
  4. 1.3 Contracts per business day in order to meet the deadline
  5. Some really busy letting months of May and June

With respect to item number five, it seems likely that if the goal of 75 projects let by July 8 is to happen, the majority of the bidding will occur toward the late part of the 120 day period. That means the months of May and June. I honestly have no idea if the administrative, contract and engineering staffs of GDOT and the other agencies involved are capable of this sort of output. I hope so, because I’d hate to leave some of the money on the table.

Things that would help:

  • Fewer contracts - with only a few exceptions, the projects on that list linked above are “small” i.e. less than $10 million. A few more large contracts in the $25-$75 million range would even things out nicely. Unfortunately, those would be difficult to drum up in the 120 days.
  • Combined contracts - I haven’t examined the list in detail, but having contractors bid on bunches of projects at the same time would reduce the workload
  • Longer timeframe - a change to the law that would allow for a longer time-to-project than the 120 days. I’m rating that as “unlikely”
  • Cooperative agencies - a great deal of the delay in reaching the letting stage of a project contract occurs during agency reviews. If these review periods were shrunk, more projects could be ready in time.

I’ll be discussing some of this in my podcast due out on Monday morning but remember, I’m only working with my own research and what I read in the papers. For all I know, there’s already a plan that is set and rolling.


1: “WAG”: Technical term standing for Wild-Ass Guess. Usually used in the context of “this is better than a guess, worse than having real data, and based on experience”.

No responses yet