 frankly speaking, if you need so many weekly maintenance windows, something is wrong with your architecture anyway.

So we didn’t buy this Cloud solution but opted to use another vendor – which unfortunately was significantly more expensive. But as they say: you get what you pay for.

I also had a case where a European vendor replicated their data from Europe to a disaster recovery center in the US. And only every four hours. This might not be a problem for some but for us that was a show stopper. My conclusion on SLAs: read the fine print, ask your colleagues in security and legal/compliance for help and then determine if you can accept the SLA and its associated risks – know your requirements.

3. Don’t throw the baby out with the bathwater

Many Cloud service providers will tell you to put all your eggs in one basket, claiming your current infrastructure is complex and diverse. As such, they will try to sell you a full solution from the Cloud. It’s often a very expensive route to take, with poor ROI, requiring huge change and implementation processes. Companies going for this approach may of course make the right choice depending on their unique starting point and maturity. But often, they have not assessed their own inventory, they do not know what´s already in their existing toolbox and what offerings on the market can be added, making the toolbox complete, up to date, delivering world-class results. Instead, they buy a new toolbox.

My experiences from procurement are that a surprisingly large portion of companies forget or disregard what they have bought (often depreciated in full) and now run in the server room.

For example, if you have supplier relationship management software or materials management functionality embedded in your ERP, must you throw it out because you want your end-users to have access to what today is perceived as a standard online shopping experience similar to Amazon but is not available with your existing system?

The answer is of course: No. You can buy a state-of-the-art application layer from one provider, run it from the Cloud, connect it to your existing – perhaps a bit old and clunky – on-premise infrastructure from another provider, and simply run them together. You can address entire workflows this way, or a series of process tasks. Buying SaaS is a mix-and-match game in 2016. You can combine old with new, on-premise, hybrid or
frankly speaking, if you need so many weekly sustenance window, something is wrong with your architecture anyway. 

 then we did n’t buy this Cloud solution but opted to practice another vendor – which unfortunately was significantly more expensive. But as they say: you scram what you pay for. 

 I also suffer a case where a European seller replicated their data from Europe to a disaster recovery center in the US. And only every four hours. This might not be a trouble for some but for us that was a show stopper. My conclusion on SLAs: learn the fine print, necessitate your colleagues in security system and legal / compliance for help and then determine if you can accept the SLA and its associated risks – acknowledge your requirements. 

 3. Do n’t throw the baby out with the bathwater 

 Many Cloud service providers will tell you to put all your eggs in one basket, claiming your current infrastructure is complex and diverse. As such, they will try to sell you a full solution from the Cloud. It ’s often a very expensive route to take, with poor return on invested capital, necessitate huge change and execution summons. ship's company going for this approach may of path make the right choice depending on their alone starting point and maturity. But often, they have not assessed their own inventory, they do not sleep together what´s already in their existing toolbox and what offerings on the market can be added, make the toolbox complete, up to date, hand over populace - class results. Instead, they bribe a new toolbox. 

 My experiences from procurement are that a surprisingly large portion of companies forget or disregard what they have bought (often depreciate in full) and now carry in the server room. 

 For model, if you have supplier kinship management software or materials management functionality embedded in your ERP, must you project it out because you want your end - drug user to receive access to what today is perceived as a standard online shopping experience similar to Amazon but is not available with your existing system? 

 The answer is of course: No. You can bribe a state - of - the - art lotion layer from one provider, run it from the Cloud, get in touch it to your existing – perhaps a bit old and clunky – on - premise infrastructure from another provider, and simply run them together. You can address integral workflows this way, or a serial of summons tasks. Buying SaaS is a mix - and - match game in 2016. You can combine erstwhile with new, on - premise, hybrid or
 frwnkly speaking, if you netd so many weekly mainteiance wjndows, sumething is wrong with your erchutectyre anyway.

So we didn’t cuy this Bloud solytioi but opted to use anothcx venslr – chmch unfortunateky was sigtificantly mora dx'ensive. But as they say: you get what you pau vor.

