Category Archives: SaaS

Iasta: Smart Source-Style! Part I.

Iasta: Smart Source-Style! Part I.

It’s 2012 and your fiscal year is coming to an end.
It’s time to get a handle on organizational spend.
Because if you don’t, you will find that the Mayans were dead on.
And in 2013, your organization will be gone.

But there’s no need to worry because, Iasta’s got (To the tune of Gangnam Style)

Sourcing Smart-Source Style.
Smart-Source Style.

Sourcing platform for users and bosses too. Sweet.
SaaS on the cloud, always on, real-time reporting complete. L33t.
Analyze this. Auctions, Performance. Real time data.
Optimize It. Contracts, and vendor schema.
One. Two. Smart-Source Success!

So what’s changed since we last covered Iasta in depth in 2008/2009? Especially since the solution footprint looks the same from a cursory review of their web site? If you’re taking a thirty-thousand foot view, not much. But if you take the time to get down in the weeds, everything!

The biggest changes are:

  1. Native Analytics Capability
  2. Improved (Native) Contract Management Capability
  3. Better, Integrated, SIM and SPM Capabilities
  4. Extensive Support for Third Party Data Feeds
  5. P2P Integration Capabilities
  6. Customizable Reporting and Dashboards for Users and Executives
  7. A Broader Services Offering

Native Analytics Capability
A few years ago, Iasta was dependent on third parties like BIQ, now part of Opera Solutions and Spend Radar, now part of SciQuest for their spend analytics capability. And while they still make use of third parties for initial cleansing and classification in new initiatives, they now have the same slice-and-dice reporting capability that you’ll find in any other sourcing suite on the market. (And while it doesn’t have the data analytics power of best-in-class solutions like BIQ, it is the 80% solution for most sourcing departments, especially in the mid-market, which typically have very little insight into spend.)

Improved (Native) Contract Management Capability
A few years ago, Iasta’s contract management capability was limited to the definition of a few meta-data elements. Now, it’s a fully featured contract management offering that allows for storage and indexing of all your contracts, authoring of new contracts, and automated reporting for SOX (Sarbanes-Oxley) to keep you out of stripes like Fox.

Better, Integrated, SIM and SPM Capabilities
You wouldn’t know it from their web-site, but Iasta has developed some fairly extensive built-in SIM/SPM capabilities that your organization can use to track compliance, performance, sustainability, and risk data elements that can have an impact on your sourcing events. In addition, this is integrated with the supplier data that has always been collected in the RFX module and the contract data in the contract module and all of this data can be sliced and diced by Iasta’s built-in analytics and reporting modules.

In Part II we’ll cover the remaining significant changes.

Technology Trials 2012 – Part IV.ii

In Part III, where we assumed that you needed to find a new solution, be it a partial best-of-breed (BoB) or a full supply suite (FuSS), we discussed the critical question that you needed to answer – do you need a point solution to fill a gap or do you need suite to modernize your process and capabilities?

In yesterday’s post, we assumed that you answered the question and determined that you needed a point best-of-breed (BoB) solution to fill a gap in your solution foot-print. In today’s post, we assume that you determined that you need an end-to-end full supply suite (FuSS) to deal with your supply issues.

(04) What are the critical functions that the solution must have?

In particular, as we are dealing with FuSS, we need to ask:

  (04.1)Are there any integration points?
  (04.2)If integration is required, who can do the integration and what is the timeframe?
  (04.3)What data formats need to be supported for supplier collaboration?
  (04.4)Is the solution a foundation for another solution? Can it be extended / integrated as needed?
  (04.5)Are there any known advantages or disadvantages to hosted or SaaS?
  (04.6)Who should support the solution?
  (04.7)What are the training and support options?
  (04.8)What are the normal use-cases that cover normal, and 80% of, expected usage?
  (04.9)Is the vendor likely to be around supporting this solution in the long term?

  (04.1)Are there any integration points?
Do we need to integrate with an ERP, MRP, or suite solution for another supply chain process? E.g. A sourcing platform may need to suck in the transactional data from an e-Procurement platform for spend analysis and spit the contracts out into the platform so that m-way matching can occur against each requisition before it is made and each invoice before it is paid. Similarly, a logistics platform may need to suck in requisitions and spit out inventory levels / goods receipts.

  (04.2)If integration is required, who can do the integration and what is the timeframe?
Can it be done in-house, by a vendor, or will a third-party be required? How long is it likely to take? (If integration will take 3 months, then a solution MUST be selected 3 months before the suite is needed.)

  (04.3)What data formats need to be supported for supplier collaboration?
