Gas Composition Import Feature

Gas Composition Import Feature

This does not affect ZCM customers, imports will be the same.

The Gas Composition import feature will allow you to bulk upload gas compositions (GCs) to your meters on Zedi Access using a .csv file.

Benefits

• Improved functionality, as it can be used to write GCs to a wider selection of meters. Not just Smart-Alek’s!

• Easier to use input file.

• Provides better feedback on what GCs were received and written to the meter.

• The new dashboard offers better visibility/feedback loop on what is sent vs what was written to the device.

• You will continue to have the ability to manually enter GCs to their meters as needed

*We will be replacing the existing “data import” feature at a future date.

What will you need?

• A new export from protrend called “Zedi Gas Comp Export” (this is comparable to “Smart-Alek EFM” export for the old feature)

• You will need to map the Zedi ID to this new export in protrend.

• The Zedi Gas Comp Export export is a csv file, which is more user friendly and offers other benefits for reporting, filtering, etc.

Below is the guide that will help you with this new feature. If you need assistance with this feature reach out to out customer care team.

Gas Composition Import File Format

The gas composition import uses a CSV file with the following format:

1. Zedi ID/Tag ID - This is the Zedi ID of the location in Zedi Access where the GCs will be written down to (integer, required)
2. Meter Code (string, optional)
3. Meter Location (string, optional)
4. Meter Name (string, optional)
5. UWI (string, optional)
6. Effective Date - formatted as YYYYMMDD, this is the start date of when this GC will be used (required). Will also accept YYYY-MM-DD date format.
7. Sample Date - formatted as YYYYMMDD (optional) Will also accept YYYY-MM-DD date format.
8. All the following components are required and must be in decimal format. If a component does not have a value, enter a 0. 

• H2
• He
• N2
• CO2
• H2S
• C1
• C2
• C3
• IC4
• NC4
• IC5
• NC5
• C6
• C7

These components are optional, and must be in decimal format is included:


• C8
• C9
• C10

The total of all values must equal 1

9. Spec Gravity (decimal, optional)

10. Heating Value is optional. A single decimal value (either BTU/ft³ or MJ/m³) Should be supplied if included.

• Heating Value (BTU/ft³)
• Heating Vale (MJ/m³)

Devices/Meters Supported for Gas Composition Import

The following devices/meters are supported for use with this feature

1. Smart-Alek
2. Smart-Alek well test locations
3. True Chart
4. Other Scada devices that meet the following parameters
   1. Device is commissioned onto Zedi Access using ACM
   2. Device uses one of the following communication protocol
      1. ROC
      2. Modbus SCADAPack
      3. Totalflow
      4. Modbus Enron
      5. Barton Scancom
      6. Eagle Research
      7. Kimray
      8. Flow Automation
      9. DNP3 FBx Protocol

Devices/Meters Not Supported for Gas Composition Import

The following devices/meters not supported for use with this feature

Note: Users can manually enter their GCs to these meters on Zedi Access

1. Field Gateway
2. Zed-Pac
3. MTRAC
4. Zedi EFM Walk-up
5. Other Scada devices on ACM with the following communication protocols:
   1. Benchmark Protocol
   2. BSAP Protocol
   3. CAMP Protocol
   4. ControlLogix Protocol
   5. Decasync Protocol
   6. DF1 / ABTCP Protocol
   7. DNP3 Protocol
   8. DRESSER ProtocolFBNet Protocol
   9. GE SRTP Protocol
   10. HEXREPEATER Protocol
   11. Honeywell - Mercury Protocol
   12. Modbus Alien 2 Protocol
   13. Modbus Block History Protocol
   14. Modbus BP WellControl Protocol
   15. Modbus DynaPump Protocol
   16. Modbus ETNG Protocol
   17. Modbus Kinder Morgan Protocol
   18. Modbus Lufkin SAM Protocol
   19. Modbus MicroMVL Protocol
   20. Modbus Omni 7000 Protocol
   21. Modbus Omni Protocol
   22. Modbus PCS Plunger Lift Protocol
   23. Modbus Prosoft Protocol
   24. Modbus Protocol
   25. Modbus Scanner 1150 Protocol
   26. NGCTT Protocol
   27. Reynolds LVC Protocol
   28. ROMET-AdEM Protocol
   29. S7 Protocol
   30. Spirit FlowX Protocol
   31. TeledyneCA Protocol
   32. TGP Protocol

