Version: 1.09 Last modified by _dm on April 1, 2010, 2:47 pm
Table of contents:
I. Vision, Mission & Values II. The Plan ..1. Course of action ....1.1 Introduction & Analysis ....1.2. Overall Plan ..2. Global structure ....2.1 Functional ....2.2 Formal & Legal III. The Protocol ..1. Basic Structure
2. General Policy ..3. RBEF strategic coordination center - the Engine Unit ..4. RBEF Operational Level: Groups..
5. RBEF Operational Level: Projects IV. Legal Structure, NPOs network ..1. Global RBEF ..2. Country NPO ..3. Auxiliary Business Projects V. Other and provisional rules ..1. Forum rules and creating new groups ..2. Users Expiration Policy VI. Related documents
I. Vision, Mission & Values
VISION The RBE (Resource Based Economy) Foundation is created from the ground up within the monetary system, using existing legal and financial mechanisms. Through the coordination of multiple activities, tasks, projects and organizations in a fully transparent way, the RBE Foundation provides resources (including funds) and a coordination platform for various projects and organizations aiming at the research and introduction of a global Resource Based Economy.
MISSION The RBEF exists as a tool for RBE Projects during the transition period and provides the necessary resources and funding. According to the principles, all work shall be done on a voluntary basis where possible. All acquired resources (including money) shall be redistributed among the RBE projects. RBEF is a link between the current monetary based system and the future resource based economy. RBEF is a redistribution and accounting center for all projects which require and/or generate resources. All decisions concerning the funds and management shall be as automated as possible based on algorithms devised in a scientific way in order to achieve 100% transparency about the funds. The RBEF shall exist as long as money is necessary and an irreplaceable resource for the start, efficient operation, and development of RBE Projects.
VALUES » Resource Based Economy - foundation exists solely because of and for the RBE Projects and Organizations. » Scientific Management - management of the Foundation should be left to the system rather to the human decisions. The operations which can be automated shall be automated and computerized as soon as possible. » Transparency - All funds are fully transparent from the moment they enter the system to the moment that they are spent. The organization and processes of the RBEF and associated organizations are transparent in all their aspects embracing e.g. decision making, team setup, team membership, responsibilities, documentation, property and other not listed aspects. On request of members, undocumented or not yet shared aspects should be published and shared promptly. » Automated Funds Distribution - distribution of the funds shall be done in an automated and pre-defined way, leaving no space for individual human decisions and errors. » Respect - for everyone, their opinions, abilities and work and that these are incomparable, and if, that they have the same value. » Free Resources - we utilize free and open content, licenses, services, hardware and resources.
II. The Plan This section describes the plan how we intend to realize the vision. It is important to notice that the development, testing and introduction of the exact and precise plan will be the task of the Experts group. As for now, the plan covers the path how we can get there ( create such a group) and it is the primary goal for the RBEF at the moment of writing.
1. Course of action Below is the simplified graph illustrating the intended process and the time line:
Attachment:
RBEF CoA timeline.jpg [ 56.64 KiB | Viewed 180 times ]
1.1 Introduction & Analysis 1.1.1 Ultimate goal The goal is to construct and apply a new type of world-wide social-economic relations (so-called Resource Based Economy). The questions are: what is it and how to get there? Problems: a) There is no strict definition of RBE, only a set of ideas plotting the general way b) There is no plan of achieving the goal c) There is nobody organized to do this plan (out of the frames of this document)
1.1.2 Goal definition Strict definition of the target point should be declared. From the current point of view it can be said, that the goal is rather a mathematical limit than a point. Thus we can constantly approach to it, but never truly achieve. Although the last claiming can be disputable, the main idea is that we need a dynamic mechanism which is designed according to constantly optimize proper parameters.
1.2. Overall Plan Goal achievement plan is in a strong connection to the target system itself. It is necessary to analyze the current situation, possibilities, requirements, predict consequences. Declare step-by-step plan with schedule and milestones. Problems: There is nobody to do this work currently. Solution: Creating the experts group.
1.2.1 Experts It is necessary to find and recruit a number of experts in areas: mathematics, economics and sociology. Orienting requirements to candidates: 1) High education degree preferred 2) Understanding of social-economic systems in general 3) Understanding and supporting the goal 4) Understanding the current world situation Problems: Motivation We cannot rely on voluntary job basis here, even if individuals fully support the goal, they should be motivated to spend the time on proper tasks and complete them efficiently. Solution: The only motivation mechanism we can have currently is the monetary supply. Problems: Funding Solution: - Creating the structure able to accept, accommodate and redistribute resources. - Creating auxiliary business projects and donations system. Problems: Management and the overall coordination Solution: Engine Unit
1.2.2 Engine Unit Note: the full description and rules for the EnU is described in the other section. The main purpose for the Engine Unit is the overall coordination of the RBEF and realization of the plan, especially coordination of auxiliary projects and the creation of the Experts group. Problems: Management of the projects and overall coordination Solution: Project Coordinators in contact with Engine Unit
1.2.3 Coordinators Note: the full description and rules for the Coordinators is described in the other section. Every Project shall have the Coordinator(s) who is in charge of this particular project, communication with EnU and realization of the project's goals. Important thing is that the project is independent entity and EnU is just to coordinate the whole group effort and ensure the efficient work. EnU is rather a supprt to the projects rather than management.
2. Global Structure
The conclusion from the above analysis is that we need some sort of the global structure which would describe the relations between different RBEF entities. RBEF structure is represented by two interconnected layers:
Functional structure This is the place where all the RBEF people are concentrated. Functional structure is at one abstraction level higher than Legal structure, thus people are not pinned to their locations to perform tasks (except cases when these tasks are pinned to some locations).
2. Legal structure This level represents RBEF Legal entities in the current world legal system
RBEF Central (global) This node is the base of the legal network, its coordination and resource (inc. funds control) center.
RBEF Countries (local) These nodes (in form of NPOs) exist in separate countries as legal representatives of RBEF, thus any legal entities of these countries may interact with RBEF (such as businesses, governments, other foundations, people, etc.)
In the sections below you can find graphs illustrating these layers. Detailed regulations and procedures are described in the section III. The Protocol and IV. Legal Structure, NPOs network accordingly for functional and legal layers.
2.1 Functional Structure This structure describes the functional connections between different organization's elements:
2.1 Functional Structure Here we have: Engine Unit – Overall coordination, strategic decision center, support for all projects. Section – Functional part of the organization Group – RBEF members working together over the same, similar or related projects and issues. Project – mid-term activity withing group, having a schedule, declared goal and necessary resources Team - several members within the group with specific skills / knowledge (eg. graphic designers, engineers etc.). At the same functional level as projects. Tasks (not shown in the picture above) – short-term activity to be done within project or group, usually by one member
Complete description of the groups will be given in another document, but it is already clear how are analysis structures mapped into this scheme.
2.2 Formal & Legal Structure Formal connections and the legal status of the different units making the RBE network / RBEF
Global RBEF - registered NPO, acting as a central hub linking other NPOs through the formal agreements and ensuring the transparency of funding and operations. Engine Unit members - formal members of the Global RBEF, performing their duties based on agreement. Expert's Coordinators - formal members of the Global RBEF, performing their duties based on agreement. Experts - formal members of the Global RBEF, performing their duties based on agreement. Global Projects (and coordinators) - projects on the global scale, formally run by the Global RBEF with coordinators being members of it. In special cases they can be run by local NPOs, based on the agreement. Country's NPO - formal structure inside the country running all aspects of RBE in the given country. The level of cooperation is described in the formal agreement between NPO and the Global RBEF. Local Projects under the Country's NPO - projects with the range limited to one or several countries, local projects, but still with fully transparent funding registered at the central database. Auxiliary Business Projects (AuxBiz) - third party ( projects or companies not being the part of the RBEF structure, including government grants ) supporting the RBE. Every donations shall be registered and every agreement transparent.
III. The Protocol The Protocol is the set of rules organizing the RBEF work and decision making process. It can be perceived as a kind of RBEF constitution / set of rules and internal laws.
1. Basic Structure
1.1 The structure of the RBEF has two main levels: - Engine Unit - strategic coordination center - Operational level - all other groups
1.2 Operational level is mainly independent in its operation, nevertheless there is a need to coordinate and communicate its activities through the Engine Unit (or
provided platform) to ensure the overall efficiency of operation.
2. General Policy
Any RBEF functional unit – Engine Unit or Groups follow the following rules:
2.1 Transparency All Group operations are absolutely transparent to everyone, including none registered RBEF visitors. RBEF tools that are provided ensure complete transparency and to certain degree organization. If the Group operates with tools not provided by RBEF, not much activity will be observed in the Group, thus Engine Unit or Coordinators may require to increase amount of summaries Group needs to submit.
2.2 None-Intervention Policy None-Intervention Policy sets the tone about each Group's work as well as resolve many issues that may arise. The Engine Unit cannot be experts in every possible field, thus they cannot dictate what kind of experts each Group needs. This means the Engine Unit cannot dictate what new members a Group has to accept, or how the Group should behave towards any other Group (not to mention any direction the Group has to take). It is up to the informal group leader (informal to RBEF) or Group Coordinator to run the Group or Project.
2.3 Tools - Each Group is obligated to use all the tools RBEF provides (except the AuxBiz Projects, not being part of the RBEF structure, where using the tools is optional and specified in the individual agreement). Group Coordinators may put forth requests concerning the organization of the forum, for instance which sections are accessible to everyone or to Group Members only. Group Coordinators may request to have an E-Mail, Documentation Management and set the rules who has the access to these tools in the Group. - If any of the Groups require Tools RBEF does not provide, development of such a Tool can be arranged with "RBEF Development" Group.
3. RBEF strategic coordination center - the Engine Unit
3.1 Description: The EnU is the global strategic decision and coordination center. The Engine Unit can also be perceived as a strategic decision and direction (coordination) center for project's coordinators - making sure that all projects work together efficiently. The Engine Unit is logically divided into four general sections: Administrative, AuxBiz, AuxDev and Research. Each section is under a direct control of assigned EnU member(s).
3.2 Functions: The primary function is making decisions concerning RBEF as an organization and preserve effectiveness of RBEF's operations. Decisions are made by 100% agreement of 100% members of the Engine Unit.
3.3 Responsibility: The EnU as a whole is responsible to itself to be efficient and productive. According to preserve the effectiveness of EnU operations, every member is obligated to: 1) Participate in decision making (as 100% votes is needed) 2) When participating in decision making, vote positively if no objections can be formulated 3) Consult other members of the EnU if a prolonged period of absence occurs 4) Do assigned tasks (if any) according to schedule 5) Support and help the evolving of the Operational Level as a main priority
3.4 Regulations:
3.4.1 Membership: - Anyone at any time can apply to become a member of the Engine Unit. - EnU members then review the candidate and make a decision. - if at any time the total number of EnU members exceeds 8, then the EnU shall either remove one of the members (with 100% agreement, including the removed
person) or restructure itself by splitting and assigning different responsibilities. This rule is to ensure the ability for efficient work and the ability to grow.
3.4.2 Removal of the EnU member (or suspension): - by voluntary declaration - on the event of lack of activity (1 month without login) - on the event of lack of activity (login, but no reply for more than 2 weeks) - continuous violation of responsibilities (more than 50% of assigned and accepted task are not completed as per schedule with no mitigating circumstance ). If the before mentioned events take place, the member will be banned from activity until all other EnU members agree to reactivate him. If consensus is not
achieved, this member will be excluded from the EnU 1 month later. If a member failed with a personal task, another member should be assigned to this task
(task - any Execution Unit position or Engine Unit project activity).
3.4.3 Vacation An Engine Unit member can activate the Vacation mode. In such a case his vote won't be counted for the required 100%. He also cannot be removed from the EnU during the vacation period (by default see point 3.4.2). At any time passed the 90th day any of the EnU can propose a vote to put the missing EnU member into Absence mode.
The EnU member returning from Vacation has the right to "veto" any resolution passed during his absence. In such a case the resolution execution shall be postponed until a consensus is reached. 3.4.4 Absence In case of longer absence (more than one week) the Engine Unit member automatically enters Absent mode. In such a case his vote won't be counted for the required 100%. Note, that unlike in Vacation mode, the member can be removed according to 3.4.2. The EnU member has the right to "veto" any resolution passed during his absence. In such a case the resolution execution shall be stopped until the consensus will be reached.
4. RBEF Operational Level: Groups
4.1 Description: This is the Level for the realization and execution of the RBEF strategy and goals through projects. Main units on this level are the Groups. Every Group is created in related section and is responsible to the Section's coordinator (EnU member). Group coordinators may not be from the EnU, but they must be approved by EnU.
4.2 Functions: 4.2.1 The general function is to oversea and realize either the appointed projects/tasks and/or the whole area of responsibility. 4.2.2 The main purpose is to have a Group with specific knowledge/interest in the topic to conduct operations in the specific area. 4.2.3 The specific function of the Group is defined at the moment of the Group formulation. 4.3 Responsibility: 4.3.1 The specific scope of responsibilities is defined at the moment of the Group formulation. 4.3.2 The responsibility shall be either realization of the specific goal in the specific time or the responsibility of the defined area.
4.4 Regulations:
4.4.1 Group creation procedure 4.4.1.1 The Group is created by the resolution of the Engine Unit 4.4.1.2 Resolution shall include: - the scope of the responsibility and specific Group function - the Group structure - the structure shall include at lease one Group leader(s) or contact window - the timetable ( in case of time-limited tasks ) 4.4.1.3 Creation of the Group can be also proposed by the any member of the RBEF directly by posting in the appropriate section of the forum or by sending the email to the engineunit@rbefoundation.com. 4.4.1.4 In case if the Group is proposed by a member, then the proposal shall include the suggested elements mentioned in point 4.4.1.2
4.4.2 Group removal procedure 4.4.2.1 Group ceases to exist on event of: - Resolution by the Engine Unit - pre-defined criteria included in the Group creation resolution, especially time, reaching the team objectives.
4.4.3. Group product 4.4.3.1. Groups are free to make any product, under corresponding Coordinators supervision. 4.4.3.2. The product is applied to RBEF and recognized as official by default. 4.4.3.3. Engine Unit may set veto on any product by proposal. 4.4.3.4. The product (with exception for EnU) which has significant influence on RBEF procedures or external affairs should be published in special internal informational section, in the same time points 4.4.3.2. and 4.4.3.3. are applied. Note: this mostly touches the Administrative Section.
4.4.4 Follow up 4.4.4.1 Every Group shall be included into the Group registry. 4.4.4.2 Engine Unit member who proposed the resolution is in charge of updating the registry by: - adding the Group after resolution passing - removing the Group after it ceases to exist
4.4.4.3 Each group is accountable to the Group Coordinator and/or to itself to deliver the best/promised results. No external entity will force the Group to action in a certain direction (see None-Intervention Policy), yet the RBEF requires the delivery of the best/promised results to further its existence. This should count as a personal incentive to motivate team members in their efforts. 4.4.4.4 The results RBEF expects from the Group is negotiated with the EnU upon the agreement. On top of delivery of promised results, each Group is obligated to summarize their work for public review. Upon registration, each Group will be given a Thread in the main forum, section Work Summary. Group Coordinators are required to submit the summary of work Group done every 3 months (4 times a year) if not stated otherwise.
4.4.5. Communication procedures 4.4.5.1. Requests to all
functional units of RBEF should come from other functional units of
RBEF, including: group/project/section coordinators and EnU resolutions.
These requests are suggested to process. 4.4.5.2. Any private
request from any person, that is not qualified as a
section/group/project coordinator request and not an EnU resolution,
should be considered by the requested entity as informal suggestion and
their processing is not required, but left on appropriate coordinator's
decision. 4.4.5.3. Requests from EnU resolutions has more priority
over other requests (but decision about priorities is left to the
requested entity, according to the None-Intervention Policy (III.2.2)),
and in the same manner go section, groups and projects requests. 4.4.5.4. All official requests between functional units will be done
via the RBEF forums.
5. RBEF Operational Level: Projects
5.1 Description:
The activity of the RBEF is mainly carried out by the projects within Groups. The whole structure is project-oriented as this is how the RBEF is achieving its goal.
5.2 Functions:
The function of project is to realize a specific task, advancing RBEF towards its goal.
5.3 Responsibility: 5.3.1 The specific scope of responsibilities is defined at the moment of the project formulation. 5.3.2 The responsibility shall be a realization of the specific goal in the specific time or performing specific activity during some period of time.
5.4 Regulations:
5.4.1 Each project must be 100% legal in the country it is being run from and must obey international laws if being done as a multinational cooperation. 5.4.2 All projects must have realistic and achievable goals. 5.4.3 All plans shall be subscribed via a special template and then, after acceptation, published. 5.4.4 Every project needs to have coordinator(s) who are fully responsible and in charge of this particular project and the realization of its plans. After project and coordinator acceptation by the Group Coordinator the project team is free to chose the best way to achieve its goals (i.e. internal management).
6. External affairs
6.1. Sections and Groups are free to create unions/partnerships with different external entities with the following conditions: 6.1.1. Area of partnership is limited by functions of corresponding Section or Group 6.1.2. Partnership is approved by corresponding Coordinator 6.2. Decisions about global partnerships of RBEF with other entities should be taken by the Engine Unit via standard procedures.
7. Supervisors Group
7.1. Description: As the organization grows it starts to be difficult to pay attention to everything going on yet preserving own productivity level. For this reason RBEF functionally is divided into Sections to keep an eye on particular areas, but this also is needed to be controlled in sense of following official rules and procedures. Thus we need a separate auxiliary group of members whose task will be to control the overall working process and notify if there are rules violation occasions.
7.2. Functions: 7.2.1. Regularly monitor RBEF forum posts and check for the rules violations (general forum rules, the protocol, other EnU resolutions). 7.2.2. Detect possible rules conflicts and weak areas. 7.2.3. Investigate claims of agreement breaches
7.3. Responsibility: 7.3.1. Work on daily basis, check all new posts. 7.3.2. Review posts to insure guidelines are being followed without overbearing censoring 7.3.3. Gather information of agreement breaches and report it to corresponding groups
7.4. Regulations: 7.4.1. Membership: Any member with good knowledge of RBEF rules and procedures. 7.4.2. Application: An applicant should be approved by at least one EnU member after interview. 7.4.3. Removal of membership: 7.4.3.1. EnU may remove a member from position within this group without declaring reasons by resolution. 7.4.3.2. Membership in the group is cancelled if a member was absent for 1 week. 7.4.3.3. A member may enter a Vacation mode on the term no longer than 1 month, after this he's considered absent. 7.4.3.4. A membership may be removed by the member's own wish.
IV. Legal Structure, NPOs network The RBEF global structure is based on the intended network of the NPOs / Foundations / Associations in different countries. It is also called the "RBEF network".
1. Global RBEF
1.1 Global RBEF is the central NPO, linking all NPOs and making the central hub for the RBEF activities. 1.2 In order to start operations inside the RBEF network, the legal entity should be created first in the given country to ensure the legality of the project and the transparency of funding. 1.3 Global RBEF is a coordination unit and the legal status provider for the projects with the global scope (such as Expert's group). In special cases the Country's NPO can also has this function.
2. Country NPO
2.1 Country's NPO means any organization with an officially registered legal status. 2.2 The main purpose of the Country's NPO is to oversee, coordinate and provide the legal status for the Projects and Activities inside the given country. 2.3 Country's NPO, after its creation, shall sign the agreement with the Global RBEF, which shall describe the formal relations, responsibilities and duties connected with joining the RBEF network, especially: - transparency of funding and cash flow . - level of coordination / independence, Global - Country's NPO relations detail.
3. Auxiliary Business Projects These are the Projects which are not part of the RBEF Network, but support it by providing funds and/or resources.
3.1 Every Auxiliary Business Project shall sign the formal agreement with the RBEF Network, ensuring the transparency of funds. 3.2 The signing unit depends on the scale of operation - in case of local companies (limited to one country or region) Country's NPO (one or more) is the legal entity signing the agreement, when in case of global corporations Global RBEF shall sign the agreement. 3.3 The same rule applies accordingly to the following situations and different types of resource providers: a) External Independent Funder - constant donations. b) External Independent Donor - one time donation. The donors and funders are free to chose the specific NPO to which they are willing to donate their resources. 3.4 This section deals with money and is a delicate issue; therefore the Engine Unit is obliged to create the detailed and transparent rules and procedures covering the above mentioned issues before signing any agreements.
V. Other and provisional rules
1. Forum rules and creating new groups
1.1 After acceptation the Project / Group shall receive a special section in the forum that can be used according to the Project's needs. 1.2 It is up to the Group Coordinators(s) to choose all parameters when registering the Group. As long as any other Group does not have the same name and/or color, Group Coordinator may use it. Group Coordinator sets internal policy for its Group. In case of multiple Group Coordinators, it is up to them to resolve any internal issues. 1.3 In case the Project already has a forum / communication platform, the RBEF forum shall act as a contact window for all other projects to see the progress. The project coordinator or anyone appointed by him is responsible for periodically updating the section by reporting the work progress / news.
2. Users Expiration Policy Users expiration policy addresses inactive registered user accounts and "cleans up" RBEF databases from records that are not beneficial in any way.
2.1 Un-Validated User Accounts Each newly registered account is given 10 days to validate via E-Mail. After this period the account is automatically deleted by RBEF Platform so new users may grab it. An E-Mail with notification will be sent to each un-validated account after 7 days of registration. 2.2 Validated User Accounts User account will be automatically deleted if all of the following statements are true: 1. Never made a post in the first 3 months and 2. Did not visit RBEF for more than 3 months and did not announce leaving in any way and 3. Is not a part of any Group
Contacts
Engine Unit
Public Forum
Activity Involvement
Organization
Groups
Your Resume
Engine Unit & Groups
General Discussion
Administrative Section
Global Cooperation Group
Information & Promotion Group
Business Section
Software Development
RBEF Development
Venux Project
Research Section
Administrators
Proposals
Resolutions
Website
Archive
Applications
Resolutions
Content older than 6 months
Advanced Search
by Group
Course of Action
by Author
Available funds: $0.00
Register
Forgot my password
Astronomy & Space
AOSDT / RBEF / RBOSE (08-02-2010)
Integration
Resume & Web of Trust