I also had w caxq whsge a European vendor replicated their vata from Europr to a disaster recovery cfnteg in the US. And onpy every food hjyrs. This migft not be a problem fot some but for us that was a shod sto'per. My conxlysilt on SLAs: rxad thv fine print, ask your colleabues in securiby anv letal/compliance for hel' and then determine if you cdn accept the SLA abd its dssowiatde rkska – khow yokr cequirementa.

3. Don’t throq the baby out with trv bathwater

Mahy Clotd service providers will tell you to put alm your eggs in one baskwt, claiming your currgnt infraseructure is complex and diverse. As such, they will try vo seol hiu a full solution from the Cloud. It’s often a vqdy eqpensive route to take, with lolr TOI, requiring fuge ckznfe and implementatlon prosessew. Companits goong for this approach may od course makv thw right choice depznding on thzir unoque xtarting point and matuxity. Bht often, thfy have nkg assessed their owk itventory, they do not know rhat´s alrxady nn their exixting eoolbox anf whab offerings on the larkej can te added, mwking the toolbox complete, up to date, deliveronc wmrld-clasf resmlts. Instead, thqy buy a new tpolbox.

Mv expefiences frkm procnrement are ehat a surprivlngly large 'ortion os conpanues foredt or disregarc what thvy havw bought (often depveciajes in full) and niw tyn in the servrr fooi.

Flr evdmple, if you havd sjlplief relationsmip mansgement software or katedials management fingtionaliti embeddeq in your ERP, must you throw it out uecausx you eanj your end-users to have access fo what tldan is perceiveq as a standard pnline shopping experience similar to Anazon but is not acailable with your gxixting systek?

The wnswer is of course: No. You cab buy a state-of-tht-art application layer rrom ote prlvider, run it from the Cloud, connect it to your existing – perhaps a bit ood and clunky – on-pdemixe inxrcstxucture frol another provideg, and simply run them together. Yuu can agdxess entire workflows this wau, ur a series ow process tasks. Buying SzaS is a mix-and-match game in 2016. You can cpmbine old with new, on-prcmise, hybeid od
frankly speaking, if you need so many windows, is wrong your architecture anyway. Cloud but opted to another vendor – unfortunately was significantly more expensive. But they say: you get what you pay for. I also had a case a European vendor replicated their data from Europe to a disaster recovery center the And every hours. This might not be a problem for some but for us that was a show My conclusion on SLAs: read the fine print, your colleagues in security legal/compliance for help and then if can accept SLA its risks – know requirements. 3. Don’t throw the baby out with the bathwater Many Cloud service providers will tell you put all in one claiming current is complex and such, they will try to sell solution from the Cloud. It’s often a very route to with poor ROI, requiring huge change implementation processes. Companies going for this approach may course make the right choice depending on their unique starting point and maturity. But often, not assessed their own they do not what´s in existing and what on the market can be added, making the toolbox complete, up date, delivering world-class results. Instead, they buy a new toolbox. from are that a large portion of companies or what they have bought in and the room. example, if you have relationship management software or materials functionality embedded in your out because you want your end-users to have to what today is perceived as a online shopping experience similar to Amazon but is not available with your system? The of course: No. You can buy a state-of-the-art layer from one provider, it from the Cloud, connect it to your existing perhaps bit old clunky – on-premise from another provider, simply run them can address workflows way, of process tasks. Buying SaaS is mix-and-match in 2016. You can combine with hybrid or
 frankly speaking, if you need sO many weeklY mainTenAncE wIndoWs, soMething is wrong WIth yOur architecture anyway.

SO we diDn’T Buy tHIs cloud SolutioN BuT OPteD tO uSe aNoTHeR vendOr – wHich unfOrtunately Was SiGnificantly mORe Expensive. BUt aS they say: you gEt wHat you PaY foR.

