¶ Product Overview
OxOracle is a primary data set of industry information where customers map their internal ETRM data, enabling counterparty communication throughout the Eleox platform. This mapping enables market participants to “speak the same language” across ETRM systems.
¶ Core Features
- Standardizes data naming, allowing for the reconciliation of customers’ ETRM systems
- ETRM data names are mapped to an Eleox data name, creating one universal language
- Users see their proprietary ETRM language while communicating in a standard language
- Multiple Eleox products leverage mapped data without incremental user effort
¶ ETRM Reference Data Flow to Eleox
ETRM Reference Data flows into OxOracle via API or uploads to the UI. Please refer to Swagger.
¶ API Endpoints
- Create Counterparty:
POST https://{{url}}/api/oracle/v1/counterparties - Create Pipeline:
POST https://{{url}}/api/oracle/v1/pipelines - Create Zone:
POST https://{{url}}/api/oracle/v1/zones - Create Location:
POST https://{{url}}/api/oracle/v1/locations - Create Broker:
POST https://{{url}}/api/oracle/v1/brokers - Create Pay Index:
POST https://{{url}}/api/oracle/v1/pay-indexes
¶ Primary Reference Data
Eleox provides the Primary Reference Data.
- The “Spec ID” field is the unique identifier for each record.
¶ Primary Reference Data Requests
Customers can request Eleox to add or update primary reference data by selecting the “request” button in the top right corner of the screen.
To request a modification of existing data, right-click and select “Create Spec Request”, choose the appropriate action, and provide a detailed comment.
For large data set requests, please email [email protected].
¶ ETRM Reference Data Mapping
New users map their ETRM data to Eleox's primary data set before sending company-specific ETRM data to Eleox. This one-time mapping enables customers to “speak the same language” across ETRM systems.
- Users can download and populate the CSV files with their company-specific ETRM reference data.
- “ETRM ID” and “Name” are required fields.
- Once the user uploads the file, please allow some processing time. An indication in the successes and failures columns in the upload grid notifies Eleox of any issues. Select any failures to see why certain records might not have been processed. Hover over the error to see a “tooltip” with the error information, reloading once corrections are made.
¶ ETRM Reference Data Maintenance
Once uploaded, customers can view, edit, or delete company-specific ETRM reference data. “Spec Name” is displayed in the grid for customer convenience.
- Use the “Add form” to add individual ETRM records.
- The form has type-ahead capabilities in the “Spec ID” column to ensure correct mapping to the primary reference data.
- The drop-down contains the spec reference information for the dataset.
Rules:
- Double-click into the cell to edit the field value. Once added, the “ETRM ID” is not editable.
- Customers updating an active ETRM reference data record in OxPair “Outbound Deals" will see a modal confirming the User wishes to modify the record. If they choose to execute the action, then the ETRM reference data record and Outbound Deal records will be updated.
- Users updating the "Spec ID" field in an OxSettle “ETRM Invoice" will see a modal confirming the User wishes to modify the record. If selected, the ETRM reference data record and invoice records are updated.
Notes:
- The “Is Affiliate” field on the ETRM Counterparties reference data record can be set to “False” if the counterparty is not the user's affiliate.
- The “Spec ID” is used in OxPair. If the “Spec Physical Location ID” is populated, the data is used in OxSettle, or else the “Spec ID” is used. The difference between “Spec ID” and “Spec Physical Location ID” allows the ETRM Location reference record to be mapped to a generic ICE location and a specific physical point as needed.
- Use the following action history API endpoints to view record changes.
- https://{{url}}/api/v1/communication/action-history?itemType=counterparty
- https://{{url}}/api/v1/communication/action-history?itemType=pipeline
- https://{{url}}/api/v1/communication/action-history?itemType=zone
- https://{{url}}/api/v1/communication/action-history?itemType=location
- https://{{url}}/api/v1/communication/action-history?itemType=payIndex
- https://{{url}}/api/v1/communication/action-history?itemType=broker
