Use cases

Requirements

Use Case: Operator Controls Printing Press USE_1
style: purple_bar

The operator wants to control the printing press

Use Case: Operator Monitors Printing Press USE_2
style: purple_bar

The operator wants to monitor the printing press

Use Case: Connectivity to Customer's Infrastructure USE_3
style: purple_bar

The owner/buyer/service personnel wants to connect the HMI/SCADA system to the customer’s infrastructure

Use Case: Job Management USE_4
style: purple_bar

The operator wants to manage print jobs (create, store, load, edit)

Use Case: Service Technician Configures System USE_5
style: purple_bar

The service technician wants to configure the system settings for the printing press.

This includes tasks such as but not limited to:
  1. Configure the connection to the PLC

  2. Configure the connection to external systems (e.g. MIS, ERP)

  3. Configure user management and roles

  4. Configure system settings (e.g. language, units)

  5. Configure alarms and notifications

  6. Configure data logging and reporting

  7. Configure network settings

  8. Configure backup and restore settings

  9. Configure database settings

  10. Configure press specific settings (e.g. print speed, ink settings, wash settings)

Use Case: PressCenter Supports Multiple Manufacturers USE_6
style: purple_bar

The PressCenter is not limited to one specific printing press manufacturer. It shall be possible to connect different printing presses from different manufacturers. This can be achieved by using standard protocols (e.g. OPC UA, MQTT, ADS) or by using custom drivers.

Use Case: PressCenter Runs on Different Hardware USE_7
style: purple_bar

The PressCenter shall be able to run on different hardware platforms.

This includes but is not limited to:
  1. Industrial PCs

  2. Embedded systems

  3. Virtual machines

  4. Cloud platforms

The system requirements shall be documented and provided to the user.

Use Case: PressCenter is Extensible USE_8
style: purple_bar

The PressCenter shall be extensible to allow for future enhancements and features.

This includes but is not limited to:
  1. Adding new protocols (e.g. OPC UA, MQTT, ADS)

  2. Adding new features (e.g. job management, reporting)

  3. Adding new hardware support (e.g. new PLCs, new HMI devices)

The system architecture shall be designed to allow for easy extensibility.

Use Case: PressCenter is Secure USE_9
style: purple_bar

The PressCenter shall be designed with security in mind to protect against unauthorized access and data breaches.

Use Case: PressCenter is Reliable USE_10
style: purple_bar

The PressCenter shall be designed to be reliable and robust to minimize downtime and ensure continuous operation.

This includes but is not limited to:
  1. Implementing error handling and recovery mechanisms

  2. Implementing redundancy and failover mechanisms

  3. Implementing monitoring and alerting mechanisms

Use Case: PressCenter is User-Friendly USE_11
style: purple_bar

The PressCenter shall be designed to be user-friendly and intuitive to minimize the learning curve for new users.

This includes but is not limited to:
  1. Implementing a modern and responsive user interface

  2. Implementing user roles and permissions

  3. Implementing user documentation and training materials

Use Case: PressCenter Supports multiple Production line configurations USE_12
style: purple_bar

The PressCenter shall be able to support different production line configurations.

This includes but is not limited to:
  1. Different number of printing units

  2. With or without coater

  3. With or without dryer

  4. With or without feeder

  5. With or without stacker

The system architecture shall be designed to allow for easy configuration of different production line setups.

If a system is not part of the configuration it can be still part of the actual maschine but is not controlled or monitored by the PressCenter.

Use Case: PressCenter Supports multiple Languages USE_13
style: purple_bar

The PressCenter shall support multiple languages to accommodate users from different regions.

This includes but is not limited to:
  1. English

  2. German

  3. French

  4. Spanish

  5. Italian

Use Case: PressCenter Supports different User Roles USE_14
style: purple_bar

The PressCenter shall support different user roles to accommodate different levels of access and permissions.

This includes but is not limited to:
  1. Operator

  2. Service Technician

  3. Administrator

  4. Guest

Each user role shall have different access and permissions to the system.

Use Case: PressCenter Supports different Screen Resolutions USE_15
style: purple_bar

The PressCenter shall support different screen resolutions to accommodate different display devices.

This includes but is not limited to:
  1. 1920x1080 (Full HD)

  2. 2560x1440 (QHD)

  3. 3840x2160 (4K UHD)

  4. 1280x720 (HD)

The user interface shall be responsive and adapt to the available screen resolution.

Use Case: PressCenter Supports different Operating Systems USE_16
style: purple_bar

The PressCenter shall support different operating systems to accommodate different user preferences and requirements.

This includes but is not limited to:
  1. Windows

  2. Linux

  3. macOS

The system requirements shall be documented and provided to the user.

Use Case: Touchscreen Support USE_17
style: purple_bar

The PressCenter shall support touchscreen input to accommodate modern HMI devices.

This includes but is not limited to:
  1. Touchscreen monitors

The user interface shall be designed to be touch-friendly and responsive to touch input.

Use Case: The operator wants to control and monitor the Press on the first print unit USE_18
style: purple_bar

The operator wants to control and monitor the printing press on the first print unit.

This includes but is not limited to:
  1. Start/Stop the press

  2. Monitor press status

  3. Adjust press settings (e.g. print speed)

  4. View alarms and notifications

  5. Start/Stop feeder drives

  6. Control the suction head system

  7. Control the suction conveyor system

The user interface shall be designed to be user-friendly and intuitive to minimize the learning curve for new users.