What formats are you currently accepting supplier data in? What formats do you need to accept to get more suppliers online? Where is the electronic marketplace going?

  (04.4)Is the solution a foundation for another solution? Can it be extended / integrated as needed?
Are you on the market for a procurement suite with the intention that you will be supplementing it with a sourcing suite at a later time, or vice versa? Are you planning to build your entire supply chain foot around a market-leading e-Sourcing platform? Know the answers to these questions up front — don’t be asking them after the fact!

  (04.5)Are there any known advantages or disadvantages to hosted or SaaS?
As with the BoB discussion, if your organization employes enhanced security protocols, does not have the resources to support a system in-house, etc., these restrictions should be known in advance of system selection.

  (04.6)Who should support the solution?
You? The vendor? A third-party? Or does it not matter?

  (04.7)What training and support options are availble to you or will be required?
If there is no in-house expertise on the type of solution the organization is searching for, expertise on the process and the platform will be required. If there is in-house expertise on the process, then only expertise on the solution will be required. In addition, are there individuals who can be trained as trainers, or will external resources be required to train new users on a regular basis? If the latter case, you will need a vendor with a consulting/training team, or one that is big enough that third parties offer that trainig.

  (04.8)What are the normal use-cases that cover normal, and 80% of, expected usage? And what are the abnormal use-cases that cover high-ROI scenarios in the remaining 20% of scenarios?
Just like you should never go to market for BoB solution without knowing the typical and atypical use cases you need to support, you should never, ever go to market for a FuSS solution without knowing the typical and atypical use cases you need to support! Otherwise, the ROI that you expected may not materialize.

  (04.9)Is the vendor likely to be around supporting this solution in the long term?
Whereas this is not that critical for a BoB solution, as you can always replace it in a few years if need be, this is very critical for a platform solution as you know you will be stuck with the solution for at least 5 years, if not 7 or 10 — even if it’s SaaS, because the bigger the solution footprint, the longer it takes to get it replaced in an organization. So you better make sure that the vendor is stable and likely to be for years to come.

Technology Trials 2012 – Part IV.i

In our last post, where we assumed that you needed to find a new solution, be it a partial best-of-breed (BoB) or a full supply suite (FuSS), we discussed the critical question that you needed to answer – do you need a point solution to fill a gap or do you need suite to modernize your process and capabilities?

In this post, we’re going to assume that you answered the question and have determined that you need a point best-of-breed (BoB) solution to fill a gap in your solution foot-print. In tomorrow’s post, we will assume that you determined that you need an end-to-end full supply suite (FuSS) to deal with your issues.

Once you’ve decided that you need BoB to help you fill a critical issue, because the need was contained and the ROI analysis indicated it was the best approach, the next (set) of question(s) you need to answer is:

(04) What are the critical functions that the solution must have?

In particular, as we are dealing with BoB, we need to ask:

  (04.1)What are the integration points?
  (04.2)What data formats need to be supported?
  (04.3)Are we limited to hosted or SaaS?
  (04.4)Can the solution be supported in-house?
  (04.5)What additional training will be required?
  (04.6)What are the use-cases? What is the expected ROI??

  (04.1)What are the integration points?
Specifically, what data do you need to get into the best-of-breed point solution from your existing platform / suite, and what data needs to be pumped back into the platform / suite when you are done with the best-of-breed solution?

  (04.2)What data formats need to be supported?
In particular,
    (04.2.1)What data formats are used by the platform / suite you need to suck data out of and spit data into?
    (04.2.2)What data formats are used by your suppliers / partners / third parties that provide data you want to get into the best-of-breed solution?
This is typically all of the data formats that you need to support for BoB.

  (04.3)Are we limited to hosted or SaaS?
If the current platform is hosted, and strict security requirements would make a SaaS solution almost impossible to deliver, or if the current platform is SaaS, and the integration or support requirements would make a hosted solution unnecessarily expensive, or if there is an edict from above that all solutions must be hosted for security or control reasons or must be SaaS due to lack of technical support, this must be known before potential solutions (and vendors) are selected.

  (04.4)Can the solution be supported in-house?
If it can’t, then the organization will either have to go SaaS (if it has the option), or contract a third-party to maintain a hosted solution.

  (04.5)What additional training will be required?
Even if the selected solution is “plug-and-play”, there’s no guarantee that your talent will have the training required to “play” with the solution as soon as it is available. You can’t just give a man a hammer and a chisel and expect him to magically transform into a master artisan.

  (04.6)What are the use-cases? What is the expected ROI of each use-case??

