Lukas M. Ziegler

They walk through a production chain step by step, identify which company supplies each layer, then point to the handoffs where information falls out. That matters in aerospace, where parts are specified to microns and grams and every production step must be documented for certification.

At the Siemens booth at AMB, Ziegler follows two parts: an oil pump for commercial aircraft turbines, redesigned with AI-driven engineering and simulation to be lighter and more efficient, and a high-precision turbine blade that illustrates machining accuracy, surface quality and throughput.

• The chain runs from NX design and Teamcenter planning through NX CAM Copilot programming, digital-twin verification, HELLER machine tools running SINUMERIK One, and Senseye Predictive Maintenance.
• They note that HELLER builds the machine while Siemens supplies the control and software layer, and that the true measure of a digital thread is how much value it delivers beyond a single-vendor showcase.

Read original

When the robot's kinematics run inside the CNC, the arm is path-controlled rather than point-to-point, and people who already know G-code can program it as they do the machine.

At Siemens' Chemnitz plant, the SINUMERIK Machine Tool Robot with Run MyRobot / Direct Control eliminates the separate robot controller.

• Ziegler links the setup to vibration compensation that counteracts oscillation during a cut, higher dynamic stiffness across the working area, and a smaller footprint with more reach than a comparable machine tool.
• The system suits applications such as aerospace and energy components, where bringing the machining system to the workpiece beats craning the workpiece into a machine.
• They cite Siemens' figure of over 200% better absolute path accuracy than a standard industrial robot.

Read original

That is both a priority and a method: a capability becomes understandable when the operating model, partners and deployment conditions are on the table. A post that skips them makes a capability claim, not an explanation.

On the Machine Tool Robot, Ziegler writes that Siemens does not make robots.

• Mechanical partners build the robot mechanics with Siemens motors inside, while a system integrator or machine builder brings the system together with the cabinet, drives, controller and software, commissions it, fits the end effector, such as a spindle, and ships it.
• They ask plainly where the catch is.
• In the physical AI post, they note that the demonstrated task is slow, that it was not possible before, and that Siemens is testing the approach in real production environments rather than lab demos.

Read original · Original 2

Their framing, credited to a Siemens robotics expert, is that large workpieces usually push buyers toward very large, expensive and inflexible machine tools, while a robotics approach quickly hits accuracy and stability limits. The useful territory lies between those two, and what matters is what changes on the floor.

Ziegler reports a customer example in which a robotic steel machining process that took 40 minutes with a standard robot runs in 5 minutes on the Machine Tool Robot, with stability and precision maintained and less floor space used.

• The framing came from Umberto Neuwerth, a robotics expert at Siemens whom they interviewed while filming at the Chemnitz factory.
• Neuwerth described the MTR as built for the space between very large machine tools and the limits of conventional robotics.

Read original

Simulation gets the same treatment—as a way to de-risk a physical process or make an invisible one tangible and discussable. Ziegler's range extends beyond factory equipment, but the argument stays the same when the setting changes.

AI-driven engineering and simulation make an aircraft oil pump lighter and more efficient; NX CAM Copilot assists CNC programming; and Senseye monitors machine health and process stability.

• Visual language action models let robots pick different cloths and place them into bags—a task Ziegler calls easy for people and very complex for machines, and says makes a robot somewhat self-aware of its surroundings.
• In the Sound of Science project, Siemens simulation captures the acoustic properties of venues such as St.
• Peter's Basilica and concert halls in Bavaria.
• Ziegler explains that conductors plan concerts around reflections, resonance and dead zones, then repeats a parallel drawn by Cedrik Neike between conducting an orchestra and orchestrating a factory.
• The acoustics post sits outside manufacturing operations but broadens the subject range, using the same approach: take an engineering capability and show what it changes in a real setting.

Read original · Original 2 · Original 3

See how Ziegler connects a headline performance result to the way the system is built and deployed.

Ziegler explains how Siemens’ SINUMERIK Machine Tool Robot sits between a large machine tool and a conventional industrial robot.

• They cite a customer example: steel machining that took 40 minutes with a standard robot took 5 minutes with the MTR.
• They also explain the system’s partner-built mechanics and Siemens control components, as well as the machine builder’s role in integration and commissioning.
• The post makes the product’s operating model as concrete as its speed claim.

For brands planning a campaign

For a robotics newsletter collaboration, this is a strong starting point for a piece about large-part machining: it pairs a specific result with the practical system and integration context manufacturing readers need. Substantiate the stated customer result before reusing it in campaign claims.

It offers newcomers a practical look at how this setup differs from a conventional robot cell.

After visiting Siemens’ Chemnitz plant, Ziegler describes a robot whose kinematics run inside the CNC rather than through a separate robot controller.

• That lets machinists program it with G-code, a familiar machine-tool language.
• They link this setup to path control, vibration compensation, and applications such as machining large aerospace or energy components, where moving the machining system to the workpiece can be useful.