Required Permissions to use Gas Composition Import Feature

The following permissions are required to upload GCs using this feature:

1. User account/login credentials to Zedi Access
2. Web permission assigned to your individual account or through a user group. This web permission allows you to access the feature on Zedi Access
   1. Flow Parameters – Gas Composition Import
3. Well permissions assigned to your individual account or through a user group for each location that you are importing GCs to. Without this, you will not be able to update a GC even if they have the well permission assigned.
   1. Basic Access/FDC Reporting
4. Manage Gas Compositions

Note: this also applies to 3^rd party locations

Importing Gas Compositions

Import Workflow

1. You have the GC import file saved to your computer
2. Click “Select File”, browse and select file
   1. Once you have selected the file to upload they will see this pop up message that tells them GCs will be written to devices on their effective date.

After this file has been processed, writes to devices will occur on gas composition effective dates. Write statuses can be viewed on the Gas Composition Import dashboard in Analytics.

1. Selected file is validated and imported with a new record created for in the history table
2. Import record will show a status of either processing or submitted
   1. Processing = Importing gas composition records
   2. Submitted = all records uploaded have been submitted
3. Once the import has a status of submitted, user can download a list of any GCs that failed to import, correct as necessary, and then re-import the corrections.
4. User now refers to the Gas Composition Import Dashboards to check status of GC write success or failure.

Zedi Location ID/Zedi ID

A key element for how the GCs knows which meter to write to is that it uses the Zedi ID. As defined in column A of the Gas Composition Import file, the Zedi ID is required and can be found in the WSD of the location in Zedi Access and in the Gas Comp Import Dashboards found in the analytics tab.

Effective Date

This date specifies when the user wants to have the meter start using the GC they are wishing to upload. The import will accept effective dates using the following rules:

1. Effective date can be backdated no further than the 1^st of the previous month from today’s date
2. Effective date can be future dated no more than 31 days in the future

Gas Composition Import Dashboards

These dashboards are designed to help support the user by providing info for set up and verification of importing GCs. These dashboards are located on the ‘Analytics’ tab of Zedi Access under the name ‘Gas Composition Imports’

1. Device Protocol – Detail listing of devices you have permissions to seeing on Zedi Access and whether they are supported or unsupported for bulk GC import.
2. Protocol Summary – tally/summary of supported vs unsupported devices by communication protocol
3. New Locations – list newly commissioned sites onto Zedi Access
4. Import Status - details the success or failure of the gas composition writing out to the device.
5. Pending Imports – this outlines a list of GCs that are waiting for the effective date/start date to roll around before the GCs are written to device

The Import history/record table

This section will describe what is shown in the history/ record import table:

Example of what the history/record import table looks like.

1. Import Date – this is the date and time for when a user has uploaded a GC file. The time shown is the Zedi Access Company time zone and may be different then users local time.
2. File Name – Name of the file the user selected to be uploaded. Must be a .csv file
3. Import by – shows the zedi access username of the user who imported a GC file.
4. Import Status – there are only two statuses. Processing and Submitted
   1. Processing = Importing gas composition records Submitted = all records uploaded have been submitted
5. Submitted = all records uploaded have been submitted

Important note: status of ‘submitted ’ does not necessarily mean the GC have been written to devices at this point. Nor does it indicate that a successful write of the GC has happened. Any future dated GC will be written to device on the Effective date. Unsuccessful writes will be found on the “import status” dashboard.

User’s will see this message upon importing a file that is meant to explain the above note:

1. Total records – shows how many GCs were included in the file imported. Is also a way for the user to verify that the expected number of records was included or received.

1. Imported – this shows the number records that have passed validation and will be attempted to write out to the devices
2. Errors – shows the number of records that did not pass validation, and these will not be attempted to write out to the device
3. Error log – this is a downloaded csv file with any errors. A file will only be available for download when the import progress status shows complete.

A user can use this file to make any corrections and reupload the file. The error log will contain the original data that was submitted with a new column appended to the file that will describe why the record was not accepted.

Here is a list of the errors that may appear in the export error file including the description and action to resolve:

Other notes about the history table:

• We only show the 20 most current records of import. Oldest get ones get dropped off first
• When an import is in processing status. That record will auto refresh (10 sec refresh rate) until the status is completed.

If you have any further questions, please reach out to

our Customer Care team at 1-866-732-6967