Common Software Used in Pre-Engineered Building Design and Detailing

PEB offices rarely live in one program. Metal Building Software (MBS) is often where frames are born. STAAD.Pro appears when a consultant wants a general analysis model or when an unusual frame leaves the PEB engine. AutoCAD still produces most approval sheets. Tekla Structures appears when the fabricator wants a BIM model. Excel becomes the unofficial database for reactions, bolt counts and comment logs. Automation — LISP, scripts, purpose-built converters — sits in the gaps.

The danger is not using many tools. The danger is not deciding which tool is master for geometry, which is master for member size, and which is master for issued drawings. When MBS, STAAD and CAD each hold a slightly different eave height, the error looks like a software bug. It is a data-ownership bug. This article maps the common stack used on pre-engineered buildings and shows how data should move, using the PEB design workflow as the spine.

StruTools sits in those gaps on purpose: MBS Reactions for reaction tables, Staad2CAD for analysis geometry heading toward drawings, MBS Approval Package for sheet assembly, plus LISP programs and Excel programs. They are mentioned here as examples of automation, not as a requirement to use them.

The PEB software stack in practice, not in a brochure

A realistic small-to-mid PEB team might size frames in MBS, check a stepped crane frame in STAAD.Pro, draft approval in AutoCAD, and send a fabricator either 2D shop drawings or a Tekla model. A larger fabricator may detail everything in Tekla and only use AutoCAD for client-facing 2D. Both can be professional. What they share, when they work, is a written rule for data mastery at each workflow stage.

Do not collect licenses to look complete. Collect a path: input → analysis → reactions → approval → detailing → CNC. If a program is not on that path, it is a viewer. Viewers are allowed. Masters that contradict each other are not.

Analysis and PEB-specific engines

Metal-building software exists because tapered built-up frames, cold-formed secondaries and PEB connection families are tedious to rebuild from scratch in a general finite-element tool. General tools exist because not every PEB is typical, and because consultants often ask for a model they can open without a PEB license.

MBS and similar PEB engines

These programs speak the PEB product: frames, purlins, girts, cladding loads, often reactions formatted for the shop’s habits. Output files and printouts then have to be read by humans or by utilities. Column reactions are a common extract. If you process those extracts by hand every week, a structured table such as the one StruTools MBS Reactions builds is simply a way to stop retyping.

STAAD.Pro as check, exception, or geometry source

STAAD.Pro is a general structural analysis environment. On PEB jobs it may be the only analysis tool, a check of MBS, or a source of node coordinates for CAD. What STAAD.Pro is and how to convert models toward AutoCAD cover those roles. The non-negotiable condition is identical geometry.

Detailing and drawing environments

Drawings are how other disciplines experience your design. AutoCAD remains the lingua franca of 2D approval packages. Tekla and other BIM tools earn their keep when piece counts, clashes and CNC matter. Neither environment should invent a haunch depth that analysis did not produce.

AutoCAD

Layer discipline, title blocks, and xref strategy decide whether a PEB approval set is maintainable. LISP and other automation help with repetitive steel drafting — grids, bolt patterns, sheet setup. See StruTools LISP programs as a category of that help, alongside whatever your office already runs.

Tekla Structures and BIM

A fabrication model can catch clashes a 2D girt elevation will miss, especially around cranes and mezzanines. Start it too early and you will detail the unapproved building. BIM does not remove the approval drawing gate; it makes violating that gate more expensive.

Spreadsheets and small automation that actually get used

Excel is where reaction tables, opening schedules, bolt summaries and consultant comment logs survive. That is either a strength — human-readable, easy to email — or a hazard if the workbook is unofficial analysis. Keep calculation-like sheets in the same revision culture as drawings. Excel programs of the checklist-and-table kind are appropriate; shadow design codes inside a personal spreadsheet are not.

AutoLISP, scripts and converters belong where a human currently copies coordinates or rebuilds the same title block. Staad2CAD is one converter pattern: analysis geometry into drawing-ready CAD. Automation should copy trusted data, not invent member sizes.

Which file is master — a decision table, not a feeling

Write this table for your office and stick it on the project. If two files claim mastery, pick one in the meeting, not after a clash.

Choosing tools without buying a second workflow

When evaluating software, ask what artefact it produces that another person can review, and how that artefact is revisioned. A program that only lives on one engineer’s machine is a risk. A program that exports a table, a PDF or a model others can open can sit on the path.

