Wednesday, December 27, 2017

Automated Tetris

Following complaints that Amazon sometimes uses excessively large boxes for packing small items, the following claim appeared on Reddit.

"Amazon uses a complicated software system to determine the box size that should be used based on what else is going in the same truck and the exact size of the cargo bay. It is playing automated Tetris with the packages. Sometimes it will select a larger box because there is nothing else that needs to go out on that specific truck, and by making it bigger, it is using up the remaining space so items don't slide around and break. This actually minimizes waste and is on the whole a greener system. Even if for some individual item it looks weird. It's optimizing for the whole, not the individual." [source: Reddit via @alexsavinme]

Attached to the claim is a link to @willknight's 2015 article about Amazon's robotic warehouses. The article mentions the packing problem but doesn't mention the variation of box sizes.

The claim quickly led to vigorous debate, both on Reddit and on Twitter. Here are a selection of the argument and counter-arguments.


  • Suggesting that the Reddit claim was based on a misreading of the MIT article.
  • Asserting that people working in warehouses (Amazon and other) were unaware of such an algorithm. (As if this were relevant evidence.)
    • Evidence that equally sophisticated algorithms are in use at other retailers and logistics companies. (Together with an assumption that if others have them, Amazon must definitely have them.)
    • Evidence that some operational inefficiencies exist at Amazon and elsewhere. (What, isn't Amazon perfectly optimized yet?)
      • Providing evidence that computer systems would not always recommend the smallest possible box. For example, this comment: "At Target the systems would suggest a size but we could literally use whatever we wanted to. I constantly put stuff in smaller boxes because it just made so much more sense." (Furthermore, the humans being able to frustrate the intentions of the software.)
      • Suggesting that errors in box sizes are sometimes caused by mix-up of units - one item going in a box large enough for a dozen.
      • Pointing out that the solution described above would only work for transport between warehouses (where the vehicle is full for the whole trip) but wouldn't work for "last mile" delivery runs (where the vehicle becomes progressively more empty during the trip).
      • Pointing out that the "last mile" is the most inefficient part of the journey. (But this doesn't stop retailers looking for efficiency savings earlier in the journey.)
      • Pointing out that there were more efficient solutions for preventing packages shifting in transit - for example, inflatable bags.
      • Pointing out that an overlarge box merely displaces the problem - the item can be damaged by sliding around inside the box.
      • Complaining about the ethics, employment policies and environmental awareness of Amazon.
      • Denigrating the intelligence and diligence of the workers in the Amazon warehouse. (Lazy? Really?)

      Some people have complained that as the claim is evidently false, it counts as fake news and should be deleted. But it is certainly true that retailers and logistics companies are constantly thinking about ways of reducing packaging and waste, and there are several interesting contributions to the debate, even if some of the details may not quite work.

      It's also worth noting that the claim is written in a highly plausible style - that's just how people in that world would talk. So maybe someone has come across a proposal or pilot or patent application along these lines, even if this exact solution was never fully implemented.

      Some may doubt that such a solution would be "greener on the whole". But any solution architect should get the principle of "optimizing for the whole, not the individual". (Not always so easy in practice, though.) 



      Will Knight, Inside Amazon’s Warehouse, Human-Robot Symbiosis (MIT Technology Review, 7 July 2015)

      Wikipedia: Packing Problems

      Thursday, December 14, 2017

      Expert Systems

      Is there a fundamental flaw in AI implementation, as @jrossCISR suggests in her latest article for Sloan Management Review? She and her colleagues have been studying how companies insert value-adding AI algorithms into their processes. A critical success factor for the effective use of AI algorithms (or what we used to call expert systems) is the ability to partner smart machines with smart people, and this calls for changes in working practices and human skills.

      As an example of helping people to use probabilistic output to guide business actions, Ross uses the example of smart recruitment.
      But what’s the next step when a recruiter learns from an AI application that a job candidate has a 50% likelihood of being a good fit for a particular opening?

      Let's unpack this. The AI application indicates that at this point in the process, given the information we currently have about the candidate, we have a low confidence in predicting the performance of this candidate on the job. Unless we just toss a coin and hope for the best, obviously the next step is to try and obtain more information and insight about the candidate.

      But which information is most relevant? An AI application (guided by expert recruiters) should be able to identify the most efficient path to reaching the desired level of confidence. What are the main reasons for our uncertainty about this candidate, and what extra information would make the most difference?

      Simplistic decision support assumes you only have one shot at making a decision. The expert system makes a prognostication, and then the human accepts or overrules its advice.

      But in the real world, decision-making is often a more extended process. So the recruiter should be able to ask the AI application some follow-up questions. What if we bring the candidate in for another interview? What if we run some aptitude tests? How much difference would each of these options make to our confidence level?

      When recruiting people for a given job, it is not just that the recruiters don't know enough about the candidate, they also may not have much detail about the requirements of the job. Exactly what challenges will the successful candidate face, and how will they interact with the rest of the team? So instead of shortlisting the candidates that score most highly on a given set of measures, it may be more helpful to shortlist candidates with a range of different strengths and weaknesses, as this will allow interviewers to creatively imagine how each will perform. So there are a lot more probabilistic calculations we could get the algorithms to perform, if we can feed enough historical data into the machine learning hopper.

      Ross sees the true value of machine learning applications to be augmenting intelligence - helping people accomplish something. This means an effective collaboration between one or more people and one or more algorithms. Or what I call organizational intelligence.


      Postscript (18 December 2017)

      In his comment on Twitter, @AidanWard3 extends the analysis to multiple stakeholders.
      This broader view brings some of the ethical issues into focus, including asymmetric information and algorithmic transparency


      Jeanne Ross, The Fundamental Flaw in AI Implementation (Sloan Management Review, 14 July 2017)

      Saturday, December 02, 2017

      The Smell of Data

      Retailers have long used fragrances to affect the customer in-store experience. See for example Air/Aroma.

      So perhaps we can use smell to alert consumers to dodgy websites? An artist and graphic designer, Leanne Wijnsma, has built what is basically an air-defreshener: a hexagonal resin block with a perfume reservoir inside, which connects over Wi-Fi to your computer. When it notices a possible data leak (like the user connecting to an unsecured Wi-Fi network, or browsing a webpage over an unsecure connection) — puff! It releases the smell of data.

      James Vincent, What does a data leak smell like? This little device lets you find out (Verge, 31 Aug 2017)

      That's all very well, but it only sniffs out the most obvious risks. If you want to smell the actual data leak, you'd need a device that released a data leak fragrance when (or perhaps I should say whenever) your employer or favourite online retailer is hacked. Or maybe a device that sniffed around a corporate website looking for vulnerabilities ...

      I'm sure my regular readers don't need me to spell out the flaws in that idea.



      Related posts

      Pax Technica - On Risk and Security (November 2017)
      UK Retail Data Breaches (December 2017)

      UK Retail Data Breaches

      Some people talk as if data protection and security must be fixed before May 2018 because of GDPR. Wrong. Data protection and security must be fixed now.

      Morrisons (2014)


      The High Court has just found Morrisons to be liable for a leak of employee data by a disaffected employee in 2014. (The perpetrator got eight years in jail.) 

      http://www.theregister.co.uk/2017/12/01/morrisons_data_leak_ruling/
      http://www.bbc.co.uk/news/uk-england-42193502

      Sports Direct (2016)


      A hacker obtained employee details in September 2016, but Sports Direct failed to communicate the breach to the affected employees.

      https://www.theregister.co.uk/2017/02/08/sports_direct_fails_to_inform_staff_over_hack_and_data_breach/

      CEX (2017)


      Second-hand gadget and video games retailer Cex has said up to two million customers have had their data stolen in an online breach

      http://www.bbc.co.uk/news/technology-41095162
      https://uk.webuy.com/guidance/

      Zomato (2017)


      Up to 17 million users affected by data breach at restaurant search platform Zomato

      https://www.infosecurity-magazine.com/news/zomato-breach-exposes-17-million/
      https://www.zomato.com/blog/security-notice

      Tesco Bank (2016)


      Cyber thieves steal £2.5m

      https://www.theguardian.com/business/2016/nov/08/tesco-bank-cyber-thieves-25m
      https://www.theregister.co.uk/2016/11/10/tesco_bank_breach_analysis/
      https://www.itproportal.com/features/lessons-from-the-tesco-bank-hack/



      Related posts


      The Smell of Data (December 2017)