Abstract In response to rapidly changing market and customer needs, product design and development (PDD) is evolving into a human-centred and data-driven design paradigm. The design environment gets more open often involving crowdsourcing and the design process becomes more complex, considering product family design along product whole lifecycle development, and needing more data support. Therefore, it is critical to effectively capture, share, and manage design-related information in such a complex design environment. From this perspective, it is a prerequisite to have a proper product design lifecycle information model (PDLIM) to guide information gathering, sharing and management. To the best of our knowledge, currently, there lacks such a PDLIM to support effective PDD, though digital twin (DT) technology shows a great potential of supporting product lifecycle information collection and management. In this paper, the overall structure of the proposed PDLIM is firstly developed to frame in all main product lifecycle stages and the corresponding key phases for structurally capturing and storing necessary data along a product lifecycle. Secondly, key design information items against the main product lifecycle stages and their corresponding key phases are explored from literature reviews and case study analyses. Thirdly, the necessity of the identified information items in the PDLIM is qualitatively evaluated by two case studies. Finally, the PDLIM is further evaluated by applying formal object-role modelling (ORM) to demonstrate how design information items are used and interacted in exemplary design interaction scenarios, and to approve that it can be formally described and managed as an information model. The evaluation results show that the PDLIM is feasible to be adapted in a crowdsourcing-combined PDD process for supporting design management, reviewing, quality control, and next round product redesign and improvement.
Addressing the Data Discontinuity in Product Design
Traditional product design and development (PDD) is often siloed. While standards like STEP (Standard for the Exchange of Product Model Data) are excellent for sharing 3D geometry and manufacturing specifications, they often ignore the "why" behind design decisions, early-stage market research, and real-world user feedback.
As we move toward Product Family Design, Crowdsourcing, and Digital Twins, the information environment becomes increasingly complex. Data gets fragmented, proprietary knowledge is lost between generations, and designers lack a "single source of truth" for the entire lifecycle. The proposed Product Design Lifecycle Information Model (PDLIM) tackles this discontinuity by treating lifecycle data as a continuous, iterative loop rather than a linear path.
Research Methodology
The researchers developed PDLIM through a systematic six-step process, moving from structural development to formal modeling and validation.
- Structural Development: Mapping the model to five key lifecycle stages: Pre-design (S1), Design (S2), Manufacturing (S3), Launch & Use (S4), and Maintenance & Recycling (S5).
- Information Extraction: Reviewing literature and 51 historical case studies to identify specific "information items" required at each stage.
- Conceptualization: Treating the model as an "information wardrobe" where each "drawer" represents a specific design phase for incremental data storage.
- Formal Modeling: Using Object-Role Modeling (ORM) to describe relationships between entities (designers, tasks, feedback loops) to ensure database compatibility.
- Validation: Testing the model against case studies to ensure it handles both traditional in-house design and complex, multi-generational product families.
The PDLIM Framework
The core of the PDLIM is its ability to capture and connect data across the entire product journey. It acts as a structured repository that bridges the gap between the physical and virtual parts of the product lifecycle.
Unlike older models, PDLIM explicitly includes structures for crowdsourcing environments, defining roles for requesters, crowd designers, and evaluators. It also treats Digital Twins as a specific data source, providing high-fidelity, real-time performance data that feeds directly back into the "Information Repositories." This formalization of backward information flows ensures that data from the "Use" and "Maintenance" stages informs the "Pre-design" of the next product generation.
Validation through Case Studies
The study relies on two distinct case studies for validation:
- Case Study 1 (Food Processor): A project used to evaluate the model's ability to capture early-stage design intent and "soft" data like personas and sketches.
- Case Study 2 (Mobike/Dockless Bikes): A real-world analysis of four generations of bike-sharing systems. This tested how PDLIM manages information flow between generations, such as how maintenance data from Gen 1 (e.g., issues with bevel-gear weight) directly triggered design requirements for the chain-driven Gen 2.
Key Results and Insights
The ORM modeling proved that PDLIM can be formally described and managed as a database, making it feasible for implementation in PDM/PLM (Product Data/Lifecycle Management) systems. Qualitative evaluation suggests that by providing a "big picture" of structured information, PDLIM reduces the time designers spend searching for data and helps prevent the "reinventing the wheel" syndrome in product families.
Limitations and Future Work
Several hurdles remain for widespread adoption. PDLIM is currently a conceptual and formal model; the next step is developing a fully functional software management system that integrates with existing ERP and PLM tools. Additionally, future work must address Intellectual Property (IP) concerns in crowdsourcing environments and incorporate AI to automatically summarize the massive volume of data generated by Digital Twins into actionable insights.
Summary updated