Skip to content

Zaeem Ahmad Notebook

Hayden Cook edited this page May 7, 2026 · 1 revision

Fall 2023

August

Week of 8/21

CPS Definition Cyber-Physical System (CPS): A CPS is defined as a physical system, often referred to as "the plant," which is controlled by a single or a set of networked computers. CPS involves the following key elements:

Physical System State Observation: CPS systems monitor the state of the physical system through various sensors. These sensors provide real-time data on variables such as temperature, pressure, voltage, and more.

Physical System State Modification: CPS systems can modify the state of the physical system using actuators. These actuators can control various aspects of the system, such as opening or closing valves, adjusting equipment settings, etc.

Control System: The control system in CPS comprises computers, sensors, and actuators. It orchestrates the interaction between the digital control layer and the physical system, making decisions and executing actions based on sensor inputs.

Team Organization: Divided into Subteams of Two for Device Modeling, ROS-Helics Integration, and Physics Modeling.

Week of 8/28

GitHub Formatting

I began by researching GitHub's basic formatting syntax and applied it to create this notebook for tracking my project's progress and troubleshooting.

September

Week of 9/4

  • During our subteam meeting this week, we commenced our preparations for the upcoming Kickoff presentation. To ensure a well-structured and informative presentation, we allocated specific slides to each team member.

  • I focused on creating the solution slide for our Kickoff presentation. This is a crucial step in effectively communicating our project's goals and value proposition to our audience, setting the stage for a successful presentation.

    1. Leveraging IEC 61850
    2. Ensuring Correctness and Security
    3. Creating Simulation Scenarios
    4. Analyzing Device Responses
    5. Enhancing Substation Communication and Security
    6. Combining Approaches for Robust Models
    7. Utilizing MITRE ATT&CK® Matrix for ICS
    8. ISO/IEC 27001 Compliance

Week of 9/11

Research on Substation Functions Modeling

This week, I delved into researching the modeling of substation functions, a critical aspect of our project. Here are the key findings and progress made during the first week of research:

Understanding Substation Functions: I explored the functions and components commonly found in electrical substations, aligning our approach with industry standards like IEC 61850. Conducted a literature review to identify modeling techniques and best practices, revealing research challenges in the field.

Data Collection: I began collecting data on substation equipment and specifications to support accurate device modeling.

Week of 9/18

I focused on co-simulation using HELICS:

Introduction to HELICS: I began by acquiring a foundational understanding of HELICS, particularly its capabilities in facilitating co-simulation for cyber-physical systems (CPS).

HELICS Documentation Review: A substantial portion of my week was dedicated to reviewing HELICS documentation and user guides. This allowed me to grasp the software's features, installation process, and its potential role in our project.

Environment Setup: I worked on setting up the HELICS environment on my development machine. This involved installing the necessary dependencies and configuring HELICS for our specific needs.

Week of 9/25

In our meeting this week, we began working on our IPR 1 Presentation for the Device Modeling Team. We divided the presentation slides among the team members, and my specific responsibilities included creating the Project Roadmap and Team Responsibilities slide.

Week of 10/2

Successfully finished setting up the nix develop environments along with building HELICS and Gridlab-D

Week of 10/9

Started working on the paper draft

I worked on 3.2 Integration of HELICS and GridLAB-D, 5.2 (Require input from the Co-simulation subteam regarding ideas and approaches for the framework and integration).

Integration of HELICS and GridLAB-D HELICS Features:

  • Support for large-scale co-simulation.
  • Synchronizes different time scales.
  • Components: Broker, Core, Federates, Executables.

GridLAB-D Features:

  • Detailed representation of power distribution networks.
  • Focuses on distributed energy resources like renewables, storage systems, demand response devices.

Benefits:

  • Accurate analysis and control of substation operations.
  • Comprehensive understanding of grid infrastructure interactions.
  • Enhances planning, operation, and management of modern power systems.

Week of 10/16

Finished working on the paper

HELICS and GridLAB-D Co-Simulation: Challenges and Collaboration

Key Focus Areas:

  • Time scale synchronization.
  • Efficient data exchange.
  • Smooth interaction between HELICS and GridLAB-D.

Technical Aspects:

  • Managing communication interfaces.
  • Synchronization mechanisms.
  • Enhancements for robust, scalable, and versatile substation modeling.

GridLAB-D and OOP:

  • Precise smart grid modeling.
  • Integration into HELICS as federates using MODBUS protocols.

Challenges:

  • Synchronizing federates.
  • Accurate modeling of substation parameters.
  • Defining subscriptions and publications within the co-simulation environment.

11/1 - 11/30

Agreed to meet before thanksgiving break to satrt planning out what we needed to do for the simulation. Missed the meeting because i had to leave early for the thanksgiving break but got updates through discords

We started working on some of the process level python files like the relay_house, UI for powerflow, and the helics-config file.

12/1 - 12/15

Focused on preparing the final presentation and completing the final research paper for the project.

Fall 2024

August

Week of 8/26. Team Reintroduction and Progress Overview

I had an introduction session where I met new teammates and got reacquainted with the team after skipping the spring semester. I spent time learning about the progress made so far, understanding the key developments and changes that occurred during the semester I missed. It was a good opportunity to catch up, get back into the workflow, and adapt to the team's current direction.

Week of 9/2

Nothing much just prepped on the presentation

Week of 9/9

worked on setting up Nix in class

I was having Issues with nix, another permission error and worked on fixing it with albert and, reinstalled it using the

https://nix.dev/manual/nix/2.18/installation/uninstall

Week of 9/16

