An information integration modelling architecture for product family life cycle in mass customisation

Defining one product data for a product

“…Sales package description of sales item combinations (Baghdadi, 2014;Kropsu-Vehkapera, 2012; Kropsu-Vehkapera and Marketing & sales plan; customer demand (Cooper, 2001;Li et al, 2011;Pan et al, 2014;Tao et al, 2017) Marketing and sales material (commercial and (Cooper, 2001;Kropsu-Vehkapera, 2012; technical) & their legal approvals Saaksvuori and Immonen, 2008;Kropsu-Vehkapera and Haapasalo, 2011) Product/service pricing and customer deal instructions (Cooper, 2001;Baghdadi, 2014;Kropsu-Vehkapera, 2012;Saaksvuori and Immonen, 2008;Sajadfar et al, 2014;Sharma and Shah, 2015) Launch plan for commercial partners (Cooper, 2001) Promotion and launch material (Kemppainen, 2010) Customer requests for product improvements (product change requirements) (CIMdata, 2002) Configuration Configuration guidelines: recommended configurations, marketing/sales limitations, properties and features, customer-specific configurations, price/cost information (Do et al, 2002;Kropsu-Vehkapera, 2012;Saaksvuori and Immonen, 2008) Pre-set configuration rules (Jinsong et al, 2005;Li et al 2016;Saaksvuori and Immonen, 2008) Delivery times and sales channels for saleable products (Kropsu-Vehkapera, 2012;Silvola et al, 2016;Tu et al, 2006) Specific customer discounts (Customer contracts as a reference) Internal product guidelines, system and realisation for reconfiguring products (Kropsu-Vehkapera, 2012;Kropsu-Vehkapera and Haapasalo, 2011) H3: Product data requirements for marketing and sales can be divided into sales & marketing, configuration and sales support. Opportunities for swift access are emphasised in the marketing and sales context.…”

Progressive modelling of feature-centred product family development

“…Therefore, a flexible information model is crucial for the systematic development and deployment of product families during all life phases of product (Nanda et al 2007). To capture, manage, share, reuse and integrate product family knowledge, Xu, Ong, and Nee (2007) initiated a product family design reuse (PFDR) process model; Nanda et al (2007) proposed a flexible knowledge management framework which is called a networked bill of material (NBOM) using formal concept analysis (FCA); Ki Moon et al (2009) presented a methodology to develop a service ontology for capturing and reusing design knowledge in a service family; Moon, Simpson, and Kumara (2010) proposed a methodology of integrating an ontology and data mining for knowledge discovery of product family; Lim, Liu, and Lee (2011) proposed a multi-facet product family ontology framework to search and retrieve information of product family; Pan et al (2014) put forward an information integration modelling architecture for product family life cycle (I 2 MAfPFL); Giovannini et al (2016) applied an anti-logicist approach for the unambiguous design-knowledge representation during a product family design stage; Lundin et al (2017) explored the computer-aided technologies (CAX) to capture and represent reuse knowledge of product families.…”

“…Modelling the evolution of a product family is critical for satisfying customer, improving performance, reducing manufacturing cost and minimising risk (ElMaraghy et al 2013). With the time changes, the main driver of PFE is adaptation such as the new requirements, the new regulations, and/or the availability of new technology (Pan et al 2014;Martin 2000), and the family redefinition, restructuring and perfective maintenance have an important effect on the change of product family (Lam 1999).…”

“…The issue of knowledge management in product family design, that is related to an effective storage, sharing and timely retrieval of design reasoning and evolution information, has become more complicated and challenging (Lim, Liu, and Lee 2011). At the same time, the main structure of a product family is dynamically and constantly evolving along with the changes of market conditions and customer demands as time goes on, which is a spiral process (Pan et al 2014). The time-dependent product family evolution caused by dynamic environments is shown in Figure 1.…”

“…The typical product family model is an architecture-and-units model describing which modules (Erens and Verhulst 1997) or units (Pan et al 2014) are part of the product family model and how they can be combined in the product family architecture. Thus, most studies focus on the product family architecture and unit information.…”