The price of light is less than the cost of darkness. Arthur C. Nielsen

Integration and Data Load Summary

This article discusses the integration and data load step in our hypothetical project to reach compliance with FERC Order 881.  This step can be completed as often as needed within the project to reach a state of “done,” but each project is different, so your experience may differ from our 9-month project plan.  The output for this step will involve passing master approval for implemented data loading and interfacing. 

System Configuration Review:

In the previous article, we discussed the system configuration, which involved providing configuration and implementation for all approved requirements related to the project. While there is a lot of flexibility in this stage, it is crucial to pay attention to details.

Integration and data load

During this phase, you may ask, “Are we there yet?” The answer could be yes, but it is also possible that you have just completed your first work package. Integration and data load can run parallel to the System Configuration stage. If so, the project may still have a few design issues and data clean-up. The main objective is to provide the definition, design, implementation, and approval of all data intelligence related to our FERC 881 requirements. It is time to provide structure for:

• Data Modeling and Data Mapping
• Data Customization, if required
• Data Extraction, Interpretation, and Conversion Rules
• Synchronization logic and data validation
• Scheduling, Trigger Notifications

Data Modeling and Data Mapping

First, the main goal of data modeling is to establish consistent data standards for your entire organization. It is used to turn the abstract into a visual representation. Data models aid in data governance, compliance, and data integrity.

Data Modeling can be broken down into physical, logical, and conceptual steps.  Conceptual data models provide a high-level visualization of business processes and rules. They help align business stakeholders, system architects, and developers on project requirements and information.

A logical data model defines the data elements and relationships in a project. It shows the names and attributes of entities in the database, specifically manufacturers name plate data, including model numbers; in addition, the IPS® asset registry can display any custom properties needed in your organization.

The physical data model specifies how data will be stored, including storage needs, access speed, and redundancy details. It’s a technical design used by database analysts and developers to define data types and requirements.

5 Best Practices for Data Modeling:

1. Clearly define the scope and stakeholders.

2. Standardize your naming conventions

3. Organize data into tables to eliminate redundancies or anomalies.

4. Use Denormalization to optimize query performance.

5. Apply Indexing Strategies to improve data retrieval.

Data Mapping connects data fields from one source to another, reducing errors and preparing your data for data reporting.

Data Customization

Data Customization may be necessary when creating an alias for data items or sorting data output. For example, suppose a piece of equipment or an entire substation was acquired in the past, and the previous equipment owner named an ABC Breaker by a different naming convention than what you use with all your other breakers. In that case, you must create an alias for that breaker to match your naming convention.

Data Extraction, Interpretation, and Conversion

Clear and specific conversion requirements help ensure the data conversion process is accurate and efficient. Interpretation involves evaluating the source data’s quality, completeness, and compatibility.  Careful planning and execution are key for successful data extraction.  The extracted data should be validated to ensure it is complete, relevant, and accurate.

Data arriving from multiple sources can be disordered and perhaps even duplicated. Data extraction and ingestion should always include data clean up. However, this can happen in the source system, in transit (typically the most efficient) or in the destination system. The Data Interpretation’s goal is to standardize all data.  For network model data, IPS® fully supports any CIM compliant data export.

Finally, data conversion rules ensure that converted data meets the quality and accuracy standards, allowing data to be shared across various applications.

Data Questions to ask:

• What migration scripts are available?
• Loading base Network Model
• Defining update processes
• Loading identified MLSE objects

This stage will involve obtaining master approval for implemented data loading and interfacing. It will also provide input for testing and training for the FERC 881 project.

Synchronization logic and data validation

Synchronization logic will establish consistency between the source and target data sources.  Data validation provides the stakeholders with reliable information to make best-case decisions. It is accomplished by taking a sample containing all the required data. The source data is matched with the schema of the destination, and it is then checked for accuracy and completeness.

Scheduling, Trigger Notifications

Decisions on what scheduling and trigger notifications to implement are necessary and should be well-defined by the project.  With the FERC 881 mandates you may require notifying users when the temperature has varied outside the projected targets.  Setting up automatic reminders or just reporting the actual temperatures for an area could be helpful for compliance support.

The key to successful data migration lies in data-mapping.  Once data has been defined and verified it becomes much easier to create data validation scripts and data migration scripts.  Successful data mapping makes the difference between successfully automating data migration or falling back on manual input.

System Configuration Summary

This article concerns FERC 881 compliance and focuses on the system configuration step. The goal is to provide configuration and implementation for all functions related to the requirements upon approval. The system configuration involves identifying facilities and significant objects, configuring rating configurations, element rating sources, and rating calculations. The final output is a system configured and running with representative data to simulate interface data related to a definition of done.