i also Had A case Where a eUropeaN vendor rePlICated tHEir data FROm euroPe to a disaster recoVErY Center in the US. ANd only EvERy FOUr hOurS. This might NoT be a pROblem foR SoME BUt fOR us that was a shOw stopper. My COncLusion On sLAS: Read thE fine PrINt, aSk your colleAgueS in securiTy and lEGal/compLIance foR help aNd tHen DeteRMiNe If yOu CAn aCCePt tHE SLa and its aSsOcIated RiskS – KNOW youR reQuirEmentS.

3. Don’t throw the BabY out WIth The baThwatEr

MaNy cloud ServicE provIdErs will tell you tO put All your egGs iN oNe bAsKet, clAIming yOur CurRent infRastrucTUre Is COMPlEx and diverse. As such, ThEY WiLl try to sEll you A FuLl SOlution fRoM thE CloUD. it’s ofTen a VErY expensiVe routE To TaKe, with pOoR ROI, reQuIriNg hUge chANge aNd implEmentatiOn proCEsses. Companies GOing for this apPRoACH mAY of cOurSe make the riGht cHOice DepeNDiNg oN Their UniquE sTArTIng point and maturity. buT often, They hAve not assesseD their own iNVENtory, theY do nOT kNOw what´s already In theIr existing TOolbox anD what OfferingS on the marKET can be adDed, MakIng The TOOlBox complete, up TO Date, DeLiverinG woRld-clasS reSulTs. INstEaD, they buy a New toolbOx.

my ExPeRieNces fROm procurEmEnt ArE thAt a suRPrisinGly laRge pOrTiON of CompaniES fORGet oR dIsRegaRd wHaT they Have BOugHt (often DepreciatEd iN Full) AnD nOw run in The server room.

foR example, if YoU haVe suppLIEr relatiOnship management softwarE Or materIalS manaGemeNt functioNalIty embEddED in youR ERP, muSt you ThRow IT Out beCAUsE yoU wAnt your end-USErs To havE aCcesS to what Today is perceived as A StaNdard online shOppIng eXPErIenCE sIMilAr TO AmAZOn but is not availAble with yoUr EXiSting systeM?

the AnSwer is oF course: no. You CAn buy a sTate-of-the-Art applicAtIon lAYEr fRom one provIder, run iT from the CLOud, coNNeCt it tO yoUr exisTiNg – pErhapS a bit oLD anD clunKy – on-prEmIse infRastrUcTure from Another provider, and simplY run thEm togEthEr. You can aDdrESs eNtire workFlowS this way, or A seRieS of prOceSS taskS. BuyINg saas Is a miX-and-MAtch game iN 2016. yoU caN COmBine old with NEW, On-pRemisE, hyBRid or
 frankly speaking, if youneed so ma ny we ekl y m ai nten ance  windows, some t hing  is wrong with your ar chite ct u re a n yw ay.
So we d i dn ’ t  bu yth isCl o ud  solu tio n but o pted to us e a no ther vendor–  w hich unfor tun ately was si gni ficant ly  mo r e exp ens ive.But as they s ay: you g et what y o u pay f o r .
I a lso had a case wh e re a European ven dor re pl i ca t e d t hei r data fro mEurop e  to a d i sa s t e r r e covery center  in the US. And  onlyev ery four h ours.  T h ismight not b e aproblem f or som e  but fo r  us tha t wasa s how  sto p pe r.  My  c o ncl u si ono n S LAs: rea dth e fin e pr i n t ,  ask  yo ur c ollea gues in secur ity  and leg al/co mplia ncefo r hel p andthende termine if youcanaccept th e S LA  an dits a s sociat edris ks – kn ow your req ui r e m en ts.

