Developing a Cloud Based IoT Dashboardfor Monitoring Data in Civil
Project Overview
TECHNICAL BACKGROUND REQUIREMENTS
Experience in developing cloud-based dashboards and user-friendly interfaces.
Hardware Components
Microcontroller - LILYGO TTGO LoRa32 T3-S3 (915Mhz)
BMP280 Barometric Pressure and Altitude Sensor
DHT22 Temperature And Humidity Sensor
5kg Body Load Cell Weighing Sensor
Software Components
Grafana Dashboard
AWS EC2 (to host grafana)
ThingsBoard.io
Things Network
Lorem Ipsum
Network Diagram
Final Hardware Images
A small river named Duden flows by their place and supplies it with the necessary regelialia. It is a paradise
Final Hardware Video
On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized by the charms of pleasure of the moment, so blinded by desire, that they cannot foresee the pain and trouble that are bound to ensue
Final Product Video
On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized by the charms of pleasure of the moment, so blinded by desire, that they cannot foresee the pain and trouble that are bound to ensue
Civil Lab Images
A small river named Duden flows by their place and supplies it with the necessary regelialia. It is a paradise
Civil Lab Video
On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized by the charms of pleasure of the moment, so blinded by desire, that they cannot foresee the pain and trouble that are bound to ensue
Our Team Members
A small river named Duden flows by their place and supplies it with the necessary regelialia. It is a paradise
Pavan Kumar Goud Karnam
Software Engineer
Syed Baquar Mehdi Razvi
Project Manager & Software Engineer
Anand Prit Singh
Hardware Engineer
Steven Paul Thangundla
Software Engineer
Amandeep singh
Hardware Engineer
ROLES AND RESPONSIBILITY
Steven Paul Thangundla
Software Engineer
Responsibilities
- Software design and development. - Implementation of sensor node firmware and software
- Integration with LoRaWAN network and cloud services
- Testing and debugging of software components
Capabilities
- Proficiency in programming languages (e.g., Python, C/C++). - Knowledge of IoT protocols and frameworks
- Experience in software development methodologies (e.g., Agile)
- Attention to detail and problem-solving skills
Syed Baquar Mehdi Razvi
Project Manager & Software Engineer
Responsibilities
- Overall project coordination and management
- Task assignment and progress tracking
- Software design, development, and testing
- Ensuring adherence to project timelines and deliverables
Capabilities
- Strong leadership and communication skills
- Proficiency in project management tools
- Experience in software development and testing
- Ability to prioritize tasks and manage deadlines effectively
Pavan Kumar Goud Karnam
Software Engineer
Responsibilities
- Software development for user interface/dashboard
- Integration with AWS cloud services and data processing pipelines
- Implementation of security features and access control mechanisms
- Documentation and technical writing
Capabilities
- Proficiency in front-end and back-end development technologies
- Familiarity with cloud computing and AWS services
- Strong writing and documentation skills
- Ability to work collaboratively in a team environment
Anand Prit Singh
Hardware Engineer
Responsibilities
- Selection and integration of sensors into sensor nodes
- Hardware design and prototyping of sensor nodes
- Testing and validation of sensor node hardware
- Collaboration with the software team for sensor data integration
Capabilities
- Knowledge of electronics and sensor technologies
- Experience in hardware design and prototyping
- Ability to troubleshoot and debug hardware issues
- Effective communication and teamwork skills
Amandeep Singh
Hardware Engineer
Responsibilities
- Selection and integration of LoRaWAN gateway devices
- Hardware design and deployment of LoRaWAN network infrastructure
- Testing and validation of LoRaWAN gateway devices
- Collaboration with the software team for network integration
Capabilities
- Familiarity with networking technologies and protocols
- Experience in hardware deployment and testing
- Ability to work in a cross-functional team environment
- Attention to detail and problem-solving skills
Week 1
Meeting Summary |
Elaboration |
|---|---|
|
Introduction and project |
The team likely discussed the goals, objectives, and scope of the project, as well as individual roles and responsibilities. |
|
Setting up |
Communication channels such as email groups, messaging apps, or project |
|
Initial brainstorming |
The team might have conducted a brainstorming session to generate ideas, |
Week 2
Meeting Summary |
Elaboration |
|---|---|
|
Assignment of initial |
Initial tasks, such as conducting research, gathering resources, or |
|
Progress update on |
Team members likely provided updates on the tasks assigned in theprevious week, discussing any challenges or achievements encountered.management platforms may have been established for team coordination. |
|
Discussion on project |
Detailed project requirements, including technical specifications, client |
|
Planning for future tasks |
The team may have outlined the next steps, including research plans, design considerations, or preliminary timelines for project milestones. |
Week 3
Meeting Summary |
Elaboration |
|---|---|
|
Confirmation of meeting |
The team confirmed the schedule for future meetings and agreed |
|
Sydney campus students |
In week 3, it was decided that students at the Sydney campus would be responsible for handling software-related aspects of the project. |
|
Melbourne campus |
Similarly, students at the Melbourne campus were tasked with handling hardware-related aspects, as discussed in the meeting. |
|
Resources to be used |
The meeting likely discussed the resources available or needed for the project, such as software tools, equipment, or online platforms. |
|
Parameters for |
Parameters for evaluating Assessment 1 were discussed, outlining criteria such as technical proficiency, presentation, or documentation. |
|
Usage of thingsboard.io |
The group agreed to utilize thingsboard.io, a platform for managing IoT devices and data visualization, for measurement purposes. |
|
Choice of platform for |
It was decided that any suitable platform could be used for creating dashboards to display project data and analytics. |
Week 4
Meeting Summary |
Elaboration |
|---|---|
|
Transition to using Teams |
The team decided to switch from using Zoom to Microsoft Teams for their meetings starting from the following week. |
|
Overview of Assessment 1 |
An overview of Assessment 1 was provided, likely including its objectives, requirements, and deadlines. |
|
Report format |
The format and structure of the report for Assessment 1 were discussed, outlining sections, formatting guidelines, and any templates. |
|
Task distribution among |
Responsibilities and tasks for completing Assessment 1 were allocated among team members based on their strengths and expertise. |
Week 5
Meeting Summary |
Elaboration |
|---|---|
|
Sharing and feedback |
A rough draft of the report was shared among team members for review and feedback, facilitating improvements before submission. |
|
Technical report |
The team likely reminded each other of the approaching deadline for submitting the technical report and discussed any pending tasks. |
|
Final review and polishing |
Team members may have conducted a final review of the technical report, making any last-minute revisions or corrections for accuracy. |
|
Preparation for |
Discussions may have focused on gathering materials and planning the structure and content of the portfolio to showcase project |
Week 6
Meeting Summary |
Elaboration |
|---|---|
|
Review and feedback on technical report draft |
The team received feedback from various stakeholders, including the unit coordinator, supervisor, and tutor, on the draft of their report. |
|
Corrections and revisions based onreceived advice |
Necessary corrections and revisions were made to the technical report in accordance with the feedback provided by the stakeholders. |
|
Focus on technical accuracy of the report |
Emphasis was placed on ensuring the technical accuracy and precision of the report content to maintain its credibility and quality. |
|
Discussion on report improvements |
The team discussed ways to improve the report, possibly focusing on areas such as clarity, depth of analysis, or presentation style. |
|
Introduction to portfolio basics |
Basics of creating and maintaining a portfolio were introduced, highlighting its importance for showcasing skills and achievements. |
|
Details on sensors and ESP32 |
Details regarding sensors and the ESP32 microcontroller were likely discussed, possibly covering specifications, functionality, etc. |
|
Booking arrangements |
The team made arrangements, possibly for equipment or facilities needed for the project, ensuring everything was in place for progress. |
Week 7
Meeting Summary |
Elaboration |
|---|---|
|
Ability to plan realistic and significant weekly tasks |
Discussion on report with professor and team members, improvement suggestions for next assessment |
|
Basic understanding and planning for E-portfolio design |
Finalizing Sensors and ESP32 details, preparing integration plan, procurement approval required from professor |
|
Researching existing cloud-based IoT platforms and dashboard solutions |
Identifying specific requirements tailored to civil engineering labs, assigning team members for market research |
|
Conducting final review |
Ensuring all components are polished before launch, accessibility for disabled users and various devices |
|
Identifying project challenges and approaches to deal with them |
Reevaluating resource allocation, considering outsourcing or negotiation, implementing clear communication |
|
Researching plugins/widgets for multimedia integration |
Testing formats for compatibility across devices and browsers |
|
Establishing quality standards and review processes |
Creating checklist for proofreading, fact-checking, and compliance with branding guidelines |
Week 8
Meeting Summary |
Elaboration |
|---|---|
|
Planning realistic weekly tasks |
|
|
Identifying project challenges and practical approaches |
|
Week 9
Meeting Summary |
Elaboration |
|---|---|
|
Planning realistic weekly tasks |
|
|
Identifying project challenges and practical approaches |
|