Before you go looking for a solution, and more importantly, vendors to support that solution, you have to know what the typical daily needs are and the atypical use-cases that you need to support (because they have high ROI) are. Software isn’t about features (and selection is not about feature check-lists, and any vendor who insists they are should be transported back to the middle ages and given free accommodations in the Tower of London where they knew what to do with people who preached blasphemy) – it’s about functionality. Any vendor can add a dozen new features into the next release, but if they don’t enable your process and save you money, what’s the point?

Technology Trials 2012 – Part I

As indicated in Monday’s post, for many of you it’s contract renewal time with respect to many of your installed and SaaS platforms, and time for you to decide if it’s time to move on to new pastures or keep grazing the one you’re in.

It’s a tough decision, and the software giants don’t make it any easier. With new buzzwords every year, new features by the dozens (that may or may not help), and new delivery models with pricing models so complicated that your CA’s head spins, it’s often tough to know what to do.

And every situation is so unique that there’s no way that one post can even begin to give you all the answers (which is why SI did a very rare thing and ran a “best-of” technology post week to try and illustrate the breadth, and complexity of the problem).

But no matter what your situation is, there is some common ground and some questions that must be answered in order to find the path that will lead you to the right decision.

(01) Is your current solution supporting the process you need?

By this I mean the process you have identified as being the right process to support the requirements you have identified for your sourcing, procurement, logistics, etc. function. And by support, I mean that you can implement the majority of the process adequately in a reasonable amount of time. If you can implement all of the core functions and 80% of the non-core functions, and can you do so without a noticeable slow-down in productivity, then it is, at the very leaset, adequately supporting the function. It doesn’t have to be a 100% solution (as we all know there is no such thing; there is a special case that will break every solution), and it doesn’t have to be the fastest (as shaving 10% off the top of process time doesn’t really save enough of your time to be considerably more productive or value generating), but it has to be at least average.

Yes – then, unless costs are increasing significantly, or a strategic solution analysis has indicated that another solution will provide considerably more saving or value generation opportunities in the future, then you should probably stick with the existing solution as the cost of switching will not be made up in the short-, or even mid-, term

Yes-And-No – the solution does most of what you need, but there are a few notable deficiencies that need to be addressed: if there are best-of-breed / standalone solutions that can address these deficiencies, then it’s probably best to stick with what you have and fill the holes with point solutions, otherwise, the answer is really No

No – you need to find a new solution – the only question is how much time you have until renewal and how broad a footprint your current solution has; if the footprint is broad (beyond one function) or has many years of data, then you will need at least 3-6 months to replace it; so, if you have less than 3-6 months, you have to pretend the answer is Yes, keep the solution for one more year and start a strategic solution analysis; otherwise, you start searching for a new solution right away

In Part II we’ll discuss what comes next.

Why Your “Peers” Buy Stupid Products


Since we’re on the topic of technology acquisition, which for many of you translates into SaaS renewals, it’s a great time to dig this post up from the archives, that was originally posted on 6-Jan-2010, on why your “peers” buy stupid products because it’s a great education on the pitfalls you could fall into if you lose sight of the goal.

For a while, I was thorougly confused as why your not-so-enlightened peers (who aren’t the smart and sexy leaders and innovators that you are, as they don’t constantly educate themselves and read industry leading blogs like this one) buy stupid products. While there are a number of great products out there, which I attempt to profile here on Sourcing Innovation as often as circumstances permit, there are also a number of bad products out there (which fall into the “products I don’t cover” bucket, which, to be fair, also contains “products of vendors who still think new media is a fad not worth spending time on” [even though they should probably be covered on SI]). This mix includes some really bad (installed) products that, year after year for reasons that escape me, keep selling, often for obscene amounts of money — especially when you consider what these products actually do compared to what newer, leaner, meaner, SaaS products do for a fraction of the price.

After a few enlightening conversations with some old pros and highly intelligent consultants (who shall forever remain nameless to protect the innocent), I have realized it is either because

  1. the buyers are timid field mice afraid to make a mistake;
  2. the buyers are lazy and inept, they know it, and they don’t want anyone to find out; or
  3. the buyers are yes-men and work for managers who are morons and
    • way too easily impressed by flash without substance; or
    • way too easily impressed by name dropping; or
    • (real) good buddies with (a member of) the vendor management team (who they just happen to be sharing a hotel room with on a regular basis)

