You walk a facility, put together a scope based on what’s visible, and sign a contract. Then the project starts and the real condition of the equipment becomes clear. A conveyor frame that looked serviceable turns out to be cracked. Controls wiring that wasn’t documented doesn’t match what anyone expected. A load that worked on the old system doesn’t transfer cleanly on the new one. Every one of those discoveries costs time, money, and credibility with your client.
Most brownfield retrofit problems get framed as commissioning surprises. They’re not. They’re assessment failures. The information that would have caught them was available before the scope was written — it just wasn’t requested, or wasn’t there, and nobody adjusted their approach accordingly.
The most valuable thing you can do before your first site visit is request documentation. What you get back tells you as much as the facility walk itself.
What to Request Before You Go
Start here. What the client can and can’t produce tells you a lot about what you’re walking into before you ever set foot on the floor.
- Original equipment documentation: Ask for OEM manuals, installation drawings, and any as-built documentation the client has on file. If they can’t produce them, that’s not just an inconvenience — it’s a signal. Systems that have been modified, repaired, or expanded over the years without being documented don’t announce themselves. They show up as surprises mid-project. If the documentation doesn’t exist, plan your assessment time accordingly and build that reality into your scope.
- Maintenance history: Request maintenance logs, repair records, and any recent inspection reports. What you’re looking for is pattern. A system with spotty maintenance history has deferred wear that hasn’t been addressed — it’s on the equipment waiting to be found. A system with consistent, documented maintenance tells a different story. The records don’t just tell you what’s been done. They tell you what hasn’t.
- Incident and downtime records: Ask specifically what has failed, how often, and what was done about it. Recurring failures in the same zone or on the same component are rarely bad luck. They’re almost always a symptom of an underlying condition that the repairs addressed temporarily without fixing permanently. Knowing where the system has been struggling tells you where to look hardest when you’re on the floor.
- Controls documentation: Ask for PLC programs, wiring schematics, and I/O lists. If these don’t exist or haven’t been updated to reflect changes made over the years, that’s a scope implication you need to understand before you commit to a number. Reverse-engineering a controls system that was never properly documented takes time, and that time belongs in your scope — not absorbed as overhead after the contract is signed.
- Load data: Get specifics on the product mix, weight range, and packaging configurations the system has been running. Then compare that to what the retrofit is expected to handle going forward. Changes in load profile are one of the most consistent sources of brownfield scope surprises and they’re entirely preventable. A conveyor that was designed and tuned for one product type may need meaningful modification to handle a different one reliably, even if the client assumes it’s a straightforward swap.
What the Documentation Tells You Before You Arrive
The documentation you receive, or don’t receive, shapes your entire assessment approach. A client who hands you a complete set of as-builts, current maintenance records, and an up-to-date PLC backup is giving you a head start. A client who can’t produce any of it is telling you something important about what you’re walking into.
Neither situation changes the scope of the physical assessment. But it changes how you weight what you find, how much allowance you build in for unknown conditions, and how you write the scope when you’re done.
If the documentation is thin, don’t treat that as a minor inconvenience. Treat it as a data point. Undocumented systems almost always have undocumented modifications, and undocumented modifications almost always become scope surprises.
Walk in knowing what the records say. Then walk the floor and find out what the records missed.
If you’re preparing for a brownfield conveyor assessment and want to talk through what you’re seeing before you finalize the scope, Power Pack has been part of enough of these projects to know where the gaps tend to hide. Talk to a Power Pack engineer.
