The zip file that you submit for the competition should be created with a standard Windows zipping utility, and it must contain all the files necessary to run your parametric or Custom Member on a standard installation of SDS/2. At a minimum, the zip file must include the required file(s) to run the project, and a file called readme.txt that instructs the customer on how to use the parametric or Custom Member.

The readme.txt file must contain any instructions that the user needs to run a parametric successfully, or to install and run a Custom Member. This should be a very clear, concise set of steps to walk the user through using the project. Put yourself in the shoes of someone who has just downloaded this; perhaps it is the first time they have used a parametric or Custom Member, and try to explain to them how they would use it.

If your entry is a parametric and contains other files that need to be relocated or modified, this needs to be made explicitly clear to the user in the readme.txt file. The user should not have any reason to contact the author to simply run the parametric or Custom Member. Be sure that you include every file that your project needs to run successfully, as well as clear, concise, well-written instructions for the user on what to do with the extra files, if anything.

If, as mentioned above, special instructions are needed prior to running your parametric or Custom Member, consider breaking your readme.txt file into two sections. One of these sections would contain the basic running instructions, and the second section would contain instructions for installation and file preparation.

If your zip file does not contain all the files necessary to run your project, it may be disqualified from the competition. Design Data may try to contact you regarding the missing information or missing files, but we are not required to do so, as this may not be feasible based on the number of submissions.