fswiki.us - User contributions [en]

Brake Rotors

2026-05-06T14:52:01Z

Emilyanthony: /* Materials */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon%
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Lightening==
[[File:Fig.-3.png|right|middle|thumb| Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system

==Venting==
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

Analysis and simulation of rotors in a Formula SAE vehicle was described in Matthew Heffernan's paper at Auburn University.<ref>Heffernan, M., "Analyzing and Simulating Brake Rotor Temperatures: A Technique Applied to a Formula SAE Vehicle," SAE Technical Paper 2006-01-1974, 2006, https://doi.org/10.4271/2006-01-1974</ref>

<references />

Brake Rotors

2026-05-06T14:51:45Z

Emilyanthony: /* Lightening */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon%
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.Post-Processing

==Lightening==[[File:Fig.-3.png|right|middle|thumb| Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system

==Venting==
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

Analysis and simulation of rotors in a Formula SAE vehicle was described in Matthew Heffernan's paper at Auburn University.<ref>Heffernan, M., "Analyzing and Simulating Brake Rotor Temperatures: A Technique Applied to a Formula SAE Vehicle," SAE Technical Paper 2006-01-1974, 2006, https://doi.org/10.4271/2006-01-1974</ref>

<references />

Brake Rotors

2026-05-06T14:49:55Z

Emilyanthony: negotiating with wiki formatting is the seventh circle of hell

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon%
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.Post-Processing

==Lightening==
<a><img alt="" src="/images/thumb/b/b2/Fig.-3.png/300px-Fig.-3.png" decoding="async" width="300" height="174" class="thumbimage" srcset="/images/thumb/b/b2/Fig.-3.png/450px-Fig.-3.png 1.5x, /images/thumb/b/b2/Fig.-3.png/600px-Fig.-3.png 2x"></a> <a class="internal" title="Enlarge"></a>Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.

A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system

==Venting==
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

Analysis and simulation of rotors in a Formula SAE vehicle was described in Matthew Heffernan's paper at Auburn University.<ref>Heffernan, M., "Analyzing and Simulating Brake Rotor Temperatures: A Technique Applied to a Formula SAE Vehicle," SAE Technical Paper 2006-01-1974, 2006, https://doi.org/10.4271/2006-01-1974</ref>

<references />

Brake Rotors

2026-05-06T14:46:17Z

Emilyanthony: Undo revision 3164 by Emilyanthony (talk)

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.Post-Processing

===Lightening===
<a><img alt="" src="/images/thumb/b/b2/Fig.-3.png/300px-Fig.-3.png" decoding="async" width="300" height="174" class="thumbimage" srcset="/images/thumb/b/b2/Fig.-3.png/450px-Fig.-3.png 1.5x, /images/thumb/b/b2/Fig.-3.png/600px-Fig.-3.png 2x"></a> <a class="internal" title="Enlarge"></a>Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:

* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
VentingVented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref>

<a>[1]</a>
# <a>↑</a> Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. <a rel="nofollow" class="external free">https://doi.org/10.25439/rmt.27580428</a>
In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

Analysis and simulation of rotors in a Formula SAE vehicle was described in Matthew Heffernan's paper at Auburn University.<ref>Heffernan, M., "Analyzing and Simulating Brake Rotor Temperatures: A Technique Applied to a Formula SAE Vehicle," SAE Technical Paper 2006-01-1974, 2006, https://doi.org/10.4271/2006-01-1974</ref>
<references />

Brake Rotors

2026-05-06T14:45:19Z

Emilyanthony: Reverted edits by Emilyanthony (talk) to last revision by HeifetzJunkie

Brake Rotors

2026-05-06T14:44:16Z

Emilyanthony:

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.Post-Processing

===Lightening===
<a><img alt="" src="/images/thumb/b/b2/Fig.-3.png/300px-Fig.-3.png" decoding="async" width="300" height="174" class="thumbimage" srcset="/images/thumb/b/b2/Fig.-3.png/450px-Fig.-3.png 1.5x, /images/thumb/b/b2/Fig.-3.png/600px-Fig.-3.png 2x"></a> <a class="internal" title="Enlarge"></a>Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:

* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
VentingVented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref>

<a>[1]</a>
# <a>↑</a> Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. <a rel="nofollow" class="external free">https://doi.org/10.25439/rmt.27580428</a>
In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

Analysis and simulation of rotors in a Formula SAE vehicle was described in Matthew Heffernan's paper at Auburn University.<ref>Heffernan, M., "Analyzing and Simulating Brake Rotor Temperatures: A Technique Applied to a Formula SAE Vehicle," SAE Technical Paper 2006-01-1974, 2006, https://doi.org/10.4271/2006-01-1974</ref>
<references />

Brake Rotors

2026-05-06T14:24:31Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening===
[[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|sub|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
Venting

Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:24:14Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening=== [[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|sub|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
Venting

Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:23:53Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance: [[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|sub|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
Venting

Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:22:46Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening[[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|sub|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
Venting

Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:21:27Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening[[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|middle|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
Venting

Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:19:20Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
[[File:Fig.-3.png|link=https://jefflange.ca/2020/12/formula-sae-brake-rotor-design-report/|right|middle|thumb|Rotor dimple pattern on UA-21 rotor design, dotted lines represent dimples on opposite side of rotor.]]

===Venting===
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

File:Fig.-3.png

2026-05-06T14:19:00Z

Emilyanthony:

Rotor dimple pattern on student-designed rotor

Brake Rotors

2026-05-06T14:17:52Z

Emilyanthony: /* Post-Processing */

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system

===Venting===
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

<references />

Brake Rotors

2026-05-06T14:17:01Z

Emilyanthony:

[[Category:Brakes]]

Brake rotors, or just rotors, are the discs that rotate with the wheel and provide a surface for the brake pads to apply friction to. They can be made using a wide variety of materials and manufacturing methods depending on the system they are used in, mostly dependent on the brake pad material.
==Materials==
The selection of material is highly dependent on the engineer's design goals for rotor operating temperature, pad-rotor coefficient of friction, material strength and other properties.Rotors can be constructed using the following materials:
* Steels of low to high carbon% 
* Chromoly (4130 Steel) or other alloys
* Cast Iron
* Aluminum Alloys
* Carbon ceramic
Typically pad-rotor coefficients of friction and ideal pairings will be specified by the brake pad manufacturer, but this can also be physically tested and verified in-house by teams who have the resources to do so.

==Post-Processing==
===Lightening===
A common practice is the drilling of holes or slots into or all the way through the rotor. This practice has several effects on brake performance:
* Decreasing the area of contact between the pad and rotor, thus impeding the flow of heat into the rotor but also venting heat off the pad
* Adds a shaving effect to keep the pad surface clean
* Increases rotor temperatures through reduction of thermal mass
* Decreases rotational inertia of system
A common misconception among designers is that doing this increases cooling effects on the brake rotor by increasing it's surface area. While drilling holes in the rotor does increase surface area, unless there is some form of air actively being guided through those holes either by brake/wheel ducts or winglets, there is no significant airflow through the holes of the rotor. Conversely, vented brake discs which are common in larger vehicles, have improved cooling as the vane design is orthogonal to the axis of rotation, not parallel, and is significantly influenced by airflow within the wheel. A study by Arthur Stephens at RMIT showed that cooling of a disc brake was improved by using an alloy wheel with a large open area.In heating tests (during braking), the initial rate of heating is a function of the thermal storage capacity of the rotor, and it was found that the thermal performance of a solid and an equivalent-sized vented rotor was similar.<ref>Stephens, Arthur (2010). Aerodynamic cooling of automotive disc brakes. RMIT University. Thesis. https://doi.org/10.25439/rmt.27580428</ref> In cooling, the vented rotor cooled faster than the solid rotor. Students seeking to improve cooling of the rotor should evaluate their designs using similar methods to the linked paper and consider airflow into the wheel well.

===Venting===
Vented rotors are rotors with fins in between either contact surface that allow air to pass inside the rotor itself. The way air travels through the rotor is dependent on the configuration of the fins inside.

<references />

List of FS/FSAE Competition Records

2026-05-06T13:53:55Z

Emilyanthony: /* Combustion records */

Everything on this page is unofficial, so take it with a grain of salt. Please no edit wars.

A lot of the info on this page was taken from [https://docs.google.com/spreadsheets/d/12ioLo9yaQqad_OI_cilvSQqqRn0w3QVdseJFznmz6xU/edit?usp=sharing this spreadsheet].
==Combustion records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|27 
|Rennteam Uni Stuttgart
|
|
|-
|Most overall wins in one legal year
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins with one car
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins in a row
|7
|Global Formula Racing
|
|
|-
|Highest score in one legal year
|4449
|Rennteam Uni Stuttgart
|2016
|
|-
|Highest score with one car
|4429
|Rennteam Uni Stuttgart
|2016 (2017 Michigan)
|
|-
|Highest score in one competition
|987.441
|Università degli Studi di Modena e Reggio Emilia
|Formula ATA 2025
|[https://www.formula-ata.it/wp-content/uploads/2025/09/Overall Class1CV_0914_h2000.pdf]
|-
|Highest score in one competition's static events
|320
|Raftar Formula Racing
|Formula Bharat 2020
|[https://www.formulabharat.com/wp-content/uploads/2020/02/Results_CV_Overall_FormulaBharat2020-2.pdf]
|-
|Highest score in one competition's dynamic events
|672.05
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Lowest skidpad time
|4.65 s
|TU Graz Racing
|FS Austria 2018
|[https://fsaustria.at/wp-content/uploads/C-Skidpad-Times-2018.pdf] 
|-
|Lowest acceleration time
|3.606 s
|Joanneum Racing Graz
|FS East (Hungary) 2019
|[https://fseast.eu/wp-content/uploads/2019/07/FS_EAST_2019_Final_Results_CV.pdf]
|-
|Lightest car at competition
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Lightest car at competition running in dynamic events
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Heaviest car at competition
|416.5 kg/918 lbs
|UAS Groningen
|FSUK 2011
|[https://www.flickr.com/photos/hanzeracingdivision/6240263216/in/dateposted/]
|-
|Heaviest car at competition running in dynamic events
|388 kg/855 lbs
|UPT Racing Team
|FS Hungary 2017
|
|}

==Electric records==

{| class="wikitable"
|-
!Record description
!Record
!Team
!When & where
!Proof
|-
|Most overall wins
|12
|AMZ
|
|
|-
|Most overall wins in one legal year
|4
|TUfast Munich
|2019
|
|-
|Most overall wins with one car
|4
|TUfast Munich
|2019
|
|-
|Most overall wins in a row
|5
|Unicamp E-Racing, TUfast Munich
|FSAE Brasil 2012, 2013, 2014, FSAE Electric 2013, 2014 
FSAE-A 2018, FSeast 2019, FSA 2019, FSG 2019, FSS 2019
|[http://students.sae.org/cds/formulaseries/results/] [http://portal.saebrasil.org.br/programas-estudantis/formula-sae-brasil/resultados]
|-
|Highest score in one legal year
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score with one car
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score in one competition
|985.4
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Highest score in one competition's static events
|317
|TU Delft
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|675
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Lowest skidpad time
|4.136 s
|TU Graz Racing Team
|FS East 2024
|[https://fseast.eu/wp-content/uploads/2024/08/Skidpad-Manual-1.2.pdf]
|-
|Lowest acceleration time
|2.999 s
|Formula Student Team Delft
|FS East 2023
|[https://fseast.eu/wp-content/uploads/2023/08/FS-East-2023-EV-results_1.2.pdf]
|-
|Lightest car at competition
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Lightest car at competition running in dynamic events
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Heaviest car at competition
|483.5 kg/1066 lbs
|Univ. of North Carolina - Asheville
|FSAE Electric 2023
|[https://www.sae.org/binaries/content/assets/cm/content/attend/student-events/results/formula-sae/fsae_ev_2023_results.pdf]
|-
|Heaviest car at competition running in dynamic events
|479 kg/1056 lbs
|Landshut UAS
|FS Germany
|[https://www.formulastudent.de/fileadmin/_migrated/content_uploads/2011_FSE_Competition_Results_Engineering_Design.pdf]
|}

==Driverless records==

{| class="wikitable"
|-
!Record description
!Record
!Team
!When & where
!Proof
|-
|Most overall wins
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Most overall wins in one legal year
|2
|AMZ
|2018
|
|-
|Most overall wins with one car
|2
|AMZ
|2018
|
|-
|Most overall wins in a row
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Highest score in one legal year
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score with one car
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's static events
|477.07
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|496
|AMZ
|FS Germany 2017
|[https://www.formulastudent.de/fsg/results/2017/]
|-
|Lowest skidpad time
|5.136 s
|Karlsruhe KIT
|FS Germany 2021
|[https://www.formulastudent.de/fsg/results/2021/]
|-
|Lowest acceleration time
|3.597 s
|AMZ
|FS Germany 2019
|[https://www.formulastudent.de/fsg/results/2019/]
|-
|Lightest car at competition
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Lightest car at competition running in dynamic events
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition
|286 kg/631 lbs
|Napoli UNINA
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition running in dynamic events
|281.5 kg/621 lbs
|Darmstadt TU
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|}
[[Category:Competition]]

Fswiki

2026-05-06T13:51:01Z

Emilyanthony:

=Welcome to FS Wiki, the only (un)official Formula SAE/Student wiki.=
<categorytree mode="pages" showcount="on">Vehicle</categorytree>

<categorytree mode="pages" showcount="on">Team</categorytree>

<categorytree mode="pages" showcount="on">Competition</categorytree>

<categorytree mode="pages" showcount="on">Engineering_Materials</categorytree>

<categorytree mode="pages" showcount="on">FSWiki</categorytree>

Please report bugs at[[User_Talk:emilyanthony]].

All pages: [[Special:AllPages]]

=Index =
===Getting Started===
New here? Go to the [[Getting Started]] page for a comprehensive FAQ and how to use this wiki.

We are constantly updating this wiki and adding extensions to improve quality of life. The current list of extensions is below along with their help pages. Follow those pages to learn about these extensions. Please submit a request to [[User:emilyanthony]] to add to this list or to report bugs.

{| class="wikitable collapsible sortable" style="width: 1788px;" data-mce-style="width: 1788px;"
|-
! style="width: 208px;" data-mce-style="width: 208px;"|Name
! style="width: 326px;" data-mce-style="width: 326px;"|Function
! style="width: 524px;" data-mce-style="width: 524px;"|Link
! style="width: 228px;" data-mce-style="width: 228px;"|Status
! style="width: 75.4px;" data-mce-style="width: 75.4px;"|Priority
! style="width: 348.6px;" data-mce-style="width: 348.6px;"|Notes
|-
| style="width: 208px;" data-mce-style="width: 208px;"|EmbedVideo
| style="width: 326px;" data-mce-style="width: 326px;"|youtube/vimeo etc support
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:EmbedVideo
| style="width: 228px;" data-mce-style="width: 228px;"| Installed 
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Medium
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|PreLoader
| style="width: 326px;" data-mce-style="width: 326px;"|preloaded formatting for new pages
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:Preloader
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|High
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|no templates created yet
|-
| style="width: 208px;" data-mce-style="width: 208px;"|LiquidThreads
| style="width: 326px;" data-mce-style="width: 326px;"|Threading and reply functions in talk tab
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:LiquidThreads
| style="width: 228px;" data-mce-style="width: 228px;"| Installed, working with quirks
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Medium
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|weird loading symbol won't go away
|-
| style="width: 208px;" data-mce-style="width: 208px;"|TinyMCE
| style="width: 326px;" data-mce-style="width: 326px;"|Rich text editor, click "Edit Source" to use
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:TinyMCE
| style="width: 228px;" data-mce-style="width: 228px;"| Installed 
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|High
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|ContactPage
| style="width: 326px;" data-mce-style="width: 326px;"|Contact forms for site visitors
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:ContactPage
| style="width: 228px;" data-mce-style="width: 228px;"|Not Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|PDFEmbed
| style="width: 326px;" data-mce-style="width: 326px;"|Embed PDFs
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:PDFEmbed
| style="width: 228px;" data-mce-style="width: 228px;"|Not Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|[[mediawikiwiki:Extension:PDFHandler]] exists for now
|-
| style="width: 208px;" data-mce-style="width: 208px;"|CategoryTree
| style="width: 326px;" data-mce-style="width: 326px;"|Visual representation of Wiki categories
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:CategoryTree
| style="width: 228px;" data-mce-style="width: 228px;"| Installed 
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|AntiSpam
| style="width: 326px;" data-mce-style="width: 326px;"|Antispam provided by cleantalk.org
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:Antispam
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|High
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|User Rights Email Notification
| style="width: 326px;" data-mce-style="width: 326px;"|emails user when group has been changed
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:User_Rights_Email_Notification
| style="width: 228px;" data-mce-style="width: 228px;"|Not Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|Translate
| style="width: 326px;" data-mce-style="width: 326px;"|translate mediawiki text
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:Translate
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|High
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|Echo
| style="width: 326px;" data-mce-style="width: 326px;"|Provides an in-wiki notification system that can be used by other extensions.
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:Echo
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|
|-
| style="width: 208px;" data-mce-style="width: 208px;"|Cite
| style="width: 326px;" data-mce-style="width: 326px;"|citations
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Help:Cite
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
| style="width: 348.6px;" data-mce-style="width: 348.6px;"|use <code><nowiki><ref>Citation info here</ref></nowiki></code> to place citation within the article body and <code><nowiki><references /></nowiki></code> at the bottom of the page to list all citations.
|-
| style="width: 208px;" data-mce-style="width: 208px;"|Math
| style="width: 326px;" data-mce-style="width: 326px;"|create math figures/equations like this: <math>\sqrt{1-e^2}</math>
| style="width: 524px;" data-mce-style="width: 524px;"|https://www.mediawiki.org/wiki/Extension:Math
| style="width: 228px;" data-mce-style="width: 228px;"|Installed
| style="width: 75.4px;" data-mce-style="width: 75.4px;"|Low
|See [[wikipedia:Help:Displaying a formula]] for syntax
|}

===Navigating the Wiki===
====Categories====
Wiki pages are divided into categories. Contributors are asked to specify categories for content. Do not place articles in the top category only; be as specific as possible.
Multiple categories may be assigned to an article. For example:
The article [[Ergonomics]] shall be listed under Category:Vehicle but not Category:Team. [[Steering Wheel]] could be listed under both Category:Vehicle, Category:Ergonomics, and Category:Electronics. The Engineering Materials category is for subjects that are not subsystem specific but engineering related such as fasteners, materials pages, simulation tutorials, etc. The FSWiki category should be reserved for master pages and pages that are far too general to get placed under Team, Competition, or Vehicle. The use of the FSWiki category tag should be actively discouraged.

The syntax for listing categories at the end of an article is:
<code><nowiki>[[Category:Name]]</nowiki></code>. This syntax may be used to create new categories. Check that the category exists prior to creating a new one. Mediawiki isn't smart enough to pick up on similar categories ("electronic" vs "electronics", for example) and this will create clutter if it is not maintained. Category names are '''CASE SENSITIVE'''. "Electronics" is not the same as "electronics". Type carefully.

The root categories for FS wiki are as follows:
<code><nowiki>[[Category:Vehicle]] [[Category:Team]] [[Category:Competition]] [[Category:Engineering_Materials]] [[Category:FSWiki]]</nowiki></code>
==Disclaimer==
This site is built and maintained by Formula SAE/Formula Student students and alumni. The owners, creators, and contributors at this site claim no official affiliation with [[Wikipedia:SAE International]], [[Wikipedia:iMechE]], Formula Student Germany GmbH, or any other official sanctioning body of the Formula SAE or Formula Student competitions. The site exists only to enable knowledge transfer and the design process, not to replace it. This site is not an official source of information regarding rules, deadlines, or competition communications.

The FS wiki is an online, open-content, collaborative encyclopedia; that is, a voluntary association of individuals and groups working to develop a common resource of knowledge in the FS competitions. The structure of this project allows anyone with an Internet connection and a user profile to alter its content. Please be advised that nothing found here has necessarily been reviewed by people with the expertise required to provide you with complete, accurate or reliable information.

Any of the trademarks, service marks, collective marks, design rights or similar rights that are mentioned, used or cited in the articles of the FS wiki are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these articles under the CC-BY-SA and GFDL licensing schemes. Unless otherwise stated, this site and any wiki site are neither endorsed by nor affiliated with any of the holders of any such rights and as such FSwiki cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.
=Site Sponsorship and Funding=
The FSWiki is sponsored by the Pittsburgh Shootout. It costs us $279 for hosting and domain fees every March to keep the wiki up. Interested in supporting the wiki? Follow the Stripe link down below to toss us $5 to keep the site up.

https://buy.stripe.com/00g9Dr5VB9Z26Na002

[[Category:FSWiki]]

Start a Shootout

2026-05-05T19:13:18Z

Emilyanthony: /* Technical Inspection */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities

Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS
An example of a proposal created by the Pittsburgh Shootout is located [https://drive.google.com/file/d/1NIbJ-gRaHJ8CiJdWc-NJP-xzySbELU8c/view here].
=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/support-us/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2025 Pittsburgh Shootout fielded 60 volunteers for 32 teams for the autocross.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started the night before the Autocross to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
<brclear=all />
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event. K&K Insurance does provide event insurance for Motorsports events and their information can be found [https://www.kandkinsurance.com/programs/motorsports-insurance here].

The Pittsburgh Shootout acquires the following insurance coverage:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.

Insurance costs can be >$1500 per day.

'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2026-05-05T19:13:02Z

Emilyanthony: /* Volunteers */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities

Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS
An example of a proposal created by the Pittsburgh Shootout is located [https://drive.google.com/file/d/1NIbJ-gRaHJ8CiJdWc-NJP-xzySbELU8c/view here].
=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/support-us/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2025 Pittsburgh Shootout fielded 60 volunteers for 32 teams for the autocross.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started the night before the Autocross to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
<brclear=all />
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/</ref>
<brclear=all />

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event. K&K Insurance does provide event insurance for Motorsports events and their information can be found [https://www.kandkinsurance.com/programs/motorsports-insurance here].

The Pittsburgh Shootout acquires the following insurance coverage:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.

Insurance costs can be >$1500 per day.

'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2026-05-05T19:11:31Z

Emilyanthony:

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities

Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS
An example of a proposal created by the Pittsburgh Shootout is located [https://drive.google.com/file/d/1NIbJ-gRaHJ8CiJdWc-NJP-xzySbELU8c/view here].
=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/support-us/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2025 Pittsburgh Shootout fielded 60 volunteers for 32 teams for the autocross.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
<brclear=all />
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/</ref>
<brclear=all />
=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event. K&K Insurance does provide event insurance for Motorsports events and their information can be found [https://www.kandkinsurance.com/programs/motorsports-insurance here].

The Pittsburgh Shootout acquires the following insurance coverage:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.

Insurance costs can be >$1500 per day.

'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

List of FS/FSAE Competition Records

2026-05-05T19:04:39Z

Emilyanthony: Undo revision 3146 by Emilyanthony (talk)

Everything on this page is unofficial, so take it with a grain of salt. Please no edit wars.

A lot of the info on this page was taken from [https://docs.google.com/spreadsheets/d/12ioLo9yaQqad_OI_cilvSQqqRn0w3QVdseJFznmz6xU/edit?usp=sharing this spreadsheet].
==Combustion records==

{| class="wikitable"
|-
!Record description
!Record
!Team
!When & where
!Proof
|-
|Most overall wins
|27 
|Rennteam Uni Stuttgart
|
|
|-
|Most overall wins in one legal year
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins with one car
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins in a row
|7
|Global Formula Racing
|
|
|-
|Highest score in one legal year
|4449
|Rennteam Uni Stuttgart
|2016
|
|-
|Highest score with one car
|4429
|Rennteam Uni Stuttgart
|2016 (2017 Michigan)
|
|-
|Highest score in one competition
|980.15
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Highest score in one competition's static events
|320
|Raftar Formula Racing
|Formula Bharat 2020
|[https://www.formulabharat.com/wp-content/uploads/2020/02/Results_CV_Overall_FormulaBharat2020-2.pdf]
|-
|Highest score in one competition's dynamic events
|672.05
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Lowest skidpad time
|4.65 s
|TU Graz Racing
|FS Austria 2018
|[https://fsaustria.at/wp-content/uploads/C-Skidpad-Times-2018.pdf] 
|-
|Lowest acceleration time
|3.606 s
|Joanneum Racing Graz
|FS East (Hungary) 2019
|[https://fseast.eu/wp-content/uploads/2019/07/FS_EAST_2019_Final_Results_CV.pdf]
|-
|Lightest car at competition
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Lightest car at competition running in dynamic events
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Heaviest car at competition
|416.5 kg/918 lbs
|UAS Groningen
|FSUK 2011
|[https://www.flickr.com/photos/hanzeracingdivision/6240263216/in/dateposted/]
|-
|Heaviest car at competition running in dynamic events
|388 kg/855 lbs
|UPT Racing Team
|FS Hungary 2017
|
|}

==Electric records==

{| class="wikitable"
|-
!Record description
!Record
!Team
!When & where
!Proof
|-
|Most overall wins
|12
|AMZ
|
|
|-
|Most overall wins in one legal year
|4
|TUfast Munich
|2019
|
|-
|Most overall wins with one car
|4
|TUfast Munich
|2019
|
|-
|Most overall wins in a row
|5
|Unicamp E-Racing, TUfast Munich
|FSAE Brasil 2012, 2013, 2014, FSAE Electric 2013, 2014 
FSAE-A 2018, FSeast 2019, FSA 2019, FSG 2019, FSS 2019
|[http://students.sae.org/cds/formulaseries/results/] [http://portal.saebrasil.org.br/programas-estudantis/formula-sae-brasil/resultados]
|-
|Highest score in one legal year
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score with one car
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score in one competition
|985.4
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Highest score in one competition's static events
|317
|TU Delft
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|675
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Lowest skidpad time
|4.136 s
|TU Graz Racing Team
|FS East 2024
|[https://fseast.eu/wp-content/uploads/2024/08/Skidpad-Manual-1.2.pdf]
|-
|Lowest acceleration time
|2.999 s
|Formula Student Team Delft
|FS East 2023
|[https://fseast.eu/wp-content/uploads/2023/08/FS-East-2023-EV-results_1.2.pdf]
|-
|Lightest car at competition
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Lightest car at competition running in dynamic events
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Heaviest car at competition
|483.5 kg/1066 lbs
|Univ. of North Carolina - Asheville
|FSAE Electric 2023
|[https://www.sae.org/binaries/content/assets/cm/content/attend/student-events/results/formula-sae/fsae_ev_2023_results.pdf]
|-
|Heaviest car at competition running in dynamic events
|479 kg/1056 lbs
|Landshut UAS
|FS Germany
|[https://www.formulastudent.de/fileadmin/_migrated/content_uploads/2011_FSE_Competition_Results_Engineering_Design.pdf]
|}

==Driverless records==

{| class="wikitable"
|-
!Record description
!Record
!Team
!When & where
!Proof
|-
|Most overall wins
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Most overall wins in one legal year
|2
|AMZ
|2018
|
|-
|Most overall wins with one car
|2
|AMZ
|2018
|
|-
|Most overall wins in a row
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Highest score in one legal year
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score with one car
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's static events
|477.07
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|496
|AMZ
|FS Germany 2017
|[https://www.formulastudent.de/fsg/results/2017/]
|-
|Lowest skidpad time
|5.136 s
|Karlsruhe KIT
|FS Germany 2021
|[https://www.formulastudent.de/fsg/results/2021/]
|-
|Lowest acceleration time
|3.597 s
|AMZ
|FS Germany 2019
|[https://www.formulastudent.de/fsg/results/2019/]
|-
|Lightest car at competition
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Lightest car at competition running in dynamic events
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition
|286 kg/631 lbs
|Napoli UNINA
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition running in dynamic events
|281.5 kg/621 lbs
|Darmstadt TU
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|}
[[Category:Competition]]

List of FS/FSAE Competition Records

2026-05-05T17:30:02Z

Emilyanthony: /* Electric records */

Everything on this page is unofficial, so take it with a grain of salt. Please no edit wars.

A lot of the info on this page was taken from [https://docs.google.com/spreadsheets/d/12ioLo9yaQqad_OI_cilvSQqqRn0w3QVdseJFznmz6xU/edit?usp=sharing this spreadsheet].
==Combustion records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|27 
|Rennteam Uni Stuttgart
|
|
|-
|Most overall wins in one legal year
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins with one car
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins in a row
|7
|Global Formula Racing
|
|
|-
|Highest score in one legal year
|4449
|Rennteam Uni Stuttgart
|2016
|
|-
|Highest score with one car
|4429
|Rennteam Uni Stuttgart
|2016 (2017 Michigan)
|
|-
|Highest score in one competition
|980.15
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Highest score in one competition's static events
|320
|Raftar Formula Racing
|Formula Bharat 2020
|[https://www.formulabharat.com/wp-content/uploads/2020/02/Results_CV_Overall_FormulaBharat2020-2.pdf]
|-
|Highest score in one competition's dynamic events
|672.05
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Lowest skidpad time
|4.65 s
|TU Graz Racing
|FS Austria 2018
|[https://fsaustria.at/wp-content/uploads/C-Skidpad-Times-2018.pdf] 
|-
|Lowest acceleration time
|3.606 s
|Joanneum Racing Graz
|FS East (Hungary) 2019
|[https://fseast.eu/wp-content/uploads/2019/07/FS_EAST_2019_Final_Results_CV.pdf]
|-
|Lightest car at competition
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Lightest car at competition running in dynamic events
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Heaviest car at competition
|416.5 kg/918 lbs
|UAS Groningen
|FSUK 2011
|[https://www.flickr.com/photos/hanzeracingdivision/6240263216/in/dateposted/]
|-
|Heaviest car at competition running in dynamic events
|388 kg/855 lbs
|UPT Racing Team
|FS Hungary 2017
|
|}

==Electric records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|12
|AMZ
|
|
|-
|Most overall wins in one legal year
|4
|TUfast Munich
|2019
|
|-
|Most overall wins with one car
|4
|TUfast Munich
|2019
|
|-
|Most overall wins in a row
|5
|Unicamp E-Racing, TUfast Munich
|FSAE Brasil 2012, 2013, 2014, FSAE Electric 2013, 2014<br\ />
FSAE-A 2018, FSeast 2019, FSA 2019, FSG 2019, FSS 2019
|[http://students.sae.org/cds/formulaseries/results/] [http://portal.saebrasil.org.br/programas-estudantis/formula-sae-brasil/resultados]
|-
|Highest score in one legal year
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score with one car
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score in one competition
|985.4
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Highest score in one competition's static events
|317
|TU Delft
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|675
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Lowest skidpad time
|4.136 s
|TU Graz Racing Team
|FS East 2024
|[https://fseast.eu/wp-content/uploads/2024/08/Skidpad-Manual-1.2.pdf]
|-
|Lowest acceleration time
|2.999 s
|Formula Student Team Delft
|FS East 2023
|[https://fseast.eu/wp-content/uploads/2023/08/FS-East-2023-EV-results_1.2.pdf]
|-
|Lightest car at competition
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Lightest car at competition running in dynamic events
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Heaviest car at competition
|483.5 kg/1066 lbs
|Univ. of North Carolina - Asheville
|FSAE Electric 2023
|[https://www.sae.org/binaries/content/assets/cm/content/attend/student-events/results/formula-sae/fsae_ev_2023_results.pdf]
|-
|Heaviest car at competition running in dynamic events
|479 kg/1056 lbs
|Landshut UAS
|FS Germany
|[https://www.formulastudent.de/fileadmin/_migrated/content_uploads/2011_FSE_Competition_Results_Engineering_Design.pdf]
|}

==Driverless records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Most overall wins in one legal year
|2
|AMZ
|2018
|
|-
|Most overall wins with one car
|2
|AMZ
|2018
|
|-
|Most overall wins in a row
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Highest score in one legal year
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score with one car
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's static events
|477.07
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|496
|AMZ
|FS Germany 2017
|[https://www.formulastudent.de/fsg/results/2017/]
|-
|Lowest skidpad time
|5.136 s
|Karlsruhe KIT
|FS Germany 2021
|[https://www.formulastudent.de/fsg/results/2021/]
|-
|Lowest acceleration time
|3.597 s
|AMZ
|FS Germany 2019
|[https://www.formulastudent.de/fsg/results/2019/]
|-
|Lightest car at competition
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Lightest car at competition running in dynamic events
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition
|483 kg/1066 lbs
|UNC Asheville
|FSAE Electric 2023
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition running in dynamic events
|281.5 kg/621 lbs
|Darmstadt TU
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|}
[[Category:Competition]]

List of FS/FSAE Competition Records

2026-05-05T17:24:01Z

Emilyanthony: update heaviest car stat

Everything on this page is unofficial, so take it with a grain of salt. Please no edit wars.

A lot of the info on this page was taken from [https://docs.google.com/spreadsheets/d/12ioLo9yaQqad_OI_cilvSQqqRn0w3QVdseJFznmz6xU/edit?usp=sharing this spreadsheet].
==Combustion records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|27 
|Rennteam Uni Stuttgart
|
|
|-
|Most overall wins in one legal year
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins with one car
|4
|Global Formula Racing, Rennteam Uni Stuttgart
|2014/2017
|
|-
|Most overall wins in a row
|7
|Global Formula Racing
|
|
|-
|Highest score in one legal year
|4449
|Rennteam Uni Stuttgart
|2016
|
|-
|Highest score with one car
|4429
|Rennteam Uni Stuttgart
|2016 (2017 Michigan)
|
|-
|Highest score in one competition
|980.15
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Highest score in one competition's static events
|320
|Raftar Formula Racing
|Formula Bharat 2020
|[https://www.formulabharat.com/wp-content/uploads/2020/02/Results_CV_Overall_FormulaBharat2020-2.pdf]
|-
|Highest score in one competition's dynamic events
|672.05
|Rennteam Uni Stuttgart
|FS Spain 2015
|
|-
|Lowest skidpad time
|4.65 s
|TU Graz Racing
|FS Austria 2018
|[https://fsaustria.at/wp-content/uploads/C-Skidpad-Times-2018.pdf] 
|-
|Lowest acceleration time
|3.606 s
|Joanneum Racing Graz
|FS East (Hungary) 2019
|[https://fseast.eu/wp-content/uploads/2019/07/FS_EAST_2019_Final_Results_CV.pdf]
|-
|Lightest car at competition
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Lightest car at competition running in dynamic events
|123 kg/271 lbs
|Berkeley
|FSAE Lincoln 2014
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ln_2014_result.pdf]
|-
|Heaviest car at competition
|416.5 kg/918 lbs
|UAS Groningen
|FSUK 2011
|[https://www.flickr.com/photos/hanzeracingdivision/6240263216/in/dateposted/]
|-
|Heaviest car at competition running in dynamic events
|388 kg/855 lbs
|UPT Racing Team
|FS Hungary 2017
|
|}

==Electric records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|12
|AMZ
|
|
|-
|Most overall wins in one legal year
|4
|TUfast Munich
|2019
|
|-
|Most overall wins with one car
|4
|TUfast Munich
|2019
|
|-
|Most overall wins in a row
|5
|Unicamp E-Racing, TUfast Munich
|FSAE Brasil 2012, 2013, 2014, FSAE Electric 2013, 2014<br\ />
FSAE-A 2018, FSeast 2019, FSA 2019, FSG 2019, FSS 2019
|[http://students.sae.org/cds/formulaseries/results/] [http://portal.saebrasil.org.br/programas-estudantis/formula-sae-brasil/resultados]
|-
|Highest score in one legal year
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score with one car
|3740.94
|TUfast Munich
|2019
|
|-
|Highest score in one competition
|985.4
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Highest score in one competition's static events
|317
|TU Delft
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|675
|Unicamp E-Racing
|FSAE Electric 2013
|[https://www.sae.org/binaries/content/assets/cm/content/attend/2018/student-events/fsae/results/fsae_ev_2013_result.pdf]
|-
|Lowest skidpad time
|4.355 s
|TU Graz Racing Team
|FS Austria 2024
|[https://fsaustria.at/wp-content/uploads/E_Skidpad_Times_2024_v2.pdf]
|-
|Lowest acceleration time
|2.999 s
|Formula Student Team Delft
|FS East 2023
|[https://fseast.eu/wp-content/uploads/2023/08/FS-East-2023-EV-results_1.2.pdf]
|-
|Lightest car at competition
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Lightest car at competition running in dynamic events
|142.5 kg/314 lbs
|TU Wien
|FS Spain 2017
|
|-
|Heaviest car at competition
|483.5 kg/1066 lbs
|Univ. of North Carolina - Asheville
|FSAE Electric 2023
|[https://www.sae.org/binaries/content/assets/cm/content/attend/student-events/results/formula-sae/fsae_ev_2023_results.pdf]
|-
|Heaviest car at competition running in dynamic events
|479 kg/1056 lbs
|Landshut UAS
|FS Germany
|[https://www.formulastudent.de/fileadmin/_migrated/content_uploads/2011_FSE_Competition_Results_Engineering_Design.pdf]
|}

==Driverless records==

{| class="wikitable"
|-
!|Record description
!|Record
!|Team
!|When & where
!|Proof
|-
|Most overall wins
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Most overall wins in one legal year
|2
|AMZ
|2018
|
|-
|Most overall wins with one car
|2
|AMZ
|2018
|
|-
|Most overall wins in a row
|3
|AMZ
|FSG 2017, 2018 FSAE Italy 2018 
|
|-
|Highest score in one legal year
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score with one car
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition
|959.57
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's static events
|477.07
|AMZ
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|-
|Highest score in one competition's dynamic events
|496
|AMZ
|FS Germany 2017
|[https://www.formulastudent.de/fsg/results/2017/]
|-
|Lowest skidpad time
|5.136 s
|Karlsruhe KIT
|FS Germany 2021
|[https://www.formulastudent.de/fsg/results/2021/]
|-
|Lowest acceleration time
|3.597 s
|AMZ
|FS Germany 2019
|[https://www.formulastudent.de/fsg/results/2019/]
|-
|Lightest car at competition
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Lightest car at competition running in dynamic events
|156 kg/344 lbs
|München TU
|FS Germany 2022
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition
|483 kg/1066 lbs
|UNC Asheville
|FSAE Electric 2023
|[https://www.formulastudent.de/fsg/results/2022/]
|-
|Heaviest car at competition running in dynamic events
|281.5 kg/621 lbs
|Darmstadt TU
|FS Germany 2018
|[https://www.formulastudent.de/fsg/results/2018/]
|}
[[Category:Competition]]

Tube Frame

2024-08-11T17:33:19Z

Emilyanthony: fix weird spacing issues

[[Category:Chassis]]
A tube frame or space frame is a chassis constructed from rigid truss members attached in a three-dimensional structure with the body panels having little or no structural function. Stiffness is maximized by triangulating the tubing to ensure that the tubes are not loaded in bending.

==Required Reading==

These 5 papers teach you more than the wiki ever could.

* Riley, W. and George, A., "Design, Analysis and Testing of a Formula SAE Car Chassis," SAE Technical Paper 2002-01-3300, 2002, https://doi.org/10.4271/2002-01-3300.
* Auer, B., McCombs, J., and Odom, E., "Design and Optimization of a Formula SAE® Frame," SAE Technical Paper 2006-01-1009, 2006, https://doi.org/10.4271/2006-01-1009.
* P Baskara Sethupathi et al 2018 IOP Conf. Ser.: Mater. Sci. Eng. 402 012184, https://iopscience.iop.org/article/10.1088/1757-899X/402/1/012184/pdf.
* Chassis Design: Principles and Analysis Milliken 0768008263.
* Dodd, C. et al, "MEEG 402-010 Chassis Design Report". 2017 https://udel.edu/~pgeneva/downloads/fsae/2017_FSAE_chassis.pdf. ("The Delaware Paper")

==Design Considerations for Systems Integration==
Designing the tube frame is a compromise between structural rigidity, weight, and manufacturing complexity while complying to the rules. One thing to remember is that the frame is basically a glorified bracket. From a systems perspective, the frame designer is primarily concerned with packaging the other vehicle components. In approximate order of importance:
# Ergonomics
# Suspension
# Powertrain/drivetrain
# Aerodynamic devices and bodywork
# Electrical

===Driver Accommodation and CAD basics in SolidWorks===
Start the frame CAD with a "driver sketch", so that the driver dimensions and margins of safety past the rules will set the dimensions of the entire frame. A driver sketch can look like this:

[[File:Image159.png|center|middle|thumb|Driver Sketch ]]

with a separate sketch building up the Side view frame around it:

[[File:Image80.png|center|middle|thumb|Driver Sketch and Side View Frame ]]

The frame CAD is best set up with the help of both 2D and 3D sketches, and then with the use of "[https://help.solidworks.com/2021/English/SolidWorks/sldworks/c Weldments_Overview.htm Weldments]" - basically pre-configured sweep features, that are generated on top of the sketches (the sketch being the neutral axis of the tube). It makes things quite easy to make, and to export later - SolidWorks generates a "cut list": a BOM of tubes.

Teams may be required to create or import [https://help.solidworks.com/2020/English/SolidWorks/sldworks/t Weldments_Creating_a_Custom_Profile.htm custom weldment profiles].

As part of smart CAD practice, it is best to have a "master sketch" (or a few in this case due to the complexity) such that the entire frame design is controlled at the top of the part tree, and so that you don't have to go to 10 different features just to make one change. Learn to work with [https://help.solidworks.com/2019/english/SolidWorks/sldworks/t inserting_reference_dimensions.htm driven dimensions], and construction geometry. 3D sketches are computationally difficult, so you may occasionally see weird bugs with things going over defined even though they shouldn't. To mitigate this, reduce the number of dimensions and sketch lines per 3D sketch.

====Example Layout====

* Driver Sketch (2D)
* Side View frame (2D)
* Bulkhead (2D, generally)
* Front Hoop (2D or 3D sketch on a plane)
* Main Hoop (3D sketch on a plane)
* Front tubes (3D)
* Middle tubes (3D)
* Rear tubes (3D)
* Suspension (2D and 3D)

[[File:Image167.png|center|middle|thumb|Front Tubes, with bulkhead and FRH visible]] <a class="internal" title="Enlarge"></a>Front Tubes, with bulkhead and FRH visibleIn-context relations deliver the suspension geometry to the a-arms, bellcranks, uprights, etc. That way, all adjustments to the geometry can be done in the frame file, and the changes would be up dated on assembly rebuild.[[File:Image107.png|center|middle|thumb|Suspension Integration into Frame file]]

==Triangulation ==
Proper triangulation makes sure that the tubes are not loaded in bending. Full triangulation is probably impossible given that the driver like, can't have a frame member through their torso, but please try?

Note that because some tubes will inevitably take bending (primarily the side impact structure, due to impossible triangulation from the big empty space the driver occupies), there should be emphasis on reducing tube aspect ratio (by either upping diameter or reducing length), and adding gussets.
==Tube Choice==
===Alloys===
[[Steel#1000 Series|10XX steel]]

is cheap, easy to weld, readily available, and easy to machine.

[[Steel#4000 Series|41XX steel]] is more expensive but stronger, more difficult to weld and machine (prone to cracking, heat treat might be required).

====Method====
ERW, DOM

==Manufacturing==
===Outsourcing===
Many teams in North America use "[https://vr3.ca/ VR3 Engineering]

" to produce their tube set.They will bend and cope tubes for the team in the $3000-5000 range for frame and suspension, depending on complexity and shipping. VR3 has strict requirements on documentation sent to their sales engineers and is detailed on their website at<a href="https://vr3.ca/request-a-quote/">https://vr3.ca/request-a-quote/.</a>

===In-house Fabrication===
====Cutting tubes====
Cutting tubes to intersect each other is called coping or notching. Tubes can be notched by hand typically using a hole saw notcher, bench grinder, or die grinder. This process is very time consuming and meticulous. Tubes can also be profiled using a water jet or laser cutter.
====Tube bending====
Manual Bending

CNC Bending

===Fixtures===
Fixtures (also known as jigs) indicate the location of tubes within the frame. Fixtures can be made of many materials. Fixtures should start measurement from a [https://en.wikipedia.org/wiki/Datum_reference datum]
. From the datum, important tubes should next be fixtured (suspension points, roll hoops, etc...).

(Fixture gallery?)

===Welding===
{{Main|Welding}}

: Tubes should be cleaned before welding. Joints should have minimal gaps, otherwise welding will be difficult. Tubes must be welded around the entire circumference<ref>FSAE Rules. https://fsaeonline.com/cdsweb/gen/DocumentResources.aspx</ref>.
==Analysis==
Goal:[[File:Image152.png|right|middle|thumb|Torsional stiffness FEA in SolidWorks]]

* To test torsional rigidity, camber (lateral) rigidity, and perhaps also toe rigidity
* To stiffen frame where needed, and change up layouts
* To make sure it doesn't break, or is too close to low FOS where welds may crack
* Frequency analysis perhaps? 

Problem:
* Solid body FEA with a triangle mesh is too time consuming, for a 50+ tube frame. IF you have to, export small sections and do a small contained study (outlined below)
* There's a quicker method - beam FEA. It makes a mesh of “pie cuts” of tubes. Way less mesh data, but very good accuracy still - a whole frame sim can run in ~30sec, on a laptop.
* It does not capture tab interfaces etc, but it does capture member stresses.
* Cannot do an assembly simulation in it, but can simulate pivot “joints”

===Torsional FEA (Beam sim) Workflow (SolidWorks):===

# Put in a mock “[[Engine|engine]]” as just a bunch of tubes, triangulated to be stiff.
# Put in mock a-arms (lower arms only, upper aren't needed unless doing camber stiffness) and pushrods
# Modify the appropriate joints to “hinges” (by right clicking on a member in the cut list folder in the tree, and clicking "edit definition")
# Apply “immovable (allowing rotation) fixtures to 3 wheel, apply 100lb upwards to the 4th.
# Bellcrank can be done but its complex computationally and my best way was to treat as direct actuation (getting decently accurate), and then performing a separate exported section get simulated with an assembly simulation - with the actual bellcrank, tabs etc. Then just add up the two deflections.
# [[File:image75.png|right|middle|thumb|FEA setup ]]Run, then view results! to understand if it makes sense, animate it - with the stress view.

Beam FEA Notes:
* Beam FEA doesn't like short members. If you have a short member, ask yourself if it can be “combined” (i.e combine operation) with another. An example is suspension tabs. In our case, they will be combined with the arm tubes.
* Beam FEA also doesn't like arcs - sharper bent tubes (making arcs that are fairly long, like 3inch plus) as nodes should be avoided, as I've had a bunch of weird bugs in FEA where the SIM node of the RRH being an arc just randomly detached
* Beam FEA works with “nodes” that it automatically computes. You can get it to manually compute, based on custom set distances - this helps eliminate (filter out) 2 super close together nodes. But keep in mind, every time you re-compute the nodes, your fixtures may change - since their referenced node will change number.
[[File:image41.png|right|middle|thumb|Configuring Hinge Joints]]

===Solid-Body Frame FEA (SolidWorks)===
Its not computationally realistic to do a solid body simulation for the entire frame. As such, I recommend exporting a section of interest, and analyzing it separately. For example, the bellcrank mounting, or a-arm tabs. In the case of the bellcrank, you'd be best to include the actual bellcrank as well and perform an assembly simulation. You never know how much it will contribute!

How to export a section? Start from having a fully merged body that includes the tubes/tabs of interest. The extruded tabs have to properly intersect the tube for merging to work. You can use the "combine" feature (just search for it in the command search box) to combine all the bodies together. Once done, right click the body, and click "insert into new part".

Proceed with solid body FEA - NOT beam FEA. Meshing is sometimes tricky, so the addition of fillets as well as mesh control (mesh per part size) helps auto refine the mesh in the sharp edges and prevent the meshing from failing.

Multi-Element Airfoils

2024-05-30T22:06:40Z

Emilyanthony:

==Parameterization for optimization==

When optimizing a multiple degree-of-freedom system like the positioning of elements in a multi-element airfoil, it can be important to have a smartly chosen set of independent variables. For example, if you change the height of only the 2nd element in a 3-element airfoil, you'll likely hurt the overall performance (due to choking a slot gap) even if the optimum position has the 2nd element placed higher - for example, if the entire multi-element airfoil should be moved higher. This method isn't impossible to optimize, just very inefficient to do so. Instead of defining the element locations globally, defining them relative to each other lets us use meaningful independent variables like slot gap and slot overlap. For adjusting angles of attack, I prefer to define the angle for each element individually. When defining angles relative to each other, increasing the angle of the 1st element will rotate the entire multi-element airfoil. While specifying the relative angles can speed up the initial optimization, it isn't efficient for fine-tuning, which is where most of ones time is spent.

Below is how to set up this parameterization:

Given elements i = 1 to N, import them all into your software of choice, whether you're optimizing them in CFD, or recreating the final design in CAD. All elements must start with their leading edge on the coordinate system origin, and with zero angle of attack.

First, pick an element to act as the 'anchor' for the multi-element airfoil. Your anchor element will define the one point that you have global control over, usually for something like placing the leading or trailing edge near a bounding box in the regulations.

Given the variables

* Global anchor position, <math>x_{anchor}</math> and <math>z_{anchor}</math>

* Element angle of attack, <math>\alpha_i</math>

* Element cord, <math>c_i</math>

* Slot gap height and overlap, <math>h_i</math> and <math>l_i</math> (Be aware that this will not be the true slot gap due to element thickness)

* Element pivot position, <math>x_{pivot,i}</math> and <math>z_{pivot,i}</math> (This is eyeballed as the location on an element that is closest to the trailing edge of the preceding element, which allows us to adjust element angles without altering the true slot gap in the process) Now to position the multi-element airfoil, starting from the back:

For each element downstream of the anchor element, starting at the back (elements j = N to <math>i_{anchor}</math>+1):

1. Rotate elements (N to j) by <math>(\alpha_j-\alpha_{j-1}</math>) about <math>(x_{anchor,j}, 0, z_{anchor,j})</math>

2. Translate elements (N to j) by <math>(c_{j-1} - l_j, 0, h_j)</math>

Now, for each element upstream of the anchor element, starting at the front (elements k = 1 to <math>i_{anchor}</math>-1):

1. Translate elements (1 to k) by <math>(l_{k+1}-c_k, 0, -h_{k+1})</math>

2. Rotate elements (1 to k) by <math>(\alpha_k-\alpha_{k+1})</math> about <math>(x_{anchor,k+1}, 0, z_{anchor,k+1})</math>

Finally, for the entire multi-element airfoil:

1. Translate the multi-element airfoil such that the anchor point is at the origin

2. Rotate the multi-element airfoil by <math>\alpha_{anchor}</math>

3. Translate the multi-element airfoil by <math>(x_{anchor}, 0, z_{anchor})</math> into its final position

[[File:1.mp4|left|middle|thumb|Example of anchoring by the front element]]

[[File:Rear Anchor.mp4|left|middle|thumb|Example of anchoring by the rear element]]

[[Category:Body_and_Aero]]

Lidar

2024-05-30T21:59:07Z

Emilyanthony: add category

[[Category:Autonomous_System]]

For the Evaluation of technical spezifikation of Lidar systems you can use the Lidardatabase. You can find further information under [//lidarlist.com lidarlist]

Epoxy

2024-05-30T21:58:20Z

Emilyanthony:

[[Category:Materials]]

<!-- NOTE: This should be a FORMULA SAE / FORMULA STUDENT *SPECIFIC* page, this is not wikipedia>
<!-- Proposed Outline:

Brief intro
=Use in composites=
==Cure time==
==Use methods, advice==
==Safety==
===exothermic reaction===
===Skin Irritation===
=Non-composite Uses=
=References=
>

Sandwich Panel

2024-05-30T21:57:18Z

Emilyanthony:

[[Category:Materials]]

Panel (generally composite) that is made of core middle sandwiched between sheets of material. Structural composites on the car are almost always of this construction type.

Wikipedia articles for further reading:
* https://en.wikipedia.org/wiki/Sandwich-structured_composite
* https://en.wikipedia.org/wiki/Sandwich_theory

<!-- maybe add some references to more academic references>

Steering Wheel

2024-05-30T21:56:38Z

Emilyanthony:

<!-- Proposed Outline:

brief intro
=rules=
=common construction methods=
=DAQ display / Electronics=
=References=
>
Rules
common construction methods
DAQ display / Electronics

[[Category:Ergonomics]]

Steering Wheel

2024-05-30T21:56:19Z

Emilyanthony:

<!-- Proposed Outline:

brief intro
=rules=
=common construction methods=
=DAQ display / Electronics=
=References=
>
=Rules=
=common construction methods=
=DAQ display / Electronics=

[[Category: Ergonomics]]

Steering Wheel

2024-05-30T21:55:48Z

Emilyanthony:

<!-- Proposed Outline:

brief intro
=rules=
=common construction methods=
=DAQ display / Electronics=
=References=
>
=rules=
=common construction methods=
=DAQ display / Electronics=

[[Category:Ergonomics]]

Torque Steer

2024-05-30T21:54:30Z

Emilyanthony: add categories

'''Torque Steer''' is a yawing effect caused by unequal stiffness [[Drivetrain#Driveshafts|driveshafts]], most frequently due to unequal length. A stiffer shaft will turn the wheel further than a softer shaft for the same input torque. Despite it's relevance to the discussion of torque steer, the calculation shown here is only an example and should not be copied for use in the design event. There are many points not covered here, and the assumptions are not justified.

=Example Calculation=

Using ballpark values, we can calculate an approximate torque steer value for a generalized FSAE car.

'''Step 1: Polar Moment of Inertia'''

The moment of inertia (J) for a hollow shaft is calculated as follows:
:π/32 * (D4-d4)

Using values from an RCV axle below, we can find J.

{| class="wikitable"
| Shaft OD (D) || 0.8"
|-
| Shaft ID (d) || 0.5"
|}

Shaft Area of Inertia: 0.034076in2

'''Step 2: Calculate Torsional Stiffness'''

We will use 4130 chromoly [[Steel|steel]] as our half-shaft material. Most steels have a very similar shear modulus (G) so this choice is not a driving factor in the result. The torsional stiffness (k) of the shaft will be found using the following formula and values:
:k = G*J / L

{| class="wikitable"
| Shaft Material || 4130 Steel
|-
| 4130 Shear Modulus || 1.16e+7 psi
|-
| Left Shaft Length (LL) || 15 in
|-
| Right Shaft Length (LR) || 19 in
|}

Left Torsional Stiffness (kL): 38.3379023 lb-ft / degree

Right Torsional Stiffness (kR): 30.26401 lb-ft / degree

'''Step 3: Find Torque'''

Our last input value that we need to find is the torque experienced by the driveshafts. This is the torque output by the motor and transmitted through the final drive ratio. The maximum torque applied to the driveshafts by the engine will be during launch, when the wheels are still and we can assume a perfect launch by the driver, applying the maximal engine torque for the split second we are examining.

Max Torque from Engine: 40 lb-ft

Final Drive Ratio: 3.55

Torque Seen by Driveshaft: 142 lb-ft

'''Step 4: Find Shaft Twist'''

This step is the meat of the calculation. We can find how far each shaft has twisted using our previous results according to the equation below:
:φ = T / k

Left Shaft Twist (φL): 3.704 degrees

Right Shaft Twist (φR): 4.692 degrees

It is important to note that shaft twist indicates how far each wheel has not rotated compared to the engine.

'''Step 5: Find Vehicle Yaw'''

If both shafts were perfectly stiff, one rotation of the driven sprocket would equal one rotation of the wheels, driving the car forward the distance equal to 2 * π * the tire's dynamic radius. Because the shafts twist, the wheels/tires will move less than one full rotation. Because the shafts have different stiffnesses, they will travel different distances under the same load. We will find the distance not rotated to compute vehicle yaw, as we are looking for magnitude, not direction.

: Tire travel (T) = φshaft/360 * Tire Circumference

: Yaw = sin-1(Tmax-Tmin / Track Width)

Circumference of Tire: 56.52 in

Left Tire Travel: 0.582 in

Right Tire Travel: 0.737 in

Rear Track: 36 in

Yaw: 0.247 degrees

'''Result'''

According to our calculations, the vehicle will yaw less than one quarter of one degree, which if even perceptible by the driver will be unlikely to force corrective action. please see further below for discussion of assumptions used and real world relevance.

==Assumptions==
The following assumptions were used in the example calculation:
* The rear wheels are the driven wheels
* The engine can output a constant torque
* The tire will not break traction with the ground
* The loading of the shaft is quasi-static
* The rear suspension (particularly toe) is infinitely stiff
* The tire contact patch is considered to be a point
* The tire's rolling radius does not change under loading
* Tire circumference is equivalent to 2 * dynamic radius * π
* Shaft hardening does not impact stiffness

[[Category:Vehicle_Dynamics]] [[Category:Drivetrain]]

Team Collaboration

2024-05-24T14:32:01Z

Emilyanthony: /* Altium 365 */

[[Category:Team]]
FSAE is a large process: a lot of parts, a lot of money, a lot of time, and possibly a lot of people. Most companies have to deal with this issue too, so there are quite a few solutions out there to help you organize the team. Solutions that work for one team may not work for another due to differences in how the team is structured.

==Collaboration During Covid-19==
If your team is allowed to work remotely during the pandemic- Weekly worknights and worknight meetings are even more important. Get everyone in on a video call weekly to check in progress. Voice channels on Discord can provide a drop-in casual chat outside meetings replacement for working together in a physical shop, house, or computer lab. Having a central CAD repository/PDM system becomes even more important when working remotely. If your team didn't have one before, it's much more important now.
===Covid-19 Team Collaboration Checklist===

* Weekly worknights (online)
* Weekly meetings (video calls)
* [[Team Collaboration#Collaboration Software|Collaboration Software]]
** Bonus: Open Voice channels
* [[Team Collaboration#CAD|CAD Vault/PDM]]

==Worknights==
Having weekly worknights is key to getting team members to all focus on working on a car together. Starting the worknight with a team meeting is a great way to encourage everyone to show up on time, to have status updates, and to get everyone on the same page. Having everyone on the team see each other work together at the same time is very underrated as a motivational tool, to build trust, and have fun. Sharing the vehicle model with the entire team can help get everyone on the same page and show off the work everyone has been doing.
==Collaboration Software==
Many teams have started to use Slack, Microsoft Teams, discord, or other collaboration software. The benefit of the software over something private-only like facebook messenger is that team members are welcome to join, leave, and adjust notifications based on conversation topic and interest. Especially helpful for getting new members into the conversation.
===Slack===
Slack brought chat channels to the professional workplace.
====[https://slack.com/pricing Versions]====

{| class="wikitable"
|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|
=====Version=====

| style="width: 55.2px;" data-mce-style="width: 55.2px;"|
=====Cost (USD)=====

| style="width: 608px;" data-mce-style="width: 608px;"|
=====Features=====

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Free
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$0
| style="width: 608px;" data-mce-style="width: 608px;"|Access to 10,000 of your team’s most recent messages
10 integrations with other apps like Google Drive, Office 365 and many more
1:1 voice and video calls between teammates
5GB Storage per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Standard
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$8/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|The full context of your organization’s message history
Timely info and actions in one place with unlimited integration
Face-to-face communication with group voice and video calls of up to 15 teammates
Secure collaboration with outside organizations or guests from within Slack
10 GB per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Plus
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$15/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|Advanced identity management through SAML-based SSO and real-time Active Directory sync with OneLogin, Okta and Ping
Compliance requirements met with data exports for all messages
Around-the-clock teamwork and assistance with 99.99% guaranteed uptime and 24/7 support with a four-hour response time 20 GB per team member
|}
Slack offers [https://slack.com/help/articles/206646877-Slack-for-Education Slack for Education] for 85% off Standard or Plus paid plans.
===Microsoft Teams===
Microsoft Teams is the newest addition. The development team has added a lot of new features during 2018-2020, which has brought it up to par with the other platforms.

'''Pros:'''
* Free with Office 365 if your school has it.
'''Cons:'''
* Channels have excessive unnecessary vertical space compared to others, which makes it less like a conversation. However, if your team uses threads properly to create sub-conversations, then this issue goes away. 
* No voice channels - only meetings and calls

===[https://support.discord.com/hc/en-us/categories/200404378 Discord]===
There is a Formula Student general discord at[https://discord.gg/QNb6qX9 https://discord.gg/QNb6qX9]

Originally branded more towards gamers, discord is likely already popular with gamers on your team.
Discord is free to make a server, and students may subscribe to Discord Nitro or Nitro classic to get the perks below:
{| class="wikitable"
|- style="height: 69px;" data-mce-style="height: 69px;"
| style="width: 64.8px; height: 69px;" data-mce-style="width: 64.8px; height: 69px;"|
=====Version=====

| style="width: 55.2px; height: 69px;" data-mce-style="width: 55.2px; height: 69px;"|
=====Cost (USD)=====

| style="width: 608px; height: 69px;" data-mce-style="width: 608px; height: 69px;"|
=====Features=====

|-
| style="width: 64.8px; height: 136.163px;" data-mce-style="width: 64.8px; height: 136.163px;"|Free

| style="width: 55.2px; height: 136.163px;" data-mce-style="width: 55.2px; height: 136.163px;"|$0

| style="width: 608px; height: 136.163px;" data-mce-style="width: 608px; height: 136.163px;"|
* Unlimited message history
* Screen sharing
* Up to 8 users on a video call
* Up to 5000 users
* Unlimited Storage
* 8MB File upload limit

|-
| style="width: 64.8px; height: 365px;" data-mce-style="width: 64.8px; height: 365px;"|

[https://discord.fandom.com/wiki/Nitro Nitro Classic]

| style="width: 55.2px; height: 365px;" data-mce-style="width: 55.2px; height: 365px;"|

$4.99/mo
$49.99/year
per user

| style="width: 608px; height: 365px;" data-mce-style="width: 608px; height: 365px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 50mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro Classic, they are awarded one boost.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.

|-
| style="width: 64.8px; height: 347px;" data-mce-style="width: 64.8px; height: 347px;"|
Nitro
| style="width: 55.2px; height: 347px;" data-mce-style="width: 55.2px; height: 347px;"|
$9.99/mo$99.99/yrper user

| style="width: 608px; height: 347px;" data-mce-style="width: 608px; height: 347px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 100mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro, they are awarded two boosts.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.
|}

'''Pros:'''
* Free
* Your team probably already has some members that use it
* Has voice channels for casual drop-in conversation and impromptu discussions. You can easily see who else is working on the car at the moment, and hang out with them.
* Has [https://support.discord.com/hc/en-us/articles/360045093012-Server-Integrations-Page integrations] such as [https://www.integromat.com/en/integrations/discord/google-drive Integromat ]for filesharing
* Bot support
'''Cons:'''
* Gamers may need a second account on discord, so you can actually see team members names instead of gamertags, although this can be avoided with [https://support.discord.com/hc/en-us/articles/219070107-Server-Nicknames Server Nicknames] 
* No ability to save messages

==CAD==
Having a single source of truth for your CAD files is very important. Every team member should have access to the latest CAD of the entire vehicle.

===SolidWorks PDM===
'''Pros:'''
* Seamless integration into SolidWorks
* Requires users to lock out files to work on them to prevent conflicting versions and accidental changes.
'''Cons:'''
* Complicated IT system required

===3DEXPERIENCE===
'''Pros: '''
* Dassault is providing free access for students during covid-19.
'''Cons:'''
* You have to use 3DExperience
===Inventor Vault===
Available for teams who use AutoDesk Inventor as their primary CAD software.
===Google Drive / Dropbox===
Works for smaller teams. For larger teams with many simultaneous users, being able to lock out files during editing to prevent version conflicts becomes more important. Also, having one main computer (such as a shop computer) which always has an up to date full-vehicle assembly will help to spot issues.

'''Pros:'''
* Free
* Most teams are already comfortable with these platforms for document sharing.
'''Cons:'''
* No SolidWorks integration 
* No ability to lock out files
* File references can become problematic
===Network Drive===
Some universities will allow you to setup a network drive so that your CAD files are accessible from anywhere on campus. If you want to work from home, you first VPN into the campus network. Universities can even setup automatic backups so that if someone saves over someone's work, not much is lost. Can work well if you are vigilant about only saving the files you need to save.

'''Pros:'''
* Free, if your university allows it
* There is only ever one set of files, so no synchronization is required
'''Cons:'''
* Easy to accidentally save over other people's work if you're not careful
* No CAD integration
* No ability to lock out files
===Subversion (SVN)===
SVN is a version control system developed for software before git. While git is a distributed system, SVN has one central vault, which users can lock out files for editing. There are hosts for SVN servers, or you can create your own SVN server using software like SVNEdge. All the users would use software like tortoiseSVN to sync files.

'''Pros:'''
* Locking out files is optional.
'''Cons:'''
* No SolidWorks integration (yet).
* IT knowledge required to set up own server.

===Git and Github===
Git is primarily used for software development. It is built upon the ability for two people to simultaneously edit a text file, and then for git to be able to merge these two files. Because of this, users are not able to "lock" so only one user can edit at a time. Unfortunately because merging is not possible with CAD files, Git is a poor option for anything other than text files.

=ECAD (PCB Design)=
ECAD collaboration software is mostly redundant with the MCAD section, however ECAD doesn't integrate quite as well with typical CAD repositories, while also having some of it's own unique tools.

===Altium 365===
Available for teams who use Altium Designer as their primary ECAD software.
* Seemless integration with Altium Designer
* Allows non-ECAD users to view models in the workspace

Altium 365 integrates with MCAD through their MCAD Designer plugin. MCAD CoDesigner integrates with Solidworks, PTC Creo, Autodesk Inventor, Autodesk Fusion 360, and Siemens NX to merge 3D CAD data with PCB design.<ref>Altium MCAD CoDesigner.https://www.altium.com/solutions/by-technology/ecad-mcad</ref>

=Software Development=
===Git and Github===
Great for software - Git is the industry standard. Central repository for files. Easy to share. Revision control. Setting up a central, team controlled git repository can be difficult. Each new member to the team should be given access to every repository for the team. Otherwise repositories become silo'ed and knowledge can be lost by graduating team members' repositories not getting shared with the younger members.
===Subversion (SVN)===
Subversion is a central repository either on a hosted service or on a team member's home server. It allows for a central storage location for all files, where the team leads can add students to all files at once. See tortoiseSVN for users and SVNEdge for the server.

SVN is usually only used if pre-existing architecture demands it; Git is much more common nowadays.

Team Collaboration

2024-05-24T14:31:20Z

Emilyanthony: /* Altium 365 */

[[Category:Team]]
FSAE is a large process: a lot of parts, a lot of money, a lot of time, and possibly a lot of people. Most companies have to deal with this issue too, so there are quite a few solutions out there to help you organize the team. Solutions that work for one team may not work for another due to differences in how the team is structured.

==Collaboration During Covid-19==
If your team is allowed to work remotely during the pandemic- Weekly worknights and worknight meetings are even more important. Get everyone in on a video call weekly to check in progress. Voice channels on Discord can provide a drop-in casual chat outside meetings replacement for working together in a physical shop, house, or computer lab. Having a central CAD repository/PDM system becomes even more important when working remotely. If your team didn't have one before, it's much more important now.
===Covid-19 Team Collaboration Checklist===

* Weekly worknights (online)
* Weekly meetings (video calls)
* [[Team Collaboration#Collaboration Software|Collaboration Software]]
** Bonus: Open Voice channels
* [[Team Collaboration#CAD|CAD Vault/PDM]]

==Worknights==
Having weekly worknights is key to getting team members to all focus on working on a car together. Starting the worknight with a team meeting is a great way to encourage everyone to show up on time, to have status updates, and to get everyone on the same page. Having everyone on the team see each other work together at the same time is very underrated as a motivational tool, to build trust, and have fun. Sharing the vehicle model with the entire team can help get everyone on the same page and show off the work everyone has been doing.
==Collaboration Software==
Many teams have started to use Slack, Microsoft Teams, discord, or other collaboration software. The benefit of the software over something private-only like facebook messenger is that team members are welcome to join, leave, and adjust notifications based on conversation topic and interest. Especially helpful for getting new members into the conversation.
===Slack===
Slack brought chat channels to the professional workplace.
====[https://slack.com/pricing Versions]====

{| class="wikitable"
|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|
=====Version=====

| style="width: 55.2px;" data-mce-style="width: 55.2px;"|
=====Cost (USD)=====

| style="width: 608px;" data-mce-style="width: 608px;"|
=====Features=====

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Free
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$0
| style="width: 608px;" data-mce-style="width: 608px;"|Access to 10,000 of your team’s most recent messages
10 integrations with other apps like Google Drive, Office 365 and many more
1:1 voice and video calls between teammates
5GB Storage per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Standard
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$8/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|The full context of your organization’s message history
Timely info and actions in one place with unlimited integration
Face-to-face communication with group voice and video calls of up to 15 teammates
Secure collaboration with outside organizations or guests from within Slack
10 GB per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Plus
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$15/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|Advanced identity management through SAML-based SSO and real-time Active Directory sync with OneLogin, Okta and Ping
Compliance requirements met with data exports for all messages
Around-the-clock teamwork and assistance with 99.99% guaranteed uptime and 24/7 support with a four-hour response time 20 GB per team member
|}
Slack offers [https://slack.com/help/articles/206646877-Slack-for-Education Slack for Education] for 85% off Standard or Plus paid plans.
===Microsoft Teams===
Microsoft Teams is the newest addition. The development team has added a lot of new features during 2018-2020, which has brought it up to par with the other platforms.

'''Pros:'''
* Free with Office 365 if your school has it.
'''Cons:'''
* Channels have excessive unnecessary vertical space compared to others, which makes it less like a conversation. However, if your team uses threads properly to create sub-conversations, then this issue goes away. 
* No voice channels - only meetings and calls

===[https://support.discord.com/hc/en-us/categories/200404378 Discord]===
There is a Formula Student general discord at[https://discord.gg/QNb6qX9 https://discord.gg/QNb6qX9]

Originally branded more towards gamers, discord is likely already popular with gamers on your team.
Discord is free to make a server, and students may subscribe to Discord Nitro or Nitro classic to get the perks below:
{| class="wikitable"
|- style="height: 69px;" data-mce-style="height: 69px;"
| style="width: 64.8px; height: 69px;" data-mce-style="width: 64.8px; height: 69px;"|
=====Version=====

| style="width: 55.2px; height: 69px;" data-mce-style="width: 55.2px; height: 69px;"|
=====Cost (USD)=====

| style="width: 608px; height: 69px;" data-mce-style="width: 608px; height: 69px;"|
=====Features=====

|-
| style="width: 64.8px; height: 136.163px;" data-mce-style="width: 64.8px; height: 136.163px;"|Free

| style="width: 55.2px; height: 136.163px;" data-mce-style="width: 55.2px; height: 136.163px;"|$0

| style="width: 608px; height: 136.163px;" data-mce-style="width: 608px; height: 136.163px;"|
* Unlimited message history
* Screen sharing
* Up to 8 users on a video call
* Up to 5000 users
* Unlimited Storage
* 8MB File upload limit

|-
| style="width: 64.8px; height: 365px;" data-mce-style="width: 64.8px; height: 365px;"|

[https://discord.fandom.com/wiki/Nitro Nitro Classic]

| style="width: 55.2px; height: 365px;" data-mce-style="width: 55.2px; height: 365px;"|

$4.99/mo
$49.99/year
per user

| style="width: 608px; height: 365px;" data-mce-style="width: 608px; height: 365px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 50mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro Classic, they are awarded one boost.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.

|-
| style="width: 64.8px; height: 347px;" data-mce-style="width: 64.8px; height: 347px;"|
Nitro
| style="width: 55.2px; height: 347px;" data-mce-style="width: 55.2px; height: 347px;"|
$9.99/mo$99.99/yrper user

| style="width: 608px; height: 347px;" data-mce-style="width: 608px; height: 347px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 100mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro, they are awarded two boosts.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.
|}

'''Pros:'''
* Free
* Your team probably already has some members that use it
* Has voice channels for casual drop-in conversation and impromptu discussions. You can easily see who else is working on the car at the moment, and hang out with them.
* Has [https://support.discord.com/hc/en-us/articles/360045093012-Server-Integrations-Page integrations] such as [https://www.integromat.com/en/integrations/discord/google-drive Integromat ]for filesharing
* Bot support
'''Cons:'''
* Gamers may need a second account on discord, so you can actually see team members names instead of gamertags, although this can be avoided with [https://support.discord.com/hc/en-us/articles/219070107-Server-Nicknames Server Nicknames] 
* No ability to save messages

==CAD==
Having a single source of truth for your CAD files is very important. Every team member should have access to the latest CAD of the entire vehicle.

===SolidWorks PDM===
'''Pros:'''
* Seamless integration into SolidWorks
* Requires users to lock out files to work on them to prevent conflicting versions and accidental changes.
'''Cons:'''
* Complicated IT system required

===3DEXPERIENCE===
'''Pros: '''
* Dassault is providing free access for students during covid-19.
'''Cons:'''
* You have to use 3DExperience
===Inventor Vault===
Available for teams who use AutoDesk Inventor as their primary CAD software.
===Google Drive / Dropbox===
Works for smaller teams. For larger teams with many simultaneous users, being able to lock out files during editing to prevent version conflicts becomes more important. Also, having one main computer (such as a shop computer) which always has an up to date full-vehicle assembly will help to spot issues.

'''Pros:'''
* Free
* Most teams are already comfortable with these platforms for document sharing.
'''Cons:'''
* No SolidWorks integration 
* No ability to lock out files
* File references can become problematic
===Network Drive===
Some universities will allow you to setup a network drive so that your CAD files are accessible from anywhere on campus. If you want to work from home, you first VPN into the campus network. Universities can even setup automatic backups so that if someone saves over someone's work, not much is lost. Can work well if you are vigilant about only saving the files you need to save.

'''Pros:'''
* Free, if your university allows it
* There is only ever one set of files, so no synchronization is required
'''Cons:'''
* Easy to accidentally save over other people's work if you're not careful
* No CAD integration
* No ability to lock out files
===Subversion (SVN)===
SVN is a version control system developed for software before git. While git is a distributed system, SVN has one central vault, which users can lock out files for editing. There are hosts for SVN servers, or you can create your own SVN server using software like SVNEdge. All the users would use software like tortoiseSVN to sync files.

'''Pros:'''
* Locking out files is optional.
'''Cons:'''
* No SolidWorks integration (yet).
* IT knowledge required to set up own server.

===Git and Github===
Git is primarily used for software development. It is built upon the ability for two people to simultaneously edit a text file, and then for git to be able to merge these two files. Because of this, users are not able to "lock" so only one user can edit at a time. Unfortunately because merging is not possible with CAD files, Git is a poor option for anything other than text files.

=ECAD (PCB Design)=
ECAD collaboration software is mostly redundant with the MCAD section, however ECAD doesn't integrate quite as well with typical CAD repositories, while also having some of it's own unique tools.

===Altium 365===
Available for teams who use Altium Designer as their primary ECAD software.
* Seemless integration with Altium Designer
* Allows non-ECAD users to view models in the workspace

Altium 365 integrates with MCAD through their MCAD Designer plugin. MCAD Designer integrates with Solidworks, PTC Creo, Autodesk Inventor, Autodesk Fusion 360, and Siemens NX to merge 3D CAD data with PCB design.<ref>Altium MCAD CoDesigner.https://www.altium.com/solutions/by-technology/ecad-mcad</ref>

=Software Development=
===Git and Github===
Great for software - Git is the industry standard. Central repository for files. Easy to share. Revision control. Setting up a central, team controlled git repository can be difficult. Each new member to the team should be given access to every repository for the team. Otherwise repositories become silo'ed and knowledge can be lost by graduating team members' repositories not getting shared with the younger members.
===Subversion (SVN)===
Subversion is a central repository either on a hosted service or on a team member's home server. It allows for a central storage location for all files, where the team leads can add students to all files at once. See tortoiseSVN for users and SVNEdge for the server.

SVN is usually only used if pre-existing architecture demands it; Git is much more common nowadays.

Team Collaboration

2024-05-24T14:28:25Z

Emilyanthony: /* CAD */ nuked grabcad info since it

[[Category:Team]]
FSAE is a large process: a lot of parts, a lot of money, a lot of time, and possibly a lot of people. Most companies have to deal with this issue too, so there are quite a few solutions out there to help you organize the team. Solutions that work for one team may not work for another due to differences in how the team is structured.

==Collaboration During Covid-19==
If your team is allowed to work remotely during the pandemic- Weekly worknights and worknight meetings are even more important. Get everyone in on a video call weekly to check in progress. Voice channels on Discord can provide a drop-in casual chat outside meetings replacement for working together in a physical shop, house, or computer lab. Having a central CAD repository/PDM system becomes even more important when working remotely. If your team didn't have one before, it's much more important now.
===Covid-19 Team Collaboration Checklist===

* Weekly worknights (online)
* Weekly meetings (video calls)
* [[Team Collaboration#Collaboration Software|Collaboration Software]]
** Bonus: Open Voice channels
* [[Team Collaboration#CAD|CAD Vault/PDM]]

==Worknights==
Having weekly worknights is key to getting team members to all focus on working on a car together. Starting the worknight with a team meeting is a great way to encourage everyone to show up on time, to have status updates, and to get everyone on the same page. Having everyone on the team see each other work together at the same time is very underrated as a motivational tool, to build trust, and have fun. Sharing the vehicle model with the entire team can help get everyone on the same page and show off the work everyone has been doing.
==Collaboration Software==
Many teams have started to use Slack, Microsoft Teams, discord, or other collaboration software. The benefit of the software over something private-only like facebook messenger is that team members are welcome to join, leave, and adjust notifications based on conversation topic and interest. Especially helpful for getting new members into the conversation.
===Slack===
Slack brought chat channels to the professional workplace.
====[https://slack.com/pricing Versions]====

{| class="wikitable"
|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|
=====Version=====

| style="width: 55.2px;" data-mce-style="width: 55.2px;"|
=====Cost (USD)=====

| style="width: 608px;" data-mce-style="width: 608px;"|
=====Features=====

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Free
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$0
| style="width: 608px;" data-mce-style="width: 608px;"|Access to 10,000 of your team’s most recent messages
10 integrations with other apps like Google Drive, Office 365 and many more
1:1 voice and video calls between teammates
5GB Storage per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Standard
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$8/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|The full context of your organization’s message history
Timely info and actions in one place with unlimited integration
Face-to-face communication with group voice and video calls of up to 15 teammates
Secure collaboration with outside organizations or guests from within Slack
10 GB per team member

|-
| style="width: 64.8px;" data-mce-style="width: 64.8px;"|Plus
| style="width: 55.2px;" data-mce-style="width: 55.2px;"|$15/mo

per active user

| style="width: 608px;" data-mce-style="width: 608px;"|Advanced identity management through SAML-based SSO and real-time Active Directory sync with OneLogin, Okta and Ping
Compliance requirements met with data exports for all messages
Around-the-clock teamwork and assistance with 99.99% guaranteed uptime and 24/7 support with a four-hour response time 20 GB per team member
|}
Slack offers [https://slack.com/help/articles/206646877-Slack-for-Education Slack for Education] for 85% off Standard or Plus paid plans.
===Microsoft Teams===
Microsoft Teams is the newest addition. The development team has added a lot of new features during 2018-2020, which has brought it up to par with the other platforms.

'''Pros:'''
* Free with Office 365 if your school has it.
'''Cons:'''
* Channels have excessive unnecessary vertical space compared to others, which makes it less like a conversation. However, if your team uses threads properly to create sub-conversations, then this issue goes away. 
* No voice channels - only meetings and calls

===[https://support.discord.com/hc/en-us/categories/200404378 Discord]===
There is a Formula Student general discord at[https://discord.gg/QNb6qX9 https://discord.gg/QNb6qX9]

Originally branded more towards gamers, discord is likely already popular with gamers on your team.
Discord is free to make a server, and students may subscribe to Discord Nitro or Nitro classic to get the perks below:
{| class="wikitable"
|- style="height: 69px;" data-mce-style="height: 69px;"
| style="width: 64.8px; height: 69px;" data-mce-style="width: 64.8px; height: 69px;"|
=====Version=====

| style="width: 55.2px; height: 69px;" data-mce-style="width: 55.2px; height: 69px;"|
=====Cost (USD)=====

| style="width: 608px; height: 69px;" data-mce-style="width: 608px; height: 69px;"|
=====Features=====

|-
| style="width: 64.8px; height: 136.163px;" data-mce-style="width: 64.8px; height: 136.163px;"|Free

| style="width: 55.2px; height: 136.163px;" data-mce-style="width: 55.2px; height: 136.163px;"|$0

| style="width: 608px; height: 136.163px;" data-mce-style="width: 608px; height: 136.163px;"|
* Unlimited message history
* Screen sharing
* Up to 8 users on a video call
* Up to 5000 users
* Unlimited Storage
* 8MB File upload limit

|-
| style="width: 64.8px; height: 365px;" data-mce-style="width: 64.8px; height: 365px;"|

[https://discord.fandom.com/wiki/Nitro Nitro Classic]

| style="width: 55.2px; height: 365px;" data-mce-style="width: 55.2px; height: 365px;"|

$4.99/mo
$49.99/year
per user

| style="width: 608px; height: 365px;" data-mce-style="width: 608px; height: 365px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 50mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro Classic, they are awarded one boost.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.

|-
| style="width: 64.8px; height: 347px;" data-mce-style="width: 64.8px; height: 347px;"|
Nitro
| style="width: 55.2px; height: 347px;" data-mce-style="width: 55.2px; height: 347px;"|
$9.99/mo$99.99/yrper user

| style="width: 608px; height: 347px;" data-mce-style="width: 608px; height: 347px;"|

* '''GIF Avatars.'''This perk allows Nitro users to change their avatar into a moving GIF.
* '''Random Discord Tag.'''This perk allows Nitro users to change their Discord tag into any number they like. However, after the subscription, the tag will randomize.
* '''Custom and Animated Emojis.'''This perk allows Nitro users to use custom and animated emojis in any server. This includes DMs. However, if one tries to send a message with Animated Emojis without having Nitro / Nitro Classic, a message will appear, telling the user, that they need Nitro / Nitro Classic in order to send animated emojis.
* '''High-Resolution Video.'''This perk gives Nitro users to screenshare with a higher video quality (720p @ 60fps). This perk also gives 1080p 60fps quality when they go live.
* '''Bigger File Uploading.'''This perk allows Nitro users to upload files up to 100mb.
* '''Server Boosting.'''This perk allows Nitro users to boost their favorite servers. When a user gets Nitro, they are awarded two boosts.
* '''Special Nitro Badge.'''This perk gives users a shiny Nitro user badge on user's profile.
|}

'''Pros:'''
* Free
* Your team probably already has some members that use it
* Has voice channels for casual drop-in conversation and impromptu discussions. You can easily see who else is working on the car at the moment, and hang out with them.
* Has [https://support.discord.com/hc/en-us/articles/360045093012-Server-Integrations-Page integrations] such as [https://www.integromat.com/en/integrations/discord/google-drive Integromat ]for filesharing
* Bot support
'''Cons:'''
* Gamers may need a second account on discord, so you can actually see team members names instead of gamertags, although this can be avoided with [https://support.discord.com/hc/en-us/articles/219070107-Server-Nicknames Server Nicknames] 
* No ability to save messages

==CAD==
Having a single source of truth for your CAD files is very important. Every team member should have access to the latest CAD of the entire vehicle.

===SolidWorks PDM===
'''Pros:'''
* Seamless integration into SolidWorks
* Requires users to lock out files to work on them to prevent conflicting versions and accidental changes.
'''Cons:'''
* Complicated IT system required

===3DEXPERIENCE===
'''Pros: '''
* Dassault is providing free access for students during covid-19.
'''Cons:'''
* You have to use 3DExperience
===Inventor Vault===
Available for teams who use AutoDesk Inventor as their primary CAD software.
===Google Drive / Dropbox===
Works for smaller teams. For larger teams with many simultaneous users, being able to lock out files during editing to prevent version conflicts becomes more important. Also, having one main computer (such as a shop computer) which always has an up to date full-vehicle assembly will help to spot issues.

'''Pros:'''
* Free
* Most teams are already comfortable with these platforms for document sharing.
'''Cons:'''
* No SolidWorks integration 
* No ability to lock out files
* File references can become problematic
===Network Drive===
Some universities will allow you to setup a network drive so that your CAD files are accessible from anywhere on campus. If you want to work from home, you first VPN into the campus network. Universities can even setup automatic backups so that if someone saves over someone's work, not much is lost. Can work well if you are vigilant about only saving the files you need to save.

'''Pros:'''
* Free, if your university allows it
* There is only ever one set of files, so no synchronization is required
'''Cons:'''
* Easy to accidentally save over other people's work if you're not careful
* No CAD integration
* No ability to lock out files
===Subversion (SVN)===
SVN is a version control system developed for software before git. While git is a distributed system, SVN has one central vault, which users can lock out files for editing. There are hosts for SVN servers, or you can create your own SVN server using software like SVNEdge. All the users would use software like tortoiseSVN to sync files.

'''Pros:'''
* Locking out files is optional.
'''Cons:'''
* No SolidWorks integration (yet).
* IT knowledge required to set up own server.

===Git and Github===
Git is primarily used for software development. It is built upon the ability for two people to simultaneously edit a text file, and then for git to be able to merge these two files. Because of this, users are not able to "lock" so only one user can edit at a time. Unfortunately because merging is not possible with CAD files, Git is a poor option for anything other than text files.

=ECAD (PCB Design)=
ECAD collaboration software is mostly redundant with the MCAD section, however ECAD doesn't integrate quite as well with typical CAD repositories, while also having some of it's own unique tools.

===Altium 365===
Available for teams who use Altium Designer as their primary ECAD software.
* Seemless integration with Altium Designer
* Allows non-ECAD users to view models in the workspace

=Software Development=
===Git and Github===
Great for software - Git is the industry standard. Central repository for files. Easy to share. Revision control. Setting up a central, team controlled git repository can be difficult. Each new member to the team should be given access to every repository for the team. Otherwise repositories become silo'ed and knowledge can be lost by graduating team members' repositories not getting shared with the younger members.
===Subversion (SVN)===
Subversion is a central repository either on a hosted service or on a team member's home server. It allows for a central storage location for all files, where the team leads can add students to all files at once. See tortoiseSVN for users and SVNEdge for the server.

SVN is usually only used if pre-existing architecture demands it; Git is much more common nowadays.

Start a Shootout

2024-05-24T13:55:52Z

Emilyanthony: /* Technical Inspection */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
 
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>
 

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2024-05-24T13:54:46Z

Emilyanthony: formatting is hard

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
 
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.

 
<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2024-05-24T13:53:50Z

Emilyanthony: /* Volunteers */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|center|middle|frame|Shootout Work Breakdown Structure]]
<brclear=all />
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.

<brclear=all />
<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2024-05-24T13:52:43Z

Emilyanthony:

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|right|middle|thumb|Shootout Work Breakdown Structure]]
 

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.

 
<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>
=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2024-05-24T13:50:39Z

Emilyanthony:

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.

Student teams choosing to use a shootout as a fundraiser should likely look elsewhere. Without sponsorship of the venue, it's unlikely this will be a reliable source of income for the team.
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand. Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.[[File:Wbs without names.jpg|right|middle|thumb|Shootout Work Breakdown Structure]]

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.

<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>
=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2024-05-24T13:42:08Z

Emilyanthony: /* Volunteers */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]

=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.
Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
## Site safety contacts
## Paddock patrol
## Traffic/access controls
## Gate monitors 
# Technical Inspection
## Mechanical
## Electrical
## Accumulator
## Rain
## Brakes
# Timing and Scoring
## Spotters
## Loggers
## Backup timers
# General Event Ops
## Registration
## Q&A
## Sponsor relations
## etc
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time. A sample [[Work Breakdown Structure]] is shown below. This was derived from the Pittsburgh Shootout's WBS, with names omitted for privacy. The structure is split between pre-event responsibilities and at-event; the race is on Saturday, and it can be seen that the branch is divvied further between Friday and Saturday tasks. Limitations on responsibility are shown, noting the red and orange boxes stating volunteers are to only pick one box.

[[File:Wbs without names.jpg|left|middle|thumb|Shootout Work Breakdown Structure]]
==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if a tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.

<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

File:Wbs without names.jpg

2024-05-24T13:36:12Z

Emilyanthony:

Start a Shootout

2024-04-11T19:00:57Z

Emilyanthony: /* Venue Selection */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]

=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2023-06-23T15:40:59Z

Emilyanthony: /* Technical Inspection */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenitiesRace tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]

=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2023-06-23T15:40:04Z

Emilyanthony: /* Financing */

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenitiesRace tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online] to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]

=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

<a>[1]</a>
# <a>↑</a> Pittsburgh Shootout Handbook. <a rel="nofollow" class="external free">https://www.pittsburghshootout.com/handbook</a>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2023-06-23T14:48:31Z

Emilyanthony: add fmea, insurance info

Generally, student teams should be discouraged from starting their own Shootout events due to the risks involved with hosting and large amount of work required to host correctly. Consider attending an established event instead.
=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenitiesRace tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online ]

to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]

=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 350 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

<a>[1]</a>
# <a>↑</a> Pittsburgh Shootout Handbook. <a rel="nofollow" class="external free">https://www.pittsburghshootout.com/handbook</a>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''


==FMEA==
FMEA can be used to evaluate risk of hosting an unofficial competition. The Pittsburgh Shootout publishes its FMEA for student teams and officials to review.

https://docs.google.com/spreadsheets/d/1dAgxpR94R8mhTuMNykopEIkIxLRzPd8csvb159GR-Og

[[Category:Competition]]

Start a Shootout

2023-06-23T14:42:31Z

Emilyanthony: /* Technical Inspection */

=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online ]to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 275 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "90%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections may be done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams. As of 2023, the Pittsburgh Shootout requires all EV participants to have passed through Rain test at an official event before attending the Shootout.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''

[[Category:Competition]]

Start a Shootout

2023-06-23T14:40:14Z

Emilyanthony: /* Insurance */

=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online ]to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 275 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "80%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections are done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.


'''Do not host a Shootout event without insurance.'''

[[Category:Competition]]

Start a Shootout

2023-06-23T14:39:51Z

Emilyanthony: /* Insurance */

=Venue Selection=
Identification of a suitable venue for a FS competition is an exercise in both the development of a relationship with a venue owner as well as meeting some simple criteria. Considerations should be made for the following when identifying a venue:
# Size and quality of drivable area
# Access to restroom facilities
# Location relative to lodging and other necessary amenities
Race tracks with skidpad/autocross designated areas are natural selections to host an unofficial event, but parking lots at universities and other spaces can be used provided they have adequate surfaces and the obstacles such as light poles can be avoided. Paddock space must be available for all teams as well; each team requires approximately a 5mx15m paddock to park the trailer, tow vehicle, and tents.

A meeting with the venue owner will be necessary prior to event planning to discuss what the team plans to do with the space, establish pricing, and set clear expectations between the team and venue. It is recommended that teams with active SCCA chapters nearby reach out to their organizers as well to learn how to run the event. Teams should bring at minimum the following with their meeting with the venue representative:
# Proposed schedule of events, specifically with "hot" times
# Estimated attendance (# of students)
# Requirements of the venue, such as:
## Provisions for restroom facilities
## Food vending
## Camping support, if available
## Providing cones, trash cans, hay bales, etc
## EMS

=Financing=
The funding required to host an event is largely dependent on the venue host and availability of sponsors. The Pittsburgh Shootout publishes financial information [https://www.pittsburghshootout.com/sponsorship online ]to clarify funding needs for its event. Most venues will give a clear quote for services in the section above and allow the team to select items a la carte.[[File:Chart.png|link=https://lh3.googleusercontent.com/AkUWvqFYiTPsGp028B8x7Lb_I_UjYAmCDVHv9SvBR_52mphcsiSLy_AP209Bha40nBpPbs_Goy6ZtmafXUw0es1sdNKp-YKSHrKINtAwVM-npgWX--7xi7u-YPUpINwLUw=w1280|alt=Pittsburgh Shootout Funding Need|right|middle|frameless|Pittsburgh Shootout Funding Waterfall]]
=Volunteers=
The number of required volunteers is dependent on attendance. There are some rules of thumb for volunteer:attendee ratio. For example, FSAE in North America has approximately 275 volunteers for 120 FSAE teams, but the volunteers serve several roles across the weekend. The 2022 Pittsburgh Shootout fielded 40 volunteers for 32 teams for the autocross, but requires closer to 50 to function correctly.

Knowledgeable volunteers must be sourced to perform technical inspection. Students may perform these tasks, but require training beforehand.

Volunteers should be allocated for the following tasks:
# Team parking/check-in
# Technical Inspection
# Timing and Scoring
# General Event Ops
# Floaters (approximately 1 floater to 10 volunteers)
There should be approximately 2-4 technical inspectors assigned per inspection "bay". Technical Inspection may take an hour+, so several groups of technical inspectors are required. At the Pittsburgh Shootout, technical inspection is started Friday night for the Autocross on Saturday to better manage time.

==Technical Inspection==
Tech inspection is an absolute necessity for unofficial shootout events. The risks in hosting other Formula teams to the host team, the venue, and SAE are astronomical if the hosting team does not take the steps necessary to ensure safety of all attendees. Technical inspection must be to a similar rigor to the official SAE events and exceptions cannot be made to requirements which compromise the safety of the student driver or other attendees. Often it's difficult to perform some of the technical inspection tasks provided at the SAE events due to a lack of a tilt table or other tools; it is the host team's responsibility to provide adequate alternatives such as requiring tech stickers from an official event, performing a modified test, or being more stringent on safety requirements to ensure student and spectator safety.

The Pittsburgh Shootout provides an "80%" technical inspection to cars which have passed a Formula SAE technical inspection, skipping steps such as SES checks. A full technical inspection performed by inspectors who also do the official events is provided for a team which cannot produce tech stickers. The Pittsburgh Shootout does not perform a tilt test or a sound test, but does perform a rain test and brakes test. There are 6 technical inspection bays at the Pitt Shootout, and cars are split by vehicle class for inspection. Accumulator inspections are done with a video prior to the event, or performed on site if the teams fail to provide the video. Teams may circumvent the accumulator inspection at the event if the tamper seal is unbroken from the official FSAE event. The Pittsburgh Shootout also built an IMD tester to verify functionality for EV teams.<ref>Pittsburgh Shootout Handbook. https://www.pittsburghshootout.com/handbook</ref>

=Risk Management=
==Insurance==
Event insurance is remarkably difficult to get due to the nature of the event being a motorsports race. Most event insurance companies will not cover FSAE shootouts. Work with your venue or your university to procure insurance. Often in track rental contracts the Host (the team, generally) is required to procure general liability insurance. Many race tracks have an open contract with an insurance company and may be able to source this insurance for the event.

The Pittsburgh Shootout acquires the following insurance coverage through the venue:

$5 million general liability $15,000 accidental death $15,000 additional medical

in addition to a waiver signed at the gate affirming all participants have a drivers license and health insurance.



'''Do not host a Shootout event without insurance.'''

[[Category:Competition]]

List of competitions

2023-06-23T14:33:28Z

Emilyanthony: /* Unofficial Active Competitions */

==Official Active Competitions==

{| class="wikitable" style="width: 1256px;" data-mce-style="width: 1256px;"
|-
| style="width: 194px;" data-mce-style="width: 194px;"|'''Country'''
| style="width: 327px;" data-mce-style="width: 327px;"|'''Name'''
| style="width: 200px;" data-mce-style="width: 200px;"|'''Sanctioning Body'''
| style="width: 137px;" data-mce-style="width: 137px;"|'''Classes'''
| style="width: 102px;" data-mce-style="width: 102px;"|'''Month'''
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|'''Years active since'''
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|'''Notes'''
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Australia
| style="width: 327px;" data-mce-style="width: 327px;"|[http://www.saea.com.au/formula Formula SAE Australasia]
| style="width: 200px;" data-mce-style="width: 200px;"|SAE Australasia
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|December
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2000
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Austria
| style="width: 327px;" data-mce-style="width: 327px;"|[https://fsaustria.at/ Formula Student Austria]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula Student Austria
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2009
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Brasil
| style="width: 327px;" data-mce-style="width: 327px;"|[http://portal.saebrasil.org.br/programas-estudantis/formula-sae-brasil Formula SAE Brasil ]
| style="width: 200px;" data-mce-style="width: 200px;"|[http://portal.saebrasil.org.br/ SAE Brasil]
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|November-December
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2004
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|China
| style="width: 327px;" data-mce-style="width: 327px;"|[http://www.formulastudent.com.cn/ Formula Student China]
| style="width: 200px;" data-mce-style="width: 200px;"|China Society of Automotive Engineers
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|October-November
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2010
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|EV and CV are held separately since 2015, DV started in 2017, and is held with EV.
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Croatia
| style="width: 327px;" data-mce-style="width: 327px;"|[https://fs-alpeadria.com/ Formula Alpe Adria]
| style="width: 200px;" data-mce-style="width: 200px;"|FS Alpe Adria
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2022
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|Unofficial event before 2022 (first held 2017).
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Czech Republic
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.fsczech.cz/ Formula Student Czech Republic]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula Student Czech Republic
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2013
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|[[FSG|Germany]] 
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.formulastudent.de/ Formula Student Germany]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula Student Germany
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2006
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|It was announced in October 2019 that FSG would transition to a full driverless competition in 2022. <ref>Formula Student Germany News. "FSG Strategic Announcement." October 24 2019. https://www.formulastudent.de/pr/news/details/article/fsg-strategic-announcement/ </ref> Due to COVID-19, this strategic plan has shifted 1 year. The competition will become driverless in 2023. <ref>Formula Student Germany News. "Update to Cancellation of FSG 2020." https://www.formulastudent.de/pr/news/details/article/update-to-cancellation-of-fsg-2020/ </ref>
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Hungary
| style="width: 327px;" data-mce-style="width: 327px;"|[https://fseast.eu/ Formula Student East]
| style="width: 200px;" data-mce-style="width: 200px;"|Association of Automotive Engineers
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2016
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|India
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.formulabharat.com/ Formula Bharat]
| style="width: 200px;" data-mce-style="width: 200px;"|[http://www.curiosumtech.in/ Curiosum Tech]
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|January
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2017
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Italy
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.formula-ata.it/ Formula SAE Italy]
| style="width: 200px;" data-mce-style="width: 200px;"|ANFIA
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2005
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Japan
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.jsae.or.jp/formula/jp Formula SAE Japan]
| style="width: 200px;" data-mce-style="width: 200px;"|JSAE
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|September
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Netherlands
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.formula-student.nl/ Formula Student Netherlands]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula Student Netherlands
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Russia
| style="width: 327px;" data-mce-style="width: 327px;"|[http://fstudent.ru/ Formula Student Russia]
| style="width: 200px;" data-mce-style="width: 200px;"|Department of Entreprenurship and Innovative Devlopment of the City of Moscow and SMP Racing
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|September
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2019
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|South Korea
| style="width: 327px;" data-mce-style="width: 327px;"|[http://jajak.ksae.org/ KSAE Formula]
| style="width: 200px;" data-mce-style="width: 200px;"|The Korean Society of Automotive Engineers
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|October
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Spain
| style="width: 327px;" data-mce-style="width: 327px;"|[http://www.formulastudent.es/ Formula Student Spain]
| style="width: 200px;" data-mce-style="width: 200px;"|STA (Spanish Society of Automotive Engineers)
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2010
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Switzerland
| style="width: 327px;" data-mce-style="width: 327px;"|[https://formulastudent.ch/index.php Formula Student Switzerland]
| style="width: 200px;" data-mce-style="width: 200px;"|FS Switzerland
| style="width: 137px;" data-mce-style="width: 137px;"|EV
| style="width: 102px;" data-mce-style="width: 102px;"|July-August
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2020 (cancelled) 
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Thailand
| style="width: 327px;" data-mce-style="width: 327px;"|[http://www.tsae.or.th/ TSAE Auto Challenge]
| style="width: 200px;" data-mce-style="width: 200px;"|SAE Thailand
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|January
| style="width: 100.8px;" data-mce-style="width: 100.8px;"| 
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|United Kingdom
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.imeche.org/events/formula-student Formula Student ]
| style="width: 200px;" data-mce-style="width: 200px;"|IMechE
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV, DV
| style="width: 102px;" data-mce-style="width: 102px;"|July
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|1998
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|
|-
| style="width: 194px;" data-mce-style="width: 194px;"|USA
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.sae.org/attend/student-events/formula-sae-michigan Formula SAE Michigan]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula SAE
| style="width: 137px;" data-mce-style="width: 137px;"|CV
| style="width: 102px;" data-mce-style="width: 102px;"|May
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|1981 
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|Held in Texas in 1981-1985, 1987, 1989 
|-
| style="width: 194px;" data-mce-style="width: 194px;"|USA
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.sae.org/attend/student-events/formula-sae-california Formula SAE West/Lincoln/California]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula SAE
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|June
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2006
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|Held in Lincoln, NE between 2012-2019, in Las Vegas, NV in 2021, and in Michigan in 2022-23. 
|}

==Official Inactive Competitions==

{| class="wikitable" style="width: 1256px;" data-mce-style="width: 1256px;"
|-
| style="width: 194px;" data-mce-style="width: 194px;"|'''Country'''
| style="width: 327px;" data-mce-style="width: 327px;"|'''Name'''
| style="width: 200px;" data-mce-style="width: 200px;"|'''Sanctioning Body'''
| style="width: 137px;" data-mce-style="width: 137px;"|'''Classes'''
| style="width: 102px;" data-mce-style="width: 102px;"|'''Month'''
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|'''Years active'''
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|'''Notes'''
|-
| style="width: 194px;" data-mce-style="width: 194px;"|Canada
| style="width: 327px;" data-mce-style="width: 327px;"|[https://www.sae.org/attend/student-events/formula-sae-north Formula SAE North]
| style="width: 200px;" data-mce-style="width: 200px;"|Formula SAE
| style="width: 137px;" data-mce-style="width: 137px;"|CV, EV
| style="width: 102px;" data-mce-style="width: 102px;"|May
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2010-2019
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|Taken over by SAE in 2019. Closed indefinitely in 2021.
|-
| style="width: 194px;" data-mce-style="width: 194px;"|USA
| style="width: 327px;" data-mce-style="width: 327px;"|Formula SAE at VIR
| style="width: 200px;" data-mce-style="width: 200px;"|Formula SAE
| style="width: 137px;" data-mce-style="width: 137px;"|CV
| style="width: 102px;" data-mce-style="width: 102px;"|April
| style="width: 100.8px;" data-mce-style="width: 100.8px;"|2008-2009
| style="width: 367.2px;" data-mce-style="width: 367.2px;"|Suspended until further notice due to economy and lack of student demand.
|}

==Unofficial Active Competitions==

{| class="wikitable" style="width: 1361px;" data-mce-style="width: 1361px;"
|- style="height: 34px;" data-mce-style="height: 34px;"
| style="width: 194px; height: 34px;" data-mce-style="width: 194px; height: 34px;"|'''City, Country'''
| style="width: 222px; height: 34px;" data-mce-style="width: 222px; height: 34px;"|'''Name'''
| style="width: 410px; height: 34px;" data-mce-style="width: 410px; height: 34px;"|'''Organizing Body'''
| style="width: 105px; height: 34px;" data-mce-style="width: 105px; height: 34px;"|'''Classes'''
| style="width: 60px; height: 34px;" data-mce-style="width: 60px; height: 34px;"|'''Month'''
| style="width: 125px; height: 34px;" data-mce-style="width: 125px; height: 34px;"|'''Years active since'''
| style="width: 472px; height: 34px;" data-mce-style="width: 472px; height: 34px;"|'''Notes'''
|- style="height: 24.8px;" data-mce-style="height: 24.8px;"
| style="width: 194px; height: 24.8px;" data-mce-style="width: 194px; height: 24.8px;"|Dallesport, WA, USA
| style="width: 222px; height: 24.8px;" data-mce-style="width: 222px; height: 24.8px;"|Dallesport Shootout
| style="width: 410px; height: 24.8px;" data-mce-style="width: 410px; height: 24.8px;"|Global Formula Racing
| style="width: 105px; height: 24.8px;" data-mce-style="width: 105px; height: 24.8px;"|
| style="width: 60px; height: 24.8px;" data-mce-style="width: 60px; height: 24.8px;"|October
| style="width: 125px; height: 24.8px;" data-mce-style="width: 125px; height: 24.8px;"|
| style="width: 472px; height: 24.8px;" data-mce-style="width: 472px; height: 24.8px;"|
|- style="height: 24.8px;" data-mce-style="height: 24.8px;"
| style="width: 194px; height: 24.8px;" data-mce-style="width: 194px; height: 24.8px;"|Pittsburgh, PA, USA
| style="width: 222px; height: 24.8px;" data-mce-style="width: 222px; height: 24.8px;"|[//www.pittsburghshootout.com Pittsburgh Shootout]
| style="width: 410px; height: 24.8px;" data-mce-style="width: 410px; height: 24.8px;"|[//www.facebook.com/Pittshootout Pittsburgh Shootout LLC]
| style="width: 105px; height: 24.8px;" data-mce-style="width: 105px; height: 24.8px;"|CV, EV, Hybrid
| style="width: 60px; height: 24.8px;" data-mce-style="width: 60px; height: 24.8px;"|July-August
| style="width: 125px; height: 24.8px;" data-mce-style="width: 125px; height: 24.8px;"|2016
| style="width: 472px; height: 24.8px;" data-mce-style="width: 472px; height: 24.8px;"|Uses Formula SAE ruleset with Supplement
Autocross and Skidpad event only
|- style="height: 16px;" data-mce-style="height: 16px;"
| style="width: 194px; height: 16px;" data-mce-style="width: 194px; height: 16px;"|Ljungbyhed, Sweden
| style="width: 222px; height: 16px;" data-mce-style="width: 222px; height: 16px;"|[https://lundformulastudent.se/nordic-test-event/ Nordic Test Event]
| style="width: 410px; height: 16px;" data-mce-style="width: 410px; height: 16px;"|[https://lundformulastudent.se/ Lund Formula Student]
| style="width: 105px; height: 16px;" data-mce-style="width: 105px; height: 16px;"|CV, EV, DV
| style="width: 60px; height: 16px;" data-mce-style="width: 60px; height: 16px;"|June
| style="width: 125px; height: 16px;" data-mce-style="width: 125px; height: 16px;"|2015
| style="width: 472px; height: 16px;" data-mce-style="width: 472px; height: 16px;"|Mock competition aimed at the nordic teams
|- style="height: 16px;" data-mce-style="height: 16px;"
| style="width: 194px; height: 16px;" data-mce-style="width: 194px; height: 16px;"|Sydney, Australia
| style="width: 222px; height: 16px;" data-mce-style="width: 222px; height: 16px;"|[https://www.fs-sydney.com.au/ FS Sydney]
| style="width: 410px; height: 16px;" data-mce-style="width: 410px; height: 16px;"|[https://www.sydneymotorsportpark.com.au/ Australian Racing Drivers' Club]
| style="width: 105px; height: 16px;" data-mce-style="width: 105px; height: 16px;"|CV, EV
| style="width: 60px; height: 16px;" data-mce-style="width: 60px; height: 16px;"|January
| style="width: 125px; height: 16px;" data-mce-style="width: 125px; height: 16px;"|2019
| style="width: 472px; height: 16px;" data-mce-style="width: 472px; height: 16px;"|Formula SAE rule set with full dynamic events and modified static events.
|- style="height: 16px;" data-mce-style="height: 16px;"
| style="width: 194px; height: 16px;" data-mce-style="width: 194px; height: 16px;"|Rotating
| style="width: 222px; height: 16px;" data-mce-style="width: 222px; height: 16px;"|[https://www.facebook.com/BalticOpenEvents/ Baltic Open]
| style="width: 410px; height: 16px;" data-mce-style="width: 410px; height: 16px;"|Baltic Open /[http://metropolia-motorsport.fi/ Metropolia Motorsport]
| style="width: 105px; height: 16px;" data-mce-style="width: 105px; height: 16px;"|CV, EV
| style="width: 60px; height: 16px;" data-mce-style="width: 60px; height: 16px;"|August-September
| style="width: 125px; height: 16px;" data-mce-style="width: 125px; height: 16px;"|2003
| style="width: 472px; height: 16px;" data-mce-style="width: 472px; height: 16px;"|Usually organized somewhere around the Baltic sea, allows grandfathered cars to compete
|}

[[Category:Competition]]

==Notes==
<references />