Week 4

We’ve been working on CATS for 4 weeks now. We’ve made a lot of progress, and we’re working very hard to ensure that we properly manage and design our prototypes. Our Product Manager, Brad Hord, has greatly assisted us in working through the best practices laid out in “Product Design and Development” by Ulrich and Eppinger.

At our first meeting we worked through defining our problem, and performing background research. We recognized that the problem we are trying to solve can be broken up into two parts:

  1. Need for a system to control the use of machines
  2. Need for a simple common identity among our users

Over the next few meetings we brainstormed possible needs, anonymously ranked all of our needs, and then brainstormed concepts based on the needs, and anonymously ranked the concepts.

This week we discussed the rankings of our concepts, and analyzed what aspects of each concept resulted in their rankings. We then generated requirements for our prototype based upon the results of our needs, and concepts rankings.

The members of the team then self-divided into a hardware, software, and housing team. The teams were then tasked with generating a prototype BOM, algorithm block diagram, and an enclosure mock-up.

 

Next week we will discuss the different prototype proposals, and we will finalize the design for the CATS Alpha model.

Hello World!

Welcome to the CATS project blog! This is our first post.

CATS stands for the Clemson (Machinery) Access Tracking System. We’re a Creative Inquiry team working to develop an open-source access tracking and control system for Makerspaces, Student Shops, and Industrial Applications.

More specifically, we are a passionate group of makers working to lower the barrier of entry for undergraduates to the Clemson Makerspace, while promoting and ensuring a culture of safety.

We are going to post weekly project reports on this blog, and we’re also going to share all of our code and hardware designs on our github.