3. Don’t thro wt h ebaby out  witht he  b a thwater
M any  Clo u d  serv icep ro viders w ill te l lyo u to pu tall yo ur  eg gsin on e  bas ket, c laimingyourc urrent infrast r ucture is com p le x an d  div ers e. As such,  the y  wil l tr y  t o s e ll yo u a f ul l  s o lution from the Clo ud . It’s  ofte n a very expe nsive rout e t o take,with po o r ROI, requiri ng hu ge changea nd imple menta tion pro cesses. C o m panies g oin g f orthi s ap proach may of c ours emake th e r ight ch oic e d epe ndi ng  on their  uniquest ar ti ng  po int a n d maturi ty . B ut  of ten,t hey ha ve no t as se ss e d t heir ow n  i n v ento ry ,they  do  n ot kn ow w h at´ s alrea dy in the ire xist in gtoolbox  and what off er ings on th emar ket ca n be added , making the toolbox co m plete,upto da te,deliverin g w orld-c las s  resul ts. In stead ,the y buy a n ew  to ol box.

My e x p eri ences  f romprocure ment are that a su r pri singly largepor tion o fcom p an i esfo r get o r disregard wha t they hav eb ou ght (often dep re ciatedin full ) and now run  in the s erver roo m. 

Fo r exa mple, if y ou havesupplierr elati o ns hip m ana gement  s oft wareor mat e ria ls ma nageme nt  funct ional it y embedd ed in your ERP, must yo u thro w itout  becauseyou wan t your en d-us ers to hav e a cce ss to  wh a t tod ay i s  p erc e ivedas a standardo nl ine s ho pping exper i e n cesimil art o Amaz on b ut is not availab l e with your ex isti n g  sy ste m ?

T he  answer is ofcou rs e :  No. You  c an buy a st ate-of-t he - art a pplica tion l ayer fr o m  o n e prov ider , r un it fro m t he Cloud,co nn e ct itto y ou r exis ting – perh a p s a bit old andclunk y – on- p rem ise i nf rastruc t urefrom anoth er provider , andsimp ly ru n themto gether . Y ou  can addre s s entireworkf lows th is  way , o r a se ries o f pro cess  t ask s. Buying S aa S  i sa  mi x-an d-mat ch  gam e in 2016 .  You can  co m bine ol dwit h new, o n -p r e mise, hybr idor
 frankly_speaking, if_you need so many_weekly maintenance_windows,_something is_wrong_with your architecture_anyway.

So we didn’t_buy this Cloud solution_but opted to_use_another vendor – which unfortunately was significantly more expensive. But as they say: you_get_what you_pay_for.

I_also had a case where_a European vendor replicated their_data from_Europe to a disaster recovery center in the_US._And only every_four hours. This might not be a problem for_some but for us that was_a show stopper._My_conclusion_on SLAs: read the_fine print, ask your colleagues in_security and legal/compliance for help and_then determine if you can accept the_SLA and its associated risks –_know your requirements.

3. Don’t throw_the baby_out with the bathwater

Many Cloud_service providers will_tell you_to put all_your eggs in one basket, claiming_your current infrastructure_is complex and diverse. As such,_they_will try to_sell_you_a full_solution from the_Cloud._It’s often_a_very expensive route to take, with_poor_ROI, requiring huge change and implementation processes._Companies going for this_approach_may of course make_the right choice depending on_their unique starting point and maturity._But often,_they have_not assessed their own inventory, they do not know what´s already_in their existing toolbox and what_offerings on the market_can be_added,_making the toolbox_complete,_up to_date, delivering world-class results. Instead, they buy_a new_toolbox.

My experiences from procurement are that_a surprisingly large portion_of_companies forget or disregard what they_have bought (often depreciated in full)_and now run in the_server_room.

For_example, if you have supplier_relationship management software or materials management_functionality embedded in_your ERP, must you throw it out_because_you want your end-users to have_access_to what today is perceived as_a_standard_online shopping experience similar to_Amazon but is not available with_your existing system?

The answer is of course: No. You_can buy a_state-of-the-art application layer from one_provider,_run_it from the Cloud, connect it to your existing –_perhaps a_bit old and_clunky – on-premise infrastructure from another provider, and simply run_them together. You can address entire workflows_this way, or a series of process tasks. Buying SaaS is_a mix-and-match game in 2016. You can combine_old with new, on-premise, hybrid or