While talking with Randy from hsbcad, he shared a familiar frustration in construction: information gets drawn, passed to another team, and drawn again. Each redraw takes time and creates another opportunity for details to change or get missed.
Component manufacturers have a reason to care about what happens to a BIM model after design. Can the next team use its information for detailing and production? Or will someone have to recreate it before work can continue?
Start with what production needs
Randy describes working closely with manufacturers to understand their production problems, then using that feedback to guide development. A bottleneck on the shop floor can reveal something that needs to change much earlier in the design process.
When reviewing software, start with what a station or team needs to do its job. Work backward from there. A drawing may be clear to a designer while still leaving the shop searching for a detail or checking which revision applies.
Take a floor cassette with service penetrations as an example. Framing and openings need to be coordinated before production. Sharing the model can help, but the teams still need to agree on what information it contains and who is responsible for resolving conflicts.
Leave room for the way each plant works
As Randy points out, one piece of software cannot do everything for every component manufacturer. Plants have different equipment, requirements, and ways of organizing work.
Some differences are necessary. Others deserve a second look. Randy recalls visiting manufacturers who believed their process was unique, only to show him something he had seen at another plant. Comparing experiences can help a team decide which parts of its workflow need custom support and which could follow an established approach.
Before discussing an integration, write down what needs to pass between the systems and who will use it. Include what needs to come back. A software provider can give a much clearer answer to a specific production requirement than to a broad request to make two applications work together.
For example, importing geometry might save a designer time while leaving the shop without the component identifiers or revision information it needs. Ask to see the connection handle a representative job, including the details the receiving team relies on.
Treat the handoff as part of the process
Randy describes information moving in both directions between production tools and enterprise resource planning systems. For a plant evaluating that connection, it is worth deciding who will check that information arrived correctly and what happens when it changes.
Follow one project from design into production. Note where someone redraws, retypes, checks a second source, or asks another department which version to use. Talk to the people doing those steps before deciding what to change.
A manual check may catch a mistake before it reaches the shop. Re-entering the same dimensions because two systems cannot exchange them serves a different purpose. Understanding why each step exists helps avoid removing a necessary review while leaving the repeated work in place.
Choose one of those repeated tasks to investigate first. Test whether the receiving team can use the information already created upstream, and check the result on an actual job before expanding the change.
