What replaces OEE Alert when you move to Vorne XL V2 boards?

What does OEE Alert actually do?

Deb-Tech Systems, Inc. publishes it, and describes it as “a browser-based Intranet application that lets you see ALL of your Vorne XL(v1) Productivity Appliances™ on a single screen”. It reads from XL v1 devices both directly and through the XL Bolt-On Data Collector, and it is built to sit on a big screen somebody walks past on the way onto the floor.

Three jobs it covers, per that same description:

• The wall. Every device on one screen, with hourly OEE or line speed, so a supervisor can see which asset is the problem without opening anything.
• The rules. Alerts raised by asset group, with control over when an alert fires and who it goes to.
• The comments. Reviewing each production event, correcting a reason code that was wrong, and typing what actually happened against the event so the next person reading the report has the context.

Deb-Tech describes the product in terms of Vorne XL v1 devices throughout. That is why this question comes up at all: the question is not about the tool, it is about what covers those three jobs once the boards underneath are V2.

What watches the thresholds once the boards are V2?

OEE Pulse does. You set the rule once and it is checked on every shift, without anyone refreshing a dashboard. Pulse groups the rules three ways, which maps closely onto how an OEE Alert install is usually configured:

• Master downtime alerts. Set thresholds for downtime events and get an email the moment a limit is exceeded. This is the ten-minutes-and-nobody-has-said-anything alert.
• Custom category filters. Build an alert by plant, location or type, and track OEE, Availability, Quality or Performance against it. This is how a rule ends up scoped to one area rather than the whole site.
• Process and state event alerts. Trigger on specific state events and reason codes, so a particular fault is escalated differently from a planned changeover.

Who gets told, and on what?

In-app banners, email and SMS, plus Teams, Slack and Discord. The channel matters more than it sounds: an alert that only lands in an inbox is an alert nobody reads on second shift.

Text messages run through a program called OEE IntelliSuite Production Alerts, and it is transactional only: production events, never marketing. A real message looks like this: “OEE IntelliSuite alert: Line 3 Packer has been DOWN for 15 minutes (since 2:42 PM). Reason: Mechanical Fault. Reply STOP to unsubscribe.” People enter their own number and check a consent box themselves inside Pulse, and a number with no consent record is never messaged. The full opt-in and opt-out flow is on the SMS alerts page.

Does it run inside our own network?

It can be, and that is the arrangement this section describes: installed inside the customer network, with the production data Pulse works from staying there. It can also be hosted for you, which draws the boundary somewhere else. Either way the opt-in for text alerts happens in the Pulse application rather than on this website, because the alerting lives in your deployment rather than on anything of ours.

Delivery is the part worth being precise about, because it depends on the channel and this is the question IT will ask. In-app alerts and email through an internal relay send nothing off the network at all. A channel hosted somewhere else receives the text of that one alert, which names a machine and a number, plus the address, phone number or channel it is going to, and nothing more. On an in-plant install the production database stays where it is whichever channel fires. Sites with no internet at all can install from an offline bundle, take updates by manual artifact transfer, and still alert by email inside the network. Which channels reach outside, and exactly what crosses on each, is set out channel by channel on the answer about alerting inside the firewall.

What happens to the comments people already wrote?

They come across. Data Converter transfers V1 OEE Alert comments into V2 notes, alongside the production history itself, and every V1 field lands on its V2 equivalent so the old records answer the same questions as the new ones. The point is that an old stop still carries the sentence somebody typed explaining it.

The history side of this is the longer story, and it is on the sibling page about what replaces OEE Studio for reporting.

What comes across, and what do you set up in Pulse?

These two halves are done by different people at different times, so they are worth separating before you start.

Carried over by Data Converter:

• Production history, rewritten into the V2 schema rather than parked in an archive.
• Comments written against events in OEE Alert, as V2 notes.
• Reason codes and the rest of the V1 fields, mapped onto their V2 equivalents.

Configured in Pulse:

• The alert rules themselves: the thresholds, the asset groups they apply to, and which of the three rule types each one is.
• Who receives what, and on which channel. Text-message recipients enter and consent to their own number, which is the one part nobody can do on someone else's behalf.
• What goes on the floor screen, since Pulse is a browser view rather than a fixed layout.

The thresholds and reason codes are the ones you are already watching, so this is a configuration exercise rather than a design one. Worth putting on the plan for the changeover rather than discovering on the day.