This is how a pilot on a barbed wire line would work. A camera at the machine, a server beside it, and every barb measured and logged as it is made. Here is what we heard. Barb spacing is critical.
Too close or too far apart is out of spec, and the product is total scrap. Today, some checks are visual and some are manual. There are no cameras on the fencing machines yet, and the plant's internet is not the fastest. These are the numbers the pilot is built around.
The machine runs at 300 barbs a minute, five every second. Nominal spacing is 6 inches. The standard is that 93% of barbs fall within three-quarters of an inch of ideal. Your engineering team confirms the final tolerance before the pilot starts.
Meet Jordan, shift lead on the barbed wire line. Let's follow one 10-minute run. Capture, measure, log, warn, act, and prove. It starts at the machine.
A fast global shutter camera is mounted close to the wire, just after the barb head, with its own lighting. Its frames go to a GPU server on the plant network beside the line. The video stays in the plant. Only measurements and alerts travel, so a slow internet connection does not get in the way.
VIDIZMO engineering confirms the exact camera, lens, and frame rate once we see video of your line. Next, every barb is measured. A model trained on your wire finds each barb as it passes the measurement zone and measures the gap to the barb before it in inches against a calibration target fixed in the camera's view. Barb 1 measures 6.19, barb 2, 5.84.
Every value is compared with the band, from 5 and a quarter to 6 and three-quarter inches, five barbs every second. Every measurement is logged. Each barb gets its own row, its number, the time, the spacing, how far it is from 6 inches, and whether it is in the band. After 300 barbs, the log also keeps a rolling share in the band and a rolling Cpk.
Minute one closes with 300 barbs, a mean of 5.99 inches, every barb in the band, and a Cpk of 1.47. Then it warns before scrap. This is the whole run, 3,000 barbs. For 6 minutes, the spacing holds steady around 6 inches.
Then the barbs start running long. At 6 minutes 35, barb 1980 measures 6.89 inches, the first one outside the band, and it is flagged. At 7 minutes 10, the rolling Cpk drops to 0.99. More than 99% of barbs are still in the band, but the process is drifting, and Jordan's warning fires.
The warning reaches Jordan and maintenance with the clip of the barb head attached, so someone can check the feed while the product is still good. If nobody acts, the next limit follows. At 8 minutes 46, the rolling share in the band falls to 92.7%, below the 93% standard, and a stop request is raised. That is 480 barbs, 1 minute and 36 seconds after the warning.
Sending a stop signal to the line's controller is a connector built for the pilot, and the rules are yours. And every result can be proven. At the end of the run, each minute has its own line. Barbs, mean, spread, smallest and largest gap, share in the band, and Cpk.
Minutes 1 to 8 pass. Minute 9 falls to 88.7%, and minute 10 to 72.3. Across the whole run, 2,870 of 3,000 barbs were in the band, 95.7%, which would pass on a run total alone. That is why every barb in every minute is logged.
The full log exports, and each alert is kept with its clip in VIDIZMO Nexus. The same approach covers two more checks. On the welded fence line, a model trained on your good and rejected panels checks that the pattern stays square and that every wire is present. A shifted pattern or a missing wire is flagged with the panel number and its clip against your own reject criteria.
And for standard work, each step of a procedure is checked in order. Here, an example changeover. When a step is skipped, it is flagged, and the flag links to the clip of that cycle. Here is how the pilot would run.
You share video of both machines and confirm the spec. VIDIZMO engineering returns a camera recommendation and a feasibility view. One camera and one server go on one line. The model is trained on your good and out-of-spec barbs, which takes about 13 to 15 weeks in a pilot, and together we agree the pass and fail criteria up front.
Alerts and logs go to the systems the plant already runs. Microsoft Teams, Exchange email, and Axis and Hanwha cameras are in the integration catalog today. A line controller or an MES that is not listed is built to your requirement or reached through a REST endpoint or an MCP server you define. Capture at the machine, measure every barb, log every result, warn before scrap, prove it minute by minute.
The next step is simple. Send us video of the barbed wire and fence machines, and we will come back with a camera spec and a one-line pilot plan.