Software Configuration
Configuration for the AMR and AVL components of the Oracle Utilities Network Management System MultiSpeak Adapter comes from the following sources:
• CES_PARAMETERS database table
• Oracle Utilities Network Management System Configuration Rules
Support for Encrypted Configuration Parameters
Some configuration parameters that are stored in the CES_PARAMETERS database table contain sensitive information, such as authentication credentials, which should be protected. To protect this data, the VALUES column can be encrypted using Oracle WebLogic Server encrypt utility. This utility encrypts cleartext strings for use with Oracle WebLogic Server. Its output can then be used to populate values in CES_PARAMETERS database table.
For detailed information see "encrypt" in the Oracle WebLogic Server Command Reference.
AMR Configuration Parameters
Entries in the CES_PARAMETERS database table for the AMR component of the Oracle Utilities Network Management System MultiSpeak Adapter should have value 'AMRInterface' in the APP column. Column ATTRIB should contain name of the configuration parameter and column VALUE its value.
The following table describes the general configuration parameters.
Parameter | Description |
|---|
config.allow_update_non_amr | Allows meter updates to be processed for meters that are not marked as AMR-enabled. This is only applicable to the incoming MeterChangedNotification messages. Default: false |
config.always_process_unsolicited | Process received unsolicited meter status (per multispeak.unsolicited_meter_statuses parameter) as unsolicited even if there is an outstanding meter status request for the same meter. Default behavior is that if received meter status was used to satisfy outstanding meter status request it will not be processed as unsolicited message. Default: false |
config.amr_vendor | AMR vendor. Supported AMR vendors: • multispeak: MultiSpeak-compliant AMR system. This parameter is required. Default: multispeak |
config.bellwether_query_type | Query type for periodic read of bellwether meters. The query type defines the list of values to be read from meters (see the multispeak.query_type parameter 15 for details). Supported Query Types: • voltage: query voltage at the meter |
config.bellwether_read_interval | Reading interval for bellwether meters in seconds. Default: 900 seconds |
config.bellwether_scada_name | Name of the entry in the SCADA_IDS table to be used to report measurements read from bellwether meters. The measurements are reported through the SCADA component of this adapter so the entry in the SCADA_IDS table must have the ADAPTER_TYPE "MULTISPEAK". Default: AMR |
config.credentials | Absolute path to the file containing user credentials the adapter will use to communicate with Oracle Utilities Network Management System. Either this parameter or both config.username and config.password parameters should be provided. If all are present, then the config.username/config.password pair is used. |
config.enabled | Enables AMR processing. Default: false |
config.ignore_unknown_meter_statuses | If enabled, then received meter status updates that correspond to the UNKNOWN meter status will be ignored. Otherwise such meter status updates will be recorded in the AMR_CU_METERS and AMR_CU_METERS_HISTORY tables and used to satisfy pending meter status requests. Note: UNKNOWN meter status will not be used to satisfy pending meter status requests; the system will attempt to ping the meter again until it receives an ON or OFF response or the configured number of attempts is exhausted. Default: true (enabled) |
config.load_side_query_type | The list of values to be read from the meters, matching the query_type parameter. The query type defines the list of values to be read from meters (see the multispeak.query_type parameter on page 15 for details). |
multispeak.load_side.<0|1> | The load side status translation map, either CONNECTED or DISCONNECTED. If the received meter load side status is not configured it will be treated as CONNECTED. |
config.max_meter_status_age | Period of time in seconds after which meter status information received from AMR system is considered stale and has to be obtained from the AMR system again. Default: 300 seconds |
config.max_ping_request_age | If difference between the current time and ping request time is greater than value of this parameter then the request is too old to be sent to the AMR system. Such requests are marked as completed in the AMR_RESPONSES table. The value is defined in seconds. Default: 3600 seconds |
config.max_ping_response_age | If the difference between current time and the unsolicited ping response time is greater than value of this property, then the response is too old to be sent to the NMS. Such responses are removed from the AMR_RESPONSES table. Default: 3600 seconds |
config.max_pings_per_cycle | Maximum number of meter ping requests to be processed in one cycle (cycle duration is defined by the config.ping_request_interval parameter). Default: 10000 |
config.max_responses_per_msg | Maximum number of meter ping responses to be sent to NMS in a single message. The allowed range for this parameter is [100...10000]. Default: 1000 |
config.message_credentials_required | If this parameter is set to false then credentials for authenticating with NMS are taken from the MultiSpeak header of the incoming message. If this parameter is set to false and credentials are not present in the MultiSpeak header of the incoming message then username and password configured in the adapter is used to authenticate with NMS. Valid Values: true|false. Default: true |
config.multiphase_meter | Comma-separated list of possible values of the AMR_CU_METERS.METER_PHASES column that indicate a multiphase meter. |
config.nms_url | URL for accessing Oracle Utilities Network Management System. If this parameter is not provided then it is assumed that MultiSpeak Adapter is deployed on the same Managed Server as cesejb.ear. This parameter is specified for each component of the adapter, but only one value is actually used; all components will connect to the same NMS instance. The value is taken from the first enabled component according to the following order of precedence: 1. SCADA 2. AMR 3. AVL Note: This parameter replaces the Foreign JNDI configuration used in earlier versions of the Adapter. |
config.password | NMS user password. Value of this parameter should be encrypted. |
config.phase_voltage_query_type | Query type for reading voltage value of the individual meter phases. When using voltage read to determine meter status this query type is used for multiphase meters. The query type defines the list of values to be read from meters (see the multispeak.query_type parameter on page 15 for details). |
config.ping_request_interval | Time interval in seconds between subsequent meter ping requests to the AMR system. Default: 60 seconds |
config.unsolicited_message_deadband | Deadband value in seconds for unsolicited messages reporting same status for a meter. If several unsolicited messages of the same type are received within the deadband then only one of them will be processed. Default: 60 seconds |
config.use_voltage_ping | Use meter voltage read instead of meter ping to determine meter status. Received voltage is compared against configured low voltage threshold value. A voltage value lower than the threshold is interpreted as the meter not having power. For multi-phase meters, voltage on any phase being below threshold means that the meter has no power. Supported Options: • always: always use voltage read • multiphase: only use voltage read for multiphase meters • never: never use voltage read Default: never. |
config.username | Valid NMS username, which has the 'NmsService' role in WebLogic Server. |
config.voltage_query_type | Query type for generic (single phase) meter voltage read. When using voltage read to determine meter status, this query type is used for single phase meters. The query type defines the list of values to be read from meters (see the multispeak.query_type parameter page 15 for details). |
config.write_power_offs_to_db | If set to 'true', the adapter will write unsolicited meter power-off messages received from the AMR/AMI system into the AMR_POWER_OFFS table instead of delivering them to JMService. Default: false |
config.ws_request_timeout | Timeout (in seconds) for web service requests to the AMR system. Request will fails if AMR system does not respond before the timeout expires. Default: 30 seconds |
The following table describes configuration parameters specific to a particular AMR vendor. This could be any MultiSpeak-compliant AMR system.
Parameter | Description |
|---|
multispeak.meter_status.<external status> | This parameter configures mapping between external (MultiSpeak) and internal meter status values. Valid Values: • ON: meter is energized • OFF: meter is deenergized • UNKNOWN: external meter status has no configured mapping. Examples: multispeak.meter_status.Outage=OFF multispeak.meter_status.PowerOff=OFF multispeak.meter_status.PowerOn=ON multispeak.meter_status.Restoration=ON multispeak.meter_status.Instantaneous=UNKNOWN multispeak.meter_status.NoResponse=UNKNOWN multispeak.meter_status.Inferred=UNKNOWN |
multispeak.od_oa.url | This parameter configures the URL of the AMR system web service. Default: https://localhost/multispeak |
multispeak.od_oa.username | Username to use when connecting to the AMR system web service. Default: empty string |
multispeak.od_oa.password | Password to use when connecting to the AMR system web service. Default: empty string |
multispeak.od_oa.header.<attribute> | Used to set the values for MultiSpeak header attributes. For example, the following would set the MultiSpeak header attribute 'Company' to the value 'Oracle':
multispeak.od_oa.header.Company=Oracle |
multispeak.od_oa.soap12 | Indicates the SOAP protocol version to use for communicating with the AMR/AMI system. Valid Values: • true: SOAP version 1.2 will be used. • false: SOAP version 1.1 will be used. Default: false |
multispeak.max_ping_attempts | Maximum number of attempts to ping a meter. Default: 3 |
multispeak.ping_attempt_interval | Number of seconds to wait for reply from the AMR system before resending a meter ping request. Default: 60 seconds |
multispeak.send_meter_number_field | This parameter designates which field in the InitiateOutageDetectionEventRequest message should be used to submit meter numbers to the AMR system. Valid Values: • meterID: meterID element should be used • objectID: objected attribute should be used • meterNo: - meterNo attribute should be used Default: meterID |
multispeak.unsolicited_meter_statuses | Comma-separated list of meter statuses for unsolicited "power up" and "last gasp" messages. Example: multispeak.unsolicited_meter_statuses=Outage,Restoration |
multispeak.max_update_attempts | Maximum number of retries for a MeterChangedNotification request to enable|disable meters. This is only supported when Oracle Utilities Network Management System is integrated with Oracle Utilities Smart Grid Gateway. Default: 3 |
multispeak.update_attempt_interval | Number of seconds the adapter will wait after failure before retrying MeterChangedNotification request to enable|disable meters. This is only supported when Oracle Utilities Network Management System is integrated with Oracle Utilities Smart Grid Gateway. Default: 60 seconds |
multispeak.max_ping_batch_size | Maximum number of meters to be included in a single ping request to the AMR/AMI system. If the number of pending meter pings exceeds this value, then multiple requests will be sent. Default: 10000 |
multispeak.max_read_batch_size | Maximum number of meters to be included in a single read request to AMR/AMI system. If the number of pending meter read requests exceeds this value, then multiple requests will be sent. Default: 1000 |
multispeak.query_type.<query type> | Mapping between the meter read query type requested by NMS and the set of AMR/AMI meter field names to be read. <query type> is the NMS query type (either name of the query type or numeric code). The value of this parameter is a comma separated list of MultiSpeak meter read field names. Supported Query Types: • voltage: generic (single phase) voltage query • phase_voltage: query for phase voltages • load_side: query for load side connection status |
multispeak.field.<known field> | Several values in the incoming messages containing meter readings have well-defined meaning. This parameter is used to map such value to MultiSpeak meter read field names. Recognized <known field> Values: • METER_NUMBER: - meter identifier • READ_TIME: meter reading timestamp. Value of this parameter is a comma-separated list of MultiSpeak meter read field names, which contain the <known field> value. If more than one the listed fields is present in the message at the same time then the list order defines field precedence (fields at the front of the list have higher precedence). |
JNDI Name for JMS Connection Factory
When JMS transport is used this parameter defines JNDI name of the JMS connection factory used for NMS to AMR data flows.
Parameter | Description |
|---|
multispeak.jms_cf_name | JNDI name of the JMS connection factory which should be used for NMS to AMR data flows. Default: ConnectionFactory |
JMS Connection Credentials
These parameters are used if credentials are required to establish connection to JMS server. They are passed to the createConnection method of JMS connection factory.
Parameter | Description |
|---|
multispeak.jms_user | JMS connection username. |
multispeak.jms_password | JMS connection password. |
AMR_LINKS
The AMR_LINKS database table is used to configure communication links to the AMI/AMR system. It is allowed to configure multiple links. The adapter will use the active link with the lowest value in the PRIORITY column. The adapter will not automatically switch to another link if the current link fails. HTTP/HTTPS and JMS links are supported.
For HTTP links WS_URL column is used to specify URL of the AMI/AMR system web service.
For JMS links, the REQUEST_QUEUE and RESPONSE_QUEUE columns are used to specify JNDI names of JMS queues used to send requests to and receive responses from AMI/AMR system.
The value in the TIMEOUT column controls how long the adapter should wait for response from AMI/AMR system (in seconds). This is only applicable to JMS links. The maximum allowed value is 3600 (1 hour).
The value in the PERSISTENT column defines delivery mode for JMS messages. If set to 'Y' then JMS messages are persistent, otherwise they are not persistent. By default, messages are not persistent. This is only applicable to JMS links.
The SITE column should contain the site value, as also used in the CES_PARAMETERS table.
Configuration in this table, if present, overrides existing configuration parameter 'multispeak.od_oa.url'.
Example
INSERT INTO amr_links (id, ws_url, priority, active, site)
VALUES (1, 'http://localhost:8088/mockAMR', 1, 'Y', 'SiteA');
INSERT INTO amr_links (id, ws_url, priority, active, site)
VALUES (2, 'http://localhost:8089/mockAMR', 2, 'N', 'SiteA');
INSERT INTO amr_links (id, request_queue, response_queue, timeout,
persistent, priority, active, site)
VALUES (3, 'queue/AmrRequest', 'queue/AmrResponse', 30, 'N', 3, 'N', 'SiteA');
AMR_LINK_OPS
The AMR_LINK_OPS table can be used to configure JMS transport differently for individual web service operations. If an operation does not have a record in the AMR_LINK_OPS table, then values from the parent AMR_LINKS record are used.
• The LINK_ID column is the foreign key into the AMR_LINKS table.
• The OPERATION column is used to specify web service operation name. Supported operation names:
• PingURL
• GetMethods
• InitiateOutageDetectionEventRequest
• GetSupportedFieldNames
• InitiateMeterReadingsByFieldName
• MeterChangedNotification.
• The REQUEST_QUEUE and RESPONSE_QUEUE columns are used to specify JNDI names of JMS queues used to send requests to and receive responses from the AMI/AMR system.
• The value in the TIMEOUT column controls how long the adapter should wait for response from AMI/AMR system (in seconds). Maximum allowed value is 3600 (1 hour).
• The value in the PERSISTENT column defines delivery mode for JMS messages. If set to 'Y', then JMS messages are persistent, otherwise they are not persistent. By default messages are not persistent.
• The SITE column should contain the site value, as also used in the CES_PARAMETERS table.
Example
INSERT INTO amr_link_ops (id, link_id, operation, ws_url,
request_queue, response_queue,
timeout, persistent, site)
VALUES (31, 1, 'PingURL', 'http://localhost:8088/PingURL', '','',
30, 'N', 'SiteA');
INSERT INTO amr_link_ops (id, link_id, operation, ws_url,
request_queue, response_queue, timeout,
persistent, site)
VALUES (32, 3, 'PingURL', '', 'queue/AmrRequest_PingURL',
'queue/AmrResponse_PingURL', 30, 'N', 'SiteA');
Overriding Configuration Parameters
The MultiSpeak Adapter configuration parameters (in the CES_PARAMETERS database table) can be overridden by setting system properties when starting the WebLogic server where the adapter is deployed.
The format of the Java Virtual Machine command-line argument for setting system property.
-D<component>.<configuration parameter>=<value>
where
• component: MultiSpeak Adapter component the configuration parameter applies to.
Possible values:
• AVLInterface
• AMRInterface
• SCADAInterface
• configuration parameter: configuration parameter name
• value: configuration parameter value
Example
Disable the MultiSpeak adapter's AMR component by setting the AMR component's 'config.enabled' configuration parameter to false.
-DAMRInterface.config.enabled=false
Storing Meter Readings in AMR_RESPONSES Table
If the adapter is used to request meter readings from the AMR/AMI system the received values are stored in the AMR_RESPONSES database table. Product configuration provides single column (VOLTAGE) for storing meter readings. If additional values need to be stored then desired number of columns should be added to the AMR_RESPONSES table and project-specific version of the eclipselink-orm.xml configuration file need to be created. The columns should have type VARCHAR2. The below set of directions should be used to define your project version of this file.
1. In your <project>/jconfig directory, create a subdirectory structure as follows:
<project>/jconfig/override/nms-multispeak-ejb.jar/META-INF/
2. Copy the Product version of the eclipselink-orm.xml file used by MultiSpeak adapter.
Note: This file can be found in the product/jconfig/override/nms-multispeak-ejb.jar/META-INF/ directory.
3. Save the file to the META-INF directory that you created in step 1.
4. In the file you should find the following entry (enclosing entity-mapping tag is omitted) for mapping meter read field "Voltage" to the column VOLTAGE in the AMR_RESPONSES table.
<entity class="com.splwg.oms.interfaces.amr.model.MeterStatus">
<attributes>
<basic name="Voltage" access="VIRTUAL" attribute-type="String">
<column name="VOLTAGE"/>
</basic>
</attributes>
</entity>
5. Add additional <basic> elements for the columns added to the AMR_RESPONSES table. Attribute 'name' defines the name of the meter read field coming from the AMR/AMI system. Attribute 'access' should have value 'VIRTUAL'. Attribute 'attribute-type' should have value 'String'. Nested element <column> defines the database column name.
6. Execute 'nms-install-config --java' to generate new nms-multispeak.ear binary.
AVL Configuration Parameters
Entries in the CES_PARAMETERS database table for the AVL component of the Oracle Utilities Network Management System MultiSpeak Adapter should have value 'AVLInterface' in the APP column. Column ATTRIB should contain the name of the configuration parameter and the column VALUE should contain its value.
The AVL component requires configuration for converting crew location information received from the AVL system into the Oracle Utilities Network Management System coordinate system. Coordinate conversion is done using reference point coordinates that are known for both systems. At least two reference points are required for coordinate conversion to work.
The AVL configuration parameters are described in the following table:
Parameter | Description |
|---|
config.credentials | Absolute path to the file containing user credentials the adapter will use to communicate with Oracle Utilities Network Management System during initialization process. Either this parameter or both config.username and config.password parameters should be provided. If all are present then config.username/config.password pair is used. |
config.username | Valid NMS username, which has the 'NmsService' role in WebLogic Server. |
config.password | NMS user password. Value of this parameter should be encrypted. |
config.nms_url | URL for accessing Oracle Utilities Network Management System. If this parameter is not provided then it is assumed that MultiSpeak Adapter is deployed on the same Managed Server as cesejb.ear. This parameter is specified for each component of the adapter, but only one value is actually used; all components will connect to the same NMS instance. The value is taken from the first enabled component according to the following order of precedence: 1. SCADA 2. AMR 3. AVL Note: This parameter replaces the Foreign JNDI configuration used in earlier versions of the Adapter. |
config.message_credentials_required | If this parameter is set to false then credentials for authenticating with NMS are taken from the MultiSpeak header of the incoming message. If this parameter is set to false and credentials are not present in the MultiSpeak header of the incoming message then username and password configured in the adapter is used to authenticate with NMS. Valid Values: true/false. Default: true |
avl.num_reference_points | Number of configured reference points |
avl.reference_point<N>.x | X coordinate of the reference point N in the Oracle Utilities Network Management System coordinate system |
avl.reference_point<N>.y | Y coordinate of the reference point N in the Oracle Utilities Network Management System coordinate system |
avl.reference_point<N>.longitude | Geographic longitude of the reference point N |
avl.reference_point<N>.latitude | Geographic latitude of the reference point N |
avl.xy_scale | Number of decimal points to use when rounding X/Y coordinates |
avl.lat_long_scale | Number of decimal points for rounding longitude/latitude coordinates |
config.enabled | Enables AVL processing Default: false |
Credentials Files
Credentials files may be used to configure usernames and passwords to be used by the parts of the adapter that communicate with the Oracle Utilities Network Management System.
Credentials files should only be readably by the operating system account under which application server is running.
The format of a credentials file is described in the following table:
Property | Description |
|---|
nms.username | Valid NMS username, which has the NmsService role in WebLogic Server. |
nms.password | NMS user password |
The following illustration shows a sample credentials file.
#
nms.username=amr
nms.password=amr-user-password
Oracle Utilities Network Management System Configuration Rules
Below is the list of configuration rules in the Oracle Utilities Network Management System, which control AMR-related functionality. These rules are not directly used by the Oracle Utilities Network Management System MultiSpeak Adapter.
amrInterfacesEnabled
This rule enables AMR processing in JMService. Its value indicates the AMR processing types that are available. AMR processing is disabled if this rule is set to 0 (default value).
Available types of AMR processing:
• 1 - Outage detection
• 2 - PSO verification
• 4 - PDO verification
• 8 - Restoration verification
• 16 - Manual AMR processing
• 32 - Unsolicited power-up processing
The rule value is a bitmask, which allows any combination of AMR processing types to be enabled. For example, if you want to enable outage detection (1) and restoration verification (8) processing, you would set the rule to 9.
meterOffThreshold
Maximum probability of meter having power when meter is still assumed to be "off". The default value is 0.
meterOffTroubleCode
Trouble code to be used when a call should be created because of information received from AMR system.
meterOnThreshold
Minimum probability of meter having power when meter is still assumed to be "on". The default value is 100.
meterQueryThreshold
This parameter is used to determine if a meter can be queried when an active request exists. When a new request is made, existing requests will be evaluated to see if any contain meter(s) from the new request. If a match is found, and the difference between the time the request was received and current time is less than value of this rule in seconds, that meter will be rejected from the new request. If set to -1 (default value), this rule will not be enforced.
meterPingPercentage
This parameter governs the percentage of meters to ping for an AMR action. When set to 100, it will ping all AMR meters downstream from the outage device. When set to -1, it will ping one AMR meter on each SND. When set to any other number between 1 and 99, JMService will attempt to ping the specified percentage of meters for each transformer affected by the outage (the resulting number of meters is rounded up so that at least one meter per transformer is pinged). It is possible to configure this rule differently for different device classes. The default value of this rule is 100.
powerOutWaitPeriod
RULE_VALUE_2 defines the wait period in seconds for AMR-reported power outs. The system will hold onto AMR-reported power out messages for the specified period of time before making a determination if the power out should be discarded, grouped into an existing outage, or if it should create a new outage.
See rules amrDeadband, momentaryAmrDeadband, and suppressAmrIncidents for the conditions that could cause power out messages to be discarded.
Grouping of incidents created from power out messages is done according to the grouping rules applicable to the trouble code specified by the meterOffTroubleCode rule.
RULE_VALUE_1 controls whether waiting power outs should be discarded if unsolicited power up message is received for the same meter or another meter on the same device.
Possible values:
• none - do not discard
• meter - discard only for the affected meter<
• meter_device - discard for all meters downstream from the same meter device as the meter that received power up. Meter device is determined from the METER_DEV_CLS and METER_DEV_IDX columns in the IVR_CES_CUSTOMERS database view
useMeterTimeForDetection
This configuration rule determines if meter read time reported by AMR system should be used as call time for incidents created by outage detection functionality.
Valid values:
• no - Meter read time will not be used, instead current system time will be used (this is the default behavior)
• yes - Meter read time will be used
If the rule_value_2 is greater than 0, and the difference between the current time and the meter read time is greater than the number of seconds specified by rule_value_2, then the meter read is too old for outage detection. The default value is 3600 seconds (1 hour).
useMeterTimeForRestoration
This configuration rule determines if meter read time reported by AMR system should be used to adjust outage restoration time as part of outage restoration verification functionality. Outage restoration time is only updated if restoration time calculated from AMR data is earlier then the current restoration time.
Valid values:
• no - outage restoration time will not be modified
• latest - outage restoration time will be updated with the latest meter read time amongst the meters which reported power on for the restored outage (this is the default behavior)
• earliest - outage restoration time will be updated with the earliest meter read time amongst the meters which reported power on for the restored outage
• percentile - outage restoration time will be updated with the earliest meter read time which covers the desired percentile of meters which have reported power on. Percentile value is specified using rule_value_2 field. It should be in the range from 1 to 99 (inclusive).
Meter read times preceding outage start time or past current time are ignored.
Example of 'percentile' setting.
rule_value_1 = 'percentile'
rule_value_2 = 50
This configuration corresponding to using median value from the all meter read times for meters, which reported power on. Given following four meter read times
00:00:10
00:00:11
00:00:20
00:00:30
the median value would be 00:00:11 (second value out of four).
meterRequestSendDelay
This configuration rule is used to control how long the outage prediction engine should wait before sending a meter ping request to the MultiSpeak adapter. This rule is only applicable for PSO Verification, PDO Verification, and Restoration Verification requests.
meterRequestTTL
This configuration rule is used to control the "time-to-live" (TTL) for meter ping requests. This is the period of time NMS will wait for a responses from AMR system. Automated meter ping requests (PSO Verification, PDO Verification, and Restoration Verification) are considered completed when TTL expires. Manual meter ping requests, which were not explicitly completed or cancelled by the user, are automatically cancelled when TTL expires.
TTL is configurable per request type. It can either be a fixed value (for example, the PSO Verification request can remain active for 15 minutes) or it can be calculated based on the number of meters in the request combined with minimum and maximum values. If TTL is set to 0, then automated meter ping requests remain active until the first response is received. Manual meter ping requests in this case remain active until explicitly completed or canceled by the user.
meterPingSuppress
This configuration rule can be used to suppress sending meter ping requests to the AMR system based on the request type.
writePowerOffsToDB
This configuration rule determines if JMService will create a new incident when a power-off message is received from the AMR system.
If this rule is set to "no", then incidents for power-off messages will be created by JMService. This is the default behavior.
If this rule is set to "yes", then, instead of creating an incident, JMService will insert a record into the AMR_POWER_OFFS database table. This record will contain the meter id and power-off timestamp. An external process is expected to read the table and process new entries.
For example, such a process can obtain customer information associated with the meter id and insert a record into the TROUBLE_CALLS table so that the NMS IVR Adapter will process it and create a new incident. This allows more flexibility to the process of creating incidents from AMR-reported power-off messages.