# Kanoa Ops Training

This section is focused on Kanoa Ops, the core operational foundation of Kanoa MES.

We'll start by modeling the assets within the plant, creating materials (items), linking them to assets, configuring their expected production rates, and configuring asset modes and states.
We'll then connect PLC tags to automate data collection, schedule operations on assets, and pull production orders from an ERP.
Next, we'll manage users and their roles, customize the navigation menu, build dashboards and marquees, and use scripts to scale the model across the enterprise.
Finally, we'll explain speed losses with performance reasons, record custom and measured process values, and analyze how effectively operators' time is used.

:::caution
The first user to log into a freshly installed Kanoa MES application automatically receives Gateway Admin rights, and only Gateway Admins can grant Gateway Admin rights to other users.
Do not log in as admin. Create a user in the Ignition default user source with a first and last name, and log in as that user.
:::

Let's start by having you log into the application. This is a **really** important first step!

:::action[Log In with your username]

1. Create a user in the Ignition default user source with a first and last name.
2. Launch the KanoaMES project from the Gateway Page and log in as that user.

:::

::embed-section{src="../../configuration/users.md" collapsed="true" summary="Reference Materials: Users - Learn how Kanoa manages users."}

Next let's setup this Gateway as a development environment. In a development environment, gateway admins can delete asserts even if they have production data linked to them. 
In a production environment, we provide safeguards against inadvertently deleting all your production data.

:::action[Setup Gateway as Development]

1. Navigate to **Configuration → Application → Settings**.
2. set Environment to 'Development'

:::

:::check

Copy this script into the Ignition Designer Script Console (**Tools → Script Console**) and run it. It checks that a user with a first and last name (not `admin`) has logged in to Kanoa and is the Gateway Admin, and that the environment is set to Development. Each check prints PASS or FAIL with what to fix. It doesn't change anything.

<details>
<summary>Show the check script</summary>

::check-script{src="ops/index.py" title="checkLesson-opsStart.py"}

</details>

:::