The BaSyx open source platform puts a focus on enabling Industrie 4.0 scenarios. Currently, we focus on the following scenarios:
- Service based production
- Service based production is a core concept of the BaSys 4.0 project. Today, PLC controllers control the production by running cyclic programs. Changing a production consequently implies the changing of PLC programs on all affected controllers. As PLC controllers are programmed in low-level languages, such as structured text, this task is both time- and effort consuming and requires the involvement of specialists. This considerably limits changeability. BaSys 4.0 realizes a service based production. PLC controllers still implement the real-time production steps but provide them via re-useable, callable services with a defined interface. The overall process control is handled by a process control component that controls invocation of these services. At the process level, real-time is no longer essential, allowing the service orchestrator to be deployed to an industrial PC. This allows an easier reprogramming using e.g. scripting or BPMN engines. This way, rapid changing of production processes is possible by changing service orchestration and service parameters. Updating of PLC is only necessary when implementing new services.
- End-to-end communication
- End-to-End communication enables direct communication between different layers of the automation pyramid. Currently, a variety of communication technologies and protocols makes the communication across layers of the automation pyramid difficult. BaSyx mitigates this with a virtual automation bus that defines abstract communication primitives. BaSyx gateways map these abstract primitives to concrete protocol operations and enable an end-to-end communication across protocol and technology borders.
- Asset Administration Shells
- Asset Administration Shells (AAS) are digital objects that enable access to information, properties, and services via a defined interface. All relevant Industrie 4.0 entities, for example products, workers, devices, and plants have an Asset Administration Shell. An AAS defines core properties, such as a unique ID and version number that identifies an AAS, as well as a list of sub models. AAS sub models contain properties and operations that depend on the sub model type. Different sub model providers enable provisioning of different input data as AAS sub models.
- Defined sub model types
- Defined sub model types define meta models (which define how to structure data) for commonly used sub models.
- Registry and Discovery service
- The registry and discovery service is used to find relevant assets like devices, products and workers in factories. The technical means to achieve that is by storing the AAS of these assets in the AAS registry. The registry enables AAS to register themselves and the looking up of a specific AAS by Industrie 4.0 components that are looking for an AAS.
|BaSyx project links: Project BaSyx main wiki page | What is BaSyx? | BaSyx Developer Documentation|