Locus Robotics Ideas Portal
All ACTIVE site files should be stored in a central location where it can be accessed by C.S. without requiring a support ticket.
All CURRENT site targets and model metrics should be available in a central location. This data should be stored such that our reports can pull information from them autonomously to avoid manual data transfer, and the associated errors that come with it.
The request here is simply an agreed upon storage location (as simple as OneDrive, or something fancier) for the active / current site information. When any updates are made, these are updated so that the current version is always available to whoever needs it.
In most cases, I would imagine these are just excel files with the current site configuration information (active LP2Bin file, active Congestion Management Configuration file, active Pick Sequence File, active Heat Map file, is Clustering ON/OFF, etc..).
Current site target information should be owned by Sales and stored in this same location. This information should be able to be referenced by our reporting tools (Executive Summary, Client Scorecard, HCS, even the Portal, etc..)
|
Problem/opportunity trying to be solved
C.S. regularly has to to submit support tickets to get the latest version of files such as the LP2Bin file, Pick Sequence file, Congestion Management configuration file. Support tickets are needed to know critical site settings, such as if Clustering is on/off. When things are time sensitive, files and information are found in Slack or old Jira tickets. This is not a sustainable way of information sharing. Additionally, searching the Sales Engineering Prospect folder is required - to dig up what we hope is the current COO in order to get targets to compare sites against. (There are example of sales revising targets, and - because we have no central location to store the new targets / model - the client and Locus C.S. continuing to work off of the old information) |
|
|
Quantify the problem/opportunity
Sites rarely know their own targets, and OSDs and CSMs often struggle to find the current target information. Without submitting a support ticket, C.S. is often guessing at what files are current / active for the site. |
|
|
What is the root cause of the problem/opportunity
No central / accessible "source of truth" for current site targets and active site files. |
|
| Customer need date | Apr 30, 2023 |
| Urgent request | No |
| Report Tag | Contingent to Sale |
This is a big, cross-functional, goal. Would need some detailed discussions and sponsorship from multiple teams for it. Some are in progress today, some may be sensitive. Can you please document this at the next level? Specific data required, why required, benefit to having it available, and prioritized.