RATC Architecture Effort

1. RATC Architecture Effort Presented by TomoPopovic Sep 21, 2012

2. RATC Architecture Outline • Progress Overview • Architectural Perspectives • Data Flow Diagrams • Ongoing Activities

3. RATC Progress Overview • Review of SOW documentation • Survey on architecture-significant requirements • Several group and individual meetings with RATC team members • Focus on overall RATC solution architecture: • Logical and functional perspectives first • Top down approach to data flow

4. RATC Solution Architecture

5. RATC Architecture Outline • Progress Overview • Architectural Perspectives • Data Flow Diagrams • Ongoing Activities

6. Architectural Perspectives

7. Context View

8. Functional View: Use Cases

9. Process View: Cascading Event

10. Process View: Generic

11. Logical View: Components

12. Principles • Louse Coupling - each component should be designed/implemented as independent as possible • Data Format Unification - components should utilize uniform and standardized formats and data structures • Minimize Dependency - each component should be designed with minimal dependency on other RATC components or third party software

13. Data View • Input Data • Static model data (branch, generator, load) • Dynamic model data (ATP) • Generator availability • Topology (connectivity) • Load flow (Scada, RTU, PMU) • Event records (DFR, DPR, CBM) • Solution-wide Data • All of the above in standardized/unified formats • Line availability • Component Specific Data • Output Data • Lines to be switched (sequence + generation pattern) • Switching overvoltage levels • Relay settings (Zone 2 and Zone 3) • Fault location reports • CB maintenance reports

14. RATC Architecture Outline • Progress Overview • Architectural Perspectives • Data Flow Diagrams • Ongoing Activities

15. Data Flow Diagrams (DFDs)

16. DFD: Top Layer DFD Nomenclature:

17. DFD: Optimization Algorithm

18. DFD: Switching Overvoltage Check

19. DFD: Switching Stability Check

20. DFD: Cascading Event Detection

21. DFD: CB Operation Evaluation

22. DFD: Relay Settings Adjustment

23. DFD: Data Integration

24. RATC Architecture Outline • Progress Overview • Architectural Perspectives • Data Flow Diagrams • Ongoing Activities

25. Ongoing Activities

26. Ongoing Activity • Support the requirements effort for all RATC optimization and analytics modules (TAMU, ASU, UCB, LLNL) • “Drill down” into the data flow and infrastructure requirements by combining top-down results with the input from TVA, ACS, and GPA • Solution-wide data format unification, updating the simulation environment • Requirements effort and data flow details will keep producing input for the overall architecture

27. Questions Comments?

28. Appendix: Support Slides • Constraints • Design View slides

29. Constraints • Technology • Platforms (Linux, Windows) • Programming languages (Python/Pyomo, Java, C#/C++, Matlab) • Relevant Standards • IEEE C37.111-1999 (Comtrade) • IEEE C37.232-2007/2011 (File naming) • IEEE C37.239-2010 (Comfede) • IEEE 1159.3-2003 (PQDIF) • IEEE 1815-2010 (DNP3) • C37.118-2005/2011 (Synchrophasor Measurements) • IEC 61850 (Substation Automation) • IEC 61970 (CIM/Energy Management) • IEEE C37.238-2011 (Time protocol) • IEEE Common Data Format • XML, ASCII

30. Design View: Optimization

31. Design View: Overvoltage Check

32. Design View: Stability Check

33. Design View: Cascade Detection

34. Design View: Relay Settings

35. Design View: CB Evaluation

36. Design View: Data Layer