OnTakt: Settings: Difference between revisions

From Knowledge Base
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 8: Line 8:


=== Defining shift times ===
=== Defining shift times ===
Shift times are used to calculate daily goals for part production. If they are not set up correctly, daily goal lines will not be drawn or they will be drawn inaccurately. Shift times can also be overridden on a per-machine basis. Be sure the time zone (also available from the Options page) is set correctly '''before''' defining shift times. Once the time zone is set, click Save Changes before defining shift times.
See [[OnTakt: Shifts|Shifts]] to learn how to create shifts.
[[File:Screenshot 2024-07-02 at 8.37.53 AM.png|center|thumb|1112x1112px|Shifts page]]
 
[[File:Screenshot 2024-07-02 at 8.35.06 AM.png|center|thumb|336x336px|Shifts can be configured under the "Machines" module]]To set shift times:
#Click the drop down arrow located to the right of the "MACHINES" module, select "Shifts"
#In the bottom right hand corner, click the green "+NEW" button
#Configure the shift info (color, name, start and end time, days that the shift applies to, and whether the shift is unattended)
#Click on "Machines" and add the machines that adhere by those shifts. Clicking exit will save the settings.
[[File:Screenshot 2024-07-02 at 8.47.53 AM.png|center|thumb|1007x1007px|Shift window]]


=== Color timing ===
=== Color timing ===
Line 47: Line 39:
*To change a user's password: click the Edit button next to that user and enter a new password.
*To change a user's password: click the Edit button next to that user and enter a new password.
*To prevent a user from logging in without deleting their account: switch off the Active option in the user editor.
*To prevent a user from logging in without deleting their account: switch off the Active option in the user editor.
<html>
For details on editing individual users, see [[OnTakt: User settings|User settings]].<html>
<div style="position: relative; padding-bottom: 64.86486486486486%; height: 0;"><iframe src="https://www.loom.com/embed/659c1c41f21c45a2a908eb0cd7651630?sid=86d93479-06c7-4bc3-9695-0123eb8c4710" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
<div style="position: relative; padding-bottom: 64.86486486486486%; height: 0;"><iframe src="https://www.loom.com/embed/659c1c41f21c45a2a908eb0cd7651630?sid=86d93479-06c7-4bc3-9695-0123eb8c4710" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
</html>
</html>


===Access levels===
The following table shows the permissions associated with each profile.
{| class="wikitable"
{| class="wikitable"
!
!'''Administrator'''
!'''Planner'''
!'''Shop Team'''
!'''Auditor'''
|-
! colspan="5" |'''Alerts <small>(Certain alert-dependent actions may not be available to all users)</small>'''
|-
!View alerts
|✓
|✓
|✓
|✓
|-
!Perform system check
|✓
| ✓
|✓
|✓
|-
!Dismiss alerts
|✓
| ✓
|✓
|
|-
!Clear all alerts
|✓
|✓
|
|
|-
! colspan="5" |'''Machines'''
|-
!View/chart machines
|✓
|✓
|✓
|✓
|-
!Modify basic machine options
|✓
|✓
|
|
|-
|-
!Submit machine state updates
|✓
|✓
|
|
|-
!Create machines
|✓
|
|
|
|-
!Modify machine system options
|✓
|
|
|
|-
! colspan="5" | '''Programs'''
|-
!View/chart programs and processes
|✓
|✓
|✓
|✓
|-
!Perform process changeovers
|✓
|✓
|✓
|
|-
!Edit/delete programs and processes
|✓
|✓
|
|
|-
! colspan="5" |'''Tools'''
|-
!View tools
|✓
|✓
|✓
|✓
|-
!View tool assignments
|✓
|✓
|✓
|✓
|-
!Replace tools
|✓
|✓
|✓
|
|-
!Create tools
|✓
|✓
|
|
|-
!Edit tools
|✓
|✓
|
|
|-
!Delete tools
|✓
|✓
|
|
|-
!Add tools to tool assemblies
|✓
|✓
|
|
|-
!Assign tool assemblies to processes
|✓
|✓
|
|
|-
! colspan="5" |'''Parts'''
|-
!View/chart parts
|✓
|✓
|✓
|✓
|-
!Edit parts
|✓
|✓
|✓
|
|-
!Delete parts
|✓
|✓
|✓
|
|-
!Edit or delete parts in bulk
|✓
|✓
|
|
|-
!Edit events
|✓
|✓
| ✓
|
|-
!Delete events
|✓
|✓
|
|
|-
! colspan="5" |'''Quality'''
|-
!View/chart AutoComp data
|✓
|✓
|✓
| ✓
|-
! colspan="5" |'''Reports'''
|-
!Generate reports
| ✓
|✓
|✓
|✓
|-
! colspan="5" |'''Options'''
|-
! Modify options
|✓
|✓
|
|
|-
!Change passwords
|✓
|
|
|
|-
!View plugin logs
|✓
| ✓
|✓
| ✓
|-
!Install and uninstall plugins
|✓
|
|
|
|
|}
|}
Line 285: Line 64:


