Data Transfer
Budget: $8 – $15 USD
I'm a skilled PLM and Database engineer, looking for additional help for a time sensitive project. I would interview the candidate and expect to see their resume. You would be required to sign NDB. Rate can be much higher for right candidate and this can go as a long term project. Below is mostly AI generated (Some is true)
I’m preparing to bring a sizeable set of product data from EBS platform into our Aras Innovator instance and need someone who understands both Aras SQL schema and typical PLM data structures inside-out.
The scope centers on a clean, validated migration of all item records—parts, BOMs, documents, and their revisions—so they land in Aras with full relationships intact. You’ll be expected to:
• Analyse the source PLM database and map every relevant table, attribute, and relationship to Aras equivalents.
• Build or refine SQL scripts, import packages, or Aras Innovator AML solutions that automate the transfer.
• Run incremental test loads, reconcile discrepancies, and adjust mappings until the imported data mirrors the source system exactly.
• Document the final migration procedure so my internal team can repeat it for future batches or audit the process later.
Success is measured by:
1. Zero orphaned or duplicated records after import.
2. All BOM levels, effectivity dates, and version histories preserved.
3. A step-by-step migration guide delivered alongside the working scripts.
I’m preparing to bring a sizeable set of product data from EBS platform into our Aras Innovator instance and need someone who understands both Aras SQL schema and typical PLM data structures inside-out.
The scope centers on a clean, validated migration of all item records—parts, BOMs, documents, and their revisions—so they land in Aras with full relationships intact. You’ll be expected to:
• Analyse the source PLM database and map every relevant table, attribute, and relationship to Aras equivalents.
• Build or refine SQL scripts, import packages, or Aras Innovator AML solutions that automate the transfer.
• Run incremental test loads, reconcile discrepancies, and adjust mappings until the imported data mirrors the source system exactly.
• Document the final migration procedure so my internal team can repeat it for future batches or audit the process later.
Success is measured by:
1. Zero orphaned or duplicated records after import.
2. All BOM levels, effectivity dates, and version histories preserved.
3. A step-by-step migration guide delivered alongside the working scripts.