View Workflow Recipe for R&D report

R&D report

Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA

R&D Report represented by a document of some type, describing the knowledge acquired and captures some know how needed to reproduce it.
This resource type is used in a workflow recipe for product development.
The workflow recipe is a formalized methodology, that allows you to plan the development process. This recipe works in combination with the Conditions for project recipe. See hos they interact in this diagrame
https://cacoo.com/diagrams/fYtiSKNAzJNwYABn#
See more on workflow recipes for R&D
http://valuenetwork.referata.com/wiki/Recipe#Workflow_recipe_for_R.26D

Ideation stage

Ideation is the first step in an R&D process. During this stage you create a rough description of what it is to be made, which responds to a specific need.

This stage is also called Concept Development": Identify Needs of target Market; Alternative concepts generated and evaluated; Refinement & Selection of the bests for further development and testing; (Concept - description of form, function and features accompanied by a set of specs, besides analysis of concurrents and an economic justification of the project.

OUTPUT: a description of the idea in the Main document of the project.

Inputs
work 2.00 HR Work - Writing
Work: Non-production work

Use the "Project main doc" document to briefly describe the main idea behind this project. Use this information to improve the Project page as well as the Project path to market page.
This description can contain sketches. photos, description of the thing to be made, needs it responds to or applications, etc.

Output
creates changeable 1.00 Idea R&D report@Ideation stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
Design considerations

NOTE: you need to create specific design processes here (Design electronic, mechanical, optical or other)

This is a high-level design effort to take into consideration a few important elements. Note that these elements maintain important relations and they cannot be considered on an individual basis.
* Ecosystem: A reflection about standards to be used, based on a map of the ecosystem this product will be part of. The goal is interoperability.
* Lifecycle: A reflection about how this product will be used and who it will end its life. Is it modular and used in conjunction with other things (see System)? Is it a "perpetual product" (i.e. the user is able repair and to update/upgrade it) and if so, how easy it is to be updated/upgraded? Will it be possible to recycle parts of the product to be used in other applications once the product becomes obsolete? Is it recyclable? Is this product meant to be shared by a group of individuals during its lifetime?
* Business model: A reflection about how the product is generating value for the community that designs and supports it. Is the value capturing mechanism based on service? Is this a product that is owned or rented? Is the product serviced on site or remotely? Is this product labeled as a sustainable product (local, ethical, environmentally friendly).
* Manufacturing: A reflection about supply chain and fabrication. What are the optical supply chain and parts in order to reduce cost and environmental impact. What the best fabrication technology/method? How important is quality?
* System: a reflection about how the thing will be put together.
* Environment: A reflection the environment in which the product will evolve
* User effects: a reflection about how the product is handled by the user and how the user can affect the integrity of the product

INPUT: idea
OUTPUT: Design considerations - a file

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)
* Sustainable

See product design philosophy doc
https://docs.google.com/document/d/1EbfyREvQKAtkdz24_NVzosf4f5t6WatMPy5mDsbD0PA/edit#heading=h.k03aelklyu2x

We should always tink larger than the project. There are different dimensions that we can identify.

! Synergy with other SENSORICA projects
! Spinoffs (modules that can take a life of their own)
! Parallel opportunities
! Network building - cohesion, activity level, energy...
! Network of network consolidation - build bridges with other networks
! ...

Inputs
to be changed 1.00 Idea R&D report@Ideation stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
work 20.00 Idea Work - General product design
Work: Design work

This is a holistic approach for design. the output is a document describing design characteristics that take into consideration the output of the Design consideration stage.
The actual design work will be done in the next stage.

Output
changes 1.00 Idea R&D report@Design considerations
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
Product design stage

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)
* Sustainable

See product design philosophy doc
https://docs.google.com/document/d/1EbfyREvQKAtkdz24_NVzosf4f5t6WatMPy5mDsbD0PA/edit#heading=h.k03aelklyu2x

Inputs
to be changed 1.00 Idea R&D report@Design considerations
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
work 20.00 HR Work - Design Electronics
Domain: Electronic, Work: Design work

This is a process for considering design characteristics for the electronics layer of the product.
If this process if the product doesn't have any electronic components.
The output of this process is a design file.

work 20.00 HR Work - Design mechanical
Domain: Mechanical, Work: Design work

This is a process for considering design characteristics for the mechanical layer of the product.
If this process if the product doesn't have any mechanical components.
The output of this process is a design file.

work 20.00 Idea Work - Design optical
Domain: Optical, Work: Design work

This is a process for considering design characteristics for the optical layer of the product.
If this process if the product doesn't have any optical components.
The output of this process is a design file.

work 20.00 HR Work - Programming for product
Work: Software development work

This is a process for considering design characteristics for the software layer of the product.
If this process if the product doesn't have any software.
The output of this process is a link to the repository of the code, github or other.

Output
changes 1.00 Idea R&D report@Product design stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
Prototyping stage

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: a detailed description placed in the main document

More than one prototype can be made, tested and documented during this process.

Inputs
to be changed 1.00 Idea R&D report@Product design stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
work 5.00 Idea Work - Documenting
Work: Non-production work

Documenting the prototype, its characteristics, behavior, functioning, observations, lessons learned, etc.

work 23.00 HR Work - Engineering
Work: Engineering

Assembling and testing of prototype.

Output
changes 1.00 Idea R&D report@Prototyping stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
Manufacturing stage

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, in order to fit manufacturing processes, and product design requirements, informed by a marketing research. The output is a production recipe.

This process is also known as Production Ramp-up: The product is made by using the intended production system. The purpose of the ramp-up is to train the workforce and to workout any remaining problems in the production processes. Products produced during production ramp-up are sometimes supplied to preferred customers and are carefully evaluated to identify any remaining flaws. The transition from production ramp-up to ongoing production is usually gradual. At some point in this transition, the product is launched and becomes available for widespread distribution. A postlaunch project review may occur shortly after the launch. This review includes an assessment of the project from both commercial and technical perspectives and intended to identify ways to improve the development process for future projects.

INPUT: prototype description
OUTPUT: manufacturing recipe

See more on manufacturing recipes
http://valuenetwork.referata.com/wiki/Recipe#Manufacturing_recipe

Inputs
to be changed 1.00 Idea R&D report@Prototyping stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA
Output
changes 1.00 Idea R&D report@Manufacturing stage
Deliverable: Document ideas, Domain: Any R&D, Source: SENSORICA