Data Entry Technician 3D Fixture Data Migration

Job Overview

The Data Entry Technician will support the migration of Rivian's tooling and fixture information from legacy 2D Excel-based shim logs and fixture images into a 3D modeling/digital-twin application.

The individual will review Excel records and fixture images, locate the corresponding fixture within an existing 3D model, visually verify the information, and accurately enter the required data into the new application.

This is primarily a data migration, visual inspection, and data-entry role, not a CAD design or engineering role.

Key Responsibilities

1. Review Legacy Data

• Review Excel spreadsheets containing fixture and shim-log information.
• Examine embedded 2D fixture images.
• Identify the relevant fixture, shim, component, location, and associated information.

2. Navigate 3D Models

• Open the appropriate existing 3D fixture/digital-twin model.
• Use basic software functions such as:
• Rotate
• Zoom
• Pan
• Select/click components
• Navigate between model views
• Locate the corresponding fixture/component in the 3D environment.

3. Cross-Reference 2D vs. 3D

• Compare the 2D fixture image and Excel information against the corresponding 3D representation.
• Use spatial awareness to determine whether the correct component and shim location have been identified.
• Verify that the information corresponds between the legacy and new systems.

4. Data Migration / Entry

• Enter accurate fixture and shim information into the 3D application.
• Cross-reference fields between Excel and the application.
• Maintain accuracy while processing a potentially large volume of records.

5. Identify Discrepancies

• Identify mismatches between the Excel/2D records and 3D model.
• Flag missing, incorrect, or inconsistent information.
• Document discrepancies for review by the appropriate quality/engineering team.
• Ask for clarification when information cannot be confidently verified.

6. Quality & Accuracy

• Perform careful visual and data checks before completing each record.
• Avoid incorrect data entry or mismatched component information.
• Maintain consistency across migrated records.