1 / 16

Homeflex Proof of Concept Architecture

Homeflex Proof of Concept Architecture. Sham Dhrampal January 2008. Purpose. To discuss the Homeflex Proof of Concept Architecture To discuss lessons learnt To share the blueprint related to AMI/Smart Metering. Homeflex Architecture.

guang
Télécharger la présentation

Homeflex Proof of Concept Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Homeflex Proof of Concept Architecture Sham Dhrampal January 2008

  2. Purpose • To discuss the Homeflex Proof of Concept Architecture • To discuss lessons learnt • To share the blueprint related to AMI/Smart Metering

  3. Homeflex Architecture

  4. Integration between Vendor Master Stations and Eskom Systems

  5. Application and Integration Layer (EAL)

  6. Application and Integration Layer (EAL) • Wanted a common back-end systems infrastructure to cater for multiple metering systems (Vendor Master Stations) • The metering systems will interact with our back end systems (CC&B, OVS, Maximo) via a common integration /meter data management layer – regulated interfaces • For the Proof of Concept (PoC), this integration and application layer was custom developed. • In future • EAL will be replaced by a COTS product (Meter Data Management system) • All interfacing will comply to IEC 61968 & 61970 (Common Information Model) (refer specifically to IEC 61968-9 Interface for meter reading) • The meter data management system is a building block for metering and will be used by Homeflex and any other related AMI/smart metering initiatives

  7. What does this layer do? • Receives data from billing system, performs mapping and sends on to relevant metering system • Receives data from metering systems, validates and sends (when required) to billing system • Stores • Half hourly data • Master data • Mappings • Load shed schedule

  8. Integration • Between Application and Integration layer (EAL) and billing system (CC&B) • From CC&B to EAL • Master data • Meter read schedule • From EAL to CC&B • Meter Reads (summarised) • Between Application and Integration layer (EAL) and vendor master stations • From EAL to VMSs • Send Load shed schedule • Execute emergency (geyser) load shed • Request on demand meter read • From VMSs to EAL • Meter reads (both half hourly and summarised) • Load shedding notification

  9. Lessons Learnt • Mapping of data between the billing system, EAL and VMSs: • Meters • Meter Reads During PoC, existing interfaces were used, in the next phase information and data architecture to be well defined • Integration between CC&B and EAL during the PoC was flat file based, in future integration will be more real time • Still envisaged that integration to VMSs will be via web services • Shadow billing done in PoC. Transition from conventional to TOU in the billing system requires careful planning: • Process to switch over from standard rates to TOU rates in billing systems • TOU billing approx 4-5 months after smart meter installation • Understand new meter changeout process and systems impact (in which system is data captured first? Which are the source systems?)

  10. Our vision…

  11. AMI/Smart Metering Systems Blueprint • Principles: • The common back-end systems infrastructure will cater for all 3 customer segments (LPU, SPU and prepayment) • Cater for multiple metering systems (also referred to as vendor master stations and head end systems) • The systems blueprint will cater for multiple communication mediums i.e. GPRS, PLC, BPLC, RF etc. • All interfacing will be XML based and comply to IEC 61968 & 61970 (Common Information Model) (refer specifically to IEC 61968-9 Interface for meter reading) • Multi vendor master station (MVMS) is required that can accommodate multiple meters (with different communication protocols) and communication mediums

  12. Systems Blueprint The systems blueprint will cater for the following: • Meter Event Messages • Outage Detection, Meter Health, Tamper/Theft Events • Power Quality Event • Customer Data Synchronization • Meter Readings • Periodic Meter Reads • On-Request Meter Read • Historical Meter Data Access • Billing Inquiry • Meter Control Messages • Load Control • Meter Installation • Meter Configuration • Meter Disconnect and Reconnect • Real-Time Pricing • Downloading of tokens to prepayment meters • Please note that systems blueprint will cater for the above however some of the above functionality depends on the capability of the meter and/or metering system.

  13. Systems Blueprint Metering Systems (Head End Systems) Eskom Systems Metering System 1 Meter Reads Interval data Demand data Voltage data Power reliability and quality events Meter health and tamper detection Outage notifications Meter Install, Remove, Disconnect, Reconnect Meter Data Management (MDM) Meter Reads On request meter reads Customer and meter data synch Remote Connect/Disconnect CIS/ Billing System Metering System 2 Outage Management System Power reliability and quality events Outage and restoration verification Meter Management Metering System 3 Meter health and tamper detection Install, Remove, Disconnect, Reconnect Work Management Metering System 4 Transaction Information (Tokens) Online Vending Server

  14. Reference Architecture (Source: IEC 61968-9 Interface for meter reading)

  15. CC&B CC&B CC&B Load Management Load Management Enerweb Application and Integration Layer COTS, Standards Compliant System for residential and C&I COTS, Standards Compliant System Meter Data Management Meter Data Management Load Management Meter Data Management Meter Data Management Collection Engine Collection Engine MV90 Service Mode (C&I) Collection Engine Vendor System Master Station VMS VMS VMS Meters Meters Meters Meters Meters Meters Meters Meters Meters Meters Meters Industry Standards e.g. DLMS, ANSI C12.22 Blueprint for Open Standards phasing-in Proof of Concept • Use proprietary system master stations and meters • Enerweb layer providing application and integration with custom developed components for meter data management (MDM) and load management Transition (Plug-in Plug-out) • Replace meter data management and collection engines with COTS, standards compliant products • MDM to be used for settlements, KSACS, Homeflex and LPU’s • Remove proprietary vendor master station systems National Rollout • COTS, standards compliant system with collection engines for residential – Multi-vendor Master Station • Majority of functionality resides in multi-vendor master station and not meters (although meters need to be smart meters, ToU capable) Proprietary Open Standards X 3 COTS/MVMS

  16. Homeflex Roadmap

More Related