==Notification setup==
==Notification setup==
See [[Notification setup]] for more information.
See [[Notification setup]] for help connecting to external services.
 
<html>
<div style="position: relative; padding-bottom: 64.86486486486486%; height: 0;"><iframe src="https://www.loom.com/embed/be8b6c2b32674375a5389c8573cc7efc?sid=35293628-0dc8-4559-82bf-edd8015f6202" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
</html>


==Trash==
==Trash==

Latest revision as of 18:53, 18 September 2024

Part of the OnTakt User Guide.


The settings window allows administrators to change how OnTakt behaves.


Machine settings

Defining shift times

See Shifts to learn how to create shifts.

Color timing

Color timing can be configured by clicking the "Edit" button in the top right hand corner of the screen, and click on "Settings"

Screenshot 2024-07-02 at 8.55.33 AM.png
  • Idle time limit: How long to fade out a machine's active color when idle. Set to 0 to fade out immediately. The default is 1200 seconds.
  • Feed hold time limit: How long to fade in a machine's feed hold color. Set to 0 to fade in immediately. The default is 300 seconds.

Advanced machine settings

Part report limit

If a machine reports more than this number of parts at once, only one part will be created.

This prevents overloading the server in cases where program errors cause the machine to report the part count incorrectly.

Screenshot 2024-07-02 at 8.59.21 AM.png

Cost savings estimation

How much money is TMAC saving you?

Screenshot 2024-07-02 at 9.28.18 AM.png

Use the Calculator button to determine the values for these fields.

  • In the calculator window, enter how much each event listed would cost you, as well as how frequently it happens. Click "Save calculations" to save your work for later and automatically copy the calculated totals into the alarm value fields.
  • For frequency, 1 means it always happens, 0 means it never happens, 0.5 means it happens in half of cycles, etc.
  • These values will be shown in reports based on how frequently TMAC alarms occur.

User management

  • To manage users: click on current profile in the top right of the screen, click on "Global Settings", and navigate to the Users Tab. Click "Add" and set the username, password, active status, access level, kudos emoji,
  • To change a user's password: click the Edit button next to that user and enter a new password.
  • To prevent a user from logging in without deleting their account: switch off the Active option in the user editor.

For details on editing individual users, see User settings.

Time zone

A production day as displayed on charts will be defined in this time zone. It is also used for server-side time-based events such as notifications and reports. Except where otherwise specified, times are displayed in the browser's local time zone regardless of this setting.

Changing the time zone affects the server's time-based actions, such as sending midnight notifications. Times displayed in the web interface will always be shown in the time zone of the client device (computer, phone, etc.).

Times are stored in the database using UTC, so changing the time zone will not change any other database entries, such as part or event times.

Steps to select time zone:

  1. Click on the profile name in the top right hand corner of the screen, select "global settings"
  2. Go to the "System Options" tab, chose the desired time zone


Notification setup

See Notification setup for help connecting to external services.

Trash

The trashed objects list is part of the Audit Log.

Database

Downloaded files are PostgreSQL dumps that can be loaded using pg_restore.

For example, to convert a backup named ontakt_db.dump to a plain text SQL file named ontakt_db.sql, run pg_restore -f ontakt_db.sql ontakt_db.dump.