I believe we have come a full circle after couple of decades of building use case based products to integrated products to finally wanting to use best of breeds in different areas and building some sort of integrations amongst those. While Unicode platforms are best way to move forward, not all users or organizations have appetite to take on all areas together. If we think about the history, any new solid innovations never really made big but new innovations that used the original innovations as their base made the mark. Internet was a top innovation but group who came up with internet as an idea didn’t make as big as apps that used Internet to their advantage.. Google is a great example.
Currently the market of AI is as such. Companies using AI as their base will make it bigger than core AI companies.
Users want a simple orchestration layer to perform their day to day jobs but want inputs from various systems that may exists in their organization. It’s not even about features anymore. What simple form can take user from point A to point B by using data from multiple systems even if they don’t own is going to be the next big thing.
Looking forward to what others think.
Devang Oza – LinkedIn comment regarding TRUE ProcureTech orchestration and intake are ineffective outside of a Metaprise Post (November 20th, 2024)
Matthew Buckingham (Focal Point)
This takes me back to 2008 and what we called Service Oriented Architecture (SOA), it is still advocated by the large ERPs and some other mega-tech companies as a way to be single sources of technology, but it never really worked. We can now do this but in a more diverse technology landscape, enabling “best of breed” or just “good enough for my needs”.
But an overall strategy or approach is first needed. Then, focus on specific needs, maybe using your existing solutions or one of the plethora of functional systems out there with specific use cases.
As Jon W. Hansen is saying above. There are two types of technology. You need the “operating system” to be the foundation of SOA and to ensure the continuity and connection of the “functional systems”.
My Response
Matthew Buckingham, here are a couple of excerpts from a post I wrote in June 2007 that is “interesting” in the context of your comment – https://bit.ly/40HDpfL
“Unfortunately, most purchasing departments “inherit” their software as an adjunct downstream byproduct of either an original finance or IT-centric initiative. This has usually meant that their input had been relegated to the realm of the afterthought versus providing decisive and proactive input when it matters the most – prior to a decision being made. Unless this hierarchical practice is changed, the majority of organizations will end up banking on the SOA train linking disparate and inefficient applications to deliver results in the emerging decentralized world of procurement.”
“Notwithstanding the June 27th, 2007 TEC News article heralding Service Oriented Architecture (SOA) as a “revolutionary technology,” it is ironic that the actual software you use has very little to do with the success of your procurement initiative. In reality, the greatest hindrance to mainstream adoption of innovative procurement practice is the direct result of what I refer to as the hierarchical implementation mechanism that is still firmly entrenched in the marketplace today.”
30
Procurement Insights
With ProcureTech, It’s Back To The Past
Posted on November 21, 2024
0
I believe we have come a full circle after couple of decades of building use case based products to integrated products to finally wanting to use best of breeds in different areas and building some sort of integrations amongst those. While Unicode platforms are best way to move forward, not all users or organizations have appetite to take on all areas together. If we think about the history, any new solid innovations never really made big but new innovations that used the original innovations as their base made the mark. Internet was a top innovation but group who came up with internet as an idea didn’t make as big as apps that used Internet to their advantage.. Google is a great example.
Currently the market of AI is as such. Companies using AI as their base will make it bigger than core AI companies.
Users want a simple orchestration layer to perform their day to day jobs but want inputs from various systems that may exists in their organization. It’s not even about features anymore. What simple form can take user from point A to point B by using data from multiple systems even if they don’t own is going to be the next big thing.
Looking forward to what others think.
Devang Oza – LinkedIn comment regarding TRUE ProcureTech orchestration and intake are ineffective outside of a Metaprise Post (November 20th, 2024)
Matthew Buckingham (Focal Point)
This takes me back to 2008 and what we called Service Oriented Architecture (SOA), it is still advocated by the large ERPs and some other mega-tech companies as a way to be single sources of technology, but it never really worked. We can now do this but in a more diverse technology landscape, enabling “best of breed” or just “good enough for my needs”.
But an overall strategy or approach is first needed. Then, focus on specific needs, maybe using your existing solutions or one of the plethora of functional systems out there with specific use cases.
As Jon W. Hansen is saying above. There are two types of technology. You need the “operating system” to be the foundation of SOA and to ensure the continuity and connection of the “functional systems”.
My Response
Matthew Buckingham, here are a couple of excerpts from a post I wrote in June 2007 that is “interesting” in the context of your comment – https://bit.ly/40HDpfL
“Unfortunately, most purchasing departments “inherit” their software as an adjunct downstream byproduct of either an original finance or IT-centric initiative. This has usually meant that their input had been relegated to the realm of the afterthought versus providing decisive and proactive input when it matters the most – prior to a decision being made. Unless this hierarchical practice is changed, the majority of organizations will end up banking on the SOA train linking disparate and inefficient applications to deliver results in the emerging decentralized world of procurement.”
“Notwithstanding the June 27th, 2007 TEC News article heralding Service Oriented Architecture (SOA) as a “revolutionary technology,” it is ironic that the actual software you use has very little to do with the success of your procurement initiative. In reality, the greatest hindrance to mainstream adoption of innovative procurement practice is the direct result of what I refer to as the hierarchical implementation mechanism that is still firmly entrenched in the marketplace today.”
30
Share this:
Related