• RumRunningDevil@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    I work for the company that made these robots; at the risk of bias I can speak to this.

    The system works great, the problem is Walmart. These systems are MASSIVELY complicated and require quite a bit of technical know-how. Walmart isn’t actually our only customer but they are our biggest. The difference between them and our other customers is Walmart insists on having its locally paid people be the ones to operate and maintain the system (which extends way beyond just the mobile robots and includes more traditional industrial controls and multi-axis robots as well).

    Walmart employees are absolute shit at doing this though and Walmart pushes the system way beyond the recommended breaking point without doing the required PMS, this leads to performance reduction over time.

    Our contract requires that, prior to a site being brought into production, it has a validation test run where we verify it can maintain the required throughput as a part of the SLA (this throughput is vastly higher than what the warehouse could do without the bots). The sites pass the validation, the issue is throughput degrades over time due to poor training and maintainence practices.

    Our other customers don’t maintain the equipment, instead we have paid Symbotic employees at the sites that do it. Those sites have measurably better performance over time and it’s an issue corporate has taken note of.

    • kerryh8er04@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      So I’m all for these kinds of systems. What I see coming from a legacy manufacturer is they have so many limitations and restrictions, or their CTO and similar departments refuse to accept some of the system requirements, that once they purchase a novel new technology system, it just falls apart. From my experience it has almost always been two things, either the vendor selling the service over sold their ability, or the purchasing company ham strung the project so much that it was doomed before it started.

      But I’m still hopeful, you actually build a system that meets the requirements, you have a customer actually embrace the systems and changes, it would enable success.

      • RumRunningDevil@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        I’ve seen the same. My current take is basically “nothing about how we did warehouses transfers to this new way, and attempting to make them dovetail gives you the worst of two worlds”.

        The cool thing is there’s so many neat new industries this can create. The downside is that, as usual, there’s a big disconnect between P&L decision makers and technical professionals.

        • kerryh8er04@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          Disconnect between P&L decision makers and technical professionals, been the same story for 40 years now. The more the C suite is filled with “business/accounting/law” the further the business moves away from its core competency. Praise be to jack welch, may he rest in piss.

    • Kay Ohtie@pawb.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      While I know you wanna stand up for your employer: don’t.

      Quite literally for your job safety you should delete this post unless you’re literally PR and speaking in a way your employer would be fine with.

      Most corporate training modules involve clear information you should never post like this because you’ll almost certainly get fired.

      If you want to share things, post it more as “I work for a company that makes robots like this. The problem with our biggest warehouse clients is X, where our smaller ones is Y, so that’s probably the case here too.” Never directly show your employer like this.

    • HaraldvonBlauzahn@feddit.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      These systems are MASSIVELY complicated and require quite a bit of technical know-how.

      You named one main problem here.

      The other ist cost. How much does a system cost that replaces one worker cost? INCLUDING the required technically skilled service staff?

      • RumRunningDevil@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        As I replied to others, in systems like this it’s not as simple as cost savings. The selling point is increased throughput. The system costs more upfront and factoring future gains from increased throughput you end up making more money than if you had kept the cheaper manual workforce.

    • Frenchgeek@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      So. The usual “Management trying to save a insignificant amount by making a stupid decision on a system they don’t understand for a job they don’t know”…

      • RumRunningDevil@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        Ummm, no?

        The system is way more expensive than the workers were. By like, orders of magnitude. They buy it because you can basically 10x a warehouses throughput using it.

        Don’t get me wrong, after accounting for increased throughput and the gains by automation you end up with a bigger margin than by having a swarm of workers in a dusty warehouse but it necessitates hiring a ton of technical professionals that you generally have to pay more. Additionally this whole space is really hard for AI to touch because it’s very cross domain and real time. For reference. My role is considered “entry level” and I get 6 figures.

        All that being said this isn’t so much managers being idiots (though there’s plenty of that) so much as “our core competencies built from the ways we did warehouses before do not translate to how we do them now and friction is being generated as a result of that transition.”

        There are technical issues with the system. It’s largely built to integrate with legacy industrial tech which ties it into the windows space, this has led to a lot of decisions about tooling that degrades performance and leads to memory leaks.

        • LePoisson@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          For reference. My role is considered “entry level” and I get 6 figures.

          Please give me a job, thank you good sir or madam.

          • RumRunningDevil@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 days ago

            This is actually a good time to get into the space. There’s not a ton of companies competing over a now growing market and the work is weird enough that AI hasn’t fully eaten it.

            Downside, see my other posts, the field wants to pull people who have a pretty diverse skill set. I would be prepared to discuss RAFT consensus in the same conversation as PID tuning and control theory.

            Checkout companies like Symbotic, Boston Dynamics, or robotics integrators like ABB

            • romanticremedy@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              0
              ·
              3 days ago

              Job sounds interesting. Several questions if u don’t mind me asking because I’m thinking to do small career change.

              • What’s the job title I should look for?
              • Do you think it’s possible to transfer from software developer? I have engineering background so I think I should be able to pick things up
              • Is ageism real in your industry? I’m in 30s so ain’t young so worried about applying to entry level positions
              • RumRunningDevil@lemmy.zip
                link
                fedilink
                English
                arrow-up
                0
                ·
                3 days ago

                Unfortunately we don’t have standardized roles in this industry.

                Jobs like these tend to touch one of a couple spaces.

                1. Controls engineering: PLC programming and traditional robotics
                2. Fleetops, application engineer, or operations engineer: I’ve seen these show up at places like Boston dynamics
                3. Technical support: look for ones that mention wanting like a EE and knowing stuff about control systems.
                4. SCADA engineer: Especially at tech startups.

                In general you’re looking for jobs that reference a mixture of networking, control systems, SCADA, DCS, PLC, IT infra, and of course robotics.

                My entire team is 30+, hard to find people with a diverse background that are also 22.

        • mirshafie@europe.pub
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          Sounds like they might be learning from their mistakes though? If so, they’re smarter than most businesses.

          • RumRunningDevil@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 days ago

            The industry is still in its infancy, not just warehouse automation but robotics and fleetops in general.

            There’s a lot of growing pains as we figure out the best ways to manipulate autonomous robot swarms that can number in the thousands.

            One of the big issues is just training personnel for all this. It’s quite rare to find people with a background in both hardware and software and who can speak both fluently.