Deisgn logo and video intro for Verdun project
Log time spent on structuring the process, making sure that everyone is on track, well informed, help contributors find stuff and execute tasks.
Log here all the time spent writing the proposal.
log here all time spent in meetings.
Work any work related to communication strategy, project strategy, etc.
Log work done on spreadsheets on budgeting, cash flow, etc.
It is important to understand the role of SENSORICA, the p2p economic model behind, [put everything into context. This is why strategic considerations are important.
Log time here is you spend time learning about how things work in SENSORICA cash flow system. Ask Tibi if you have questions.
Log here if you will have meetings for coordination this work.
Log here the time you spend working with the Spreadsheet.
Find the grant proposal by participating to the OpenIDEO challenge
Re-format DEC proposal and other Sensorica presentations
Go to the Nesta event in London to meet teams of innovators.
Write a ressource allocation document to explain how the grant will be udes by Sensorica.
Design of the transmitter & receiver circuits.
Whatever is required/
This is about creating and maintaining relations with potential partners of the project. It goes through email communication, social media communication, phone calls, meetings, etc.
give a presentation
Create different scenarios and associated budgets. Document at the following link:
This is about creating virtual spaces for collaboration, like setting up a webpage, a folder for documents, for adding the project into the NRP-VAS, etc...
Creation of documents, forms, etc...
Time spent building a team to work on this funding and recruit new contributors.
Time you spend familiarizing yourself with new concepts and processes, whatever makes you more effective. ATTENTION! ff you quit the project and don't use what your new knowledge or know how other affiliates might raise a RED flag and propose to eliminate your contribution from the redistribution scheme.
Helping others find stuff, make sure that everyone knows what to do and when
See also Writing.
Time you spend documenting your work. Documentation happens in this doc.
Time you spend in meetings with other collaborators for this initiative.
Time you spend looking for stuff on the Internet and within the SENSORICA documentation, you need to document that well, leave traces, show others that you actually did the work, and allow them to build on your work.
Time you spend on the organization / group behind this project.
Time you spend training new collaborators to become productive for this initiative.
Time spent for the redistribution of benefits, value equation, etc.
Talk to Tibi or Jim.
Time you spend writing the proposal.
Upload blockchain stack configurations here: https://github.com/Sensorica/Interspace-Access
Analyse the information gathered by different affiliates and extract the essential, produce synthesis, reformat in a more coherent way, extract next steps of the project from it.
Help affiliates get up to speed with the work done here.
Search information sources for pertinent information, filter and curate.
If you read and document log that under documentation.
You can use Diigo
with Tags "blockchainaccess_project" and "paper" or "book"
You can also use other tools to build a list of references.
NOTE that this work requires reading. Log all time spent, but just make sure you justify.
Create summaries of your reading, in a way that you can save time to other affiliates, if they want to integrate the same information.
While documenting, also think that your summaries can be picked up in reports.
Other will use your summaries to analyse and strategize.
Log time spent on meetings here. Mention the people you were in a meeting with and link to a meeting notes doc.
Log time spent on documentation.
PCB Printing x 10, meaning one hour each.
Task for Jim.
Message for Jim : try to make on PCB in one hour?
PCB Design Updates. A total of 10 hours, but let's take 5 for this second iteration, since we are only making one more node, and reserve the other 5 for a future iteration.
Online or physical shopping activities.
Producing a Bill of Materials. Total is 10 hours, but let take 5 to complete and update for this iteration and reserve other 5 for the next iteration.
Testing the new node on site.
This is a task for Dave, to finish the design and 3D print a second box.
This needs coordination with the people working on the electronics.
NOTE: we need to integrate wire connectors in the box - ask Tibi, Jim or Scott.
Scrum meetings at the partner's location, or between sensoricans, concerning the project.
Present, explain, demo a sensor, a prototype, a software, something technical about the project to someone at the sponsor.
Training someone on different aspects of the project.
Solving more difficult technical problems, troubleshooting, repairs that require some in-depth knowledge, but not in the context of a precise, pre-planned task.
Solving less difficult technical problems, troubleshooting, repairs that require some in-depth knowledge, but not in the context of a precise, pre-planned task.
Technical support work
Technician work is work that doesn't result in the design of something new, or doesn't require high skills like for example for debugging a circuit or a program. Example of activities are: soldering, wiring, connecting and arranging things around, ...
Documentation work is about capturing the essence of activities in order to pass it on to other collaborators and stakeholders. Documentation MUST be shared with your peers and you need to drop a link with your log. Documentation can be text, video, pictures, or a mix. It also must be relevant to the project.
Render SENSORICA docs non publishable.
Requires new project governance, segregation of documents into public and non-public ones
Prepared a load cell using semiconductor composite material for testing, polished surface of electrodes. Tests on the device was performed the day after.
Only for work done on the Vibration sensor
(4H) Wrap everything up into a comprehensive document and link this information in other documents of the project
Only for work on the Distance sensor
(4H) Connect selected hardware together as explained in solution outline and verify signals responds as expected
(1H) Create outline for software implementation
(5H) Interface the displacement sensor with the Sensor Node at the firmware level
(1H)Make adjustments to the cloud communication software in order to accommodate this new sensor.
(3H) Test this new sensor in a real life situation with the rest of the system
See doc for estimations
Someone who organizes an event, like the Grand opening, logs time.
This is for people who do the budgeting, who take care of the NRP-VAS, who do the money distribution, etc. Mostly for CAKE administrators, or whoever else wants to help.
You actively participate in a meeting? Log your time here.
Here you log time recruiting new contributors to this video project.
This is where those who work on the video, shooting, editing, or sound log their time.
Anything related to documentation is logged here. For example, taking notes during a meeting, or during a Workparty, updating the Coordination doc, etc.
Documentation is VERY important in order to work stigmergically!!
This is about writing the storyline, the video script, etc.
Valentin and Valentin can log here.
Building SENSORICA landing website
Documenting the prototype, its characteristics, behavior, functioning, observations, lessons learned, etc.
Assembling and testing of prototype.
Write the Arduino code.
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.
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.
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.
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.
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.
See governance about spending commun funds
I can start or add to a Google Doc with spreadsheets. Vas newbie
See governance for important tasks
Acquire new skills. You might want to document something if you discover something new, or update the training manuals or the documentation that the network is using.
Doing outreach, seeding individual emails to people you know, setting up and attending meetings with people, all that with the goal of getting more people to work on the project.
You need to present a short description of what you did when you log.
Searching for information, designs, prototypes, doing some background checks, search prior art, ...
You need to save that search in a document and store it in the project folder (or any other location that is shared with all the project affiliates) and link to it when you log.
Looking for something to purchase, online or offline. Gathering, comparing and analyzing information about a product to purchase. Might require communication with salesman, even meetings. Might also require traveling. In the end, the agent makes a choice, issues a recommendation and/or purchases the product.This activity doesn't necessary need to result in a purchase.
You need to document the options you found somewhere where people can easily find them, and link to it when you log. The idea is to allow someone else to continue the job, or to provide feedback.
Administration activities around projects.
Stigmergy is part of our functioning, meaning leaving as many traces of your work as possible, including instructions for those who might want to build on our work.
You must document in a place that everyone agrees and can find. The documentation must be open to All affiliates to edit.
Participating in a gathering to discuss, plan, analyse, etc. Might require some traveling. Meetings can also be virtual. Might require documentation and further communication.
Helping others acquire new skills.
Facilitation means guiding affiliates, helping them with technical issues, navigation issues, administrative issues, ... helping
Information mining for AWS:
Best practices - architecture - cost efficient design - solutions integration.