July 11, 2007

e.r.p. and social media are not the same thing, dammit

rich3332.jpg
In res­ponse to my recent post about the lines that sepa­rate ERP and social media beco­ming blu­rrier over time, my old high school friend, Hamish, who works a lot with SAP, talks about ERP and Social Media, and the place where the twain shall never meet.

In SM, the mes­sage that is recei­ved, read or wha­te­ver, is not pre-determined for any pur­pose, it could be a blog entry about how cool sun­sets are, or why LA sucks, the net­work does not care. All inter­pre­ta­tion of the mes­sage is done by the human recei­ver. The lan­guage it is writ­ten in, the con­tent, the refe­ren­ces to exter­nal events and cul­ture, are all par­sed by the human. The soft­ware is just the con­duit, or the envi­ron­ment in which the dis­cus­sion takes place, if you will.
In ERP by con­trast we have a whole load more stuff to do, as all inter­pre­ta­tion is done by the soft­ware, or more accu­ra­tely by rules writ­ten in soft­ware by a desig­ner who is not in situ to inter­vene in any ambi­guous situa­tions. Is the mes­sage a request for spare parts for a car fac­tory deli­ve­red by EDI, or is it holi­day request from an emplo­yee? At the net­work and deli­very level it is not pos­si­ble to tell. The ERP soft­ware has to have a lot of addi­tio­nal infor­ma­tion and pro­ces­sing to deter­mine this, with a cons­trai­ned and con­sis­tent data model, with spe­ci­fic pro­ces­ses that will create dif­fe­rent out­co­mes under dif­fe­rent ini­tial con­di­tions, etc.

I’m wai­ting with bai­ted breath to hear Sigurd’s res­ponse.
[UPDATE:] Sigurd lea­ves a com­ment:

And as I said a bit ear­lier: “Actually it boils down to the defi­ni­tion of what ‘social soft­ware’ is…“
As Chad says — take the fle­xi­bi­lity and trans­pa­rency inhe­rent in SM and add struc­ture to the flows if requi­red and design so that all data and events and wha­te­ver is pro­perly cap­tu­red. Add repor­ting capa­bi­li­ties and voila SM as ERP ;)
(Have more to dis­cuss with Hamish there though as much of the rules-requirements in ERP or pro­cess sys­tems is a lef­to­ver from the good (?) old days of pen and paper inhe­ri­ted “event docu­men­ta­tion thin­king” — but that would be a another story!)

"Hugh's Daily Cartoon" Newsletter. A new cartoon sent out every weekday morning to your inbox [RSS version here.]. A wee chuckle to start your day off right etc.

11 Responses to “e.r.p. and social media are not the same thing, dammit”

  1. Chad says:

    This reminds me of what I hear about main­frame appli­ca­tions, “we’ll never get rid of the main­frame, it’s to com­plex and does deep dark sec­ret stuff”. But some­body must have imple­men­ted it ori­gi­nally. Same with these mys­ti­cal ERP rules. Who’s to say we can imple­ment a much more efficient/flexible/schematized/whatever work­flow on a social plat­form? Some­body must have deve­lo­ped the rules in the first place, why can’t some­body do it again?

  2. keith says:

    Another ama­zing and unfor­get­ta­ble car­toon, Hugh. I will quote you on this one.

  3. I’m with Hamish but for dif­fe­rent rea­sons but there are periphe­ral use cases where social media does have an impact.

  4. sig says:

    *clea­ring throat*…
    And as I said a bit ear­lier: “Actually it boils down to the defi­ni­tion of what “social soft­ware” is.…. “
    As Chad says — take the fle­xi­bi­lity and trans­pa­rency inhe­rent in SM and add struc­ture to the flows if requi­red and design so that all data and events and wha­te­ver is pro­perly cap­tu­red. Add repor­ting capa­bi­li­ties and voila SM as ERP ;)
    (Have more to dis­cuss with Hamish there though as much of the rules-requirements in ERP or pro­cess sys­tems is a lef­to­ver from the good (?) old days of pen and paper inhe­ri­ted “event docu­men­ta­tion thin­king” — but that would be a another story!)

  5. Hold it Sig — where’s the SM com­po­nent here or rather where does it fit in your thin­king? I can see use some cases but you’re being as clear as mud.

  6. Lidach says:

    your pics are really nice and dif­fe­rent :)
    hugs and kisses

  7. Brad says:

    @mark… yeah, but it pro­bably opens up some nice new options for how to do it.

  8. Clive Birnie says:

    For me the pro­blem is dis­course and data. Num­bers and words. The ERP flow is a river of num­bers from which my ERP sys­tem allows me to dip the buc­kets of cla­rity and com­pliance. Its all about the hard num­bers. SM is dia­lo­gue, dis­cus­sion, debate, ins­pi­ra­tion, crea­ti­vity. Well, hey, I need that too so the ques­tions in my mind at the moment are about how can I use SM soft­ware, models, and an open colla­bo­ra­tive approach to help drive pro­cess impro­ve­ment. Pro­cess impro­ve­ment is ongoing and feeds back into our ERP deve­lop­ments any­way but at the moment I just can’t quite put my fin­ger on how exactly I can use exis­ting SM appli­ca­tions inside the company.

  9. momo says:

    Don’t we all? But then again, I do it any­way.
    Fun
    Fun
    Fun!
    H

  10. John Barben says:

    SAP isn’t known for it’s com­pe­tent hand­ling of whimsy

  11. Peter Wilson says:

    Although it is in prin­ci­ple pos­si­ble to use an SM sys­tem for ERP the chance of errors is so high in the gene­ral case that in the near future it will not be prac­ti­cal. You have to take a free­form natu­ral lan­guage input, com­plete with idioms and regio­nal varia­tions, and con­vert that into a rigid struc­tu­red lan­guage. In anything other than the tri­vial case this is an open research pro­blem.
    There are cases like con­ver­sa­tio­nal tra­ding sys­tems where the natu­ral lan­guage used is suf­fi­ciently limi­ted so as to be able to extract mea­ning con­sis­tently, but that is hardly SM.