Skip to main content

Release History

VersionDate
2.9.005 June 2025
2.8.022 October 2024
2.7.009 March 2023
2.6.022 June 2022
2.5.003 March 2022
2.4.023 September 2021
2.3.013 January 2021
2.2.011 November 2020
2.1.015 June 2020
2.0.114 May 2020
2.0.016 December 2019
1.7.229 November 2019
1.7.126 November 2019
1.7.030 October 2019
1.6.020 Aug 2019
1.5.14 June 2019
1.5.031 May 2019
1.4.021 December 2018
1.3.024 August 2018
1.2.120 April 2018
1.2.026 Feburary 2018
1.1.030 November 2017
1.0.014 November 2017

Breaking Changes
  • None.
New Features
  • None.
Enhancements
  • Added support for EPSG4326 in addition to WGS84 as valid geo world translations.
Fixes
  • Correctly populating the connection point identifiers from the TCS schema when using 'NMI' as the connectionPointIdentifier.
  • No longer creating an empty NameType 'NMI' when using a different connectionPointIdentifier.
Notes
  • None.

v2.5.0

Breaking Changes
  • Changed the TCS schema processing to pull the connection point identifier from CD_CUSTOMER.PERSONAL_NO.
  • Relocated connection point identifiers (e.g. NMI) to be stored as a 'Name' associated with a UsagePoint rather than as the name of a Location assigned to a Meter.serviceLocation.
  • LV UsagePoint instances that can not find their EnergyConsumer are no longer associated directly to a PowerTransformer. They are now connected via a generated EnergyConsumer via an EquivalentBranch to the LV side of the PowerTransformer.
  • Using new database schema.
  • Removed command line option -icn, --ignore-conductor-names, which has been replaced by PoF configuration option conductorNaming.
  • Primary EnergySource instances no longer create any associated EnergySourcePhase instances, but set isExternalGrid instead.
New Features
  • Populating PowerTransformer.function.
  • Added a PoF configuration option conductorNaming, which can be used to select the COMPONENT_HEADER field to use as the conductor name (COMPONENT_PATHNAME, COMPONENT_ALIAS or COMPONENT_ID).
Enhancements
  • None.
Fixes
  • Added support for null personal_no in cd_customer when readings meter mappings from the TCS schema.
Notes
  • None.

v2.4.0

Breaking Changes
  • The tool no longer outputs an id-correlations.json file and instead populates the GIS id and DMS id as additional names.
  • Added support for creating Pole instances from nodes. This requires a new poleClasses key to be added to the PoF data config file.
  • Added support for ignoring source demarcations on specified classes. This requires a new ignoreSources key to be added to the PoF data config file.
New Features
  • Worlds with GEO transformations are now extracted as geographical co-ordinates in addition to the schematic view.
  • Can detect feeder breakers that are not flagged correctly. Will get it wrong if there are additional breakers between the feeder breaker and the feeder start point.
  • Added command line option --ignore-conductor-names which can be used to populate the conductors names with the component_id. This means the map tiles in EWB will not render the name and will show the container name (e.g. feeder) instead.
  • Added command line option --disable-fixes which should be used when extracting an imported GEO world.
  • Meters can now be sourced from the TCS schema instead of a meter mapping file using the meterSourceType app config field.
  • The connection point identifier can be renamed via the connectionPointIdentifier app config field. e.g. use ICP instead of NMI.
  • Conductor graphics are now stitched into a single DiagramObject where possible.
Enhancements
  • Improved detection of distribution side of feeder start points if there are no feeder breakers defined.
  • Feeder start points no longer require graphics if they are connected to a visible conductor.
Fixes
  • None.
Notes
  • None.

v2.3.0

Breaking Changes
  • Added processing step to determine the correct head terminal for feeders. This change was necessary after updates to the logic for assigning equipment to feeders in the evolve-sdk.
  • Feeders with no clearly correct head terminal will no longer populate equipment until they are corrected in the PoF data.
  • Updated the logic to find zones for feeders in the network hierarchy processor.
