Matthew Hause: The Smart Grid and MBSE Driven IoT
•
2 likes•1,317 views
EnergyTech2015.com Track 3 Session 3 Moderator: Mark Walker The integration of the Internet of Things (IoT) and MBSE in an Energy System and Complex energy grid management in a changing and dynamic future. Matthew Hause – Paper 1: Making the Smart Grid Smarter, MBSE Driven IoT The future of IoT success, including technology advancements and revenue generating potential across the business spectrum, is dependent on the application of solid Systems Engineering and Model Based Systems Engineering (MBSE) principals. Without MBSE, the complexity involved in the design, development, and deployment of IoT systems would consume both system and operational providers. Absent of any industry standards, IoT systems cannot be built in a vacuum and their success will only be realized through application of modern day systems engineering processes, methods, and tools. The infrastructure and management will need to be established prior to, or in conjunction with, the smart systems that support them. This paper will show an Energy system and connected systems and how an MBSE and SoS approach will help guide development.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (12)
Similar to Matthew Hause: The Smart Grid and MBSE Driven IoT
Similar to Matthew Hause: The Smart Grid and MBSE Driven IoT (20)
More from EnergyTech2015
More from EnergyTech2015 (20)
Recently uploaded
Recently uploaded (20)
Matthew Hause: The Smart Grid and MBSE Driven IoT
- 1. MATTHEW HAUSE The Smart Grid and MBSE Driven IoT
- 2. Agenda • System of Systems Modeling (SoS) • MBSE Overview • The Smart Grid • Systems Modeling (SysML) • The Internet of Things (IoT) • Summary
- 3. Complex Systems of Systems • “Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist, but that's just peanuts to space.” • Douglas Adams, The Hitchhiker's Guide to the Galaxy • Common SoS characteristics: operational independence of the individual systems, managerial independence, geographical distribution, emergent behavior and evolutionary development or independent life cycles. • Complex systems of systems: • Smart Cities • The energy grid • The Internet of Things
- 4. The Energy Grid - Transmission • The transmission network • The high voltage network comprising generating plants, substations, transmission lines, circuit breakers, high voltage transformers, etc. • Often at multiple voltage levels such as 69kv, 138kv, and 345kv. • Large geographically dispersed systems • Multiple operators and regulators • Overlapping responsibilities and control • Generally very reliable, resilient, dependable and flexible • However, most are run for profit so resources are limited • Thousands of interconnections and points of failure • Outages can be catastrophic • Northeast US and Canada blackout of 2003 • European blackout of 2006 • Southwest 2011
- 5. The Energy Grid - Distribution • The distribution network • Low(er) voltage network comprising substations, distribution lines, circuit breakers, low(er) voltage transformers, capacitors, consumer/customer drops, metering systems, etc. • Often at multiple voltage levels such as 39kv, 12kv. • Local(ish) geographically located systems • Single operator and (usually) single regulator • Concentrated responsibilities and control • Generally very reliable, resilient, dependable and flexible • However, most are run for profit so resources are limited • Often monopoly operated • Thousands of interconnections and points of failure • Consumer/customer oriented • Outages are normally localized
- 6. The Energy Grid - Generation • The generation “system” • Electricity suppliers of multiple capacities and owners • Corporate high capacity nuclear systems • Corporate medium capacity fossil fuel – coal, gas, etc. • Municipal local generation • Government and private hydro generators • Industrial co-generation • Distributed renewable generation • Solar panels on homeowner houses • Etc. • Multiple cost/efficiency/availability models • Outage impact depends on load, capacity, network state, local and distributed circumstances, etc.
- 8. Potential Causes for Network Failure • Excess of demand • Bad weather conditions • Physical obstacles such as trees • User error • Understaffing • Miscommunication • Faulty telemetry • Etc. • Most blackouts are caused by a combination of these
- 9. Fault Condition #1 – Conductor Overload Results in Short • This fault was one of the causes of the East Coast blackout in 2003 • Transmission lines (69KV, 138KV, 345KV), and most primary lines (12KV, 19KV) are bare conductors. • Insulated conductors cause the line to overheat and reduce capacity. • Conductors therefore placed away from obstructions (buildings, trees, etc.) • However, lines often in forested areas, meaning trees need to be cut back. • On this occasion, the trees were not cut back, the lines overloaded and sagged, making contact with the trees. • (The laws of physics remain constant in spite of our best efforts) • The circuit breaker on the line opened • This resulted in the loss of a major line, causing other lines to overload, and so forth.
- 10. Fault Condition #2 – Real/Reactive Power Mismatch • Power factor is the ratio of the real power to the reactive power flowing to the load. • Also known as cosine (phi). • A dimensionless number between 0 and 1. • Important when assessing voltage profiles, reactive reserves, and voltage stability. • Reactive elements can interact with the system and with each other to create resonant conditions, resulting in system instability and severe overvoltage fluctuations. • High air-conditioning loads lower the power factor • This was a contributing factor of the 2003 Northeast Blackout.
- 11. THE INTERNET OF THINGS (IOT)
- 12. 2010 2020 2035 7 Billion Connected Devices 50 Billion Connected Devices 1 Trillion 5M APPS 100M APPS 5B
- 13. The Internet of Things (IoT) • Systems used to be mechanical and electrical parts • Now complex systems that combine hardware, sensors, data storage, microprocessors, software, and connectivity. • “Smart, connected products” enabled by: • Improvements in processing power • Device miniaturization • Ubiquitous wireless connectivity. • Smart, connected products have three core elements: • Physical components, • “Smart” components, and • Connectivity components. • Smart components amplify the capabilities and value of the physical components, while connectivity amplifies the capabilities and value of the smart components and enables some of them to exist outside the physical product itself such as in the cloud. Smart, connected products require a rethinking of design. At the most basic level, product development shifts from largely mechanical engineering to true interdisciplinary systems engineering.
- 14. Company Network IoTArchitecture BUSINESS LOGIC 3D STORAGE ENGINE REST APIs SYSTEM SERVICE INTEGRATION COMMUNICATIONS BIG DATA ANALYTICS CLOUD SERVICES BUSINESS ENTERPRISE SYSTEMS Sensors, Devices & Equipment Connectivity Application Enablement Connected Applications MASHUP BUILDER SQUEAL External System & Services Products Plants Logistics
- 15. The Smart Grid • An electrical grid which includes a variety of operational and energy measures including smart meters, smart appliances, renewable energy resources, and energy efficiency resources. Electronic power conditioning and control of the production and distribution of electricity are important aspects of the smart grid. • Roll-out of smart grid technology also implies a fundamental re- engineering of the electricity services industry. • “For many, smart grids are the biggest technological revolution since the Internet. They have the potential to reduce carbon dioxide emissions, increase the reliability of electricity supply, and increase the efficiency of our energy infrastructure.” • Berger, Lars T. and Iniewski, Krzysztof, ed. (April 2012). Smart Grid - Applications, Communications and Security.
- 16. The Smart Grid Motivation • Improved telemetry systems • Variation in demand during the day • Smart metering systems • Renewable Energy • Wind, solar, hydro, co-generation systems, geo-thermal, etc. • Change from centralized grid topology to one that is highly distributed. • Power is generated and consumed right at the limits of the grid. • Deregulation of the electricity industry • Leading to higher risk (See ENRON) • Situational awareness
- 17. Smart Grid Goals • Reliability • Fault detection, fault prediction, state estimation, multiple routes, etc. • Flexibility in Network Topology • Bi-directional energy flows allowing for distributed generation, local generation, etc. • Efficiency • Demand-side management, load adjustment/balancing, peak leveling, time of use pricing, etc. • Sustainability • Enabling renewable energy: solar, wind, tidal, geo-thermal. • Force-multiplier will be energy storage • Market Enabling • Increased communication between suppliers and consumers, variable tariffs, demand response support, etc. • Consumer awareness • Smart meters, smart homes, supplier choice, device demand, etc.
- 19. Modeling The Energy Grid • Different models are possible • The physical network • The telemetry and Supervisory Control and Data Acquisition (SCADA) system • The telemetered view via the SCADA system • The analyzed view via the load flow program • A simulated view for performing what-if scenarios based on current data • A historical view for reviewing the cause of problems and network outages • A model of the human operators making decisions • Etc.
- 20. System Engineering Process Conceptual Architecture Functional Architecture Logical Architecture Physical Architecture C1 C2 C3 F1 F2 F3 F4F5F6 F11 F12 F5L1 L2 L3 F3 F4F13 P1 P2 P3 P4P6 P5 P7 Requirements Test,V&V
- 22. Electrical Network – Stakeholder View • Use cases represent goals, actors are stakeholders
- 23. Electrical System Building Blocks • Customer Load • Consumer of electrical power • Generator • Generates power for the customer • Conductor • Transfers power between equipment «block» operations New () ConsumePower (in Tm : Timespan) Resistance () : Single Inductance () : Single Capacity () : Single Load «block» operations New () GeneratePower (in Tm : Timespan) Resistance () : Single Inductance () : Single Generator «block» operations New () TransferPower (in Tm : Timespan) Resistance () : Single Inductance () : Single Capacity () : Single CKTOpen () : Single HighLoad () : Single HighVolt () : Single HiHiLoad () : Single InAlarm () : Single LowVolt () : Single Transfer () ScalarPower () : Single TR Conductor
- 24. Electrical System Building Blocks • Transformer • Converts electrical power between different voltages • e.g. 69KV for transmission, 22KV for customers • Substation • Connection point for transmission and distribution lines «block» operations New () TransferPower (in Tm : Timespan) TurnsRatio () : Single PrimaryResistance () : Single PrimaryInductance () : Single PrimaryCapacity () : Single SecondaryResistance () : Single SecondaryInductance () : Single SecondaryCapacity () : Single TR Transformer «block» operations New () TransferPower (in Tm : Timespan) Resistance () : Single Inductance () : Single Capacity () : Single CKTOpen () : Single HighLoad () : Single HighVolt () : Single HiHiLoad () : Single InAlarm () : Single LowVolt () : Single Transfer () ScalarPower () : Single Substation
- 25. Behavior Specification – Conductor Overload • The overload condition logic is specified with a state machine • This models the states, reset capabilities, faults and other behaviors
- 26. Simple Network Topology • Simple network showing generation, transmission, and distribution ibd [block] Electrical Network Context Small «block» Electrical Network Context Small GN1 : Generator QOut : PwrTx CN4a_TR1_LDs : TRConductor QOut : PwrTx QIn : PwrTx LD1 : Load QIn : PwrTx RPh : RephasingUnit QIn : PwrTx ARPh : AutoRephasingUnit QIn : PwrTx SW1 : Switch LD2 : Load QIn : PwrTx CN2_SW_TR1 : TRConductor QIn : PwrTx QOut : PwrTx TR2_SW_CN4 : TRTransformer QIn : PwrTx QOut : PwrTx CN4_TR2_LD3 : TRConductor QIn : PwrTx QOut : PwrTx LD3 : Load QIn : PwrTx TR3_CN3_CN5 : TRTransformer QIn : PwrTx QOut : PwrTx CN5_TR3_LD4 : TRConductor QIn : PwrTx QOut : PwrTx LD4 : Load QIn : PwrTx SUB1 : Substation QIn : PwrTx QOut : PwrTx TR1a_11k_69k : TRTransformer QIn : PwrTx CN1b_TR1a_SUB1a : TRConductor QIn : PwrTx QOut : PwrTx CN1a_GN1_TR1a : TRConductor QIn : PwrTx QOut : PwrTx TR1_11k_380 : TRTransformer QIn : PwrTx QOut : PwrTx TR1b_69k_11k : TRTransformer QIn : PwrTx QOut : PwrTx SW_TR1b_CN2QIn : PwrTx QOut : PwrTx SW_CN3_TR2 QIn : PwrTx QOut : PwrTx CN3_TR1b_SW : TRConductor QIn : PwrTx QOut : PwrTx ResetT- R2 ResetT- R1 ResetT- R1b ResetT- R3 ResetT- R1a ResetGN
- 27. ibd [block] Network Display Context Small «block» Electrical Network Context Small CN2 : TR Conductor QOut : PwrTx POut : OBooleanValue CN2_Disp : PwrDisplay InP : PwrTx PwrToday : PwrDisplay InP : PwrTx GN1 : Generator QOut : PwrTx TR1_Disp : PwrDisplay InP : PwrTx GN1_Sub1 : TR Conductor QOut : PwrTx POut : OBooleanValue Pwr1 : PwrDisplay InP : PwrTx TestLamp : Lamp PIn : OBooleanValue TestSwitch : SSwitch POut : OBooleanValue GN1_Sub1_alm : Lamp PIn : OBooleanValue CN2_alm : Lamp PIn : OBooleanValue CN3 : TR Conductor POut : OBooleanValue QOut : PwrTx CN4 : TR Conductor POut : OBooleanValue QOut : PwrTx CN5 : TR Conductor POut : OBooleanValue QOut : PwrTx CN3_alm : Lamp PIn : OBooleanValue CN4_alm : Lamp PIn : OBooleanValue CN5_alm : Lamp PIn : OBooleanValue SUB1 : SubstationPOut : OBooleanValue QOut : PwrTx SUB1_alm : Lamp PIn : OBooleanValue CN1a_GN1_TR1a : TR Conductor POut : OBooleanValue QOut : PwrTx CN1b_TR1a_SUB1a : TR Conductor POut : OBooleanValue QOut : PwrTx CN1a_alm : Lamp PIn : OBooleanValue CN1b_alm : Lamp PIn : OBooleanValue Network Topology with Input Controls • Separate diagram within the same context (Electrical Network Context Small) • Clarifies relationships without cluttering the diagram
- 28. ibd [block] Electrical Network Context Small [1] «block» Electrical Network Context Small LoadX : SingleValueGenerator Out : POutput LoadImp : SingleValueGenerator Out : POutput LoadImp2 : SingleValueGenerator Out : POutput LoadX2 : SingleValueGenerator Out : POutput LoadX3 : SingleValueGenerator Out : POutput LD3 : Load InSimR : OSingleValue InSimX : OSingleValue LoadImp3 : SingleValueGenerator Out : POutput LD4 : Load InSimR : OSingleValue InSimX : OSingleValue LoadImp4 : SingleValueGenerator Out : POutput LoadX4 : SingleValueGenerator Out : POutput LD2 : Load InSimX : OSingleValue InSimR : OSingleValue LD1 : Load InSimX : OSingleValue InSimR : OSingleValue Consumer Loads with Input Controls • Separate diagram within the same context showing control inputs
- 29. Dynamic Displays
- 31. Connected Field Service Management ManageandExecute Service Event Execution connects products with the remote and field technicians • Auto-Creation of Work Order and Cases improve response time – Products are the first to report the problem • Remote Access to Connected Devices reduces field service costs – Technicians can remotely access devices, perform file transfers and software upgrade • Automated diagnostics improve first time fix rate – Diagnostics are automated based on data from the connected device to provide the best solution to the problem • Access to diagnostics and repair procedures improves technician productivity – Technicians can view the results of the automated diagnostics session, and can continue the diagnostics as needed – Technicians can view repair documentation as required
- 32. • Product is identified (QR, Barcode, Serial Number, etc.) • As manufactured, or latest as maintained, Software configuration obtained from the product cloud. • Product publishes software configuration to App • Differences highlighted to the user • Software updates that are available • Known issues against existing configuration • Critical security vulnerabilities • Opportunity presented to: • Learn more about findings • Update software OTA WithAugmented Reality (Software Configuration) VU#577193 Vulnerability in SSL 3.0 Security Vulnerabilities Details 78988 – infinite loop logging war… 98723 – memory not released wh… Known Software Issues GENERAC- 0020394432 GENERAC- 007898873 Johnny Hockey Search… + AR + User toggles between hardware, fluid, electrical and software views of the product Relevant details about the software configuration are obtained from the product and the cloud SEN9833 – firmware v7.2.33.2 SEN7430 – firmware v4.54.3.221 ECU3445 – firmware v1.23.54.506 DRV1011 – v0.9.89.322 Software Configuration Warning 002334: Software recall on ECU3445. Update Drill down into a number of connected Apps to get details on specific content Alerts are presented in the context of the system or subsystem
- 33. • Operational data streamed from the product • Data compared with engineering norms in the product cloud • Optional software updates to improve product performance are presented • Learn more about findings • Update software OTA – May require new licensing terms (and hence new revenue opportunities for vendor) • Access to role-based control app(s) to tune and manipulate the product WithAugmented Reality (Feature Entitlement) GENERAC- 0020394432 GENERAC- 007898873 Johnny Hockey Search… + AR + Generator is operating at >65% utilization, a power upgrade is available . Upgr ade More Info Operational Trends Operating analytics displayed in real-time as coming from the product Available upgrades, capabilities or parameter settings to boost efficiencies Remote UI Available Downl oad
- 34. • Remote access Apps generated or created by the manufacturer are presented to the user • May be several relevant for different users or roles (operator, junior service tech, master service tech, OEM) • App SDK enables AR, Mobile or Desktop user interfaces. • Product is connected such that access does not have to be “on site” Software Delivery Enables On-Site or Remote Access Johnny Hockey Search… + AR + V A Hz Voltage Adj. Power Outage Threshold Auto Manual Off GENERAC- 0020394432 Control the product through AR, Mobile or remote desktop applications.
- 35. • Clarification of goals • Why build the smart grid? • What will it accomplish? • How will it evolve over time? • Definition of strategy • IoT systems can have a “code first design later” philosophy • Modeling helps to clarify system strategies • Abstraction of complex systems of systems • Helps to understand the system from multiple viewpoints at multiple levels of abstraction. • Defining and understanding behavior • Through modeling, simulation, trade-off analysis, etc. How does MBSE help?
- 36. System Modeling System Model Must Include Multiple Aspects of a System Start Shift Accelerate Brake Engine Transmission Drive Shafts Control Input Behavioral Requirements Structural Components Performance Requirements Mass Properties ModelEfficiency Model Safety Model Other Engineering Analysis Models Cost Model System Model Vehicle Dynamics Power Equations
- 37. Model Based Systems Development Model Driven Systems & Software Engineering Process System Requirements Engineering Customer requirements, business initiatives / strategy, concept development System Architecture & Design Software Requirements Software Architecture & Design Software Coding Software Unit Tests (Verification) Software Integration & Test Software Validation System Integration & Test System Validation Manufacturing / Service planning, execution; after-market activities Enterprise Analysis Systems Engineering Software Engineering Requirement&ModelRepository
- 39. Operational Level System Level SysML Level – System Level SysML/UML Level – Component Level (for each Component) SysML Level – Subsystem Level (for each Subsystem)
- 41. Questions and Answers DescriptionDescription You :Attendee Me :Speaker loop1 You :Attendee Me :Speaker loop1 while open questions exist Question1.1 end loop while open questions exist Question1.1 Question Answer1.1.1 Question Answer1.1.1 AnswerAnswer end loop {Speech Time}{Speech Time}