SENSORICA Value Network
Show Help
Process: Milestone 1 - Design considerations to R&D plan for PV characterization starting 2015-06-16 ending 2015-06-30

If you were logged in and working on this process, you would log your work on this page.

Outputs

Scheduled:

R&D report @Design considerations 1.00 Idea due June 30, 2015
Completed: changes 1.00 Idea June 23, 2015
  Resource: R&D report: Design Considerations document for the PV characterization project 1.00 Idea

Work

Planned Work: (Requirements are ordered by due date)

Work - General product design: 8.00 Time - Hours due June 16, 2015

I will be interfacing between the client and the sensorica affiliates for tightly integrated product.

Also providing overall connection between various design teams to make sure that everyone is working towards a coherent, compatible and workable end product.

Taken by Abran
Work - General product design: 20.00 Time - Hours due June 16, 2015

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.
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#

Taken by Tibi
Work events:
May 14, 2015 0.33 Time - Hours Done by Tibi

Created the section in the design doc.
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.zcwgs9vzwhvn
And started to through some ideas in the table. This table was remixed from Barda project.

Work - General product design: 8.00 Time - Hours due June 16, 2015

I will be interfacing between the client and the sensorica affiliates for tightly integrated product.

Also providing overall connection between various design teams to make sure that everyone is working towards a coherent, compatible and workable end product.

Taken by Abran
Work events:
July 2, 2015 2.30 Time - Hours Done by Abran

Finalized recommendations on rotary encoders. Presented materials and updated milestone 1 official documents with it.

Work - Programming software: 10.00 Time - Hours due June 24, 2015

Explore design considerations for the PV Characterization device software. documenting here
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.vgic2ggfnmk9

Taken by Tibi
Work events:
June 26, 2015 1.20 Time - Hours Done by Tibi

Created two tables in the doc, on talking about basic commands and the other one about functions. I communicated this to Maria and John.
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.vgic2ggfnmk9
I also created a diagram showing connections between the gimbal, the lamp, a third party device and the computer, giving an idea about the entire system for integration.
I also wrote some ideas about uManager, as an open source software for integration.
I entered some considerations about open loop and closed loop control of gimbal motion.

Work - Design mechanical: 10.00 Time - Hours due June 29, 2015

exploring different mechanical designs and their characteristics, for gimbals and clamps, trying to find some existing shared models we could use in the project and to blend ideas

Taken by Daniel
Work events:
June 30, 2015 3.00 Time - Hours Done by Daniel

Looked at Clamp design ideas on Thorlabs, Thingiverse and 3D warehouse for the PV Cell sample-holder and other clamps in the system. Added pics and links to the Document, with some thoughts on the main designs. These arre not all the designs out there..

June 29, 2015 3.00 Time - Hours Done by Daniel

Been looking at different gimbal designs on Thingiverse and 3D Warehouse for easy download and integration. added some designs to the wrong document and Tibi copy-pasted them into the right one.

Work - Design Electronics: 2.00 Time - Hours due June 30, 2015

Defined pros and cons for different motor types

Taken by Jim
Work events:
June 30, 2015 2.00 Time - Hours Done by Jim
Work - Design Electronics: 3.00 Time - Hours due June 30, 2015

Further develop motor selection criteria for the project.

Taken by Jim
Work events:
June 30, 2015 3.00 Time - Hours Done by Jim

Further explained stepper motor theory and added details to doc

Work - Design Electronics: 10.00 Time - Hours due June 30, 2015

Think about electronic design, in collaboration with other affiliates.
Document in the Design and prototyping document.
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.u428yq3nlxrb

10 hours total time allocated for this part. If you take this task you can invite others to help you. The group can accumulate more than hours on this task, but the budget for this task will not increase. The funds allocated will be distributed to all the contributors in proportion to their contributions. Contributors can elect to have their extra hours accounted for fluid equity in the commercial version of the product.
See budget allocation.
https://docs.google.com/spreadsheets/d/1WtMcgn96mZZbb8nZ14ywIjrIZ6MPW5pc8zmueae0IqY/pubhtml#

Taken by Abran
Work events:
June 29, 2015 1.00 Time - Hours Done by Abran

Researched and presented material about encoders, their operating principles and pros and cons according to type.

