Simplifying SMS Alerts in EcoStruxure: How TextBolt Makes Event Notification Easier

If you run Power Monitoring Expert (PME) and you want SMS alerts when a breaker trips, a meter faults, or your switchgear throws an overload, you’ve probably hit the same wall everyone else does. PME’s Event Notification Module supports SMS out of the box, but only if you open a separate SMS account, register for 10DLC compliance, and figure out where the API keys live inside your OT stack.

That’s a lot of plumbing for what should just be a notification.

Good news: there’s a shortcut. TextBolt’s email-to-text gateway lets PME send SMS using nothing but the email-notification rules you already have. Add one new recipient address, and your existing ENM rule starts texting the on-call operator. No SDK, no code changes, no third-party SMS credentials anywhere inside PME.

Why SMS Matters in EcoStruxure and OT

In Schneider Electric’s EcoStruxure platform, real-time awareness is everything. From low-voltage switchgear to data-center power-monitoring systems, you’re collecting thousands of data points across sensors, edge devices, and sub-stations.

But alerts that only live inside PME, dashboards, or tickets are only half-solved. For critical events like overloads, voltage dips, breaker trips, or cybersecurity-related alarms, direct SMS to operations teams is often the fastest way to respond.

That’s where Schneider’s Event Notification Module (ENM) in Power Monitoring Expert (PME) comes in: it lets you send notifications via email, SMS, or SNMP when specific alarms or incidents occur.

Until recently, however, using SMS with ENM meant one thing: Twilio.

What the Event Notification Module (ENM) Expects Today

Let’s be precise: PME’s Event Notification Module already supports SMS. The help documentation is clear:

• The Event Notification Module uses the Alarms application to detect system events.
• You create notification rules that trigger when an alarm becomes active, or when a new incident appears in a view.
• Those rules can notify email addresses, phone numbers (for SMS), or SNMP servers.

To configure SMS, PME requires:

• Alarm views (default or custom) that define which events should trigger notifications.
• Recipient phone numbers for SMS.
• SMTP server details for email-based notifications.
• An SMS account with Twilio, because “the SMS capabilities of the Event Notification Module are built on technology from Twilio.”

In plain terms: if you want SMS, you must:

1. Open a Twilio account.
2. Sign up for SMS service (including 10DLC registration if you’re in the U.S.).
3. Configure PME to talk to Twilio (credentials, API keys, etc.).

This is fine if:

• Your PME environment already integrates with modern APIs.
• Your IT team is comfortable managing Twilio-specific SDKs, secrets, and 10DLC compliance in parallel with your existing OT stack.

But in many legacy or OT-heavy environments, that’s exactly the friction you want to avoid.

The Real Pain: Twilio Plus Old-Generation OT Stacks

In practice, EcoStruxure deployments often span:

• Old-generation power-monitoring hardware (metering devices, legacy PME-enabled servers).
• Windows-based SCADA-style systems that run on-prem.
• Norm-aware but not “cloud-native” teams, who are great at configuring alarm views and SNMP, but not at maintaining API-driven SMS integrations.

For these environments, wiring Twilio into PME can mean:

• Managing yet another cloud account and API key.
• Learning Twilio’s SMS/10DLC model instead of focusing on power-system behavior.
• Writing or maintaining custom scripts that bridge PME to Twilio when ENM doesn’t expose the exact fields you need.

This is where TextBolt changes the equation.

How TextBolt Changes the SMS-in-PME Story

TextBolt is an email-to-text gateway that converts standard email messages into carrier-compliant SMS over 10DLC channels.

From the PME perspective, that means:

• You can keep using PME’s existing email-notification capabilities.
• You route some of those emails to TextBolt-powered addresses instead of pure email addresses.
• TextBolt then converts those emails into SMS and delivers them to your OT team’s phones.

Critically:

• No SDK. You do not add Twilio-specific libraries to PME or any other part of your OT stack.
• No code change. Your existing ENM notification rules and email-routing logic stay exactly as they are.
• No API-level integration with Twilio. You no longer need to configure Twilio credentials inside PME or in a separate “bridge” script.

What “No SDK, No Code Change” Really Means for PME

Today, using Twilio with ENM looks roughly like this:

1. PME detects an alarm (e.g., Overload on Main Feeder).
2. ENM triggers a notification rule.
3. That rule sends an SMS request to Twilio (via Twilio-specific configuration or a side system).
4. The SMS hits an operator’s phone.

With TextBolt, the flow changes slightly:

1. PME detects Overload on Main Feeder.
2. ENM triggers a notification rule.
3. That rule sends an email to:
   • operations-team@company.com (for email alerts), and
   • 15551234567@sendemailtotext.com (for SMS to a specific operator).
4. TextBolt receives the email, converts it to SMS, and delivers it via 10DLC.

From PME’s point of view, step 3 is still “send an email.” The only thing you change is the destination address. There is no SDK, no Twilio-specific API, and no code rewrite. For the broader walkthrough across any app that already sends email, see how to send text with no SDK or code changes.

Concrete Example: ENM Plus SMS via TextBolt (No Twilio Coding)

Let’s walk through a realistic example using Power Monitoring Expert 2023 plus the Event Notification Module.

Step 1: Define the Alarm View in PME

You create an alarm view in PME that shows:

