Batch Provisioning

1. From ERS Provisioning screen, click the Export button. The Export Results screen displays.
   • Note: You can only download a sample batch file from Deployment. The batch file structure is the same regardless of where you download it from.
2. Enter a file name.
3. Choose the selection of record items to export (ERL, Subscribers, Subnets). By default, all record items are selected. At least one record item is required.
   (Optional) Select any additional record fields to export. By default, the fields required for batch provisioning are automatically selected.
   • Warning: Do not uncheck fields marked with an asterisk. Unchecking required fields can result in an error when you upload this file into the ERS.
4. Click the Export button. The file is ready for download in the file manager.
5. Click on the file to download it.

Batch File Structure

As a part of your initial provisioning, Midco uploaded your original batch data. The first row of the batch file always contains the Account Name, Account ID and the date and time that it was generated.
The second row of the batch file contains the following column titles:

• Operation (OP)
• Result (RES)
• Message (MSG)
• Item
• Account ID
• Account Name
• Sub Account ID (Sub Account ID)
• Sub Account Name (Sub Account Name)
• Subscriber ID
• ERL ID
• Civic address information
• Batch File Structure Considerations
• Account ID, Account Name are always populated with the deployment account ID and name.
• OP, RES, and MSG columns are empty when you download the sample batch file.
• Item column helps discern if the row belongs to an ERL, Subscriber, Subnet or Account.

For batch operations, all other information is provided by the user. This includes the OP (operation) as well as the provisioning data.

1. Open the CSV batch file.
2. Enter the operator values in the OP column and provide all necessary information. The operator and the information you provide varies based on the batch action you want to perform. Use the Batch Operator Values provided below to perform an action. For instance, “A” operator is used for adding whereas “D” operator is used for deleting.
3. Provide all necessary information based on the batch operation you want to perform. All the batch operations supported by ERS, along with examples are provided below in Batch Operations and Examples.

Batch Operator Values

These operations are entered in the OP column of the CSV file, based on the action you want to perform.

A: Add or Modify 

D: Delete

Batch Operations and Examples

All batch operations supported by the ERS are provided here with examples.

Do not modify the first two rows of the batch file. These are mandatory rows that the ERS auto-generates and are required for proper provisioning.

1. In the OP column, enter A.
2. In the ERL ID column, enter a value for the ERL ID according to Appendix A: Field Descriptions. If this field is left empty, the ERS will auto-generate an ERL ID.
3. In the Account ID column, enter the deployment account’s ID.
4. To provision this ERL under a sub account, enter the account’s name under the Sub Account Name column.
5. Enter the civic address information.

All other fields that appear in the batch file are optional.

1. In the OP column, enter A.
2. In the Subscriber ID column, enter a valid Subscriber ID.
3. In the Account ID column, enter the Account ID of the deployment account.
4. If the ERL is to be provisioned under a Sub Account, then enter a name in the Sub Account Name column.
5. Enter the civic address information.

1. In the OP column, enter A.
2. In the Subscriber ID column, enter a valid Subscriber ID.
3. In the ERL ID column, enter the ERL ID of the ERL to which you want to add this subscriber.

1. In the OP column, enter A.
2. In the Subscriber ID column, enter a valid SubscriberID.
3. In the Account ID column, enter the ID of the deployment account.
4. If the subscriber is to be added to a Sub Account, then enter the name in the Sub Account Name column.
5. Enter the civic address data.

In order to modify a subscriber ID, users have to delete the existing record and create a new one.

1. In the OP column, enter A.
2. In the Account ID column, enter the ID of the deployment account.
3. In the Subscriber ID column, enter a valid SubscriberID.
4. In the ERL ID column, enter a valid ERLID.
5. If the address you want to modify belongs to a subscriber that is contained in a Sub Account, enter the name of the Sub Account in the Sub Account Name column.
6. Modify the address information, as desired.

The D operation deletes the ERL, provided that no subscribers are attached to it.

1. After making the desired changes and additions to the batch CSV file:
   Save the changes you made.
2. Please ensure that you have saved the batch file in CSV format. Microsoft Excel asks to save the file twice.
3. Go to the ERS Provisioning screen and click the Batch Provisioning button. The Batch Provisioning screen displays.
4. Click on Provision File button and select the desired batch file it to upload it. ERS displays a message asking for confirmation to complete the action.
5. Click the Confirm button. ERS performs address validation and system checks to ensure that the information in the batch file is valid. The results are displayed in real-time under the Status column.
   • When the Remaining column displays 0, this means that ERS has finished processing the file.
6. Click the Return to Provisioning button. This returns you to the Provisioning screen. You can view your newly added provisioning data here.

When you upload a batch file and click on the Provision File button, ERS processes the CSV file row-by-row. Information in the rows that are valid are added to ERS records. Records in rows that failed address validation or system checks are rejected. The batch operations-successes and errors are recorded by the ERS. These can be viewed in the Batch Provisioning History section of the Batch Provisioning screen.

ERS generates a log file in CSV format to record the results of the batch operations and to provide feedback on the result of the operation. The original batch file that was uploaded is returned with the RES (result) and MSG (message) column populated with the appropriate message. For instance, the RES column in the log file displays OK and the MSG column displays Location successfully added to advise the user that the ERL row was valid and added to ERS records.

The log file is generated even when no errors are detected in the batch file. If your file did contain errors, you can correct those errors and re-upload into the ERS.

ERS also generates an Error File if any of the rows failed validation. This file contains only the rows that generated an error. The RES (result) and MSG (message) columns display the result of the validation and the reason for the error.