Show TOC

Object documentationMessage Locate this document in the navigation structure

 

A communication of an occurrence on the shop floor that may affect production and requires a response from the system or users.

 

The system generates messages to notify appropriate manufacturing personnel that planned conditions have not been met. For example, the system can be set up so that when a nonconformance is logged using a particular NC code, an alarm message is sent to the production supervisor (see Real-Time Warnings Maintenance and SPC Alarm Severity Maintenance).

The system sends messages to one or more user groups defined for the message type, so any user who belongs to the specified group can process the message and acknowledge the message’s importance and requirement to do something to close it. A message can be processed only by one person at a time in order to prevent overriding any processes completed by another person.

Replaceable Parameters

Messages, defined in Message Type Maintenance, can include replaceable parameters (see Replaceable Parameters).

Example Example

You can include %SFC% in a message so that when the message is sent, the specific SFC number is inserted into the message:

SFC number 6754 is not being produced per design.

Message to be sent: “SFC %UNIT_SFC% has been nonconformed”.

Result when message is triggered: SFC 6754 has been nonconformed.

End of the example.

Structure

This object can have the following attributes:

  • Message Type

  • Severity

  • Process Workflow

  • Subject

  • Body

  • Auto Close on Process Workflow Completion

  • Auto Close Interval

  • POD Notification

  • User Group

  • Notification

  • Status

For more information, see Message Type Maintenance and Message List (Messages).

Message Types and Process Workflows

There are several predefined types of messages. They include the following:

  • BUYOFF_REQUEST

    Allows two manual steps (accept or reject); accept closes the message, reject requires a user to log an NC code to close the message.

  • RTW_CONSEC_NC, RTW_YIELD_RATE, SPC_ALARM_VIOLATION and SPC_ALARM_WARNING

    Consists of five sequence steps that need to be completed before the message can be closed.

    The first two steps are automatic. They are triggered as soon as the message is generated and place the operation and resource on hold when something went beyond the planned parameters (for example, yield processing rate fell below the value defined in Real-Time Warnings Maintenance). This means that the operation and resource cannot be used until the message is processed.

    The third step is manual. The user must enter Reason, Cause and Resolution and complete the Log Codes action.

    The last two steps are automatic. The system releases hold from the operation and resource. The message status changes to Closed.

  • FREE_FORM and all other types

    The SIMPLE process workflow is used for all other message types that exist in the system (see Process Workflow).

    This process workflow has no automatic or manual sequence steps, which means that it may or may not need a manual action by a user to close the message.

    A message type with this process workflow can be closed by a user choosing the Close Message button in the Message Board POD, by the system if the Auto Close Interval or Auto Close On Process Workflow Completion, checkboxes are selected.

More Information

Create Message