OnTakt: Settings: Difference between revisions

From Knowledge Base
No edit summary
 
(16 intermediate revisions by 2 users 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.
See [[OnTakt: Shifts|Shifts]] to learn how to create shifts.
 
To set shift times:
#Navigate to the Options page by clicking the link in the top navigation bar.
#Enter the start and stop times for the shop.
#Click Save Changes.
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.


=== Color timing ===
=== 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"


* '''Max idle time:''' How long it takes for a machine to fade to yellow when in feed hold mode.
[[File:Screenshot 2024-07-02 at 8.55.33 AM.png|center|thumb|1199x1199px]]
* '''Max feed hold time:''' How long it takes for a non-running machine to fade from green. The color will fade to blue if OnTakt thinks production has stopped, or grey otherwise.
* '''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 ===
=== Advanced machine settings ===
Line 27: Line 23:


This prevents overloading the server in cases where program errors cause the machine to report the part count incorrectly.
This prevents overloading the server in cases where program errors cause the machine to report the part count incorrectly.
[[File:Screenshot 2024-07-02 at 8.59.21 AM.png|center|thumb|1151x1151px]]


==Cost savings estimation==
==Cost savings estimation==
How much is TMAC saving you?
How much money is TMAC saving you?
 
[[File:Screenshot 2024-07-02 at 9.28.18 AM.png|center|thumb|1241x1241px]]
Use the Calculator button to determine the values for these fields.
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.
* 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.
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.
 
These values will be shown in reports based on how frequently TMAC alarms occur.


==User management==
==User management==
To manage users: click on the user menu at the top right of OnTakt, open Options, and then switch to the Users tab on the left.


To change a user's password: click the Edit button next to that user and enter a new password.
*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 [[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>
</html>


To prevent a user from logging in without deleting their account: switch off the Active option in the user editor.
===Access levels===
{| 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
|✓
|
|
|
|
|}
|}


==Time zone==
==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.).
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 [[wikipedia:Coordinated_Universal_Time|UTC]], so changing the time zone will not change any other database entries, such as part or event times.
Times are stored in the database using [[wikipedia:Coordinated_Universal_Time|UTC]], so changing the time zone will not change any other database entries, such as part or event times.


==Notification setup==
Steps to select time zone:


===Slack Setup===
#Click on the profile name in the top right hand corner of the screen, select "global settings"
This must be done by a workspace administrator.
#Go to the "System Options" tab, chose the desired time zone
#Go to https://api.slack.com/apps
#If prompted, sign in to the correct workspace
#Click the Create New App button at the top right
#Enter an app name ("OnTakt" works just fine) and choose the correct workspace, then click Create App
#Under "Add features and functionality", click Incoming Webhooks
#Turn on the switch at the top right to activate incoming webhooks
#For each channel you want OnTakt to post to:
##Click the Add New Webhook to Workspace button at the bottom
##In the page that opens, choose the channel you want to post to and click Allow
##Copy the Webhook URL from the list (make sure it's for the right channel)
##Paste this URL into the Slack Webhook URL field in the OnTakt machine settings page
To add or remove webhooks in the future:
#Go to https://api.slack.com/apps
#Click the name of the OnTakt app from the list
#Click Incoming Webhooks under Features in the left sidebar
If you would like the app to add an icon to the bot that posts messages:
#Go to https://api.slack.com/apps
#Click the name of the OnTakt app from the list
#Scroll down to Display Information
#You can choose any icon, but here is the OnTakt logo
#Click '''+ Add App Icon''' under "App icon & preview" and choose the file


===Microsoft Teams Setup===
[[File:Ontakt Settings - Time Zone.mov|800px|frameless|center]]
This must be done by a team administrator.
#Go to https://teams.microsoft.com/l/app/203a1e2c-26cc-47ca-83ae-be98f960b6b2
#Click the "Add to a team" button
#Search for the channel you want to send notifications to
#Click the "Set up a connector" button
#When the configuration page opens, enter any name, such as "OnTakt"
#You can choose any icon, but here is the OnTakt logo
#Click the "Create" button
#After the page reloads, scroll to the bottom and copy the URL it provides
#Click "Done"
#Paste this URL into the machine's Microsoft Teams Webhook URL field in OnTakt


=== Email setup ===
A notification channel can have an email address instead of a webhook URL, however, sending email will not work until an email server is configured. To do this, visit the Notifications tab of the global settings window inside OnTakt and fill in the following fields:


* '''Server host:''' IP address or hostname of the SMTP server.
==Notification setup==
* '''Server port:''' usually 587 for TLS connections or 25 for unencrypted connections.
See [[Notification setup]] for help connecting to external services.
* '''Secure with TLS:''' strongly recommended, but requires the SMTP server to support it. SSL is much less secure and therefore not supported.
* '''Username:''' username to log into the SMTP server with.
* '''Password:''' password to log into the SMTP server with.
* '''From email address:''' emails will appear to be from this address. Defaults to the SMTP username if not set.


The correct values for these fields depends on your email provider. Instructions for common providers can be found here:
<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>


* [https://support.google.com/a/answer/176600 Google Workspace]
==Trash==
* [https://support.google.com/mail/answer/7126229 Gmail]
* [https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-8361e398-8af4-4e97-b147-6c6c4ac95353 Microsoft 365]
* [https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040 Microsoft Outlook.com]
* [https://support.apple.com/en-us/HT202304 iCloud Mail]
* [https://www.zoho.com/mail/help/zoho-smtp.html Zoho Mail]
* [https://help.yahoo.com/kb/SLN4075.html Yahoo Mail]
 
Note that sending emails is slower than publishing to webhooks, so webhooks are preferred where possible.
 
== Trash ==
The trashed objects list is part of the [[OnTakt: Audit Log|Audit Log]].
The trashed objects list is part of the [[OnTakt: Audit Log|Audit Log]].


== Database ==
==Database==
Downloaded files are PostgreSQL dumps that can be loaded using [https://www.postgresql.org/docs/current/app-pgrestore.html pg_restore].
Downloaded files are PostgreSQL dumps that can be loaded using [https://www.postgresql.org/docs/current/app-pgrestore.html pg_restore].


For example, to convert a backup named <code>ontakt_db.dump</code> to a plain text SQL file named <code>ontakt_db.sql</code>, run <code>pg_restore -f ontakt_db.sql ontakt_db.dump</code>.
For example, to convert a backup named <code>ontakt_db.dump</code> to a plain text SQL file named <code>ontakt_db.sql</code>, run <code>pg_restore -f ontakt_db.sql ontakt_db.dump</code>.
[[Category:OnTakt]]
 
[[File:Ontakt Settings - Database.mov|1920x1080px|thumb]]
[[Category:OnTakt User Guide]]
[[Category:OnTakt User Guide]]
{{DEFAULTSORT:Settings}}
{{DEFAULTSORT:Settings}}

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.

Retrieved from "https://kb.wolframmfg.com/index.php?title=OnTakt:_Settings&oldid=2163"