• Prefer tools that preserve member marks from analysis into drawings.
• Ask how tapered sections survive export; many general formats flatten them.
• Require a way to print or export reactions with combination names intact.
• Treat BIM as detailing after freeze, unless the contract is model-first and the team is staffed for it.
• Do not replace engineering review with a converter’s success message.
• Budget training; unused Tekla seats do not coordinate cranes.
• Keep a fallback 2D path for consultants who will not open a model.

Standing up software on a PEB project

Do this at kickoff so you are not inventing a data path during the first comment cycle.

1. Name the analysis master (MBS, STAAD.Pro, or both with a stated check relationship).
2. Name the drawing master for approval (usually CAD sheet set or a BIM drawing layout).
3. Name the reaction-table master and who emails civil.
4. Agree file-naming, revision letters and where superseded files go.
5. List permitted automation: converters, LISP, Excel extractors — and who validates their output.
6. Run a one-bay pilot from model to a sample approval sheet before production modelling.
7. Record which exports are one-way (analysis → CAD) so nobody round-trips blindly.
8. Revisit the map after first approval; detailing may switch master to Tekla without changing the approved envelope.

Engineering tips

• If STAAD is only a check, lock MBS geometry first and rebuild STAAD from those dimensions, not from memory.
• Keep a human-readable member-size list as a bridge between programs that do not talk.
• Plot PDFs from the CAD sheet set, not from a layout someone has open with unsaved changes.
• Store converter settings with the project so the next export uses the same units and layers.
• Use Excel for tables you will review; do not hide load combinations only inside a binary model.
• When Tekla and AutoCAD both exist, decide which one issues the stamped 2D set.

Software habits that create two buildings

Exporting STAAD to CAD, then editing depths in CAD because it “looks heavy”

That is a design change. Take it back to analysis or leave the depth alone.

Letting MBS and STAAD both issue reactions

Civil will pick the larger number, or the later email. One table per revision.

Starting Tekla from an unfrozen architectural model

You will detail docks that move. BIM amplifies freeze discipline; it does not create it.

Personal Excel design sheets with no second checker

If it affects member size, it is a calculation and needs the same review as the analysis file.

Automation without a sample check

A LISP that numbers sheets wrong will number them wrong at scale. Check the first output on every job.

PEB software coordination checklist

A short audit you can run when a new person joins the job.

• Analysis master file name is written on the approval cover or notes.
• Units are consistent across MBS, STAAD, CAD and Excel.
• Tapered members did not become prismatic in an unnoticed export.
• Column marks match among model, reaction table and drawings.
• Only one reaction table is circulating for the current revision.
• CAD xrefs point to the architectural revision named on the notes.
• Automation settings (layers, scales, converters) are stored in the project folder.
• Tekla, if used, is aligned to the approved envelope.
• Excel workbooks have dates, authors and a purpose line.
• Consultants know whether they will receive PDF, model, or both.
• Backup and superseded locations are known to more than one person.

Frequently asked questions

Is STAAD.Pro required for PEB design if the office already uses MBS?

Not universally. Many PEB frames are sized in metal-building software. STAAD.Pro is added for consultant preference, unusual structures, or geometry export. If both are used, geometry must match. See what STAAD.Pro is.

Should PEB approval drawings be produced from Tekla or AutoCAD?

Whichever environment your team can revision-control and the consultant can review. Many consultants still expect 2D PDFs. BIM can generate those PDFs, but only after the team agrees that the model is the drawing master.

Where do converters like Staad2CAD belong?

After the analysis model has been checked, as a way to get trusted geometry into CAD layers. They do not replace model checking or drawing review. Staad2CAD is that class of tool.

Can Excel be the reaction master?

Yes, if the workbook is generated from the analysis output, dated, and issued as a document. No, if someone types numbers from a faded printout and emails an untitled sheet called “reactions latest.”

Software should carry one building, not several

MBS, STAAD.Pro, AutoCAD, Tekla, Excel and small automation tools are normal on PEB work. The professional question is not how many logos the office can list. It is whether geometry, sizes, reactions and issued drawings can be traced to one revision of one building. Pick masters by stage and treat converters as copyists.

For the process around those tools, use the design workflow and coordination guides. For STAAD-specific paths, continue with STAAD.Pro to AutoCAD. Software mentions in this article, including StruTools, are educational. Design responsibility stays with the project engineer and the standards named in the design basis.