# Software Parts Classification for Agile and Efficient Product Life Cycle Management

Anmol Gaurav, Bhanu Prakash Ila, Naveen Mehata Kondamudi, Pinky Deshwal

► To cite this version:

Anmol Gaurav, Bhanu Prakash Ila, Naveen Mehata Kondamudi, Pinky Deshwal. Software Parts Classification for Agile and Efficient Product Life Cycle Management. 19th IFIP International Conference on Product Lifecycle Management (PLM), Jul 2022, Grenoble, France. pp.15-24, 10.1007/978-3-031-25182-5_2. hal-05420928

HAL Id: hal-05420928

https://inria.hal.science/hal-05420928v1

Submitted on 17 Dec 2025

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
<figure><img src="image_2.png" /></figure>

ifip

International Federation for Information Processing

This document is the original author manuscript of a paper submitted to an IFIP
conference proceedings or other IFIP publication by Springer Nature. As such, there
may be some differences in the official published version of the paper. Such
differences, if any, are usually due to reformatting during preparation for publication or
minor corrections made by the author(s) during final proofreading of the publication
manuscript.
# Software Parts Classification for Agile and Efficient Product Life Cycle Management

Anmol Gaurav<fnref n="1" />(✉), Bhanu Prakash Ila<fnref n="2" />(✉), Naveen Mehata Kondamudi<fnref n="1" />(✉), and Pinky Deshwal<fnref n="1" />(✉)

**Abstract.** The proliferation of software components and embedded systems in bundling of smart and innovative products and services has augmented the need of software classification in manufacturing context. Existing software classification standards are limited to information technology, networking, and mobile applications. To gain efficiency in product development through reusability and reduction in search and retrieval time for multi domain part structure development; software classification is imperative.

This paper discusses the different classification and nomenclature systems available for software, its benefits in Product Lifecycle Management (PLM) and other business areas, as well as limitation of existing PLM applications. This paper explains a novel, and contextual framework for classification of software components to enable strategic cataloguing for improved traceability, reusability, and Bill of Materials (BOM) management.

**Keywords:** Software part · Software part classification · Classification framework · Software classification standards · Classification for ALM

## 1 Introduction

Traditional business drivers are no longer sufficient to provide sustainability and growth to an organization. Globalization, pricing pressure, product complexity and competition are new drivers demanding organizations to substitute part of their existing portfolios with innovative products. Burgeoning of embedded systems in products to make it smarter, complaint with new regulatory requirements and experiential offerings for customers have raised the bar [1, 2]. Embedded software market is estimated to grow with CAGR of 7% and would create a value of more than $20 billion by 2027 [3]. Surge in its demand is being seen more in automotive industry due to increased regulatory pressure and advanced features requirements, and in healthcare industry due to COVID-19

<footnote n="1">¹ Business Consulting NPI/PLM Europe Manufacturing, Tata Consultancy Services, 1/G1, SIPCOT IT Park, Kanchipuram 600119, Tamil Nadu, India
{anmol.gaurav,naveen.kondamudi,pinky.deshwal}@tcs.com</footnote>

<footnote n="2">² Business Consulting NPI/PLM Europe Manufacturing, Tata Consultancy Services, Initial Tower, 1 Terr. Bellini, 92800 Puteaux, France
bhanuprakash.i@tcs.com
http://www.tcs.com/</footnote>
impact. PLM applications provide capabilities to define firmware and software as a part and features to link with their executables. But these are not sufficient for manufacturers who are looking to classify their software and firmware parts like hardware parts. There are international standards like UNSPC<fnref n="1" />, ECLASS<fnref n="2" />, GPC<fnref n="3" />, CPV<fnref n="4" />, ETIM<fnref n="5" /> etc. which provide taxonomy for products and services [4, 5]. These standards are highly skewed towards the classification of hardware components. Adopting the current standard of four level hierarchical classification structure is not a fool-proof solution since hardware part can have one to many relationships with the corresponding software parts. Multiple relationships exist due to different supplier, versions, and specific features of the software. This paper covers investigation and analysis on existing global classification standards and has proposed a structured approach for software part classification.

