T-Nexus AEPs new Network Model Management Solution Eric Hatter, - - PowerPoint PPT Presentation

▶
t nexus aep s new network model
SMART_READER_LITE
LIVE PREVIEW

T-Nexus AEPs new Network Model Management Solution Eric Hatter, - - PowerPoint PPT Presentation

Nov 05, 2023 647 likes •944 views

T-Nexus AEPs new Network Model Management Solution Eric Hatter, Program Manager, AEP Margaret Goodrich, Project Consultants, LLC Integration Lead Ljubljana, Slovenia June 5-7, 2018 Network Model Management Improvement at AEP AEPs

slide-1
SLIDE 1

T-Nexus – AEP’s new Network Model Management Solution

Eric Hatter, Program Manager, AEP Margaret Goodrich, Project Consultants, LLC Integration Lead Ljubljana, Slovenia June 5-7, 2018

slide-2
SLIDE 2

Network Model Management Improvement at AEP

AEP’s Network Model Management Improvement Program (NMMI) ▪ Who is AEP? ▪ Why do it?

  • and Benefits

▪ How did it happen?

  • History and Success Factors

▪ What is AEP doing?

  • Technical Foundation
  • Phase II Implementation Strategy
slide-3
SLIDE 3

American Electric Power (AEP) as a Utility

▪ Headquartered in Columbus, Ohio ▪ Serves customers in 11 U.S. states ▪ Maintains the largest transmission network in the U.S. with over 40, 000 miles of transmission ▪ Member of three RTOs: PJM, SPP, and ERCOT ▪ Combined PJM, SPP & ERCOT state estimator cases exceed 14,000 substations and 22,000 buses.

Who? Large, Transmission-Focused, Multiple Footprints

slide-4
SLIDE 4

4P

AEP T-Nexus

Purpose

▪ Revise network model management in the AEP Operations, Planning, Protection and Asset Management domains with the intent of gaining qualitative benefits across all AEP Transmission footprints

Goals

▪ Unify modeling processes across the AEP Transmission footprints ▪ Reduce manual effort of mapping between applications ▪ Improve data governance ▪ Implement clear information flow throughout AEP Transmission

  • rganization

▪ Enable data analytics

slide-5
SLIDE 5

5P

AEP T-Nexus Program Benefits

▪ Improved efficiency and reduction in operating cost

  • Eliminate existing duplicate processes
  • Facilitate automation
  • Decrease labor

▪ Improved overall accuracy of network models ▪ Reduced likelihood of serious operating / planning errors stemming from bad models ▪ Reduced time required to perform or update studies

  • Support for post-event analysis
  • Tracking of model changes with ability to recreate cases after

changes ▪ Forward-looking solution positions AEP to effectively deal with future process or application changes (both internal and external)

Why? Efficiency, Accuracy, Future Flexibility

slide-6
SLIDE 6

AEP T-Nexus Program History

▪ 2013 Integrated Network Model Management EPRI project

  • Scope: Operations (EMS and Outage Scheduling)
slide-7
SLIDE 7

AEP T-Nexus Program History

▪ 2013 Integrated Network Model Management EPRI project

  • Scope: Operations (EMS and Outage Scheduling)
  • Existing information flows
  • Network Model Manager (NMM) vision
slide-8
SLIDE 8

AEP T-Nexus Program History

▪ 2013 Integrated Network Model Management EPRI project

  • Scope: Operations (EMS and Outage Scheduling)
  • Existing information flows
  • Network Model Manager (NMM) vision

▪ 2014 NMM Tool Functional Requirements EPRI project

  • Industry vision for Transmission NMM architecture and tool
  • 8 utilities, 2 vendors

▪ 2015 AEP T-Nexus program launch

  • Multi-year, multi-million dollar integration/procurement project
  • Scope: Operations, Planning, Protection
slide-9
SLIDE 9

AEP T-Nexus Program History

