Weekly Blogs

Design for Demise: Fall Wrap-Up

This semester marked a major learning phase for our IPPD team as we began developing our re-entry “Design for Demise” solution for Honeywell Aerospace. Our primary objective was to build a strong foundation in ANSYS Fluent, understand the aerodynamic behavior of re-entry conditions, and prepare for the more advanced simulations we will run next term.

We spent much of the semester learning the fundamentals of ANSYS Fluent—how to create and refine meshes, assign boundary conditions, choose appropriate turbulence models, set up solvers, and interpret results. Because real re-entry conditions are extremely difficult to reproduce in the real world, having a reliable CFD workflow is essential to our project. Over time, we became more confident in our ability to set up simulations correctly, troubleshoot issues, and understand why the flow behaved the way it did.

One of the most important milestones was completing a flow-over-a-cylinder proof-of-concept simulation. The cylinder is a classic test case in fluid dynamics, and running it allowed us to validate that our methods were correct. We observed the expected stagnation point on the front of the cylinder and identified alternating vortices known as a Von Kármán vortex street forming downstream. Understanding this phenomenon required us to revisit concepts from fluid mechanics and study how vortex shedding works and why it appears at certain flow regimes. This project strengthened not only our technical skills but also our ability to interpret and explain physical results.

Another major achievement this semester was developing a Kriging surrogate model to optimize our design parameters before running full CFD simulations. Since high-fidelity simulations are computationally expensive, we needed a systematic way to determine which configurations were worth testing. To do this, we first identified the key geometric and physical variables of our design. We then used a structured set of sample points to train the Kriging model, which created a predictive map of how different parameter combinations influence performance. This model helped us narrow down the design space and select the most promising configurations for next semester’s simulations. Building the model taught us how surrogate modeling can guide engineering decisions and allowed us to work more efficiently with the resources we have.

 

We also prepared and delivered our System Level Design Review. For the SLDR report, we wrote detailed sections explaining how ANSYS works, what simulations we ran, how the simulation process functions, and why this software is crucial for our mission. Presenting this information pushed us to think carefully about clarity and communication. Many of us realized the challenge of presenting technical information smoothly, and the experience gave us insight into how we can improve our presentation skills going forward.

Throughout the semester, we grew significantly as a team. We learned how to divide tasks, explain complex ideas to one another, question results, and support each other as we worked through the learning curve of CFD, optimization, and re-entry physics. Even the challenges—such as understanding unexpected flow features or refining mesh strategies—played an important role in helping us become better engineers.

Next semester, our focus shifts toward simulations that are much more relevant to re-entry. We will begin modeling hypersonic flow conditions involving extreme Mach numbers, shock structures, and high thermal loads. Our simple test geometry will evolve into analyses of our actual design concepts, giving us insight into how they behave during re-entry and how we can improve their demisability. The Kriging model will continue to guide which configurations we test, allowing us to combine optimization and CFD to converge on a final design.

This semester laid the groundwork. We built the tools, established the workflow, validated our simulation process, and strengthened our ability to collaborate. Next semester, we take everything we’ve learned and apply it to the real engineering challenge of creating a design that safely and effectively breaks apart during re-entry. We’re proud of the progress we’ve made and excited for what’s ahead.

SLDR Peer Review Presentation

This week in IPPD was all about preparing for our upcoming System Level Design Review (SLDR). Although we didn’t make major technical changes, we made important progress in refining how we communicate our project and ensuring we’re ready for the formal SLDR on December 2.

We started the week with our final liaison meeting of the semester. Michael updated our Honeywell liaisons on the SLDR schedule and reminded everyone that this was our last status memo. Since most of our time has been dedicated to presentation preparation, we kept updates brief. Joseph shared stories about a past Honeywell competition—including a Rube Goldberg machine that won in 2018—and Loi presented his latest ANSYS Fluent work modeling flow over a cylinder and the Von Kármán vortex street. We wrapped up with a practice run of our SLDR presentation over Teams.

On November 18, we delivered our SLDR peer review presentation. Zach opened with an overview of our project, the Kessler syndrome, and recent real-world spacecraft debris incidents. The feedback we received was helpful: reviewers encouraged us to clarify the cost function, refine the parameters we use to measure demisability, and simplify technical sections like Kriging and ANSYS. Dr. Lind emphasized “telling a story” with our presentation rather than overwhelming the audience with details.