Development of new software classifications standards and harmonized meta data attribute definition will significantly reduce search retrieval time, improve correctness, reliability, reusability and traceability and ease trade across countries [6–8]. For instance, when a designer is looking for a software component to meet a new product specification, the classification attributes would help to narrow down search and give relevant information from large repository of data. This would also help to avoid creation of duplicate parts. In another scenario, a field engineer would be able to reduce root cause analysis time and identify similar components when a warranty claim is reported.

## 2 Classification System

In this digital age, for a company to stay relevant and survive, depends on rate of innovation and its introduction through complex supply chain web [9]. Classification is essential to businesses to improve supplier sourcing strategy, optimize productions, for targeting buyers and reduce business transactions time.

Classification means logical grouping and ordering of large and expanding range of commodity types according to common characteristics. Existing international standards vary in terms of objectives, data model, granularity, breadth of category and adoption with respective to the region and refer Sect. 3 for more details. In general, all classification standards provide coded name, identification number and textual description in noun-modifier combination with different schema. Variety of part types, for example, hardware, electrical, mechanical, software etc. are categorized at different levels. The bar graph given in Fig. 1. shows distribution of categories of software parts at multiple hierarchy levels by 4 popular international standards.

<footnote n="1">¹ United Nations Standard Products and Services Code.</footnote>

<footnote n="2">² ECLASS is a cross-industry product-data standard for the classification and unique description of products and services.</footnote>

<footnote n="3">³ Global Product Classification.</footnote>

<footnote n="4">⁴ Common Procurement Vocabulary.</footnote>

<footnote n="5">⁵ European Technical Information Model.</footnote>
<figure><img src="image_3.png" /><figcaption>**Fig. 1.** Software classes at different levels for 4 global classification standards (Data is compiled from the codeset of each of the mentioned global standards).</figcaption></figure>

## 2.1 Need for Software Classification System and Standardized Data

Business discontinuity due to COVID-19 has accelerated the process to have virtual collaborative environment to take design decisions quickly and need of IT systems with robust integrated data management capabilities. Design specific decisions get delayed due to variability in product data model definition and schema across enterprise level systems like PLM, ERP<sup>6</sup>, MES<sup>7</sup>, CRM<sup>8</sup> and SCM<sup>9</sup>. Uniform, classified & unambiguous data definition form the backbone of any enterprise-wide digital initiative. Manufacturing companies are looking for implementation of international standards for classification of different part types because proprietary standard of classification restricts an organization to collaborate with suppliers, partners, dealers, and retailers.

Available international standards do not fully define and classify different software parts created by R&D. On average, only 1% of total product classes (bottom of the hierarchy) are defined for software parts as shown in Fig. 2.

They provide rich taxonomy and attribute definition for electronic, hardware, electric and mechanical part types but not for software part types. Existing PLM systems only offer association between different part types as shown in an illustration (refer Fig. 3).

<footnote n="6"><sup>6</sup> Enterprise Resource Planning.</footnote>

<footnote n="7"><sup>7</sup> Manufacturing Execution System.</footnote>

<footnote n="8"><sup>8</sup> Customer Relationship Management.</footnote>

<footnote n="9"><sup>9</sup> Supply Chain Management.</footnote>
<figure><img src="image_4.png" /><figcaption>**Fig. 2.** Consolidated software vs hardware classes in current standards.</figcaption></figure>

Only association feature of PLM system is not enough to fulfill the needs of engineering departments and associated areas. There is considerable dearth of software data definition and classification. More and more companies are adopting ALM<fnref n="10" />-PLM integration to strengthen the new product development to reduce time to market but its full potential is not being realized in the absence of standardized software attributes and taxonomy. In current scenario, software data is fragmented and residing in multiple systems with inaccurate, incomplete, and inconsistent information. So, it is imperative to have well-defined classification and nomenclature system for software and its adoption into extended enterprise systems.

