Case Study: Semantic Integration as the Key Enabler of Interoperability and Modular Architecture for Smart Grid at Long Island Power Authority (LIPA)

Transcription

1 Case Study: Semantic Integration as the Key Enabler of Interoperability and Modular Architecture for Smart Grid at Long Island Power Authority (LIPA) Predrag Vujovic, Stipe Fustar, Phillip Jones, Fran Clark

2 Overview Real-life Case Study of LIPA Architecture and integration approach in their Smart Grid Program Our Story: LIPA Smart Grid Architecture approach Semantic Integration as the Key Enabler of Modular / pluggable architecture A real-life solution change scenario (switching from one solution provider to another one / ( unplug one and plug another system)

3 LIPA -driven Architecture Business Drivers Establish a loosely-coupled SOA architecture through : Leveraging an Exchange (EXM) for model-driven development, that mediates all interfaces through a LIPA Enterprise Semantic (ESM), which is based on available industry standards (e.g. CIM) Use of a model-driven design and development process to: Speed development process Improve reusability Improve governance and change management Require that any new vendor applications: Conform to LIPA end points (canonical interfaces, staging areas) as much as possible / practical When not possible, conform to applicable industry standard interface Publish interfaces / APIs so that knowledge of underlying database structures is not required for integration (transactional or analytical)

4 Key Elements of LIPA Semantic Integration Centrally Managed Semantic (Data) Heterogeneous interfaces mediated through common model Based on industry standards (IEC CIM is the key reference model) Centrally Managed Semantic Mapping and Business Rules Integrate & Reuse Business Rules, transformations, mappings Automate gap analysis, documentation Centrally Managed Development and Run-Time Deployment Generate ready-to-go SOA services Continuous testing Deploy into any runtime environment Automate impact analysis on change 6

5 LIPA -driven Architecture Benefits Reduce cost of implementations and integrations including maintenance / change management Reduce risk to implementations and integrations Increase speed of implementations and integrations Improve ability to solve business problems by choosing best of breed applications and services Avoid vendor- and technology lock-in s Support Multiple Service Providers Architecture: Near Plug and Play, Flexibility, Agility & Portability Consistent semantics for data in-flight and persisted data stores Event-driven Flexibility of Business Intelligence Options Open to new technology, solutions, applications

6 Foundation -driven process LIPA has adopted a model-driven process for defining, designing, developing and deploying: Services on the Enterprise Service Bus Persistent data stores for analytics (ODS, Data Warehouse, Datamart) The -driven approach leverages industry standards (e.g. EC CIM) wherever possible to: Promote reusability Accelerate development cycles Facilitate visibility, governance and change management Four key models Enterprise Semantic Service Exchange Data Process & Governance

7 -Driven Information, Integration & Intelligence Semantic ing Relevant Standards (e.g. IEC CIM MultiSpeak) Semantic Mapping Enterprise Enterprise Integration View Process Integration (Simple & Complex Data Exchanges, Transacting processes) Business Intelligence (e.g. Spotfire) Data Services LIPA Specific Utility Domain Dictionary Single / Common Enterprise Semantic Data Services Interface Tier Meta-data Business Logic Tier Focus is on Semantics Data Tier Slide 10

8 Driven Development Integration Services & Data-store Design Design Develop Deploy Cycle (information perspective) Design- & Development Run-Time Industry Standards Reference Trfrm LIPA ESM Reference Base Implementation (ODS, ODW) DB Schema Business Vernacular Application Meta-Data XSD Reference Trfrm Reference Base Gap analysis & extension SM Context Semantic Service Design Inputs Process Design Inputs ODS, ODW CopyBook Reference Trfrm Reference Base Gap analysis Extension import import API etc Reference Reference Base Trfrm Gap analysis Extension Exchange Driven Development Map once & Develop Mapping Reports Gap Analysis Impact Analysis Test Deploy Versioning Impact Analysis DXSI Run-time Components

9 Common Data Centralized Data Enterprise Semantic XMI LIPA EDM Workflow : Lossless Metadata The Information Architecture team implements the exchange model integrating with the necessary systems and performs initial data transformation testing Centralized Mapping, Design Enterprise Exchange DXSI Components for production are generated by the integration team, re-tested and passed to the operations team for deployment Testing Operations Team deploys Components in the production environment. Distributed run-time ESB Local requirements The Information Architecture team customizes the common data model with local requirements Information Architecture Schema Schema Schema Xtensible Solutions Continuous Inc. Testing Integration Team The Integration team performs complete testing, including process execution and exception handling. Operations Team Stateless for scalability Runs in any Java container Connects to any bus

10 LIPA ESB Platform by Business Domain

11 LIPA SP Integration-Ready Gateway Energy Trading LIPA and three service providers Repeatable patterns and solutions Staging areas Privacy of participant s internal data and systems Parallel development Ready for future plug and play Centrally managed data model Plans to introduce event-driven patterns T & D OMS, MDM, ODS / ODW, Customer Communication projects data exchanges Centrally managed data model Repeatable patterns and solutions Event-driven patterns Use of Semantic Integrator DXSI and Sonic ESB Ready for future plug and play Proxy/Reverse proxy Secures access to façades of canonical and adaptor-enabled service Host SP queues, if applicable

12 15 Key Integration Patterns

13 Key Integration Patterns - Pluggable Endpoints 16

14 Key Integration Patterns Integration Ready infrastructure Adaptor / Canonical Pattern (P) Canonical Service Patterns (P) (C) Adaptor Service Patterns (P) (C) Adaptor / Canonical Pattern (C) Integration Ready Plug-n-play 17

15 Key Integration Patterns Library of Adaptor / Canonical Pattern (P) Endpoints Canonical Service Patterns (P) (C) Adaptor Service Patterns (P) (C) Adaptor / Canonical Pattern (C) Library of integration-ready / pluggable endpoints and services increases by each project 18

16 Solution Change Scenario: From Vendor A to Vendor B 19 Unplug OMS Solution from Vendor A

17 Solution Change Scenario: From Vendor A to Vendor B Endpoints unaffected by OMS solution change 20 Plug OMS Solution from Vendor B

18 Key Take-Away Points Innovative Integration approach with benefits of Near Plug and Play for systems and Analysis Solutions Driven Development, End-to-End Benefits of automation for integration, testing, maintenance, updates Significantly Lower Life Cycle Cost and more effective system deployments -driven approach that leverages Industry Standards (CIM) for interoperability Scalable (Structured, planned, model-driven approach) Semantic understanding is guaranteed (explicit, not implicit) ; availability of strongly typed syntactical interfaces is not a requirement for success any more Easier updating and tracking of standards development Modular / pluggable architecture has been proven in a real-life change scenario

19 Predrag Vujovic Stipe Fustar Phillip Jones Thank You Fran Clark, Arpeggio Technology