powered by CADENAS

Manual

Manual

Chapter 3. Guidelines / Most important - CADENAS Design Manual (CDM)

Table of Contents

3.1. Introduction
3.2. General rules
3.2.1. Naming of catalogs (physical name - display name)
3.2.2. Definition of catalog Company key (license key)
3.2.3. Renaming of existing catalogs
3.2.4. Use of PARTproject QA SVN
3.2.5. Folder Structure of catalog in PARTproject
3.2.6. Copy projects
3.2.7. Translation of catalog / Default column
3.2.8. Preview Pictures in Folder Structure
3.2.9. Pictograms in table
3.2.10. No units in table
3.2.11. Technical Previews (PRA)
3.2.12. Classification by Category / Alphabet / Country
3.2.13. Automatic Classification of standardized Parts
3.2.14. Special labeling of catalog with icons
3.2.15. Copyright Project
3.2.16. Set Up Tag Cloud Exclusion
3.2.17. Classification according to CNSORDERNO / CNSTYPECODE
3.2.17.1. Use of CNSORDERNO and CNSTYPECODE with examples
3.2.17.2. Limit resolving of value ranges (yellow fields) via config key
3.2.17.3. Index order numbers dependent on value ranges
3.2.17.4. "Adjust order number and type code" Plugin
3.2.17.5. "Resolve check" Plugin
3.2.17.6. TestMeta: General for Order number or Typecode
3.2.17.7. TestMeta: ReverseConfigs
3.2.17.8. Benefits of classification according to CNSORDERNO and CNSTYPECODE
3.2.18. Release Notes
3.2.19. Materials
3.2.20. Render attributes
3.2.21. Insert Chamfer/Fillet... using the Blend Feature
3.2.22. Quick & Simple catalogs
3.3. Quality
3.3.1. Quality Demand
3.3.2. Software Training
3.3.3. Specification Workshop
3.3.4. Creation of Pilot Parts
3.3.5. Use of PARTproject QA SVN
3.3.6. Manual Test Instances
3.3.7. Standardized Check Protocols
3.3.8. Electronic Test Run (TestMeta)
3.3.9. Release by the Contractor
3.3.10. Administrative Final-Checking
3.3.11. CIP Release Check
3.3.12. Innovation Workshop
3.3.13. QA Seal
3.3.14. Corrections in the published catalog
3.3.15. QA Workflow
3.4. ERP
3.4.1. Identification type
3.4.2. Add ERP-Mapping... / Edit ERP-Mapping...
3.4.2.1. Change of folder structure, project names and paths
3.4.2.2. Deletion of projects
3.4.2.3. Change and new creation of tables
3.4.2.4. Rename of value range variables
3.4.2.5. Change of value range contents
3.4.2.6. Value ranges as „name of values“
3.4.2.7. Change of NBs
3.5. Architecture
3.5.1. General
3.5.2. Supported Systems
3.5.3. Characteristics
3.5.4. LOD
3.5.5. Classification
3.5.6. TestMeta
3.5.7. Advanced Tests
3.6. Simulation
3.6.1. General
3.6.2. Supported Systems
3.6.3. Simulation - Specification for Mechatronics Concept Designer (MCD)
3.6.3.1. Rotative and linear simulation (MCD)
3.6.3.1.1. Example for a linear simulation with a FESTO ADN compact cylinder
3.6.3.1.2. Example for a rotative simulation with an AFAG RE-50 rotary module
3.6.3.1.3. Test the simulation in the Mechatronics Concept Designer
3.6.3.2. Simulation for Sensors and Conveyor belts (MCD)
3.6.3.2.1. Conveyor belts
3.6.3.2.2. Sensors
3.6.3.3. Limits of joints (MCD)
3.7. Electronic
3.7.1. General
3.8. Plant Design
3.8.1. General
3.8.2. Supported Systems
3.8.3. Characteristics
3.9. Specification Data Supply