<figure><img src="image_5.png" /><figcaption>**Fig. 3.** Illustrative diagram showing software part type relationship with hardware part types.</figcaption></figure>

## 2.2 Benefits of Classification System

Uniform, standard, and common engineering language for product characteristics has significant impact on metrics like engineering hours, procurement time, material costs

<footnote n="10">¹⁰ Application Lifecycle Management.</footnote>
etc. with error free data and less time-consuming processes [10, 11]. It declutters the process for searching of information from different solution providers, catalogues, on internet, by data conversion, and users from different field of engineering. Especially, software classification in digital era in context to hardware will significantly boost mass personalization and enhanced traceability and reuse-based software development [12].

## 3 Analysis of Existing International Standards

Table 1 shows the comparison of top 5 international standards categorizing software components at different levels, and it could act as reference map and further populated

<table><caption>Table 1. Eleven Criteria comparison of international classification standards</caption><thead><tr><th>Criteria</th><th>ECLASS</th><th>UNSPC</th><th>GPC</th><th>CPV</th><th>ETIM</th></tr></thead><tbody><tr><td>Standard Objective</td><td>Empower procurement, sales, engineering</td><td>Procurement</td><td>Buyers & manufacturers in cataloguing</td><td>Public procurement</td><td>Taxonomic classification of technical products</td></tr><tr><td>Classification or Product data dictionary</td><td>Product data dictionary</td><td>Classification</td><td>Product data dictionary</td><td>Classification</td><td>Product data dictionary</td></tr><tr><td>Schema (Classification level)</td><td>Four</td><td>Four</td><td>Four</td><td>Five</td><td>Two</td></tr><tr><td>Applicable Industry</td><td>Multi sector e.g., Automotive, construction, Electrical, Textile etc.</td><td>Multi sector e.g., electronic, Oil, Software, Energy, Healthcare etc.</td><td>Specific sectors such as apparel, consumer goods, etc.</td><td>Specific sectors e.g., Raw material, tourism, toys, Biotechnology, etc.</td><td>Specific sectors such as Electrotechnical, plumbing, shipbuilding etc.</td></tr><tr><td>Semantic definition and Attributes or feature availability</td><td>Partially available but rich in attributes</td><td>Not available</td><td>Available but number of attributes less compared to ECLASS</td><td>Not available</td><td>Partially available but rich in attributes</td></tr><tr><td>Language support</td><td>16</td><td>15</td><td>25</td><td>24</td><td>17</td></tr><tr><td>Geographic dominance</td><td>Germany & other European countries</td><td>US, Asia, Australia</td><td>Global</td><td>European countries</td><td>European countries</td></tr><tr><td>Adoption by companies</td><td>4000+</td><td>2100+</td><td>20L+</td><td>2.5L+</td><td>300+</td></tr><tr><td>Industry 4.0 (Digital Twin)</td><td>Provide library for machine readable characteristics</td><td>No references found</td><td>No references found</td><td>No references found</td><td>No references found</td></tr><tr><td>R&D specific features</td><td>ECLASS ADVANCED is mainly used in engineering and CAx areas.</td><td>No references found</td><td>No references found</td><td>No references found</td><td>Characteristics for 3D product data & Building information management</td></tr><tr><td>Licenses</td><td>Required</td><td>Free</td><td>Required</td><td>Required</td><td>Free</td></tr></tbody></table>
with more contextual criteria. Few standards like UNSPC are more focused on categorization of products and services rather than defining properties and associated values and units.

## 3.1 Classification Schematic Comparison for Software

ECLASS classification standard provides more software classes compared to other global standards (as mentioned in Sect. 2), but it lacks in quality and quantity as well. Newness in the name of software classes is created by appending information in parentheses signals lack of due diligence. Figure 4 elucidates variation in nomenclature and variety of category at different levels of software part classification schema.

Grouping of software are generic and based on how they are used instead of what they are. For example, nomenclature of software is based on application areas like telecommunication devices, office applications, engineering applications etc. There is a lack in variety, associated definition, and redundancy of software characteristics. The repetition of similar attributes also makes difficult to distinguish two disparate classes.

