Stephan Amsbary EnerNex. #ConnWeek

Transcription

1 Smart Grid (Enterprise) Architecture 101 Stephan Amsbary EnerNex #ConnWeek

2 Architecture as usually practiced ARCHITECTURE OR BUY A VENDOR S PACKAGE (Apologies to Mr Adams and my fellow architects) There is never enough time (or money) to do it right the first time There is always enough time and money to fix it over and over again -Anonymous #ConnWeek 2 Santa Clara, CA May 23-26, 2011

3 What is Architecture? IEC : The formal organization of a system embodied in its components, their relationship to each other and the environment and the principles governing it s design and evolution. Architectural process is a phased approach. It documents with every increasing levels of granularity and specificity, the requirements, relationships, services and sequence necessary to realize those goals Architectural art is intuition tempered by experience; it usually takes practice to master. Artistry is needed to define the appropriate levels of component ontological abstraction for each phase Enterprise Architecture is the process of translating business vision and strategy into effective organizational change. #ConnWeek Santa Clara, CA May 23-26, 20113

4 Why We Need Architecture Logical but? Yes, it s a Kitchen/ Bathroom First in first out/ Priority of the day Input OR Architectural Process Output

5 Architecture uses Frameworks Including TOGAF*, DoDAF, MoDAF, FEA, Zachman, &c They have their own Methodology, Techniques and Tools Incorporate Lifecycle maps for Project Management (PMO) and Systems Engineering lifecycles (ITIL) * The Open Group Architecture Framework

6 Architecture Phases Rather then trying to eat an elephant all at once, architecture identifies goals and decomposes them into services that ultimately relate to the physical entities Don t worry we ll cover phases E H later This breaks-down into: Preliminary, What do you have Vision, what goals you trying to achieve Requirements, what needs do the goals impose Business Services, what abstracted services are needed to support a requirement Information (or Application) Services, what sort of applications are needed to support the abstracted service Technical Service, what is actually performing the service

7 Architecture Ontology In Philosophy, Ontology is the study of reality which defines objects by looking for the natural joints between objects. By extension in Computer Science, Ontology is a domain model used to identify components/servicesservices and their relationships to each other (their interfaces) Joints or interfaces Input Output Process/ Service Component Actor Actor

8 Simple Building Architecture Example Magic in this case is the ability to infer the options Input Joints or interfaces Process/ Service Output Vision Comfort Requirements Water Heat/Air Light Outside environ Sanitary Business Services Hot Water Source Treatment Application Services Solar Gas Electric Technical Services Panels Batteries Inverter &c Green Energy Eff Material Reuse Rebates Budget Op Costs Initial Cost Timeframe Rate Incentive

9 Why we need sequence Sequence ensures the right thing is done in the right order & illuminates alternatives It s not as easy as it sounds Impact of no sequence 1. Build High Rise Complex 2. Dig drainage canal to prevent flooding

10 Sequence changes based on the Situation Simple restaurant * example Business Requirement Business Service A. Sit-down Restaurant B. Fast Food Chain 1. Order 2. Eat 3. Pay 1. Order 2. Pay 3. Eat * Courtesy of Doug Houseman C. Buffet 1. Pay 2. Order 3. Eat

11 Smart Grid Architecture Produces Strategic Plans Technical Road Maps Use Cases Reference Models Vendor selection Migration Plans Change Requests Security and Governance In short what is required to move from today s state to the stakeholder s goal

12 TOGAF Iteration & Architecture layers TOGAF cycle and corresponding Artifact level of detail Contextual Conceptual Logical Physical Conceptual Logical Physical Conceptual Logical Physical Contextual/Vision What are the Goals What is the current state Conceptual What it shall accomplish What services are required Logical How it shall be accomplished How is the architecture structured Physical What resources shall be required

13 Architecture roadmap Business Automation Technologies Input from strategy & context Business Architecture Information Architecture Automation Architecture Physical Architecture Conceptual What? Vision/ Contextual Why? What is the business What are the info processing requirements What type of applications are required What physical IT services are required Logical How? How is the business structured How is information structured How are these systems structured How are the boxes structured Physical With what? Which parts of the business will change What manual & automated processes need to be linked What packages & bespoke software What Hardware, software & network component

14 NIST Conceptual Architecture Effort 9500 pages of national laws 400 National Goals 20 high level families 655 Use Cases, 20 System Requirement Documents, 33 originators Requirements 400 high level families of requirements 400 business requirements 450 technical requirements (4 domains complete, 3 to go)

15 Number of new business requirements (based on NIST Conceptual Architecture Project Analysis) #ConnWeek Santa Clara, CA May 23-26, 2011

16 The Rest of the Story Ok, now we understand what it takes to design a Smart Grid. Now we have to implement it, migrate legacy procedures/systems, operate it, handle changes and ensure governance Yikes. Remember the other half of the cycle? That s where those areas are handled This ensures the architecture stays viable instead of stale Think of this as your honey-do list #ConnWeek Santa Clara, CA May 23-26,

17 (Smart Grid) Architecture Summary Affects the entire organization, not just computer techies Small steps with a little magic (experienced insight) to transition from one step to the next A process that minimizes risk and gives insight into how the business operates today and what changes are needed to achieve the business Smart Grid objectives Initial work being done being identified by NIST SGAC A means to: Gain operational efficiencies Maximize assets and personnel Bring order to IT delivery - aligning Business Services with the underlying automation Services-Oriented (SOA) foundation

18 Questions (or see me at our booth) How does this work? Electric Research, Engineering, and Consulting STEPHAN AMSBARY Director, Utility Enterprise Architecture Phone: FAX: Grants Mountain Rd, Marion, NC, #ConnWeek Santa Clara, CA May 23-26,

19 TOGAF Architecture / process Vision what are the enterprise s vision (goals/objectives) and current corporate/it context Drivers: business case, regulation Legacy: processes, systems/applications Principals: foundation software (eg: SAP), outsourcing, security/privacy Requirements, scope, duration Business Services functions are needed to support the goal(s) Service decomposition, process/steps, organization Information documents & processes needed to support those services System Atomic functions (ultimately applications) providing those objects Plus: Security How information, processes and infrastructure are protected Governance How oversight is executed Information Technology what sort of technology and configurations required to support those applications requirements

20 Overview Smart Grid Enterprise Architecture Roadmaps High-level vision/goal attainment Business Case Goal business justification, risk & benefits Use Cases High-level vision/goal attainment DMS Vendor-G Network Vendor-F Substa-Auto Vendor-E Distirb-Auto Vendor-D AMI Vendor-A AMI Vendor-B AMI Vendor-C Pilots Test vendor capabilities Meet immediate stakeholder requirements Architecture Integration plan for entire ecosystem

21 Where our EA practice lives 21