Guardian Shield Systems

Guardian Structural Technologies makes Guardian Shield panels, an engineered thermal envelope panel system for residential and commercial buildings. The panels are cut out of foam billets, and the company is building an automated line to do it: an infeed table, a cutting section and an outfeed table in a row, 36 servo axes and six hot wires. A raw billet 18 feet long is squared against a fence and pushed to a stop, a vertical wire slices a panel off its face, four wires cut the channels for the structural steel in one pass, and an overhead wire traces the window and door openings. Motion runs on a Bosch Rexroth ctrlX CORE with IndraDrive Mi drives, and the cutting paths arrive as G-code, one program per wire.

The engagement began in May 2026 and runs on two tracks, both ahead of commissioning. The first is the control software. The PLC project - IEC 61131-3 Structured Text written by the client's controls developer - came in for an independent review before the machine is powered up. The review had to be static: the ctrlX PLC Engineering project is a single encrypted binary that opens only in the vendor's Windows IDE, so it worked from a text export of all 46 program blocks, read line by line and cross-checked against the supplied documentation and the motion library calls. The report ranks findings by consequence, separates what is a fix from what is a question of design intent, says plainly what could not be checked without the device configuration, and ends with 15 questions for the developer rather than verdicts. A companion analysis covered how the hot-wire power controllers should reach the PLC, fieldbus module or analog I/O, a decision that had to land while the panel was still being built.

The second track is everything an operator and a maintenance technician need around the controller, built as one web console. It talks to the ctrlX CORE through the Data Layer: REST for browsing, reads and typed writes, server-sent events for live values. Its home screen is a machine map. All 36 axes are located on the real geometry, converted from the client's STEP assembly into a web 3D model, and each one is tied to its name in the PLC and the process specification, its sheet in the electrical drawings and its drive chain. A new alarm flies the camera to the faulted component. Around the map sit a fault logbook, cases that open themselves from alarms, maintenance with a per-shift pre-start checklist, escalation by email and SMS, security and network views, backups, and an admin side with usage and cost metering.

The assistant inside the console answers in English and Spanish from the machine's own paper: nine source PDFs, 2,531 pages in all - the 62-sheet electrical drawing set and the drive manuals, the largest of them 1,442 pages - plus the bill of materials, the process specification and assembly facts read out of the CAD file. Answers cite the document and the page, and the citation opens the PDF at that page. It can read the controller through tools, and it can propose a write, but only a person confirming in the interface executes one.

The status is stated as it is. The machine is not commissioned yet, and today the console is bound to a ctrlX CORE on a test bench that exposes a single axis. The 36 axes on the map come from the CAD model, the drawings and the bill of materials, an axis that is not bound to the controller never shows an invented live state, and binding the full machine is a written procedure waiting for the day it comes online.