In previous columns (October 2009 and January 2010), we discussed four key steps behind the Software Error Reduction Plan, or SERP, and expanded upon the first two steps. This article focuses on part of the third step of the SERP process: Research and create written processes and procedures in your office for software usage (Processes).

Because of the variety of tools available and the number of different people who might use the programs, it is important to have company-defined processes in place. The purpose is twofold: first, to make sure that items are not overlooked while using software, in creating the model, and in running the analysis. Second, processes can help provide the correct output for experienced engineers in the office to review, so that in the future, if there is no model available, data could be reviewed and results verified.

Who in the office should be involved in creating these processes? The software champion for each program in the office should be included to help provide guidance on creating models and identifying where specific results should be obtained. Experienced engineers in the office should also be included; they can provide guidance on what results should be obtained and what information would be needed for future reviews, if necessary. It is possible that this could be the same person, but if the champion is a younger engineer, then an experienced engineer should also be included.

Creating a checklist of items to review
One of the concerns in using structural engineering software is that if incorrect information is entered into the program, then the results will likely be incorrect (garbage in = garbage out). For example, if an engineer enters the load due to the self-weight of the floor slabs as an area load, and the program also has a setting enabled to calculate the self-weight of the slabs automatically, then a double load is being applied, and the results do not reflect the real-life situation. How can engineers be sure that they are entering the correct information based on the program they are using?

Certainly, training (discussed in the January 2010 column) plays a large part in the process of making sure that engineers understand how the programs work, and the best ways to perform modeling tasks such as applying loads in a particular program. Creating processes is another way to give direction to engineers on how modeling should be approached in each program.

In addition, create a list of items to be considered during modeling and performing analysis and design within the software program. To help with the example given above, this would include reviewing the load properties and layouts after modeling, and reviewing the self-weight criteria to ensure that the program is including (or not including) the load as expected.

In analysis and design, include a check in the process to review the design criteria to ensure the correct design codes and deflection criteria are being used based on the type of the structure. For lateral load analysis, this would mean reviewing the applied wind and seismic loads, and also viewing the deflected shape of the building under the lateral loads. Viewing the deflected shape can be helpful in identifying modeling problems — such as foundation nodes incorrectly located — and in revealing areas where the building may require additional stiffness.

Other items to include on the checklist vary with the software being used. The experienced engineer and software champion should work together to identify critical items to be added to the checklist.

Creating written processes in the form of a checklist is important to the process of reducing risk in using structural software. These processes can help eliminate frustration by giving engineers a guide of items to check in their model and results to ensure they are getting reasonable results.

In a future column we will address the second part of creating processes and procedures, with a focus on generating output so that results can be verified in the future. Please contact us with any questions and also refer to our new technology website www.findyourtechnology.com

Lisa Willard, P.E., and Brian Quinn, P.E., are with SE Solutions, LLC — a firm dedicated to helping match top notch structural engineers with great companies and unique opportunities. They formerly worked for a combined 21 years at RAM International/Bentley Systems and can be reached at lisa.willard@findyourengineer.com or 805-482-8436 and brian.quinn@findyourengineer.com or 616-546-9420, respectively.