▪ 2013 Integrated Network Model Management project

  • Scope: Operations (EMS and Outage Scheduling)
  • Existing information flows
  • Network Model Manager (NMM) vision
  • EPRI “Guide to Exploring Centralized Network Model

Management” (freely available at www.epri.com PID 3002000609)

▪ 2014 NMM Tool Functional Requirements project

  • Industry vision for Transmission NMM architecture and tool
  • 8 utilities, 2 vendors
  • EPRI “Network Model Manager Technical Market Requirements”

(freely available at www.epri.com PID 3002003053)

▪ 2015 AEP T-Nexus program launch

  • Multi-year, multi-million dollar integration/procurement project
  • Scope: Operations, Planning, Protection
slide-10
SLIDE 10

AEP T-Nexus Program History

2016 T-Nexus Program progress

▪ Initiated Program

  • Charter, stakeholder identification, groups & roles definitions
  • Executive approval
  • Consultants selected/engaged

▪ Completed exploration/documentation of AEP current state ▪ Articulated high-level design via Business Scenarios

AEP Network Analysis Actors AEP Data Source Actors Ext Network Analysis Actors Network Model Management Model Part Repository

Business Scenarios for configuring network analysis. Business Scenarios for creating AEP network data.

· Model Parts · Projects · Framework

NMM Workspace

· Navigation · Editing · Case Assembly

New Construction Projects Scenario Group EMS Scenario Group Transmission Planning Scenario Group

RTO Modeler EMS Modeler Planning Modeler Station Eng’g Line Eng’g Network Analyst

slide-11
SLIDE 11

AEP T-Nexus Program History

2016 T-Nexus Program progress

▪ Initiated Program

  • Charter, stakeholder identification, groups & roles definitions
  • Executive approval
  • Consultants selected/engaged

▪ Completed exploration/documentation of AEP current state ▪ Articulated high-level design via Business Scenarios ▪ Identified requirements (especially for Network Model Manager tool) ▪ Held technical training (Common Information Model & integration) ▪ Completed product/vendor selection process

  • Initial demonstrations-Complete
  • Request for Proposal - Complete
  • Vendor trials - Complete
slide-12
SLIDE 12

AEP T-Nexus Program Success Factors

▪ An ‘improvement’ mindset

  • Goal was not ‘replacement’ or ‘new system’

▪ A effective champion ▪ Persistence

  • Continuous attention over multiple years

▪ Business alignment

  • Transmission is AEP’s business focus
  • Encouraged interest at all levels

▪ Engaging integration resources ‘early and often’

  • Integration expertise, knowledge of similar initiatives
  • Engagement with CIM standards community

▪ Fortuitous timing

  • Benefitted from other projects (ERCOT, ENTSO-E)
  • Benefitted from NMM Technical Market Requirements work
  • CIM readiness to support inside-the-utility data management

How? Inspired Vision, Business Alignment, Humility, Luck

slide-13
SLIDE 13

Network Model Management Improvement at AEP

AEP’s T-Nexus Program ▪ Who is AEP?

Large, Transmission-Focused, Multiple Footprints

▪ Why do it?

Efficiency, Accuracy, Future Flexibility

▪ How did it happen?

Inspired Vision, Business Alignment, Humility, Luck

▪ What is AEP doing?

  • Technical Foundation
  • Phase II Implementation Strategy
slide-14
SLIDE 14

14

T-Nexus Functionality Overview- What we have today

Architecture Layout – Siloes of Duplicated Information

slide-15
SLIDE 15

15

T-Nexus Functionality Overview – Where We Are Going

slide-16
SLIDE 16

16P

Key Technical Drivers

▪ All engineering studies and operation centers derive models from the same core data building blocks. ▪ Any given grid element (like a transformer) will be represented in the same way in every study in which it is present. ▪ Consistent practices across AEP units in ERCOT, SPP, PJM. ▪ Different sets of data come from different sources.

