Mr.Vasantha Kumar Narayan, Cyclotis Software Solution, Bangalore
Ms. I. Manimozhi, Assoc.Prof., & CSE – HOD, MVJCE, Bangalore
Ms. Premalatha, Assoc.Prof.& EEE – HOD,MVJCE, Bangalore
Mr. Naveen B, Asst.Prof.– Mech., MVJCE, Bangalore
The Student Development Programme – 3, on ‘Foundation SkillIn Integrated Product Development’ (FSIPD) was organized on 27th August, 2018, at 8.30 am, at Smt. Rajalakshmi Seminar Hall, MVJ College of Engineering. The SDP3was conducted from 27th August 2018 to 29th August 2018, and on 08th September 2018, in the campus.Dr. Nagaraj Sitaram, Principal, MVJ College of Engineering graced the occasion, with his esteemed presence. Prof. I Manimozhi, Chief Coordinator, MVJ College of Engineering, presided over the event.
Dr. Nagaraj Sitaram,in his speech,highlighted the essence and objective of the programme. He emphasized that the core of Engineering is problem-solving. With real-world examples, he pointed out the yawning gaps that prevail, between the various services in India, and said that the SDP is designed to examine these gaps and seek possible solutions. He also mentioned that this SDP is a firm push to kick start the integration of different knowledge minds across various disciplines.
The Inauguration meet concluded with a Vote of Thanks by Premalath, Assoc. Prof.&HOD of Electrical and Electronics Engineering department.
Day 1: 27/08/2018
The first day of the SDP was conducted under 5 Sessions. The first 3 sessions were on making a project from the industrial design perspective. The next 2 sessions discussed case studies about the products.
This SDP was aimed at focusing on the new standards for knowledge-sharing between the industry and the educational institutions, and has contributed significantly towards strengthening the knowledge .
Morning Session: 9.00 AM to 12:45 PM
The topics Covered were:
The Speakers Ms. Manimozhi and Mr. Naveen gave a brief overview on how a Product is developed. They also touched upon the Factors Affecting Product Decision.
The Speakers had assigned roles and responsibilities to team members from all disciplines of Engineering. The faculty members selected the case study of products like lawnmowers, self- monitoring cylinder, cruise control, screw driver etc. The forenoon session ended with a talk on Cost of Defects and also Terms and Definitions of Requirement Engineering.
Afternoon Session:1:20 PM to 4:20 PM
The topics covered in the afternoon session were:
There was also a discussion on four case studies of Requirement Engineering, by all the student members, following which they were grouped into 13 groups with each group being given one case study to work on and present.
Team 1 presented the topic Heart Attack Detection System.
Heart attack (coronary artery disease) is one of the most common and very serious effects of aging. Cholesterol, fatty deposits, emotional stress, and drug intake lead to the building of spasms in the walls of blood vessels. As the spasm grows, there is reduced blood flow through the arteries. As a result, the heart muscle can’t get the blood or oxygen that it needs. This can lead to a heart attack. In this Project, the students presented a system which will help to decrease the death rate due to heart attacks, through early detection of a heart attack. In their system, they usea smart Heart Beat sensor, which is easily available in the market.
Team 2 presented automatic segregations of waste system (ASEG)
The nation, and the world, is facing a huge problem today, of disposal, segregation and recycling of solid waste. Improper management of these wastes pose dangers to human health and ecological system and are hazardous. There is a rapid increase in the volumes and categories of solid waste, as a result of urbanization, constant economic growth, and industrialization. Global Waste Management Market reported that the amount of waste generated worldwide is 2.02 billion tones. “Wastes are not always waste, and can be convert manure.To properly manage the waste, it has to be handled, segregated, transported and disposed properly, so as to reduce the risks to public lives and to the environment. The economic value of waste is best comprehended, when it is segregated. Currently, there is no such system for the segregation of glass, plastic and metallic wastes, at industrial level. This paper presented by this team, proposes an Automation of Waste Material Segregation, in the scrap industry. This method is an easy and simple solution, for segregation of three types of wastes – glass, metal and plastic. It is designed to sort the trash into metallic waste, plastic waste and glass waste, ready to be processed separately for the next process of operation. The method uses inductive sensors for metallic items, and capacitive sensors to distinguish from dry waste.
Team 3 presented the product,Smart Helmet.
The impact when a motorcyclist gets involved in a high-speed accident without wearing a helmet is very dangerous and can cause fatality. Wearing a helmet can reduce shock from the impact and may save a life. There are many countries enforcing the regulation that requires a motorcycle rider to wear a helmet while riding a motorcycle. Malaysia is an example.
This project was specially developed by this team, to improve the safety of the motorcycle rider. A motorcyclist will be alarmed when the speed limit is exceeded. A Force Sensing Resistor (FSR) and BLDC Fan are used for detection of the rider’s head, and detection of the motorcycle’s speed, respectively. A 315 MHz Radio Frequency Module acts as wireless link which will be able to communicate between the transmitter circuit and the receiver circuit. PIC16F84a is a micro controller to control the entire component in the system. The engine of the motorcycle will start, only when the rider buckles the helmet over his head. An LED will flash if the motorcycle speed exceeds 100 km/hour.
Team 4 team proposed a Smart Car.
In contrast to a traditional mechanical car, the Smart Car is a highly computerized automobile, featuring ubiquitous computing, intuitive human-computer interaction, and an open application platform. In this paper, this team of students proposed an advanced Smart Car demonstration platform, with a transparent windshield display and various motion sensors where drivers can manipulate a variety of car-appropriate applications in augmented reality.
Similar to smartphones, drivers can customize their Smart Car through free downloads of car-appropriate applications,to suit their needs. Additionally, three potential car-appropriate applications related to computer vision are investigated and implemented in the platform by the students, for increased driving safety. The first and second car appropriate applications aim to enhance the driving visual field, by restoring the low-visibility scenes captured during inclement-weather or nighttime driving conditions to be high-visibility ones, and display them on a transparent windshield display. It also surveys pedestrian tracking techniques that combine multiple driving recorders’ information as a mobile surveillance network, including one proposed framework the team has developed as the third car-appropriate application. By embedding these car appropriate applications, the Smart Car has the potential to increase safety of driving conditions, both in daytime and nighttime, even in bad weather.
Team 5 proposed b BOOK.
Braille is a system of reading and writing by touch, used by the visually impaired. It consists of arrangements of dots, which make up letters of the alphabet, numbers, and punctuation marks. The basic Braille symbol, called the Braille cell, consists of six dots arranged in the formation of a rectangle, three dots high, and two across. Other symbols consist of only some of these six dots. The six dots are commonly referred to by number, according to their position in the cell.
In Braille, there are no separate symbols for capital letters. Capitalization is accomplished by placing a dot 6, in the cell just before the letter that is capitalized. The first ten letters of the alphabet are used to make numbers. These are preceded by a number sign which is dots 3-4-5-6.
Thus, 1 is number sign a; 2 is number sign b; 10 is number sign a-j and 193 is number sign a-i-c.
Team 6 proposes an amphibious vehicle (or simply amphibian). It is a vehicle capable of plyingon land as well as on (or under) a waterway.
DAY 2: 28/08/2018
Day 2 of the FDP Program was also divided into 5 sessions. The first 3 sessions were devoted to making a project, and the next 2 sessions to discussions around the project done.
Morning Session: 8:30 AM to 12:30 PM
The trainers focused mainly on System–Level Requirements, and discussed about the Case Study: Laptop and Mobile Electronic items, for circuit branch students. They mainly dealt with solar amphibious system as a example for Mechanical and Aeronautical students.
The trainers listed out some of the responses from students for the Case Study:
Requirements Analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep, and documentation of all aspects of the project development process, from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs, rather than attempting to mould user expectations to fit the requirements. Requirements Analysis is a team effort that demands a combination of hardware, software and human factors – engineering expertise as well as skills in dealing with people.
The trainers addressed the activities for Requirement Analysis, and also listed out the categories. Requirements Analysis is critical to the success or failure of a system or software project. The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.
Conceptually, Requirements Analysis includes four types of activities:
Eliciting requirements: The task of communicating with customers and users, to determine what their requirements are. This is sometimes also called Requirements Gathering.
Analyzing requirements: Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues.
Requirements modeling: Requirements might be documented in various forms, such as natural-language documents, user cases, user stories, or process specifications.
Review and retrospection: Team members reflect on what happened in the iteration, and identify actions for improvement, going forward.
DAY 3: 29/08/2018
Day 3 of theSDP Program consisted of 4 Sessions. The first 2 sessions were on Design issues of Product Development. The third session was on Validations and Verifications. And the last sessionwas on the proposal of the Product done by MVJCE faculty members. The proposals were reviewed and approved by the Speakers.
Morning Session: 8:30AM to 12:45PM
The focus of the speakers was mainly on ‘How to design the products,based on Industrial Design’. The following points were addressed:
There was also an intense discussion with the participants,on the following Case Studies:
Speakers analyzed real time issues of all the products and faculty members were also given a task to discuss the issues related to each product.
A few other concepts relating to Industrial Designs that were discussed:
Afternoon Session: 1:20 PM to 5:30 PM
The following products were finalized to work out low level and high level design parts:
DAY 4: 08/09/2018
Mr. Vasantha Kumar Narayan, General Manager, Robert Bosch, Bangalore
Evaluation process procedure:
Stage 1: Problem Statement
Each Product should have 6 Phases:
Phase 1: Analysis, Requirement Engineering and Specification about the product
Phase 2: Industrial Design (H/W + S/w + User interface Design) as per industrial standards
Phase 3: Validations and Verification’s
(All the testing procedures should be written through TEST CASES)
Phase 4: Simulation and Modeling – use advanced tools (This Phase is optional)
Phase 5: Model/MOCK of product prototype (use any materials). It can be functional or non-functional
Phase 6: Documentation about the product