220 likes | 417 Views
KP3213 CAD/CAM. Snapshot Lecture 4 3D Transformation Objective of Lecture 5 Understand Product Data Management Lecture 5: Product Data Management Class on 6 August 2007 is shifted to 7 August 2007, DK4, 11am-12pm. 3D Transformation. 3D Transformation. Assignment # 2.
E N D
KP3213 CAD/CAM • Snapshot Lecture 4 • 3D Transformation • Objective of Lecture 5 • Understand Product Data Management • Lecture 5: Product Data Management • Class on 6 August 2007 is shifted to 7 August 2007, DK4, 11am-12pm.
Assignment # 2 An object in space is rotated by 90 degrees about an axis that is parallel to the x-axis of the worlds coordinate system and passes through a point having coordinates (0,3,2). If a point on the object has model coordinates (0,1,1), what will be the world’s coordinates of the same point after the rotation. Due: 7 August 2007.
Team-based Design • Most product development is done by multi-disciplinary design teams • Team members must communicate and share information throughout the design process • In the past, CAD tools were used by individual designers • CAD/CAM tools must support team-based design
Issues in Team-based Design • Easy sharing of product data • Access control • security • data consistency and integrity • Version management • Workflow and coordination • Support for steps in process
Private Vs. Shared Data • Private data • individual, preliminary work • similar to private notebook • model files stored in private user directory • Shared data • data available to all team members • similar to shared team binder • data stored in shared repository
Private Data in I-DEAS • Individual projects • model files in user directory • workbench • bins • parts
I-DEAS Model Files Bins Parts Model File
Team “Projects” in I-DEAS • Team projects keep everything in one place • Private data is still private • Data is shared through Libraries
An I-DEAS Project Library Catalog Model file Model file Library Catalog Model file Library Model file Project
Libraries • Libraries are shared databases • Parts, assemblies and drawings must be put in libraries to be shared with the team
Putting Data into Libraries • To share data, it must be checked into the library • Several options: • check in, keep to modify (others can copy and reference, but can’t change it) • check in, keep copy (others can copy and modify it) • check in, keep reference (others can copy and modify) • check in, don’t keep • Once available, others can access it in several ways
Accessing Data in Libraries Users can access data in library several ways: • Check out • Check out to make modifications. Only one user can check out a part at a time • Reference • Cannot change referenced data, but reference will update if original is modified • Copy • Makes an unassociated copy, which can be changed as desired
Version Control • Every time a part is checked out, modified and checked back in, a new version is created • All previous versions are also stored • These can be associated with product revision numbers
Catalogs • Catalogs are libraries for standard parts or features • Parts can be stored in parameterized form • e.g., different sizes of fasteners
approved approved ECO ECO Initial Pre-release Released A Team Project
Configured Projects Configured projects permit: • Assignment of team members • Definition of roles • Assignment of members to roles • Definition of states • Item access rights
Industrial Designer Engineer Marketing Manager Assignments Roles Members Members and Roles
Preliminary work, dynamically changing Initial Approval Redesign Reviewed, checked and approved Few changes Pre-release ECO Approval Final design, frozen and released to manufacturing Final Release States
Item Access Rights • Restrict access to authorized people • Access rights depend on project state • Assign appropriate permissions: • no access • read only • read and copy • read, copy, write, delete • read, copy, write, delete, approve