Monthly Archives: October 2015

Technological Damnation 91: Proprietary Madness Continued


Can I play with madness?
The prophet stared at his crystal ball
Can I play with madness?
There’s no vision there at all
  Dickinson, Harris, & Smith, 1988

And, as a result, big companies have decided to create their own vision, separate from everyone else’s, and thrust their own visions of damnation upon us. Locking us into technology platforms that we just can’t get out of.

Proprietary designs. Proprietary protocols. Proprietary APIs. All designed to lock you in and keep you in chains.

All the big companies in the tech space at large have done it. Adobe. Apple. Google. IBM. Microsoft. Etc. And now some, like Microsoft, are taking it further than we ever thought possible. Earlier this year, Microsoft decided to go beyond automatic updates to automatic OS upgrades without the user’s permissions. (Which, of course, bricked a number of machines due to problems with drivers and underlying hardware incompatibility.) Now, they’ve supposedly backtracked on this, but it seems that those who have been upgraded, or choose to upgrade, to Windows 10 will have updates forced upon them with no ability to choose or defer, meaning their machines could be bricked at anytime! Ouch! (And that’s why the doctor does not use Windows.)

But they didn’t start the fire. (Although it appears they did a lot of research in choosing the best accelerants.) Pretty much every big tech company has forced proprietary designs (that restrict upgrades to other products provided by the same company or authorized partners), protocols (for interfacing), or APIs (for developing) upon us and still does.

And it’s not limited to the tech space at large and underlying operating systems. In our space, we have proprietary networks, like Ariba, that mandates its hosted P2P tool users also use the Ariba network for all connectivity with suppliers, even in cases where suppliers are connected to other networks that then connect to Ariba’s in the same transaction stream (Source: SpendMatters: “Ariba Doesn’t Have Customers It Has Prisoners”). (And since suppliers have to pay to use the Ariba Network, this puts a heavy price tag on purchases through the network as opposed to a network where the buyer pays a flat fee and the supplier doesn’t, because the supplier is just going to increase their prices to cover this cost.) And to make matters worse, as Ariba starts to lose prominence in the traditional analyst rankings, it’s stepping up its efforts with the smaller tier firms who, probably lacking the manpower to do the in-depth analysis the larger firms are capable of, are giving it rave reviews on the plus side with very little mention of the weaknesses on the negative side. Case in point: a recent review by Ovum which called Ariba the “largest supplier network”, listed four strengths, and only one weakness. SI has to wholeheartedly agree with Spend Matter’s review of Ovum’s analysis  in “beware analyst research ovums review of the ariba network” — the coverage of the weaknesses was not thorough or fair and while SI does not have insight into Ariba’s network statistics beyond what they publish, SI does know that Basware’s volume is on par with Ariba’s published numbers. While Basware may not be a household name in North America, they are probably the biggest and most established network player in Europe in this space and one of the oldest (as the company turned 30 this year).

To make matters worse, there’s not a lot of open standards in our space. You could say that we have cXML, which a number of PunchOut sites are based on, but do we? While it is open and free for use without restrictions apart from restrictions relating to publications of modifications and naming, this protocol was not only created by Ariba in 1999 but is still controlled by Ariba. They could change it at any time, force all sites on the Ariba network to update at that time, and offer very little documentation or guidance as to how anyone outside of that network will go about doing that and, more importantly, support multiple versions simultaneously (for those in the network and those not), which would be a major IT headache. Even worse, they could decide to replace it with cXML 2.0, keep that version proprietary, and create a dichotomy where only those in the network have 2.0 and those don’t.

There is no completely free, non-proprietary, fully open-source standard in our space, and no guarantees. Proprietary Madness is a damnation that is going to haunt us for years to come.

Thirty Years Ago Today

The Free Software Foundation, which launched the GNU General Public License, was founded by Richard Stallman, and the fee software movement, which started when he launched the GNU Project on 27 September 1983, began in earnest.

It took less than 15 years from the start of the movement, to the dismay of companies like IBM and Microsoft, for many open source projects, including Linux (1991), Apache (1995), MySQL (1995), and PHP (1995), to dominate the web.

And allow LOLCats everywhere to dominate the web. 😉

Seventy Three Years Ago Today

The space race begins with the launch of a V2/A4-rocket from Test Stand VII at Peenemunde, Germany which becomes the first man-made object to reach space.

Less than nineteen years later, Yuri Gagarin became the first man in space when he orbited the earth on 12 April 1961 in a Soviet Vostok spacecraft.

And a mere eight years later, unless conspiracy theorists are to be believed, the United States put the first man on the moon on 20 July 1969.

Less than two years after that, the Soviet Union launched the first space station, Salyut, and public-sector extra-planetary supply management began.

Speaking of the space race, the Space Shuttle Atlantis made its maiden flight thirty years ago today on 3 October 1985, forty two years after the space race began. Atlantis, the fourth operational space shuttle, flew thirty-three missions and orbited the earth a total of 4,848 times, travelling a distance that was more than 525 times the distance from the Earth to the Moon. Notable missions were it’s 4th, which deployed the Magellan probe bound for Venus, its 5th, which deployed the Galileo probe bound for Jupiter, its 14th, which represented the 100th US manned mission and the first shuttle docking with Mir, its 21st, which was its first docking with the International Space Station (ISS), and its 30th, which was the final Hubble Space Telescope Servicing Mission.

And eleven years ago, less a day, on 4 October 2004, SpaceShipOne won the $10 Million Ansari XPrize when it became the first-even private vehicle to carry a human being into space.

And this year, Space Exploration Techologies, SapceX, became the first company to ship private cargo to the ISS using its own rocket and ship, the Dragon.

And Virgin Galactic is working on a new SpaceShipTwo that could be ready to take commercial passengers into space as early as next year.

