I met the other co-op student joining the team today, our jobs for this week was going to consist of going to meetings and binge learning as much about supply chain, our current reporting structure, and the design of TPS as we can. That’s how this week went really, most of my day was spent in meetings discussing how the TPS application should and will be structured. It was really confusing at the start, but as the week neared its end it started getting easier to understand. Basically we’ve separated the application into 3 distinct parts, first is the builder where we pull raw data about a shipment from our existing databases, the next was the analyzer where we isolate and parse important and useful information about a shipment, and the final part was the calculator which calculates KPIs (KPI stands for Key performance index) that we use when generating the reports. This isn’t set in stone yet but it is what we’re going with for now. The goal is to have this project in quality assurance by early June but apparently that is flexible. The goal for the next week or so is to get a very solid design set up so we can quickly code the application and have it into QA by June. On the other side of the coin I was able to make a few changes to the COAT application with the guidance of the rest of the team and redeploy the application. I don’t believe that I will be working on this much longer however as I believe most of my time will be devoted to TPS.