R22 and previous year's designs

[gbrettmiller]

If I read the definition of COTS and VENDOR correctly, a simply publishing a design as 'open-source' does not make that design a COTS product. Based on the definition of VENDOR, an FRC team does not qualify, which means they cannot be a valid source of COTS.

[Gary Dillard]

Originally Posted by gbrettmiller

If I read the definition of COTS and VENDOR correctly, a simply publishing a design as 'open-source' does not make that design a COTS product. Based on the definition of VENDOR, an FRC team does not qualify, which means they cannot be a valid source of COTS.

Read Example 3 of the definition of COTS - a design which is available to all teams is a COTS item, but the part built from that design is not. If you have a previous design you want to use, as I interpret it you can either

1) Generate an all new model and drawings to build it
2) Publish the model and build it from the model
3) Publish the model and create new drawings from the model to build it
4) Publish the model and drawings and build it from the drawings

[Gary Dillard]

OK after reading my last post and thinking about it, do you really need to publish your design if you are willing to share it if anyone asks for it?

If I know that team XYZ had a really nice omni wheel last year and I ask them for their design and they give it to me, and I know they would willingly give it to any team that asks, isn't that the same intent? How is finding the model online any different from seeing a design online, asking for it and getting it, other than actively publishing versus passively publishing it?

Also one other thing comes to mind, that I believe is technically not allowed but I would be willing to accept it. Suppose another team has a really nice CNC machined part they built last year and goes through the whole process of sharing their design, then they go to their partner company to have it made again this year. By the rules the company would have to recreate the CNC program from scratch before they build the part; do we really want to ask companies who are donating very expensive manufacturing resources to do that? I could probably live with letting them reuse the program.

[gbrettmiller]

The distinction I see is that Example 3 refers to obtaining the design from "a professional publication", not from another - or your own - team. In fact, the definition of COTS itself specifies:

"...part commonly available from the VENDOR, available from a non-team source, ..."

And the definition of VENDOR seems to exclude an FRC team, based on the requirement to meet all of the conditions it sets.

[Gary Dillard]

Originally Posted by gbrettmiller

The distinction I see is that Example 3 refers to obtaining the design from "a professional publication", not from another - or your own - team. In fact, the definition of COTS itself specifies:



And the definition of VENDOR seems to exclude an FRC team, based on the requirement to meet all of the conditions it sets.

Yes, but the definition refers to the fabricated part (it says component or mechanism) not the design. The part is not COTS, period. But it doesn't say that the design had to come from a vendor - if they got it from a professional publication it didn't necessarily come from a vendor. Example 2 says "openly available blueprints". There is no distinction on who generated the design.

[gbrettmiller]

Originally Posted by Gary Dillard

Yes, but the definition refers to the fabricated part (it says component or mechanism) not the design. The part is not COTS, period. But it doesn't say that the design had to come from a vendor - if they got it from a professional publication it didn't necessarily come from a vendor. Example 2 says "openly available blueprints". There is no distinction on who generated the design.

From example 3:

The design drawings would be considered a COTS item.

This to me means that the design itself would have to meet the criteria given in the definition of COTS, which include being provided by a VENDOR.