The Artifactory has a wide selection of tools which cover the majority of member needs.
This policy applies when a member wants to bring in their own tools ("BYO tools") to use at the space.
Low Risk 🟢, Medium Risk 🟡, and High Risk 🔴 are defined in the Training policy.
In most circumstances Casual / Day Pass users are not allowed to BYO tools. Exceptions may be made to facilitate specific events and activities (e.g. Women's Woodworking, Arduino U) by a member of the Management Committee or relevant event host.
The casual attendee will be treated as a member for the purposes of this policy, all other restrictions still apply. Exceptions are once off (for that specific instance of the event) and do not carry over to other events or days.
- Members can BYO tools that we classify (or would classify) as Low Risk 🟢 tools.
- If a member is not 100% certain that their tool is Low Risk 🟢, they should seek advice from a member of the Management Committee or the Infrastructure Subcommittee.
- Mains-powered tools must have been tested and tagged within the last 6 months.
- For a member to BYO a Medium Risk 🟡 or High Risk 🔴 tool of a type covered by an Artifactory tool induction, the member must be an Artifactory authorised operator for that same type of tool.
- The member must justify why the tool needs to be BYO instead of using the equivalent Artifactory tool.
- This justification must be approved by a trainer who is authorised to train on the equivalent Artifactory tool.
- Tools that we would classify as a Medium or High Risk tool, but which are not covered by an Artifactory tool induction, cannot be used without approval from a member of the Infrastructure Subcommittee.
- Mains-powered tools must have been tested and tagged within the last 6 months.
- A member can authorise themselves to BYO a tool if they would otherwise be authorised to do so under this policy.
Approved BYO tools must be recorded in a place that is visible to all delegated approvers (e.g. a Slack channel.)
The record must include -
- What the tool is, and who's bringing it in
- The justification for why the Artifactory equivalent isn't appropriate
- Whether the attendee required a casual user/day pass exception
- Whether the tool required an Infrastructure Subcommittee authorisation
- The timeframe of the authorisation (members only)