BaSyx / Glossary
|(technical) functionality||services of the I4.0 component that create the added value of an object|| The (technical) functionality is part of the administration shell.
The (technical) functionality can be located in the functional layer or in the integration layer of the RAMI 4.0. The technical functionality is the sum of all skills
|architecture||combination of elements of a model based on principles and rules for the purpose of its construction, development and utilization|
|asset||entity which is owned by or under the custodial duties of an organization, having either a perceived or actual value to the organization|
|Asset Administration Shell (AAS)||virtual digital and active representation of an I4.0 component in a I4.0 system|
|attribute||representation, in information technology, of a property|
|changeability||characteristic of an item, to adopt it with little effort to changes which were NOT known during planning|
|communication behavior||specific manifestation of communications||Examples: synchronous/asynchronous, acknowledged/not acknowledged/with reply, deterministic/non-deterministic, stateful/stateless, unicast/multicast/broadcast|
|communication channel||connection between a transmitter/sender and recipient/receiver which allows the exchange of information|
|component manager||organizer of self-management and of access to the resources of the I4.0 component, for example, I4.0 component, item, technical functionality, virtual representation Note: In many documents, component manager is referred to as resource manager, but the term component manager should be used in future.|
|core model||reference model of basic concepts and contexts which concern a general aspect of systems|
|cyber physical production system (CPPS)||CPS which is used in production|
|cyber physical system (CPS)||system which links real (physical) objects and processes with information-processing (virtual) objects and processes via open, in some cases global, and constantly interconnected information networks||A CPS optionally uses services available locally or remotely, has human-machine interfaces, and offers the possibility of dynamic adaptation of the system at runtime.|
|deployment view||structural mapping of applications to resources||Practical example is the distribution of the contents of an administration shell across different IT systems.|
|digital twin|| Definition 1: Virtual digital representation of physical assets.
Definition 2: Simulation model || In future, the digital twin will be a synonym for the asset administration shell if the development will continue as before. In the context of Industrie 4.0, the term asset administration shell is preferred.
|ecosystem||loose community of various autonomous players connected in a network with a common goal of creating products and/or services based on a (standardized) communication and system infrastructure|| Players can be participants of the value-added system as well as educational or research institutions, political units, standardization organisations or associations.
Within an ecosystem, players can be engaged at the same time both in cooperation and in competition. n ecosystem is characterized by a common further development (co-evolution) of the players and the ecosystem
|event||sudden change that can be observed||An event can trigger a state transition in a state model.|
|flexibility||characteristic of an item, to adopt it with little effort to changes which were known during planning|
|horizontal integration||integration within a functional/organizational hierarchical level across system boundaries|
|horizontal interaction||interaction within a functional/organizational hierarchy level across system boundaries|
|human-machine interaction||collaboration between users and technology, such as computers, machines or CPS|| Implemented by human- and task-oriented technical systems at the interface between users and technology.
Includes the analysis, design and evaluation of such systems. Collaboration synonymous to interaction
|I4.0 component||globally uniquely identifiable participant with communication capability consisting of administration shell and asset (corresponds to CP24, CP34 or CP44) within an I4.0 system which there offers services with defined QoS (quality of service) characteristics|| For its services and data, the I4.0 component offers protection commensurate with the task.
An I4.0 component can represent a production system, a single machine or station, or even an assembly within a machine.
|I4.0 platform||implementation of a (standardized) communication and system infrastructure with the necessary management and production services and defined QoS (quality of service) characteristics as a basis for the efficient construction and integration of I4.0 systems in an application domain|| To ensure interoperability, an I4.0 platform must be based on a reference architecture.
An I4.0 platform must define a relation to the I4.0 system.
|I4.0 system||system, consisting of I4.0 components and components of a lower CP classification, which serves a specific purpose, has defined properties, and supports standardized services and states|| A system may be present as a component in a further I4.0 system.
An I4.0 system must define a relation to the I4.0 platform. Flexibility, transformability, etc. are features of an I4.0 system
|interface||defined connection point of a functional unit which can be connected to other functional units|| “Defined” means that the requirements and the assured properties of this connection point are described.
The connection between the interfaces of function units is also called an interface. In an information system, the defined exchange of information takes place at this point. An interface places certain requirements on the connection that is to be made. An interface demands certain features.
|interoperability||ability of different components, systems, technologies, or organizations to actively work together for a specific purpose||Interoperation is collaboration put into practice.|
|lifecycle||continuous number of processes which an item passes from creation to dissolution|
|manifest||externally accessible defined set of meta-information, which provides information about the functional and non-functional properties of the I4.0 component||The manifest can be regarded as similar to the manifest in computer science.|
|Middleware||Software that provides services to software applications beyond those available from the operating system.|
|model||coherent, sufficiently detailed abstraction of aspects within a field of application|
|non-functional requirement||requirement that does not belong to the actual system function||Examples: availability, performance, usability, compatibility, maintainability, security …|
|orchestration of services||flexible connection of individual services for a defined purpose||This can be done during the planning phase and/or at runtime.|
|physical world||the totality of all actually existing items and individuals|| The real world corresponds to the physical world.
Software loaded or in memory is part of the physical world. The frame of reference of the totality in question must be defined.
|plug & work||setting up, modification or termination of interoperation between two or more involved parties with minimal effort|| The interoperability of those involved is assumed.
The minimum effort can vary depending on the state of the art. Plug & play and plug & produce are synonyms or similar terms.
|process||entirety of procedures in a system by means of which the material, energy or information is transformed, transported or stored|
|Quality of Service (QoS)||Performance of end-to-end communication between different partners|
|reference architecture||model for a description of the architecture (for I4.0) which is used generally and is recognized as appropriate (with the character of a reference)||A reference architecture can be defined on the basis of a reference model.|
|requirement||specification of required criteria||The system can fulfill the required criteria step-by-step, if necessary.|
|service||demarcated scope of functionality which is offered by an entity or organization via interfaces||One or multiple operations can be assigned to one service|
|service consumer||entity or organization that consumes the service of a provider|
|service orientation||paradigm which enables the straightforward exchange, addition or removal of loosely coupled services|
|service provider||entity or organization that provides a service||An entity or an organization can be a consumer and a provider (both at the same time).|
|skill of an I4.0 component||potential of an Industrie 4.0 component to achieve an effect within a domain|| Skill can be orchestrated and hierarchically structured.
Capability is often used as synonym to skill. Skills can be made executable via services. The impact manifests in a measurable effect within the physical world.
|smart product||produced or manufactured (intermediate) product which in a smart factory delivers the (outward) communication capability to network and to interact intelligently with other production participants|| The product is a produced or manufactured article or semi-finished product.
A digital image is part of the product intelligence and can be localized on the product itself but also spatially separate from it. Unique identification and product-related information makes it possible for the product to be linked to the smart factory.
|Software Development Kit (SDK)||a set of software development tools that allows the creation of applications for a certain software framework, hardware platform, or similar development platform.|
|state||manifestation of the characteristics of an object at a certain point in time|| An object can only have one state at any point in time.
Statements about a state can be made without any specific reference to a time.
|submodels||Separate parts of the AAS concerning the description and structure of certain aspects of the asset||Submodel examples: Topology, geometry, power consumption|
|timeliness||temporal correctness that has yet to be specified in detail||Response must be given to events at precisely defined times or events must be triggered at defined times, e. g. not before, not after, or within a specified time interval|
|type||descriptive entity that is characterized by a quantity of common properties and their type|
|validation||examination/testing of described/defined requirements for a predefined application or use||A product fulfills the requirements of the customer, i. e. examination according to the customer requirement specifications was successful.|
|value added chain||sequence of value-creation processes (linear or hierarchical, formally this means directed acyclically)||Corporate boundaries are not necessarily relevant to a value-creation chain or value chain.|
|value added process||process from which goods valuable to customers arise|
|value added system||network or system consisting of value-creation chains or value chains which can include not only cross-connections but also dependencies between them|| The goods in question may be not only physical in nature (such as raw materials, products) but even intangible (such as knowledge, data, services).
Value assessment and pricing are not considered here.
|verification||examination/testing of the requirements described/defined in the specifications||A product fulfills the specifications, i.e. examination according to the functional requirement specifications was successful.|
|vertical integration||integration within a system which crosses functional/ organizational hierarchy levels|
|vertical interaction||interaction within a system across functional/organizational hierarchy levels|
|virtual representation||digital models of the I4.0 component throughout the entire life cycle|| The virtual representation is part of the administration shell.
The virtual representation can be located in the information layer or in the integration layer of the RAMI4.0. The manifest is part of the virtual representation.
|BaSyx project links: Project BaSyx main wiki page | What is BaSyx? | BaSyx Developer Documentation|