Business Solutions: business rules, principles, and best practices Applications: configuration...
13
Business Solutions: business rules, principles, and best practices Applications: configuration management document management product configurators collaboration project management User functions: data vault and document management workflow and process management product structure management classification management program management Utility functions: communication and notification data transport and translation image services administration application integration © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Figure 2.1 A PDM business solution model.
-
Upload
angelina-george -
Category
Documents
-
view
218 -
download
4
Transcript of Business Solutions: business rules, principles, and best practices Applications: configuration...
Business Solutions:business rules, principles, and best practices
Applications:configuration management
document managementproduct configurators
collaborationproject management
User functions:data vault and document management
workflow and process managementproduct structure management
classification managementprogram management
Utility functions:communication and notificationdata transport and translation
image servicesadministration
application integration
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.1 A PDM business solution model.
Design/engineering
Projectmanagement
Manu-facturing
Purchasing
Marketingand sales
Service
Productlifecycle
Customers
Partners
Suppliers
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.2 PDM supporting the whole PLC.
SubmitCheck in
WIPVault
ReleaseVault
Check out
Revise
Worklocation
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.3 Example of data vault usage.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.4 Example of a workflow for change approval.
!WIP vault Work order Designer
Production and inventory control
Manufacturing engineering
Configuration control
Release vault Change review board
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.5 Quantified BOM of a bicycle.
Tire HubSpoke
1 32 1
Saddle
Bicycle
Pedal WheelsHandlebars Frame
1 2 1 2 1
Variants
Revisions
Can
1111 Rev1
Lid
2222 Rev1
Bottom
5555 Rev1Cylinder
Container
3333 Rev1
Cylinder large
4444 Rev1
Cylinder large
4444 Rev2
Cylinder large
4444 Rev3
Cylinder medium
4333 Rev3
Cylinder small
4222 Rev1Cylinder large
Part
Assembly
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.6 Example of different product structures.
Design view
Manufacturing view
Assembly100
Part200
Part300
Part400
Assembly100
Part200
Assembly500
Part300
Part400
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.7 Example of a product structure describing a can with variants and versions.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
PartCylinder large4444 Rev3
SpecificationSpec. large can1321 Rev2
CAD modelLarge can1213 Rev4
Spec_can.doc Can_large.doc
Documents(As business items)
Documents(As data items)
Figure 2.8 Illustration of representation of documents by both business items and data items.
System
*Compress
GPSassembly
GPScomponent
PlatformProductfamily
Variant
Variantgroup
Variantsystem
Basic andstable system
Variantstructure
Selectioncondition
Relativeoccurence
Genericproduct
structure
Implements
Alsoimplements
Class
Generic module element
Productprogram
Aspected system
Mirror image system
Generic productelement
GPSPart
*ProductProgram ID*Classification*UniqueID
*Part number*Revision number
*ProductProgram ID
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.9 Example of an information model.
A
B
B;1
B;2B;1
Revise Check-out
Versions
Check-out
Check-in
Revisions
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.10 Example of the connections between revisions and versions.
The file: desc.doc
Managed files in file systems
Metadata Database
Clients
PDM System
Project: Mobile PhoneObject: DocumentDate: 03-04-24Revision: BDocument #: 1056-ABCFile: h:\PDM\doc\desc.docApplication: MS-Word 6.0
Metadata table
Example of metadata in
one cell in the table
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.11 A PDM system with data vaults.
Workgroup server
Corporate server
Local areaserver
Local areaserver
Workgroupserver
Workgroupserver
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.12 Example of a system architecture in a PDM system.
Workstations Workstations
WorkstationsWorkstations
Corporate server
Site A Site C
Site B
Site A Site C
Site C
Metadatareplication
Metadatareplication
Data
Workgroup server
Data
Local server
Data
Local server
Data
Workgroup server
Data
Workgroup server
Data
Local server
Data
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Figure 2.13 Example of a distributed environment in a PDM system.
