To choose rebar software, start from your company: the whole chain, adoption on the shop floor, total cost, your data, standards and support.
To choose rebar software, start from your company, not from the vendor's feature list. Check five things: that it follows the steel without a break from drawing to invoicing, that your people on the shop floor will actually use it, that the total cost is known in writing before you sign, that your data belongs to you and can come out, and that someone who knows the trade answers when something gets stuck.
I spent ten years in the shop and on job sites as a detailer and a placer, and I've been programming for more than 30 years. I used rebar software for years, on the side of the people who use it every day, while also understanding what's behind the screen. This guide gathers the questions I'd ask any vendor. For an overview of the category, start with the complete guide to rebar software.
Because a feature list describes the software, not the way you work. Two vendors can tick the same boxes and deliver very different results once they're on the shop floor.
Before the first demo, take an hour to describe how information moves in your company. A rebar company goes through roughly the same steps every time: the call for tenders, the estimate and the bid, the contract award, detailing the drawings, the bar lists, purchasing, production, delivery and placing, then invoicing. For each one, write down who does the work, in which tool, and at what point the information gets retyped somewhere else.
The result is often revealing. In a mid-sized fabrication shop, you'll easily find a list of bids in one file, project tracking in another, bar lists in a spreadsheet, tags in a machine's software and billing in the accounting system. Each tool does its job. The problem is between them.
In my view, this is the criterion that weighs the most. Costly rebar mistakes rarely happen in the middle of a step. They happen at the handoff from one step to the next: a bar list retyped with a wrong length, which then gets copied onto the tags the shop fabricates from; a drawing revision that never made it to the shop's tags; an extra placed on site that never shows up on the invoice.
Take a common case. A change comes in when the steel for a wall is already cut and bent. You need to know right away what's been produced, separate what's lost from what's still good, and get the extra approved before the site moves on to something else. If that information lives in three different tools, someone has to reconcile it by hand, often at the end of the day, and the extra gets lost along the way.
Ask the vendor to follow a real bar in front of you, from the drawing to invoicing, through the bar list, the tag and loading. Watch how many places something has to be re-entered, a file exported or the software switched. Every re-entry is a place where an error can get in. You'll find more detail on these steps in the bar lists and production sections of the complete guide.
Every piece of software comes with choices already made: how to number a bar list, how to group bars into bundles, how to calculate a billable weight, how to handle an extra. The real question is who made those choices, and whether they've ever worked in a company like yours.
Large suites have a real merit: they bring structure and impose good practices. In return, they're often more complex than necessary and hard to adapt. When software promises to configure everything to your needs, you're the one who has to supply the expertise for that configuration, or pay someone to do it.
The balance I look for is simple to state: sensible defaults, set by people in the trade, and the ability to change them when your company has a good reason to work differently. Ask the question directly: who set the defaults, based on what experience, and what does a change cost?
The licence price is only part of the bill. Licensing and technical services costs are often what make a company hesitate in front of the large suites. Before comparing two offers, put every item on paper:
Ask for a total price in writing, for your company, before you sign. A vendor who can't tell you what you'll be paying a year from now is leaving the risk with you. We'll come back to this in an article on the real cost of rebar software.
Software nobody uses costs more than no software at all. On the shop floor, the rule is brutal: if the tool is more tedious than paper, paper wins. The shop foreman keeps his own spreadsheet, the project manager writes the extras in a notebook, and the software ends up reflecting only part of reality.
Adoption is rarely decided in the owner's office. It's decided with the person who prepares the bar lists, the one who prints the tags, the one who loads the truck, and the foreman who has to log hours and extras at the end of a day on site. The shortage of skilled labour adds a constraint: a new employee has to become productive quickly, without depending on the one person who knows the system.
During the evaluation, have those people try the tool, not just management. Bring a real bar list from one of your recent projects. Ask how long it takes to train someone who has never seen the software, and who handles that training.
Your bar lists, your bid history, your placing hours by type of work: that's your company's accumulated know-how. It's also what will let you estimate the next contract better. That know-how has to belong to you, whatever the software.
Four questions to ask in writing:
A serious vendor answers these questions without hesitating. A contract that says nothing about getting your data out is a signal worth noting.
General business software doesn't know what a 15M (≈ #5) bar, a standard hook or a bar list is. Rebar software should. Your work relies on the standards that govern the design of concrete structures and the placing of reinforcing steel where you work, and on the industry's standard detailing practices.
The ways you bill matter too. A lump-sum contract is often billed as a percentage of the weight delivered, while a unit-price contract is billed by weight and placing hours, not forgetting the extras for steel and placing. Ask the vendor how their current customers bill these two types of contracts, and check that the software doesn't make you redo the calculation in a spreadsheet.
Also ask who on the vendor's team has ever detailed, fabricated or placed rebar: the answer says a lot about how well these practices were understood.
Support isn't measured on demo day. It's measured on a Friday afternoon, when the tags won't print and the truck has to leave. The construction season is tight: companies rush to finish their projects before it ends, and that's exactly when a blockage costs the most.
Ask who answers, in what language, how quickly, and whether the person on the other end of the line understands the difference between a bar list and an invoice. Also ask to speak with a customer company about your size, and ask them a single question: the last time you had a problem, how long did it take to fix?
Finally, think about when to roll it out. Switching systems in the middle of the season, while the shop is running at full capacity, is rarely a good idea. The quieter period that follows the busy season leaves time to train the team and bring the data over. An upcoming article will cover rolling out software without stopping production.
Some signals come up often and deserve a closer look:
None of these signals rules out a piece of software on its own. Several together do.
It's a real option, and it deserves an honest comparison. In many companies, the real competitor of rebar software isn't another piece of software: it's a well-built spreadsheet, or a person who knows everything by heart and who, in practice, is the system.
That works, until the day that person goes on vacation, changes jobs or retires. Your expertise and your ways of working are what set you apart from the competition. If they exist only in someone's head or in a file only they understand, you won't be able to pass them on to the next generation. And a bar list retyped by hand from one file to the next will sooner or later produce a costly mistake.
So the question isn't "software or no software," but: can the way you work today grow with you, and survive the departure of a key person? We compare these options in more detail in Excel, homegrown software or rebar software: when is it time to switch?
Keep this list for your meetings. Ask every vendor the same questions, and write down the answers.
Metacis is rebar software built by people in the trade. If these questions are coming up in your company, let's talk: request a demo.
Share
Metacis is rebar software designed by people in the trade.