Status Letter Team Milestones: Ongoing Tasks: Outstanding Action
Contents
1. Daniel Zakzewski Separate GtVinte Subsystems due Feb 7 Hansen Liang V Hansen Liang A preliminary systentacceptancetest strategy applicable te this phase due Feb 8 Jaejoon Yang V Jaejoon Yang due Feb 8 due Feb 8 John Bloore Y John Bloore Risk AssessmentDeeument due Feb 4 A risk assessment identifying critical areas of risk and strategies for managing or ameliorating potential adverse consequences of that risk V John Bloore GestAnatysis due Feb 4 A cost analysis and detailed program budget that demonstrates compliance with financial constraints John Bloore Write eststandtest plan due Feb 2 John Gehrig Y John Gehrig D eutine due Feb 9 Y John Gehrig Gemputer Dashbeard HardwareSelection due Feb 9 Y John Gehrig rite PbR temptate due Feb 6 Y John Gehrig Researeh Embedded Gomputer due Feb 4 Y John Gehrig Setup greup repesitery hesting due Feb 6 Y John Gehrig GestAnatysis due Feb 5 Jordan Blake https app asana com 0 sear ch 26404012932039 26404012932039 3 6 2 8 2015 e Search Asana Jordan Frank Jordan Frank Gt Safety teep PBR due Feb 7 Cost Analysis Risk Assessment Requirements Checklist Preliminary Test Plan Kai Ottaway V Kai Ottaway Examine FSAE Electric rules for battery design due Feb 6 Katie Nellis Y Kati due Feb 8 Nate Hand V Nate Hand Sysiten State Anatysis due Feb 4 A system state analysis that enumerates the system states and the events that cau2. Breakdewn Siides V Stephen Mazich FaskBreakdewn due Feb 5 Y Stephen Mazich Develep Gemplete Hierarehicat Subsystem Breakdown due Feb 4 A system design baseline including detailed and complete hierarchical subsystem breakdown This breakdown shall be reflected in all other documentation consistently Traceability matrices risk assessments schedules etc shall all be consistent with this breakdown Y Stephen Mazich Write sensers est plan due Feb 2 William Stathis https app asana com 0 search 26404012932039 26404012932039 5 6 2 8 2015 e Search Asana Yiming Chen V Yiming Chen Statustetter Monitoring the group on completing tasks Zach Helwig Zach Helwig GE4 C PBR Cost Analysis Risk Assessment Requirements Checklist Preliminary Test Plan Unassigned https app asana com 0 search 26404012932039 26404012932039 due Feb 7 due Feb 7 due Feb 4 due Feb 4 due Feb 3 due Feb 4 due Feb 5 due Feb 4 due Feb 5 due Feb 5 due Feb 5 due Feb 4 due Feb 3 due Feb 3 due Feb 2 6 6 2 8 2015 e Search Research languages IDEs to use Asana Incomplete Tasks due within the next 7 days Adam Cornwell Adam Cornwell Getting Started due Feb 11 Adam Cornwell Write Revise the user manual due Feb 13 Adam Cornwell Research languages IDEs to use due Feb 11 Alex Hytha Alex Hytha Calibration and Accuracy Draft due Feb 14 Work on converting the Calibration and Accuracy outline in the Calibration an
3. Pertien interface Deeument Y Daniel Zakzewski due Feb 2 due Feb 8 due Feb 7 due Feb 7 due Feb 7 due Feb 7 Make some slides on your assigned part and add it to the drive Take a look at last years and 2013s PDR presentation Nick DiNino GL Pewer Jordan Frank Safety Aloysius Posillico FS Zach Helwig VGt Vehicle Gomputertnierface Daniel Zakzewski Understand the safetieep designed in 2043 V Daniel Zakzewski Gemptetehierarchicat subsystent breakdown Daniel Zakzewski Werk Break down Structure WBS V Nick DiNino GL Pewer Jordan Frank Safety Aloysius Posillico F V Zach Helwig VGH Vehicle Gomputertnterface Daniel Zakzewski Formatting inte a Gantt Ghart Y Daniel Zakzewski Management Sehedute Daniel Zakzewski Requirements anatysis traceability matrix Y Nick DiNino GL Pewer Jordan Frank Safety Aloysius Posillico FS Zach Helwig VGH Yehicle Gompttertinterface Daniel Zakzewski Finatlayeut Daniel Zakzewski Pretiminary tayeut https app asana com 0 search 26404012932039 26404012932039 due Feb 7 due Feb 7 due Feb 7 due Feb 7 2 6 2 8 2015 e Search Asana V Daniel Zakzewski Acceptancetest strategy due Feb 7 V Nick DiNino Gt Pewer Jordan Frank Safety Aloysius Posillico St Zach Helwig VGH Vehicle Gomputertnterface Daniel Zakzewski Summear andFermatting Daniel Zakzewski Set Up Att Deeument templates due Feb 7
4. Status Letter Week 3 2 8 15 LFEV Team Milestones VSCADA We plan to complete the user manual and finish individual research topics Start the purchase of the hardware DYNO We plan to prepare AEC 401 for the Dyno use Completed the motor controller research and begin the draft for the user manual TSV We plan to complete the users manual correct many of the outstanding errors from the previous year s design and create a usable BoM to plan purchases GLV We plan to complete the users manual correct many of the outstanding errors from the previous year s design and create a usable BoM to plan purchases Ongoing Tasks Teams will update the acceptance test plan maintenance plan Interface control document calibration and accuracy document and conduct Individual research Outstanding Action items Final a website that meets the long term website requirement Sam and Steve Mazich Budget John will meet with teams and discuss the results of the PDR budget No purchases have been made yet 2 8 2015 e Search Asana Tasks due within the last 8 days Adam Cornwell V Adam Cornwell SystenStateAnatysis Prepesat Alex Hytha V Alex Hytha See deliverable D004 for requirements V identify systentobjectives V Stephen Mazich Vyrte serserstest pier Y John Bloore Wrie eststarndtest pian V Brendan Malone Write interfacetest plan V Nate Hand Write pewer supply test plan V Alex Hytha Vrrte safe
5. d Accuracy draft by adding more detail This includes use case calculations and arguments for sufficiently accurate Alex Hytha Acceptance Test Plan Draft due Feb 14 Work on converting the ATP outline into the ATP draft by added more detail to the document Aloysius Posillico Aloysius Posillico GLV TSI User Manual due Feb 12 Ben Ben Design battery cell restraint due Feb 12 Bikram Shrestha Bikram Shrestha Control Panels Drawings small due Feb 10 Bikram Shrestha Research Database systems due Feb 11 Bikram Shrestha maintenance plan Elaboration due Feb 13 Brendan Malone Brendan Malone Power Supply Research due Feb 14 Learn everything there is to know about the power supply Work with John in setting up AEC 401 in terms of limitations and safety concerns of the power supply Create a document that the group can use as a cheat sheet List important spec and safety concerns as well as anything else that could be useful ata glance Brendan Malone Connector Research due Feb 14 Learn how the power supply connects to the motor controller Find a connector that is compliant with the motor controller and with TSV TSI Create a document outlining your findings Make an argument for your decision of connector type Daniel Zakzewski Daniel Zakzewski Compile User Manual due Feb 12 Hansen Liang Hansen Liang Design retaining mechanism for pack due Feb 15 https app asana com 0 search 26404012932033 256978298 10482 1 4 2 8 2015
6. e Feb 11 Yiming Chen Functions and Controls due Feb 12 John Gehrig User Troubleshooting due Feb 12 Rameel Sethi Calibration due Feb 13 Bikram Shrestha maintenance plan Elaboration due Feb 13 Yiming Chen Functions and Controls due Feb 12 https app asana com 0 search 26404012932033 256978298 10482 3 4 2 8 2015 e Search Research languages IDEs to use Asana Zach Helwig Zach Helwig GLV VCI User Manual due Feb 12 Unassigned Cost welding battery case due Feb 12 Is welding a feasible option for the battery case cost and strength wise check if there is overlap with PDR due Feb 10 D002 Users Manual due Feb 16 A users manual per GPRO01 shall be provided This should be a high level document that contains an annotated drawing of the physical system annotated screen shots of all user interface screens annotated drawings of any physical control panels indicator buttons power switches and other controls The users manual must include a simplified block diagram explains all operational procedures and techniques needed to operate the system is a safe and effective manner including getting started FAQ detailed explanations of all functions and controls and user level troubleshooting calibration and maintenance D015 Draft Project Interface Control Document due Feb 13 A project level Interface Control Document ICD is required This document shall be produced by the collaborative effort of all the design teams b
7. e Search Research languages IDEs to use Asana Hansen Liang Acceptance test plan draft due Feb 15 Jaejoon Yang Jaejoon Yang Create BoM for needed materials due Feb 15 Jaejoon Yang Contact Formula competition about window in pack due Feb 15 John Bloore John Bloore Prepare AEC 401 due Feb 14 Prepare the room for testing by rearranging and removing unnecessary components Ask yourself Is the room ready for testing Document your progress A visual representation of the room would do nicely John Bloore MSC Development due Feb 14 Propose a plan for housing connecting and testing the motor control system This should including where every component goes where the wires run etc Be sure to document your decisions such that anyone would be able to set up the room John Gehrig John Gehrig User Troubleshooting due Feb 12 John Gehrig Hardware Interface control spec due Feb 13 Jordan Blake Jordan Blake Redesign charging structure due Feb 15 Jordan Blake Calibration and Accuracy report draft due Feb 15 Jordan Frank Jordan Frank GLV Safety Loop User Manual due Feb 12 Kai Ottaway Kai Ottaway Design BMS Restraints due Feb 12 Katie Nellis Katie Nellis Correct BoB board errata due Feb 15 Katie Nellis User s manual due Feb 15 Nate Hand Nate Hand Motor Controller Research due Feb 14 Learn and document everything you can about the motor Begin building a document that outlines how to basic operations with the c
8. ontroller in a simple to follow manor This will get added to the user manual soon Nick DiNino Nick DiNino GLV Power User Manual due Feb 12 https app asana com 0 search 26404012932033 256978298 10482 2 4 2 8 2015 e Search Research languages IDEs to use Asana Rameel Sethi Rameel Sethi Research wireless communication systems due Feb 10 Rameel Sethi Calibration due Feb 13 Rameel Sethi Software Interface Screenshot due Feb 12 Rameel Sethi expand ATP from outline due Feb 12 Sam Sam Research sensors protocols already on the system and possible additions due Feb 11 Work with other team and focus on protocols check if there is overlap with PDR due Feb 10 Sam FAQ due Feb 12 Sam Block Diagram due Feb 10 Stephen Mazich Stephen Mazich ICD Draft due Feb 14 Begin a more detailed version of the Interface control document Add as much detail as possible Work together with the other groups to add as much as possible Stephen Mazich Safety Plan Draft due Feb 14 Draft the Safety Plan required to begin testing the Dynamometer and associated systems in AEC 401 William Stathis William Stathis Correct AMS board errata and bugs due Feb 15 William Stathis Hash out communication interface with SCADA due Feb 15 Yiming Chen Yiming Chen Unit Testing Research Good Coding Practices due Feb 10 Submit a documentation upon this research Yiming Chen Operation Procedures due Feb 12 Sam FAQ due Feb 12 Adam Cornwell Getting Started du
9. se transitions between states This analysis must describe exactly where system state information is maintained in hardware and or software what the state information consists of and how the information required for state transitions is communicated among different locations V Nate Hand rite pewer supply test ptan due Feb 2 Nick DiNino V Nick DiNino G Power PBR due Feb 7 Cost Analysis Risk Assessment Requirements Checklist Preliminary Test Plan Nick DiNino System StateAnatysis due Feb 7 Nick DiNino GL Pewer Jordan Frank Safety Aloysius Posillico St V Zach Helwig VGH Vehicle Gomputertnterface Daniel Zakzewski FiratbLayeut Y Nick DiNino Remeveteep Gentreter fron meunt due Feb 7 V Nick DiNino Find experimentatvatre for Amperage threugh AR due Feb 7 Rameel Sethi V Rameel Sethi Aceeptanecetest Plan Outre due Feb 5 j i i A due Feb 4 Sam V Sam Safety Risk Assessment due Feb 5 https app asana com 0 search 26404012932039 26404012932039 4 6 2 8 2015 e Search Asana due Feb 5 due Feb 3 due Feb 4 due Feb 5 due Feb 5 due Feb 2 Stephen Mazich Y Stephen Mazich Greate PDR sresentation due Feb 6 See deliverable D000 for requirements V Alex Hytha Fest Plar Stides Y Stephen Mazich Subsysterns Sides Brendan Malone Requirement Analysis Slides V Nate Hand Syster StateSiides John Bloore RiskAssessment Sides John Bloore Gest Anatysis Slides Y Stephen Mazich Fask
10. tytest pten V Alex Hytha Deeumentationfortittest pian Alex Hytha Decumentation forfutHest plan V Alex Hytha Vyrte safety test pten Aloysius Posillico Aloysius Posillico GLY FS PBR Cost Analysis Risk Assessment Requirements Checklist Preliminary Test Plan Ben V Ben Examine prototype fer rute comptianee V Ben Deeide side vs reartmix battery placement Bikram Shrestha Bikram Shrestha Subsystem Hierarchical Breakdown Z Devel hiah level byeldad Brendan Malone https app asana com 0 search 26404012932039 26404012932039 due Feb 4 due Feb 4 due Feb 2 due Feb 2 due Feb 2 due Feb 2 due Feb 2 due Feb 3 due Feb 3 due Feb 2 due Feb 7 due Feb 8 due Feb 8 due Feb 5 due Feb 3 due Feb 4 due Feb 4 due Feb 5 1 6 2 8 2015 e Search Asana Y Brendan Malone due Feb 4 A requirements analysis traceability matrix showing that the design addresses all requirements and constraints The traceability matrix shall allocate every top level requirement to a functional requirement or interface in at least one subsystem and every subsystem shall have each of its functions and interfaces related to at least one top level requirement V Brendan Malone Write interfacetest plan Chris Melgar Y Chris Melgar ME SafetyPian Daniel Zakzewski V Daniel Zakzewski GL pertion Calibration Accuracy Deebbbbbbb V Daniel Zakzewski PBR Repert Compilation and formatting Y Daniel Zakzewski GLY
11. ut a specific individual or task team shall be entirely responsible for the accuracy of the ICD This document shall accurately and completely define all electrical mechanical and semantic aspects of top level interfaces including cables and connectors functional states and processes wireless interfaces communications protocols software APIs mechanical mounting interfaces limits keep outs boundaries and any other relevant fact about the system that needs to be coordinated between different designers D011 Draft Calibration and Accuracy due Feb 13 Any data acquisition system design or test plan must be accompanied by a Calibration and Error Analysis document that estimates the uncertainties associated with all system measurands This document must include both analytical estimates of measurement uncertainty as well as a justified design of acceptance tests to determine the uncertainty achieved in practice The testing design from this document shall be incorporated into the system ATP D004 Draft Acceptance Test Plan due Feb 13 The Acceptance Test Plan ATP is a document that describes how the system as a whole will be tested and demonstrated so as to prove compliance with all requirements and specifications The ATP should include forms that can be filled out by testers during execution These filled out forms will be used to create the ATR GLV TSV SCADA DYNO https app asana com 0 search 26404012932033 256978298 10482 4 4
Download Pdf Manuals
Related Search