Process: Milestone 2 - Design considerations to Deliver the Spider Rig starting 2018-09-03 ending 2018-09-10

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 Sept. 10, 2018

Unplanned Production:

Created: R&D report: SpiderRig - Milestone 2 Design doc 1.00 Idea Sept. 25, 2018

Work

Planned Work: (Requirements are ordered by due date)

Work - General product design: 20.00 Time - Hours due Sept. 3, 2018

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.

Unassigned
Work events:
Sept. 23, 2018 3.00 Time - Hours Done by Khalid

POZYX Board, Full Board Specification, Positioning duration and update rate of the reading data from the board, How to setup the board, how POZYX determine the position, Describe the main Interrupts used in POZYX board,describe in details the Register Map,Describe the main function of interface protocol,describe the main function (programming)that can be used to read data from the PROZYX board, finally, how to connect PROZXY shield with Arduino and how to program it.

Sept. 23, 2018 0.75 Time - Hours Done by Ahmed

A brief description of system components, and composing the section of electrical system based on the email discussion between Tibi and Alejandro

Sept. 23, 2018 0.50 Time - Hours Done by Ahmed

Proposing a system diagram that shows system components and how they integrate together

Work - R&D mechanics: 10.00 Time - Hours due Sept. 10, 2018

Design the mechanical layer of the SpiderRig device.

Unassigned
Work - Design Electronics: 10.00 Time - Hours due Sept. 10, 2018

Design the electronic layer of the SpiderRig device.

Unassigned
Work - Programming for product: 10.00 Time - Hours due Sept. 10, 2018

Design the software layer of the SpiderRig device, including the motion control algorithm (Alejandro and Aref).

Unassigned
Work - Meeting: 5.00 Time - Hours due Sept. 10, 2018

Meetings for better coordination

Unassigned
Work events:
Sept. 25, 2018 1.00 Time - Hours Done by Timx

Meeting with Tibi on structuring the Design approach. I proposed a nice framework, we implemented it and Tibi communicated to the group.

Sept. 25, 2018 1.00 Time - Hours Done by Tibi

Meeting with Tim on structuring the Design approach. Tim proposed a nice framework, we implemented it and communicated to the group.

Work - Facilitation and coordination: 5.00 Time - Hours due Sept. 10, 2018

Facilitation and coordination of the project

Unassigned
Work - Training self: 4.00 Time - Hours due Sept. 10, 2018

Spending time understanding the project and where and how to contribute
these contributions will be discarded is no other valuable contribution are made to the project

Unassigned
Work events:
Sept. 24, 2018 1.50 Time - Hours Done by Aref

Phone conversation with Tibi on the project.
Reading documents.

Work - Outreach-Marketing: 3.00 Time - Hours due Sept. 10, 2018

Send signals about progress and needs.

Unassigned
Work events:
Sept. 25, 2018 0.30 Time - Hours Done by Tibi

Revisited all the posts on social media (Facebook and Linkedin) and posted progress with a call for participation.

Process context:

Pattern: Change
Context: Spider rig
Order: Work order 278 for Deliver the Spider Rig due: 2018-09-11

Previous processes:

Milestone 0 - Project Administration to Deliver the Spider Rig starting 2018-08-21 ending 2018-09-30

Next processes:

Milestone 3 - Product design stage to Deliver the Spider Rig starting 2018-09-10 ending 2018-09-30


Process notes:

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