--- title: How to use user defined operators description: "Go to the "Company settings" menu. Click the Use user defined operators in report stop history, views production status and operator button:  Now users can define an operator, when they create break" --- [Skip to content](https://kb.dataintel.dk/how-to-use-user-defined-operators#main-content) English Show submenu for translations [Submit a request](https://kb.dataintel.dk/kb-tickets/new?hsLang=en) ![DIAP-1.png\]](https://kb.dataintel.dk/hs-fs/hubfs/DIAP-1.png?height=41&name=DIAP-1.png) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) Open main navigation Close main navigation - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) - English Show submenu for translations - [Submit a request](https://kb.dataintel.dk/kb-tickets/new) - Go to Data Intelligence A/S Go to Data Intelligence A/S Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [Help Center](https://kb.dataintel.dk/?hsLang=en) 2. [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en) 3. [Guides](https://kb.dataintel.dk/oee-site?hsLang=en#guides) # How to use user defined operators ### Introduction - This guide describes how to use an operator defined by a user. This operator is used for showing who reported or categorized a stop. ### Setup Go to the "**Company settings**" menu. ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015897940mceclip0.png) Click the **Use user defined operators in report stop history, views production status and operator **button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015910019mceclip1.png)  Now users can define an operator, when they create breaks or categorize stops. ### Check in an operator Both in **Views-\>Production status** and **Views-\>Operator**, there is an operator window in the top right corner of the site: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015898780mceclip0.png) Click the **Change operator** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015910499mceclip1.png) Now provide the name for the operator: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015910699mceclip2.png) and click the **Check in** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015910779mceclip3.png) Now your operator is checked in: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015899280mceclip4.png) ### Change operator If an operator is checked in, then one can change the operator by following the step in [Check in a operator](https://kb.dataintel.dk/how-to-use-user-defined-operators#CheckInAnOperator) the difference is, that there will be a **Change operator** button instead of a **Check in** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015911239mceclip6.png) ### Check out operator If an operator is checked in, then one can check out the operator. Open the operator window as shown in [Check in a operator](https://kb.dataintel.dk/how-to-use-user-defined-operators#CheckInAnOperator) and click the **Check out** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015899820mceclip7.png) You can see, that no operators are checked in, when the operator field is blank in the operator window: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015911919mceclip9.png) ### User defined operators is paired with orders ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-14-48-06-PM.png) The Operator that is checked in: ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-17-30-15-PM.png) Is paired with the new order and you can see them in the new operator column in "Reports-\>Order", when the new order has ended: ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-19-21-45-PM.png) ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-20-46-48-PM.png) You can also see the operator in the detailed popup for the order: ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-22-35-75-PM.png) ![](https://kb.dataintel.dk/hubfs/image-png-Jun-02-2021-12-23-36-37-PM.png) ### Use operator when creating a break You can create breaks in the **Views-\>Production status** and **Views-\>Operator** sites. When you create a break, you can bind your operator to that break. This done by having an operator checked in and create a break. Here are the steps: 1\. Have an operator check in: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015901300mceclip10.png) 2\. Have the break button(s) configured to be used: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015901400mceclip11.png) 3\. Start a break. You can see more details on how to use the breaks here: [How to use the "break" button](https://kb.dataintel.dk/how-to-use-the-break-button?hsLang=en) ### Use operator when categorizing a stop You can categorize a stop with an operator in the **Views-\>Production status** and **Views-\>Operator** sites. When you categorize a stop, you can bind your operator to that stop. This done by having a operator checked in and categorize a stop. Here are the steps: 1\. Have an operator check in: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015901300mceclip10-1.png) 2\. Select a stop to categorize: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015913639mceclip12.png) 3\. Select a stop cause: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015913679mceclip13.png) You can see more details on how to categorize a stop here [How to use stop reason tree structure](https://kb.dataintel.dk/how-to-use-stop-reason-tree-structure?hsLang=en) under section **Assign stop reason in Production status**. ### Categorizing a break overwrites the operator on the stop If you have a created a break with an operator, where stop cause has children, then you can overwrite the operator by ending the break, change the operator and categorize the stop cause on the stop created from the break. Here is an example: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015914860mceclip0.png) ### View the operators that reported the stops Go to **Reports-\>Stop history**: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015906620mceclip15.png) Select your unit, search period and filters: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015906700mceclip16.png) Click the **Apply** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015918079mceclip17.png) Now you can see who has created or categorized the stops, under the **Operator** column: ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-01-24-34-58-PM.png) If an operator is blank, then the stop is either created by a service, an operator wasn't check in or the user defined operators wasn't configured to be used, when the stop was created. You can also use the filter icon, to search for stops, created or categorized by a specific operator: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015922419mceclip23.png) Type in a select your operator, then click the **OK** button: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360015922459mceclip24.png) Now you only see stops with that operator: ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-01-25-55-93-PM.png) ### Split stop in stop history with a operator In stop history if you split a stop, that had an operator in it, then the new stop will also have the same operator in it. ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-01-27-03-94-PM.png) ### Changing stop cause for a stop in stop history, doesn't change the operator Unlike the sites **Views-\>Production status** and **Views-\>Operator**, changing the stop cause for a stop, when in the **Stop history** site, doesn't change the operator in that stop.   - [DIAP Gateway](https://kb.dataintel.dk/diap-gateway?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/diap-gateway?hsLang=en#getting-started) - [Troubleshooting](https://kb.dataintel.dk/diap-gateway?hsLang=en#troubleshooting) - [Known issues/limitations](https://kb.dataintel.dk/diap-gateway?hsLang=en#known-issues-limitations) - [General](https://kb.dataintel.dk/general?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/general?hsLang=en#faq) - [Configuration](https://kb.dataintel.dk/configuration?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/configuration?hsLang=en#faq) - [Troubleshooting](https://kb.dataintel.dk/configuration?hsLang=en#troubleshooting) - [Guides](https://kb.dataintel.dk/configuration?hsLang=en#guides) - [Protocols](https://kb.dataintel.dk/configuration?hsLang=en#protocols) - [Live/Real time site](https://kb.dataintel.dk/live-real-time-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/live-real-time-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/live-real-time-site?hsLang=en#faq) - [Guide](https://kb.dataintel.dk/live-real-time-site?hsLang=en#guide) - [Features](https://kb.dataintel.dk/live-real-time-site?hsLang=en#features) - [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/oee-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/oee-site?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/oee-site?hsLang=en#guides) - [Configuration](https://kb.dataintel.dk/oee-site?hsLang=en#configuration) - [Remote Access](https://kb.dataintel.dk/remote-access?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/remote-access?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/remote-access?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/remote-access?hsLang=en#guides) - [API](https://kb.dataintel.dk/api?hsLang=en#main-content) - [API](https://kb.dataintel.dk/api?hsLang=en#api) - [Release information](https://kb.dataintel.dk/release-information?hsLang=en#main-content) - [DIAP Release Notes](https://kb.dataintel.dk/release-information?hsLang=en#diap-release-notes) - [Live/Real time site](https://kb.dataintel.dk/release-information?hsLang=en#live-real-time-site) - [OEE site](https://kb.dataintel.dk/release-information?hsLang=en#oee-site) - [Management site](https://kb.dataintel.dk/release-information?hsLang=en#management-site) - [DIAP Gateway](https://kb.dataintel.dk/release-information?hsLang=en#diap-gateway) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) [![Chill listening crop-3](https://kb.dataintel.dk/hs-fs/hubfs/Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png?width=221&height=26&name=Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png "Chill listening crop-3")](https://diap.hubspotpagebuilder.com/-temporary-slug-5b226bcb-69c8-45c1-82ff-e060e2d4037d?hsLang=en) Copyright © 2026, Data Intelligence A/S