SYNC 5000

Sync 5000 is a server based data concentrator dedicated for a metering application like AMM, AMI etc. SYNC 5000 can consolidate meter data from many thousands of meters and provide this consolidated information over open standards based interface to a Metering Head System. Sync 5000 can talk to local as well as remote meters over a wide range of physical communication media like, RS232, RS485, RS422, Ethernet Base Tx/Fx 10/100/1000 Mbps, GSM/GPRS/CDMA/PSTN/LPR etc. Some of these interface shall be direct interfaces, and other can be through port servers, modem banks etc.  Data collected from meters are stored into a RDBMS based permanent storage, so that a communication link failure with the head end system will not create any data loss. Sync 5000 support standards based IEC-62056 DLMS/COSEM, Modbus RTU/TCP protocols apart from some proprietary protocols, and using a driver development kit it is possible to add new protocol adapters.

Related Products:

• SYNC 4000 M2M Server
• SYNC 4000 Front end processor
• SYNC 1000 DCU
• SYNC 2000 DCU
• SYNC 3000 DCU
  

Front End (SYNC7000 for Configuration, Diagnostics and HMI)

1. Product administration
2. Configuration
   • Add and configure nodes
   • Nodes will support multiple levels of addressing. These levels can be configured to group meters by any organization schema (for example, Feeder, Transformer, Premises, MeterID or Region, Zone, Subdivision, Circle etc.)
   • Configure communication channels for meters. Allocate channels from the communication subsystem to each meter. Automatically updates the meter-list for each channel
   • Configure Database servers and databases. Meters can be allocated to databases individually or in groups
   • Configure polling intervals, timeouts and retry limits
   • All configuration data stored to dedicated Config database
   • Import/Export configuration data to XML files for backup
3. HMI
   • View meters with connectivity, last failed information
   • View loading of individual channels – distribution of meters across channels
   • System diagnostics display
   • Meter alarms and events display
   • Trigger connection/disconnection of meters
   • Pull up last received data and reports for individual feeders, DTs and consumer meters
4. Reports
   • Consumption figures for different groups of meters, for eg. feeder-wise, DT-wise and consumer-wise for last n periods or specific date-ranges
   • Custom reports
   • Export AMI data to Text files (CSV, ASCII)

Web based front end

Data Acquisition – Meter reading Modules

1. Meter reading modules with DLMS/COSEM, Mod-bus RTU/ASCII/TCPIP
2. Meter reading module with IEC62056-21 
3. Meter reading modules with ANSI C12.x
4. Meter reading modules for MIOS and custom protocols

Data Delivery Modules (Data export options)

1. DLMS/COSEM Server
2. Modbus server (RTU/ASCII/TCP)
3. ODBC
4. OPC-DA Server
5. OPC-AE Server
6. OPC-UA Server
7. Enterprise messaging publish/subscribe bus through SYNC6000
8. Customized interfaces for specific integration requirements

Distributed database

1. All meter data from different protocols stored in common format enabling cross-platform reports
2. Scalability achieved through automatic distribution of data across multiple database servers

Communication subsystem

1. Communication channels can be plugged into the system through the LAN, by using Kalkitech gateways and terminal servers, leased lines to service providers, modem banks etc
2. Support for direct serial connections, serial connections extended with radio, PSTN, GSM modems, GPRS/CDMA based IP networks, TCPIP on direct Ethernet or WAN etc

Notification subsystem

1. Notification through SYNC6000 enterprise bus to subscribed clients
2. SMS Notifications to subscribed users

1. Multiple meter reading modules can run on different machines publishing and subscribing to/from the Bus
2. Multiple database modules (clustered) can run on different machines to support the entire AMR database, plugging into the Bus
3. Multiple channels can be added through FEPs and terminal servers, with specific allocation to MRMs, data delivery modules and notification engines
4. HMIs can be run on multiple machines with access to all Databases through the Bus
5. All components can also be run on a single machine for small-scaled deployments

Security

1. The AMRS shall provide security by enabling VPN across unsecured communication channels. This shall be in addition to protocol specific security features like encryption etc. which may not be present in all protocols considered
2. The AMRS user management shall provide authentication and audit-trail logging of user activities
3. The AMRS user management shall provide authentication and audit-trail logging of user activities

Control Center/Data Center