15-04-2023, 11:07 AM
(This post was last modified: 13-01-2025, 08:19 PM by Emlar Racta.)
Accessing Public File; Downloading from 'Sith;Sarias'Download Complete; Displaying File:
The Research Bureau is an initiative founded to address the matters of Research and Development, striving to function as a 'nexus' for it among the many branches within House Horuset. To facilitate a functioning Bureau that creates effective research, development, education and results. It is a a joint effort between branches of the powerbase and members of the Bureau to see projects created and carried to completion.
Bureau Structure
Designed to work with multiple branches of the powerbase at once, the Bureau is established around a structure to avoid unneeded bureaucracy. Upkeeping regular contact with the branches of the powerbase, it will advice, propose and upkeep a continuous open dialog of potential projects.
Bureau Leadership
The leader is responsible for deciding on which projects are officially sanctioned by the Bureau. They decide which projects are approved. They also run the branch, overseeing communications and ensuring each project has the right hands working to it. Additionally, they sanction affiliates and ensure their offered resources are put to appropriate use.
Branch leaders are not Bureau Leadership by default, but they are the ones deciding what their branch brings forward per month. They are also, by default, who the Bureau will conduct meetings with on a regular basis - unless Branch leadership decides to delegate it to another member.
Currently, Sith Sarias is the assigned Head of Bureau.
Bureau Members
Bureau members are members of the represented branches and also members from outside of the officially associated branches who wish to join. These people work together on projects and are sometimes assigned leadership of their branch’s project, or Bureau projects as a whole. They report to Bureau leadership directly.
Bureau Affiliates
These are those who offer resources, support, and other non-specific skills for the research projects. They need not be members of the Bureau or a specific branch.
To become an Affiliate, one need only approach the Head of the Branch and a meeting will be arranged. Afterwards, the Affiliate will be added to the Bureau database for easy contact, in relation to projects and use of their offered assets.
Examples include:
-A Neophyte, with significant experience facing droids, offers advice on designing a combat droid.
-The assistant beastmaster offers live targets from feeder-animals from the bestiary.
- A Household Sith offers use of specific people under their command (scientists within a particular field, engineers, etc).
Database and Projects
The Bureau utilizes a database solely focused on managing projects, tracking their progress and communication between Bureau and branches. Branches are automatically added to the database upon agreement to a project, with relevant channels such as documentation and communication lines. Affiliates are added, following their meeting with Branch Leadership.
Projects Guidelines
A set of rules and phases of development has been established, to ensure the Bureau retains focus on seeing projects to completion, than having an unending list of unfinished and wasted assets.
Project Phases
Every project presented to the Bureau, will undergo a series of 4 phases.
Research Bureau Hub
The Research Bureau is an initiative founded to address the matters of Research and Development, striving to function as a 'nexus' for it among the many branches within House Horuset. To facilitate a functioning Bureau that creates effective research, development, education and results. It is a a joint effort between branches of the powerbase and members of the Bureau to see projects created and carried to completion.
Bureau Structure
Designed to work with multiple branches of the powerbase at once, the Bureau is established around a structure to avoid unneeded bureaucracy. Upkeeping regular contact with the branches of the powerbase, it will advice, propose and upkeep a continuous open dialog of potential projects.
Bureau Leadership
The leader is responsible for deciding on which projects are officially sanctioned by the Bureau. They decide which projects are approved. They also run the branch, overseeing communications and ensuring each project has the right hands working to it. Additionally, they sanction affiliates and ensure their offered resources are put to appropriate use.
Branch leaders are not Bureau Leadership by default, but they are the ones deciding what their branch brings forward per month. They are also, by default, who the Bureau will conduct meetings with on a regular basis - unless Branch leadership decides to delegate it to another member.
Currently, Sith Sarias is the assigned Head of Bureau.
Bureau Members
Bureau members are members of the represented branches and also members from outside of the officially associated branches who wish to join. These people work together on projects and are sometimes assigned leadership of their branch’s project, or Bureau projects as a whole. They report to Bureau leadership directly.
Bureau Affiliates
These are those who offer resources, support, and other non-specific skills for the research projects. They need not be members of the Bureau or a specific branch.
To become an Affiliate, one need only approach the Head of the Branch and a meeting will be arranged. Afterwards, the Affiliate will be added to the Bureau database for easy contact, in relation to projects and use of their offered assets.
Examples include:
-A Neophyte, with significant experience facing droids, offers advice on designing a combat droid.
-The assistant beastmaster offers live targets from feeder-animals from the bestiary.
- A Household Sith offers use of specific people under their command (scientists within a particular field, engineers, etc).
Database and Projects
The Bureau utilizes a database solely focused on managing projects, tracking their progress and communication between Bureau and branches. Branches are automatically added to the database upon agreement to a project, with relevant channels such as documentation and communication lines. Affiliates are added, following their meeting with Branch Leadership.
Projects Guidelines
A set of rules and phases of development has been established, to ensure the Bureau retains focus on seeing projects to completion, than having an unending list of unfinished and wasted assets.
- Only one active project per branch - A branch may only have one official project running at a time. Members of branches with an active project, may however propose project ideas on an individual level to Bureau Leadership. Individuals, not belonging to any branches, can also bring forward proposals.
- The Bureau can undertake projects of its own volition separate from the involved branches - These projects will be a group effort and will adhere to the same structure as branch projects. They may be funded by the Bureau itself, or independently funded by those requesting the projects.
- Projects, once approved, will be made public - As the Bureau is intended to serve the entire powerbase, approved projects will have a datafile created and published below these writings. It lays within the Bureau, to ensure its maintained with larger updates and notable developments. Not just for practicality, but to showcase its work and invite inspiration in those with ideas, or those of relevant skills to offer themselves to become involved.
- A monthly report will be send to the Conservancy - A monthly report will be sent to Darth Horuset, Lord Kalkoran and the Conservancy. It will detail any changes, current projects updates or relevant news from the Bureau's efforts.
Project Phases
Every project presented to the Bureau, will undergo a series of 4 phases.
- Proposal - Project is presented to Bureau leadership by the branch. Regardless of a project currently being underway, proposals should be presented - this will ensure new projects can replace those running dormant or finding completion. Should it be deemed of potential, the project is reviewed. If it is approved, Relevant databases are updated to reflect a new project being undertaken, and the project enters the development stage.
- Development - An outline of the project’s progression is finalized. Agreed upon plans begin and are monitored via the “Project Status” channel. Bureau leadership is to be informed of situations that require direct intervention or assistance. The project is added to the monthly report, and has a file created within the "Research Bureau Hub", located under the conservancy database.
- Finalizing - Final field testing, last preparations and finishing touches are performed. If more time is required, problems occur or things go wrong, it's returned to development.
This phase concludes with a presentation where those relevant gather for its display.
- Completion - With an accepted project conclusion, a summary is written and a plan-of-action is crafted to see the project’s results carried out (Via funding, materials granted and onwards). The summary will be logged permanently within the database, alongside relevant documentation. Project slot is freed up for the branch, and project entry marked complete within the "Research Bureau Hub" files.