Documentation Theory: Difference between revisions
Jump to navigation
Jump to search
(Created page with "*For composed CAD at product level (hundreds of parts) - create part trees with Visualization Priority, not Taxonomy Priority. *Version Product by number, so it can be...") |
No edit summary |
||
| Line 1: | Line 1: | ||
*For composed CAD at product level (hundreds of parts) - create part trees with [[Visualization Priority]], not [[Taxonomy Priority]]. | *For composed CAD at product level (hundreds of parts) - create part trees with [[Visualization Priority]], not [[Taxonomy Priority]]. | ||
*Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy. | *Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy, simply by knowing [[Product Nomenclature]]. | ||
*Design documentation taxonomy in a fashion that allows any outsider to Orient themselves fully to find any documentation asset whatsoever no matter how granular, simply by understanding basic principles of OSE taxonomy. | |||
*Remember always that the goal is [[Integration by Degeneracy]] | |||
Revision as of 19:33, 26 February 2025
- For composed CAD at product level (hundreds of parts) - create part trees with Visualization Priority, not Taxonomy Priority.
- Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy, simply by knowing Product Nomenclature.
- Design documentation taxonomy in a fashion that allows any outsider to Orient themselves fully to find any documentation asset whatsoever no matter how granular, simply by understanding basic principles of OSE taxonomy.
- Remember always that the goal is Integration by Degeneracy