what is recPLM?
Origins of recPLM.
recPLM originates from dozens of years of product development methodologies deployment in very different domains and industries and supports virtually any way of developing products: Agile, Iterative, Waterfall, ….
recPLM is putting requirements in the center of the field of any complex product development. A requirement is any product’s characteristic that need to be present in the product so it satisfies all its stakeholders’ needs. Exhaustive forward and backward product characteristics traceability is key to recPLMto provide a sound structure for product changes and problem solving.
recPLM is taking a wide view on the product development as it is encompassing companies’ departments such as: Marketing, Sales, Design, Engineering, Quality, Compliancy, Production, Sustaining, Legal, …..
recPLM is a methodology targeted towards all product development actors (NPD/NPI):
- Company’s top management
- Marketers as the users proxies, Product Manager, Sales persons
- Designers, Architects, Engineers, Product Developers
- Project Managers, Compliancy managers, Testers
- Customer Service and Sustaining teams
In contrary of traditional Requirements Management approaches, recPLM consider that creating requirements, linking requirements between them should not be a task of a “requirements engineer” embedded in a project but it should be all NPD/NPI’s actors responsibility and furthermore their core work.
Thanks to recPLM, all the actors of product development are working on the single source of truth. Clear ownership, responsibility, accountability on products’ features and characteristics are therefore one of the benefits of the application of recPLM.
The power of recPLM is that all these NPD/NPI actors are using the same language and artefacts at high level while using their domain language and related artefacts for the internal details of their contribution to the product.
Layers in recPLM.
recPLM recognies three important layers in product development where critical design decisions are made and resources are committed:
• Business layer • Product specification layer • Architectural layer
The Business layer (red level) allows the development to constantly focus on the real needs of all product stakeholders by understanding what they are trying to achieve in real life situations. Requirements originating from the Business layer are typically owned by the company’s top management and could be delegated to the Marketing department and/or Design as users proxies.
In the context of a product concept, the Product specification layer (green level) is defining how the product stakeholders’ needs are satisfied when interacting with the product. The Product specification layer is under the responsibility of Product Management.
Architectural layer (blue level) defines the complete solution (logical functions and physical designs ). The scope is not limited to the physical product, as it is traditionally the case, as it covers also the production, service, delivery, marketing, … means. The Product architect owns the top level of this solution layer and collaborates with the top-level sub-systems owners for making sure that the top-level sub-systems implements the product requirements completely.
More than requirements.
recPLM is mainly about requirements but not only requirements as it covers in a consistent and strong linkage, testing and risk analysis in the above layers.
recPLM is consistent and complements standards such as IREB, BABOK (IIBA), SE Handbook (INCOSE).
recPLM is also a framework.
recPLM is a framework where advanced techniques such as the ones promoted by PPAP, QFD, Lean, Six Sigma, 5S (5C), 8D or Problem Solving approaches are nicely fitting and plugged into like FMEAs, Fish bones diagrams, 8D, Pareto, HOQ, ….
recPLM provides a dedicated support for Management and Engineering of : Requirements Risks Tests and interactive and dynamic links with all others traditional PLM areas.
recPLM supports your company ‘s journey to satisfy international standards and regulations such as ISO 9001:2015; ISO 13485; ISO/IEC/IEEE 15288:2015; ISO 14001; IS 14971; ISO 16949; SPICE; CMMI
Tools and recPLM.
recPLM is implemented within or compatible with the most common leading PLM tools.
As an example, recPLM is available as a plugin to Aras Innovator which does not change its core PLM data model. It just complements it by providing a sound methodology for all actors of the product development process.
Arena PLM, Siemens/TeamCenter, PTC/WindChill, Dassault/Enovia, Oracle/Agile, …
Please contact us to discuss how these tools can accomodate recPLM.
Traditional requirements management tools: e.g. DOORS, Visure, Polarion, HP/QC/ALM; Blueprint, …
Please contact us to discuss how these tools can accomodate recPLM and interface with PDM/PLM tools.
MS-Office tools: Word, Excel, Powerpoint
MS-Office tools are the most widely tools used for NPD/NPI. recPLM can be easily implemented on this tool as a first PLM deployment phase.