The assessment is only half the work on a brownfield conveyor retrofit. What you do with what you find determines whether the project is profitable. Most scope problems don’t come from bad work — they come from integration points that weren’t mapped, boundaries that weren’t defined, and conditions that were observed but never written down. By the time those gaps surface, you’re already mid-project and the conversation with your client is a difficult one.
Two things tend to separate retrofits that finish on budget from ones that don’t: knowing every point where the conveyor system touches something else, and writing a scope that reflects exactly what you found during the assessment.
Integration Points
Every connection between the conveyor system and surrounding equipment is a potential scope gap. Map them all before you write the scope.
- Upstream and downstream interfaces: Document every point where the conveyor system connects to upstream or downstream equipment, whether that’s manual workstations, automated equipment, receiving docks, or other conveyor systems. Each interface is a scope boundary that needs to be explicitly defined.
- AMR and AGV interfaces: If the retrofit includes mobile robot integration, assess the existing transfer station locations against AMR docking requirements. Existing transfer stations almost never meet AMR integration requirements without modification.
- WMS and MES connectivity: Identify what warehouse management or manufacturing execution system the conveyor controls need to communicate with. Confirm the protocol, the data requirements, and whether the existing controls infrastructure can support the integration or whether new hardware is needed.
- Scanning and vision systems: If the system includes barcode scanning, vision inspection, or other identification systems, assess their condition and compatibility with the retrofit. These systems are frequently overlooked in conveyor retrofit scopes and surface as additions mid-project.
Protecting Your Scope
Everything in the sections above is an assessment input. What you do with that information in your scope document determines whether the project is profitable.
A few principles that have served us well on retrofit projects:
- Name what you found: Document the conditions you observed during the assessment explicitly in your scope. If you found chain wear at 80% of its service life, say so. If the PLC program backup doesn’t exist, say so. If the floor has levelness variations that will require shimming, say so. Conditions you document can’t become your problem later. Conditions you don’t document frequently do.
- Define the boundary of existing equipment: Be explicit about which existing components you are and aren’t responsible for. If you’re reusing existing drives, state that their condition was assessed as acceptable at the time of scope and that failures of existing equipment are outside your warranty. If you’re recommending replacement and the client declines, document that too.
- Include an allowance for concealed conditions: On every brownfield retrofit, include a line item for concealed or inaccessible conditions that couldn’t be assessed during the facility walk. The size of that allowance should reflect the age and documentation quality of the existing system. A well-documented ten-year-old system warrants a smaller allowance than an undocumented thirty-year-old one.
- Tie the scope to your assessment findings: Write your scope so that it’s traceable to specific findings from the assessment. When a client questions a line item, you should be able to point to the assessment condition that drove it. This protects you in scope disputes and builds credibility with clients who can see that your recommendations are grounded in what you actually found.
A scope that doesn’t reflect what you found during the assessment is a liability, not a proposal. The goal isn’t to win the project at the lowest number. It’s to win it at a number you can actually deliver.
Retrofit scopes get complicated fast when the integration picture isn’t fully mapped before the project starts. If you’re working through a brownfield application and want to talk through the conveyor side of the scope before you commit to a number, Power Pack can help you ask the right questions at the right stage.
