1 / 17

Gene Perry gperryna-ips

At Integrated Partner Solutions, Inc., our mission is to provide Best In Class Products and Unparalleled Services, while increasing your productivity. When you establish a working relationship with Integrated Partner Solutions, Inc., you will be our

ray
Download Presentation

Gene Perry gperryna-ips

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    2. At Integrated Partner Solutions, Inc., our mission is to provide Best In Class Products and Unparalleled Services, while increasing your productivity. When you establish a working relationship with Integrated Partner Solutions, Inc., you will be our #1 priority. Our dedication to you will improve your total process, while your trust in us will ensure that you have the Best Products and Services available. About US

    3. Trusted Resource If you have not implemented the selected PDM, please do not attempt to take this on without a support resource. Too many headaches. Expedite the entire process. The resource must be knowledgeable in many areas: SolidWorks (and other CAD applications) Microsoft Networking (32-bit vs. 64-bit) SQL Server (database management 32-bit vs. 64-bit) API (programming experience) Accessibility (conference call and web-conferencing).

    4. Trusted Resource Avoid a resource that answers questions about their competition. Resources should only be speaking and representing their applications to the best of their ability, but unfortunately they will sometimes revert to (FUD – Fear, Uncertainty, and Doubt) about their competitors. Resources should only focus on their positives… Try to avoid over-purchasing (purchasing because of a feature that is not a requirement from your list): Follows the food shopping rule (don’t shop when you are hungry or without a shopping list).

    5. PDM Application Create a minimum requirements list for your environment: Can adapt to your environment changes (workgroup to enterprise) SolidWorks AutoCAD Word, Excel, PDF, … Web Access – supported interface ERP/MRP/SAP integration support Distributed Site needs and methods Must have an open and published API: Fact is, each organization has its own rules to accommodate.

    6. PDM Application Look for a solution that is open (not proprietary). Understand that there is no single PDM/PLM application that is correct for the entire world. For larger environments, the PDM/PLM application is a long-term investment that will likely be inheriting customer specific changes on a regular basis. Applying controlled modifications for the benefit of the organization is a good thing because you are getting more out of your investment. The rules you develop, define the boundaries for the “Complete PDM/PLM Application” for your organization’s needs.

    7. Infrastructure Considerations Network: Performance of the network infrastructure. Security within the network (LAN and WAN). Site specific considerations (WAN). Non-engineering workstations (view and print). Servers (Windows): Existing vs. new file servers. Existing vs. new database servers. Workstations: Are the engineering computers out-dated for today’s applications? Stability (64-bit with 8GB of memory).

    8. Investment Application: Training (Administration vs. User). Services: Legacy data management (easy to underestimate the complexity of handling the legacy data – “crap-in/crap-out”). Customer specific needs (Part Schemas, Revision Schemas, etc.). Your time to test/validate the results. Implementation. Network peripherals may have to be considered (WAN – distributed sites). Servers (Files vs. Database). CAD complient Workstations for engineering (non-engineering workstations).

    9. Fields Separate the data into appropriate fields: Part Number (referenced in multiple locations, TitleBlock, BOM, Tree, etc.). Description (referenced in multiple locations, TitleBlock, BOM, Tree, etc.). Revision (referenced in multiple locations, TitleBlock, REVISION TABLE, etc.). Material (referenced in multiple locations and can be inherited SolidWorks property). Custom Properties can be imported and/or written to. ERP/MRP/SAP (field length/type if synchronized) Envelope address, GPS, and phone books are all examples of how fields are used for specifying criteria.

    10. Schemas Save-As Schema: Next available part number generation vs. part number generation based on a category/classification. Smart vs. partially-smart Part Numbers. Configuration management (single file representing multiple part numbers). Model ? Drawing inherited relationships. Model ? non-CAD file inherited relationships. Physical File Name and Folder Name (path location) of files. Display within the SolidWorks Tree. Revision Schema Major/Minor Sequence. Promotion process (Alpha, Beta, Production, …).

    11. Schemas BOM Schema (essentially a report): SolidWorks Models DWG files Phantom/Fake Components Make/Buy field implications/control (BOM, No Expand, No BOM Item, etc.) Global vs. Local implication/control. Accommodate quantity changes (washers, rivets, etc.). Accommodate unit of measure changes (FT, EA, etc.).

    12. Schemas Workflow Schema (repeatable procedure with triggers and notifications): Keep it as simple as possible. Separate conditions for an ECR vs. and ECO. Separate conditions based on the file type (Model, Drawing, Excel, …). Separate conditions based on the design intent (Mechanical vs. Electrical components). CAD users vs. non-CAD users that participate in the workflow approval process. ERP/MRP/SAP connections.

    13. Beyond Engineering Within your organization, who needs access to the engineering data and what type of data do they need access to? Native CAD file access (be careful with configurations which mandates a knowledge of SolidWorks). Converted files (DXF, PDF, e-Drawings, etc.). Local access vs. web-based access. Where Used and Used By references. BOM data. Workflow (ECR and ECO) functionality. Projects (equipment type, sales order, etc.) for searching – reference any electronic shopping cart experience, like Dell/HP. ERP/MRP/SAP data entry (data authorization).

    14. Common Legacy Challenges Duplicates: Same File Name in different folders: May or may not be the same exact file. Different physical file names, but an exact copy. Configuration references within the SolidWorks file only complicate the entire issue (multiple “Default” references). File Paths: The FILE_NAME means very little to a PDM application. The FILE_PATH means very little to a PDM application. Ratio of FILES to FOLDERS should be established for performance considerations only: Not recommend to save 30,000 files into a single folder. Not recommend to create a new folder for almost every file.

    15. Legacy Challenge Solutions IPS developed and/or proven tools for success: Scan for all duplicates (provide visibility). Read all related PATHS into a table: Separate the FILE_NAME from the FOLDER_NAME. Read all SolidWorks Internal References into a table. Separate the FILE_NAME from the FOLDER_NAME. Export all inconsistencies to Excel: Allow team to update the Excel file to host legitimate data. DataStream (reading updated data from the Excel file and applying changes to mapped database tables/fields). Rename: Move files and folders as needed. State (Approve, Check-In, etc.).

    16. Generic File Promotion Maintain your revision history which includes your legacy Generic Documents

More Related