WIXLIB

Smart Grid Architecture DevelopmentIEEE Power & Energy Society SF ChapterElectric Grid Modernization (Smart Grid) WorkshopOctober 17, 2011San Francisco, CaliforniaJoe Hughes, CEOReef Energy Systems, LLC

SOME DEFINITIONSArchitecture: The Structure of Components, their relationships,and the principles and guidelines governing their design andevolution over time**DoD Integrated Architecture Panel, based on IEEE Std 610.12

DEVELOPING ARCHITECTURE FOR THE SMART GRID Why: Business and Technical Drivers BehindArchitecture Development What: Architecture Development: Some Basics How: Smart Grid Architecture DevelopmentProcesses

Drivers for Architecture developmentMore automation equipment is required to beintegrated and interwork Across more functional and department“boundaries” with more robust implementations against futureobsolescence to be operated seamlessly into anenterprise/industry wide system. to be well managed and adequately secure and all to be supported by fewer people

TODAY’S SITUATION: “SMART” COMMUNICATION ANDAUTOMATION SYSTEMS “Islands of Automation”Little IntegrationAcross the IndustryProprietarySystemsCommunication SystemsWhere’s theArchitecture?No Integration withConsumer Equipment

WITHOUT ARCHITECTURE

Business Drivers For Open Standards Capital Cost Savings– Competitive Procurement of intelligentequipment through Standards and OpenSystems– Multi-vendor support and avoidance of singlevendor “lock-in”– Extensible and Scalable “Industry-wide” Life-Cycle Cost Savings– More uniform Standards based systems– Extensible for the Future– More capable systems, easier to maintain– Immune to single vendor limitations Security Policy Implementation

Open Standards Are Not Enough WithoutArchitecture Many existing “solutions” are not solutions cannot be integrated with other systems cannot be scaled up to large numbers lack critical capabilities such as managing securitypolicies consistently across domains devices and networks cannot be effectivelymanaged on the required scale data cannot be effectively managed on therequired scales systems cannot be maintained at reasonablecosts over the long term cannot be effectively extended for future needs

General Economic Drivers For ArchitectureOpen SystemsImplementationsCapital CostReductionsSystems Engineering andArchitecture MethodsLife Cycle Cost Robust DesignsReductionsEnablingInfrastructuresDecrease CostsCommunicationsAsset sEnable ConsistentIncrease ValueManagement/Security

Architecture Development is Required to EffectivelyIntegrate Open Standards Multi-vendor procurement of interoperable equipment (Capital ) integration of equipment from different vendors.(Avoid singlevendor “lock-in”) Avoid functional lock-in, minimize obsolescence Save life-cycle costs: system upgrades and maintenance (O&M ) Leverage available Human Resources Consistency in minimum sets of critical requirements Avoiding “Forklift Upgrade” (O&M ) Bottom Line: Architecture Development is Requirement for theSmart Grid to Exist

Why do an architecture? Necessary to manage complexity More completely and accurately link: goals, business models,drivers and stakeholders with supporting technical developmentand management processes Provides approaches to enterprise and industry leveldevelopment and documentation Enables understanding of synergies/problems that lower levelviews miss Primary approach for consistently establishing and implementingsecurity policies across the enterprise/industry Currently there is no complete open architecture for smart grid

ARCHITECTURE IS CRITICAL TO MEET SPECIFIC GOALS“Section 1305(d) of the Energy Independence and Security Act of 2007 directs theCommission to institute a rulemaking proceeding to adopt such standards andprotocols as may be necessary to insure smart-grid functionality andinteroperability in interstate transmission of electric power, and regional andwholesale electricity markets once it is satisfied that the work of the NationalInstitute of Standards and Technology has led to “sufficient consensus” on smartgrid interoperability standards.”UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION[Docket No. RM11-2-000] Smart Grid Interoperability Standards(Issued July 19, 2011)

ARCHITECTURE DEVELOPMENT IS THE ONLY WAY THAT SPECIFICSTAKEHOLDER AND POLICY GOALS CAN BE ACHIEVED Security Policy Management Systems Management Industry Level Integration– ISO/RTO Operations across ISO lines Wide Area Situational Awareness– Customer End Use Equipment Integration Electric Vehicles Heating, Ventilation, and Air Conditioning Appliances Other Other

PRESENTATION OVERVIEW Why: Business and Technical Drivers BehindArchitecture Development What: Architecture Development: Some Basics How: SGIP Smart Grid Architecture Committee

ARCHITECTURE IS NECESSARY FOR LARGE SCALE DEVELOPMENT Standards, User Implementation Agreements, Technology Guidelinesand other documents are important building blocks but are insufficientin themselves for large scale integrated systems like smart grid Architecture provides the integration necessary to bring together the fullvision of the intended system– Identify key domains and domain interfaces– Identify where open standards need to be harmonized, unified orotherwise integrated– Identify and manage how legacy systems should be integrated Architecture is necessary to ensure a minimum levels of completeness insystem requirements including the following categories:– Systems and Network Management– Security Management– Applications Development– Requirements Traceability to Identified Stakeholder Needs

“IT”Power procurementMarket operationsRegional TransmissionOperatorDistribution Control CenterExternal corporationsPower ructureDataintegrationApplicationsArchitecture: Developing and Managing IntegrationAcross the Greater Smart Grid IndustryLarge Scale GenerationintegrationTransmission AMIDER integration“PE”

Characteristics of differentENABLE INTEGRATION ACROSS DIFFERENT “ENVIRONMENTS”distributed computing icationDelayToleranceDelays ution“Soft”Real-timeShort delays aretolerableDatabaseaccess overa LAN“Hard”Real-timeDelays can failan application, delaysmust be tions

