Product Network Manager Integrating PLM and Requirements Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Product Lifecycle Management (PLM) systems and Requirements Management (RM) systems fail to effectively integrate 'why' or 'intent' data with 'how' or 'content' data, leading to workers making decisions that may not align with the overall organizational objectives, and lack automation in managing complex day-to-day organizational activities.
Innovation Solution
A Product Network Manager (PNM) system that integrates a PLM with a requirements management system, using a networked database and existing infrastructure to provide users with a unified view of both content and intent data, allowing for the presentation and editing of requirements trees across the organization, enhancing decision-making consistency with high-level organizational premises.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If PLM systems use data translation middleware to extract data from departmental software, then data accessibility across departments is improved, but system complexity increases
Solution Approach 1:
The patent employs a requirements management system as an intermediary layer between PLM and other enterprise systems (ERP, CRM, SCM). This intermediary captures, structures, and manages requirements data in a standardized format that can be shared across departments, improving data accessibility while managing system complexity through standardized interfaces and data models.
2Productivity
If PLM systems collect multi-source data from various departments, then organizational effectiveness is improved, but difficulty in aligning with high-level requirements increases
Solution Approach 1:
The patent segments requirements into a hierarchical tree structure with high-level requirements at the top and detailed sub-requirements branching downward. This segmentation allows organizations to maintain visibility of high-level objectives while managing detailed operational requirements, ensuring that multi-source data from various departments remains aligned with overarching organizational goals.
Solution Approach 2:
The requirements management system provides feedback mechanisms that trace requirements throughout the product lifecycle. By linking requirements to specific projects, tasks, and deliverables, the system continuously monitors and reinforces alignment between operational activities and high-level organizational requirements, preventing drift even as organizational effectiveness increases.
3Adaptability or versatility
If requirements management is manual in complex organizations, then flexibility in handling unique cases is improved, but time consumption increases
Solution Approach 1:
The patent implements a dynamic requirements management system where the requirements tree can be easily modified, expanded, and reorganized as organizational needs change. The system allows for flexible addition of new requirements, modification of existing ones, and dynamic reassignment of requirements to different projects or departments, providing adaptability while maintaining structured management through automated workflows and tracking.
Data Source
AI summary
The invention is directed to an integrated computerized product lifecycle manager and requirements manager system for associating high-level requirements data with everyday product lifecycle management activities. The system includes a networked database comprised of one or more central computerized data servers, and a plurality of user computers (terminals, workstations) connected to the central server or servers by a computer data network. The server or servers will usually run multiple software modules such as database modules, various product lifecycle management modules, data viewer and decoder modules, and requirements management modules all operating in an integrated manner so that selected portions of the requirements tree, from the top high-level requirements to more detailed low level requirements, can be presented to users in a context relevant manner. The invention additionally includes context management module by which selected portions of the requirements data may be exposed or redacted according to organizational needs.