<figure><img src="image_6.png" /><figcaption>Fig. 4. Classification schema across global standards</figcaption></figure>

## 4 Framework for Software Part Classification

Limitation posed by existing international standards urges for further exploration for new approaches to categorize software components. This necessity triggers pertinent questions as mentioned below:
* Are business needs for classification of hardware and software components same?

* What should be the approach? Should it be like current approaches of HW classification; and clustering software components in the same group of HW components?

* How should an organization classify software components? Should it adopt one international standard or custom approach to best serve the organization need?

* What should be the classification schema? Multi hierarchy vs flat taxonomy structure needs to be investigated.

The structured approach discussed in this section is based on our experience in implementation of software part classifications projects and can be guide for an organization to establish center of excellence for software part classification and disseminating knowledge across virtually integrated value chain. The success of enterprise-wide program depends upon strong governance structure and adoption of industry best practices for execution [13]. Setting up vision in line with organization objectives, audit frequency, hierarchical data governance structure and standardized business processes are key enablers for sustenance of such program. Framework shown in Fig. 5 presents end to end view of contextual approach with necessary processes, concepts, and tools for digital journey of software parts classification and their standardized data definition.

<figure><img src="image_7.png" /><figcaption>Fig. 5. Proposed framework for software part classification</figcaption></figure>

## 4.1 Awareness and Persuasion

The digital journey of classification starts with dissemination of knowledge within enterprise and suppliers to create awareness. The potential adopters who could be at any level in their organization and acquired information from various communication channels. They should first enrich themselves with knowledge from primary and secondary research. Good understanding of the business use cases is essential to highlight the benefits and values that classification brings to the table.
The next step is by persuasion of top management or steering committee to approve business case for designing and implementation of standard coding & taxonomy system for products and services. A strong business case is prerequisite for buy-in from top management. Partnering with right consulting services to conduct interviews, workshops, and survey can trigger learning environment for employees to assimilate knowledge about global nomenclature and classification systems and will expedite overall implementation program. In depth, due diligence by evaluating pros and cons of existing schema with respect to various global schemas will be beneficial. Understanding existing internal processes and data model and analyzing it carefully with the support of experts are required to come up with multiple evaluation criteria. Identify industry best practices and latest trends while defining classification hierarchy.

## 4.2 Design Decision

Harmonization in classification of product and services and associated attributes definition across multiple systems are critical aspects for digital transformation journey of an organization. Standard coding system leads to part data synchronization, process flow integration and data standardization across company divisions, suppliers, and global locations. Identify and define SMART<fnref n="11" /> metrics and set the base levels to be compared after implementation of standardized classification system. Choose few metrics initially which aligns with near term goals as well as with business key performance indicators and perform benefit appraisal just before and after implementation.

It is advisable to kick off the implementation program with PoC (Proof of Concept) to take critical design decisions before full fledge rolling out. Doing part classification project using big bang approach could be risky and may create additional stress in the system. So, it is advisable to have phased approach for design and implementation of the project. Starting with PoC in an agile way with limited data set and few divisions will help to develop methods, frameworks, tools and selection of relevant business technological solutions and IT interventions for large program execution. The aim of PoC is to generate awareness, realization of benefits and return on investment demonstration to reduce organizational frictions.

## 4.3 Transformation

Tools and methods identified in previous steps will be leveraged for scaled agile roll out across divisions, product groups and suppliers. In general, organization product data resides on multiple systems with unique information. IT tools for data extraction automates the process for large volume of data. Based on the type of enterprise system and the situation, it is possible to select the partial or full data model. Extracted data can't be used as it is and needs to go through data wrangling process. The next step of transformation is the classification. Manual approach using statistical methods could suffice if the volumes are low otherwise it is advisable to go for automated classification solutions with quality assurance checks. Artificial Intelligence (AI) based automated classification approach involves training, tuning, model selection and testing using different types of

