Owner/Founder for North America & ArchitectureLayer Consulting | CRM Specialist | Supply Chain Analyst | Front-End Developer | Enterprise Architect
At SHAPE headquarters outside Brussels, she oversaw sports programming for more than 700 military families and led a staff and volunteer group of over 50. Week-long trips across Europe, financing, lodging, tournaments. She was playing for a Belgian national division team at the same time. Nothing in that résumé line predicts a career in enterprise systems architecture. Almost everything in it predicts how she practices one.
The Architect Who Tells Companies Their Standard Is Not a Standard
Elizabeth Cruz is the founder and Principal Enterprise Systems Architect for North America at ArchitectureLayer Consulting, the firm she launched in June 2026 after two decades spent on the seam where factory machinery meets enterprise software. Her clients are multi-site manufacturers and logistics operators running standardization programs that quietly stopped being standard. What defines her is a willingness to say so in the room, to the person who signed for it.
Belgium, Fort Polk, and Two Master’s Degrees Earned Sideways
The Brussels years ran from 2009 to 2014, and she spent the middle of them earning a master’s in psychology from University of Maryland University College while the sports program was still running. A second master’s followed, this one in computer software engineering, finished in 2016. The order matters. She studied people first and systems second, which is the reverse of how nearly everyone in her field arrives.
The technical career began in support work. Zodiac Aerospace from 2013, remote desktop and networking, where she held call satisfaction scores between 95 and 100 percent against a 90 percent average. Then the Department of Defense hired her as Information Technology Program Director covering seven facilities at Fort Polk serving 26,000 personnel, handling network security and the transfer of confidential military records.
Markem-Imaje came in 2017 and lasted eight years. This was serialization: track and trace, aggregation, unique product coding, and record keeping that has to satisfy U.S. Title 21 CFR Part 11 auditors while a packaging line runs at speed. She worked with Global Pack Leaders on data-flow discrepancies and with OEMs on integration, and she learned where these systems break.
“Most other issues can be resolved with the right technical approach, but maintaining end-to-end data traceability is non-negotiable.”
Lose sight of where data originates and where it is consumed, and diagnosis becomes guesswork. Confidence in the whole system goes with it.
BEUMER Group brought her into warehouse logistics in 2025, where she architected a Software Control Layer for large e-commerce networks. By her account of that period, she re-architected a $220 million infrastructure standard at Amazon and reduced engineering labor by 47 percent. Her objection to what she found there was not that it was badly built. It was that it had been built to last only until the next firmware release.
“OPC can be a useful integration tool, but it is not, in my view, a reliable long-term strategy for enterprise-scale standardization.”
That is a heretical thing to say about the most common integration method in industrial automation. She said it anyway, in white papers and in meetings, and then went independent to keep saying it.
Forty-One Projects at Once, and She Still Walks the Floor
ArchitectureLayer exists to close what Elizabeth Cruz calls the Physical-to-Digital Integrity Gap: the distance between what actually happens on a production line and what the software believes is happening. Her first engagement was the technical architecture for a $250 million-plus software control standardization program across multi-site enterprise operations. The rest of the work is triage, auditing multi-vendor integrations that are failing and recovering the data flow before a deployment date collapses.
The numbers behind her are dense. Forty-one concurrent customer projects delivered across North America. Forty-four percent annual revenue ownership and a $6.3 million regional contribution. An 80 percent reduction in implementation timelines through standardization, and more than $14 million in total business impact.
Volume like that usually comes from staying at a desk. She does the opposite.
“Is there a partially completed pallet hidden in the corner? A vision camera that has been disabled because it creates more problems than it solves?”
Those are the questions she asks herself walking a plant, and they are diagnostic. A disabled camera means an operator decided the technology cost more than it returned. A hidden pallet means a rework process nobody documented. Neither appears in a requirements document, and both will break an integration designed without them.
Her verdict on why multi-site programs fail is unsentimental.
“If you treat each plant as a completely independent entity, true standardization becomes impossible and the organization ends up creating a false narrative that every site requires a unique solution.”
One global chemical manufacturer learned this the expensive way. She quoted the work, the customer balked at the price and hired another vendor to standardize its palletizing operations the cheaper way. A year later they came back. Firmware upgrades had broken printer integrations, interfaces could not be copied between devices, and every palletizer, AGV and vision system had grown its own code to maintain. In her summary, they had standardized the technology stack but not the business logic. She still had the original architecture, adjusted it, and moved the project forward.
She prices against the same conviction, working from a firm not-to-exceed model. If a project runs over budget without an approved customer change request, her execution team absorbs it, not the client.
“When I make a mistake, I take ownership of it immediately.”
That posture extends to who she is willing to contradict. Standing across from a chief executive and respectfully challenging an assumption is, in her description, part of an architect’s job rather than a risk to be managed around.
Seven Hundred Families, Forty-One Projects, One Problem
The Belgium job was never really about sports. It was 700 families, 50-plus staff and volunteers, buses and lodging and money and dates, all of it required to converge without anyone stranded in a foreign country. The plants she walks now have the same shape and higher stakes. Different machines, different vendors, different local habits, one enterprise that has to behave as though it is one enterprise.
Elizabeth Cruz has spent seventeen years solving the same problem in increasingly expensive rooms.
She has always done logistics. The cargo just changed from children to data.
Elizabeth Cruz, MS, is the founder and Principal Enterprise Systems Architect for North America at ArchitectureLayer Consulting, based in Medford, New Jersey. She works with manufacturers, logistics operators and industrial enterprises to reconcile real-world plant conditions with scalable software architectures across multi-site operations. To connect with Elizabeth or learn more, visit https://architecturelayer.com/ or find her on LinkedIn.