New Features
  • Now populating the metadata with the extractor name and version.
Enhancements
  • None.
Fixes
  • None.
Notes
  • None.

v2.2.0

Breaking Changes
  • Updated to use CIM based database (v17.0).
New Features
  • None.
Enhancements
  • ID correlations are now added for usage points.
Fixes
  • None.
Notes
  • None.

v2.1.0

Breaking Changes
  • Updated to use CIM based database (v14.0).
New Features
  • None.
Enhancements
  • None.
Fixes
  • Correctly removing terminals left dangling when applying network fixes.
Notes
  • None.

v2.0.1

Fixes
  • Updated the CRO extraction query to look at ops.CURRENT_STATE instead of pmts.CURRENT_STATE.

v2.0.0

Breaking Changes
  • Updated to create a v12.0 network database.
  • Updated to use the CIM based network model objects.
New Features
  • CROs are now extracted as operational restrictions.
Enhancements
  • None.
Fixes
  • None.
Notes
  • None.

v1.7.2

Fixes
  • Stopped collapsing equipment with usage points.
  • Stopped wiring fixes collapsing significant nodes as terminals.

v1.7.1

Enhancements
  • Added logging when a valid database record fails to save correctly.
Fixes
  • No longer writing invalid LV simplification records if a transformer fails to save.

v1.7.0

Breaking Changes
  • Updated to create a v11.0 network database.
New Features
  • Underground/Overhead conductor processing has been added. You can override the default underground cable pattern of hvugc by adding a new value undergroundPattern to your extractors pof config file. All conductors that do not match the pattern are marked as overhead.
Enhancements
  • You can now configure the Oracle port number to use via the command line.
Fixes
  • None.
Notes
  • None.

v1.6.0

Breaking Changes
  • None.
New Features
  • None.
Enhancements
  • HV meters are now saved to the meters table in the database.
Fixes
  • If a meter id is mapped to both an LV and HV supply point, the LV mapping ignored and a warning is logged.
Notes
  • None.

v1.5.1

Breaking Changes
  • None.
New Features
  • None.
Enhancements
  • None.
Fixes
  • Updated SQLite driver to support JDK 11.
Notes
  • None.

v1.5.0

Breaking Changes
  • Updated to create a v10.0 network database.
New Features
  • None.
Enhancements
  • None.
Fixes
  • None.
Notes
  • None.

v1.4.0

Breaking Changes
  • None.
New Features
  • Zone points are now considered normally open.
Enhancements
  • You can now configure the zone clone ID's by specifying a list of id's under the 'zoneCloneIds' key in the config.
Fixes
  • Both zero length and maximum length use the maximum trace voltage configuration parameter.
Notes
  • None.

v1.3.0

Breaking Changes
  • None.
New Features
  • DPA busbar nodes are now removed from the network.
  • Now removing internal conductors that bypass symbol centres.
  • Symbols that have external conductors connected to the middle of the symbol instead of the disconnect points are now being rewired.
Enhancements
  • None.
Fixes
  • None.
Notes
  • None.

v1.2.1

Breaking Changes
  • None.
New Features
  • None.
Enhancements
  • None.
Fixes
  • Network is now being extracted as a 3 wire network (was previously 4 wire).
Notes
  • None.

v1.2.0

Breaking Changes
  • The network model database schema has changed to support new features.
New Features
  • Added Iso transformer type.
  • Added support for HV supply points / meter mappings.
Enhancements
  • Latitude / Longitude interpolation is now more accurate.
  • Components marked as open as no longer converted to switches as all assets can now be marked as open.
  • Feeder and Zone processing now better handles unclean component hierarchies.
Fixes
  • Voltages were not always being processed correctly.
  • Fixes to issues handles sources.
  • Various minor fixes.
Notes
  • None.

