Vishnu Sanjay
08-15-2017, 12:01 PM
Hello! I am Vishnu Sanjay and until I recently graduated, I was the mechanical lead at the FSE team, 4ze Racing, of SRM University, Chennai. With Formula Student Germany 2017 recently concluded and with my team looking to compete at next year’s edition of the competition, I thought I could help out a bit by starting a discussion regarding the conceptual design stage on these forums.
A word of warning; this post contains about 3000 words and might put you to sleep if you attempt to read it in one go.
Anyways, now that I have mentioned the possibility of that happening, the key reasons for me deciding to do this are twofold, and neither of them is my interest in developing a textual soporific. They actually are:
1. I spent a lot of time thinking about stuff after seeing them debated on these forums. The facts that there were multiple viewpoints presented in discussions, and that I didn’t have a way of knowing which arguments were right, were what spurred me to explore fields of study that I had a poor understanding of prior to coming across that discussion. This then led me to understand and develop tools and systems that enabled me to verify for myself, from first principles, which of the viewpoints presented had possible merit, and with what assumptions they did so. This is how I was able to start thinking in terms of the system instead of just in terms of the parts. It was by this method that I was able to guide and convince my juniors to devote their time and efforts towards understanding certain aspects of the car and project that I deemed necessary. HOWEVER, it was not always possible for me to convey what assumptions I was making when I told them something, and so if they accepted what I was saying without thinking them through, they could easily, in the future, end up misusing what I said. They are not necessarily to blame, as it requires being at a certain vantage point, before being able to see most system level issues clearly. On these forums however, there are people who will definitely be able to tell me if I missed out something important, that they should be aware of.
2. In Geoff Pearson’s (Big Bird’s) excellent ‘Reasoning…’ thread, he subdivides the project into 4 levels. Most of the damage to the project is done when people ‘blindly follow’ other teams when making any decisions at Level 1, without themselves deriving them from whatever their own higher level capabilities are. Now, during my time at college, during my final year, I understood the necessity for better project management and systems engineering in my team and was fortunate enough to meet and get a like-minded faculty member at my University to hold a few Project Management sessions and classes on Control Systems with the team. More than all else I did, this was, in my opinion, the biggest contribution I made to my team. The current team is definitely better equipped than mine was, when starting out with this project. Very briefly, their Level 4 and some of their Level 3 goals have been defined, with the car to be designed completely by December, and the car running by March. All the consequent implications get flowed down to Level 2 and Level 1 goals. Now it is with respect to Level 2 (Vehicle Integration, which is what a conceptual design stage occupies itself with) that I hope most of this thread will devote itself to. I do have some ideas regarding these and the current team leads are aware of them. However I would really like to hear how other people would do it too.
THE CURRENT SITUATION:
Now, before I proceed further, I would like to state that most of what I say from now on is aimed at a team like my juniors (a team that understands/must satisfy the following before getting into any of this: reliability is key, rule compliance is key, low cost is key (no top team budget) and a car for FSG needs to be done by March). They have about 15-20 students who were recruited just prior to our build, with about half of them being more equal in my eyes than the rest. They also have about a dozen new recruits, who will spend this year getting up to speed. The budget for my batch’s project was around $17000 overall for the entire project, including costs for the competition, and they are not likely to get significantly more this time around, due to the many other projects that the University also funds. The fact that we won our National Competition (more because we had a more-reliable-than-the-rest car than because it was fast) might get us slightly more, and hopefully attracts support from a few more sponsors during the course of this season. They have spent the time since the competition ended testing the car and figuring out in what ways and why the car did not deliver what design predicted. I have been helping them process and interpret this data,(I have posted some of it on Bill Cobb’s ‘Testing…’ thread) and together we have found how much compliance and poor attention to manufacturing detail contribute to a disappointing track car.
However, I don’t intend to keep complaining about the car. Testing it was a very useful what-not-to-do lesson to everyone involved and will have significant impacts in the way the next car is designed. I shall continue describing in what other ways they might face constraints. A major manufacturing constraint due to a limited budget was: My batch wasn’t allowed to operate the CNC machines in our CNC lab (we have operators) and this significantly drove up production time. The Hybrid team found a clever way around this by writing all their CNC code before they showed up to machine their stuff, and spent only about half the time we did. Nevertheless, not being allowed to operate the machines yourselves could be a disadvantage (the CNC lab closes at 5 every evening). It forces the team to be better organised, and to rely less on machining, if they want to get stuff done. The more organised a team already is, and the more ways it knows to make strong parts quickly (hint: sheet metal fabrication and welding) the better equipped it is to make light of this. It also makes it critical for a design freeze to happen before December. Now, allowing for at least a month for a detail design stage, this only leaves them two and a half months to explore the design space. It is this that I would like to make easier for them with the help of this thread.
Of course, you guys could share stuff that has worked for you under different constraints. I for one would be very interested to hear about them, and it might tell my current team which constraints to try to eliminate for future batches.
Right now, the things that they have going for them that I didn’t are: an understanding of testing of a car, test data from a car, an understanding of control systems and improved project management (means there are still the usual annoying ego clashes, and some lazy individuals, but most of the guys who want to contribute have their heads screwed on somewhat better than I did). But, and this is where I’m trying to help, they do not yet have the kind of clear communication between subsystems and are (so far) still slightly sketchy in their understanding regarding what tools enable this to happen.
Also, another thing that I have only recently realised in a conversation with a friend was that viewpoint transfer is just as important as knowledge transfer in a project like this. Unless this is done, it is likely that people will do things because someone in the know said so. This kind of stuff is level 4 and since a competition rarely asks for such documents, such documents are rarely prepared. Funnily enough, our National comp required of us two things that an international FS comp doesn’t. One was a Gantt chart, and the other is that our car needs (certain parts) to be assembled and disassembled within an hour. They were both useful. And also, when explaining our Gantt chart, and helping my juniors make theirs, a lot of the project’s quirks and potential pitfalls became apparent to them. They now currently understand that managing the project is more important than and at least as difficult as the Level 1 work they had been mostly spending time on previously.
[Character limit, continued in the next post]...
A word of warning; this post contains about 3000 words and might put you to sleep if you attempt to read it in one go.
Anyways, now that I have mentioned the possibility of that happening, the key reasons for me deciding to do this are twofold, and neither of them is my interest in developing a textual soporific. They actually are:
1. I spent a lot of time thinking about stuff after seeing them debated on these forums. The facts that there were multiple viewpoints presented in discussions, and that I didn’t have a way of knowing which arguments were right, were what spurred me to explore fields of study that I had a poor understanding of prior to coming across that discussion. This then led me to understand and develop tools and systems that enabled me to verify for myself, from first principles, which of the viewpoints presented had possible merit, and with what assumptions they did so. This is how I was able to start thinking in terms of the system instead of just in terms of the parts. It was by this method that I was able to guide and convince my juniors to devote their time and efforts towards understanding certain aspects of the car and project that I deemed necessary. HOWEVER, it was not always possible for me to convey what assumptions I was making when I told them something, and so if they accepted what I was saying without thinking them through, they could easily, in the future, end up misusing what I said. They are not necessarily to blame, as it requires being at a certain vantage point, before being able to see most system level issues clearly. On these forums however, there are people who will definitely be able to tell me if I missed out something important, that they should be aware of.
2. In Geoff Pearson’s (Big Bird’s) excellent ‘Reasoning…’ thread, he subdivides the project into 4 levels. Most of the damage to the project is done when people ‘blindly follow’ other teams when making any decisions at Level 1, without themselves deriving them from whatever their own higher level capabilities are. Now, during my time at college, during my final year, I understood the necessity for better project management and systems engineering in my team and was fortunate enough to meet and get a like-minded faculty member at my University to hold a few Project Management sessions and classes on Control Systems with the team. More than all else I did, this was, in my opinion, the biggest contribution I made to my team. The current team is definitely better equipped than mine was, when starting out with this project. Very briefly, their Level 4 and some of their Level 3 goals have been defined, with the car to be designed completely by December, and the car running by March. All the consequent implications get flowed down to Level 2 and Level 1 goals. Now it is with respect to Level 2 (Vehicle Integration, which is what a conceptual design stage occupies itself with) that I hope most of this thread will devote itself to. I do have some ideas regarding these and the current team leads are aware of them. However I would really like to hear how other people would do it too.
THE CURRENT SITUATION:
Now, before I proceed further, I would like to state that most of what I say from now on is aimed at a team like my juniors (a team that understands/must satisfy the following before getting into any of this: reliability is key, rule compliance is key, low cost is key (no top team budget) and a car for FSG needs to be done by March). They have about 15-20 students who were recruited just prior to our build, with about half of them being more equal in my eyes than the rest. They also have about a dozen new recruits, who will spend this year getting up to speed. The budget for my batch’s project was around $17000 overall for the entire project, including costs for the competition, and they are not likely to get significantly more this time around, due to the many other projects that the University also funds. The fact that we won our National Competition (more because we had a more-reliable-than-the-rest car than because it was fast) might get us slightly more, and hopefully attracts support from a few more sponsors during the course of this season. They have spent the time since the competition ended testing the car and figuring out in what ways and why the car did not deliver what design predicted. I have been helping them process and interpret this data,(I have posted some of it on Bill Cobb’s ‘Testing…’ thread) and together we have found how much compliance and poor attention to manufacturing detail contribute to a disappointing track car.
However, I don’t intend to keep complaining about the car. Testing it was a very useful what-not-to-do lesson to everyone involved and will have significant impacts in the way the next car is designed. I shall continue describing in what other ways they might face constraints. A major manufacturing constraint due to a limited budget was: My batch wasn’t allowed to operate the CNC machines in our CNC lab (we have operators) and this significantly drove up production time. The Hybrid team found a clever way around this by writing all their CNC code before they showed up to machine their stuff, and spent only about half the time we did. Nevertheless, not being allowed to operate the machines yourselves could be a disadvantage (the CNC lab closes at 5 every evening). It forces the team to be better organised, and to rely less on machining, if they want to get stuff done. The more organised a team already is, and the more ways it knows to make strong parts quickly (hint: sheet metal fabrication and welding) the better equipped it is to make light of this. It also makes it critical for a design freeze to happen before December. Now, allowing for at least a month for a detail design stage, this only leaves them two and a half months to explore the design space. It is this that I would like to make easier for them with the help of this thread.
Of course, you guys could share stuff that has worked for you under different constraints. I for one would be very interested to hear about them, and it might tell my current team which constraints to try to eliminate for future batches.
Right now, the things that they have going for them that I didn’t are: an understanding of testing of a car, test data from a car, an understanding of control systems and improved project management (means there are still the usual annoying ego clashes, and some lazy individuals, but most of the guys who want to contribute have their heads screwed on somewhat better than I did). But, and this is where I’m trying to help, they do not yet have the kind of clear communication between subsystems and are (so far) still slightly sketchy in their understanding regarding what tools enable this to happen.
Also, another thing that I have only recently realised in a conversation with a friend was that viewpoint transfer is just as important as knowledge transfer in a project like this. Unless this is done, it is likely that people will do things because someone in the know said so. This kind of stuff is level 4 and since a competition rarely asks for such documents, such documents are rarely prepared. Funnily enough, our National comp required of us two things that an international FS comp doesn’t. One was a Gantt chart, and the other is that our car needs (certain parts) to be assembled and disassembled within an hour. They were both useful. And also, when explaining our Gantt chart, and helping my juniors make theirs, a lot of the project’s quirks and potential pitfalls became apparent to them. They now currently understand that managing the project is more important than and at least as difficult as the Level 1 work they had been mostly spending time on previously.
[Character limit, continued in the next post]...