Feb 08

Sourcing trees are popular: here is a second example

Cool tools, Purchasing, Template    ---    2007 Jean-Philippe Massin, 4,231 views Add comments

In october last year, I’ve explained – shortly I admit, but with a nice exhibit – what a sourcing tree is (product / service categorisation). If I recon my stats about my popular posts, this is definitly one of interest. So, here is a more extensive example of a sourcing tree (which I used in real in my first life – i.e. not in second life ;-) ). Enjoy, it’s free. Still!


Related Posts:
  • Comparing online traffic on leading eSourcing vendor’s websites (Alexa)
  • Top 100 Purchasing & Supply Management Tips
  • Howto estimate the duration of a reverse auction
  • Comparing e-Sourcing vendors’ traffic ranking (Alexa)
  • Sourcing, the way to lower costs for direct material
  • Profiling: A Must, for successful eAuction deployment


  • 4 Responses to “Sourcing trees are popular: here is a second example”

    1. 1. David Rotor Says:

      Jean-Phillippe,

      Thanks for sharing your sourcing tree, I look forward to exploring it for new ideas. I follow a similar approach to natural categorization, and have opened the category hierarchy approach I use to wiki style collaboration at http://wiki.procurementinvestor.com/pmwiki, I’d be interested in hearing your thoughts on the similarities and divergence between the two approaches.

      Cheers,

      David Rotor

    2. 2. jp.massin Says:

      Hey David, You’re welcome, and btw, congratulation for your blog I discovered lately. I don’t get your point really about the ’2 approaches’. do you mean Blog vs Wiki?

    3. 3. David Rotor Says:

      Thanks JP. By “2 approaches” I meant our respective approach (and the category content) for sourcing trees. After reading your tree and comparing it with the category hierarchy approach here are some initial thoughts.

      While we are both using a hierarchal approach only two levels seem to have similar content. Even though both have a three tier structure I don’t have anything comparable to the content of your category, and you don’t aggregate at a level similar to my Family

      JP: Family -> Category -> Sourcing Group
      DR: Family -> Group -> Category

      JP -> DR
      n/a -> Family (my highest level of aggregation)
      Family -> Group
      Category -> n/a
      Sourcing Group -> Category

      Cheers,

      David Rotor

    4. 4. jp.massin Says:

      Right. 3 points:

      1. I’ve shown only 3 levels but there is a more precise one after the SGs which is ‘SG item’ or ‘SG families’ (SGI or SGF)

      2. This post is following this one:
      http://www.massin.eu/2006/10/31/example-of-a-sourcing-tree/ where you can see that the logical levels are 1) Category – 2) Family – 3) SG – 4) SGI (not said)

      3. then, our categorisation tree is basically the same but with different names:
      JP: Category -> Family -> Sourcing Group -> SGI
      DR: ( n.a. ) -> Family -> Group -> Category

      Don’t know if I’m crystal clear…

    Leave a Reply

    i3Theme sponsored by Top 10 Web Hosting, Hosting in Colombia and Web Hosting Reviews