Killarney Logistics is a Third-Party Logistics (3PL) company structured by 4 main departments: Finance, Engineering, Operations and Business Development. Next is an organizational chart showing the names and titles of the main characters of the company, with whom you will be working closely. You and your team will work closely with different people across different departments depending on the business needs and skills required to achieve the deliverables for each week. This is part of the overall company-wide objective of increasing revenue, retaining existing clients, and attracting new clients. As part of the onboarding process, Ron introduces you to all your teammates within the engineering department and shares information about an upcoming project where you will be taking a leading role Onboarding and Orientation Killarney Logistics is a Canadian 3PL company that specializes in fashion and lifestyle brands storage and fulfillment. Killarney Logistics has presence in the west end of the GTA across multiple locations, adding to more than 1,200,000 sq ft of operation. In the efforts to increase revenue and retain existing clients within the Killarney Logistics network, The Managing Director, Jost Capito has been exploring an opportunity that involves one of the biggest clients currently. It was communicated by the spokesman of the client that in the spirit of maintaining the relationship with Killarney Logistics, the client is expecting a considerable reduction of annual operating budget for the next contract renewal cycle, which is due for a proposal in the next couple weeks. Jost wants you to take the leading role in this opportunity from a design point of view. He also points out that the common denominator in most of the warehouses is that these are 28 ft clear to the roof truss. This used to be the market standard decades ago, but now warehouses are capable to have from 36 to 40 ft clear, which allows for a better cube utilization and a smaller footprint to store the same or potentially more units. The intention is that as part of the contract renewal proposal, Killarney Logistics includes a transition/relocation plan where we show the company's commitment to grow with the client and share savings for the growth of both parties. The Director of Engineering, Ron, would like you to meet with your teammates and start building a professional relationship where the team goes around and assigns team roles for this opportunity, creating a Responsibility Assignment Matrix (RAM), as well as some meeting minutes of key points that the team calls out during the conversations. This week has the intention to allow you to get to know your teammates, understand the team dynamic and work culture of Killamey Logistics. Also, allow yourself some time to review all the data that is available from the client. Being familiar with the data available is important in the efficiency of the team. You will be provided with additional information about the organization each week and be asked to document your responses to several key deliverables. Each case study presented is associated with a relevant topic and realistic situation relevant to your field of study. Case studies will provide practice in analyzing and making decisions in a work environment. Week 1 Onboarding Expectations and Participation Your task this week is to participate in training and orientation for the WIL Project. You will participate in a variety of exercises that are designed to get to know you better and to understand your role within the team. You will participate in exercises that prepare you for success within the WIL Project. As with any position, you will have an excellent opportunity to build on your skills as a leader so long as you put forth your best effort. Use this week to develop a communication plan with your team and be ready to dive into the deliverables starting next week. Sizing the Opportunity since Jost Capito has shared the broad intention that the company wants to follow to re-engage with the client and show the commitment that Killarney Logistics has with the relationship, the Information Technology (IT) department shared information about the current state of the account, and along with some notes from Ron, we are expected to present a summary to the leadership team where we summarize a high-level scope of work, timeline, milestones, and team roles. These must be documented and presented for the Go/ No-Go meeting. Ron mentions that it is known that most players agree with the approach so this should be a go. During the Go/No-Go meeting, after it was agreed to go ahead with the opportunity, Jost asked you to generate a Scope of Work (SOW) document where it is outlined with detail the actions and steps required to complete the transition of the account from the current warehouse to the new one. Jost mentioned that he is targeting a facility that is 40ft clear to the roof truss and that all calculations can be started assuming that the new facility is going to be 40ft clear. Ron suggests that you start the SOW document from scratch since the previous format the team was using was somewhat unclear and did not transmit the idea in a proper way. Apply knowledge of the functional components within logistics to the interrelationships in the integrated supply chain Threats Assessment After the SOW is completed, Ron informs you that the next step consists in generating a report with all the possible threats to the projects. This follows the culture of Killarney Logistics of being risk-averse. There are multiple approaches to follow. using a Strengths-WeaknessesOpportunities-Threads (SWOT) approach or a Political-Economical-Social-TechnologicalEnvironmental-Legal (PESTEL) approach. If enough time is available, you could do both approaches. Ron suggests that since we now have a good idea on the Rough Order of Magnitude (ROM) and the risks that may impact the project, we should also generate a set of questions or list of missing information that the engineering team thinks would be helpful and does not possess right now. This will mitigate acting without all the needed information. Deliverables for This Week's Case Study 1. Threat Analysis document and statement of the likelihood of completing the project on time. 2. Internal question list for the team, based on the information previously disclosed by IT