Forms & Objects

Standard documentation linked to a Parent Object

Overview

A form is a document use to collect operator input. The information collected is stored in 9 different categories, or Parent Objects: Alert, Company, Events, Machine, Operator, Part, Process Data, Production Run, and Work Orders. A subcategory, or child object, can be created from a Parent Object. 

Each object contains custom fields created by the customer to store information or perform custom calculations. 

Function

An employee can submit data and trigger related events like downtime, quantity, and scrap with a form. Some fields might be required depending on the type of form and event you would like to create. For example, if you choose to have a form that also created a downtime event, the operator is required to input the downtime event code. 

Custom Objects

Before you can create a form, you would need to create Custom Objects. These are the fields you will be using to create your forms and link them to a category.

Types of Custom Objects

• Parent Object: Objects preloaded in the Mingo System. A second submission of the same parent object's custom field will overwrite the original characters set. 
• Child Object: Allows you to group custom fields. This feature is only available for Company, Machine, Part, Production Run, and Work Order Parent Object. This object allows multiple entries for one custom object. It does not overwrite the previous custom fields, unless edited by a user with the proper permission.  

Custom Forms

Forms have different purposes. Their main purpose is to get rid of paper in your facility. There are two types of forms: customizable and display-changing Forms. 

Types of Forms

• Custom: report data and in some cases creates an event when submitted. 
• Display-Changing: adds a new metric to the Production Details, End of Run Report, and Work Order Details.