High-Level Architecture Review:

Last week, we discussed high-level architecture and project design. We primarily discussed understanding data sources and data locations to ensure compliance with FERC 881 standards. We also touched on the importance of the network model and how it relates to the project’s overall success.

System Configuration Details

Configuration is essential to ensure compliance with the FERC Order 881, not just the immediate steps of the project creation but over time, even when changes to the order may occur. Secondly, this configuration must be able to accept replacement components as those objects will be replaced or updated for system efficiency. In our compliance project, we have a well-defined plan, allowing us to focus on details.

Meanwhile, as part of our hypothetical nine-month implementation, we have allotted fifty-five work days for this step. Understanding the high-level architecture and the design decisions are interdependent with system configuration and must work together to ensure compliance with the requirements of FERC Order 881. Therefore, it is vital to complete the system configuration step. To this end, we should have several things ready to analyze in further depth.

Configuration and Implementation

The primary goal is to provide configuration and implementation for all functions related to the approved requirements. Each approved requirement may be completed separately using an agile/lean methodology. Furthermore, we can halt or resume the process multiple times to adapt to changing circumstances.

Tasks within the system configuration include: 

• Facilities:
  • Configure facilities
  • Configure significant objects

• Rating Configurations
  • For each facility, configure normal and, when needed, abnormal configurations
  • Configure components and groups for facility ratings report creation
  • Select calculations for the facility ratings report

• Element Rating Sources
  • Identify the primary rating source
  • Define more as needed for each component

• Rating Calculations
  • Configure all variables for each rating type
  • Choose selection criteria for each rating type defined in previous steps

• Provide feedback for Testing Each Work Package
• Provide feedback for Training each Work Package
• Update Implementation and Integration to Testing
• Update Implementation and Integration to Production Systems

Success is in the Details

The success of the entire process lies in paying attention to details. First, tasks within the system configuration should include identifying and configuring facilities and significant objects, such as line and connected stations, and normal and abnormal configurations for each facility, such as bypass, transfer, and outage derates. Additionally, we should select the calculations we want to use for the Facility Ratings Report. IPS^®AFRM, designed for your FERC Order 881 project, enables easy selection of reports on the facility or object. Just Right-click and choose the report option.

In addition, we need to identify the primary rating source and then define more, if required, for each component. Further, the outputs are a system configured/implemented and running with representative data. This simulates interface data related to a definition of done. Also, the definition of done and input for unit, integration, and UAT use cases delivered. Finally, each system configuration gives a bit more of what the result compliance to FERC Order 881 will look like.

Next week, we will focus on Integration and Data load.

Defining and Understanding Review

Last week, we introduced defining and understanding our FERC 881 compliance project.  For review, we looked at:

• Defining the FERC 881 project
• Defining Facilities
• Defining MLSE Elements
• Defining Facility Ratings Calculations.
• High-Level Architecture and Project Design

High-Level Architecture and Project Design can run parallel with our previous step Definition and Understanding. With this hypothetical project with nine months, we are allocating 35 workdays for this step.   This timeline depends on the resources of individual utilities, but running the two processes in parallel can speed up the overall project time. Additionally, this allows the plan’s optimization and alterations throughout the project.

Focusing Goals for Project Success

The main goal of this week’s installment of FERC Order 881 compliance implementation is to analyze all requirements, sources, and logic for all external (to the system) data needed to calculate the facility ratings:

• Analyze high-level system architecture requirements and data sources.
• Where is the network connectivity sourced?
• Where are the base ratings for the components?
• Analyze data and specify all data types per data source.
• Analyze interfacing technology, type, and logic (such as Unidirectional, bidirectional, etc.)
• Specify the number of interface requests per data source and data object.
• Analyze Network Model Sources
• Define which active model contains primary equipment.
• Determine if additional models are available or desired.
• E. is there a system of record for auxiliary equipment such as wave traps and conductors?
• Checking if the model elements are complete with rating information?

During the analysis of the base model, you may discover that certain elements lack rating information. In this case, identifying the source of the missing data takes additional time. In conclusion, success in this step requires correctly identifying and defining all required data specifications and sources.

Network Model

One important source for storing facility component connectivity will be the Network Model.  A Network Model is a central repository and management system and is crucial for a sustainable FRM solution whether you use IPS® Network Model Management to store the connectivity and the ability to generate all needed components of the facility or chose to load the facility from a spreadsheet or list from another solution.  Without the connectivity within the network model, it is exceedingly difficult to support the manual process of assuring that all shared equipment is updated in all facilities.