Overall, the peer review was a valuable checkpoint. Seeing other teams’ progress and receiving outside feedback helped us better tailor our message for a broader audience. While we’ll take a short break for Thanksgiving, our team plans to meet on November 30 to finalize the SLDR presentation and paper.

We’re looking forward to the formal SLDR and the chance to present our work to Honeywell and industry professionals next week.

One of Loi’s ANSYS Fluent simulations (flow over a cylinder). The blue/green swirl behind the circle demonstrates the Von Kármán effect.

SLDR Preparations

This week our team has been preparing for one of the most important milestones in our project, the System Level Design Review (SLDR). This phase marks our transition from conceptual validation to detailed system refinement, where we must demonstrate a strong understanding of both our design and simulation results.

A major focus this week has been improving our ANSYS model. We’ve spent hours running simulations, adjusting parameters, and validating assumptions to ensure that our data accurately reflects our design’s behavior. Through this process, we identified key simplifications to make our simulations more manageable, such as maintaining a constant velocity and density throughout the analysis. These assumptions help us balance realism with computational efficiency.

Learning Ansys has been a challenge in itself: the software is powerful but complex. Interpreting the data that comes out of our simulations has required careful study and collaboration. Despite the steep learning curve, we’re gradually becoming more confident with the tool, thanks to continuous testing, peer discussions, and countless tutorial videos.

As we prepare for the SLDR, we’re proud of the progress we’ve made in understanding computational fluid dynamics (CFD) and how it applies to our prototype. Each week, our simulations become more refined, our data more reliable, and our teamwork stronger.

Next week, we’ll continue improving our Ansys models and finalizing our report so that we can confidently present our findings to reviewers. The learning process hasn’t been easy, but it’s been deeply rewarding, and we’re excited to showcase how far our team has come.

Prototype Inspection Day

This week marked an exciting milestone for our IPPD team as we participated in Prototype Inspection Day (PID) at the University of Florida. During this event, we presented our project to a panel of IPPD alumni, technical professors, and academic professionals, sharing our progress and receiving valuable feedback to guide our next steps.

Our 20-minute presentation focused on outlining our project’s purpose, technical development, and future plans. We received two main categories of feedback: the first centered on presentation delivery, including our professionalism, clarity, and how effectively we communicated complex ideas. The second set of feedback involved technical insights, such as potential improvements to our design and simulation methods. Both types of feedback were incredibly helpful and will directly influence how we refine our project going forward.

In preparation for PID, our team put in extensive hours of effort, especially in running and finalizing our first Ansys Fluent simulation. This process took nearly 15 hours from setup to completion. Most of that time was spent learning the software’s various features, setting appropriate parameters, and understanding the computational fluid dynamics behind our system. Running this simulation marked a key step toward validating our design under re-entry conditions.

During our weekly meeting, we also discussed the assumptions and simplifications we will use in future simulation runs. Because our project involves complex re-entry dynamics, finding the right balance between realistic modeling and manageable scope has been a constant challenge. Our goal is to keep simulations as close as possible to real conditions while ensuring they remain achievable within our time and resource limits.

Overall, PID was both rewarding and challenging. Condensing months of research, design, and testing into a 20-minute presentation was no easy task, especially given how intricate our system is. Some audience members found it difficult to grasp all the technical details, which reminded us of the importance of clear communication and strong visuals when explaining complex engineering concepts.

As we move forward, we’re taking these lessons to heart. Our team plans to focus on improving how we present technical content, refining our simulation accuracy, and ensuring our design continues to evolve in line with both academic rigor and industry relevance. Prototype Inspection Day was a defining moment and a chance to see how far we’ve come as well as how much potential lies ahead.

Tagged as: ,

PID Prep

Hey crew! 

We’re rounding out Week 10 with some heavy‑lifting in prep for the prototype inspection day. This week’s highlights: 

The Krging that makes the world spin

Dr. Lind presented a short lecture on surrogate based modeling, called kriging. This will be utilized to make a design space with our variables. We still have a lot to learn regarding this process and are excited to pursue this subject further!

We also have begun brainstorming potential cost functions and editing the Kriging code to account for all of our variable changes in both the inputs and the outputs. This will all be done to further our prototype for PID this upcoming Tuesday!

The image above shows the cost functions we are starting to develop; they quantify how effective our design is at achieving controlled demise during reentry by combining key physical and performance variables into a single metric, J, that can be minimized. Each term represents a tradeoff among competing objectives: lower mass reduces orbital debris risk, higher heat flow promotes structural failure, and the ratio of the center of pressure to the center of mass (COP/COM) influences aerodynamic stability. Additional factors such as price per kilogram, vibration level, and natural frequency capture manufacturability and mechanical resilience.

The nonlinear exponents and constants in the equations weight these parameters based on their importance to design requirements, allowing the Kriging model to predict how changes in geometry or material affect demisability. In short, minimizing J identifies configurations that are lightweight, thermally responsive, and physically tuned to fail safely upon atmospheric reentry, meeting the core goal of the Design for Demise project.

Fresh Air – The Great Outdoors Session 

The weather turned out fantastic, so we moved the Thursday meeting outside. Fresh air lifted the mood and sparked a few creative ideas with how we will present our prototype on PID on Tuesday!

Visually 

Updated CAD files now are able to be 3D printed and run through ANSYS Fluent. A preliminary ANSYS Fluent model has been conducted to familiarize ourselves with the tool and prepare for more complex modeling.

Thanks for the great collaboration, and let’s keep the momentum going in next week for SLDR Prep! 

Tagged as:

Prototyping

This week we spent a lot of time discussing what our prototype presentation was going to look like. Because our project is much more research and development than the other projects, we needed to find a way to present our work in the midst of other teams.

We decided to present our project as a design platform that can determine the demisability of different component housing designs. To do this we finalized our CAD model down to the last detail and decided what parameters to test in Ansys.

We aim to get at least one baseline Kriging model done before PID to show how this design platform can show demisability of different designs using machine learning and learn how this type of modeling work.

Over the past week our electrical system has changed, we finally got a quote for how much the frangibolt (release mechanism for the flaps) costs and it was way over our budget, so we changed the scope of our electronic system to use servo motors rather then the frangibolts as a way to release the flaps. We also have started ordering some of our electronical components so we are excited for them to come in so we can start breadboarding them.

We hope to learn more about our judges soon and hope we impress them with our work!

A Successful PDR

On Tuesday, October 14th, 2025, the team traveled down to Clearwater to present our PDR to our sponsor Honeywell Aerospace. The teams presentation went great and we enjoyed being able to tour the site.

This PDR event was a large milestone for our team as moving forward we can start solidifying our CAD models and begin running our Ansys simulations. Our next steps are to begin preparing for our Prototype Inspection day (November 4th)

Tagged as: , ,

PDR Maxing – Blog #6, 10/10/2025

These past two weeks have been very hectic in team ARC. We had our peer reviewed PDR presentation on Tuesday 10/7 and got some very valuable feedback from professors on our preliminary design. We also made a new block diagram to show our preliminary design in a more friendly way.

There are a few changes in this design compared to the previous block diagrams we have made. Firstly, the introduction of some new electronics. In the red is the Fiber Bragg grating system which is a complex temperature sensing system that can provide an accurate temperature field measurement. This temperature field will be used to determine when the flaps on the back would actuate and open up. Another new piece is the pink blocks. These blocks are a dampening system meant to protect the electronics during launch, orbit, and the beginning stages of re-entry to allow for all of the flaps to actuate before they demise. Additionally, its not a new electronics piece, but we re-designed the flaps to open past the end of the body to better influence the center of pressure whilst also being more friendly to design around.

We also narrowed down the electronic selection for the PDR and made a block diagram showing how distribution of power and control signals. This decisions are preliminary so we have some beginning power calculation, so parts may change in the future.

The next step for our team is our actual preliminary design report presentation at Honeywell Aerospace in Clearwater. This is in a few short days so the team is staying busy!

Tagged as: ,

Ansys – Blog #5, 10/3/2025

Hey folks! 
We’re almost there with our Preliminary Design Review (PDR) and wanted to give you a quick, behind‑the‑scenes look at what we’ve been chewing on this week. 

We’re talking P‑frust (a new way to say “pyramidal frustum”) 

  • Why the shape? 
    Think of a pyramid with a short top. That gives us surface area to play with while keeping the center of mass stable. Plus, it’s a good canvas for our “flaps” that pop out to suck up drag when the vehicle slams into the atmosphere. 
  • What’s in the flap‑drama? 
    We’re testing how long they are, how far they lean out from the body, and how that changes the center of pressure/gravity and heat generation 

Visually 

  • 3‑D CAD (SolidWorks): We modeled dozens of “what‑if” variants, each a slightly tweaked frustum or flap combo. 
  • Heat‑Up Analysis (ANSYS): Those CADs are pulled into a simulation engine that tells us where the air‑fire hits hardest and how fast the heat preforms. We down selected our variables to focus on 
  • Shape of the frustum (how vertex angle and weight distribution effects of COP, COM, and heat generation) 2.  
  • The design of the flaps (how flap length and angle from frustum effects of COP, COM, and heat generation)  
  • Later the material parameters will be defined and tested. 
  • Brant Chart: This simple, graphic roadmap will line up the work for the next few weeks to keep us organized 

The Crew & Their Missions 

Who Mission 
Electrical Duo Building the flap‑channeled wiring, control loops, and battery budget. +2 handle the tri‑state logic to keep the flap actuation smooth and ultra‑light. 
Modeling Quintet Each of us blocks out a new parametric “family.” We’ll push the parameters, run the heat‑flags, then hand off the best pairings to the electrical folks. 

We’re split to keep things moving. The electrical and modeling workflows are now tightly intertwined – a bit of code‑first, a bit of geometry‑first. 

Road‑Map & Next Tweaks 

  1. Lock the baseline shape in SolidWorks – we’re picking a prototype that balances drag and thermal load. 
  1. Run the first ANSYS thermal snapshot – get a quick heat‑flux map so we know where the “hot spots” sit. 
  1. Finalize the Brant Chart before the weekend – this ensures we joke about deadlines, not crisis. 
  1. Material deep‑dive next week – high‑conductivity, low‑density alloys (think aluminum‑silicon and lightweight composites). We’ll compare them by melting point, oxidation dance, and weight. 

At the end of the day, it’s a lot of math, a lot of questions to explore down the road. But we’re getting there – the P‑frust is almost ready to spring into action, and the flaps are ready to give the drag a performing‑arts twist. 

Stay tuned for the next update – we’ll share the ANSYS plot that will either blow us away or make us rethink the whole angle.

Tagged as: ,

Pyramidal Frustum – Blog #4, 9/26/2025

Above is our first SolidWorks model, a pyramidal frustum with flaps that open up to both increase surface area and stability during re-entry. One of the main issues of design for demise is how difficult it is to simulate re-entry conditions on Earth. There are three main things that make design for demise difficult to implement; 1. Re-entry processes such as fragmentation have not been fully understood and therefore is not possible to simulate at this time, 2. Simulating the conditions of low earth orbit re-entry on the ground is extremely difficult and costly, and 3. The dynamics of re-entering fragments is not fully understood and very difficult to simulate. This design helps to mitigate the effects of the third challenge. By having our design orient itself, the dynamics of the part can then be more accurately simulated.

Of course, all great ideas start from a basic sketch. Building off of an initial idea of a cube that could open, the pyramid shape was born. Cubes would be chaotic in re-entry, tumbling so fast that their dynamics would be near impossible to simulate. Pyramids on the other hand have a center of gravity ahead of the center of pressure, creating a restoring moment that should orient the part. The wings should also help with this as they further move the center of pressure back.

Also this week, we have been working diligently on our Preliminary Design Report (PDR). The PDR is a comprehensive document to be presented to our liaisons at Honeywell. The paper contains everything we have done so far as a team formatted into one digestible paper.

Furthermore, we have developed the end goal of our project a little further. Instead of creating one model for one scenario, we would like to develop multiple models for multiple scenarios and then use those models to create a machine learning model utilizing Kriging. We believe this is the best way to approach our solution, as one model does not nearly cover all of the possible variables of satellite missions. What if the satellite is made of steel? Aluminum? What if it is entering from geostationary orbit rather than low earth orbit? These are all variables we would like to account for in the model we develop.