Workflows reduce the time to resolve a problem by providing guidance, work instructions, and supporting documents, etc.  Workflow actions can be triggered and closed out manually by authorized personnel or automatically by the machine/controller itself – it’s up to you.  

SQUEAKS seamlessly integrates with other applications.  Events and associated Workflows can be initiated by other applications via SQUEAKS APIs and easily incorporated into a SQUEAKS message.

The SQUEAKS escalation process and rules provide a framework for ensuring that concerning events (downtime, product quality, operator calls, etc.) are addressed at the appropriate level of management based on their severity and complexity.  An escalation process can also be initiated if a Squeak isn’t acted upon in a timely or correct manner.

Escalation Process

You decide how and when you want the escalated alert to move up the chain of command and how you want to be notified.  In many organizations, the process includes a set of predefined escalation levels, each corresponding to a different level of management responsibility depending on the condition/event.  For example, a Level 1 issue may be addressed by a team leader, while a Level 2 issue may be escalated to a department manager or area leader.  More complex or critical issues may be escalated to higher levels of management, up to and including the executive leadership team.

The escalation process helps ensure that “issues or events” are addressed promptly and effectively and that the appropriate resources are allocated to resolve the issue. By escalating issues as needed, teams can quickly access the expertise and resources they need to identify the root cause of the problem and implement an effective correction action plan.