For brands planning a campaign

This supports a technically focused newsletter feature on how CNC and robotics converge, especially for readers who already know machining. A campaign should explain the programming and application fit rather than lead with a broad claim that robots are easier to use.

See the showcase workflow and the integration question that matters beyond a single-vendor demonstration.

Using an aerospace showcase at the Siemens booth at AMB, Ziegler follows two parts through a production chain: an oil pump redesigned with AI-driven engineering and simulation, and a turbine blade used to illustrate machining accuracy and throughput.

• They name the software and production stages, from NX design and Teamcenter planning through CNC programming, digital-twin verification, machining, and predictive maintenance.
• They distinguish HELLER’s machine tools from Siemens’ control and software layer, then note that real factories often combine vendors.

For brands planning a campaign

This example suits a newsletter collaboration about connecting design, planning, machining, and monitoring. Its mixed-vendor focus gives a campaign a useful question to explore: how does the proposed digital thread work with equipment and systems already in a plant?

See the concept and the demonstration’s stated limits before assessing claims about factory readiness.

Ziegler describes a Siemens booth demonstration in which robots pick different cloths and place them into bags.

• They introduce visual language action models, which combine vision, language, and actions, and explain why handling varied objects is difficult.
• They frame adaptive production as a longer-term possibility and say Siemens is testing the approach in production environments.
• The post also notes that the demonstration is slow and the work is at an early stage.

For brands planning a campaign

This could anchor an exploratory newsletter item on physical AI, but the campaign should distinguish the demonstrated task and ongoing tests from mature, broadly deployed capability. The post acknowledges the speed and early-stage status, helping set reader expectations.

See how they use a concrete example from a creative field and judge whether that explanatory style suits a broader audience.

Ziegler describes Siemens’ “Sound of Science” project, which uses simulation to capture acoustic properties of venues such as St.

• Peter’s Basilica and concert halls.
• They explain why that matters to conductors: anticipating reflections, resonance, and dead zones can inform orchestra positioning.
• They then draw a parallel between coordinating an orchestra and coordinating a factory.
• This takes simulation outside the factory and makes it understandable through a sensory, cultural application.

For brands planning a campaign

For a robotics newsletter, this is a less direct fit than the machining and CNC posts, but it could support a broader story about simulation or industrial technology in unexpected settings. Use it when a campaign needs an accessible analogy, not as evidence of robotics expertise.

The aerospace showcase follows a digital thread from AI-powered design in NX through Teamcenter, NX CAM Copilot, digital-twin verification, HELLER machine tools running SINUMERIK One, and Senseye Predictive Maintenance.

• A separate post describes the SINUMERIK Machine Tool Robot, with robot kinematics running inside the CNC so machinists can program it in G-code.
• The material repeatedly distinguishes machine builders from control and software suppliers, helping brands see where a component or platform fits in a mixed-vendor line.

Walks through sequences and labels each layer: design, planning, programming, verification, machining, and maintenance. Uses named systems and roles rather than generic capability claims.

For brands planning a campaign

Useful for a vendor selling into a multi-vendor manufacturing stack that needs an explainer showing where its product fits alongside machine builders, controllers, and software. A campaign should supply named components, integration points, and at least one concrete production metric; the posts show how much the format depends on those specifics.

Examples: Source 1 · Source 2 · Source 3

The posts cover booth demonstrations, plant-floor demonstrations, and conversations with Siemens staff.

• In one, they interview Umberto Neuwerth about the SINUMERIK Machine Tool Robot and cite a customer example where robotic steel machining dropped from 40 minutes to 5.
• In another, they meet Matthias Schulz at Hannover Messe to discuss physical AI on production floors.
• The reporting focuses on what they saw and heard, not on a product datasheet.

First-person visit reporting with quotes from named Siemens people and details from live demonstrations.

For brands planning a campaign

A vendor with an event presence or a customer-accessible plant can use this approach for a walkthrough that feels observed rather than scripted. The campaign needs access to a real demo, a named technical spokesperson, and permission to report a specific application or result.

Examples: Source 1 · Source 2 · Source 3

The aerospace digital-thread post notes that real manufacturing environments are rarely single-vendor and that a digital thread's value depends on how well it works in mixed environments.

• The Machine Tool Robot post explains that Siemens does not build the robot mechanics; mechanical partners build them with Siemens motors, and a system integrator or machine builder commissions the full system.
• The physical AI post says the demonstrated robot task is slow but previously impossible, and is being tested in real production rather than only lab demos.

For brands planning a campaign

Effective for a vendor that wants to address adoption friction openly.

• Campaign material should include integration responsibilities, current limitations, and what is already running in production.
• The format rewards vendors willing to name partners and constraints.

Examples: Source 1 · Source 2 · Source 3

AI-assisted CNC programming, AI-driven design, and predictive maintenance sit inside a digital thread.