Finished setting up Nix. Spent most of the time doing research readings and catching up on tasks.

https://docs.google.com/document/d/1SetasjCpVjC5Hmb5hCy3NKJc6rthLcOuz_2VJcRoEoE/edit

https://ieeexplore.ieee.org/document/8765874

A digital substation replaces analog systems with digitized data over Ethernet networks using the IEC 61850 standard. Effective network design with VLANs, QoS, and redundancy protocols (RSTP, PRP, HSR) ensures reliable, efficient operations. Factory Acceptance Testing (FAT) helps identify issues early and reduces commissioning time.

Week of 9/23

Class was switched to virtual. We reviewed research findings and questions during the session, and discussed subteam tasks.

Week of 10/01

Worked on the research paper draft

Research paper draft Project Focus: Substation Device Modeling and Co-Simulation

Tasks:

  • Worked on updating the device modeling section of the research paper.
  • Focused on Python class improvements for substation devices such as transformers, circuit breakers, and bay controllers.
  • Reviewed the accuracy of the current simulations of device behaviors and discussed potential class structure improvements.
  • Engaged in discussions about future implementations and enhancements to expand the range of devices modeled in the simulation.

Week of 10/07

I mostly worked on the midterm presentation and met with my teammates on Sunday and Wednesday night to finalize the presentation, as well as the device modeling goals and tasks. We also discussed what we plan to achieve by the end of the semester.

Week of 10/14

divided tasks from these

  • Task 1 - GLM Object Implementation
  • Task 2 - DNP3 server commands
  • Task 3: Fault Tolerance and Recovery
  • Task 4: Powerflow-ML

currently working on task 1 and 2 almost done with research and learning will start trying to implement within the next few weeks.

Week of 10/21

No one from device modeling attended the Sunday meeting, so there were no updates from that end. I primarily focused on research related to GLM implementation and had discussions about the research findings. I didn't accomplish much this past week as I currently have a lot of midterms.

10/28 - 11/11

Mostly worked on Task 1 and 2 completed most of the research and started working on the implementation phase. Had 3 midterms during this time so didn't get much done.

11/18

Started working on the final presentation slides meet on sunday to divide up work and spend the week finishing up the slides.

11/23 - 12/04

Started working on the final research paper due on Dec 4th

Spring 2025

January

Week of 01/20

Caught up on last semesters work with teammates and started working on the Kickoff presentation.

Week of 01/27

Finished the presentation and wasn't able to catch up on a lot of stuff this week since i had a lot class work and interviews this week.

February

Week of 02/03

Discussed and divided tasks in meeting and continued on research.

Week of 02/10

Met in a virtual meeting and discussed finishing up the midterm paper submitted on Wednesday. We divided up the tasks for the midterm paper but couldn't make much progress this week due to a heavy workload of exams and project deadlines. Additionally, we started working on the midterm presentation and split up the slides among team members.

Week of 02/17

Met in a virtual meeting and discussed finishing up the midterm paper submitted on Wednesday. We also started working on the midterm presentation and split up the slides for each team member.

Week of 02/24

We primarily worked on the midterm presentation, completed it, and delivered it on Thursday.

Week of 2/24 – 3/1

This week was a bit slow for me due to a busy schedule with other classes and project deadlines. While I didn’t make any direct progress on the codebase, I stayed engaged during our team meeting and made sure to review what the rest of the device team had been working on. I also touched base to understand where the API integration work stood, and started planning how I could assist once my schedule cleared up.

Week of 3/2 – 3/8

Due to midterms, I wasn’t able to work hands-on with the project. However, I helped organize shared documentation and attended meetings to provide feedback on ongoing transformer research. I also revisited DNP3 documentation to better understand how we’ll structure device inputs and outputs.

Week of 3/9 – 3/15 (Spring Break)

Over spring break, we didn’t have any team meetings, but I did take a bit of time to look over the DNP3 database structures and revisited the documentation that Kaden had shared earlier. I also synced with the device team group chat to check in on our pacing for the semester. Planning to be more active once classes resume.

Week of 3/16 – 3/22

This week I reviewed transformer concepts, particularly current transformers and multi-ratio CTs. I contributed to discussions around device behavior and helped clarify how we differentiate between CTs and VTs in our modeling. I also provided input on documentation cleanup.

Week of 3/23 – 3/29

We worked on preparing our midterm presentation this week. I helped refine the content for the slides, specifically around the device section, and supported the visual layout for clarity. I also gave feedback during practice runs to help with presentation flow and technical clarity.

Week of 3/30 – 4/5

I worked with the team on refining the API diagram and verifying device-to-network data interactions. I also assisted in reviewing transformer-related definitions to ensure our final documentation and diagrams were accurate.

Week of 4/6 – 4/12

Our focus this week was on the final presentation. I helped prepare slides related to the device sub-team’s progress and reviewed technical content to make sure it aligned with what we built over the semester. I contributed to the visual design and layout, and helped with dry runs to finalize the flow. Started researching for the final paper.

Week of 4/13 – 4/19

This week, I contributed to the research paper as part of the Device Modeling team. My work focused on refining and writing content that explains the role of substation devices in our co-simulation framework. I helped draft and structure sections covering the classification of transformers, the function of sensor devices, and the broader goals of integrating monitoring and communication protocols. I also assisted in summarizing relevant case studies, including the 2003 Northeast Blackout, to highlight the importance of real-time fault detection and system resilience. This contribution was aimed at improving the clarity and cohesion of our section and ensuring it aligns with the overall objectives of the project.

Active Notebooks
Archive
Tutorials

Clone this wiki locally