Detailed study with final recommendations still in progress.

June 26, 2015 2.00 Time - Hours Done by Abran

Presented material for design considerations. Research on DC Motors, encoders etc

June 24, 2015 0.00 Time - Hours Done by Abran
Work - Design mechanical: 20.00 Time - Hours due June 30, 2015

Mechanical design considerations, to be documented here
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.ftgj4zdh1jzh

20 hours total time allocated for this part. If you take this task you can invite others to help you. The group can accumulate more than hours on this task, but the budget for this task will not increase. The funds allocated will be distributed to all the contributors in proportion to their contributions. Contributors can elect to have their extra hours accounted for fluid equity in the commercial version of the product.
See budget allocation.
https://docs.google.com/spreadsheets/d/1WtMcgn96mZZbb8nZ14ywIjrIZ6MPW5pc8zmueae0IqY/pubhtml#

Taken by Abran
Work events:
May 20, 2015 3.00 Time - Hours Done by Abran

Evaluated different configuration of pivoting points, mounting points, rotational and tilt angles for the PV mounting plate. Output was documented in the main project design document.

Work - Programming software: 10.00 Time - Hours due June 30, 2015

Design considerations for software development. This work will be documented here
https://docs.google.com/document/d/1N5Y3KgZOe4IVM0976p_UVjGnC5KRov9c7yFKBoioqjA/edit#heading=h.vgic2ggfnmk9

26.7 hours total time allocated for this part. If you take this task you can invite others to help you. The group can accumulate more than hours on this task, but the budget for this task will not increase. The funds allocated will be distributed to all the contributors in proportion to their contributions. Contributors can elect to have their extra hours accounted for fluid equity in the commercial version of the product.
See budget allocation.
https://docs.google.com/spreadsheets/d/1WtMcgn96mZZbb8nZ14ywIjrIZ6MPW5pc8zmueae0IqY/pubhtml#

Taken by Maria
Work events:
July 28, 2015 0.30 Time - Hours Done by Maria

review and add to design document

June 25, 2015 1.30 Time - Hours Done by Maria
May 26, 2015 2.50 Time - Hours Done by Maria

Design considerations of software applications. Work was entered in design document on May 26, 2015.

Work - Design Electronics: 3.00 Time - Hours due June 30, 2015

Researched and added to the doc a detailed study of using Inertial Measurement Unit and Attitude Heading Reference System as a feedback mechanism or closed loop motion control.

Taken by Jim
Work events:
June 30, 2015 3.00 Time - Hours Done by Jim
Work - Programming software: 1.50 Time - Hours due June 30, 2015

Created structural chart for embedded and client software and to design doc. Will continue to add modules proposed by Abran, John and Maria for graphical representation.

Taken by Jim
Work events:
July 1, 2015 4.00 Time - Hours Done by Jim

Designed a block diagram defining the basic structure of the the software systems for the PV characterization device and added it to the main design doc
https://www.lucidchart.com/documents/edit/f815457e-7465-4bd6-a894-36540101a9a5?shared=true

June 30, 2015 1.50 Time - Hours Done by Jim

Unplanned Work:

Work event: Work - Design mechanical 5.00 Time - Hours July 2, 2015 Done by Daniel

Made some 3D sketches for possible setup configurations. The goal is to clarify with the client what configuration would work best and would be simplest.
This exercise helped us (Jim, Tibi and me) visualize and simulate Gimbal movement and light projection angles onto the PV Sample. And possible hardware configurations.

Work event: Work - Design mechanical 2.00 Time - Hours June 30, 2015 Done by Jim

Add to the design doc

Work event: Work - General product design 2.00 Time - Hours May 16, 2015 Done by Abran

Facilitation with creating work space for the PV project.
Provided brief overview of what the project entails and what kind of systems can be used to reach our end-goal.

Process context:

Pattern: Documentation
Context: PV characterization
Order: Work order 164 for R&D plan for PV characterization due: 2015-07-12

Previous processes:

Ideation stage to R&D plan for PV characterization starting 2015-06-18 ending 2015-06-20

Next processes:

Milestone 2 - Product design stage to R&D plan for PV characterization starting 2015-07-03 ending 2015-07-17


Process notes:

NOTE: you need to create specific design processes here (electronic, mechanical, software)

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
! ...