• Physical AI is shown picking cloths and placing them into bags using visual language action models, with the argument that flexible manufacturing can reconfigure around product mix without reprogramming.
• A non-factory post uses Siemens simulation to capture the acoustics of historic venues, then draws a parallel between conducting an orchestra and orchestrating a factory.

An acoustics post extends the subject beyond factory equipment, using a musical metaphor.

For brands planning a campaign

A vendor with an AI or simulation product can pitch a story about what the technology does on a real line or in a real process.

• The strongest angle is a before-and-after task, cycle-time, or quality problem, not a general AI narrative.
• The acoustics example shows they will also cover a creative or public-facing simulation application if it has a clear analogy to industrial orchestration.

Examples: Source 1 · Source 2 · Source 3

The posts are short, scannable explanations: a hook, a concrete example, a named system or person, and a closing news or event link. Hashtags include #SiemensPartner with #Sponsored or #sponsored.

For brands planning a campaign

A brand can evaluate the format as a sponsored explainer that points to a newsletter.

• The posts disclose the relationship with hashtags; a campaign should follow that practice.
• Because every post includes a newsletter call to action, the collaboration would need to account for a robotics newsletter audience, not only a single LinkedIn post.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Ziegler reports from a Siemens plant visit in Chemnitz, the Siemens booth at AMB in Stuttgart, Hannover Messe and Transform UK.

• The posts read as sponsored field reporting rather than advertising copy: they name Siemens staff (Umberto Neuwerth on the SINUMERIK Machine Tool Robot, Matthias Schulz on physical AI, Cedrik Neike on simulation acoustics), walk through products such as NX, Teamcenter, NX CAM Copilot, SINUMERIK One and Senseye, and give technical detail, numbers and trade-offs.
• The AMB aerospace post also notes the division of labour in the showcase, with HELLER building the machine tool and Siemens supplying the control and software layer.

Original disclosure

#SiemensPartner #Sponsored (posts vary between #SiemensPartner, #sponsored and [Ad])

View example

Ziegler promotes it from their own account, and it is hosted on a subdomain carrying this name.

View example

Both connect trade-fair demonstrations to their implications for production, naming technologies such as MES, OEE and physical AI rather than speaking in general trends.

Vieira writes from inside a technology-services provider, framing stories around client outcomes, the company’s booth and their own leadership role, including representing Marco Stefanini at the Brazilian pavilion opening. Ziegler reports from outside a vendor’s business, explaining which partner supplies each layer of its equipment and software rather than writing about running the business.

Read original · Original 2

The overlap with Ziegler’s coverage is direct: shop-floor protocols, robot software and digital twins.

M. is a builder who shares open-source engineering work and library-level decisions, with code showing the work. Ziegler reports on systems companies have already deployed, interviewing the people who run them and explaining adoption tradeoffs rather than implementation choices.

Read original · Original 2

Both treat robotics adoption as a production-floor question and anchor posts in named visits and events.

Tohumcu’s posts sit at the cloud-platform and enterprise-transformation level, framing market forecasts, cost-reduction figures and partner strategy for executives and boards. Ziegler focuses on the machine: control architecture, programming language, path accuracy and who commissions the system.

Read original · Original 2

In a Hannover Messe reflection, the post connects Physical AI to an earlier warehouse-inventory drone project and notes recurring client interest in MES and OEE.

• A shorter post about the Brazilian pavilion sets the event in a digital-manufacturing context.
• The material is a better fit for a business-level transformation story than a detailed demonstration of CNC-integrated robotics.

The examples frame technology through client challenges, event activity, and digital transformation; they do not explain a machine-tool robot’s programming, accuracy, or machining process. A campaign needing engineering detail about a robot cell would find stronger evidence in their technical demonstrations.

Examples: Source 1 · Source 2

The project overview describes C# tools for EtherNet/IP, ROS, simulation, and digital twins.

• In a digital-twin experiment, an ONNX walking policy trained in MuJoCo runs in PhysX through Gemelli Studio; the post notes that matching the policy’s conventions took work.
• This integration example is more useful than a product overview when buyers need to assess developer access and interoperability.

The posts focus on the creator’s own projects and an open, composable software approach, not sponsored vendor demonstrations or machine-tool performance. They suit engineering audiences interested in interfaces and implementation better than plant executives or buyers seeking customer outcomes.

Examples: Source 1 · Source 2

The Japan and Nagoya takeaways discuss product priorities, software-defined vehicle architecture, compute constraints, and AI-partner decisions.

• Separately, the VivaTech post reports a panel discussion on AI in industrial supply chains and gives cost-reduction and forecast-accuracy figures.
• Together, the posts offer a strategic narrative, not a technical account of how a robot cell works.

The material takes a corporate, strategic view from a cloud provider’s perspective rather than offering a close technical demonstration of automation hardware. It is a stronger editorial match for senior transformation buyers than for machining engineers evaluating a CNC-integrated robot.

Examples: Source 1 · Source 2