# content
I301          *It is your teams ROBOT. The ROBOT and its MAJOR MECHANISMS must be built by the FIRST Tech Challenge team that has registered for the event and intends to use the ROBOT to participate in MATCHES or as part of judged awards.

A MAJOR MECHANISM is a group of COMPONENTS and/or MECHANISMS assembled together to address at least 1 game challenge: ROBOT movement, SCORING ELEMENT manipulation, FIELD element manipulation, or performance of a scorable task without the assistance of another ROBOT.

This rule requires that the ROBOT and its MAJOR MECHANISMS were built by its team but is not intended to prohibit or discourage assistance from other teams (e.g., fabricating elements, supporting construction, writing software, developing game strategy, contributing COMPONENTS, and/or MECHANISMS).

Examples that would generally not be considered MAJOR MECHANISMS, and thus are not subject to this rule include, but are not limited to, the following:

A.      a gearbox assembly,

B.      a COMPONENT or MECHANISM that is part of a MAJOR MECHANISM, or

C.      COTS items.

The intent of this rule is that a teams ROBOT is a product thats representative of the current team members experience and is intended to discourage complete solutions which are provided wholly by outside organizations or companies. Also see R301.

# contentMap.en
I301          *It is your teams ROBOT. The ROBOT and its MAJOR MECHANISMS must be built by the FIRST Tech Challenge team that has registered for the event and intends to use the ROBOT to participate in MATCHES or as part of judged awards.

A MAJOR MECHANISM is a group of COMPONENTS and/or MECHANISMS assembled together to address at least 1 game challenge: ROBOT movement, SCORING ELEMENT manipulation, FIELD element manipulation, or performance of a scorable task without the assistance of another ROBOT.

This rule requires that the ROBOT and its MAJOR MECHANISMS were built by its team but is not intended to prohibit or discourage assistance from other teams (e.g., fabricating elements, supporting construction, writing software, developing game strategy, contributing COMPONENTS, and/or MECHANISMS).

Examples that would generally not be considered MAJOR MECHANISMS, and thus are not subject to this rule include, but are not limited to, the following:

A.      a gearbox assembly,

B.      a COMPONENT or MECHANISM that is part of a MAJOR MECHANISM, or

C.      COTS items.

The intent of this rule is that a teams ROBOT is a product thats representative of the current team members experience and is intended to discourage complete solutions which are provided wholly by outside organizations or companies. Also see R301.