checked up on! - with Bart Nieuwborg, Rockwell
Margo - Orchestrating the Edge
In April 2024, the Linux Foundation launched the "Margo" initiative with the goal of defining and implementing mechanisms for the interoperable orchestration of edge applications at scale. Bart Nieuwborg, Senior Program Manager, Open Architecture Management and Chair of Margo at Rockwell Automation, on the status quo.
Which specific milestones, particularly in the development of the first Margo version, the reference implementation, and a minimum viable product, have already been achieved?
As of April 2025, Margo has made significant progress and put in place a solid foundation for the first version of the deliverables. The community reached consensus on the underlying system design and published the pre-draft specification for this first version. Both are published and available to the public on GitHub and on www.margo.org.
Prototyping and regular meetups between domain experts allowed the community to mature the concepts.
How far along is the deployment of the compliance testing toolkit, and what challenges have arisen in the process?
The compliance testing toolkit will be a natural evolution of the reference implementation activities and is targeted to become available once the first version reaches the general availability milestone (GA 1.0). The community has not yet tackled the development of the compliance testing toolkit. The priority for 2025 is to build iterations of the reference implementation, aligned the envisioned first release of the specification.
How does Margo integrate modern security concepts and measures to ensure cybersecurity and data integrity?
While Margo's core mission centers on interoperability, cybersecurity, and data integrity are key principles for the community. The open standard and open-source nature of Margo were also deliberately chosen to allow anyone interested to share security best practices with the community. During our first year of operations, we have already seen the positive impact from this approach. Security experts joined the Margo community and shared guidance to improve the system design. We have a dedicated security focus group in the technical community to foster cybersecure design.
What specific steps have been taken to avoid overlaps with other standards, app stores, or consortia, and instead create complements?
Three keywords: openness, focus, and collaboration.
The Margo community is transparent in what it does. Everyone can have a look, contribute, enhance. And at the same time the scope is very focused. Margo does not envision to address all interoperability challenges, but focuses on the interoperable orchestration at the edge, for the industrial automation market. The founding members felt that this specific interoperability area was not yet addressed. So far, we have seen little to no overlap with other initiatives but rather seen positive reactions confirming the Margo specification being complementary. Where appropriate, we collaborate with related organizations or initiatives, and leverage already developed open-source solutions where possible.
To what extent has the Margo project gained new members or partners, and what impact does this have on project development?
Since its inception in April 2024, the Margo initiative quadrupled its member community from the 6 founding members. We now have a healthy mix of steering members (10) and contributing members, each with diverse backgrounds and profiles representing the ecosystem, from small to multinational suppliers, from IT to OT profiles, with software, hardware and services background.
The inclusion of these new members has positively influenced Margo's development. The technical expertise has increased significantly, and with the broadened representation of the ecosystem we are paving the way for accelerating the adoption of Margo in commercial offerings.
How does Margo plan to transition from the current development phase to a widely adopted standard in industrial automation?
The reference implementation and the compliance testing toolkit are 2 important pillars of this transition. They will lower the barriers for future adopters to embed the Margo standard in their commercial offerings. The open-source nature of these 2 deliverables will be instrumental to support a wide adoption.
But there is more. Margo will also actively seek feedback from the users of Margo enabled solutions: Industrial manufacturers, machine builders, all the personas that will be faced in the future with the challenge of managing a fleet of devices and applications in industrial manufacturing. On a quarterly basis, Margo will bring together experts from various users to collect advice on intended direction and priorities and support motivated users with pilot projects proving out the value Margo’s interoperability standard.
What is your perspective on the long-term role of Margo in the context of digitalization and Industry 4.0, and what strategic goals are being pursued to meet the growing challenges?
Digitalization is happening today in industrial automation and will accelerate as industrial manufacturers are trending towards software defined, autonomous plants. At the same time, managing the exponentially growing installed base of software and associated edge devices in their plants is a new challenge, and potentially a barrier for innovation. Margo’s mission is to remove this barrier through enabling interoperable orchestration of these fleets, so that users can continue choosing best-in-breed solutions in a multi-vendor ecosystem. Combining this freedom of choice with the ability to manage their fleets at scale in an automated fashion will continue to foster innovation and move towards more autonomous, adaptive and agile systems.