The IPS® Network Model Management meets all requirements for Network Model Management solutions published by EPRI in the “Network Model Manager Technical Market Requirements – The Transmission Perspective” and upgraded based on findings by the CIM User Group. This CIM-based object structure allows efficient data exchange with all CIM compliant applications, eliminating manual work of verifying and consuming data from other systems.

During the project design, there may be objects identified that do not currently reside in the network model.   If this occurs, the project team must decide the necessity and handling of these objects.

Conclusion: Improved Project Design and High-Level System Architecture

This work can lead to well-defined and improved High-Level System Architecture, defined data sources, and defined data intelligence. All the data sources are defined, and all required interfaces, such as the interfacing technology, direction, number of interfacing requests needed, frequency of those requests, and description of the integration as either single side or end-to-end integration, are defined.  Taking the time to understand the sources, data, and where that data will fit into complying with FERC 881 standards is vital to project completion.

Next week, our focus will be on System Configuration.

Introduction: Defining the Project Requirements

Project requirements definition is a crucial step toward achieving project success. This step comes after establishing a project team, testing environment, and budget. Our next objective is to provide a framework that complies with FERC Order 881. We have allocated 30 days to complete this task for our hypothetical nine-month project. In this phase, we need to keep the following essential considerations in mind:

• Analyses and Understanding Requirements
• Define Facilities
• Define MLSE Elements
• Define the Facility Ratings Calculations

Responding to the FERC 881 Requirements:

Although the default project requirements are derived directly from FERC Order 881, each organization must decide how to respond. For example, a smaller utility with a limited budget may keep these calculations manually using a spreadsheet or an in-house designed database. However, depending on the size of the utility, staffing to manage the required data may be prohibitive. In this case, a solution like IPS^®Advanced Facilities Ratings would help fulfill the requirements of FERC Order 881.

Understanding Weather Requirements of FERC 881:

Some facility ratings, such as base, seasonal, and emergency ratings, are currently calculated by most organizations.  Additionally, some organizations already use dynamic line ratings required by the FERC order. Expanding seasonal ratings and using accurate weather sources are needed for compliance. What are the considerations for applying that weather source to meet the project requirements?

We should consider questions such as:

• Will this be by region or zip code?
• Are there elevation concerns to address, making regions more complicated?
• Is a weather service already in use, such as an in-house system?
• Will additional costs be needed for an outside weather service?

Conclusion: Successful Project Definition and Understanding

Measuring the success of this step in the project for FERC 881 requirements compliance is ongoing and multifaceted. This step takes approximately six weeks to complete for our hypothetical nine-month project. If using a hybrid methodology, this process step can run until the end of the project. We should be finalizing some requirements while starting others. In this step, we still need to be aware of scope creep or, as some may refer to it, requirement creep.  The team’s responsibility will be to stay firmly within the defined project. Still, ultimately, we must have an approved list of requirements, and a High-Level System Architecture framework is a marker for success.

Next week, we will delve deeper into High-Level Architecture and Design. Stay tuned!

There may still be some confusion about FERC 881.  However, full compliance with FERC Order 881 requirements by July 2025 is mandatory. So now is the time to move from inaction to planning and taking action.  Our hypothetical scenario uses a nine-month project timeline with a hybrid methodology. We are using IPS®Advanced Facility Ratings Management Implementation for the FERC Order 881 compliance project.  We have allocated 17 days to complete this step.  Meanwhile, if you are still in the planning stage, check out our articles that address making a plan!

When designing a plan for your organization, assessing other plans and adjusting your goals based on budgets, time, and scope is crucial to making confident and informed decisions.

FERC 881 Project Initiation Where to Start

A significant question at this stage is what is needed to start.  If you are still unsure of what FERC Order 881 is about, check out the Federal Energy Regulatory Commission’s E-Library.

Project Initiation requires project development and a testing environment, a project team, a kick-off date, preparing your system(s), and core team familiarization. Our first team decision is to utilize software to accomplish the requirements of FERC 881.  Then, preparation for the DEV environment for testing new concepts/versions is required.  But first, we must select the team!

FERC 881 Project Initiation Organize the Team

Selecting the Ideal Team

What criteria should be considered for the FERC 881 project team?

An ideal project team will include individuals who work in facility ratings and transmission planning. In addition, other key project team members include operations SMEs and at least one individual who knows where the data is located. Having the right team in place can ensure the project is successful and completed on time.

Questions the team needs to ask might include:

• What is the Timeline
• What is the Budget
• Are there obstacles to project completion
• What are the expected outcomes

Project Methodology 

Next, we must organize the project team and familiarize them with the chosen methodology.  A hybrid methodology usually leads to the quickest completion. Hybrid methodology is preferred because it allows many tasks to run parallel.

FERC 881 Approvals and Plans

