If a control panel stops doing what you need and the only person who can fix it is the shop that built it, you don’t own that machine. You’re renting access to it. That’s the question buyers in Middle Tennessee almost never ask up front when they hire someone to build a panel or program a PLC: when the job is done, who actually has the code?
Why This Matters More Than the Price on the Quote
A control panel build looks like a one-time purchase, but the PLC program inside it is the part that keeps running your line for the next ten years. If the builder hands you a locked, unlabeled, or password-protected program with no source files, every future change (a new part number, a new safety interlock, a line speed-up) has to go back through them, on their schedule, at their price. That’s not a service relationship anymore. That’s a dependency.
We see this most often when a shop inherits equipment from a previous integrator who is slow to respond, has closed up shop, or just quotes support work at a rate that makes a "simple" change feel like a renegotiation. By the time it’s a problem, it’s an expensive one to fix.
What "Owning Your Code" Actually Means
Owning your code isn’t a legal abstraction. It means three concrete things sit in your hands, not just your vendor’s:
- The actual program files, in an editable format, not just a compiled or locked copy
- Documentation that explains what the logic does, so a different qualified person could open it and understand it
- No password or access barrier that only the original builder can clear
If any one of those three is missing, you don’t have full ownership, no matter what the invoice says.
Questions to Ask Before You Sign
These are worth asking any panel builder or integrator before the project starts, not after:
- Will I get the source program, or just a compiled file I can’t edit?
- Is there a password on the program, and do I have it?
- Do I get wiring diagrams and a bill of materials, not just the panel itself?
- If I call a different shop in two years, can they open your files and understand your logic without calling you first?
- Where does the documentation physically live when the job is done?
A straight answer to all five is a good sign. Hedging on any of them is worth pausing on.
What a Documented Handoff Looks Like
A panel that’s actually yours leaves the shop with a labeled drive or printed set holding the current program version, the wiring diagram, the parts list with part numbers for anything you’d need to replace, and a note on what firmware or software version it was built and tested on. None of that should be a special request. It should be standard practice, because the builder shouldn’t need to be the only person who can touch it again.
How We Build Panels at Black Pearl
Our engineers program on Allen-Bradley/Rockwell, GE, FANUC, Mitsubishi, and Omron platforms, and every panel we build or program leaves with the current source files and documentation included, not held back. We’re ITAR registered and run an AS9100 Rev D quality system, which means documentation discipline is part of how we already work, not an add-on. If you’ve inherited a panel from someone else and can’t get a straight answer about the code inside it, that’s a conversation we can have too, before it becomes a production problem.
This isn’t unique to us, and it shouldn’t be. It’s a baseline a buyer should expect from any shop doing control panel work, PLC programming, or robotic integration (FANUC Authorized System Integrator or Universal Robots cobot work) in Middle Tennessee.
What This Costs You (Usually Nothing)
Handing over complete, documented files costs a builder almost nothing extra at the time of the build. It’s a documentation habit, not an engineering expense. The cost shows up later, and only for the buyer who didn’t ask: a service call that could have been a five-minute in-house fix instead becomes a multi-week wait for the original integrator to have time for you.
FAQ
Q: Is it normal for a PLC program to be password protected?
A: A password to prevent accidental changes on the floor is normal. A password only the original builder holds, with no way for you to get it, is not the same thing and isn’t something you should accept.
Q: What if I already have equipment and don’t know whether I own the code?
A: Ask your current integrator directly for the source files and documentation. If you get resistance, that’s your answer, and it’s worth getting a second opinion before the next change you need turns into a bigger problem.
Q: Does this apply to robotic cells too, not just PLC panels?
A: Yes. The same questions apply to FANUC and Universal Robots cell programming: you should get the program files and documentation, not just a working cell you can’t modify yourself.
Q: Will asking for full documentation slow my project down or cost more?
A: It shouldn’t. A shop that documents as it builds isn’t adding a step, it’s just not skipping one. If a builder quotes extra for documentation you should have received anyway, that’s worth factoring into the comparison.
Q: Who should I ask these questions to before starting a panel build or PLC project?
A: Whoever is quoting the work. It’s a fair, normal question for a shop based anywhere in Middle Tennessee, and a shop confident in its own work will answer it without hesitation.
If you’re planning a control panel build, a PLC programming job, or a FANUC or Universal Robots integration and want a shop that hands over full documentation as standard practice, request a quote and send us the print. Please don’t upload ITAR- or EAR-controlled drawings through a web form; we’ll give you a secure way to send those once we’re talking.
Send us the print.
BlackPearlLLC.com | (615) 439-5260