Proposal Progress | Week 6

Dates: 6/11/25 - 6/15/25

I took ownership for a wide range of implementation and documentation tasks on the project website, with a focus on system programming and improving the clarity and accuracy of our content. Several formatting and organizational updates were completed. The Time and Effort Log, Engineering Requirements, and Engineering Specifications tables were all migrated to Google Sheets to improve readability, ease of updates, and formatting control. In addition, the logs were restyled using Google Docs to match the website’s visual theme, with improved spacing, alignment, updated week listings covering the entire summer semester, and created the new Task Allocation and Team Synchronization page with content. 

I revised the task allocation section to reflect implementation-only responsibilities and updated the terminology from “System Integration” to “Assembly.” In the Time and Effort Log, I switched the duration and  named person categories for consistency, and I adjusted the Project Log to reflect weekly meeting ranges instead of calendar weeks. Additionally, I reformatted the Weekly Meetings Summary by placing the actual meeting date in front of each weekly entry to improve traceability. For the engineering requirements,

Standardized the titles to begin with “System shall” and corrected terminology and spelling issues, including updating requirement #5 to reflect the minimum and maximum operating temperatures based on the component with the highest heat output. I also incorporated a power dissipation estimate and fixed requirement #8 for accuracy. Range and response time values were updated to reflect worst-case scenarios based on component datasheets. In the engineering specifications section, I replaced specific product names like “Pico” with general terms such as “microcontroller” to maintain consistency and adaptability. For the monetary budget,

I streamlined the list to include only essential items, added a total cost estimate, and marked college-provided components with an asterisk along with a legend for clarification. Lastly, I made a future recommendation to scale the system design to support 16 motors instead of 8, ensuring the project is adaptable to future expansion.​ 

Created the first iteration of the power budget based on the components we have chosen to start the project with via a google sheet document, adjustments can be made as revisions occur. 

This week, I connected with Tyler and provided him with an overview of the NAVI project and the accompanying survey. He will be reaching out to HR to ensure the survey meets their internal requirements and to identify potential participants, including staff, members, and others who may be appropriate for the initial rollout. Additionally, their IT department will assist in verifying that the survey is accessible and ready for proper distribution with online and hands on formats. We plan to follow up on Wednesday, once Tyler shares his availability, to discuss the survey in more detail and determine next steps.