5 Use cases
The use cases defined below are applicable to one or more roles in each factory or plant. Examples: Service technician, plant manager, quality engineer, machine integrator, factory planner, IT manager, etc.
5.1 Asset Management
| Name | Asset Management – Overview of System, Identification and Lifecycle Management of Assets. |
| Objective | To provide detailed information about the different assets in a system. It includes a standard organized way of accessing the list of assets from a given system. |
| Description | Joining System can contain multiple assets. For each asset in the joining system, it allows: get a list of assets in standard way from a given system. receive a unique identification of the asset. receive a standardized base identification information of the asset like serial number, manufacturer, product code, and revision information, etc. set and receive specific identification information that is tailored to the needs, like a user-specific name or identification. |
5.2 Condition Monitoring
| Name | Condition Monitoring – Health and Maintenance information of the asset. |
| Objective | To provide regular or permanent recording of the machine condition by measuring and analyzing physical quantities and other parameters. |
| Description | For each asset in the joining system, it allows to get the condition and health information like temperature, power on duration, error, service, calibration, etc. |
5.3 Result Management
| Name | Result Management – Standard result structure and interface to access the result data. |
| Objective | To provide standard content for result and standard methods, events, to access the result from a given system. |
| Description | For every operation in the joining system, the result information: provides a standard and flexible result model across various joining technologies and other domains. allows to get the process values in different levels of detail. This starts at the basic level with OK / NOT_OK up to values of each step and traces. provides a standard interface to access the result data. allows structured results from a joining system such as Single, Batch, Sync, Job, etc. |
5.4 Event Management
| Name | Event Management |
| Objective | To provide various system events and conditions in a standard way. |
| Description | The joining system allows: to send events or a condition with the standard payload. to filter based on the respective use case. to acknowledge the respective conditions. |
5.5 Joint Management
| Name | Joint Management |
| Objective | To manage the joint information in a standard way. |
| Description | The joining systems allows: to select a joint to perform the respective joining operation. to include the joint identifier in the results. to exchange the joint information between the joining system and external system. |
5.6 Joining Process Management
| Name | Joining Process Management |
| Objective | To manage the joining process in a standard way. |
| Description | The joining system allows: to perform the joining operations using standard set of methods to manage a joining process for use cases such as: single joining operation comprehensive joining process with sub-process(es) Examples: Batch Process, Synchronized Process, Job to exchange the joining process between joining system and external system. |