GVCS Development Areas: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Integrated Concurrent Engineering (ICE) Approach= | =Integrated Concurrent Engineering (ICE) Approach - Theory= | ||
There are several main aspects of [[OSPD]]: | There are several main aspects of [[OSPD]]: | ||
#Specification | #Specification | ||
| Line 12: | Line 12: | ||
This blends into OSE paradigm of [[Multilevel Learning]], [[Integrated Design]], [[Integrated Enterrpise]], [[Product Ecology]], [[Construction Set Approach]], [[Second Toyota Paradox]], [[Concurrent Engineering]], [[Extreme Manufacturing]], and [[Extreme Learning]], and [[Extreme Enterprise]] - and now [[Prompt Engineering]]. All these approaches are taken on at the same time - pending the availability of bodies to make it happen. If we engage in [[GVCS]] development of 50 core tools using the [[Development Template]], or pursue the underlying [[500 Modules]] - then thousands of people can collaborate - all at the same time. Using wikis or concurrent working Google Slides along 50 tools and 80 development steps - or the underlying 500 modules, then we have 44,000 people that can collaborate meaningfully using existing tools. Including the [[Zachman Ontology]], we can wrap our head around how this process works with seamless [[Collaboration Architecture]] - but the caveat is a huge prerequisite of [[Collaborative Literacy]]. | This blends into OSE paradigm of [[Multilevel Learning]], [[Integrated Design]], [[Integrated Enterrpise]], [[Product Ecology]], [[Construction Set Approach]], [[Second Toyota Paradox]], [[Concurrent Engineering]], [[Extreme Manufacturing]], and [[Extreme Learning]], and [[Extreme Enterprise]] - and now [[Prompt Engineering]]. All these approaches are taken on at the same time - pending the availability of bodies to make it happen. If we engage in [[GVCS]] development of 50 core tools using the [[Development Template]], or pursue the underlying [[500 Modules]] - then thousands of people can collaborate - all at the same time. Using wikis or concurrent working Google Slides along 50 tools and 80 development steps - or the underlying 500 modules, then we have 44,000 people that can collaborate meaningfully using existing tools. Including the [[Zachman Ontology]], we can wrap our head around how this process works with seamless [[Collaboration Architecture]] - but the caveat is a huge prerequisite of [[Collaborative Literacy]]. | ||
=Practice= | |||
In practice, it suffices to say that in technical development, all economic sectors, disciplines, and roles are present - but for any participant to collaborate, they must be aware of this framework. Once this happens, then the artist no longer asks - "this is all great, but I'm not an engineer and therefore there is no way for me to contribute". In truth, 'art' or 'heart' enters in the specification, concept, technical design, BOM, build, product, and production engineering - in areas such as interface design, communications, visual workshop, pokayoke design, graphic design, ergonomic design, ecological integration, and countless other areas. In other words, we take on an integrated approach. Thus, we ask so called technologists, artists, humanitarians, social scientists etc to stop labeling themselves to avoid getting engaged in OSE work - as we are all generalists and specialization is for insects. We start with a common ground of addressing material security for everyone, so that purpose and the good life can follow - which is the art of life. | |||
=Areas= | =Areas= | ||
Revision as of 00:42, 28 July 2025
Integrated Concurrent Engineering (ICE) Approach - Theory
There are several main aspects of OSPD:
- Specification
- Concept design
- Technical Design
- BOM
- Build
- Enterprise Product
- Production Engineering
These above are largely included in the Development Template of Open Source Product Development.
This blends into OSE paradigm of Multilevel Learning, Integrated Design, Integrated Enterrpise, Product Ecology, Construction Set Approach, Second Toyota Paradox, Concurrent Engineering, Extreme Manufacturing, and Extreme Learning, and Extreme Enterprise - and now Prompt Engineering. All these approaches are taken on at the same time - pending the availability of bodies to make it happen. If we engage in GVCS development of 50 core tools using the Development Template, or pursue the underlying 500 Modules - then thousands of people can collaborate - all at the same time. Using wikis or concurrent working Google Slides along 50 tools and 80 development steps - or the underlying 500 modules, then we have 44,000 people that can collaborate meaningfully using existing tools. Including the Zachman Ontology, we can wrap our head around how this process works with seamless Collaboration Architecture - but the caveat is a huge prerequisite of Collaborative Literacy.
Practice
In practice, it suffices to say that in technical development, all economic sectors, disciplines, and roles are present - but for any participant to collaborate, they must be aware of this framework. Once this happens, then the artist no longer asks - "this is all great, but I'm not an engineer and therefore there is no way for me to contribute". In truth, 'art' or 'heart' enters in the specification, concept, technical design, BOM, build, product, and production engineering - in areas such as interface design, communications, visual workshop, pokayoke design, graphic design, ergonomic design, ecological integration, and countless other areas. In other words, we take on an integrated approach. Thus, we ask so called technologists, artists, humanitarians, social scientists etc to stop labeling themselves to avoid getting engaged in OSE work - as we are all generalists and specialization is for insects. We start with a common ground of addressing material security for everyone, so that purpose and the good life can follow - which is the art of life.