Engagement is a recurrent problem in open p2p communities and networks. It translates into keeping a critical number of participants focused on a task or a project until its completion.
Open p2p communities and networks do not operate based on engagement contracts, such as job contracts used in traditional organizations. They crowdsource their activities and allow free flow of participation in and out of a project. This open and participatory mode of operation bring in a new management paradigm.
General admin tasks.
Explore the application domain of the Sponsor to understand the its context.
Writing reports for Sponsor and other sponsor-related communication.
Create visual content for outreach. - Max
Reach out to other communities through social media and gather support for the project.
Important, administrative meetings for the project.
General project facilitation and coordination task, among affiliated, during the course of the project.
This is initial engagement in developing the relation with the Sponsor, prior to the start ...
This is an onboarding task, taking care of new comers to the project.
General project administration tasks.
This is a process for considering design characteristics for the electronics layer of the product ...
This is a process for considering design characteristics for the mechanical layer of the product ...
This is a process for considering design characteristics for the software layer of the product ...
NOTE: you need to create specific design processes here (Design electronic, mechanical, optical, software or other)
This design stage focuses on the product itself and feeds on the Design considerations stage. Designs can be of multiple types: mechanical, electronic, optical/photonic, etc. Designs are Resources in the NRP-VAS system, and are represented by some sort of design file: a sketch, a CAD file, link to a software repository, etc.
INPUT: all from Ideation and Design considerations
OUTPUT: product design - file(s), can be multiple
Distinguish 2 levels of design at this stage:
1- System Level Design: Definition of product architecture, decomposition into subsystems and components, and preliminary design of key components. Plans for the production system and final assembly; Outputs: Geometric Layout of the product, a functional specification of each subsystems, and a preliminary process flow diagram for the final assembly process.
2- Detail Design: Complete specification of geometry, materials, tolerance of all unique parts; identification of all the standard parts to be purchased from suppliers. Process plan established and tooling designed for each fabricated part within the production system. Outputs: Control Documentation for the product - drawings or computer files describing the geometry of each part and its production tooling, specs of purchased parts and the process plan for fabrication and assembly. Three Critical issues: Materials Selection; production cost; and robust performance.
Desired design characteristics
* Shareable (the sharing economy)
* Modular (perpetual products and customizable) - see this link about a specific effort to define a standard for scientific parts.
* Interoperable (standards)
* Socializable (offer value through social interactions and communities)
See product design philosophy doc
Documenting the prototype, its characteristics, behavior, functioning, observations, lessons learned, etc.
Produce a physical prototype of the Spider rig device.
Prototyping stage of an R&D process. This stage is about making something tangible, in the physical world, that uses a design and that works to a satisfactory level.
During the R&D process there is a cycle between Prototyping and Design, meaning that the prototyping process might unravel problems with the design, which will trigger changes of the design.
Prototyping produces a detailed description of a tangible thing, how it is made, how it functions, how well it functions. This description is based on empirical data or physical experimentation.
This process is also known as Testing and Refinement: Construction and evaluation of multiple pre production versions of the product. Early (alpha) prototypes are usually built with production intent-parts-same geometry and material properties as intended for the production version of the product but not necessarily fabricated with the actual processes to be used in production. Alpha prototypes are tested to determine whether the product will work as designed and whether the product will satisfy the key customer needs. Later (beta) prototypes are usually built with parts supplied by the intended production process. Beta prototypes are extensively evaluated internally and are also typically tested by customer in their own use environment. The goal here is to answer questions about performance and reliability in order to identify necessary engineering changes for the final product.
INPUT: a product design
OUTPUT: design files and improved prototype descriptions, presenting the path of improvements, justify choices made.
More than one prototype can be made, tested and documented during this process.
This is the last stage of an R&D process. The output is a product, which is a functional thing. This process is about modifying the last and best working prototype, itself based on the best design. The output is a production recipe.
INPUT: prototype description
OUTPUT: Final prototype with user tutorials and repair tutorial. Report describing remaining limitations and future improvements.
See more on manufacturing recipes