Easy enough with Automations.

Create one with a "When record matches conditions" trigger in your Scanning table, set to fire when "Floor" and "Project Name" are not empty. Then make a Create Record action in your Modeling Table, with your field settings as Name= "Name" (from Scanning), Project Name= "Project Name" (from Scanning). You can also link the Scanning and Modeling records together recursively (I'd use the passed through Airtable record ID).

Thanks @DisraeliGears01 it was easier than I thought!!! Could you explain how to use "You can also link the Scanning and Modeling records together recursively (I'd use the passed through Airtable record ID)." Im lost with the records ID

It's easiest to understand with previews and test steps being modeled. Recursively also might not have been the best word for what I mean.? Regardless...

Basically you can also make it link the newly created modeling record to the scanning record that triggered it's creation. All records inherently have a RecordID, even if it's not visually expressed in your base. When AT automations run, behind the scenes they use that RecordID, and you can use it to specify records. So in this automation (pic included) after the trigger is launched, it creates the new record by copying the name from the Floor field in Scanning, it creates the same project link as the scan record, and then it link the modelling record to it's scan record by RecordID. It's really just if you want to directly link Scanning-->Modeling