| NESTech > CAD SERVICES > CAD DATA MIGRATION |
|
||||||||||||||||||||||||||||||||||||||||||||||||||
|
Data Migration |
SAMPLES... | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
NESTech customizes the data migration process for each customer's specific requirement. NESTech's custom data migration projects create consistent models that incorporate the original design intent of your design. This makes future redesign steps easier, and the reusability of your 3D CAD data can dramatically shorten the design cycle for new products. You can expect to save time and money while gaining a competitive advantage in your industry. Benefits from our services:
Legacy CAD database migration is not an automated process. Models have to be created or rebuilt incorporating design intent step by step. Now you have an opportunity to have this data converted to your CAD platform of choice at a price you can afford, and in a timeframe that is realistic. NESTech engineers can take your products from paper drawings through 3D modeling to complete manufacturing solutions, while your engineers continue to focus on on-going projects. NESTech specializes in efficient, intelligent CAD data conversion. We combine high-caliber engineering talent, customized specifications, secure data environments, and a global infrastructure to provide best-in-class solutions.
Incorporation of Standard Procedures in Data Migration ProjectsGeneral Modeling and Documentation MethodologiesCompanies implementing CAD Software must develop and document standards and methods for the use of CAD Software. There will be a lot of interaction between CUSTOMER and the NESTech consultants during the development of these company standards. The goal is to have a pre-thought-out method for modeling each item so that the following conditions are met:
Numbering schemesEstablishment of a numbering scheme is of major importance internal tracking of drawings within CUSTOMER, also for designing in the CAD Software environment. Because of the associativity of CAD Software files, unique names must be assigned to parts, assemblies, drawings, family table instances, etc. In addition, the numbering scheme can actually be a way of categorizing files that can be later tracked in PDM. This categorization of parts and assemblies will help to eliminate duplication of design effort. Authorization and revision proceduresAccess to the database can be controlled by setting authorizations for access to files. Revision history is automatically tracked which includes the date of the change; the user who made the change as well as a host of other information that can be tracked. Files can be promoted or demoted to different release levels such as release for manufacturing or release for preliminary design. These procedures should be established early in the project so that information can be tracked from the earliest portion of the design cycle. Formats and drawing conventionsFormats and drawing convention should be established early in the project. Information can be added to the parts and assemblies in the form of “parameters” that can later be automatically added to the drawing format. Information such as designer, drawing creation date, and revision level of the part are all information that can added to the drawing automatically when the user identifies which part or assembly he is making a drawing of. Drawing conventions, such as standard text heights, dual dimensioning, arrow lengths, etc. can be controlled from one location so that drawings will be created to CUSTOMER specifications. Automatic BOM’s are able to be displayed in customized formats.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
© NESTech, HOME | SITE MAP | DISCLAIMER | PRIVACY POLICY |