Skip to main content

SPM Campaign Launch Process for O&R and CECONY

Srikanth Chinnammagari
Organization
Convey Logo

SPM Campaign Launch Process for O&R and CECONY

This knowledge base article outlines the steps for launching a Storm Management Campaign (SPM Campaign) for Orange and Rockland (O&R) and CECONY.

Overview

ConEdison will raise a support ticket requesting the MB team to send SMS messages to their customers.


Prerequisites

Before you begin, ensure you have the following:

  • CECONY/O&R Production and QA Enterprise Portal access 
  • Production and QA Database access 
  • External and Internal SFTP access

Step 1: Preparation Work

1.1 Verify Auto-Enrollment File

The team will receive an Auto-enrollment file (customer master data file) through the automated SFTP process.

Note: It is common practice to use the latest existing records received in the weekly auto-enrollment file.

SFTP Paths:
        QA External SFTP Path: 
                10.10.3.81 > 10521_61302 > sftpData > ToMB > Autoenroll

        Prod External SFTP Path: 
                10.10.3.81 > 10521_61303 > sftpData > ToMB > Autoenroll

Validation
Verify that the file has been successfully dropped into the SFTP location.

Example:

1.2 Verify File Ingestion into Database
Once the file is received, the data is initially ingested into a temporary table before being inserted into the primary customer master data table.

Primary Tables:
        O&R: 
                conedoutage.customermasterdate_oru

        CECONY: 
                conedoutage.customermasterdata_cecony

Validation
Check that the records are successfully ingested into the temporary and primary tables.

Example:

1.3 Verify Email Notification
An automated email notification is generated once records are successfully ingested into the primary tables.

Validation
Check that the records are successfully ingested into the temporary and primary tables.

Example:

Step 2: Create Storm Event (If Not Yet Created)

Note: The client typically creates the Storm event in the portal before MB launches the campaign on their behalf.

2.1 Access the Enterprise Portal
Log in to the appropriate Enterprise Portal environment.

Portal URLs 
           PROD O&R MB URL – Login Form
           PROD CECONY URL – Login Form
           QA O&R MB URL – Login Form
           QA CECONY MB URL – Login Form

2.2 Create the Storm Event

  1. Navigate to the Storm Management tab. 

  2. Click Add New Storm. 

  3. Enter the following information:
           Storm Date
           Begin Date
           End date

  4. Select the script specified in the support ticket.

  5. Select the appropriate When option.

  6. Click Add New Storm.

Validation
The Storm event can also be validated in the database using the following table:
conedoutage.stormdetails

Once created, the Storm Created status will appear in the portal.

Step 3: Launch Seed Test

Procedure: 

  1. Click the Pencil/Edit icon for the Storm event.

  2. Scroll down to the Storm details section.

  3. Enter the seed phone number provided by the client.

    Note: Multiple phone numbers may be entered using commas (,).

  4. Click Launch Seed.

  5. Once the confirmation pop-up appears, click Close.

Step 4: Add Regions

Procedure: 

  1. Select the required regions.

  2. Click Update Storm Record.

    Note: If the client initially set up the SPM campaign, the MB team may edit the regions as needed.

Step 5: Load Data Queue

Procedure: 

  1. Click the Pencil/Edit icon again.

  2. Scroll down to the Storm details section.

  3. Click Load Data Queue.

  4. Verify that the Storm status changes to: Loading Queue

  5. Refresh the browser until the status changes to: Ready to Launch Campaign

    Note: The MB team monitors the queue loading process to ensure the counts align with the “Total SMS” count displayed in the UI.

Step 6: Launch the Campaign

Procedure: 

  1. Click the Pencil/Edit icon.

  2. Click Launch Campaign.

  3. Verify that:
    A green banner message appears stating: Campaign has been launched
    The status changes to: Campaign Launched

Step 7: Retrieve Report Data

Note: Once the Storm event is completed, the results are automatically included in the 30-minute reporting files sent to the client. Occasionally, the client may request an additional report.

7.1 Create the Storm Event
Download and use the following template: Heatwave_SPM_Reporting_20250623.xlsx

Important Note

Download the template and avoid modifying the original file.

7.2 Retrieve Storm ID

Run the following query:
          
      SELECT * FROM conedoutage.stormdetails ORDER BY id DESC;

Take note of the ID corresponding to the Storm event created.

7.3 Retrieve SMS Counts Per Region

Run the following query:

SELECT count(*), region_vch FROM conedoutage.spm_sms_messages WHERE       storm_id_int = 'storm ID' AND pulled_int = '1' GROUP BY region_vch;

Note: Replace 'storm ID' with the actual Storm ID obtained from the stormdetails table.

7.4 Retrieve First and Last Message Time

Run the following query:

SELECT * FROM conedoutage.spm_sms_sent ORDER BY created_at_utc DESC;

7.5 Monitor SPM Message Counts

Run the following query:

SELECT count(*) FROM conedoutage.spm_sms_sent WHERE id > '{enter Id}';

Note: Replace {enter Id} with the appropriate Storm-related ID.

Step 8: Upload and Send Report

Procedure: 

  1. Access the SharePoint folder: O&R SPM Sharepoint folder

  2. Create a new folder.

    Best Practice: Name the folder using the following format:
    OpCo SPM StormName Date

  3. Upload the completed report file.

  4. Inform the client that the report has been uploaded.

References & Related Tickets

For internal team use: Reference past KT session, Zendesk ticket, and Confluence page related to this article.

Related to

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk