Project Narrative

In this project my group and I focused on the design, development and testing of three interconnect components for an airport baggage management system

1. A mechanism used to transport luggage from an upper platform to a lower platform using a rotary actuator
2. A software program to summarize passenger and airplane information from files.
3. A control program that uses QR codes on luggage to operate a q-arm, sorting them into either a rejection bin or the transport mechanism

What we did:

<aside> 💡

Use 3D models to simulate the mechanism (see left)

</aside>

<aside> 💡

Prototyped parts for hands-on understanding

</aside>

<aside> 💡

Adopted a divide-and-conquer approach to address project components

</aside>

<aside> 💡

Used a variety of strategies and materials

</aside>

What We Learned:

• Simplified designs reduce mechanical failure points.
• Virtual prototyping using CAD tools can substitute effectively for physical iterations when resources are limited.
• Adaptable and clear coding practices enhance software reliability.

• The Mechanism:

• Hardware and Software Programs:

Team’s Work and Personal Contributions

Teamwork:

• Collaborative brainstorming of design strategies.
• Shared prototyping tasks using both CAD models and limited physical prototypes to leverage individual strengths.
• Regular discussions ensured alignment and resolved issues effectively.

Mistakes we Made as a Team:

• Tried for too long to solve issues as individuals rather then bringing it to the attention of our team
• Did not put enough emphasis on the Q-arm code

Personal Contributions:

• Designed and refined the rotary actuator’s glowstick-type connector using CAD tools, with multiple iterations captured virtually.
  • Example: CAD screenshots showcasing design iterations.
• Led the redesign of the drawbridge ramp, focusing heavily on virtual prototyping due to material constraints.
  • Example: Series of CAD models showing the ramp’s evolution.
• Organized the graphical interface for data visualization in the software program.
  • Example: Code snippet showcasing the graphical interface structure.
• Assisted in troubleshooting and refining the hardware program.
  • Example: Diagram of coordinate-based commands used in the hardware program.

# Gathers and formats information found in the functions we called upon
        plane_model = layover1[plane][0]
        b_over = "Oversold Business seats: " + str(oversold_b[plane][1])
        e_over = "Oversold Economy seats: " + str(oversold_e[plane][1])
        bags = "Overweight bags: " +str(weight1[plane][1])
        lay = "Layover Passengers: " + str(layover1[plane][1])
        
        # Write each peice of information going down the column
        w.up()
        w.goto(x+20,65)
        w.write(plane_model, font = ("Arial", 12, "bold"))
        
        w.goto(x+5,20)
        w.write(b_over, font = ("Arial", 10, "normal"))
        
        w.goto(x+5,-10)
        w.write(e_over, font = ("Arial", 10, "normal"))
        
        w.goto(x+5,-40)
        w.write(bags, font = ("Arial", 10, "normal"))
        
        w.goto(x+5,-70)
        w.write(lay, font = ("Arial", 10, "normal"))
        
        x += 200 # Move to next column

Reflection

Here discuss events that occurred and the possible reasons for them. Mention any questions you have, any skills or aspects you learned that you may carry on for future projects. You can also mention what you would have done differently given the chance. Remember a reflection is NOT a summary of the event, a list of actions, and it is not written in third person. A reflection is a process of identifying, questioning and assessing our deeply held assumptions. Do NOT use bullet points for this section.

This project was a learning curve in the balance between theoretical knowledge and practical application. The major challenge included malfunctioning of the Q-arm during testing, thus limiting our ability to fully validate the hardware program. This issue highlighted the need for contingency planning and more rigorous pre-testing to identify potential flaws early on.

The second important lesson was iterative prototyping. While there were limitations to the number of physical prototypes, the use of CAD models for design simulation became very useful. Such experiences highlighted the importance of adaptability and persistence when confronted with unforeseen obstacles.

With this in mind, I would allow more time for hardware testing and debugging to avoid last-minute rushes. I would also try more advanced CAD simulation tools earlier in the development of virtual prototyping.

This project gave further depth to my understanding of teamwork, technical design, and problem-solving. Skills and insights to be used thereafter-managing iterative workflows and designing for adaptability-will definitely be carried forward into future engineering challenges.