Inventory Management

The inventory management process for this mobile installation project involves several key steps to ensure efficient handling of units. It begins with referencing the "Inventory Unit Request and Shipping" ticket, which initiates a dialogue with the Production team to gather necessary details. Subsequently, Pre-Flight tickets are verified and attached to the main request, outlining specific actions required for each unit. Within Salesforce, PMO executes the generic removal tasks for each Pre-Flight ticket, followed by customer assignment to allocate units appropriately. Screenshots are taken at each stage to document completion and provide proof of work. Once all Pre-Flight tickets are processed, they are assigned to the On-Boarding team for site assignment, and updates are made in the Mobile Install Parent (MIP) to track the progress of units sent for onboarding.

Overall, the process emphasizes meticulous attention to detail and thorough documentation to ensure accurate inventory management. By following a structured approach, including verification, execution, and tracking, the project management team maintains visibility and control over the status of each unit. This systematic workflow streamlines operations, facilitating smooth transitions between teams and minimizing the risk of errors during mobile installations.

• • Reference the side conversation ticket “Inventory Unit Request & Shipping” with the Production team: Begin by checking the "Inventory Unit Request" ticket that involves a side conversation with the Production team. This ticket likely contains details about the units that need to be managed.

  • Verify that the Pre-Flight Tickets have been attached to the inventory unit request ticket per the Production team's process: Ensure that all relevant Pre-Flight Tickets, which likely contain information about tasks or actions required for each unit, are attached to the main "Inventory Unit Request" ticket as per the Production team's process.

  • For each Pre-Flight ticket, execute the generic removal within Salesforce: Go through each Pre-Flight ticket and perform the necessary actions for generic removal within Salesforce. This likely involves specific steps to detach units from a generic opportunity or perform other relevant tasks.

  • Update the Pre-flight ticket with screenshots once generic removal has been completed as proof of work: After executing the generic removal for each Pre-Flight ticket, capture screenshots as proof of completion. Update each Pre-Flight ticket with these screenshots to document the work done.

  • Execute Customer Assignment in Salesforce for each Pre-flight unit removed from the generic opportunity: Following the generic removal, proceed to assign each unit to a specific customer within Salesforce. This ensures proper tracking and organization of the units.

  • Update the Pre-flight ticket with screenshots of Customer assignment in Salesforce as proof of work: Similar to step 4, capture screenshots of the customer assignment process within Salesforce for each unit. Update the respective Pre-Flight tickets with these screenshots for documentation purposes.

  • Assign all Pre-Flight tickets now Customer Assigned to the On-Boarding team for Site Assignment: Once all Pre-Flight tickets have been processed and the units have been assigned to customers, assign these tickets to the On-Boarding team. They will handle the next steps, likely involving site assignment or deployment.

  • Update MIP with Pre-Flight tickets that are sent to Onboarding for tracking: Finally, update the Master Inventory Plan (MIP) with information about the Pre-Flight tickets that have been sent to the On-Boarding team. This ensures proper tracking and visibility of the units throughout the project management process.