Architecture Development FocusBusiness &Industry GoalsTechnical EnterpriseArchitectureDomain ArchitecturesData, communications andmanagement system architecture(s)Applied Technology and Components

DEVELOPING ARCHITECTURE FOR THE SMART GRID Why: Business and Technical Drivers BehindArchitecture Development What: Architecture Development: Some Basics How: SGIP Smart Grid Architecture Committee

SYSTEMS ENGINEERING: REQUIREMENTS DEVELOPMENT Requirements Types– Functional Describe the functions of the application: What theApplication Should do for the end-user– Non Functional Describe the supporting functions to enable theapplication to properly execute Also includes systems and networking management aswell as security

RECOMMENDED APPROACHES: DEVELOP FUNCTIONAL AND NONFUNCTIONAL REQUIREMENTS TOGETHER Applications:– System must support the requirements coming from powerengineering needs Systems and Network Management:– Installed communications networks and intelligent equipment mustbe able to be observed and maintained Security:– System must include adherence to security policies and includesystem “hardening” as well as managing residual risk

REQUIREMENTS SOURCES From Existing Systems Documentation System and Technology Plans Stakeholder Interaction– Power Engineers– Systems Administrators– Security Personnel Standards and Consortia Industry Plans and Documents For Future Systems– EPRI Reports and Project Results Ideally:– A combination of Text and Graphical Representation– Standardized Terminology to the extent possible– Use of Computer Based Tools and a “Model” of systemcharacteristics

REQUIREMENTS DEVELOPMENT: USE CASE AND REQUIREMENTSDEVELOPMENT TEMPLATE“Word” DocumentSpreadsheetUsed for narrativediscussionPerformanceLevel Details

Conversion from Requirements to IndustryModels One Method“Use Case de Area ControlADARTPWide Area Mea DOMAImportWordTemplatesinto theCASE ToolCreate agraphicalrendering(UML)Computer Aided SystemsEngineering (CASE) Tool

ARCHITECTURE HOW: ENABLES MORE COMPLETEREQUIREMENTS DEVELOPMENT Necessary to encompass different stakeholder perspectives– Applications Development– Security– Technical Management (includes Life-cycle management) Thorough Requirements are Critical for–––– Field Equipment with limited resourcesForward looking and Robust Network and Physical Communications DesignsDeveloping Robust Standards leading to robust system designsDeployments of field equipment must last 20 to 30 yearsConsequences of weak or incomplete requirements– Cost of incomplete requirements caught at design time .caught at implementationtime caught after deployment .

UNDERSTAND THE COMPLEXITIES WITHIN THE REQUIREMENTSReal-Time Pricing Enterprise Activity (RTP Function)Showing Interactions and Information Flows between ApplicationsMarket Operations SystemsEnergy Services Providers SystemsSubmit aggregatedenergy schedulesScheduleEnergy Database Aggregateenergyschedules Database Energy SchedulesManage AncillaryServicesAggregatedCustomer SchedulesSubmit ancillaryservices offersAggregateancillaryservicesbids/offers Database Ancillary ServiceBids/Offers Database Trigger calculationevery hourCalculateBaseRTP TimeOfDay Provide energyschedulesProvideforecast loadsMarketTimerAggregatedCustomer OffersMarket Interface Server Database CalculateRTP rate tables perCustomer Type Database Forecast PowerSystem ConditionsCustomer LoadForecastSend base RTP dataProvide ancillaryservice bids/offersBase RTP Data Database Forecast Loads Database CustomerGeneration OffersMarketTariffSecurity is majorconcernAudit RTPReceive weather dataWeatherExternal OverseersAvailability, highspeed, andaccuracy aremajor concernsSend powersystem data such asscheduled outagesSend powersystem data such asscheduled outagesTransmission Operations SystemsMonitorTransmissionPower SystemValidateCompliance Database Transmission PowerSystem DataSupmit DRgeneration offersAuditDataRegulatorsSubmit customerload forecastsAudit Customer-specificRTP Rate TablesAudit RTPValidate marketrules for RTPAuditorsConfiguration and mediaissues are major concernsDistribution Operations Systems Database Distribution PowerSystem DataMonitorDistributionPower SystemMulti-cast RTP toselected customer systemsCustomer Building Automation System powertype Transmission PowerSystem powertype Distribution PowerSystemAvailability, highspeed, andaccuracyDistributed Energy ResourcesMonitor DRControl DR PowerSystemDevice DistributedResources DataManage es and offers Database Customer-specificRTP rate table Human CustomerSet and reviewparametersTrigger load andgeneration forecastsOptimize load and DRoperations based on RTPSchedule DR generationSchedule loadsProvideload dataCreate load schedule Database DER Schedule powertype CustomerLoads Database Load schedule TimeOfDay ForecastTimer

Industry-Level Architecture Seeks toIntegrate Between StandardsFramework forManagement andSecurity rmonizationin progressIEC61850IEC61968MaturingANSIC12IEC61970IEC TC 13IEEE1459PartialEIA 600MissingIEEESCC31ASHRAESSPC 135IntegrationbetweenStandards(ProposedWork)

Gridwise Architecture to SGIP Priority Action Plan MapBusiness ProceduresPhysical Connection111System EvolutionDiscover & ConfigPerform, Reliable, ScaleSystem PreservationXaction & State MgmtLog & Audit1Security & PrivacyBusiness ObjectivesTime-Sync & SequenceResource IdentShared meaningEconomic/Regulatory2234Business Context3645Semantic Understanding59 10 117841612 13 146777881212121313131414148Syntactic Interoperability910Network Interoperability111215Network Interoperability1115151628