Check the asset data drop before handover

Open the model and list the assets it holds with the data attached to each, from make and model to serial, warranty and the maintainable-item flags the operator needs.

เหตุผล: You cannot check data you have not looked at. Reading straight from the model is what shows whether the designer's promise of a data-rich handover survived into the file you were actually given.

Run each asset's properties against the required set, flag the blanks and the wrong formats, and log the failures back to whoever owns the model to fix before handover, not after.

เหตุผล: Handover is the last moment you have leverage to get the data fixed for free. A defect list raised now is corrected by the delivery team; the same gap found next month is your problem to chase and fund.

Bring the assets that passed the check into the register with their data intact, and hold back the ones that failed until they are corrected, so the register never inherits a known-bad record.

เหตุผล: The register is what the whole FM operation runs off, so a bad record there spreads into every work order and report. Loading only the passing data keeps the single source of truth actually trustworthy.