Again,… SketchUp is a 3D model space application. It does not have “sheets”.
But it’s Pro edition companion, is LayOut. In LayOut is where your sheets would reside, and each one of your “sections” 1, 2 and 4 would be a viewport looking into a SketchUp model (“.skp” file.) Your section 3 would be a LayOut 2017+ table linked to a external Excel file.
But Layout does not yet have a “live” automation API, but there is a static C API. The C API can be leveraged from within SketchUp’s Ruby process (because the Ruby language is implemented in C.)
So things can be automated from within SketchUp (but only during “.layout” file creation,)… think clicking a button and an extension creates the new LayOut file, sets up the sheets, creates the viewports (“sections”) linking them to the SketchUp model(s), and the external Excel sheet.
Sections 1, 2 and 3 are no problem. 4 can be basically setup without issue, … but …
I will not guarantee, that there will not be some manual work within the LayOut file afterward. Ie, the labeling of parts (callouts) in section 4. I am not sure can be done automatically. Perhaps yes, if the callouts already exist in the template, and can be identified by attribute, and that attribute mated with a line item in the Excel worksheet.
But you will need to develop this functionality, or hire someone to do so for you. This kind of specialized workflow is not part of the core feature set of SketchUp/LayOut (yet.)
For an example of a SketchUp extension that creates a LayOut file with each model scene page imported as a viewport on a separate sheet, see the link in this topic thread:
[Create LayOut File from Scenes] talk, bugs & feature requests