In the March 2010 Technology column, we focused on the third step of the Software Error Reduction Plan (SERP): processes and procedures. To continue that discussion, we will focus on how to produce a consistent set of results and output for every project that can be easily understood by anyone in the company. This would be advantageous for a number of reasons; for managers in the office who might not be familiar with how the programs work, it would provide them the information necessary to review the designs. It would also allow for consistency from project to project, regardless of the program used. When information about the project is needed for QA/QC, or in the future, having this set of output would allow for engineers to quickly gather the information they need.

Creating a standard set of output — In the process of putting together a set of project calculations, often there is a senior engineer or manager who is responsible for reviewing them. The manager may not be familiar with every software application used in the office, so if there is a standard set of output created, each manager can use that output to see the design calculations that are needed to complete his or her review. In developing this standard set of output, it also creates consistency from project to project, regardless of which software program is used.

Preparing a standard set of output can also be helpful for QA/QC and future verification of results. While the results created can be helpful for immediate review, they can also be helpful at any point in the future. If the software program is no longer available or has changed, how would other engineers have the information to verify the results? Having a standard set of output created would allow any engineer at any time to go back to that project and have the information necessary to see how the project was designed.

Creating a checklist for a standard set of output — Who in the office should be consulted about putting together a standard set of output? First, experienced engineers in the office will be a valuable resource to help determine what information should be included in this set of output. These senior engineers might be the ones who typically know what information they use on each project to review the designs. This would likely be similar to the information needed in the future to verify the designs should it become necessary. Second, the software champion (discussed in our October, 2009 column) for each program should be consulted to determine how to best gather this output from the program. Once the experienced engineers have created their list of information desired for the output, the champion for each program can help determine where these results or outputs can be generated.

Some examples of standard output to be generated include a variety of load reports. For applied gravity loads, a diagram of each floor plan showing the application areas and values for surface loads, line loads, and point loads would be helpful. For lateral load calculations, the criteria used to generate the loads, as well as the applied loads at each level can be used for reviewing the model both now and in the future.

Reports that show the criteria used for the design might also be part of the standard output. This lets the manager reviewing the results know what assumptions were made for the analysis and design of the structure.

In summary, creating processes and procedures for verification of results can be helpful for engineering firms in many ways. Having a checklist to create a standard set of output can be helpful to companies as they are going through a QA/QC process. In addition, this will help ensure consistency between projects, even when different software programs are used, and can be helpful when results may need to be reviewed in the future. We would be happy to provide you with a document template to help get you started in creating your own checklist for verifying results in structural software.

In a future column we will address the last step in the Software Error Reduction Plan: perform internal reviews of models. Please feel free to 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.