Onboard Hardware in Bulk
Oracle Enterprise Communications Platform Oracle ECP provides a Comma Separated Value (.csv) formatted template file that you can use to onboard multiple pieces of hardware in one work flow. You can onboard up to one hundred Cloud Connectors or devices at one time with the .csv template.
- Download the CSV Template for Bulk Boarding and replace the sample information with the actual equipment details in the same format. Provide a row of equipment details for each item you want to onboard.
- When you onboard MDM-enabled devices, confirm that the customer's MDM account is functional on Oracle ECP before onboarding.
- Ensure you include Product ID for Cellular Devices (this information can be found on the Add Hardware page's Subscription field or on the Settings, Subscriptions page).
Note:
Oracle ECP displays an error when any required fields are missing information.During bulk Cloud Connector onboarding, Oracle ECP can automatically populate the longitude and latitude fields required for Satellite connectivity when the addresses in the .csv file are sufficient to discover the coordinates. When Oracle ECP detects insufficient addresses, the Requests Details page displays a list of the rejections. You can manually enter the longitude and latitude coordinates in the rejected Cloud Connectors and then onboard them one at a time.
The CSV template uses separate column groups for deployment and registration information. Complete the Deployment Address or Deployment Coordinates columns for every device or edge node. Complete the Registration Address columns only for a Starlink-connected edge node or hardware that uses a FirstNet SIM.Oracle ECP validates each row before onboarding it. The Onboarding Request Details page identifies rejected rows. Correct a row and submit it again when any of the following conditions occurs:
- Both deployment address and deployment coordinates are missing.
- A deployment address is present, deployment coordinates are missing, and Oracle ECP cannot geocode the address.
- The supplied deployment address and deployment coordinates do not identify locations in the same city.
- A required Starlink or FirstNet registration address is missing.
- A Starlink registration address cannot be converted to coordinates.
- Registration information is supplied for hardware that does not use Starlink or FirstNet connectivity.
Note:
If Oracle ECP cannot geocode a FirstNet registration address, onboarding can continue without registration coordinates. The registration address remains required.- If you onboard MDM-enabled devices after Oracle ECP onboarding, you can download a QR code or enrollment token on the Onboarding Request Details page. You can provide the QR code or token to end users along with instructions to facilitate onboarding to the external MDM using the onboarding profile created during ECP onboarding.
Download the Oracle ECP CSV Template for Bulk Onboarding
Oracle Enterprise Communications Platform Oracle ECP provides a Comma Separated Value (CSV) formatted template file that you can use to onboard multiple pieces of hardware in one procedure.
Use the following procedure to download the CSV template that you need for the bulk hardware onboarding procedure. Save the file to a local location for future use when you will drag and drop it into a field during the bulk hardware onboarding procedure.
- Access the template and follow its format to add up to one hundred devices (of a single type).
- Onboard Hardware in Bulk