You need to document software licensing and services provided if you use a software solution.

It is now time for you to decide on strategies for managing approvals for software delivery for your projects success.  You will also want to develop plans for organizing maintenance and support.  These are crucial steps to comply with the FERC Order 881 requirements.

Project Initiation Duration Variables

Our assumption is our FERC 881 project will take nine months to implement.  However, the project’s duration may vary depending on the number of assets and the availability and condition of data.  One thing to watch out for is scope creep.  For example, this can happen when a team tries to put in items not a part of the initial project.  Consequently, the project controller must keep the project on track and in scope, which may require more than a year for some organizations.

FERC 881 Project Looking Ahead

Next week, we will cover Part Two: Definition and Understanding. By following these guidelines and taking confident and decisive actions, you can ensure that your organization reaches FERC 881 compliance by the deadline.

It is important to note that full compliance with FERC Order 881 requirements by July 2025 is mandatory, and it is time to start your FERC 881 Order project and move from inaction to planning and taking action.  Our hypothetical scenario uses a nine-month project timeline with a hybrid methodology and Solution Implementation. We have allocated 17 days to complete this step.

“Let our advance worrying become advance thinking and planning” -Winston Churchill.

When designing a plan for your organization, assessing other plans and adjusting your goals based on budgets, time, and scope is crucial to making confident and informed decisions.

FERC Order 881 Project Starting Point

A significant question at this stage is what is needed to start.  Project Initiation requires project development and a testing environment, a project team, a kick-off date, preparing your system(s), and core team familiarization. If utilizing software is the choice to accomplish the requirements of FERC 881, preparation for the DEV environment for testing new concepts/versions is required.

Organize the Team

Organize the project team and familiarize them with the chosen project methodology.  A hybrid methodology usually leads to the quickest completion time by allowing many tasks to run parallel.  You need to document software licensing and services provided if you use a software solution. Create plans for managing approvals for software delivery and organizing maintenance and support plans.  These are crucial steps to comply with the FERC Order 881 requirements.

Select the Ideal Team

An ideal project team will include individuals who work in facility ratings and transmission planning. Other key project team members include operations SMEs and at least one individual who knows where the data is located. Having the right team in place can ensure the project is successful and completed on time.

Questions the team needs to ask might include:

• What is the Timeline
• What is the Budget
• Are there obstacles to project completion
• What are the expected outcomes

Duration Variables

Our assumption is our project will take nine months to implement.  However, the project’s duration may vary depending on the number of assets and the availability and condition of data.  Additionally, the project controller must keep the project on track and in scope, which may require more than a year for some organizations.

Looking Ahead for FERC Order 881 compilance

Next week, we will cover Part Two: Definition and Understanding. By following these guidelines and taking confident and decisive actions, you can ensure that your organization reaches FERC Order 881 compliance by the deadline.

FERC Order 881 may seem far in the future, but like looking in the rearview mirror, it is closer than it appears.  FERC Order 881-A, finalized in March 2022, requires hourly AARs 10 days out. AARs must be adjusted anytime the temperature changes by 5 degrees or more, and they must consider solar irradiance.

“Planning is bringing the future into the present so that you can do something about it now” – Alan Lakein.

FERC 881 Deadline

Goals for implementing new processes and procedures for hourly Ambient Adjusted Ratings, managing DLR equipment such as line monitors, sag detectors, and communication devices, deciding which weather applications to use, managing future hours data, and storing data for five years can be time and resource consuming.  There may be an attitude of wait and see because there is some mystery as to exactly how to meet the demands of these sweeping changes.  But with the deadline of July 2025, there needs to be a plan of action to ensure you are ready for FERC 881!

Project Plan

In order to assist with planning a hypothetical FERC 881 project, we will be breaking down the project tasks. Using a hybrid/lean methodology because many tasks can be going on at the same time if resources are present to implement the project in a timely and efficient manner. This timeline of nine months is based on a software implementation with IPS^®Advanced Facility Ratings Management.

However, it is acknowledged that every utility is different, and this is just a guide. The individual timelines and methodologies will change depending on the individual organizations.  As much as possible, there is an attempt to keep the project information general so that these articles can be used on a smaller scale using logical adjustments for individual utilities. Using a skilled project team, these principles can be helpful to utilities of any size. Over the next several weeks, we will look into how to make a plan and the data needed for a successful implementation to meet the demands of FERC Order 881.

Steps we will look at in future articles include:

• Project Initiation
• Definition and Understanding
• High-Level Architecture and Design
• System Configuration
• Integration and Data Load
• Testing
• Training
• Go Live
• Post Go Live Support

Check back next week when we look into Part One: Project Initiation.