• Only alarms for critical breakers (e.g., main incomer, critical sub-feeders).
• With severity Critical or Major.
• Filtered by location (e.g., “Data Center, Main Switchboard”).

This becomes your “to-trigger-SMS” view.

Step 2: Configure ENM Notification Rules (Email-Based)

In the Event Notification Module, you create a notification rule:

• Trigger: When an alarm becomes active in the critical-breaker view.
• Recipients:
  • ops@datacenter.company.com (email inbox).
  • noc-team@datacenter.company.com (PagerDuty/Slack email integration, if used).
• SMTP: Your existing corporate/Exchange/M365 SMTP server.

So far, this is 100% standard PME configuration, no SMS, no Twilio, no code.

Step 3: Add SMS With TextBolt (Zero Code Change)

Now you want SMS alerts to the on-call operator for critical events.

With Twilio, you’d typically:

• Add Twilio account info in ENM or a bridging system.
• Possibly write a script that listens to PME-generated emails or SNMP traps and sends them to Twilio.

With TextBolt, you instead:

1. In your TextBolt account, ensure you have:
   • A sender ID (e.g., DataCenter Alert).
   • 10DLC-compliant registration (if in the U.S.).
2. Treat TextBolt as an email gateway:
   • Every SMS destination becomes an email-style address:
     • 15551234567@sendemailtotext.com → SMS to +1 555-123-4567 (on-call operator).
3. In the same ENM notification rule, add that email-SMS address as a recipient:
   • Recipients:
     • ops@datacenter.company.com
     • noc-team@datacenter.company.com
     • 15551234567@sendemailtotext.com

That’s it. PME still:

• uses the same alarm engine,
• uses the same SMTP server,
• uses the same notification rule engine.

It doesn’t need to know Twilio exists. It just sends one more email, to a TextBolt-powered address.

Step 4: What the Operator Sees

When the alarm activates, the operator’s phone receives an SMS like:

[DataCenter Alert]
Overload on Main Feeder (Location: Main Switchboard)
Timestamp: 2026-05-12 08:30:00
Severity: Critical

The email recipients see the same content in their inbox, formatted for their email-based tools.

If the operator replies, TextBolt can route that reply back into email (or a defined workflow), depending on your TextBolt configuration.

Why This Matters for Legacy and OT Stacks

For many Schneider Electric and EcoStruxure customers, the stack is a mix of:

• Old-generation hardware (sub-station meters, legacy PME-enabled servers).
• Windows-centric OT software that doesn’t speak REST APIs natively.
• Operations teams that are expert at configuring alarms, views, and SNMP, but not at maintaining Twilio SDKs.

By using TextBolt behind PME’s email-notification layer, you get:

• No Twilio SDK in OT code. PME never needs to talk Twilio directly.
• No custom code to bridge PME to Twilio. You avoid maintaining a separate SMS-bridge script.
• No SMS-configuration complexity inside PME. You configure SMS by adding an email address, not by configuring third-party SMS credentials.
• Easy 10DLC testing and compliance. TextBolt can handle carrier-specific registration and compliance, while your PME focus stays on power-system behavior.

In other words: you keep the OT stack as-is, and shift the SMS complexity into the gateway layer.

Example: Extending SMS Coverage to Old-Generation PME Models

Suppose you have:

• PME-2012 running on an older database server, used for a legacy manufacturing plant.
• The Event Notification Module is enabled but your team has never used SMS because “Twilio is too much hassle for this site.”

With TextBolt, ramping up SMS here is trivial:

1. Do not upgrade the PME version.
2. Do not install any SDKs on the old server.
3. Configure the existing ENM notification rules to send emails to:
   • plant-ops@company.com
   • 15559876543@sendemailtotext.com (local maintenance lead).

Now, even that old-generation PME instance can send SMS alerts, without any code change, without touching Twilio, and without exposing sensitive API keys on a legacy OT server.

What This Means for EcoStruxure and OT Strategy

From an EcoStruxure and OT-strategy perspective, using TextBolt with PME-based Event Notification fits a clean pattern:

• PME and Alarms stay focused on power-system behavior.
• Event Notification Module stays focused on who gets notified and when.
• TextBolt takes care of SMS delivery and carrier compliance (including 10DLC).

This separation of concerns is especially valuable when:

• You want consistent SMS behavior across multiple PME instances (legacy and new).
• You want minimal blast radius if SMS providers, APIs, or compliance rules change.
• You want to avoid baking vendor-specific SMS logic into your OT stack.

Send PME Alerts as SMS Without Code

In short:

• PME’s Event Notification Module already supports SMS, but it leans on Twilio today.
• That means you either configure Twilio in ENM or build a side integration, which adds complexity and lock-in for OT-heavy environments.
• TextBolt lets you bypass that entirely: you keep PME’s email-notification rules, and simply add TextBolt-powered email-SMS addresses as recipients.

The result:

• No Twilio SDK.
• No code changes in PME or surrounding OT systems.
• No SMS-specific configuration inside your OT stack.

You get SMS alerts for critical power events the way EcoStruxure should: focused on alarms, views, and schedules, while TextBolt quietly handles the 10DLC-compliant delivery part.

For Schneider Electric customers, that’s a rare win: advanced SMS alerting without modernizing your OT stack.