...

In order to enable good collaboration CAD must be clean and useable for all parties. Compliance with the standard is required for submitting CAD to the Rocket Team SVNGitHub.

• Shall - A mandatory requirement
• May - Permissible. Can also represent a suggested implementation where other valid solutions exist.

...

If you're only here for a minute, read this before commiting to SVN!GitHub!

• You need GitHub desktop installed, and a GitHub enterprise account though MIT.
• Clone the repository onto your computer if you haven't already. You should only need to do this once.
• Before making changes, pull changes.
• Make changes by modifying the files in the GitHub directory
• Update the SVN before starting your modification. Right click and use SVN to lock the file or folder you are modifying.
• Make your changes.
• Check the highest level assembly in your project. Ensure it opens without any errors and that no mates are broken.
• Ensure your part has a material and appearance.
• Ensure your part is named and located somewhere that other people can make a good guess at what you were trying to do
• Update your SVN immediately prior to committing
• .
• On GitHub desktop verify Verify you are committing the files (and only the files) you mean to.
• Add a commit message to the SVN that says what you did.
• Commit.
• Push. You can verify your commit by visiting this site. Ensure you release your edit lockpush by checking the GitHub repository online.

COTS Part File Naming

COTS parts shall be named X (Title) where X is the manufacturer assigned part number. Title shall be a descriptive word or phrase, being the commonly used name of the part. If the part is modified by the Rocket Team such that it is no longer equivalent to a part received new (i.e. a new part cannot be flown without modification). It shall receive a proprietary part name. Maintenance and repairs do not require a proprietary part name.

...

AS is an assembly code representing large upper level assemblies. Every AS code shall have it's own folder. Every AS code shall have an assembly file AS000 (Major Assembly Name). Examples of assembly codes are shown below.

Assembly codes shall not be reused within a project. Assembly Codes may be reused between projects, particularly to indicate similarity of function, design heritage, or commonality.

...

Drawings shall be fully constrained and dimensioned. Where possible they shall inherit dimensions from other sketches and parts. When multiple features are being defined from the same plane they shall all be in a single sketch.

2D sketches are highly preferred over 3D sketches. A 3D sketch may be substituted for a 2D sketch where the geometry cannot be defined by a 2D sketch, such as a helix or complex loft.

Parts

Parts shall be dimensioned as they are to be constructed. Tolerances for fit and function shall be modeled. Internal threads may be modeled with Solidworks cosmetic threads feature or modeled explicitly (as required by digital manufacturing). External threads shall be explicitly modeled.

...

The team prefers even numbered UNC fasteners through #10 thread. Exceptions should be considered on a case by case basis. Fasteners should have a corrosion treatment, either plating or black oxide.  

Solidworks Toolbox

Solidworks toolbox components shall not be used on flight parts. In order to generate an accurate bill of materials, a part number that can be referenced to a manufacturer should be used. Example: you are creating the assembly for the motor case and adding in the bolts. You know you need a UNC 1/4-20 5/8 cap head bolt. You may not insert it from the solidworks toolbox. You may download the file from McMaster-Carr and add it to the assembly that way.