Scenario 1: CC&B + MWM + WAM v1.9.1.x
In this scenario, the integration product coordinates processing between three Oracle Utilities application products based on configuration settings described. All three application products and the integration product must be configured to enable this business scenario. This section of the document describes the configuration required for one of the application products.
In addition to the business processes orchestrated by the integration product, you must also configure customer and asset data synchronization between Oracle Utilities Customer Care and Billing and Oracle Utilities Work and Asset Management v1.9.1.x.
Complete the following general steps in Oracle Utilities Customer Care and Billing to configure the integration:
1. Set up a synchronization database link between Oracle Utilities Customer Care and Billing and Oracle Utilities Work and Asset Management v1.9.1.x to support synchronization of customer and asset data.
2. Configure the admin tables to support integration.
3. Configure message senders to pass messages with integration layer.
Configure Oracle Utilities Customer Care and Billing for Scenario 1
1. Configure customer and asset data synchronization.
• Establish a database link
• Create integration triggers
• Set up and schedule background processes
2. Map to Plant.
3. Configure administrative menu tables.
• Characteristic Type
• Algorithm
• Field Activity Type
• To Do Roles
• Slot Group
• Customer Contact Type
• Service Provider
• Notification Download Type
• XML Application Integration (XAI)
• Notification Download Profile
• Field Activity Integration Algorithm
• Feature Configuration
• Dispatch Group
• Field Service Control
4. Configure main menu tables.
• Stock Location
Configuring Customer and Asset Data Synchronization
You must synchronize all customer and service point data from Oracle Utilities Customer Care and Billing to Oracle Utilities Work and Asset Management v1.9.1.x in order for the rest of the integration between these products to function correctly.
Set up Feature Configuration as described in this guide before you run data synchronization processes.
Synchronization Schedule
Schedule the processes so that the synchronization of data is done at regular intervals based on your business requirements. If the customer and service point data is not kept up to date you may experience errors within the integrated business processes included within the Implementation Guide product.
Mapping to Plant
One important decision to make about the integration and mapping is how to map Oracle Utilities Customer Care and Billing to Plant in Oracle Utilities Work and Asset Management v1.9.1.x.
Note: You cannot define multiple plants in Oracle Utilities Customer Care and Billing if Oracle Utilities Mobile Workforce Management is part of your integration.
Multiple Plants
The integration between Oracle Utilities Customer Care and Billing and Oracle Utilities Work and Asset Management v1.9.1.x is structured to support multiple plants in Oracle Utilities Work and Asset Management v1.9.1.x (within one database schema). The integration between Oracle Utilities Work and Asset Management v1.9.1.x and Oracle Utilities Mobile Workforce Management does not support multiple plants.
The intent of setting up multiple plants is to segregate the data so that within a single database instance users signed into Plant 01 cannot see records in Plant 02 and so on. The plant column is a primary key on all Oracle Utilities Work and Asset Management v1.9.1.x database tables.
In most cases where multiple plants are used, the data is being segregated by organization or geographic location. For example, a client may use a single database instance for two maintenance organizations in different parts of a state - each location may be its own plant. In another example, a client in a single geographic region may segregate the gas and electric data into different plants. For the latter, a single Premise in Oracle Utilities Customer Care and Billing (with both gas and electric Service Points) must have two corresponding Asset records in Oracle Utilities Work and Asset Management v1.9.1.x - one for each Plant. The associated Service Point for gas only resides in the Oracle Utilities Work and Asset Management v1.9.1.x Plant for gas, and the Service Point for electric only resided in the Oracle Utilities Work and Asset Management v1.9.1.x Plant for electric.
Because a multiple plant configuration impacts whether one or more Asset records need to be created for a single Premise record, the value for Plant must be defined only at the Service Point in Oracle Utilities Customer Care and Billing. The Premise and Account records associated to the Service Point use the value for Plant designated on that Service Point.
Mapping in Oracle Utilities Customer Care and Billing
Oracle Utilities Customer Care and Billing supports several ways to define plant. Based on your business requirements, define the Plant Source and Plant Value option types in Feature Configuration according to the following:
Single Plant Configuration
Plant Source Option Type: Feature Configuration (FECO).
Plant is defined in the Plant Value option type in Feature Configuration.
Plant Value Option Type: Enter a value for the plant such as PL1 in the Value column.
Note: In Oracle Utilities Work and Asset Management v1.9.1.x, the Plant field is only 3 characters long.
Multiple Plant Configuration (Service Point)
Plant Source Option Type: Service Point Operations Area (OPAR)
Plant Value Option Type: Enter a Field Service Class in the Value column.
The defined Field Service Class is used to retrieve the Plant Value defined in the Operations Area on the Service Point.
Plant is defined in the Operations Area for the Service Point with Field Service Class = Plant Value defined in Feature Configuration. Use this configuration if you choose to use a separate plant for each Geographic Area or for each Service Type. This is an alternative to using SP Characteristic. Use one configuration or the other. Not both.
Note: Field Service Class and Operations Area must be defined in the CC&B Control Tables.
Configure Service Point for Multiple Plant
1. Navigate to Admin > Operations Area.
2. Define operations areas with values for each plant.
3. Navigate to Admin > Field Service Class.
4. Reference the plant Operations Areas defined in Step 2.
Multiple Plant Configuration
Plant Source Option Type: Service Point Characteristic (SPCH)
Plant Value Option Type: Enter a Characteristic Type in the Value column for the Plant Value Option Type.
The Characteristic Type is used to retrieve the Plant Value defined in the Characteristic on the Service Point. The Characteristic Type must also be defined in the CC&B Control Table and link to the SP Types to be used. Plant is defined in the Characteristic value for the Service Point with Characteristic Type = Plant Value defined in Feature Configuration. Use this configuration if you choose to use a separate plant for each. Service Point Type or another criteria on the service point. This is an alternative to using Operations Area. Use one configuration or the other. Not both.
Defining plant on the SP Characteristic allows for more flexibility. Here there is also space to specify latitude/longitude, SP Type, or any attribute on SP.
Configure Service Point Characteristic for Multiple Plant
1. Navigate to Admin > Characteristic Type.
2. Define a characteristic type with predefined value for plant.
For each plant, enter a predefined characteristic value.
3. Set the Characteristic Entity as Service Point.
4. Navigate to Admin > SP Type > SP Characteristic.
5. Define a SP Characteristic referencing the characteristic defined in Step 2.
6. Design and run a process that populates Plant Characteristic value on every Service Point.
For more information about creating these settings in Oracle Utilities Customer Care and Billing, refer to the Oracle Utilities Customer Care and Billing user documentation titled “Feature Configuration.”
Configure Admin Tables
This section describes unique setup issues specifically related to configuring your system for the integration.
For more information about configuring Oracle Utilities Customer Care and Billing, see the Oracle Utilities Customer Care and Billing User Guide section titled “Setting up the System to Enable FA Integration.”
CIS Division
A CIS division is associated with a jurisdiction. The definition of a jurisdiction is a geographic-oriented entity with unique business rules. For example, if you conduct business in California and Nevada, and each state has different collection rules, you will need a separate jurisdiction for each state. Set up a CIS division for each jurisdiction in which you conduct business.
The codes defined here must exactly match values in the DVM indicated.
Characteristic Types
The following characteristic types must be defined to facilitate the integration.
Feature Configuration
Manage Feature Configuration
1. Navigate to Admin > Feature Configuration.
2. Create new feature configuration with FA Integration as the Feature Type and enter required option types and values for the service provider you have configured for this integration.
3. Populate entries for the applicable options.
Option | Notes |
|---|
Account Relationship Type – Company Contact | This option type indicates the user defined account relationship type code for the contact person. This is an optional field. For this Option Type, the Option Value must be a valid Account Relationship Type defined in the Account Relationship Type Table. Applicable only if integration with WAM is available. No need to set it up for integration between CC&B and-MWM only. |
Allow Forced Appointments | Set to Y if you use MWM appointment functionality. |
Allow Manual Appointment | Set to Y if you use MWM appointment functionality. |
Allow Manual Appointment Cancellation | Set to Y if you use MWM appointment functionality. |
Allow Multiple Reservations | Set this to N. |
Allow Narrowing Of Appointment Window | Set to Y if you use MWM appointment functionality. |
Allow Slot group | Set to Y if you want to pass slot group to MWM for Appointments. If this value is not passed to MWM, Integration reads a default slot group from AIAConfigurationProperties.xml file. The lookup that controls the values of the slot group that is being passed from CC&B is C1_TIME_OF_DAY |
Appointment Java Class Interface | The system provides the java class com.splwg.wfmi.workforce.SPLWFMSystem for real-time appointment logic. Applicable if appointments functionality needed |
Default Days Of Available Appointment | A number defined by the implementation. |
Intermediate Status to Prevent FA Cancel | Create an entry in the option collection for any FA Intermediate Status value that is set to prevent the system from automatically canceling a field activity. |
Intermediate Status To Skip Message | Populate FA Intermediate Status to indicate that field activity is created or updated by an external system. For the base product settings set this value to Created/Changed by external system. |
Message ID Database Sequence Name | Sequence field used in the database to generate message ID. The base application uses CI_WFM_MSGID_SEQ sequence. |
Phone Characteristic | If the Override Phone option is defined, the system overrides the Account Phone Number with value defined as characteristic on the FA. |
Phone Number Type - Business | This option type indicates the user defined business phone number type code. This is an optional field. For this Option Type, the Option Value must be a valid Phone Number Type defined in the Phone Type Table. Applicable only if integration with WAM is available. No need to set it up for integration between CC&B and-MWM only. |
Phone Number Type - Fax | This option type indicates the user defined fax phone number type code. This is an optional field. For this Option Type, the Option Value must be a valid Phone Number Type defined in the Phone Type Table. Applicable only if integration with WAM is available. No need to set it up for integration between CC&B and-MWM only. |
Phone Number Type - Home | This option type indicates the user defined home phone number type code. This is an optional field. For this Option Type, the Option Value must be a valid Phone Number Type defined in the Phone Type Table. Applicable only if integration with WAM is available. No need to set it up for integration between CC&B and-MWM only. |
Plant Source | Mapped to the Plant in WAM. |
Plant Value | Mapped to the Plant in WAM. |
Reservation Characteristic Type | This option is not applicable for this integration. |
Review Hi-Low | If you do want to use invoke Hi/low review for meter reads passed from an external system, set this option to Y. |
Service Provider | Service Provider defined for integration layer |
To Do Type for Negative Acknowledgment | To Do Type used to create a To Do Entry when a negative acknowledgment is received. The example provided with the system - TD-FARSP To Do Type |
Feature Configuration - Messages
If the feature exists to interface with an external system, define the mapping between error and warning codes in the external system and our system.
1. Navigate to Admin, Feature Configuration and open the Messages tab.
2. For each message that may be received from an external system, define the External Message Category and External Message Code to identify the message.
3. Map the exact contents of the ExernalMessageCode received from Oracle Utilities Mobile Workforce Management or Oracle Utilities Work and Asset Management v1.9.1.x to the External Message Code defined on the Messages tab in Feature Configuration.
A corresponding message must be defined in the system message tables. For each message, identify the Message Category and Message Number. The Message Category for new messages is 90000 by default. Numbers 90000 or higher are designated for custom use so as to avoid being overwritten in an upgrade.
FA Type
When you set up your field activity types, keep in mind that a field activity cannot have more than 7 steps if it will be completed by an external system.
Following is the list of supported FA Types:
Additional configuration maybe needed to support other order types.
Note that appointments are not supported in Oracle Utilities Work and Asset Management v1.9.1.x, so unless Oracle Utilities Mobile Workforce Management is part of the integration, Appointment Booking should not be set to Required for Dispatch.
To Do Type/ To Do Role
Create the To Do Type, To Do Role, and Error Message (as needed) to be used to create the following:
Warn the user when multiple accounts are linked to a Service Point (To Do Entry).
Appropriate To Do roles must be created to handle To Do entries created for this To Do Type coming from the external systems. Navigate to the To Do Type portal under the Admin menu to create this role.
Customer Contact Class and Type
Define the customer contact class and type to be used when Oracle Utilities Work and Asset Management v1.9.1.x sends a customer information creating customer contacts for the following events:
• Extracting customer data updates
• When service requests become field activities
Navigate to the Customer Contact Class and Customer Contact Type modules under the Admin menu to make these updates.
To Do Role for Customer Contact
Create an appropriate To Do role to receive To Do entries for incoming messages from the external system. Oracle Utilities Work and Asset Management v1.9.1.x sends Customer Contact and To Do information to Oracle Utilities Customer Care and Billing when customer or service point information is updated for the following events:
• Extracting customer data updates
• When service requests become field activities
The value of meter read source is controlled within the configuration file under the ABCS Name and Property Name ToDoRole.
Bill Charge Line Type
Bill charge line types simplify the creation of billable charges in Oracle Utilities Customer Care and Billing. Each line type contains values that are defaulted onto the line details associated with the uploaded billable charges.
The codes defined here must exactly match values in the DVM for the invoice charge line type code indicated.
Item Type
Items are any type of equipment, other than meters. Every item has an item type that defines characteristics common to all items with this type.
The codes defined here must exactly match values in the DVM for item type code indicated.
Meter Configuration Type
Every meter configuration must reference a meter configuration type. The meter configuration type indicates the valid (required or optional) unit of measure and time of use registers for the configuration.
The codes defined here must exactly match values in the DVM for meter configuration type indicated.
Meter Type
Every meter references a meter type. The meter type defines the type of service and common characteristics shared by its meters. The codes defined here must exactly match values in the DVM for meter type code indicated.
Operations Area
When you set up a service point, define the operation areas that manage its fieldwork.
The codes defined here must exactly match values in the DVM for disconnect location code indicated.
Disconnect Location
When a service point is disconnected from the supply source, a disconnect location must be specified. This location defines where service was severed. It also controls the type of field activity generated to reconnect service.
The codes defined here must exactly match values in the DVM for disconnect location code indicated.
Meter Read Source
The FA Completion process populates the Meter Read Source on meter reads passed from the workforce management system. In order to use the base product FA completion, create this meter read source.
The value of meter read source is controlled within the configuration file where:
ABCS Name = ProcessWorkOrderCompleteOUMWMUtilitiesReqABCSImpl
Property name = Default.MeterReadSource
FA Integration Algorithm
To integrate with external systems, create an algorithm for FA Integration.
Set the first two parameters as per your business practice. Use FA ID Characteristic Type defined for this integration (see Characteristic Types section).
Information About this Algorithm Type
This FA integration algorithm creates Notification Download Staging (NDS records) to notify an external system if an FA is created, changed or canceled.
For each NDS record created
• The service provider (SPr) on the external system for the dispatch group is used.
• The NDS type used is the one associated with the download condition flag value indicated in the details below.
• A context entry is created for the FA ID. This is needed to extract the FA details
• If you populate FA ID Char Type, (parm 1) the FA ID is also linked as a char, enabling you to easily navigate to the FA from the NDS
• A context entry is created for a unique outgoing Message ID for the external system. Message ID is calculated using a DB sequence whose name is referenced in the option Message ID Database Sequence Name on the external system feature config.
• The algorithm creates an NDS as follows:
• FA creation where the Intermediate Status is not in the option Intermediate Status to Skip Message on the external system feature config:
• If the Appt Booking flag on the FA type is Req'd For Dispatch and the Postpone FA Interface After Appt Is Booked (parm 3) is Y and the FA is not associated with an appointment, no message is created. It is interfaced when the appointment is booked. This is the recommended setup for FA Types that require appointment to be booked.
• If the FA type doesn't require an appt for dispatch, a record is created. The download condition is FA Creation.
• For FA cancellation, online or batch, the download condition is FA Cancellation. If the FA is has an appointment and the Appointment Processing using orders (parm 4) is N, a second NDS is created to cancel the appointment.
Certain FA Changes
• Changing the FA type from one that was not eligible to be interfaced to one that is eligible. The download condition is FA Creation.
• Changing the dispatch group on the FA to one that references a different external system sends an FA Cancel message to the previous external system and an FA Creation message to the new external system.
• Populating the appointment period when Postpone FA Interface After Appt Is Booked is Y. The download condition is FA Creation.
• Changing the schedule date. The download condition is FA Rescheduled.
• Completing an FA in Oracle Utilities Customer Care and Billing sends an FA Cancel message. Either the FA Cancellation or the Appointment Cancel using the FA Cancel download condition is used based on the cancel FA rules previously described.
• Other changes besides a change to External ID or Intermediate Status where the Intermediate Status is not in the option Intermediate Status to Skip Message on the external system feature configuration. The download condition is FA Changed.
Note: The external ID and intermediate status fields only change after info is received from the external system so our system does not need to send a message in this case.
• For the situation where many records are generated for the same FA in a short period of time, the algorithm attempts to manage the records. Before creating an FA Cancel or FA Change, the algorithm checks for an existing NDS record for the same SPr and FA ID in Pending or Retry status
For FA Cancel
• If an FA Create message is found, it is canceled and no new message is created.
• If an FA Change message is found, it is canceled and a new FA Cancel record is created.
• If no other message is found, a new FA Cancel record is created.
For FA Change
• If an FA Create or an FA Change message is found, no new record is created.
• If no other message is found, a new FA Change record is created.
• If Create Log Entry (parm 2) is Y, an FA log record is created for the following events:
• Status change; log type is FA Status Change
• Intermediate status change; log type is FA Intermediate Status Change
• External ID change; log type is FA External ID Change
• Appt period change (and populated); log type is Appointment Booked
• Appt period reset; log type is Appointment Canceled
Dispatch Group
A dispatch group is a logical group of representatives located at an operations area. When a field activity is created, the system assigns it to a dispatch group based on the type of activity, the type of service point, and the operations area that manages the service point.
Create a dispatch group to be used for field activities that are to be integrated with the other participating applications.
The codes defined here must exactly match values in the DVM for Dispatch Group indicated.
Representative
A representative is the individual (or equipment) that performs field activities. This is the Representative to be used when Oracle Utilities Mobile Workforce Management or Oracle Utilities Work and Asset Management v1.9.1.x sends an order completion message to Oracle Utilities Customer Care and Billing.
Add Representative to the Dispatch Group you are using for the integration layer.
Add this value to AIAConfigurationProperties.xml file according to the following example:
Service Point Type
Every service point must reference a service point (SP) type. The SP type controls almost all aspects of the service point behavior (for example, the type of field activity that may be dispatched to it, the type of service agreement that may be linked to it, the type of meter that may be installed at it).
Create the service point types required by your business and populate the necessary information.
Billable Charge SA Types
Create a SA Type to be used for the creation of a Billable Charge SA if the account does not have an existing billable Charge SA.
The codes defined here must exactly match values in the AIAConfigurationProperties.xml file indicated.
Billable Charge SA Start Option
If a SA Start Option is needed to create a Billable Charge SA, make sure this is also created in Oracle Utilities Customer Care and Billing.
The code defined here must exactly match values in the AIAConfigurationProperties.xml file indicated. This is an optional value. If your implementation does not use SA Start option, leave it blank.
Field Service Control
In order to ensure that the appropriate dispatch group is referenced on the appropriate field activities, set up field service control records to indicate the default dispatch group. A record must be created for every combination of operations area, SP type and the previously defined field activity type(s).
Stock Locations
A stock location is a physical or logical location at which meters and/or items are stored while they are not installed at a service point.
The codes defined here must exactly match values in the AIA configuration file for the Item and/or Meter Stock Location Codes indicated.
Note: Mixed case, hyphens and spaces cannot be used in Oracle Utilities Mobile Workforce Management code tables. This limitation affects the Oracle Utilities Customer Care and Billing values passed to Oracle Utilities Mobile Workforce Management such as meter badge numbers. Make sure your implementation is using all capital letters for badge numbers in Oracle Utilities Customer Care and Billing.
Slot Group
The slot group in Oracle Utilities Customer Care and Billing application is used to indicate the time of day for which the appointment is needed. This maps to the Appointment Booking Group in Oracle Utilities Mobile Workforce Management . It is controlled by lookup C1_TIME_OF_DAY.
Geographic Type
If your company uses geographic coordinates, you may setup a geographic type for each type of geographic coordinate you capture on service points. This information is extracted from Oracle Utilities Customer Care and Billing when a field activity is created or updated and passed to Oracle Utilities Mobile Workforce Management.
The codes defined here and used on service points must exactly match values in the AIA configuration file for the geographic coordinates.
Configure Notification Download Staging
Configuring CCB to Process Activities Using Middleware
The following provides information for processing activities using middleware.
Integration between Oracle Utilities Customer Care and Billing and the Field Work Process Integration Pack is provided by processing for NDS records in Oracle Utilities Customer Care and Billing.
Message Senders and Message Route Types specified in Oracle Utilities Customer Care and Billing are not used in the integration. Instead, XSL transformations are performed in the integration layer. The C1FAIntExtOrderCreateUpdateCancel.xsl is directly called by the ProcessNDSRecordOUCCBUtilitiesEBF integration composite.
Configure NDS Records Processing
To configure this processing in Oracle Utilities Customer Care and Billing:
1. Navigate to Admin > Notification Download Profile.
2. Search for and select Fieldwork PIP External System (SOA).
3. Set the Processing Method field to SOA for Create/Update/Cancel entries.
Leave the XAI Route Type section blank.
Additionally, the XAI Download Staging (XDS) table is not used to store messages. The FA Response sent to Oracle Utilities Customer Care and Billing from Oracle Utilities Mobile Workforce Management or Oracle Utilities Work and Asset Management v1.9.1.x (asynchronous business response) was formerly recorded on the XDS table as a response. Now, responses are not stored in the table, but they can be viewed from the SOA Enterprise Manager.
Please refer to
Chapter 22:
Processing CC&B NDS Records Using Middleware/BPEL for more information, performance tuning details and customization details. Methods of using alternative transformations are described in the
Customization Techniques section.
Configuring Messages (All Processing)
Configuring messages involves the following:
Create an HTTP Message Sender for Appointments
Create a new Message Sender for appointments which points to the CC&B Requester ABCS for the Appointments integration point.
1. Navigate to Admin, Message Sender.
2. Enter a unique Message Sender and Description.
3. Populate values as follows:
Invocation Type = XAI
Message Class = HTTPSNDR. This is the class for Real-time sender to route messages using HTTP.
MSG Encoding = UTF-8 message encoding
4. Select the Active check box.
5. Navigate to the Context tab and set the values for the following Context Types.
• HTTP Login User – User ID for the url to be accessed
• HTTP Login Password – Password for the url to be accessed
• HTTP Header – SOAPAction: "GetWOLineApptWinAvail"
• HTTP Method (POST/GET) – POST
• HTTP Proxy Host – Set the proxy server name if applicable
• HTTP Proxy Port – Port for the proxy server if applicable
• HTTP Transport Method – SendReceive
• HTTP Timeout: 60 (in seconds)
• HTTP URL 1 – Set the URL to be accessed. If the URL value does not fit, use the additional HTTP URL types to set the complete URL. This should point to the Query Appointment Requester ABCS
Example: http://soa-server:soa-port/soa-infra/services/default/ GetWOLineApptWinAvailOUCCBUtilitiesReqABCSImpl/GetWOLineApptWinAvailOUCCBUtilitiesReqABCSImpl
• Character Encoding – UTF-8
Create an External System
Create a new External System for the integration layer.
1. Navigate to Admin, External System.
2. Enter a unique External System and Description.
3. Set Our Name in Their System to CC&B.
The values set in the AIA Configuration properties Default.Notification.External.ID and Default.Reply.To.Message.Source must match the External System name created in Oracle Utilities Customer Care and Billing.
Create a Service Provider
Create a new Service Provider to be used for the integration layer.
1. Navigate to Admin, Service Provider.
2. Enter a unique Service Provider and Description.
3. Set External System to the External System created for the integration layer.
4. Set Notification DL Profile to the Notification Download Profile created for the integration layer.
5. Set Person ID to the Person representing this service provider ( If not exist, create one in Person Page)
Notification Download Type
Only the following download conditions identified in Setting up Outbound Messages are applicable to this integration.
• FA Cancellations
• FA Creation
• FA Change
• FA Reschedule
• Get Available Appointments
Get Available Appointments NDS Type - reference CDxProcessXDS inbound web service and no context types.
NDS Types FA Cancellation/FA Creation/FA Change/FA Reschedule - reference ExtractFAInfo Inbound web service and the following context types:
Refer to the demonstration data for an example of NDS Types and Context Type/XPATH settings.
Hosting Inbound XAI Legacy Services
XAI Inbound Service Deployment Status section holds the Legacy Services which needs to be enabled in Feature Configuration:
• Feature Name: External Messages
• Feature Type: CI_EMAIL
• Support XAI Deployment via IWS should be set to true
Notification Download Profile
Create a notification download profile for the service provider previously created.
Define a Notification Download Profile
1. Navigate to Admin > Notification Download Profile.
2. Enter a unique Notification Download Profile and Description.
Include an entry in the profile for each NDS type created previously in the NDS collection.
3. Enter the Processing Method for each NDS type with values according to the following: