--- title: "Shift Starter Meeting" slug: "shift-starter-meeting" updated: 2024-01-16T12:38:30Z published: 2024-01-16T12:38:30Z canonical: "support.tulip.co/shift-starter-meeting" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Shift Starter Meeting To download the app, visit: [Library](https://tulip.co/library/apps/shift-starter-meeting/) *This Article summarizes how the Shift Starter Meeting application is structured and built.* ## Purpose The Shift Starter Meeting app is developed with the specific needs of line leaders and operators in mind. This vital tool assists in conducting daily meetings that are integral to successful operations. ## Setup The app focuses on key operational aspects including Safety, Quality, Scheduled Procedures, Performance, Today’s Target, and Attendance. Each topic can be discussed thoroughly with the opportunity to update information in real-time during the meeting. The 5S step is an extra step that can be integrated into the meeting workflow. Presently, no step leads there. While the 5S isn't needed in daily meetings, it can be added to the weekly ones. To include it, a button with Trigger logic must be set up to direct users to this Step. ## Tables Used The application uses the **Order Materials**, **Operator Activity History**, **Users Table**, **Scheduled Procedures**, **Sample Inspections**, and **Safety Incidents** Tables. The **Order Materials** table is used in the 'Today Target' and 'Today Target - New Order' steps. It contains the 'Get Order 1' query that assists in creating a new order ID in the 'Today Target - New Order' step. The **Operator Activity History** table is utilized in the 'Availability/Attendance' step. The **Users Table** is also used in the 'Availability/Attendance' and 'Plan Attendance' steps. The **Scheduled Procedures** table is employed in the 'Scheduled Procedures', 'Schedule Procedure', and 'Create Safety Event' steps. The **Sample Inspections** table is called upon in the 'Additional 5s' step. It comprises 5 queries: 'Standardize', 'Shine', 'Sort', 'Sustain', 'Set in Order'. Each of these queries carries two filters to set the time and an aggregation to sum the results for the designated time. Lastly, the **Safety Incidents** table is used in the 'Safety', 'Create Safety Event', and 'Safety Event History' steps. ## App Structure The first Step Group in the app is **Scheduled Procedures**, which consists of two steps. The first step, also called **Scheduled Procedures**, allows users to view the procedures scheduled for the day. Users have the ability to select, reassign, or reschedule these procedures as needed. The second step is accessible from the **Scheduled Procedures** step. In this step, users can create a new procedure. While on this step, users have the capability to create new Records with the new procedure in the 'Scheduled Procedures' table. ![Screenshot 2024-01-05 at 11.59.49.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2011.59.49.png) The second step group in the app is **Safety**, which comprises three steps: **Safety**, **Create Safety Event**, and **Safety Event History**. On the **Safety** step, users can view analytics connected to previous safety events and a table containing open safety events. If a user selects an open safety event, they can comment on it, and the comment will be saved in the corresponding event's comment field. ![Screenshot 2024-01-05 at 12.30.34.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.30.34.png) Both **Create Safety Event** and **Safety Event History** steps are accessible from the **Safety** step. On the **Create Safety Event** step, users can generate a new event by creating a table record in the 'Safety Incident' table. ![Screenshot 2024-01-05 at 12.30.43.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.30.43.png) The **Safety Event History** step allows users to search within the 'Safety Incident' table. They can select an incident and review its details. ![Screenshot 2024-01-05 at 12.30.52.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.30.52.png) The next step is the **Quality** step. In this step, users can view Analyses related to quality measures. They also have the ability to comment on these analyses. Such comments will be saved as a part of completion data. ![Screenshot 2024-01-05 at 12.32.12.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.32.12.png) The next step is the **Performance** step. Similar to the Quality step, users can view analyses related to performance and comment on them. These comments will be saved as part of the Completion data. ![Screenshot 2024-01-05 at 12.37.14.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.37.14.png) The **Today Target** step group follows the **Performance** step. It contains two steps: **Today Target** and **Today Target - New Order**. In the **Today Target** step, users can view analyses regarding the daily work orders. You can reschedule the work orders if needed. ![Screenshot 2024-01-05 at 12.38.33.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.38.33.png) The **Today Target - New Order** can be accessed from the **Today Target** step. In this section, users have the capability to create new work orders ![Screenshot 2024-01-05 at 12.38.43.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2012.38.43.png) This follows the **Availability/Attendance** step group, which contains two steps: **Availability/Attendance** and **Plan Attendance**. On the **Availability/Attendance** step, users have the ability to view both the User Table and the Operator Activity History Table. They can log the day's attendance into the Operator Activity History Table. By selecting an individual from the User Table and clicking either the 'Present' or 'Absent' button, a new record appears in the Operator Activity History Table. This action also updates the status color in the User Table, providing immediate visual feedback about each person's attendance status. Moreover, this step offers a **Complete** button. Once users are finished with their tasks, they can click on this button, which finalizes the app's operations and saves all variables into the completion data. ![Screenshot 2024-01-05 at 13.00.36.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2013.00.36.png) The **Plan Attendance** step can be accessed from the **Availability/Attendance**. In this step, users have the option to plan future attendance. They can select an individual from the User Table and a future date, then click either the 'Planning for Attend' or 'Planning for Absence' button. Doing so will update the User Table with the detailed plan. ![Screenshot 2024-01-05 at 13.00.28.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2013.00.28.png) The last step, referred to as the 5S step, is not accessible while the app is running. It's an optional additional step that users can incorporate if they want. In this step, users can search for 5S scores according to specific dates. ![Screenshot 2024-01-05 at 13.02.29.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-01-05%20at%2013.02.29.png) ## Further Reading The following apps can enhance the user experience and efficiency when using the Shift Starter App: - [Order Tracking Template](https://tulip.co/library/apps/order-tracking-template/) - [Safety Incident Manager](https://tulip.co/library/apps/safety-incident-manager/) - [Attendance App Suite](https://tulip.co/library/suites/attendance-app-suite/) - [5S Checklist](https://tulip.co/library/apps/5s-checklist/) - [Performance Visibility Terminal](https://tulip.co/library/apps/performance-visibility-terminal/) - [Digital Tier Board](https://tulip.co/library/suites/digital-tier-board/) - [Order Tracking Functional Example](https://tulip.co/library/apps/order-tracking-functional-example/) **Trigger** **Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**. **Triggers** can contain **actions**, **transitions**, and **conditions**. **Step** A view your users will see within an application. **Steps** can be viewed chronologically or in whatever order best fits your process. Steps can be grouped into **Step Groups**to manage and organize your app Steps. **Tulip Tables** **Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif) **Step Group** **Step Groups**are a mechanism to organize and group individual steps. Step groups can be duplicated/deleted and reordered like individual steps. **Table Record** A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger. To edit a record it must be loaded into a **Table Record Placeholder.** **Analysis** An **analysis** is a live updating combination of a data query and a visualisation. It allows to show metrics based on app completion data, Tulip Table data, or machine data. Analyses can be embedded and dynamically filtered within apps, placed on dashboards and shared via a direct link Example - Bar chart ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-1662410531382.png) **App Completion** **App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.** By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.