▪ Each datum should have one authoritative source. ▪ Automated feed from engineering sources, including automated derivation of analytical models from detailed design.

▪ Repeatable build processes that minimize manual steps.

slide-17
SLIDE 17

Network Model Management Improvement at AEP

AEP’s T-Nexus Program ▪ Who is AEP?

  • Large, Transmission-Focused, Multiple Footprints

▪ Why do it?

  • Efficiency, Accuracy, Future Flexibility

▪ How did it happen?

  • Inspired Vision, Business Alignment, Humility, Luck

▪ What is AEP doing?

  • Technical Foundation
  • Phase II Implementation Strategy
slide-18
SLIDE 18

AEP T-Nexus Program Phases and Deployments

Vendor/Product selection – Phase I

▪ Vendor Trials between 2 best products ▪ Contract negotiation ▪ Product deployment ▪ This was completed in January, 2017

Incremental Integrations – Phase II

▪ First Deployment – by January 2019

  • PSSE/MOD Integration (planning)
  • EMS and Planning Model Alignment
  • TGIS Population/Integration (transmission line engineering detail)
  • TOA/DOL Population Integration (outage scheduling)

▪ Second Deployment – By July 2019

  • EMS Integration (operations)
  • IPS Population/Integration (substation engineering detail)

▪ Third Deployment – By December 2019

  • Aspen Integration (protection)

▪ SCADA & ICCP Deployments – Phase III - 2020

slide-19
SLIDE 19

19

T-Nexus Functionality Overview- Future Data/Project Flows

Projects are vetted extensively before they are applied to as-built

slide-20
SLIDE 20

20

T-Nexus Functionality Overview- Model Building

▪ A projection of all changes that are scheduled to occur on or before a given date/time on top

  • f a base model.

▪ Slide Courtesy of John Moseley of ERCOT

Base Model Jul 20, 2017 1:00 pm Jul 20, 2017 2:00 pm Sep 1, 2017 8:00 am Sep 1, 2017 9:00 am Sep 1, 2017 10:00 am Sep 30, 2017 9:00 am Nov 8, 2017 8:00 am

As-built versions are kept as history Applied projects define ‘deltas’ between as-built versions

slide-21
SLIDE 21

The Flow of Data

21

slide-22
SLIDE 22

The Flow of Changes

22

slide-23
SLIDE 23

Data Viewing

23

slide-24
SLIDE 24

Programmatically Generate and Manually Adjust Single Line Diagrams

24

  • Examples of Rendered one lines from the

connectivity stored in the model

  • Content of one lines are driven by the

stored Model

  • Layout can be adjusted to suit the needs
  • f the users
slide-25
SLIDE 25

Ability to collapse topology to Bus Branch

25

Support for collapsing all switching devices to export bus-branch model for planning studies

slide-26
SLIDE 26

Profile Controlled Export

26

  • Screen to export CIM

XML files by profiles in CIMv16 (Equipment, Dynamics, etc.)

  • Each Profile contained in

a separate file

  • Exported files are zipped
slide-27
SLIDE 27

27

T-Nexus Functionality Overview- Testing Approach 5 Levels of Testing prior to Model/Case Release

Level 1

  • Ran by User prior to “submission”
  • Range Checks
  • Association Checks
  • Completeness Checks (may include Power Flow)

Level 2

  • Model Coordinator Visual checks
  • Additional Programmatic Sanity Checks

Level 3

  • Engineer Review
  • Assessment for Power Flow using the single project against the current

As-Built

Level 4

  • Power Flow test with the project incorporated with all other projects for a

specified timeframe

Level 5

  • EMS Testing in the EMS Staging Environment (includes attachment of

external model and EMS Vendor validation processes)

slide-28
SLIDE 28

28P

Please contact: Eric Hatter: edhatter@aep.com Margaret Goodrich: margaret@j-mgoodrich.com