It won’t be long before someone puts up a private space station, and private sector extra-planetary supply management becomes a reality. (And when it does, and you need someone to optimize those supply models, you know who to call.)

Infrastructure Damnation 14: Roads


Roll on highway, roll on along
Roll on daddy till you get back home
Roll on family, roll on crew
Roll on momma like I asked you to do
And roll on eighteen-wheeler, roll on (roll on)
  David Loggins, 1984

When we think about transportation in Procurement, we typically think about Carriers and 3PL Firms, two of our provider damnations, but Carriers and 3PLs typically transport your goods using eighteen wheeler trucks, and eighteen wheeler trucks have to use roads. And they have to roll on — which they usually do, until they don’t.

Wait, what?

They roll on until they don’t. Roads deliver their own special type of universal damnation, which impacts Procurement more than most.

Road Hazards: Pot Holes, Sharp Debris, Liquid Tar

Your eighteen wheelers can’t roll on without those eighteen wheels. A pot hole, sharp debris (nails, industrial strength broken glass, etc.), and the asphalt itself (which can reach temperatures 50C or 100F higher than the ambient air temperature in the blazing hot sun) can cause tire blowouts on a regular basis due to the hard impacts, big holes, and the rubber melting temperatures they create. And your truck is grounded until the tires are replaced.

Road Conditions: Often Abysmal at the Best of Times

While the roads in most big cities and the roads that are designated as major highways are typically in pretty good condition in the USA, in some countries, your average highway is full of craters, and sometimes isn’t even paved. So while your goods may roll on at 110 km or 70 miles an hour in the USA, in some places in India, if you can get 30 km or 20 miles per hour, consider yourself lucky. The reality is that in some places, your goods aren’t moving any faster than if they were being transported by an old-fashioned horse-drawn carriage.

And sometimes more prosperous countries will attempt to improve the roads, and the you have construction. Instead of covering 30 km / hr, your driver will spend over half of his driving day sitting in a traffic jam and will watch the horses trot by.

And if the roads are good, and near a big city, everybody tries to use them and you get bumper to bumper traffic jams where traffic moves at about the same pace as a person who is speed walking.

In other words, truck transport is often slow, slow, slow.

Highwaymen

A lot of theft occurs on the open road. Sometimes your driver, on his own, is unlucky enough to be held up at gun point when he stops to investigate a hazard, heed the call of nature, gas up, or grab some hot food at a truck stop. Sometimes, he’s lucky enough to have his rig broken into, hot wired, and driven off when he’s heeding the call of nature in a restroom or eating in a roadside truck stop. Either way, his mode of transportation and your cargo is gone, gone, gone.

Confiscation

Sometimes the highwaymen won’t steal the truck, but will instead try to use it to transport illegal goods or aliens. The driver will pull over at a stop, the truck will be a few hundred kilos heavier than the paperwork says the truck should be, the truck will get searched by authorities, contraband will be found, and the whole truck and all of its contents will get seized. And if he’s unlucky, your driver will get arrested, and then, upon his release, immediately tell you where to stick the next driving assignment you try to push his way.

We may not want to think much about them, but roads are an eternal damnation of the Procurement professional as they are literally what the trucking industry rolls on. Sometimes it really is best to return to the rails.

Influential Damnation 98: Pundits / Futurists

Pundits and Futurists, who are one in the same, are the third influential damnation we are discussing, having already addressed consortiums and conferences. In order to see how these individuals are one in the same, we’ll start by reviewing standard definitions.

A pundit is defined as a person who offers to mass media their opinion or commentary on a particular subject area on which they appear to be knowledgeable.

A futurist is defined as a person who regularly makes predictions about the future, which is precisely what a pundit typically does when they offer their opinion and commentary to mass media!

Why are these individuals a damnation?

First of all, as clearly explained in Sourcing Innovation’s recent series on The “Future” of Procurement: What’s Old is Still Old! and An Expose of Procurement “Future” Trends: Digging Deep to Reveal the Truth, most of what those bloody futurists are proclaiming as the grand future of Procurement is old news, ongoing blues, or remanufactured shoes. Most of what they have been preaching from the worn out pulpit the last few years is the exact same message that their futurist predecessor were preaching one or more decades (or even centuries) ago!

Secondly, like the purveyors of apps, mobile, big data, and cloud, most of their messages are based in fear. If you don’t prepare for this today, you will go out of business tomorrow. If you don’t get this platform today, you will be relegated to the third world tomorrow. If you don’t jump on this process today, you will bleed red tomorrow.

Thirdly, when they get tired of preaching their tired old messages, they jump on the first vendor that gets a bad rap in the gossip chain as a result of an implementation that didn’t go perfectly, typically before figuring out why and who is really to blame. While it’s usually the case that the vendor didn’t do as good of a job managing the project as they should have done, it’s often the case that the customer didn’t heed the advice of the vendor and tried to rush ahead or do something themselves that was difficult without getting proper training and guidance. Enterprise technology, and especially enterprise technology that relies on a lot of integrations, data, advanced analytics, or sophisticated models, is always more involved and difficult to implement, integrate, and configure than you think it is and trying to do it yourself without an understanding of the nuances and gotchas is just asking for trouble. And while it is true that some vendors charge a lot for this service, it was the customer’s choice to select that vendor in the first place so the blame typically rests as much on the customer as on the vendor. And a pundit that just jumps all over the vendor without getting a full picture of what went wrong and how it could have been prevented doesn’t help anyone. We need to identify failings, their root causes, and solutions so that everyone can learn and move forward. Not encourage Perez Hiltons’ to invade our space.

Anyway, they’re a damnation and that’s why if the doctor is anything, he’s an anti-futurist.