In the smartfoundry.community, many foundries contribute to ongoing development. Development costs are shared across customers. Experience from everyday production helps improve applications and develop new solutions. Those who also wish to join shared data projects decide voluntarily on their contribution and the agreed use. Members can learn from one another and develop their foundries together.
Community Applications let you investigate questions that the data from your own foundry alone cannot answer. Participating companies provide selected data under jointly agreed conditions. This can lead, for example, to comparisons, analyses or new assistance functions.
For each application, you decide whether to participate and which data to contribute. Purpose, access and use of results are defined in advance. Your other data remains in your private instances.
A pump failure or wear in a component may occur only rarely on an individual machine. Developing reliable condition models, however, requires many traceable observations, including the conditions before and during a fault.
A fleet of comparable machines provides more such cases under real production conditions. Shared measurements and confirmed fault patterns help investigate typical changes and develop and validate models with or without AI.
How does your foundry compare with similar operations in productivity, availability or energy consumption? Agreed KPIs and suitable peer groups can help assess your performance and identify opportunities for improvement.
For a meaningful comparison, factors such as machine types, production conditions and calculation methods must be comparable. Automatically collected data can reduce the effort required for recurring comparisons.
You know the tasks your employees face every day. Contribute this experience and your ideas for new functions and applications. Together, we can prioritise topics that benefit several foundries.
Customers already share the cost of ongoing development through the subscription model. You decide whether to make an additional contribution to specific development projects. Scope, contribution and usage rights are agreed separately.
Machine, tool and component manufacturers can also learn from selected operating data, for example to improve their products. If you contribute data or expertise, a return for your contribution can be agreed.
This may include financial compensation, additional services or other benefits. You decide whether to participate and which data may be used for which purpose under a specific agreement.
Developing complex models generally requires large volumes of data and many event observations. These can often only be collected to a limited extent within your own production. A shared fleet extends the data foundation with observations from many operations.
Example: For a pump failure model, we want to collect 30 documented events. With one machine, this can take a very long time. Across a fleet, these observations are made in parallel.
Move the slider to see how the shared data foundation grows.
100 comparable machines collect the expected number of events 100 times as quickly. This provides an earlier foundation for development and validation.
Progress after one year · Example target: 30 documented events
100 machines · One relevant event per pump every 4 years on average · Example target: 30 events
The event interval and collection target are freely chosen example values. The target is neither a general minimum requirement nor proof of a deployable model. The calculation shows expected quantities, not predictions of individual failures.
Customer data is not shared by default. Your own smartfoundry solution can be used independently of participation in Community Applications or joint development projects.
Each customer uses one or more private instances. Data from different customers is neither mixed nor combined by default. A shared data foundation is created exclusively for explicitly agreed Community Applications.
Through the subscription model, all customers contribute to ongoing development. This shared funding is already part of the solution model and does not require you to release your own production data.
Specific Community Applications use selected datasets that have been explicitly approved for sharing. Focused terms define purpose, data scope and access for each application. You can weigh benefits and risks and decide whether to participate and which data to release.
Participation in specific joint development projects is also your decision. Contributions, participation and use of results are governed by agreed usage contracts. You choose the project and form of participation that suit your company.
Let us discuss a suitable community project, the data required and your potential contribution.