Transfers between ventures - Revision history

TiberiusB: /* Introduction */

2022-08-14T19:15:07Z

Introduction

TiberiusB: /* Introduction */

2022-08-14T19:11:23Z

Introduction

Sensorica-wiki at 03:13, 20 October 2021

2021-10-20T03:13:08Z

Sensorica-wiki: Sensorica-wiki moved page Value transfer between ventures to Transfers between ventures

2021-10-20T02:18:35Z

Sensorica-wiki moved page Value transfer between ventures to Transfers between ventures

Sensorica-wiki at 02:17, 20 October 2021

2021-10-20T02:17:19Z

Sensorica-wiki: Sensorica-wiki moved page Value transfer between projects to Value transfer between ventures

2021-10-20T02:12:41Z

Sensorica-wiki moved page Value transfer between projects to Value transfer between ventures

199.168.222.162: /* Introduction */

2014-03-30T17:12:49Z

Introduction

New page

This doc is a deeper reflection and an attempt to model value exchanges between [[projects]] within a value network.

=Our Material used in this attempt=
Use the vocabulary extracted by Bob ([https://docs.google.com/document/d/1LSt337DLqd_ndjt24XvgiRaN3AaMDQ-gdueUXucA0mk/edit#heading=h.i8zcydbly61d open Doc])

Use the [https://docs.google.com/document/d/1fERNK99y_3aMx5XgGirRa_76WMz3WhEInWORJ7zfBqg/edit Value System doc].
Use also other docs in the [https://drive.google.com/folderview?id=0BzrQyEif2HItZDI1NWE3YzQtOTBhNC00NDY4LWE3YzUtNjI0NGM4MDJkOWEz&usp=sharing SENSORICA/INFRASTRUCTURE] folder.

=Introduction=

At this moment there are 3 ways to transfer value from one [[project]] to another:
# Through child-parent relationships between projects.
# Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes).
# [[Recipes]] (to be explored...)

[[Projects]] are nodes nodes in a [[value accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[project]] level, where goals appear, therefore the [[value equation]] is applied at the project level too.

However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[projects]], therefore value passes between [[projects]] at the resource level.

[[Projects]] are modeled as static structures. Value is modeled as flows. Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen. The processes are where the actual value exchanges happen.

For example, the Mosquito project will last a long time. During that time, many Mosquitos will be created by many processes. The designs of the Mosquitos and the methods of making them may change many times, but the Mosquito project will be the context for all of them.

=Preliminary considerations=
==Categories of projects==
It is important to separate [[projects]] into categories because they can be so different that they need special treatment within the value accounting system. Moreover, different types of [[projects]] attract different types of individuals and tend to create specific cultures around them. That can lead to different group decisions in terms of evaluations of contributions and the value equation.

One idea is to categorize [[projects]] along the categories of business activities:
* [[R&D projects]] - uncertain, high risk, dynamic, chaotic, less structured, high degree of interdependence between them, sometimes the goal is not so clear, can lead to unexpected applications...
* Building - clear goal, less risky if well sourced, well-structured...
* Marketing and sales - ex. developing new markets
* add others...

=Papers to get and read=
[http://www.sciencedirect.com/science/article/pii/S0263786306000482 Managing collaborative R&D projects development of a practical management tool]

@@ Line 11: / Line 11: @@
 At this moment there are 3 ways to transfer [[valuables]] from one [[venture]] to another:
-# Through child-parent relationships between [[venture]].
+# Through child-parent relationships between [[ventures]].
 # Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes).
 # [[Recipes]] (to be explored...)
-[[Ventures]] are nodes nodes in a [[contribution accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[venture]] level, where goals appear, therefore the [[value equation]] is applied at the [[venture]] level too.
+[[Ventures]] are nodes in a [[contribution accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[venture]] level, where goals appear, therefore the [[benefit redistribution algorithm]] is applied at the [[venture]] level too.
-However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[ventures]] or [[projects]], therefore value passes between [[ventures]] or [[projects]] at the resource level.
+However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. [[Resources]] created by one [[process]] can be used within a different [[process]]. [[Processes]] can belong to different [[ventures]] or [[projects]], therefore [[valuables]] passes between [[ventures]] or [[projects]] at the resource level.
-[[Ventures]] or [[projects]] are modeled as static structures.  Value is modeled as flows.  Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen.  The processes are where the actual value exchanges happen.
+[[Ventures]] or [[projects]] are modelled as static structures.  [[Valuables]] are modelled as flows.  Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen.  The [[processes]] are where the  exchanges happen.
 For example, the Mosquito venture will last a long time.  During that time, many Mosquitos will be created by many processes.  The designs of the Mosquitos and the methods of making them may change many times, but the Mosquito venture will be the context for all of them.

@@ Line 10: / Line 10: @@
 =Introduction=
-At this moment there are 3 ways to transfer value from one [[venture]] to another:
+At this moment there are 3 ways to transfer [[valuables]] from one [[venture]] to another:
 # Through child-parent relationships between [[venture]].
 # Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes).

@@ Line 1: / Line 1: @@
-This doc is a deeper reflection and an attempt to model exchanges between [[ventures]] within an OVN.
+This doc is a deeper reflection and an attempt to model transfers (could be exchanges) between [[ventures]] within an OVN.
 =Our Material used in this attempt=
@@ Line 9: / Line 10: @@
 =Introduction=
-At this moment there are 3 ways to transfer value from one [[project]] to another:
+At this moment there are 3 ways to transfer value from one [[venture]] to another:
-# Through child-parent relationships between projects.
+# Through child-parent relationships between [[venture]].
 # Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes).
 # [[Recipes]] (to be explored...)
-[[Projects]] are nodes nodes in a [[value accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[project]] level, where goals appear, therefore the [[value equation]] is applied at the project level too.
+[[Ventures]] are nodes nodes in a [[contribution accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[venture]] level, where goals appear, therefore the [[value equation]] is applied at the [[venture]] level too.
 However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[ventures]] or [[projects]], therefore value passes between [[ventures]] or [[projects]] at the resource level.

← Older revision	Revision as of 02:18, 20 October 2021
(No difference)

@@ Line 1: / Line 1: @@
-This doc is a deeper reflection and an attempt to model value exchanges between [[projects]] within a value network.
+This doc is a deeper reflection and an attempt to model exchanges between [[ventures]] within an OVN.
 =Our Material used in this attempt=
@@ Line 16: / Line 16: @@
 [[Projects]] are nodes nodes in a [[value accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[project]] level, where goals appear, therefore the [[value equation]] is applied at the project level too.
-However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[projects]], therefore value passes between [[projects]] at the resource level.
+However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[ventures]] or [[projects]], therefore value passes between [[ventures]] or [[projects]] at the resource level.
-[[Projects]] are modeled as static structures.  Value is modeled as flows.  Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen.  The processes are where the actual value exchanges happen.
+[[Ventures]] or [[projects]] are modeled as static structures.  Value is modeled as flows.  Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen.  The processes are where the actual value exchanges happen.
-For example, the Mosquito project will last a long time.  During that time, many Mosquitos will be created by many processes.  The designs of the Mosquitos and the methods of making them may change many times, but the Mosquito project will be the context for all of them.
+For example, the Mosquito venture will last a long time.  During that time, many Mosquitos will be created by many processes.  The designs of the Mosquitos and the methods of making them may change many times, but the Mosquito venture will be the context for all of them.
 =Preliminary considerations=
-One idea is to categorize [[projects]] along the categories of business activities:
+==Categories of ventures==
-* [[R&D projects]] - uncertain, high risk, dynamic, chaotic, less structured, high degree of interdependence between them, sometimes the goal is not so clear, can lead to unexpected applications...
+It is important to separate [[ventures]] into categories because they can be so different that they need special treatment within the [[contribution accounting system]]. Moreover, different types of [[ventures]] or [[projects]] attract different types of individuals and tend to create specific cultures around them. That can lead to different group decisions in terms of evaluations of contributions and the [[benefits distribution algorithm]]. See more on the [[Venture]] page.
 =Papers to get and read=
 [http://www.sciencedirect.com/science/article/pii/S0263786306000482 Managing collaborative R&D projects development of a practical management tool]

← Older revision	Revision as of 02:12, 20 October 2021
(No difference)