Chapter 2: General Description of PDM

Figure 2.1: A PDM business solution model.

Figure 2.2: PDM supporting the whole PLC .

Figure 2.3: Example of data vault usage.

Figure 2.4: Example of a workflow for change approval.

Figure 2.5: Quantified BOM of a bicycle.

Figure 2.6: Example of different product structures.

Figure 2.7: Example of a product structure describing a can with variants and revisions.

Figure 2.8: Illustration of representation of documents by both business items and data items.

Figure 2.9: Example of an information model.

Figure 2.10: Example of the connections between revisions and versions.

Figure 2.11: A PDM system with data vaults.

Figure 2.12: Example of a system architecture in a PDM system.

Figure 2.13: Example of a distributed environment in a PDM system.

Chapter 3: General Description of SCM

Figure 3.1: Basic version control.

Figure 3.2: A bound configuration can be defined by tagging all files with the same label.

Figure 3.3: Developers use different configurations concurrently.

Figure 3.4: Replication of repositories.

Figure 3.5: An example of a CR process.

Figure 3.6: From a CR, it is easy to see which files have been changed (what version has been created) due to the CR. For a specific version of an item, it is also easy to see why this version was created, due to which CR.

Figure 3.7: As part of the release notes, all CRs implemented between the last and the new release are listed. From these CRs, the actual changes made can be traced as depicted in Figure 3.6.

Chapter 4: Comparison of Technical Principles and Key Functionality

Figure 4.1: Server replication in a typical PDM tool.

Figure 4.2: Server replication in a typical SCM tool.

Figure 4.3: Version management in PDM.

Figure 4.4: Version management in SCM.

Chapter 5: Analysis and general findings

Figure 5.1: Hardware development process and information usage.

Figure 5.2: Software design process and information usage.

Figure 5.3: An example of processes and information storage for hardware development.

Figure 5.4: An example of processes and information storage for software development.

Figure 5.5: Product development configurations.

Figure 5.6: Complex PLC.

Figure 5.7: Function overlap in PDM and SCM.

Chapter 6: PDM and SCM Integration

Figure 6.1: PDM and SCM integration—Common API and common repositories.

Figure 6.2: PDM and SCM loose integration.

Figure 6.3: A loose integration using middleware technology.

Figure 6.4: Example of integration of software items.

Figure 6.5: Saving and exchanging data.

Figure 6.6: Check out sequence from PDM into SCM.

Figure 6.7: Check out sequence from SCM into PDM.

Figure 6.8: Relationship between CIs in eMatrix and ClearCase.

Figure 6.9: Architecture ClearCase and eMatrix interoperability.

Figure 6.10: eMatrix and ClearCase client-server architecture.

Figure 6.11: Architecture of distributed systems.

Figure 6.12: Data exchange architecture.

Chapter 7: Evaluation and Deployment

Figure 7.1: The entire process divided in several phases with documentation delivered.

Figure 7.2: Distribution of internal and external costs.

Figure 7.3: Estimated investments and return on investment.

Figure 7.4: Graphical presentation of the fulfillment of functional requirements.

Figure 7.5: Deployment project resources and activities.

Chapter 8: Case Studies

Figure 8.1: The eight phases of Suns structured process.

Figure 8.2: Product approval committees .

Figure 8.3: Phase completion reviews.

Figure 8.4: A transparent interface to SCM tools.

Figure 8.5: The PPDC network architecture.

Figure 8.6: Example of an Ericsson product structure.

Figure 8.7: Generic project organization and roles in a large project.

Figure 8.8: Example of project organization from the PPDC product line.

Figure 8.9: Time-to-market flow for PDC systems.

Figure 8.10: The four different subsystems in PRIM.

Figure 8.11: The baseline content.

Figure 8.12: The CR flow.

Figure 8.13: Overview PPDC information flow.

Figure 8.14: The requirement flow in the product specification phase.

Figure 8.15: Information flow for software and hardware development.

Figure 8.16: Information flow for hardware design.

Figure 8.17: Software program and document library production.

Figure 8.18: Information flow and tools used in the design and manufacturing processes. The following abbreviations are used: Design status (DS), production ready status (PR), design just started (DS-/PR-), ready for preproduction (PR1/DS1), product test doc (PRA/DS4), ready to be sold (PRA), and product revision information (PRI).

Figure 8.19: PDM tool architecture.

Figure 8.20: Modeling the products by rules describing the products.

Figure 8.21: Tools supporting product and document management.

Figure 8.22: Example of a product structure: (a) product structure, (b) product low volume, and (c) product high volume.

Figure 8.23: An example of an article and its constituent parts .

Figure 8.24: CAS system functions.

Figure 8.25: CAS II system architecture.

Figure 8.26: Life cycle model.

Figure 8.27: Overall system architecture and its relationship to the development phase during the product development process.

Chapter 9: A Survey of PDM Tools

Figure 9.1: Different management tools and PDM systems.

Figure 9.2: eMatrix integration solutions.

Figure 9.3: TeamCenter applications in the PLC.

Figure 9.4: Windchill runtime architecture.

Chapter 10: Survey of SCM Tools

Figure 10.1: Development process managed by AllFusion Harvest Change Manager.

Figure 10.2: Rational ClearCase Family products for development projects of different sizes.

Figure 10.3: Multisite management of different branches of a file.

Figure 10.4: Different principles in sharing of data: (a) Object replication, (b) hub-and-spoke parallel development, (c) peer-to-peer parallel development.

Figure 10.5: PVCS tools collaboration.

Chapter 11: Document Management Systems

Figure 11.1: The overlap of DMS and PDM functions.

Figure 11.2: Document life cycle and basic DMS functions.

Figure 11.3: Document container as a unique document.