Archive | eProcurement RSS feed for this section

We Are All Permanent Beta… or we SHOULD be

5 Oct

Back in May, we hired a new Client Support Specialist.  He is a very bright individual, but new to our technology and our line of business.  Now, four months later, he and I were having a discussion about a few customer issues, and I was struck by how, well, comfortable, he looked.

I commented on this, and he told me that while he is more comfortable, he considers himself “Permanent Beta”.  I had never heard that term before (a phrase I believe coined by Reid Hoffman earlier this year).  I love the term, much more high tech than ‘work in progress’

I did a bit of googling and found numerous references to ‘Permanent Beta’.  Ironically, this term has both positive and negative connotations.  The positives being continuous improvement, self improvement, etc.  The negatives were in articles about products that are never finished (example: Google Apps End Their State of Permanent Beta).

Frankly, I like the idea!  Is ‘never finished’ a bad thing?

When I joined the iPhone set, I thought it was really cool that Apps are updated continuously, with no requirement for me to go somewhere to get the update.

I am happy to see technology that brings me along.  I don’t have time to look for version 5.1.3.2.55 or whatever.

So, who would complain about ‘Permanent Beta’?

– People and organizations that are rigid.

– People and organizations using products or technology that require ‘big-bang’ implementations.

– People and organizations that want things ‘the way they used to be’

Not me, I’m loving this idea.

I just joined the local rec center, I’m there every morning, huffing and puffing on the treadmill, lifting embarrassingly small amounts of weight on the machines.  No matter.  I feel better, I have more energy.  I’m permanent beta.

Let’s talk eProcurement.  A year ago I didn’t know what it was.  today I’m creating punch-out supplier connections, loading local catalogs.  I’m permanent beta.

Y’all better get on this band wagon.  The Permanent Beta train is leaving the station and it NEVER STOPS.

The alternative?  You get left behind.

– RTR

 

Where PLM and eProcurement Meet…

29 May

My previous world (PLM) and new world (eProcurement) collided in a blog by my friend Oleg Shilovitsky; “New Definition of PLM from UK Datamation Info Assets”.

There has been a significant amount of ‘virtual ink’ spent discussing “exactly what is PLM?”  It’s provided me with a lot of blogging material over the months….

This new ‘definition’ in Oleg’s blog I found to be intriguing:

PLM is different from say CAD, ERP, CRM, etc. and therefore investment decisions in it should be based on different criteria. PLM’s key role, as defined in the Datamation PLM Model report, is the effective management of information assets through-life. In other words, it is a “live entity”

There you have it.  PLM is typically sold based on what it does for you now (vaulting… security… design process management).  Not all that different from an eProcurement system (catalog management, purchasing, contracting).  The key value through life is not that it can handle these day to day tasks.  The key value is based on the fact that it builds an endless repository of all of those transactions.

In the PLM world, this data could be used to create design best practices, or it could be used for intelligent trouble shooting of design flaws.

In the eProcurement world, this data powers Purchase Decision Optimization (PDO).  PDO means that each and every purchase can be optimized, based on previous buyer experience, supplier performance, trends, etc.; the kind of social marketplace that has become 2nd nature in the consumer world, but is still rare in business to business transactions.

So, whether it’s design data in a PLM system, or purchasing data in an eProc system, it’s not how you get the data, it’s what you do with it once you have it that counts.  Learn more about PDO here.

– RTR