Kit Team

Purpose

The purpose of the Kit Team is to oversee and manage the development, maintenance and support of the SR Kit. The Kit Team is responsible for providing a Kit Service to the Competition team in order to enable the SR Competition Programme.

The kit is defined as the hardware and software (including software services) that are provided to school teams to enable them to take part in the annual robotics competition.

The Kit Service includes, but is not limited to:

  • Provision of sufficient working kit to meet the needs of the Competition Team

  • Recovering and checking kit following a competition cycle

  • Storing the kit safely

  • Maintaining an inventory of the kit

  • Development of kit

  • Maintenance of kit (both during and outside of the competition cycle)

  • Manufacture/purchasing of kit

  • Technical documentation for competitors and for volunteers

  • Technical support to competitors and volunteers (both remote and in-person at events)

Structure and Operation

The Kit Team is a group of volunteers that work together to provide a Kit Service. The team is lead by a committee that is responsible for fulfilling the aims of the team.

The Kit Team is separate from the Competition Team. However, it is expected that Kit Team volunteers will have previously volunteered with the Competition Team and that volunteers from both teams will be available to help run the annual competition.

Volunteers apply through the Kit Team Committee to join the team. The committee will ensure the team has an appropriate balance of relevant skills. The committee should not unreasonably restrict membership of the team.

The Kit Team Committee

The Kit Team Committee is a group of 3-5 people who develop and clearly communicate a strategic vision, coherent with the values of Student Robotics, for the Kit. The committee ensures that resources are always used in the best interests of the charity and is accountable to the Trustees, The committee delegates responsibilities and resources to the rest of the team.

Joining the committee

Volunteers join the committee by application to the Trustees. The committee will operate on a continuous/rolling timeline. Each member has a maximum term of two years, after which they are automatically retired from the committee. Before the conclusion of the two year term the member may apply to the Trustees to extend their term for a further two years, without a gap in membership.

Resignation of a committee member

If a committee member wishes to resign they should email the Trustees. The Trustees will work with the individual to see if there is any more help and support that they can provide to allow them to continue in their role. If there is no option for the individual to continue, the Trustees will work with the rest of the committee to find a volunteer to become a replacement committee member.

Collective responsibilities of the committee

The committee is collectively responsible for:

  • Communicating a strategic vision for the kit.

  • Ensuring that resources are deployed only for the purposes of delivering the Student Robotics Competition Programme or as directed by the Trustees.

  • Maintaining a record of team members, with their abilities and desired workload.

  • The management, tracking and distribution of assets within the team.

  • The management of the workload of members of the team.

  • Ensuring projects are open source, open to contribution from external parties, and inviting to work on by volunteers.

  • Assigning and managing projects/maintenance to team members, this may be assigned to self organising subgroups of individuals.

  • Communicating with the Competition Team Committee to ensure successful delivery of the annual competition programme.

  • Maintain documentation of processes and anything else that they feel relevant relating to their responsibilities to help both current and future volunteers This documentation should be licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

Individual Responsibilities/Roles within the committee

The following responsibilities must be divided up among the committee members. Each responsibility listed below must be taken by a single member.

  • Reporting to Trustees. This committee member is responsible for ensuring that the committee provides regular updates to the Trustees to update them on the work of the team. They must also ensure that minutes are taken at committee meetings and that these minutes are made publicly available.

  • Budget and expenditure management. This committee member is responsible for drawing up an annual budget within the overall budget provided by the Trustees. They must submit the budget to the Trustees once it has been agreed. They must also do the following:

    • Keep financial records (in a form to be agreed with the trustees)

    • Understand and follow the requirements defined in the Money Matters section

  • Communicating with the Competition Team. This committee member is responsible for formal liaison with the Competition Team to make sure that any issues relating to the kit are communicated effectively and that the committee is kept fully aware of pressures and deadlines.

The committee should self-organise to elect these roles within their group, along with any other roles that they deem necessary, e.g. Software Coordinator.

Accountability

The Kit Team is accountable to the Trustees. A report will be delivered by the committee member responsible for reporting to the Trustees, every 4 months, to update them on the work of the team and the state of the kit.

Minutes of meetings should be made available to the general public although access to any sensitive commercial data, may be restricted to the Trustees.

Budget

A budget will be made available to allow the kit to be stored safely and maintained in good working order.

Specific budgeting for development projects will be managed on a case by case basis, applying for budget from the Trustees in each of these cases.

A "Development Pot" will be made available to cover low-cost resources used in the development process.

Last updated