In the first case, the buyers often look for the biggest vendor in the space who currently has the “best” reputation and simply use the “Well, no one ever got fired for buying IBM” excuse, replacing IBM with the “big” vendor of the day. This isn’t always bad, as some of the current “big” vendors do have some pretty darn good solutions, but it often is a bad choice because not all products in their “big” vendor solution suite are equal, and, most importantly, even the best product the “big” vendor has might not be appropriate to a particular company’s situation. An MRP won’t solve your problem if what you really need is an on-line RFX and e-Auction tool.

In the second case, the 9-to-5 buyers — who give intelligent, hard-working, and successful procurement professionals like you a bad name — are pretty sure that a good product would quickly uncover the millions of dollars of waste from unmanaged or non-compliant spend, or quickly uncover the lack of process that allows maverick spend to run unchalllenged, or quickly uncover the sheer amount of work they are not doing but should be (like managing spend, sending out RFPs, doing post-bid briefings, etc.) and want to do everything in their power to make sure that they get a solution that is as inept and inefficient as they are.

In the third case, even if the yes-men identify, and want, a good solution, Maury the Management Moron steps in and strongly recommends the worst solution identified (and indicates the buyer’s job could very well depend on making the “right” choice) because:

     

a) it has a nice flash interface with (useless) dashboards and colorful graphics-rich reports that make his under-developed brain go “ooh” and “aah” (while failing to tell you anything that you didn’t know already, like you spent 800M and your top 10 suppliers included 8 of the suppliers you regularly send million-dollar purchase orders to)

b) the company has a lot of “big-name” competitors as customers and / or a number of “big-name” companies your CXO really admires and, therefore, must know what they’re doing and be the right choice (even if they haven’t upgraded their solution in 5 years).

c) the company “obviously has a superior product” even though the real reason is that the company has one or more senior managers that are your boss’ golf buddies and/or hotel room buddies.

And sometimes, it is a combination of these reasons. The buyer knows he is lazy and/or inept, isn’t overly concerned with improving himself, but desperately wants to keep his job (which pays very well considering the amount of effort he actually puts in). He also knows he works for Maury the Management Moron who is easily impressed by flashy dashboards and pretty reports and so chooses a solution that will simultaneously make Maury’s mouth moisten while failing to uncover anything that could be embarassing and jeopardize his job in anyway.

For example, for our timid buyer with Maury the Management Moron for a boss, it would be really bad if he acquired a modern contract compliance system when he recently spent Millions on the current EIPP system two years ago and just found out it contains a big gaping hole, that a few of his suppliers have been exploiting since it was installed, that allows the supplier to charge whatever they want on substitutions and holds, regardless of what contract pricing is in place. For example, he just found out that if:

  1. he punches out for a SKU and
  2. the vendor is out of stock and
  3. the vendor places the order in the “on hold” queue because they don’t want to reject the order then
  4. when the SKU arrives and
  5. the vendor brings up the “on hold” order to “fill” it
  6. the price field isn’t carried forward to the “active” queue so
  7. the vendor can enter any price it likes, which is usually “list” and
  8. the system doesn’t do an invoice-price-vs-contract-price comparison, allows the “list” price, and doesn’t even flag it as pricing that violates the contract.

So, because he thought a few million would buy him perfect software (and didn’t do his homework), he just assumed everything was wonderful, paid what the vendors asked, and lost millions over the last couple of years. He’s not entirely sure how many millions, but is fairly certain that 15% to 20% of purchases were made off of contract pricing. He can’t let the boss find out! (Even though there are specialist consultancies out there who are great at finding these overcharges and helping their clients recover their money.)

Finally, he knows that his boss, easily impressed by flash, is too dumb to realize that dashboards, static reports and “real time alerts” are — when you really think about it — incredibly stupid ideas at the core. For example, so what if the boss can instantly see that 90% of shipments are on time. All that tells you is that 10% of the shipments are not on time. It doesn’t tell you what shipments, to whom, why, and more importantly, what to do to fix the situation. A report that you spend 10M with Wesley’s Widgets isn’t very useful. If that’s all I have, here’s how the negotiation is going to go. “We demand a 10% discount because we spent 10M last year.” ‘So? The price of steel went up 20% … you should be thankful we only raised prices by 15%!‘ “Uhm … erm …” If I don’t know what % was on steel parts, and what % of cost was steel in those parts, I can’t negotiate anything meaningful. And how useful is a “real time alert” at 3 am in the morning that tells you that your container is stranded 500 miles from port because the 3PL forgot to transmit the manifest 48 hours in advance and the carrrier isn’t allowed to enter American waters. Not! You need a system that tells you what you have to do before the order is shipped.