4.1. RQ1. How Are SPA Being Used, Focusing on the Type of Applications Deployed and Their Op-Erational Implications?
Many interviewees commented on the range of applications which are available in strategic procurement. R06 commented “there are a lot of tools available and a lot of different solutions” but both R01 and R06 noted that there is a lack of interconnection and harmonisation between the applications. R01 pointed out “a typical situation is that it’s a bit here and there… (there are) a lot of things already available, (that) are not automatically linked”. Partly because of this lack of integration, several respondents, coming from different commodities (R05, R06, R15), reported the utilisation of manually maintained databases, e.g., for annual supplier performance reviews or contract overviews. In one commodity, a central database was required to be updated by members with predefined information, e.g., received or sent claims, value, aircraft programme, components and expected settle date. Usually, these databases are used for management reporting purposes.
Respondents described their individual experiences and knowledge about the specific applications. Qlik Sense, an analytics tool which visualizes data from Skywise and other sources, was known by several interview partners and actively used by some of them (R02, R06, R15). R02 informed that Qlik Sense is used for visualisation of “actual supplier performance, to have an overview of all our suppliers’ capabilities and current capacity at any time”. In addition, a recent transition from SAP Business Warehouse (an application used for price and spend analytics) to Qlik Sense for spend analysis was witnessed. In the past, it was extremely difficult to determine the spend per supplier for a specific product group, e.g., simple aluminium sheet metal. The identification of the supplier is relatively simple, but the allocation to a specific procurement commodity and thus the determination of business volume with a certain supplier for a specific group of products has, to date, often been inaccurate and out-of-date. The source of this problem was identified as the error prone process of allocating material groups to new parts in the SAP ERP system. This is based on people’s knowledge and experience, and determines the classification of a material and, thus, its belonging to a particular strategic procurement commodity.
R15 concluded that Qlik Sense is used heavily as a visualisation tool including several interactive dashboards. A few interview partners (R01, R02, R03) mentioned corporate business intelligence, where published information about suppliers, customers, competitors, and the aviation industry as a whole, are received in a consolidated form. The P360 system was described as an application platform consolidating data from different internal procurement systems, such as SAP and the company-wide sourcing tool ePROC, while also including external web-based data.
The application P360 provides an overview of all procurement end-to-end (E2E) activities, and enriches it with external data, e.g., for proactive risk management (R01, R04, R05, R06). It enables the creation of individual dashboards (self-service analytics) containing all data of interest, e.g., supplier spend, performance, contractual documentation and external alerts. Drill-down menus allow a high level of granularity up to the part level, e.g., to indicate which suppliers have delivered a specific part in the past. As for Qlik Sense, most interview partners knew the name of the platform or at least were aware of it, but only a few respondents actively used it. R06 acknowledged that the “data is somewhere available centrally (i.e., stored in the ERP system) where you had in the past to request many different departments … … to provide spend reports”. However, R06 mentioned noticeable master data integrity issues and the absence of simple user manuals. The frustration about unreliable data entry (R07, R13) was shared by other respondents.
Some general reference was made to Skywise, an open data platform developed for the aviation industry (R04, R06, R07, R08). More specifically, R11 and R15 were aware that the platform was used for the extraction of data for strategic procurement KPI building, but not for further data analysis for procurement commodity management. A few respondents reported the use of Google Data Studio (R04, R14), where the application connects data from Google Sheets and visualises data into a picture or report. In one commodity, Google Data Studio was implemented to create an easy-to-understand picture of low performing suppliers that were managed by this specific strategic procurement function, and thereby avoid the manual creation of several Microsoft PowerPoint presentations. R15 summarised today’s application of SPA. It “serves for the creation of dashboards to facilitate visualisation and reporting of past transactional data”. Ideally, SPA would be used for forecasting purposes, but at present this is performed on a limited basis via forecast methods built into the SAP system.
Overall, there was a perception among interview participants that they were aware of the existence of the specific applications and could name the applications, but they could not operate them (R05, R06, R09, R11, R12, R13, R14). “There are a lot of tools, but I think most of us are not in contact with the tools” (R06). One respondent mentioned that the introduction of a technology is left to the individual commodity management to decide upon (R15). R01 consistently emphasised that he/she was not aware of a strategic procurement technology strategy. The responses to the question concerning the type of information provided by presently available SPA revealed different understandings of data analytics applications by the interview participants (see
Figure 8). The applications implemented to date are generally of a descriptive character, providing insights on historical data.
The full potential of advanced data analytics has not yet been exploited. R1 found that good progress has been made applying the Skywise platform, but “the power of analytics really leveraging information from, for example our suppliers, our supply chain, maybe Engineering, I would say we’re not really there yet” (R01). R01 envisaged the utilisation of SPA for strategy development by leveraging all available internal and external data, for example, market views or new possible entrants, suppliers, or technologies. Participants evidenced that currently this knowledge is put together manually. Furthermore, the introduction of contract analytics or applications that simulate different negotiation strategies was estimated to be of particular interest (R01). R07 reflected on the positive progress made by deploying Skywise for procurement data, but still sees the case study organisation being on the “starting blocks” of digital transformation, and that there is “a long way to go” in terms of applying data analytics, such as automating, managing, and accessing contractual and commercial data, as well as finding new ways to collaborate with suppliers. However, positive feelings about the future were expressed.
The perception as to whether the existing data analytics applications are well integrated within the technology and process landscape ranges from “partially” to “poorly” or “almost zero” (R02, R04, R05). R02 noticed a partial integration but observed the lack of a systematic approach to allow “the backflow of this data into the technology, especially technology or process landscape of other functions” (R02). The respondent criticised the current separation of data storage and extractions and applications for analysis (i.e., there is no end-to-end visibility in one function), suggesting that they might be available in another department. Insights are predominately shared in rather traditional ways such as discussions, emails, and Excel files. The landscape of used applications is neither harmonised nor integrated between functions, e.g., between the engineering and strategic procurement departments. Overall, insights from one function are not considered or do not trigger technological or procedural change in another function. Problematic issues are the complexity, the vast amount of data, and difficulties in technology operation by staff members, even after training. The long lifetime cycle of the product, and thus the requirement to maintain data over a long period of time is a peculiarity of the aviation industry, which was identified as another obstacle to establishing proper data integrity. R04 reported that a project involving the replacement of the current sourcing tool ePROC had to be stopped due to the lack of adequate fit between the proposed new tool and existing procurement processes. Furthermore, the view was expressed that the high number of different data pools leads to a lack of clarity regarding where the master data sits and which functions maintains it. The integration of different technologies was poor, and some are not connected, e.g., the sourcing tool and SAP ERP systems (R06).
In summary, a large number of relevant tools are available in strategic procurement, but their effectiveness is hampered by a lack of knowledge and awareness and poor technology integration. Overall, data integrity was perceived as poor and a transition of mindset to consider data an asset has seemingly just started. This is despite the deployment of the Skywise platform in 2017, and the overall recognition of the value of data at corporate level. Data used for reporting, monitoring, or decision making requires consultation of different sources (systems and stakeholders) to retrieve it, followed by manual checks, updates, and/or cleansing before being able to use it for the desired purpose. This results in an inherent lack of trust in the data quality which consequently influences the way data is used and impacts confidence in data-driven decision making.
4.2. RQ2. Can a New Maturity Model Be Developed and Validated to Assess the Deployment of SPA in the Aviation Industry?
In the interview process, each of the respondents was presented with the PCF, and asked to indicate the current maturity level for each change dimension in strategic procurement, according to his/her personal perception. In the PCF, the concentric circles (from the centre to the outside) represent the levels of digital maturity, to which are assigned numerical values 1 (low) to 4 (high) as perceived by the 15 interviewees, with the positions furthest from the centre indicating greater maturity of the change dimension. This understanding was shared with the respondents before asking them to identify the present digital maturity of each change dimension in the strategic procurement function. The assessments of the 15 interviewees is shown in
Figure 9. The greatest variation in the assessment by the respondents concerns the technology and process change dimensions. While one respondent (R03) considered the technology dimension relatively mature in the organisation, some (R05/ R12/R13/R14) perceive it to be in an early stage of maturity. R06 sees process maturity as being relatively high, whereas others consider it a lot less developed. The assessment of the people dimension is more homogeneous and balanced between respondents except one rating (R13). The structure dimension displays the lowest level of diversified perceptions.
It is noticeable that, except for the responses from R03 and R12, the maturity rating of the individual change dimensions per respondent is coherent. At individual level, there are no wide gaps between the dimensions, which suggests the change dimensions are interlinked in a multi-dimensional phenomenon. Furthermore, it presents a consistent presentation of the overall maturity of the strategic procurement function in the case study company. While the people dimension seems to be slightly more advanced, the maturity level in the technology, process and structure change dimensions are positioned on average inside the second ring, indicating a lower level of perceived digital maturity. The consolidation of individual ratings by the respondents provides an illustrative synthesis of opinions expressed during the in-depth interviews.
The graphical positioning of the individually perceived maturity per change dimension, shared by each of the respondents during the interview and presented in
Figure 9, can be aggregated to provide an average value of the current level of digital maturity per change dimension (
Table 2). Overall, the strategic procurement function in the case study organisation was perceived by interview participants to be in the early stages of development of digital maturity.
To advance the framework and identify key characteristics of different digital maturity levels, the model was progressed through the inclusion of maturity stages that were loosely aligned with the concentric rings in the PCF. In accordance with Berghaus and Back (2016), the maturity stages reflect the evolutionary path towards maturity. Following this principle, four maturity stages were identified, namely basic, intermediate, standardised and transformed. Building upon some of the concepts identified in the literature review, the analysis of interview responses and the authors’ reasoning, key characteristics for each maturity stage per change dimension were specified. These are set out in detail in
Appendix A, and shown in consolidated form in
Figure 10.
To validate the model, an online survey involving six participants, randomly chosen from the in-depth interviewees, was conducted. The survey comprised seven statements and a five-point Likert scale from Strongly Agree (SA) through Neutral (N) to Strongly Disagree (SD) (
Table 3). In case of disagreement or strong disagreement with a statement, the respondents were requested to provide a brief explanatory comment. After confirming their participation, each contributor was invited to a brief preparation session via video-conference of approximately 15 minutes where the purpose of the online survey was explained, the initially introduced PCF was revisited, and the adjusted model was presented. In addition, a further item (no.8) asked for the re-assessment of the perceived level of digital maturity of strategic procurement, using the grid structure of the digital maturity model, this being approximately 12 months after the initial assessment was given in the in-depth interviews.
Overall, the developed model was considered by five respondents as appropriate to assess the status of actual digital maturity (statement no.1). The design of the model framework encompassing the four maturity dimensions (technology-process-people-structure) and the maturity stages was similarly endorsed by five respondents (statement no.2). The indicators per change dimension and maturity stage were judged as meaningful and sophisticated for the evaluation of the present digital “footprint” of strategic procurement (statement no.3). The model addresses the deployment of SPA in strategic procurement and the experts from the function taking part in the survey acknowledged the practical utility of such, and the guidance the model could provide for the implementation of SPA (statement no.4). Broad consensus was expressed that the model could be used repeatedly over time to re-assess the level of maturity. It was also suggested that the model allows the development of action plans per change dimension and could potentially be used as a support tool for determining and detailing the objectives and actions of a digital transformation programme in strategic procurement (statement no.7).
While two respondents expressed strong agreement with statement no.5 (support for the development of data-driven decision making), half of the participants could not form an opinion as to whether the model had the capability to engender data-driven decision-making (DDD). An underlying issue is the limited acceptance and consequential application of DDD across all hierarchy levels. The general perception was stated that decision making in the case study organisation varies between intuitive and data-driven, both at individual and managerial levels. One reason is the distrust in the accuracy of data. While it was expressed that decision making in strategic procurement was to some extent naturally based on facts and figures, it still highly relies on personal experience and subjective opinion, and that the true incorporation of data-driven working practices is yet to be achieved.
Divided feedback was also provided for statement no.6, regarding whether the model could trigger and help to boost data quality. Half of the participants agreed or strongly agreed, while the other half disagreed or even strongly disagreed. R01, in signaling his strong disagreement, recommended: “PMT (Processes Methods Technology) architecture with core (and limited amount of) tools to be defined and clear accountability for data lakes to be added. Dashboards to drive attention of leadership to improve data quality. Clear priority as top company objective is to drive data maturity”. The enhancement of data integrity was considered a management task, or at least it would require management focus to cascade top-down and develop a sensitivity for data integrity across the organisation. R03 commented on his/her disagreement thus: “we can implement high-tech tools and still struggle with (maintaining) master data maintenance. I do not think that it depends on the model used, but more on the willingness of the organisation in general”.
There was one respondent (R04) who disagreed or strongly disagreed consistently with the statements, pointing out the short-comings of the model, and commenting, for example, in response to statement no.1, that the model “could be a first point of orientation but especially process and technology should be somehow amalgamated”. The dimensions of change were perceived to be too distinct and would hamper an integrative approach for the assessment of digital maturity in the strategic procurement function. Because of the respondents concerns, a follow-up interview was scheduled to further discuss these issues. A high degree of discontent and frustration of how the company progressed with process modernisation to respond to technological change was shared: there is a strong tendency to only focus on the implementation of the technology; the lack of willingness, resources, and capability to truly simplify and adapt processes can result in the deployment of state-of-the-art technology in a legacy process environment; this would then inhibit the successful application and exploitation of state-of-the-art technology, that would impact assessment against the model.
In summary, the respondent perceived the developed model as a matrix as not holistic enough. However, there is broad consensus amongst the academic and practitioner communities that using several interrelated change dimensions as points of reference for the construction and operation of digital maturity models is appropriate, and the respondents’ views were thus taken on board, but were not deemed to undermine the validity of the model. The developed model highlights the importance of, and the high dependences between, the dimensions. It explicitly emphasises the necessity to encompass all dimensions and progress them at a similar pace to successfully transform to a digital organisation.
As noted above, respondents were also requested to repeat the assessment of the current digital maturity of the strategic procurement function in the case study company, applying the adapted model, per change dimension and maturity stage (
Figure 11). The technology change dimension was judged to be at the intermediate stage by five of the six respondents (R01/R02/R03/R04/R05). Even though the SPA are predominately of a descriptive nature, the introduction of diagnostic analytics is an objective. The deployment of the P360 application is an example of how external supplier data can be used for enhanced risk management. Applications for the visualisation of supplier spend and supplier performance with interactive and customised dashboards are widely used. Data integrity is still one of the key issues in the case study organisation. R06 was alone in suggesting technology had advanced to the standardised stage. This respondent has a deep understanding of, and is predominately working with, the Skywise data-platform, with real-time updates, in the role of a data analyst. In a discussion that was held following the online survey, it was mentioned that data integrity, foremost for new data updates (e.g., materials) is improving.
The positioning in terms of process maturity was less homogeneous. R01/R05/R06 concurred in their perception of the process change dimension as being at the standardised stage, which could be interpreted as a reflection of the rigid procurement process applied in the organisation, and emerging RPA applications. However, other respondents gave basic (R03), intermediate (R04), and transformed (R02) assessments of process maturity.
Three participants (R01/R02/R06) assessed the people change dimension to be at the intermediate stage, reflecting the level of digital competencies that the staff of strategic procurement possess. SPA capabilities are still limited to few trained experts. A comprehensive appreciation of the value of data and the importance of maintaining it has not yet been achieved. R04 perceived the level of skills and working practices, as components of the people dimension, as basic. On the other hand, R03 and R05 saw this dimension to be more mature, at the standardised stage.
Structure was assessed to be at the intermediate stage by the majority of respondents (R03/R04/R05/R06), acknowledging the strong commodity focus and perceived silo mentality. The organisation is characterised by a hierarchical structure and a strong line of command. Meanwhile, R02 perceived structure to be at the basic stage, and R01 at the standardised stage.
In summary, the reassessment of the level of maturity by the 6 respondents confirms the value of the model in assessing maturity as regards the deployment of analytics. The collective view is largely in line with the original assessments (
Figure 9), although this sub-set of the interviewees suggest the process dimension is more advanced than the other three dimensions, being at the standardized stage (on average), with the other three dimensions mainly viewed as being at the intermediate stage.