|
Importing Emissions Input Data
Emissions Input data can be imported, either manually or via a scheduled process.
Downloading an Import Template
To assist with the import process, users can download an Import Template from the New Emissions Screen. This CSV file will
- be generated in the correct structure which is required for the Import (details below)
- contain all the outstanding records as displayed on the screen. I.e. users can reduce the list by applying a filter.
The structure of the CSV file will be as follows - in this order:
- Location
- Source
- Time Period
- Input
- Input Value
- Value Unit
- Actual/Estimate
Information in this CSV file needs to be provided as follows:
- Input Value: you must provide a number,
- Value Unit: you can change the Unit as long as the new unit can be converted to the original unit (e.g. kWh
 GWh) - All other entries, including the header line, must remain unchanged.
- If the CSV file contains any invalid entries, the corresponding records will be rejected.
Example 1: One Input Only
Kalgoorlie,Site Energy Usage,2023 (01) January,Quantity,12764,GWh,Actual
Example 2: Multiple Inputs
In case you need to provide multiple inputs for a record, the CSV file will show a separate line for each of the inputs.
Kalgoorlie,Site Energy Usage,2023 (01) January,Quantity,12764,GWh,Estimate
Kalgoorlie,Site Energy Usage,2023 (01) January,Days,365,Days,Actual
How it works
The import process uses a compound key:
Location (Name) – Emissions Source (Name) – Time Period (Description)
- If no existing Emissions Result record is found using this compound key, then a new Emission Result record is created and the Input data is added (assuming there is actually Outstanding Data for the Location / Emissions Source / Time Period – if not, the record will not be imported)
- If an existing Emissions Result record is found using this compound key then the Input data will be added/updated on that Emissions Result, using the Input (Name) as a key.
After each Input is imported, the system will attempt to calculate the Emissions Results Outputs. If it can, then Emissions result will be found in the Existing Data area. If it cannot be calculated (either because there are still some Inputs that have not been imported, or because some referential data cannot be found) then it will be found in the Incomplete Data area.
Importing Emissions Records
|
SCHEDULED IMPORT
|
For the task of ...
|
I need to ...
|
Creating the Import Event
|
Navigate to Designer Events
|
Naming the Event
|
Give the Event a name which clearly identifies its purpose
|
Selecting the Event Type
|
Select the Event Type Emissions - Data Import
|
Scheduling the Event by defining the Run Time
|
The import will run once a day, at the time defined in Run Time.
You must enter the time in 24 hour format.
|
NOTE:
For the Event to be triggered, Tomcat must be running at the specified time.
If Tomcat is down at the defined time, the system will not re-try the import until the next day
|
You will need to SAVE the record before continuing onto the next page.
|
IMPORT DETAILS
|
Defining the FULL path to the import files
|
The CSV files for the import must be placed into a shared folder, a folder Tomcat must have access to.
For example:
\\server\ImportFolder\
The import will attempt to import all CSV files in the specified folder.
|
Define email recipient for error log
|
For scheduled Imports, the system will generated and send a report ONLY when there have been any issues.
You must manually enter an email in the To Address of the recipient
|
MANUAL IMPORT
|
For the task of ...
|
I need to ...
|
Running an Import
|
- Navigate to ...Emissions Management Data Entry Outstanding Data
- Click the Import Data button to open the file selection dialog
- Select the CSV file you want to import and click OK
- You will see a summary dialog of how many records were updated and/or you will receive an email detailing any errors that occurred
|
|
