mirror of
https://github.com/fablabsg/fablab-docs.git
synced 2024-12-23 03:14:11 +00:00
68 lines
3.3 KiB
Markdown
68 lines
3.3 KiB
Markdown
# Conceptualisation ToR
|
|
|
|
## Project objectives
|
|
|
|
### Scope
|
|
|
|
- Engage with the multiple communities of makers in Singapore about the idea of affiliating them and their members into a new FabLab Singapore federation.
|
|
|
|
- Using exiting entities and structures as proxies (ie. institutions controlled by the members of the project), allow for the FabLab Singapore federation to be temporary governed and operated through the Conceptualisation Phase.
|
|
|
|
- Setup the legal framework required for the FabLabs (ie. SP FabLab) to be able to take workflows from the community and provide training, certification and other services to them, while being FabLab Singapore's proxies the grantors and accountable parties on behalf of the community members.
|
|
|
|
- Setup and operate a temporary IT infrastructure required for the FabLabs (ie. SP FabLab) to be able to take workflows from the community and provide training, certification and other services to them during the Conceptualisation Phase.
|
|
|
|
- Develop and implement the marketing and communications strategies and plans required to develop, build, grow and sustain the FabLab Singapore during the Conceptualisation Phase.
|
|
|
|
- Develop and implement the FabLab Singapore's Social Responsability Charter during the Conceptualisation Phase.
|
|
|
|
### Deliverables
|
|
|
|
* A MOU with at least 1 FabLab who can take workflows from the community and receive payments from them through FabLab Singapore.
|
|
|
|
* A temporary IT ifrastructure enabling the data flows from the community to the FabLab and the delivery of the required applications to the community.
|
|
|
|
* A marketing and communications strategy and plan for the Pilot Design and Development phase, ready to be implemented and executed.
|
|
|
|
* A MOU with at least 1 beneficiary to provide their cases for the Pilot Challenge.
|
|
|
|
* A group of Community Leaders and community members interested and pre-signed up for participating of this project, which is significant enough to believe that we can move to the next phase.
|
|
|
|
* The Pilot Design and Development ToR agreed by all the relevant parties, including its funding.
|
|
|
|
## Project roles and responsibilities
|
|
|
|
> List and description of the roles and reponsibilities of the people involved in the project.
|
|
|
|
* Same as the ones described for the overarching project.
|
|
|
|
## Resources, financial and quality plan
|
|
|
|
This face requires very limited resources, basically the internal effort needed to perform the tasks and produce the documents required for the next phase.
|
|
|
|
The budget is estimated in 80 hours of effort.
|
|
|
|
All the deliverables will be reviewed and approved by the leadership on Stage Gate 1 in order to proceed to the next phase.
|
|
|
|
## Work breakdown structure and schedule
|
|
|
|
The details of the tasks and status can be found in the project on GitHub [here](https://github.com/orgs/FabLabSG/projects/2).
|
|
|
|
The main milestones of this phase are as follow:
|
|
|
|
- Project Start - 13/8/2024
|
|
|
|
- Stage Gate 1 - 11/9/2024
|
|
|
|
## Key issues and risks
|
|
|
|
> List of the significant issues or risks identified at the time of the prepararion of these ToR.
|
|
|
|
No new issues or risks were identified. Same as the ones identified for the overarching project.
|
|
|
|
## Assumptions and constrains
|
|
|
|
> List of the significant assumptions that were made at the time of the preparation of these ToR.
|
|
|
|
- No new assumptions were made. Same as the ones indetified for the overarching project.
|