mirror of
https://github.com/fablabsg/fablab-docs.git
synced 2024-11-16 09:52:13 +00:00
60 lines
3.1 KiB
Markdown
60 lines
3.1 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
|
|
|
|
> Describe the roles and reponsibilities of the people involved in the project.
|
|
|
|
## Resources, financial and quality plan
|
|
|
|
> Describe the resources needed and how they are going to be obtained, provided or paid for.
|
|
>
|
|
> This means man-hours of effort, infrastructure, etc. and their cost.
|
|
|
|
## Work breakdown structure and schedule
|
|
|
|
> Describe the project timeline and its main milestones.
|
|
>
|
|
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
|
|
>
|
|
> Each project phase will have its own ToR in a separate file.
|
|
|
|
## Key issues and risks
|
|
|
|
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
|
|
>
|
|
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
|
|
|
|
## Assumptions and constrains
|
|
|
|
> List of any significant assumptions we have made at the time of preparing the ToR.
|