Week 5 (Mar 17 - Mar 23)

During this week, the team officially began preparing for the intermediate presentation of the project. We are now taking the first steps into the development of the first prototype of SafeNoise.

To kick off this new phase of the project, the team focused on researching and assembling a list of materials required for the development of the prototype. This list includes the RP2040 board that had been previously selected, as well as a battery charging module and several portable battery options that are currently being evaluated. The goal is to ensure that the final device remains lightweight, portable, and capable of functioning for extended periods, without compromising reliability or safety.

In parallel, and following the conclusions reached from the interviews carried out over the past few weeks, we also took the time to define the requirements that our solution must fulfill. These interviews provided valuable feedback regarding the features and functionalities that professionals in the field consider essential. As a result, a detailed requirements list was created, serving as a foundation for the design and development process moving forward.

The team also initiated contact with IStartLab to discuss matters related to 3D printing, including which software to use when creating the first 3D model of our prototype, as well as the application required to send that model to the 3D printer. During this interaction, we also had the opportunity to discuss potential testing environments for our solution. As a result, we were offered the chance to test our prototype in a small-scale but realistic setting: a machine room used by this student group.

This particular room is known for generating high noise levels due to the equipment in operation, which makes it a relevant environment for evaluating our device. The users of this space are required to wear hearing protection and follow safety protocols, providing a valuable context to assess how our portable device performs in real-life conditions and whether it can effectively alert users about dangerous noise exposure.

Lastly, the team has started working on the diagrams and technical drawings that will illustrate the structure and functionality of what is intended to be our prototype, as we move into the development phase.

Group Meeting Notes - Week 5

Components for PPE

• RP2040 (includes gyroscope, accelerometer, microphone, Bluetooth, and WiFi)
• Capacitive sensor
• PCB
• 3D-printed case
• Battery

User Alerts

We have two options:

1. Wristband (for companies that do not allow or prefer not to use mobile phones in the workplace)
2. Mobile phone (for companies that are open to using existing devices)

Note: If one of these options is not implemented, we can argue that it was our goal and present the reason.

Steps in Prototype Development

1. Detect excessive noise levels (instantaneous) // Integrate PPE components.
2. Detect whether the user is wearing PPE correctly.
3. Alert the user to use PPE.

Note: Steps 2 and 3 can be performed in parallel since alerts can be triggered as soon as noise is detected.

Members Present

• David Antunes
• João Silvestre
• Tomás Dias
• Miguel Simões

---

Requirements List

Functional Requirements

1. Detect whether the user is in a noisy environment. This detection is performed on the PPE itself.
2. Detect whether the user is wearing PPE correctly. This detection is performed on the PPE itself.
3. Alert the user to use PPE. This alert will be performed via a device (mobile phone or wristband with LEDs).
4. Ideally:
   • Continuously monitor environmental noise levels and PPE usage.
   • Allow synchronization with an external application (mobile/web) for data analysis.
   • Generate automatic reports for different profiles (worker, safety technician, manager).

Non-Functional Requirements

1. Performance:
   • The system should respond as quickly as possible (preferably ≤ 1 second latency for alerts).
   • Sensors should have an appropriate sampling frequency to ensure accuracy without compromising battery life.
2. Usability:
   • The hardware should be balanced and lightweight to avoid discomfort for the user.
   • The software should have an intuitive interface with minimal interaction required.
3. Reliability:
   • Ideally, achieve ≥ 95% accuracy in detecting noise and incorrect PPE usage.
4. Scalability:
   • Should maintain a scale that allows integration into PPE.
5. Security:
   • Communication between devices should use secure protocols.
6. Compliance:
   • Must comply with European occupational safety standards and data protection regulations (e.g., GDPR).

---

This week marked significant progress as we transitioned into the prototype development phase and began preparing for the intermediate presentation. The team is excited to continue refining the project and working toward a functional prototype.