Yes, this is a very common workflow. the standards approach is to set up a dataset with a 1-M relationship. Aka Parent + Related table. The parent table with unique features is your assets and any 'static' data such as asset ID, date first installed. The related Many table is to record inspections against this asset.
You could create the dataset initially using Survey123 Connect with a repeat, or use an existing layer with a 1-M relationship i.e. published from ArcGIS Pro.
You then create a (second) survey from the existing feature layer, but only target the related table. This means removing the XLSForm rows for the parent table and the being /end repeat.
To maintain the relationship you can generate custom URLs. This could be done from a web map pop-up, or configured some other way (barcode, QR code, email). The URL should pass the parent table globalid into the related table parentglobalid field to maintain the relationship for that asset. You could also pass any other data as desired.
There's a dated but fundamentally sound video on this here:
https://youtu.be/vECznnoJHGk?t=2565
The user makes a survey for water assets (roughly timestamped above) and then a second survey targeting only the repeat at the timestamp below
https://youtu.be/vECznnoJHGk?t=3925
Worth noting that photos can be a little difficult to access if they're attached to the related table instead of the parent, so you may want to consider and test this in a trial build.
If your equipment is mobile, you could set up geometry in the repeat as well to help with tracking and the above. Just consider how this data will look