1. System of Systems Architecture Project 1 System-of-Systems (SoSA) TPTF Review Line of Sight Jeyant Tamby November 6, 2006

2. System of Systems Architecture Project 2 SoSA – TPTF Review Presented for TPTF review – 29 Sep Comments received by 18 Oct –3 TPTF members sent comments (covered System Operations and Market Information) –1 TPTF member was on site and went thru System Operations –Comments Accounting Spreadsheet will be posted on November 6 –Many comments added by ERCOT as the posters hung in the hall Size –34 Enterprise Use Cases –85 Black Box Operations

3. System of Systems Architecture Project 3 SoSA – Locality Modeling What is it? Locality modeling takes the SoSA models and maps the operations from systems and components to the localities or logical groupings of physical devices used to support them. Possible locality types are: communication intensive (SCADA), computation intensive (RUC), and storage intensive (EDW). Benefits –Allows full impact analysis – from a Protocol change to its impact on ERCOT infrastructure. –Clearly delineates the functionality a logical grouping of physical devices supports. –Allows for easier data center capacity planning when paired with services approach by linking supplemental requirements to both the logical systems/components and the physical devices. Example – SCADA is hosted in a Communication Intensive locality and State Estimation is hosted in a Computation Intensive locality, new hardware is available to support communication intensive systems – Do we need to upgrade our Communication Intensive locality? –Ability to map specific SLAs to the appropriate logical device grouping. –Trace physical device failure to business process impacts. –Design the Disaster Recovery environment. When –Working on the Proof of Concept (draft 10 Nov 06) –Complete the Locality Model once the System and Component level Use Cases are completed by the projects.

4. System of Systems Architecture Project 4 SoSA – Locality Modeling Logical model diagram showing one use case scenario Locality model diagram showing same scenario The same sequence of operations happens as a collaboration of logical entities, as well as “physical” entities. The localities show where the functionality happens. This is useful for analyzing: Non-functional requirements Disaster Recovery Capacity Planning

5. System of Systems Architecture Project 5 SoSA - Domain Model What is it The Domain Model contains model elements representing information/data used by the SoSA model. Domain ModelSoSA Model used in operation parameters information passes to/from the systems IO Entities describe the types of data passed between systems.

6. System of Systems Architecture Project 6 SoSA – Domain Model Sample Mapping of I/O Entities between MP and Nodal The diagram identifies which I/O Entities are passed between the Market Participant and Nodal. This information is used when designing the User Interface and Web Service APIs.

7. System of Systems Architecture Project 7 SoSA - Domain Model Benefits –Keeps consistency across enterprise and systems. A single definition of information used throughout the models. Simplifies information maintenance – updating/modifying terms and attributes. Facilitates identifying impacts of proposed changes. –Defines information usages between actors and systems. –Basis for designing the Market Participant APIs. –Will be used to “publish” a Glossary. When –Initial Enterprise I/O Entity identification – Complete. –Integration of Enterprise I/O Entities into SoSA – November, 10. –Addition of attributes to the Enterprise I/O Entities - November, 28. –Initial System I/O Entity identification – November, 28. –Integration of System I/O Entities into SoSA – Early Q1, 2007. –Addition of attributes to the System I/O Entities - Early Q1, 2007.

8. System of Systems Architecture Project 8 SoSA - End-to-End Usages, Scenarios and Test Cases Purpose –Provide a holistic view of Nodal that runs horizontally across the functional areas Benefits –Ensure successful integration across an entire business process. –Demonstrate full functionality. –Validate training program. –Verify end results of end-to-end usages of Nodal. When –End-to-end usages: first iteration will be completed in Nov 2. 1. 3. 4. 5. 1. Identify end-to-end usages of Nodal with the help of SoSA use cases. 2. Prioritize this list of end-to-end usages of Nodal, based on factors such as risk, frequency, volume, etc.

9. System of Systems Architecture Project 9 SoSA - End-to-End Usages, Scenarios and Test Cases The end-to-end usages will be assembled into a few scenarios The end-to-end scenarios will be developed into Test Cases (?) A preliminary insight into we are going… –Construct scenarios that include a combination of high-priority end-to-end usages of Nodal. –Choose a few of these scenarios to be developed into preliminary end-to-end test cases. –Once the conditions and results of these few are stable, develop more end-to-end test cases that test permutations of these chosen scenarios.