The negative impacts of the spaghetti architecture in Supplier Information Management

Thierry Jaffry - October 18, 2017

Most companies are struggling to maintain and update supplier information, leading to financial and performance impacts.

 

1 – Multiple systems create chaos

Because of multiple systems (and we don’t only see that in companies with external growth), the supplier creation process is complex, with many different entry points, and various contributors.

Moreover, many users from various departments may have access to the data, creating and updating suppliers data without any process or control. Unicity check, in such a context, is also quite impossible.

This generates duplicates, inaccurate data and risk exposition. But sometimes, because of the company history/context or investment capacity, it is not easy to start a “One ERP for all” project. Then it’s time to invest in a SIM middleware to bring back supplier data management under control.

 

2 – Team (un)productivity

Fragmented data over multiple systems kills global efficiency. A spaghetti architecture implies a labyrinth synchronization between softwares, sometimes requiring buyers and AP clerks to manually update supplier data in different systems. This duplication of tasks means  hours of unproductive work, and less focus on strategic added value tasks. According to AMR Research, employees spend eight times more energy on managing supplier relationships in companies equipped with a SIM (Supplier Information Management).

spaghetti-architecture-english-1

Figure I: The Spaghetti Architeture

3 – Maintenance Costs

A complex system architecture means costs – whether it’s SAAS or On-premise model. IT departments face challenges every day in maintaining the consistency of data flows between ERPs, BI tools, eSourcing suites and P2P solutions (and we’re only focusing here on supplier/buying side): they have to deal with referentials synchronization, technical issues and conflicts, data mapping, real time interfaces and nightly batches everywhere. Also, as complex integration are built, changing a system configuration requires a deep impact analysis.

Centralizing supplier data in a SIM solution will clarify the architecture and help reducing the number of systems (or optimizing their usage), thus reducing the costs of the global IT architecture.

 

4 – Life with a SIM

The challenges we have pointed out earlier are the reasons why we decided to develop Simetryk – a Supplier Information Management solution.

Simetryk is a one-stop shop to create, enrich, and validate supplier data ; all the associated systems – ERP, E-sourcing solutions, Spend Analytics tools,.. – will then consume accurate and validated data at a defined frequency.

 

diagram-simetryk

Figure II: Simetryk linear process

spaghetti-architecture-simetryk-flower

 

 

 

This solution guarantees a creation/modification/deactivation process under control, as well as data integrity and uniqueness. It also cleanses, consolidates, and spreads supplier data in the connected applications.

 

Conclusion :

As more and more enterprise processes are digitalized through specific solutions, most IT departments need to manage multiple systems (including Saas and On Premises) and associated integration flows. These complex architectures lead to data corruption.

It is now a priority to streamline the data management process and set-up governance. Otherwise, Procurement & Finance (and the whole company) will be exposed to risks, fraud, extra costs and unproductivity.

It's only fair to share...
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInEmail this to someone

About the author

Thierry Jaffry has an extensive expertise in S2P projects working successively with Ivalua and Flucticiel software solutions and integrators. He is the man behind Simetryk.


Want to be the first to know about the next blog release?