Our IT infrastructure is also an important aspect of our conceptual design process since we are working in a distributed manner. As the design progresses we are developing spreadsheets for each subsystem. For the generation of our the system level budgets (e.g. mass, power, etc) we are using the J-CDS Concurrent Design Platform Platform to link together the relevant outputs from our subsystem spreadsheets together
The first step in our design process was to define the overall scope of the conceptual design study. The aim was to define the principal assumptions that will drive the detailed design of the subsystems.
Next the main design options for each subsystem were identified, in preparation for more detailed analysis of the various options.
That's about as far as we've got so far. The next step which is due to kick off this week will be to start the design, looping through the subsystems – starting with the issues that most drive the design - trajectory analysis, propulsion, lander and rover architectures, etc.
Right from the beginning we realized that this would need a big team. Projects with unpaid team members are never easy, and landing a rover on the moon and sending back high quality video and photography is probably one of the most challenging volunteer projects ever attempted!
The first order of business was to tackle the IP issues. How can a distributed team of unpaid people be confident that they will get whatever rewards they are looking for from participation in such a project? Well, it wasn't easy but through lots of discussions we finally converged on a way to keep people motivated.
Also, early on we recognized the challenges with the information system. We investigated some different options but we eventually settled on using a wiki framework for keeping track of general discussions and an https secure web folders for our detailed documentation and larger files. We are continuously evaluating other options however, and we may later switch to other solutions or add new elements to our information system. Google Sites (http://sites.google.com) looks interesting and we are just starting to see if it will meet out needs.