Northeast Florida has plenty of plant floors and a short list of integrators who actually pick up the phone. I'm HillPoint Automation, one senior controls engineer, and the person who writes your code is the one who answers when you call.
A control system integrator is the person who makes your machines, your PLCs, and your SCADA talk to each other and do what production needs. That covers writing the PLC logic, building the HMI screens, standing up the SCADA layer, wiring the panel to code, and getting data off the floor and into whatever system your office runs on.
The reason to hire an integrator instead of a general electrician or a panel shop is accountability. When a line goes down at 2 a.m., you don't want three vendors pointing at each other. You want one engineer who knows the whole system and can trace the fault from the sensor to the server. That's the job.
I'm HillPoint Automation. Solo firm, Will Cordero, 18 years in industrial controls on programs for NASA, OneWeb Satellites, and Airbus US Space and Defence. I'm based in Melbourne on the Space Coast, and I take work up the coast to Jacksonville and across Northeast Florida. When you call, the engineer who does the work answers.
Jacksonville has a lot of plant floors and not many integrators to service them. Most of the manufacturers and distribution operations I talk to in Northeast Florida end up calling a firm out of Atlanta or Orlando, waiting two or three weeks for a slot, and then getting a junior tech who has to phone home every time something's unusual.
That gap is the whole reason I take work in the Jacksonville market. You get the senior engineer on the first visit, not the third. I scope the job, write the code, commission it, and I'm the one you call when you have a question six months later. There's no account manager in the middle and no handoff to someone who wasn't on-site for the build.
Being vendor-agnostic matters here too. A lot of the local options are tied to one product line, so their answer to every problem is the hardware they resell. I'll tell you straight whether your existing Allen-Bradley platform has years left in it or whether it's time to plan a migration, and I've got no incentive to sell you a rip-and-replace you don't need.
Most of my Jacksonville PLC programming work is Allen-Bradley and Siemens, because that's what's on the floor here. On the Rockwell side that means ControlLogix and CompactLogix in Studio 5000, plus the older SLC 500 and PLC-5 systems still running lines all over Northeast Florida. On the Siemens side it's S7-1200 and S7-1500 in TIA Portal, and I work in RSLogix on the legacy Rockwell platforms.
If you're on a PLC-5 or an SLC 500, you're on borrowed time. Allen-Bradley discontinued the PLC-5 line and the SLC 500 is end-of-life, which means spare processors and cards are getting expensive and hard to source. When one fails, you're on eBay hoping a used part holds. I plan and execute those migrations to ControlLogix or CompactLogix with the downtime windows worked out ahead of time, so you're not gambling your production schedule on a conversion that runs long.
New builds and retrofits are the other half of the work. I write the logic, build the PanelView or Perspective HMI, and document it so your maintenance team can actually read the program a year from now. Clean, commented code the next person can follow is part of the deliverable, not an upsell.
SCADA is where I spend a lot of my time, and my platform is Ignition 8.3. If you're running a plant in Jacksonville and you want real visibility across your lines, Ignition is hard to beat on licensing and flexibility. I build in Perspective, so your screens run in a browser or on a phone without a separate client install for every seat.
The bigger piece is getting your data organized. I use MQTT with Sparkplug B and build toward a Unified Namespace, which is a plain way of saying every piece of equipment publishes its data once, in a consistent structure, and anything that needs it can subscribe. No more polling forty devices from six different scripts, and it scales cleanly when you add a line.
From there I can tie the floor into your business systems. I've done MES work and MES-to-ERP integration, including NetSuite, so the numbers your operators see on the line and the numbers your office sees in the ERP come from one source, updating live instead of from a spreadsheet someone keys in at the end of a shift.
Northeast Florida's industrial base isn't one thing, and the controls problems change with it. Here's where I do most of my work in the region:
I keep client names off my website, so what I can give you is the shape of the work, not a logo wall. A couple of examples of what that looks like in practice.
A Space Coast supplement manufacturer with no controls engineer on staff needed someone to own their automation from the PLC logic to the panel to the production reporting. That's a common setup for me. I become the outside controls department for a company that isn't big enough to keep one on payroll.
On the water side, a Central Florida municipal water utility needed reliable pump and SCADA controls for infrastructure that can't just be taken offline for a rebuild. That work is about doing the cutover carefully and testing every failure mode before it matters, not moving fast and hoping.
Beyond programming and SCADA, the service list covers what goes with them: UL 508A control panel design and modification, VFD setup and troubleshooting, OT network design, and emergency controls service when a line is down and production is stopped. If you've got a line dead right now, that's the call to make first.
Whether it's a PLC-5 that needs to migrate before the next processor fails, an Ignition SCADA build, or a panel that has to meet UL 508A, you'll talk to the engineer who does the work, not a salesperson. Call (321) 378-0424 and tell me what you're dealing with. What system is giving you trouble?