v1.1.0

Breaking Changes
  • Path to the failed directory needs to be specified in the config file.
New Features
  • Added config to log messages to syslog.
  • Input files that fail to process are moved to a "failed directory"
  • Now ignores records before a provided date via command line arguments.
Enhancements
  • None.
Fixes
  • The current log is now logged to the specified log path instead of just archive logs.
Notes
  • To enable logging messages for files which failed to process, add the required syslog options in the config file. Refer to Load Processor config options for more info.
Breaking Changes
  • Added PoF config option eastingNorthingStoreLongLat, which is now used to control the processing of easting/northing values and defaults to false.
New Features
  • LV feeders are now added to the secondary terminal of each distribution transformer.
Enhancements
  • None.
Fixes
  • None.
Notes
  • None.\n\n---\n
Breaking Changes
  • Updated to produce database schema v56 which has been split into three databases, one each for network, diagrams and customer details.
New Features
  • LV feeders are now added to the secondary terminal of each distribution transformer.
  • The phase consistency processing now takes into consideration of the phaseCode value of UsagePoint associated with the EnergyConsumer to determine the correct phaseCode of EnergyConsumer terminal.
Enhancements
  • Locations for each UsagePoint are populated from the TCS.CD_ADDRESSES table.
  • A Customer will be created for each entry in TCS.CD_CUSTOMERS, populating specialNeed with TCS.CD_CUSTOMER_TYPE.CT_NAME for each entry with a TCS.CD_CUSTOMER_TYPE.SENSITIVE_LEVEL.
  • Each Customer will be linked to an Organisation representing their retailer.
Fixes
  • Updated the expected format of the transformerTypes configuration fields to be camelCase rather than the previous snake_case. The old field names will still work, but will now generate an obsolete warning and should be updated in your config file:
    • rating_min has been renamed to ratingMin
    • rating_max has been renamed to ratingMax
    • cyclic_rating_factor has been renamed to cyclicRatingFactor
    • power_factor has been renamed to powerFactor
  • Added support for TCS.CD_CUST_PROPERTY_ASSOC.USAGE_END_DATE with non-date column types.
Notes
  • None.\n\n---\n

Breaking Changes

  • Removed PoF configuration option txRatingAttribute. It has been moved into the new attributeMapping options.
  • Transformer ends are now correctly numbered from 1 instead of 0. If you were relying on explicit end number, rather than just the order, you will need to update your processing to be 1-based.
  • All transformers will now have at least one end created. If you were relaying on a transformer to be missing ends, you will need to update your logic.

New Features

  • Many new attributes can now be mapped via the attributeMapping section of the PoF data configuration file. See the docs for details.

Enhancements

  • Updated the base voltage processing to share base voltage instances between the conductor and node processing.
  • Added MVA units to the ratings parsing to support larger rating values.
  • Ratings and voltages no longer require units, and will use the multiplier provided in the attribute mappings if no units are found.
  • LinearShuntCompensators now populate the sections and bPerSection when defined in the attribute mappings. It can also populate assetInfo with a simple reference into an external system.
  • PowerTransformers now populate r, x, r0, x0, stepVoltageIncrement, highStep, lowStep, neutralStep, normalStep, tapControlEnabled and transformerUtilisation when defined in the attribute mappings. It can also populate assetInfo with a simple reference into an external system.

Fixes

  • Updated the TCS customer queries to work on Oracle again.
  • We no longer set defaults for TransformerStarImpedance r and x when the PowerTransformerEnd has null or 0 ratedS/ratedU, which avoids NaN/Infinity numbers being set for impedances.
  • Re-support Oracle query when doing TCS extract
  • Phases are now correctly assigned to the LV side of an LV2 transformer that is in parallel with a previously energised LV1 transformer.

Notes

  • Updated to use new tracing API from the EWB SDK. No functional change.
  • CIM database version updated to 59.\n\n---\n