The Open Manufacturing Platform (OMP) is a global alliance helping manufacturing companies accelerate innovation at scale through cross-industry collaboration, knowledge and data sharing, and access to new technologies. Founded in 2019 under the umbrella of the Linux Foundation, OMP brings together business leaders and technologists from manufacturing companies, solutions providers, systems integrators, independent software providers, and more to solve common but complex and critical challenges.
The goal of the OMP is to bring forward platform-agnostic solutions, open standards and technologies to enable smart manufacturing, break down data silos, and solve real problems across the industry—regardless of technology, solution provider, or cloud platform. The OMP provides community members with a reference architecture with open source components based on open industrial standards. The approach is designed to standardize industrial data models to accelerate analytics and machine learning scenarios by unlocking access to data that was historically stored in proprietary systems. Through collaboration, knowledge and resource sharing, and the formulation of open standards and best practices—we aim to bring the OMP member alliance and community:
- Develop practical solutions that enable smarter manufacturing
- Collaborate for faster time-to-value
- Drive new efficiencies and reduce costs
The OMP prioritizes challenges that stall innovation across the manufacturing ecosystem. One example is the complexity of connecting manufacturing systems to a commercial cloud. Industrial IoT can enable predictive maintenance, better quality control, automation, and other important scenarios that enhance operational efficiency and output. However, some systems use proprietary protocols that don’t allow manufacturers to share data with other systems and gain holistic insights from the shop floor to the rest of the supply chain. OMP is helping manufacturers gain complete ownership and control of their own data and intellectual property (IP). Together, we implement new industry standards and evolve existing standards, develop open source reference architectures, common data models, and more.
Joining the OMP
We invite any organization throughout the manufacturing value chain that shares the values and principles of the OMP, and that believes one of the best ways to accelerate innovation is through the power of collaboration—designing, building, and sharing solutions to common problems together.
- Openness – open and interoperable platforms and processes, work products that can be implemented on any cloud platform or underlying technology, openly published results, a neutral independent legal entity
- Ability to execute – focused on solving real-world challenges in production (getting out of proof of concept purgatory), engineer-driven
- Focused on manufacturing and the industry’s end-to-end value chain
- Diversity – geo-diversity and sub-segment diversity from process to discrete manufacturing
- Visit open-manufacturing.org and click the Get Involved link in the navigation. You may choose from several options:
- Join the community at no cost to stay up-to-date on the OMP’s progress and innovations, contribute ideas, and use the output of the OMP’s working groups
- Apply to be part of the member alliance to work alongside leading manufacturers in working groups (members pay an annual membership fee)
All members are expected to:
- appropriately resource and constructively participate in working groups, and meet the minimum participation threshold as defined by their working group
- pay annual membership fees and meet obligations as defined by their member tier
Members from all tiers are eligible to participate and contribute to working groups, propose working group priorities, and contribute and consume output. Steering Committee and Associate memberships are by invitation-only and applications must be approved by the Steering Committee.
|OMP Member Alliance|
|Use the output of working groups|
|Stay up-to-date on OMP progress & innovations|
|Contribute to working groups|
|Propose new working groups|
|Influence working group solutions and outcomes|
|Participate in working group governance|
|Approve new working groups|
|Participate in OMP governance|
|Approve new Steering or Associate members|
|Steering Committee||Sept 2020||$60K|
Funds are used for ongoing support including maintaining non-profit status, administrative services, program management, marketing and legal support, and website maintenance.
The heart of the OMP is collaborative working groups. These small engineering groups focus on solving prioritized challenges, establish standards and best practices, and build solutions that can affect the entire value chain. Each working group is established via a charter that describes the scope and intellectual property terms used to develop the materials. Working groups use implementation frameworks, common data models and the principles of open development, including transparency and collaboration. Documentation and use cases are shared and available to everyone. We define and use a common data model aimed at breaking down data silos and overcoming the challenges of proprietary systems and vendor lock-in.
When a company becomes an OMP member and signs the agreement, they identify the working group they wish to participate in and sign the corresponding working group charter. Ad-hoc onboarding procedures may vary slightly, as determined by the respective working group.
Anyone may suggest a new working group, which is officially created if the following milestones are met:
- At least two participants are committed to contributing to the working group
- A Working Group Specification Document is completed and approved by at least two Steering Committee members
- Once approved, the Working Group Charter is completed and signed
The output varies depending on charter and problem being addressed. Examples Include:
- Code samples – managed through a shared repository and openly published; samples are detailed and structured in a way to demonstrate how to solve the problem with significant attention to quality, efficiency, and security; the code can be forked and used in proof-of-concepts, testing scenarios, or production-ready environments
- Production-ready code – deployable code that has been fully tested for quality, efficiency, and security; and determined by the working group to have met rigorous defined exit criteria
- Best practices – published as a whitepaper, this document includes a series of recommendations to optimally address a specific problem; each recommendation is accompanied by a justification, alternatives, and associated tradeoffs
- Specifications – published as a whitepaper, this document defines technical parameters used to solve a specific problem and is fed back to official standards organizations for consideration
- Architectural blueprints – diagrams and explanations demonstrating how different technological components fit together to provide a solution
All work products are openly published for anybody to review and use. Sample and production-ready code is published in a GitHub repository, the link for which is found on open-manufacturing.org along with whitepapers and other resources. All code is governed under open source IP rights.
Typically, projects will follow this process:
|1. Proposal||2. Incubation||3. Build||4. Production|
|Project ideas are submitted to the OMP Steering Committee for review. Anyone may submit an idea using the template. Proposals must have a well-defined scope and identify initial working group contributors and maintainers.||Approved projects go public and get a working group charter and applicable OMP workspace (e.g., GitHub, JIRA). The working group explores ideas and established specific work packages. The group starts to accept additional contributors at this stage.||Projects that successfully meet defined criteria enter the build phase. Criteria includes legal, test, support, documentation, infrastructure, and other requirements and considerations. A working model is put into practice and collaboration ramps up. Work packages are addressed by teams of engineers.||Projects that successfully meet defined release criteria enter the production phase. This includes fulfilling the project’s charter, adhering to best practices, completing a security audit if needed, earning approval from the OMP steering committee, and other requirements and considerations. Work packages are finalized and published. A maintenance plan is established and executed.|
The community members retain full control over their own data and IP. The IP generated by OMP members while working within an OMP working group is owned by the OMP legal entity and managed according to each working group’s pre-defined policy.