<footnote n="11">¹¹ Specific, Measurable, Achievable, Relevant, Time-bound.</footnote>
data set. In AI based classification, predominantly, there are 2 steps. First is the fully automated classification step, where ML (Machine Learning) model parameters are generated based on the training data. Next one is the guided automation where some degree of manual intervention required for quality assurance. The final step of transformation is data loading, where classified data is updated into the enterprise systems. If consolidated item master or electronic catalogs already exists because of standardized processes and enterprise applications can skip few steps in transformation.

## 4.4 Sustenance and Continuous Improvement

Continuous evaluation, identification of new use cases, and automation of classification systems are necessary to stay agile, innovative, competitive and remove inefficiency in the system. To retain integrity of the data over time, regular maintenance based on the principles of information asset life cycle management is required [14]. Any modification must be reported through formal change request for analysis and evaluation by change control board of the data governance structure. Updating of existing data set or introduction of new category should follow operational guidelines of implementation. It should be open, flexible, easier to adopt and attract classification of new software-based products and services.

# 5 Summary

In the era of Industry 4.0, where each manufacturing company is looking to extract business value leveraging digital twins; it is imperative to have standardized product data across entire vertically integrated value chain. Harmonized product characteristics and classification not only simplify R&D processes but also streamline procurement, sales & marketing, material management and manufacturing processes. Common engineering language or semantic system facilitates automation of design works to create circuit diagrams, part lists, wiring lists, assembly diagram as well as automation of robotic manufacturing process. Since number and variety of embedded software and firmware are increasing, organization should look for new use cases to support adoption of software part classification. Each of the elements mentioned in the proposed framework needs to be adapted and contextualized as per company needs and could be utilized for classification of other part types as well.

## References

1. Tomás, S.L., Damith, C.R., Bela, P., Duncan, M.: Taxonomy, technology and applications of smart objects. Inf. Syst. Front. **13**, 281–300 (2011)

2. Müllerburg, M.: Software intensive embedded systems. Inf. Softw. Technol. **41**(14) (1999)

3. GMI. https://www.gminsights.com/industry-analysis/embedded-software-market#:~:text=Industry%20Trends,to%20spur%20the%20industry%20growth. Accessed 05 Apr 2022

4. http://www.infoterm.info/pdf/members/strategic_documents/cen ws agreements/cwa_16138.pdf. Accessed 27 May 2022
5. Wolfgang, W., Peter, J.A.R., Laura, E.G.M.: Flexible classification standards for product data exchange. In: Handbook of Research on E-Business Standards and Protocols: Documents, Data and Advanced Web Technologies. IGI Global (2012)

6. ECLASS. https://eclass.eu/aktuelles/broschueren. Accessed 27 May 2022

7. Thomas, T., Sven, A., Christian, K., Ina, S., Gunter, S.: A classification and survey of analysis strategies for software product lines. ACM Comput. Surv. 47(1), 45, Article no 6 (2014)

8. Alberto, P., Jose, D.R., John, S.W.: Beyond the information technology agreement: harmonization of standards and trade in electronics. World Econ. 33(12), 1870–1897 (2010)

9. Elena, C., Orietta, M.: Survivor: the role of innovation in firms’ survival. Res. Policy 35(5), 626–641 (2006)

10. ECLASS. https://www.eclass.eu/en/news/videos.html. Accessed 04 Apr 2022

11. Granada Research white paper: Why coding and classifying products is critical to success in Electronic commerce. Published September 1998, Updated October 2001

12. Mahdi, N., Ebrahim, B., Weichang, D.: Non-functional Properties in Software Product Lines: A Taxonomy for Classification. Published in SEKE 2012. Computer Science, Business

13. UNSPC. https://unece.org/fileadmin/DAM/trade/agr/meetings/ge.11/2005/2005_i04_UNS_PSC.pdf. Accessed 04 Apr 2022

14. Verdantis. https://www.verdantis.com/downloads/whitepapers/adopting-unspsc.pdf. Accessed 04 Apr 2022