Neptune 360 1.4.6 Release Notes

Neptune is pleased to announce release 1.4.6 of Neptune 360 – the cloud-hosted data management platform from Neptune. This release includes bug fixes and new features for register change out, data logging in 360, and the Days of Consecutive Flow (AMI) – Consumption Based report.

System Requirements

  • Neptune 360
    • Google Chrome (67.0+); Microsoft Edge (42.17134+)
  • Neptune 360 Mobile
  • iOS (10.3.1+); Android (5.1+)
  • Neptune 360 Sync
    • Windows (7+)
    • Processor: 2 GHz or faster
    • Memory: 4GB
    • Hard disk space: at least 1.5 GB available

New Features

  • Register Change Out – This feature provides users with the ability to configure register change outs in their Customer Inquiry asset management in order to avoid consumption spikes that may occur between an old and new register readings.
  • Data Logging in Neptune 360 – This feature allows users to review data logs generated on their 360 Mobile devices within the Neptune 360 web application.
  • Days of Consectuive Flow (AMI) – Consumption Based Report – This report functions the same way as the existing Days of Consecutive Flow (AMI) report by aggregating days of constant flow into discrete events but is driven by consumption rather than flags.
  • New API Calls
    • New /v2/lastreadings API call available. Is a copy of /v1/lastreadings with a new field added (register_change_out) to indicate if a register changeout transaction occurred.
    • New /v2/readings API call available. New field added (register_change_out) to indicate if a register changeout transaction has occurred. Unlike the /v1/readings call, this one returns all readings received between the date range requested.

Enhancements and Bug Fixes

  • Updates to the performance and the UI of the Customer Inquiry screen
  • New /v2/lastreadings API call available. Is a copy of /v1/lastreadings with a new field added (register_change_out) to indicate if a register changeout transaction occurred.
  • New /v2/readings API call available. New field added (register_change_out) to indicate if a register changeout transaction has occurred. Unlike the /v1/readings call, this one returns all readings received between the date range requested.
  • Improved header information on Customer Inquiry consumption exports
  • Renamed existing Days of Consecutive Flow (AMI) report to differentiate between flag based and consumption based versions
  • Fixed: Incorrect value for Days of Consumption flag populated in export file
  • Fixed: Days of Consecutive Flow Export – report header needs wider columns
  • Fixed: Resolved issue of inactive MIU showing on Meters Not Received Detail report
  • Fixed: Keyed readings are not being displayed under the Keyed Reading column on the Complete Readings Detail report
  • Fixed: The Collector Reading in the export file should not be populated for Keyed readings
  • Fixed: Resolved intermittent issue with account and MIU statuses not getting updated after import
  • Fixed: Route and Readsequence do not get set on 35day reports when the meter number has leading spaces
  • Fixed: API – YAML file updates to fix errors and improve usability
  • Fixed: The tooltip for Auto-Complete Days shows technical description

Neptune 360 1.4.5.3 Release Notes

Neptune is pleased to announce release 1.4.5.3 of Neptune 360 – the cloud-hosted data management platform from Neptune. This release includes bug fixes and new features for displaying active and inactive status on Customer Inquiry and the Endpoint Consumption report.

System Requirements

  • Neptune 360
    • Google Chrome (67.0+); Microsoft Edge (42.17134+)
  • Neptune 360 Mobile
  • iOS (10.3.1+); Android (5.1+)
  • Neptune 360 Sync
    • Windows (7+)
    • Processor: 2 GHz or faster
    • Memory: 4GB
    • Hard disk space: at least 1.5 GB available

New Features

  • Endpoint Consumption Report – This report provides a listing of Daily or Hourly readings and consumption for an endpoint for the date range provided.
  • Account/MIU Status Display – The status of the Account and the MIU, along with the install and deactivation dates, have been added to the Customer Inquiry search results. This will easily allow for determining which account/MIU is currently active.

Enhancements and Bug Fixes

  • Added Privacy Policy to Neptune 360 About section of the UI
  • System Consumption KPI performance improvements
  • Import performance improvements
    • As part of this, the import progress screen will not update total imported counts until the import has completed processing
  • Fixed: Handling of duplicate meter number records
    • If multiple records on import have the same meter number but unique meter size or meter key or read sequence then a unique meter will be created with appropriate details and reflected on export
  • Persist “Search By” selection on Customer Inquiry
  • Fixed: Handling 07000000 as an invalid read
  • Fixed: Show reading on Active Account instead of Inactive Account
  • Fixed: 500 Error When Requesting Token from /token API
  • Fixed: Speed Issue with Continuous Consumption and Major Reverse Flow KPI
  • Fixed: Gateway KPI Showing “0” Despite Collectors Sending in Readings
  • Fixed: No Flow Flags Not Showing Up in 360 on N_SIGHT PLUS conversion accounts
  • Fixed: Correct Active Dates within More Meters
  • Fixed: Duplicate Accounts on Reports After Merging Routes
  • Fixed: Inactive Accounts in 360 Despite MIU Being Active in Import File
  • Fixed: Adjust timing of Received KPIs to match logic used in Complete Readings KPI